How can I change the interval for when the checks are performed?

I would like to shorten the interval for checks from 30min

theres a --refresh-interval flag for it.

i was also wondering how i could change the interval in the best way, since there was no mention of it in the readme.
as an approvement, maybe the --refresh-interval flag can be documented better in the readme. :)


Consider publishing WALT results on a public website

After users run a test they could be given the option to upload the results to a server (Firebase? GAE?) which would then display a filterable list of devices and measurements.

See separate email

For now added some sample numbers for several Nexus devices in the markdown docs here.
e.g: dda75831bf9df43167764964bd809b898bc7913c

Hi, I would be interested in this enhancement as well.
I noticed the Superpowered site (https://superpowered.com/latency) in @kamrik 's comment. Does anyone know of any formal tests looking at if audio latency is correlated strongly with tap latency or screen latency?

This is old topic, but I started to measure and list tap/screen drawing latency and audio output latency with WALT:
https://androplus.org/en/entry/android-smartphone-benchmark-results/#Tap_and_screen_latency
Hope this helps someone.

@AndroPlus-org This is pretty cool, thanks for testing, publishing and sharing this information.


feat: add Northwest Florida State College to edu list

The university official website URL : https://nwfsc.edu
The university address: 100 College Blvd E, Niceville, FL 32578, U.S
IT-related courses: https://www.nwfsc.edu/academics/degrees-offered/computer-programming-and-analysis

@aow3xm I am sorry, the domain nwfsc.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Pack at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Fix Odata Client docs broken links

Docs Build status updates of commit 4f486ae:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

Odata-docs/client/annotation-support.md
:x:Error

Details

Odata-docs/client/async-operations.md
:x:Error

Details

Odata-docs/client/basic-crud-operations.md
:x:Error

Details

Odata-docs/client/batch-operations.md
:x:Error

Details

Odata-docs/client/code-generation-tool.md
:x:Error

Details

Odata-docs/client/get-response-content.md
:x:Error

Details

Odata-docs/client/getting-started.md
:x:Error

Details

Odata-docs/client/navigation-properties.md
:x:Error

Details

Odata-docs/client/pagination.md
:x:Error

Details

Odata-docs/client/query-options.md
:x:Error

Details

Odata-docs/client/tracking.md
:x:Error

Details

Odata-docs/client/using-extensions.md
:x:Error

Details

Odata-docs/client/using-hooks.md
:x:Error

Details

Odata-docs/client/using-httpclient.md
:x:Error

Details

Odata-docs/extensions/migration.md
:warning:Warning

Details

Odata-docs/client/annotation-support.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/async-operations.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/basic-crud-operations.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/batch-operations.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/code-generation-tool.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/get-response-content.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/getting-started.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.
Line 35, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-0-4-0-extension-download.png'.
Line 40, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-add-connected-service-menu.png'.
Line 42, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-connected-services-window-OCS.png'.
Line 49, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-added-to-project.png'.
Line 140, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-sample-program-output.png'.

Odata-docs/client/navigation-properties.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/pagination.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/query-options.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/tracking.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-extensions.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.
Line 13, Column 94: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-hooks.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-httpclient.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/extensions/migration.md

Line 124, Column 1: [Warning-sensitive-language-ma] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'This project uses the master branch for development.  '
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'aayc' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4f486ae:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

Odata-docs/client/annotation-support.md
:x:Error

Details

Odata-docs/client/async-operations.md
:x:Error

Details

Odata-docs/client/basic-crud-operations.md
:x:Error

Details

Odata-docs/client/batch-operations.md
:x:Error

Details

Odata-docs/client/code-generation-tool.md
:x:Error

Details

Odata-docs/client/get-response-content.md
:x:Error

Details

Odata-docs/client/getting-started.md
:x:Error

Details

Odata-docs/client/navigation-properties.md
:x:Error

Details

Odata-docs/client/pagination.md
:x:Error

Details

Odata-docs/client/query-options.md
:x:Error

Details

Odata-docs/client/tracking.md
:x:Error

Details

Odata-docs/client/using-extensions.md
:x:Error

Details

Odata-docs/client/using-hooks.md
:x:Error

Details

Odata-docs/client/using-httpclient.md
:x:Error

Details

Odata-docs/extensions/migration.md
:warning:Warning

Details

Odata-docs/client/annotation-support.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/async-operations.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/basic-crud-operations.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/batch-operations.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/code-generation-tool.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/get-response-content.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/getting-started.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.
Line 35, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-0-4-0-extension-download.png'.
Line 40, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-add-connected-service-menu.png'.
Line 42, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-connected-services-window-OCS.png'.
Line 49, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-added-to-project.png'.
Line 140, Column 1: [Warning-file-not-found] Invalid file link: '../../assets/2020-03-06-OCS-sample-program-output.png'.

Odata-docs/client/navigation-properties.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/pagination.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/query-options.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/tracking.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-extensions.md

Line 13, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.
Line 13, Column 94: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-hooks.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/client/using-httpclient.md

Line 12, Column 17: [Error-include-not-found] Invalid include link: '../../includes/appliesto-odataclient-v7.md'.

Odata-docs/extensions/migration.md

Line 124, Column 1: [Warning-sensitive-language-ma] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'This project uses the master branch for development.  '
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'aayc' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 51c7b99:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/extensions/migration.md
:warning:Warning
View
Details

Odata-docs/client/annotation-support.md
:white_check_mark:Succeeded
View

Odata-docs/client/async-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/basic-crud-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/batch-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/code-generation-tool.md
:white_check_mark:Succeeded
View

Odata-docs/client/get-response-content.md
:white_check_mark:Succeeded
View

Odata-docs/client/getting-started.md
:white_check_mark:Succeeded
View

Odata-docs/client/navigation-properties.md
:white_check_mark:Succeeded
View

Odata-docs/client/pagination.md
:white_check_mark:Succeeded
View

Odata-docs/client/query-options.md
:white_check_mark:Succeeded
View

Odata-docs/client/tracking.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-extensions.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-hooks.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-httpclient.md
:white_check_mark:Succeeded
View

Odata-docs/extensions/migration.md

Line 124, Column 1: [Warning-sensitive-language-ma] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'This project uses the master branch for development.  '
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'aayc' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 51c7b99:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/extensions/migration.md
:warning:Warning
View
Details

Odata-docs/client/annotation-support.md
:white_check_mark:Succeeded
View

Odata-docs/client/async-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/basic-crud-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/batch-operations.md
:white_check_mark:Succeeded
View

Odata-docs/client/code-generation-tool.md
:white_check_mark:Succeeded
View

Odata-docs/client/get-response-content.md
:white_check_mark:Succeeded
View

Odata-docs/client/getting-started.md
:white_check_mark:Succeeded
View

Odata-docs/client/navigation-properties.md
:white_check_mark:Succeeded
View

Odata-docs/client/pagination.md
:white_check_mark:Succeeded
View

Odata-docs/client/query-options.md
:white_check_mark:Succeeded
View

Odata-docs/client/tracking.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-extensions.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-hooks.md
:white_check_mark:Succeeded
View

Odata-docs/client/using-httpclient.md
:white_check_mark:Succeeded
View

Odata-docs/extensions/migration.md

Line 124, Column 1: [Warning-sensitive-language-ma] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'This project uses the master branch for development.  '
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'aayc' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


eth_nxp_enet_qos: implement set_config

implements  the set_config api for the eth_nxp_enet_qos_mac driver as in FRDM_MCXN947

Hi, the PR looks good at a glance, I will review more when I get a chance. For now make sure you ran the scripts/ci/check_compliance script and passed (expect clang format check is optional, the driver might already not pass clang format)

@theadib thankyou for the contributions. Can you address the compliance issue:
Commit message body line exceeds max length (85>75): "implements  the set_config api for the eth_nxp_enet_qos_mac driver as in FRDM_MCXN947"


Add boardgame.io

Why do you think the link is worth adding on this list?
boardgame.io is a popular JS game engine with over 8k stars on GitHub.
Does this project has any License?
MIT

thanks @delucis


[master] Bump Mesos to nightly 1.7.x 8419b87

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/dcos/dcos-mesos-modules/compare/29561f11a12372752b77839be73418d1d75abe63...a005574630b114babdd1ca06ba07d9f5da2ab5a3

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

Closing this because DC/OS master is now 1.13-dev which should be pointed to Mesos master.


Update README.md

This doesn't make sense to add and doesn't serve any useful purpose. If it's useful for someone, then it is, you don't need to say that right at the start of the README.

@GhostofGoes This is a cheap attempt at a PR for Hacktoberfest. You should mark it as spam or invalid with a label.

@spikespaz Thanks for reminding me. I had reported abuse, but learned that's not the way you're supposed to do it via a nice message from GitHub support 😅


Initial version of modGui

Description
Initial version of Aion kernel GUI.  Supports a single use case: open GUI, launch the kernel, exit GUI, re-open GUI, terminate kernel.
Dependencies

aion_api: needed small change to postpack.sh script.  It is pushed to remote branch but not yet merged into dev of aion_api: https://github.com/aionnetwork/aion_api/commits/dev-modGui

Note on class/code design:
The GUI application code uses a variation of MVC.  For us, we'll divide up the
responsibilities into the following layers:

1) Model: any class that interfaces with components outside of the GUI; i.e. KernelLauncher
   for interface with the OS to launch processes; KernelConnection provides interface to
   Aion API.  The state of Aion API lives in the model layer.  The model does not know about
   Controller or View, it just publishes events into an EventBus.

