Rewrite the Run function of configStoreMonitor

Please provide a description of this PR:
There are several problems with the old logic when stop has been closed:

Can't make sure all the events in the eventCh been processed.

To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @whalecold. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@whalecold: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test release-notes

gencheck_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test gencheck

release-notes_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test gencheck

release-notes_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test release-notes

unit-tests-arm64_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
74105f846b9fa67f330c5044f63fbfbdcdcc672d
link
true
/test gencheck

release-notes_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test release-notes

unit-tests-arm64_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test unit-tests-arm64

unit-tests_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test unit-tests-arm64

unit-tests_istio
515baecb338afe54b1c4bf87d492b8b0bc4b4e31
link
true
/test unit-tests

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

integ-pilot-multicluster_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

integ-pilot-multicluster_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-multicluster

integ-pilot_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

integ-pilot-multicluster_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-multicluster

integ-pilot_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

integ-pilot-multicluster_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-multicluster

integ-pilot_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-telemetry_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-istiodremote

integ-cni_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-cni

integ-pilot-multicluster_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot-multicluster

integ-pilot_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-pilot

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

integ-telemetry_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test integ-telemetry-istiodremote

release-notes_istio
a428df1eda20be4d41f2fd937860c9c39092eae2
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test release-notes

lint_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test release-notes

lint_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test lint

gencheck_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test lint

gencheck_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test gencheck

release-notes_istio
236eb262d0330de99f464fd21d524ce9fd00da64
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7767c075e6a556e8d64ad3b7530eee0552317301
link
true
/test gencheck

release-notes_istio
236eb262d0330de99f464fd21d524ce9fd00da64
link
true
/test release-notes

lint_istio
236eb262d0330de99f464fd21d524ce9fd00da64
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
236eb262d0330de99f464fd21d524ce9fd00da64
link
true
/test lint

release-notes_istio
84988037984825cc14a35743ef39907f1a14b9b3
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/release-note-none

/test release-notes

@whalecold: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8ccafa6df730315ee7bb7eae8247e40bd21674ad
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8ccafa6df730315ee7bb7eae8247e40bd21674ad
link
true
/test lint

gencheck_istio
8ccafa6df730315ee7bb7eae8247e40bd21674ad
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test lint

gencheck_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test lint

gencheck_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test gencheck

unit-tests-arm64_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test lint

gencheck_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test gencheck

unit-tests-arm64_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test unit-tests-arm64

unit-tests_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test unit-tests

integ-security-multicluster_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test gencheck

unit-tests_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test unit-tests

integ-security-multicluster_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test integ-security-multicluster

lint_istio
4dbe69e932fad84a3e65cf0cd4958ceec468be55
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
a948ec18da2ea8da08f1b43a365079aecf37abcb
link
true
/test integ-security-multicluster

lint_istio
4dbe69e932fad84a3e65cf0cd4958ceec468be55
link
true
/test lint

gencheck_istio
4dbe69e932fad84a3e65cf0cd4958ceec468be55
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@whalecold: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
b2c0b055d5d516ad2dd5d3594001fc70f03b1946
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient

/test integ-ambient

/reopen


