[release-1.6]Cherry-pick: remove cacert.pem and use x509.SystemCertPool()

[release-1.6]Cherry-pick: remove cacert.pem and use x509.SystemCertPool()
(this pr)[https://github.com/istio/istio/pull/27657] is merged in master
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@xulingqing: PR needs rebase.

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.

@xulingqing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-pilot-k8s-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test analyze-tests_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test analyze-tests_istio

release-test_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-test_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test analyze-tests_istio

release-test_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-test_istio

lint_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test lint_istio

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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-notes_istio

integ-operator-controller-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test unit-tests_istio

integ-security-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test analyze-tests_istio

release-test_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test release-test_istio

lint_istio
25dec51b5e24f17ea4739d6c98e63d34869577ae
link
/test lint_istio

integ-mixer-k8s-tests_istio_release-1.6
693837145cf07cf002099b508606f5d592f78604
link
/test integ-mixer-k8s-tests_istio_release-1.6

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.

@istio/release-managers-1-6 Could you take a look at the PR? Thanks!


Please consider add Windows Command Prompt default support in "terminal.integrated.defaultProfile.windows": "Command Prompt"

Dear developer, this is a really nice vscode extension and I love it.
However, there is a little flaw for the windows command prompt terminal.
every time I press F5 and it can not open the ipython correctly.
(I have read your guidance and try to install another Git for Windows to enable the Git Bash, and it worked.)
(And I think this will make a barrier for more windows users who don't use Git Bash often.)
I have a quick temporary solution that I made a bat file which name is i.bat to correct the string format in windows cmd.exe.
Here is the quick i.bat file:

ipython --no-autoindent --InteractiveShellApp.exec_lines="%%load_ext autoreload" --InteractiveShellApp.exec_lines="%%autoreload 2"
With this solution, I just press another "i" and enter, the extension is working perfectly.
the solution contains 2 key points:

Use " instead of ' in windows command prompt.
Use double % mark to output a correct % mark in the string that embraced by " ".

Please consider add this solution to your source file, thank you!

Thank you for the suggestion. I'll look into it 🙏

@psyrocloud, happy New Year!
Just publish an update that should resolve this issue.  It should enable you to use PowerShell and/or CMD terminals.  Let me know if this works for you.  Thanks!


React Project - A Dynamic Calculator

assign me

assign me

Make sure you star our Repository.
You should complete the task within 10 hours
You should provide documentation for this task , which include everything Regarding this task.

Please assign me this task

@Codetoadeath  is  I have to create same UI

could you assign me this task @Codetoadeath

@therefat do I need to create a new repo dynamic calculator for this ?
please let me know asap

Assign me @Codetoadeath  , I'll complete real fast than these assignees.

Assign me @Codetoadeath , I'll complete real fast than these assignees.

Sure . Please complete asap


Rage Nerf - Remove Bluespace Crystal craft from protolathe

About the PR
Remove Bluespace Crystal craft from protolathe. Now it's rare ore only.
Why / Balance

Bluespace crystal entirely ruining economy (one crystal costs 3000 credits when components costs less than 50 credits)
Craft 30 bluespace crystals - get 30 scram implants without cooldown.

:cl:

remove: Removed bluespace crystal craft from protolathe.

We gamble no more 😔


fix(circom): Change version and remove tests

Unfortunately, we need to work with specific circom commit.
Because even with a patch applied the build for circom-pairing still fails
Explanation: https://github.com/yi-sun/circom-pairing/issues/11#issuecomment-1211069201


ADBDEV-5228-flag: New default-buffer-size option

The cat command from Centos 7 coreutils 8.22 uses a buffer size equal to the maximum of 64 kilobytes and the file system block size, which can be found with the following command
stat -fc %s .

Newer versions of the cat command use 128 or even 256 kilobytes. Moreover, in the latest versions this is not just a maximum, but a much more complex algorithm.
At the same time, gpbackup for read and write uses the buffer size from the bufio package, which is 4 kilobytes by default.
Therefore, this patch makes a new option default-buffer-size, when set, gpbackup will use the specified buffer size instead of the default 4 kilobytes.

New default-buffer-size option
The cat command from Centos 7 coreutils 8.22 uses a buffer size equal to the
maximum of 64 kilobytes and the file system block size, which can be found with
the following command stat -fc %s .
Newer versions of the cat command use 128 or even 256 kilobytes. Moreover, in
the latest versions this is not just a maximum, but a much more complex
algorithm.
At the same time, gpbackup for read and write uses the buffer size from the
bufio package, which is 4 kilobytes by default.
Therefore, this patch makes a new option default-buffer-size, when set, gpbackup
will use the specified buffer size instead of the default 4 kilobytes.


Make preflight more robust when cleaning up

Bug Description
Preflight needs to be more robust when it comes to cleaning up after itself, especially in the cluster arena.
For instance, DeployableByOLM attempts to clean up, but does not check that it does so. It also may not handle a transient API error.
So, for this particular bug, a focus on DeployableByOLM should be the first place. If other locations in the code are identified for cleaning up, we should file another bug for that.

this effort also needs to review whether or not we clean up CSVs on tear down. I'm thinking we may be leaving CSVs behind.

Closing this issue due to no activity, please open a new issue if needed.


Android StopRecording fails if scene with VideoKitRecorder in get's unloaded and reloaded.

I have Scene with a VideoKitRecorder gameobject in it (see screenshot).
The first time I run and load this scene on Android it works fine, and saves the recording correctly.
Note, the VideoKitRecorder gameobject is disabled by default, and I call SetActive(true) on it with a small delay so I can control when the prepareRecorder logic starts running, as it stalls the scene for a sec or two.

Hey @supermoos can you try disabling the Prepare on Awake boolean then trying again? Let me know if the issue persists.

What device and OS version are you recording on? Can you share the full logs from app start in a .txt attachment? Make sure to capture all logs (no filtering).

This looks to be device-specific at first glance.

Disabling prepare on wake worked at least one time now. Here's the log with prepare on wake enabled.
log.txt

log_no_prepare_on_wake.log
Here's one that failed even though prepare on awake was not checked.

What device and OS version is this? This issue is device-specific:
Warn CCodec previous call to queue exceeded timeout
Error MediaCodec Codec reported err 0x80000000, actionCode 0, while in state 6

One last thing to try is to record at 1280x720 and see if that helps.

Try out 1280x720 and let me know if that has the same behaviour.

1280x720_prepare_on_wake.log
It works when prepare on wake is not checked, however when it is checked it only works the first time the scene is loaded, if I unload it, and load it again the above log errors appear.

This is an device-specific bug. From the logs:
Warn CCodec previous call to queue exceeded timeout

Then everything from there fails and the errors cascade. We have to improve error handling so that the logs don't get spammed with IllegalStateException, but that isn't the actual issue here. I'm closing this issue.

Minor note on this: NatCorder doesn't actually have a timeout for how long it's willing to wait for the encoder. We ask to wait infinitely until the encoder is ready to give us a buffer to use.

Okay, well is there some workaround maybe? It's also an issue on another device I tested on (pixel3a, android 10, api 29).
Log attached.
pixel3a.txt

Just did another test on a Lenovo YT-J706f android 11 api 30 - it also throws a bunch of errors and outputs a completely black video.
lenovo_yt_j706f_android_11_api_30.txt

The second time I try a recording on the Lenovo it works.

And here's another failed test on a Pixel 4A, Android 13, SDK 33.
pixel4a_android13_sdk_33.txt

It works fine on a Pixel 7. However that's a lot of devices that don't work / work very flaky - I'm not entiely sure I would write it off as a device issue without at least providing better error handling, perhaps including some fallback configurations that could be retried. My understanding was that MP4 recording and api level 24+ was suppose to be the only minimum requirements for it to work? But maybe I'm missing something? :-)

Okay, well is there some workaround maybe? It's also an issue on another device I tested on (pixel3a, android 10, api 29).
Log attached.

Same error:
Warn CCodec previous call to queue exceeded timeout
Error MediaCodec Codec reported err 0x80000000, actionCode 0, while in state 6

Just did another test on a Lenovo YT-J706f android 11 api 30 - it also throws a bunch of errors and outputs a completely black video.

Info MPEG4Writer setStartTimestampUs: 105257
Info MPEG4Writer Earliest track starting time: 105257
Warn MPEG4Writer Condition timestampUs >= 0LL failed for Video track
Error MPEG4Writer Dumping Video track's last 1 frames' timestamps(pts, dts) and frame type :
Error MPEG4Writer (0us, 0us Key frame)

This seems to be complaining about negative timestamps, but that can't be the case since timestamps generated for recording are guaranteed to be monotonic. The only potential issue, which is also extremely unlikely, is if pixel buffers are being committed out of order. One way to test this is to set your app to render with OpenGL ES3 in Player Settings, then add the following code before you start recording:
NatML.Recorders.TextureInput.UseGLESTextureInput = false;

And here's another failed test on a Pixel 4A, Android 13, SDK 33.

Same as the other Pixel errors:
Warn CCodec [c2.qti.avc.encoder] previous call to queue exceeded timeout
Error MediaCodec Codec reported err 0x80000000/UNKNOWN_ERROR, actionCode 0, while in state 6/STARTED

I can't help but notice that for the 4-5 seconds where you record, there are no logs being generated:
2023/05/03 **10:01:38.048** 9589 14287 Info MPEG4Writer Earliest track starting time: 0
2023/05/03 **10:01:42.452** 9589 9617 Info Unity Stop recording

Are you filtering logs? If so, please refrain from doing that cos I need to see everything.

I haven't configured any filtering. The logs are from the Unity Android Logcat window. The filtering is set to verbose?
I just ran another test on pixel 7 and this time it started throwing errors and produced a fully black video.
Logs attached.
pixel7_error.txt

Same error as the Lenovo:
Info MPEG4Writer setStartTimestampUs: 5126
Info MPEG4Writer Earliest track starting time: 5126
Warn MPEG4Writer Condition timestampUs >= 0LL failed for Video track
Error MPEG4Writer Dumping Video track's last 1 frames' timestamps(pts, dts) and frame type :
Error MPEG4Writer (0us, 0us Key frame)

Did you try out what I mentioned above?

Do you mean like the screenshot?
I'm getting a compile error with the code snippet you provided:
Assets/game_doodles/Scripts/GameManager.cs(133,13): error CS0234: The type or namespace name 'TextureInput' does not exist in the namespace 'NatML.Recorders' (are you missing an assembly reference?)

Let me know if it's easier to jump in discord on a call or something.

Oops, missed a namespace:
NatML.Recorders.Inputs.TextureInput.UseGLESTextureInput = false;

Yes that seems to work on the pixel 7 at least the two times I've tested now.
Here's the log. However I'm not. sur eof the implication of switching th
pixel7_es3.txt
e graphics API for my app. Shouldn't it work without this non-default setup too?

The pixel 4a worked on the first run, second run failed.
pixel4a_second_run_error_es3.txt

Yes that seems to work on the pixel 7 at least the two times I've tested now.
Here's the log. However I'm not. sur eof the implication of switching the graphics API for my app. Shouldn't it work without this non-default setup too?

This means that the pixel readback buffers are likely out of order. Your app was rendering with Vulkan before, which means that it's a bug from Unity's implementation of AsyncGPUReadback. The readbacks don't seem to be coming back in the same order as they were requested.

The pixel 4 still doesn't work however.

Same error:
Warn CCodec previous call to queue exceeded timeout
Error MediaCodec Codec reported err 0x80000000, actionCode 0, while in state 6

The pixel 4a worked on the first run, second run failed.

Same error:
Warn CCodec [c2.qti.avc.encoder] previous call to queue exceeded timeout
Error MediaCodec Codec reported err 0x80000000/UNKNOWN_ERROR, actionCode 0, while in state 6/STARTED

TL;DR: For the Pixel 4s, it's device-specific. And for the Pixel 7 and Lenovo, it's a Unity bug.

Okay, is it something you're planning to add work arounds for, since effectively you're solution (we have a subscription for) is not working on a whole bunch of Android devices? Happy to help out in any way I can with debugging.

Okay, is it something you're planning to add work arounds for.

We might be able to add a workaround for the timestamp issue on the Pixel 7. As for the Pixel 4, there isn't anything we can do; it's a device-specific issue.

since effectively you're solution (we have a subscription for) is not working on a whole bunch of Android devices

We don't have any other reports of this, so it seems "whole bunch of Android devices" only refers to the Pixel 4 series. Except you have more?

The Pixel 3A also exhibits the same issue. Would be great with a workaround for the pixel 7, and perhaps better error handling for the devices you're unable to support.

Added workarounds for Pixel 7 in latest VideoKit alpha build.. I'm closing this issue.


ColorPicker in VisualShader is scaled based on zoom

Godot version
v3.4.1.stable.official [aa1b95889]
System information
Windows 11, macOS 11.6
Issue description

Steps to reproduce

Open VisualShader editor
Create a ColorConstant node
Zoom in/out
Click color button in node

Minimal reproduction project
BugTest_001.zip

This does not appear to be present in the latest build (v4.0.dev.custom_build [489f11ee0])

Works fine in 830b54a03b480f29e60b4ebc813c1e24ac140a70

This does not appear to be present in the latest build (v4.0.dev.custom_build [489f11e])

This is expected, as color picker dialogs are spawned in their own window in the master branch. The bug may reappear if you enable Single Window Mode in the Editor Settings, as it goes back to a behavior similar to 3.x (subwindows are embedded).

This does not appear to be present in the latest build (v4.0.dev.custom_build [489f11e])

This is expected, as color picker dialogs are spawned in their own window in the master branch. The bug may reappear if you enable Single Window Mode in the Editor Settings, as it goes back to a behavior similar to 3.x (subwindows are embedded).

Even this doesn't seem to be the case. I can't reproduce it in master with Single Window Mode enabled. Perhaps I was too quick to make an issue.

Perhaps I was too quick to make an issue.

It's fine – we should still look into fixing this in 3.x :slightly_smiling_face:


Move the plugin docs to the fastlane docs page

          1 Warning

:warning:
Please provide a changelog summary in the Pull Request description @KrauseFx

  Generated by :no_entry_sign: Danger

Yeah, we have the best contributors :)


