spinel.h: Adjust spacing and alignments (again...)

This commit fixes the spacing and alignment in spinel.h header
file. This was done earlier in commit 227d2a091b but was overwritten
(back to the older version) in commit 2fa7a13c1b (which intended to add
two new spinel properties related to commissioning in spinel.h).

Codecov Report

Merging #1587 into master will increase coverage by 0.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1587      +/-   ##
==========================================
+ Coverage   68.83%   69.57%   +0.74%
==========================================
  Files         158      159       +1
  Lines       20229    20239      +10
  Branches     2481     2481
==========================================
+ Hits        13924    14082     +158
+ Misses       5399     5245     -154
- Partials      906      912       +6

Impacted Files
Coverage Δ

src/core/thread/data_poll_manager.cpp
65.44% <0%> (-2.95%)
:arrow_down:

src/core/common/message.hpp
96.29% <0%> (-1.86%)
:arrow_down:

src/core/thread/mesh_forwarder.cpp
78.33% <0%> (-1.23%)
:arrow_down:

src/core/thread/topology.hpp
87.8% <0%> (-1.22%)
:arrow_down:

examples/platforms/posix/radio.c
77.17% <0%> (-0.42%)
:arrow_down:

examples/apps/ncp/main.c
100% <0%> (ø)

src/core/thread/mle.cpp
81.59% <0%> (+0.21%)
:arrow_up:

src/ncp/ncp_base.cpp
34.59% <0%> (+0.54%)
:arrow_up:

src/core/mac/mac.cpp
79.62% <0%> (+1.25%)
:arrow_up:

src/core/common/message.cpp
95.85% <0%> (+1.38%)
:arrow_up:

... and 14 more

Continue to review full report at Codecov.

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


Implement hotjar for AR filing to see the path the user takes and if there are any drop off points

This tix is to implement hotjar so we can see the path the user takes and if there are any drop off points.
Does hotjar also capture if they are using a mobile, O/S, browser, resolution, location, etc.?
If not, how can we capture this data?
Could we please have this ready for the first actual release, around mid-June?

@pwei1018 please confirm whether we still have a licence for these recordings.  And if we don't, how much will it cost?
I seem to recall it would capture the information Trish is looking for (except for maybe resolution?)

As per Patrick:  we dropped the licence about 2 years ago because we weren't reviewing the recordings.
We used to get 35 daily sessions.
Recommend getting the Business licence @ 1,188/year USD.

@pwei1018 please complete spending approval form to purchase the licence.


Use google/protobuf/empty.go and align at the same time

Hi KKKIIO,
When I use the plugin, I ran into a problem. When I use google/protobuf/empty.go and align at the same time，the following situation occurred:
Before:
    google.protobuf.Empty open_panel = 4;
    UpStartBattle start_battle = 5;
    UpEndBattle end_battle = 6;

After
    google .      protobuf. Empty open_panel       = 4;
    UpStartBattle start_battle                     = 5;
    UpEndBattle   end_battle                       = 6;

google .      protobuf. Empty seems did not meet expectations.

Thanks for the quick fix.


[CleanShot X] Add option to send captured area to new AI chat

Extension
https://www.raycast.com/Aayush9029/cleanshotx
Description
The new Send Captured Area to AI Chat is great! Right now it sends it (understandably) to whatever AI chat is active. I would to have an option in the command's settings to either send to the active chat, or, start a new chat with the attached screenshot.
Who will benefit from this feature?
Anyone who would often be starting new chats based on a screenshot.
Anything else?
No response

This would likely require changes from both the Raycast app and the CleanShot app. I suggest either emailing the CleanShot team, or posting in the Raycast slack to contact the respective dev teams.


Add coverage report

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@b5f91d6). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage        ?   86.66%
=======================================
  Files           ?        2
  Lines           ?      330
  Branches        ?       64
=======================================
  Hits            ?      286
  Misses          ?       28
  Partials        ?       16

Flag
Coverage Δ

unittests
86.66% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


WWTTF will damage your computer. You should move it to the Trash.

the workflow doesn't work for some reason and there's a warning popup every time I try to 'ww' on alfred.

Same!

I fixed this by downloading the latest release

now in Alfred Gallery.


pthread: remove enter_critical_section in pthread_barrier_wait

Summary
reason:
We decouple semcount from business logic by using an independent counting variable, which allows us to remove critical sections in many cases.
Impact
pthread_barrier_wait
Testing
Build Host:
OS: Ubuntu 20.04
CPU: x86_64
Compiler: GCC 9.4.0
Configuring NuttX and compile:
$ ./tools/configure.sh -l qemu-armv8a:nsh_smp
$ make
Running with qemu
$ qemu-system-aarch64 -cpu cortex-a53 -smp 4 -nographic
-machine virt,virtualization=on,gic-version=3
-net none -chardev stdio,id=con,mux=on -serial chardev:con
-mon chardev=con,mode=readline -kernel ./nuttx

[Experimental Bot, please feedback here]
This PR appears to partially meet the NuttX requirements. Here's a breakdown:
Strengths:

Provides a reason for the change: Decoupling semcount from business logic to remove critical sections is a valid justification.
Specifies the impacted function: pthread_barrier_wait is clearly identified.
Lists the build host environment:  OS, CPU, and compiler details are provided.
Includes build instructions and how to run it: This offers helpful context for reviewers.

Weaknesses (requiring further information in the PR):

Missing details in the Summary:  While the reason is provided, the "what" and "how" are missing.  The summary should explain how the decoupling is achieved and what changes are made to the code.  A related NuttX issue number should be included if one exists.
Incomplete Impact Assessment: While pthread_barrier_wait is mentioned, the PR needs to explicitly answer all the impact questions (user impact, build impact, hardware impact, documentation impact, security impact, compatibility impact).  Just stating the impacted function is insufficient.  Even if the answer is "NO," it should be stated explicitly.
Missing "before" and "after" testing logs: The provided example logs are placeholders.  Actual logs demonstrating the change's effect (e.g., performance improvement, corrected behavior) are crucial.  The testing section also lacks information about the target being tested (qemu-armv8a is mentioned in the build instructions but not explicitly in the Testing section).  It would also benefit from explaining the test case used to generate these logs.

To fully meet the NuttX requirements, the PR needs to:

Expand the Summary: Explain the technical implementation details and how the change works.  Include a related NuttX issue number if applicable.
Complete the Impact Assessment:  Explicitly answer all the impact questions (even with "NO" if no impact). Provide details if any impact is "YES."
Provide real testing logs: Include "before" and "after" logs demonstrating the change's effect and explaining the test case used.  Clearly state the target architecture and board configuration used for testing.

By addressing these points, the PR will be much clearer and easier for reviewers to evaluate.


Google Cloud Functions - NPM install fails.

Deploying some changes to a thumbnailer script that sharp uses (great script, btw - thanks!) and the npm build is now failing trying v0.28.3 (previously was using 0.18.1 and working, so not sure where the issue was introduced)
GCF doesn't show the errors from the build itself but trying to run the thumbnailer script it errors:

Provided module can't be loaded.
Did you list all required modules in the package.json dependencies?
Detailed stack trace: Error: Cannot find module 'sharp'
... package doesn't exist.

Google Cloud Functions: Tried with Node 10, 12 & 14
I saw a number of other issues on different chipsets, toolkits related to this so adding Google Cloud Functions into the mix.
I'll go back through the issues to find an earlier version that should work and specify that release so my problem should be all good. Just letting you know the issue is breaking usage on GCF too.

Please provide more information, including answering the questions from the installation issue template.
Lots of people are successfully using sharp on Google Cloud Functions so it's likely there is something that needs updating or fixing in your build/deployment configuration.