2) View: the layer that contains the UI elements; i.e. all of the JavaFX .fxml files.  The
   elements in the View (i.e. a Button) have associated handler methods, which are part of
   Controller.  Through these associated methods, View knows about Controller and
   delegates control to classes/methods in Controller.  The View is very "dumb" and doesn't
   have logic to modify itself.

3) Controller: this layer mediates interaction between Model and View by serving two purposes:
     (a) Contains handlers to which the View is registered (through the view's FXML).
         Usually these handlers manipulate Model through some method call.  The heavy
         lifting of the logic should live in Model.
     (b) Subscribe to events published by Model and update View accordingly.  Events that it
         may need to handle include kernel state change (e.g. # of peers).  EventBus is the
         mechanism used to facilitate PubSub pattern.
   Generally, each View component has one or zero accompanying classes that are part of the
   Controller layer (usually a class name ending with "Controller").  Within it are the
   handlers for its corresponding View and also handlers for Model events that would cause a
   change in that View component.

Depending on how the code develops we can revisit this.  The fact that Controller layer has
two purposes may end up getting unwieldy; if so, maybe move (a) into the responsibility of
View or call it out as something else ("View controller"?).

Type of change
Insert x into the following checkboxes to confirm (eg. [x]):

[ ] Bug fix.
[x] New feature.
[ ] Enhancement.
[x] Unit test.
[ ] Breaking change (a fix or feature that causes existing functionality to not work as expected).
[ ] Requires documentation update.

Testing

58% lines coverage for unit and integ tests.  Most of the uncovered lines come from classes that will likely change when developing the next feature.  Jenkins output: https://ci.aion.network:8443/job/aionnetwork/job/dev-modGui2/1/
unit tests for most Model classes
integ tests for most Controller classes and accompanying Views
manual testing of GUI

Verification
Insert x into the following checkboxes to confirm (eg. [x]):

[x] I have self-reviewed my own code and conformed to the style guidelines of this project.
[x] New and existing tests pass locally with my changes.
[x] I have added tests for my fix or feature.
[ ] I have made appropriate changes to the corresponding documentation. [there is none currently]
[x] My code generates no new warnings.
[x] Any dependent changes have been made.

Is this the final version of the first phase of modGui? @aion-kelvin @AionJayT


ReactNative - Could not find "store"error after upgrading to 6.0.0 (from 5.1.1)

Do you want to request a feature or report a bug?
bug
What is the current behavior?
I get an error:

Invariant Violation: Could not find "store" in the context of "Connect(Home)". Either wrap the root component in a , or pass a custom React context provider to  and the corresponding React context consumer to Connect(Home) in connect options.

This error is located at:
in Connect(Home) (created by SceneView)
in SceneView (at createTabNavigator.js:39)
in RCTView (at View.js:45)
in AnimatedComponent (at BottomNavigation.js:576)
in RCTView (at View.js:45)
in AnimatedComponent (at BottomNavigation.js:561)
in RCTView (at View.js:45)
in RCTView (at View.js:45)
in BottomNavigation (created by Context.Consumer)
in ThemeProvider (created by Context.Consumer)
in withTheme(BottomNavigation) (at createMaterialBottomTabNavigator.js:51)
in BottomNavigationView (at createTabNavigator.js:197)
in NavigationView (created by Navigator)
in Navigator (created by SceneView)
in SceneView (at StackViewLayout.js:793)
in RCTView (at View.js:45)
in AnimatedComponent (at StackViewCard.js:69)
in RCTView (at View.js:45)
in AnimatedComponent (at screens.native.js:58)
in Screen (at StackViewCard.js:57)
in Card (at createPointerEventsContainer.js:27)
in Container (at StackViewLayout.js:858)
in RCTView (at View.js:45)
in ScreenContainer (at StackViewLayout.js:311)
in RCTView (at View.js:45)
in AnimatedComponent (at StackViewLayout.js:307)
in Handler (at StackViewLayout.js:300)
in StackViewLayout (at withOrientation.js:30)
in withOrientation (at StackView.js:79)
in RCTView (at View.js:45)
in Transitioner (at StackView.js:22)
in StackView (created by Navigator)
in Navigator (at createKeyboardAwareNavigator.js:12)
in KeyboardAwareNavigator (created by SceneView)
in SceneView (created by SwitchView)
in SwitchView (created by Navigator)
in Navigator (at createAppContainer.js:388)
in NavigationContainer (at App.js:57)
in WrappedRoot (created by NamespacesConsumerComponent)
in NamespacesConsumerComponent (created by WithMergedOptions)
in WithMergedOptions (created by Context.Consumer)
in WithMergedOptions(NamespacesConsumerComponent) (created by LoadNamespace)
in LoadNamespace (created by WithMergedOptions)
in WithMergedOptions (created by Context.Consumer)
in LoadNamespace(WrappedRoot) (at App.js:64)
in Provider (at App.js:46)
in I18nextProvider (at App.js:45)
in App (at renderApplication.js:34)
in RCTView (at View.js:45)
in RCTView (at View.js:45)
in AppContainer (at renderApplication.js:33)
renderWrappedComponent
index.bundle?platform=ios&dev=true&minify=false:171398:34
updateContextConsumer
index.bundle?platform=ios&dev=true&minify=false:16716:31
performUnitOfWork
index.bundle?platform=ios&dev=true&minify=false:19453:27
workLoop
index.bundle?platform=ios&dev=true&minify=false:19487:47
renderRoot
index.bundle?platform=ios&dev=true&minify=false:19558:21
performWorkOnRoot
index.bundle?platform=ios&dev=true&minify=false:20278:23
performWork
index.bundle?platform=ios&dev=true&minify=false:20205:30
performSyncWork
index.bundle?platform=ios&dev=true&minify=false:20181:20
requestWork
index.bundle?platform=ios&dev=true&minify=false:20060:26
scheduleWork
index.bundle?platform=ios&dev=true&minify=false:19932:22
enqueueSetState
index.bundle?platform=ios&dev=true&minify=false:14373:23
setState
index.bundle?platform=ios&dev=true&minify=false:5045:37

index.bundle?platform=ios&dev=true&minify=false:86047:26
tryCallOne
index.bundle?platform=ios&dev=true&minify=false:3044:16

index.bundle?platform=ios&dev=true&minify=false:3145:27
_callTimer
index.bundle?platform=ios&dev=true&minify=false:24010:17
_callImmediatesPass
index.bundle?platform=ios&dev=true&minify=false:24046:19
callImmediates
index.bundle?platform=ios&dev=true&minify=false:24265:33
__callImmediates
index.bundle?platform=ios&dev=true&minify=false:2439:35

index.bundle?platform=ios&dev=true&minify=false:2276:34
__guard
index.bundle?platform=ios&dev=true&minify=false:2422:15
flushedQueue
index.bundle?platform=ios&dev=true&minify=false:2275:21
What is the expected behavior?
It worked fine in 5.1.1
Which versions of Redux, and which browser and OS are affected by this issue? Did this work in previous versions of Redux?
React Native

I have the same problem

Directly as a prop
 render() {
    return (
        <I18nextProvider i18n={i18n}>
            <Provider store={store}>
                {this.getRequiredStack()}
            </Provider>
        </I18nextProvider>)
   }

What version of React and React Native are you using?

"react-native": "0.57.7"
"react": "16.6.1"

"react-native": "0.57.7"
"react": "16.6.1"

I use the same version as well

Same, but without React Native.

For anyone experiencing this issue, please provide a CodeSandbox or similar project that reproduces the issue.  What I've seen since the release is that this is usually a misconfiguration in your application.

And here's a really simple example with 6.0 installed: https://snack.expo.io/@timdorr/react-redux-6

https://repl.it/repls/StrangeModernGraphs Hope it helps, I've never done this before. It's a micro-version of my repo Okulys Color Tests

@Clebal: aha.  It's because you're trying to define your own custom store context instance and passing that to <Provider store={store} context={StoreContext}>, but you're not passing that same context object to the connected component.
You shouldn't need to define a custom context object, except in exceedingly rare cases.  Just do <Provider store={store}>.
Also, FYI, you can simplify the connect usage:
const mapDispatch = {
  attemptAddComparisonTest,
  cleanError,
}

export default connect(mapStateToProps, mapDispatch)(ComparisonTest)

Thanks for the advice, @markerikson. I've deleted context attribute from Provider, but the problem just moved from the server to the client, the error now appears in Chrome console:

I'm trying to reproduce that error in repl.it.

@markerikson @timdorr https://codesandbox.io/s/v8796vz3m5 Any doubt, just tell me.

After many hours I've found the silly error, my code was importing connect from 'react-redux/lib/connect/connect' instead of 'react-redux'.

It has problem on SwitchNavigator works fine on first stack doesn't work on second

As I said, it sounds like pretty much every example of this that is popping up is an app misconfiguration issue.
@alexandrius, can you clarify why you had imports that looked like that?  We've never suggested that pattern.

@markerikson I believe WebStorm imported this way

VS Code did the same bad job as WebStorm

Nope. Maybe they're doing deeper package inspection. It's nothing we're doing, though.

Like you, I had the same bug.
In my case, the reason was that we use company private npm modules.
Each module there was a dependency on redux and react-redux.
Version 5 worked fine with this structure,
but starting from version 6th,
the  and connect()
should be imported from the same "node_modules/react-redux" folder.
When using "npm link moduleA" this error occurred.
Solution:
Import "react-redux" and "redux" from "node_modules"
only Once in one of your npm modules (for example in "moduleA").
All others projects should do:
import { Provider, connect } from 'moduleA/reactRedux';

Downgrading Redux from 4.0.1 to 3.0.1 solved an issue.

@helenkapatsa : that sounds extremely odd.  The specific version of Redux shouldn't matter here.  (Also, there's no reason you should be using Redux 3.0 at this point - the latest 3.x version is 3.7.2.)

I'm still hitting this issue with React Native 0.59.2. Besides downgrading Redux, did anyone find a solution to this?

When it comes to an educational project with existing education repo, sometimes copying all the dependencies version into my package.json and running 'npm install' helps, so that dependencies compatibility issue is resolved by somebody else.

I've noticed I only get this error in components that have been connected to Redux store that are nested inside components already connected via connect() from react-redux.
Say I got this kind of component hierarchy:

Provider

App

connect(mappedProps)(ConnectedComponent)

ConnectedComponent

connect(mappedProps)(ConnectedSubComponent)

ConnectedSubComponent

So it would crash at the deeper nested connect with this Invariant Violation error.
I should be able to plug into the store via a deep nested component/connect like that right?

@tuomohopia : if you can provide a small project that reproduces the issue separately, that would help.
But yes, in general, you should be able to nest connected components as much as you want.

@markerikson yeah I understand we need to produce a code base where this happens get to the bottom of this, I'm trying to put one together as my own is large and not open source.

@markerikson I've now managed to reproduce the error in a new project. In my case, it was produced by placing a connected component inside another library's component (react-native-popup-dialog).
Looks like at least in my code base it did not have anything to do with react-redux itself. It's good that you pushed me to replicate this in a new code base so we got to isolate the problem to another library!

In case anyone has the same problem I filed a bug report here:
https://github.com/jacklam718/react-native-popup-dialog/issues/168
This is the code base I used to replicate the issue with:
https://github.com/tuomohopia/reduce-fail

@tuomohopia : yep, exactly :)  Every case of this we've seen so far has been some kind of a build configuration issue.