How to resolve issue (#489) for my local(dev) microraiden instance?

Thanks @andrevmatos for resolving issue (#489) . I do have one microraiden instance running on my local server. I am now facing same issue(#489) with that instance. Please let me know how I can fix my local microraiden instance?.

That issue means that your server isn't being able to see the same channels as the client. Ensure both the node in your server and the client are on the same chain and on latest version of the ethereum clients (due to hardfork fixes).

@andrevmatos Please confirm the steps that I need to perform:
Upgrade geth to latest version
Resync ropsten testnet
Restart microraiden server
Please let me know if anything more to do?


Create consumer theme for form input

Issue Description
To match consumer UX, we want to enable the theming of terra input.
Here is a screenshot of the current component:

Evaluate if we will solve this issue as well
https://github.com/cerner/terra-core/issues/755
Issue Type

[ ] New Feature
[x] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
CSS custom properties are added to enable the theming of the <Input /> component to match consumer UX visuals.

Tech Design
4 Consumer Theme states need to be added to a themes.scss file for input
-Default
-Focus
-Active
-Disabled
In order to achieve this variables in input.scss will be needed to change into variables so they can be modified in consumer theme for example with height currently it is
//Input.scss
:local {
  ...
  height: 1.857em;
  ...
   &[type='checkbox'],
   &[type='radio'] {
      height: auto;
      ...
    }
 ...
}

This will need to change to
//Input.scss
:local {
  ...
  height: var(--terra-input-height, 1.857em_;
  ...
   &[type='checkbox'],
   &[type='radio'] {
      height: auto;
      ...
    }
 ...
}

//_themes.scss
@include cerner-consumer-theme {
   --terra-input-height: 32px;
}

This way the input text box can be modified for the consumer theme while keeping the defaults for legacy terra-core input, this "pattern" will need to be followed for all of the css props that would change in the consumer theme opacity,border etc.

With the currently recommended tech design, we would have to override every value we set back to the original values specifically for radio/check boxes. This could get messy and easy to forget or get things wrong. Additionally, when we start theming the control.scss file more, and creating our custom inputs, there would be css affecting radio/checkbox in multiple css files, and i'm not actually even sure how the specificity wins out here.
What if we instead used a not selector, or maybe radio/check shouldn't even consume the same base input as its going to look very different. @JakeLaCombe  thoughts?

@alex-bezek  perhaps that would be the right move would be to move scss for checkbox and radio from Input.scss to the Control.scss file

So for example it would work like this
//Input.scss

:local {
...
.input:not([type='checkbox']):not([type='radio']) {
  //input box css variables would go here defaulted
  //to what the current values are for example..
  border: var(--terra-input-border, #dedfe0 solid 1px;);
  ...
}
}

Then all radio and checkbox css would move to the input class in Control.scss so
.input in Control.scss would become
   .input {
      vertical-align: middle;
      border: 0;
      font-size: 1em;
      display: inline-block;
      height: auto;
      width: auto;
      padding: 0.178em;
    }

Using the not selector is a good indication of poor encapsulation. My vote is for the second approach Alex suggested. The Control should either not consume the base input or the base input should contain the bare minimum styles that apply to every input and do not cause conflicts. It feels awkward the base Input.scss immediately overrides declared styles to satisfy radio / checkbox and then then Control.scss also adds its' own styles.
There's already some conflicting styles in Input.scss from Control.scss
https://github.com/cerner/terra-core/blob/master/packages/terra-form/src/Control.scss#L5
https://github.com/cerner/terra-core/blob/master/packages/terra-form/src/Input.scss#L15
My opinion is that radio / checkbox specific theme-able styles should be encapsulated in Control.scss, or Radio.scss / Checkbox.scss respectively

perhaps that would be the right move would be to move scss for checkbox and radio from Input.scss to the Control.scss file and then use CSS variables in Input.scss for what needs to be themed for input box

+1 to this idea.

Ok, so I'll encapsulate the radio/checkmark in their own scss files, probably better for them to have their own separate ones for in the future when theming starts happening for checkmark and radio.

Tech Design
4 Consumer Theme states need to be added to a themes.scss file for input
-Default
-Focus
-Active
-Disabled
In order to achieve this variables in input.scss will need to be added, for example in order to handle height
//Input.scss
  height: var(--terra-input-height, 1.857em);

//_themes.scss
  --terra-input-height: 32px;

With the current design checkbox and radio would have its css overwritten so the css for checkbox and radio that is currently in input.scss will be moved into control.scss, perhaps in the future this will be broken up into radio.scss/checkmark.scss for theming purposes.
Therefor the based input component will need to make sure that it does not apply the .input class from Input.scss to inputs with type radio or checkmark.
A _themes.scss file will be need to be created this will contain all the themes for the terra-form package.

Therefor the based input component will need to make sure that it does not apply the .input class from Input.scss to inputs with type radio or checkmark.

This logic can either be added in the Input.jsx file as a conditional check on type or we could make Control render its own input element instead of wrapping the <Input /> component. I'm fine with either way.

@bjankord  was thinking of modifying this line: https://github.com/cerner/terra-core/blob/master/packages/terra-form/src/Input.jsx#L58
to something like this instead of having control render its own input element
    const inputClasses =
    cx([(customProps.type === 'radio' || customProps.type === 'checkbox') ?
    '' : 'input', additionalInputProps.className]);

OCS input has been created and will be resolved by current work tracked instead with this new issue #1207


How about cut email functions off mail-time, just make a common lib.

I have a suggestion:

mail-time some feature is awesome. like queue, multiple server, retries, strategy, and so on. this should be in sms, crawler, and some async things.
How about cut email functions off mail-time, just make a common lib

Hello @fangjj ,
Very sorry for late reply, I'm glad you've found this library useful.
By the way it's based on top of josk NPM library which should be a great fit for tasks you've described. Let me know wdyt.

Closing in favor of #7


The redo CreateOperation is not equal to the initial CreateOperation

This took me a lot of time to understand and track down.

enable autosave (only reproduces with autosave on!)
do the following change in bulkFileEdits.ts:

have a ts file with the contents:

const myInterestingAndVeryLongedNameFunction = () => {

}

function myUtility() {
    return 5;
}

select the function entirely
do the quick fix "Move to a new file"
undo
redo
Observe that an exception is thrown. The exception is very hairy to understand, but the root cause is that a text buffer is created for myUtility.ts, but its content hash does not equal the content hash when the text buffer was disposed, so the undo-redo element is not rehydrated, so that's why there's an error. The root cause is that in the "redo" case the CreateOperation is not creating an empty file, but a file with contents. I can only speculate that this has to do with autosave. I suggest that the DeleteOperation has an optional reference to a CreateOperation and that it can return the exact same CreateOperation instance for the "redo" as the "do"...

The root cause is that in the "redo" case the CreateOperation is not creating an empty file, but a file with contents. I can only speculate that this has to do with autosave. I suggest that the DeleteOperation has an optional reference to a CreateOperation and

Makes sense. The DeleteOperation creates an undo operation which always restores the file contents. That IMO makes sense given that a delete could occur for any file. However, a delete which undoes a create shouldn't not do this.


Add CFU playground example, initially for Arty

Instructions for someone already familiar with CFU-Playground:
Use the proj/mnv2_first project.   Cd to that directory.
Build the bitstream: make bitstream.
Go to the gateware build directory, soc/build/digilent_arty.mnv2_first/gateware/.
Look in the tcl script for the sources and copy them to the appropriate locations in fpga-tool-perf (it seems the pre-generated VexRiscv Verilog should go under third-party/)
Add project/cfuplayground.json with tests for "arty-a35t" and "arty-a100t" at 100MHz.
(Compare with the baselitex.json if necessary)

We may want the "hps_accel" project instead of the "mnv2_first" project.   Consult with tcal before starting work.
We'll also want to test this example with the Oxide toolchain.


Cannot reproduce the results on "correlated" setting for CIFAR-10C

Thank you for your work and for creating this repository for different TTA settings. While trying your code for "roid.yaml" file and "correlated" TTA setting, I cannot reproduce the results from the paper. I tried batch sizes of 64 as well as 200.  Below is the output generated for roid:
[23/07/23 21:57:51] [conf.py:  353]: PyTorch Version: torch=1.13.1+cu117, cuda=11.7, cudnn=8500
[23/07/23 21:57:51] [conf.py:  354]: ADACONTRAST:
  ALPHA: 1.0
  BETA: 1.0
  CE_SUP_TYPE: weak_strong
  CE_TYPE: standard
  CONTRAST_TYPE: class_aware
  DIST_TYPE: cosine
  ETA: 1.0
  NUM_NEIGHBORS: 10
  QUEUE_SIZE: 16384
  REFINE_METHOD: nearest_neighbors
BN:
  ALPHA: 0.1
CKPT_DIR: ./ckpt
CKPT_PATH:
CONTRAST:
  MODE: all
  PROJECTION_DIM: 128
  TEMPERATURE: 0.1
CORRUPTION:
  DATASET: cifar10_c
  NUM_EX: -1
  SEVERITY: [5]
  TYPE: ['gaussian_noise', 'shot_noise', 'impulse_noise', 'defocus_blur', 'glass_blur', 'motion_blur', 'zoom_blur', 'snow', 'frost', 'fog', 'brightness', 'contrast', 'elastic_transform', 'pixelate', 'jpeg_compression']
COTTA:
  AP: 0.92
  RST: 0.01
CUDNN:
  BENCHMARK: True
DATA_DIR: ./data
DESC:
DETERMINISM: False
EATA:
  D_MARGIN: 0.05
  FISHER_ALPHA: 2000
  NUM_SAMPLES: 2000
GTTA:
  LAMBDA_MIXUP: 0.3333333333333333
  PRETRAIN_STEPS_ADAIN: 20000
  STEPS_ADAIN: 1
  USE_STYLE_TRANSFER: False
LAME:
  AFFINITY: rbf
  FORCE_SYMMETRY: False
  KNN: 5
  SIGMA: 1.0
LOG_DEST: roid_230723_215751.txt
LOG_TIME: 230723_215751
MODEL:
  ADAPTATION: roid
  ARCH: Standard
  EPISODIC: False
  WEIGHTS: IMAGENET1K_V1
M_TEACHER:
  MOMENTUM: 0.999
OPTIM:
  BETA: 0.9
  DAMPENING: 0.0
  LR: 0.001
  METHOD: Adam
  MOMENTUM: 0.9
  NESTEROV: True
  STEPS: 1
  WD: 0.0
RMT:
  LAMBDA_CE_SRC: 1.0
  LAMBDA_CE_TRG: 1.0
  LAMBDA_CONT: 1.0
  NUM_SAMPLES_WARM_UP: 50000
RNG_SEED: 1
ROID:
  MOMENTUM_PROBS: 0.9
  MOMENTUM_SRC: 0.99
  TEMPERATURE: 0.3333333333333333
  USE_CONSISTENCY: True
  USE_PRIOR_CORRECTION: True
  USE_WEIGHTING: True
ROTTA:
  ALPHA: 0.05
  LAMBDA_T: 1.0
  LAMBDA_U: 1.0
  MEMORY_SIZE: 64
  NU: 0.001
  UPDATE_FREQUENCY: 64
SAR:
  RESET_CONSTANT_EM: 0.2
SAVE_DIR: ./output/roid_cifar10_c_230723_215751
SETTING: correlated
SOURCE:
  NUM_WORKERS: 4
  PERCENTAGE: 1.0
TEST:
  ALPHA_DIRICHLET: 0.1
  BATCH_SIZE: 64
  NUM_WORKERS: 4
  N_AUGMENTATIONS: 32
  WINDOW_LENGTH: 1
[23/07/23 21:58:18] [base.py:  141]: #Trainable/total parameters: 17952/36479194 	 Fraction: 0.05%
[23/07/23 21:58:18] [test_time.py:   45]: Successfully prepared test-time adaptation method: ROID
[23/07/23 21:58:18] [test_time.py:   56]: Using the following domain sequence: ['gaussian_noise', 'shot_noise', 'impulse_noise', 'defocus_blur', 'glass_blur', 'motion_blur', 'zoom_blur', 'snow', 'frost', 'fog', 'brightness', 'contrast', 'elastic_transform', 'pixelate', 'jpeg_compression']
[23/07/23 21:58:18] [test_time.py:   77]: resetting model
[23/07/23 21:58:18] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:58:41] [test_time.py:  111]: cifar10_c error % [gaussian_noise5][#samples=10000]: 74.77%
[23/07/23 21:58:41] [test_time.py:   81]: not resetting model
[23/07/23 21:58:41] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:58:57] [test_time.py:  111]: cifar10_c error % [shot_noise5][#samples=10000]: 74.09%
[23/07/23 21:58:57] [test_time.py:   81]: not resetting model
[23/07/23 21:58:57] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:59:12] [test_time.py:  111]: cifar10_c error % [impulse_noise5][#samples=10000]: 77.68%
[23/07/23 21:59:12] [test_time.py:   81]: not resetting model
[23/07/23 21:59:12] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:59:27] [test_time.py:  111]: cifar10_c error % [defocus_blur5][#samples=10000]: 70.83%
[23/07/23 21:59:27] [test_time.py:   81]: not resetting model
[23/07/23 21:59:27] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:59:42] [test_time.py:  111]: cifar10_c error % [glass_blur5][#samples=10000]: 78.51%
[23/07/23 21:59:42] [test_time.py:   81]: not resetting model
[23/07/23 21:59:42] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 21:59:57] [test_time.py:  111]: cifar10_c error % [motion_blur5][#samples=10000]: 71.41%
[23/07/23 21:59:57] [test_time.py:   81]: not resetting model
[23/07/23 21:59:57] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:00:13] [test_time.py:  111]: cifar10_c error % [zoom_blur5][#samples=10000]: 70.43%
[23/07/23 22:00:13] [test_time.py:   81]: not resetting model
[23/07/23 22:00:13] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:00:28] [test_time.py:  111]: cifar10_c error % [snow5][#samples=10000]: 73.13%
[23/07/23 22:00:28] [test_time.py:   81]: not resetting model
[23/07/23 22:00:28] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:00:44] [test_time.py:  111]: cifar10_c error % [frost5][#samples=10000]: 71.34%
[23/07/23 22:00:44] [test_time.py:   81]: not resetting model
[23/07/23 22:00:44] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:01:01] [test_time.py:  111]: cifar10_c error % [fog5][#samples=10000]: 70.62%
[23/07/23 22:01:01] [test_time.py:   81]: not resetting model
[23/07/23 22:01:01] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:01:18] [test_time.py:  111]: cifar10_c error % [brightness5][#samples=10000]: 68.15%
[23/07/23 22:01:18] [test_time.py:   81]: not resetting model
[23/07/23 22:01:18] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:01:34] [test_time.py:  111]: cifar10_c error % [contrast5][#samples=10000]: 70.70%
[23/07/23 22:01:34] [test_time.py:   81]: not resetting model
[23/07/23 22:01:34] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:01:50] [test_time.py:  111]: cifar10_c error % [elastic_transform5][#samples=10000]: 75.45%
[23/07/23 22:01:50] [test_time.py:   81]: not resetting model
[23/07/23 22:01:51] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:02:06] [test_time.py:  111]: cifar10_c error % [pixelate5][#samples=10000]: 73.71%
[23/07/23 22:02:06] [test_time.py:   81]: not resetting model
[23/07/23 22:02:06] [data_loading.py:  133]: Using Dirichlet distribution with alpha=0.1 to temporally correlated samples by class labels...
[23/07/23 22:02:22] [test_time.py:  111]: cifar10_c error % [jpeg_compression5][#samples=10000]: 76.69%
[23/07/23 22:02:22] [test_time.py:  114]: mean error: 73.17%, mean error at 5: 73.17%

I see, you use RN-26 GN architecture instead of standard architecture.


Should dropping a Body implicitly release remaining capacity?

Body is used to release capacity on a stream. If the body is dropped and the remaining capacity is not released, then that connection level capacity is lost.

Probably. Once the Body is dropped, there is no more API surface to release the capacity. Technically, it's possible that the user has taken the chunks, and dropped the body, but not dropped the chunks, and so the resource capacity is still in use... But, there's a lot of things a user could do that that would by-pass any smart thing we might do.
Like just copying the chunks into a Vec<u8>...

When all user references to a stream are dropped (SendStream, RecvStream, ReserveCapacity), the unreleased stream capacity will now be given back to the connection automatically.


Add overview of available modules to guidelines?

There is an overview for elements, attributes etc., but not for the available modules. Maybe this would be good to have, as every element description is pointing to a certain module and attributes and models and the like can be sorted "by module".
Additionally, there could/should be a link from both locations to the module overview descriptions.

Modules are here: https://github.com/music-encoding/music-encoding/tree/develop/source/modules

I was thinking about adding that to the new chapter 1 of the Guidelines, but that might be too hidden…

Yes, too hidden. May be as a separate entry on the right panel next to Elements, Atttribute Classes etc..

And from there on? Open a page with the full list of modules. Each of those could be a link that points to another overview page which gives a brief description at the top (probably just the //moduleSpec/desc), and then lists all elements, model / att classes etc. from that module. Right?

Yes, analogue to the Elements, Attributes etc. pages

Closing since modules are now integrated into the guidelines dev version.


gopass show -o shows unexpected warning

gopass still shows warnings, when passing the -o flag to gopass show:
correct and expected behavior:
gopass some/thing
⚠ some/thing is a secret and a folder. Use 'gopass show some/thing' to display the secret and 'gopass list some/thing' to show the content of the folder
Secret: some/thing

612709qBg2rCkQckzy9pxwRNz80tglG

imho unnecessary but i guess acceptable behavior:
gopass show some/thing
⚠ some/thing is a secret and a folder. Use 'gopass show some/thing' to display the secret and 'gopass list some/thing' to show the content of the folder
Secret: some/thing

612709qBg2rCkQckzy9pxwRNz80tglG

note: the warning does not appear when using gopass list. intended behavior?
gopass list some/thing
some/thing/
├── api_key
└── api_secret

unexpected behavior:
gopass show -o some/thing
⚠ some/thing is a secret and a folder. Use 'gopass show some/thing' to display the secret and 'gopass list some/thing' to show the content of the folder
612709qBg2rCkQckzy9pxwRNz80tglG

gopass help show | grep -- -o
   --password, -o             Display only the password. Takes precedence over all other flags. (default: false)

This gopass is installed from Manjaro community repo:
gopass --version
gopass 1.12.6 (2021-05-11 15:27:04) go1.16.4 linux amd64

@roalcantara The proper way to store a "pin" in an entry is to rely on key-values:
$ gopass generate --clip --generator memorable leaf.jp/naruto 20

$ gopass generate --clip --generator memorable leaf.jp/naruto pin 6

$ gopass show -f leaf.jp/naruto
Secret: leaf.jp/naruto

hollow5deliver5shoe2
pin: extra4

$ gopass show -f leaf.jp/naruto pin
Secret: leaf.jp/naruto
Key: pin

extra4

Notice the way I use a space to add a key to an entry:
gopass generate --clip --generator memorable leaf.jp/naruto pin 6

This adds a key "pin" to the entry "leaf.jp/naruto", whereas what you are doing is creating a new entry "leaf.jp/naruto/pin" in the folder "leaf.jp/naruto" while there already is an  existing entry "leaf.jp/naruto" as well.
See maybe also the documentation:

about key-values: https://github.com/gopasspw/gopass/blob/master/docs/commands/show.md#parsing-and-secrets
about "shadowing an entry with a folder": https://github.com/gopasspw/gopass/blob/master/docs/commands/list.md#shadowing

This should works as expected in theory with the bridge and everything.
@mcnesium I can still reprodruce the issue with -o showing the warning, will look into that.

Thanks for fixing :+1:


Enable CSS transitions for moving plot points

Overview
There is no way to add transitions to point elements that move around inside the plot area. This includes any points that are tied to a line (are drawn with the line). Currently, when transitions are added, lines will move smoothly to next arrangement but, the points on the line will just jump to next positions.
Proposed changes
This likely requires a few changes:

add x and y properties to CSS transition properties
make class names or id's given to transition-capable elements more stable so that when other parts of the SVG changes, the names in other parts are not effected.

one strategy is to use the SVG element position in the DOM tree to generate more stable names

add point elements to transition dictionary

525ff51


Mapping Copilot (F23) -> CTRL not working

Microsoft PowerToys version
0.79.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I am trying to map the Copilot / F23 on my new keyboard back to CTRL
I have set up the below configuration but it is not working

✔ Expected Behavior
That the CoPilot key functions like the CTRL key
❌ Actual Behavior
The CoPilolt key now does nothing when pressed
Other Software
No response

I am willing to bet that the physical button sends a combination. Try and use "Remap a shortcut" and let us know if that helps.

Try and open "remap a shortcut" in Keyboard manager. Then press the button, like you did.

Hi Jay, I have tried that, and I have added a shortcut mapping as below, but this still does not give the desired results

I've also tried mapping it to "X" and other keys, but the Copilot key simply stops working.
Incidentally, when I click OK to confirm and close the shortcut setup box, the underlying PowerToys dashboard window closes abruptly, though the PowerToys icon remains in the taskbar.

Hm. This key is relatively new, so I don't know for sure how it exactly works. Another idea: is the keyboard compatible with the MS Mouse and Keyboard app? Maybe you can change something in there.

Hi Jay, no I don't believe it is, its the built in keyboard on the laptop.
Would be great to get this working in PowerToys as I can't believe I'm the only person who will wan to remap this crazy key (at least until Copilot becomes more useful).

Hey, I'm not sure if you've fixed this yourself, but I had some success with this by remapping it as a shortcut specifically via PowerToys like so. Hopefully this sorts you out as well.

Willing to get rid of the Copilot key too on a laptop keyboard where I really need the right ctrl (Ctrl + / to comment or uncomment code), I ended up with the same shortcut as @itswyll. However it does not work all the time. To make the Copilot button behave as the Ctrl key in combination I have to hit and release the Copilot button first, and only then the Ctrl + other key combination works.
@itswyll do combinations work all the time first time for you or is your experience similar to what I'm observing?

Willing to get rid of the Copilot key too on a laptop keyboard where I really need the right ctrl (Ctrl + / to comment or uncomment code), I ended up with the same shortcut as @itswyll. However it does not work all the time. To make the Copilot button behave as the Ctrl key in combination I have to hit and release the Copilot button first, and only then the Ctrl + other key combination works.
@itswyll do combinations work all the time first time for you or is your experience similar to what I'm observing?

It works on the first try for me. I'm on a Lenovo Yoga. My use case is the same as yours with 'ctrl + /' and 'ctrl + backspace'
This is the edit view for my shortcut. I didnt make any other changes other than this one, so I don't have much else I can add unfortunately.

Thanks @itswyll, I have the exact same mapping on a Lenovo Legion Pro, and this is the only one I have.
The 'wake up call' after focussing the window seems to be systematically needed for all the applications I use (CLion, VSCode, Firefox). I'll keep observing / investigating and will report here. Before finding this solution I did a few tests with AutoHotKeys but AHK is no longer running so I doubt it will have changed anything.

I just opened a very similar issue #33589 on Jul 1, 2024: "Keyboard Manager Doesn't Remap key F23 to Ctrl key, instead Remaps it to Ctrl+Shft ."    I have tried it with the same Remap a Shortcut configuration described above, and pictured below.  BUT, It just now worked properly as Ctrl key when I deleted a Remap Key instruction that was also listed, which must have been interfering.  I still don't understand the "Win + Shift + F23" instructions, which self populated when I pressed the pencil button and then pressed the copilot key.  I'm using a Lenovo -IdeaPad Slim 5i with Windows 11. Thanks for all the suggestions.  I'll close my issue#, but it has some details.

my asus zenbook remapping work now. after tried, use remapping keys (maybe) not remapping key

So weird that with my ASUS Expertbook i do exactly the mapping as suggested here (by ChisLynnCL, but for me it does not work.
why why why?  CoPilot button is still a nightmare... What am i missing?


Feat/updates for v5

Fixes #183.
Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

[ ] Update target to next
[ ] Update CI workflow to v4 tag

Need to sync next before merging

I'll sync next before merging


401 Token Refresh Error silently causes realtime connection to fail and edits are lost

If I open or create a realtime document, make changes, then leave the page open for about an hour I get the following errors on the console:
GET https://drive.google.com/otservice/bind?id=1foZRE7k3IRUxWnQaOHDrsN_OfSi3gjs…RID=rpc&SID=FFE129C546C61272&CI=0&AID=201&TYPE=xmlhttp&zx=f2rvegin3z1g&t=1 401 (Unauthorized) api:80
Drive Realtime API Error: token_refresh_required: The OAuth token must be refreshed. api:186

There is no error presented in the UI, or anywhere else. Then if I continue to make changes to the realtime data model they appear to be applied successfully (i.e. no errors and the changes show in the "Event Log" panel on the right). However, when I refresh the page and re-open the document, none of the changes I made after the previously mentioned error (401) occurred were actually saved.
This is a problem since data was silently lost without any indication in the UI. Can the app automatically re-authorize when a 401 occurs and still maintain the realtime connection to the data model? Is there an error/event which indicates when updates to the data model are not actually saved?

Got the same error in my app and I have no idea how I can catch it.

+1


Is it possible to run the server with Node.js?

I am trying to import lsp-server into my own ide. So I am trying to understand what vscode-languageserver engine to do to launch and keep lsp-server running.
Here is my experiment:

webpack an existing language-server into a .js file, in my experiment it's server.js
start server.js with the command line "node server.js --socket=1219 --pid=33048"  1219 is my own port and 33048 is my own client process id.
but it didn't work. am I got sth wrong?

@feilongsword Did you a) write your own language server or b) download an existing language server from somewhere?

@feilongsword Did you a) write your own language server or b) download an existing language server from somewhere?

Yes, i download an existing language server and webpacked it.

start server.js with the command line "node server.js --socket=1219 --pid=33048"  1219 is my own port and 33048 is my own client process id.
but it didn't work. am I got sth wrong?

@feilongsword Can you elaborate on what "it didn't work" means? What happened? Did you get an error message or something? Providing as much information as possible will help narrow things down.

@feilongsword Did you a) write your own language server or b) download an existing language server from somewhere?

Yes, i download an existing language server and webpacked it.

Which language server did you download?

start server.js with the command line "node server.js --socket=1219 --pid=33048"  1219 is my own port and 33048 is my own client process id.
but it didn't work. am I got sth wrong?

@feilongsword Can you elaborate on what "it didn't work" means? What happened? Did you get an error message or something? Providing as much information as possible will help narrow things down.

@feilongsword Did you a) write your own language server or b) download an existing language server from somewhere?