Hi,
I'm having a similar issue on Github actions. The full output can be found here: https://github.com/pietervdvn/MapComplete/runs/3170239620?check_suite_focus=true
(For reference:
 npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! ../src/common.cc:24:10: fatal error: vips/vips8: No such file or directory
npm ERR!    24 | #include <vips/vips8>
npm ERR!       |          ^~~~~~~~~~~~
npm ERR! compilation terminated

Machine info:

Operating System
  Ubuntu
  20.04.2
  LTS
Virtual Environment
  Environment: ubuntu-20.04
  Version: 20210718.1
  Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20210718.1/images/linux/Ubuntu2004-README.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20210718.1

Someone of the team also had this on their local machine (a windows with WSL IIRC)

@pietervdvn Please open a new installation issue and answer all of the questions. https://github.com/lovell/sharp/issues/new?assignees=&labels=installation&template=installation.md

@lovell  - Adding questionaire for completeness as I still haven't been able to get a build on GCF working. The GCF deployment still fails with the sharp module being 'missing' (my read is npm install difficulty). The last successful build was Dec 2020 (package.json fixed with 0.18.1 - Node 10).
The build used to just work, has anything changed that would make a straight npm install not run anymore?
package.json (the only build configuration available)
{
  "name": "crop-thumbnailer",
  "version": "0.1.3",
  "dependencies": {
    "sharp": "^0.28.3",
    "@google-cloud/storage" : ">=3.0.0",
    "mysql": ">=2.5.0"
  }
}

Installation Issue Questionnaire

Did you see the documentation relating to installation?

Yes

Have you ensured the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime?

It's all handled by GCF, I have to assume yes.

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?

These commands are not possible to run on the Google Cloud Platform, Google Cloud Functions Framework.

If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?

No, I've tried deploying ot GCF's Node 10, Node 12 and Node 14 environments all with same issue.

If you are using npm v7, does the user running npm install own the directory it is run in?

N/A

If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?

N/A

What is the complete output of running npm install --verbose sharp? Have you checked this output for useful error messages?

It's not possible to see build logs, let alone verbose ones within GCF

What is the output of running npx envinfo --binaries --system?

Again - It's not possible to shell to a GCF instance to to run these commands.

It's not possible to see build logs, let alone verbose ones within GCF

https://cloud.google.com/functions/docs/building#accessing_your_build_image_logs

I went through those. It only shows errors with your code and not the
dependencies build. 🤷♂
On Wed, Aug 4, 2021, 9:33 PM Lovell Fuller @.***> wrote:

It's not possible to see build logs, let alone verbose ones within GCF
https://cloud.google.com/functions/docs/building#accessing_your_build_image_logs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lovell/sharp/issues/2811#issuecomment-892662335, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5XHE6WV6M56FHNM3SMVJLT3E6RZANCNFSM5A75EIUQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Disregard previous.
I tried though the console. Will try a command line deploy and report back
tomorrow.
On Wed, Aug 4, 2021, 9:33 PM Lovell Fuller @.***> wrote:

It's not possible to see build logs, let alone verbose ones within GCF
https://cloud.google.com/functions/docs/building#accessing_your_build_image_logs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lovell/sharp/issues/2811#issuecomment-892662335, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5XHE6WV6M56FHNM3SMVJLT3E6RZANCNFSM5A75EIUQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@lovell  I can redeploy the last successful build from the command line, so here are the logs for trying to redeploy with Sharp 0.18.4 as a requirement.
Build logs - Node10 Sharp 0.18.4 (last working deployment - no code change)
2021-08-05 11:14:10.957 - starting build "b688c464-7e35-486b-9b0a-b82b35303788"
2021-08-05 11:14:10.957 - FETCHSOURCE
2021-08-05 11:14:10.957 - Fetching storage object: gs://gcf-sources-299431218570-us-central1/DEV-crop_thumbnailer-16e73b41-2b80-4a3c-8806-74bb57638453/version-8/function-source.zip#1628126050136230
2021-08-05 11:14:16.240 - Copying gs://gcf-sources-299431218570-us-central1/DEV-crop_thumbnailer-16e73b41-2b80-4a3c-8806-74bb57638453/version-8/function-source.zip#1628126050136230...
2021-08-05 11:14:16.377 - / [0 files][ 0.0 B/ 3.4 KiB] / [1 files][ 3.4 KiB/ 3.4 KiB]
2021-08-05 11:14:16.377 - Operation completed over 1 objects/3.4 KiB.
2021-08-05 11:14:17.588 - Archive: /tmp/source-archive.zip
2021-08-05 11:14:17.588 - inflating: /workspace/index.js
2021-08-05 11:14:17.588 - inflating: /workspace/package.json
2021-08-05 11:14:17.588 - inflating: /workspace/testEvent.json
2021-08-05 11:14:17.874 - BUILD
2021-08-05 11:14:18.486 - Starting Step #0 - "prep"
2021-08-05 11:14:18.487 - Step #0 - "prep": Pulling image: us.gcr.io/fn-img/utilities/crane-shell:nodejs10_20210713_10_24_1_RC00
2021-08-05 11:14:19.522 - Step #0 - "prep": nodejs10_20210713_10_24_1_RC00: Pulling from fn-img/utilities/crane-shell
2021-08-05 11:14:19.601 - Step #0 - "prep": b49b96595fd4: Already exists
2021-08-05 11:14:19.615 - Step #0 - "prep": bb771d6dc9a1: Already exists
2021-08-05 11:14:19.625 - Step #0 - "prep": 82eb23873ec5: Pulling fs layer
2021-08-05 11:14:19.625 - Step #0 - "prep": 72164b581b02: Pulling fs layer
2021-08-05 11:14:19.625 - Step #0 - "prep": c15d52701efb: Pulling fs layer
2021-08-05 11:14:19.684 - Step #0 - "prep": 72164b581b02: Verifying Checksum
2021-08-05 11:14:19.684 - Step #0 - "prep": 72164b581b02: Download complete
2021-08-05 11:14:19.704 - Step #0 - "prep": 82eb23873ec5: Verifying Checksum
2021-08-05 11:14:19.704 - Step #0 - "prep": 82eb23873ec5: Download complete
2021-08-05 11:14:19.813 - Step #0 - "prep": c15d52701efb: Verifying Checksum
2021-08-05 11:14:19.813 - Step #0 - "prep": c15d52701efb: Download complete
2021-08-05 11:14:19.912 - Step #0 - "prep": 82eb23873ec5: Pull complete
2021-08-05 11:14:20.011 - Step #0 - "prep": 72164b581b02: Pull complete
2021-08-05 11:14:20.284 - Step #0 - "prep": c15d52701efb: Pull complete
2021-08-05 11:14:20.306 - Step #0 - "prep": Digest: sha256:746291589a530c825103f606a7fbe7633ba65fe573f614fe2f115892ecac48ad
2021-08-05 11:14:20.313 - Step #0 - "prep": Status: Downloaded newer image for us.gcr.io/fn-img/utilities/crane-shell:nodejs10_20210713_10_24_1_RC00
2021-08-05 11:14:20.319 - Step #0 - "prep": us.gcr.io/fn-img/utilities/crane-shell:nodejs10_20210713_10_24_1_RC00
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable BUILDER_OUTPUT to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_DEBUG to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_RUNTIME to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_LABEL_BUILDER_VERSION to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_LABEL_BUILDER_IMAGE to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_LABEL_RUN_IMAGE to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_FUNCTION_TARGET to buildpacks.
2021-08-05 11:14:21.221 - Step #0 - "prep": Passing build environment variable GOOGLE_FUNCTION_SIGNATURE_TYPE to buildpacks.
2021-08-05 11:14:21.404 - Finished Step #0 - "prep"
2021-08-05 11:14:21.404 - Starting Step #1 - "validate-images"
2021-08-05 11:14:21.406 - Step #1 - "validate-images": Already have image (with digest): us.gcr.io/fn-img/utilities/crane-shell:nodejs10_20210713_10_24_1_RC00
 2021-08-05 11:14:25.557 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:6ea402ebdaf85c8ad885027394d994bea275d806401c5dd50cace180cade1f2b
2021-08-05 11:14:25.561 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:9675bb9e968fd1192e15e32f26d77a09c4861425e6ccde828299dc16deee27ed
2021-08-05 11:14:25.565 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:d22b00816366056147e8f7c6b516c52b28c3c3a5cec23f648c2a4d3dd2f8792c
2021-08-05 11:14:25.587 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:f6909a737046ea5893451ee53868796bb489a0d556cf10608f1bddd34e91073d
2021-08-05 11:14:25.589 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:0533677bb37d0a93a1bc75adb94df8b68dece84f7415223d16cfc9bc346f5f94
2021-08-05 11:14:25.589 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:3e0b49ba1f68338d761c18dde71c71f07c15ae0da3dec74f3ba5d55d7e9c2e26
2021-08-05 11:14:25.601 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:928f56b671ac816f5194ab4656053ab3d8ae4e70a9db5be8cc6d1b9a44b63b30
2021-08-05 11:14:25.610 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:603dab334a4261a6ef71eba4aa37f6413566f2f5a5e21672bfb591ef4bb7ac5b
2021-08-05 11:14:25.617 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:00ab17d3df7c2d0714df265bbc519ea9fec79e220aee5c34c9d4e9eaa9e90e8b
2021-08-05 11:14:25.622 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:d0ed2b8c108fe7298f4b03fcbe1430e15abfd2ce104f7a350e5d7f8ec49b32f2
2021-08-05 11:14:25.624 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:18cee90eb87f2a77415eb5a15794935d13e3bd13b92042df56f3836d8a68b10a
2021-08-05 11:14:25.640 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:5a44e4f7b58d74fe6f92dd7028075c91191128d1e2e7f39846fe061a9a98836e
2021-08-05 11:14:25.715 - Step #2 - "pre-tag": 2021/08/05 01:14:25 existing blob: sha256:f10d184b98108935c6b514be86861053026e217186bd4d4100acd5fa67b38fc3
2021-08-05 11:14:25.961 - Step #2 - "pre-tag": 2021/08/05 01:14:25 us.gcr.io/searcheraggregator/gcf/us-central1/16e73b41-2b80-4a3c-8806-74bb57638453:DEV-crop_thumbnailer_version-8: digest: sha256:8a00c7376b9961686027ac63d4f1e9be2c9f61d8634e5278794beb8ac3af80af size: 5446
2021-08-05 11:14:26.149 - Finished Step #2 - "pre-tag"
2021-08-05 11:14:26.149 - Starting Step #3 - "build"
2021-08-05 11:14:26.150 - Step #3 - "build": Pulling image: us.gcr.io/fn-img/buildpacks/nodejs10/builder:nodejs10_20210713_10_24_1_RC00
2021-08-05 11:14:26.787 - Step #3 - "build": nodejs10_20210713_10_24_1_RC00: Pulling from fn-img/buildpacks/nodejs10/builder
2021-08-05 11:14:26.789 - Step #3 - "build": 228505c46125: Already exists
2021-08-05 11:14:26.799 - Step #3 - "build": 52b243a9211b: Already exists
2021-08-05 11:14:26.808 - Step #3 - "build": 3c2cba919283: Already exists
2021-08-05 11:14:26.817 - Step #3 - "build": 94b9159bf001: Already exists
2021-08-05 11:14:26.827 - Step #3 - "build": de3a1d1384e7: Already exists
2021-08-05 11:14:26.836 - Step #3 - "build": f48f5e846525: Already exists
2021-08-05 11:14:26.843 - Step #3 - "build": 56ae46af1768: Already exists
 2021-08-05 11:14:26.884 - Step #3 - "build": 1872f6afe650: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": 7d5f0d832abc: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": 7e8f029fa81d: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": 7b9ca1c3ab5b: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": a43ea245e86c: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": 4f4fb700ef54: Pulling fs layer
2021-08-05 11:14:26.884 - Step #3 - "build": c4bb98b50e02: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 918ecc66eae4: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": d74463ff2a9e: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 9645f1569810: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 96a4e2ef1369: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": ff1205b292fb: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 3dcec76d3627: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 6d43c0455dd6: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 06f428a8446f: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": df2a11ebcd38: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": cb30c9442e95: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": c3e0da70529e: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 176bb191af92: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 833850cf7cc5: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 1872f6afe650: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 7d5f0d832abc: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 7e8f029fa81d: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 7b9ca1c3ab5b: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": a43ea245e86c: Waiting
2021-08-05 11:14:26.884 - Step #3 - "build": 4f4fb700ef54: Waiting
 2021-08-05 11:14:27.916 - Step #3 - "build": 4f4fb700ef54: Download complete
2021-08-05 11:14:27.920 - Step #3 - "build": a43ea245e86c: Verifying Checksum
2021-08-05 11:14:27.920 - Step #3 - "build": a43ea245e86c: Download complete
2021-08-05 11:14:27.931 - Step #3 - "build": b01724cf3119: Pull complete
2021-08-05 11:14:29.849 - Step #3 - "build": c4bb98b50e02: Pull complete
2021-08-05 11:14:29.944 - Step #3 - "build": 918ecc66eae4: Pull complete
2021-08-05 11:14:30.133 - Step #3 - "build": d74463ff2a9e: Pull complete
2021-08-05 11:14:30.229 - Step #3 - "build": 9645f1569810: Pull complete
2021-08-05 11:14:30.329 - Step #3 - "build": 96a4e2ef1369: Pull complete
2021-08-05 11:14:30.422 - Step #3 - "build": ff1205b292fb: Pull complete
2021-08-05 11:14:30.552 - Step #3 - "build": 3dcec76d3627: Pull complete
2021-08-05 11:14:30.645 - Step #3 - "build": 6d43c0455dd6: Pull complete
2021-08-05 11:14:30.739 - Step #3 - "build": 06f428a8446f: Pull complete
2021-08-05 11:14:31.019 - Step #3 - "build": df2a11ebcd38: Pull complete
2021-08-05 11:14:31.223 - Step #3 - "build": cb30c9442e95: Pull complete
2021-08-05 11:14:31.408 - Step #3 - "build": c3e0da70529e: Pull complete
2021-08-05 11:14:31.601 - Step #3 - "build": 176bb191af92: Pull complete
2021-08-05 11:14:31.791 - Step #3 - "build": 833850cf7cc5: Pull complete
2021-08-05 11:14:31.976 - Step #3 - "build": 1872f6afe650: Pull complete
2021-08-05 11:14:32.176 - Step #3 - "build": 7d5f0d832abc: Pull complete
2021-08-05 11:14:32.366 - Step #3 - "build": 7e8f029fa81d: Pull complete
2021-08-05 11:14:32.463 - Step #3 - "build": 7b9ca1c3ab5b: Pull complete
2021-08-05 11:14:32.563 - Step #3 - "build": a43ea245e86c: Pull complete
2021-08-05 11:14:32.655 - Step #3 - "build": 4f4fb700ef54: Pull complete
2021-08-05 11:14:32.670 - Step #3 - "build": Digest: sha256:eae506c00b260304ed7ea698f485470d9a4e96bcd4ca5daa5b65c86f25d7f397
 2021-08-05 11:14:45.594 - Step #3 - "build": gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2021-08-05 11:14:45.594 - Step #3 - "build": gyp ERR! cwd /workspace/node_modules/sharp
2021-08-05 11:14:45.594 - Step #3 - "build": gyp ERR! node -v v10.24.1
2021-08-05 11:14:45.594 - Step #3 - "build": gyp ERR! node-gyp -v v5.1.0
2021-08-05 11:14:45.594 - Step #3 - "build": gyp ERR! not ok
2021-08-05 11:14:45.730 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No description
2021-08-05 11:14:45.731 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No repository field.
2021-08-05 11:14:45.734 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No license field.
2021-08-05 11:14:45.734 - Step #3 - "build":
2021-08-05 11:14:45.748 - Step #3 - "build": npm ERR! code ELIFECYCLE
2021-08-05 11:14:45.749 - Step #3 - "build": npm ERR! errno 1
2021-08-05 11:14:45.750 - Step #3 - "build": npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
2021-08-05 11:14:45.751 - Step #3 - "build": npm ERR! Exit status 1
2021-08-05 11:14:45.753 - Step #3 - "build": npm ERR!
2021-08-05 11:14:45.753 - Step #3 - "build": npm ERR! Failed at the<EMAIL_ADDRESS>install script.
2021-08-05 11:14:45.753 - Step #3 - "build": npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-08-05 11:14:45.766 - Step #3 - "build":
2021-08-05 11:14:45.766 - Step #3 - "build": npm ERR! A complete log of this run can be found in:
2021-08-05 11:14:45.766 - Step #3 - "build": npm ERR! /www-data-home/.npm/_logs/2021-08-05T01_14_45_759Z-debug.log
2021-08-05 11:14:45.774 - Step #3 - "build": Done "npm install --quiet (NODE_ENV=production)" (4.469620576s)
2021-08-05 11:14:45.775 - Step #3 - "build": Failure: (ID: 49341d49) ><EMAIL_ADDRESS>install /workspace/node_modules/sharp
2021-08-05 11:14:45.776 - Step #3 - "build": > node-gyp rebuild
2021-08-05 11:14:45.776 - Step #3 - "build":
2021-08-05 11:14:45.777 - Step #3 - "build": ERROR: https://dl.bintray.com/lovell/sharp/libvips-8.5.5-linux-x64.tar.gz status code 403
2021-08-05 11:14:45.778 - Step #3 - "build": gyp: Call to 'node -e "require('./binding').download_vips()"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! configure error
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! stack Error: `gyp` failed with exit code: 1
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! stack at ChildProcess.emit (events.js:198:13)
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! System Linux 5.4.0-1046-gcp
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! cwd /workspace/node_modules/sharp
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! node -v v10.24.1
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! node-gyp -v v5.1.0
2021-08-05 11:14:45.778 - Step #3 - "build": gyp ERR! not ok
2021-08-05 11:14:45.779 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No description
2021-08-05 11:14:45.779 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No repository field.
2021-08-05 11:14:45.779 - Step #3 - "build": npm WARN<EMAIL_ADDRESS>No license field.
2021-08-05 11:14:45.779 - Step #3 - "build":
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! code ELIFECYCLE
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! errno 1
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! Exit status 1
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR!
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! Failed at the<EMAIL_ADDRESS>install script.
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-08-05 11:14:45.779 - Step #3 - "build":
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! A complete log of this run can be found in:
2021-08-05 11:14:45.779 - Step #3 - "build": npm ERR! /www-data-home/.npm/_logs/2021-08-05T01_14_45_759Z-debug.log
2021-08-05 11:14:45.779 - Step #3 - "build": --------------------------------------------------------------------------------
2021-08-05 11:14:45.783 - Step #3 - "build": Running "mv -f /builder/outputs/output-5577006791947779410 /builder/outputs/output"
2021-08-05 11:14:45.784 - Step #3 - "build": Done "mv -f /builder/outputs/output-5577006791947779410 /builder/o..." (9.987915ms)
2021-08-05 11:14:45.786 - Step #3 - "build": ERROR: failed to build: exit status 1
2021-08-05 11:14:46.642 - Finished Step #3 - "build"
2021-08-05 11:14:46.642 - ERROR
2021-08-05 11:14:46.642 - ERROR: build step 3 "us.gcr.io/fn-img/buildpacks/nodejs10/builder:nodejs10_20210713_10_24_1_RC00" failed: step exited with non-zero status: 145

This installation log is for sharp v0.18.4 - please see #2574 and upgrade.

Yes, it's all I can deploy to get the logs without changing the build
pipeline. Same deployment issue occurs with 0.23.3
On Thu, Aug 5, 2021, 4:25 PM Lovell Fuller @.***> wrote:

This installation log is for sharp v0.18.4 - please see #2574
https://github.com/lovell/sharp/issues/2574 and upgrade.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lovell/sharp/issues/2811#issuecomment-893268096, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5XHEYSNP5DOLKPFLIP54DT3JDHFANCNFSM5A75EIUQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

GCF just built the Node 10 function successfully sharp with v.0.28.3 as a dependency. Thanks for your patience.


fix(bch-js): Bumping to v4.15.19

:tada: This PR is included in version 1.5.3 :tada:
Your semantic-release bot :package::rocket:


Add Pre-loader

Added Pre-loader
Issue No: #236

Hey @soumyajit254 please add the full Rentalog logo instead of this.

@soumyajit254 ?


Crop the aspect ratio

Is there an option to keep the original size (for example original width) of the picture and just crop the aspect ratio no matter the size of the container? If I upload a picture with dimensions 1200x700px I would like to crop the image to fit the aspect ratio of 16:9 and get 1200x675px. Is this possible?

I've managed to do it by checking the "naturalWidth" on resize and after upload and updating the "quality" based on the width of the container.
Sample for resize event:
if(this.myCroppa.naturalWidth > 0){
   if(picWrapper.getBoundingClientRect().width < this.myCroppa.naturalWidth)
   this.picQuality = this.myCroppa.naturalWidth / picWrapper.getBoundingClientRect().width;
}

can you post a full code?


[Don't merge, these sample depends on app service project] Adding traffic manager, dns and vm from custom and specialized image

Hi @anuchandy, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (anuchan). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

using System.Reflection;

where is my license headers? :))

