Fix test race

Please provide a description for what this PR is for.
fixes: #16093
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

e2e-simpleTests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

e2e-simpleTests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-master

istio-codecov-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-codecov-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

e2e-simpleTests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-master

istio-codecov-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-codecov-master

istio-unit-tests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-unit-tests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

istio-codecov-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-codecov-master

istio-unit-tests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-unit-tests-master

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test e2e-simpleTests-distroless-master

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

istio-codecov-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-codecov-master

istio-unit-tests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-unit-tests-master

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-lint-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-lint-master

istio-codecov-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-codecov-master

istio-unit-tests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-unit-tests-master

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
2ef9b2b95c557322564746a0a0889440b6d0a2e5
link
/test istio-unit-tests-master

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

integ-mixer-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-mixer-k8s-presubmit-tests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-distroless-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

integ-mixer-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-mixer-k8s-presubmit-tests-master

integ-new-install-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-new-install-k8s-presubmit-tests-master

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

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

integ-mixer-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-mixer-k8s-presubmit-tests-master

integ-new-install-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTestsMinProfile-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test e2e-simpleTestsMinProfile-master

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

integ-mixer-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-mixer-k8s-presubmit-tests-master

integ-new-install-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-codecov-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-codecov-master

istio-unit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-unit-tests-master

istio-racetest-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test istio-racetest-master

integ-mixer-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-mixer-k8s-presubmit-tests-master

integ-new-install-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-presubmit-tests-master
71922cc26ad5952a47239d1213338f3f4ef411aa
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

istio-pilot-multicluster-e2e-master
562db5fbe859b657208455b16996cb816e27e826
link
/test istio-pilot-multicluster-e2e-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

istio-pilot-multicluster-e2e-master
562db5fbe859b657208455b16996cb816e27e826
link
/test istio-pilot-multicluster-e2e-master

integ-new-install-k8s-presubmit-tests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test integ-new-install-k8s-presubmit-tests-master

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

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

istio-pilot-multicluster-e2e-master
562db5fbe859b657208455b16996cb816e27e826
link
/test istio-pilot-multicluster-e2e-master

integ-new-install-k8s-presubmit-tests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-master

istio-pilot-multicluster-e2e-master
562db5fbe859b657208455b16996cb816e27e826
link
/test istio-pilot-multicluster-e2e-master

integ-new-install-k8s-presubmit-tests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test integ-new-install-k8s-presubmit-tests-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

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.

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-pilot-multicluster-e2e-master
562db5fbe859b657208455b16996cb816e27e826
link
/test istio-pilot-multicluster-e2e-master

e2e-simpleTestsMinProfile-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTestsMinProfile-master

e2e-simpleTests-distroless-master
562db5fbe859b657208455b16996cb816e27e826
link
/test e2e-simpleTests-distroless-master

integ-new-install-k8s-presubmit-tests-master
562db5fbe859b657208455b16996cb816e27e826
link
/test integ-new-install-k8s-presubmit-tests-master

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.


AttributeError: '_io.TextIOWrapper' object has no attribute 'strip'

This is the error that is showing in my terminal.
AttributeError: '_io.TextIOWrapper' object has no attribute 'strip'
>>>unable to get battery node
unable to get backlight node
unable to get backlight node
unable to get smc values

Thank you so much for submitting an issue. I will have a mac with me tomorrow. What is your hardware config?

I'll try to fix it now, tell me if it works.

Okay, try doing: pip install MacTmp==0.0.2

Okay, wait, I need to change the command I am using to get Cpu temp. Sorry for the delay. I will get it working in the next 1-2 days.

Okay, try doing pip install MacTmp==0.0.6
The cpu temp should work, but the gpu temp is still broken. I will fix the gpu temp soon.

@minshinkhant cpu temp fixed, gpu temp still broken. I will fix the gpu temp soon.

Hi, Thank you for fixing it. I am also trying to put clear instruction for the readme and will submit the commit.
Also, the last update still giving me this issue. The CPU one.
IndexError: list index out of range

Okay, I will have a mac in 1 hour. I will fix then.

Okay, try doing pip install MacTmp==0.0.7
I tested it on a mac, and it worked.

The gpu temp will not work with Intel Integrated Graphics.

@minshinkhant try doing pip install MacTmp==0.0.8 and then try.

it is still giving me this error.
unable to get smc values
'CPU Temperature not found'

I am using macmini mid 2011.
I also try with Window and still showing 'CPU Temperature not found'

Okay, for windows use: https://github.com/kethan1/WinTmp
Please type this in your command prompt: sudo powermetrics --samplers smc -i1 -n1

Oh, and I heard there are issue with the command I am using, sudo powermetrics --samplers smc -i1 -n1 with mac minis. I will see if I can fix this.

Okay, for windows, there was a bug with the path of a dll, that I fixed, so do: pip install WinTmp==0.0.4

Let me know when you fixed the issue with the Mac. Thank you..

As I don't have a Mac Mini, I will be using Github Actions to test. Expect updates in the next weeks or two.

Thank you.

Github Actions doesn't allow access to SMC, I will try to update module and see it if works though...


Support writing output to a file

Output writing to a file is needed for some filetypes (e.g. odt, docx).
Closes: #43
Also remove idea/pycharm project files from git

The test failure seem to be unrelated:
test_conversion_from_markdown_with_extensions (__main__.TestPypandoc) ... pandoc: Unknown reader: markdown+strikeout
pandoc: Unknown reader: markdown-strikeout
FAIL
test_conversion_with_markdown_extensions (__main__.TestPypandoc) ... pandoc: Unknown writer: markdown+strikeout
pandoc: Unknown writer: markdown-strikeout
FAIL

Does travis has a older version available? IPython has some version handling stuff https://github.com/ipython/ipython/blob/master/IPython/nbconvert/utils/pandoc.py

Edit: yep, extensions on travis willnot work until a newer than 0.10 version of pandoc is installed: http://johnmacfarlane.net/pandoc/releases.html#pandoc-1.10-2013-01-19 -> 6th item:

It is now possible to enable or disable specific syntax extensions by appending them (with + or -) to the writer or reader name. [...]

yep, extensions on travis will not work until a newer than 0.10 version of pandoc is installed: http://johnmacfarlane.net/pandoc/releases.html#pandoc-1.10-2013-01-19 -> 6th item:

Ok. Maybe it would be possible to work around this? Ie. skip tests in some particular case (not ideal but better current situation). Anyway, this goes beyond this PR.
The PR is looking good to me.
@msabramo Any thoughts?


Add preamble in generated .sql

This should include babar marketing stuff, version etc.

Maybe a splash screen too with some ascii art


Helm chart failing when namespace is purely numeric

Hello folks. I stumbled upon a strange error when installing localstack via helm. Here is the error:
Error: unable to build kubernetes objects from release manifest: [unable to decode "": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Namespace: ReadString: expects " or n, but found 4, error found in #10 byte of ...|mespace":4444412}}|..., bigger context ...|0.4.1"},"name":"localstack-mod-test","namespace":4444412}}|..., unable to decode "": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Namespace: ReadString: expects " or n, but found 4, error found in #10 byte of ...|mespace":4444412},"s|..., bigger context ...|0.4.1"},"name":"localstack-mod-test","namespace":4444412},"spec":{"externalTrafficPolicy":null,"port|..., unable to decode "": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Namespace: ReadString: expects " or n, but found 4, error found in #10 byte of ...|mespace":4444412},"s|..., bigger context ...|0.4.1"},"name":"localstack-mod-test","namespace":4444412},"spec":{"replicas":1,"selector":{"matchLab|...]
The following modification at all places, where Namespace is referenced, seems to fix the issue:
{{ .Release.Namespace | quote }}
So, whenever we reference the Namespace, we use the "| quote" thing.
Would this be a good fix for the issue? Is there any other way to circumvent the problem?