Yes, i download an existing language server and webpacked it.

Which language server did you download?

The language server is an AutoHotkey language server. Here is its source code mainted by gitee:https://gitee.com/orz707/vscode-autohotkey2-lsp.
I webpacked this server and so I got a server.js in /server/dist.
and then I run the command "node server.js --socket=1219 --processid=33048" in /server/dist.
but when I am trying to connect to the port, I got a connection error: ErrorCode 10061 Connection Refused. My client and server works on the same machine. My client code written in C#
            string jsonstr ="{\"jsonrpc\":\"2.0\",\"id\":0,\"method\":\"initialize\",\"params\":{ \"processId\":0,\"rootUri\":\"home\",\"capabilities\":{ }}}";             m_Process = new Process();             Process curProcess = Process.GetCurrentProcess();             string filepath = @"D:\GitHub\vscode-autohotkey2-lsp\server\dist\start.bat";             StreamWriter writer = File.AppendText(filepath);             writer.Write(curProcess.Id.ToString());             writer.Close();             m_Process.StartInfo.FileName =filepath;             m_Process.EnableRaisingEvents = true;             m_Process.StartInfo.RedirectStandardError = true;             m_Process.StartInfo.RedirectStandardInput = true;             m_Process.StartInfo.RedirectStandardOutput = true;             m_Process.Start();             Console.WriteLine("Server Start");             StringBuilder strbuild = new StringBuilder();             byte[] bytes = System.Text.Encoding.Default.GetBytes(jsonstr);             strbuild.Append("Content-Length:"+ bytes.Length);             strbuild.Append("\r\n");             strbuild.Append("\r\n");             Console.WriteLine("Header is:" + strbuild.ToString());             string header = strbuild.ToString();             Socket sendsocket = new Socket(AddressFamily.InterNetwork,SocketType.Stream,ProtocolType.Unspecified);             sendsocket.Connect(new IPEndPoint(IPAddress.Parse("<IP_ADDRESS>"),1219));