I'm having the same issue.  In my case my server side Provider is part of another "shared" library in my private npm repo.  When I pull from my repo, it works fine.  When I npm link to this repo I get the error.  But I don't have this issue prior to version 6 when I npm link.

@kmcrawford : correct - we only started using a singleton React.createContext() instance in v6.

@markerikson thanks, but that doesn't explain why the same code works as a private npm package and throws the error when running locally using npm link.
Below is how the code has looked for nearly a year:  context in this case is just an empty object {} any thoughts to how I should be using React.createContext()?
<Provider store={store}>
        <StaticRouter location={req.url} context={context}>
          <div>{renderRoutes(Routes(contextPath))}</div>
        </StaticRouter>
      </Provider>

The issue would likely be because different copies of React-Redux are ending up in your application.  Since our internal ReactReduxContext instance is a singleton, if two different parts of the app are using different copies of React-Redux, they're not using the same ReactReduxContext instance, and so the connected components can't talk to <Provider>

@markerikson I think it's starting to make sense.  So if my main app has react-redux in it's node_modules and when I npm link I'm using the react-redux in the linked package (which has the <Provider> in it) node_modules, could that cause this issue?

Yep, definitely would!

@markerikson Thanks!  I will keep this thread posted if I get around this.

Similar issue, but doesn't fix me.  https://github.com/facebook/create-react-app/issues/6027

We hit the same error when upgrading from react-redux 5.1.1 to 6.0.1, and it was also due to a stray
import connect from "react-redux/lib/connect/connect"

statement.

With version 5.0.7 i could test my connected components like this:
// Libraries
import 'jest';
import { createStore, applyMiddleware, combineReducers } from 'redux';
import thunk from 'redux-thunk';
import { shallow, ReactWrapper } from 'enzyme';
import * as React from 'react';

// Reducers
import cartReducer from '../../../../Reducers/Cart/CartReducer';
import user from '../../../../Reducers/User/UserReducer';

// Modules
import Cart from '../../../../Modules/Cart/CartScene';

// setUp store
const myReducers = combineReducers({
  user: userReducer,
  cart: cartReducer
});

const store: any = createStore(
  myReducers,
  applyMiddleware(thunk)
);
let component: any;

const updateShallowComp = () => {
  component = shallow(
    <CartScene navigation={navigation} />,
    { context: { store } },
  );
  return component;
};