Refers to: Samples/ResourceManagement/Dns/ManageDns/Properties/AssemblyInfo.cs:1 in cfe168f. [](commit_id = cfe168f27f7cdbe86f6ae61f1db32e40caeb9d7f, deletion_comment = False)

using System.Reflection;

where are my license headers? :))

Refers to: Samples/ResourceManagement/TrafficManager/ManageTrafficManager/Properties/AssemblyInfo.cs:1 in cfe168f. [](commit_id = cfe168f27f7cdbe86f6ae61f1db32e40caeb9d7f, deletion_comment = False)

using System.Reflection;

where are my license headers? :))

Refers to: Samples/ResourceManagement/Compute/CreateVMsUsingCustomImageOrSpecializedVHD/Properties/AssemblyInfo.cs:1 in cfe168f. [](commit_id = cfe168f27f7cdbe86f6ae61f1db32e40caeb9d7f, deletion_comment = False)

@hovsepm ah.. your license header is on the way.. :) // thanks - will update PR

@hovsepm uncommented the app service usage sections in the samples as we discussed, please review..

@azureadkci retest this please


kaggle kernels push -k: unrecognized arguments: -k

On this side https://www.kaggle.com/docs/api#interacting-with-notebooks it says you have to reference the kernel by -k when using kaggle kernels push . But this returns kaggle: error: unrecognized arguments: -k

Hi @tbrodbeck - thanks for reporting this issue!  I've updated our documentation accordingly.


Added HackerNews social link

Thanks. But i don't think anybody would want to show it on their page. Because this link will only show about users's karma, created date etc, not submitted link or something. It's not like reddit.  If somebody really want to add, they can add on their own.

Oh, my mistake. I didn't look very well. It seems they have submissions and comments button. Sorry. :disappointed:


Unknown Error while Deploying

Hey!
I was checking out this website and trying to run my Flask API on it. I am running it on repl.it as of now, but your service fascinates me tbh. Anyways, well it was starting without any error(s) on repl.it and on my local laptop. But while deploying, I am getting this error again and again.
Running micro...

Response:
{
        "errorMessage": "'path'",
        "errorType": "KeyError",
        "stackTrace": [
                "  File \"/opt/python/detalib/debugger.py\", line 154, in wrap\n    raise e\n",
                "  File \"/opt/python/detalib/debugger.py\", line 142, in wrap\n    result = func(event, context)\n",
                "  File \"/var/task/_entry.py\", line 14, in handler\n    return handle(event, main)\n",
                "  File \"/opt/python/detalib/handler.py\", line 32, in handle\n    return handlers.handle_bare_wsgi(event, main, context)\n",
                "  File \"/opt/python/detalib/handlers.py\", line 32, in handle_bare_wsgi\n    return resolve(main.app, event)\n",
                "  File \"/opt/python/detalib/adapters/wsgi/__init__.py\", line 149, in resolve\n    result = app(get_environ(event), response.start_response)\n",
                "  File \"/opt/python/detalib/adapters/wsgi/__init__.py\", line 22, in get_environ\n    \"PATH_INFO\": event[\"path\"],\n"
        ]
}

I have listed both of my dependencies in the requirements.txt (python-aiml and flask) and, if this is important, I don't use deta library in my code. Help would be appreciated!
Thanks!

Hi @Hunter2807, please share your code for us to be able to help you. Feel free to reach out on Slack for faster support.

Hey there @abdelhai!
Thanks for the reply, but the code is quite big. What part do u want? The one, with which I make the Flask API? Actually I have a private AI API and it has some AI files and a JSON file to store some information. Could be something is wrong with the path of those?
Anyways, I cannot give u the whole code cz of privacy purposes too, but I can provide u the code where I make the Flask API. Will that be sufficient?