the command in start.bat is
@echo node D:\GitHub\vscode-autohotkey2-lsp\server\dist\server.js  --socket=1219 --processId=
I check the port 1219 status with 'netstat' command and find this port is not in use.

The language server is an AutoHotkey language server. Here is its source code mainted by gitee:https://gitee.com/orz707/vscode-autohotkey2-lsp.
I webpacked this server and so I got a server.js in /server/dist.
and then I run the command "node server.js --socket=1219 --processid=33048" in /server/dist.

@feilongsword Did you try running the server without webpacking it? Does that work?

The language server is an AutoHotkey language server. Here is its source code mainted by gitee:https://gitee.com/orz707/vscode-autohotkey2-lsp.
I webpacked this server and so I got a server.js in /server/dist.
and then I run the command "node server.js --socket=1219 --processid=33048" in /server/dist.

@feilongsword Did you try running the server without webpacking it? Does that work?

Not tried it yet now. I am new to TypeScript, so just followed the author's suggestion.
I am also searching a way to convert a ts project to a c# project, but it seems like that there is no way.

The language server is an AutoHotkey language server. Here is its source code mainted by gitee:https://gitee.com/orz707/vscode-autohotkey2-lsp.
I webpacked this server and so I got a server.js in /server/dist.
and then I run the command "node server.js --socket=1219 --processid=33048" in /server/dist.