get-descr no response

Hello, Dexter seems to be working.
I followed your instructions on getting it running quickly from the README.
I am in the Swagger UI, trying to use get-descr to get wiki-ids for named/linked entities.
However, get-descr doesn't seem to be working when the parameter title-one is set to false.
Here are the screen shots (first one when parameter is false and output is not as desired; second one when parameter is true and the output is as desired):

I'm trying to get the named-entity's wiki-id. If there's some way to figure that out without having to call get-descr, that would be helpful.
[Just as an FYI, I'm using Dexter is because it tries to link to the entity with the correct sense.]

dear @gk159yo, if you use the generated model files get-desc will not work anymore because it is using the wikipedia api that is no longer available I think (you could try to fix the client in dexter if you want https://github.com/dexter/dexter/blob/master/dexter-webapp/src/main/java/org/wikipedia/Wiki.java).
You could generate a new model following the steps in https://github.com/dexter/dexter/blob/master/dexter-core/doc/steps-to-use-dexter.txt and that will generate a lucene index that dexter can use to produce the descriptions without relying on wikipedia (but the index will take several gigabytes on the disk, that why I didn't put it as a resource).
for what concerns wikinames, if you add the parameter wn=true to your annotate request, you will get them:
http://localhost:8080/dexter-webapp/api/rest/annotate?text=london&n=50&wn=true&debug=false&format=text&min-conf=0.5
in alternative you can use get-id with title-only enabled - as you noticed. if title-only is disabled it will try to use the wikipedia api and will fail.. (I should have thrown an exception).
Please let me know if it worked.
Diego

@diegoceccarelli Thanks for the reponse!
All the entity dumps I found were multistream dumps. https://dumps.wikimedia.org/wikidatawiki/
If I download the multistream dump, would uncompressing it make it json-wikipedia processable?
Alternatively, would a JSON entity dump suffice (so I won't run this through json-wikipedia)`? https://archive.org/details/wikibase-wikidatawiki-20171209
Also, do you know if Dexter is capable of returning the wiki-id? For example, a wiki-id of 101401 can be quickly looked up in wikidata as such: https://www.wikidata.org/wiki/Q101401 Wiki-data id's can be found under the wikidata button of every wikipedia entry, under the tools section in the left sidebar.
Thanks!


Some citations don't have links

Sometimes, Stampy will cite something but the link doesn't work.  Asking Stampy Who is Robert Miles produces two citations that do not have links consistently.  I've tried restarting the service and cache but this seems to always be the case.  Your results may vary.

This isn't a bug, but an issue with the dataset. Some data (notably all the books) don't have anything we could link to. Usually in these cases googling the citation yields the source.
I agree that the current solution of linking to nothing feels a bit rough. The two real solutions I could envision would be:

Just link to a DuckDuckGo search for the exact citation in these cases, hope that will bring it up
Start an effort on the dataset to add links to all sources, like to corresponding publisher or author webpages for books

All the entries in the updated dataset should be valid urls, including books which will link to goodreads. We can leave this for now and double check again after the re-embedding the new ARD.

sgtm

Related to StampyAI/alignment-research-dataset#2

if we should keep this open, lmk

I'd like to keep this open for now, as a placeholder, to avoid people creating new issues with essentially the same idea until we've fully resolved it.
DuckDuckGo is a good stop gap. It would be nice to also do that not only for empty urls but invalid urls, like private or removed pages. Hopefully, this'll be needed less and less but it's nice to have as a backup.


Fix for /upload url path that never worked in staging

Production config is different from the one stored in the repository.
This PR updates the configs to match working configuration.

Looks good.
The only caveat (unrelated to the change) is that caddy doesn't seem to restart on config changes (when using docker-compose -p orbitar-dev -f docker-compose.local.yml up -d --build).

Will create an issue.


Use custom tabs to open links on Android (like FB messenger, FB, twitter etc).

iOS already have better implementation (which looks like custom tabs).
https://developer.chrome.com/multidevice/android/customtabs

@zulipbot claim


Major revisions to navbar and template

This is what the update looks like

I like the look of the image! But, the GitHub actions are failing to build, and it seems like an awful lot of files were changed. Is all of this really necessary? You can also try pushing another commit to rerun the actions if yes and you think you've fixed it.

(That is to say, try not to copy-paste too much stuff from Dr. Mistriotis's site if it is not needed here / yet!)


Add 'Reading Mode'

I was thinking it would be handy to create a 'Reading mode' button which turns off the panels to the right (term translations and dictionaries) and adds various buttons for different modes:

Default mode (single lang, single column)
the 'bidirectional' one you suggested here
interlinear mode (for example)
Linguistic mapping (NN, VV, etc) [POS-tagging]*
Other ideas?

*With multiple translations fields + POS-tagging, you could create even more accurate and detailed term translations, but that's a convo for another time.

This feels quite out of scope for Lute.  Even the bidirectional item feels like a stretch (though I added it as an issue just as a placeholder), and is better served by bidirectional readers.  The linguistic mapping is far out of scope, I believe, but that could be my own limited understanding of its applicability to language learning!
But hey, future thinking.  (I wish there was a better way to manage GitHub issues, the current manner of listing everything makes it hard to see real issues vs future ideas.  I may tag this later as "wishful-thinking" :-) )

I figured that these are perfectly in scope for Lute. Funny that!
Again, on this one, it could be forked as an advanced/linguistics mode and/or made into a plugin.


Increase column min width from 50px to at least 100px

Current minimum size too small for meaningful view. This is visible while doing table resize.

Can be changed in styles.

Solution:
.Table { --grid-col-size: minmax(100px, 1fr); }


Create missing translation files

Patches langman:sync by adding a --create option, when used, the section keys found in view files are then created in each language directory in case they're missing.

@themsaid are you still maintaining this package? if so this seems like a really useful timesaver

merged into https://github.com/liip/laravel-langman


fish-like autosuggestions

Fish has this nice feature of suggesting commands from history without pressing Ctrl+R every time:
https://fishshell.com/docs/current/tutorial.html#tut_autosuggestions
Would you like to have something like this implemented in liner?

I would certainly like to see this for the Ion shell.

@MovingtoMars I'm looking at the code, but not sure where to start. Where would you suggest me to implement this and do you want to make it optional?

I'd say create a HistoryCommandCompleter that implements the Completer trait.

I think that is missing the point of autocompletion, because it would not be automatic, i.e. without pressing tab or Ctrl+R. Have you seen my PR?

Oh sorry, just looked. It's great!

@msehnout Think you could also add the dedup() line from my PR to yours, to avoid needing to merge two PRs?

@mmstick Just the one line? I can see that we have conflicting changes, but I think it won't be hard to merge them by hand.

@msehnout That one line is the only one that matters. The rest are just recommendations from Clippy.

@mmstick ok no problem

Is there anything else that needs to be done for this?

There probably is according to Ion's readme:
https://github.com/redox-os/ion/blob/master/README.md
But I'm not sure what @mmstick meant.

What's missing right now is autocompletions with the right arrow key.

That's done as of #44


apply slick lightbox to a group of images

In my site there are multiple times i used slick lightbox..When i clicked on an image it will show the  image but when click next it will load all the images that i'm using in all slick sliders in the page..can't we group and show images? I initialized plugin using class. is that the problem?

That sounds like a problem with your code. Provide a minimal jsfiddle/codepen.

http://codepen.io/anon/pen/kXEaWm?editors=1010
See this pen..I separated my slides in two sets(set 1 and set 2).. but when we see in lightbox all the images (set 1 and set 2) displaying together. i want to group those.(as set 1 and set 2)

You're right. I'll fix that. For now, use .each http://codepen.io/mreq/pen/EyExzk?editors=1010#anon-login

This solution not work for the appended images..any fix?


Why does it take less time to push artifacts to different projects than to the same project?

https://github.com/goharbor/perf/wiki/Harbor-2.5.0

Because each project is quota limited, there is an additional lock cost for checking and updating quotas when a large number of concurrent pushes to the same project.


[SPARK-19298][Core] History server can't match MalformedInputException and prompt the detail logs while repalying eventlog

History server can't match MalformedInputException and prompt the detail logs while repalying eventlog, because MalformedInputException is a subclass of IOException.

Can one of the admins verify this patch?

Isn't this changing the default behavior for non-IOExceptions? now they're rethrown.

@srowen
i think the logs were just for MalformedInputException, it does't matter that non-IOExceptions will be rethrown, because they will be catched by upper callers.

I'm not clear why you believe the exception handling should be changed. If IOExceptions are fatal, and this is a form of I/O exception (corrupted input), why change it?

Ping @sharkdtu

Let's close this if there is no follow-up


switching identity documentation

https://github.com/Nitrokey/pynitrokey/blob/master/README.md#switching-id
Is it possible to send the specific attribute with a scd command? Until this is done: https://github.com/Nitrokey/pynitrokey/issues/61 it can be a little bit difficult to install pynitrokey, e.g. under RPi zero and alpinelinux.

Hi!
Yes, I believe this should be possible without any problem, but unfortunately does not work for me.
The APDU is 0x85, 0x00, {ID}, where {ID} is in range [0;2]. E.g.:
# id 2
$ gpg-connect-agent --hex "scd apdu  85 00 02" /bye
ERR 65539 Unknown version in packet <Unspecified source>

I must be missing some bytes.

Ah, yes. The 00 prefix.  Corrected. Now it works.

Fixed with https://github.com/Nitrokey/pynitrokey/commit/da508c0e61e2c5b065980b2a2c1f40dd8601982a

Add other possible scenarios. Details below:

https://github.com/Nitrokey/pynitrokey/commit/da508c0e61e2c5b065980b2a2c1f40dd8601982a#commitcomment-55902706


Specify initial ML LDD

Summary
The initial Machine Learning LDD contains these classes:

Trained_Machine_Learning_Model: Specify model used to generate an ML product.

Includes attributes (all required):

trained_model_version_id
trained_model_name
trained_model_metric
trained_model_performance

and components:

Training_Set (required)
Validation_Set (optional)
Test_Set (optional)

Machine_Learning_Algorithm: Specify the algorithm used to train the model.

Includes attributes (all required):
algorithm_learning_style: Choose one of Supervised_Learning, Semisupervised_Learning, or Unsupervised_Learning
algorithm_type: Currently the only option available is Convolutional_Neural_Network_Classifier
algorithm_name

Image_Data_Set: Abstract class, with three sub-classes:

Training_Set
Validation_Set
Test_Set
and these attributes (required):

data_set_version_id
data_set_size

Test Data and/or Report
Regression tests in test/ yield expected results:

test_mars_VALID.xml: pass
test_mars_nodata_FAIL.xml: fail (no training data specified)

@jordanpadams Great idea!  I've added a Machine_Learning parent class.  Could you take a look and let me know if this addresses your suggestion?

looks great! you are go for a merge if you are ready

@wkiri ☝


[[FIX]] Always warn about missing "use strict" directive

Fixes gh-2668

Rebased and merged to master at commit e85c2a139b4314c13c563d8b359912198ab48f7b. Thanks!


MicrosoftDebuggingDataModelDbgModelApiXtnPath empty in Directory.build.targets

I did a build, and saw this warning:
  MSBUILD : warning MSB5029: The value "\**\*" of the "Include" attribute in element <ItemGroup> in file "C:\src
\github\SizeBench\src\Directory.Build.targets (53,11)" is a wildcard that results in enumerating all files on th
e drive, which was likely not intended. Check that referenced properties are always defined.

Directory.build.targets has a line that does this:
    <None Include="$(MicrosoftDebuggingDataModelDbgModelApiXtnPath)\**\*" CopyToOutputDirectory="PreserveNewest" Visible="False" Link="%(RecursiveDir)%(FileName)%(Extension)"/>

which means that MicrosoftDebuggingDataModelDbgModelApiXtnPath must be empty.
Protecting it with a check ('$(MicrosoftDebuggingDataModelDbgModelApiXtnPath)' != '') fixed it for me:
  <!-- This is all the stuff necessary to use DbgX at runtime, it's needed in multiple projects, so it's centralized here -->
  <ItemGroup Condition="'$(IncludeDbgXAssets)'=='true' And '$(MicrosoftDebuggingDataModelDbgModelApiXtnPath)' != ''">
    <Content Include="..\ExternalDependencies\DIA\msdia140.dll">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
    <None Include="$(MicrosoftDebuggingDataModelDbgModelApiXtnPath)\**\*" CopyToOutputDirectory="PreserveNewest" Visible="False" Link="%(RecursiveDir)%(FileName)%(Extension)"/>
  </ItemGroup>

I'm not entirely sure why MicrosoftDebuggingDataModelDbgModelApiXtnPath isn't set, but this fixes it for me.
It looks like I don't have permissions to create a Pull Request.

Thanks for reporting this - this path gets set by a NuGet package that SizeBench depends on, but the path isn't set until that package is restored, so on the first NuGet restore it'll be empty.  Your fix is the right one, so I'll be adding that in a PR shortly along with some other work.

This should be fixed now.


Some metadata needs to be checked

Some maps were not found in OPAC and will need to be checked manually

I have checked these today - there are only a couple of maps with missing metadata now (which we can decide to keep or not).


KNOX-2632 - Properly copying generated content on tokengen UI

What changes were proposed in this pull request?
Implemented the copy-to-clipboard function in a cross-browser safe manner.
How was this patch tested?
Tested manually using Google Chrome, Firefox and Safari.

cc. @zeroflag

LGTM


hardcoded example strings in src/lis-gene-search-element.ts (and probably other components) ought to be customizable

because they aren't appropriate for use on all sites (e.g. Glyma.13G357700 isn't a good example for peanutbase)

This is a good feature. Mind adding it to the relevant UI specs? Also, this would be a good feature for someone that wants to dip their toe into Web Component development.

one thought occurred to me earlier today about this issue I'd be curious to hear opinions about. It seems like it would be possible to auto-generate examples that would work by querying the server with no constraints and using the values returned from the first (or randomly selected) record as example constraints. This would have the advantage of never falling out of sync with database content, but the disadvantage of likely giving an "uninteresting" example. I'd imagine that the graphql server would pre-load such examples on startup and the relevant web components would just ask for them upon instantiation. Maybe the advantages are not so compelling as to warrant significant extra work, but it seems like a nice way to avoid having to think about minutiae related to content updates (e.g. when pangene sets are updated, having to think about changing the pangene ids in examples).

I'm not sure "avoid having to think" is a good reason to introduce a major hack into the system. :)

well if I had a nickel for every time one of the hard coded examples elsewhere in our system stopped working, I could pay someone to think for me- which I pretty much do anyway ;)
it may just be a bad idea, though

one thought occurred to me earlier today about this issue I'd be curious to hear opinions about. It seems like it would be possible to auto-generate examples that would work by querying the server with no constraints and using the values returned from the first (or randomly selected) record as example constraints. This would have the advantage of never falling out of sync with database content, but the disadvantage of likely giving an "uninteresting" example. I'd imagine that the graphql server would pre-load such examples on startup and the relevant web components would just ask for them upon instantiation. Maybe the advantages are not so compelling as to warrant significant extra work, but it seems like a nice way to avoid having to think about minutiae related to content updates (e.g. when pangene sets are updated, having to think about changing the pangene ids in examples).

Our web components are dumb and this is a pretty smart feature so I don't think endowing the web components with this functionality is appropriate. I do, however, think it's a good idea so the question is where does it make sense to implement this? The easiest approach would be to add some graphql scripts to the theme that you can mindlessly call when adding a component to your site. A more robust solution would be to add a file like _data/examples.yml to your site that contains such examples. This file could be auto-generated or be a hand-curated list. I like the latter solution because it supports a broader set of scenarios and we could add an example of this to the Jekyll starter site, i.e. it's not a theme-level feature but a cool thing you can easily implement with our stack.

Thanks, indeed I forgot about the web-components-are-dumb principle in how I envisioned it being implemented. Your suggestion to make it work via a yaml file that could be hand-crafted or auto-generated makes sense. I will try to revisit the relevant UI specs and prepare my toe for dipping into web component development as you suggested above (weeks ago).


[MM-28483] Surface custom about modal for cloud instances

Summary
The default about modal reveals a lot of information that a Cloud user will not care about (and probably shouldn't see for security reasons). This PR adds a custom about modal that appears for Cloud licenses. It utilizes the default AboutCloudModal as an entry-point.
Ticket Link
https://mattermost.atlassian.net/browse/MM-28483
Related Pull Requests
n/a
Screenshots

Fixed the text, added the padding as requested @matthewbirtch
With that new padding it doesn't necessarily match the design, distance between the top of the mattermost svg and the header is 46 pixels in figma, but now with 15 px padding on top its 61. Let me know what you think.

but now with 15 px padding on top its 61. Let me know what you think.

Ya, you're right. With the 15px on top, it feels off balance. I think you can make that top padding 0 actually. That should do the trick

@matthewbirtch back to 0px padding at the top on the next spinwick update. Let me know what you think!

/cherry-pick cloud-beta

Cherry pick is scheduled.


Can not run in Angular 11

I just installed and tried to run an recived a error:
PS: The command ng test is working great.

Can not load "KarmaTestExplorerReporter"!
TypeError [ERR_WORKER_UNSUPPORTED_EXTENSION]: The worker script extension must be ".js" or ".mjs". Received ".cjs"
Log Karma Server:

Karma Test Explorer: Launching Karma
05 05 2023 14:01:41.085:WARN [karma-server]: Passing raw CLI options to new Server(config, done) is deprecated. Use parseConfig(configFilePath, cliOptions, {promiseConfig: true, throwErrors: true}) to prepare a processed Config instance and pass that as the config argument instead.
[2023-05-05 17:01:41.105] [DEBUG] [KarmaConfigLoader]: Loading Karma config: C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/karma.conf.js
[2023-05-05 17:01:41.314] [DEBUG] [KarmaConfigLoader]: Using custom launcher: {
"base": "Chrome",
"flags": [
"--headless",
"--disable-gpu",
"--disable-dev-shm-usage",
"--remote-debugging-port=9222"
]
}
05 05 2023 14:01:45.379:ERROR [reporter]: Can not load "KarmaTestExplorerReporter"!
TypeError [ERR_WORKER_UNSUPPORTED_EXTENSION]: The worker script extension must be ".js" or ".mjs". Received ".cjs"
at new Worker (internal/worker.js:85:15)
at Pe.KarmaTestExplorerReporter (C:\Users\lucas.gomes.vscode\extensions\lucono.karma-test-explorer-0.8.2\dist\karma.conf.cjs:1:109835)
at invoke (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:75:15)
at Array.instantiate (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:59:20)
at Injector.get (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:48:43)
at C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\reporter.js:118:75
at Array.forEach ()
at createReporters (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\reporter.js:100:9)
at Array.invoke (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:75:15)
at get (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:48:43)
at C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:71:14
at Array.map ()
at Injector.invoke (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:70:31)
at createWebServer (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\web-server.js:74:24)
at Array.invoke (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:75:15)
at Injector.get (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\di\lib\injector.js:48:43)
at Server._start (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\server.js:215:38)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Server.start (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\server.js:155:7)
05 05 2023 14:01:45.399:WARN [karma]: No captured browser, open http://localhost:9976/
05 05 2023 14:01:45.401:INFO [karma-server]: Karma v6.4.2 server started at http://localhost:9976/
05 05 2023 14:01:45.402:INFO [launcher]: Launching browsers KarmaTestExplorer_CustomLauncher with concurrency unlimited
05 05 2023 14:01:45.402:ERROR [karma-server]: Error: Found 1 load error
at Server. (C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\karma\lib\server.js:243:26)
at Object.onceWrapper (events.js:298:28)
at Server.emit (events.js:214:15)
at emitListeningNT (net.js:1332:10)
at processTicksAndRejections (internal/process/task_queues.js:79:21)
Log Test Explorer:
[2023-05-05 17:08:30.977] [INFO] [Adapter]: Resetting adapter
[2023-05-05 17:08:30.977] [DEBUG] [KarmaTestExplorer]: Test operation cancellation requested - Aborting any currently running test operation
[2023-05-05 17:08:30.977] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-05-05 17:08:30.977] [DEBUG] [DefaultTestManager]: Karma event listener is already stopped
[2023-05-05 17:08:30.977] [DEBUG] [DefaultTestManager]: Karma server is already stopped
[2023-05-05 17:08:30.977] [DEBUG] [DefaultTestManager]: Stopped test manager
[2023-05-05 17:08:30.978] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-05-05 17:08:30.979] [DEBUG] [DefaultTestManager]: Karma event listener is already stopped
[2023-05-05 17:08:30.979] [DEBUG] [DefaultTestManager]: Karma server is already stopped
[2023-05-05 17:08:30.979] [DEBUG] [DefaultTestManager]: Stopped test manager
[2023-05-05 17:08:30.982] [DEBUG] [Adapter]: Assembling new test explorer
[2023-05-05 17:08:30.982] [DEBUG] [Adapter]: Re/creating test explorer with extension configuration: {
"logger": {
"loggerName": "ExtensionConfig",
"appender": {
"outputChannelName": "Karma Test Explorer (bs-workspace: corretor-lib)",
"options": {
"enabled": true,
"lazyCreate": false
},
"outputChannel": {
"name": "Karma Test Explorer (bs-workspace: corretor-lib)"
}
},
"logLevel": "debug"
},
"projectType": "angular",
"projectName": "corretor-lib",
"projectPath": "C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib",
"projectInstallRootPath": "C:/Users/lucas.gomes/Documents/repos/bs-workspace",
"projectKarmaConfigFilePath": "C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/karma.conf.js",
"baseKarmaConfFilePath": "C:/Users/lucas.gomes/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs",
"karmaPort": 9976,
"testTriggerMethod": "http",
"testParsingMethod": "ast",
"failOnStandardError": false,
"defaultSocketConnectionPort": 9999,
"logLevel": "debug",
"karmaLogLevel": "info",
"karmaReporterLogLevel": "disable",
"autoWatchEnabled": true,
"karmaReadyTimeout": 900000,
"testGrouping": "folder",
"flattenSingleChildFolders": true,
"environment": {},
"envExclude": [],
"reloadOnKarmaConfigChange": true,
"customLauncher": {
"base": "Chrome",
"flags": [
"--headless",
"--disable-gpu",
"--disable-dev-shm-usage",
"--remote-debugging-port=9222"
]
},
"testFiles": [
"/*{.,-,_}{test,spec}.{ts,js}",
"/{test,spec}{.,-,}.{ts,js}"
],
"allowGlobalPackageFallback": true,
"excludeDisabledTests": false,
"showOnlyFocusedTests": false,
"showUnmappedTests": true,
"showTestDefinitionTypeIndicators": true,
"debuggerConfig": {
"name": "Karma Test Explorer Debugging",
"type": "chrome",
"request": "attach",
"browserAttachLocation": "workspace",
"address": "localhost",
"port": 9222,
"timeout": 60000,
"webRoot": "C:/Users/lucas.gomes/Documents/repos/bs-workspace"
},
"reloadOnChangedFiles": [],
"defaultDebugPort": 9222,
"excludeFiles": [
"/node_modules//"
]
}
[2023-05-05 17:08:30.982] [DEBUG] [Adapter]: Creating main factory
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Detecting test framework from karma config file: C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/karma.conf.js
[2023-05-05 17:08:30.982] [DEBUG] [SimpleFileHandler]: Reading file synchronously: C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/karma.conf.js
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Detected frameworks from karma config: jasmine, @angular-devkit/build-angular
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Detected test framework: jasmine
[2023-05-05 17:08:30.982] [INFO] [MainFactory]: Using test framework: jasmine (auto-detected)
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Creating test helper
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Creating process handler
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Creating test locator
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Creating AST test definition provider
[2023-05-05 17:08:30.982] [DEBUG] [MainFactory]: Creating test store
[2023-05-05 17:08:30.982] [DEBUG] [Adapter]: Getting process handler from factory
[2023-05-05 17:08:30.983] [DEBUG] [Adapter]: Getting test locator from factory
[2023-05-05 17:08:30.983] [DEBUG] [Adapter]: Getting test store from factory
[2023-05-05 17:08:30.983] [DEBUG] [Adapter]: Getting test manager from factory
[2023-05-05 17:08:30.983] [DEBUG] [AngularFactory]: Creating Angular test server executor
[2023-05-05 17:08:30.983] [INFO] [AngularFactory]: Using Angular project 'corretor-lib' at root path 'C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib' and karma config file 'C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/karma.conf.js'
[2023-05-05 17:08:30.983] [DEBUG] [KarmaFactory]: Creating Karma http test run executor
[2023-05-05 17:08:30.983] [DEBUG] [Adapter]: Getting file watcher from factory
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Creating file watchers for monitored files
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Registering file handler for files: [
"karma.conf.js"
]
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern 'karma.conf.js' using base path: c:\Users\lucas.gomes\Documents\repos\bs-workspace
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Creating file watchers for test file changes
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Registering file handler for files: [
"**/*{.,-,}{test,spec}.{ts,js}",
"/{test,spec}{.,-,_}*.{ts,js}"
]
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '/{.,-,}{test,spec}.{ts,js}' using base path: c:\Users\lucas.gomes\Documents\repos\bs-workspace
[2023-05-05 17:08:30.983] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/{test,spec}{.,-,}.{ts,js}' using base path: c:\Users\lucas.gomes\Documents\repos\bs-workspace
[2023-05-05 17:08:30.983] [DEBUG] [Adapter]: Creating test explorer
[2023-05-05 17:08:30.983] [DEBUG] [KarmaTestExplorer]: Test load started
[2023-05-05 17:08:30.983] [DEBUG] [KarmaTestExplorer]: Test hard refresh started
[2023-05-05 17:08:30.983] [DEBUG] [TestLocator]: Refresh requested for all spec file(s): ["/*{.,-,_}{test,spec}.{ts,js}","/{test,spec}{.,-,}.{ts,js}"]
[2023-05-05 17:08:30.983] [DEBUG] [TestLocator]: No refresh currently in progress - will commence new refresh for files: ["**/{.,-,}{test,spec}.{ts,js}","/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-05 17:08:30.983] [DEBUG] [TestLocator]: Refreshing all spec file(s): ["/{.,-,}{test,spec}.{ts,js}","**/{test,spec}{.,-,}.{ts,js}"]
[2023-05-05 17:08:30.985] [DEBUG] [KarmaTestExplorer]: Refresh request - Test manager is not started - Starting it
[2023-05-05 17:08:31.000] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9976 acquired: 9976
[2023-05-05 17:08:31.000] [INFO] [DefaultTestManager]: Using requested --> available karma port: 9976 --> 9976
[2023-05-05 17:08:31.247] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9999 acquired: 10022
[2023-05-05 17:08:31.247] [INFO] [DefaultTestManager]: Using requested --> available karma listener socket port: 9999 --> 10022
[2023-05-05 17:08:31.258] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9222 acquired: 9222
[2023-05-05 17:08:31.258] [INFO] [DefaultTestManager]: Using requested --> available debug port: 9222 --> 9222
[2023-05-05 17:08:31.258] [DEBUG] [KarmaTestListener]: Attempting to listen on port 10022
[2023-05-05 17:08:31.259] [INFO] [KarmaTestServer]: Starting karma server
[2023-05-05 17:08:31.260] [DEBUG] [AngularTestServerExecutor]: Executing server start with karma port '9976' and karma socket port '10022'
[2023-05-05 17:08:31.276] [DEBUG] [AngularTestServerExecutor]: Found '@angular/cli' module at: C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules@angular\cli
[2023-05-05 17:08:31.276] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process amc0ipf0oxv:
Executing command: 'C:\Program Files\nodejs\node.EXE'
with args: ["C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules\@angular\cli\bin\ng","test","corretor-lib","--karma-config=C:/Users/lucas.gomes/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs","--progress=false","--no-watch"]
[2023-05-05 17:08:31.282] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process amc0ipf0oxv - process spawned successfully with PID 21104 for command: C:\Program Files\nodejs\node.EXE C:\Users\lucas.gomes\Documents\repos\bs-workspace\node_modules@angular\cli\bin\ng test corretor-lib --karma-config=C:/Users/lucas.gomes/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs --progress=false --no-watch
[2023-05-05 17:08:31.284] [INFO] [KarmaTestListener]: Waiting for Karma to connect on port 10022
[2023-05-05 17:08:31.330] [DEBUG] [SimpleFileHandler]: Resolved 2 file(s) from file patterns: ["/*{.,-,_}{test,spec}.{ts,js}","/{test,spec}{.,-,}.{ts,js}"]
[2023-05-05 17:08:31.330] [DEBUG] [TestLocator]: Requested --> filtered file count to refresh: 2 --> 2
[2023-05-05 17:08:31.330] [DEBUG] [SimpleFileHandler]: Reading file async: C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/src/lib/services/data-power/data-power-private.service.spec.ts
[2023-05-05 17:08:31.334] [DEBUG] [AstTestFileParser]: Parse operation e0xspcpymed: Parsed 2 total tests from file 'C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/src/lib/services/data-power/data-power-private.service.spec.ts' in 0.00 secs
[2023-05-05 17:08:31.334] [DEBUG] [SimpleFileHandler]: Reading file async: C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/src/lib/services/data-power/data-power-protected.service.spec.ts
[2023-05-05 17:08:31.336] [DEBUG] [AstTestFileParser]: Parse operation ok2i6ahtlk9: Parsed 2 total tests from file 'C:/Users/lucas.gomes/Documents/repos/bs-workspace/projects/corretor-lib/src/lib/services/data-power/data-power-protected.service.spec.ts' in 0.00 secs
[2023-05-05 17:08:31.336] [DEBUG] [TestLocator]: Refreshed 2 spec files from glob list in 0.35 secs: ["**/{.,-,}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
Package.json
{
  "name": "bs-workspace",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~11.2.14",
    "@angular/common": "~11.2.14",
    "@angular/compiler": "~11.2.14",
    "@angular/core": "~11.2.14",
    "@angular/forms": "~11.2.14",
    "@angular/platform-browser": "~11.2.14",
    "@angular/platform-browser-dynamic": "~11.2.14",
    "@angular/router": "~11.2.14",
    "rxjs": "~6.6.0",
    "tslib": "^2.0.0",
    "zone.js": "~0.11.3"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1102.18",
    "@angular/cli": "~11.2.19",
    "@angular/compiler-cli": "~11.2.14",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "jwt-decode": "^3.1.2",
    "karma": "^6.4.2",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "~1.5.0",
    "ng-packagr": "^11.0.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~4.1.5"
  }
}

// Karma configuration file, see link for more information
// https://karma-runner.github.io/1.0/config/configuration-file.html

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular-devkit/build-angular'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage'),
      require('@angular-devkit/build-angular/plugins/karma')
    ],
    client: {
      jasmine: {
        // you can add configuration options for Jasmine here
        // the possible options are listed at https://jasmine.github.io/api/edge/Configuration.html
        // for example, you can disable the random execution with `random: false`
        // or set a specific seed with `seed: 4321`
      },
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    jasmineHtmlReporter: {
      suppressAll: true // removes the duplicated traces
    },
    coverageReporter: {
      dir: require('path').join(__dirname, '../../coverage/corretor'),
      subdir: '.',
      reporters: [
        { type: 'html' },
        { type: 'text-summary' }
      ]
    },
    reporters: ['progress', 'kjhtml'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome'],
    singleRun: false,
    restartOnFileChange: true,
  });
};

