Bumping branch protection wait as heroku was faster than expected

Description of Changes

Heroku gets the event significantly faster than local via ngrok, so I'm bumping the wait to prevent 404s because the repo branch hasn't been created yet.
Related Issues

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   94.33%   94.33%
=======================================
  Files           6        6
  Lines          53       53
  Branches        3        3
=======================================
  Hits           50       50
  Partials        3        3

Impacted Files
Coverage Δ

src/api/webhook/repository.ts
92.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


split Dockerfile build into two stages

One stage for building, one for the runtime. This enables near-instantaneous builds of source only changes

@kentbull This is great and speeds up the testing flow a great deal. Do you have any plans to merge this?

Though I don't have merge access it would be nice if this was merged.

I am using a different structure than this and have some thoughts... Do you need to use venv and a multi stage build to achieve this? I suggest keeping the single stage build and only separate the dependency and source with layers.
I suggest to use something like this:
FROM python:3.10.4-alpine3.16

RUN apk update && apk add --no-cache alpine-sdk libffi-dev libsodium libsodium-dev bash && curl https://sh.rustup.rs -sSf | bash -s -- -y

WORKDIR /keria
COPY requirements.txt setup.py /keria/
RUN mkdir /keria/src
RUN source "$HOME/.cargo/env" && pip install -r requirements.txt

COPY src/ src/
COPY scripts/keri/ scripts/keri/

ENTRYPOINT [ "keria" ]
CMD ["keria", "start",  "--config-file", "demo-witness-oobis", "--config-dir", "./scripts"]

Arguably, the config with hard coded witness oobis should be left out and provided by whoever starts the image. But that could wait.

The codecov failures are not accurate here, going to merge.


Allow for returning simple array of input/output variable names from modelSpec