@feilongsword Did you try running the server without webpacking it? Does that work?

It seems like impossible to start the server without webpacking. Because He use ESM and TypeScript at the same time. I got the same problem as https://stackoverflow.com/questions/65097694/to-load-an-es-module-set-type-module-in-the-package-json-or-use-the-mjs-e when I am trying to "node server.ts"

Which client are you using to connect to the server. The VS Code client library assumes that it will start the server using the node runtime you provide it. It doesn't work well with server you start by hand.


Solution to Issue #3

Incorrect conditional of user vs assistant when creating history:
https://github.com/Me163/rusty_llama/issues/3

thanks for this! For me this bug didn't have any obvious effect on the functionality, which is really interesting...


add todo apps writen by go

🚀 Follow me, 💬 Join the WhatsApp Group, and ⭐ Star the Repo to support our journey together!


Localize Text, Content & Buttons

Currently I need to do something like the following to get the localized text for the alert:
extension String {
  func getLocalizedTextForAlert() {
        let path = Bundle.main.path(forResource: "ar", ofType: "lproj")
        let bundle = Bundle(path: path!)
        return NSLocalizedString(self, tableName: nil, bundle: bundle!, value: "", comment: "")
  }
}

where ar is one of the supported languages in my app (Arabic), because doing just: Text("some text") will always fallback to the English version of the some text text. Giving that I have two Localizable.strings files in the app: one for en and the other for ar localization.

Hi, I see there is an issue while providing the title. There are 3 variants of providing the title for the Custom Alert. One with Title, one with LocalizedStringKey and one with StringProtocol
With the first one (Title), localization works like any Text. Text("some string") will be localized as long as "some string" is a key in your Localizable.strings
.customAlert(Text("Title"), isPresented: $showAlert) {
    Text("My localized Message")
} actions: {
    Button(role: .cancel) {

    } label: {
        Text("OK")
    }
}

In this example everything is localized, as long as "Title", "My localized Message" and "OK" are String Keys in Localizable.strings
The issue I see is that the third (StringProtocol) one is preferred over the second (LocalizedStringKey) one at the moment. This will be fixed in v2.3.0 the current workaround would be. Then again  everything is localized, as long as "Title", "My localized Message" and "OK" are String Keys in Localizable.strings
.customAlert("Title" as LocalizedString, isPresented: $showAlert) {
    Text("My localized Message")
} actions: {
    Button(role: .cancel) {

    } label: {
        Text("OK")
    }
}

The localization of the Content and Buttons should just work like any localization with any Text in SwiftUI, it is up to the integrator how they want to provide Localization. Text("some string") will be localized as long as "some string" is a key in your Localizable.strings

Title should be fixed with v2.3.0. The Localization of Content and Buttons is up to the integrator and should just work like any other localization in your app.

TestLocalizedAlert.zip
Thank you for the prompt reply, however, I didn't mention that when the iPhone's main language in Settings app is set to English then the alert won't localized the Title, Message and Action buttons to Arabic even if the strings are added in the Localizable.strings files, and it localizes to the other language (Arabic) as expected when the iPhone's main language is set to Arabic.
My real app gives the user the option to set its locale to English or Arabic regardless to the main iPhone's language through injecting the @Environment(\.locale) into the main app's view (ContentView in the attached sample project).
check the attached sample and see how the alert doesn't localize the Title to Arabic when the iPhone's main language is set to English.

I see, thank you for the example. That helps a lot. The way CustomAlert works is that the CustomAlert is in its own UIWindow, but the SwiftUI Environment is not automatically transferred to it, since it's a completely new root view.
The SwiftUI.Environment of the calling view will be propagated in v2.4.0 which should fix your issue. If not please let me know.

yes v2.4.0 did exactly that and the issue is fixed. Thank you so much for your quick fix.


server/routers.go: Fix checkNameExists

When copy a model with a existed name, it suppose to error out, but it success.
The old checkNameExists only report exist model name in case the name is different, but they are same when both of
them convert to upper case, it means TEST and test is a same name, but test and test is not a same name.
# ollama cp tinyllama tinyllama
copied 'tinyllama' to 'tinyllama'

And we should not check name existence on create and pull, because
it suppose to replace some layers of the existing model

@mxyng PTAL

there seems to be some misunderstanding. this is working as expected
checkNameExists is intended to perform a case-insensitive check to see if the name already exists in some form, e.g. name and Name
an exact match of the name doesn't constitute existence since overrides are possible
here's a summary:

checkNameExists("name", "name") == false
checkNameExists("notname", "name") == false
checkNameExists("Name", "name") == true

@mxyng thanks for the clarification


Refactor Listr2 tasks to remove closures and ensure they are stored in Classes with a single responsibility

Get rid of all of the task closures and organize into classes using SOLID principles
### Tasks
- [ ] AccountCommand

depends on https://github.com/hashgraph/solo/issues/655

duplicate, rolling into https://github.com/hashgraph/solo/issues/1053


Change post date

Describe the bug
On android I can change a date of a post, but it fails and sets the date for a timestamp of 0 (1970...). In firefox on a PC I can't edit a date at all.
Steps to reproduce
Android:

Edit post
Click date
Save it, observe wrong time stamp

PC:

Edit post
Click date
Nothing happens

The version of Memos you're using.
latest
Screenshots or additional context
No response

Are you able to confirm the version you are using

I believe this issues should be fixed for versions > v0.22.5

Oh my, I'm so sorry, I didn't update... Version: v0.22.5


CamelCase -> SnakeCase conversion not supported?!

Getting missing field errors when my  Struct has fields such as field_example but the dynamodb table field is "fieldExample".

Can workaround with #[serde(rename="stream_name")].


"byText" and "withText" conditions should ignore non-breakable spaces

Hello&nbspworld cannot be found by $(byText("Hello world")) or $(withText("Hello world"))

Have yout tried with by/withText("Hello world")?
--
Alexei Vinogradov
Am 8. September 2017 um 15:04:38, Maria-Fedorova-sb (
<EMAIL_ADDRESS>schrieb:

Hello&nbspworld cannot be found by $(byText("Hello world"))
or $(withText("Hello world"))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeborne/selenide/issues/597, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGQ4YDLdyMbR5ujIopJjqT4J1UryBOPsks5sgTtmgaJpZM4PRJyU
.

Yea. It's not working too.
      Element not found {with text: Hello world}
      Expected: exist
      Timeout: 4 s.
      Caused by: NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":".//*/text()[contains(normalize-space(.), "Hello world")]/parent::*"}

only \u00A0 works well


Ability to customize falco's http_output for logstash http input plugin.

Motivation
I attempting to ship falco events via http_output to logstash's http input. I am missing a field that would identify the incoming events as produced by falco. http_user_agent is also empty.
Feature
An ability to add additional field to http payload (or a fixed field) that would help identify the incoming data in logstash. e.g.
"source" => "falco"

Alternatives
Custom script that would wrap the log message with additional fields. But ideally http_output ought to be a little bit customizable.
Additional context
Example of data that comes into logstash http input via falco's http_output, for reference  (as seen in logstash) :
{
   "output_fields" => {
                          "fd.name" => "<IP_ADDRESS>:45264-><IP_ADDRESS>:22",
                       "proc.pname" => "sshd",
                     "proc.cmdline" => "sshd",
                        "user.name" => "root",
                           "fd.sip" => "<IP_ADDRESS>",
                 "evt.time.iso8601" =><PHONE_NUMBER>668757005,
                     "container.id" => "confes02_prod",
                           "fd.num" => 0,
                    "user.loginuid" => 1000,
                   "container.name" => "confes02_prod",
       "container.image.repository" => nil,
                          "fd.type" => "ipv4",
                        "proc.name" => "sshd",
                         "proc.tty" => 0
   },
          "output" => "2021-12-31T13:10:06.668757005+0000: Warning Redirect stdout/stdin to network connection (user=root user_loginuid=1000 confes02_prod (id=confes02_prod) process=sshd parent=sshd cmdline=sshd terminal=0 container_id
=confes02_prod image=<NA> fd.name=<IP_ADDRESS>:45264-><IP_ADDRESS>:22 fd.num=0 fd.type=ipv4 fd.sip=<IP_ADDRESS>)",
         "headers" => {
           "http_accept" => "*/*",
          "content_type" => "application/json",
          "http_version" => "HTTP/1.1",
          "request_path" => "/",
        "request_method" => "POST",
             "http_host" => "<IP_ADDRESS>:8080",
        "content_length" => "870",
       "http_user_agent" => nil
   },
      "@timestamp" => 2021-12-31T13:10:06.743Z,
            "host" => "<IP_ADDRESS>",
        "@version" => "1",
            "rule" => "Redirect STDOUT/STDIN to Network Connection in Container",
            "time" => "2021-12-31T13:10:06.668757005Z",
          "source" => "syscall",
        "priority" => "Warning",
            "tags" => []
}

