Trivial GraphqlEndpointSource listing /graphql@{get,post,options}…

… endpoints as configured in graphql.yml to match what the GraphqlRouter will set up.
Usage:
paths:

# Standard GraphQL End-Points

- source: com.networknt.graphql.router.GraphqlEndpointSource
  exec:
  - common-chain
  - graphql-verify
  - audit
  - graphql-validator
  - graphql-handler

The following gets logged at startup (with default graphql.yml):
10:21:38.644 [main] is.thing.usernotes.0.0  INFO  com.networknt.config.Config getConfigStream - Config loaded from default folder for graphql.yml
10:21:38.649 [main] is.thing.usernotes.0.0  INFO  c.n.g.router.GraphqlEndpointSource listEndpoints - Generating /graphql from graphql.yml

@logi @NicholasAzar Thanks for the great work.


AMD GPU (ROCM) Interoperability

This pull request adds GPU execution on via ROCM through Harmonize. It also contains adjustments to match changes in the Harmonize interface.
Significant changes
Rethinking Arrays
As  mentioned a few weeks back, Numba arrays are a bit funky. Their lifetime (the span of time they have an exclusive claim over their memory) does not persist into function calls they haven't been passed into, even if references to their content are passed in.
This is an artifact of how Numba manages arrays. Whether or not an array can be deallocated is managed through reference counting, where an incref function is applied to the array whenever a reference to it is copied and a decref function is applied whenever a reference is dropped. If the number of decref calls comes to match the number of incref calls, then (at least to Numba) there are no more references to that array and it can be deallocated.

This, of course, ignores any references to things contained by that array, leading to a bunch of hazard and uncertainty in what data we can and cannot trust.
This has necessitated quite a few changes to how we work with our variables.
Passing Records as single-element arrays
Essentially any non-primitive variable, (Records, Arrays, etc) can only be created by creating arrays, and so the only way to reliably use their storage is to pass along references to their containing array and then extracting out the element in each function body.
I've attempted to do this in the least obnoxious way possible, but there are only so many options available that fall within these constraints. While these lifetime issues are more likely to be observed on GPU, this is a problem on every platform and is baked into Numba itself.
Until Numba can account for element lifetimes, or until StructRef is both stabilized and available on GPU, this may be the best we can do.
Please note that there are a few "gotchas" to look out for. Namely, if you need to overwrite a particle variable so that it references different storage, you must update both the array and the element variable.
For example, this would result in incorrect behavior:
P_arr = adapt.local_array(1,type_.particle)
P = P_arr[0]

if (condition):
    P = bank[index]

Instead, you would need to do something like this:
P_arr = adapt.local_array(1,type_.particle)
P = P_arr[0]

if (condition):
    P_arr = bank[index:(index+1)]
    P = P_arr[0]

The local_array intrinsic
Harmonize now provides a local_array intrinsic which switches between the implementations of np.empty, cuda.local.array, and hip.local.array, depending upon the compilation context. This patches over a feature deficit in Numba, which prevents us from being able to rely upon the validity of array content without having those arrays declared in that function or passed in as an argument.
To allow Harmonize as an optional dependency, the CPU array creation function (np.empty) is implemented in the adapt module as a local_array intrinsic, and the full implementation is substituted if Harmonize is available.
An example of its usage:
array = local_array(1234,numpy_type_here)

To make sure this function works consistently across platforms, local_array has all the limitations of all implementations. Hence, only literals may be supplied as the array shape, and none of the array's content is actually initialized. This means that elements need to be explicitly zeroed after the fact, if subsequent code relies upon it. Luckily, all implementations support tuple literals as well, so N-D arrays should still be available.
Removal of local_... functions in adapt
With the advent of local_array, and with the revelation of how Numba manages lifetimes, the current local_... functions are both not needed and represent a potential avenue for bugs. This PR gets rid of them.
Adding local_array to Numba
I'm setting up a local clone of Numba to put together a PR to add local_array to both the main repo and the AMD fork. This would remove the burden of maintaining the intrinsic in MCDC and Harmonize.
The leak intrinsic
To allow us to reliably use mcdc and data without passing it around everywhere as single element arrays, we need to prevent Numba from thinking we are no longer using the arrays containing those records.
The leak intrinsic essentially calls incref, but supplies no corresponding decref. With any luck (assuming Numba doesn't do anything that strips extra incref calls), calling leak on the arrays containing mcdc and data should gurantee that the arrays will never deallocate. This sort of trick would not work for other variables, which we don't want to last for the entire program lifetime, but it should work for anything like mcdc or data.
Using Harmonize's array_atomic_add and array_atomic_max intrinsics
Since the AMD fork of Numba does not support atomics, we had to implement our own. Without getting into the grizzly details of how that's accomplished in Harmonize, we now have a set of magic functions that do that for us.
Fixes for Parallel Additions to Tallies
Recent pull requests to dev have additions to tallies that used += instead of global_add. While this works on CPU, the global_add function is provided to switch from normal += to an atomic addition, which is necessary for tallies from GPUs to add up correctly. Without it, the additions made by one thread can be overwritten by another thread, leading to difficult-to-track-down bugs.
This is partly on me, since I should have reviewed that PR to double check how tallies were handled, but that tiny discrepancy took three days to diagnose. For future reference, any tally accumulations performed through global_add should remain that way when refactoring.
Updates to .gitignore
Since Harmonize now no longer simply caches ptx, the corresponding cache directory name has been updated to simply __harmonize_cache__.
The .gitignore was updated to ignore folders with this name.
Additional command-line options
To allow the users of MCDC to better control execution on GPUs, the following options have been added:

--gpu_strat: the execution strategy used during GPU execution, with async and event as possible values
--gpu_arena_size: the size of buffer used to store intermediate data, in terms of how many promises can be stored. This incurs more proportional memory for the event strategy, since it uses two buffers for each event type, and async uses only one buffer.
--gpu_block_count: the number of blocks (aka work groups) which each kernel launch uses
--gpu_rocm_path: path to the ROCm installation to use
--gpu_cuda_path: path to the CUDA installation to use

Platform and Path Auto-detection
Since CUDA execution requires normal Numba and AMD execution requires the HIP fork, Harmonize checks which is available as numba and automatically switches between the two without any input required.
If execution is on AMD, Harmonize will try to find all of the paths on its own. This still requires you to run module load <version of rocm here>, but Harmonize will look at the hipcc introduced by that load and trace back where the rest of the installation is. If all of the requisite programs are where they should be, no other input should be required, otherwise, the path to the ROCm installation should be set.
On Regression Tests
All regression tests pass for the mean results, but not the standard deviation, for all non-eigenvalue problems. This makes sense, given that GPUs perform sampling all in one batch, whereas CPUs do it in a set of smaller batches. The close matching in the mean should mean that the simulated events correspond very closely on CPU and GPU.
Non-reproducible Population Control
Eigenvalue problems currently do not reproduce because population control is not yet deteministic for GPUs. This is because:

Population control currently relies upon deterministic ordering of particles in census banks
Parallelism requires us to be able to process particles independently, and so we cannot guarantee the ordering that particles are added to the bank

Evidence
You can verify this by checking the results of eigenvalue problems after only one iteration and compare it with multi-iteration output. Output matches on one, but not after the second, but the outputs match very closely, indicating that the simulation is still "correct" in most senses.
Fixing Population Control
To make population control deterministic again, we'll need to add on a deterministic particle binning process. By that, I mean we need a way to deterministically select exactly N particles from a set, where the set of particles is deterministic, but the order we encounter those particles is not.
I've already sketched out an algorithm for this a few years ago (you may recall it, @ ilhamv), but I think this is something that would be better to put in a later PR.
Updates to Examples
Some example problems were broken by the switch to CSG. This PR includes some fixes.
New Minimum Version Requirement (Harmonize)
This latest PR will require a fresh version of Harmonize. This version is currently accessible through the amd_event_interop_revamp branch. Once this PR is accepted, this branch will be merged into main and the old version of main will be split off into a legacy branch for convenience when working with older versions.

There's still one unit test failing, but that should (hopefully) resolve quickly. I think this PR is at least far enough along to open up discussion on the changes.
One fix that will be included in future commits to this PR is the naming conventions we use for accessors and types. I currently have it set up where accessing mcdc on gpu via the program handle is mcdc_constant. It was brought up at the most recent meeting that his wasn't the most applicable, so let me know what name you prefer to use in the accessor.
Also, I believe @ilhamv  suggested tally as the name of the record type that defines the data variable that is passed around.  That change is on also on the docket for inclusion in the PR.

This latest commit has revised the accessor for mcdc to mcdc_global and revised the name of the type of data to tally, as previously suggested.

Thanks @Braxton!
For the non-reproducible population control on the eigenvalue problem, we can follow the suggestion from this paper where we essentially do a bookkeeping on the particle parent ID and progeny number and then followed by an efficient sorting algorithm at the end of each batch/cycle.

I made some cosmetic edits: particle_arr --> particle_container (feels more physical).
I removed

the old local array creation (local.py and code_factory.py).
predefined maximum RPN buffer (not it is allocated as needed, that is, the size of the tokens)

@braxtoncuneo , can you please remind me why the GPU mode can't print()?

I made some cosmetic edits: particle_arr --> particle_container (feels more physical).
I removed
* the old local array creation (`local.py` and `code_factory.py`).

* predefined maximum RPN buffer (now it is allocated as needed, that is, the respective size of the region tokens)

@braxtoncuneo , can you please remind me why the GPU mode can't print()?

The AMD fork of Numba does not support print, and the process of implementing a print comparable to that available on CUDA looks non-trivial.  If the solution is anything like the CUDA Numba implementation, it will require making an intrinsic that generates a custom call to HIP's version of the CUDA vprintf function for every combination of input types used in the print function in the program.  It's on the to-do list, but it will take time.
I did add in a limited form of print in harmonize*, but it resulted in a linking error in one out of maybe 100 print statements, and the conditions that cause those errors are still an open question. Even very subtle changes in seemingly unrelated functions could cause the bug to occur.
*If you would like to use it, it's accessible as harmonize.print_formatted. It accepts a single float/integer value and prints it in parentheses.

Didn't know that the creation of a local array needs to be literally sized...


[Feature Request] Can be toggle Meka-Bow 'Auto Fire Mode' via key

It is best to use Mekanism's  'Item Mode Switch' key in my think.

thanks for the request! I hadn't thought about that possibility
can you test the latest commit to make sure it's working correctly?


Feature/63 sign transaction

:tada: This PR is included in version 0.13.0-development.5 :tada:
The release is available on:

npm package (@development dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(rust): improve output of node create command

Updates the human-readable format
Adds machine and json output formats
Convert some debug logs to info, and add new info logs, for messages that output information visible when running node show (e.g. services created, TCP listener created, secure-channel listener, ...)

How to test
if [[ -z $OCKAM ]]; then
  export OCKAM=ockam
fi

# Human output, full
$OCKAM reset -y && $OCKAM node create
$OCKAM reset -y && $OCKAM node create --foreground

# Human output, with previous state
$OCKAM node create
$OCKAM node create --foreground

# Machine output
$OCKAM node create 1> ./output && cat ./output && rm ./output

# Json output
$OCKAM node create --output json | jq

# Duplicated node error message
$OCKAM node create n1
$OCKAM node create n1 # returns: "Node n1 has been already created"
$OCKAM node create n1 --foreground # returns: "Node n1 is already running"
$OCKAM node create n1 --foreground --skip-is-running-check # doesn't fail

@adrianbenavides the output looks really neat!

When I tested it the machine and json output there was also some console like Creating Node restful-gull.... I think this a bit unusual for this kind of flag which is generally used for automation, and not interactive use.

@etorreborre let me tackle this in the https://github.com/build-trust/ockam/pull/7966 PR, as the only way right now to filter out some messages would be to add them as a spinner message and in the other branch I've done some modifications that will affect the json/machine outputs.


add ldflags back

Summary
I've run a v0.10.0-rc.1 and when checking the output of the version command some information were missing
$ ./rekor-cli-darwin-arm64 version
  ____    _____   _  __   ___    ____             ____   _       ___
 |  _ \  | ____| | |/ /  / _ \  |  _ \           / ___| | |     |_ _|
 | |_) | |  _|   | ' /  | | | | | |_) |  _____  | |     | |      | |
 |  _ <  | |___  | . \  | |_| | |  _ <  |_____| | |___  | |___   | |
 |_| \_\ |_____| |_|\_\  \___/  |_| \_\          \____| |_____| |___|
rekor-cli: Rekor CLI

GitVersion:    v0.10.0-rc.1
GitCommit:     unknown
GitTreeState:  unknown
BuildDate:     unknown
GoVersion:     go1.18.4
Compiler:      gc
Platform:      darwin/arm64

which sounds weird because if build locally I can see it
$ ./dist/rekor-cli-darwin-arm64 version
  ____    _____   _  __   ___    ____             ____   _       ___
 |  _ \  | ____| | |/ /  / _ \  |  _ \           / ___| | |     |_ _|
 | |_) | |  _|   | ' /  | | | | | |_) |  _____  | |     | |      | |
 |  _ <  | |___  | . \  | |_| | |  _ <  |_____| | |___  | |___   | |
 |_| \_\ |_____| |_|\_\  \___/  |_| \_\          \____| |_____| |___|