But with version 7.0.3 this throws me the same error of https://github.com/reduxjs/react-redux/issues/1117#issue-389662847
I do not user Provider because it's harder to access instance methods and states. How can I test my connected comps now without using a Provider

@nikoremi97 : we no longer use the old context API.  Either pass the store directly as a prop to the connected component, or use a <Provider>.

@markerikson Thanks! I will keep this thread posted if I get around this.

Did you manage to find a solution. I have the same problem on a project

Wanted to throw in my experience in case anybody else is seeing something similar.
I have a monorepo set up (using Yarn workspaces). I had already made sure that only one react-redux existed in my node_modules, but because I had set up Webpack with resolve.symlinks = false, I ended up having a Webpack build that copied in multiple react-reduxs, one for each of my "workspaces".
If you're seeing this issue with Webpack, open up a non-minified build and grep around for react-redux. You probably have multiple instances in there.

Hey @markerikson !
I'm publishing reusable modules with Redux logic attached to each of them, something similar to what @UserBug did.
Reading your comment, I understand that the Redux store have now becomes a singleton, so different package will result in different store.
In your opinion, what is the best practice to enable sharing the same store across these modules? Can we can an official documentation on this? I believe reusable modules are quite a common thing.

@jacklimwenjie 	: I'm not quite sure what you're saying there.
The described issue doesn't have anything to do with the Redux core or Redux stores.  It's specifically about React-Redux using a React context instance.  You need to make sure there is only a single copy of React and React-Redux loaded into your app, otherwise there may technically be multiple versions of the context that are created.
Note that this is not a problem that is specific to React-Redux, this would apply for any library that creates a singleton React context instance for internal use.

I had the same problem as @Ashoat described. I fixed it with an alias in Webpack:
    resolve: {
      symlinks: false,
      alias: {
        react: path.resolve('./node_modules/react'),
        'react-redux': path.resolve('./node_modules/react-redux'),
      },
    },


roleEligibilityScheduleRequests - Missing Scopes [add alternative required scope]

I have read through #195 and can see that the permission 'RoleEligibilitySchedule.ReadWrite.Directory' is required. However, looking through Microsoft's documentation (Link) I can see that 'RoleManagement.ReadWrite.Directory' is a higher privileged permission that's also allowed.
Shouldn't Maester take this into account as well? I happen to have an application with this privilege already, so I would like to avoid adding more if possible.
If this permission is also checked in Maester as an alternative required scope, I won't have to do any changes 🙏 🙏
If I'm not mistaken, this could be fixed by replacing all instances of:
$permissionMissing = "RoleEligibilitySchedule.ReadWrite.Directory" -notin $scopes
With
$permissionMissing = "RoleEligibilitySchedule.ReadWrite.Directory" -notin $scopes -and "RoleManagement.ReadWrite.Directory" -notin $scopes

Added a pullrequest to implement this: #538

With the merge of your PR I am closing this. Thanks for the contribution @magnusjak!


Add failing memory test tokio util

Motivation

Solution

Not sure why this is still open even, I should delete this entire repository


Documentation:Expanded the docker compose instructions and details

Expanded the docker compose instructions and details
Changes proposed
The steps and options to use the project locally were expanded for clarity
We added git as a requirement.
We included docker desktop as an option because it's installable on all OS's.
We expanded the the details of the steps to make them more clear.
We included an optional drop down option which covers the steps needed to run the next.js app
locally and a mongoDB instance in docker  when Mongo Compass is needed as it won't work
with Docker compose.
Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Suggestion:-
-  Click me for instructions
+   Click here for instructions

Sorry for the confusion, it is my fault, I mentioned to Ken on Discord that there was no need to raise an issue for these changes - I broke the rules 🤦♂ I created an issue for it (@kbventures please can you comment on the issue and I can assign it to you) https://github.com/EddieHubCommunity/LinkFree/issues/8612

Sorry for the confusion, it is my fault, I mentioned to Ken on Discord that there was no need to raise an issue for these changes.

It's okay, Eddie. I've gone through the conversation in Discord for the context to the changes! 🙂


SIW <IP_ADDRESS>00322

SIW - System Information for Windows
Microsoft Reviewers: Open in CodeFlow

 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.:x: gtopala sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Include session name in Trading Simulation and Live Trading panels name

There is no way to tell to which session each trading panel corresponds to:

Fiexed


CRI: Add app params to "rkt app add"

Adding the following flags in rkt app add: --memory, --cpu, --caps-retain, --caps-remove, --seccomp. Instead of adding the flags manually, the code for rkt app add and rkt run is factorised. Thanks to @krnowak for the patches. See also https://github.com/coreos/rkt/pull/3205#issuecomment-247551585
--memory and --cpu successfully update the manifest with the isolator. However, they are not enforced yet. I will need further work in another PR. The reason for that is that the cgroup filesystem for the memory & cpu controller are generally mounted read-only and rkt mount some files specific to the application in read-write mode. But at the time the pod is created (rkt app sandbox), the list of  applications is not known yet, so the mounts in read-write mode for the specific application is not done.
The refactoring commit is independent from CRI and might need to be applied to master first in order to avoid too much divergence between the "master" and "cri" branches. I would like to do that before merging this PR.
/cc @yifan-gu @s-urbaniak

@alban ok, let's prepare against master first then, and then merge the refactorings here in the CRI branch.

Blocking on https://github.com/coreos/rkt/pull/3209

Updated.
I tested the following options:
$ sudo rkt list
UUID		APP	IMAGE NAME	STATE	CREATED		STARTED		NETWORKS
f97588c0	-	-		running	2 seconds ago	2 seconds ago	default:ip4=<IP_ADDRESS>
$ sudo rkt app add f97588c0 quay.io/coreos/alpine-sh:latest --memory=444M --user=1000 --group=1000 --exec=/bin/sh -- -c 'echo id=;id'
image: using image from local store for image name quay.io/coreos/alpine-sh:latest
$ sudo rkt app start f97588c0 --app=alpine-sh

It displays the following:
[13197.107054] alpine-sh[21]: id=
[13197.123986] alpine-sh[21]: uid=1000 gid=1000 groups=1000

I added a new commit for adding mount/umount in all flavors

It seems overall fine but I won't have time to review it properly in a timely manner. @yifan-gu @s-urbaniak can you have a second pass on this?


Handle trailing/leading method calls and syntax

From https://github.com/zombocom/dead_end/issues/64 the algorithm doesn't work well unless a chunk of code fits logically into the concept of a "line". This assumption fails when we have trailing slashes (mitigated in https://github.com/zombocom/dead_end/pull/28) as well as leading/trailing method calls.
User
  .where(name: "schneems")

The other known leading/trailing syntax is boolean operators:
irb(main):017:0* 1 == 1 &&
irb(main):018:0* 2 == 2 ||
irb(main):019:0> 3 == 3
=> true

We can use a lexer to detect leading/trailing method calls. However it becomes very hard to do without full context.
If you are using the full code it tells us that we have on_ignored_nl elements:
irb(main):005:1" Ripper.lex(<<~EOM
irb(main):006:1"   User
irb(main):007:1"   .where
irb(main):008:1"   .first
irb(main):009:1*   EOM
irb(main):010:0>   )
=>
[[[1, 0], :on_const, "User", CMDARG],
 [[1, 4], :on_ignored_nl, "\n", CMDARG],
 [[2, 0], :on_period, ".", DOT],
 [[2, 1], :on_ident, "where", ARG],
 [[2, 6], :on_ignored_nl, "\n", ARG],
 [[3, 0], :on_period, ".", DOT],
 [[3, 1], :on_ident, "first", ARG],
 [[3, 6], :on_nl, "\n", BEG]]