I see some value in making the http output a little more customizable. If so, I think source would not be a good name for any new field, since we already use that to indicate the event source (see "source" => "syscall" in your example). Would you mind opening a PR to propose your changes?

once i get familiar with falco's code - sure.

https://github.com/yoshi314/falco/commit/d3dfa61759f5624dc5dd87726dcc8f89825c8e57
i made a commit to my fork, but i have no clue how to do a PR (not really familiar with github).  A simple addition of user-agent is sufficient for my needs, since it seems to be unset by default.
This way i can filter out falco's data stream for other ones going into logstash from the same ip.
The commented out lines add ability to inject version to user agent string, although that might be a bit more expensive for logstash if regexp or substring matching is going to be involved.

This can become a good contribution! Why not adding a new config field to falco.yaml like http_output.user_agent? You can find the contribution guidelines of our community here: https://github.com/falcosecurity/.github/blob/master/CONTRIBUTING.md
Also, check this for opening a PR in GitHub: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

ok, i'll try that again.

ok, i'll try doing a PR later today.
For now the updated changes are here : https://github.com/yoshi314/falco/commit/d8148c7981bf5137b26f6c3a376fe63077538c83


remove unnecessary Authorization header on webhook endpoints

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[x] Internal code
[ ] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes #1898
Description
this PR removes the Authorization header from callback endpoints requests. I'm not sure which endpoints don't require this, so assistance is welcome

I currently don't intend to merge this as it was stated that this is not something that libraries should be handling.
This is a bug in the Discord platform itself.


Multiple emails sent for vulnerabilities

Hi all
The vulnerabilities scan is a great feature, but shouldn't it only send email notifications once? At the moment emails about the same vulnerabilities are being sent every couple of days.

Messages with the scan result are sent each time such a scan is performed. Currently, when updating the vulnerability database, such a scan starts automatically, so you receive this message more than once. This should motivate you to fix the vulnerabilities.
You might be tempted to introduce an option that would allow you to "freeze" the scan for a given package. But in order to do this, more people would have to appear. I'm closing for the moment. If you have any further questions, comments or doubts, feel free to discuss.


HADOOP-17869. fs.s3a.connection.maximum should be bigger than fs.s3a.threads.max

Description of PR
This PR aims to increase fs.s3a.connection.maximum to be bigger than fs.s3a.threads.max.
How was this patch tested?
HADOOP-15183 defined this variable like the following.

https://github.com/apache/hadoop/commit/e02eb24e0a9139418120027b694492e0738df20a#diff-268b9968a4db21ac6eeb7bcaef10e4db744d00ba53989fc7251bb3e8d9eac7dfR1216-R1221

Controls the maximum number of simultaneous connections to S3. This must be bigger than the value of fs.s3a.threads.max so as to stop threads being blocked waiting for new HTTPS connections.

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

what do you think should be good values for modern systems? Say:? 64 threads and 96 connections? having lots of threads isn't so bad if they are all uploading to/downloading from S3 as they'll be waiting for network IO, not fighting for CPU time with worker threads

Changing fs.s3a.connection.maximum from 48 to  96 sounds good to me. I'll update this PR according to your opinion.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
11m 47s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 38s

trunk passed

+1 :green_heart:
compile
29m 11s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
24m 22s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
4m 26s

trunk passed

+1 :green_heart:
mvnsite
2m 55s

trunk passed

+1 :green_heart:
javadoc
1m 51s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 31s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
4m 35s

trunk passed

+1 :green_heart:
shadedclient
18m 28s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 56s

the patch passed

+1 :green_heart:
compile
28m 19s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
28m 19s

the patch passed

+1 :green_heart:
compile
24m 28s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
24m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 21s

the patch passed

+1 :green_heart:
mvnsite
2m 50s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 48s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m 34s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
5m  6s

the patch passed

+1 :green_heart:
shadedclient
19m  7s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m 41s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 58s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

244m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3337/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3337

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 6522380e4d89 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 057a45706927a20f44c6f316c49f67cd4cd1769e

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3337/2/testReport/

Max. process+thread count
2504 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3337/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

LGTM
I've actually been thinking about having better thread pooling here with a RejectedExecutionHandler which

increments a statistic
hands on to ThreadPoolExecutor.CallerRunsPolicy

So rather than do blocking when the pool is full, fall back to executing in the current thread. Goal: when the pool is full we still get useful work done because the current thread is doing it.
I worry about this though when it comes to things like RenameOperation; is the use of CompletableFuture<> creating expectations in the code that the work will actually be done by a separate thread.
How about we merge this patch in as this, and then look at that problem in more detail.

Thank you, @steveloughran . It sounds like a good plan.
cc @sunchao , too.

ok, in trunk & 3.3. Thanks for this

Thank you so much, @steveloughran and @sunchao !


Duplicate entries

I constantly find duplicate record entries when I go to save. Anyone else experiencing this?

I haven't seen anything like this... Can the problem be reproduced reliably (is there a procedure we can follow to see it happening)?


🐛 BUG: worker named "accounts" yields bizarre behavior

What version of Wrangler are you using?
2.0.22
What operating system are you using?
Mac
Describe the Bug
For several weeks I have been working on a worker names "accounts". Our team has several workers, of which this is one. This worker, unlike any of my other workers, shows really strange behavior when ever interacting with the wrangler CLI / the Workers service.
We reuse a lot of configuration and logic between workers, so believe me that there is nothing unique about the worker, its configuration (.toml), or settings selected on the Cloudflare dashboard.
Note: I had created the worker during a Workers outage on October 19th, and had always thought in the back of my mind that the strange behavior was tied to something that went wrong during the outage, like a bug in the Workers service inserted an invalid value in Cloudflare's database or something.
Now I'm wondering if the name "accounts" somehow breaks wrangler or the Workers service.
If indeed the worker name "accounts" is somehow not supported or is a reserved keyword, this should be fixed or at least called out in the wrangler CLI when you attempt to create it.
I know I am using a slightly outdated version of wrangler (2.0.22) as you'll see in behavior below, and if this has been solved please link to the PR or release that contains a bug fix (I couldn't find it).
wranger.toml
The only thing unique about this worker for us is the name.
name = "accounts"
workers_dev = true
compatibility_date = "2022-05-03"
node_compat = true

Behavior
Whenever deploying the worker
Total Upload: 1138.09 KiB / gzip: 196.72 KiB
Worker ID:  accounts
Worker ETag:  <NOT SHARING THIS>
Uploaded accounts (1.63 sec)

✘ [ERROR] A request to the Cloudflare API (/accounts/<NOT SHARING THIS>/workers/scripts/accounts/subdomain) failed.

  Could not route to
  /client/v4/accounts/<NOT SHARING THIS>/workers/scripts/accounts/subdomain, perhaps
  your object identifier is invalid? [code: 7003]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/wrangler2/issues/new/choose

Although the worker does deploy, shows as updated in the Workers dashboard, and my logic is updated.
New environment variables
worker-accounts wrangler secret put EXAMPLE_VARIABLE
 ⛅ wrangler 2.0.22 (update available 2.6.2)
------------------------------------------------------
Retrieving cached values for account from node_modules/.cache/wrangler
Enter a secret value: *
🌀 Creating the secret for the Worker "accounts"

✘ [ERROR] A request to the Cloudflare API (/accounts/<NOT SHARING THIS>/workers/scripts/accounts/secrets) failed.

  Could not route to
  /client/v4/accounts/<NOT SHARING THIS>/workers/scripts/accounts/secrets, perhaps
  your object identifier is invalid? [code: 7003]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/wrangler2/issues/new/choose