rekor-cli: Rekor CLI

GitVersion:    v0.10.0-rc.1-dirty
GitCommit:     cfa65a86e69fade0d33619bc2638b6a994f191a2
GitTreeState:  dirty
BuildDate:     2022-07-28T13:18:53
GoVersion:     go1.18.4
Compiler:      gc
Platform:      darwin/arm64

maybe the is related to the proxy that we use? not sure.
but to make sure we have the data we need I'm adding back the ldflags
Release Note

Documentation

Codecov Report

Merging #944 (ac72b0d) into main (cfa65a8) will increase coverage by 0.05%.
The diff coverage is n/a.

:exclamation: Current head ac72b0d differs from pull request most recent head 53d9327. Consider uploading reports for the commit 53d9327 to get more accurate results

@@            Coverage Diff             @@
##             main     #944      +/-   ##
==========================================
+ Coverage   48.24%   48.30%   +0.05%
==========================================
  Files          61       61
  Lines        5383     5383
==========================================
+ Hits         2597     2600       +3
+ Misses       2504     2502       -2
+ Partials      282      281       -1

Impacted Files
Coverage Δ

pkg/types/alpine/v0.0.1/entry.go
55.46% <0.00%> (+1.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


Signer 1.3.0 shows no account selected

Issue: As in the screenshot if a user has multiple account and logs in after a lockout shows no account selected.

I wasn't able to repro this - @cspramit would you mind trying again with the new asset (I'm just about to attach it) to see if it's resolved?

@George-cl Yes seems to be a CNR, the defect can be closed.


Interesting but error with %store

Hello,
I ran across your bot and find it very interesting.
I'm newish to python and having a syntax error with the %store lines.
What does %store do? is it specific to Ipython?

%store is used to pass the variable to another script. Here it is passing the variable to "api" script. %store works only with Ipython interpreter. What you can do is save the script as either .ipy or .ipynb and run either in jupyter notebook or in command line using: ipython


Fix typo

Fix MicrosoftDocs/azure-docs#106503

@dawei-wang - thanks for submitting this correction.


feat: add option to skip terminal jobs in analyze

Looks like some conflicting changes happened while I was doing this.  Yay, now I get to figure out merge conflicts in git.

At this point I mostly use pycharm for things that git can't resolve itself.  If not pycharm then kdiff3 or meld.  I have all three setup as git mergetools so I can git mergetool --tool=charm.  A lot of the time they can just resolve either everything or almost everything automatically.  But sure, probably also good to be able to do stuff with git directly.

I'm fairly sure it's because #89 was merged and it changes the indent of the analyze function 😞

OK, I think I made it through.  Ready for review @altendky !


Plugin mechanism

Currently, this library supports FIDO2 and TOTP. Theoretically, it should be simple to add more methods. The only place where these are hard-coded are MFAFormView.method and MFAKey.method.
I am not sure whether I want to go down that route or stay focused on a fixed set of methods.

I would add email as an easy and popular 2fa mechanism
other mechanisms that might make the difference for "the people" are social networks like whatsapp and telegram
I would not invest on something already offered by other solution but on a different stream where simplicity, usability and accessibility would be the value of this product


Uses mastodon_home var to determine where bundle is located.

Just like the mastodon-web.service, we should not hardcode
/home/mastodon/ as this can be changed by variables to other places.

Thanks!


[FRONTEND] Change calling convention from METH_VARARGS to METH_FASTCALL

Reducing the kernel launch overhead by using METH_FASTCALL for launch instead of METH_VARARGS.

The code block within launch reduced from 18.2 us to 17.9 us (averaged over 1000 runs).

After more investigation with @zahimoud , it seems like most of the overhead is actually in our runtime check for CUDA tensors, so this PR brings a lot of complexity for not much benefit at all. This PR also introduces code divergence between the Nvidia and the AMD backend. Let me make a few changes before we merge this and switch to METH_FASTCALL


Run Cloud Code on another Server?

Since cloud code needs to be on the parse server this could really eat into the resources for the server depending on how many triggers or functions you are running.  I know from the parse cloud code you can run your own Heroku server with cloud code, would their be a way for us to fire up another Heroku instance and have the cloud code run on that instead of the same server as the Parse Server?

this is a very tough decision to make actually (google , amazon or Heroku )
Heroku  is a bit expensive than Amazon and google.
what do you think ?

Some eventual client SDK support for AWS lambda would be pretty awesome for executing cloud code functions.

Well, put it this way what ever cloud system your in, it would be nice to have another server that can handle the processing or what ever is happening under the hood since latency would be very low staying in the same provider.

I currently have parse-server + mongodb deployed on an ubuntu vm at digital ocean (smallest size: 1 core, 512mb). If you share your benchmark script, I'd like to run the same test.

@doender please see this thread https://github.com/ParsePlatform/parse-server/issues/185#issuecomment-178800219

Check github.com/flovilmart/parse-anywhere

Follow on in #500, this will be possible with webhooks.


unable to run the psql command inside a container that includes Postgres

I am not sure if this is deliberate or not, but I cannot run run the pqsl command.  I get a bash command not found error.
I have also tried to manually install but would keep getting psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed as error
I saw a commit here from 2021 of a user claiming to have fixed it and tried to copy the exact same yaml file with no success.

VSCode Version: 1.67.2
Local OS Version: Win 11
Local chip architecture: <x86, arm64, Apple Silicon> arm64
Reproduces in: Containers
Name of Dev Container Definition with Issue: Go + PostgresDB

Steps to Reproduce:

Connect to container
run the command

Try with postgres user. su postgres then psql should work. Also make sure you are executing in database container not go container.

What is the database container? I'm using the "Go & PostgreSQL" Dev container and there is no differentiation.
I tried this command in my bash terminal and I got an error saying there is no user. I then checked the users using "cat /etc/passed" and there is no user names postgres

It actually creates two seperate containers using docker compose.  I seem to not be able to access it inside the container even though I can access it via WSL. How would I be able to connect to it inside the container or is that not feasible?

I don't use WSL but it should be possible to run docker commands from bash either from powershell or inside the WSL VM itself. You would use regular exec command to ssh into the container such as  docker exec –it mycontainer /bin/bash.


bosh create-release does not use latest blobs, only the ones in the blobs cache directory