Currently the UserConfig.modelSpec function is expected to return full InputSpec[] and OutputSpec[] arrays.
The InputSpec interface in particular has some required properties (defaultValue, minValue, maxValue) that are not strictly needed when generating a model, and are only provided for use by other plugins (specifically plugin-check, for the purposes of building a default model-check bundle that is capable of setting inputs to their default, min, and max values.
The OutputSpec interface currently only contains a single property, varName.
For projects (like some simple example apps) that aren't using plugin-config or plugin-check, it's inconvenient to have to provide full InputSpec and OutputSpec instances.  For these simple cases, it would be sufficient to provide an array of input and output variable names.
I will change the ModelSpec type as follows:

The following diff shows how this change will simplify the config file for the new house-game example:

As part of this, I made a few small changes to the build package APIs (which should have no impact on existing projects or plugins):

Added ResolvedModelSpec interface; we now pass a ResolvedModelSpec to the plugin callback functions instead of a plain ModelSpec.

Changed the InputSpec interface to make the defaultValue, minValue, and maxValue properties optional.

Changed the ModelSpec interface to make the datFiles property optional (this no longer needs to be specified for projects that don't use dat files).

Also, one small behavior change to the plugin-check package:

The default bundle template will skip inputs that don't have the defaultValue, minValue, or maxValue properties set in the InputSpec and will warn the user.  This shouldn't happen too much because most projects will provide these values (i.e., via plugin-config).


Continued motion to move stuff out of root - solution.prop

Summary of the Pull Request
Moving solution.prop to src folder where other props are

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

@jay-o-way. Why the thumbs down?

Hi, we've added the "Don't Merge" tag to the PR, since we're trying to keep the repo stable for the release and possible hotfix if necessary. Please don't merge the PR while the tag is still in here. This allows people to review the PR and approve with less fear that it'll get merged 😄


Allow option to disable the Theme's alternative checkboxes.

Is your feature request related to a problem? Please describe.
I have incorporated the alternative checkboxes from Minimal, LYT Mode, AnuPpuccin, and ITS themes all via css snippets, and I have to comment out the minimal theme's checkboxes in order to get them to work like I would like.
Describe the solution you'd like
All I need is a setting to turn off the theme's alternative checkboxes so I can re-incorporate them via a snippet. This allows me to synthesize several sets of alternative checkboxes into one cohesive set.

this can be achieved by adding more specificity to your snippet


Updated the README.md to include swift

Including Swift in the metadata to be parsed by http://esri.github.io
@dg0yal Please verify

This is good.


Jwt support for cloudflare access

This PR intents to expand the support of JWT authentication to Cloudflare Access service.
Changes summary:

Fixing configuration parsing

Fixup includes test for claims parsing

Adding specific validation for audience due to the JWT spec allowing the audience claim to be a an array
Removing convey in JWT tests to align with Grafana's contribution guideline
Adding testing with Cloudflare Access test tokens and keys

Hi @jregistr ,
First, good work you and @ryantxu put into this!
I'm looking into adding support to Cloudflare Access and what you already had was just a few steps away of allowing that therefore I'm looking to contribute with you guys to get it into Grafana's mainline.
I will probably add some more contributions like:

configuration tests
test data relocation (like it is done in pkg/setting)

Looking forward to hear from you!

Amazing!
Thank you for this!
Have you tried this change against Google IAP?

Just with the unit tests that were already there.
I’m going to setup a test and give it try.

Hey @jregistr !
I finally had time to setup Google IAP and test, and it looks good:


ADD: chirpstack integration

The prerequisite part is the same for all the integrations, maybe we should consolidate it.

Yes there is indeed a lot of duplication. We can refactor the documents at a later stage. For now it's more important having this information out there for people to use. Thanks for writing this!


git-commit-id-plugin plugin causes error when git worktree feature is used.

Using Git Worktree feature is useful to juggle multiple branches and tags.
However the path for all the Git metadata and directories is not always present. When working in a worktree path.
For example a mvn package goal will fail due to the git-commit-id-plugin throwing an error.
[ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.0:revision (get-the-git-infos) on project qDup: Could not complete Mojo execution...: Error: Missing unknown 1fc7ef9fc818e5a6edff7a1b059375ce8a9c3ac7 -> [Help 1]

We use this to embed the commit hash in the java code. Is there a different way to capture the git hash?

by creating the worktree in the folder worktrees allows the worktree branch to work as expected with Git.


Stroke for barplot

As in the title.
It would be nice to add a stroke attribute to barplot

What's it supposed to be doing?

This issue is known...sadly we had to take away stroke from rectangle scatter, which barplot uses under the hood :D Maybe we should just use poly! for the barplot recipe

Should be fixed in: https://github.com/JuliaPlots/AbstractPlotting.jl/pull/331


Update docs.ms targeting during release

This PR adds the necessary scripting and yml. Still will require a PR to enable.
Originally, I had this script as a single function for reach of the paths with conditionals to change which property is accessed, etc. I'll take the structural duplication for clarity during the actual run though.
Update 7/28. Updated for json configs. Remove update-docs-ci.yml. About to rename update-docs-metadata.yml to update-docs-ci.yml
One other important thing to mention is we are leaving the "build up all the readme updates" in favor of "all the updates to do with single package".
Java

[x] Test Release
[x] PR Checks Out

.NET

[x] Test Release
[x] PRs Check Out. (metadata) (ci-onboarding)

~~Discovered complications here. Need to submit the PR for the readme updates, then handle the CI updates on a different branch, given that I can't update the .NET CI Job to do what we do. ~~
JavaScript

[x] Test Release
[x] PR Submits Properly

Python

[x] Test Release
[x] PR Submits Properly

Goal is to execute a template release for all, merge the PR, then do another pass to actually enable across the board. (with synced eng/common instead of copied)
Also discovered an issue with codeowners that I am tackling after the .NET issue is addressed.
@Azure/azure-sdk-eng

Last piece of confirmation. without updating archtype-<language>-release in the local repos, releases are still g2g.
Python
.NET
I judge this to be enough testing, as the "changeless" releases are extremely similar for python, java, and js. .NET I specifically tested because it makes use of the onboardingbranch argument, and I wanted to ensure that none of that templating logic breaks if we don't take advantage of it.

/check-enforcer override


"Logrești" is listed in the drop-down menu

Description:
"Logrești" is listed in the drop-down menu alongside its corresponding county, according to the law
Precondition:
The website is up an running.

Step 1
Type "Logrești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Logrești, GORJ".

ENVIRONMENT: ui.orase
URL: https://peviitor-ro.github.io/ui.orase/
Browser: Google Chrome
Device: Laptop
OS: Windows 10 Pro
STEPS TO REPRODUCE:
Open URL in browser.
Type "Logrești" in the search bar.
EXPECTED RESULTS:
The location is listed in the drop-down menu as "Comuna Logrești, GORJ".
ACTUAL RESULTS:
"Comuna Logrești, GORJ" is missing in the drop-down menu.

Fixed! Poti sa retestezi

@ElenaColonel please retest

@ElenaColonel please remove the bug and FAIL labels and put the label PASS if the TC is PASS


Failure on ppc using gcc

[ 1867s] Consider output of recursively compiled program: with space
[ 1867s] Comparing output of 'with space/Space Main.py' using '/usr/bin/python3' with flags silent, expect_success, plugin_enable:pylint-warnings, remove_output, recurse_all, original_file, two_step_execution ...
[ 1882s] Running the package tests with options '' with python3.8:
[ 1882s] Run '/usr/bin/python3 ./tests/packages/run_all.py search' in '/home/abuild/rpmbuild/BUILD/Nuitka-<IP_ADDRESS>'.
[ 1882s] Using concrete python 3.8.5 on ppc64le
[ 1882s] Consider output of recursively compiled package: sub_package
[ 1883s] Comparing output of 'sub_package/kitty' using '/usr/bin/python3' with flags silent, expect_success, remove_output, module_mode, two_step_execution, ignore_warnings ...
[ 1898s] GNU gdb (GDB; openSUSE Tumbleweed) 9.2
[ 1898s] Copyright (C) 2020 Free Software Foundation, Inc.
[ 1898s] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[ 1898s] This is free software: you are free to change and redistribute it.
[ 1898s] There is NO WARRANTY, to the extent permitted by law.
[ 1898s] Type "show copying" and "show warranty" for details.
[ 1898s] This GDB was configured as "ppc64le-suse-linux".
[ 1898s] Type "show configuration" for configuration details.
[ 1898s] For bug reporting instructions, please see:
[ 1898s] <http://bugs.opensuse.org/>.
[ 1898s] Find the GDB manual and other documentation resources online at:
[ 1898s]     <http://www.gnu.org/software/gdb/documentation/>.
[ 1898s]
[ 1898s] For help, type "help".
[ 1898s] Type "apropos word" to search for commands related to "word"...
[ 1898s] Reading symbols from /usr/bin/python3...
[ 1898s] (No debugging symbols found in /usr/bin/python3)
[ 1898s] Starting program: /usr/bin/python3 -W ignore -c import\ kitty
[ 1898s] [Thread debugging using libthread_db enabled]
[ 1898s] Using host libthread_db library "/lib64/libthread_db.so.1".
[ 1898s]
[ 1898s] Program received signal SIGSEGV, Segmentation fault.
[ 1898s] 0x00007ffff74bbc6c in ?? () from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 1898s] #0  0x00007ffff74bbc6c in ?? ()
[ 1898s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 1898s] #1  0x00007ffff748e26c in ?? ()
[ 1898s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 1898s] #2  0x00007ffff7d78744 in _PyImport_LoadDynamicModuleWithSpec ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #3  0x00007ffff7d78158 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #4  0x00007ffff7c829b4 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #5  0x00007ffff7c921dc in PyVectorcall_Call ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #6  0x00007ffff7c71d04 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #7  0x00007ffff7c69984 in _PyEval_EvalCodeWithName ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #8  0x00007ffff7c820e8 in _PyFunction_Vectorcall ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #9  0x00007ffff7c70cf0 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #10 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #11 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #12 0x00007ffff7c6bff4 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #13 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #14 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #15 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #16 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #17 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #18 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #19 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #20 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #21 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #22 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #23 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #24 0x00007ffff7c81a74 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #25 0x00007ffff7c94a3c in _PyObject_CallMethodIdObjArgs ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #26 0x00007ffff7c93874 in PyImport_ImportModuleLevelObject ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #27 0x00007ffff7c705c0 in _PyEval_EvalFrameDefault ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #28 0x00007ffff7c69984 in _PyEval_EvalCodeWithName ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #29 0x00007ffff7c695b0 in PyEval_EvalCodeEx ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #30 0x00007ffff7d4001c in PyEval_EvalCode ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #31 0x00007ffff7d5394c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #32 0x00007ffff7d49cbc in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #33 0x00007ffff7d45214 in PyRun_StringFlags ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #34 0x00007ffff7d450fc in PyRun_SimpleStringFlags ()
[ 1898s]    from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #35 0x00007ffff7d6a76c in Py_RunMain () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #36 0x00007ffff7d28c84 in Py_BytesMain () from /usr/lib64/libpython3.8.so.1.0
[ 1898s] #37 0x0000000100000a38 in main ()
[ 1898s] A debugging session is active.
[ 1898s]
[ 1898s] 	Inferior 1 [process 10014] will be killed.
[ 1898s]
[ 1898s] Quit anyway? (y or n) [answered Y; input not from terminal]
[ 1898s] --- /usr/bin/python3 (stdout)
[ 1898s] +++ nuitka (stdout)
[ 1898s]
[ 1898s] @@ -1,6 +1 @@
[ 1898s]
[ 1898s] -__name__ is kitty
[ 1898s] -__package__ is kitty
[ 1898s] -From sys.modules <module 'kitty' from 'xxxxx'>
[ 1898s] -__loader__ present: True
[ 1898s] -OK, kitty.speak loaded.
[ 1898s]
[ 1898s] Exit codes 0 (CPython) != -11 (Nuitka)
[ 1898s] Error, outputs differed.
[ 1898s] Error exit! 1
[ 1898s] error: Bad exit status from /var/tmp/rpm-tmp.7uZj6w (%check)

Using clang works well.

Can you try with gcc and --debug though, because this may just be undefined behaviour not hitting. It's happening right in Nuitka module code. If that crashes, or better asserts, I would like to know. Thanks for your reports!

Sure.  I have submitted Nuitka to the openSUSE main repo https://build.opensuse.org/request/show/827726 , so I will wait for that to finish before doing lots of extra builds to debug gcc.

Just to be clear, the bug would probably not be in gcc, but in Nuitka from the looks.

openSUSE now has Nuitka in the python area, and now https://build.opensuse.org/request/show/828246 on its way into the Factory .
Log of just running tests with export NUITKA_EXTRA_OPTIONS="--debug"  - not sure how helpful that is.
I'll add debug symbols now, and report back when it is done.
[ 2201s] Run '/usr/bin/python3 ./tests/packages/run_all.py search' in '/home/abuild/rpmbuild/BUILD/Nuitka-<IP_ADDRESS>'.
[ 2201s] Using concrete python 3.8.5 on ppc64le
[ 2201s] Consider output of recursively compiled package: sub_package
[ 2201s] Comparing output of 'sub_package/kitty' using '/usr/bin/python3' with flags silent, expect_success, remove_output, module_mode, two_step_execution, ignore_warnings ...
[ 2221s] GNU gdb (GDB; openSUSE Tumbleweed) 9.2
[ 2221s] Copyright (C) 2020 Free Software Foundation, Inc.
[ 2221s] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[ 2221s] This is free software: you are free to change and redistribute it.
[ 2221s] There is NO WARRANTY, to the extent permitted by law.
[ 2221s] Type "show copying" and "show warranty" for details.
[ 2221s] This GDB was configured as "ppc64le-suse-linux".
[ 2221s] Type "show configuration" for configuration details.
[ 2221s] For bug reporting instructions, please see:
[ 2221s] <http://bugs.opensuse.org/>.
[ 2221s] Find the GDB manual and other documentation resources online at:
[ 2221s]     <http://www.gnu.org/software/gdb/documentation/>.
[ 2221s]
[ 2221s] For help, type "help".
[ 2221s] Type "apropos word" to search for commands related to "word"...
[ 2221s] Reading symbols from /usr/bin/python3...
[ 2221s] (No debugging symbols found in /usr/bin/python3)
[ 2221s] Starting program: /usr/bin/python3 -W ignore -c import\ kitty
[ 2221s] [Thread debugging using libthread_db enabled]
[ 2221s] Using host libthread_db library "/lib64/libthread_db.so.1".
[ 2221s]
[ 2221s] Program received signal SIGSEGV, Segmentation fault.
[ 2221s] 0x00007ffff74bbc6c in ?? () from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 2221s] #0  0x00007ffff74bbc6c in ?? ()
[ 2221s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 2221s] #1  0x00007ffff748e26c in ?? ()
[ 2221s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[ 2221s] #2  0x00007ffff7d78744 in _PyImport_LoadDynamicModuleWithSpec ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #3  0x00007ffff7d78158 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #4  0x00007ffff7c829b4 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #5  0x00007ffff7c921dc in PyVectorcall_Call ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #6  0x00007ffff7c71d04 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #7  0x00007ffff7c69984 in _PyEval_EvalCodeWithName ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #8  0x00007ffff7c820e8 in _PyFunction_Vectorcall ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #9  0x00007ffff7c70cf0 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #10 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #11 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #12 0x00007ffff7c6bff4 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #13 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #14 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #15 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #16 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #17 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #18 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #19 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #20 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #21 0x00007ffff7c6bbc0 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #22 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #23 0x00007ffff7c8259c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #24 0x00007ffff7c81a74 in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #25 0x00007ffff7c94a3c in _PyObject_CallMethodIdObjArgs ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #26 0x00007ffff7c93874 in PyImport_ImportModuleLevelObject ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #27 0x00007ffff7c705c0 in _PyEval_EvalFrameDefault ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #28 0x00007ffff7c69984 in _PyEval_EvalCodeWithName ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #29 0x00007ffff7c695b0 in PyEval_EvalCodeEx ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #30 0x00007ffff7d4001c in PyEval_EvalCode ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #31 0x00007ffff7d5394c in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #32 0x00007ffff7d49cbc in ?? () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #33 0x00007ffff7d45214 in PyRun_StringFlags ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #34 0x00007ffff7d450fc in PyRun_SimpleStringFlags ()
[ 2221s]    from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #35 0x00007ffff7d6a76c in Py_RunMain () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #36 0x00007ffff7d28c84 in Py_BytesMain () from /usr/lib64/libpython3.8.so.1.0
[ 2221s] #37 0x0000000100000a38 in main ()
[ 2221s] A debugging session is active.
[ 2221s]
[ 2221s] 	Inferior 1 [process 9606] will be killed.
[ 2221s]
[ 2221s] Quit anyway? (y or n) [answered Y; input not from terminal]
[ 2221s] --- /usr/bin/python3 (stdout)
[ 2221s] +++ nuitka (stdout)
[ 2221s]
[ 2221s] @@ -1,6 +1 @@
[ 2221s]
[ 2221s] -__name__ is kitty
[ 2221s] -__package__ is kitty
[ 2221s] -From sys.modules <module 'kitty' from 'xxxxx'>
[ 2221s] -__loader__ present: True
[ 2221s] -OK, kitty.speak loaded.
[ 2221s]
[ 2221s] Exit codes 0 (CPython) != -11 (Nuitka)
[ 2221s] Error, outputs differed.
[ 2221s] Error exit! 1

Logs at https://build.opensuse.org/package/show/home:jayvdb:branches:devel:languages:python/python-Nuitka
[  791s] Reading symbols from /usr/bin/python3...
[  791s] Reading symbols from /usr/lib/debug/usr/bin/python3.8-3.8.5-1.2.ppc64le.debug...
[  791s] Starting program: /usr/bin/python3 -W ignore -c import\ kitty
[  791s] [Thread debugging using libthread_db enabled]
[  791s] Using host libthread_db library "/lib64/libthread_db.so.1".
[  791s]
[  791s] Program received signal SIGSEGV, Segmentation fault.
[  791s] 0x00007ffff74bbc6c in ?? () from /var/tmp/packages/python3.8-nodebug/kitty.so
[  791s] #0  0x00007ffff74bbc6c in ?? ()
[  791s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[  791s] #1  0x00007ffff748e26c in ?? ()
[  791s]    from /var/tmp/packages/python3.8-nodebug/kitty.so
[  792s] #2  0x00007ffff7d78744 in _PyImport_LoadDynamicModuleWithSpec (
[  792s]     spec=<ModuleSpec(name='kitty', loader=<ExtensionFileLoader(name='kitty', path='/var/tmp/packages/python3.8-nodebug/kitty.so') at remote 0x7ffff755cdc0>, origin='/var/tmp/packages/python3.8-nodebug/kitty.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x7ffff755cd60>, fp=<optimized out>) at ./Python/importdl.c:164
[  792s] #3  0x00007ffff7d78158 in _imp_create_dynamic_impl (module=<optimized out>,
[  792s]     file=<optimized out>,
[  792s]     spec=<ModuleSpec(name='kitty', loader=<ExtensionFileLoader(name='kitty', path='/var/tmp/packages/python3.8-nodebug/kitty.so') at remote 0x7ffff755cdc0>, origin='/var/tmp/packages/python3.8-nodebug/kitty.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x7ffff755cd60>) at Python/import.c:2185
[  792s] #4  _imp_create_dynamic (module=<optimized out>, args=<optimized out>,
[  792s]     nargs=<optimized out>) at Python/clinic/import.c.h:330
[  792s] #5  0x00007ffff7c829b4 in cfunction_vectorcall_FASTCALL (
[  792s]     func=<built-in method create_dynamic of module object at remote 0x7ffff7697090>, args=<optimized out>, nargsf=<optimized out>, kwnames=<optimized out>)
[  792s]     at Objects/methodobject.c:422
[  792s] #6  0x00007ffff7c921dc in PyVectorcall_Call (
[  792s]     callable=<built-in method create_dynamic of module object at remote 0x7ffff7697090>, tuple=<optimized out>, kwargs=<optimized out>) at Objects/call.c:205
[  792s] #7  0x00007ffff7c71d04 in do_call_core (kwdict={},
[  792s]     callargs=(<ModuleSpec(name='kitty', loader=<ExtensionFileLoader(name='kitty', path='/var/tmp/packages/python3.8-nodebug/kitty.so') at remote 0x7ffff755cdc0>, origin='/var/tmp/packages/python3.8-nodebug/kitty.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x7ffff755cd60>,),
[  792s]     func=<built-in method create_dynamic of module object at remote 0x7ffff7697090>, tstate=<optimized out>) at Python/ceval.c:4983
[  792s] #8  _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3559
[  792s] #9  0x00007ffff7c69984 in PyEval_EvalFrameEx (throwflag=0,
[  792s]     f=Frame 0x7ffff755ba60, for file <frozen importlib._bootstrap>, line 219, in _call_with_frames_removed (f=<built-in method create_dynamic of module object at remote 0x7ffff7697090>, args=(<ModuleSpec(name='kitty', loader=<ExtensionFileLoader(name='kitty', path='/var/tmp/packages/python3.8-nodebug/kitty.so') at remote 0x7ffff755cdc0>, origin='/var/tmp/packages/python3.8-nodebug/kitty.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x7ffff755cd60>,), kwds={})) at Python/ceval.c:741
[  792s] #10 _PyEval_EvalCodeWithName (_co=<code at remote 0x7ffff76969d0>,
[  792s]     globals=<optimized out>, locals=<optimized out>, args=<optimized out>,
[  792s]     argcount=<optimized out>, kwnames=0x0, kwargs=0x7ffff7603b90,
[  792s]     kwcount=<optimized out>, kwstep=1, defs=0x0, defcount=0, kwdefs=0x0,
[  792s]     closure=0x0, name='_call_with_frames_removed',
[  792s]     qualname='_call_with_frames_removed') at Python/ceval.c:4298
[  792s] #11 0x00007ffff7c820e8 in _PyFunction_Vectorcall (func=<optimized out>,
[  792s]     stack=<optimized out>, nargsf=<optimized out>, kwnames=<optimized out>)
[  792s]     at Objects/call.c:441
[  792s] #12 0x00007ffff7c70cf0 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=<optimized out>, callable=<optimized out>)
[  792s]     at ./Include/cpython/abstract.h:130
[  792s] #13 call_function (kwnames=0x0, oparg=2, pp_stack=<synthetic pointer>,
[  792s]     tstate=0x1000334f0) at Python/ceval.c:4963
[  792s] #14 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3469
[  792s] #15 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx (f=<optimized out>,
[  792s]     throwflag=<optimized out>) at Python/ceval.c:741
[  792s] #16 0x00007ffff7c8259c in function_code_fastcall (co=<optimized out>,
[  792s]     args=<optimized out>, nargs=2, globals=<optimized out>)
[  792s]     at Objects/call.c:289
[  792s] #17 0x00007ffff7c6bff4 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=<optimized out>,
[  792s]     callable=<function at remote 0x7ffff7653790>)
[  792s]     at ./Include/cpython/abstract.h:130
[  792s] #18 call_function (kwnames=0x0, oparg=<optimized out>,
[  792s]     pp_stack=<synthetic pointer>, tstate=0x1000334f0) at Python/ceval.c:4963
[  792s] #19 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3486
[  792s] #20 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx (f=<optimized out>,
[  792s]     throwflag=<optimized out>) at Python/ceval.c:741
[  792s] #21 0x00007ffff7c8259c in function_code_fastcall (co=<optimized out>,
[  792s]     args=<optimized out>, nargs=1, globals=<optimized out>)
[  792s]     at Objects/call.c:289
[  792s] #22 0x00007ffff7c6bbc0 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=<optimized out>, callable=<optimized out>)
[  792s]     at ./Include/cpython/abstract.h:130
[  792s] #23 call_function (kwnames=0x0, oparg=1, pp_stack=<synthetic pointer>,
[  792s]     tstate=0x1000334f0) at Python/ceval.c:4963
[  792s] #24 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3500
[  792s] #25 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx (f=<optimized out>,
[  792s]     throwflag=<optimized out>) at Python/ceval.c:741
[  792s] #26 0x00007ffff7c8259c in function_code_fastcall (co=<optimized out>,
[  792s]     args=<optimized out>, nargs=1, globals=<optimized out>)
[  792s]     at Objects/call.c:289
[  792s] #27 0x00007ffff7c6bbc0 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=<optimized out>, callable=<optimized out>)
[  792s]     at ./Include/cpython/abstract.h:130
[  792s] #28 call_function (kwnames=0x0, oparg=1, pp_stack=<synthetic pointer>,
[  792s]     tstate=0x1000334f0) at Python/ceval.c:4963
[  792s] #29 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3500
[  792s] #30 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx (f=<optimized out>,
[  792s]     throwflag=<optimized out>) at Python/ceval.c:741
[  792s] #31 0x00007ffff7c8259c in function_code_fastcall (co=<optimized out>,
[  792s]     args=<optimized out>, nargs=2, globals=<optimized out>)
[  792s]     at Objects/call.c:289
[  792s] #32 0x00007ffff7c6bbc0 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=<optimized out>, callable=<optimized out>)
[  792s]     at ./Include/cpython/abstract.h:130
[  792s] #33 call_function (kwnames=0x0, oparg=2, pp_stack=<synthetic pointer>,
[  792s]     tstate=0x1000334f0) at Python/ceval.c:4963
[  792s] #34 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:3500
[  792s] #35 0x00007ffff7c6b4a4 in PyEval_EvalFrameEx (f=<optimized out>,
[  792s]     throwflag=<optimized out>) at Python/ceval.c:741
[  792s] #36 0x00007ffff7c8259c in function_code_fastcall (co=<optimized out>,
[  792s]     args=<optimized out>, nargs=2, globals=<optimized out>)
[  792s]     at Objects/call.c:289
[  792s] #37 0x00007ffff7c81a74 in _PyObject_Vectorcall (kwnames=0x0,
[  792s]     nargsf=<optimized out>, args=0x7fffffffe720,
[  792s]     callable=<function at remote 0x7ffff76ad3a0>)
[  792s]     at ./Include/cpython/abstract.h:150
[  792s] #38 _PyObject_FastCall (nargs=<optimized out>, args=0x7fffffffe720,
[  792s]     func=<function at remote 0x7ffff76ad3a0>)
[  792s]     at ./Include/cpython/abstract.h:150
[  792s] #39 object_vacall (base=<optimized out>,
[  792s]     callable=<function at remote 0x7ffff76ad3a0>, vargs=<optimized out>)
[  792s]     at Objects/call.c:1192
[  792s] #40 0x00007ffff7c94a3c in _PyObject_CallMethodIdObjArgs (obj=0x0,
[  792s]     name=<optimized out>) at Objects/call.c:1250
[  792s] #41 0x00007ffff7c93874 in import_find_and_load (abs_name='kitty')
[  792s]     at Python/import.c:1698
[  792s] #42 PyImport_ImportModuleLevelObject (name='kitty', globals=<optimized out>,
[  792s]     locals=<optimized out>, fromlist=None, level=<optimized out>)
[  792s]     at Python/import.c:1798
[  792s] #43 0x00007ffff7c705c0 in import_name (level=0, fromlist=None, name='kitty',
[  792s]     f=Frame 0x7ffff7603800, for file <string>, line 1, in <module> (),
[  792s]     tstate=<optimized out>) at Python/ceval.c:5139
[  792s] #44 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
[  792s]     at Python/ceval.c:2993
[  792s] #45 0x00007ffff7c69984 in PyEval_EvalFrameEx (throwflag=0,
[  792s]     f=Frame 0x7ffff7603800, for file <string>, line 1, in <module> ())
[  792s]     at Python/ceval.c:741
[  792s] #46 _PyEval_EvalCodeWithName (_co=<code at remote 0x7ffff7579be0>,
[  792s]     globals=<optimized out>, locals=<optimized out>, args=<optimized out>,
[  792s]     argcount=<optimized out>, kwnames=0x0, kwargs=0x0,
[  792s]     kwcount=<optimized out>, kwstep=2, defs=0x0, defcount=0, kwdefs=0x0,
[  792s]     closure=0x0, name=0x0, qualname=0x0) at Python/ceval.c:4298
[  792s] #47 0x00007ffff7c695b0 in PyEval_EvalCodeEx (_co=<optimized out>,
[  792s]     globals=<optimized out>, locals=<optimized out>, args=<optimized out>,
[  792s]     argcount=<optimized out>, kws=<optimized out>, kwcount=<optimized out>,
[  792s]     defs=<optimized out>, defcount=0, kwdefs=0x0, closure=0x0)
[  792s]     at Python/ceval.c:4327
[  792s] #48 0x00007ffff7d4001c in PyEval_EvalCode (co=<optimized out>,
[  792s]     globals=<optimized out>, locals=<optimized out>) at Python/ceval.c:718
[  792s] #49 0x00007ffff7d5394c in run_eval_code_obj (co=co@entry=0x7ffff7579be0,
[  792s]     globals=globals@entry={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>},
[  792s]     locals=locals@entry={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>})
[  792s]     at Python/pythonrun.c:1125
[  792s] #50 0x00007ffff7d49cbc in run_mod (mod=mod@entry=0x100071e68,
[  792s]     filename=filename@entry='<string>',
[  792s]     globals=globals@entry={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>},
[  792s]     locals=locals@entry={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>},
[  792s]     flags=flags@entry=0x7fffffffeec0, arena=arena@entry=0x7ffff76ff7b0)
[  792s]     at Python/pythonrun.c:1147
[  792s] #51 0x00007ffff7d45214 in PyRun_StringFlags (str=<optimized out>,
[  792s]     start=<optimized out>,
[  792s]     globals={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>},
[  792s]     locals={'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <type at remote 0x1000444b0>, '__spec__': None, '__annotations__': {}, '__builtins__': <compiled_module at remote 0x7ffff768e090>},
[  792s]     flags=0x7fffffffeec0) at Python/pythonrun.c:1034
[  792s] #52 0x00007ffff7d450fc in PyRun_SimpleStringFlags (
[  792s]     command=0x7ffff76638c0 "import kitty\n", flags=0x7fffffffeec0)
[  792s]     at Python/pythonrun.c:460
[  792s] #53 0x00007ffff7d6a76c in pymain_run_command (cf=<optimized out>,
[  792s]     command=<optimized out>) at Modules/main.c:258
[  792s] #54 pymain_run_python (exitcode=0x7fffffffeeb8) at Modules/main.c:597
[  792s] #55 Py_RunMain () at Modules/main.c:685
[  792s] #56 0x00007ffff7d28c84 in Py_BytesMain (argc=<optimized out>,
[  792s]     argv=<optimized out>) at Modules/main.c:739
[  792s] #57 0x0000000100000a38 in main (argc=<optimized out>, argv=<optimized out>)
[  792s]     at ./Programs/python.c:16
[  792s] A debugging session is active.
[  792s]
[  792s] 	Inferior 1 [process 4189] will be killed.