Please Provide the Following Information

OS and Version: Win 10
Node Version: 12.10.0
VS Code Version:  1.78.0

Fixed update node to 14


Height conversion between DNN and DVR90 not correct

When running the app using the commands in the README
the result is an application that gives wrong height values when converting from DNN to DVR90
Example:
http://<IP_ADDRESS>:8000/v1.0/trans/EPSG:23032+5733/EPSG:7416/551359.00,6368207.00,28
gives
{
"v1":<PHONE_NUMBER>742307,
"v2": 6367999.219770487,
"v3": 27.96584952889701,
"v4": null
}
But the correct result given by api.dataforsyningen.dk is
{
"v1":<PHONE_NUMBER>241157,
"v2": 6367999.219725298,
"v3": 27.980722557094055,
"v4": null
}

The same problem exists when running webproj in a Docker container defined by the Dockerfile

Release 1.2.2 of webproj does not have this issue


Payment integration

[x] Create products overview to display features
[x] Create success page to display after a successful checkout
[x] Create cancel page to display after a failed checkout
[ ] Handle subscription downgrades / upgrades (needs discussion)
[x] Handle cancellation
[ ] Disallow multiple subscriptions
[x] Implement integration with the machine learning component
[x] Find a solution to log out after issuing new jwt
[x] Fix jwt expiration times