Hi @pguglev , thanks for reporting - sounds like a good solution to quote the namespace values. This repo is largely maintained by the community (not by the LocalStack core maintainers) - do you think you could create a pull request to add this functionality? Thanks for your help!
/cc Any other thoughts @LaikaN57 ?

Yes, I can do that. Be warned however, that I am not an expert in the matter. But I am sure someone more experienced will review my merge request.

Thanks @pguglev , fixed in https://github.com/localstack/helm-charts/pull/63 👍


Our previous lab group

Hi,
I remember we have a lab GitHub repo? Does it still exist ?
Songpeng

Hi Songpeng. Here it is: https://github.com/biotcm/


Imprecise sentence

"By default, the cluster certificates for node-to-node security are added to the allowed client admin certificates list."
This is not precise as it suggests that you can remove cluster certs from allowed client admin cert list.

This is not possible as cluster cert needs those permissions to function.
in the client cert list you don't get to see the certificate.

A better sentence would be:
"Cluster certificates have the same rights as client admin certificates. However, they should be used only by cluster and not by administrative users as a security best practice."

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a5258d97-54db-f748-46bc-50d3162a9bfa
Version Independent ID: bd553e49-d868-c5e5-4b8a-0e1ed6e3ff5c
Content: Secure an Azure Service Fabric cluster
Content Source: articles/service-fabric/service-fabric-cluster-security.md
Service: service-fabric
GitHub Login: @athinanthny
Microsoft Alias: atsenthi

@peledins I updated the doc. Once the PR merges the changes go live after a few hours.
If you have further suggestions please submit a PR against the doc yourself and the authors and I will review.


Inconsistent order of media attachments for scheduled posts

Hey 👋,
I'm building an app to schedule posts and noticed that the mediaAttachments and params.mediaIds in ScheduledPost have inconsistent ordering. params.mediaIds appears to have the correct order, while mediaAttachments are sorted numerically by their id. I'm not sure whether this would be considered to be a bug in the Mastodon API, but it would be nice to have consistent ordering in TootSDK. If you agree, I can create a pull request to add a decodable implementation of ScheduledPost that fixes the ordering based on params.mediaIds.

Hey 👋
I’d definitely be interested to see a PR from you for this!


Appstudio update test-custom-default-branch-sczv

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-dtnt-on-pull-request-
creating pipelinerun test-annotations-dtnt-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-zuiz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Use Next's Link component

Motivation
The create fuels app template should use  next's Link component to avoid unnecessary refreshes.
Usage example
No response
Possible implementations
We could just change the current Link component to use Next's Link instead of an a tag

As discovered in #2691, there are still some places where this work needs to be done. Re-opening

@Dhaiwat10, as mentioned here, can I send another PR to add Next's Link to the template?


compilation bugs fixed

Sorry for the late time.
There is a fork updated to typescript 2.6.
For me it stops in "loading assets"

@raphaelMuth Does this now compile? Could you post the console output.

It's in portuguese, sorry
1>------ Recompilação total iniciada: Projeto: WormsHTML5, Configuração: Release Any CPU ------
1>  WormsHTML5 -> C:\Users\Raphael\Documents\Visual Studio 2017\Worms-Armageddon-HTML5-Clone-master\bin\WormsHTML5.dll
========== Recompilar Tudo: 1 com êxito, 0 com falha, 0 ignorados ==========
VS 2017

Sorry, i will check this guy a little more, and update the PR
Some wild errors appeared, i was looking in the wrong place

I'm going exclude this PR, update it from the start again, take more attention and time.
At least can you send bandwithmonitor.ts ? its missing in master


No editor features in new workflow file

I wanted to create a new workflow using the autocomplete and hover help features but it seems like they don't work in my new workflow file even though they work in pre-existing ones.
I can see a stack trace whenever I go to a new line and start typing a keyword:
stack trace: TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
	at Ct (/home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:407334)
	at n (/home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:411503)
	at /home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:412477
	at yt (/home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:408282)
	at Et (/home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:409277)
	at /home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:411740
	at /home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:411793
	at /home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:411840
	at t (/home/espeed/.vscode-server-insiders/extensions/cschleiden.vscode-github-actions-0.8.1/dist/extension.js:1:407422)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)

Yikes, thanks for reporting. I can repro, something doesn't look quite right here.

Eventually after I finished I was able to get some autocomplete to work.
One idea I had is that the incomplete files were not parsable and that prevented everything else from working.

I'm having a hard-time reproducing this with the latest version, everything works for me now:

Closing this for now.


next/release

:tada: This PR is included in version 1.4.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Updates to include Call with Chat Docs

What
Changes to include Call with Chat Composite documentation. Including:

Moving composite overviews to their overview page

Moving UI Components overview to its own page

Adding overview for Call with Chat composite

Simplify main overview page (Pending design input on the UI Artifacts section.

Why
Simplify our current overview page to be a better exploration experience that leads developers towards the documentation they are looking for.
How Tested
Locally tested

Video: https://msit.microsoftstream.com/video/057c0840-98dc-997d-ea1e-f1ecb789c488

Cleaned up PR ready for submission.
@ddematheu2 I updated the 4 boxes on the overview page to this:

(taken from an old Figma @pereiralex did a while ago)

Have sign off from david and alex offline


feat(router): set additional X-Forwarded headers

Currently X-Forwarded-Proto does not work correctly behind a load balance with SSL termination. This hopes to fix that and ensures the most common protocol related headers are set.
1.) Ensure X-Forwarded-Proto header is always set for greater application compatibility.
2.) Add X-Forwarded-Protocol and X-Forwarded-Ssl headers for greater application compatibility.
3.) Attempt to detect the proper protocol when running behind load balancers or proxies.

wow, I literally just came across this issue in the last 10 minutes and checked here 43 seconds after you'd posted this.
I can verify this is happening, I'm running on AWS I have SSL being terminated by the ELB.
ELB passes out X-Forwarded-Proto and X-Forwarded-Port, deis-router appears not to pass these on to my app.
My Rails 4 app has force_ssl set so it becomes an infinite redirect.

@rjocoleman That would make sense. The goal of this is to allow apps to accurately detect if they are running under ssl.

If #3264 gets merged use $access_scheme instead of $scheme and this should be a straightforward fix.

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Rebased, updated for #3264, and modified commit message to follow the style guide.

Jenkins, add to whitelist.

Code LGTM.

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Code LGTM. Thanks @croemmich!


The tutorial uses OnUpdateFrame which is obsolete

The tutorial uses OnUpdateFrame in https://opentk.net/learn/chapter1/9-camera.html#walk-around, also it's really hard to know where to put all the code shown before as in the repo it shows being used to render each frame but in tutorial it only needs to be assigned at OnLoad? It's hard to tell because it's not written in it.

OnUpdateFrame is not deprecated?


Enable generic method parsing by default

Running tests locally now...

