Implementation of the grade-school exercice

Hello everyone,
As first contribution to exercism.io i chose to work on a php version of an existing exercice.
Since it won't be my only contribution in PHP exercices if any of you wants one in particular, let me know.

I'll work on it later today. I have a question i should have asked ealier, i looked at some other exercices in php and it doesn't seem to be the case but do you think messages related to tests should be added in here ? The tests are pretty self explanatory i know but at the same time exercices are meant to help learn programming.

Thanks @Pierre-Vdsp! what sort of questions do you mean? There is a generic exercises repository for all languages here: https://github.com/exercism/x-common which is a good place if it is a generic question about the exercise. If it's PHP specific then ask away in here, or create an issue :)


Resampling fix

Adapts the resampling code to address upstream changes in Xarray.
Closes #57

The build failure here is unrelated to the fix, but rather something else that's broken.
It looks like it's an issue in the animation notebook.  Trying to pin down the issue, but I think it might be some other recent Xarray changes.

Or rather Xarray interactions w/ NumPy 2.0.2 (may just be Numpy 2+)

Looks like it's this https://github.com/pydata/xarray/issues/9043
We're passing DataArrays to np.linspace (buried in the Xarray code) via the vmin and vmax params.

@jukent, I think I may have broken the automatic reviewer assignment or maybe it doesn't work for cookbooks.  Either way, it doesn't look like folks are getting assigned automatically and I don't have permissions to request a review.
This should address the CI failures though.

@jukent ah, I see.  I saw something in the PR template about it, but I'm guessing that propagated from some Project Pythia templating.
Feel free to merge.  I don't have permissions on this.
And if you'd rather not squash-merge, I can clean up the commit history.  Just let me know.


NixOS 24.05 creates a new letsencrypt account and breaks CAA

After updating to 24.05, it appears that the ACME client (with the default infrastructure: security.acme/services.nginx.xxx.enableACME etc.) registers a new account for obtaining letsencrypt certificates. If you had CAA with account binding enabled on your domains, the certificate renewals will now fail.
If you are affected by the problem, here is how you can figure out the new account URI in order to update your CAA entries:

ls -l /var/lib/acme/.lego/accounts/ and take the most recent directory
cat<EMAIL_ADDRESS>
This should probably be added to the release notes.

cc @NixOS/acme

Did you update from 23.11?

Suspect 4494fcaab7abb0f9eb63371c243826afcc0fb9c1, because the two different directories I have now match the SHA256 of "https://acme-v02.api.letsencrypt.org/directory ec256 <email>" and " ec256 <email>". (Note the space at the start, which is the toString null of the old default for the server option.)

Wow @stephank good catch. Yes sounds like that is the issue

Do what's the plan forward? IMHO we should fix this whitespace and backport it to stable, assuming there's more people who didn't yet upgrade to the latest release vs that did.

Apparently this bug was brought up during review: https://github.com/NixOS/nixpkgs/pull/270221#issuecomment-1930561704 :(

Maybe we can keep the current method, but if the correct accounts directory doesn't exist, check if one exists under the old hash and move it?
One thing I'm unclear about: only the account hash should've changed, I believe? So why is it renewing all domains as well? Is there a link between domains and account ID somewhere, I'm not seeing?

What's really rad is neither @NixOS/acme got highlighted on the issue, nor did the release note update happen. This currently is a tire fire for everyone switching to it, either having them run into rate limits or having to update CAA records (after they notice, at all).

This currently is a tire fire for everyone switching to it

I've updated probably 25 VMs all with certs and didn't run into an problems and already forgot that this was a problem 4 months ago.

IMHO we should fix this whitespace and backport it to stable, assuming there's more people who didn't yet upgrade to the latest release vs that did.

We cannot just do that, as that would cause the opposite direction for anyone on unstable for the last 4 months, that already migrated or that recently installed 24.05.
We probably need some state convergence.

Since https://github.com/NixOS/nixpkgs/pull/106857 landed the rate-limit issue is probably less of an issue in practise.   I think we really only should care about breaking people's CAA setup.
In that case I think we can get away with just an entry in the release notes and  state convergence can be seen as a nice to have but not a must have.

the rate-limit issue is probably less of an issue in practise.

At the Flying Circus, there's a high likelihood we're going to be affected by this nonetheless, despite the head-of-line registration blocker setup you mentioned, @arianvp. We have several hundred machines that'll request a new account when rolling out 24.05.

You can create a maximum of 10 Accounts per IP Address per 3 hours. You can create a maximum of 500 Accounts per IP Range within an IPv6 /48 per 3 hours.

https://letsencrypt.org/docs/rate-limits/
When having to fix this downstream, I'd probably adopt a state convergence activation script approach.
Alternatively, @stephank had proposed to re-allow null as the account URL again, which would allow getting back the previous account hash string. If we adopt this here in NixOS upstream, that's a decent solution as well.

I'll work on a patch to re-allow null tonigh. Will post here for review in a bit!


Timeline for raw caffe2 c++ to support FPN

Hi,
I would love to use e2e_faster_rcnn_R-50-FPN_1/2x for inference in caffe2 c++. I know that currently FPN is not yet supported. Do you guys have a timeline for when it would be supported?
Thanks a lot!

Hi @ChengshuLi. We are working on it so stay tuned! More work is still needed, but part of it is at https://github.com/caffe2/caffe2/pull/2254


Reference label config file correctly.

Not sure how to get this moving, so I set it to draft for now.


Push button does not enable bluetooth (RockPi)

[x ] I understand that this is only to report software bugs and not for customer support. Please use nebra.io/helium-support.

Describe the bug
Bluetooth button not working.
As described in the manual, in order to enable the Bluetooth we must press the back button for 10 seconds however nothing happens. Workaround is to turn off and turn on - since bluetooth is enabled for some minutes after boot.
Other people experiencing this issue:
https://www.reddit.com/r/NebraMiner/comments/thrivl/my_experience_with_4_rock_pis_so_far/
To Reproduce

Press button for 10-15 seconds

Expected behavior
Bluetooth enabled and visible in Helium app
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):

Device: OnePlus Nord
OS: Android 11
Helium app v. 4.0.1

Additional context
Model of unit: Nebra HNT Indoor Hotspot Miner - RockPi version 868 MHz (SKU: NBR-0063) - NEBHNT-HHRK4-868

Ping @NebraLtd/developers

@antonioli86 I'm moving this over to hm-config repo. We will investigate.
Can you create a ticket at https://support.nebra.com with a picture of the label on the device? And reply back with the ticket number?