Tasks to implement:

[x] Limit Training Time
[x] Limit Number of Users in a Project
[ ] Storage
[x] Parallel Jobs
[ ] Optimization

New design details:

Subscription is implemented on user level.
However projects created by a premium user also have the same features and users added to this project can use these features.
To prevent misuse of a premium account, number of projects a user can create should be limited (?)

(I can't recall the reason without 4.)

To further prevent misuse, number of users added to project should be limited (?)

Premium user can add 10s of users to a project, so if an organisation needs only a few projects point 3. would be ineffective and the whole organisation gains access to premium features without paying.

Open Questions:

[ ] Current ml design allows more than one user to run train on the same project simultaneously. Should it be changed to implement parallel jobs feature?

@TobiasRoeddiger @tk-king @omeryagmurlu @ilteen

Open Questions:

[ ]  Current ML design allows more than one user to run train on the same project simultaneously. Should it be changed to implement parallel jobs feature?
the number of parallel trainings should be on a per user level. that makes the most sense. so a project could have five parallel jobs if they come from 5 dev sub users.

Open Questions:

[ ]   Current ML design allows more than one user to run train on the same project simultaneously. Should it be changed to implement parallel jobs feature?

the number of parallel trainings should be on a per user level. that makes the most sense. so a project could have five parallel jobs if they come from 5 dev sub users.

This would be abusable if we didn't plan to limit number of users added to a project, but it's fine with it. We just need to set this number and pro level users' parallel job number balanced, so there wouldn't be a scenario where someone needs to run many parallel jobs on a project and they create 10 standard accounts and run the training on them instead of getting a pro subsciption and run 4 parallel jobs.
This scenario would even apply even when the account limit in project is 2 people, since you gain an extra parallel job by creating a second account, but then it would be a tradeoff as you give up the right to add someone else to the account in order to gain an extra parallel job.
So all we need to think about this question is how to set the account limit in project and number of parallel jobs in pro subscription in a compatible manner.

Open Questions:

[ ]    Current ML design allows more than one user to run train on the same project simultaneously. Should it be changed to implement parallel jobs feature?

the number of parallel trainings should be on a per user level. that makes the most sense. so a project could have five parallel jobs if they come from 5 dev sub users.

This would be abusable if we didn't plan to limit number of users added to a project, but it's fine with it. We just need to set this number and pro level users' parallel job number balanced, so there wouldn't be a scenario where someone needs to run many parallel jobs on a project and they create 10 standard accounts and run the training on them instead of getting a pro subsciption and run 4 parallel jobs. This scenario would even apply even when the account limit in project is 2 people, since you gain an extra parallel job by creating a second account, but then it would be a tradeoff as you give up the right to add someone else to the account in order to gain an extra parallel job. So all we need to think about this question is how to set the account limit in project and number of parallel jobs in pro subscription in a compatible manner.

That's fine. If someone wants to take the effort to do that I don't mind.

Multiple subscriptions problem briefly explained:

We are using stripe checkout and customer portal
Stripe does not think of different subscriptions as substitutes of each other, which means user can subscribe to Pro and Pro+ at once
Buying a subscription is done via checkout
To prevent this scenario, we don't generate new checkout sessions if user has an active subscription (checked via information in jwt)
Instead user is redirected to the customer portal
Information in jwt is only updated when token is refreshed / user logs in
Token needs to be refreshed directly after a successful checkout event

Upgrade/Downgrade problem briefly explained:

Upgrading works fine, Pro user can upgrade to Pro+ by paying the required amount and Pro+ features are unlocked immediately (token needs to be refreshed)
Downgrade causes the following problem:
Pro+ is billed annually, so user pays for a year upfront
When user decides to downgrade to Pro, it takes effect immediately, which means user loses benefits which they paid for.
And they are billed by stripe next month for the Pro subscription
This cannot be fully circumvented by keeping the subscription expiration dates in the database
This would help keep user the benefits of the Pro+, however:
They will be billed for the Pro regardless each month, even though they are essentially paid for Pro+ and using its features
Customer portal will be misinforming the user, telling them the active subscription is Pro instead of Pro+
Downgrades and upgrades go in tandem, we cannot disable single one of them without disabling the other.
Easiest solution would be to make Pro+ billed monthly, then stripe takes care of it.
Hard way is to disable the customer portal by stripe and implement it on site

[ ] /payment is directly redirected to / without showing the subscription page unless the user has at least one project.


[Bug] Screenshot shown a route credit expiry transaction but the details is not reflected. User is confused about what has happen

Display when route pass expires is empty

Related to #485

To be fixed under revamp UI view for transaction history


Rsync: Configured username ignored

There’s already a PR fixing this: #127
The bug got introduced in https://github.com/middleman-contrib/middleman-deploy/commit/86f76b2a53b408487eb294c5462c31be0751232a#diff-6d0c130d155d957759feb2f03e0d7f1b: self is necessary here, because the local variable user is shadowing the attribute accessor.

+1

Workaround:
deploy.host          = 'root@host'
~~

Thanks for the workaround @alexec

I've been hitting my head against the wall the past 20 minutes trying to figure out why I was getting a "Permission denied (public key)" error.. and it was because of this. Please release at least a minor version with this is not a minor bug.


I have 18.6 million tokens but am getting a prompt is too long error:  prompt is too long: 200661 tokens > 200000 maximum

Describe the bug
I have 18.6 million tokens but am getting a prompt is too long error:  prompt is too long: 200661 tokens > 200000 maximum
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-jbxypz
Steps to reproduce
See screenshot
Expected behavior
See problem description
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 52921517,
  "usedJSHeapSize": 49021865,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = respkid
Chat ID = 735496a28d7d

Additional context
None

Sonnet 3.5 context window limitations.
Cf. #1322 for tips

On Sunday, November 10th, 2024 at 5:13 PM, LaurentBarbareau @.***> wrote:

Sonnet 3.5 context window limitations.
Cf. #1322 for tips
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I don't understand. The prompt was like 3 sentences

Open the project in StackBlitz and create an ignore file in .bolt directory
.bolt/ignore
Then specify the files you want bolt to ignore so you don't exceed the prompt limit
Example
src/context/*
src/styles/*
src/components/Splash/*
src/utils/TokenManager.ts
src/components/Dashboard/BottomNav/*
Hope this helps

I don't understand. The prompt was like 3 sentences
So you can conclude that the context window is not just what you seem to believe. ;)

Such a strange question from a user on a no code site amirite ;)
On Monday, November 11th, 2024 at 4:58 AM, LaurentBarbareau @.***> wrote:

I don't understand. The prompt was like 3 sentences
So you can conclude that the context window is not just what you seem to believe. ;)

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hi all,
Correct, this issue is being tracked here: #1332. Appreciate your patience as improvements continue to be made!


Do not reraise cancellations

What was wrong?
When a stream is cancelled the exception is re-raised. I don't recall why I did that or if it was just a left over but it causes these problems in Trinity.
WARNING  12-07 20:34:23      DiscoveryService  Task <coroutine object DiscoveryService.handle_get_random_bootnode_requests at 0x7f45ad668150> finished unexpectedly:
   DEBUG  12-07 20:34:23      DiscoveryService  Task failure traceback
Traceback (most recent call last):
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/p2p/service.py", line 141, in _run_task_wrapper
    await awaitable
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/p2p/service.py", line 160, in _run_daemon_task_wrapper
    await awaitable
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/trinity/plugins/builtin/peer_discovery/discovery_service.py", line 70, in handle_get_random_bootnode_requests
    async for event in self._event_bus.stream(RandomBootnodeRequest):
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/venv/lib/python3.6/site-packages/lahja/endpoint.py", line 267, in stream
    raise e
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/venv/lib/python3.6/site-packages/lahja/endpoint.py", line 261, in stream
    yield await queue.get()
  File "/usr/lib/python3.6/asyncio/queues.py", line 167, in get
    yield from getter
concurrent.futures._base.CancelledError
   DEBUG  12-07 20:34:23      DiscoveryService  All tasks finished
    INFO  12-07 20:34:23     DiscoveryProtocol  stopping discovery
    INFO  12-07 20:34:23              FullNode  Timed out waiting for <trinity.nodes.full.FullNode object at 0x7fd8de625ef0> to finish its cleanup, forcibly cancelling pending tasks and exiting anyway
   DEBUG  12-07 20:34:23              FullNode  Pending tasks: [<Task pending coro=<Node.handle_network_id_requests() running at /home/cburgdorf/Documents/hacking/ef/py-evm/p2p/service.py:141> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fd8d7e9a738>()]>>]
 WARNING  12-07 20:34:23              FullNode  Task <coroutine object Node.handle_network_id_requests at 0x7fd8d7e7a258> finished unexpectedly:
   DEBUG  12-07 20:34:23              FullNode  Task failure traceback
Traceback (most recent call last):
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/p2p/service.py", line 141, in _run_task_wrapper
    await awaitable
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/p2p/service.py", line 160, in _run_daemon_task_wrapper
    await awaitable
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/trinity/nodes/base.py", line 59, in handle_network_id_requests
    async for req in self.event_bus.stream(NetworkIdRequest):
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/venv/lib/python3.6/site-packages/lahja/endpoint.py", line 267, in stream
    raise e
  File "/home/cburgdorf/Documents/hacking/ef/py-evm/venv/lib/python3.6/site-packages/lahja/endpoint.py", line 261, in stream
    yield await queue.get()
  File "/usr/lib/python3.6/asyncio/queues.py", line 167, in get
    yield from getter
concurrent.futures._base.CancelledError

How was it fixed?
Don't reraise these exceptions.
Cute Animal Picture

Apparently, there's an issue with that under Python 3.7. Investigating...

Ok, weird. I can reproduce this on local master as well. But that makes me wonder why it worked just a couple of days ago with the last PR that was merged. :thinking:

@carver this fixes https://github.com/ethereum/py-evm/issues/1561 in Trinity

Ok, figured it out. Instead of re-raising the the exception we just catch it, cleanup and break. There seems to be a difference between Python 3.6 and Python 3.7 where the wait_for API would not work with Python 3.7 if we don't break but it kinda makes me wonder why it works with Python 3.6 without the break because it really seems logical to need it :)

Surprised to not see a test for this though... Is it something we can test?

We do have tests that already test that the cancellation works. It was just that previously we re-raised the cancellation exception. So, this change not breaking the existing tests should be good enough. Plus, I verified that it fixes the issue in Trinity. Adding test that verify that we do not re-raise exceptions would feel a little weird.

Adding test that verify that we do not re-raise exceptions would feel a little weird.

This surprised me, it seems very reasonable to me to add a test that shows execution completes without an exception. This isn't a :-1: on the PR, just a general note.


When I use certain tools, I occasionally get printing exceptions.

Windows Terminal version
1.19.10821.0
Windows build number
10.0.22631.3296
Other Software
When I use the latest version of nuclei to scan a target, printing exceptions may occur.

Steps to reproduce
nuclei -u url
Expected Behavior
Normally, each piece of information should be output from the beginning of a line.

Actual Behavior
In fact, in some cases, several grids will be added before the printed text.

GitHub.com
Marques A Ware Sr
On Tue, Apr 30, 2024, 6:10 AM Mike Griese @.***> wrote:

Does this repro if you run nuclei in the vintage console, conhost.exe,
instead of the Terminal/?
This looks to me like either a newline mode not being set right, or
someone only emiting \n and not \r\n, or something like that.
(I see projectdiscovery/nuclei#5122
https://github.com/projectdiscovery/nuclei/issues/5122 filed upstream,
they may have a better ability to debug here)
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/17159#issuecomment-2085011346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEB3USTKCMF3CYYTYXHWIXLY7533VAVCNFSM6AAAAABG7YM7U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBVGAYTCMZUGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

GitHub.com Marques A Ware Sr
…
On Tue, Apr 30, 2024, 6:10 AM Mike Griese @.> wrote: Does this repro if you run nuclei in the vintage console, conhost.exe, instead of the Terminal/? This looks to me like either a newline mode not being set right, or someone only emiting \n and not \r\n, or something like that. ------------------------------ (I see projectdiscovery/nuclei#5122 <projectdiscovery/nuclei#5122> filed upstream, they may have a better ability to debug here) — Reply to this email directly, view it on GitHub <#17159 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEB3USTKCMF3CYYTYXHWIXLY7533VAVCNFSM6AAAAABG7YM7U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBVGAYTCMZUGY . You are receiving this because you are subscribed to this thread.Message ID: @.>

This problem will also occur when using the original cmd to execute nuclei, and it may not be a terminal problem.

This problem will also occur when using the original cmd to execute nuclei, and it may not be a terminal problem.

Thanks for confirming! Since that's the case, I'd reckon it's not a terminal bug. I'll close this in favor of the upstream bug. Thanks!
/dup https://github.com/projectdiscovery/nuclei/issues/5122


Allow primitive response types for operations

Right now, only objects and arrays are allowed as responseModel types, but there are many APIs where a raw data type is return, such as a string or number.  Would it be possible to implement this?  I believe old guzzle service descriptions allowed that.

Closing. See comment on #74.


BUG:Book Reccomendation text cannot be Read

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

pls assign it to me

@Ketanop321 Assigned!
Make sure to attach before & after screenshots in your PR. Also, star the repo before working on it. While creating your PR, ensure you pull all existing changes beforehand to avoid conflicts.
Happy open-source contributing!


Implement DeferredResult

@rmjohnson this should be ready for review

@rmjohnson ok NOW it should be ready for review. Had a heck of a time getting the freaking standard version release bot to work but now this should be up to date with all that


Add more functions

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (03ac327) 100.00% compared to head (a774bfb) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #564   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           24        24
  Lines         2068      2076    +8
  Branches       263       263
=========================================
+ Hits          2068      2076    +8

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


[FEATURE] Create About section

Detailed description
If you click on the About Tab you will only see About without fully details.
but there is About Section on the page, is just to link the About tab to the section on page.
Context
-- Give new visitor a brief of what the website is all about
-- click on the About Tab to link to the section
-- Help others to easily navigate
Possible implementation
No response
Additional information
No response
Code of Conduct

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

I can work on this

Sure, i am assigning this issue to you.

Thanks

hi @kabir0x23 . I'd like to work on this issue. Can you assign it to me?

hi @kabir0x23 . I'd like to work on this issue. Can you assign it to me?

this issue has already been assigned to @yhoungdev
you can work on #31 this issue
Thank you


[Suggestion] It would be better if the locations below "Recommended" and "Other" are sorted respectively with the first letter

OS: All
Build Version: 20210518.3
Repro Steps:

Create an advanced web app -> Select a location for new resources.
Check the location list.

Actual:
Locations are not sorted.

Suggestion:
It would be better if the locations below "Recommended" and "Other" are sorted respectively with the first letter.

We're using the sorting provided to us in the ARM api call, which matches what the portal does when creating a resource group. I'm pretty sure they have some sort of smart sorting based on which regions they want people to use. If we sort alphabetically a ton of people will end up creating stuff in Australia East, which doesn't really make sense to me.


Change text input placeholder

My application is in french and I woul like to add a custom placeholder for the message input but I currently cannot (or I haven't found how to and this is pretty frustating.
The way I see this being implemented is with a simple prop input-placeholder of type String to the ChatWindow component.
This:

Would become like this after modification:

And an example of it being used:
    <chat-window :input-placeholder:"'Votre message'" :current-user-id="currentUserId" :rooms="rooms" :messages="messages" @fetch-messages="getMessages"
      @add-room="addRoom" :show-files="false" :show-audio="false" :height="'800px'" :load-first-room="false"
      :loading-rooms="loadingRooms" :rooms-loaded="roomsLoaded" :messages-loaded="messagesLoaded"
      :show-new-messages-divider="false" />```

You can use text-messages prop:
text-messages="{
  TYPE_MESSAGE: 'Tapez votre message',
}"


Define convenient socket options

Provided a slightly nicer and easier-to-use way of accessing socket options.
Motivation:
Socket options were very verbose to set, and difficult to find if you didn't know the exact spelling, prefix, etc. Old usage: ChannelOptions.socket(SOL_SOCKET, SO_REUSEADDR)
Modifications:
Created wrapper options in ChannelOptions.swift. New method of use: ChannelOptions.Socket.allowLocalAddressReuse
Result:
Deprecated the old method, with a recommendation to use the new.

@Lukasa yep, apologies I didn't mark as WIP. We have a meeting later today to discuss the exact API.

Shutting this down as a result of our meeting


Do not discard build services that are build event listeners after storing configuration cache entry

Fixes #?
Context
Build event listeners may also collect configuration time metrics, so do not discard them after configuration time.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation

@bot-gradle test and merge

OK, I've already triggered a build for you.


feat: lalrpop lexer prototype

Description
Problem*
Resolves https://github.com/noir-lang/noir/issues/4655
Summary*
NOTE: I've added CC0-1.0 to deny.toml. Its purpose is to release work to the public domain.
TL;DR
lalrpop generates a part of a parser for our grammar and the noirc_frontend/experimental_parser feature can be used to run it alongside the existing parser: when the existing chumsky parser succeeds, the lalrpop parser is run and the results compared.
Detail
Run with cargo test --features=noirc_frontend/experimental_parser
Originally investigating lalrpop for lexing, now for parsing:

lalrpop doesn't handle string literals with escape characters well

this is due to how LR(1) parsers handle context
I realized this after discovering that all of the larger examples (solidity, python, etc) use the lexer to handle strings

pivoted this PR to use our existing lexer

this entailed a version of Token without String so that e.g. Token::Str("hi") can be matched on. (which is essential to lalrpop)
currently using a shim to minimize impact to the rest of the code:

conversion to/from SpannedToken
lexing the whole input into a Vec and using iter() to feed token lifetimes to lalrpop

current state:

WIP parsing use statements (missing support for recursive statements)
unit tests for use statements test lalrpop parser
feature flag experimental_parser enables running the experimental parser on every part of the AST that's successfully parsed with the existing chomsky parser

Changes:

Now rejecting whitespace other than \t \n\r

Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

@TomAFrench I went through the TODO's and cleaned up: the last remaining one is marking the place to continue the parser


feature/120_pr_template

Before merging, determine which of the templates are useful or if we want to go with the generic vs bump-version uption. The following checklist is to decide which templates we'll keep:

[ ] PULL_REQUEST_TEMPLATE/bug-pull-request.md
[ ] PULL_REQUEST_TEMPLATE/feature-pull-request.md
[ ] PULL_REQUEST_TEMPLATE/generic-pull-request.md
[ ] PULL_REQUEST_TEMPLATE/release-pull-request.md

@astrochun the templates are ready for your review.

@damian-romero I've implemented a few changes to clean it up. You can view how it will look here


[ha-agent] Add haagent component

What does this PR do?
[ha-agent] Add haagent component that will be used for HA Agent feature.
Motivation
haagent component is needed for High Availability Agent project.
Describe how to test/QA your changes
This component doesn't do anything as it, it will be used by follow-up PRs:
https://github.com/DataDog/datadog-agent/pull/31156
https://github.com/DataDog/datadog-agent/pull/31172
https://github.com/DataDog/datadog-agent/pull/31186
Right now, assessing that agent still start normally is enough.
Possible Drawbacks / Trade-offs
Additional Notes

@DataDog/documentation can I have a review for this PR ?

/merge


(placeholder) support additional stablecoin liquidity

Goals

Retain TVL outflows from USDC in Connext TVL
Diversify risk (worstcase scenario)
Support users with more asset optionality (ex/ Gnosis requested DAI and USDT

Proposed Solution
We should at least support USDT given it is twice the TVL of USDC at this point
https://defillama.com/stablecoins
Options
Option 1: Multi-asset Pools
ex/ USDC-USTC-DAI Pool (New)
https://curve.fi/#/ethereum/pools/3pool/deposit
https://synapseprotocol.com/pools/polygonnusd
Option 2: Separate Pools
ex/ USDC Pool (Existing) ||  USDT Pool (New) || DAI Pool (New)
This follows the same design
Questions for each
How does this impact existing Transfer stableswap functionality?  What changes are needed?
How does this impact existing Pool stableswap functionality?  What changes are needed?
How does this impact existing Pool liquidity? What does migration look like?
How does this impact existing Router liquidity? What does migration look like?
Acceptance Criteria
From an end tester and/or user perspective, the below criteria must be met to consider this done:

[ ] X happens

P1 for basic spec here to get back to Gnosis

Can we start by just analyzing what it would take for a 3pool?

decided -- support now without multiasset


when I train coco format dataset,I meet a bug.

When the image only have one object box，the CrowdDet will meet a error.
I also use original format dataset,using a image with one object,while the CrowdDet also meets the error.

Let me have a look. So far, this code has not been tested on coco. After fixing it, I will update the code.

I modify the line 5035 in the annotation_train.odgt as follow which means there is only one object in the image.
'
{"ID": "273278,c97af0004011f393", "gtboxes": [ {"tag": "person", "hbox": [224, 212, 98, 130], "head_attr": {"ignore": 0, "occ": 0, "unsure": 0}, "fbox": [-71, 136, 471, 839], "vbox": [0, 136, 400, 764], "extra": {"box_id": 4, "occ": 0}}]}
'
then there is the bug.

I will fix it and update the code in a few days. The code is now being refactored.

#12 could also solve the problem.

@ZJU-lishuang If you still have the code that loads in the COCO format data, could you please send it to me?


[feature request] - Adding interface to include location data from other moving objects in the scheduling

For an holistic traffic management it would be great to incorporate also location data of other moving objects (pallets, forklifts, people) in the scheduling | planing process

the VDA5050 protocol is a interface between the AGV and MasterControl, you could use fake AGV for you palles/objeckts or use an other channel fot this information

Yes. Having an data feed based on the open-locating standard  can been used, like some vendors already do. But in principle it would be great having the master control beeing able to distribute order also to non-AGVs (like fork lifts or even humans)


DDS create_datareader

PIM implementation of create_datareader
PIM implementation of delete_datareader
PIM unit tests for create and delete datareader
Unit testing including delete_subscriber failing if there is a datareader alive
Adaptation of testcases and examples to delete datareaders and subscribers and topics before deleting participants
PSM implementation of datareader constructor
PSM unit tests for datareader constructor
Testcase to ensure a Topic cannot be removed if there is a datareader using it

**Must be merged after #1153 **

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows


Only do routing hack on the web as it breaks hot reload functionality

I believe that fixes #1

Fixed in #8 by simplifying routing.


chore(ui): adjust wording on LndConnect tab

Description:
Rename Node URI to LndConnect since that is more accurate to what it actually is.
Motivation and Context:
Fix #1771
How Has This Been Tested?
Manually
Types of changes:
UI Enhancement
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 21.363% when pulling 14e6d1bbb39a2138a6a93dd00cea4dc63bd6ff1a on mrfelton:chore/copy-tweak-lndconnect into 3421faafee6cebd123fde9a05e1b2762adf842a5 on LN-Zap:next.

Coverage remained the same at 21.363% when pulling 14e6d1bbb39a2138a6a93dd00cea4dc63bd6ff1a on mrfelton:chore/copy-tweak-lndconnect into 3421faafee6cebd123fde9a05e1b2762adf842a5 on LN-Zap:next.