irb(main):011:1" Ripper.lex(<<~EOM
irb(main):012:1"   User.
irb(main):013:1"   where.
irb(main):014:1"   first
irb(main):015:1*   EOM
irb(main):016:0>   )
=>
[[[1, 0], :on_const, "User", CMDARG],
 [[1, 4], :on_period, ".", DOT],
 [[1, 5], :on_ignored_nl, "\n", DOT],
 [[2, 0], :on_ident, "where", ARG],
 [[2, 5], :on_period, ".", DOT],
 [[2, 6], :on_ignored_nl, "\n", DOT],
 [[3, 0], :on_ident, "first", ARG],
 [[3, 5], :on_nl, "\n", BEG]]

However, if we're lexing without full context, we need to piece that info together after the fact:
Ripper.lex(".first")
=> [[[1, 0], :on_period, ".", DOT], [[1, 1], :on_ident, "first", ARG]]

We also have to consider other elements such as spaces and comments.
irb(main):022:0> Ripper.lex(" where. # trailing method call with a comment")
=>
[[[1, 0], :on_sp, " ", BEG],
 [[1, 1], :on_ident, "where", CMDARG],
 [[1, 6], :on_period, ".", DOT],
 [[1, 7], :on_sp, " ", DOT],
 [[1, 8], :on_comment, "# trailing method call with a comment", DOT]]

It may be possible to piece-meal this together one line at a time, but I'm thinking we can maybe benefit from some technique that lexes the whole document and "stuffs" data back into codelines rather than needing codelines to lex themselves out of context. This could (possibly) also help with the "heredoc problem" which was partially mitigated in https://github.com/zombocom/dead_end/pull/19 but continues to be a thorn in my side.
Worth noting that trailing && also generates ignored newline lex:
irb(main):024:0> Ripper.lex("foo &&\n bar")
=>
[[[1, 0], :on_ident, "foo", CMDARG],
 [[1, 3], :on_sp, " ", CMDARG],
 [[1, 4], :on_op, "&&", BEG],
 [[1, 6], :on_ignored_nl, "\n", BEG],
 [[2, 0], :on_sp, " ", BEG],
 [[2, 1], :on_ident, "bar", ARG]]

The downside of changing code to "stuff" lexing data into code lines is that the CodeLine class was one of the first ones to be written and its fairly coupled to a  large number of other test cases so it might be a large refactoring needed just to see if the concept can work. All the lex extraction logic would need to be re-written. Also there's the unknown of what problems might be intractable with this "injection/stuffing" approach. Ultimately I think it's the right thing to move towards rather than trying to manually replicate the lexer logic of detecting edge-cases like on_ignored_nl


AWS: Couldn't download resources from specific region.

I am able to import S3 bucket configurations from all other regions except us-east-1 region. Do you think it's related to permission?
us-west-2 region:
❯ terraformer import aws -r s3 --profile=*** --regions=us-west-2 --filter="Name=id;Value=xyz"
2021/05/14 08:04:15 aws importing region us-west-2
2021/05/14 08:04:19 aws importing... s3
2021/05/14 08:04:35 aws done importing s3
2021/05/14 08:04:35 Number of resources for service s3: 1
2021/05/14 08:04:35 Refreshing state... aws_s3_bucket.tfer--xyz
2021/05/14 08:04:39 Filtered number of resources for service s3: 1
2021/05/14 08:04:39 aws Connecting....
2021/05/14 08:04:39 aws save s3
2021/05/14 08:04:39 aws save tfstate for s3
us-east-1 region:
❯ terraformer import aws -r s3 --profile=*** --regions=us-east-1 --filter="Name=id;Value=objstoretest.s3.amazonaws.com"
2021/05/14 08:06:17 aws importing region us-east-1
2021/05/14 08:06:19 aws importing... s3
2021/05/14 08:06:41 aws done importing s3
2021/05/14 08:06:41 Number of resources for service s3: 0
2021/05/14 08:06:41 aws Connecting....
2021/05/14 08:06:41 aws save s3
2021/05/14 08:06:41 aws save tfstate for s3

when using s3 us-east-1 is the default region,
Try to run it without --regions

If I don't provide the regions then I am getting this warning messages and s3_bucket.tf doesn't have any resources listed:
❯ terraformer import aws -r s3 --profile=hwx --filter="Name=id;Value=objstoretest.s3.amazonaws.com"
2021/05/14 13:22:52 aws importing default region
2021/05/14 13:22:53 aws importing... s3
2021/05/14 13:23:14 aws done importing s3
2021/05/14 13:23:14 Number of resources for service s3: 1
2021/05/14 13:23:14 Refreshing state... aws_s3_bucket.tfer--objstoretest-002E-s3-002E-amazonaws-002E-com
2021/05/14 13:23:14 WARN: Fail read resource from provider, wait 300ms before retry
2021/05/14 13:23:15 WARN: Fail read resource from provider, wait 300ms before retry
2021/05/14 13:23:15 WARN: Fail read resource from provider, wait 300ms before retry
2021/05/14 13:23:16 WARN: Fail read resource from provider, wait 300ms before retry
2021/05/14 13:23:16 WARN: Fail read resource from provider, wait 300ms before retry
2021/05/14 13:23:17 Fail read resource from provider, trying import command
2021/05/14 13:23:17 Filtered number of resources for service s3: 1
2021/05/14 13:23:17 aws Connecting....
2021/05/14 13:23:17 aws save s3
2021/05/14 13:23:17 aws save tfstate for s3
❯ cat s3_bucket.tf
resource "aws_s3_bucket" "tfer--objstoretest-002E-s3-002E-amazonaws-002E-com" {}

i notice when using env var with  AWS_SESSION_TOKEN AWS_SECRET_ACCESS_KEY AWS_ACCESS_KEY_ID
for some reason, it first tries to use the AWS profile and then the env var
and of course, it failing
did you check that you don't have any AWS env var exported?

@sergeyr87 Thanks. It's working now. I changed my region in .aws/config to us-east-1 and removed --regions parameters.

We have experienced the same issue. The primary issue is that based off the terraformer response everything looks fine, except that we know we are missing resources (it fails successfully :)). However it is actually worse that, it makes us wonder, what else is missing that we don't know of.
Terraformer should respect the --regions parameter if it has been provided, and if there is some implicit conflict in configuration/auth then it should at least fail or report on it.


TableSet.from_csv should not require headers for type inference

Should work like Table.from_csv

Fixed in 54d6ebf


Circular reference problem when using decorators in circular referenced classes

I'm tired. I hate circular reference problems.
We have migrated a huge codebase to Typescript a few month ago, and now there is a problem that totally blocks us. I think this is a huge problem that prevent people to write a large scale apps.
TypeScript Version: @next
Code:
I can't describe a problem clearly, its really better to see it. I created a basic project a with same models I have. They all are plain classes + one file that bootstrap the app + one empty decorator that brings a problem. I can't post a code here, to clearly show a problem you need to checkout repo and run the app. It is a real-world app.

git pull git@github.com:pleerock/typescript-circual-reference-problem.git
npm i
npm start

Actual behavior:
Application is not running because of circular reference problem. It throws an error.
Expected behavior:
It should run without errors.

How to fix this error:

open ./src/modules/general/concept/entity/Concept.ts
on line 68 change attachedPhoto: AttachedPhoto to attachedPhoto: any
run app again and you'll not see error anymore

If you remove a decorator - everything will work. I think the problem in emitted code:
const AttachedPhoto_1 = require("../../../widget/attached-photo/entity/AttachedPhoto");

/// .......................................

__decorate([
    Decorated_1.Decorated(),
    __metadata('design:type', AttachedPhoto_1.AttachedPhoto)
], Concept.prototype, "attachedPhoto", void 0);

And I even have no idea how to at least monkey patch it