This has forced me to manually update the variables from the Workers dashboard, and sometimes they disappear randomly after I save them.
Partial Solution
Now I have decided to rename my worker to "accts" and everything works perfectly like my other workers.
Contributing
I'm not new to Workers or wrangler as a developer, but I am not at all familiar with the source code in this repo to contribute to a solution. I also suspect it may involve the Workers service / Cloudflare API which is not hosted here.
I am happy to give any information about our configuration that I can and will check my notifications for questions / responses to this Bug Report to help it be investigated and get solved for others in the future.

I can reproduce on a wrangler init with accounts and the latest version of wrangler.
It's definitely the name accounts that does it, see below where I try account and then accounts
➜  accounts git:(main) ✗ cat wrangler.toml
name = "account"
main = "src/index.ts"
compatibility_date = "2022-12-16"
➜  accounts git:(main) ✗ npx<EMAIL_ADDRESS>publish
 ⛅ wrangler 2.6.2
-------------------
Total Upload: 0.19 KiB / gzip: 0.16 KiB
Uploaded account (1.87 sec)
Published account (1.58 sec)
  https://account.erisacf.workers.dev
Current Deployment ID: 72328ed7-2c87-4e4c-90c5-6ac7d5dc0cc4
➜  accounts git:(main) ✗ nano wrangler.toml
➜  accounts git:(main) ✗ cat wrangler.toml
name = "accounts"
main = "src/index.ts"
compatibility_date = "2022-12-16"
➜  accounts git:(main) ✗ npx<EMAIL_ADDRESS>publish
 ⛅ wrangler 2.6.2
-------------------
Total Upload: 0.19 KiB / gzip: 0.16 KiB
Uploaded accounts (1.87 sec)

✘ [ERROR] A request to the Cloudflare API (/accounts/2d0d216f0f48937d2a261c5af101afd7/workers/scripts/accounts/subdomain) failed.

  Could not route to
  /client/v4/accounts/2d0d216f0f48937d2a261c5af101afd7/workers/scripts/accounts/subdomain, perhaps
  your object identifier is invalid? [code: 7003]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/wrangler2/issues/new/choose

@zpg6 thanks for the detailed write-up, and @Erisa for the repro! We're working on this now, and will update it as progress is made.

Might have ran into this when trying to upload a folder named accounts to r2:
⛅ wrangler 3.0.0
------------------
Creating object "accounts/test.txt" in bucket "mybucket".

✘ [ERROR] Failed to fetch /accounts/ACCOUNT-ID/r2/buckets/mybucket/objects/accounts/test.txt - 404: Not found);

Still an issue ⛅ wrangler 3.20.0

@missinglink yes it is. This is due to an underlying Cloudflare API restriction. The only workaround currently is to not use the name accounts.


xml the text color is dark.

The color text on xml files is black, with the dark gray background it is difficult to read.
For the rest it works nice, thank you.

Well, I tried to reproduce this issue as follows:

Created a file with the XML extension.
Wrote some XML.
Wrote XML similar to what is in the screenshot.

The result looks like this:

As you can see, the syntax highlighting was correct.
The check was performed in the following environment:

Visual Studio 2022 version: 17.4.3
Extension version: 1.1.0
Is the resharper installed: tested with and without it

Please check if everything is updated and if the problem persists, give me more context when and how it is reproduced.

This one was a xamarin AndroidManifest.xml, the one created by VS.
AndoirdManifest.xml

new project:

activity_main.xmls

However, if I create a new single xml file it works perfect. I copy paste the same xml on a new xml file and it looks nice.

In version 1.1.1, I made changes that should fix this. I tested it on one of my old Xamarin projects and it worked for me. I hope this will work for you too👌.
If the problem persists, please reopen this issue.


NestedScrollView overlapTop behavior and Toolbar

Hi! I want to achieve this behavior where NestedScrollView overlap CollapsingToolbarLayout and MenuItems of Toolbar are still clickable. But the problem is if i place the NestedScrollView above SmoothAppBarLayout then the MenuItems of Toolbar are clickable but  the content inside the NestedScrollView stay behind CollapsingToolbarLayout. And if i place NestedScrollView below SmoothAppBarLayout then the Toolbar stay behind NestedScrollView so its MenuItems are not clickable anymore. Any suggestion?
Toolbar's Menu Items clickable but looks bad

Toolbar's Menu Items are not click able, i want it to look like this

I already managed to resolve the problem by placing the Header inside NestedScrollView.


Fix parsing multiple types of codes

This fixes an issue where the extract_markers function in parser.gd sometimes places BBCode tags in the wrong location due to not correctly interpreting the locations of the other codes (wait, speed, etc.).
Here is what the following line looks like in the test scene before and after this change.
Test: Waiting for [b]boldness[/b]...[wait=3] Waiting for [i]italics[/i]...[wait=4] Done [color=blue]blue[/color] waiting!
Before fix:

After fix:

Thanks 👍


Fix tz2 signature verification and signing

ring doesn't seem to offer a way to sign/verify a prehashed message. ed25519-dalek does, and the methods we're using atm also to the sha512 (so we do two hashing).

Unless we don't need to do the blake2b hash for tz1? @clehner

blake2b is not needed for tz1. Ed25519 specifies SHA-512: https://datatracker.ietf.org/doc/html/rfc8032#section-5.1

blake2b is not needed for tz1

Actually I'm not sure, seeing as the hash step is removed in https://github.com/spruceid/ssi/pull/200/commits/a573b25c90f6604406984922c44b0095ad565213#diff-859afcdde128730c6eb7badc55e61454f63fed6cbb70d7a513f70502420d57cfL1256
Tests should check that the signature in edpk_jwk_tz_edsig and did-pkh/tests/vc-tz1.jsonld remain valid, as those were produced from a Tezos wallet.

I think adding the three algorithms is a correct approach given the current API. But if there is a simpler way, that could be good.
If/when LDP in ssi is refactored to not require JWK for signing and verification but instead use verification method and proof objects directly, TezosSignature could be updated to use crypto library functions directly instead of going through ssi::jws.
RFC 7515 says the algorithm (alg) name should either be registered in the IANA JSON Web Signature and Encryption Algorithms registry, or contain a "Collision-Resistant Name" (ES256K-R does not follow this):

https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.1
https://datatracker.ietf.org/doc/html/rfc7515#page-6
https://www.iana.org/assignments/jose/jose.xhtml#web-signature-encryption-algorithms

If using the current approach, maybe EdBlake2b, ESBlake2b, ESBlake2bK should be renamed to URIs?

The remaining test was failing due to a mismatch of the old EdDSA in the proof and the use of the new EdBlake2b in the JWK. I have allowed those pairs for the time being (only for the verification, and only the provided public key can have an different/old alg).

I agree that specifying a custom alg doesn't fit the specs and the purpose of those proofs.

If/when LDP in ssi is refactored to not require JWK for signing and verification but instead use verification method and proof objects directly, TezosSignature could be updated to use crypto library functions directly instead of going through ssi::jws.

I might be wrong and biased, but that confirms my previous intention of using the trait combination of Signer + Digest for a potential Signature trait. That being said, we still need to handle those VCs in the wild which we have issued already, so I feel like this work wasn't in vain (yes we're creating more mess that way, but at least it's unambiguous).
How do you specify the public key without publicKeyJwk?

How do you specify the public key without publicKeyJwk?

The other property listed in DID Core is publicKeyMultibase: https://www.w3.org/TR/did-core/#dfn-publickeymultibase
(Previously it was publicKeyBase58 but that is deprecated now.) This property represents a public key encoded as bytes, but it doesn't specify how, which I think leaves it up to the signature suite / verification method specifications (i.e. our choice here). We could use the existing Tezos-style type-prefixed base58-encoded public key, and prepend "z" to make it multibase-encoded (e.g. zedpk..., zsppk..., zp2pk...).

trait combination of Signer + Digest for a potential Signature trait

I would be interested to see more what you mean.

Rebased and squashed.

We could use the existing Tezos-style type-prefixed base58-encoded public key, and prepend "z" to make it multibase-encoded (e.g. zedpk..., zsppk..., zp2pk...).

 Actually now that I write this it feels like using multibase wouldn't save us from having custom logic on how to interpret the key (i.e. you need to know about the signature type to know how to use the key).

trait combination of Signer + Digest for a potential Signature trait

I would be interested to see more what you mean.