I think, you should retry this once 0.6.10 is out, as I believe there was a bug that might have causes this, potentially even fixed in 0.6.9 already, but not so sure now.

I believe I tested this issue against 0.6.9 at the same time I was testing https://github.com/Nuitka/Nuitka/issues/809#issuecomment-708207171 . In any case, I will do a re-test on 0.6.10 .

Tested now, and all green.

Tested now, and all green.


Introduce abstract Annotation and AnnotationManager

This PR pulls some shared logic into a base class, this should improve maintainability of the generated code.

I like this changes! Also, looking through https://github.com/mapbox/mapbox-plugins-android/pull/685 where we need to add a lot of duplicating code to handle a different type of click - do you see an option here to generify the layer initialization and click resolvers as well? It seems like the only missing pieces in order to achieve that are layer/source IDs which could be provided with an abstract method.


mbedtls_ctr_drbg_set_entropy_len is redundant

Description

Type: Bug
Priority: Minor
The API mbedtls_ctr_drbg_set_entropy_len is redundant.
When a user calls mbedtls_ctr_drbg_seed , it calls mbedtls_ctr_drbg_seed_entropy_len with MBEDTLS_CTR_DRBG_ENTROPY_LEN as entropy len.
When a user calls mbedtls_ctr_drbg_seed_entropy_len, then they decide in this function what the entropy len is ( as the entropy_len in the context is overridden)