Reproducible steps:
git clone https://github.com/cloudfoundry/loggregator
cd loggregator
git checkout v74.0.1
bosh create-release
git checkout v74.0.2
bosh create-release
#notice the output, nothing about downloading blobs
rm -Rf blobs/
bosh create-release
vimdiff dev_releases/loggregator/*.yml

This doesn't work even if you explicitly call bosh sync-blobs before bosh create-release.

for now you have to rm -rf blobs/ before running bosh create-release.
Sent from my iPhone

On Jan 19, 2017, at 2:36 PM, Warren Fernandes<EMAIL_ADDRESS>wrote:
This doesn't work even if you explicitly call bosh sync-blobs before bosh create-release.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This seems to be related to #145. It will be great to have better error when switching from bosh cli v1 to bosh cli v2.

Closing - duplicate of #145. As mentioned, a workaround is bosh reset-release.


Netbird will not work when any VPN is active.

Describe the problem
If programs such as AvastVPN/NordVPN are active, peers cannot be pinged.
To Reproduce
Steps to reproduce the behavior:

Install Avast VPN.
Assign 2 peers to the same group and allow ICMP type in the group policy.
Peers cannot ping each other.

Expected behavior
While the VPN is active, peers should be able to ping each other without any problems.
Are you using NetBird Cloud?
No, Self Hosted.
NetBird version
0.28.7
NetBird status -dA output:

Do you face any (non-mobile) client issues?

Screenshots

Additional context

To be honest so much can go wrong here I would not expect any kind of support for running multiple VPN solutions at the same time apart from help investigating the networking side:

your other VPN might be taking over all routes
your other VPN might be inserting firewall rules forwarding packets somewhere else before Netbird rules
switching VPN activation order might help or it might not
it can be anything in between or everything all at once

As I have written it is highly specific to exact implementations of all VPN solutions you want to mix together and most likely not possible to tune without modifying their source codes. Only sane way I would see it working would be running each in their own container/VM and setting up routing on the host system yourself.

This does not seem to be a viable method. It doesn't seem to work in a system with hundreds/thousands of users.

Generally Netbird itself is quite unobtrusive, modifies very little in the system and can easily run multiple instances of itself at the same machine (minus DNS integration), the problem is often with the other VPN you are trying to run alongside either being either too invasive or having a few incompatible touch points.

I think maybe you're confusing the "real" VPN solutions with what is commercially branded a "VPN".
VPN stands for Virtual Private Network. Those are meant for securely connecting clients (or whole sites) to (selected set of) resources running inside a private/internal/non-public networks over (insecure) internet connection. They are often described or branded as zero-trust networks. Examples of "VPNs" are: Netbird, OpenVPN, Wireguard. Some examples of zero-trust networks are: Twingate
The commercial "VPN" offerings are pretty much anonymizations proxies meant for routing all of consumer device's traffic through those so: 1) they appear located somewhere else 2) the traffic is not leaking into (or peeked through) insecure public hotspots. They are very often purpose-built for hijacking all of the traffic and not allowing anything not going through them (which prevents working together with other solutions) to deliver on their primary purpose of making average internet user more secure on public hotspots. Examples of those are: Tor Network, Mullvad VPN, Avast VPN, Nord VPN, Proton VPN.
Some solutions are hard to definitely put into one of those 2 buckets. Generally I would not expect any kind of "commercial VPN" solution to work alongside "real" VPN/zero-trust network unless 1) the "commercial VPN" were extremely well behaved and thoughtfully implemented 2) it explicitly supported running alongside other solutions.

If there is no solution for this that netbird can do, then I guess it is not a bug.

I ran into the same problem, Tailscale is installed on the machines and no ACL rules work :(
Disabling tailscale it helps, will there be a solution to this problem?

I'm investigating a similar issue, and this seems to be related, so apologies if this misses the mark.
Although I have no illusions of the ability to co-exist with any traditional VPN solutions as they in most cases by nature take the "this is my world and no one else are allowed" approach and traditionally this has also been the desired approach for customers. In a more fragmented and globalized reality where traditional VPNs have had growing pains amongst others.
I had hoped to be able to coexist with other wireguard based solutions in more modern security settings, as there is no technical reason it could not be done without larger problems.
In my case the investigation kicked off on a Linux system where I need to have Tailscale and ideally netbird at once to avoid having to do separate systems and duplication of work.
The first obvious hurdle is that Netbird configures it's DNS server on the interface to be its own client  RFC 6598 IP. This causes a constant log spam of

systemd-resolved[63872]: Using degraded feature set TCP instead of UDP for DNS server 100.97.NNN.NN

Now, while there is a range collison between Netbird and Tailscale in this instance, I suspect that the actual underlying problem is either in how netbird handles DNS in combination with the desicion to use such a large address space to be routed increasing the chance of collisions for anyone unfortunate enough to reside behind a CGNAT.
Abusing  RFC 6598 subnets is not isolated to Netbird or Tailscale, but also commonplace nowdays both for container solutions and kubernetes further increasing likelyhood of conflicts when using /16 by default.
Tailscale approach:

IP4.ROUTE[1]:                           dst = 100.76.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[2]:                           dst = 100.81.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[3]:                           dst = 100.91.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[4]:                           dst = 100.99.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[5]:                           dst = 100.113.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[6]:                           dst = 100.93.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[7]:                           dst = 100.97.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[8]:                           dst = 100.99.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[9]:                           dst = <IP_ADDRESS>/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[10]:                          dst = 100.89.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[11]:                          dst = 100.90.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[12]:                          dst = 100.96.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[13]:                          dst = 100.103.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[14]:                          dst = 100.105.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[15]:                          dst = 100.124.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[16]:                          dst = 100.91.70.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[17]:                          dst = 100.116.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52
IP4.ROUTE[18]:                          dst = 100.125.NNN.NNN/32, nh = <IP_ADDRESS>, mt = 0, table=52

In contrast to netbird's broader approach:

IP4.ROUTE[1]:                           dst = <IP_ADDRESS>/16, nh = <IP_ADDRESS>, mt = 0

Most specific route wins, and it would at minimum be wise to add some kind of check and warning if nothing else when such conflicts arises with a link to a caveat knowledgebase to inform.
I don't expect this to turn into a supported use case, but it would have been nice.


PKCE with OIDC/OAuth2

Description
The environment variables passed to the application are bundled in the build produced by webpack. Therefore, any secret values in the environment variables are actually accessible by the end-user's browsers.

We cannot store the Client Secret for the webui as an environment variable and this is a known vulnerability for single-page apps like the new webui.
The correct way to handle single page apps was to use the Implicit Grant Type, however, this has been deprecated in favor of the PKCE with Authorization Code flow. RFC7636 describes this workflow.
A good article I found on this new workflow is here
The OIDC/OAuth2 workflow must be adapter to use code_verifier and code_challenge in its token and authorization requests respectively instead of the client_secret. If an oauth provider does not support PKCE with Authorization Code workflow, an error should be raised on the client side.
Steps to reproduce
No response
Rucio WebUI Version
master
Additional Information
No response

https://www.npmjs.com/package/react-oauth2-code-pkce
https://github.com/soofstad/react-oauth2-pkce#all-configuration-parameters


New endpoint for FCC cat API for posting data using AJAX.

I am planning to add a challenge in "JSON APIs and AJAX" challenges where campers can post data to server using AJAX. Currently FCC has no endpoint for POST.  Currently what I have thought is that if user clicks on a button named "Cats" then server should return a page containing image of cats, and if the user clicks on "Dogs" then server should return a page containing image of dogs. So if an endpoint  can be made to support this then this challenge can be added.   Challenge is simple and has been kept in theme with the existing challenges.

@MayankPratap thanks for reporting.
I am moving the thread to Curriculum Expansion Repository, for discussion.


Question about building VINS-Fusion with GPU support using OpenCV 4.6.0

I'm trying to build VINS-Fusion with GPU support using OpenCV 4.6.0, but I'm encountering some difficulties. Specifically, I'm unsure about the correct configuration and build steps required to enable GPU acceleration with OpenCV 4.6.0.
I've already followed the installation instructions for VINS-Fusion and have successfully built it without GPU support. However, I'm not sure how to incorporate OpenCV 4.6.0 with CUDA support into the build process to enable GPU acceleration.
Could someone provide guidance or pointers on how to correctly configure and build VINS-Fusion with GPU support using OpenCV 4.6.0?
Environment:

Operating System:  Ubuntu 20.04
OpenCV Version: 4.6.0
CUDA Toolkit Version:  11.4
Model: jetson xevier nx

Hi @ranjithlesoko , you probably want to post your issue in this repo: https://github.com/HKUST-Aerial-Robotics/VINS-Fusion. This repo does not include VIO.


项目启动报错 2020-08-22

(node:6464) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
$ concurrently "npm:mock" "vue-cli-service serve"
'concurrently' ▒▒▒▒▒ڲ▒▒▒▒ⲿ▒▒▒Ҳ▒▒▒ǿ▒▒▒▒еĳ▒▒▒
▒▒▒▒▒▒▒▒▒ļ▒▒▒
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

should be fixed.


[WIP] Creating windows from existing handles

Summary of the PR
Adds support for existing window handles during window creation. Additionally window platforms can be queried for support of this feature(GLFW as of 3.3 doesn't support existing window handles)
Related issues, Discord discussions, or proposals
https://github.com/Ultz/Silk.NET/issues/189
Further Comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing due to inactivity, if this progresses feel free to reopen a PR!


Enhance eks downstream cluster autoscaler

SURE-3222
Rancher Server Setup
Rancher v2.5.5
Rancher2 Provider v1.16.0
Information about the Cluster

Kubernetes v1.18 (EKS)
AWS
-->

User Information
See SURE ticket
Describe the bug
The customer ran into an issue trying to get their Rancher EKS cluster to work with their regional STS endpoint via Terraform.
This is the error:
E0728 14:57:31.939172 1 xxx_yyyyyyy.zz:265] Failed to regenerate ASG cache: cannot autodiscover ASGs: RequestError: send request failed caused by: Post
https://autoscaling.us-east-2.amazonaws.com/
: x509: certificate signed by unknown authority
F0728 14:57:31.939195 1 xxx_yyyyyyy.zz:382] Failed to create AWS Manager: cannot autodiscover ASGs: RequestError: send request failed caused by: Post
https://autoscaling.us-east-2.amazonaws.com/
: x509: certificate signed by unknown authority
Which lead them to replace some of their components (see YAML attachments):
Repro steps:
Follow the documentation above for deploying the cluster autoscaler on a downstream EKS cluster.
Set the desired number of nodes in ASG to 2, minimum to 2, and Maximum to 20.
Actual behavior:
No scaling policy is created. So even if the cluster is 99% utilized no new nodes are created.
Expected behavior:
The autoscaler should increase the nodes up to 20, since that is the max.
"We got the autoscaler to work using the attached which replaces the aws-node daemonset provided by Rancher
Can this be integrated with Rancher so it works automatically?"
Files, logs, traces:
See the SURE ticket

waiting for more input from the SURE ticket

Additional information was not received and the associated support issue is closed. Closing.


Wrong ut_tld and ut_domain if a valid TLD is in the middle of the string but not at the end

Example: 1.something.com.local
This is not a valid domain, however, since "com" is in the middle of the string, it returns "com" as ut_tld and "l.com" as ut_domain. It should return None instead.
Suggested fix:
In ut_parse_lib.py, under the findTLD() function, add the following check right before returning TLD:
    if (len(items)>0 and items[-1]!=parts[-1]):
         # the TLD is not found at the end of the string, not a valid TLD
         TLD=None

Hi @teresachila ,
Thank you for bringing this up!
I’d like to inform you that I tried applying your fix, but unfortunately, it didn’t work.
It should have theoretically resolved the issue; however, it still doesn’t seem to be functioning correctly. I suspect it’s still referencing the Public Suffix List (PSL) rules and expects the input to align accordingly. It continues to check the PSL and returns 'com' as the TLD, as specified.
I’ll label this as a duplicate, as it appears to be the same as issue #7 , but I’ll keep it open for now.
Please let me know if you have any thoughts or suggestions. I’d greatly appreciate any help or feedback!

I updated the repository at https://github.com/splunk/utbox/tree/utbox-PSL-update with the latest Public Suffix List from https://publicsuffix.org/list/.


Modal changing URL

Hello,
I am facing an issue that when i open the modal it changes my url of the page. Which is fine but it does not change it back on closure. Which leads to potential problems if users want to share link of the page or hit reload. Is there some solutions on that ? I am calling the modal from within another livewire component like this:
  <button type="button" class="btn btn-primary"             wire:click="$emit('openModal', 'backend.shared.media-item-selector')">{{__('components.media_item_selector.btn_text')}}</button>
Upon opening the modal the url in browser changes to this:

Thank you!

I found out that this is an issue with using Livewire Pagination inside the modal.
My solution was to switch to classic pagination with customized pagination component.
Do you think of some other solution how the livewire pagination would not affect the url?

Pagination 'should' work but it sometimes can be a bit buggy. A PR was made to make it easier to work with pagination but it didn't make it, unfortunately. https://github.com/livewire/livewire/pull/1997


feat(chart): include Williams %R indicator

What have you changed and why?
Williams Percentage Range (%R) indicator file is added
Related Issues
https://github.com/rodrigo-brito/ninjabot/issues/110

Codecov Report

Merging #115 (ad1f624) into main (657fa90) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   49.88%   49.88%
=======================================
  Files          15       15
  Lines        2211     2211
=======================================
  Hits         1103     1103
  Misses       1045     1045
  Partials       63       63

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 657fa90...ad1f624. Read the comment docs.

@RobertKwiatkowski thank you for the contribution! Nice work!


fix tests broken because max_funding_dollars has been removed

I changed the db schema and forgot to update the tests.  Before we had a single integer, "max_funding_dollars" to represent how much an artist could ask for in funding.  Now we have a (hacky) string that is a comma-separated list of values, like: 1,50-99,500,1000.  All the tests that expect max_funding_dollars need to be fixed to work with this string instead.  In some cases just removing the max_funding part will work, in others the test will need to be tweaked depending on what it's testing

This turned out to be super difficult, sorry!  Fixed in 7b48c0d0e40b902e9054498b5487e6f9a661ed1d


Feature/disable blank submit

Purpose
Fix the problem that add unconfirmation email submit button is always enable even if there is no input. Closes https://github.com/CenterForOpenScience/osf.io/issues/3413.
Change
Before:

After:

A while back, we decided that disabling submit buttons is an antipattern: https://github.com/CenterForOpenScience/osf.io/issues/1035 . Instead of disabling the submit button, validation errors should be displayed after the form is submitted. Can you implement this behavior instead?


Add Ability To Provide Fake Players Through Cli

This adds a --players argument which you can provide a player & uuid (using a : to split) to be sent.
The PR also changes --online-players to use the --players count if not provided (and ofc defaults to 0 if neither is provided).
Example: mc-honeypot --players jeb_:853c80ef-3c37-49fd-aa49-938b674adae6 --players Notch:069a79f4-44e9-4726-a5be-fca90e38aaf5

thank you for your contribution


Possible Class Library For Zipper

Have you thought of the idea of a class library as a starting point.  One possibility can be an external class library which I can actually create.  In that case, you just go to add nuget packages.  Then reference it.   Since I am very good with interfaces, I can easily create a system where interfaces are done.  You can implement the interfaces.  Then when ready, it will use that and do its job.   Can even do mocking for zipping so a process can be done where it pretends like its zipping it its really not zipping for test purposes.  If you would be interested in that then I can create a nuget package and explain how to use it so creating this project would be much easier.
In this case, then the class library does not care what UI is used (console, WPF, Windows Forms) or even blazor.

The goal here isn't to create a library that we can call from code. The goal is to create a working application that we can easily use. I'm not intending to create a NuGet package out of this.


Vim9: using "#" as a comment leader on the header of a legacy function in a Vim9 script is confusing

Describe the bug
In a Vim9 script, we must use # as a comment leader on the header of a legacy function, instead of ", which is confusing.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    fu Func() " comment
    endfu
EOF
)

E488 is raised:
E488: Trailing characters: " comment

Expected behavior
No error is raised.
Environment

Vim version: 8.2 Included patches: 1-1307
OS: Ubuntu 16.04.6 LTS
Terminal: XTerm(358)

Additional context
I think this error is intended, and was introduced in the patch 8.2.1268.  But it seems inconsistent.
Here are the possible comment leaders for an inline comment in a legacy script:
┌────────────────────────────────────────────┬───────────────────────┐
│ context                                    │ inline comment leader │
├────────────────────────────────────────────┼───────────────────────┤
│ legacy script level                        │           "           │
├────────────────────────────────────────────┼───────────────────────┤
│ header of legacy function in legacy script │           "           │
├────────────────────────────────────────────┼───────────────────────┤
│ body of legacy function in legacy script   │           "           │
├────────────────────────────────────────────┼───────────────────────┤
│ header of Vim9 function in legacy script   │           #           │
├────────────────────────────────────────────┼───────────────────────┤
│ body of Vim9 function in legacy script     │           #           │
└────────────────────────────────────────────┴───────────────────────┘

And here are the possible comment leaders for an inline comment in a Vim9 script:
┌──────────────────────────────────────────┬───────────────────────┐
│ context                                  │ inline comment leader │
├──────────────────────────────────────────┼───────────────────────┤
│ Vim9 script level                        │           #           │
├──────────────────────────────────────────┼───────────────────────┤
│ header of Vim9 function in Vim9 script   │           #           │
├──────────────────────────────────────────┼───────────────────────┤
│ body of Vim9 function in Vim9 script     │           #           │
├──────────────────────────────────────────┼───────────────────────┤
│ header of legacy function in Vim9 script │           #           │
├──────────────────────────────────────────┼───────────────────────┤
│ body of legacy function in Vim9 script   │           "           │
└──────────────────────────────────────────┴───────────────────────┘

Notice the asymmetry between the two tables.
In the first table, the last two contexts share the same comment leader (#), which is different than the first 3 contexts because, ultimately, a Vim9 function has priority over the type of script in which it's defined; but not in the second table.  In the latter, a Vim9 script has priority over a legacy function when determining which comment leader must be used.
The 2 tables could be turned into this diagram:
                                  *******************
                             *****                   *****
                          ***   do you write a function?  ***
                             *****                   *****
                                  /******************\
                                 /                    \
                            +-----+                  +----+
                            | yes |                  | no |
                            +-----+                  +----+
                           /                               \
                          /                                 \
        *******************                             *********************
   *****                   *****                   *****                     *****
***  is it a legacy function?  ***              ***  do you write a Vim9 script?  ***
   *****                   *****                   *****                     *****
        *******************                             *********************
       /                   \                           /                     \
      /                     \                         /                       \
 +-----+                  +----+                 +-----+                    +----+
 | yes |                  | no |                 | yes |                    | no |
 +-----+                  +----+                 +-----+                    +----+
    |                        |                      |                          |
    |                        |                      |                          |
+-------+                +-------+              +-------+                  +-------+
| use " |                | use # |              | use # |                  | use " |
+-------+                +-------+              +-------+                  +-------+

Except that the diagram is wrong in the case of the header of a legacy function in a Vim9 script.  So, it has to be made more complex to fit the current situation.

This also seems to contradict the help:
https://github.com/vim/vim/blob/6d585f4c5c8d120f768dd61bfd32f6e57ad562a7/runtime/doc/vim9.txt#L53
And in a legacy function, " must be used as a comment leader.
I think that inside a :fu function – including its header – the legacy syntax and semantics should be used, regardless of whether the script starts with :vim9script.  Just like in a :def function, the Vim9 syntax and semantics are used even when
the script does not start with :vim9script.

I suspect that it could be made to work, but that it increases the code complexity and therefore was considered not worth it, especially since using a legacy function in a Vim9 script is – in itself – already considered to be confusing:
https://github.com/vim/vim/blob/6d585f4c5c8d120f768dd61bfd32f6e57ad562a7/runtime/doc/vim9.txt#L54
So maybe this small inconsistency is to be expected.
If so, feel free to close the issue.

I've also noticed that there was no hit-enter prompt, even though the error contains multiple lines; as a result, the error message is automatically erased after 1 or 2 seconds:
vim9script
fu Func() " comment
endfu

Error detected while processing ...
line    2:
E488: Trailing characters: " comment

In contrast, this other error is not automatically erased:
vim9script
fu Func()

Error detected while processing ...
line    3:
E126: Missing :endfunction
Press ENTER or type command to continue

Just to illustrate the inconsistency:
vim9script
fu Func() # header
    " body
endfu " footer

Notice # must be used on the header, while " must be used in the body and footer.

Also, when refactoring a legacy script into a Vim9 script, you may have fold markers on the functions headers:
fu Foo() "{{{1
    ...
endfu

fu Bar() "{{{1
    ...
endfu

fu Baz() "{{{1
    ...
endfu

As soon as you write vim9script at the top of the script, your script will raise a lot of E488 errors; that wouldn't happen if " was still used on the header.


add romanian translation

Thanks to you for your translation @totpero!

The version 0.2.2, with your translations, is now published on NPM and Bower! 🎉


Feature: Add Facepunch SteamSockets Transport

Satisfies Feature Request #58, which was opened by me.
This transport is also based on the one provided by nico1207 in the feature request, but refactored and expanded by me. It still needs implementation of a way to get the round-trip time, but i couldn't figure out a good way to do that.

Will be looking at this aswell!
Fantastic initiative!

@Floris0106 What do you think about my proposed changes? Something you are interested in doing?

I agree with your proposed changes. Would have done it that way originally if I had known it is possible to write transport event based.

I have not yet looked at your changes, since i'm kinda busy with school atm. I'll probably look in to them around this weekend.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Floris0106:x: nico1207You have signed the CLA already but the status is still pending? Let us recheck it.

I agree with your changes, and I too would have done it like that, but sadly the documentation on writing transports is really lacking. @nico1207 does have to sign the cla though now.

Does anyone plan to finish this?

Does anyone plan to finish this?

afaik this is ready to merge? We implemented all the changes proposed by TwoTenPvP

afaik this is ready to merge? We implemented all the changes proposed by TwoTenPvP

Oh you are totally right. I wasn't aware. You already have my approval. @TwoTenPvP could you quickly review this again?


Add memcached suffix for Memcached CR name

Some resources created for Memcached CR do not contain prefix/suffix and use instance name. So adding the suffix, following how we create transport url, would be needed to help users identify resources created for Memcached CR.

/retest


Create abstract model for headline object - required for #7

For #7 to work, need to define interface for headline object with source and related info to filter it.

Fixed in #56


Add PBKDF2

Implemented in https://github.com/alecgn/crypthash-net/commit/c132c74c024389069b558bd0f84ab471df2a9a6f


Docs - fix broken Examples link

remove examples.md
correct reference link

I need approval to squash and merge and cherry-pick to published docs.

@kiritigowda and @rrawther this PR is to fix broken links in the documentation that return errors when the user clicks on them. This also fixes some spelling errors to avoid meltdown during linting checks, and repair a few cosmetic inconveniences while other work was being done. It is a small PR with some very worthwhile updates, but it needs someone to approve it, or provide feedback of additional effort to undertake. Thank you for any assistance you can offer.


cognitiveservices Deployment real-time percentage usage

https://learn.microsoft.com/en-us/python/api/azure-mgmt-cognitiveservices/azure.mgmt.cognitiveservices.models.deployment?view=azure-python
Is your feature request related to a problem? Please describe.
I want to load-balance between different OpenAI deployments based on their real-time percentage usage.
Describe the solution you'd like
As part of the Deployment class, or any of its underlying properties, it would be helpful to have not only the configured rate limits, but also the real-time usage (especially for TPM, not just RPM).
Describe alternatives you've considered
I have looked into Azure Metrics, but I found two problems with this approach:

the percentage usage metrics are only for Provisioned Managed Throughput, whereas I am looking for Standard TPM usage
metrics are not available in real-time

Additional context
sample code:
client = CognitiveServicesManagementClient(credential=DefaultAzureCredential(), subscription_id=sub_id)
deployments = client.deployments.list(resource_group_name="some_rg", account_name="some_acct")
print('Deployments:')
for d in deployments:
   ...

sample out:
Deployments:
================
gpt-4-turbo
================
{
  "additional_properties": {},
  "id": "...",
  "name": "gpt-4-turbo",
  "type": "Microsoft.CognitiveServices/accounts/deployments",
  "sku": "{'additional_properties': {}, 'name': 'Standard', 'tier': None, 'size': None, 'family': None, 'capacity': 10}",
  "system_data": "{'additional_properties': {}, 'created_by': '...', 'created_by_type': 'User', 'created_at': datetime.datetime(2024, 4, 10, 15, 19, 31, 6416, tzinfo=<isodate.tzinfo.Utc object at 0x10673f050>), 'last_modified_by'<EMAIL_ADDRESS>'last_modified_by_type': 'User', 'last_modified_at': datetime.datetime(2024, 4, 10, 15, 19, 31, 6416, tzinfo=<isodate.tzinfo.Utc object at 0x10673f050>)}",
  "etag": "...",
  "properties": "{'additional_properties': {}, 'provisioning_state': 'Succeeded', 'model': <azure.mgmt.cognitiveservices.models._models_py3.DeploymentModel object at 0x106bf7710>, 'scale_settings': None, 'capabilities': {'chatCompletion': 'true'}, 'rai_policy_name': 'Microsoft.Default', 'call_rate_limit': None, 'rate_limits': [<azure.mgmt.cognitiveservices.models._models_py3.ThrottlingRule object at 0x106bf79d0>, <azure.mgmt.cognitiveservices.models._models_py3.ThrottlingRule object at 0x106bf7a90>], 'version_upgrade_option': 'OnceCurrentVersionExpired'}"
}
================
Properties:
{
  "additional_properties": {},
  "provisioning_state": "Succeeded",
  "model": "{'additional_properties': {}, 'format': 'OpenAI', 'name': 'gpt-4', 'version': '1106-Preview', 'source': None, 'call_rate_limit': None}",
  "scale_settings": null,
  "capabilities": {
    "chatCompletion": "true"
  },
  "rai_policy_name": "Microsoft.Default",
  "call_rate_limit": null,
  "rate_limits": [
    "{'additional_properties': {}, 'key': 'request', 'renewal_period': 10.0, 'count': 10.0, 'min_count': None, 'dynamic_throttling_enabled': None, 'match_patterns': None}",
    "{'additional_properties': {}, 'key': 'token', 'renewal_period': 60.0, 'count': 10000.0, 'min_count': None, 'dynamic_throttling_enabled': None, 'match_patterns': None}"
  ],
  "version_upgrade_option": "OnceCurrentVersionExpired"
}

If there is an existing solution to this, please let me know.
Thank you!

Hi @vandreiradu Python sdk is auto generated by swagger definiton, as we're not domain expert, I have to transfer this issue to service team to seek for help. If there's already similar feature in swagger, sdk team will help find the sdk function for you to use, otherwise python will release a new version once there's any updates. Thanks!
related swagger: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/stable/2023-05-01/cognitiveservices.json#L3497


[dplay] Migrate DiscoveryPlusItaly to DiscoveryPlus

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
DiscoveryPlus in Italy migrated to the standard discoveryplus.com, so I migrated the DiscoveryPlusItaly extractor as a subclass of DiscoveryPlus.
I also removed the old, no more working DiscoveryPlusItalyShow extractor.
This should fix #2138

I also removed the old, no more working DiscoveryPlusItalyShow extractor.
So some other extractor does it's job? Or u just completely removed it bcoz it stopped working?

The functionality (generating playlist from a show page) must be rewriten
because of a change in the site.
On Thu, 13 Jan 2022, 05:41 Ashish Gupta, @.***> wrote:

I also removed the old, no more working DiscoveryPlusItalyShow extractor.
So some other extractor does it's job? Or u just completely removed it
bcoz it stopped working?
—
Reply to this email directly, view it on GitHub
https://github.com/yt-dlp/yt-dlp/pull/2315#issuecomment-1011791318, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFDXHGQRWMWQE5CLDF2YMTUVZJYDANCNFSM5LZUO6UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

@timendum if that's the case then don't remove it. (unless u plan on writing in this PR)

Hi,
i reverted the changes on the DiscoveryPlusItalyShow extractor.
The fix is only for the DiscoveryPlusItaly extractor.


fix(go.dev): adjust dark/light application selectors

🔧 What does this fix? 🔧
Sometimes the data-theme attribute doesn't exist, like if it is your first time visiting the website. This adjusts the theme application selectors to use prefers-color-scheme if there is no attribute set, as if data-theme="auto".
🗒 Checklist 🗒

[x] I have read and followed Catppuccin's contributing guidelines.
[x] I have updated the version appropriately in the ==UserStyle== header of the catppuccin.user.css file.

FYI for userstyles you maintain, you have the responsibility of merging PRs once you've approved them :)


unityInstance is not defined

Hello, and thank you for the asset.
I am having some issues trying to use it in Unity 2020.1.11f1
After exporting to WebGL, I get the following error when Monetization start. I am not sure what causes this, and was hoping for some help on the matter.
Invoking error handler due to
ReferenceError: unityInstance is not defined
    at sendMessageToWebMonetizationBroadcaster (http://localhost:60126/Build/DemoWebMonetization4.framework.js:2:42955)
    at HTMLDivElement.<anonymous> (http://localhost:60126/Build/DemoWebMonetization4.framework.js:2:43117)
    at <anonymous>:6:33
DemoWebMonetization4.framework.js:2 Uncaught ReferenceError: unityInstance is not defined
    at sendMessageToWebMonetizationBroadcaster (DemoWebMonetization4.framework.js:2)
    at HTMLDivElement.<anonymous> (DemoWebMonetization4.framework.js:2)
    at <anonymous>:6:33

I noticed that there have been some changes in 2020.1 https://forum.unity.com/threads/changes-to-the-webgl-loader-and-templates-introduced-in-unity-2020-1.817698/ I will either make some adjustments myself, or use an older version of Unity


Send User inputs (apiKey and apiVersion) and sends the information to the backend to be stored

Establish a page for users to submit their API key and Version ID information, a method to send this information to the backend, and appropriate functionality on the backend to temporarily store this information.

UploadPage.js was established with user inputs, a successful method was developed in UserRequests.js to send this information to the backend which can write into apiAccess.properties.


Delete cadence domain?

How to delete cadence  domain?

What is the reason that you want to delete a domain? It’s not supported because simply delete the domain will cause corruption to existing tasks and data associated to the domain. So it’s generally recommended to register another one instead.

I Just created samples-domain for testing purpose. Now after completion of testing I need to clean it up. thats the only reason.

https://stackoverflow.com/questions/65154054/can-i-or-how-to-delete-a-cadence-workflow-domain/65154055#65154055
I summarized it here.


Closes #<1713> 1713 call convert blanks@devel

Hi @danleibovitz where is the PR template and is this ready to review?

@zdz2101 I changed a few lines here - can you just double check real quick.
@danleibovitz we got it from here.  trying to get all the PRs done in the next few hours.


The import package sort adjustment in the go file.

…cmd/yurt-controller-manager/options

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind enhancement
What this PR does / why we need it:
The order of the go file import package is not standardized
Which issue(s) this PR fixes:

Fixes #652
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm
/approve


[Feature Request]: To add 2048 game

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To add the game 2048.
Tech Stack:HTML,CSS,JS
Use Case
It would be a addition of new project in the games section.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I have starred the repository

@aindree-2005 according to the participation guidelines by GSSOC , you can't add new projects.
cc @apu52


Investigate errors produced by decdk-schema

decdk-schema throws a few hundred lines of errors. Most of these appear to be caused by cyclic definitions, but some of these say e.g. "optional proprety omitted because it cannot be schematized". We should see if any of these can be fixed directly in AWS CDK, and/or if any of these are causing APIs to be unrepresentable.

This is down to 4 warnings now.

[resource "aws-cdk-lib.aws_apigateway.SpecRestApi"]
  [interface "aws-cdk-lib.aws_apigateway.SpecRestApiProps"]
    [required property "apiDefinition"]
      [enum-like "class aws-cdk-lib.aws_apigateway.ApiDefinition"]
        [method "fromAsset"]
          [interface "aws-cdk-lib.aws_s3_assets.AssetOptions"]
            [optional "bundling"]
              [interface "aws-cdk-lib.BundlingOptions"]
                [optional "local"]
                  optional property omitted because it cannot be schematized
                  didn't match any schematizable shape

[resource "aws-cdk-lib.aws_cloudfront.CloudFrontWebDistribution"]
  [interface "aws-cdk-lib.aws_cloudfront.CloudFrontWebDistributionProps"]
    [required property "originConfigs"]
      [array "Array<aws-cdk-lib.aws_cloudfront.SourceConfiguration>"]
        [interface "aws-cdk-lib.aws_cloudfront.SourceConfiguration"]
          [required property "behaviors"]
            [array "Array<aws-cdk-lib.aws_cloudfront.Behavior>"]
              [interface "aws-cdk-lib.aws_cloudfront.Behavior"]
                [optional "forwardedValues"]
                  [interface "aws-cdk-lib.aws_cloudfront.CfnDistribution.ForwardedValuesProperty"]
                    [required property "queryString"]
                      [union "boolean | aws-cdk-lib.IResolvable"]
                        [polymorphic "aws-cdk-lib.IResolvable"]
                          [impl "aws-cdk-lib.SecretValue"]
                            [method "any"]
                              didn't match any schematizable shape
                              cannot schematize method because parameter cannot be schematized
                            [method "uncachedAny"]
                              didn't match any schematizable shape
                              cannot schematize method because parameter cannot be schematized

[resource "aws-cdk-lib.aws_events.Rule"]
  [interface "aws-cdk-lib.aws_events.RuleProps"]
    [optional "targets"]
      [array "Array<aws-cdk-lib.aws_events.IRuleTarget>"]
        [polymorphic "aws-cdk-lib.aws_events.IRuleTarget"]
          [impl "aws-cdk-lib.aws_events_targets.CloudWatchLogGroup"]
            [method "<initializer>"]
              [interface "aws-cdk-lib.aws_events_targets.LogGroupProps"]
                [optional "logEvent"]
                  optional property omitted because it cannot be schematized
                  didn't match any schematizable shape

ICommandHooks
✅ Legitimate omit of optional properties. Only an object with methods can satisfy this and no built-in class is provided since the feature is intended as an escape hatch.
[resource "aws-cdk-lib.aws_lambda_nodejs.NodejsFunction"]
  [interface "aws-cdk-lib.aws_lambda_nodejs.NodejsFunctionProps"]
    [optional "bundling"]
      [interface "aws-cdk-lib.aws_lambda_nodejs.BundlingOptions"]
        [optional "commandHooks"]
          optional property omitted because it cannot be schematized
          didn't match any schematizable shape

ICommandHooks ✅
Legitimate omit of optional properties. Only an object with methods can satisfy this and no built-in class is provided since the feature is intended as an escape hatch.
[resource "aws-cdk-lib.aws_lambda_nodejs.NodejsFunction"]
  [interface "aws-cdk-lib.aws_lambda_nodejs.NodejsFunctionProps"]
    [optional "bundling"]
      [interface "aws-cdk-lib.aws_lambda_nodejs.BundlingOptions"]
        [optional "commandHooks"]
          optional property omitted because it cannot be schematized
          didn't match any schematizable shape

ILocalBundling ✅
Legitimate omit of optional property. Only an object with methods can satisfy this and no built-in class is provided since the feature is intended for user land functionality.
[resource "aws-cdk-lib.aws_apigateway.SpecRestApi"]
  [interface "aws-cdk-lib.aws_apigateway.SpecRestApiProps"]
    [required property "apiDefinition"]
      [enum-like "class aws-cdk-lib.aws_apigateway.ApiDefinition"]
        [method "fromAsset"]
          [interface "aws-cdk-lib.aws_s3_assets.AssetOptions"]
            [optional "bundling"]
              [interface "aws-cdk-lib.BundlingOptions"]
                [optional "local"]
                  optional property omitted because it cannot be schematized
                  didn't match any schematizable shape

LogGroupTargetInput ⚠
This appears to be a bug in CDK and it is actually not possible to satisfy this with built-in means.
Needs investigation. Related to https://github.com/aws/aws-cdk/pull/20748
[resource "aws-cdk-lib.aws_events.Rule"]
  [interface "aws-cdk-lib.aws_events.RuleProps"]
    [optional "targets"]
      [array "Array<aws-cdk-lib.aws_events.IRuleTarget>"]
        [polymorphic "aws-cdk-lib.aws_events.IRuleTarget"]
          [impl "aws-cdk-lib.aws_events_targets.CloudWatchLogGroup"]
            [method "<initializer>"]
              [interface "aws-cdk-lib.aws_events_targets.LogGroupProps"]
                [optional "logEvent"]
                  optional property omitted because it cannot be schematized
                  didn't match any schematizable shape

Lazy.any(), Lazy.uncachedAny() ⚠
The trace appears to be misleading and implying there is an issue with SecretValue. Incidentally the schema for all involved cloudfront.CfnDistribution.ForwardedValuesProperty, SecretValue, IResolvable, Lazy appears to be generated correctly.
Not very concerned about this warning, since it's in fringe usage and we should probably remove schema support for IResolvable all together.
[resource "aws-cdk-lib.aws_cloudfront.CloudFrontWebDistribution"]
  [interface "aws-cdk-lib.aws_cloudfront.CloudFrontWebDistributionProps"]
    [required property "originConfigs"]
      [array "Array<aws-cdk-lib.aws_cloudfront.SourceConfiguration>"]
        [interface "aws-cdk-lib.aws_cloudfront.SourceConfiguration"]
          [required property "behaviors"]
            [array "Array<aws-cdk-lib.aws_cloudfront.Behavior>"]
              [interface "aws-cdk-lib.aws_cloudfront.Behavior"]
                [optional "forwardedValues"]
                  [interface "aws-cdk-lib.aws_cloudfront.CfnDistribution.ForwardedValuesProperty"]
                    [required property "queryString"]
                      [union "boolean | aws-cdk-lib.IResolvable"]
                        [polymorphic "aws-cdk-lib.IResolvable"]
                          [impl "aws-cdk-lib.SecretValue"]
                            [method "any"]
                              didn't match any schematizable shape
                              cannot schematize method because parameter cannot be schematized
                            [method "uncachedAny"]
                              didn't match any schematizable shape
                              cannot schematize method because parameter cannot be schematized

Completed. One warning remaining with is a bug in CDK.


Update README.md

add ladumor/laravel-pwa in dev composer

@vahidalvandi  why it should be in dev?

Because it does not need to be installed in the production environment
composer u --no-dev

ok, I will test and merge today!


Change the name of SciPy integration functions

Several of the integration functions in SciPy have been renamed, but throughout ARES the old functions were still being imported. In particular, SciPy has renamed simps -> simpson, trapz -> trapezoid, and cumtrapz -> cumulative_trapezoid. As of version 1.14, these are no longer issuing a DeprecationWarning and have been entirely removed, which leads to import errors when running in an environment with recent-ish versions of SciPy.
In addition to these changes, this PR adds a version requirement to SciPy (>=1.6), as that seems to be the first version when the new names were added. It sounds as though this is just a name change and the underlying functionality is the same as previous, though I have not tested this personally.
It looks like NumPy has made a similar name change, though this would require NumPy version >=2. Because that seems like a more onerous requirement given how new it is, I have only changed the SciPy names (which have been around for a few years).

Looks good, thanks for doing this @plaplant !


Need to Validate Functionality when auto-loot is on or off in default settings

Regardless of what setting a user has, GogoLoot should function the same way.

Handled by #8


index/list API calls do not work

You get the following error:
ArgumentError: options must be a hash.
I traced the error to the JSON gem.
Two possible fixes:

use JSON.parse directly in base.rb
https://github.com/flori/json/blob/master/lib/json/common.rb#L466
pass an empty hash to JSON(RestClient.send(method, url, parameters))
https://github.com/HashNuke/mailgun/blob/master/lib/mailgun/base.rb#L75

@realdlee thanks for debugging this.
If you can send a PR and test it out, I'll merge it in.


Immediate Reauthenticate Loop

Describe the bug
When authenticating using any method (with or without login proxy, with or without oauth), authentication is successful and the device is found, but upon attempting to interact with the device (volume up/down, send tts, play/pause, etc.), a notification pops up that says the integration must be reconfigured. Doing so restarts the loop, with successful authentication (2fa, username, and password are all corrent) followed by a reconfigure notification.
To Reproduce
Steps to reproduce the behavior:

Install alexa media player through HACS
Add the integration
Authenticate using any method
Adjust volume or send TTS to device

Expected behavior
Authenticating should allow the user to use the device without simply being asked to reauth every time.
Screenshots
Notification Screen
System details

Home-assistant (version): 2021.2.1
Hassio (Yes/No): No, docker container
alexa_media  (version from const.py or HA startup): 3.6.4
alexapy (version from pip show alexapy or HA startup): 20.2.4
Amazon 2FA is enabled: Yes, although I disabled it to test all combinations of proxy/oauth without. The problem is the same regardless as to whether 2FA is enabled.

Logs
021-02-05 11:48:16 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2021-02-05 11:48:20 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2021-02-05 11:48:21 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for ical which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2021-02-05 11:48:48 WARNING (MainThread) [alexapy.helpers] alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0xb15c6a18>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: ('Expecting value: line 1 column 1 (char 0)',) 2021-02-05 11:48:48 WARNING (MainThread) [alexapy.helpers] alexaapi.get_state((<alexapy.alexaapi.AlexaAPI object at 0xb030e0b8>,), {}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',) 2021-02-05 11:48:49 WARNING (MainThread) [alexapy.helpers] alexaapi.get_guard_details((<alexapy.alexalogin.AlexaLogin object at 0xb15c6a18>,), {}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',) 2021-02-05 11:48:59 WARNING (MainThread) [alexapy.helpers] alexaapi.get_state((<alexapy.alexaapi.AlexaAPI object at 0xb030e0b8>,), {}): An error occured accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',) 2021-02-05 11:50:01 WARNING (MainThread) [alexapy.helpers] alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0xb15c6a18>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: ('Expecting value: line 1 column 1 (char 0)',)

Please enable logging on alexapy and post your logs showing the login (please scrub). Has the component ever worked for you?

Same issue, component was working fine for more than an year.

It had never worked, no. After enabling logs everything is working as intended. If it comes up again I'll post the failure logs.


Does not play music

When adding 10+ songs to the queue, music stops playing instantly.  After 6 or 10 seconds it starts skipping music.

please fix this

Hey there!
Thanks for reporting that savage issue! This is a bug, and we completely appreciate what you have reported! This issue will be marked as a bug.
@HasanBrandsXD

As Maya said, this is a bug. I'll post updates on this.

Fixed this, if this is still encountered please DM me (HasanBrandsXD#4120)


[ToBeClosed][WIP] Chainer sklearn qm9

I think Classifier and Regressor are introduced now, so inference can be done in very simple way.
Only the remaining advantage of this PR is training by fit.
But maybe we can consider different way to support wasy training? it may be ok to just close this PR.

@corochann Can we close this PR?

ok


Add spec for FFTOp

closes #357

status.md for verification is set to revisit due to #381 and #382.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1071 ms

Resolved: Bofrost.lu performance has improved in 48498b3 after 17 minutes.


Azure kincet view can't start Depth Camera

I install https://download.microsoft.com/download/1/9/8/198048e8-63f2-45c6-8f96-1fd541d1b4bc/Azure Kinect SDK 1.2.0.msi

Please help me

I think you have a bad device. There is no reason you should be getting a TransactionId of 0x5555555. Do you have a 2nd Azure Kinect?

I have only a brand new Azure Kinect. why bad device? . What can I do?

Use the k4aviewer and see if you can start just the color camera. Your log indicates reading the depth calibration is returning an invalid transaction ID, and there is no reason for that except the device or firmware are broken.
You can also try a factory reset, and then restore firmware to the version you have above.
https://support.microsoft.com/en-us/help/4494277/reset-azure-kinect-dk


Major rewrite for docs munger

This takes the total time to run the docs munger from around 1.2 seconds to .4 seconds.

Do this by splitting files into mungeLines which are just strings with metadata.
each munger only deals with mungeLines
mungers can skip doing work on lines given certain metadata
mungers do not need to do any magic newline handling or string/byte contortions

It adds a rather expensive new munger which strips whitespace from the end of lines. (takes about .11 of the .4 seconds)
add _test.go for a number of untested mungers.

@thockin @lavalamp

general comment... should keep everything as []byte. switching back and forth between strings incurs a runtime cost and is a little silly, given that we start with []byte and end with []byte. The bytes package has all of the things from the strings package that you need.
Also I'm not sure if splitting by lines is really an improvement. I'm pretty sure it broke the link checker, for one thing.

Splitting by line is a HUGE improvement. cutting runtime in 1/3 and obviously greatly reducing code complexity in the mungers. Just look at all of the wacky '\n' handling we don't need to handle. Tim and I briefly chatted about should it be 'lines' or some form of 'groups' (like the old splitByPreformatted).  Or going to some sort of full on AST. I see this as a good start.
I'll look at trying to keep things at []byte the whole time.

Sorry this took me a while to get to. I was on vacation. I haven't gone over everything yet, but I agree with @lavalamp that this might be better if we just stuck to []byte everywhere instead of switching between []byte and string. As @lavalamp mentioned, the bytes package has a lot of similar functions as the strings package, and the regexp package has []byte compatible functions as well.
I will look at this more this afternoon.

I'm quite happy to switch the whole thing to []byte and see how it looks.
/me gets excited working in high level tools that understand strings. I'm just needlessly running from my life as a C programmer.

Awesome transformation!

Thanks for doing this. And sorry it took me so long to get through a first pass.

So I started looking at getting rid of the conversions from string<->[]byte.  Check out https://github.com/eparis/kubernetes/commit/7b214552775ed59dab2f09660c0378303424a4fa all I did was remove the one big string(fileBytes) line and start going from there. That patch only touched 2 mungers (so an actual conversion would be a lot bigger with a lot more transforms). I wasn't smart, there were definitely times I should have gone []byte->string instead of just always picking string->[]byte but it really makes me think I don't want to do this...
I also looks at doing []byte->string in the rest of the code, using all string regexp functions, etc. That patch is MUCH smaller and more reasonable.
Is it the one big fileBytes->string conversion that has people worried, because I'm really feeling like the string code is better after looking at more []bytes code

@eparis We're just prematurely micro-optimizing. Every time you convert from a string to a []byte or back, it does a full copy. We were just trying to avoid them. From what I saw, that looks to be a messy and large enough effort that should be a separate PR anyway. For this one, lets just stick with strings and reap the awesome speedup we have. Let me know when you address the above comments.

@eparis This needs a rebase. I think doWork in the links code should have a better name.

Shippable is failing because util.go needs gofmt. Otherwise this looks good.

apparently my vim save hook runs gofmt, but not gofmt -s.  Gotta figure that one out. Hopefully this time it'll pass.

Super happy to see this change!  Thanks

do I get a LGTM or someone to tell me what we wrong with jenkins if not?

@eparis It looks good. Jenkins seems to have failed in cleanup. I would ask it to test this again, but this PR needs a rebase (again.. sorry) and could you go ahead and squash the commits? Then I'll put on the label.

rebased.  not squashed as each commit is free standing and implements a single 'thing' (even if one of those 5 commits is a lot bigger than the others)

Thanks for doing this! My git hooks thank you as well.


How to run Zap example?

I'm getting an error of Error: Please use a nostr extension when trying to run the Zaps example, what am I doing wrong?
(async () => {
  const { LightningAddress } = require("alby-tools");
  const ln = new LightningAddress("mikey@getalby.com");

  await ln.fetch();
  const zapArgs = {
    satoshi: 1,
    comment: "Awesome post",
    relays: ["wss://relay.damus.io"],
    p: "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
    e: "44e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
  };

  const invoice = await ln.zap(zapArgs); // generates a zap invoice
  console.log(invoice.paymentRequest); // print the payment request
})();

@LAMike310 in order to zap it will create a nostr event that needs to be signed by the zapper (you). You have the Alby extension installed in the browser that executed this code, right?

Closing due to inactivity


[MINOR][SQL] Remove redundant field verboseLayout from LogDivertAppender

What changes were proposed in this pull request?
This pr just remove a redundant field verboseLayout from LogDivertAppender.
Why are the changes needed?
Remove redundant field,
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions

friendly ping @viirya

Merged to master. Thanks.

thanks @srowen @viirya


objects/objects.txt: add SHA-3 OIDs.

Ref: http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/algorithms.html
I'm not totally sure about some of the naming conventions, please double-check...

Can you explain the dsa sha2 related changes?

Apparently request can close itself if you re-base and force-push as intermediate step. Red cross from appveyor is irrelevant, apparently it's auto-cancel thing. Now additions are backward compatible. I've commented shake-len lines till better times. As for id- prefix. It originates from specs and I figured that it would be appropriate to make explicit "connection". As for suggestion to use capitals instead. Well, actually that field is kind of meant as "machine-readable", which is another argument for adhering to something that leads you to spec. On the other hand it's the name that appears in dgst output. I meant when you say openssl dgst -something file it prints something(file)= .... Second "something" is "middle" name in objects.txt. However, when you say openssl speed -evp something it uses right-most name...

On the other hand it's the name that appears in dgst output.

The first hand is "machine-readable" and "on the other hand" formulation implies that dgst output is rather human-readable. But this last thing can actually be challenged, i.e. expectation that dgst output is not machine-readable...

Bottom line is that extra opinion is appreciated. To id- or not to id-? If not to id-, only nist_hashalgs, all of them or only those that require no additional information, i.e. pure digest algorithms and not HMAC? With rationale that that's what users are likely to expect to see in dgst output?

It would be understandable to use the nist names whether or not they begin with id-.
However it looks like the dgst -help command advertises only -sha256 but
accepts both the -SHA256 and -sha256 on the command line.
If the SHA256 alias is changed to id-sha256 then the output looks different
but also the command accepts dgst -id-sha256 and no longer -SHA256.
That is probably too much impact on the dgst command?
Do the alias names play only a role on digests and not on hmac?

Resorted to unprefixed all-capital "middle" names for "pure" hash algorithms.

Re-based.

@dot-asm: Will you merge this?

Merged. Thanks.


Notifications on withdrawals and deposits for selected address

As I understand, EthConnect is a bridge into Ethereum permissioned chains. Is it possible to register set of address in the permissioned chains to get notification for: withdrawal from and deposit to these address?

Hi @anujmax ,
EthConnect is the raw connector for Ethereum chains (see #149 for where the community is up to on chains with less predictable behaviors than BFT chains with predictable finality).
As a quick incomplete summary it provides:

Nonce management and reliable transaction submission
Full ABI<->JSON management for paylods, with simple APIs
Swagger API generation - note this is moving architecturally up to the FireFly Core layer
Reliable event streams to register subscriptions for events

I think this is what you're asking about

It does not understand the concept of a "Token" natively, as that's a higher level concept.
But you can absolutely teach it about any ABI of a contract that happens to use tokens.
FireFly Core on the other hand, does fully understand those concepts. So if you're looking for pre-built support for caching of historical transfers on tokens (vs. just the raw events), it's worth looking there: https://hyperledger.github.io/firefly/gettingstarted/mint_tokens.html


Return value of read_gpio_pin_analogue_value is unclear

It is not clearly documented what the scale of the return value of GPIOPinInterface.read_gpio_pin_analogue_value should be. Is it

between 0 and 1?
between 0 and the maximum ADC reading? (usually 255 or 1023 for an arduino)
between 0 and the reference voltage? (usually 5 V for an arduino)

I think the last option is the most useful to the user.
https://github.com/j5api/j5/blob/master/j5/components/gpio_pin.py#L76

The latter was my intention when I wrote the interface.

We should clarifiy this in code, but between 0 and the reference voltage? (usually 5 V for an arduino) is what it should be

Makes sense to me.
I think (not sure since it's been a while since I looked at this) that there's a few places in the code that don't follow this, so we should look through and make sure the right scale is being used consistently throughout the codebase.


int Usage,Or from code like

FlexboxLayout flexboxLayout = (FlexboxLayout) findViewById(R.id.flexbox_layout);
the R.id.flexbox_layout not found in my project,why?

Unless you put an id of flexbox_layout in any of your layouts, R.id.flexbox_layout isn't going to be generated.


optimize_projections fail due to difference schemas

Describe the bug
I run the follow sql in main 3ddd5ebc80444a5b40fa6b916f6ae69e5ed78d7d , get the follow error
❯ create table t(x bigint, y bigint) as values (1,2), (1,3);
0 rows in set. Query took 0.011 seconds.

❯ select z+1, y from (select x+1 as z, y from t) where y > 1;
Optimizer rule 'optimize_projections' failed
caused by
optimize_projections
caused by
Internal error: Failed due to a difference in schemas, original schema: DFSchema { fields: [DFField { qualifier: None, field: Field { name: "z + Int64(1)", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} } }, DFField { qualifier: Some(Bare { table: "t" }), field: Field { name: "y", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} } }], metadata: {}, functional_dependencies: FunctionalDependencies { deps: [] } }, new schema: DFSchema { fields: [DFField { qualifier: None, field: Field { name: "t.x + Int64(1) + Int64(1)", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} } }, DFField { qualifier: Some(Bare { table: "t" }), field: Field { name: "y", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} } }], metadata: {}, functional_dependencies: FunctionalDependencies { deps: [] } }.
This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker

but it work in datafusion-cli v33
DataFusion CLI v33.0.0
❯ create table t(x bigint, y bigint) as values (1,2), (1,3);
0 rows in set. Query took 0.003 seconds.

❯ select z+1, y from (select x+1 as z, y from t) where y > 1;
+--------------+---+
| z + Int64(1) | y |
+--------------+---+
| 3            | 2 |
| 3            | 3 |
+--------------+---+
2 rows in set. Query took 0.006 seconds.

To Reproduce
No response
Expected behavior
No response
Additional context
looks like it is related to #8340

cc @mustafasrepo

By the way, I have opened a mini PR to solve this issue (which implements approach 2).

Thanks for quick fix @mustafasrepo, but I check #8438 and find the output column name change,
❯ create table t(x bigint, y bigint) as values (1,2), (1,3);
0 rows in set. Query took 0.015 seconds.

❯ select z+1, y from (select x+1 as z, y from t) where y > 1;
+---------------------------+---+
| t.x + Int64(1) + Int64(1) | y |
+---------------------------+---+
| 3                         | 2 |
| 3                         | 3 |
+---------------------------+---+
2 rows in set. Query took 0.009 seconds.

what do you think add alias to make schema consistent? I find we before use alias in merge_project to make schema consistent.  But I am afraid it maybe make the incorrect schema correct.
https://github.com/apache/arrow-datafusion/blob/8f48053fc5f6fc3de27b69cd6f229558d8fc8990/datafusion/optimizer/src/merge_projection.rs#L80-L85

Thanks @haohuaijin I changed implementation as you suggested. It is much more better. Thanks for the suggestion

. However, their schemas are different.

FWIW I think we can always preserve the invariant that the schemas are the same via the alias suggestion @haohuaijin  suggests
Thank you for https://github.com/apache/arrow-datafusion/pull/8438


make team card clickable

team cards in /sports page need to be updated to point to details of the team.

we decided to keep the surface area small per now. so just static photo gallery


Add duration to to_next_epoch

What does this PR do?
Adds duration to the to_next_epoch function to increment total_wct.

Stack:

#3019
#3017
#3013
#3012 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.
What issue(s) does this change relate to?

Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ ] Did you run the tests locally to make sure they pass?
[ ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

✓ Commit merged in pull request #3017


"Plugin Disabled"

[x] This issue isn't duplicated - you can check if it is by using the search bar located at the top left hand corner and select "Issues" on the left.
[ ] This issue includes appropriate markdown for sections - e.g. code blocks for crash dumps.
[x] This issue is understandable - feel free to use your native language to write issues if you are not comfortable with English.

Issue description
What problem do you have? I load the plugin, the file folder is created, but every time I try to use commands, it says "plugin disabled." There is no proper documentation explaining how to configure and set up the plugin and I don't know what to do from here.

Reproducing the issue

... Install plugin
... Try to run commands

Client information
PocketMine-MP Version: 1.2.12 API 3-alpha 11
Plugin Version: 1.2.3
PHP version: 7.2.1 (default)

Optional information
Put a console error here

I don't understand what the unsupported custom installation is. Can you please elaborate and point me in the right direction so I can fix it? I downloaded directly from poggit (where it was approved), and am using PMMP.

Ok, thank you so much!

29.03 15:50:12 [Server] Server thread/INFO This plugin is disabled
29.03 15:50:12 [Multicraft] CMiko12 ran command: p help
29.03 15:49:17 [Multicraft] Skipped 46 lines due to rate limit (30/s)
29.03 15:48:39 [Server] Startup Done (0.245s)! For help, type "help" or "?"
29.03 15:48:39 [Server]<PHONE_NUMBER>888 888        888       888    888 888    888
29.03 15:48:39 [Server] 888   888P "Y88b d88   888  888        888       888    888 888    888
29.03 15:48:39 [Server] 888   888d888b.   d8P<PHONE_NUMBER>    8888888   888    888 888    888
29.03 15:48:39 [Server] d8P 888  888        888       888    888 888    888
29.03 15:48:39 [Server] 888   d88P  Y88b    d8P888  888        888       d88P  Y88b d88P  Y88b
29.03 15:48:39 [Server] Server thread/NOTICE PurePerms by 64FF00 & ProjectInfinity! #LEET.CC
29.03 15:48:39 [Server] Server thread/INFO Loading PurePerms v1.4.1-4
29.03 15:48:39 [Server] Server thread/INFO Loading Festival v1.0.2-11
29.03 15:48:39 [Server] Server thread/INFO Loading BadWordBlocker v1.1.0
29.03 15:48:39 [Server] Server thread/INFO Loading AllSigns v1.0.7
29.03 15:48:39 [Server] Server thread/INFO Loading BasicHUD v1.0.6-4
29.03 15:48:39 [Server] Server thread/INFO 時刻を Asia/Tokyo に合わせました。
29.03 15:48:39 [Server] Server thread/INFO Loading timeSetter v1.1.0
29.03 15:48:39 [Server] Server thread/INFO Loading EssentialsPE v2.0.0
29.03 15:48:39 [Server] Server thread/INFO Loading resource packs...
29.03 15:48:39 [Server] Server thread/INFO Loading recipes...
29.03 15:48:39 [Server] Server thread/INFO PocketMine-MP [#40b995a 2018-03-10] is distributed under the LGPL License
29.03 15:48:39 [Server] Server thread/INFO This server is running PocketMine-MP [#40b995a 2018-03-10] version 1.7dev "[REDACTED]" (API 3.0.0-ALPHA11)
29.03 15:48:39 [Server] Server thread/INFO Opening server on <IP_ADDRESS>:25650
29.03 15:48:39 [Server] Server thread/NOTICE To disable authentication, set "xbox-auth" to "false" in server.properties.
29.03 15:48:39 [Server] Server thread/NOTICE Online mode is enabled. The server will verify that players are authenticated to Xbox Live.
29.03 15:48:39 [Server] Server thread/INFO Starting Minecraft: PE server version v1.2.10
29.03 15:48:39 [Server] Server thread/INFO Selected English (eng) as the base language
29.03 15:48:39 [Server] Server thread/INFO Loading server properties...
29.03 15:48:39 [Server] Server thread/INFO Loading pocketmine.yml...
29.03 15:48:39 [Server] INFO Launching mod. Please be patient...
29.03 15:48:39 [Multicraft] Failed to copy jarfile from global JAR directory
29.03 15:48:39 [Multicraft] JAR file not found, copying from global JAR directory
29.03 15:48:39 [Multicraft] Failed to create local JAR directory
29.03 15:48:39 [Multicraft] Loaded config for "_Minecraft Pocket% PocketMine-MP PMMP% MCPE 1.2.10 - API 3.0.0-alpha11 (Auto Update)% MCPE v1.2.10 alpha11% 192% PocketMine-MP PMMP is the Official PocketMine-MP software, now back in action with regular updates!WARNING: API 3.0.0-ALPHA7+ WILL BREAK MANY PLUGINS!!

This pack includes EssentialsPE and PureEntitiesX, both updated for alpha11 changes.

AUTOMATIC Update!Just restart your server to activate the latest VG tested build."
29.03 15:48:39 [Multicraft] Starting server!

Does the plugin appear green when you do /plugins?

It lists it as a plugin, but appears red

It looks like multicraft is hiding the issue. I can't help you.

Thanks for trying. On a side note, would you be open to me commissioning you to write some plugins for me?


Pass error code when unexpected error occurs.

Knowing error code helps to resolve the problem.
NOTE: Error code from iOS can be negative value.

@christophercotton Thank you for the fix. I've published to 0.3.14. Also follow the readme that version that is not mentioned in changelog may occur some bug because I've not tested that yet.. Sorry.

How does it get pushed to NPM? Since I just did an install, and as a first time user it made me wonder what had happened. Is it possible to keep those out of NPM until they are tested?