Continuing off the above, I thought we could keep the interpretation of the key pure, independent from the signature. The oddities of the signatures would be restrained to a Digest trait which would be responsible on formatting (e.g. hashing) the input data for the Signer. In other words, the Signature trait is responsible for picking the right Digest and the right Signer.
But I don't know if it's feasible, I might be too optimistic on how much we can segregate the hashing from the actual signing.


[FIX][INTERNAL] sap.m.Popover: Stabilize _onOrientationChange method

There is a fix from v1.75. Please correct me if I am wrong about the correction process.
There might be some race conditions where the Popover gets destroyed and the orientation to change.
So, we should ensure that if there's no popover, this method would be skipped.
Change-Id: Id4cc8e7e4f967c543483af1db737ba316a1cbfc3
BCP:<PHONE_NUMBER>

 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.

Hello @sharapinski ,
Thank you for your pull request. I've created an internal record<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Also have in mind that you have to sign the Contributor License Agreement.
Regards,
Yana

Hello @yanaminkova ,
thank you for the internal record and your attention.
Hm, I see the message "You have signed the CLA for SAP/openui5" on the CLA page, but it's not updated here.
Best regards,
Raman

Hi @sharapinski ,
The issue is fixed with change - I4d458e77c448c3b100f0bf8f66a159f59768ce9e
Best regards,
Martin


[ILX-49850-2] Upgrade react-native-scanner

Upgrade react-native-scanner

This is not required, we have created another PR


The component does not work on safari (iOS)

Hi,
great component, but there is an issue on iOS. Users and Browserstack are consistent about it. I tried your own site, https://dmnwebdesign.github.io/vue-fb-customer-chat/, too. The code from Facebook itself works. I am guessing that you use a version of the SDK which is not the most actual one!
Keep up the good work,
Leo

I looked into your code: you're loading SDK  version: 'v3.0' facebook now uses  version: 'v5.0'. I proposed the change.

Hi @leosok,
thx for your comment. I've just upgraded SDK Version, but I'm not sure it help in your problem.

@dmnWebDesign, you are right. It's a messenger Bug. A very strange one: when you open a link from inside the Facebook Messenger App (it opens a browser which I suppose is a Web-View) it would not show the Messenger-Chat-Bubble. In a normal Browser Window it worked all the way. But because I sent the link to my friends via messenger they didn't see it. Maybe something to mention in the Docs?
Nevertheless good thing to update the SDK.


NEMO data access

I have a windows operating system and don't have access to Linux or a super computer.
I was wondering if there was an online database or somewhere I could access some NEMO data to be used in my dissertation project. I am looking for 3D data as I am going to be modelling particle release from the sea floor from hydrothermal vents.
thanks!

Hi @cbreasley,
At https://marine.copernicus.eu/ there are many different ocean products available including reanalyses using NEMO data. Note: the velocity data from the NEMO C-Grid is interpolated onto an A-grid for these products (see here for more information)
Cheers,
Reint


remove fill from polygons

updated to use no fill for polygons. Changed outline color to red -
consistent with range ring rendering.

@csmoore can you please review merge?

LGTM


Bug Fix: Use toRad function of wrapper instead of one that has been in number prototype

There were some calls of .toRad(..) still in code. They are now blindly replaced by toRad(..) available in wrapper.

Nice catch! Thanks!


attempt to index field 'running_var'

Hi, I'm trying to test your network, however I got an error while running "DelugeNet-146 on CIFAR-10"
I created docker image myself for CUDA 7.0 + CUDNN 4.0 + Torch + fb.resnet.torch,
and I checked the fb.resnet.torch works well.
However, when I put your model files to models/ and run your CIFAR train command, it returns an error.
following messages are the error, I don't know how to treat that.
Do you have any solution?

root@a041bf04ed08:~/fb.resnet.torch# th main.lua -batchSize 64 -nEpochs 300 -optnet true -netType delugenet -dataset cifar10 -depth 146.1
=> Creating model from file: models/delugenet.lua
| DelugeNet-146.1 CIFAR-10
/root/torch/install/bin/luajit: /root/torch/install/share/lua/5.1/nn/Container.lua:67:
In 2 module of nn.Sequential:
In 3 module of nn.Sequential:
In 1 module of nn.Sequential:
In 1 module of nn.ConcatTable:
In 1 module of nn.Sequential:
./models/CrossLayerDepthwiseConvolution.lua:54: attempt to index field 'running_var' (a nil value)
stack traceback:
./models/CrossLayerDepthwiseConvolution.lua:54: in function <./models/CrossLayerDepthwiseConvolution.lua:45>
[C]: in function 'xpcall'
/root/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/root/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function </root/torch/install/share/lua/5.1/nn/Sequential.lua:41>
[C]: in function 'xpcall'
/root/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/root/torch/install/share/lua/5.1/nn/ConcatTable.lua:11: in function </root/torch/install/share/lua/5.1/nn/ConcatTable.lua:9>
[C]: in function 'xpcall'
/root/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/root/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function </root/torch/install/share/lua/5.1/nn/Sequential.lua:41>
...
/root/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function </root/torch/install/share/lua/5.1/nn/Sequential.lua:41>
[C]: in function 'xpcall'
/root/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/root/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function 'forward'
/root/torch/install/share/lua/5.1/optnet/init.lua:387: in function 'optimizeMemory'
./models/init.lua:47: in function 'setup'
main.lua:33: in main chunk
[C]: in function 'dofile'
/root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk
[C]: at 0x00406670

WARNING: If you see a stack trace below, it doesn't point to the place where this error occurred. Please use only the one above.
stack traceback:
[C]: in function 'error'
/root/torch/install/share/lua/5.1/nn/Container.lua:67: in function 'rethrowErrors'
/root/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function 'forward'
/root/torch/install/share/lua/5.1/optnet/init.lua:387: in function 'optimizeMemory'
./models/init.lua:47: in function 'setup'
main.lua:33: in main chunk
[C]: in function 'dofile'
/root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk
[C]: at 0x00406670
root@a041bf04ed08:~/fb.resnet.torch#

Please try updating Torch modules to the latest versions.

@xternalz
I ran 'luarocks install torch', it still returns same error.
But during that command, building process showing log about failing to find "MKL library".
Is that mandatary?

Reinstall Torch according to the official guide http://torch.ch/docs/getting-started.html#_.  You have to update more than just the torch package (cutorch, nn, cunn, cudnn, ...).

I started with clecn ubuntu 14.04 + CUDA + CUDNN docker image, so everything about torch is based on fb.resnet.torch install instruction.
should I update everything?

cuDNN v4 is obsolete, please opt for cuDNN v5 and the latest Torch's cudnn package.

Got it. Because of the fb.resnet.torch install instruction guided with v4, I installed that version.
After update to v5, cudnn package, I will let you know.
Thanks for your help.

I updated CUDA to 7.5 and CUDNN to 5.1, I works well.
Thanks @xternalz .
I will close this issue.


bugs fix

Fixed bugs in K8s deployment

Can one of the admins verify this patch?

Also can all API server image value in values.yaml be changed to latest 5.5.0 release image tags @SRINI2410

API servers images tag has been updated @abhi4578


error 403

### CODE
await _dio.download(
urlPath,
'${dir.path}/Download/$filename.mkv}',
cancelToken: _cancel,
onReceiveProgress: (count, total) {
progress = ((count / total) * 100).toInt();
filesize = total ~/ 1024;
downlaodResponse(progress, filesize);
},
);
} catch (e) {
print(e);
}
### ERROR
url :-https://eduid01-my.sharepoint.com/personal/mi_eduid01_onmicrosoft_com/_layouts/15/download.aspx?UniqueId=aab222da-9e79-4389-bc27-5a90e4bd2823
I/flutter ( 5002): DioError [DioErrorType.response]: Http status error [403]
I/flutter ( 5002): #0 DioMixin.assureDioError
package:dio/src/dio_mixin.dart:819
I/flutter ( 5002): #1 DioMixin._dispatchRequest
package:dio/src/dio_mixin.dart:678
I/flutter ( 5002):
I/flutter ( 5002): #2 DioMixin.fetch.. (package:dio/src/dio_mixin.dart)
package:dio/src/dio_mixin.dart:1

Facing the same problem on Android!

Facing the same problem on Android!

are you also facing same problem
?

Facing the same problem on Android!

yes

all necessary permissions already exists


typo

Hm, great catch !
Thank you!