there are 7 failed tests (11693 passed)
All in the form
FAIL: analysis engine | generated tests | DirectoryBasedDartSdkTest | test_[fromFile_XYZ | getXYZ]
  Expected: not null
    Actual: <null>

Did the tests pass before your change?

Did the tests pass before your change?

You ask good questions!

@bwilkerson Same failures before/after.

This looks fine, as far as it goes, but Phil also needs to make a small change before we actually publish (unless we can't wait and have to publish twice).

Yes.  Please!
Could you change the constraint on isolate?
isolate: '>=0.2.2 <2.0.0'

Thanks!

@pq @bwilkerson Reran tests with the latest isolate pkg. No new failures. I think we're good. PTAL

lgtm


[Task] Payment-Handler in Account manager uses JS SDK

Task
Contributors are able to complete this task and earn thenewboston coins.  Check out the labels to learn how much you can earn for contributing by completing this task.  Please make sure to be honest if you wish to contribute by saying you can't finish this and we can just un-assign you with no harm done!  There is no point in delaying tasks from being completed for miscommunication!

Overview

changeActivePrimaryValidator
src/renderer/dispatchers/app.ts
Changes the pv tha processes transactions

changeActiveBank
src/renderer/dispatchers/app.ts
Changes the bank that processes transactions

sendBlocks
src/renderer/utils/blocks.ts
Sends created blocks through a specific bank

Behavior
Account manager uses js sdk installed from NPM https://www.npmjs.com/package/thenewboston
Payment-Handler in Account manager uses JS SDK
/* code examples are awesome */

Please ask for this task to be assigned to you and earn and its sweet reward 😉
Remember to include your account number in your PR description for us to pay you 💰
** Pull Requests **
All Pull Request should be made to development branch, read contributors guild for more information about contributing

closed by https://github.com/thenewboston-developers/Account-Manager/pull/616


Failed to load module.

I'm trying to import StyledContentLoader after installing package through npm.

After import my component throws error Module not found

@creativejaved  styled-components is a peer-dependency of this package, you have to install it yourself.

@rfoel Thank you for your reply. I have updated doc and requested a pull request.


chore(deps): update dependency chai to v4.5.0 - abandoned

This PR contains the following updates:

Package
Type
Update
Change

chai (source)
devDependencies
minor
4.4.1 -> 4.5.0

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

chaijs/chai (chai)
v4.5.0
Compare Source

Update type detect (#1631)  1a36d35

What's Changed

Update type detect by @koddsson in https://github.com/chaijs/chai/pull/1631

Full Changelog: https://github.com/chaijs/chai/compare/v4.4.1...v4.5.0

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.

Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.


Add clang-tidy support

g:neomake_c_clangtidy_args_conf needs to be properly set, especially with the -p option indicating the build directory containing the compile command database.

Added a couple of comments. Once those are resolved I'll be happy to merge!

Thanks!


MC solution and guideline alignment

In order to keep track of what we started to discuss in today's meeting I open this issue:
Due to the last decisions that were made in commonalities (based on votes (https://github.com/camaraproject/WorkingGroups/discussions/169) related to this issue(https://github.com/camaraproject/WorkingGroups/issues/157)) the current guideline indicates that the API input and output business data would follow the lowerCamelCase notation
Currently there are two flavors in Number Verification and Sim Swap APIs. The argument to include MC proposal was to have a solution that is consistent with the available solution in the market AS-IS. But now, we have to align it to the guidelines so it’s not going to be the AS-IS definition. Mobile Connect APIs (proposed in SIM Swap and Number Verification Sub-Projects) parameters follow snake_case notation and now must be changed to lowerCamelCase.
Maybe it’s the time to reevaluate this part and see what benefits developers can get from having APIs similar to MC but not exactly aligned with them nor with 3GPP/TMF?

@monamok @bigludo7 @hazarig - thank you for the great discussion we had around this issue.
There's a proposal for an issue that we have to place in commonalities and later push to OpenGateway team:
(awaiting your feedback)

name: 🚀 Existing API standards inside CAMARA
about:  💡
Context

What are you trying to do and how would you want to do it differently? Is it something you currently you cannot do? Is this related to an issue/problem?

Currently CAMARA lacks support for API standards, that had been already defined and are commercially available.  SimSwap NumberVerify OTPValidation Working Group members working on CAMARA APIs definition, which is common with Mobile Connect APIs, tackled this issue and identified a need to assess an issue inside Commonalities WG on following actions:

Keep Mobile Connect APIs as they are - MC services are standardized by GSMA, open to developers, and commercially available, so there is no need to reinvent these and adapt to CAMARA.
Bring Mobile Connect APIs (& others that might come, like TMF, 3GPP, etc.) as APIs available over OpenGateway in parallel to CAMARA APIs (MC APIs are following the same OAUTH/OIDC framework so this is something that both standards have in common).
Ensure CAMARA APIs simplicity and focus on resource definition, for the sake of simplicity for software developers.
Adapt local (national) breakouts to CAMARA APIs, that result from e.g. legal/regulatory conditions.

Alternatives

Can you achieve the same result doing it in an alternative way? Is the alternative considerable?

Leave it as it is - creates confusion for developers trying to consume CAMARA APIs. Creates competing APIs - not good for developers & MNOs.
Archive conflicting APIs - lack of support of some APIs inside CAMARA initiative, leave it for other API standards, narrows CAMARA focus to specific 5G APIs; standards/initiatives for archived CAMARA APIs takes the lead for API development (OpenGateway should support other initiatives)
(please think of other alternatives)

Has the feature been requested before?
No
If the feature request is approved, would you be willing to submit a PR?
Yes

@DT-DawidWroblewski - Thanks !! this is good.
2 proposal in italic. Thanks for your consideration

Hi @bigludo7 !
I changed the content of the issue, please let me know if it is clear now and we can push it to Commonalities.
Have a nice long weekend!

Thanks @DT-DawidWroblewski  - looks good for me.

@DT-DawidWroblewski issue https://github.com/camaraproject/WorkingGroups/issues/200 was kind of resolved but we have still this issue open. Could you please manage the changes?
I can open a PR to sort out and adapt the repository if you prefer.

MC cleared


Handle connection error on dcos-history

When running dcos-history, if the flask app cannot bind to the port assigned it does not fail and keeps retrying. Using gunicorn ensures that the app fails and master is marked unhealthy.
https://mesosphere.atlassian.net/browse/DCOS-5334
Unit tests passed
Syntax test passed

Ready for review

I really don't think go would help here / fix the issues. The problem is purely around how people chose to structure this API in python. People made a try/catch loop that caught a little too much. I guarantee there are C++ libraries and Go libraries which have the same issue around trying to bind.
There was also a lot of learning about how different pieces work in the history of building this (how dcos_generate_config.sh works / is constructed among other things).

@cmaloney Fair point, but what I was getting at is that the threading as implemented has some weird side effects and makes it a bit more difficult to work with


Update components' tables of arguments

Ensuring table of arguments for each components is accurate.
Updates to  index.njk and README.md files for each component.
Trello ticket: https://trello.com/c/rRQl78KY/1038-make-sure-all-component-argument-tables-are-accurate
For reviewers: Might be easiest to go through each component page on Github in the branch to check the rendered README file.

@hannalaakso updated with comments


Unable to install pyproj into a dockerized linue alpine 3.12 environment

Using the python:3.9.1-alpine3.12 docker image available here as an official Python docker image:
https://hub.docker.com/_/python
I'm not able to install pyproj in the container (using pip 20.3.3):
# pip install -U pyproj

Collecting pyproj>=3.0.0
  Using cached pyproj-3.0.0.post1.tar.gz (663 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/bin/python /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp1myemgxu
       cwd: /tmp/pip-install-md9fcpl1/pyproj_dbaf8c3187964b4fabb892bc45efdb2b
  Complete output (1 lines):
  proj executable not found. Please set the PROJ_DIR variable.
  For more information see: https://pyproj4.github.io/pyproj/stable/installation.html
  ----------------------------------------
ERROR: Command errored out with exit status 1:
/usr/local/bin/python /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp1myemgxu
Check the logs for full command output.

I read through this issue: https://github.com/pyproj4/pyproj/issues/582
I installed proj-util but then there is a version mismatch:
# pip install -U pyproj
Collecting pyproj
  Using cached pyproj-3.0.0.post1.tar.gz (663 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/bin/python /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpnmgicdw8
       cwd: /tmp/pip-install-jstxoo0j/pyproj_75781808031145b2bef2e74e83c8a804
  Complete output (1 lines):
  ERROR: Minimum supported proj version is 7.2.0, installed version is 7.0.1.
  For more information see: https://pyproj4.github.io/pyproj/stable/installation.html
  ----------------------------------------
ERROR: Command errored out with exit status 1:
/usr/local/bin/python /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpnmgicdw8
Check the logs for full command output.

And indeed, proj-util has installed this version of proj (which was not present before installing proj-util):
# proj
Rel. 7.0.1, May 1st, 2020
usage: proj [-bdeEfiIlmorsStTvVwW [args]] [+opt[=arg] ...] [file ...]

Even by searching in the edge branch; https://pkgs.alpinelinux.org/packages?name=proj&branch=edge , I'm not able to figure out a proj in a minimal 7.2.0 version as stated above.
How would you fix this?
Many thanks !

See the version compatibility matrix here: https://pyproj4.github.io/pyproj/stable/installation.html#installing-from-source

See the version compatibility matrix here: https://pyproj4.github.io/pyproj/stable/installation.html#installing-from-source

I am going to close for preference to: https://gis.stackexchange.com/questions/383726/unable-to-install-proj-related-python-packages-in-a-linux-alpine-environment

I am going to close for preference to: https://gis.stackexchange.com/questions/383726/unable-to-install-proj-related-python-packages-in-a-linux-alpine-environment


fix: wrong order when columns prop changes

After modifying the columns, they appear at the end of the table instead of being displayed in the order provided.
export const CustomRowActionButtonsLastColumn = () => {
  const [columns, setColumns] = useState([
    { accessorKey: 'key2', header: 'header2' },
  ]);
  return (
    <MaterialReactTable
      columns={columns}
      data={[{ key2: 'value2' }]}
      enableRowActions
      positionActionsColumn="last"
      renderRowActions={() => (
        <Button
          onClick={() => {
            setColumns([
              { accessorKey: 'key1', header: 'header1' },
              { accessorKey: 'key2', header: 'header2' },
              { accessorKey: 'key3', header: 'header3' },
            ]);
          }}
        >
          action
        </Button>
      )}
    />
  );
};

I'm not sure this is a change I want to make. Usually it is up to each individual dev to manage their own column order if they want it to be derived from dynamic columns

I think it's a bit strange that the display order is different from the columns without providing order, the table components I've used, such as tanstack and antd, are generally sorted based on the provided columns. Meanwhile, maintaining the columnOrder requires taking into account the built-in columns, which can be a bit complicated.

I tested this more, but it introduced more bugs with display columns and manually managed columnOrder state. More would have to be done here.


Rest API to understand load on Azure SingalR service instance

Is your feature request related to a problem? Please describe.
I am trying to customize negotiate to balance requests to multiple Azure SignalR instances. This is for scaling. But Negotiate server has no visibility in to how loaded its Azure SingalR instances are. This visibility provides better load balance for redirection at Negotiate server.
Right now we are trying to some basic hash function based on UserID to partition the ASRs and it will not know the current load of a particular ASR instance.
Describe the solution you'd like
Please provide a rest API in to Azure Singnal R instances to emit current metrics like Connection count, Inbound/Outband Bandwidth, messageCount.. Also if you can aggregate these can quantify as capacity metric and emit certain % of capacity still left , that would be awesome. But I can understand  if second ask i.e. capacity metric is a strech goal.
.

We're going to expose metrics in ServiceEndpoint properties in the coming version, with ConnectionCount first, as Connection Count is a concurrent value while some others are accumulated values that need some further discussion.
So for short, you could use ServiceEndpoint.EndpointMetrics.ClientConnectionCount for customized routing use,  with upgrade to version 1.5.2. Please notice that there's dependency on our service side latest release which is in progress and should be done in 1-2 weeks.
Besides, for the current available metrics under resource Monitoring entry in Azure Portal, like MessageCount/ConnectionCount/Inbound&Outbound Traffic, you can leverage AzureMonitoring Rest API to get data, refer Here.


Basic publisher exemple with teensy36 stops aftern logger setup

Issue template

Hardware description:  Teensy 3.6 plugged to a Raspberry pi 4
RTOS:
Installation type:  basic installation
Version or commit hash: Humble

Steps to reproduce the issue
 platform.ini is modified for the use of a teensy 3.6
      then micro-ros_publisher is built and uploaded without errors.

Expected behavior
                                            ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0
                                            should display Running..Logger setup .......Datawriter created
                                             ros2 topic lists should display a new topic micro_ros_platformio_node_publisher...

Actual behavior
                                 When the Teensy is plugged with the Rapsberry pi 4
                                          The display stop after logger setup and nothing else happen

                                    When the Teensy is plugged with the portable computer
                                          The display stop after datawriter created that is looking good
                                           but
                                           ros2 topic list list no topic except the default
                                                            /parameter_events
                                                            /rosout

Additional information

There was an error on Teensy builds with serial transport, which was fixed on this PR: https://github.com/micro-ROS/micro_ros_platformio/pull/99
Please clean your project dependencies and give it another try.

Thanks for your help
I have tried with my old teensy 3.6 and my new teensy 4.0 and had the same result ??????

Closing as resolved.
For the record, its a good practice to modify your code to check the Agent connection before micro-ROS is initialized. More details on this tutorial: Reconnections and liveliness


Objects participating in === comparison fail to typecheck

Test case:
var obj;
if (obj.x == 1);  // error: Property cannot be accessed on possibly undefined value
if (obj.x === 1); // no error ?!

(running Flow 0.14.0)

See #698 :)

I believe this is a different issue: the problem is not in accessing possibly non-existent property (x), but in accessing it on a possibly undefined object (obj). The code as written will cause a runtime error, Flow better warn me about this :)

Yes indeed, sorry, my comment was not very comprehensible but I wanted to say that this is (a bug ?) caused by the refinement recently introduiced.

This bug seems to be fixed in v0.21:
examples/01-variables/01-variables.js:31
 31: if (obj.x == 1);  // error: Property cannot be accessed on possibly undefined value
         ^^^^^ property `x`. Property not found in possibly undefined value
 31: if (obj.x == 1);  // error: Property cannot be accessed on possibly undefined value
         ^^^ uninitialized variable

examples/01-variables/01-variables.js:32
 32: if (obj.x === 1); // no error ?!
         ^^^^^ property `x`. Property not found in possibly undefined value
 32: if (obj.x === 1); // no error ?!
         ^^^ uninitialized variable

examples/01-variables/01-variables.js:32
 32: if (obj.x === 1); // no error ?!
             ^ property `x`. Property not found in possibly undefined value
 32: if (obj.x === 1); // no error ?!
         ^^^ uninitialized variable

@pasha-mf gonna close this based on @raquo's comment, but please let me know if it's not fixed


Articulate Error: A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name

Hi,
After some years of running, today I’ve this error : A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique.
Parameter name: name
Umbraco 7.7.6 and Articulate 3.0.1
All site is down.
Stack trace:
[ArgumentException: A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name]    System.Web.Routing.RouteCollection.Add(String name, RouteBase item) +4254616    Articulate.ArticulateRoutes.MapMetaWeblogRoute(RouteCollection routes, String nodeRoutePath, IPublishedContent node) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\ArticulateRoutes.cs:208    Articulate.ArticulateRoutes.MapRoutes(RouteCollection routes, ContextualPublishedCache umbracoCache, UrlProvider umbracoUrlProvider) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\ArticulateRoutes.cs:67    Articulate.UmbracoEventHandler.ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\UmbracoEventHandler.cs:53    Umbraco.Core.ApplicationEventHandler.OnApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) +50    Umbraco.Core.CoreBootManager.b__38_0(IApplicationEventHandler x) +379    Umbraco.Core.EnumerableExtensions.ForEach(IEnumerable1 items, Action1 action) +167    Umbraco.Core.CoreBootManager.Complete(Action1 afterComplete) +416    Umbraco.Web.WebBootManager.Complete(Action1 afterComplete) +177    Umbraco.Core.UmbracoApplicationBase.StartApplication(Object sender, EventArgs e) +381  [HttpException (0x80004005): A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name]    System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +520    System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +176    System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +165    System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +267    System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +341  [HttpException (0x80004005): A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name]    System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +523    System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +107    System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +688

I cleaned the cache and ported the "blog" node under main site node because I don't want to assign an hostname to blog node.

Do you have any steps to replicate the issue? Have you tried using the latest 3.x version?

The issue happened after republish the entire blog. The blog has a lot of article. The blog node was at the same level with the "home" content node. Any main nodes has "hostname". So I solved:

delete umbraco xml file anche cache files
I assigned an hostname to main content node
I assigned an hostname to blog node, but for customer rule, I moved it under "home" node.

MAIN ISSUE: I lost tags and categories but the articles have them into backoffice.

Update: this happened after the customer move blog node.


website: implement rule list page

Rule list page: https://deeyasingh.github.io/rule.html
The rule view page effectively reads and interprets YAML files. The page utilizes JavaScript and the library js-yaml to parse these YAML files, transforming their content into a JavaScript object.
Each rule is then dynamically rendered into a visually appealing and easy-to-understand rule card, offering an encapsulated view of individual rule information directly to the user.

Cool, I think the features should be shown as raw yml text instead as a parsed JSON.

@mr-tz I've updated the features to be displayed in YAML format instead of parsed JSON. Could you take a look and let me know if this looks better?

Perfect, that looks great.


Transition notes: Add link on home page, and page to review all notes

Who is this PR for?
8th and 9th grade counselors
What problem does this PR fix?
Helping review which students still need transition notes, scan for students starred for in-person discussion.
Screenshot (if adding a client-side feature)

Checklists
Which features or pages does this PR touch?

[x] Home page
[x] Transitions

Does this PR use tests to help verify we can deploy these changes quickly and confidently?

[x] Included specs for changes
[x] Improved specs for existing code in need of better test coverage
[x] Manual testing made more sense here

selfie


[9.x] Fix failing SQL Server integration tests

Replaces https://github.com/laravel/framework/pull/41984

Avoid the other PR's approach where test setup depends on calling Schema::getAllTables() / SqlServerBuilder::getAllTables() since these are the methods the integration tests are covering.
Simplify the test cases (that copied DatabaseSqliteSchemaBuilderTest / DatabaseMySqlSchemaBuilderAlterTableWithEnumTest) which were cramming 2 or 3 different cases into each test method.
DB::connection('sqlsrv') / Schema::connection('sqlsrv') don't need explicit calls as this is already the default database connection when any test class extending SqlServerTestCase is run.

Thanks!

fair enough,  thanks @derekmd


Fixed the expected device info for MI50/MI60/MI100/MI200.

@jayfurmanek Also let me know if there are other branches that we want to add this.


IPC service support

In the 14a29e566f1f328bbe947f04c9bb29ff42b12a70 commit, resolve the conflicts by discarding nrf53_sync_rtc changes which are not present yet in downstream.

@kapi-no [nrf fromlist] commits should always have a reference to their upstream counterparts.
Also note that https://github.com/zephyrproject-rtos/zephyr/pull/43412 has been merged and can thus be changed into a [nrf fromtree] instead.


calling tHMM needs to be in the try statement

small fix, the tHMM init function calls functions that are part of fitting. I didn't catch this in the previous changes.

Hello @shak360! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file lineage/Analyze.py:

Line 30:80: E501 line too long (81 > 79 characters)


[NPM Lite] Fix for NPM Lite Yaml File

Reason for Change:

Fixes a syntax error in npm lite yaml file
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

/azp run


Configuration of the toolbar(s)

Hi,
Thank you for your work.
I just tried to run it on our symfony project and it seems to work fine, but I was trying to find a way to configure it like CKEditor (trying to find an alternative to it), where there's a yaml file containing an array of the buttons you want to have in your toolbars, and you can have as many different toolbars as you want, like this :
my_toolbar_advanced: [["Bold", "Italic", "Underline", "TextColor", "BGColor", "RemoveFormat", "-", "Undo", "Redo", "-", "Table", "NumberedList", "BulletedList", "-", "Outdent", "Indent", "-", "Maximize"]]
my_toolbar_basic: [ [ "Bold", "Italic", "RemoveFormat", "-", "Maximize" ]]
my_toolbar_empty: [["Maximize"]]

I tried to look in the readme and the quill doc but I don't think I found the file in question (or I missed it).
In the meantime I created my own type that implements your QuillGroupInterface and have a method for each toolbar I want to implement, seems to be the closest to what I'm talking about, but if there's a simpler way, I'm open to it.
Have a good day.

Hello, thanks for using this bundle !
Sorry, but there is indeed no way at the moment (maybe a future feature if the community find it useful and necessary) to preconfigure a toolbar in a yaml format.
The best way to do this is indeed to create a FormType (or multiple FormTypes) and preconfigure it.
I didn't find it necessary to have an external file (like a yaml) to configure toolbars as I think it is very easy to create a formType that can be reused and configured to have multiple toolbars.

Alright, thanks for the answer. I'll close the issue then.


no redirect before user login

See #3392 Detailed description
Quick briefing: When a user not login, www.hydroshare.org should not redirect to www.hydroshare.org/landingPage. The url should not change.

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]

@Lizabrazil has approved the solution. I need an approval to this PR.


js files are being linted with both eslint and jshint

We recently implemented eslint into some of our projects and we want these projects to be linted only with eslint. .lintrc files were updated there, jshint was replaced with eslint, however,  jshint still reviews those projects and posts reviews along with eslint, is there some misconfiguration on our side or we have to get rid from jshint entirely?
Any reply is much appreciated.

Do you have jshint enabled in the default linters by chance?

LINTRC_DEFAULTS  here?

Yes. If LINTRC_DEFAULTS enables jshint, it will be applied to all projects your lintreview runs on.

we only have tool_  prefixed  sections there for tools, config file for jshint is there, but there is no [tools] section

Actually removing [tool_jshint]  section helped, jshint doesn't run now on  projects where  it's not specified in .lintrc. But this means that we have to set config path in each project individually.
Is this expected behaviour?

But this means that we have to set config path in each project individually.
Is this expected behaviour?

Yes. Each project will need to configure the tools it uses.

Closing as this was a configuration issue.

Thanks for quick response


timeout setting CURLOPT_TIMEOUT_MS

Currently it looks like the timeout parameter has two options:

single integer to set CURLOPT_TIMEOUT_MS
tuple of (connect timeout to set CURLOPT_CONNECTTIMEOUT_MS, and a value that is added to the connect timeout to set CURLOPT_TIMEOUT_MS)

The parameter is defined as:

how many seconds to wait before giving up.

I would think timeout in this context is to deal with network and server issues (i.e., the connect phase taking to long or the server not responding with any data for an http request in time).
https://github.com/yifeikong/curl_cffi/blob/d0c6c9c08ecf4ab6a1a9e0bd7ea6ff80e562385b/curl_cffi/requests/session.py#L304-L311
I'm opening this as I'm not sure if setting CURLOPT_TIMEOUT_MS is the best action - or at least forcing it when wanting to set a connect timeout.
What CURLOPT_TIMEOUT_MS appears to do is timeout the entire request and transfer, even if data is successfully being received from the server. This is particularly noticeable when using streaming, as you can be processing data coming in and it throws a timeout error just because the transfer is taking too long?

https://curl.se/libcurl/c/CURLOPT_TIMEOUT.html

Perhaps it may be better to set CURLOPT_CONNECTTIMEOUT_MS (and maybe  CURLOPT_SERVER_RESPONSE_TIMEOUT if its not a general transfer timeout?)  by default instead? I'll need to double check this, but I believe that is similar behavior to what libraries such as requests do.
Alternatively, could there be a way of setting the above two while not setting  CURLOPT_TIMEOUT_MS with the timeout option?
Versions

OS: linux 64bit
curl_cffi version 0.5.10b4

Additional context
Which session are you using? async or sync? Which loop implementation are you using
sync

I see. You are right, it should be read_timeout instead of overall_timeout, which would also be consistent with requests' behavior.

One caveat of CURLOPT_SERVER_RESPONSE_TIMEOUT is that it can only be set in seconds, not milliseconds.

I tried to use CURLOPT_SERVER_RESPONSE_TIMEOUT and it's not working. It turns out that this option is for FTP and not HTTP, thus not useful here.

Darn. In that case I'm not sure if curl has an equivalent read timeout :pensive:
I suppose what you have done here is fine
I did find this workaround: https://unix.stackexchange.com/a/305311

I started a thread in the curl mail list, it seems that they do not intend to implement it.

Interesting, thanks for linking.
I take note of this reply from one of the devs:

For HTTP we already provide:

CURLOPT_CONNECTTIMEOUT
CURLOPT_TIMEOUT
CURLOPT_LOW_SPEED_LIMIT + CURLOPT_LOW_SPEED_TIME

I think the latter here, which I believe is also what the stackoverflow comment suggests, is perhaps what we want for a read timeout similar to requests? Seems like that might be intended, though slightly annoying it's not super obvious.
From https://requests.readthedocs.io/en/latest/user/advanced/#timeouts:

Once your client has connected to the server and sent the HTTP request, the read timeout is the number of seconds the client will wait for the server to send a response. (Specifically, it’s the number of seconds that the client will wait between bytes sent from the server. In 99.9% of cases, this is the time before the server sends the first byte).'

So perhaps set CURLOPT_LOW_SPEED_LIMIT to 1 byte/s or something really low, then the timeout value can set CURLOPT_LOW_SPEED_TIME?
Though, it doesn't support ms values..

Works better now, thanks!. I've set CURLOPT_LOW_SPEED_LIMIT and  CURLOPT_LOW_SPEED_TIME my end and that seems to work well for a read timeout too.


[REEF-894] GetBridgeInjector should not create a new Injector

This addressed the issue by

Make BridgeInjector and BridgeConfiguration static lazy.

JIRA:
REEF-894

It would appear that some tests are unstable with this PR, I'll take a closer look...

Can the reviewer pull and run tests on Local? I don't believe my changes should affect the tests that are run in the Jenkins environment. Thanks!

@afchung , I tested and it passed, too.

Thanks @dongjoon-hyun!


Forced reflow triggered on page first load

Vue version
3.2.47
Link to minimal reproduction
https://github.com/mathias22osterhagen22/force-reflow
Steps to reproduce

npm install
npm run dev
F12 open the console
Hit F5 multiple times till the message appears in the console: [Violation] Forced reflow while executing JavaScript took xxx ms (make sure to check all messages)

What is expected?
No [Violation] Forced reflow while executing JavaScript took xxx ms message
What is actually happening?
Get a [Violation] Forced reflow while executing JavaScript took xxx ms message in the console
System Info
Reproduction:

  System:
    OS: Windows 10 10.0.22000
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 10.45 GB / 31.71 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.18 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (112.0.1722.64)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    vue: ^3.2.47 => 3.3.4

Prod:
  System:
    OS: Windows 10 10.0.22000
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 10.22 GB / 31.71 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.18 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (112.0.1722.64)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    vue: ^3.2.47 => 3.2.47

Any additional comments?
Sometimes it doesn't happen on the reproduction but I have it systematically on the production project.
I don't know if it could be linked but I know that on the reproduction project I can trigger the warning message more often by enabling the Wappalyzer extension.
I tested with all extension disabled on production and and still gets the warning violation message.

I'm sorry, but I'm not sure what you are expecting us to do here.
The warning isn't Vue specific, nor does reproduction show that it is caused by something that should be "fixed" in Vue core. If rendering a huge table causes a reflow, it could theoretically trigger the same warning without Vue involved. I don't see there's anything actionable here.


Clean up build warnings for CFE 6.6

There are several warnings that appear in a build of the current development branch that should be cleaned up prior to the 6.6 release.
For instance:
{{{
fsw/cfe-core/src/es/cfe_es_api.c: In function ‘CFE_ES_GetAppID’:
fsw/cfe-core/src/es/cfe_es_api.c:748:11: warning: unused variable ‘TaskId’ [-Wunused-variable]
uint32 TaskId;
}}}
There is also a cmake warning in new versions of the tool (v3.5+ which is in Ubuntu 16.04) and another const-ness warning regarding CFE_TBL_DumpToFile that shows up with -Wwrite-strings enabled.

Imported from trac issue 202.  Created by jphickey on 2017-09-07T09:33:31, last modified: 2019-03-05T14:58:28

Trac comment by jphickey on 2017-09-07 10:25:27:
Pushed commit [changeset:5344db9] branch trac-202-cleanup-warnings
With this change in place my build is warning-free using cmake 3.5.1 and gcc 5.4.0 on Ubuntu 16.04, at least for the CFE stuff (apps and tools still have their own warnings)
(NOTE: rebased to current development branch as of 2017-09-13, and included in the ic-2017-09-13 test build)

Trac comment by glimes on 2017-09-15 11:39:35:
Recommend approval.

Trac comment by sstrege on 2017-09-13 17:02:00:
Recommend/approve

Trac comment by sstrege on 2017-10-20 12:17:41:
The following commits address the CCB approved solutions above:

cfe_es_start.c:417 – in CFE_ES_SetupResetVariables function remove “status =” from all calls to CFE_ES_WriteToERLog [changeset:18c3d0a]

cfe_es_apps.c:659 – in CFE_ES_AppCreate function, add return code check after call to OS_remove(RamDiskPath), if error then WriteToSysLog [changeset:769e198]

cfe_es_apps.c:890 - in CFE_ES_LoadLibrary function, add return code check after call to OS_remove(RamDiskPath), if error then WriteToSysLog [changeset:8157f47]

cfe_es_api.c:393 - Address CFE_ES_ResetCFE return by adding WriteToSysLog even if SUCCESS and log the return code, follow this by an explicit return  [changeset:5fba9c7]

cfe_es_api.c:1925 - CFE_ES_ProcessCoreException function, remove “Status =” from call to CFE_ES_RestartApp. In CFE_ES_RestartApp function, line 246 else case where “App ID is not valid” add WriteToSysLog [changeset:49aa9f9]

cfe_es_api.c:761 - CFE_ES_GetAppID function, remove “Result” variable initialization [changeset:c099fc6]

Trac comment by sstrege on 2017-10-19 14:06:06:
The following CCB approved solutions address the cppcheck failures reviewed during the 9/26/17 CCB meeting:
Variable is assigned a value that is never used.  Explicitly add cast to void? This will identify the functions that have un-meaningful returns. Adding “if(Status) do nothing;” will hide the warning. Agreement the best solution will be to remove the un-meaningful returns. Confirmed cppcheck to look for ignored returns is disabled. Enabling this check for future release will help identify the functions (recourse for having a return status) vs. procedures (no recourse for having a return status) and initiate a scrub to update the functions that should be procedures.

cfe_es_start.c:417 – in CFE_ES_SetupResetVariables function remove “status =” from all calls to CFE_ES_WriteToERLog
cfe_es_apps.c:659 – in CFE_ES_AppCreate function, add return code check after call to OS_remove(RamDiskPath), if error then WriteToSysLog
cfe_es_apps.c:890 - in CFE_ES_LoadLibrary function, add return code check after call to OS_remove(RamDiskPath), if error then WriteToSysLog
cfe_es_api.c:393 – call to CFE_ES_ResetCFE function should never return in flight, it will return in unit test. Address return by adding WriteToSysLog even if SUCCESS and log the return code, follow this by an explicit return
cfe_es_api.c:1925 - CFE_ES_ProcessCoreException function, remove “Status =” from call to CFE_ES_RestartApp. In CFE_ES_RestartApp function, line 246 else case where “App ID is not valid” add WriteToSysLog

Performance: Variable is reassigned a value before the old one has been used:

cfe_es_api.c:761 - CFE_ES_GetAppID function, remove “Result” variable initialization

Trac comment by glimes on 2017-10-20 12:51:42:
I recommend approval of all six commits.

Trac comment by glimes on 2017-10-24 15:50:04:
commit [changeset:252ed2a] integrated to development.

Trac comment by glimes on 2017-10-22 10:58:42:
Updating branch per CCB meeting to reflect the trivial change
to the CFE_ES_ExitApp() function. Commit ID numbers changed:
Commit [changeset:5fba9c7] becomes [changeset:08add53] as the content is modified.
Commit [changeset:49aa9f9] becomes [changeset:252ed2a] as it was a descendent of the commit above.
Preparing an integration candidate using the revised commits above.

Trac comment by jhageman on 2019-03-05 14:58:28:
Milestone renamed


Squiggles and arrows

Codecov Report

Merging #67 into master will decrease coverage by 1.46%.
The diff coverage is 68.62%.

@@            Coverage Diff            @@
##           master     #67      +/-   ##
=========================================
- Coverage   84.06%   82.6%   -1.47%
=========================================
  Files          28      29       +1
  Lines        1293    1368      +75
  Branches      173     211      +38
=========================================
+ Hits         1087    1130      +43
- Misses        206     238      +32

Impacted Files
Coverage Δ

src/component/chart/ContactMapChart.tsx
100% <ø> (ø)
:arrow_up:

src/component/ContactMap.tsx
82.2% <ø> (ø)
:arrow_up:

src/component/VizSelectorPanel.tsx
100% <100%> (ø)
:arrow_up:

src/helper/DataHelper.ts
100% <100%> (ø)
:arrow_up:

src/ChellVizApp.tsx
100% <100%> (ø)
:arrow_up:

src/data/chell-data.ts
100% <100%> (ø)
:arrow_up:

src/component/chart/PlotlyChart.tsx
97.63% <100%> (+0.01%)
:arrow_up:

src/component/NGLComponent.tsx
100% <100%> (ø)
:arrow_up:

src/component/InfoPanel.tsx
39.13% <39.13%> (ø)

src/data/ChellPDB.ts
37.5% <50%> (+0.32%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Toolbars load cleanup

cache loaded toolbar definitions
limit and cleanup calls to eval for toolbar properties

LGTM, better than before :+1: (though the evals are still a bit too eval-y :)).


Improve the Collection admin

closes #99

Add help text to all fields
Set fields as read-only where appropriate
Add a reminder to provide information in all languages
Add a filter to easily find collections with missing information
Use fieldsets instead of overriding django-modeltranslation internals

Other changes:

Make the Collection.language translatable
Force the active job to be edited via the Collection admin
Remove null=True for CharField and MarkdownxField, so that blank fields are "", not either "" or None
Add verbose_name to models and fields

@jakubkrafka I can't get the app running locally (please can you provide instructions?), so I'm not able to create the database migration.
I also want to hide Issues and Tasks from the admin menu, such that they are only editable as inlines from Collection and Job. I'm not sure if I can just delete admin.site.register or if another solution is needed. Leaving them in the menu is just confusing, because you never want to edit them in isolation.

Its hard to help, when I don't know the exact issue/problem. In general, its regular Django app, nothing special. All configurations parameters are in environment variables. This is taken from my VisualCode launch.json:
{
	"name": "Webserver",
	"type": "python",
	"request": "launch",
	"program": "${workspaceFolder}/manage.py",
	"args": [
		"runserver",
		"8000",
		"--settings=core.settings.docker"
	],
	"envFile": "${workspaceFolder}/.env",
	"django": true,
},

and should be equivalent to
python manage.py runserver 8000 --settings=core.settings.docker
```.

There is blank env file data-registyry.env in the repo. For the webappp, you should only need the db:

DB_NAME=name
DB_USER=user
DB_PASSWORD=password
DB_HOST=<IP_ADDRESS>
DB_PORT=5432

This PR adds a README.md with the minimum steps for development.


Solution for Smaller Unit Development (Lazy Compile Per Module or isolated app - but without the cost of micro front-end)

🚀 Feature request
Command (mark with an x)

[ ] new
[ ] build
[ x] serve
[ ] test
[ ] e2e
[x ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
A very large Angular App can take several minutes to compile, when only a Unit Module or Feature is needed for development. (E.g. Imagine Compiling all of Angular Material Components when only 1 material component module needs development.)
There have been proposed solutions that allow faster compile/development such as Micro Front Ends (Where a large app is broken into smaller embedded apps in the view). Although it is very wrong performance wise to have multiple angular apps in 1 view. (e.g. why bootstrap angular 5 times if the web app view used 5 micro front ends?)
https://speakerdeck.com/naltatis/bye-bye-frontend-monolith-accelerating-feature-development-with-micro-frontends?slide=36
Describe the solution you'd like
Allow developers to ng serve a spec file (single / module scoped) for development (in compile isolation to the rest of the app - the server can be reached via browser to view development results). A spec file should contain mock data needed to bootstrap itself to a micro app for development.
Below are 2 approches:
A: Unit Testing UI but for Development with Lazy Compile
I would like a feature where the angular cli has a navigatable UI environment (like how karama test runner opens the browser)
and allows us to choose Unit Testable modules for development work. Only the module selected is lazy compiled and it is fast to get up and running with development.
B: ng serve command per module
ng serve moduleName
The command can open a micro-app for unit development and faster compilation.

Angular is considered to be quite heavy that it is suggested to try other frameworks when using the micro front end pattern:
https://speakerdeck.com/naltatis/bye-bye-frontend-monolith-accelerating-feature-development-with-micro-frontends?slide=59
If a dev team decides to convert lazy route navigation into micro front ends as well, it really feels like we loose the benefit of a SPA if each new route has to get a new html document and bootstrap all over again, instead of updating the DOM quickly (if user goes back and forth multiple times)
We should seek to isolate in dev apps during development but still ship a single app that gives us the performance and speed of a SPA.
Describe alternatives you've considered
 Have you considered any alternative solutions or workarounds?

Have you looked at https://storybook.js.org? I think this may provide a part of what you are looking for.

@petebacondarwin Thank you for the reply. Yes Storybook seems really great for documenting and developing.
Although it still compiles the full app. (In case of a large codebase with 500+ components) I've found others try to use webpack loaders to lazy compile storybook as well.
https://github.com/liximomo/lazy-compile-webpack-plugin/issues/13
To be more specific for my case, I work in an Nx workspace where I have libs/vendor folder with many (1 component only) modules to be imported in the main app.
I suppose, I'm hoping the feature would be a webpack config that can make lazy AngularModule compiling work seamlessly with Storybook or Nx.
ng add storybook (has lazy compile) or nx serve moduleName
I really hope you put this request into consideration.


Supporting earlier versions of Dart SDK

In order to make this repository more accessible for older projects, can we also maintain 0.1.x versions (which depends Dart SDK >=2.8) for some time in a separate branch and release new features for 0.1.x also?

I don't really have the time to maintain another branch, but if you're willing to do so. Then I'll take you up on the offer 👍

Sure, let's do it

Which commit do you want as a starting point?

I added the changes on top of 288c726bd712186996cb24daf7d600c5db8eadff

You can now target your PR at https://github.com/ueman/unleash/tree/v0.1

I'll release a new v0.1.x version today 👍


Optionally trim attribute keys & values?

Related to https://github.com/open-telemetry/opentelemetry-specification/issues/504
Java provides optional attribute value truncation: https://github.com/open-telemetry/opentelemetry-java/blob/a021a59b9433691c06ab2265b4c574eab825b0ed/sdk/tracing/src/main/java/io/opentelemetry/sdk/trace/SpanBuilderSdk.java#L195-L197
    if (traceConfig.shouldTruncateStringAttributeValues()) {
      value = StringUtils.truncateToSize(value, traceConfig.getMaxLengthOfAttributeValues());
    }

We have some ad-hoc truncation and UTF8 validation in the Redis instrumentation, for example: https://github.com/open-telemetry/opentelemetry-ruby/blob/1a680bbd489eee18cdf78b24a99e3cc0333c41e5/instrumentation/redis/lib/opentelemetry/instrumentation/redis/utils.rb#L60-L80
It is likely worth extracting this into a common utility module, and implementing attribute truncation in a single place with a configurable limit (most likely in the SDK Span class).

I believe this issue has been addressed. Should we close or is there more to do here?

I think #1136 is relevant here.


SWDEV-403382 - Add Semaphore structs for graph node

Signed-off-by: sdashmiz<EMAIL_ADDRESS>Change-Id: I5c4a8b55c16ca5bf4ffbf003519e75b63524c0c1

Duplicate of #3261. Closing this.


[FEATURE]: CSS-variable for font-family

Now is hardcoded. Have to use crutch:
[aria-label][data-cooltipz-dir]::after, [aria-label][class*=cooltipz]::after {
  font-family: $font-family-base;
}

Will investigate this customisation as I can see it conflicting with FontAwesome config.
Please stick to the issue template provided, it helps prioritise tasks.

Released in v2.1.0


Update structure marshaling guidance for .NET Core 3.0

Contributes to #11396
Continued from #12101

dotnet/coreclr#22041 fixed marshaling explicit-layout structures on non-Windows platforms.

/cc @jkoritzinsky

@mairaw The code owner @jkoritzinsky is not requested for review. #15355

@mairaw
@jkoritzinsky is not identified as the code owner. #15355

https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners

The people you choose as code owners must have write permissions for the repository.

I'm not sure if he has write permissions in dotnet/docs repo, but if he doesn't have write permissions then that is the problem.

I'm not sure if he has write permissions

The approval marks of those who have write access are green.

I'm not sure if he has write permissions

The approval marks of those who have write access are green.

Well, then this is the problem.

We're revisiting all the assignments, code owners, perms, etc. I'm still in the process of doing this after Ron left but I can review and approve this in the meantime given that @jkoritzinsky already approved this.


feat(react-refresh): update function that usses react-refresh

Very short PR:

added an update function to the IRenderable interface
implemented update with RefreshRuntime.performReactRefresh() as the react version for it

I think this should not happen via codux-core. It is specific to codux's way of wanting to edit code with live refresh.
The update() fn itself is useless without a transformer adding and wrapping code.
Unrelated: we add devDependencies in the root of mono-repos. Not the packages themselves.


Users/anjanich/tg1

Added documentation for Task Group as PREVIEW.

@chandan-anjani,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Request: Button/link to go to latest signal

When in historical state, if you try to fire any new signals you will receive the error:
Cerebral - Looking in the past, ignored signal yourSignal

Which makes total sense. However, if you wish to continue, the only way to do so is to mash the forward button (or reset the state entirely). This can be quite tedious, so I propose a new button or link in the debugger that goes back to the latest signal.

Makes perfect sense :-) will bring on next version!

Okay, in now, will be part of next release


Write page for cloud.gov on M-21-31 compliance (due 8/27)

In order to inform customers about how we address M-21-31, we want to write up public documentation that outlines how we meet, or intend to meet, the outlined requirements.
Acceptance Criteria

[ ] GIVEN a requirement listed in M-21-31
WHEN a user looks for information on this requirement
THEN documentation exists on how we meet or intend to meet this requirement

Security considerations
This will outline several security and compliance changes to meet requirements
Implementation sketch
[links to background notes, sketches, and/or relevant documentation

[ ] Create public documentation page
[ ] Conduct research and write up documentation for each requirement

This is the WIP PR: https://github.com/cloud-gov/cg-site/pull/2165

This is live: https://cloud.gov/docs/compliance/logging-requirements/


⚠ Bofrost.lu has degraded performance

In cd77b49, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2397 ms

Resolved: Bofrost.lu performance has improved in 00a942e after 13 minutes.