next-translate Cannot find module './locales/en/common.json'

I am trying to integrate the next-translate library into my Next app, however I am getting an error when configuring the loadLocaleFrom function
This is what my i18n.js file looks like:
module.exports = {
  locales: ["en", "fr", "es", "ru", "ar", "zh", "hi", "sw"],
  defaultLocale: "en",
  pages: {
    "*": ["common"],
    "/": ["home"],
  },
  loadLocaleFrom: async (lang, ns) => {
    try {
      const m = await import(`./locales/${lang}/${ns}.json`);

      return {
        ...m.default,
      };
    } catch (error) {
      console.log(error);
    }
  },
};

And my next.config file:
const withPlugins = require("next-compose-plugins");
const withImages = require("next-images");
const nextTranslate = require("next-translate");

module.exports = withPlugins([withImages, nextTranslate], {
  reactStrictMode: true,
  images: {
    disableStaticImages: true,
  },
});

package.json versions:
next-translate: ^1.5.0
next: 12.1.6
react: 17.0.2

Even though my directory has both, the common.json and the home.json files in the correct folder structure, the loadLocaleFrom function still throws an error that looks like this:
Error: Cannot find module './locales/en/common.json'
    at webpackEmptyContext (D:\projects\mk\mk-academy\.next\server\pages\index.js:529:10)
    at eval (webpack-internal:///./i18n.js:64:89)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.loadLocaleFrom (webpack-internal:///./i18n.js:63:23)
    at async Promise.all (index 0) {
  code: 'MODULE_NOT_FOUND'
}

I did try using the appWithI18n hoc in _app.js but that doesn't solve it too. I also did try moving the locales to a different directory under src but that shouldn't make a difference.

@salmanfazal01 first try printing the path which you construct. Maybe something not properly generating the path hence it cannot find the correct file. I'm talking about this part of your code ./locales/${lang}/${ns}.json

Turns out import didn't work for me but require did. Took me a while to figure this out
await require(./locales/${lang}/${ns}.json)

Don't use require, it increases the bundle size... We are searching for a good solution, but for the moment I recommend this workaround to don't increase the bundle sieze: https://github.com/aralroca/next-translate/issues/851#issuecomment-1173611946
Any feedback for a solution to this will be very welcome! Thanks!


Jest support for NativeScript + Angular.

Is your feature request related to a problem? Please describe.

I'm always frustrated when I try to unit test my NativeScript + Angular application using Jest.
Describe the solution you'd like

I would appreciate support for using Jest with NativeScript + Angular.
Describe alternatives you've considered

Please see this stackoverflow question, where I outline my struggles. What is holding it back at the moment is transpilation of @nativescript/core and @nativescript/angular  prior to running the tests. There are some import statements which Jest does not like, and when I follow the instructions from Jest and instruct ts-jest or babel-jest to transpile, I get another error about not being able to find ./application, or ~package.json.
Additional context

With guidance I would be willing to continue working the problem and search for a solution. Or some comments and/or responses to my stackoverflow question would be greatly appreciated, even if it is to comment on why it cannot easily be done. Thank you.

@jameone This might be a useful reference - https://github.com/nstudio/xplat/issues/170#issuecomment-574898977


Native app host performance issue

Comparison with the previous result:

Launchingtime (ms)
Native
.NET (loader)
.NET(standalone)

Jul 2020
562
577
-

Mar 2021
1178
849
1316

PSS (KB)
Native
.NET (loader)
.NET(standalone)

Jul 2020
20183
38336
-

Mar 2021
29509
46837
45634

(measured with the same jsonexample app on TW3)
The regression over time is somewhat understandable because our embedder implementation has grown a lot during the period. However, according the recent measurements, native host apps were even slower than .NET host apps unexpectedly. Need to investigate why.
Tip. You may also use this command to trace detailed start-up time events:
flutter-tizen run --profile --trace-startup

This specific issue has been fixed by #62. We'll look into other performance-related issues later on with more detailed measurements.


Allow outer shebangs so justfiles can be used as scripts

This was long overdue, since it was really just a matter of removing code.
With this change, justfiles can be used as scripts. Just write a justfile with a shebang line on top:
#!/usr/bin/env just --justfile

foo:
  echo foo

and you can do:
$ ./justfile
echo foo
foo

You can use a shebang like this to avoid changing directories:
#!/usr/bin/env just --working-directory ./ --justfile

Fixes #367.

I'm very curious what uses people put this feature to, so do let me know if you wind up using it!

I'm using to make more custom and convenient wrappers around the himalaya command line interface tool for emails. It's extremely convenient to be able to hack around and improve on the user experience of a raw CLI. Makes CLI composable, in some sense.


Fix object notation error in navigation docs

Thanks but it's not an error, it's an ES6 feature (object property shorthand)


TempReporting not working, log reporting ad nauseam

What issue do you have? Please be as thorough and explicit as possible.
I just installed the plugin and had my 2 heaters load automatically, but the plugin loggin was constantly throwing warnings that "tempReporting" should be set to true. I'm using HOOBS interface, and that isn't an option for automatically loaded devices. So, I manually added them and turned the setting on. Now it's still running with it as false and the warning is still logging (though now every minute instead of every few seconds).

Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
HOOBS, running the latest.

Which version of Homebridge/HOOBS do you have?

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Box, see screenshot.

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

10.3.0, new install.

Which Govee devices do you have that are causing issues? Please include product models if applicable.
2 Smart Heaters, product model H7130

Please paste any relevant logs below.
See screenshots.

Any luck here?

Unfortunately not, @wdimondi. I'm stilling getting logs for each device every minute.

@bwp91 Appreciate the update, but unfortunately even after updating I'm still having this same issue.

reopening 😃

In this case most likely the device id is written wrong in the config, please make sure to use the device ID as shown in the hoobs log from the line
[Device] initialised with id [XXX]

this is 23 characters long (including the colons) in the form
XX:XX:XX:XX:XX:XX:XX:XX

@bwp91 The config for each device is already correct. The device functions in HomeKit and there don't seem to be any issues there, but the logging in HOOBS is nonstop as mentioned. The devices are space heaters (H7130), but for some reason they appear in the Home app as fans and don't show the temperature—perhaps there's something wrong with how these devices are handled in your code?


Deprecated functionality for Ruby 2.7

Hey there.
/app/vendor/cache/ruby/2.7.0/bundler/gems/scoped_search-b692e7335357/lib/scoped_search/definition.rb:309: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/app/vendor/cache/ruby/2.7.0/bundler/gems/scoped_search-b692e7335357/lib/scoped_search/definition.rb:27: warning: The called method `initialize' is defined here

Seeing this error a lot with the separation of positional and keyword arguments.
https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/
I am using the v4.1.9 branch.

This should most likely be fixed by https://github.com/wvanbergen/scoped_search/pull/204 , could you check with latest master?

Yep, seems to be fixed. @adamruzicka
BTW, saw that there are some tags being made but no releases.  Is there a reason for that?

I'm not sure I follow. The tags are in the repo and corresponding releases are out on rubygems. Or are you talking about some other release?

Sorry, spoke too soon.  My logs just spat out the same error for master at rev 92939afa16dd

I'm not sure I follow. The tags are in the repo and corresponding releases are out on rubygems. Or are you talking about some other release?

Ah, yes I was looking at the gh releases.  Thought it was all tied together.

Just FYI, seeing the latest with 4.1.9

also got
/usr/local/bundle/ruby/2.7.0/gems/scoped_search-4.1.9/lib/scoped_search/definition.rb:309: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/usr/local/bundle/ruby/2.7.0/gems/scoped_search-4.1.9/lib/scoped_search/definition.rb:27: warning: The called method `initialize' is defined here


Design Landing Page

Refer to #29 for an overview of all design related tasks

This issues has been completed


ochttp and standard library docs inconsistency

From godoc documentation:
type RoundTripper interface {
        // RoundTrip executes a single HTTP transaction, returning
        // a Response for the provided Request.
        //
        // RoundTrip should not attempt to interpret the response. In
        // particular, RoundTrip must return err == nil if it obtained
        // a response, regardless of the response's HTTP status code.
        // A non-nil err should be reserved for failure to obtain a
        // response. Similarly, RoundTrip should not attempt to
        // handle higher-level protocol details such as redirects,
        // authentication, or cookies.
        //
        // RoundTrip should not modify the request, except for
        // consuming and closing the Request's Body. RoundTrip may
        // read fields of the request in a separate goroutine. Callers
        // should not mutate or reuse the request until the Response's
        // Body has been closed.
        //
        // RoundTrip must always close the body, including on errors,
        // but depending on the implementation may do so in a separate
        // goroutine even after RoundTrip returns. This means that
        // callers wanting to reuse the body for subsequent requests
        // must arrange to wait for the Close call before doing so.
        //
        // The Request's URL and Header fields must be initialized.
        RoundTrip(*Request) (*Response, error)
}

More exactly: RoundTrip should not modify the request, except for consuming and closing the Request's Body
and &ochttp.Transport{} clearly modified the request by adding additional headers.
Thus I want to hear the rationale behind this decision (or go's standard library). Personally, I agree with ochttp's approach and perhaps go's documentation should indicate it's ok to change/add headers because there's no other way to implement client middleware that I know of.
This issue is primarily to raise awareness of this inconsistency.

Thanks much for catching this bug. traceTransport should shallow copy the request and modify it rather than modifying the original request. RoundTrip should be safe for concurrent use for the same request object, that's why the interface enforces this constraint.


Refactor filter

Filter is now its own proper directive, and it gets reused in the ooni-grid-wrapper and in ooni-explorer-list
Added ability to sort by country to filter

When I am on the explorer view I don't see the country filter:

Investigating what is going on.

Scratch that it seems like there was a name clash between your branch and another branch I had named in the same way.
It does seem to be working properly.

Ok this looks good.
I am going to merge :+1:

@hellais glad to hear it! I should have probably done that work on a new branch, sorry!


Open old dot link when offline or there is network error

@sketchydroide @sobitneupane
Details
In order to open old dot link we don't require authToken anymore but will include it we can fetch it.
Fixed Issues
https://github.com/Expensify/App/issues/10625
Tests / QA

Login to new dot expensify
Send an old dot link (example: www.expensify.com/inbox) to someone.
Click on the link.
Verify that, when online, opening link works and includes authToken in the url params.
Verify that, when offline, opening link works and no growl is displayed.

[x] Verify that no errors appear in the JS console

PR Review Checklist

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
QA Steps

Login to new dot expensify
Send an old dot link (example: www.expensify.com/inbox) to someone.
Click on the link.
Verify that, when online, opening link works and includes authToken in the url params.
Verify that, when offline, opening link works and no growl is displayed.

[x] Verify that no errors appear in the JS console

Screenshots

MacOS - Chrome
https://user-images.githubusercontent.com/11381171/194131721-4f426092-1896-42d9-8c8c-0b8736ab4a32.mov
iOS - Native
https://user-images.githubusercontent.com/11381171/194130869-2346b701-f797-4c0a-b970-0f437943b2d6.mov
Desktop
https://user-images.githubusercontent.com/11381171/194672514-becf0ffe-89bf-484d-aae7-23049bac1b72.mp4
iOS - Safari
https://user-images.githubusercontent.com/11381171/194672568-8f6dd4b9-753f-4d96-af29-a7208e4b538c.mov
https://user-images.githubusercontent.com/11381171/194672590-0cd9cf71-fae8-487b-a655-3ad634d9bc05.mov
Android - Native
https://user-images.githubusercontent.com/11381171/194672731-361a1080-3576-4cfa-afe7-12e886b1bcda.mp4
Android - Chrome
https://user-images.githubusercontent.com/11381171/194672969-b86fd173-cf4c-4b2b-b05b-5a024a5a733a.mp4
https://user-images.githubusercontent.com/11381171/194672979-4f4dc686-b29a-45f2-9466-a9255d2dc892.mp4

@sobitneupane @sketchydroide Fixed formatting and added videos for all platforms

@vladamx Pressing Old dot Expensify link (example: www.expensify.com/inbox) on IPhone simulator safari browser does not open the link.
Also, please be more descriptive while writing the Test and QA steps. You can follow other PRs for reference. For example: https://github.com/Expensify/App/pull/11557

@sobitneupane Updated the instructions

@sobitneupane  Can you re-run the check?

@sobitneupane Can you re-run the check?

I don't think I can re-run the check.
@sketchydroide Looks like changes were made in PR template after this PR was raised. So, PR Author Checklist test is failing.

yeah, I was reading about it in slack, I can see that the checklist is done by both the creator and the reviewer, so I'm merging this and then I will remove the emergency label.

Not an emergency, the failed test is failing at the moment but the reasons for the failure are unrelated with the PR.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @sketchydroide in version: 1.2.15-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.15-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[Bug]: Footer component requires footerLogo to be set

Describe the bug
When upgrading to version 72.1.0,  I hit this issue with the footer component, where it needs the footerLogo option to be set. From looking at the docs, it shouldn't be required as we're just trying to use the default logo in the footer.
Here is some log lines from the error we're facing.
File "/Users/grundr/Projects/SSDC/srm-rh-ui/rh_ui/templates/base.html", line 111, in top-level template code
    {%- set pageConfig = {
  File "/Users/grundr/Projects/SSDC/srm-rh-ui/rh_ui/templates/layout/_template.njk", line 138, in top-level template code
    {% block body %}
  File "/Users/grundr/Projects/SSDC/srm-rh-ui/rh_ui/templates/layout/_template.njk", line 200, in block 'body'
    {% block footer %}
  File "/Users/grundr/Projects/SSDC/srm-rh-ui/rh_ui/templates/layout/_template.njk", line 203, in block 'footer'
    onsFooter({
  File "/Users/grundr/.virtualenvs/srm-rh-ui-iCTpfZ2X/lib/python3.11/site-packages/jinja2/runtime.py", line 782, in _invoke
    rv = self._func(*arguments)
         ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/grundr/Projects/SSDC/srm-rh-ui/rh_ui/templates/components/footer/_macro.njk", line 10, in template
    {% set extraLogo = params.footerLogo.logos.logo2 %}
  File "/Users/grundr/.virtualenvs/srm-rh-ui-iCTpfZ2X/lib/python3.11/site-packages/jinja2/environment.py", line 487, in getattr
    return getattr(obj, attribute)
           ^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'footerLogo'

Expected behaviour / outcome
I would expect the footer to not require params.footerLogo to be set and just use the default footer logo.
List the steps necessary to reproduce the bug
Try using the Footer component without any footerLogo to see if it works.
Additional context
I've managed to get around the issue by putting this into the footer options, but this doesn't seem like a good solution.
    'footerLogo': {
        'logos': {
            'logo1': {},
            'logo2': {}
        }
    },

What version of the ONS Design System are you using?
72.1.0
What device(s) are you using?
Desktop
What operating system(s) are you using?
macOS
What browser(s) are you using?
Chrome

hello @ryangrundy7,   thank you for raising this issue. Team will look into it and we will give you an update as soon as possible.


Eslint: Fixed 'angular/controller-as' violations in Blueprint Editor and Canvas

No visual differences in GUI, just improving the source code :smile:
This PR contains #186, please merge #186 first!
Also fixed 'eslint consistent-this' in Blueprint Order List Service.
@AllenBW , @chriskacerguis , @serenamarie125

@dtaylor113 If you could please do not do a "please merge X before this ticket" I would appreciate that a great deal.  It becomes too much of a pain to keep track of that.

@chriskacerguis is that a GitHub thing?!  I have never filed a 'merge X before Y' ticket before. -thanks

Ok, do NOT do a 'merge X before Y comment' -got it


Fix error missing tini; use sbin

This PR fixes a bug running tini in the current Dockerfile. Perhaps this is a recent change, but the tini binary installs to /sbin, not /usr/bin, so pinata-ssh-forward fails.

Addresses issue https://github.com/avsm/docker-ssh-agent-forward/issues/6.

This pull requests solved the issue in my case
IMHO, only the modification in Dockerfile is needed.

This solved my issue as well.


Ability to draw words with no spacing at all between letters/characters/symbols

I've dug into this problem now a few times and it appears to be non-trivial and a product of drawing each letter separately with pygame. I hope there's a way around this, however.

This can be easily done: the x-coordinate (or horizontal location) of characters are decided here (and here). You can make this distance however small you like.

I tried messing witht hose values but didn't seem to be able to get at a
difference because making the value too small made the text overlap and
since the text sizes are all different, it was hard to reach a single value
that would work for every size text. I'll try playing around with this some
more to see if I can figure it out. It's also very possible that i"m doing
something drastically wrong! lol
On Thu, Jan 26, 2017 at 6:00 PM, Ankush Gupta<EMAIL_ADDRESS>wrote:

This can be easily done: the x-coordinate (or horizontal location) of
characters are decided here
https://github.com/ankush-me/SynthText/blob/master/text_utils.py#L148
(and here
https://github.com/ankush-me/SynthText/blob/master/text_utils.py#L221).
You can make this distance however small you like.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ankush-me/SynthText/issues/16#issuecomment-275541354,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABL1YPcURazB38re0q1NlUMfJVGtFT2Qks5rWSWHgaJpZM4LvIal
.

You could have a <1 proportion of the character width:
x += p * ch_bounds.width, with p < 1 and something similar for render_curved.

I had tried this originally and it was hard to find a value that worked
with every siE text (for every character width). I'll keep trying.
On Jan 26, 2017 6:36 PM, "Ankush Gupta"<EMAIL_ADDRESS>wrote:

You could have a <1 proportion of the character width:
x += p * ch_bounds.width, with p < 1 and something similar for
render_curved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ankush-me/SynthText/issues/16#issuecomment-275548198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABL1YBadxWciIK-5-1eVDpjv5tyYBUiHks5rWS3zgaJpZM4LvIal
.


Add support for editor_palette to WP Graphql schemas

Thanks for this amazing plugin (and all the other ones you make, you're a real lifesaver!)
I use the roots stack along with acf-composer to build headless WP backends, and as useful as this plugin is, it doesn't natively resolve into Graphql fields.
I am presently adding a resolver myself in my themes (usually to setup.php) but am thinking you might want to include this as part of the plugin?

/**
 * Add "editor_palette' to the graphql schema.
 *
 * @return void
 */

 add_action( 'wpgraphql/acf/registry_init', function() {
    register_graphql_acf_field_type( 'editor_palette', [
      'graphql_type' => 'string',
      'resolve' => function ($root, $args, $context, $info, $field_type, $field_config ) {
        $value = $field_config->resolve_field($root, $args, $context, $info);

        if (is_null($value)) {
          return null;
        }

        return $value['slug'];
      },
    ]);
  });

you can see the WP Graphql developer reference for adding support for 3rd party ACf field types here

hey no problem.
i haven't used ACF with GraphQL but I'm definitely open to a PR.


Development: Add docker compose for server and client

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

This will allow developers to start client, server (with integrated life cycle), and database with a single docker-compose file
Description

Added a docker compose file to start client, server (with integrated life cycle), and database services.
Added a Dockerfile to build the webapp image. This requires an nginx config, which is also contained in this PR.
Steps for Testing

Prerequisites:

Make sure that ports 3306, 5005, 8080, and 9000 are free on your host machine
Make sure that you don't have an instance of client or server running on host machine
1 Student
1 Programming Exercise (preferably with online IDE enabled)

start containers: docker compose -f docker/webapp-artemis-localci-localvc-mysql-dev.yml up
Log in to Artemis as a student
Navigate to the programming exercise, and submit any code
From the terminal of the host machine, make sure that the localCI created a new docker container (this can be done by watch -n 1 docker ps)
Make sure that the submission was graded in the client

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test 1
[ ] Test 2

Test Coverage

3. The webapp is already a part of the normal Artemis Docker image, so having it as a separate service is redundant and adds unnecessary maintenance effort to the Docker setup.
I missed this when testing locally as I don't think it's mentioned in the docs. Closing this PR


Move file that lost its way during packaging merge

The fix from PR #1515 was left behind in an old location during the packaging merge.
This change moves
include/objc/module.modulemap → tools/include/objc/module.modulemap

:shipit:


Remove question marks

Nodejs throws compilation errors because of ? present in code.
Seems to fix https://github.com/liamcottle/sungrow-eyem4-exporter/issues/1 issue

Seems to be solved by using newer nodejs version


Faceted search has internationalization issues

Both facets and values can have a name/value different from what is displayed. But for both, it only works for searching. Example: You have a facet "Autor" with an internal name of "author" and one of its possible values is "Konzertheld" with an internal value of "admin". You can type "a" and "Autor" will be suggested but when you select it "author" will be displayed. Then values will be suggested, you can type "a" or "k" and "Konzertheld" will be selected but once selected the displayed content of the faceted searchbox will be "author: admin" and not "Autor: Konzertheld".
Also, we include post statuses, types etc, but they are not translated before they are added to the list.

Even more, we can't just translate status names, content types etc back. Because of that and for better code (less translation-backtranslation annoyances) we should modify visualsearch to be able to actually display the display values and keep the internal values internal.


Wrong types for non-standard saved variables

Is your feature request related to a problem? Please describe.
At the startup of the pydase app, internally the variables are set to whatever values have been saved previously. However, the type of non-standard type variable are wrong, in particular:
pydase.units.Quantity: set as dict
pydase.components.ColouredEnum: set as str
This becomes problematic for example if we would like to check if the variable is in a specific state:
self.lock_status: LockStatus = LockStatus.LOCKED
And later we might want to check it:
if self.lock_status == LockStatus.LOCKED
This will return false if self.lock_status has been set to the string "LOCKED"
Describe the solution you'd like
Make sure the variables are set in the original type format.

Thanks for the issue. I got an assertion error when trying to load ColouredEnums from a settings file. That should be fixed now.
However, I cannot produce an issue with a Quantity. Could you provide me with an example for a Quantity? This is a working example:
import pydase
import pydase.units as u

class Test(pydase.DataService):
    def __init__(self):
        self._unit: u.Quantity = 1 * u.units.A
        super().__init__(filename="settings.json")

    @property
    def some_unit(self) -> u.Quantity:
        return self._unit

    @some_unit.setter
    def some_unit(self, value) -> None:
        self._unit = value

if __name__ == "__main__":
    service = Test()
    pydase.Server(service).run()

What if you try accessing the magnitude of the value in the setter? This can be necessary when talking to devices which expect only a number. E.g.:
import pydase
import pydase.units as u

class Test(pydase.DataService):
    def __init__(self):
        self._unit: u.Quantity = 1 * u.units.A
        super().__init__(filename="settings.json")

    @property
    def some_unit(self) -> u.Quantity:
        return self._unit

    @some_unit.setter
    def some_unit(self, value) -> None:
        print(f"The magnitude of the value is {value.m}")
        self._unit = value

if __name__ == "__main__":
    service = Test()
    pydase.Server(service).run()

I see. I would have to take care of the conversion when reading from the settings file. Thanks for pointing that out.


ERA-10485: Support EFB schemas in das-web-react form rendering -  Form Component

What does this PR do?

It adds the SchemaForm component which handles the general logic to render EFB schemas
It adds the base pattern to manage EFB schema forms

Relevant link(s)

Tracking tickets: ERA-10485

Where / how to start reviewing (optional)

For this PR still there is nothing to QA to test, all these changes are the base for adding EFB fields support

Just a heads up, this PR has nothing that can be tested by our QA folks, I started working on the primitive fields support I put that branch behind this one, there will be actual testable features, I used this ticket to set the foundations
@luixlive @JoshuaVulcan

Before I got too deep on adding support for primitive fields, I know the idea is to make the form in das-web-react look like the one in EFB, the most easy way to do it is to install React MUI in this repo, but that will increase the loading time of the page for the users, also I've been searching for some lightweight CSS material implementation, I would like to hear your opinion on this matter, also I think that an option can be use CSS on our own and get something really good 👀
@luixlive @JoshuaVulcan

All the components inside fields/ have partial implementation and are missing test coverage, that will be addressed in their respective PRs, just add them to make the patter/approach easier to follow 🫡

@luixlive I have addressed most of the feedback, I left some things out I would like first to have a green light before getting into these

Schema mocks naming and condition: you made some comments about this, my idea is to add a FF
Failing unit test, I would like to work on fix them once We hit common ground
Implementing a mock selector inside the event form to facilitate QA explorations


Update to 8.0

8.0.beta3 is out, so it seems like we need to update a few packages.

Update sagemath-db-conway-polynomials to 0.5
Update cysignals to 1.6.3
Update pari to 2.9.2

Also need to package cypari2

@jdemeyer, would you be interested in creating a recipe for cypari2?

@jdemeyer, would you be interested in creating a recipe for cypari2?

To be honest, I never really used conda. So I guess the answer is "no". That being said, it's just a Python package, so pip install should do it.

For cysignals, better use version 1.6.4, see https://trac.sagemath.org/ticket/22691

Superceded by #10


Minor typo correction

Inserted a missing 'to'

Description

GitHub Issues

Coverage remained the same at 74.054% when pulling 16f5b10a738ec7febe439ea725ec9199a3d9b62a on robertsvensson:patch-1 into 86b62fd175b5ca722f063745392c69ac88a2aa8e on Miserlou:master.

Thanks!


Batch upload is not working as expected

I tried uploading a single 5 page pdf document via "Add documents in Batch". I get the prompt that 1 document is being upload and that this will happen asynchronously and will take time. However even after waiting for more than an hour I cannot see the converted file in Index Management. What am I doing wrong? All necessary components have been provisioned in Azure.
Below are logs of the error -
azure-open-ai-embeddings-qna-batch-1  | info: Function.BatchStartProcessing[1]
azure-open-ai-embeddings-qna-batch-1  |       Executing 'Functions.BatchStartProcessing' (Reason='This function was programmatically called via the host APIs.', Id=9f86e0ca-325c-461c-bf10-9391d9cce231)
azure-open-ai-embeddings-qna-batch-1  | fail: Function.BatchStartProcessing[3]
azure-open-ai-embeddings-qna-batch-1  |       Executed 'Functions.BatchStartProcessing' (Failed, Id=9f86e0ca-325c-461c-bf10-9391d9cce231, Duration=1ms)
azure-open-ai-embeddings-qna-batch-1  |       Microsoft.Azure.WebJobs.Host.FunctionInvocationException: Exception while executing function: Functions.BatchStartProcessing
azure-open-ai-embeddings-qna-batch-1  |        ---> Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcException: Result: Failure
azure-open-ai-embeddings-qna-batch-1  |       Exception: KeyError: 'QUEUE_NAME'
azure-open-ai-embeddings-qna-batch-1  |       Stack:   File "/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/dispatcher.py", line 357, in _handle__function_load_request
azure-open-ai-embeddings-qna-batch-1  |           func = loader.load_function(
azure-open-ai-embeddings-qna-batch-1  |         File "/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 44, in call
azure-open-ai-embeddings-qna-batch-1  |           return func(*args, **kwargs)
azure-open-ai-embeddings-qna-batch-1  |         File "/azure-functions-host/workers/python/3.9/LINUX/X64/azure_functions_worker/loader.py", line 132, in load_function
azure-open-ai-embeddings-qna-batch-1  |           mod = importlib.import_module(fullmodname)
azure-open-ai-embeddings-qna-batch-1  |         File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
azure-open-ai-embeddings-qna-batch-1  |           return _bootstrap._gcd_import(name[level:], package, level)
azure-open-ai-embeddings-qna-batch-1  |         File "", line 1030, in _gcd_import
azure-open-ai-embeddings-qna-batch-1  |         File "", line 1007, in _find_and_load

If you did not use the template for resource creation, please create a "doc-processing" queue in the Azure Storage account associated with your Azure Function as per READme  Double check you also have an env variable named "QUEUE_NAME" with value "doc-processing"


Add option to open the table at the source file row but always column 1

Version?

vs code plugin

Feature
Currently there are only two options for openTableAndSelectCellAtCursorPos: initialOnly or never.
I generally like the idea to open the table from where the cursor was in the source file...
However, when I click through the table and just want to open it, the cursor normally ends up at the end of the line.
This means I always open the table in the correct row but at the last column (which feels odd).
I propose a new option for openTableAndSelectCellAtCursorPos which opens the correct row but always selects the cell in the first column, e.g., initialOnly_RowOnly.
For the future one should separate the options to open the table from the cursor pos (never, initialOnly, ...) and what should be selected (correctRowFirstColumn, .... as a separate option).
Not sure how other users feel but I think this should be the new default.

Will be called initialOnly_correctRowAlwaysFirstColumn.
Renamed initalOnly to initialOnly_correctRowAndColumn


Add more appropriate linting setup

Currently the linting setup is designed around a creating a React app and so isn't particularly useful for us. I've switched us over to use a Typescript compatible linting setup.
This does require a Typescript install however I'm expecting that we're going to have this anyway from #28 so it's not extra overhead.

Sorry to use this as a test, but I'm setting up notifications so I need to make a comment on a PR.

Sounds like we're waiting until https://github.com/actualbudget/actual-server/pull/28 land?

There no strict dependency on #28 so they could be merged in either order. Just we probably wouldn't want to install typescript in this PR if we weren't planning on migrating the server over to typescript at some point.

Yep, that's fine with me. Was mainly thinking it will conflict with the other PR, but it shouldn't be too bad. I'll go ahead and merge this one to move things along and hopefully the author of the other can rebase & cleanup.

There are probably some rules I want to tweak, but we can do that later


Update help doc

There are actually three commits on this branch:

The changes requested in #404 to explicitly reference vim.api everywhere
While I was in the doc I fixed some typos
This commit includes some formatting and language changes

I made them as separate commits so that I can back out any changes that aren't desired.

Happy to have been able to contribute!


Extend vertical line plot to plotting against model_level and height

What problem does your feature request solve?
Currently the vertical line plot allows to plot against a log pressure axis.
This ticket extends the plotting capability to allow plotting against model level number as well as height coordinate.
https://github.com/MetOffice/CSET/pull/567#pullrequestreview-2083466715
https://github.com/MetOffice/CSET/issues/494
Describe the solution you'd like
Extend the existing vertical line plot capability to pass in type of height coordinate to be plotted against.
Describe alternatives you've considered

@jfrost-mo as pressure levels won't be available for now in Lfric we should take the lfric based pressure level reliant recipes out and replace them with model level number reliant ones.

[ ] recipe vertical profile on mlevels
[ ] recipe spatial fields on mlevels
[ ] cylc include vertical profile mlevels
[ ] cylc include spatial fields on mlevels
[ ] introduce mlevels to rose meta
[ ] introduce mlevels model fields to rose meta
[ ]

as pressure levels won't be available for now in Lfric we should take the lfric based pressure level reliant recipes out and replace them with model level number reliant ones.

Now that we can read UM and LFRic data with the same recipe, the same recipe will work for both. We can keep it around to use on the UM.

PR: https://github.com/MetOffice/CSET/pull/697


Parallel tests

Depends on #1127 .
This PR is a tentative to enable parallel tests with bats (requires bats 1.3.0 + parallel installed on the remote machine).
Please note that the test harness has been modified:

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!

[ ] Ensure that the pull request title represents the desired changelog entry

[ ] Please describe what you did

[ ] Link to relevant issues in GitHub or Jira

[ ] Link to relevant pull requests, esp. upstream and downstream changes

[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Closing in favor of #1130 1128


Tooltip Implementation onMousehover the Circle

Hello,
Is that possible to implement the tooltip to display Label and values while mouse hover the circle...?

Hi @ganapathi-egr -- you can use the onHover prop to do this. Pass in a function and it will be called with the currently hovered value/label (or null if the user is no longer hovering over something). See https://github.com/shauns/react-d3-radar/blob/v-next/src/Radar.js#L22 . It's then on you to decide what to do with that data and how you'd like to show it.


Add missing type to setStackRoot

:tada: This PR is included in version 6.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please run tests against Python 3.6 and 3.7

I believe they will pass anyway 👍 Is it enough to add them to tox.ini and Readme.rst, or are there some other places?

I found 3 related PRs:

https://github.com/AltSchool/dynamic-rest/pull/254
https://github.com/AltSchool/dynamic-rest/pull/276
https://github.com/AltSchool/dynamic-rest/pull/259

Now included in v1.9.4 which has been pushed to PyPI.

Actually, still need to add tests for Py 3.7. Reopening.

https://github.com/AltSchool/dynamic-rest/releases/tag/v1.9.5 now supports this. U can close this


Add reportbacks and signups shortcuts to the profile.

Changes
:white_check_mark: New Feature: Adds a /profile/signups "shortcut" endpoint to get the authenticated user's signups. This will return the same format of response as /signups index.
:white_check_mark: New Feature: Adds a /profile/reportbacks "shortcut" endpoint to get the authenticated user's reportbacks. This will return the same format of response as /reportbacks index.
:arrows_counterclockwise: Changed: The ?user=xxx query string on the /signups and /reportbacks indexes will now translate a Northstar ID into a Phoenix user ID when forwarding the request to Phoenix. So make sure to provide the full Northstar ID when setting a filter on this endpoint. :smile:
Fixes #277.
How should this be tested?
Automated tests should continue to pass. :traffic_light:

For review: @angaither or @weerd
/cc @aaronschachter @jonuy

:+1:

:+1:


please help me

I am using typescript and tslint in my project

vscode show errors but tslint cli didn't show me errors.

your CLI output there is showing typescript-eslint, which is not part of this repo. It's unclear what command you're running there, so it's hard to diagnose the issue.

Hi @webmaster0820! Sorry to hear this is being a pain.
It looks like you're using @typescript-eslint. This repository is for TSLint, an older TypeScript linter that's being deprecated (#4534).
One quick thought: are the errors being shown in VS Code from TypeScript or from a linter, such as ESLint? The two are separate things.

👌

Could you help me? @JoshuaKGoldberg

@webmaster0820 let's talk on https://gitter.im/palantir/tslint.

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


customizations: enhance menu customization docs

Retargeted https://github.com/inveniosoftware/docs-invenio-rdm/pull/615 with some little improvements. Overall kudos go to @martinobersteiner .
Screenshot

I'll leave this around until tomorrow and then merge if no objections.

Checking up on PRs before I go. This one could be merged, but it has pictures that are rendered so small that without an image preview plugin like https://github.com/inveniosoftware/docs-invenio-rdm/issues/680 , the experience wouldn't be very good. I'll leave it as-is for now, but may comeback and merge it in at some point with or without the preview plugin.


3.3.0 uses storage-engine which breaks installs in docker

Can't use version 3.3.0 in docker node:12 anymore because of dep on storage-engine which gives an
Error: EACCES: permission denied error
3.2.1 is fine

This has been addressed ^^, you can use master or 3.2.1 till we cut the next release

3.3.1 was released

Hi - just to say that this change has broken our system - we install node in a docker image that doesn't have git.
This change now it pulls a dependency from git gives a problem if git isn't present.
We're using
ARG NODE_VER=12.16.1
FROM node:${NODE_VER}-alpine

I'm not sure if related, but I'm getting
``npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

@DABH
Hi, cloud you please use a npm diagnostics dependency rather than git? It's may be fragile in some network area to access the git address.
install diagnostics from git github:DABH/diagnostics#master, may be very slow, please keep patience


[helpers] add as_dict() method to hp.Firmware

Because sometimes you really need an old fashioned, down-to-earth, no-nonsense dict.
Signed-off-by: Avi Miller<EMAIL_ADDRESS>

do you need a photons release with this?

Nope. As some point (hopefully soon), I'll be opening a draft PR for photons_lib which one could think of as Photons in asyncio IoT library drag, i.e. it presents as a library that knows about Discovery and Lights (of various kind).


Hostname should be a little away from client names

the color of the hostname should be different to the clients and be under another category to see how many clients have buzzed already.

Interesting - just to confirm I understand, is the host actively buzzing in your event? (so you would like to distinguish the host buzzing from other players who have buzzed?)

No - the host is not buzzing. I want to distiinguish the host color or position from the other players. So the players can quickly see, which of the players have already buzzed. So if 3 from 4 players have buzzed they know 1 has not buzzed. Or 4 of 4 have buzzed they are able to see quickly that all players have bust, just the host not (because he is not in the same list/ position/ color) of the normal players.


Added coverage and validations

Pull Request Test Coverage Report for Build 26

155 of 155 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 22:
0.0%

Covered Lines:
945

Relevant Lines:
945

💛  - Coveralls

GraphBuilder>>loopOn:labeled: is not covered in any test


Update screenshots on How to examine and edit CSS

Take new screenshots for Examine and Edit CSS
Acceptance criteria

[x] All images on the page have been replaced with Firefox 65 images
[x] Accompanying text has been edited as necessary to properly describe the new images

All images have been updated.


Bugfix/incremental output

set enable search to false for default chat configuration.
Fix incremental output issue and support streaming function call.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yuanci seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add allow-mock-accuracy parameter

Needed for getodk/collect#4768
Why is this the best possible solution? Were any other approaches considered?
What are the regression risks?
Does this change require updates to documentation? If so, please file an issue here and include the link below.
Before submitting this PR, please make sure you have:

[x] included test cases for core behavior and edge cases in tests_v1
[x] run nosetests and verified all tests pass
[x] run black pyxform to format code
[x] verified that any code or assets from external sources are properly credited in comments

The required dependency update has been merged.

Codecov Report

Merging #560 (d0c6815) into master (3380599) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #560      +/-   ##
==========================================
+ Coverage   83.31%   83.36%   +0.04%
==========================================
  Files          25       25
  Lines        3728     3738      +10
  Branches      872      875       +3
==========================================
+ Hits         3106     3116      +10
  Misses        482      482
  Partials      140      140

Impacted Files
Coverage Δ

pyxform/xls2json.py
76.31% <100.00%> (+0.34%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3380599...d0c6815. Read the comment docs.


Save Raw Data into GCP Buckets

Should we also setup loading from the buckets?

We should save the raw_blocks and raw_txs table through a corn job to GCP.


[Suggestion] Breeders active/idle visuals

I'm not sure if this is viable in terms of efficiency, but I'd love to see when my Breeders are actively working (chickens + at least 2 seeds are inside).
Right now there is visual effect after finishing each breed, which let's you know when it's done, but after that effect disappears it's not possible to distinguish between breeders.
Main reason behind changing that is improving chickens to 10/10/10 takes quite some time, and personally I'm doing it by placing 2 chickens and 4 seeds to breed 2 better chickens, and repeat the process. When doing it with multiple species at the same time it's very time consuming to check all breeders if they are done.

Better do this when the Output is full and no breed could be done

I added an alpha release file to CurseForge, if everything looks good, I'll promote it to the official 1.3.0 release.
https://minecraft.curseforge.com/projects/roost/files/2635449

This is added in 1.3.0


Vendor in latest containers/buildah

Fixes issues with builtin volumes having correct ownership and permissions
when doing podman builds.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

LGTM

LGTM and happy green tests

@rh-atomic-bot r+


Question

Before updating to 1.2.0 and 4.0.0 of the trainer, what codes aren't currently working?

I tried weapons, Bows, Armors, Rupees, moon jump and everything else.. everything worked for me. I got the EU version updated to 1.2.0 with trainer 4.0.0

I don't think coordinate are working. I tried to track my coords and got the same error you would get if you used the old version of the trainer for v80

I just updated to fix wolf code and coordinate stuff


Add title to the generated HTML page

Add to the head element of the generated HTML report:
<title>Test coverage for {name} {version}</title>
Taking name and version from the Cargo.toml file

You can't read a title that long on the tab without mouse over and the project name is visible in the actual report body so I'm just going to close this as a WONTFIX unless there's a compelling reason on why it's needed


ci: add black formatting

This works well, except one thing. The black suggester does not suggest changes to the tests. However, the checking is applied to tests. So merging for now and will address this issue in the future.


Can dependencies be trusted?

We are in a highly secured environment and I am currently in a test phase for SecretManagement/Microsoft.PowerShell.SecretStore
I did some successful testing with the SecretManagement.KeePass (0.9.2) extension on my private machine.
Now we are bringing the items into our environment, it appears that there is an dependency on PSFramework.
How can the security of the 3rd party modules be guaranteed/trusted?
See also: #184 Can extensions be trusted?

All the modules are open source, you can review them yourself. You also can "pin" your dependencies so that you never pull a newer version without review.
Otherwise unless you want to sponsor me, this is a "best effort" open source project, it is not a commercial module with a team constantly reviewing and scanning for vulnerabilities.

Hello Justin,
Thanks for the answer.
No offence, I am sure that are only good intentions in your open source project.
The "trust" thoughts where I am dealing with: the owner of the SecretManagement (Microsoft) has quiet a lot to lose if there is a leak somewhere (besides, there are a lot of eyes looking in what they are doing). The responsibility of an opensource writer is a lot less "All the modules are open source, you can review them yourself". I do have some Open Source projects myself and e.g. I do care less for e.g. a breaking change that then Microsoft (or the PowerShell team) does.
But this concerns Secret data and therefore I would control the code at the highest (SecretManagement) level or at least at a extension level (SecretManagement.KeePass) and not include further (module) parties.

@iRon7 you are free to not use this module if you do not trust it as a pinned dependency. I'll happily give back the money you paid for it :)

PSFramework is managed/written by Fred. Fred is working for Microsoft. He's also a trusted member of the PowerShell community. After downloading, review the code, and use Justin's module along with the PSFramework module that you reviewed on your own trusted platform (aka internal PSGallery). This will give you a trust that you only run trusted code (already reviewed). Than every time there's new update by Justin or Fred you go thru the process again and again.


github issue route

Added backend route to create issue using github api.

why this check failed??

That's an error in Actions Config, don't worry won't bother the code.

@DeadSpoon18  are you working on this: https://github.com/AasthaGithub/Elemento/issues/85  as you commented earlier ?

No sorry, I am not working on that issue right now.
And how can I edit commits I can't figure out.

Okay no worries. The PR solves https://github.com/AasthaGithub/Elemento/issues/84 making issue end point as required. Merging now. Thanks for contributing.


Breakpoint issue with editing language toggle

Private Zenhub Image

@connorscarolyns was this on tablet? Can you re-test and see if the issue still persists?

Yes, this issue still persists

Issue no longer persists with new navigation


 When I then make a comment, the whitespace preferences are discarded. (Probably because of the #issuecomment-<number> part in the url)
When I then again set my whitespace preferences, I am no longer automatically moved to the comment I just made. Hence, I have two feature requests:

When making a comment, your whitespace & splitscreen preferences should not be discarted.
When changing your preferences, you want to be moved to the comment in your URL.

I think this can be fixed by changing the comment movement parameter to a GET-variable, but I am not sure if this is indeed possible (I do not know any GO).

I think it can also be considered as a bug, because in some cases when the whitespace setting is reset after pressing 'add commit' the page can't restore the reading position with the anchor link (I guess because it shows different lines then before)
related report: https://github.com/go-gitea/gitea/issues/13758

It has been fixed by https://github.com/go-gitea/gitea/pull/15566


C1: QA fixes - 6

Summary by CodeRabbit

New Features

Added conditional rendering for branding elements in the configuration connector.
Introduced new styling for success and failure indicators in the dashboard export summary section.
Updated onboarding stepper to accurately reflect completion status with reordered icons.

Style Updates

Improved visual consistency across the app with updates to input fields, dropdowns, and buttons for better user experience.
Enhanced app theme with custom CSS variables for line height, text size, and color schemes.
Refined UI elements in various components with adjustments to padding, borders, and font weights for clearer, more accessible design.

Bug Fixes

Fixed hover styling issues on dropdown items and input fields to ensure visual feedback is clear and consistent.

Documentation

Updated theme documentation with new custom properties for better theme customization and consistency.

@coderabbitai review

@coderabbitai review


prune a squeezenet ssd example

assuming I have a sq-ssd-lite trained model: sq-ssd-lite.pth
could you give an example code for pruning this model?
model = prune_model(model, factor_removed=[SOME PROPORTION OF CHANNELS YOU WANT TO REMOVE])
What exactly [SOME PROPORTION OF CHANNELS YOU WANT TO REMOVE] this mean? a sequence of number of channels for each layer to remove? e.g.  [128, 100, 500]? or a fraction of numbers [0.2, 0.8, 0.9] means 20%, 80%, 90% to remove? Please provide a working example. That would be nice. Thank you very much for your help.

This code just serves as one example. The basic idea of pruning here is in this pseudo code:
percentage = 0.9 //value from 0 to 1
weights = model.weights
weights.sort()
weights[:percentage*len(weights)] = 0 //pruning the weights by setting them to zero
model.weights = weights


Adding a github repo as dependency fails to get manifest information

This failure causes the root field of gyro.zzz to fall back to "src/main.zig". If the package has a different root, this will cause a build failure.
I was able to trace this to the getGithubGyroFile() function in api.zig.
    // @line 266, api.zig
    var extractor = tar.fileExtractor(subpath, gzip.reader());
    return extractor.reader().readAllAlloc(allocator, std.math.maxInt(usize)) catch |err| {

In this case readAllAlloc is consistently returning error.FileNotFound. I believe the http transactions are succeeding based on verifying that a 200 code was returned, so it is unclear what is causing FileNotFound.

Problem found. This was only actually happening when adding zig-clap from github. It turns out that these two are not equivalent:
gyro add --src github hejsil/zig-clap
gyro add --src github Hejsil/zig-clap

So basically this was on me for not capitalizing.


Recommended Setup: Property Greeting Does Not Exist On Type

Hi,
I'm following the recommended setup: https://trpc-nuxt.vercel.app/get-started/usage/recommended
And encountering this error: Property 'greeting' does not exist on type 'Ref<{ greeting: string; } | null>'.ts-plugin(2339)
This is my app.vue:

<template>

{{ hello.data?.greeting }}

    <Button>Button</Button>

</template>

Doing just: {{ hello.data?.greeting }} returns { "data": { "greeting": "hello client" }, "pending": false, "error": null, "status": "success" }
Where: {{ hello.data?.greeting }} returns nothing.
This is my ~/server/trpc/routers/index.ts:
import { z } from 'zod';
import { publicProcedure, router } from '../trpc';

export const appRouter = router({
  hello: publicProcedure
    .input(
      z.object({
        text: z.string().nullish(),
      })
    )
    .query(({ input }) => {
      return {
        greeting: `hello ${input?.text ?? 'world'}`,
      };
    }),
});

// export type definition of API
export type AppRouter = typeof appRouter;

Following the simple setup works, but I'd prefer to use the recommended setup.

Doing this in app.vue solves the issue, but is this best practice?:

      {{ hello.data?.value.greeting }}

    ```

This is something from Nuxt. I'll try to find an existing report on their side and I'll add it here.
For now what you want to do is destructure it before using inside the template:

<template>

{{ data?.greeting }}

    <Button>Button</Button>

</template>


Fixed #136: getChildRoles() throws an exception when role has no children

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#161

There are no fixes between versions...

@samdark , I updated commit (if you still insist on this).

Not really...

@samdark , I can change it back :)

... Done.)

Thank you!


Defmt test macros v0.2.0

Bumps defmt-test-macros to v0.2.0, make defmt-test use this version and bump itself to v0.2.1.
Fixes #417

bors r+


GCP Actions give unhelpful error when permissions are missing

Describe the bug
Created a new GCP credential (turned out it did not have enough access)
Tried to execute List GCP Buckets action. Got the following error
Error: Parameter type validation failed: list indices must be integers or slices, not str
which is not really helpful. The problem was that the service account did not have enough privileges.
To Reproduce
See above
Expected behavior
The error should mention something like "Access Denied", or "Not enough permissions"
Screenshots
See attached
Desktop (please complete the following information):

OS: MacOS
Chrome

@abhishek-unskript please review this PR.


0.9.3 for 1.20.1 - Zombies converted into Drowned lose their inventory

Just managed to lose all my gear by having the zombified player drown before I could kill him, he still carried the axe after becoming Drowned but on death only dropped one rotten flesh.
Id expect the drowned should also receive the inventory in this case?

Thanks for the bug report, I will have a look

I can confirm it's a bug, the Zombified Players should not convert at all. Will be fix in the next release

fix released (in version 1.0.0), please reopen if there are still problems


Redundancy in unsuccessful drag start tests

See this line... We initialise the dragDataSource mock after we setup the coordinator. When we make the call to the coordinator's creation method we end up passing a nil data source, so during all the tests in this suite the coordinator's data source is nil making most of these tests redundant at present because they won't actually fail.

I'd like to review these tests to see if we can't make them a bit leaner.


Why Completable/Single is not supported as direct return type for @Insert or @Delete methods in @Dao?

I am wondering if there is a contradiction for a RxJava/Room to be able to return Completable/Single types directly from methods annotated with @Insert or @Delete annotations in class annotated with @Dao
For example
In my @Dao, I have function like
@Insert(onConflict = OnConflictStrategy.REPLACE)
fun insert(model: SomeObject)

when switching to RxJava2 I wrote
@Insert(onConflict = OnConflictStrategy.REPLACE)
fun insert(model: SomeObject) : Completable

and later
@Insert(onConflict = OnConflictStrategy.REPLACE)
fun insert(model: SomeObject) : Single<Long>

but compiler yells at me that @Insert can return either void or Long type.
I thought I have made mistake somewhere and writing this way is acceptable, but after investigating an official RxJava + Room sample.
I can see code (line 59) similar to:
return Completable.fromAction(() -> {
      dao.insert(.....)
}

Pojo is wrapped into completable so it can be thrown into RxChain
If Room is able to return RxObjects From @Query annotation, why can't it return them from @Insert, @Delete aswell, and we are forced to wrap them ourselves if we want to keep DB api consistent.
Thanks

This issue has already been reported on the official issue tracker here.
Please only create issues related to the samples here. More info on this can be found in the issue template.

@florina-muntenescu
Thanks for reply. Good to know this issue is already reported.
Gotta keep in mind, to post architecture components bugs/feature proposal in google bug tracker in future


Regression: PDF preview page of an ODT file is blank

Due to the fix described in https://github.com/algoo/preview-generator/pull/100#discussion_r303020089, specific PDF page previews of office documents are empty.

regression found here:
for unknown reason, using stream instead of file path in get_decrypted_pdf() which use PdfFileReader inside doesn't provide a correct pdf (it result in an empty pdf).
see https://github.com/algoo/preview-generator/issues/194
Originally posted by @inkhey in https://github.com/algoo/preview-generator/pull/100#discussion_r463565867

Related Tracim issue : https://github.com/tracim/tracim/issues/3401
Implemented solution:
https://github.com/algoo/preview-generator/pull/200
Hack to convert stream in a known working format for pypdf2, this is not an effective solution (as this lead to in memory content), but this does work and is not a regression (we do use the same "code" as pypdf2 itself use for file).

This regression is visible/exists in Tracim (latest release) ?

This regression is visible/exists in Tracim (latest release) ?

The fix was added in preview generator 0.15.4 that tracim is using.

So this issue need to be stay open or can be closed ?

We can close it.


Question: Get body data if Error

When it is an error, we use
request.errorBlock = ^(NSError *error) {}
But what if i need to fetch a response body, when it is an error? What should i do?

You can use request.responseString in errorBlock.

Thx!
Note: Capturing 'request' strongly in this block is likely to lead to a retain cycle
so use __weak typeof(request) weakRequest = request;
Thumbs up if helped.


CharacterBody3D's up_direction property is unsettable.

Godot version
v4.0.alpha6.official.e4f0fc50f
System information
N/A
Issue description
The property up_direction cannot be set in CharacterBody3D instances.  up_direction is locked to the default value of Vector3(0, 1, 0).
Steps to reproduce
Instantiate a CharacterBody3D with the following GDScript.
extends CharacterBody3D

func _ready():
	# Cannot set with direct access.
	up_direction = Vector3.ZERO
	assert(up_direction == Vector3.ZERO, "up_direction should match what it was just set to")

	# Same with the setter/getter.
	set_up_direction(Vector3.ZERO)
	assert(get_up_direction() == Vector3.ZERO, "up_direction should match what it was just set to")

Minimal reproduction project
No response

cc @fabriceci

I've just noticed that it's exclusively Vector3.ZERO that it does not accept.   In fact, there's an entire error I missed.
E 0:00:00:0707   _ready: up_direction can't be equal to Vector3.ZERO, consider using Floating motion mode instead.
Should this be the case?  Maybe it's the documentation that's not caught up yet.  The documentation for CharacterBody3D in this snapshot says If set to Vector3(0, 0, 0), everything is considered a wall. This is useful for topdown games.

Good finding, the documentation does not seem to be up to date, I will update it!

Errr, the up_direction is a normal, and normals can't be zero or a lot of math breaks down. I went and took a quick glance at CharcaterBody3D and it is used a lot for floor siding and other calculations which would break down with zero.
So it's definitely the docs that need to be updated

Ah.  Makes sense.  Given the documentation, I'd just assumed it was an analog/rename of the old snap vector which could be zero.  My bad.


unpacker.next() counterpart

Hi,
in msgpack C++ msgpack::unpacker::next() => returns true if one complete msgpack messege is proccessed.
Is there any counterpart for upacker.next in the msgpack-cli package?

Unpacker.Read(), then get LastReadData.

thanks yfakariya.
I did something wrong on the c++ send side. I just recognized serializer.Unpack is a blocking call and returns only when a complete message is processed.

There is a ReadAsync which is aaynchronous(nonblocking) and awaitable. Note that async method has some overhead, and you should use buffering option on Unpacker.Create.

Closed because it is no response for answer. It is welcome to reopen for further question. Thank you for contribution.


CI: v1.2: Kafka failure has minimal logs

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/7180/testReport/junit/k8s-1/7/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/
In the following failure, the zip file for debugging only contains these files:
cilium_test.log
cmds.log
monitor.log
test-output.log

I would expect full bugtool output, not sure why it is missing.
Stacktrace
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:376
Failed to produce to empire-hq on topic deathstar-plans
Expected
    <*errors.errorString | 0xc42850e820>: {
        s: "ExecKafkaPodCmd: command 'kubectl exec -n default empire-hq-2917507631-2qpsg sh -- -c \"echo 'deathstar reactor design v3' | ./kafka-produce.sh --topic deathstar-plans\"' failed '' || 'The connection to the server <IP_ADDRESS>:6443 was refused - did you specify the right host or port?\n'",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:177
Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Cilium pods: []
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:

Standard Error
STEP: Wait for Kafka broker to be up
STEP: Creating new kafka topic empire-announce
STEP: Creating new kafka topic deathstar-plans
STEP: Waiting for DNS to resolve within pods for kafka-service
STEP: Testing basic Kafka Produce and Consume
=== Test Finished at 2018-10-11T16:09:08Z====
===================== TEST FAILED =====================
===================== Existing AfterFailed =====================

bd4d6df5_K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies.zip

If K8s isn't reachable, there isn't much we can do :/ I think this can be closed.


Update CHANGELOG and remove unused metric

Motivation
Follow up to #6422: Update changlog and remove unused metric.
Description
I forgot to update the changelog and remove the now unused metric, so I created another PR.
Test Plan

TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge

bors merge


Cannot read property 'end' of unedfined

Query: function(string, fn) {
	this.connection.query(string, function(err, rows) {
		if(err) { console.log(err); fn(null); this.connection.end(); }
		else {
			fn(rows);
			this.connection.end();
		}
	});
}

My Query function runs the Query perfectly, but I cannot end the connection afterwards.

Hi! This is a common mistake when first learning JavaScript :) Inside another function (like the callback), the "this" is not the same as in the other function unless you use bind. The best thing to do is simply store the other this in a variable and reference that variable from in the callback:
Query: function(string, fn) {
    var that = this;
    this.connection.query(string, function(err, rows) {
        if(err) { console.log(err); fn(null); that.connection.end(); }
        else {
            fn(rows);
            that.connection.end();
        }
    });
}


[tracy] fix 0.11.1 update, install only release tools

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Update tracy to 0.11.1 and fix tools install to work with release/debug only triplets.

Fix update to 0.11.1 (#40671 broke tracy[cli-tools])
Only build and install tools in the release build

All features are tested successfully in the following triplet:

x86-windows
x64-windows

Duplicate of https://github.com/microsoft/vcpkg/pull/40671, @moritz-h, You don't need to update the version, just treat this PR as a port bug and fix it, because PR https://github.com/microsoft/vcpkg/pull/40671 has updated tracy to the latest version.

@JonLiu1993 Yes I just saw that there was an other PR opened last night which is already merged (and broke tracy[cli-tools]). I will update as soon as possible, but please note that this originally was not a duplicate as the other PR is just 8h old.

Tested usage successfully by tracy:x64-windows:
tracy provides CMake targets:

  # this is heuristically generated, and may not be correct
  find_package(Tracy CONFIG REQUIRED)
  target_link_libraries(main PRIVATE Tracy::TracyClient)


Terraform 1.6

Describe the solution you'd like
Validate support for Terraform 1.6 in Terragrunt
Describe alternatives you've considered
N/A
Additional context
https://github.com/hashicorp/terraform/releases/tag/v1.6.0
https://www.hashicorp.com/blog/terraform-1-6-adds-a-test-framework-for-enhanced-code-validation
https://developer.hashicorp.com/terraform/language/upgrade-guides

With terraform 1.6.0, terragrunt (0.52.0) init fails with this message:

-10-06T09:08:57Z level=error msg=Unable to parse Terraform version output: [command]/home/runner/work/_temp/99eb66ee-b605-4d22-9ab8-d97d2c74e871/terraform-bin --version
Terraform v1.6.0
on linux_amd64

It seems to be failing with terraform 1.5.7 as well.

Ok, will try to verify, it may be a tg bug introduced in 0.52.0

It seems to be failing with terraform 1.5.7 as well.

Can't confirm on MacOSX (M1). For me, terragrunt 0.52.1 works with terraform 1.5.7

1.6.0 added support for Terraform "projects" Would it be possible to add support for this in Terragrunt?
https://developer.hashicorp.com/terraform/cli/cloud/settings#project
Currently, we generate a backend like below but can't find a way to plug in the project without error.
generate "backend" {
path      = "backend.tf"
if_exists = "skip"
contents  = <<EOF
terraform {
backend "remote" {
hostname     = "app.terraform.io"
organization = "XXXXXX"
workspaces {
name = "azure-${local.tenant}-${local.region_abbr}-${local.subscription}-${local.application}-${replace(path_relative_to_include(), "/", "-")}"
}
}
}
EOF
}

terrgrunt init works with tg 0.52.1 and tf 1.6.1 on Mac M1, but not on linux_amd64 (GitHub worker)

I just got this error in Github Actions using hashicorp/setup-terraform@v2. When setting terraform_wrapper: false the error go's away.
So my guess is that somehow the wrapper is messing something up.

terragrunt init works after upgrading version to 0.52.3 with terraform v1.6.1 on Ubuntu 22.04.

Update: It does work with setting terraform_wrapper: false for hashicorp/setup-terraform@v2 action. Still not sure I want to add that config in all repos...

Not all Terragrunt tests are passing with Terraform 1.6, so far found issue https://github.com/hashicorp/terraform/issues/34066 which sometimes appear on projects

@denis256 The issues from #34066 should be fixed as of Terraform 1.6.2.

Hi, I don't see this is fixed. Could someone take a look?

Hi, I don't see this is fixed. Could someone take a look? I use both latest terraform and terragrunt.

Is that GitHub Actions? Can you check how you setup terraform? We had to switch to hashicorp/setup-terraform@v3 (used to use v2)

Thanks, @mgerlach ! It works with hashicorp/setup-terraform@v3.


UI Redesign - Desktop - Settings

Description
The task is to implement the new design for the settings menu in the desktop app.
Assets and Design Screens
All assets and design screens have already been created.

The Figma design can be found here https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=1%3A2
The Assets required can be found here https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=0%3A1

For help with using Figma please watch this short tutorial video
https://user-images.githubusercontent.com/69275762/192322842-2ac40f88-c396-4a66-933b-3c8abae516c3.mov
Additional context
This work should be done on the UI_Redesign branch https://github.com/atsign-foundation/atmosphere_pro/tree/ui_redesign

This is for the web app right? Like I will have to run it on chrome? Can I work on this as well?

Sorry, tested it and it is a desktop app only. Can I work on this issue?

@AdiAr11 sure

Hi, I think there is nothing much in the settings screen besides the background and a search button. Should I first create the navigation menu in the left and add the settings screen after that?
Also is there a discord group or something so that I can communicate with you faster?
Thank you!

@AdiAr11 the graphics are already created under the Design Systems link - https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=0%3A1

Hi. yes I've seen the design. https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=1%3A2
If you see here the settings page for desktop doesn't have much except a background and a search icon. is it in development or is that what i have to make?
Thank you

@AdiAr11 Apologies, the detail on this was missed. It needs to have functionality to allow people to switch atSign, delete atSign and backup their keys. You can refer to the current version of the app to see how this functionality works. For now it could be 3 buttons as shown in the mobile version, but if you would like to create the screens for the functionality, that would be fine too. We would then bump this up to an intermediate issue card

@tinashe404 Sure, I'll take a look at the mobile app and take inspiration from there. Thank you

Hi @tinashe404 I'm sorry but this issue was assigned to me and I also have started working on this.


diff() returns -0 for the exact same 'start of' day

-0 (negative zero) seems to be expected behavior in certain cases (see issues #2503 and #2590).  The recommendation is to use startOf('day') when comparing dates based on the discussion in these tickets.
But if you run the following comparison using the exact same timestamp:
var moment = require('moment-timezone');

function isNegative(n) {
  return (1 / n) < 0;
}

var ts = '1977-05-12 00:00:00.000';
var format = 'YYYY-MM-DD hh:mm:ss.SSS';
var timezone = 'America/Los_Angeles';

var d1 = moment(ts, format).tz(timezone).startOf('day');
var d2 = moment(ts, format).tz(timezone).startOf('day');

console.log('Diff on years is negative zero?: ' + isNegative(d2.diff(d1, 'years')));
console.log('Diff on months is negative zero?: ' + isNegative(d2.diff(d1, 'months')));
console.log('Diff on days is negative zero?: ' + isNegative(d2.diff(d1, 'days')));

The resulting output will be:
Diff on years is negative zero?: true
Diff on months is negative zero?: true
Diff on days is negative zero?: false

You can verify this using this jsfiddle link.
It seems inconsistent that years and months are -0 but days is regular +0 for what should be the exact same point in time.
A few other things to note:

I get the same result even if I don't use moment-timezone
This does not occur for versions prior to 2.9.0 (e.g. version 2.8.4 does not have this issue)

I'm currently employing a workaround of explicitly adding +0 to ensure I don't encounter -0 as follows:
console.log('Diff on years is negative zero?: ' + isNegative(d2.diff(d1, 'years') + 0));

If behavior is not a bug, would it be possible to update the moment.js documentation to provide an explanation and suggested workaround.
(P.S. Thanks for a great library!!)

It definitely looks like a bug, and thanks for the nice writeup. I think we'd accept a patch for this.
It sounds like the bug may be in moment-timezone? If so, it might make more sense to file the bug there.

Fixed in #3059


Smart City Infrastructure Enhancement Using IoT, AI, and Quantum Computing

Capstone
Dataset:

Publicly available datasets on urban infrastructure, energy consumption, traffic patterns, environmental data (e.g., pollution levels), and public safety records.

Question:

How can the integration of IoT, AI, and quantum computing optimize urban infrastructure for improved sustainability, security, and efficiency?

Project Steps:

Data Collection:

Gather data from IoT sensors placed throughout the city (e.g., traffic cameras, pollution sensors, energy meters).

Data Processing and Analysis:

Use AI algorithms to analyze the data, identify patterns, and make predictions (e.g., traffic congestion, energy demand).

Quantum Computing Integration:

Apply quantum algorithms to solve complex optimization problems, such as efficient energy distribution and traffic flow management.

Implementation:

Develop a prototype system that integrates IoT sensors, AI models, and quantum computing capabilities.

Testing and Validation:

Test the system in a controlled environment, evaluate its performance, and make necessary adjustments.

Documentation:

Document the methodology, results, and potential areas for improvement.

Why This Works/Doesn't Work:

A detailed analysis of the successes, challenges, and limitations encountered during the project.

This project aims to demonstrate how cutting-edge technologies can collaborate to create smarter, more sustainable urban environments.

Project: Torremolinos-Sensor-Data
Objective:
Develop a comprehensive program and proposal for Torremolinos to enhance the city’s infrastructure through real-time data collection from sensors, databases, and public devices. The goal is to attract quality tourism for Europride 2027.
Key Points:

Data Collection: Real-time data from various sensors and devices.
Database Integration: Centralized data repository for analysis.
Smart City Proposal: Create a detailed plan to improve urban infrastructure and sustainability.

For more details, visit the GitHub issue. https://github.com/AdLinke-Media/Robbbo-T/commit/41615925a637560e46f38ec20234ac2df2738053

Summary of Capstone Project: Smart City Infrastructure Enhancement Using IoT, AI, and Quantum Computing
Objective:
Develop a program to optimize urban infrastructure in Torremolinos using IoT, AI, and quantum computing, aimed at improving sustainability, security, and efficiency for Europride 2027.
Key Steps:

Data Collection: Deploy IoT sensors to gather real-time data.
Data Processing: Analyze data with AI algorithms.
Quantum Integration: Use quantum algorithms for optimization.
Implementation: Create and test a prototype system.
Documentation: Detail methodologies and results.

For more details, visit the GitHub issue.

Best Smart City Model by Ampel Systems
Objective:
Develop an advanced smart city model to enhance urban living through the integration of IoT, AI, and quantum computing.
Key Components:

IoT Integration:

Deploy sensors for real-time data collection on traffic, environment, and public safety.

AI Analytics:

Use AI for data processing, pattern recognition, and predictive analytics to optimize city services.

Quantum Computing:

Implement quantum algorithms for complex optimization tasks like traffic management and energy distribution.

Sustainability:

Focus on green technologies and sustainable urban planning to reduce carbon footprint.

Citizen Engagement:

Develop user-friendly interfaces for citizens to interact with city services and provide feedback.

Implementation Steps:

Data Collection:

Install and configure IoT devices across the city.
Ensure secure data transmission to a centralized repository.

Data Processing:

Utilize AI models to analyze collected data and generate actionable insights.

Optimization:

Apply quantum computing to solve intricate urban challenges and improve efficiency.

Visualization:

Create real-time dashboards for city officials and applications for citizens to access data and services.

Testing and Iteration:

Pilot the system in specific areas, evaluate performance, and iterate based on feedback.

Scalability:

Plan for scalability to expand the model to other urban areas or cities.

Outcome:
A smart city model that leverages cutting-edge technology to improve urban infrastructure, enhance sustainability, and engage citizens, making Torremolinos a benchmark for future urban developments.


Transcription versus regulation of transcription

Hello,
During our discussion with Ruth and Marcio yesterday we came up with the following proposal:
Transcription by the different polymerases always takes place via the same process, regardless of the transcription being produced.
The types of proteins mediating those processes are: polymerase, GTFs and Mediator.
For example:
GO:0042796	snRNA transcription from RNA polymerase III promoter
GO:0042797	tRNA transcription from RNA polymerase III promoter
are mediated by the same proteins that mediate
GO:0006383	transcription from RNA polymerase III promoter
Hence these should be merged.
Regulation of transcription of these different transcripts is what (potentially) changes. The types of proteins mediating those processes are specific tx factors.
For eg for snRNA: existing terms:
GO:1905380	regulation of snRNA transcription from RNA polymerase II promoter
GO:1905381	negative regulation of snRNA transcription from RNA polymerase II promoter
GO:1905382	positive regulation of snRNA transcription from RNA polymerase II promoter
(well they should match in terms of the polymerase... another thing to worry about)
Logical definitions:
GO:1905380 regulation of snRNA transcription from RNA polymerase II promoter
CURRENT:
biological_process
and (regulates some 'snRNA transcription by RNA polymerase II')
PROPOSED:
'biological regulation'
and (regulates some 'transcription by RNA polymerase II')
and ('has output' some snRNA)

@RLovering @krchristie @thomaspd @ValWood @ukemi @vanaukenk
Are you OK with this proposal ?
Thanks, Pascale

I agree that this proposal was conflating multiple things incorrectly. See new proposal: #14998

new proposal coming soon.


changeset not working on pnpm workspace exclude rules

Affected Packages

pkg: git
pkg: apply-release-plan
pkg: release-utils
pkg: get-dependents-graph
pkg: pre
pkg: config
pkg: cli
pkg: assemble-release-plan
pkg: get-release-plan
Problem

pnpm-workspace.yaml:
packages:
  # all packages in subdirs of packages/ and components/
  - 'packages/**'
  # exclude packages that are inside test directories
  - '!**/test/**'

project:
  - test
    - packages
      - pkg-1   # (need)
      - pkg-2  # (need)
      - test   # (not need)
    - pnpm-workspace.yaml

if project absolute cwd path matches the pnpm workspace exclude rule, getPackages won't get any packages.
Proposed solution

fixed in https://github.com/Thinkmill/manypkg/pull/122 .
After the @manypkg is released, changeset dependencies need upgrade

Thank you for the fix, we'll have to await @mitchellhamilton's approval and the downstream release


toBeDisabled matcher proposal

Describe the feature you'd like:
I would like to have a matcher that would check if the form element is disabled from user's perspective.
In this case, simply checking the 'disabled' attribute is not enough.
Describe alternatives you've considered:
In many cases .toHaveAttribute('disabled') is sufficient alternative.
But I think that the dedicated matcher would be less dependent on the implementation details
Teachability, Documentation, Adoption, Migration Strategy:
Examples and comparison with toHaveAttribute matcher.
// in simple cases toHaveAttribute and toBeDisabled behave the same

// ...
// <button disabled={true}>CLICK</button>
expect(getByText(container, 'CLICK')).toHaveAttribute('disabled')
expect(getByText(container, 'CLICK')).toBeDisabled()
// ...

// toBeDisabled can detect when a disabled state is inherited

// ...
// <fieldset disabled={true}><button>CLICK</button></fieldset>
expect(getByText(container, 'CLICK')).not.toHaveAttribute('disabled')
expect(getByText(container, 'CLICK')).toBeDisabled()
// ...

// 'a' element is not disabled, even if it has the 'disabled' attribute

// ...
// CLICK
expect(getByText(container, 'CLICK')).toHaveAttribute('disabled')
expect(getByText(container, 'CLICK')).not.toBeDisabled()
// ...

I think this would be great 👍

I'm happy that you like the idea. I can send PR for this feature.

This is great. I did not think before about disabled being inherited by child elements, so it makes sense to make it easy and declarative to check for that.
I have one question though: why this?
// 'a' element is not disabled, even if it has the 'disabled' attribute

I assume it is documented somewhere, so I'd like to learn about that. Why this special treatment with a elements?

There are only 7 elements that can be actually disabled. Other elements are not disabled by the disabled attribute, a element is not special here.

Implemented by @callada in #19


services_cli: Fix list command wrongly showing root user as owner

When running brew services with a couple of services started as a normal user, and one service started as root, this was the output:

➜ brew services
Name       Status  User   Plist
mosquitto  started issyl0 /Users/issyl0/Library/LaunchAgents/homebrew.mxcl.mosquitto.plist
postgresql started   issyl0 /Users/issyl0/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
vault      error   root /Library/LaunchDaemons/homebrew.mxcl.vault.plist

When running sudo brew services with the same combination of services, this was the output:

➜ sudo brew services
Password:
Name       Status  User Plist
mosquitto  started root /Users/issyl0/Library/LaunchAgents/homebrew.mxcl.mosquitto.plist
postgresql started root /Users/issyl0/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
vault      error   root /Library/LaunchDaemons/homebrew.mxcl.vault.plist

That is, the User column always showed root for all started services. That's because the started?(as: :user) conditional wrongly used the user invoking the [sudo] brew services command as the owning user for that process.

This change fixes that by parsing the user_path for just the started?(as: :user) part of the if condition, and getting the username out of it.

Fixes #287.

Force-pushed to appease RuboCop.

This approach would only show started processes with populated User data, because errored processes don't have PIDs.

I think this would be ok! They could either not show the user at all or fall back to the existing logic?

Also, getting user info through ps, sudo brew services would display no user information for processes that weren't started as root.

Can you explain this a bit more, I'm not sure I understand?

@MikeMcQuaid The fallback to using ENV["HOME"] if no PIDs are found solves the "sudo brew services doesn't work" part of my previous comment.

Code makes sense to me as-is! Unfortunately it looks like CI is broken 😅

The tests pass fine for me locally. I don't have enough permissions here to re-run CI to see if it was just a temporary blip.

@issyl0 Failed twice in a row here I'm afraid 😭

@MikeMcQuaid 😭 I'll dig into it tonight!

I've tested this branch on two separate MacBooks (one Catalina and one Big Sur) and I can't reproduce the brew services start mysql failures. I enabled GitHub Actions on my fork, and it fails with the same error message both on this branch and master (link to master branch run). So it must be an Actions hosted runners thing. 😕

@issyl0 Could try to bump the sleep or improve the debugging output on failure?

Nice fix and work here in general, thanks @issyl0!

Thanks much, @issyl0! I just confirmed that it's working on my box.

Hurray! 🎉


[Feature Request] update and delete index operation on Weaviate vectorstore

Feature request
Currently, Weaviate vectorstore doesn't provide option for updation of vector embeddings on existing index and deletion of index.
Motivation
This feature request is related to an experiment project for which we need CRUD operations on Weaviate vectorstore.
Your contribution
I can provide my contribution if no one is currently working on this request.

Not sure if I should write this or if it's considered spam, but I'd love to have this included in the library as well.

@Ryangr0  Are you or someone else working on this issue?
or, do you want my contribution to this feature?


add support for watchpoint on kernel space address

Description
Add support for watchpoint on absolute kernel space address, so the following command can run correctly:
# bpftrace -e "watchpoint::0x$(awk '$3 == "jiffies" {print $1}' /proc/kallsyms):8:w {@[kstack] = count();}"
Attaching 1 probe...
^C
@[
    do_timer+12
    tick_do_update_jiffies64.part.22+89
    tick_sched_do_timer+103
    tick_sched_timer+39
    __hrtimer_run_queues+256
    hrtimer_interrupt+256
    smp_apic_timer_interrupt+106
    apic_timer_interrupt+15
    cpuidle_enter_state+188
    cpuidle_enter+41
    do_idle+536
    cpu_startup_entry+25
    start_secondary+355
    secondary_startup_64+164
]: 319

Checklist

[x] Language changes are updated in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

@fbs Do you think this should be a squash + rebase + merge or just rebase + merge?

Looking at the individual commit messages an rebase+merge seems ok to me.  But for cases where its a simple add test for a single change a squash sounds better to me


Assign: Eligibility error should give the precise problem

Currently it gives a list of possible problems, which is long and doesnt give precise guidance for what is the next step
Opened by @jayvdb at Gitter

@palash25 are u still working on the issue?

@prashant0598 I was going to but can't due to exams so you may go ahead.

Please also read this gitter discussion to get the things more clear https://gitter.im/coala/corobo?at=5a20304dcc1d527f6bd4b3b8

https://github.com/coala/corobo/issues/296 must be finished first

How is that a blocker for this one?

It was blocked during GCI as there should only ever be one issue available about a single area of code, otherwise we end up with one student making the other students valid work unmergable, which is deeply unfair.  #296 already had a PR.
Anyway, I have closed that PR, and unblocking this.
This one could easily solve #296 at the same time.


presto-admin: make presto-admin parse teradata versions

Now we are checking that presto is installed before checking version using 'rpm -q presto' and 'rpm -q presto-server-rpm'.
So, now we will get 'Presto is not installed' message just in case when presto is not installed at all.
Then if presto is installed, we are trying to parse presto version usin '(\d+).(\d+)t?([-.]SNAPSHOT)?' regexp.
First group - is the major version, second group is the minor version.
This regexp should parse all possible versions including teradata ones and snapshot ones.
When version doesn't match this pattern we are showing to user 'Incorrect presto version' message
instead of telling him that presto is not installed at all.
Testing: manual

Can you please run "make test" to check unit tests are passing and also run product tests for install and uninstall?

@ilfrin: presto-admin is meant to work with all version of Presto -- 115, 115t, and any SNAPSHOT version.
@arhimondr: Please also run make lint, if you haven't already, and the status product tests.

@cawallin I know, but my point is now if you say it needs 115 if will accept ANY 115 flavor, there is no way of stating that I want a vanilla 115 or a TD 115 build.

@ilfrin All this check is doing is seeing if the Presto version is compatible with this version of presto-admin. Since there aren't breaking changes between 0.115 and 0.115t, this is fine.  Hopefully there will never be changes that are that significant, but if there are we can do version checking differently then.

looks good % changes

@cawallin got it, thanks, we'll revisit this if it creates any issues.

@cawallin
Lint, unit tests and product tests are passing. I'm going to merge it into the master.

Thank you Andrii.
czw., 20 sie 2015, 22:39 Andriy Rosa użytkownik<EMAIL_ADDRESS>napisał:

Merged #38 https://github.com/prestodb/presto-admin/pull/38.
—
Reply to this email directly or view it on GitHub
https://github.com/prestodb/presto-admin/pull/38#event-388125689.


Byproduct reconstruction mesh files

Hi, I'm wondering if the mesh files are contained in the result generate by eval.py, or I need to find ways to generate them manually?
Also, I met a problem when I try to generate result by instruction provided in README, which the eval.py only generate empty folder, could you kindly tell me where is the problem?
Thank you!

Hi，

for export mesh, you could try to add a export_mesh function after optimizing shape.
maybe your test data path is empty, check your data path first.

I solved my problem and also got reconstructed mesh, thanks for your response!


Don't use internal-buffer style name in follow mode

Missed in #98, since it derived from #89.

Self-merging this simple bugfix.