Not that this is related to your problem, as changing it didn't resolve anything, but why is Decorated a decorator factory and not a decorator? Also, why are you using the same decorator, that has no behavior on class properties and on classes? Why apply the same decorator to multiple times to the same property (one of them had three Decorated annotations). Also, it looks like a lot of this code was generated by a template which has some odd notions.

Also, it looks like a lot of this code was generated by a template which has some odd notions.

no, this code is from a real project

Why apply the same decorator to multiple times to the same property

Its because I have bulk changed all its different decorators to a single decorator, to simplify an example. But decorator can be applied multiple times without problems, right

Also, why are you using the same decorator, that has no behavior on class properties and on classes

Again, because its the simplest example of reproduction of the problem. I simply removed all behaviour because its unrelated to the problem

why is Decorated a decorator factory and not a decorator?

I need decorator factory. Here are a real decorators I used

Not that this is related to your problem,

I don't think so, because I have a very simple project but with many relations and it simply should work without an issue. There is no my logic that breaks everything. Only references between objects.

as changing it didn't resolve anything

what do you mean? If you change it the way I described and recompile the project - it should resolve the issue

what do you mean? If you change it the way I described and recompile the project - it should resolve the issue

I mean that I changed the decorator factory to a decorator and removed multiple applications of the decorator and that did not help. I was just trying to understand the issue.
Upon further reflection, I think it has to do with how node handles circular references https://nodejs.org/api/modules.html#modules_cycles

Upon further reflection, I think it has to do with how node handles circular references https://nodejs.org/api/modules.html#modules_cycles

Yes its most probably related to this issue, but I also think if in my situation everything is working as expected, then maybe typescript can emit/handle differently such situations

I mean that I changed the decorator factory to a decorator and removed multiple applications of the decorator and that did not help. I was just trying to understand the issue.

Did you try to do what I described without changing everything else?:

open ./src/modules/general/concept/entity/Concept.ts
on line 68 change attachedPhoto: AttachedPhoto to attachedPhoto: any
run app again and you'll not see error anymore

Yes I did, and it fails just as you describe under TypeScript 2.1.0-dev.20160723, Node 6.2.2. I do believe the issue is in the runtime. I'm not sure how TypeScript could resolve runtime issues like this without introducing other problems and making overly broad assumptions about current and future runtimes. It is also not a design goal of TypeScript to provide runtime support of any kind. Proper circular references are supported by module loaders such as SystemJS, so it may be worth investigating alternatives.
You may find this interesting https://github.com/ModuleLoader/es6-module-loader/blob/v0.17.0/docs/circular-references-bindings.md

We can't really look at repros with dozens of files. Please pare this down to a minimal example and we can figure out whether there's something we can do on our side vs in the codebase itself.

@RyanCavanaugh its minimal example. There is NO logic in the codebase. Only dummy classes with dummy properties and decorated with dummy decorator set. That's it. It was a hard work for me to left only models and remove everything else. I tried to reproduce in small codebase (with only few models), but I could not reproduce it the same way. I tried to make installation process as minimal as possible.

Forgive the directness, but I'm extremely skeptical that whatever you're seeing can't be reproduced in three or four files. You're saying if you remove even one file from this repo, you know longer see the problem?

after few days of experiments I have resolved my issue by manually settings the order in which files are being imported (now importing all abstract classes at last). But I still feel very uncomfortable with this issue. I'll reopen this if this issue again reproduce. Btw here somebody describe very similar problem


No return on query lspci -nn | grep 089a - google coral M.2 pcie, Ubuntu 22.4

I've been looking at this for a while now and I can see various issues during installation - I can't see what the issue is for me.
I have success through the previous steps of the installation as per the instructions on https://coral.ai/docs/m2/get-started#2-install-the-pcie-driver-and-edge-tpu-runtime
However, at the stage where it instructs:
Now reboot the system.
Once rebooted, verify that the accelerator module is detected:
lspci -nn | grep 089a
No value is returned.  I've repeated the steps but still nothing.
The output of "lspci -vvv" is as follows.  Any help appreciated, thanks.
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
Subsystem: Hewlett-Packard Company 8th Gen Core Processor Host Bridge/DRAM Registers
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: Hewlett-Packard Company CometLake-S GT2 [UHD Graphics 630]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 125
Region 0: Memory at b0000000 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at a0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 3000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 0000
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 00008000, Page Request Allocation: 00000000
Kernel driver in use: i915
Kernel modules: i915
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH Thermal Controller
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000  Data: 0000
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company Cannon Lake PCH USB 3.1 xHCI Host Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 123
Region 0: Memory at b1020000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Address: 00000000fee00258  Data: 0000
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH Shared SRAM
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Region 0: Memory at b1032000 (64-bit, non-prefetchable) [disabled] [size=8K]
Region 2: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH HECI Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 126
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00298  Data: 0000
Capabilities: [a4] Vendor Specific Information: Len=14 <?>
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation Cannon Lake PCH Active Management Technology - SOL (rev 10) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company Cannon Lake PCH Active Management Technology - SOL
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin D routed to IRQ 19
Region 0: I/O ports at 3088 [size=8]
Region 1: Memory at b1037000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:<PHONE_NUMBER>000000  Data: 0000
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: serial
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company Cannon Lake PCH SATA AHCI Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 122
Region 0: Memory at b1030000 (32-bit, non-prefetchable) [size=8K]
Region 1: Memory at b1036000 (32-bit, non-prefetchable) [size=256]
Region 2: I/O ports at 3080 [size=8]
Region 3: I/O ports at 3090 [size=4]
Region 4: I/O ports at 3060 [size=32]
Region 5: Memory at b1035000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 0000
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.0 ISA bridge: Intel Corporation Q370 Chipset LPC/eSPI Controller (rev 10)
Subsystem: Hewlett-Packard Company Q370 Chipset LPC/eSPI Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 127
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=16K]
Region 4: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [80] Vendor Specific Information: Len=14 <?>
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee002b8  Data: 0000
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_cnl
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SMBus Controller
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SPI Controller
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Region 0: Memory at fe010000 (32-bit, non-prefetchable) [size=4K]
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
DeviceName: Onboard Lan
Subsystem: Hewlett-Packard Company Ethernet Connection (7) I219-LM
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx+
Latency: 0
Interrupt: pin A routed to IRQ 124
Region 0: Memory at b1000000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00278  Data: 0000
Kernel driver in use: e1000e
Kernel modules: e1000e

what do you see when you do "ls /dev/apex_0" ?
I followed that page and it all worked, but then I tried to do the Python stuff and got confused and it didn't work (Linux Mint 21.3 Mate).
Another thread somewhere (lost it now) showed me that if $ ls/dev/apex0 works (you just get it repeated back to you) then all of the drivers are installed and it's ready to go.  That's what I found.
My LSPCI returns thus:
$ lspci -v |grep Edge
24:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (prog-if ff)
	Subsystem: Global Unichip Corp. Coral Edge TPU

and it works with frigate (as does the USB dongle I finally got hold of).
There are a number of complications regarding any adaptor board which takes the M.2 and fits it into a PCIe slot which you need to be aware of; perhaps that is a hurdle?  If the wrong lanes are presented in the wrong way, the device won't show up.

Yeah, I've been having trouble with that, too - when I check it get:
"ls: cannot access '/dev/apex_0': No such file or directory"
I spent several hours going through github pages of recommendations around uninstalling/reinstalling "gasket-driver" and all sorts, to no avail unfortunately.
I wonder if it's a problem with the board.  However, when I input "lspci -nn | grep 089a" I get the output:
"01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]"
So it would appear to see something.

what do you see when you do "ls /dev/apex_0" ?
I followed that page and it all worked, but then I tried to do the Python stuff and got confused and it didn't work (Linux Mint 21.3 Mate).
Another thread somewhere (lost it now) showed me that if $ ls/dev/apex0 works (you just get it repeated back to you) then all of the drivers are installed and it's ready to go. That's what I found.
My LSPCI returns thus:
$ lspci -v |grep Edge
24:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (prog-if ff)
	Subsystem: Global Unichip Corp. Coral Edge TPU