@Hunter2807 you seem to be using deta run, this command is not related to running your web app. Just visit your Micro URL. You can find it in your dashboard (web.deta.sh) or by running deta details locally inside your project's directory.

Ah, it works now. could be some cache problem that time... BTW, may I know what's the use of deta run then?

Ah, thanks. It works!
Also, do u know how can I access the linux VM for my website?

@Hunter2807 you were getting the error because you were entering the deta run command (no caching issues).
Deta Run is a completely different product that runs on Micros which helps you make web-based CLI apps. You needn't to learn it for Flask, etc.
Micros run automatically after you deploy the code.

Also, do u know how can I access the linux VM for my website?
No.


Notables saved twice

I think this line shouldn't exist. because the method already called inside saveSaves().
https://github.com/DenizenScript/Denizen-For-Bukkit/blob/master/plugin/src/main/java/net/aufdemrand/denizen/DenizenCommandHandler.java#L304
Also, is it okay if denizen save process running outside main thread? would be good to reduce lag spike.

... how many notables do you have that you lag from saving them 0.0

@mcmonkey4eva I mean, for the saves.yml

... how much general disorganized save data do you have that you lag from saving it?

It's not me,
https://one.denizenscript.com/denizen/logs/denizen-dev#2016/10/04-06:01:16

lol big servers with poorly optimized scripts lag... I mean we can only async the saving so far. We can asynchronize the copy from RAM to disk, but it still has to do a lot of sync calculations to ready the save data...
Denizen2 is a lot nicer on save data in theory (it operates within Minecraft's own save data, not in separate YML's)... as far as Denizen1: the trick is to use SQL and YAML commands to optimize things in your scripts, the built in saves are really old and weak :/

yeah, I understand that async isn't always good.
I will close this as the problem is fixed.
Denizen2 looks promising, can't wait for it to ready!


Method to parse URN and convert it into an identifier?

In this task:

https://github.com/metanorma/obp-access/issues/7

We need to obtain the "edition number" from the URN since it is not provided in the PubID.
Do we have a method to parse a URN?

In this task:

Output NISO STS XML format from an ISO OBP HTML obp-access#7

We need to obtain the "edition number" from the URN since it is not provided in the PubID.
Do we have a method to parse a URN?

We are not parsing URNs currently.

Let’s add a mechanism to parse ISO and IEC URNs.


raftstore: set is_merging flag after restart

What have you changed?
Fix a region merge bug, set is_merging flag after restart.
When a crash/restart after prepareMerge being applied before compact log being applied, is_merging is not set so the compact log can not be ignored.
Then panic happens on getting entries for proposing commitMerge.
Add a failpoint test case, previous code panic almost every time I run this test.
What is the type of the changes?

Bugfix

How is the PR tested?

Integration test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

/test


failed to lower mrcnn model(https://github.com/ahmedfgad/Mask-RCNN-TF2) with iree-import-tf

I referrred to https://github.com/ahmedfgad/Mask-RCNN-TF2 and created model with output contains only detection layer.When I run with /data/aruna/iree-latest/iree/integrations/tensorflow/bazel-bin/iree_tf_compiler/iree-import-tf -tf-import-type=savedmodel_v1 -tf-savedmodel-exported-names=serving_default /data/aruna/Mask-RCNN-TF2/detection  --print-ir-after-all &>log.txt -o hlo.mlir
I am getting error as :
error: The following Tensorflow operations still remain:
tf.CropAndResize (count: 4)
tf.DenseToDenseSetOperation (count: 2)
tf.NonMaxSuppressionV4 (count: 1)
tf.SparseToDense (count: 2)
tf.StridedSlice (count: 21)
tf.TensorListFromTensor (count: 1)
tf.TensorListGetItem (count: 1)
tf.TensorListReserve (count: 1)
tf.TensorListSetItem (count: 1)
tf.TensorListStack (count: 1)
tf.TopKV2 (count: 2)
tf.Unique (count: 1)
tf.Where (count: 8)
I was going through the these ops seperately when tried tf.TopKV2 with static inputs I able to lower the op to HLO.
I have attached model file.
saved_model.zip

The first part below indicates tf python API and right hand side is the tf ops corresponding to python tf API.
tf.where->tf.where
tf.sets.intersection->tf.DenseToDenseSetOperation
tf.sparse.to_dense->tf.SparseToDense
tf.unique->tf.Unique
tf.image.non_max_suppression->tf.NonMaxSuppressionV4
tf.map_fn->tf.TensorListFromTensor,tf.TensorListGetItem,tf.TensorListReserve,tf.TensorListSetItem ,tf.TensorListStack
tf.nn.top_k->tf.TopKV2
tf.image.crop_and_resize->tf.CropAndResize
x[2:]->tf.StridedSlice
tf.keras.layers.Conv2DTranspose->tf.Conv2DBackpropInput
tf.keras.layers.UpSampling2D(size=(2, 2),interpolation='bilinear')->tf.ResizeBilinear
tf.keras.layers.UpSampling2D(size=(2, 2),interpolation='nearest')->tf.ResizeNearestNeighbor
In this I took seperate test cases and if shapes are static then I able to lower tf.TopKV2,tf.StridedSlice and tf.Conv2DBackpropInput .tf.ResizeBilinear and tf.ResizeNearestNeighbor if it has argument  half_pixel_centers = false I able to lower to MHLO.
But In this case the output tf.where is dynamic and which is given as input to other ops.  In this model half_pixel_centers=true
these ops are failing while lowering to MHLO using iree-import-tf
Thanks


Add "complex-conjugate"

Although R7RS standardizes procedures related to complex numbers, a procedure for computing the complex conjugate was not included. Which Scheme implementations have a core procedure for computing the complex conjugate of a number?

Excellent. Thanks again!

https://docs.scheme.org/surveys/complex-conjugate/


Support tokio-rusqlite?

It might be valuable to support tokio-rusqlite. We could put that behind a feature, to prevent this crate from becoming heavier in the general case and expose methods that take an “async” Connection.
Feel free to share your opinion in comments or to 👍🏼 / 👎🏼 .

@cljoly I had a first look on how to implement it and unfortunately what I understand is it will require sprinkling a lot of async on multiple functions.
Do you imagine a completely separate implementation or do you have some code sharing in mind?

Thanks for chiming in @Czocher
What you have in mind seems sensible, it seems to allow a bit of code reuse and so the additional maintenance burden would not be too big. Do you have a project already where you would use that library if it supported async?

@cljoly I can provide a PR for you to review in the near future. As for a project - yes. I have a project currently using sqlx but I really love how your project handles the versioning of sqlite and I plan to migrate from sqlx to tokio-rusqlite and rusqlite-migration somewhere after March.

Hey @Czocher , thanks for sharing about your project.
As for the review, I’m happy to review a PR you may send, but I can’t say in advance if I’ll accept it, in particular if the additional maintenance burden it would create is high. I appreciate that this is a significant time investment on your part, so I suggest you share the code early, so that we limit any time lost. Thanks for considering a contribution!

No problem @cljoly, I consider it a fun learning opportunity. I have no expectations regarding if or when it shall be merged ;).

I created a preliminary version for you to have a look at and comment. There's still a couple of things missing/that should be discussed, which I provided as a list in the PR. Feel free to point any other deficiencies.

I would like to see ergonomic rusqlite + async but it's strange that tokio-rusqlite uses a standard thread to spawn the database handler instead of tokio::task::spawn_blocking given the name and all.

@matze I can probably explain the reasoning. I don't know for sure though, just basing it on my experience from other languages.
tokio's executor is based on a certain number (usually equal to the number of CPUs or CPU cores) of OS (red) threads which are created in a pool. Those threads are then assigned to be used by the async tasks to perform their operations.
If a given async task has an await point it is considered a preemption point for the tokio executor. Those preemption points may be of two distinct categories, let's call them red and green (analogous to red - OS - and green - user space - threads).  A green preemption point is when there's no syscall involved, a red one is when a OS call is performed on behalf of this task and it needs to await the result from the OS.
This means that in a best case scenario, when a task only requires green preemption points, the OS threads managed by tokio can be reused to perform other tasks in the meantime while the given task awaits.
On the other hand, when a red preemption point occurs one of the threads from the pool is OS-preempted and therefor cannot be used by the tokio executor for the time being.
Since sqlite is mostly io-bound, and accessing the io layer is a clear red preemption point, it would mean that it would constantly block the given thread. If it was a tokio thread, then it would lower the overall performance of the app, by limiting that thread's usefulness for the tokio executor to be used for other green-preempted tasks.
Choosing a normal red OS thread, instead of a green tokio thread, removed this bottleneck.

Thanks for the explanation. I know you don't want to block the executor or any "real" async tasks but isn't exactly that then the case for tokio::task::spawn_blocking? According to the docs

Runs the provided closure on a thread where blocking is acceptable.

and

In general, issuing a blocking call or performing a lot of compute in a future without yielding is problematic, as it may prevent the executor from driving other futures forward. This function runs the provided closure on a thread dedicated to blocking operations.

Good point @matze, raising an issue with tokio-rusqlite would be a good idea. Either we'd fix this overlook or get a definitive answer as to why this solution was chosen.


resnet18: AttributeError: 'SVDDecomposedConvLayer' object has no attribute 'min_rank'

SVDDecomposedConvLayer has no min_rank field. I'm getting exception.
Anaconda3\envs\musco\lib\site-packages\musco\pytorch\compressor\decompositions\svd_layer.py in __init__(self, layer, layer_name, rank_selection, rank, pretrained, vbmf_weaken_factor, param_reduction_rate)
    157
    158         if rank_selection == 'vbmf':
--> 159             self.rank = estimate_vbmf_ranks(self.weight, vbmf_weaken_factor, min_rank = self.min_rank)
    160         elif rank_selection == 'manual':
    161             self.rank = rank

AttributeError: 'SVDDecomposedConvLayer' object has no attribute 'min_rank'

because of https://github.com/musco-ai/musco-pytorch/commit/6e4c9477efa330c5b679a482efe912e43f7c8a06

hi everybody! can anyone fix it? doesn't seem like a big issue more like a bug.

hi everybody! can anyone fix it? doesn't seem like a big issue more like a bug.

https://github.com/musco-ai/musco-pytorch/blob/master/musco/pytorch/compressor/decompositions/svd_layer.py#L168
looks like out_features/in_features should be considered too....

https://github.com/musco-ai/musco-pytorch/blob/master/musco/pytorch/compressor/decompositions/svd_layer.py#L168
looks like out_features/in_features should be considered too....

any fix?

Hi @aupuzikov and @aswanthkrishna, thank you for noticing this bug! Now it is fixed

thanks a lot :)