Both ways, mbedtls_ctr_drbg_set_entropy_len value is ignored
The only location where it is not ignored is if it is called before mbedtls_ctr_drbg_reseed , but in this case, it’s more dangerous for an error, by setting an invalid value, since it cannot exceed MBEDTLS_ENTROPY_BLOCK_SIZE
In addition, when calling mbedtls_ctr_drbg_reseed , it means that there was already a previous call to mbedtls_ctr_drbg_seed, and the entropy_len was already defined

Bug \ Enhancement
mbed TLS build:
Version: development
Expected behavior
Deprecate mbedtls_ctr_drbg_set_entropy_len function

ARM Internal Ref: IOTSSL-2318


How do I properly serialize Parse Objects in cloudcode BeforeSave?

if I have a Numeric field and increment it using the sdk something like
...
someTestClassQuery.find().then(function(results) {
 results[0].increment("MyNumericField");
 results[0].save();

and I have cloudcode something like:
Parse.Cloud.beforeSave("TestClass", function(request, response) {
var fieldValue=req.object.get('MyNumericField'); //this holds the expected field value, already incremented.

  var jsonBody = {};
  jsonBody.object = req.object.toJSON();
  jsonBody.object.className = req.object.className;

/*at this point,  jsonBody.object has lost its actual current value, and its replaced by an IncrementOp with a value of 1.

var unmarshalled = JSON.parse(jsonBody.object);
this object is not the same as  req.object.
var fieldValueb=req.object.get('MyNumericField'); returns IncrementOp, not value
*/

how should I properly marshall/unmarshall parse objects such that they maintain their integrity?
thanks

AFAIK That's unfortunately not possible with the current SDK's. The beforeSave has the client 'operations' and not the full values. an afterSave would have the proper values.
Also, possibly fixable with the internals of the JSSDK, if the operations are stored differently than the values.

See: https://github.com/ParsePlatform/Parse-SDK-JS/blob/master/src/ParseObject.js#L418

Hey, thanks for reporting this issue.
Can you please add all the info specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.


Use scitokens library rather than decode_token.sh

It turns out to be pretty straightforward, with one caveat: more exceptions from down below.
Pretty much if anything went wrong with decode-token.sh, you got an empty string back
with ValueError being the only exception you got back; the new one has a half dozen or
so exceptions, and validates tokens for expiration, etc. all the time.   Minimal code changes
for it, although the except Exception  bit in checkToken may be overly broad.

No, some of my comments are still open. I'd really prefer we leverage the functionality the library provides when possible.

LGTM

I'll just put in another pull request later to remove decode_token.sh

Sorry, I ended up just re-adding decode-token.sh, so the merge conflict went away, and submitted
a new pull request to get it back out.
--
Marc W. Mengel
Computer Services Senior Developer
Data Management and Applications
Fermi National Accelerator Laboratory
630 840 8256 office
www.fnal.gov
https://email.fnal.gov/owa/redir.aspx?C=JkVsWjSyHEuWV2kFJWNPyC9OyMKf7dEIp_yxPk9yfhfadE3mdLfI6T8Ztf8BVaJjzoIe8oJ5H0M.&URL=http%3A%2F%2Fwww.fnal.gov
Connect with us!
Newsletterhttps://email.fnal.gov/owa/redir.aspx?C=-29AtpIe40SAvGF4aiNr86KvVjap7dEIuxIdg8Q5bYa9sT7QTFVhxhVnl8zwXkEuBSuAQLRkEfg.&URL=http%3A%2F%2Fwww.fnal.gov%2Fpub%2Ftoday | Facebookhttps://email.fnal.gov/owa/UrlBlockedError.aspx | Twitterhttps://email.fnal.gov/owa/redir.aspx?C=-29AtpIe40SAvGF4aiNr86KvVjap7dEIuxIdg8Q5bYa9sT7QTFVhxhVnl8zwXkEuBSuAQLRkEfg.&URL=https%3A%2F%2Ftwitter.com%2FFermilabToday

From: Shreyas Bhat @.>
Sent: Wednesday, October 18, 2023 9:54 AM
To: fermitools/jobsub_lite @.>
Cc: Marc W Mengel @.>; Mention @.>
Subject: Re: [fermitools/jobsub_lite] Use scitokens library rather than decode_token.sh (PR #480)
@marcmengelhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_marcmengel&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=mA4qFs7Hfq-joWhWXnsXfA&m=Wroa3GL7Va5GYk_h7OCymMy-s9E6ur73zo2mAjbQbc4FWrQhpiSUOx-drYqf6O10&s=t1LwNOrikiitzsQSDKlW7mTII0BUQn5UKloMvH_l9HE&e= have you had a chance to take a look at this merge conflict? I think you'll just need to assert that deleting decode_token.sh is the right thing here.
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_fermitools_jobsub-5Flite_pull_480-23issuecomment-2D1768642023&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=mA4qFs7Hfq-joWhWXnsXfA&m=Wroa3GL7Va5GYk_h7OCymMy-s9E6ur73zo2mAjbQbc4FWrQhpiSUOx-drYqf6O10&s=btQakFdWH-Z_zbtPVMBZAfsL5bHkEhIirypnSbTLfng&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAB6GV77CMTKLE2YPHK7MQ3X77URPAVCNFSM6AAAAAA5M64M7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRYGY2DEMBSGM&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=mA4qFs7Hfq-joWhWXnsXfA&m=Wroa3GL7Va5GYk_h7OCymMy-s9E6ur73zo2mAjbQbc4FWrQhpiSUOx-drYqf6O10&s=kndYFbFBiMkXPFLyQMUvZ7gkwa73rAEhsqvrRe9AClQ&e=.
You are receiving this because you were mentioned.Message ID: @.***>

No problem - that works.


Package request: Lorien

Project description
Lorien is an infinite canvas drawing/note-taking app that is focused on performance, small savefiles and simplicity.
Metadata

homepage URL: https://github.com/mbrlabs/Lorien
source URL: https://github.com/mbrlabs/Lorien
license: mit
platforms: windows, linux, darwin

Add a :+1: reaction to issues you find important.

I've found a game with Godot that could be used as inspiration: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/games/oh-my-git/default.nix

Already packaged: https://search.nixos.org/packages?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=lorien


for features, labels in training_data:       2     x.append(features)       3     y.append(label)       4 x = np.array(x).reshape(-1, IMG_SIZE, IMG_SIZE, 1)  ValueError: not enough values to unpack (expected 2, got 1)

Does anyone know why I got this error while running that piece of code?

Thank you @tommieezpark for raising the issue. We'll need a little more information to help you with the issue.

Could you post the code before the error happen?

Is the code coming from somewhere, e.g. the NLTK book or some examples on the web? If so, where did you get it from?

Which version of NLTK are you using? Which Python version are you using?

Which OS are you using to run the code snippet?


Work Showcase Section - HTML/CSS

GIVEN I need to sample a potential employee's previous work
WHEN I click on the link to the section about their work
THEN the UI scrolls to a section with titled images of the developer's applications

This was addressed in a prior branch merge and functions as such


Over-weighted gate loss.

The MSE loss is averaged across the data dimensions. So the weight for each mel dimension loss is 1. / mel_dim. However the weight for the gate loss is 1. So the gate loss may be considered over-weighted.
If the weights for each mel dimension loss and the gate loss are modified to 1 / (mel_dim + 1.), the model will learn alignments in an earlier iteration.

@bfs18 how earlier does the model learn attention with this alteration to the loss?


research spike: what is best way to automate muun?

Someone who knows Java and/or android app development can figure it out.
Can we simply send requests to an api to do wallet actions?
https://github.com/muun/apollo

https://github.com/labcif/Tutorial-AndroidNetworkInterception


PUBLISHED and REJECTED

CVE Services 2.1 recently(?) changed state text PUBLIC-->PUBLISHED and REJECT-->REJECTED.
I'm testing cvelib and some other clients in advance of the October transition and a virtual workshop on 11/2.

Fixing(?) spaces in test_client.py so tests pass.

Ah, nice catch. We actually had commit https://github.com/RedHatProductSecurity/cvelib/commit/8f0967ecb96649d71b4527086fcd8f02de01bd75 on this branch but then it got reverted with a rebase from master :facepalm:
If you don't mind, I'll just re-revert that c1f5edeb2cb1a39dfbab1813a3bc68ae4c04661d commit instead of merging your change (it's essentially the same code change). I'll keep the cherry-picked commit with the note on the 2.1.0 branch though.

Done as 0a44aa4396e4a0f26e16a08a93124368d02570e5 and 132fe833fb0bcb073dd9586d9d97cf0304f9ba3f.


desmume: Add version 0.9.13

Closes #7158

[x] I have read the Contributing Guide.

the sourceforge package is still 0.9.11 out of date

/verify

The manifest works fine, but I think this should go to the Games bucket.

https://github.com/Calinou/scoop-games/pull/684


NumberInput interface needs an on_change event

Looking into this but I need some help.

Do you still need some help @voltagex ?

Yep. I will have some time to look at this again tonight (GMT+10) and on
the weekend.
On 1 Jun 2017 7:28 AM, "Jonas Schell"<EMAIL_ADDRESS>wrote:

Do you still need some help @voltagex https://github.com/voltagex ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pybee/toga/issues/150#issuecomment-305322905, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJvTxxu9I517boi6LTrdZnefp7lpHXaks5r_dtrgaJpZM4NHQ9d
.

This issue can be closed, it was solved in https://github.com/beeware/toga/commit/5e34abb4c67ca14ad717b3a560709e930d64af00


Return me to the last line of any reverted change

Step 0. Version 1.35.0 with extensions disabled.
Step 1. Open a file with changes committed in git
Step 2. Use ALT+F3 to navigate to the next change in-line
Step 3. Click Revert Change
Step 4. find the line number you were on and move your cursor there, then hit ALT+F3 again

I would like vscode to remember where I was whenever I revert a change, then return me to that place, so that I can see the change disappear and so that I can proceed using hotkey to the next change.

We might just have to set the cursor in that position, should be simple. Would you like to submit a PR?

@joaomoreno I can take a look at this.. As this will be my first pull request here in vscode repo, I will require some help.
Do let me know a good starting point for this..

Hi, I would like to work on this issue. I'll submit a PR soon.

@joaomoreno Do we want to fix this for 'stage change' functionality too? It behaves now the same way as 'revert change' - it starts searching from the beginning, instead of placing cursor in staged line position.

@Wowol Sounds good.


Typescript types are too loose

A number of the type definitions are nullable for no reason I can discern. This is forcing me to write code like:
if (
  !apiContext ||
  !apiContext.validation ||
  !apiContext.validation.errors ||
  !apiContext.request
) {
  // Return a 500 error which will probably never actually happen
  return
}

// Otherwise continue with the handler

This is from a validationFail handler, but at least some similar checks might be needed in any handler. Is there any reason these things all need to be nullable?

Hi @mkrauss ! Thanks for the feedback. There may well be some definitions where things are unnecessarily left nullable, even though there should never be such a case.
I'll look into the ones you've pointed out here.

For now I'm using this to avoid the conditionals that @mkrauss was using:
import { Context } from "openapi-backend";
import { Request, Response} from "express";
import ajv from "ajv";

type ContextWithErrors = Context & {
  validation: { errors: ajv.ErrorObject[] };
};

api.register(
  "validationFail",
  (context: ContextWithErrors, _req: Request, res: Response): void => {
    // Use `context.validation.errors`
  }
);


Formatting issue in the documentation

Describe the bug
The formatting in this section is incorrect: https://django-simple-history.readthedocs.io/en/latest/common_issues.html#using-custom-onetoonefields
If you are using a custom OneToOneField that has additional arguments and receiving
the the following ``TypeError``::

.. code=block:: python

    TypeError: __init__() got an unexpected keyword argument

It should be:
If you are using a custom OneToOneField that has additional arguments and receiving
the the following ``TypeError``::

    TypeError: __init__() got an unexpected keyword argument

To Reproduce
Steps to reproduce the behavior:

View docs here: https://django-simple-history.readthedocs.io/en/latest/common_issues.html#using-custom-onetoonefields
Note how the documentation includes the RST text.

Expected behavior
The documentation should not have included .. code=block:: python in the generated output.
Screenshots

Environment (please complete the following information):

OS: Fedora
Browser (if applicable): Chrome
Django Simple History Version: 3.1.1
Django Version: 4.0.6
Database Version: SQLite 3

Additional context
None.

I'm currently prepping a PR.

Closed in #1011


Update databox.json

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@msyyc this new API version has been merged two days ago only, here is the PR to confirm
https://github.com/Azure/azure-rest-api-specs/pull/15652
we forgot to add one property in a model, the API version hasn't been checked in ARM manifest, so we aren't affecting anybody as nobody has started using this version
need to get it quickly reviewed and merged so that we can continue with manifest checkin, since if we don't add this then our service will start giving many S360 KPI issues for this single property

approve for python breaking change.

Hi @ammaralavi I can't merge it because of the CI error:

Please follow bot advice to fix it.

Do I have to attend the office hours to get approval for breaking change or can I talk to someone quickly to get approval for this, I have created the following ADO item for this
Scenario 11002427: Breaking change approval for adding field to a property in Azure DataBox version "2021-08-01-preview" - Boards (visualstudio.com)https://msazure.visualstudio.com/One/_workitems/edit/11002427
From: msyyc @.>
Sent: 24 September 2021 12:13
To: Azure/azure-rest-api-specs @.>
Cc: Ammar Alavi @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Update databox.json (#16144)
Hi @ammaralavihttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fammaralavi&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820295889|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=4%2BEikaxxwMJMCip00Km0cs%2BP4YpnjqZQzod4R%2FOK100%3D&reserved=0 I can't merge it because of the CI error:
[Image removed by sender. image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F70930885%2F134629864-031a1a67-1971-45f7-8cd9-904509f94d2a.png&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820295889|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qf%2FgIufCp2vY671XPe9XxINYLllGR%2BW0zik%2FEc4rkZI%3D&reserved=0
Please follow bot advicehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F16144%23issuecomment-926384371&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820305882|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=1icIn7J9YY2MaO32W2f5KiigY5WByz2QGV5sMt0F1cM%3D&reserved=0 to fix it.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F16144%23issuecomment-926385492&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820315879|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=m5a67P%2BEBMb94JFSf8T1BvE%2BD6kTYQvNr1TBh5fCv58%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAVGHNRXBMNUHBZFRONISMVDUDQMW5ANCNFSM5EVC3NDQ&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820315879|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DdmgL%2B0G4mzT7jywRoYyhVOehEPWZtyehNiw%2BHKKVXY%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820325873|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=RsVbO8WrgxDQKOZoXvQiBGwnN3e9OG6Tsl4RaGOTNgI%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|ammaralavi%40microsoft.com|6e0f7b18824d4d78916a08d97f268a44|72f988bf86f141af91ab2d7cd011db47|1|0|637680625820325873|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=4QUY8FMa4ELwl720TSXfUqyPSf5Dr0zBnrgj%2F5lx2yE%3D&reserved=0.

@msyyc Do I have to attend the office hours to get approval for breaking change or can I talk to someone quickly to get approval for this, I have created the following ADO item for this
https://msazure.visualstudio.com/One/_workitems/edit/11002427

@ammaralavi  You could try to send e-mail to @josefree<EMAIL_ADDRESS>) for help. She is responsible for swagger breaking change

@msyyc have got the Approved-BreakingChange tag, please go ahead and merge this PR


SDK function not available in targeted version

Environment

Cppcheck plugin version: 1.4.2

Actual behaviour

Interestingly this is the function which is called when #23 happens


Make release notes nav clearer

Deploy preview for calico ready!
Built with commit 7cf1e823d6d2e74d87b83f6b610ac77d0058be38
https://deploy-preview-3555--calico.netlify.app


Miguelhar.mod migration

Updates the example terraform configuration to integrate missing components like flyte.
Fixes provisioning the costs buckets part of the storage module even when costs is disabled

looks good to me, :shipit:


Where has more example?

I was wondering more code for the kit.
If has more example, please tell me.
Or I will close the issue.
Thanks

We do not have a full application example, sorry. You might find https://suspicious.website/2016/04/29/starting-out-with-react-redux-starter-kit/ helpful, however. I also recommend checking out our gitter channel (in the readme) and asking around there since other users may be able to point you in the right direction.
Closing since there is no action to be taken in the starter kit. Good luck!


Projects Page

A summary page with completed, and maybe upcoming projects all in one. Use mockups for things like the AmeDoko app and stuff.
Showcase some of our projects in a nice, visually appealing way, instead of just directing to Github.
Include links to both the project URL and the source code, for visual stuff use mockups.

I’m down once I finish localization setup

Projects defnitely to mention in their own sections:

amedoko with a nice mockup like https://daisyui.com/components/mockup-phone/
hololive fan booth and holoquest app
vtscribe & holosays.net


Hippunfold on pediatric data?

Hi Jordan,
I am aware that Hippunfold was trained with adult data, and I am curious if you have already validated Hippunfold on kids' data or have plans to do so.
Thanks,
Oliver

Hi Oliver, sorry for the slow response. I don't know of any project to apply HippUnfold to children. I suspect it will work in some cases, but may have a higher than usual failure rate. If you're interested, you could fine-tune our segmentation model on training data from a subset of images where the results are good, and/or add additional cases by manual segmentation. I'd be happy to help with this, and if you're willing to make your fine-tuned model openly available then it would be a very valuable addition to HippUnfold! (happy to give you credit of course)

Hi both, sorry didn't see this earlier - Oliver what is the age range for your data? I recently ran hippunfold on T1w images in a sample of healthy 8-18 year olds. Overall the results looked good, and only required slight manual corrections in a handful of hippocampi.

Hi Jordan and Bradley, sorry for the late reply. I plan to use it on the HCP-D dataset (5-21), with the future goal of applying HippUnfold to pediatric patients. It is good to know that it worked well for 8 yo TDs. My collaborators at UMD recently have started a project to compare ASHS/freesurfer/Hippunfold subfield segmentation in young children (4-8yo), who also do manual segmentation. Depending on their findings, we will see if fine-tuning is needed for HippUnfold for kids.
Also, I know at least one more study that uses hippounfold in young kids (https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>5423v1).


#6 resolved format issues within prettier / chai eslint plugins

Coverage remained the same at 100.0% when pulling a9ca3a5017e02be648164045181b0e0b21718e99 on feature-6 into 8037d090b0efab6cc4df8047c3892f209fdecc19 on develop.


Sanitize Node.js standalone sample templates

add 'use strict';
remove placeholders
correctly use yargs
initialize the client

@vchudnov-g @beccasaurus @alexander-fenster  PTAL

@alexander-fenster I captured the restructure of the samples directory in #2574 and it might be better we do it in a separate PR, since the work will shuffle the files in the baseline and would be hard to review.
@vchudnov-g  PTAL

@hzyi-google is this ready to be merged?

@beccasaurus PTAL


WIP: Build working Windows container images

Fixes #361
The main discoveries while implementing this have been:

Windows containers expect contents to be in a Files/ root directory in the tar archive

...and for a Hives/ root directory to be present, though it can be empty

Executable entries in the tar archive must have a PAXRecords value to be executable at runtime

Even after this work lands, users building images will have to make sure they use a base image that provides the exact Windows OS version that they intend to run the image on. Users wishing to produce a multi-OS image with ko will probably also have to stitch together a suitable base image from nanoserver etc., and whatever Linux base image they want to use (distroless, alpine, etc.), since AFAIK suitable multi-OS base images aren't exactly prevalent in the wild.

Codecov Report

Merging #374 (bd1a61f) into main (23ecf47) will decrease coverage by 0.22%.
The diff coverage is 58.92%.

:exclamation: Current head bd1a61f differs from pull request most recent head 2a47b11. Consider uploading reports for the commit 2a47b11 to get more accurate results

@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
- Coverage   43.43%   43.21%   -0.23%
==========================================
  Files          33       33
  Lines        1570     1585      +15
==========================================
+ Hits          682      685       +3
- Misses        760      768       +8
- Partials      128      132       +4

Impacted Files
Coverage Δ

pkg/build/gobuild.go
58.08% <58.92%> (-1.64%)
:arrow_down:

Continue to review full report at Codecov.

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


Uncanny overlay behavior... bug in overlayfs?

Ah! Because user.overlay.opaque is set to y. :facepalm:
Kernel docs had me looking for trusted.overlay.opaque.

It appears that overlayfs is not creating the whiteout file for old when the directory is recreated(?)

Right: it doesn't need to, because an opaque directory ignores everything from the lowerdir. It's a bug in our summary/commit semantics (and in the kernel docs lol).

for context:

whiteouts and opaque directories
In order to support rm and rmdir without changing the lower filesystem, an overlay filesystem needs to record in the upper filesystem that files have been removed. This is done using whiteouts and opaque directories (non-directories are always opaque).
A whiteout is created as a character device with 0/0 device number or as a zero-size regular file with the xattr “trusted.overlay.whiteout”.
When a whiteout is found in the upper level of a merged directory, any matching name in the lower level is ignored, and the whiteout itself is also hidden.
A directory is made opaque by setting the xattr “trusted.overlay.opaque” to “y”. Where the upper filesystem contains an opaque directory, any directory in the lower filesystem with the same name is ignored.
An opaque directory should not conntain any whiteouts, because they do not serve any purpose. A merge directory containing regular files with the xattr “trusted.overlay.whiteout”, should be additionally marked by setting the xattr “trusted.overlay.opaque” to “x” on the merge directory itself. This is needed to avoid the overhead of checking the “trusted.overlay.whiteout” on all entries during readdir in the common case.

Okay, so in the commit logic, we want to check each directory for user.overlay.opaque, and completely replace the lowerdir of that directory with it.

When that is set to y, it means we need to destroy the existing lowerdir. But don't worry about this---I am doing it!


Use smaller picture in README.md

The default is obnoxiously big.
The text readability can benefit from more images. And the large size is holding me back from inserting more images (like screenshots).

https://github.github.com/gfm/#images

Solved by making the image landscape mode.


Creating Logs on Andorid

Hi, Is there a way to create logs on Android, when I use predictor in WhatsThis applcaition

Do you mean in the cpp part?
In the cpp file you can use this
 #include <android/log.h>
...
__android_log_print(ANDROID_LOG_INFO, "TAG_FOR_THE_APP", "LOG_MESSAGE");

When you compile the shared library you have to link android log with
-llog

Hi @SlipknotTN thank your for providing your feedback.
But when i use amalgalmation part of mxnet with all stuff you mentioned earlier lead to an issue of below stuff not defined
ANDROID_LOG_INFO

As i am not clear about where to place -llog in amalgalmation folder.

You have to add -llog in the Makefile of the amalgamation.
For example, instead of

CFLAGS=-std=c++11 -Wno-unknown-pragmas -Wall
ifneq ($(MIN), 1)
CFLAGS += -I${OPENBLAS_ROOT} -I${OPENBLAS_ROOT}/include
LDFLAGS+= -L${OPENBLAS_ROOT} -L${OPENBLAS_ROOT}/lib -lopenblas
endif

use this

CFLAGS=-std=c++11 -Wno-unknown-pragmas -Wall
LDFLAGS = -llog
ifneq ($(MIN), 1)
CFLAGS += -I${OPENBLAS_ROOT} -I${OPENBLAS_ROOT}/include
LDFLAGS+= -L${OPENBLAS_ROOT} -L${OPENBLAS_ROOT}/lib -lopenblas
endif

Hi @SlipknotTN thnx for your help. We are now able to have android logging working.


python312Packages.yalexs: 6.4.1 -> 6.4.2

Diff: https://github.com/bdraco/yalexs/compare/refs/tags/v6.4.1...v6.4.2
Changelog: https://github.com/bdraco/yalexs/releases/tag/v6.4.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 325552 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.august

4 packages built:

python311Packages.yalexs
python311Packages.yalexs.dist
python312Packages.yalexs
python312Packages.yalexs.dist


The ligershark library referenced does not work in asp.net core 6

[Enter feedback here]

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

ID: 36f55e9a-cd3f-83a0-f142-969dc10d3ceb
Version Independent ID: f6845f70-1ac6-2036-f213-a3b665b3d8bf
Content: Bundle and minify static assets in ASP.NET Core
Content Source: aspnetcore/client-side/bundling-and-minification.md
Product: aspnet-core
Technology: aspnetcore-clientside
GitHub Login: @Rick-Anderson
Microsoft Alias: scaddie

Dup of  #20808


IPN dates are parsed w/o timezone information

While playing with IPN I've noticed that the field payment_date was POSTed with value '16:23:34 May 05, 2015 PDT' and parsed as  datetime.datetime(2015, 5, 5, 16, 23, 34, tzinfo=<UTC>), ie: ignoring the timezone specified in the string.
I'm a django newbie, but perhaps this can be fixed by using the input_formatsargument of DateTimeField in here, right?
Also, this issue may also apply to fields auction_closing_date, next_payment_date, time_created, retry_at, subscr_date, subscr_effective and case_creation_date

models.DateTimeField doesn't support input_values, only forms.DateTimeField - https://docs.djangoproject.com/en/1.8/ref/forms/fields/#django.forms.DateField.input_formats
We are already using that. However, it doesn't support timezone parsing, probably because the underlying library (datetime.datetime.strptime) doesn't support it - https://docs.python.org/2/library/datetime.html#datetime.datetime.strptime
I do have some alternative ideas for fixing this though.

Great!
As I said, I'm a Django newbie so I'm quite confident that your alternative is much better.

This is fixed in 0.2.4. There is a migration documented if you want to fix your old data: http://django-paypal.readthedocs.org/en/latest/release_notes.html#version-0-2-4

Thanks Luke!

There is another PR I missed, with other date fields that have the problem:
https://github.com/spookylukey/django-paypal/pull/95/files
So you might want to wait until I address that before upgrading


az connectedk8s connect fails ungracefully with http.client.IncompleteRead error when installing helm client

Related command
az connectedk8s connect --name andrewlee-k8s --resource-group andrewlee-08mar --location eastus'
Extension name (the extension in question)
connectedk8s (Version 1.3.7)
azure-cli 2.38.0
Description of issue (in as much detail as possible)
The issue here is that https://github.com/Azure/azure-cli-extensions/blob/main/src/connectedk8s/azext_connectedk8s/custom.py, the install_helm_client
Enabling Azure Arc for Kubernetes. This may take a while.
Command: 'connectedk8s connect --name andrewlee-k8s --resource-group andrewlee-08mar --location eastus' failed with exit code: 1
WARNING: This operation might take a while...

WARNING: Downloading helm client for first time. This can take few minutes...
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: IncompleteRead(11699020 bytes read, 2003097 more expected)
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/root/.azure/cliextensions/connectedk8s/azext_connectedk8s/custom.py", line 176, in create_connectedk8s
    helm_client_location = install_helm_client()
  File "/root/.azure/cliextensions/connectedk8s/azext_connectedk8s/custom.py", line 426, in install_helm_client
    responseContent = response.read()
  File "/usr/lib64/python3.6/http/client.py", line 472, in read
    s = self._safe_read(self.length)
  File "/usr/lib64/python3.6/http/client.py", line 624, in _safe_read
    raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(11699020 bytes read, 2003097 more expected)
To open an issue, please run: 'az feedback'

The relevant code is:
        try:
            response = urllib.request.urlopen(requestUri)
        except Exception as e:
            telemetry.set_exception(exception=e, fault_type=consts.Download_Helm_Fault_Type,
                                    summary='Unable to download helm client.')
            raise CLIInternalError("Failed to download helm client.", recommendation="Please check your internet connection." + str(e))

        responseContent = response.read()
        response.close()

On the http.client.IncompleteRead issue - see e.g : https://stackoverflow.com/questions/14442222/how-to-handle-incompleteread-in-python for how to fix
it would be more python and safer to use a contextmanager here and do:

with urllib.request.urlopen(requestUri) as response:
    do some things..

route to CXP team

@andrew-lee-metaswitch Thanks for reaching out to us and reporting this issue. Could you please update your extension connectedk8s  and check if that helps.

az extension update -n connectedk8s

On a side note, also please update the Azure CLI. Hope this helps.


Cache GCS exists 2; iterdir boogaloo

Reimplementation based on @illusional's #497, with a slight adjustment of how the cloud dirs are tested.
Swaps out the google storage client call for a cloudpathlib iterdir. The former was having issues for me - returning empty sets on all directories.
Side issue is that dirname or basename calls on the GSPath objects seems to trigger a get, which is usually not permitted as a local user. Translating to a Str first solved this.
For discussion -
The pipeline has a version of this written in which is aiming to do the same thing, but in a really inelegant way (i can say that, I wrote it), I'd be keen to swap out that whole process for this one.
In addition, how do you feel about migrating this functionality to cpg-utils instead of keeping it pipeline specific?

I'm pretty content to merge this..
lil test case

https://batch.hail.populationgenomics.org.au/batches/429916 a test batch set off, cancelled after the first two stages completed
the same batch restarted, the first two stages are not repeated (output found)


After customizing shortcuts, Tab key no longer works

Discussed in https://github.com/imzbf/md-editor-v3/discussions/646

Originally posted by hao163 August 21, 2024
update 4.19.1 after , Tab key bug

=4.19.2已修复


Add “carpentry-lesson” tags to lessons to make them more discoverable

https://github.com/carpentries/lesson-infrastructure/issues/8#issuecomment-400786844

Done: https://github.com/topics/carpentry-lesson


Too many call on Service Catalog ?

AFT Version: 1.10.4
Bug Description
Too many API call on Service Catalog
Actually i have more than 30.000 API Calls on Service Catalog, is this normal ?
On CloudTrail i see many recurrence

Any idea why ?
Thanks

I've been using AFT for years, and I'm also worried about this. In a system
where no new accounts are created and no accounts updated, I still see lots
of Service Catalog calls, to the point where the free tier is exhausted
many times over.
AFT is obviously quite inefficient and expensive in this respect. I see no
reason why this incessant polling should take place. Perhaps its creators
can elucidate.
On Wed, 25 Oct 2023 at 10:45, Ménahem @.***> wrote:

AFT Version: 1.10.4
Bug Description
Too many API call on Service Catalog
Actually i have more than 30.000 API Calls on Service Catalog, is this
normal ?
On CloudTrail i see many recurrence
[image: Opera Instantané_2023-10-25_103151_eu-west-3 console aws amazon
com]
https://user-images.githubusercontent.com/1558463/277929966-85d60364-f484-472d-8fc2-ebec2daf9311.png
Any idea why ?
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAA6OMQTBPUGAH2WNA2MCDYBDGS5AVCNFSM6AAAAAA6O7QCCWVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DAOBXGE3TKMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Hey @Menahem1! Can you tell us the time range where you are seeing the API calls? In addition, how many customizations are you running?

Hey @hanafya
No time range is configured on the screenshot (on the monthly bill i see more that 30.000 api calls on September)
Juste one customizations and very few accounts created

Hey @Menahem1 How many accounts are in your AWS Organization?

about 15

The guilty one is here: https://github.com/aws-ia/terraform-aws-control_tower_account_factory/blob/main/modules/aft-account-request-framework/eventbridge.tf#L68
That lambda runs every 5 mins and makes many calls to Service catalog API. As a quick workaround we just manually changed that to like 12hours (even that is too much). Ideally, it should be triggered by SQS only

Has this been fixed?

I've noticed this as well. Removing the NAT gateway requirement dramatically reduced the cost of running AFT (from $100/month to $50/month, roughly). Now, the Service Catalog calls make up the bulk of the cost.

If this could be changed in a new minor release, it would halve the cost again. The screenshot above is for an AFT setup with 8 accounts, and no new accounts created this calendar year.

I suspect this part of the aft_account_request_processor is causing excessive call.
it might be a good intention to throw warning earlier, but I argue this call should begin only when there's a new message in the SQS queue.

Any progress on this? Any reaction from the dev team? Any activity at all??

Hi, Any update on this ?
Due to too many API calls within short time period, when there are lot of provisioned products exists (Total accounts 250+).
we are getting below error as well.
An error occurred in the 'aft-account-request-processor' Lambda function.

Error Message: An error occurred (ThrottlingException) when calling the
ScanProvisionedProducts operation (reached max retries: 4): Rate exceeded

Hi Everyone,
Adding to this conversation, I was thinking on opening a New issue but I decided to do a search first and bumped into this one
Fresh new install, and saw Service Catalog cost rising up which did not make much sense at first, digging deeper, I found out exactly what is reported on this thread:

The "aft-account-request-processor" lambda has an EventBridge "rate(5 minutes)" trigger, and
The Lambda is calling Service Catalog every time, disregarding if there are new messages to process, which as mentioned above is inefficient and wasteful

A screenshot from Cost Explorer, Dimension = "Usage type", Service = "Service Catalog":

There have been days where we have not used AFT for sure, so you can see an almost consistent charge of $0.81 cents per day, it is not much, but considering is not adding any value, I believe this is something that should be fixed
Here is an screenshot from the "aft-account-request-processor" lambda logs where seems to show that Service Catalog is called first, before actually verifying if there are any messages to process in SQS:

A better approach would be to either call Service Catalog ONLY IF there were messages in the queue (check SQS first), or to trigger the Lambda only based on events in SQS; either of the approaches should take care of the issue

FYI, I have just disabled manually the trigger on EventBridge for now, I will observe cost for a couple of days and report my findings:

Hi Everyone,
Adding to this conversation, I was thinking on opening a New issue but I decided to do a search first and bumped into this one
Fresh new install, and saw Service Catalog cost rising up which did not make much sense at first, digging deeper, I observed the same that is reported on this thread:

The "aft-account-request-processor" lambda has an EventBridge "rate(5 minutes)" trigger, and
The Lambda is calling Service Catalog every time, disregarding if there were new messages to process, which I think is inefficient and wasteful

A screenshot from Cost Explorer, Dimension = "Usage type", Service = "Service Catalog":
There have been days where we have not used AFT for sure, so you can see an almost consistent charge of $0.81 cents per day, it is not much (it might become significant as the number of accounts grows), but considering is not adding any value, I believe this is something that should be fixed
Here is an screenshot from the "aft-account-request-processor" lambda logs where seems to show that Service Catalog is being called first and some info extracted, this before actually verifying if there were any messages to process in SQS:
A better approach would be to either call Service Catalog ONLY IF there were messages in the queue (check SQS first), or to trigger the Lambda based on events in SQS alone (as mentioned by @wellsiau-aws, prob. better); either of the approaches should take care of the issue

Good info, thank you. and good option would be call Service Catalog API if there are messages in the queue — we are already implementing this approach internally and it works fine. However, triggering the Lambda based on SQS events could lead to issues due to the limitations in Service Catalog's provisioning. Currently, only a maximum of five products can be provisioned in parallel. If more than five account requests are submitted at once, it could create issues with provisioning the sixth account, and there is a risk that the SQS message might be lost. and it might need more changes in the AFT framework to handle it.

@Tharsan05, thank you for the angle on SQS events and maximum products limitation.
Aside from the method, I think the key conclusion we are reaching is that Service Catalog should only be called if there is something to process, and revising the lambda logic might be a good place to start.

I just want to provide a quick update, as suspected, the daily consistent cost for Service Catalog went away as soon as I disabled the EventBridge trigger for "aft-account-request-processor".
The trigger was disabled on Nov-13, in the Cost Explorer screenshot below you can see the partial day (day cost went down already), and Nov-14 (yesterday) it completely went away:

I used heavily AFT Account/Global customizations yesterday through CodePipeline to provision VPCs, etc., but this did not cause any Service Catalog charges, because I believe, it is only used in early stages of ADD/UPDATE Account Request operations.
As we know, Account Request operations (provision accounts, bring under management, update meta parameters) do not happen often, so I think it is not necessary to run the "aft-account-request-processor" lambda every 5 minutes, specially if it is calling Service Catalog every time within.
For the time being, I will keep the EventBridge lambda trigger disabled manually, and only enable it when I have account requests to process, easy enough to do, just an unnecessary manual step to remember so I hope this can be investigated and released as a bug fix/improvement soon.


add npy reader and writer

needs tests...

@llohse we used your code. can we remove the MIT license and only keep the BSD, with your copyright?

@wolfv: Yes, you may remove the MIT license.
I would kindly ask for any significant improvements to be provided to the original project.

Note that the newest version of libnpy has compile-time type-checking and byte-order determination.

ok, great, I modified the license in the header accordingly.
I would have contributed improvements back, but most of what is changed is style + the map_type (which is kind of runtime, but i guess the compiler will remove all branches (as the type is known at compile time) and it reduced the code size quite a bit, so this is rather a stylistic change.
Thanks for the great piece of work!
Wolf

hnggg... the github user interface offered me a merge of master ... probably we're gonna rebase anyways.

indeed I think you'll rebase, squash, remove that commit and force push once the light are green

@llohse awesome! libnpy is really nice.
By the way, we are working hard to support more and more features of numpy in xtensor (see the cheat sheet). Don't hesitate to hop on our gitter chat if you are interested.

so, unsigned long is 8-bytes long on linux whereas it is 32-bytes long on Windows. I think we should use types with explicit size such as uint_32 / uint64_t in the tests to avoid that kind of errors.

You can rebase on master now that the xbuffer_adaptor thingy is in.

@SylvainCorlay if you could look at the casters ... this way it seems to somewhat work :)


Use rcodesign verification on Xcode

Description of changes
This is currently very much a best-effort thing on linux, but beforehand we did no effort and gave no warning to the user, so it seems like an improvement on both counts.
$ rcodesign verify Xcode.app/Contents/MacOS/Xcode
no problems detected!
(we do not verify everything so please do not assume that the signature meets Apple standards)

Verifying the .app or the binary seems to be the same (which is good because rcodesign complains it can't verify a directory). The order seems to vary across invocations even for the same path, so I added a sort.
$ codesign -v --verbose=6 Xcode.app 2>&1 | sort > dir
$ codesign -v --verbose=6 Xcode.app/Contents/MacOS/Xcode 2>&1 | sort > bin
$ diff dir bin
557,558c557,558
< Xcode.app: satisfies its Designated Requirement
< Xcode.app: valid on disk
---
> Xcode.app/Contents/MacOS/Xcode: satisfies its Designated Requirement
> Xcode.app/Contents/MacOS/Xcode: valid on disk

I thought the .wip was the signed thing but apparently not
$ codesign -v Xcode14.wip:
Xcode14.wip: code object is not signed at all

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I see this was marked as draft? What must be done before merging is feasible?

Bump?

@wegank why mark this as draft?

Oh, I thought #254330 (comment) was in the todo list, sorry.

It was more of a "should we optimistically build these tools" doubt, but I guess that's independent of this PR per-se as it also applies to the pre-existing steps. I'm thinking one solution would be adding one last step along the lines of "you can run these commands inside nix-shell -p blabla"

LGTM, just need to adhere to the commit conventions.

Should be better now. Also rebased


Parsing Json to ASP

I have a Json object posted to an asp page.
I need to parse the json object and get each key/property.
Code example (not working)
Dim jsonString
jsonString = {"date":"4/28/2017","custType":"100","vehicle":"1"}

Dim jsonObj, outputObj
set jsonObj = new JSONobject
set outputObj = jsonObj.parse(jsonString)

response.write("
 date :" & outputObj.date & "
")
response.write("
 custType :" & outputObj.custType & "
")
response.write("
 vehicle :" & outputObj.vehicle & "
")

Microsoft VBScript runtime error '800a01b6'
Object doesn't support this property or method: 'date '
How can I get the key/value from the Json String some way?

Working Code:
response.write("
 date :" & outputObj("date") & "
")
response.write("
 custType :" & outputObj("custType") & "
")
response.write("
 vehicle :" & outputObj("vehicle") & "
")


fix: request to https if the tls is enabled

fixes: #437  if TLS is enabled all requests are directed to the HTTPS.

Thanks @Sanket-0510, I've approved the CI run. If CI tests fail, it means you need to also update snapshots. Just run locally:
npm run test:e2e-update

And commit changes. Fablo doesn't have local dev docs with that information yet (sorry for that). We have an issue to handle that: https://github.com/hyperledger-labs/fablo/issues/436.

Thanks @Sanket-0510, I've approved the CI run. If CI tests fail, it means you need to also update snapshots. Just run locally:
npm run test:e2e-update

And commit changes. Fablo doesn't have local dev docs with that information yet (sorry for that). We have an issue to handle that: https://github.com/hyperledger-labs/fablo/issues/436.

Is this fine now?

Let's see if CI passes. Also the DCO check fails, what means, because all commits needs to contain DCO sign-off: https://wiki.linuxfoundation.org/dco
You need to either squash or update commits, and then force push.

Let's see if CI passes. Also the DCO check fails, because all commits needs to contain DCO sign-off: https://wiki.linuxfoundation.org/dco
You need to either squash or update commits, and then force push.

I squashed the commit, and have signed it. Also I have run the e2e test command, tests pass successfully

Hey @dzikowski any idea why the tests are failing cause I guess I have done the changes at correct location, also I've ran e2e test also, nothing is failing locally!

test-k8 fails, because those are still in progress: https://github.com/hyperledger-labs/fablo/pull/425 and https://github.com/hyperledger-labs/fablo/pull/431
test-03-private-data fails, because it's a bit outdated, and we eventually want to remove this check: https://github.com/hyperledger-labs/fablo/issues/396
test-04-snapshot should be fixed on main branch now, once you merge, it should pass

test-k8 fails, because those are still in progress: #425 and #431
test-03-private-data fails, because it's a bit outdated, and we eventually want to remove this check: #396
test-04-snapshot should be fixed on main branch now, once you merge, it should pass

I have rebased my dev branch with fablo's main updated branch, I hope this will solve the problem


Is there any way to get an alert on DNS ping failure

I have two DNS mapped to a running container. Now sometimes one url fails but other works as expected.Need to know if there is any option to monitor the same.

I am a little bit confused about your setup. You have two external or internal DNS's pointed at the container IP?
What is failing and where is docker-alertd in this whole picture?


Decoding of EC Public Keys is broken in OpenSSL 3.0

I am unable to import neither DER, nor PEM public keys in OpenSSL 3.
Note: This might be related to https://github.com/openssl/openssl/issues/16977 as my public key strings created with the encoder look similar.
Whenever I try reading a public key, I get the error routines::unsupported.
However, importing a private key works just fine.
As we cannot share private keys of course, not being able to create an EVP_PKEY from our public key material is a crucial issue that makes us unable to continue at all.
We are trying to do a ECDH key exchange, but, as importing the public key material from the other peer does not work,  we have no chance of doing so.
I have tried using both DER and PEM encodings as stated before, with private key imports being fine for both of them.
Either the documentation needs to be updated - stating that EVP_PKEYs cannot be constructed from EC public keys, and additional information and workarounds habe to be provided - or the bug needs to be fixed asap.
This is a huge issue.
For further investigation, here is how we encode our public key.
    constexpr char FORMAT[] = "DER"; // Either PEM or DER

    auto key = EVP_EC_gen(SN_brainpoolP256r1);
    unsigned char* publicKey = nullptr;
    size_t publicLen = 0;
    auto ptr = OSSL_ENCODER_CTX_new_for_pkey(
                                             key,
                                             EVP_PKEY_PUBLIC_KEY,
                                             FORMAT,
                                             nullptr,
                                             nullptr
                                             );
    OSSL_ENCODER_to_data(ptr, &publicKey, &publicLen);
    OPENSSL_free(ptr);

publicKey is then sent to our backend, which stores it.
Later, another peer downloads the publicKey, and passes the key material and its length (via strlen, as stated private keys work perfectly fine, so this isn't an issue of misconfiguration). The downloaded key is then passed to the derive function, which does the ECDH key exchange.
As said before this does not work, as the public key part fails to create the needed EVP_PKEY.
This is how we are creating an EVP_PKEY from our public key:
    constexpr char FORMAT[] = "DER"; // Either PEM or DER
    // Theirs is the downloaded public key material from the other peer, either in PEM or DER format
   void DeriveKey(..., const unsigned char* theirs, size_t theirsLen) {

    EVP_PKEY_CTX* ctx = nullptr;
    EVP_PKEY* peerKey = nullptr;
    auto ptr = OSSL_DECODER_CTX_new_for_pkey(
                                             &peerKey,
                                             FORMAT,
                                             nullptr,
                                             nullptr,
                                             EVP_PKEY_PUBLIC_KEY, // EVP_PKEY_KEYPAIR works fine when used with a private key; We also tried several other options, with none of them being successful on public keys.
                                             nullptr,
                                             nullptr
                                             );
    auto result = OSSL_DECODER_from_data(ptr, &theirs, &theirsLen);
    // result == 0
    auto err = ERR_get_error();
    auto buff = new char[512];
    ERR_error_string(err, buff); // error:1E08010C:DECODER routines::unsupported
}

If you can supply the actual public key material we can determine whether it has been encoded correctly or not (i.e. whether it is actually issue #16977 or something different)

@mattcaswell
Encoding a public key in PEM format yields this:
-----BEGIN EC PUBLIC KEY-----\nBJlgr2TNcLkBSbDdb9N0tc1Kr42RGMBdRMSddWpekPAyY5F4P7hZ5TJYiOgcJc9f\nbz+/+oyuan/b40nvCJhNUuM=\n-----END EC PUBLIC KEY-----\n\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa

this is taken right from the char buffer, without uploads or anything

This is what the encoded key material looks like when using the fix mentioned in the other issue.

And this is the opposite, prior to the workaround

It appears that the only change is the lack of EC, e.g. BEGIN PUBLIC KEY instead of BEGIN EC PUBLIC KEY

It's not just about the header. The contents of the "EC PUBLIC KEY" isn't correct for a "PUBLIC KEY", as there's a difference in structure (the contents of that "EC PUBLIC KEY" is actually highly unstructured, it's simply a dumped big number, totally raw... it's not even DER).

@levitte Well that’s unfortunate.
As it has been made clear that this ticket is related to the other one, I’ll close this.