Created yesterday - ticket (#350112).

It might now be directly related but looks like we have a regression in here:
https://github.com/NebraLtd/hm-config/commit/822ed2aaad4a70527c2ed842edb2864bb0b2d926
@marvinmarnold, as per @pritamghanghas's changes on hm-config, we're not using synchronous sleeps and infinite loops for polling anymore. It is not directly impacting Bluetooth advertisement on startup, but most probably interferes with the button press. Could you take a look at it?

@MuratUrsavas those are different threads. Shouldn't interfere.

Hi,
Just to inform - after interaction with Nebra Support in ticket (#350112) - "ROCK Pi Indoor green light is off" - now its working and Bluetooth is enabled after push button.

those are different threads. Shouldn't interfere.

@pritamghanghas You're right, missed that point. Probably I've been mislead by the log output. Couldn't see the advertisement startup in the logs.
@antonioli86 glad your problem has been resolved. We'll keep this case open until we sort out the effects of the commit I've mentioned.

I have the same problem on one of my devices. I could resolved it by rebooting - luckily the miner enables bluetooth on start up for a short amount of time.
But its worse on another miner of mine. There is no bluetooth at all - not even on start up. So i'm not able to connect and get it up running.
Ticket #351429

I have the same problem on one of my devices. I could resolved it by rebooting - luckily the miner enables bluetooth on start up for a short amount of time.
But its worse on another miner of mine. There is no bluetooth at all - not even on start up. So i'm not able to connect and get it up running. Ticket #351429

@ymc-frgu just leave it online on Ethernet and it'll pull in the latest update with the new firmware


option is already decklared

Issue description
can't change "programs.bash.promptInit"
error: The option programs.bash.promptInit' in /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/programs/bash/bash.nix' is already declared in `/etc/nixos/bashrc.nix'.

Would you mind sharing your config and the rev of nixpkgs you use to build your system?

my actual config here - https://github.com/rndd-AK/configs_for_laptop/tree/master/nixos
-bash-4.4$ nix run nixpkgs.nix-info -c nix-info -m

system: "x86_64-linux"
host os: Linux 5.2.16, NixOS, 19.03.173522.021d733ea3f (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.03.173522.021d733ea3f"
channels(rndd): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Your module appears to provide the same options we have in nixpkgs causing this collision

https://github.com/rndd-AK/configs_for_laptop/blob/9d23103c41105d85ae3b836eeb800e08f581fa08/nixos/bashrc.nix

ok, my goal is modifying $PS1 :/

The promptInit option has the types.lines type which means that multiple configurations can assign values and those will be concatenated in the end. If you want to ensure that your config actually overrides PS1, you may want to use mkAfter:
{ lib, ... }:
{
  programs.bash.promptInit = lib.mkAfter ''
    export PS1='...'
  '';
}

It's also possible to completely override an option value using mkForce:
{ lib, ... }:
{
  programs.bash.promptInit = lib.mkForce ''
    # now everything else will be discarded.
    export PS1='...'
  '';
}

Apart from that I'd recommend to take a closer look at the resources from the following Discourse thread to get a more detailed explanation of the module system: https://discourse.nixos.org/t/best-resources-for-learning-about-the-nixos-module-system/1177/4

well, it really works =)
But what if I want different $PS1 for different users?

But what if I want different $PS1 for different users?

The NixOS module system is responsible for system-wide configuration. You could implement this with some hacks like if [ "$(whoami)" = "foo" ]; then export PS1='bar'; fi, but I'd actually recommend  to define a PS1 for each user locally. If you'd like to manage this with Nix as well, you might want to take a closer look at home-manager: https://github.com/rycee/home-manager


musikcube 0.90.0 installed from snap (on non-Ubuntu distros) doesn't start

OS: Linux 5.4.31-1-MANJARO x86_64 19.0.2 Kyria
musikcube: 0.90.0
This is my 1st attempt of installing Musikcube from snap.
Steps:

install musikcube from snap
start musikcube.app

Result:

~ >>> sudo snap install musikcube
[sudo] password for adem:
musikcube 0.90.0 from clangen installed
~ >>> musikcube
zsh: command not found: musikcube
~ >>> musikcube.app                                                                                [127]
terminate called after throwing an instance of 'std::runtime_error'
what():  locale::facet::_S_create_c_locale name not valid
zsh: abort (core dumped)  musikcube.app
~ >>>                                                                                [134]

Interesting, it seems to work fine for me on Ubuntu. This must be some sort of environment-specific issue. Will try to figure out what's going on...

Same error on Ubuntu 20.04 and musikcube 0.92.1 :
❯ musikcube.app
terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
[1]    6237 abort (core dumped)  musikcube.app

From Fedora, does not work musikcube with snap

Looks like the 0.93.1 release fixed the original issue... @chriztheanvill what happens when you try to start the app? Is there any output to the terminal? I tried on my Fedora 33 VM and it seemed to function fine.

After installing with sudo snap install musikcube, if I try to run musikcube, does not run, with whereis, does not find it.
I've tried with snap refresh, there is no update.

@chriztheanvill what about musikcube.app? Also, after I install snapd on Fedora I had to reboot before the snaps worked properly -- no idea if that's your issue, just an observation.

No. After install snap, I've tried to run snap install musikcube, and I get an error, wait some seconds, then again run snap and works.
I do not now if my problem was running 'sudo snap install musikcube' instead of using without sudo. Because, right now I run 'snap install musikcube', then musikcube.app and works.
Note: I did not reboot my machine since some months.

Snaps are causing more problems they are solving, unfortunately, due to the sandbox rules. It's going to be removed from future releases. https://github.com/clangen/musikcube/commit/2ad8c17461188f74bd219e40eef96e970e14bc38

Yep, besides extra-delayed cold starts, I often find myself running snaps in classic mode for compatibility reasons :/


Add to short course student team

Please add me to the Short Course Students GitHub team.


fatal error: THC/THC.h: No such file or directory

Hi I would like to try out your repo but when I do installation step 5) python setup.py build_ext develop. It gives
In file included from /code/SoftGroup/lib/softgroup_ops/src/softgroup_ops.h:5,
from /code/SoftGroup/lib/softgroup_ops/src/softgroup_api.cpp:4:
/code/SoftGroup/lib/softgroup_ops/src/hierarchical_aggregation/hierarchical_aggregation.h:9:10: fatal error: THC/THC.h: No such file or directory
I found THC.h file is only in cuTorch code which is very old. Am I supposed to compile Torch7 and cuTorch?
Another note is that I see you are using spconv 1.x,  and now sparseconv offers 2.x for faster speed.  spconv 2.x can be installed with pip under cuda 11.4 version, which is more modern.  Are you considering updating to spconv 2.x? For your interest, there is a summary on what you need to do to update from 1.x to 2.x.

Thank you for your information. I suggest to install the repo with recommended libraries (pytorch 1.1 and spconv 1.0). We will check whether the results can be reproduced in spconv 2.0.

Please check the spconv2.x support on #5.


unittest: test func ping

Current coverage is 37.00% (diff: 100%)

No coverage report found for master at 5a130fa.

Powered by Codecov. Last update 5a130fa...a60204c


Overview of functionalities

Core Functionalities:
User Management:

Admin and customer registration, login, authentication, and authorization.
User profile management.

Vehicle Management:

Vehicle listing (make, model, year, type, availability, price, etc.).
Vehicle image management.
Vehicle booking and cancellation.

Booking Management:

Booking creation, modification, and cancellation.
Payment integration (optional).
Rental history.

Payment Integration:

Integration with a payment gateway (can try)

Authentication flow via JWT Token


support additional languages

I think the focus should be on:

french
spanish
russian

as soon as any of these are supported by Alexa, yes :)

could i help u for an italian version?


Set a placeholder image for Sponsor

Is it a ?

[ ] Bug Report

[x] Feature Request

[ ] Chore

Feature Request
Feature Description
Currently, no placeholder image is set to be displayed if the Logo URL is kept empty while creating a Sponsor, leaving the UI mysterious and incomplete. We can use the existing cirlce_placeholder.xml drawable as the placeholder.
Before:

After:

Previous
Would you like to work on the issue?
Yes.

@iamareebjamal Please share your view for the same.

Go ahead, but use a different placeholder. The one we are using for events and such

@iamareebjamal Alright. Will send a PR right away with the placeholder used for events.


Get/use bluetooth device from OS

Hi,
There is a way to get the deviceInfo from already connected bluetooth device when launching EscPos and then EscPos.connect easily without listeners on device connection?
Alex.

@leesiongchan ^

Using another lib?

Or simply using the bluetoothDeviceFound listener, but it doesn't work, only the bluetoothStateChanged works on connection.

Another question: (I'm trying to debug) how to print react-native-esc-pos logs to JS server which is running an application using this library?

There is a way to get the deviceInfo from already connected bluetooth device when launching EscPos and then EscPos.connect easily without listeners on device connection?
Probably we could store the connectedDevices in the lib. I will need to refer to one of the famous lib (https://polidea.github.io/react-native-ble-plx/#blemanagerdevices).

Another question: (I'm trying to debug) how to print react-native-esc-pos logs to JS server which is running an application using this library? Probably just a loglevel or a mode to set?
Agree with your suggestion, a debug: boolean option could probably be beneficial to the developer.

I am in the midst of rewriting the codebase, but I have very little time on this project as of now, if that is something bothering you probably will need your help on contributing to the project 💯


Disabling sleep mode at a specific time does not work

I have a specific time set and enabled for sleep mode to automatically disable but it does not work. This is a very useful feature to be woken up by gradual increase of light rather than a loud alarm, loud alarm using my phone would be a backup.

ok not sure what happened but suddenly it worked again, I woke up before the set time by a few minutes two days in a row and waited to see if it would disable but it didn't. I reset the time (same time) and saved and it worked today so i guess its ok now xD. Thanks and sorry to bother you with this :D


How do I test it on a graphical interface

I can't make it work. Can anyone please explain how to list files from ftp on a debug node? It should be very simple but I can't make it work.

@guypaskar It works with the following flow.
[{"id":"df1ae147.109e4","type":"inject","z":"e618397e.9b1cd8","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":137.5,"y":103,"wires":[["19a34ff5.34859"]]},{"id":"19a34ff5.34859","type":"ftp in","z":"e618397e.9b1cd8","ftp":"c3a22e5f.e9be1","operation":"list","name":"","x":316,"y":104,"wires":[["a0cb42cc.9f7e"]]},{"id":"a0cb42cc.9f7e","type":"debug","z":"e618397e.9b1cd8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":496,"y":102,"wires":[]},{"id":"c3a22e5f.e9be1","type":"ftp","z":"","host":"localhost","port":"21","secureOptions":"","user":"user","connTimeout":"","pasvTimeout":"","keepalive":""}]


Add Azure.Identity to CLU README

Because the Conversations README shows an example of creating a new DefaultAzureCredential, be sure to make sure the using Azure.Identity is in there along with an Authoring sub-namespace like I did for QA.

Resolved in #31510


Post-checkout failure

This just happened, I'm not sure what's going on:
± [matijs@bean master+] git co -b rails-5-2
Switched to a new branch 'rails-5-2'
Directory not empty @ dir_s_rmdir - /home/matijs/Projects/playdate/.git/hooks/old-hooks
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:250:in `block in rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `each'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/2.5.0/fileutils.rb:249:in `rmdir'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:142:in `preserve_old_hooks'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:58:in `update'
/home/matijs/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/overcommit-0.43.0/lib/overcommit/installer.rb:20:in `run'
.git/hooks/post-checkout:67:in `<main>'
Report this bug at https://github.com/brigade/overcommit/issues

I think overcommit made old-hooks in the first place, so it shouldn't be surprised to find stuff there.
Update: This happens on regular branch checkout as well.

Hey @mvz, this issue should have been fixed by 7c85c6651b7249cecf92f2cfa848bbd16a488f03 (reported in #554).
Would really appreciate if you temporarily modified lib/overcommit/installer.rb:142 to add Dir.entries(old_hooks_path).inspect before that line on your system. Thanks!

Hi @sds, the result of that puts is:
[".", "..", "commit-msg", "pre-rebase", "pre-commit", "post-commit"]

Apologies @mvz. I thought we had released the fix already.
Please update to Overcommit 0.44.0 to avoid this issue. Thanks!


Health Checks topic+sample updates for 3.0

Fixes #13340
Internal Review Topic

Sample update to 3.0. Confirmed working.
Lot's 'o updates here. Plz review me carefully :eyes:. We're not in a major rush, so review can wait if too busy right now to look. 🏃🏃🏃🏃😅
Whole topic versioning. You only need to review the top-half of the markdown file (the >=3.0 section).
Goes with endpoint routing.
RequireHost, RequireAuthorization, and RequireCors added.
Let me know if we aren't going to stick with MapWhen to limit the HTTP verb: Is there an endpoint routing way to do it? (See the Restrict health checks with MapWhen section.)

@rynowak Ok ... ready. This isn't holding anything up, so there's no rush from the docs side.


Re-do directions to be friendly for cycling and driving

Valhalla + the web TTS api should make this tractable, but it should probably be split to its own issue eventually.

We might need to swap the map style to be friendlier for this. I'm in favor of removing all map label text for driving, personally. Every time someone nearly kills me on my motorcycle I get more and more cautious about how we implement this, and I have close calls nearly every day. I don't want blood on my hands because someone did a distracted driving. I think we should also only enable it for platforms that allow you to acquire a wake lock.
In the future we could use quasar's mobile export functionality to publish apps that use native tools for wake locks, then we could also push it out on iOS.


Enable importing field data from JSON file on Page Create

These changes enables importing field data upon page creation, using a syntax such as:
wireshell page:create \
    --template page \
    --parent home \
    --title "Hello World" \
    --fielddatafile fielddata.json

... where fielddata.json can contain, for example:
{
    "Body": "Hello World!"
}

It has worked very well for my use case so far, though I guess there's for sure things that can be improved.

Sorry again, realize I should PR against develop, not master.


Build wheels in parallel, add aarch64

This PR should prepare us for a patch release 0.42.1. I've bumped the version number and changelog accordingly.
Changes:

Modifies our wheel job to run in parallel, which is must faster and makes the jobs more understandable. Uses cibuildwheel --print-build-identifiers to dynamically generate the job matrix, which pick up the supported builds from pyproject.toml.
Changes the cibuildwheel dependencies from test to test-core, to only run the limited test set on the built wheels.
Adds aarch64 on linux, closes #3061

Example wheel build workflow run (passes).
Example job matrix:

@thatlittleboy if you're happy, I can go ahead and publish the patch release once this PR is merged.

Thank you for the pull request and all the work on Shap (and toward the patch release). For me, it looks ok. If I compare wheels offered with Scipy/Numpy only musllinux wheels are missing (which are mostly used in containers).
I am trying to make them available at
https://github.com/slundberg/shap/pull/3087, but it is not as crucial as other weels the new release will offer.
All other wheels are unnecessary since users must build Numpy and Scipy anyway. I also noticed that cp37 and cp38 wheels could be dropped also since Numpy and Scipy dropped them already (as I understood it was planned to be done in the future).

That's helpful, thanks. Enjoy your vacation - hope you resist the urge to check GitHub!

I would say that the release is made without musllinux wheels, and I can work on them when I am back. Tests do not go through because some packages (scikit-learn) do not offer musllinux wheels and would need to be properly compiled.

That's helpful, thanks. Enjoy your vacation - hope you resist the urge to check GitHub!

It was no problem, happy to help. :)

Created an issue to track the musllinux proposal for future reference: #3089 .


Add Jenkinsfile for Rummager

This adds the Jenkinsfile to Rummager to allow builds on the Jenkins pipeline.
This has now been successfully tested, although build times are slower than the current CI environment at ~13 minutes rather than ~5 minutes.
The release tag pushing is still disabled in the PR, but if we decide to migrate then the steps should be:

Push new commit enabling tag pushes
Update build number on new CI to reflect the build number on the current CI environment
Update the webhook
Merge the PR

Do we know why build times are slower? Would be great to speed that up if we can. Waiting 13m to get to a deploy can be quite annoying if you're just making minor improvements on a PR 🙁

Looks good.  One query.
In the original job on the old CI, two post build steps are specified.  Were these omitted deliberately?

@MatMoore build times are slow for an unknown reason, but I suspect underlying infrastructure. I will be looking to migrate the CI machines over to more performant hardware next week. We obviously don't want to switch over while build times are almost three times of the current CI.

@djsd123 great point, and I overlooked that because I just looked at the "rummager_branches" build job, which means there is some extra stuff still required on this. Thanks!

@MatMoore we've upgraded the CPUs and the build time took 8 mins 52 seconds. I hope that's more acceptable, although I note it still feels slower than the current CI.

@suzannehamilton I've pushed some changes (different rubylinter options and removed the linking of images as it looks superfluous). Can you let me know if this looks OK?

I've added build parameters so this can be used to test changes to the content schema, and removed the commented-out release tagging, because it's OK for Jenkins 2 to do the release tagging once this has been merged to master.


new installer version test from element

comment on the issue from the new issue linked room

another comment from the issue linked room


Let's add support to JSON files

Some configuration files have been written in JSON format. So let's add support to them. We can use something like: "_comment": "@todo #123:30min Subject...". WDYT?

@yegor256/z please, pay attention to this issue

@fabriciofx/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

I don't think you should use a key in the json file to add a @todo. Depending of where/how you're using this file it may even trigger some error for having unsupported key. Maybe just add the puzzle where you're supposed to use the parsed config?

@lastk you're right. I'll close this issue because it doesn't make any sense. Thanks!

Job gh:yegor256/pdd#118 is not assigned, can't get performer

This job is not in scope


[now-next] Remove node 8 test

This removes the node 8 firebase test since node 8 is being deprecated and we have the same test running against node 10 also

I renamed the fixture names to not have the gap and looks like there were some files in those directories that hadn't been formatted yet


Question: Cloning whole site approaches

Hi,
Firstly, a great, polished tool!
Has anyone got AB running in combination with something else to successfully clone an entire site? Having to collect the links of a site manually is a time-consuming process for a few projects I could do with cloning.
I'm curious as to what other tools people are combining this with to create archives of entire sites.
Thanks!

Ignore - it appears to do this already, the process had error'd! :)

It actually doesn't clone whole sites, so I'm curious as to how you managed to do that with AB.
It is on the roadmap though: https://github.com/pirate/ArchiveBox/issues/191


Obit r632

This primarily fixes the missing facet issue reported in https://skaafrica.atlassian.net/browse/SPR1-566 but also contains updates to deal with other fixes in R632. I've tried to explain whats going on in the commit messages - but please ask if anything too Obitty doesn't make sense :)

Ok, if you're happy with the error handling then I'll trust your experience with Obit.


Problem with retrieval of Gone into Rapture

http://www.goneintorapture.com/ seems to be down . Corresponding tumblr is still working fine.

It seems like the website is up but format has changed.

New format actually corresponds to a Tumblr


CanCanCan Authorization of activate and deactivate is broken

The code authorize! :be, :admin used in ApplicationController#activate and #deactivate doesn't do anything as far as we can tell. This should be investigated and fixed.

ok, if thats all that is needed this is ready for review


ESBuild doesn't work if using core services

PHP Version
No response
Shopware Version
No response
Actual behaviour
If using services or classes from the Shopware core the compilation doesn't work.
According to the documentation e.g. import Plugin from 'src/plugin-system/plugin.class'; already causes this error.
shopware-cli extension build custom/static-plugins/shopware-platform-delivery-time/

up to date, audited 2 packages in 5s

found 0 vulnerabilities
npm notice
npm notice New major version of npm available! 8.19.2 -> 9.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
INFO[0004] Downloading dart-sass
INFO[0005] Using dart-sass binary /root/.cache/dart-sass-embedded/dart-sass-embedded

  extension.js   126.4kb
  extension.css   21.0kb

⚡ Done in 602ms
INFO[0005] Using dart-sass binary /root/.cache/dart-sass-embedded/dart-sass-embedded
✘ [ERROR] Could not resolve "src/plugin-system/plugin.class"

    custom/static-plugins/shopware-platform-delivery-time/src/Resources/app/storefront/src/deliveryDate/deliveryDate.plugin.js:5:19:
      5 │ import Plugin from 'src/plugin-system/plugin.class';
        ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "src/plugin-system/plugin.class" as external to exclude it from the bundle,
  which will remove this error.

✘ [ERROR] Could not resolve "src/service/http-client.service"

    custom/static-plugins/shopware-platform-delivery-time/src/Resources/app/storefront/src/deliveryDate/deliveryDateTime.js:1:23:
      1 │ import HttpClient from 'src/service/http-client.service';
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "src/service/http-client.service" as external to exclude it from the bundle,
  which will remove this error.

2 errors

Expected behaviour
It should compile
Steps to Reproduce?
build:
  zip:
    composer:
      enabled: true
    assets:
      enabled: false
      enable_es_build_for_admin: true
      enable_es_build_for_storefront: true
    pack:
      excludes:
        paths:
          - .cache
          - .editorconfig
          - .gitignore
          - .idea

docker run --rm -ti -v $PWD:/tmp/build -w /tmp/build --entrypoint= ghcr.io/friendsofshopware/shopware-cli:0.1.44 bash
shopware-cli extension build custom/static-plugins/shopware-platform-delivery-time/

It should be explained in detail here: https://shyim.me/blog/how-to-build-shopware-extension-assets-faster/#extracting-shopware-storefront-components-for-isolated-build
So in order to use ESBuild the plugin itself needs to be adjusted and may not use any core services.


Add miscelaneous haddock doc improvements to the normal API

In particular, discuss snapshots and duplicates: durability and persistent data structures.

To model these additional requirements, the model should have access to some "global state". For example, creating new sessions in the same folder

I don't think it's worth modelling that. All model sessions can live independently of each other.
I.e. the Session type is not shared by the model.


TypeError: Cannot handle the data type in PIL Image

First of all, thank you for the code! I really appreciate it.
While using your code, I keep on encountering the problem as can be seen in the screenshot below. If I get rid of the lines of code relevant to self.add_image in the writer.py, the code runs fine. However, I want to use the code to visualize the target and predicted mel spectrograms. I have been looking through the code and editing some parts, but it does not seem to solve the problem. Any advice would be much appreciated. Thanks in advance.

I think I solved the above error.
So apparently in "melgan/utils/plotting.py", I commented out line 13 (data = np.transpose(data, (2, 0, 1)). This gave a different a different error (TypeError: add_image() got an unexpected keyword argument 'dataformats') in writer.py in the lines with the HWC. I got rid of "dataformats = HWC" and now I can train using the pretrained melgan model with my own dataset (not English).
I will be looking into why the process I detailed works, but since I am just an amateur, I would be most grateful if someone more experienced can give an explanation.


Feature Request: Wrap *ProjectionImageFilter with 4D to allow usage over multiple images

There are a number of *ProjectionImageFilter in ITK which could be used to produce various types of averages/projections across a number of images. In order for this to work however, they need to have a 4D implementation, so that the 3D images can be stacked and collapsed.
I'd like to request this wrapping be added.

Ref: #1426


v1.2.0-beta.1

Show all compatible wallets in the modal (#140)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
31

💛  - Coveralls


Dependabot alert #165 and #166: Upgrade async package

Solves https://github.com/kiegroup/kie-tools/security/dependabot/165 and https://github.com/kiegroup/kie-tools/security/dependabot/166

@thiagoelg Hi there I do not see any package.json changes, this won't solve it in a long run.

@domhanak We don't need to change the package.json, as versions are locked by yarn.lock. The changes made here were bumping patch releases, which is aligned with what is defined in our package.json. Remember that our dependencies do not "automatically update" even though we're using ^-prefixed versions. That's the whole purpose of yarn.lock.


Fix the last (almost 😅) part of broken links

Thank you so much!! How have u been fixing these? Manually?
Sent with GitHawk

Thank you so much!! How have u been fixing these? Manually?
Sent with GitHawk

Yes, manually. I've not noticed any relations between the old links and the new ones 🙁. So, I just went by iTunes links and got screenshots from there, or from the repos. Luckily, it was not necessary to make new screenshots)


JAVA-2961 ObjectId generation with number of bytes > 12 should throw expection

As per documentation of getting ObjectId from bytes, IllegalArgumentException should be thrown if bytes is null or bytes.length!= 12 . But presently for bytes.length > 12, it returns ObjectId using first 12 bytes.
https://jira.mongodb.org/browse/JAVA-2961

@umang-jalan Our apologies for losing track of this PR and doing our own implementation of this issue.  See https://github.com/mongodb/mongo-java-driver/commit/468bcb95a3d1904c2033a52453476b56b94d9bff for what got committed to the repository.


Added batch commands for including RenderManager and Android libs in …

Tested that this works with a test CI build. Merging into master, then updating the main Unity CI build...


Show full version on package details page

Only display the full version in the title.
Use NormalizedVersion anywhere else.

Why no full version in the version list at the bottom of the page?
Also, is this full version visible on web UI package upload or package edit?

Why no full version in the version list at the bottom of the page?

Full Version may be quite large (I've seen people using metadata parts of 50+ characters), so wouldn't want to clutter the table. As the URL for those hyperlink uses NormalizedVersion anyway, I figured it made sense to keep those as is.
Same for the version in the left side bar, don't want it to flow through in other text.

Also, is this full version visible on web UI package upload or package edit?

That is already the case. Try uploading one ;)

Sounds good. Thanks.


spark: Limit the Seq size in RddPathUtils::extract() to avoid OutOfMemoryError for large jobs

Problem
Closes: #3146
Solution
As suggested in #3146#issuecomment-2404985178, first we validate just the first element, and later we take a slice of the first few (here, 1000) elements and process it.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

One-line summary: Limit the data Seq size in RddPathUtils::extract() to avoid OutOfMemoryError for large SparkPi jobs
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2024 contributors to the OpenLineage project

To make sure my understanding is correct: sometimes ParalllelCollectionRDD contains a sequence of files to be read which is valuable lineage metadata, but sometimes it has the content of RDD and tries to extract lineage for each element of it.
Yes. The former is the intended use case, and the latter is what's causing this error.

And there is no way to distinguish one case from another. Right?
Not sure about this one. If there is a way to differentiate these two cases, that would be the ideal scenario. We can just add that check and move on. But I am not aware if there is a way to do that.

@codelixir  Looks like Spark 3.3.4 tests are failing. I rerun them. In case they fail again, you can try running them locally. I am happy to merge PR once CI tests are passing.

Thanks!

Great work @codelixir Thank you for fixing this 🥇


label collision movement

hide less prominent (current strategy, probably only works well on desktop)
run force/voronoi and separate, then maybe hide if too far
some hybrid? since on mobile it might be better to just hide and show legend

try flipping vertically to avoid collision. worry about mobile later.


feat: added segment based containerizer

Signed-off-by: Pablo Loyola<EMAIL_ADDRESS>

Are the constant file changes required?

Are the constant file changes required?


merge all unit tests and cleanup assets

Make them available at image.test()  (like torch7 ones)
Move all images to the assets folder

test_rotate.lua and test_warp.lua are not merged since they do not contain asserts. test_rotate.lua remains in the travis build as before.
Update: handled properly the fact that the tests require graphicsmagick but not the image package.

nice! much needed.


Add MobileNetV4 conv series

Description
Please include a summary of this pull request in English. If it closes an issue, please mention it here.
Part of #508
We recommend to link at least one existing issue for PR. Before your create a PR, please check if there is an issue for this change.
Change(s)

Add MobileNetV4 conv series.
Hybrid series models are not implemented yet.

Code Formatting
If you PR to either master or dev branch, you should follow the code linting process. Please check your code with lint_check.sh in ./scripts directory.
For more information, please read the contribution guide in CONTRIBUTING.md.
Changelog
If your PR is granted to dev branch, codeowner will add a brief summary of the change to the Upcoming Release section of the CHANGELOG.md file including a link to the PR (formatted in markdown) and a link to your github profile.
For example,
- Added a new feature by `@myusername` in [PR 2023](https://github.com/Nota-NetsPresso/netspresso-trainer/pull/2023)

Please enable Allow edits and access to secrets by maintainers so that our maintainers can update the CHANGELOG.md.

I added FCConv class temporarily, but this will be removed later through refactoring.


Calling cmd.exe from bash results in special escaping/transformation of input arguments

I'm attempting to run this Win32 command through bash:
cmd.exe /c for %A in ("C:\Documents and Settings") do @echo %~sA
The correctly escaped command for bash is:
cmd.exe /c for %A in '("C:\Documents and Settings")' do @echo %~sA
However, this results in this error:

"("C:\Documents was unexpected at this time.

Using this command from bash:
cmd.exe /c echo for %A in '("C:\Documents and Settings")' do @echo %~sA
I can see that the command was transformed into:

for %A in "("C:\Documents and Settings")" do @echo %~sA

The "(\" should be just (" and the \")" should be )"
However, this appears to be special escaping for cmd.exe.  If I run another executable, in this case a C++ executable that just prints out the arguments, I get the correct arguments:
test.exe /c for %A in '("C:\Documents and Settings")' do @echo %~sA

C:\Users\Andrew\source\repos\test\x64\Release\test.exe
/c
for
%A
in
("C:\Documents and Settings")
do
@echo
%~sA

The source for test.exe is below:
#include <iostream>
#include <string>

int main(int argc, char* argv[])
{
	for (int n(0); n < argc; ++n)
	{
		::std::cout << argv[n] << ::std::endl;
	}
	return 0;
}

Details of my environment:
uname -a:

Linux DESKTOP 4.4.0-17763-Microsoft #194-Microsoft Mon Dec 03 17:58:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux

ver:

Microsoft Windows [Version 10.0.17763.195]

I confirmed that this still occurs in a recent insider build:
uname -a:
Linux DESKTOP-HLO5ULF 4.4.0-18917-Microsoft #1000-Microsoft Fri Jun 07 19:42:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
ver:
Microsoft Windows [Version 10.0.18917.1000]
Also tested in WSL2 with same results.
uname -a for WSL2:
Linux DESKTOP-HLO5ULF 4.19.43-microsoft-standard #1 SMP Mon May 20 19:35:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


Custom Input Container

Summary
I would like to use my own, custom input controls inside of the existing clarity forms UX.

What is the change?

Provide an API, controls, containers, or other method by which we can use clarity's normal form layout, with an input type that clarity itself does not support.

Why should it go in Clarity?

Clarity is opinionated about how helper messages, labels, and error messages are shown, but it cannot cover all possible input type cases.

Does this change impact existing behaviors? If so how?

It could impact the internal Forms API in a way that makes it exposable.

If this change introduces a new behavior, is this behavior accessible?

Depends on the external form control.
Use case
<clr-custom-input-container>
    <label for="customControl">My Label</label>
    <multi-range [min]="0" [max]="100" [step]=".1">
        <multi-range-slider formControlName="lowValue" maxValue="20"></multi-range-slider>
        <multi-range-slider formControlName="highValue" minValue="50"></multi-range-slider>
    </multi-range>
    <clr-control-helper>Please choose a low and a high value on the slider above.</clr-control-helper>
    <clr-control-error *clrIfError="'maxValue'">Some error message</clr-control-helper>
    <clr-control-error *clrIfError="'minValue'">Some other error message</clr-control-helper>
</clr-custom-input-container>

Examples
The Price slider from AirBnB.
Workarounds
Clone the entire forms codebase and provide a custom wrapper implementation for each custom form control.

I think this is a duplicate of #2886, so I'm going to close it in favor of #2886. Please follow it for more details. It is something on our radar in the near future.


[BUILD] Auto-detect OpenVDB ABI when building Houdini plugin

Environment
Operating System: Linux CentOS 7.7.1908
Version / Commit SHA: 8.1.0
CMake Version: 3.18
Compiler: gcc 9.4.0
Describe the problem
When building openvdb_houdini for houdini-19.0.376 cmake errors out with:
CMake Error at CMakeLists.txt:655 (message):
  Located OpenVDB installation is not ABI compatible with Houdini Version
  19.0.376.  Requires ABI 7, found ABI 8.

-- Configuring incomplete, errors occurred!

houdini-19.0.376 does ship with openvdb-8.1.0 with ABI 8 according to the version file:
<houdini_root>/toolkit/include/openvdb/version.h
// Auto generated build configurations from CMake

///@{
/// @brief Library major, minor and patch version numbers
/// @hideinitializer
#define OPENVDB_LIBRARY_MAJOR_VERSION_NUMBER 8
/// @hideinitializer
#define OPENVDB_LIBRARY_MINOR_VERSION_NUMBER 1
/// @hideinitializer
#define OPENVDB_LIBRARY_PATCH_VERSION_NUMBER 0
///@}

/// @note  This ifndef exists for compatibility with older versions of OpenVDB.
///   This value should never be different from the value configured when
///   OpenVDB was built, but this previously needed to be defined by downstream
///   software. Redefining it here would cause build failures, so this allows
///   users to transition and remove the define in their build systems.
#ifndef OPENVDB_ABI_VERSION_NUMBER
/// @brief The ABI version that OpenVDB was built with
/// @hideinitializer
#define OPENVDB_ABI_VERSION_NUMBER 8
#endif

/// @brief Library version number string of the form "<major>.<minor>.<patch>"
/// @details This is a macro rather than a static constant because we typically
/// want the compile-time version number, not the runtime version number
/// (although the two are usually the same).
/// @hideinitializer
#define OPENVDB_LIBRARY_VERSION_STRING "8.1.0"

/// @brief Library version number string of the form "<major>.<minor>.<patch>abi<abi>"
/// @details This is a macro rather than a static constant because we typically
/// want the compile-time version number, not the runtime version number
/// (although the two are usually the same).
/// @hideinitializer
#define OPENVDB_LIBRARY_ABI_VERSION_STRING "8.1.0abi8"

The error looks to be in the logic of how openvdb detects the abi.
<openvdb_src>/cmake/OpenVDBHoudiniSetup.cmake:
# ------------------------------------------------------------------------
#  Configure OpenVDB ABI
# ------------------------------------------------------------------------

# Explicitly configure the OpenVDB ABI version depending on the Houdini
# version.

if(Houdini_VERSION VERSION_LESS 17)
  set(OPENVDB_HOUDINI_ABI 4)
elseif(Houdini_VERSION VERSION_LESS 18)
  set(OPENVDB_HOUDINI_ABI 5)
elseif(Houdini_VERSION VERSION_LESS 18.5)
  set(OPENVDB_HOUDINI_ABI 6)
else()
  set(OPENVDB_HOUDINI_ABI 7)
endif()

A simple fix would be to just add:
diff -urB a/cmake/OpenVDBHoudiniSetup.cmake b/cmake/OpenVDBHoudiniSetup.cmake
--- a/cmake/OpenVDBHoudiniSetup.cmake	2021-06-11 14:38:41.000000000 -0700
+++ b/cmake/OpenVDBHoudiniSetup.cmake	2021-09-16 10:47:08.902414953 -0700
@@ -335,8 +335,10 @@
   set(OPENVDB_HOUDINI_ABI 5)
 elseif(Houdini_VERSION VERSION_LESS 18.5)
   set(OPENVDB_HOUDINI_ABI 6)
-else()
+elseif(Houdini_VERSION VERSION_LESS 19.0)
   set(OPENVDB_HOUDINI_ABI 7)
+else()
+  set(OPENVDB_HOUDINI_ABI 8)
 endif()

 # ------------------------------------------------------------------------

But maybe it should get fancy and extract the ABI from the openvdb/version.h in houdini?
To Reproduce
Steps to reproduce the behavior:

Checkout the openvdb repo, I used the 8.1.0 tag but everything up to commit: ab6137b216fe4fda886214f9949170e8dce9d12a should give the same result.
Run CMake
Here's our slightly modified build recipe (which lives in a yaml file)

---
recipes:
  build:
      # Build
      - args=(
          -DCMAKE_INSTALL_PREFIX=$distDir
          -DCMAKE_BUILD_TYPE=Release
          -Wno-dev

          -DOPENVDB_BUILD_CORE=ON
          -DOPENVDB_BUILD_BINARIES=OFF
          -DOPENVDB_BUILD_MAYA_PLUGIN=OFF
          -DOPENVDB_BUILD_PYTHON_MODULE=OFF
          -DOPENVDB_BUILD_HOUDINI_PLUGIN=ON
          -DOPENVDB_BUILD_UNITTESTS=OFF
          -DOPENVDB_ENABLE_RPATH=OFF

          -DUSE_DEFAULT_HOUDINI_INSTALL=OFF

          -DCMAKE_INSTALL_PREFIX=$distDir
          -DCMAKE_CXX_STANDARD=14

          -DBoost_NO_BOOST_CMAKE=ON
          -DZLIB_ROOT="$ZLIB_PACKAGE_ROOT"
          -DTBB_ROOT="$TBB_PACKAGE_ROOT"
          -DHOUDINI_ROOT="$HOUDINI_PACKAGE_ROOT"
        );
        mkdir -p $tempDir/build &&
        cd $tempDir/build &&
          cmake "${args[@]}" ../openvdb-$vendorVersion &&
          cmake --build . -j$(nproc) &&
          cmake --install .

Build with gcc-9.4.0, boost-1.73.0, houdini-19.0.376, tbb-2020.2, zlib-1.2.11
See error in description

Thanks for reporting, I submitted a slightly modified PR to fix this - #1176. I agree your suggestion of pulling the ABI from the version.h shipped with Houdini would be even better - if you wished to submit a PR to do that, I'd be happy to cancel mine and accept yours instead. :)

Sure, I can give it a go. But don't cancel yours just because of that. Better to have that merged, than wait on a potential PR from me :slightly_smiling_face:

@plattfot - agreed! :) I merged that PR to fix the ABI for later versions of Houdini and renamed this issue for auto-detection instead.

@danrbailey - thanks! I got an implementation of this ready. I'm just waiting on work to fix the CLA then I'll create PR for this.

Getting the CLA sorted out, took way longer than I anticipated. It's finally done so here is the the PR: #1243

Merged! Thanks a lot @plattfot


Links with examples on codesandbox are broken

Links in README.md are broken:

Ooop, old branch. Will fix it shortly.


luv_handle_gc segfault (from neovim)

Describe the bug
When running neovim I regularly (somewhere between once every 30 minutes and 3 times in a minute or two) get a segfault which kills neovim.
Backtrace shows something with libluv

        Signal: 11 (SEGV)
     Timestamp: Wed 2024-04-24 22:38:51 AEST (29s ago)
  Command Line: /nix/store/xcldy06fxypbpbnlnrwmqr8rpyr2fpkp-neovim-0.9.4/bin/nvim --embed -u /nix/store/vh3w2vxh9mi7rryii8rrxn256nzhr047-init.vim --cmd $'lua vim.g.loaded_node_provider=0;vim.g.loaded_perl_provider=0;vim.g.loaded_python_provider=0;vim.g.python3_host_prog=\'/nix/store/xcldy06fxypbpbnlnrwmqr8rpyr2fpkp-neovim-0.9.4/bin/nvim-python3\';vim.g.loaded_ruby_provider=0' --cmd $'set packpath^=/nix/store/jx41n9lxf9l3msx72ri16jwmk245bnva-vim-pack-dir' --cmd $'set rtp^=/nix/store/jx41n9lxf9l3msx72ri16jwmk245bnva-vim-pack-dir'
    Executable: /nix/store/ikvvv0hfxhgmzxnp3kww6yzql7y3prdn-neovim-unwrapped-0.9.4/bin/nvim
       Message: Process 205658 (nvim) of user dumped core.

                Module libparinfer_rust.so without build-id.
                Module clojure.so without build-id.
                Module libstdc++.so.6 without build-id.
                Module libgcc_s.so.1 without build-id.
                Module libluajit-5.1.so.2 without build-id.
                Module libunibilium.so.4 without build-id.
                Module libtree-sitter.so.0 without build-id.
                Module libmsgpack-c.so.2 without build-id.
                Module libvterm.so.0 without build-id.
                Module libtermkey.so.1 without build-id.
                Module libluv.so.1 without build-id.
                Module libclang_rt.scudo-x86_64.so without build-id.
                Stack trace of thread 205658:
                #0  0x00007fca16fe581e uw_frame_state_for (libgcc_s.so.1 + 0x1681e)
                #1  0x00007fca16fe757b _Unwind_Backtrace (libgcc_s.so.1 + 0x1857b)
                #2  0x00007fca16851c43 __backtrace (libc.so.6 + 0x11ac43)
                #3  0x00007fca16a20b79 _ZN12_GLOBAL__N_19BacktraceEPmm (libclang_rt.scudo-x86_64.so + 0x20b79)
                #4  0x00007fca16a1efa5 _ZN8gwp_asan18AllocationMetadata12CallSiteInfo15RecordBacktraceEPFmPmmE (libclang_rt.scudo-x86_64.so + 0x1efa5)
                #5  0x00007fca16a1fe34 _ZN8gwp_asan20GuardedPoolAllocator10deallocateEPv (libclang_rt.scudo-x86_64.so + 0x1fe34)
                #6  0x00007fca1714286a luv_handle_gc (libluv.so.1 + 0xb86a)
                #7  0x00007fca17042a36 n/a (libluajit-5.1.so.2 + 0xba36)
                #8  0x00007fca17089de7 n/a (libluajit-5.1.so.2 + 0x52de7)
                #9  0x00007fca1708a0d8 n/a (libluajit-5.1.so.2 + 0x530d8)
                #10 0x00007fca1708a6c5 n/a (libluajit-5.1.so.2 + 0x536c5)
                #11 0x00007fca1709fcc1 n/a (libluajit-5.1.so.2 + 0x68cc1)
                #12 0x00007fca17044a19 n/a (libluajit-5.1.so.2 + 0xda19)
                #13 0x0000200000000020 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

We need more Info, if you can, please do that.

nvim -v tell nvim version

nvim --cmd "lua print(vim.loop.version_string())" tell luv version

and please describe how to reproduce this.

We need more Info, if you can, please do that.

nvim -v tell nvim version

NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1693350652

nvim --cmd "lua print(vim.loop.version_string())" tell luv version

1.48.0

and please describe how to reproduce this.

I don't have a reliable reproduction sorry, it seems to happen randomly - but it's pretty consistent - a few times per hour

NVIM v0.9.4

try Nvim 0.10 (development prerelease). The Releases page has pre-built archives for Linux/Windows/macOS.

Still happens on NVIM v0.10.0-dev-435dee7
(gdb) thread apply all bt

Thread 5 (LWP 72373):
#0  0x00006cf49faf7c5e in __futex_abstimed_wait_common () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#1  0x00006cf49fafa4c0 in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#2  0x00006cf49fc79569 in uv_cond_wait () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#3  0x00006cf49fc666ae in worker () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#4  0x00006cf49fafb272 in start_thread () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#5  0x00006cf49fb76dcc in clone3 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6

Thread 4 (LWP 72375):
#0  0x00006cf49faf7c5e in __futex_abstimed_wait_common () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#1  0x00006cf49fafa4c0 in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#2  0x00006cf49fc79569 in uv_cond_wait () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#3  0x00006cf49fc666ae in worker () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#4  0x00006cf49fafb272 in start_thread () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#5  0x00006cf49fb76dcc in clone3 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6

Thread 3 (LWP 72374):
#0  0x00006cf49faf7c5e in __futex_abstimed_wait_common () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#1  0x00006cf49fafa4c0 in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#2  0x00006cf49fc79569 in uv_cond_wait () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#3  0x00006cf49fc666ae in worker () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#4  0x00006cf49fafb272 in start_thread () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#5  0x00006cf49fb76dcc in clone3 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6

Thread 2 (LWP 72372):
#0  0x00006cf49faf7c5e in __futex_abstimed_wait_common () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#1  0x00006cf49fafa4c0 in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#2  0x00006cf49fc79569 in uv_cond_wait () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#3  0x00006cf49fc666ae in worker () from /nix/store/m5hi3j55l2l2yvsa2vz0p0il60vznz90-libuv-1.48.0/lib/libuv.so.1
#4  0x00006cf49fafb272 in start_thread () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#5  0x00006cf49fb76dcc in clone3 () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6

Thread 1 (LWP 72353):
#0  0x00006cf49fa6281e in uw_frame_state_for () from /nix/store/hc0jij4wmrcdrad7fd381r4x2j12d550-gcc-12.3.0-lib/lib/libgcc_s.so.1
#1  0x00006cf49fa6457b in _Unwind_Backtrace () from /nix/store/hc0jij4wmrcdrad7fd381r4x2j12d550-gcc-12.3.0-lib/lib/libgcc_s.so.1
#2  0x00006cf49fb81c73 in backtrace () from /nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libc.so.6
#3  0x00006cf49fe20b79 in (anonymous namespace)::Backtrace(unsigned long*, unsigned long) () from /nix/store/civcvh53r4h3g3797rpgkdafi2ibq04k-malloc-provider-scudo/lib/libclang_rt.scudo-x86_64.so
#4  0x00006cf49fe1efa5 in gwp_asan::AllocationMetadata::CallSiteInfo::RecordBacktrace(unsigned long (*)(unsigned long*, unsigned long)) () from /nix/store/civcvh53r4h3g3797rpgkdafi2ibq04k-malloc-provider-scudo/lib/libclang_rt.scudo-x86_64.so
#5  0x00006cf49fe1fe34 in gwp_asan::GuardedPoolAllocator::deallocate(void*) () from /nix/store/civcvh53r4h3g3797rpgkdafi2ibq04k-malloc-provider-scudo/lib/libclang_rt.scudo-x86_64.so
#6  0x00006cf4a042285a in luv_handle_gc () from /nix/store/v2m6bbgi0zxrhg2vk7gj25lhfrd18jiy-libluv-1.44.2-1/lib/libluv.so.1
#7  0x00006cf49fd7ca36 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#8  0x00006cf49fdc3fc7 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#9  0x00006cf49fdc42b8 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#10 0x00006cf49fdc48a5 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#11 0x00006cf49fdd9ff1 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#12 0x00006cf49fd7ea19 in ?? () from /nix/store/3m3ppqyz39ysm3qrxymxh09sd4zr6z1p-luajit-2.1.1693350652-env/lib/libluajit-5.1.so.2
#13 0x5946666656555857 in ?? ()
#14 0x59495f4666665f4e in ?? ()
#15 0x9999999999999999 in ?? ()
#16 0x2020202020202020 in ?? ()
#17 0x3ff0000000000000 in ?? ()
#18 0x4000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()

Anything else you need @zhaozg @justinmk - this is very annoying to have neovim crash regularly. Understand that's my problem not yours, but wondering if there's anything I could assist with in terms of debugging, etc ?

Do you have any plugins installed? If so, a list of your plugins would be helpful.
Unfortunately, luv_handle_gc can be called in a wide variety of scenarios (a handle is the base type of most libuv types), so it's difficult to narrow down the cause without being able to reproduce the problem.

Do you have any plugins installed? If so, a list of your plugins would be helpful.
Unfortunately, luv_handle_gc can be called in a wide variety of scenarios (a handle is the base type of most libuv types), so it's difficult to narrow down the cause without being able to reproduce the problem.

Okay fair - I'll try to put together a minimal reproducible example


Fix typo in README

Coverage remained the same at 41.082% when pulling 07f3234323c837c985c8f4a7cf822f7d1053ba6a on danielg1111:patch-1 into b71cef5db4162e9cd871ad7a1bf5716fffabe5ff on jlfwong:main.

Thanks!


baetyl-cloud安装配置更新

Codecov Report

Merging #144 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #144      +/-   ##
==========================================
- Coverage   69.52%   69.44%   -0.09%
==========================================
  Files          76       76
  Lines        4634     4634
==========================================
- Hits         3222     3218       -4
- Misses       1035     1038       +3
- Partials      377      378       +1

Impacted Files
Coverage Δ

common/string.go
80.00% <0.00%> (-20.00%)
:arrow_down:

server/mis_server.go
59.57% <0.00%> (-4.26%)
:arrow_down:

Continue to review full report at Codecov.

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


Facebook too, please! :)

Elegantly simple script. I would love it it also undirected links clicked from facebook too!
Both platforms make it similarly impossible to right-click copy link addresses to external sites, using the same redirect method.

I don't think this is an active project any longer.

That would be a shame.  It still works.  Doesn't have any malware or advertising like its competition does.  Has a good marketable name.  Should be expanded and promoted along side Privacy Badger for reducing user tracking.

Well, it's not active because it was complete and, dare I say, bug free!
The Facebook support sounds like a good idea, I'll check it out, it looks simple enough to do at a glance

Doneski, the Googles says it might take up to an hour to be published.  I'll close it out when I've tested the published version.

Daaang that was fast! You're a good man, Charlie Brown.

For a moment I thought this plugin was hacked or gone bad until I checked here (what plugin suddenly needs access to specifically my facebook?!), great work! 👍

what plugin suddenly needs access to specifically my facebook?
How does that work bmelman? I received no permissions query for this addon to strip out facebook's click-tracking redirects. Is that a set of development features or a "plugins firewall" of sorts?

Maybe it'd be a good idea if the settings default to off, allowing the user to opt-in each checkbox for each site it's going to augment links on. a-raccoon caused such a mess of things!

My chrome showed a popup when I opened a new (Incognito) Window, telling me undirect was disabled because it needed extra permissions to access facebook.com site info (I don't remember the exact phrase), offering me to allow or delete the extension.

Unfortunately, permissions in Chrome extensions don't work that way - you specify the sites to allow in the manifest, not in the code, so it can't be dynamic or user-selectable.  The first release of the plugin actually said "all data on all sites" until I restricted it to Chrome.
My only options that I can see are

Rename the extension to "Undirect for Facebook and Google" so it's clear
Make 2 extensions - one for facebook, one for google
Leave it as is

I think I'll stick with #3 - perhaps I'm selfish, but this plugin is mainly for myself, and I don't mind it accessing my facebook ^_^

Somehow it was linked to this github repository, so it's fine anyway, anyone who notices it should be wise enough to find out how and what themselves.
(I do start wondering how to check that the installed extension actually is based on this source anyway... lol)

It looks like this needs to be updated again.  Facebook likes to tack on ?fbclid=PDpsYoABR-dTfrnqEonoNetWrhfTbPsbEcOuxmOjxtPvuWisnIITMpydodLTP (example) to the end of external links.

(I do start wondering how to check that the installed extension actually is based on this source anyway... lol)

@bmelman The code is in javascript, and js is not compiled.  Open Chrome's Extensions page and View Details for this extension in question.  Note the extension's ID number (eg dohbiijnjeiejifbgfdhfknogknkglio).  Locate the folder on your harddrive by the same name.  You will find the .js files in there to compare against the source code on github.


No dist folder in "5.8.4"

When installing version 5.8.4 via npm install ip-address there is no "dist" folder anymore.
Going back to 5.8.2 works.

hey @GuyShaanan, I can add the dist/ folder back to npm, what's your use case for using it that way though?

Hmm... seems like I've been using this in the wrong way.
I used to simply include the ip-addresses-globals.js in my Angular2 project, and not require individual modules.
Though many libraries do use a dist/ folder for their "compiled" files, and offer a .min.js versions for production.

Hmm... seems like I've been using this in the wrong way.
I used to simply include the ip-addresses-globals.js in my Angular2 project, and not require individual modules.
Though many libraries do use a dist/ folder for their "compiled" files, and offer a .min.js versions for production.

@GuyShaanan not passing judgment on whether it's right or wrong, just wanted to understand how you were using it :)
added back in 5.8.6!


Building video resources...🛑 Cannot read property 'dev' of undefined

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.11.0
Amplify CLI Version
10.5.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
Red dot appears with the message: Cannot read property 'dev' of undefined
And most important, gets stuck at "Building video resources..."
Expected behavior
Expected no red flags and not stuck IMHO
Reproduction steps

amplify init
amplify video add

Project Identifier
93161a585d77835b2a7161f57e78fd0b
Log output

# Put your logs below this line

amplify video add
? Select from one of the below mentioned services: Video-On-Demand
? Provide a friendly name for your resource to be used as a label for this category in the project: myvodservice
? Select a system-provided encoding template, specify an already-created template name:  Default HLS+DASH Adaptive Bitrate
? Do you want to get notifications on the video processing job? Yes
? Do you want a custom function executed for notifications? Yes
? Is this a production enviroment? Yes
? Do you want to protect your content with signed urls? Yes
? Do you want Amplify to create a new GraphQL API to manage your videos? (Beta) No
⠋ Building video resources...🛑 Cannot read property 'dev' of undefined

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @gvasquez95 👋 thanks for raising this! Please refer to the explanation from one of our team members on this closed thread regarding the third party video plugin https://github.com/aws-amplify/amplify-cli/issues/11112#issuecomment-1268804613. In short, the plugin will need to be updated to support the latest CLI versions, and another developer has recently filed https://github.com/awslabs/amplify-video/issues/357 on their repository

ok thanks @josefaidt for the heads up, I'll try downgrading the CLI and see if it works that way

trying with npm i -g<EMAIL_ADDRESS>did the trick! Thanks again.


"Opatița" is listed in the drop-down menu

Description:
When user writes "Opatița"  the location appear in the drop-down menu next to the the county and commune witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Opatița"

Expected results
The location appears in the drop-down menu as "Sat Opatița, TIMIȘ DETA)"


Fix typo

"RSTP" should be "RTSP".
Thanks.

@yfancc20 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good/verified.


SharePoint designer does not work on SharePoint site that comes with a new MS Team.

See title; is this by design, or a known issue?

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

ID: 41ddf8ce-fda9-ee9d-d96a-801f9a2f66b7
Version Independent ID: 9aa5a49f-c440-95a8-83a1-9d38bdaeda39
Content: Known issues for Microsoft Teams
Content Source: Teams/Known-issues.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@EloquentData - I am not sure on this but I want to make sure you get this answered ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

Make sure you explicitly add yourself as a site collection admin to the site created by teams via powershell using
Set-SPOUser
-IsSiteCollectionAdmin
-LoginName
-Site .
If this doesn't work, it might be related to having to reverse the "HiddenFromExchangeClientsEnabled" to false. But usually having explicit site collection admin will allow you to edit those sites.

It is an extraordinary activity and chance to work for a pioneer in the field, pick up involvement, all around regarded looks great on continue, decent offices, free drinks, cafeteria, notwithstanding, it is extended periods, legislative issues (likewise with most organizations), difficult to get advanced except if you have somebody higher up at https://writemyessayguru.com in the organization,

@Turismon - thanks for info. Closing this out but if something still needs addressed please re-open.


Add sound to APNS push notifications

How can I add sound to push notifications? What kwarg should be passed to APNSDeviceQuerySet send_message function ?

found
Add sound param to send_message


feat(FN-2050): handle non-ascii characters in csv files

Introduction :pencil2:
We need to handle non-ascii characters in csv files in case during the download any of the characters are not ascii characters due to the different encoding used
Resolution :heavy_check_mark:
Replace any non-ascii characters including the 65533 unicode question mark character with spaces. This works for the current mock reports we are using with the allowed headers

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

Comparison is base (91637c1) 17.31% compared to head (caaeaf1) 0.48%.
Report is 224 commits behind head on main-stbr-tfm-5.

Additional details and impacted files
@@                 Coverage Diff                 @@
##           main-stbr-tfm-5   #2593       +/-   ##
===================================================
- Coverage            17.31%   0.48%   -16.84%
===================================================
  Files                 1120     104     -1016
  Lines                25591    1452    -24139
  Branches              4101     360     -3741
===================================================
- Hits                  4432       7     -4425
+ Misses               18423    1231    -17192
+ Partials              2736     214     -2522

Flag
Coverage Δ

api-test
0.48% <ø> (ø)

ui-test
?

unit-test
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Hi! is this package still actively maintained?

I'm doing research on offline-first CRUD application and came across this, however, this package isn't seem to be actively managed? Is this working well for the author?

Yes, the package is being use in production :-) It didn't have updates in months because it didn't need them yet :-) Do you have any update improvement suggestion?

Looking at the code, I'm struggling to figure out a way to show the newly created entity together with the already created. For example this situation:

I have a post which have 4 comments (the post and the comments has already synced to the server)
User add one more comment and the network is bad so assume it will only be created locally.

so how to I get all 5 comments together and if yes how do I identify them (which id should I use)

It should be done automatically since the local redux state has already the 5 comments. Do you have some code to replicate your problem?

Hi! Sorry for delayed response, I actually had the same question to the redux-offline library maintainer in this issue: https://github.com/redux-offline/tools/issues/3


SB-852: Add an option to not download remote Maven indexes for proxy repositories

Thanks for your help, @fuss86 ! :)


Authorization mechanism issue

It's an issue I just had, but I found the solution. Posting here in case someone else encounters the same problem.
I had a bucket in the eu-central-1 (Frankfurt), and upload wasn't working. I was just receiving an error: true. With some debugging I found that the authorization mechanism was the problem, as explained here:
http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4
Looks like new regions are using a new way of securing datas: "AWS4-HMAC-SHA256, also known as "V4," is one of two authentication schemes in S3.". The temporary solution was to change region for eu-west-1 (Ireland), but I guess that the new mechanism will soon be the standard, so... any plan to support it in this package?
Thanks.

I'm definitely updating the package to V4

Great! Hope you'll keep the way it works for now. Your package is the only one using local collections to store objects, and it's really handy for treating multiple images uploads at once and managing disconnected state.

No more auth issues since 46998ed01dd9d0b9166a4e520b69f4f257015d86, but can't delete files. API returns true as if no error happened, but the file is not deleted on S3... Deleting files works fine with the previous bucket (eu-west-1). Policies and CORS are the same. The only difference is the owner of the bucket – no idea why I'm not the owner of the new bucket (different behaviours per region?) – but I guess this is not related to the issue...


LTV non-repudiation error

Hello Matthias,
First of all great work you have done with pyHanko.
Describe the bug
We are planning on using pyHanko on a large scale for signed pdf docs for the Greek public sector. For that we need
the signed documents to be LTV enabled. I have tried to make an initial implementation but when I use the param embed_validation_info I get an pyhanko.sign.general.SigningError: ("The signer's certificate could not be validated", InvalidCertificateError('The X.509 certificate provided is not valid for the purpose of non repudiation')) error.
To Reproduce
The code I have written so far looks like this
    cms_signer = signers.SimpleSigner.load_pkcs12(
        certificate_filename, passphrase=password.encode('utf-8'))

    w = IncrementalPdfFileWriter(pdf_buffer)
    tst_client = timestamps.HTTPTimeStamper('https://timestamp.aped.gov.gr/qtss')

    sv = fields.SigSeedValueSpec(
        reasons=[],
        digest_methods=[],
        flags=3,
    )

    sp = fields.SigFieldSpec('Signature', seed_value_dict=sv, box=(15, 705, 175, 798))

    image = PdfImage(image=settings.STAMP_IMAGE)

    style = TextStampStyle(background=image, border_width=0)

    vc = ValidationContext(trust_roots=[cms_signer.signing_cert])

    out = signers.PdfSigner(signature_meta=signers.PdfSignatureMetadata(
                                            field_name='Signature',
                                            reason='My reason',
                                            location='My location',
                                            use_pades_lta=True,
                                            subfilter=fields.SigSeedSubFilter.PADES,
                                            embed_validation_info=True,
                                            validation_context=vc
                                            ),
                            signer=cms_signer,
                            timestamper=tst_client,
                            stamp_style=style,
                            new_field_spec=sp
                            ).sign_pdf(w)

Where the certificate_filename is a p12 signing certificate and pdf_buffer is the document I want to sign in BytesIO
Expected behavior
In the end I expect a signed document that when opened with Adobe Acrobat Reader it is listed as "LTV enabled"
Screenshots

Environment (please complete the following information):

Docker with python:3.7 image
MacOS 11.2.2

Additional context
The same issue exists in both 0.4.0 as well as 0.5.0-dev1
I have contaced HARICA which is the Hellenic Academic & Research Institutions Certification Authority and they told me that non-repudiaton has nothing to do with LTV and it shouldn't be needed to LTV enable a document.

Quick Update:
I used this flag signer_key_usage={'digital_signature'}, and now it works, but Adobe still says it is NOT LTV enabled.

Hi milouk, thanks for checking in!
Your first issue is indeed due to the fact that pyHanko (by default) requires signer certificates to have the nonRepudiation key usage bit set. However, some CAs exclusively use the digitalSignature bit instead (whether that's an appropriate decision is a matter for debate). As ta validator it is of course your prerogative to determine which key usages you consider appropriate, so you can override that default (and it seems that you've found out how that works, so that's OK).
As for your second issue: from the error message I'm seeing here, I guess that the time stamping authority that you're using is not supplying all certificates in its chain of trust. This isn't a hard requirement of the time stamping protocol, so that sometimes happens. What you can then do is try to track down the relevant certificate(s) yourself, and add them to the ValidationContext you're using to handle signing/validating. I found a certificate with a subject line that matches the missing one here: http://pki.aped.gov.gr/ca/APEDRoot.crt. Chances are that adding that one to the ValidationContext will do the trick.
Hope this helps, if anything's still unclear, feel free to ask. :)

Thanks for the very quick and detailed reply and for your research as well.
What you proposed indeed worked and I got the document signed but it still shows as "Signature is not LTV enabled" in Adobe. Am I missing something here?

Hard to tell just from that screenshot, but I'm 90% sure that that's because the TSA authorising the timestamp is untrusted in Acrobat. You can fix that on your own machine by importing the root certificate from earlier into Acrobat's trust store (it's somewhere deep in the settings menu), but that won't necessarily help if you want these signatures to be verifiable by others as well. Regardless, if marking the TSA as trusted makes the signature LTV enabled, then you'll know that that was the problem.
Is there a reason why you have to use this particular TSA? If the platform you're targeting requires this specific TSA I would simply mark the relevant certificate as trusted and move on, but otherwise you might be better off looking for a TSA that is more widely trusted (e.g. one authorised by a certificate authority on the AATL or EUTL).

So I added it to trusted certificates as you mentioned and now I got this

Is this considered an "LTV enabled" document although the "Rev 1" signature is not LTV enabled?
PS: We are using this TSA as its the Greek Governments official TSA

Interesting. Then it could be due to missing revocation information for one of the intermediate certificates, perhaps. Can you send me a signed dummy file at pyhanko.samples  mvalvekens.be?
Adobe's "LTV" criteria aren't officially documented, so this kind of thing is not always easy to debug.

Ah, wait, before you try all that: I noticed just now that you didn't add the allow_fetching=True parameter to your validation context. That's another potential reason.
Hmm, perhaps I should have pyHanko log a warning if allow_fetching is False when embedding revocation info...

Ah, thought about it as I was reading through the ValidationContext declaration but I thought it wouldn't make any difference. Im trying it now.

Ooh, I get it now! I should have read your code more carefully.
You marked the signer's certificate as a trust root in the validation context. This is very likely not what you want: in almost all trust models based on X.509, trust roots are absolute, and in particular things like "revocation status" and so on don't apply to them, so pyHanko doesn't fetch revocation info for trust roots (because that wouldn't make any sense).
You'll want to instead mark the highest relevant certificate in the chain as a trust root here; any intermediates go under other_certs. The signer's certificate doesn't need to be included in the validation context at all.
Fortunately, your cert seems to have been directly issued by a CA on the EUTL ("HARICA Qualified Legal Entities SubCA R3"), so marking that one as a trust root should work.
PS: after writing my previous comment I realised that the CLI won't help you in this case, since there's no way to get rid of the nonRepudiation key usage requirement from the CLI. That's on my roadmap of issues to fix, though.

Finally, this worked.
Matthias thank you very much for your patience and for your help. I learned a lot.
Cheers.

Hello Matthias,
First of all thanks (I am also at GRNET where we implement signing / validation services for the Greek public sector). Just a note for the non-repudiation bit. I think it is important to make it configurable, in order for the signatures to be compliant with the ETSI EN 319 412-2, section 4.3.2 (Key Usage) standard; there you can see the permitted combinations of Key Usage settings. The notes are particularly interesting.
In practice, non-repudiation is used with Qualified Electronic Signatures, not with Advanced Signatures.
Best Regards,
Panos.

Hi Panos,
Thanks for that! I was aware of the difference in semantics between digitalSignatures and nonRepudiation from X.509 / RFC 5280, but I didn't know of this specific call-out in the ESI standard.
Key usage constraints are already fully configurable in the API, but you've convinced me to make getting that into the CLI a priority (esp. for validation). It's not a lot of work---just a matter of exposing the right settings; I should be able to take care of that by the time 0.5.0 is released (which should be soon).
Thanks!

Dear Matthias
about signed pdf document validation
I am stucking in "The signer's certificate is untrusted." error(same as above).
I'm sure I'm setting the right one (root and int CA's).
I am also using signer_key_usage={'digital_signature'} at signing stage.
$ python3 verify.py
The active key usage policy requires at least one of the key usage extensions non repudiation to be present.
Chain of trust validation for Common Name: xxxxx failed.
If there are any other possibilities, could you please advise?
`
root_cert = load_cert_from_pemder('/home/ubuntu/ws/hanko/class1-root-only.crt')
int_cert = load_cert_from_pemder('/home/ubuntu/ws/hanko/intca.crt')
tsa_root_cert = load_cert_from_pemder('/home/ubuntu/ws/hanko/tsa_cacert.pem')
vc = ValidationContext(
trust_roots=[root_cert],
other_certs=[int_cert]
)
ts_vc = ValidationContext(
trust_roots=[tsa_root_cert]
)
with open('signed-13.pdf', 'rb') as doc:
r = PdfFileReader(doc)
sig = r.embedded_signatures[0]
status = validate_pdf_signature(sig, vc, ts_vc)
print(status.pretty_print_details())
`

Hi @inui-sdt2 !
You need to tell the validator to accept the digital_signature key usage as well. Right now, pyHanko takes a conservative default position by rejecting all signer certificates that don't have the nonRepudiation/contentCommitment key usage bit set.
You can change that behaviour using the key_usage_settings argument to validate_pdf_signature. See here:

https://pyhanko.readthedocs.io/en/latest/api-docs/pyhanko.sign.validation.html#pyhanko.sign.validation.validate_pdf_signature
https://pyhanko.readthedocs.io/en/latest/api-docs/pyhanko.sign.general.html#pyhanko.sign.general.KeyUsageConstraints

In your case, you probably want to pass in KeyUsageConstraints(key_usage={'digital_signature'}).
I should probably add a few words to the library usage guide to make this part of the API a bit easier to find.

PS: If you have any follow-up questions, could you please create a thread in the discussion space instead? That makes it easier to keep the issue tracker somewhat organised :).

I had the same problem (Signature is not LTV enabled and will expire after xxx) using Sectigo's QTSA server. Fortunately, the comments in this issue helped me to configure the trust root/other certs properly.
trust_root_paths = [
  'ca/sectigo/Sectigo-Qualified-Time-Stamping-Root-R45.crt', # https://crt.sh/?id=3547980726
  'ca/sectigo/Sectigo-Qualified-Time-Stamping-CA-R35.crt', # https://crt.sh/?id=3547998112
]
other_certs_paths = [
  'ca/sectigo/Sectigo-Qualified-Time-Stamping-Signer-3.crt', # https://crt.sh/?id=9297382517
]
trust_roots = [ load_cert_from_pemder(each) for each in trust_root_paths ]
other_certs = [ load_cert_from_pemder(each) for each in other_certs_paths ]

My issue was using Sectigo-Qualified-Time-Stamping-Signer-3.crt as trust_root, but it have to go in other_certs!


New feature: outline badges

This PR closes #23882
It adds outlined badges and they look like this:

Do you think it's worth adding the same hover animation to badges as in btns for consistency?

@andresgalante: maybe change the light badge to use a darker background?
As for the animation, personally I'd add it, but let's wait for @mdo to chime in.

Is there any progress on getting this integrated?  Currently I am using the button classes to get around this:
Primary

Should not it have the same size for normal and outline?
Buttons have it:

This is awesome: bump!

Is there any update on this? Would love to see this merged.

I would love this feature!
I think it's better adding the same hover animation to badges as in .btns for consistency. Also as @ocarreterom mentioned, it would be nice if the normal and outline variants have the same size.

I've made another PR which takes care of the focus state of default linked badges (#27136), this PR also adds the transition.

Now, we can make a outlined badge by utility classes. Please reconsider the necessity of new specific classes.
Primary outlined
Secondary outlined

I think badges should have flexibility to allow various custom colors. Not only theme colors defined in Bootstrap. Please see #27149 for more details.

@ysds Yeah, there are discussions here and elsewhere around how to rollback badges in v5. Do we take that stance now, or do we keep adding and improving until then?
Some things on my mind around badges:

If we don't have hover styles, we should just be using utilities (e.g., ...).
Utilities are great, but at some point we're passing CSS weight onto page weight. At a certain scale, it's better to have component classes vs utilities repeated heavily.
Ideally anyone can take .badge and pass their own background-color via inline style or class. This is possible now, and would remain regardless of any future changes.
We need to be better, with badges and beyond, at saying no to things and having limitations in the core that can easily scale up.

Writing all that out, it feels like we say no to this in v4.x given their future in v5.x?


chore(saucelabs): fix microsoft edge version

The last days the Saucelabs mode in the CI is failing with Microsoft Edge.

As per error message, there seems to be an invalid browser configuration.

While looking at the Saucelabs API and comparing the "available" versions for SL_EDGE, it looks like they have changed the versions to match the HTML engine

See https://gist.github.com/DevVersion/ffcd03143de80a22bc49aae52b612d16

Ah, good catch. Thanks!


404 in part-2

When I run npm start in the part-2 directory, the web app starts up but doesn't show anything. The JS console shows
Failed to load resource: the server responded with a status of 404 (Not Found)

Ugh NM, I just had to run npm run bundle before running.


You can decode ","

Just a demo. I have a str = 'MjAxOTA5MzAlMkMwLTAlMkMwLTAlMkMwLTA=', i will get a strange result = '20190930%2C0-0%2C0-0%2C0-0'

What's wrong with it? they all return 20190930%2C0-0%2C0-0%2C0-0

Base64.decode(str)
atob(str) // of browser built-in
/usr/bin/base64 -D # of MacOS


feat(asgi): support the ASGI WebSocket connection scope

Summary of Changes
This patch adds support for the ASGI WebSocket connection scope. The primary code paths have been tested via uvicorn/daphne and the feature is considered alpha quality until full test coverage and documentation are added. Note also that there is currently no support in the testing module for simulating WebSocket connections.
Related Issues
#321
Pull Request Checklist
This is just a reminder about the most common mistakes.  Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once; it will save you a few review cycles!
If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

[x] Applied changes to both WSGI and ASGI code paths and interfaces (where applicable).
[x] Added tests for changed code.
[x] Prefixed code comments with GitHub nick and an appropriate prefix.
[x] Coding style is consistent with the rest of the framework.
[ ] Updated documentation for changed code.

[ ] Added docstrings for any new classes, functions, or modules.
[ ] Updated docstrings for any modifications to existing code.
[ ] Updated both WSGI and ASGI docs (where applicable).
[ ] Added references to new classes, functions, or modules to the relevant RST file under docs/.
[ ] Updated all relevant supporting documentation files under docs/.
[ ] A copyright notice is included at the top of any new modules (using your own name or the name of your organization).
[ ] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.

[x] Changes (and possible deprecations) have towncrier news fragments under docs/_newsfragments/, with the file name format {issue_number}.{fragment_type}.rst. (Run towncrier --draft to ensure it renders correctly.)

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
PR template inspired by the attrs project.

This should be test complete now...just need to finish up the docs!

Regarding event vs future, I've tried to do a test to see if there is actually some difference. The test (that is quite pointless)
import asyncio
import random
import time

async def with_event(num):
    async def wait():
        await evt.wait()

    async def setter():
        for i in range(10):
            pass
        evt.set()

    for i in range(num):
        evt = asyncio.Event()
        await asyncio.gather(wait(), setter())

async def with_event2(num):
    async def wait():
        await evt.wait()

    async def setter():
        for i in range(10):
            pass
        evt.set()

    evt = asyncio.Event()
    for i in range(num):
        await asyncio.gather(wait(), setter())
        evt.clear()

async def with_future(num):
    async def wait():
        await fut

    async def setter():
        for i in range(10):
            pass
        fut.set_result(None)

    for i in range(num):
        fut = asyncio.Future()
        await asyncio.gather(wait(), setter())

count = 100_000

operations = [with_event, with_event2, with_future]
random.shuffle(operations)
for op in operations:
    start = time.perf_counter()
    asyncio.run(op(count))
    print(op.__name__, time.perf_counter() - start)

On windows with python 3.8.5 I get there results
with_event 4.5359089
with_future 4.216959699999999
with_event2 4.491865800000001

so there is a bit of difference, but it's not very large ~6%

I left this FAQ item out of https://github.com/falconry/falcon/pull/1782 in favour of this PR, but we could tackle it on that one too :slightly_smiling_face:

From my perspective, the only pending item is the back pressure discussion and message buffering refinements.
I am otherwise ready to approve :+1: :shipit:

OK gents, I have attempted to address the latest round of feedback. Let me know what you think regarding enabling the receive queue by default.


an issue with acompcor_select.py in the container

Dear developers,
Thank you for creating and maintaining this tool. It is awesome!
I am rather new using it. I am using the latest version: 1.2.1.
I created the image with singularity build xcpengine-1.2.1.sif docker://pennbbl/xcpengine:1.2.1
It seems that the function acompcor_select.py is not working from the container. Instead of saving the first 5 components of CSF and WM, it is saving random components of the same desc-confounds_regressors.tsv file.
The code looks fine. I tested it outside the container and works. I think the issue is with the container since I ran it using singularity shell --cleanenv xcpengine-1.2.1.sif and it also produced those random results every time I ran it. I also ran it with docker and got the same random a_comp_cor columns.
docker run --rm -it -v /Users/jperaza/Desktop:/data --entrypoint /xcpEngine/utils/acompcor_select.py pennbbl/xcpengine:1.2.1 -j /data/sub-01_ses-01_task-rest_desc-confounds_regressors.json -c /data/sub-01_ses-01_task-rest_desc-confounds_regressors.tsv -o /data/test.txt
I wonder if I am doing something wrong in my call to the container. Is this working for you with the container from your side?
Thank you for your help!

Hi @JulioAPeraza
you can read more about it here  https://github.com/PennBBL/xcpEngine/issues/334.  in the confound regressors, the components are not being arranged in order of  VarianceExplained. it is just random ordering. You can check *desc-confounds_regressors.json to see the detail.  it is better is better to select the  first 5 components by VarianceExplained because the arrangement in the .tsv file is not in order. You can plot one subject to see.

Hi @a3sha2
Thank you so much. I checked issue #334. I am using the latest version of both fMRIPrep and xcpEngine.
I believed the component are organized according to their singular value (https://fmriprep.org/en/stable/outputs.html#confounds).
The function acompcor_select.py is ok, the issue from my side is only happening inside the container.
I ran it outside the container
python acompcor_select.py -j /Users/jperaza/Desktop/sub-01_ses-01_task-rest_desc-confounds_regressors.json -c /Users/jperaza/Desktop/sub-01_ses-01_task-rest_desc-confounds_regressors.tsv -o /Users/jperaza/Desktop/test-local.txt
and it selected the right components. For example, for CSF: a_comp_cor_300, a_comp_cor_301, a_comp_cor_302, a_comp_cor_303, a_comp_cor_304, which indeed explained the 50% of the variance since CumulativeVarianceExplained(a_comp_cor_304) > 0.5
But when I ran it using the same data but inside the container,
docker run --rm -it -v /Users/jperaza/Desktop:/data --entrypoint /xcpEngine/utils/acompcor_select.py pennbbl/xcpengine:1.2.1 -j /data/sub-01_ses-01_task-rest_desc-confounds_regressors.json -c /sub-01_ses-01_task-rest_desc-confounds_regressors.tsv -o /data/test-container.txt
it selected different random components every time I ran it. For example,
Docker run 1 for CSF: a_comp_cor_329, a_comp_cor_342, a_comp_cor_319, a_comp_cor_386, a_comp_cor_435;
Docker run 2 for CSF: a_comp_cor_422, a_comp_cor_312, a_comp_cor_338, a_comp_cor_331, a_comp_cor_337
I do not have any experience with docker/singularity, so I do not know why this function is having odd behavior inside the container.  I was wondering if this function works for you inside the container?
Thank you for your time!

I have run the function acompcor_select.py outside the container but with the python version (3.5.3) of xcpEngine's container, and it did not work.
The function did work with the python version (3.7.1) of fMRIPrep.

Thank you Julio, I am looking at now to see what went wrong

@JulioAPeraza
Pls can you pull for new docker image (pennbbl/xcpengine:latest or pennbbl/xcpengine:1.2.1) and let me know.
thanks
nice to meet you neurohackedemy 2019

Hi @a3sha2,
The function is working. Thank you so much for fixing this so quickly.