It seems not to be fixed if it gets installed with pip. I still have:
~/anaconda3/lib/python3.8/site-packages/musco/pytorch/compressor/decompositions/svd_layer.py in __init__(self, layer, layer_name, rank_selection, rank, pretrained, vbmf_weaken_factor, param_reduction_rate)
    157
    158         if rank_selection == 'vbmf':
--> 159             self.rank = estimate_vbmf_ranks(self.weight, vbmf_weaken_factor, min_rank = self.min_rank)
    160         elif rank_selection == 'manual':
    161             self.rank = rank

AttributeError: 'SVDDecomposedConvLayer' object has no attribute 'min_rank'

I used musco-pytorch 1.0.6. Solution:
pip uninstall musco-pytorch -y
git clone https://github.com/musco-ai/musco-pytorch
cd musco-pytorch
python setup.py install

This results in:
~/anaconda3/lib/python3.8/site-packages/numpy/linalg/linalg.py in _raise_linalgerror_svd_nonconvergence(err, flag)
    104
    105 def _raise_linalgerror_svd_nonconvergence(err, flag):
--> 106     raise LinAlgError("SVD did not converge")
    107
    108 def _raise_linalgerror_lstsq(err, flag):

LinAlgError: SVD did not converge

or
~/anaconda3/lib/python3.8/site-packages/numpy/lib/function_base.py in asarray_chkfinite(a, dtype, order)
    495     a = asarray(a, dtype=dtype, order=order)
    496     if a.dtype.char in typecodes['AllFloat'] and not np.isfinite(a).all():
--> 497         raise ValueError(
    498             "array must not contain infs or NaNs")
    499     return a

ValueError: array must not contain infs or NaNs

Which would be a new issue though, but I thought I at least mention it. The output seems random. Used code from Github readme.


Razorpay Added in the table

Razorpay is the Indias biggest payment gateway. They have a repository for Omnipay. Therefore I am adding it to the table.

Razorpay added to the table.


Could not resolve file for path 'snippets/16-bizarre-javascript'

Thanks @dalirnet for catching the typo, It's fixed in #1


Heartbeats being sent, despite no publishing.

I have a publishing application on one host and an instance of Aeron Archive running on another host. On the publishing host, I'm observing within AeronStat that Bytes sent and Heartbeats sent continue to increase, even after I've terminated the publishing program (pub-pos does not increase). This causes the recording within Archive to be considered active, which precludes it from deletion. I'm currently mitigating this by restarting aeronmd.
Is there something I need to configure to have the publication deleted in the driver after some timeout where pub-pos isn't incremented? Thanks!
I've also got ssc=True and fc=min set on this channel.

Anecdotally, I'm also observing that this isn't happening when I reduce the publish rate of my application.

Do you still have an active subscription somewhere that hasn't reached the most recent published position.  This will result in a publication remaining active in the driver.

There wasn't an active subscription here, outside of the one that I imagine exists in the Archive.

How long did you see heartbeats being sent for?  There is also a linger timeout associated with publications before they get removed from the driver.  If it was indefinite, could you post a code example that demonstrates the problem?  Also did you check see if the publication is still visible in AeronStat?

We'll reopen if this become a priority again; it initially manifested when we were under an unrealistically high load.


Is there any interactive viewer to see results?

Hi,
Thank you so much for your work.
I am testing and get nice rendering results.
However, it will be wonderful if I can render and check using an interactive viewer similar to nerfstudio. Is there any viewer which help me to do that, or guide me how to do?
Thank you in advance and hope get your help.

The closest thing we have for that is https://smerf-3d.github.io/, but the training/baking code for that hasn't been open-sourced yet.

The closest thing we have for that is https://smerf-3d.github.io/, but the training/baking code for that hasn't been open-sourced yet.

Thank you so much for your help, @jonbarron  .
I also see that SMERF is another wonderful work, but code has not open-sourced yet. Hope one day can use this code for testing.
Many thanks.

I'm also interested.


VERGE appears to ignore some VERGE.conf settings and hangs.

VERGE on my end is compiled from source and it appears to be hanging, never loading the QT GUI. When I check the debug.log it seems like it's mining for coins although I have set gen=0.  Check the attached files.
VERGE.conf
debug.log

on what os? arch?

also which version of qt are you using? this requires qt webkit, so that might be the issue

I have the qt5 set including webkit

hmm. something had to have happened during compilation.. do you have a log of the configure or make still?

also just to clarify, the daemon is working properly on arch, just not the qt wallet?

Both VERGEd and VERGE-qt isn't working correctly for me.   Attached is a build log.
build.txt

New log attached
VERGE-qt --debug
debug.txt

well i've narrowed it down to a lib or qt thats included in arch and the newest ubuntu (16.04). ill keep this issue open until i've got it patched. i was able to reproduce this result on ubuntu 16.04, and it's syncing even though it's still showing the Done Loading screen and the wallet hasn't opened. When it finishes, if it opens, it'll be much easier to narrow down. thanks for reporting this and supplying information to me =]

@ShapeShifter499 is this still happening?

I'm not ShapeShifter499, but yes it's still happening here. I suspect it's an "improvement" in QT. But I also get a hung wallet that doesn't get past the splash screen. It's busy downloading blocks in the background. I don't know yet if the gui appears when it's caught up.

Nope ... the github compiled version still hangs in Linux land even after all the blocks are loaded.

@Fluffkin i'll get to the bottom of this..

bottom reached yet? :D

Hehehe .. I fixed it .. but can't remember how .. (yes! one of those posts! sorry internet!)

dangit internet!

plz close this issue already @justinvforvendetta  :P

never! @buzztiaan

This linux GUI hang issue was brought up like 16 months ago in v2.1 to the DEV by multiple people in IRC,  even a couple times since then check the channel logs ;)
I am quite surprised it still has not been addressed till this day #Progress

@PrintedNOTmade we stop pursuing the issue when @fluffkin said he fixed it, @Fluffkin what did you do to fix this on your end?

Wakes up ... Eh?
Well .. it was one of those .. I compiled it for the Nth attempt .. wandered off, did other things for a few days, came back to it, ran the binary and it worked .. occasions ..
I think it was related to my Qt5 installation at the time. The current Qt5 configuration in Gentoo seems fine with producing a running version, and I'm fairly sure the Qt4 version (even though it looks like it compiles ok), doesn't play nice. I also seem to remember trying Qt5 earlier and it didn't work initially, so I have to assume I had something borked that then got upgraded.
Sorry folks, it's all I've got!

@PrintedNOTmade what version of qt did you have?

super old - - closing issue -- please re-open or open new issue if this is still a problem with the latest release


KeyError: 'LlavaConfig'