and it works with frigate (as does the USB dongle I finally got hold of).
There are a number of complications regarding any adaptor board which takes the M.2 and fits it into a PCIe slot which you need to be aware of; perhaps that is a hurdle? If the wrong lanes are presented in the wrong way, the device won't show up.

Yeah, I've been having trouble with that, too - when I check it get:
"ls: cannot access '/dev/apex_0': No such file or directory"
I spent several hours going through github pages of recommendations around uninstalling/reinstalling "gasket-driver" and all sorts, to no avail unfortunately.
I wonder if it's a problem with the board.  However, when I input "lspci -nn | grep 089a" I get the output:
"01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]"
So it would appear to see something.

That's frustrating.  unfortunately, my linux expertise is pretty shallow so I am unlikely to be of much use (the Frigate forum seems likely to be your best bet which is where I saw your post).
If you think it would help, I can find out the exact Coral M.2 module I bought for about 30 quid a year or so ago - from Farnell, I think it was the single rather than the dual - and the eBay source for the adaptor card I am using is.
https://www.ebay.co.uk/itm/394440262106
A  link  which talks about adaptor cards but it could be a red herring as you pointed out:
https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter
On mine:
lspci -nn | grep 089a
24:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

other ideas - shutdown, remove and see if there are another responses to commands which mean they were read herrings (because this time they cannot be related to the Coral).

Your computer does not see the hardware. Potential reasons:Defective coralCoral incompatible with the slot you have it inSlot you have it in is disabled and / or BIOS settings preclude you from using the coral in itSlot you have it in is defectiveEither way, until you see it in lspci there’s nothing else you can do in software. Sent from my iPhoneOn Aug 11, 2024, at 7:08 AM, gtramsey2000 @.***> wrote:
I've been looking at this for a while now and I can see various issues during installation - I can't see what the issue is for me.
I have success through the previous steps of the installation as per the instructions on https://coral.ai/docs/m2/get-started#2-install-the-pcie-driver-and-edge-tpu-runtime
However, at the stage where it instructs:
Now reboot the system.
Once rebooted, verify that the accelerator module is detected:
lspci -nn | grep 089a
No value is returned.  I've repeated the steps but still nothing.
The output of "lspci -vvv" is as follows.  Any help appreciated, thanks.
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
Subsystem: Hewlett-Packard Company 8th Gen Core Processor Host Bridge/DRAM Registers
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information: Len=10
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: Hewlett-Packard Company CometLake-S GT2 [UHD Graphics 630]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 0000
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 00008000, Page Request Allocation: 00000000
Kernel driver in use: i915
Kernel modules: i915
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH Thermal Controller
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000  Data: 0000
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company Cannon Lake PCH USB 3.1 xHCI Host Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 123
Region 0: Memory at b1020000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Address: 00000000fee00258  Data: 0000
Capabilities: [90] Vendor Specific Information: Len=14
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH Shared SRAM
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort-
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation Cannon Lake PCH Active Management Technology - SOL (rev 10) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company Cannon Lake PCH Active Management Technology - SOL
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin D routed to IRQ 19
Region 0: I/O ports at 3088 [size=8]
Region 1: Memory at b1037000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:<PHONE_NUMBER>000000  Data: 0000
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: serial
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company Cannon Lake PCH SATA AHCI Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 122
Region 0: Memory at b1030000 (32-bit, non-prefetchable) [size=8K]
Region 1: Memory at b1036000 (32-bit, non-prefetchable) [size=256]
Region 2: I/O ports at 3080 [size=8]
Region 3: I/O ports at 3090 [size=4]
Region 4: I/O ports at 3060 [size=32]
Region 5: Memory at b1035000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 0000
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.0 ISA bridge: Intel Corporation Q370 Chipset LPC/eSPI Controller (rev 10)
Subsystem: Hewlett-Packard Company Q370 Chipset LPC/eSPI Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 127
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=16K]
Region 4: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [80] Vendor Specific Information: Len=14 <?>
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee002b8  Data: 0000
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_cnl
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SMBus Controller
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at<PHONE_NUMBER> (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
Subsystem: Hewlett-Packard Company Cannon Lake PCH SPI Controller
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Region 0: Memory at fe010000 (32-bit, non-prefetchable) [size=4K]
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
DeviceName: Onboard Lan
Subsystem: Hewlett-Packard Company Ethernet Connection (7) I219-LM
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx+
Latency: 0
Interrupt: pin A routed to IRQ 124
Region 0: Memory at b1000000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00278  Data: 0000
Kernel driver in use: e1000e
Kernel modules: e1000e
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


how to get all method form route

i want has all method form route. how to ?
I need to have resources for all modules acl is route and method
function routerApp(req, res, next) {
    app._router.stack.forEach(function(r){
        if (r.route && r.route.path){
            console.log(r.route.path) // + r.route.method not working
        }
    })
    next();
}

app.use(routerApp);

please help me !

Unfortunately it is not possible to do.


SyntaxError: Unexpected token '.'

yarn run v1.22.10
$ tsc
Hook Module named "copy-files" threw an error, more information bellow:
/home/project/node_modules/tsc-hooks/hooks/copy-files.js:8
    const include = tsconfig.include?.map(file => path.resolve(tsconfigDir, file));
                                     ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:931:16)

This looks like node might be having trouble with the new ES11 syntax for optional chaining.
If you use Node version 14 or greater, should fix your problem, but if other things are prohibiting you from using a more modern node version, I could be compelled to make support for earlier versions.

Closing for now, will consider integrating with Babel in a version >=v1.1.0


FIX-#4071: Fix DataFrame and Series equals() for None values.

Signed-off-by: mvashishtha<EMAIL_ADDRESS>
What do these changes do?
Currently, we implement DataFrame.equals() by calling DataFrame.eq() on both
input frames, then checking that every element of the result is True. However, pandas does not define equals equivalently. pandas.eq does not consider None to be equal to None, while pandas.equals does:
import pandas
assert pandas.DataFrame([[None]]).equals(pandas.DataFrame([[None]]))
assert not pandas.DataFrame([[None]]).eq(pandas.DataFrame([[None]])).any().any()

It's hard to tell what exactly equals means for pandas, so I reimplemented it as a binary operation that transforms a pair of dataframes to dataframes with a single element telling whether the two dataframes are equals, followed by a check that every element of the result is true.

[x] commit message follows format outlined here
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #4071
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date
[x] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

What about adding a none_equals parameter to the query_compiler's eq method and handling the None values conditionally in that way?
Right now, this PR is passing metadata state from the API layer all the way to the internal dataframe representation.

@devin-petersohn How could I do handle the none_equals=True case? the pandas equals appears to check that all pairs of blocks [1] are array_equivalent [2], where array_equivalent checks [3] that the arrays have None in the same places. How could we port that logic to Modin?

@devin-petersohn please let me know what you think about this question. If we want to continue with the approach in this PR, maybe we could pass a new bool param should_compute_axis_labels to binary_op that tells whether to recompute axis labels because the binary op could change them? That way we at least won't be passing the new metadata down from the API layer.

It's hard to tell what exactly equals means for pandas

Roughly: ((x == y) | (isna(x) & isna(y))).all().   Similar to np.array_equal(x, y, equal_nan=True).  For object-dtype we also check for matching-NAs, see, pd._libs.lib.array_equivalent_object


Set value badge total

I need to set the amount that I want in the badge with the total of events of a certain day. I researched a lot and did not find a way to do that. Could you help me with this problem?
I thought of something like this:
$scope.events = [
{
title: 'Available'
startsAt: new Date(),
endsAt: new Date(),
badgeTotal: 30
}
]