Traceback (most recent call last):
File "/remote-home/zhubin/LISA/chat.py", line 263, in
main(sys.argv[1:])
File "/remote-home/zhubin/LISA/chat.py", line 76, in main
tokenizer = AutoTokenizer.from_pretrained(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/anaconda3/lib/python3.11/site-packages/transformers/models/auto/tokenization_auto.py", line 718, in from_pretrained
tokenizer_class_py, tokenizer_class_fast = TOKENIZER_MAPPING[type(config)]
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/root/anaconda3/lib/python3.11/site-packages/transformers/models/auto/auto_factory.py", line 663, in getitem
model_type = self._reverse_config_mapping[key.name]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'LlavaConfig'

the same problem...have you solved it?

try to download this weights again and it runs successfully

the same problem...have you solved it?

try to download this weights again and it runs successfully

yes，it is


Add a Notes field to Environments

Underneath the Env name and client side key, add a textarea called "Notes" that can store 20kb of text.

Please add the API for this then assign to @kyle-ssg

Is the FE done for this? If not please assign @kyle-ssg !

@kyle-ssg new field called description on the environment.


Modified e2e regression tests to reproduce only one bug

The e2e regression tests on every PR were reproducing all the bugs and hence consuming a lot of time. Have modified it to reproduce only one bug (chosen at random).

The change looks good, just a minor comment on naming the tests, as the first step to make the per-PR bug reproduction CI work again. I think we should explicitly name the tests as bug reproduction tests, because there are other regression tests in the repo that are not doing bug reproduction.
We will add a weekly action to reproduce all bugs after this.

I think the Regression Test / unittest (push)  action is also running the bug reproduction, because of how the pytest mark is specified in its action file. We may need a good way to distinguish between unittest and end-to-end tests

@ThrivikramanV Do you know what is causing the e2e test to be canceled?

I had manually canceled it since I assumed that it would be running the original regressions (reproducing all the bugs) until we merge this PR with main. Is this not the case?

I think it would run against the PR branch, which contains the updated github actions.
The only thing to fix is the Regression Test / unittest (push) I think


[BUG]开启kerberos认证之后，隔一天之后tgt失效

在开启了kerberos之后，上传文件到hdfs正常。
但是过了一天之后，tgt失效了，再次上传文件，后端api-server的日志中报kerberos认证失败。无效的tgt。

重启escheduler服务之后，上传文件到hdfs正常，kerberos认证正常。

OK，I will check it out.

Beacuse HadoopUtils is singleton
so need modify below if kerberos is startup ：
public static HadoopUtils getInstance(){
// if kerberos startup，need new instance
if (CommonUtils.getKerberosStartupState())  {
return new HadoopUtils();
}
return instance;
}

Hello! I also encountered this problem, file upload hdfs to read the file on the hdfs normal, do the timing task, but after a day to execute the failure, reported tgt failure, this case I restart the next work process to return to normal, but if there is no scheduled task to carry out, I would be OK to carry out a few days later, what is the reason? SOLVER!


Eigen update needed to fix tensorflow build failure on ppc64le

Request to update Eigen in TF to https://gitlab.com/libeigen/eigen/-/commit/06c2760bd1139711eeffa30266ead43423891698
to fix compilation issue on ppc64le.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux CentOS 7
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source master branch
TensorFlow version:
Python version: 3.9
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 3.7.2
GCC/Compiler version (if compiling from source): gcc 9, gcc8, gcc 7
CUDA/cuDNN version: NO CUDA (CPU only)
GPU model and memory:

Describe the problem
While building tensorflow on ibmcom/tensorflow-ppc64le:devel-manylinux2014 docker image for ppc64le and using gcc 9 (tried gcc 8 and gcc 7 too), we are seeing a compilation error related to Eigen. The fix for the same has been pushed to Eigen repository yesterday at https://gitlab.com/libeigen/eigen/-/commit/06c2760bd1139711eeffa30266ead43423891698
If TF updates the eigen version to the above mentioned commit, we will get the issue fixed without any patching.
Provide the exact sequence of commands / steps that you executed before running into the problem
BAZEL_LINKLIBS=-l%:libstdc++.a bazel build -c opt --config=v2 --local_cpu_resources 4 --local_ram_resources 4096 \
    //tensorflow/tools/pip_package:build_pip_package
bazel-bin/tensorflow/tools/pip_package/build_pip_package --nightly_flag --cpu $WORKSPACE/tensorflow_pkg```

Error:
tensorflow/compiler/xla/service/cpu/runtime_single_threaded_matmul.cc:121:76:   required from here
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:498:20: error: taking address of rvalue [-fpermissive]
  498 |             lhs0 = &lhs(j + 0, i);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:499:20: error: taking address of rvalue [-fpermissive]
  499 |             lhs1 = &lhs(j + 1, i);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:501:20: error: taking address of rvalue [-fpermissive]
  501 |             lhs0 = &lhs(j + 2, i);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:502:20: error: taking address of rvalue [-fpermissive]
  502 |             lhs1 = &lhs(j + 3, i);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:505:20: error: taking address of rvalue [-fpermissive]
  505 |             lhs0 = &lhs(i, j + 0);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:506:20: error: taking address of rvalue [-fpermissive]
  506 |             lhs1 = &lhs(i, j + 1);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:508:20: error: taking address of rvalue [-fpermissive]
  508 |             lhs0 = &lhs(i, j + 2);
      |                    ^~~~~~~~~~~~~~
external/eigen_archive/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:509:20: error: taking address of rvalue [-fpermissive]
  509 |             lhs1 = &lhs(i, j + 3);
      |                    ^~~~~~~~~~~~~~

I think this should be resolved now?

@npanpaliya,
Looks like issue is resolved, Take a look at similar thread #45746. Thanks!


Incorrect URL in azure-asyncoperation header in the response for PUT deployment

Steps to reproduce

Create a sample deployment:-
URL: http://<IP_ADDRESS>:8001/apis/api.ucp.dev/v1alpha3/planes/radius/local/resourceGroups/default/providers/Microsoft.Resources/deployments/my-deployment
Body:

{
    "properties": {
        "mode": "incremental",
        "template": {
            "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
            "languageVersion": "1.9-experimental",
            "contentVersion": "<IP_ADDRESS>",
            "metadata": {
                "_EXPERIMENTAL_WARNING": "Symbolic name support in ARM is experimental, and should be enabled for testing purposes only. Do not enable this setting for any production usage, or you may be unexpectedly broken at any time!",
                "_generator": {
                    "name": "bicep",
                    "version": "<IP_ADDRESS>",
                    "templateHash": "16752784152099553522"
                }
            },
            "parameters": {
                "application": {
                    "type": "string",
                    "metadata": {
                        "description": "The app ID of your Radius Application. Set automatically by the rad CLI."
                    }
                }
            },
            "imports": {
                "radius": {
                    "provider": "Radius",
                    "version": "1.0"
                }
            },
            "resources": {
                "sim1": {
                    "import": "radius",
                    "type": "Applications.Core/containers@2023-10-01-preview",
                    "properties": {
                        "name": "sim1",
                        "properties": {
                            "application": "[parameters('application')]",
                            "container": {
                                "image": "ghcr.io/radius-project/samples/demo:latest",
                                "ports": {
                                    "web": {
                                        "containerPort": 3000
                                    }
                                }
                            }
                        }
                    }
                }
            }
        },
        "parameters": {
            "application": {
                "value": "/planes/radius/local/resourceGroups/default/providers/applications.core/applications/demozz"
            }
        }
    }
}

You should see a 201 response. Check the URL returned in the azure-asyncoperation response header:- https://<IP_ADDRESS>:443/apis/api.ucp.dev/v1alpha3/planes/radius/local/resourcegroups/default/providers/Microsoft.Resources/deployments/my-deployment/operationStatuses/08584955639081991237?api-version=2020-10-01
This has incorrect version number
Observed behavior
The URL returned: https://<IP_ADDRESS>:443/apis/api.ucp.dev/v1alpha3/planes/radius/local/resourcegroups/default/providers/Microsoft.Resources/deployments/my-deployment/operationStatuses/08584955639081991237?api-version=2020-10-01 has an incorrect version number
Desired behavior
The URL returned should be directly usable.
Workaround
No response
rad Version
0.29.0    v0.29.0   0.29.0    6abd7bfc3de0e748a2c34b721d95097afb6a2bba

Operating system
macOS Sonoma
Additional context
No response
Would you like to support us?

[ ] Yes, I would like to support you

AB#10980

We now have a workaround for this issue, so we may want to remove the important label.


fixes #743 made data classes final

Now that Bytes objects are no longer created using the MutableBytes in core.  I think we should move back the tests in org.apache.fluo.core.data to org.apache.fluo.api.data.

Now that Bytes objects are no longer created using the MutableBytes in core. I think we should move back the tests in org.apache.fluo.core.data to org.apache.fluo.api.data.

Good point.  However, I think the vint thing will impede this effort.  I was thinking I would like to get rid of it too.  Maybe  I can do that in a follow on PR and move the test.

Re removing vint thing, I opened #746.

+1


[Business Rules Validation]Business Rules "passed" not displayed in "open status screen" when some schema versions do not match

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[ ] Bug affects both Android and iOS, for specific issues - I only tested for Android, please check IOS
[x] Bug is not already reported in another issue

Technical details

Device name: LGH-815 (but should be true for all)
iOS/Android version: Android 6.0 (but should be true for all)
App version: 2.6.1

Describe the bug
When DCCs are validated against the business rules of countries of arrival (CoA), CWA (and other wallet apps) need to show an "open status screen", when at least one rule could not be validated due to schema version mismatch between DCC schema version and business rule schema version. For example, as of today (07.08.2021) the Netherlands are providing business rules for vaccination certificates with schema version 1.3.0, while many vaccination certificates in Germany have been issued with schema version 1.0.0. In result, CWA currently shows for vaccination DCCs (issued before July 1st) an "open status screen" when validating against NL business rules, where every business rule is displayed for the vaccination certificate to be able (for human beings) to verify, if every rule nevertheless is compliant with requirements for vacc. DCCs set up by the NL health authorities.
But now NL added some rules for test certificates (TR-NL-0005, TR-NL-0006), where the schema version is set to "1.0.0", while other business rules for test DCCs are still schema version "1.3.0".
All business rules with schema version 1.3.0 are resulting in a status "open", and they are displayed accordingly in CWA's validation information screen. But rules that pass validation with status "pass", are not shown at all.
It would be expected, that in case some rules pass but other rules are "open" that CWA shows all rules with their related DCC content, so that the human user is able to validate its complete DCC against information found on https://reopen.europa.eu .
By the way: the other way round it's working well: when one rule fails while all other rules are "open", then CWA shows all results correctly (failed rules on top, open rules below), see https://github.com/corona-warn-app/cwa-documentation/issues/671#issuecomment-894494672. So "fail/open" is correct, "pass/open" is not correctly displayed.
Steps to reproduce the issue

Scan TEST DCC above. The sample of the rapid immunoassay was/will be taken at 09.08.2021T10:00:00Z, and is valid for 24 hours according to rule TR-NL-0006.
Check validity of DCC against Netherland rules between/for entry time between 09.08.2021T10:01:00Z and 10.08.2021T10:00:00Z
See that rule TR-NL-0006 is missing in the list of all rules displayed. But it should show up (either as "passed" or at least as "open").
Check validity of DCC against Netherland rules after/for entry time after 10.08.2021T10:00:00Z.
See that rule TR-NL-0006 is displayed correctly as failed, while all other rules are displayed as open.

Expected behaviour
When checking  validity of DCC against Netherland rules between/for entry time between 09.08.2021T10:01:00Z and 10.08.2021T10:00:00Z, the rule TR-NL-0006 should be displayed as either "passed" or also as "open", when using DCC you find above.
Possible Fix
Align logic to display validation results with mixed rules "pass/open" to the logic "fail/open".
Additional context
You'll find the related NL business rules here:
Acceptance_Rules-NL-20210806.json.txt
Pay attention to rules TR-NL-0006 (for antigen test used here) and TR-NL-0005 for NAAT.

Internal Tracking ID: EXPOSUREAPP-8909

An unpleasant additional problem ... different EU vaccination certificates with different QR codes for one and the same vaccination and person!
Please verify.
There are different EU vaccination paper certificates (1) for one and the same vaccination of the same person, which can or lead to different results when the certificate is checked by the CWA with regard to entry requirements!
(1): EU certificates with "QR code left and text right" (old) and "text left and QR code right" (new).
Technical details:
Samsung Galaxy Note 10, SM-N970F/DS
Android 11 (One UI 3.1) with Android security update: 01. July 2021
Google Play-Systemupdate: June, 1st, 2021.
CWA Version: 2.6.1
ENF:<PHONE_NUMBER>0
Describe the problem:
I have two different EU vaccination certificates for myself (with identical dates); once in the 'version old' (QR code on the left and text on the right https://github.com/corona-warn-app/cwa-app-android/issues/3514#issuecomment-865872016) and once in the 'version new' (text on the left and QR code on the right; see PS below); downloaded from my account at the local vaccination center.
Actually, I assumed that the QR codes were identical in each case - after all, as I said - it is the same two vaccinations. 'Old version' of the EU vaccination certificates was downloaded on June 21, 2021; 'Version new' on 07/30/2021.
Due to @vaubaehn's post, I have tested my two scanned EU vaccination certificates ('version old' and 'version new', each certificate from sheet 2/2, BionTech) with the entry date "09.08.2021T14:00:00Z" for the Netherlands and get different results!
Result (EU vaccination certificate, 'version old' (QR code on the left and text on the right)):

Result (EU vaccination certificate, 'version new' (text on the left and QR code on the right)):

Steps to reproduce the issue:
For the EU certificate 'version old' (QR code on the left and text on the right):

Select "Certificates"
Select your 'old certificate' (2/2): scroll down, check the URN with paper print to be sure to have the old certificate!
Check validity of DCC against Netherland rules for entry time 09.08.2021T14:00:00Z
Result: “Result (EU vaccination certificate, 'version old')…”; see above.

For the EU certificate 'version new' (text on the left and QR code on the right):

Select "Certificates"
Select your 'new certificate' (2/2): scroll down, check the URN with paper print to be sure to have the new certificate!
Check validity of DCC against Netherland rules for entry time 09.08.2021T14:00:00Z
Result: "Result (EU vaccination certificate, 'version new')..."; see above.

Selecting the certificates:

Additional context:
I cannot check and evaluate what is normal, wrong or right here - in this respect I would like my post to be understood as a reference to be checked.
However, it might be helpful to have a hint for the user that says which of his EU vaccination certificates - if the user has several - should be used. At the moment it seems clear: the newer (currently the one with the “text on the left and QR code on the right” (new); see above) should be used.
But then it also applies: if you have the EU certificate "QR code left and text right" (old), you should get a newer one.
And what if more versions of the EU certificates come out with further QR code changes?
Possible Fixes:
Due to the different sizes of the QR codes (hopefully there are more unique version numbers in the QR code or similar) between "QR code left and text right" (old) and "text left and QR code right" (new) it could be determined which version the scanned EU vaccination certificate is. A note could be derived from this stating that the EU vaccination certificate should be renewed.
If relevant, the CWA could even check itself whether the stored certificates are stored in the current version of certificate.
Derived from the size of the QR code (or clearer version differences), the standard QR code displayed / used by CWA could be the most current / valid in each case.
Unfortunately, the QR code of the first scanned, i.e. older, certificate is currently displayed by default.
Alternatively, it would also make sense to simply advise the user to delete their old QR codes. However, these should then be marked in some way.
...
Overall, however, I cannot evaluate whether my mentioned 'possible fixes' represent sensible, permanent solutions.
In this sense, best regards, Joachim.

PS: The Links “DCC Certificate of Recovery“, ”DCC Test Certificate“ and “DCC Vaccination Certificate” in https://github.com/Digitaler-Impfnachweis/certification-apis/tree/master/templates are actually wrong: error 404.

@Jo-Achim

There are different EU vaccination paper certificates (1) for one and the same vaccination of the same person, which can or lead to different results when the certificate is checked by the CWA with regard to entry requirements!

It is to be expected if an EU digital vaccination certificate is reissued, that it will have a different QR code. That is because the date of issue will be different (not the date of vaccination) and that date is included in the QR code.
The reason that you are getting different results for the check with the Netherlands is probably because the older certificate is using the 1.0.0 scheme and the newer one is using 1.3.0.
The simplest workaround is to remove any older vaccination certificates from CWA and just leave the newest 2 of 2 certificate in the app. You don't need any older certificate.
It would be better for you to post your issue as a separate new one. It is actually more related to https://github.com/corona-warn-app/cwa-app-android/issues/3838.
The CovPass-App currently also chooses the first certificate which was scanned in. See https://github.com/Digitaler-Impfnachweis/covpass-android/issues/57.

PS: The Links “DCC Certificate of Recovery“, ”DCC Test Certificate“ and “DCC Vaccination Certificate” in https://github.com/Digitaler-Impfnachweis/certification-apis/tree/master/templates are actually wrong: error 404.

You should report this issue in the https://github.com/Digitaler-Impfnachweis/certification-apis repository.

@vaubaehn Thank you very much for detailed report: Internal Tracking ID: EXPOSUREAPP-8909

@MikeMcC399
Thanks for information.
It is understandable that there are newer versions of the EU vaccination card from time to time. But if older versions lead to the above-mentioned test result "Your certificate could not be fully checked", I will stick to my 'possible solutions' in https://github.com/corona-warn-app/cwa-documentation/issues/679#issuecomment-895154648.
For example:

If relevant, the CWA could even check itself whether the stored certificates are stored in the current version of certificate.

... with appropriate information.
This would also prevent some possible frustration with the CWA.
Because a “normal consumer” who, for example, had an EU vaccination card issued - in his pharmacy, at the doctor's or in the vaccination center - hardly ever comes up with the idea that he might need a more recent certificate for the same vaccination. Therefore I think...

The simplest workaround is to remove any older vaccination certificates from CWA and just leave the newest 2 of 2 certificate in the app.

From my point of view, the easiest way is not the best here. Especially if further 'newer' vaccination certificates are expected in the future.

Unfortunately, the QR code of the first scanned, i.e. older, certificate is currently displayed by default.

It would be better for you to post your issue as a separate new one. It is actually more related to corona-warn-app/cwa-app-android#3838.

I think this point is already dealt with extensively there. But is that just an Android problem only?
Nevertheless, I added a cross-reference to my post above: https://github.com/corona-warn-app/cwa-app-android/issues/3838#issuecomment-895282720.

PS: The Links “DCC Certificate of Recovery“, ”DCC Test Certificate“ and “DCC Vaccination Certificate” in https://github.com/Digitaler-Impfnachweis/certification-apis/tree/master/templates are actually wrong: error 404.

Done in: 'Wrong links in “DCC Certificate of Recovery“, ”DCC Test Certificate“ and “DCC Vaccination Certificate”'.

@MikeMcC399

The CovPass-App currently also chooses the first certificate which was scanned in. See Digitaler-Impfnachweis/covpass-android#57.

According to my knowledge and test, this is no longer relevant!
CovPass version 1.28.7 shows the more recent EU vaccination certificate by default.
Compare the CWA screenshot here under "Selecting the certificates:" above with this one from CovPass (v1.28.7):

(It is sure, that this selected certificate is the newer one.)
Best regards, Joachim.

@vaubaehn I guess this was not fixed in the meantime, was it?


Correct grammatical issues on Intro page

Related to issue #121

@ddavison could you close the issue related to it? Or what else needs to be done?

almost, it looks like point 2 wasn't satiated


feat: make the dependency manager accessible on ManagerAccessMixin

What I did
I noticed when trying to manager global dependencies in python, it can be awkward referencing the local project to do this.
this makes it less awkward.
How I did it

How to verify it

Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

Are there other places where this would be useful?

I don't think so, most everything uses the ManagerAccessMixin, so this basically fixes it all in 1 spot!


500c011 error will not clear

I'm running bambu-farm (1.3) with 6 P1S's.  All are on the latest firmware (<IP_ADDRESS>). I have a single Panda Touch connected to all 6
2 out of 6 printers show this error which I believe is a false error based on a previous issue.

power cycling does not help.
is there anyway to clear this error or determine what is causing the error.

closing issue because it has gone away with firmware 1.07


Support USE statement (Issue #109)

Fixes #109
We can now perform "USE <keyspace name>" in session like this:
session.use_keyspace("ks").await ?;

This is propagated to all active and future connections.
Session gets a new field:
struct Session {
    current_keyspace: AsyncRwLock<Option<String>>,
    // ...
}

While this lock is locked current keyspace can't change so all operations adding new connections should lock it when manipulating pool.
pick_connection is a bit complex but I don't see any easy way to fix it and it will probably get rewritten soon when #118 gets implemented.

This PR needs a big rewrite because of #140 and #144, I will do it once #144 gets merged.

This PR needs a big rewrite because of #140 and #144, I will do it once #144 gets merged.

This required a full rewrite, I did it on a new branch in #160


Forming a Magic Square (Hackerrank)

I would like to add the solution to this problem from Hackerrank.
Link to the problem is https://www.hackerrank.com/challenges/magic-square-forming/problem.
I would like to add my solution to this problem in Java language.
Please assign this issue to me under LGM-SoC'21.
Programming language

[ ] C
[ ] C++
[x] Java
[ ] Python

@Ayush7614 Please assign it to me under LGM-SOC'21, I will implement it in C++

please assign it to me under LGM-SOC21 , in java


Could not resolve "ethers/lib/utils.js" in React vite

Getting Error Could not resolve "ethers/lib/utils.js" in React vite.
Version:-
connectkit @1.1.2
wagmi @0.11.0
react @18.2.0

Just checking with you here. You need ethers as well, did you install that as well?
If not, use yarn add ethers or npm install ethers

hey @starc007 can you confirm that you've installed ethers? thanks ☺

yes, ethers was installed...

for now, you need to downgrade to ethers@5. More context: https://github.com/wagmi-dev/wagmi/issues/1785

@kremalicious is correct, wagmi hasn't included support for ethers v6 yet so we require v5.
our peer dependency config should have thrown an error for you on install, but this may have been easily missed.
we've also recently updated the docs to reflect this with the following for the install script:
npm install connectkit wagmi ethers@^5


fix(theming): light text on colored backgrounds should be opaque

According to Material Design Guidelines, white text on colored backgrounds should be displayed at an opacity of 100%.
I also changed the naming of the variables to [dark/light]-primary-text instead of [black/white]-87-opacity, since it better reflects the names used in the guidelines.
This PR fixes #6236

I signed it!

@josephperrott can you take a look to see how this compares to the spec / mdc-web?

@jelbourn
These changes match up with the values currently in the spec (under the heading Text on backgrounds)
MDC uses the same opacity in their theming
@Maistho Can you rebase the PR?

@josephperrott I've rebased it!

@Maistho Looks like there are some build errors now?

@josephperrott Sorry, I had apparently used $dark-disabled in some places and $dark-disabled-text in others.
Fixed it and rebased on master again.

Caretaker note: this PR will likely affect many screenshot tests and should be synced by itself. Reach out to teams to ensure that everything still looks correct.

Hi, what's the status on this PR? Anything I can do to help speed things up?

Our merge process is just a bit behind at the moment; see https://github.com/angular/material2/blob/master/CODE_REVIEWS.md#how-prs-are-merged for more context.
This change is particularly involved because it involves updating many screenshot tests.

@Maistho looks like there is a test failure on CI- can you rebase and see if it goes away?

@Maistho can you also restore the removed scss variables and mark them as deprecated? Upon running an internal presubmit it turns out quite a large number of apps consume on them.

@jelbourn I've rebased it!
How do I add the deprecation notice? Not sure if you use sassdoc, if I should add it to the commit message, or if there's some other way.
I added sassdoc compatible comments for now.

Looks good to me

@jelbourn Tests pass - do you consider this a patch or minor

I would consider this acceptable for a patch because it only changes colors


[Nova] Deeply nested reducers dont work and freeze the app running it

Describe the bug
When you have a reducer that depends another reducer that also depends another reducer the query freezes the app. Nova can support 2 reducers deep, 3 or more makes it fail.
  addReducers(Deals, {
    notesLength: {
      dependency: {
        notes: true,
      },
      async reduce(deal) {
        return deal.notes?.length;
      }
    },
    hasNotes: {
      dependency: {
        notesLength: true,
      },
      async reduce(deal) {
        return deal.notesLength > 0;
      }
    },
    sureItHasNotes: {
      dependency: {
        hasNotes: true,
      },
      async reduce(deal) {
        return hasNotes === true;
      }
    }
  });

  const tasks = await query(Deals, {
      _id: 1,
      name: 1,
      sureItHasNotes: 1,
  }).fetch();

With this reducers notesLength works ok, hasNotesworks ok, but sureItHasNotesfreezes the app running the query.
To Reproduce
Just add reducers like in the example and create a query that calls the deeply nested reducer.
Expected behavior
The query should not freeze, and should return the values of hasNotes.
Desktop (please complete the following information):

OS: OSX
Node 20.9

I think it’s because of a failed reduce promise? It should be deal.hasNotes === true.
but tell me how the app hangs as we should have descriptive errors everywhere

@pmogollons please confirm if this has been fixed with the one above and also what does it mean to 'freeze'? It blocks the server into infinite loop?

Yes, still having the issue. The server is blocked, in some cases I cant even close the terminal as it gets completely blocked or freezed. It doesnt crash.

Sorry for the delay<EMAIL_ADDRESS>should be fine now with as many dependencies as you wish.


Error  already exists outside of <...> package hierarchy due to missing packages

This is more to document an issue I encountered following an S/4 upgrade. Perhaps the error handling could be improved, but not the highest priority.
When I wanted to update abapGit, it came back with a bunch of these:

It turns out that the upgrade (S/4 2022 -> 2023) wiped out all non-SAP local packages starting with $. Just deleted, leaving orphaned objects, and everything still functioning as normal.
The message was misleading, could possibly be improved here: https://github.com/abapGit/abapGit/blob/01df9ce9484ca261fbbdc83a98b90730d4345264/src/repo/zcl_abapgit_repo_status.clas.locals_imp.abap#L222 but definitely not a high priority. My first thought is to simply check if the assigned package actually exists and just pull the package if not. That's working around a situation that isn't consistent to start with.
My solution was to run abapGit standalone, then on the pull screen only selecte DEVC's to pull all the packages first and get the system consistent before pulling anything else, just to be on the safe side.

(as an aside, the background of this popup reloads unnecessarily after each tick mark, causing a delay of several seconds per click)
There were a few more 'odd' messages on subsequent pulls (duplicate instances of objects found and others), but after 3-4 pulls it eventually corrected itself and got back to a clean pull state.

also see #3224

i hate changing custom code to work around SAP bugs. how on earth did the upgrade drop $ packages? what's the SAP note/fix for this?

Oh don't get me started talking to SAP about it... we're on RISE, which in marketese means SAP manage the system and it's all wonderfully cloudy and fluffy and they're with you every step of the way. The reality is that SAP outsource their part and we have to deal with a shocking level of incompetence (*). So I don't bother asking because life's too short.
But interesting that other have experienced this on a 1709->1909 upgrade, so this is a regular thing. I also have my own local $ZPACKAGE and sub packages underneath that and they also all got wiped out. The object still exists and references $Z... in TADIR but the package itself is gone.
(*): For example, it took two months just to get connectivity from Private Cloud to GitHub. Should in theory be a simple matter of adding GitHub.com to a firewall allowlist or similar. Several tickets, several attempts to explain the requirement. Then they kept assuring us it was done and each time we gave them the same SM59-test-failed screenshot and instructions how to use SM59 to test it.

And the background update is not related to the SAP Note or issue. It's this:
https://github.com/abapGit/abapGit/assets/25539927/4c25bf4b-ec48-406a-8370-edd28b0d7f58
With more objects the refresh takes longer, 4-5 seconds on my case. Not a big deal, and may be related to my using HTMLGUI.

That's unfortunately a general issue with HTMLGUI: round trips refresh all of the HTML

Possible root causes for the missing $ packages:

SAP Note 2478895 - ATO Package Lost in Upgrade
SAP Note 3066003 - Check of changeability of $ package component

In transaction S_ATO_SETUP, you can find a little hint:
"Please use packages which will survive the upgrade (e.g. packages which start with "TEST" )."

Hey Marc, great find!
The first note does state it explicitly:
In an upgrade all $ Packages get lost
Solution
1 Solution: Recreate the $ packages
So I guess it wasn't just a quirk of our upgrade but a general 'feature' of upgrades. Thanks for confirming.
Let's leave this issue open for a couple of weeks and I'll see if I can find time to fix up as this may be worth addressing if it's going to affect anyone who's using a $ package and upgrading.

Yeah, I'm dealing with wiped out $-packages every other week. So certainly a fix for this would be appreciated.
Also had some upgrades where basis consultants insisted on deleting all $-packages before the upgrade.

Modern day practice:
Serialize TDEVC and TDEVCT to a repo before SAP upgrades 😉

Modern day practice:
Serialize TDEVC and TDEVCT to a repo before SAP upgrades 😉

or just move the code thats needed in DEV to production
anyhow, theres also packages starting with something like "TEST_" or something, which acts like "$", perhaps they are handled differently?

apparently T-packages survive. still i call this a major sap bug. as a customer i would not rest until i had an SAP note

close? the packages were deleted by SAP

Given this is a known 'quirk', I still think abapGit's handling should be improved. When I last looked at it, it was not a 5 minute fix, but I may have some time over the next week or two.
The message is correct if the object belongs to another package. But for the scenario where it belongs to a nonexistent package we can do two things:

Provide a different message
Pull the package if it does fit into the hierarchy

I'll do 1. as I think this is the minimum we should do.
2 is a nice to have, but was a bit fiddly when I looked at it as the code was already modified to work in the other direction. Will poke around a bit more but I don'1 think it's high priority so if it gets messy we can leave it.

Agree. If an object is orphaned (tadir entry with package that does not exist), then it should issue a warning (instead of the error) and restore the package on pull.

Here's a small test case:
https://github.com/abapGit-tests/PROG, branch "subpackage"
Pull everything to package $PROG, then delete the TDEVC and TDEVCT entries for the packages $PROG and $PROG_SUB (simulating the upgrade issue).
The problem is not the status calculation. It's the selection of local objects (zcl_abapgit_tadir=>select_objects). AG first selected all packages and sub-packages. This is where the missing TDEVC entries "hurt": No sub-packages are found. The root package of the repo is added by default.
The subsequent object selection is based on the found packages and therefore won't find any objects for the sub-packages. In turn, the objects are not serialized and the status calc will treat them as non-existing locally.
Without the package hierarchy (in TDEVC), there's no way for AG to determine which objects belong(ed) to a repo.
PS: The root cause is SAP dropping packages. I firmly believe SAP should fix this (or provide an easy way for customers to restore the local packages + package hierarchy after the upgrade).

Close?

Yeah, thanks


Weapon addition

Hello there, I am in need of help with adding some weapons. Some of the weapons listed on the page are too long to fit on one sign line like there Porter's X2 Ray Gun. Is there any way I could add this weapon?

P.S. is there a way you can add more mobs like skeletons, blaze, creeper, etc.

Hello there, I am in need of help with adding some weapons. Some of the weapons listed on the page are too long to fit on one sign line like there Porter's X2 Ray Gun. Is there any way I could add this weapon?

Unfortunately not. there's not really any way to give the guns that are too long to fit on the screen currently.

P.S. is there a way you can add more mobs like skeletons, blaze, creeper, etc.

Nope Just zombies. Keeping with the theme of realism towards the actually game mode


feat: Added Letter Spacing option

Summary
Added Letter Spacing option
resolves #251
Type of change

[x] New feature (added a non-breaking change which adds functionality)

How Has This Been Tested?

[x] Ran tests with composer test
[x] Added or updated test cases to test new features

Some error in "Format with Prettier"
Run EndBug/add-and-commit@v9
  with:
    message: style: Formatted code with Prettier
    default_author: github_actions
    add: .
    cwd: .
    fetch: --tags --force
    pathspec_error_handling: ignore
    push: true
    github_token: ***
Running in /home/runner/work/readme-typing-svg/readme-typing-svg
Add input parsed as single string, running 1 git add command.
> Using 'github-actions<EMAIL_ADDRESS>as author.
> Using "style: Formatted code with Prettier" as commit message.
Internal logs
  > Staging files...
  > Adding files...
  > No files to remove.
  > Checking for uncommitted changes in the git working tree...
  > Found 5 changed files.
  > Fetching repo...
  {
    raw: '',
    remote: null,
    branches: [],
    tags: [],
    updated: [],
    deleted: []
  }
  > Not pulling from repo.
  > Creating commit...
  {
    author: null,
    branch: 'main',
    commit: '28e0c4[3](https://github.com/DenverCoder1/readme-typing-svg/actions/runs/9760791461/job/26940859740?pr=302#step:7:3)f41a473cd8e214d42c2eda2a4d76b9652',
    root: false,
    summary: { changes: 5, insertions: 10, deletions: 28 }
  }
  > No tag info provided.
  > Pushing commit to repo...
  Error: Error: Pushing to https://github.com/mpa12/readme-typing-svg
  remote: Permission to mpa12/readme-typing-svg.git denied to github-actions[bot].
  fatal: unable to access 'https://github.com/mpa12/readme-typing-svg/': The requested URL returned error: [4](https://github.com/DenverCoder1/readme-typing-svg/actions/runs/9760791461/job/26940859740?pr=302#step:7:4)03

Outputs
  committed: true
  commit_long_sha: 28e0c43f41a473cd8e214d42c2eda2a4d76b96[5](https://github.com/DenverCoder1/readme-typing-svg/actions/runs/9760791461/job/26940859740?pr=302#step:7:5)2
  commit_sha: 28e0c43
  pushed: false
  tagged: false
  tag_pushed: false
Error: Error: Pushing to https://github.com/mpa12/readme-typing-svg
remote: Permission to mpa[12](https://github.com/DenverCoder1/readme-typing-svg/actions/runs/9760791461/job/26940859740?pr=302#step:7:13)/readme-typing-svg.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/mpa12/readme-typing-svg/': The requested URL returned error: 403

Thanks!


Label For ID: Does not work unless multiselect is searchable

When multiselects are given label for="thing" with multiselect id="thing", the label does not open the multiselect field unless the multiselect is flagged as searchable. It looks like the associated input field doesn't exist inside the multiselect component unless it's flagged as searchable.
Repro fiddles:
Searchable (label working)
https://jsfiddle.net/7ma9xuvp/1/
Unsearchable (label not working)
https://jsfiddle.net/7ma9xuvp/2/

Never tried it, but I’m not sure if a label can trigger focus on something different that an input. You can open the multiselect yourself using the by adding ref="multiselect and then doing this.$refs.multiselect.focus().

This isn't really invalid; its an actual problem from an accessibility perspective.
For me, it's not about providing focus, it's about having the multiselect add the ID parameter properly so that the label is properly connected.
With searchable="false" the given id is not passed to the underlying input element. This is an issue for assistive technologies and goes against the use of labels in forms.
Are you saying we should not use labels on multiselects where searchable="false"?

Looking underneath the hood in a bit more detail, it seems that there is no input when searchable="false", so  I guess, technically the current implementation is correct.
From a user perspective though, this is just a select and it would be expected to be accessible.
For the time being I'll just allow the field to be searchable. Not ideal in my circumstances but it best fits from an accessibility point of view.


MINOR: Support java.util.Optional in the auto-generated protocol

The AK protocol often relies on sentinel value (e.g. null or -1) to indicate that a field was not provided. Usually, these sentinels are turned into java.util.Optional that is empty when the field is equal to the sentinel. Until now, we were doing this transformation while mapping the Struct to internal Request or Response classes. With the generated protocol, we would like to get rid of these internal classes and also avoid spending time to construct them.
This PR is an attempt to support java.util.Optional in the auto-generated classes. A field can be marked as optional that indicates to the generator that its type must be wrapped in an Optional.
When an optional is written, its internal value is used or its default if the optional is undefined. When an option is read, the value read is used or it defaults to an empty optional if the default value is read.
I did a deep integration by changing all the places where values are written or read to do the above conversions. I just wrote it as a proof of concept to discuss this further. The code may be simplified.
An alternative to this would be to only provide getters and setters which convert the internal value to an Optional and vice versa. That would limit the scope of the change. The downside would be that every time the getters or the setters are called, it requires to do the conversion.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

PR is outdated. Closing it.