You can use the cell modifier to do this: http://plnkr.co/edit/W8LbMJo1TscV1sETbaP2?p=preview

Thank you so much.


bind-address option are not suffisant to make k3s listen on specifique ip address

Environmental Info:
K3s Version:
lastest : v1.28.8+k3s1 (653dd61a)
Node(s) CPU architecture, OS, and Version:
ubuntu 22.04 with 4 cores and 32go.
Cluster Configuration:
single server, with one private ip and many public ip.
Describe the bug:
i try to configure k3s to listening on specifique ip.
when i configure my cluster to listen on specifique ip ("privateip") with --bind-address options they refuse to start, with error :
Apr 07 00:55:10 myhost k3s[1149269]: time="2024-04-07T00:55:10+02:00" level=info msg="Connecting to proxy" url="wss://"publicip":6443/v1-k3s/connect"
Apr 07 00:55:10 myhost k3s[1149269]: time="2024-04-07T00:55:10+02:00" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp "publicip":6443: connect: connection refused"
Apr 07 00:55:10 myhost k3s[1149269]: time="2024-04-07T00:55:10+02:00" level=error msg="Remotedialer proxy error" error="dial tcp "publicip":6443: connect: connection refused"

Steps To Reproduce:
export NODE_IP=<IP_ADDRESS>
export HOSTNAME=myhost

export INSTALL_K3S_EXEC="server \
    --bind-address=${NODE_IP} \
    --node-ip=${NODE_IP} \
    --node-external-ip="mypublicip" \
    --server=${NODE_IP} \
    --tls-san=${NODE_IP} \
    --kubelet-arg=address=${NODE_IP} "

export K3S_URL=https://${NODE_IP}:6443
curl -sfL https://get.k3s.io | sh -s - --docker

Expected behavior:
k3s listening on private ip, up and running without error.
Actual behavior:
k3s not start completely.

I think you should use AdvertiseIP instead of bind-address. If you don't mind me asking: why are you using --node-external-ip but then require your kube-api to listen in a private address?

If you don't mind me asking: why are you using --node-external-ip but then require your kube-api to listen in a private address?

i want to expose my kube-api only on private (to avoid security problem if public exposed), and application exposition (ingress and co) to public ip.

when i use advertise ip in place of bind-address :
# netstat -lnput | grep k3s
tcp        0      0 <IP_ADDRESS>:10248         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10249         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10258         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10259         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10256         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10257         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10250       <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:6444          <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp6       0      0 :::6443                 :::*                    LISTEN      2625498/k3s server
tcp6       0      0 :::41373                :::*                    LISTEN      2625498/k3s server

i have tcp6 listen on any interface...

i found the sollution for ::6443 in documentation of k3s dual stack ipv4 ipv6 networking :
--kubelet-arg="node-ip=${NODE_IP}"

but i think that is not normal that  --node-ip of k3s server not set correctly the value in the kubelet config...
the last think that last problem are :
tcp6       0      0 :::41373                :::*                    LISTEN      2625498/k3s server

it's dynamique port and is listening on ipv6....

there a solution to see who listen in k3s server, witch part of k3s is listening on any interface ?

when i use advertise ip in place of bind-address :
# netstat -lnput | grep k3s
tcp        0      0 <IP_ADDRESS>:10248         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10249         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10258         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10259         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10256         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10257         <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:10250       <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp        0      0 <IP_ADDRESS>:6444          <IP_ADDRESS>:*               LISTEN      2625498/k3s server
tcp6       0      0 :::6443                 :::*                    LISTEN      2625498/k3s server
tcp6       0      0 :::41373                :::*                    LISTEN      2625498/k3s server

i have tcp6 listen on any interface...

This output is weird, 6443 should be available in all interfaces for ipv4 or ipv6. I recommend you to use ss instead of netstat. Netstat is supposed to be deprecated (like ifconfig, route, etc)

This output is weird, 6443 should be available in all interfaces for ipv4 or ipv6. I recommend you to use ss instead of netstat. Netstat is supposed to be deprecated (like ifconfig, route, etc)

After use node ip option is now listening only on ipv4 I setted but we have dynamique port continuing listening...
Sorry I use netstat by habitude....

but when try to access to my container with exec command i receive this error:
# kubectl run -i -t --image=alpine debug
If you don't see a command prompt, try pressing enter.
warning: couldn't attach to pod/debug, falling back to streaming logs: error dialing backend: proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:10250, code 502: 502 Bad Gateway
Error from server: Get "https://<IP_ADDRESS>:10250/containerLogs/ch2o/debug/debug": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:10250, code 502: 502 Bad Gateway


GPU container for onnxv7 semi-auto annotation fails deploying

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Steps to Reproduce (for bugs)

When following: https://opencv.github.io/cvat/docs/administration/advanced/installation_automatic_annotation/
run the following script or the deploy_gpu.yaml or the following modified one

#!/bin/bash
# Sample commands to deploy nuclio functions on GPU

SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
FUNCTIONS_DIR=${1:-$SCRIPT_DIR}

nuctl create project cvat

shopt -s globstar

func_config="$FUNCTIONS_DIR/onnx/WongKinYiu/yolov7/nuclio/function-gpu.yaml"

echo "$func_config"
func_root=$(dirname "$func_config")
echo "Deploying $(dirname "$func_root") function..."
nuctl deploy --project-name cvat --path "$func_root" \
    --volume "$SCRIPT_DIR/common:/opt/nuclio/common" \
    --file "$func_config" --platform local

nuctl get function

Expected Behaviour
gpu container deploy using end with success
Current Behaviour
onnx-yolov7 fail to deploy.
  nuctl get function

  NAMESPACE |                      NAME                      | PROJECT |  STATE   | REPLICAS | NODE PORT
  nuclio    | onnx-yolov7                                    | cvat    | error    | 1/1      |

#10 [ 6/13] RUN wget https://github.com/WongKinYiu/yolov7/releases/download/v0.1/yolov7-nms-640.onnx
#0 0.080 /bin/sh: 1: wget: not found
#10 ERROR: process "/bin/sh -c wget https://github.com/WongKinYiu/yolov7/releases/download/v0.1/yolov7-nms-640.onnx" did not complete successfully: exit code: 127
------
 > [ 6/13] RUN wget https://github.com/WongKinYiu/yolov7/releases/download/v0.1/yolov7-nms-640.onnx:
#0 0.080 /bin/sh: 1: wget: not found
------
Dockerfile.processor:28
--------------------
  26 |     WORKDIR /opt/nuclio
  27 |
  28 | >>> RUN wget https://github.com/WongKinYiu/yolov7/releases/download/v0.1/yolov7-nms-640.onnx
  29 |
  30 |     RUN ln -s /usr/bin/python3 /usr/bin/python
--------------------`
ERROR: failed to solve: process "/bin/sh -c wget https://github.com/WongKinYiu/yolov7/releases/download/v0.1/yolov7-nms-640.onnx" did not complete successfully: exit code: 127

    /nuclio/pkg/cmdrunner/shellrunner.go:96
Failed to build
    /nuclio/pkg/dockerclient/shell.go:117
Failed to build docker image
    .../pkg/containerimagebuilderpusher/docker.go:54
Failed to build processor image
    /nuclio/pkg/processor/build/builder.go:263
Failed to deploy function
    ...//nuclio/pkg/platform/abstract/platform.go:197

Possible Solution
install wget on the base image in the build directives of function-gpu.yaml
Context
Running the semi automation for creating dataset for my master thesis
Your Environment

Git hash commit: 8956a368ccfb445418490b7f5b28ea0c0c962ef5
Docker version: Docker 23.0.1
Are you using Docker Swarm or Kubernetes? NO
Operating System and version:Linux 5.19.0-32-generic 22.04.1-Ubuntu

Fixed by #5731.