Add tests for create_bids_dataframe function

Fixes #563
This PR add tests for the create_bids_dataframe function for the new loader.
It also contains corrections to the function for:

target_suffix as a nested list (as of PR #546)
filtering when no contrast_params are provided in the config file

The new tests won't passed until PR #6 on data-testing repo is merged and released, and the link to download updated here.

This PR is ready for review.
Note: The PR #6 in data-testing must be reviewed at the same time and merged first to update the download link here.
@charleygros or @andreanne-lemay, would you like to review?

Pull Request Test Coverage Report for Build 436822642

35 of 35 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.0%) to 90.059%

Totals

Change from base Build 431305693:
1.0%

Covered Lines:
5979

Relevant Lines:
6639

💛  - Coveralls


Reformat the README, and fix examples in light of #50.

Ref https://github.com/JuliaGPU/CUDArt.jl/issues/45#issuecomment-245589686

I'm going to merge this, because the README now contains factual errors.


[helm3] Outdated Releases Command

This is a Feature Request on which I wanna work and I would maintain it also
I'm the Maintainer of a Fork from a Plugin called whatup, the goal of this Plugin is to show the User which installed Charts are outdated and whats the newest Version.
With hem v3 Tiller has been removed, so this Plugin will not work anymore.
Since its a nice feature to have a list which shows which releases are outdated and what the newest Chart Version is it would be nice to have this Command directly in Helm.
For example: helm outdated would print a List with all Outdated Releases.
Ref: fabmation-gmbh/helm-whatup#10
Ref: https://github.com/bacongobbler/helm-whatup/issues/23
There exists an active Pull-Request: #7021

Just my thoughts, irrespective of it being present in helm or not, this sounds really cool! Please go ahead and start working on the same helm plugin to add v3 support. It shouldn't be tough to integrate it later if needed
And I have seen many cool plugins. It always feels like - "this is so good and general, why not have it in helm? 🤔 ". In general, in software development, I think agreeing to add a feature comes with some cost (more maintenance, more venues for possible errors, possible increased complexity). I'm interested to know on what basis features are accepted in Helm 😄 I'm hoping to see what the core maintainers have to say about this

A couple of things here:

I am the original author of the plugin, and I am still actively maintaining it.
This plugin will continue to work regardless of Tiller's presence or not. The code for release lookups relied on tiller, but it isn't required. The plugin path lookup code can be updated to work for Helm 3 as well.
the plugin is licensed as MIT. You will require a sign-off from every author that has contributed to the plugin since its inception, as all Helm projects are apache 2 licensed.
the proposal was originally raised at https://github.com/bacongobbler/helm-whatup/issues/21. The discussion is still ongoing.
as the original author, the plugin and its design has serious design flaws, which is why I have advocated for it to NOT be a core project.

I'm interested to know on what basis features are accepted in Helm

A few cases for accepting plugins as core features has been:

is it a command which is used in all cases, or is it a niche case?
has the maintainer performed all of the legal due diligence required to contribute the code?
is the codebase stable, or does it require a ton of maintenance to support?
has the plugin demonstrated a high caliber of code quality, or is it a mishmash of bash scripts hacked together over a weekend?
does it include tests?
does it include documentation?

As the original author, I can definitely say from that rubric:

definitely a niche case. Not everyone deploys from a remote chart repository.
see above
it will require many changes over time to support new cases from the community
it was written over a weekend. It does not include any tests.
no
a README with usage information doesn't count

I'd also add a "7. is there an alternative way to do it?", and I couldn't find any.
Regarding 1., that can be addressed by making it more specify, for example, as a sub-command to helm repo

There is an alternative  @fcuello-fudo , it's the existing whatup plugin

I'd love to see this in core helm! I was the one suggesting to @l0nax to persue this. I picked his fork because it seemed to have more maintenance.
A package manager needs to tell whether there are upgrades available. Imagine apt being unable to tell you that there is a security update? This is a first good step towards that.
Agreed that tests and docs are needed, but I still think this is a good first step to further get to a ready to merge state.

I'd love to see it in core helm too. It is a first step to automate charts update with help when a new chart is pushed in a repository.
It would increase security as there is no manual operation needed anymore to keep a kube cluster up to date.

I agree to all the points. The feature is really good. I still don't see why it should be in core helm ? Why not be a plugin and still work ? Everything still works. All good.
I do have some concerns about the discoverability of such good plugins, like the one mentioned here https://github.com/bacongobbler/helm-whatup/issues/21#issuecomment-550432715. Which can be solved differently - probably by providing a platform similar to Helm Hub but for Helm plugins
Also, I think we need more points and thoughts on the goals of Helm to take such decisions, along with the great points mentioned here https://github.com/helm/helm/issues/7014#issuecomment-555568414 and https://github.com/helm/helm/issues/7014#issuecomment-555572103 .

It would increase security as there is no manual operation needed anymore to keep a kube cluster up to date.

The plugin only informs you that there's an update available. It does not automatically update outdated charts. That's the role of helm upgrade. :)

Which can be solved differently - probably by providing a platform similar to Helm Hub but for Helm plugins

We have discussed that topic before at Helm Summit NA, though that was long ago and nobody followed up from there. It would require an overhaul of the existing plugin system, which we decided not to tackle for Helm 3 due to low demand.

Is there any outdated command yet for helm? This is a key feature IMHO.

You can currently use one of the two outdated plugins to have this feature until the proposal has been written:

(bacongobbler) https://github.com/bacongobbler/helm-whatup
(l0nax) https://github.com/fabmation-gmbh/helm-whatup

@l0nax Ah, I see. The second one even works for me. I tried one of them 2 weeks ago and I got errors. Now the  installation worked! Thanks a lot.

Is there an official reason why Helm would not want a native outdated command? Being able to find upgrades is one of the, if not the most important, features of a package manager.
I'm aware of the various discussions over the years so I'm not asking why the original or  current whatup command isn't part of core Helm. I'm asking if there is a technical or fundamental reason why this functionality, if implemented correctly, shouldn't be included?

Is there an official reason why Helm would not want a native outdated command? Being able to find upgrades is one of the, if not the most important, features of a package manager.
I'm aware of the various discussions over the years so I'm not asking why the original or  current whatup command isn't part of core Helm. I'm asking if there is a technical or fundamental reason why this functionality, if implemented correctly, shouldn't be included?


Fix: Fix the documentation link

I have updated the documentation link to point to the home page .
Fixes #1064

@Prakhar-Agarwal-byte  Can you please update the documentation link to point to https://move2kube.konveyor.io/commands. Thanks!

Also, please change the label in the PR title from Fix: to fix:, so that it passes the label_pr check.


Add bandit security static analysis to tests in setup.py.

Description
This is useful for general python security mistakes made during development.
Bandit project is described as:
"Bandit is a tool designed to find common security issues in Python code. To do this, Bandit processes each file, builds an AST from it, and runs appropriate plugins against the AST nodes. Once Bandit has finished scanning all the files, it generates a report."
Only requires a extra test dependency in setup.py and another line in Validate.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ x] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x ] I've read and agree to the Code of Conduct.
[ x] I've searched for any related issues and avoided creating a duplicate issue.

https://github.com/slackapi/python-slackclient/pull/460

As with #460 , please allow me to close this issue now. https://github.com/slackapi/python-slackclient/pull/460#issuecomment-611394225


Message Invoking ... breaks command substitution and pipelining

Observed Behaviour
The ibmcloud tool adds a line like Invoking 'cf ...' to stdout of the invoked command:
$ ibmcloud cf curl /v2/info
Invoking 'cf curl /v2/info'...

{
  "name": "IBM Cloud",
  "build": "6.8.0",
   ...

The Problem
This breaks many use cases where the output is being used in shell substitutions or pipelines, for instance for grabbing a specific value from the command above using jq:
$ ibmcloud cf curl /v2/info | jq -r .app_ssh_endpoint
parse error: Invalid numeric literal at line 1, column 9

Doing the same with the plain cf command works fine, because it does provide valid JSON:
$ cf curl /v2/info | jq -r .app_ssh_endpoint
ssh.eu-de.cf.cloud.ibm.com:2222

Suggested Solution
I would like to suggest to write this line to stderr instead, or providing an option to suppress this line.
Workaround
Suppressing the offending line with an additional grep helps, but it is annoying and should not be necessary:
$ ibmcloud cf curl /v2/info | grep -v '^Invoking' | jq -r .app_ssh_endpoint
ssh.eu-de.cf.cloud.ibm.com:2222

Meta
$ ibmcloud --version
ibmcloud version 0.18.1+09d36ed-2019-08-19T09:04:14+00:00

I just found that there is --quiet, which does what I want:
$ ibmcloud --quiet cf curl /v2/info | jq -r .app_ssh_endpoint

Why is this global option not documented?

cf is actually a separate CLI that is not developed by this team, but can be invoked by the IBM Cloud CLI.


[Snyk] Upgrade sinon from 11.1.2 to 15.0.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade sinon from 11.1.2 to 15.0.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 10 versions ahead of your current version.
The recommended version was released a month ago, on 2022-12-15.

Release notes

Package name: sinon

15.0.1 - 2022-12-1515.0.1

15.0.0 - 2022-11-2815.0.0

14.0.2 - 2022-11-0714.0.2

14.0.1 - 2022-10-0314.0.1

14.0.0 - 2022-05-0714.0.0

13.0.2 - 2022-04-1413.0.2

13.0.1 - 2022-02-0113.0.1

13.0.0 - 2022-01-2813.0.0

12.0.1 - 2021-11-04

12.0.0 - 2021-11-03

11.1.2 - 2021-07-27

    from sinon GitHub release notes

Commit messages

Package name: sinon

ef76b5b 15.0.1
bfa9216 Missing lock file update
aa493da Upgrade to fake-timers v10.0.2
b3ee0aa Use Node version 18 in Runkit examples
62caa67 Bump nokogiri from 1.13.9 to 1.13.10
35652f3 15.0.0
0fdb05f Remove unused custom formatter
b75fbfa Fix 2448: remove custom formatter
49ef930 docs: Fix a few typos
225b140 14.0.2
4d70f6e Upgrade nise to latest
96a0d75 Update @ sinonjs/samsam to latest
babb473 Prefer @ sinonjs/commons@2
b9e5f7d Bump nokogiri from 1.13.7 to 1.13.9
c4345dc 14.0.1
fc30a41 Update lock file
6c4753e Fixed CSS selectors in _base.scss and changed blockquote default size to 16px.
35fde18 Bump actions/cache from 2 to 3
72b6c61 Bump actions/setup-node from 2 to 3
5db24d2 Bump actions/checkout from 2 to 3
a9ffa02 chore: Included githubactions in the dependabot config
df92659 chore: Set permissions for GitHub actions
3bb7eb4 Bump nokogiri from 1.13.4 to 1.13.7
cd50360 Bump tzinfo from 1.2.9 to 1.2.10

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

This issue will be resolved with this PR - 598


Print error messages in initialization

Summary:
Print errors in random initialization.
Intended Effect:
These were accidentally omitted. This should help make debugging models a little easier.
How to Verify:
Run the model in #1326. This should now print error messages.
Side Effects:
None.
Documentation:
None.
Reviewer Suggestions:
Bob.

This looks OK, but is there some way to actually print whatever caused the problem?  Or did that get fixed at some point?

Bob, it's been fixed. If you change the model to:
model {
  reject("foo");
}

The output looks like:
...
Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
foo
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.
Rejecting proposed initial value with zero density.
Rejecting initialization at zero because of vanishing density.
...

Of course, that spits out 100 times, but it does get reported.

Great.
I should've just tested myself --- it looked like that
fragment was just going to swallow the error.

On Mar 16, 2015, at 1:26 PM, Daniel Lee<EMAIL_ADDRESS>wrote:
Bob, it's been fixed. If you change the model to:
model {
reject("foo");
}
The output looks like:
...
Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
foo
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.
Rejecting proposed initial value with zero density.
Rejecting initialization at zero because of vanishing density.
...
Of course, that spits out 100 times, but it does get reported.
—
Reply to this email directly or view it on GitHub.

Fixes #1326.


Added missing link

https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/714

@JoanneHendrickson @MikePlumleyMSFT Hi Joanne and Mike, changes look correct. Could you please confirm and merge? Thanks!


x/sys/unix: failing tests on android

The tests in the vendored copy of golang.org/x/sys/unix (through https://golang.org/cl/112436) fail on android.
https://build.golang.org/log/ad205265eb82b05e15ce4484f31ead3d7882ed02
--- FAIL: TestPpoll (0.00s)
	syscall_unix_test.go:567: mktmpfifo: failed to create FIFO: permission denied
--- FAIL: TestPoll (0.00s)
	syscall_unix_test.go:567: mktmpfifo: failed to create FIFO: permission denied
--- FAIL: TestGetwd (0.00s)
	syscall_unix_test.go:447: Chdir: chdir /usr/bin: no such file or directory
--- FAIL: TestFchmodat (0.00s)
	syscall_unix_test.go:541: Fchmodat: unexpected error: operation not supported

/cc @hyangah

On android/{arm,arm64}, also TestDevices and TestSchedSetaffinity fail in addition to the already mentioned tests:
https://build.golang.org/log/064fd97a14c0995ace8d4e2cc978a8b0814ddea0
--- FAIL: TestDevices (0.00s)
    --- FAIL: TestDevices//dev/full_1:7 (0.00s)
    	dev_linux_test.go:36: failed to stat device: permission denied
--- FAIL: TestPpoll (0.00s)
	syscall_unix_test.go:567: mktmpfifo: failed to create FIFO: permission denied
--- FAIL: TestSchedSetaffinity (0.00s)
	syscall_linux_test.go:265: SchedSetaffinity: invalid argument
--- FAIL: TestPoll (0.00s)
	syscall_unix_test.go:567: mktmpfifo: failed to create FIFO: permission denied
--- FAIL: TestGetwd (0.00s)
	syscall_unix_test.go:447: Chdir: chdir /usr/bin: no such file or directory
--- FAIL: TestFchmodat (0.00s)
	syscall_unix_test.go:541: Fchmodat: unexpected error: operation not supported

/cc @eliasnaur

Some tests fail on iOS as well:
https://build.golang.org/log/3503d3c0543b005b00f6d7dc2f5ff9844376ceea

Thanks. The TestDevices failures should be gone with https://golang.org/cl/114396. I'll send a fix for the others.


Super up

This supers up more.
After some searching across the codebase for other hook methods, I also found gems/sorbet/lib/gem-generator-tracepoint/tracer.rb. Not sure what this is/if we should super up here as well. (I suppose we should.)
Motivation
To fix bugs that used to be latent but were uncovered by #1353.
Test plan
None.

After some searching across the codebase for other hook methods, I also found gems/sorbet/lib/gem-generator-tracepoint/tracer.rb. Not sure what this is/if we should super up here as well. (I suppose we should.)

I think that tracer.rb should also super up.

I think that tracer.rb should also super up.

After further analysis, I think not. The reason why tracer.rb was on my radar is because it defines method_added, which is the name of a hook method. But this method_added has the wrong argument count and I think it might not actually be used as a hook.

After further analysis, I think not. The reason why tracer.rb was on my radar is because it defines method_added, which is the name of a hook method. But this method_added has the wrong argument count and I think it might not actually be used as a hook.

Can we rename the method?

👍


[OTHER][DOCS] Update links at bottom of README

What would you like to share?
Proposed change
-On line 80 and 81 at the bottom of the README
Discord Link Change
-Join our Discord community.
or
-Join our Discord community.
Youtube Link Change
-Subscribe to our YouTube channel.
or
-Subscribe to our YouTube channel.
This is in order to make the links a little more concise and help the flow of the document.
-Please post your thoughts to this update below
Additional information
No response

@Nithin108 go on for it :)

yes

any one review my pull request

@schmelto review my pull request and merge it

Hello @Nithin108 , Are you still working on this??

@TheRemyD @schmelto If this issue is not closed, can I work on it?

@schmelto @krshkodes here the PR for review - https://github.com/EddieHubCommunity/support/pull/3940


canvas loading issues

when loading canvas UI. envelop error generated

I fixed this problem
this is node version problem.
node version is different to last project.

This problem is very good


Rustfmt and clippy

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

CI tests passed. Gonna take a look.

r? @inetic


Serial editor is all the same color

Everything is blue! We need to set whatever colors in pxtarget.json are required to get a nicer theme.

How do we get into serial editor? I don't see console.log blocks. Can we cut this feature for arcade for now?


Spanish translation / Traducción al español

This thread tracks the translation of the documentation to Spanish. Feel free to post either in Spanish or English in this threads, whatever seems most appropriate.
cc @aslozada

The title of the index.html without translation
index.po (Spanish)

index.po (German)

I think this might be a bug in sphinx-design, the Fortran package manager is a card title which apparently not captured with babel, similar issue for the button-ref, I will report those upstream.

Some warnings when translating menu options

fpm-docs/pages/index.md:1: WARNING: inconsistent term references in translated message. original: ['tutorial'], translated: []
fpm-docs/pages/index.md:1: WARNING: inconsistent term references in translated message. original: ['how-to'], translated: []
fpm-docs/pages/index.md:1: WARNING: inconsistent term references in translated message. original: ['design'], translated: []
fpm-docs/pages/index.md:1: WARNING: inconsistent term references in translated message. original: ['spec'], translated: []

Result

Yeah, I found this one as well. Most likely due to https://github.com/executablebooks/sphinx-design/issues/44, another issue with sphinx-design, resulting from the translation of the button-ref labels. I just went with not translating those for now until we get a fix upstream.

Description in "How-to" section:
file  how-to.po. installation.md:3

Installing fpm
This how-to guide covers the installation of  Fortran on various platforms.

Fortran or fpm?

Buttons lose features after translation. (Text-color, Background-color, action)
is this another issue with sphinx-design?

I changed the markup to capture the card titles, I'll look into a way to get the button-ref directives working. I could make the whole card clickable as alternative

Hi Sebastian @awvwgk,
The languages links are missing in fpm.fortran-lang.org

An update of the sphinx-book-theme broke your side. I'll pin it to 0.2.0 and than figure out later what was changed.


[FEATURE] Aggregate the necessary Docker images

quay.io has an outage today, which is blocking the deployment and development of Longhorn.
We should figure out the necessary images for Longhorn deployment, re-tag/re-publish them to longhorn in Docker Hub. This has two advantages:

Remove the extra dependency on different container image registry.
The users can easily pull all the necessary images to their air-gap environment.

Of course, Docker Hub is still the single point of failure. We might want to set up some way to mitigate that later, e.g. mirroring images to other registries.
Some examples from Rancher:
https://github.com/rancher/rancher/releases/download/v2.2.12/rancher-images.txt
https://github.com/rancher/rancher/releases/download/v2.2.12/rancher-save-images.sh
https://github.com/rancher/rancher/releases/download/v2.2.12/rancher-load-images.sh

Pre-merged Checklist

[x] Does the PR include the explanation for the fix or the feature?

[] Is the backend code merged (Manager, Engine, Instance Manager, BackupStore etc)?
The PR is at longhorn , manager

[ ] ~Is the reproduce steps/test steps documented?~

[x] Which areas/issues this PR might have potential impacts on?
Area: Longhorn installation using private registry, air-gap installation.

[ ] If the fix introduces the code for backward compatibility Has an separate issue been filed with the label release/obsolete-compatibility?
The compatibility issue is filed at

[ ] If labeled: area/ui Has the UI issue filed or ready to be merged?
The UI issue/PR is at

[ ] ~~if labeled: require/doc Has the necessary document PR submitted or merged?
The Doc issue/PR is at ~~

[ ] If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case?
The automation skeleton PR is at
The automation test case PR is at

[ ] if labeled: require/automation-engine Has the engine integration test been merged?
The engine automation PR is at

[ ] if labeled: require/manual-test-plan Has the manual test plan been documented?
The updated manual test plan is at

Reproduce/Testing:

run script scripts/longhorn-save-images.sh in longhorn repo to pull and export images to a tar file
run script scripts/longhorn-load-images.sh in longhorn repo to load image from the tar file and push it to private registry
Install Longhorn using the private registry
Expected: successfully install.

We need to add a document for the end-user.

@PhanLe1010 I've tweaked the name and images of the list a bit. See https://github.com/longhorn/longhorn/pull/1592 . Can you update the document and test steps? Remember to include the option to not save the images to a tar.gz file.
Btw, I found if I run the script like this:
./scripts/load-images.sh test

It will just hang there without error out. We should fix this.

I got it. Fixing them

Validation: PASSED


Provide tags on hub.docker.com with major version

Can we have a major stable version? I mean, when 5.7.2 comes out, can it be also tagged as 5.7 and just 5. To have a better lockup by major version in docker-compose.yml. So, it wouldn't be needed to edit a docker-compose.yml each time new minor versions come out.
Igor.

I agree it could be a good idea, but I don't know if we can do this with the Docker Hub auto-build from the Github repository. @carlosasj Do you think it could be possible ?

Indeed it would be possible using a custom hook. I am building my docker images and tag it later as latest to ensure latest is always my latest build.
An example post_push hook is available in my hooks repository. If required, I can provide such a hook script to ensure tagging of new builds for different version numbers.

@pichouk since docker 1.10 we can provide multiple image tags at build.
Example: docker build -t mattermost-prod-app:5.7.2 -t mattermost-prod-app:5.7 -t mattermost-prod-app:5 -t mattermost-prod-app:latest .
I'm not familiar with Docker Hub, but it seems it could be done via tags and regexp.

Hope this helps a little.
Igor.

Could be great, I don't have the access to configure Github/Docker Hub hooks for the repository. Maybe @cpanato can ?

Just my two cents: In case that works, it will cause multiple build processes. Currently, I have some issues setting up my automated builds. I would go for the build hooks, which just adds additional tags to the last build.

I can take a look at this


Refine Seq shape inference

Try to refine static shape info for seq.

The definition of SeqType is modified for static shape inference. It's very likely another field (memref) will be added for dynamic shape and lowering
Static shape starts from empty seq and the newly inserted tensor is merged with the existing tensor type of the seq.

Jenkins Linux ppc64le Build #2201 [push] Refine Seq shape inferen... started at 10:10

Jenkins Linux s390x Build #3085 [push] Refine Seq shape inferen... started at 10:06

Jenkins Linux amd64 Build #3094 [push] Refine Seq shape inferen... started at 09:06

Jenkins Linux s390x Build #3085 [push] Refine Seq shape inferen... passed after 37 min

Jenkins Linux ppc64le Build #2201 [push] Refine Seq shape inferen... passed after 49 min


Release workflow doesn't support 2FA

The workflow added in #27 doesn't work because of a limitation in NPM's authentication strategy. Currently, you can either have 2FA for authorization only (login), or for everything (including publishing libraries) - unfortunately, that applies to tokens as well.
So during the action run, it attempts to publish and asks for an OTP (one-time-password) - which of course I can't provide.
Memorializing this Twitter conversation.

I swapped the token used with a different account (without publish 2FA), so this should be resolved.


In search for original Teckin SP22 firmware

Hello,
sorry if this isn't the right place.
I need to reflash the original firmware on one (about a year old, should use ESP8266) Teckin SP22.
Maybe someone from the community still has the original firmware image from the setup process.
Would be really cool!
If this request does not fit here, just let me know and I'll remove it.
Kind Regards

You won't be able to use another device's firmware image with yours if you wish to use the Tuya cloud. Each firmware image has a uniquely assigned key specific to each device.

@kueblc  alright, thanks for your reply. I hope I'll find the original firmware somewhere (I know I extracted it somewhere). And even if not, luckily they are cheap.


Add support for zsh

Doesn't seem to work in zsh right now. Pressing prefix + I just print the script.

It works on zsh 5.2 for me, but the script is displayed for about a second.

It's supposed to be working on zsh 5.2 at least. Maybe an old bash version?
What does /usr/bin/env bash --version return for you?

As for the 1s delay, I'm working on a performance improvement, should be fixed on next release! Thanks for pointing out @arecarn! :ok_hand:

GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)
Copyright (C) 2007 Free Software Foundation, Inc.

and I'm on Mac OS X

That should be the issue, can you try upgrade to bash 4? I've tested it on OSX with bash 4 and tmux 2.x and it's working.
You need to make sure that /usr/bin/env bash returns 4.x version and not the native 3.2 one ( that's under /bin/bash )

/usr/bin/env bash will return the first bash that it finds in your $PATH, you just need to make sure that /usr/local/bin/bash comes before /bin/bash
That should work :tm: !

I just upgraded bash to version 4 and checked that /usr/bin/env bash really is the new version but running tmux-fingers still only show:
cat /var/folders/v9/7f_8xhsx2j76z59gqtbqz6500000gn/T//tmux-fingers.e19TOU6E | /Users/peter/.tmux/plugins/tmux-fingers/scripts/fingers.sh "%4" "%5" /var/folders/v9/7f_8xhsx2j76z59gqtbqz6500000gn/T//tmux-fingers.e19TOU6E

Ah, it works after displaying the above script for about 1 second, as @arecarn mentioned. But the problem is that there is no coloring of the identifiers, so I missed them.

Cool! The one second delay should be gone in next update.
I'm still wondering why the lack of colors. Does printf "\033[1;33m%s\033[0m" "testing" print as yellow to you? Maybe I should use tput instead of printf

No, that line doesn't print in any color for me. I'm using tmux which supports true color though, so maybe that's the problem.
Another problem I encountered is that trying ifconfig and then prefix + F just show a blank screen, so no IPs are showing to be yanked.

What about echo $(tput setaf 3)$(tput bold)testing$(tput sgr0)?
If you can run tmux capture-pane -p > output.txt and provide me the input I can take a look. Make sure to do not leak any sensitive information! :point_up:
Thanks for all the feedback!

echo $(tput setaf 3)$(tput bold)testing$(tput sgr0) just print a grey text "testing", no colors either. Here is the output.txt file
output.txt

Oops, sorry, I meant for the ifconfig output.

Here is a part of the output from ifconfig that contains an IP address:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 ::1 prefixlen 128
        inet <IP_ADDRESS> netmask 0xff000000
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        nd6 options=1<PERFORMNUD>


[ODP] docx sha1 mismatch

hi all,
I think the sha1 hash got a little problem in mime_type: application/vnd.ms-word.document.12
file id  : BC6BAF0531250242!67529
sha1_hash: E3F8566423ECA45422FD28FDA334C03A54EE1E1C

after download and run openssl sha1
4668f15966dda307576006a0e905977d00335214

but in mime_type: application/vnd.ms-excel.12; charset=UTF-8
file id  : BC6BAF0531250242!8538
sha1_hash: 58C7BD39FE7DBCD9628BD76EEB84C5ECD9B87572

after download and run openssl sha1
58c7bd39fe7dbcd9628bd76eeb84c5ecd9b87572

it matchs!

Hi @joewutaiwan, I asked around and apparently there was an issue that could have caused this hash discrepancy. It will be resolved by one of the following actions:

An edit to the file in question
A notification from the sync client that the hash is mismatching

For your specific repro it'll probably be easiest to edit the file and save it, at which point the hashes should match again.


add action property to first nested menu

:tada: This PR is included in version 1.4.0-rc.39 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


additional client information

Is it possible to get more client information from sh station? e.g. Pow (SNR), Channel, A-Time (Associated time), Phymode

I used aeromiko to get data from the APs.  If what you are looking for is in there, it can be exposed.  I'm not using this myself since everyone in my house has switched to iPhones.  Not I can just just the iCloud plugin.


⚠ Bofrost.hr has degraded performance

In 0731e6f, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 1927 ms

Resolved: Bofrost.hr performance has improved in 42453ee after 3 hours.


怎样获取群聊所有成员

from wxpy import *
bot = Bot(cache_path=True)
groups = bot.groups().search('群名')[0]
for member in groups:
print(member)

groups = bot.groups().search('19尔雅吃胖胖')[0]
Traceback (most recent call last):
File "", line 1, in
IndexError: list index out of range


运行export_llama.py显示  if output_attentions:就停止运行了

你好，我在运行第一步导出onnx的时候，出现了下面的警告，并且到 if output_attentions就停止运行了，我想知道是不是torch版本的影响，如果可以的话，能不能分享一下导出的onnx文件，非常感谢！
(ascend2) usr@il003:/mnt/nvme1/usr/ascend-llm/export_llama$ python export_llama.py
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/utils/generic.py:441: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/modeling_attn_mask_utils.py:94: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if (input_shape[-1] > 1 or self.sliding_window is not None) and self.is_causal:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/modeling_attn_mask_utils.py:137: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if past_key_values_length > 0:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:912: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  all_self_attns = () if output_attentions else None
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:913: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  next_decoder_cache = [] if use_cache else None
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:384: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  out_key_value = (key_states, value_states) if use_cache else None
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:397: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if attn_weights.size() != (bsz, self.num_heads, q_len, kv_seq_len):
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:404: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if attention_mask.size() != (bsz, 1, q_len, kv_seq_len):
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:414: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if attn_output.size() != (bsz, self.num_heads, q_len, self.head_dim):
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:431: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if not output_attentions:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:696: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if output_attentions:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:699: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if use_cache:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:943: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if use_cache:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:944: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  key_values= layer_outputs[2 if output_attentions else 1]
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:948: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  next_decoder_cache.extend(layer_outputs[2 if output_attentions else 1])
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:950: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if output_attentions:
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:959: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  next_cache = torch.concat(next_decoder_cache).reshape(len(self.layers),2,*next_decoder_cache[0].shape) if use_cache else None
/home/usr/anaconda3/envs/ascend2/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:960: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if output_attentions:

生成的onnx文件已经上传到阿里云盘上了，我用的torch版本为2.1.1，当时出问题的代码版本是哪一版，最新的代码还有该问题吗


Make fee configurable

Preview is available here:http://stellar-demo-wallet-client-pr338.previews.kube001.services.stellar-ops.com/


Replace Reddit with daily.dev

Is your feature request related to a problem? Please describe
Reddit seems to not be used a lot in regards to what we are tackeling.
Describe the solution you'd like
Replace the link to reddit with a link to daily dev, so we can grow that community instead.
Additional context
Link: https://dly.to/ra0ANxPXhwl

Hey Björn, I'd like to solve this issue.

Hey Björn, I'd like to solve this issue.

That'd be great, thank you! Do you need more info on anything?

Hey Björn, I'd like to solve this issue.

That'd be great, thank you! Do you need more info on anything?

yeah, where/ how do I do this?

Hey Björn, I'd like to solve this issue.

That'd be great, thank you! Do you need more info on anything?

yeah, where/ how do I do this?

It is in the documentation-website repository. You would need to find and add a logo, remove the reddit logo and exchange the social link in the social nav component.


Linux app keeps resizing the window after user finishes editing a time entry

is connected to getSizeHint that is in the timeentrycellwidget.cpp.  Set SizeHint acts a littlebit as setMinimumSize. Basically setSizeHint changes both width and height. We only actually need height changing to make entries with header taller.
Might be fixed with eda92db8895c0e61be0e5abd3001c17563081c51  Needs to be double checked.


Conventions dissapeared

I have been stressed to see 404, when I was opening conventions cheat sheet to choose commit type for commit. Where I can find them now?
404 link is https://github.com/ajoslin/conventional-changelog/blob/master/CONVENTIONS.md#type

nevermind, it is here now https://github.com/ajoslin/conventional-changelog/blob/master/conventions/angular.md =)

Where do you get the link? Why does it link to a master branch where things might change?

I get this link from searching inside repo.

Why does it link to a master branch where things might change?

so what? I’m bookmarking it to my browser’s toolbar like this:

No worries. I thought it was referenced from a web page so that we need to fix.

no, it’s only mine shortcut reference for types in conventional changelog


Error Object: ObjectChance (.?AUObjectChance@@)

Nooo... Is it really impossible to unprotect Dota Allstar?
Maps: https://www.epicwar.com/maps/337265/
Output: https://anonymfile.com/KVx9N/dota-v678c-ai-14e-farewell-deprotected.w3x

I'm not sure why that particular version doesn't deprotect, but you could try this version, it works for me (on reforged)
https://www.epicwar.com/maps/317436/
DotA_Allstars_7.03b2.w3x
Something difficult about Dota is that some versions use a memory hack which makes them not work in Reforged.
If you search for *.dll inside the MPQ & inside war3map.j, you will see how it's done.
The memory hack gives WC3 extra functionality that's not built into the base game.
You can open Dota in reforged world editor, but you can't run it in game without removing the memory hack, which will break important functionality.
If you want to run on classic, where memory hack is supported, you have to downgrade the map version after deprotection, my tool doesn't support older versions.
You could try this tool for that: https://www.hiveworkshop.com/threads/map-adapter.326456/

Ok, if that's the case, thank you in advance for your reply.
actually I only play Warcraft Classic because I don't like Reforge moreover I want to edit dota just want to redeploy the shop which I think is too far hahaha...
It seems that after this game has been around for 21 years, it's time to forget it. and after I tried to open the DotA_Allstars_7.03b2.w3x protection it turned out it didn't run on my device at version 127.17085


Bug - splash screen has battery / wifi icon in it

When the splash screen is shown, in the top right you can see the battery and wifi icon in it. It looks like a screenshot and does not look good. We should remove that from the splash screen

fixed in virtual nation PR


Storage release commit

The versions should be:

Azure.Storage.Blobs.Batch v12.3-preview.1
Azure.Storage.Blobs v12.5.0-preview.5
Azure.Storage.Common v12.5.0-preview.5
Azure.Storage.Files.DataLake v12.3.0-preview.1
Azure.Storage.Files.Shares v12.3.0-preivew.1
Azure.Storage.Queues v12.4.0-preview.5

/azp run net - storage - ci

/azp run net - storage - tests

The live tests are fine, other than SAS and Blob Batch-Set Tier with Snapshot or VersionId.
See the live test run on this PR earlier today, which we should also merge because it fixes live test failures - https://github.com/Azure/azure-sdk-for-net/pull/13203

https://github.com/Azure/azure-sdk-for-net/pull/13203 also needs to merge before release.

/azp run net - storage - ci


mirror s3

@jdorfman thoughts? close if no.

I think all we need to do is just enable it in the AWS console. Every time I try, it fails. Not sure if a screen share would be good or not. I'll leave this open until we can address it.

@jdorfman All this PR is doing is making github match what's currently in s3. Including file permissions. This is the result of running an s3 to local sync. They should match and these files should be 0644, basic rw for files, as opposed to 0755, which is rwx for directories and executables.

The permissions change is fine. The image changes too; my guess is I optimized it some time in the past when I shouldn't have touched those.
But, the new bootstrap v4 files are redundant. We never exposed them...

Also, v3.3.7 doesn't have a bundle file; I have no idea where you guys took it from...
Finally, having the old jquery in the CDN seems bad to me. We didn't expose it ever to the public.


Error with !bbstart	command, the other commands works

hi, the !bbstart command doesn't work, with a rock 5a (RK3588) the rest of the commands work, but bbstart doesn't, here's the error it gives:
2024-04-06T15:58:11.183570Z ERROR belabot::belabox: failed to deserialize e=Error("missing field password_hash", line: 0, column: 0) obj=("config", Object {"acodec": String("opus"), "asrc": String("USB audio"), "bitrate_overlay": Bool(false), "delay": Number(0), "max_br": Number(4500), "pipeline": String(" "), "relay_account": String("2142"), "relay_server": String("3"), "remote_key": String(" "), "srt_latency": Number(3000), "ssh_pass": String(" ")})
thanks in advance

Hi @djr0x ,
Thanks for opening an issue. This was already known, but I didn't have time to update it.
Will be working again in the next release v0.3.4


Joe/embedverifier cherrypick

Codecov Report

Merging #23 (cdd7011) into main (59bf5ca) will increase coverage by 0.93%.
The diff coverage is 71.42%.

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

@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
+ Coverage   41.02%   41.96%   +0.93%
==========================================
  Files          27       28       +1
  Lines        2486     2521      +35
==========================================
+ Hits         1020     1058      +38
+ Misses       1466     1463       -3

Impacted Files
Coverage Δ

masp_primitives/src/primitives.rs
68.88% <ø> (ø)

masp_proofs/src/lib.rs
60.71% <ø> (+60.71%)
:arrow_up:

masp_proofs/src/params.rs
71.42% <71.42%> (ø)

masp_proofs/src/circuit/convert.rs
61.42% <0.00%> (-1.43%)
:arrow_down:

masp_proofs/src/circuit/sapling.rs
66.77% <0.00%> (+0.31%)
:arrow_up:

masp_proofs/src/hashreader.rs
46.15% <0.00%> (+46.15%)
:arrow_up:

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 59bf5ca...ed30c3f. Read the comment docs.

merged by #25


Upgrading from 26 to 27 breaks mocks adjacent to node_modules

💥 Regression Report
Previously, with Jest 26, I had a monorepo structured like this:
backend/services/serviceA/__mocks__/axios.ts
backend/services/serviceA/src/api.spec.ts
backend/services/serviceA/src/api.ts
node_modules/axios
package.json

where axios.ts looks something like:
const axios = jest.createMockFromModule('axios')

axios.create.mockImplementation(() => axios)

export default axios

api.ts looks something like:
import axios from 'axios'

export default axios.create({
  baseURL: 'baseURL'
})

and api.spec.ts looks something like:
import axios from 'axios'

jest.isolateModules(() => {
  require('./api')
})

it('should create api', () => {
  expect(axios.create).toHaveBeenCalledWith({
    baseURL: expect.stringContaining('baseURL')
  })
})

axios was automocked as per the documentation.
Currently, with Jest 27, the same monorepo suddenly has errors that look like:
    expect(jest.fn()).toHaveBeenCalledWith(...expected)

    Expected: {"baseURL": StringContaining "baseURL"}

    Number of calls: 0

I was able to "fix" this by explicitly using jest.mock('axios'). If I console.log inside of the mock implementation of axios.ts, it does get used with or without the explicit mocking, but somehow the test is failing without it.
Last working version
Worked up to version: 26.6.3
Stopped working in version: 27.0.6
To Reproduce
Steps to reproduce the behavior:

Mock a node module manually
Use assertions for something in that node module
Get errors in Jest 27

Expected behavior
Tests should continue to pass by using the manual mock of the node module axios.
Link to repl or repo (highly encouraged)

Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS 11.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
    Yarn: 2.4.2 - ~/.nvm/versions/node/v14.15.0/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.15.0/bin/npm
  npmPackages:
    jest: 27.0.6 => 27.0.6

We had to hold off on upgrading to Jest 27 due to this. If we have time we might try again since it has been a few months.

Here is a simple reproduction: https://github.com/eliw00d/jest-27-issues-repro
We are still experiencing this with 27.5.1.

The documentation still states that this is possible: https://jestjs.io/docs/manual-mocks#mocking-node-modules
But every time I try to upgrade to Jest 27 this is a blocker.

Closing in favor of https://github.com/facebook/jest/issues/12777


Update README.md

Coverage remained the same at 81.908% when pulling 1a93ed4364965672ee6ecfa7d3d98667c0c9918f on update-readme into 436a2f21e5e28c7c761130720befe05381db0765 on master.


Update v0.1.0beta

Checklist

[x] Used a fork of the feedstock to propose changes

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


FBSDKCoreKit/FBSDKCoreKit.h file not found

I have FBSDKCoreKit/FBSDKCoreKit.h file not found error and  struggled with this problem a couple of days but can't solve it((
Any ideas?
react-native 0.40
react-native-fsdk 0.5.0
facebook sdk: 4.19.0

please ref: https://nsulistiyawan.github.io/2016/07/05/Fix-FBSDKCoreKitFBSDKCoreKith-file-not-found-on-React-Native.html

http://stackoverflow.com/questions/41995528/fbsdkcorekit-fbsdkcorekit-h-file-not-found-error-react-native-ios

Still having the same issue, have had this problem for days now

Followed every step and looked at every stack overflow

☝ I cant believe that was the issue for me. But yes, that solved it for me! Thanks @selfeky !

When you download the FacebookSDK, remember to copy all the files within that zip to ~/Documents/FacebookSDK, I copied the whole folder that was extracted and had problems, it wasnt until i copied all the files within the folder and extract it into ~/Documents/FacebookSDK, when my problem was fixed.


Support for preleases

Currently, a kots prerelease will always use master (alpha image tag) of kotsadm. We intentionally ignore prerelease tags and always use alpha. IIRC, we do this so that interim releases work, but this is starting to make beta releases difficult. The code is here: https://github.com/replicatedhq/kots/blob/5dd232b0e5361630f0cc0ed441151749087d0ae3/pkg/kotsadm/kotsadm_version.go#L30
There doesn't seem to be a test preventing us from changing this. @divolgin or @laverya do you know why this code exists?

This is added in 1.14.0 (and being tested with 1.14.0-beta.2 tag)


Update project links

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

Project coverage is 100.00%. Comparing base (944553c) to head (d5716c0).

Additional details and impacted files
@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          462       462
  Branches        50        50
=========================================
  Hits           462       462

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


Detect when the user has entered a lat/lng into the location field and set the map to that position

Description
I had a bunch of specific lat/lng's that didn't correspond to addresses so there was no autocomplete option, and I cbf punching each one into google maps so I could then click-to-place in the Location field's map.
This pull request uses regex to detect when the user has entered a lat/lng string like -38.149926, 144.361808 and sets the map to there.
Related Issues
None.

I'm wondering if there's any reason to make this an opt-in rather that change the default behavior. Something like adding an autoDetectLatLngValue prop and a corresponding option on the map partial.
cc. @ifox

Hi guys, this is a nice feature but I agree with @pboivin that it should probably be an opt-in. We never know what Twill users ended up doing with the map field and I wouldn't want to unexpectedly change the behavior for them.

@pboivin @ifox up to you but if it was in the next major release you could flag it as "potentially breaking"? I can't imagine too many users would have implemented a custom lat/lng detector on the frontend themselves.

I think this could be released sooner in 2.6 if we could add the debounce and the "feature flag". Do you have some time to look into this @mattdinthehouse?

@pboivin unfortunately I'm slammed for the next few weeks so I won't be able to commit to delivering it on time. I'll check back here once things calm down to see if it still needs doing though.

@mattdinthehouse No worries, thanks for the quick reply :)


add Boost to app list

Issue: #116

Cool! Thank you!

I really can't thank you enough for adding my app! Have a nice day! :tada:


bilibili

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that a supported site is broken
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
中国
Provide a description that is worded well enough to be understood
bilibili在导入cookie后无法下载
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-v', 'https://www.bilibili.com/bangumi/play/ep289960?spm_id_from=333.337.0.0', '--cookies-from-browser', 'edge']
[debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[392389b7d] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19044-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-01-04-git-4a80db5fc2-full_build-www.gyan.dev (setts), ffprobe 2023-01-04-git-4a80db5fc2-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[Cookies] Extracting cookies from edge
[debug] Extracting cookies from: "C:\Users\Administrator\AppData\Local\Microsoft\Edge\User Data\Default\Network\Cookies"
[debug] Found local state file at "C:\Users\Administrator\AppData\Local\Microsoft\Edge\User Data\Local State"
[Cookies] Extracted 346 cookies from edge
[debug] cookie version breakdown: {'v10': 346, 'other': 0, 'unencrypted': 0}
[debug] Proxy map: {}
[debug] Loaded 1786 extractors
[BiliBiliBangumi] Extracting URL: https://www.bilibili.com/bangumi/play/ep289960?spm_id_from=333.337.0.0
[BiliBiliBangumi] ep289960: Downloading webpage
ERROR: [BiliBiliBangumi] ep289960: Unable to extract play info; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 694, in extract
  File "yt_dlp\extractor\bilibili.py", line 376, in _real_extract
  File "yt_dlp\extractor\common.py", line 1256, in _search_json
  File "yt_dlp\extractor\common.py", line 1242, in _search_regex

Closing in favor of #6701 as it is better reported


Generated regex contains \. which it turns into a path

Type: Bug
Ask it to explain [Rr][Ee][Aa][Dd][Mm][Ee](\..*)?
It explains:
[Rr][Ee][Aa][Dd][Mm][Ee]: Matches "README" in a case-insensitive manner.
(\..*)?: Matches an optional group where:
vscode-readme-auto-open (THE PATH): Matches a literal dot.
.*: Matches any character (.) zero or more times (*).
?: Makes the entire group optional.

Extension version: 0.22.2024100702
VS Code version: Code 1.94.1 (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
63.67GB (42.20GB free)

Process Argv
.

Screen Reader
no

VM
0%

Thanks, should be fixed in the next chat insiders release

asked this and the markdown turned to into a link in my question - is that expected?

We renderer the input as markdown too so in that example you would actually need to use inline code:
Ask it to explain `[Rr][Ee][Aa][Dd][Mm][Ee](\..*)?`

Otherwise [Ee](\..*) is a valid markdown link. So this is expected if you don't use the inline code
It's a little tricky because there really are cases where you want to use markdown syntax in your input , such as for fenced code blocks


chore(deps): protobuf-java dependency upgrade to the latest 3.11.1

protobuf-java dependency upgrade to the latest 3.11.1.
Background
The class path generated by the pair com.google.api:gax-grpc:1.52.0 x com.google.api.grpc:proto-google-common-protos:1.17.0 has the following linkage errors, because proto-google-common-protos has old protobuf-java dependencies. com.google.api:gax-grpc needs protobuf-java 3.10 or higher.
Linkage Error on com.google.api:gax-grpc:1.52.0 x com.google.api.grpc:proto-google-common-protos:1.17.0
Class com.google.protobuf.GeneratedMessageV3$UnusedPrivateParameter is not found (type: CLASS_NOT_FOUND)
  io.grpc.alts.internal.RpcProtocolVersions (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.StartClientHandshakeReq (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.HandshakerStatus (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.ServerHandshakeParameters (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.StartServerHandshakeReq (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.NextHandshakeMessageReq (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.AltsContext (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.Identity (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.HandshakerResult (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.Endpoint (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.HandshakerReq (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.HandshakerResp (io.grpc:grpc-alts:1.25.0)
  io.grpc.lb.v1.InitialLoadBalanceRequest (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.InitialLoadBalanceResponse (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.ClientStatsPerToken (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.Server (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.ClientStats (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.ServerList (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.LoadBalanceRequest (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.LoadBalanceResponse (io.grpc:grpc-grpclb:1.25.0)
Class com.google.protobuf.AbstractMessageLite$InternalOneOfEnum is not found (type: CLASS_NOT_FOUND)
  io.grpc.alts.internal.HandshakerReq (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.Identity (io.grpc:grpc-alts:1.25.0)
  io.grpc.lb.v1.LoadBalanceResponse (io.grpc:grpc-grpclb:1.25.0)
  io.grpc.lb.v1.LoadBalanceRequest (io.grpc:grpc-grpclb:1.25.0)
Class com.google.protobuf.TypeRegistry is not found (type: CLASS_NOT_FOUND)
  com.google.protobuf.util.JsonFormat (com.google.protobuf:protobuf-java-util:3.10.0)
(com.google.protobuf:protobuf-java:3.7.1) com.google.protobuf.Descriptors$FileDescriptor's method internalBuildGeneratedFileFrom(String[] arg1, com.google.protobuf.Descriptors$FileDescriptor[] arg2) is not found (type: SYMBOL_NOT_FOUND)
  io.grpc.alts.internal.HandshakerProto (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.TransportSecurityCommonProto (io.grpc:grpc-alts:1.25.0)
  io.grpc.alts.internal.AltsContextProto (io.grpc:grpc-alts:1.25.0)
  io.grpc.lb.v1.LoadBalancerProto (io.grpc:grpc-grpclb:1.25.0)

The presubmit check failure has been there already.

@lukesneeringer @noahdietz Would you review/merge this PR?

@vam-google I don't know how this repo is used by any of the mentioned dependencies. This repo probably shouldn't be used as I don't think it is being maintained. Would you mind taking a look?

I often see proto-google-common-protos dependency in Google-related repositories. At least the following artifacts use proto-google-common-protos:

io.grpc:grpc-protobuf:1.26.0
org.apache.beam:beam-sdks-java-io-google-cloud-platform:2.16.0
com.google.api.grpc:grpc-google-cloud-redis-v1:0.82.0

@noahdietz The status of this repo is "undefined". This means it should not be used, but it used to be used, and I used recently once because there was no alternative (to release iam protos, because those are upsed very rarely and there were no new place for them).

@suztomo @noahdietz FYI (forgot to mention you in the previous comment)

@vam-google Thank you for response. Yes, I’m familiar with BOM, with which users can solve the inconsistency. (You can forget about grpc. It happened to be the artifact that had conflict)
I feel concerned, because this widely-used artifact being unmaintained may cause a risk of diamond dependency problem in Google-related Java libraries. Would you share the reason why this repository is not maintained any more? (team change, difficult release process, etc.?)

@suztomo The artifact is maintained, but this repo is not... This repository existed solely to push the generated stuff on github, because the root-level gradle build script in this repo has the "pushing" logic in it.
The artifact proto-google-common-protos, published to the maven should be considered as a maintained artifact without a maintained public repository for it. The the code in this artifact is automatically generated, that is why not having a public repo with sources kind of makes sense.

@vam-google Thanks. It’s good to hear the artifact is maintained. The directory name “generated” was strange to me as well. But you also edited a build.gradle few months back https://github.com/googleapis/api-client-staging/pull/678/files#r363570370 .
Should I try to edit different files (this repo or google3?) to upgrade the dependencies of proto-google-common-protos for a future release?


Fix link to worflows in README

Changes made in Readme
Before
(./github/workflows):
After
(.github/workflows):

Thank you!

If you would like to grab another issue, this one is also beginner friendly: https://github.com/yvesgurcan/web-midi-player/issues/46


Sending media files

Has anyone implemented sending media files

Has anyone implemented sending media files

You Can reference Issue :
#126

@tiwarishrijan That code is not clear can you please put complete code


Update _index.md

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Remember to delete this note before submitting your pull request.
For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For pull requests on Chinese localization, set Base Branch to release-1.14
For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
If you need Help on editing and submitting pull requests, visit:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
If you need Help on choosing which branch to use, visit:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/assign @zhangxiaoyu-zidif

/cc @jimangel

Page preview:
https://deploy-preview-15895--kubernetes-io-master-staging.netlify.com/docs/setup/

/assign @zacharysarah

hi @jaypipes, could you please review? thanks!

/assign @zacharysarah

hi @jaypipes, could you please review? thanks!

Does Platform9 Managed Kubernetes allow the customer to completely self-manage the control plane? If not, then I don't think the "Custom" options are appropriate, since those are for entirely self-managed systems.

@jaypipes thanks for the comments, perhaps we don't understand the definition of custom, here is an explanation of what we do

W.r.t Custom (Cloud, Baremetal, VMs: Platform9 Managed Kubernetes supports all of these infrastructures)

Control plane is deployed into the customer's infrastructure (their Cloud environment, Virtual Machines or on Bare metal servers)
Extensive configuration is allowed for the control plane (e.g changing authentication provider, changing the number of pods etc.)
Customers are able to out of band management like backup or monitoring (in addition to what Platform9 Managed Kubernetes provides)
Platform9 Managed Kubernetes provides the necessary monitoring like health checks, performance monitoring

As you can see we do allow customer to change the control plane and hence looking to add ourselves to the Custom category. Let us know if we misunderstood that.

Fully agreed with @jaypipes' feedback.
@avigailof Please incorporate feedback as given.

Fair enough, Avigail. Works for me. :)

phew.. :) Thanks, Jay!!

@jaypipes If you're OK with this as is, please feel free to give an /lgtm.

/lgtm
/approve


Expose a hook to send a message as soon as a Kernel WebSocket is created

We are building an extension which using jupyter extension to connect remote kernel. Now we need to send some extra comm_msg to let server get more status to run extra task.
Could jupyter extension expose an API which can send some extra message actively after connecting to kernel?
Some further thoughts. We can expose a callback hook that fires every time a websocket message is returned. This allows the caller to actively send specific information through the received message.
Seems extension currently supports these capabilities. Could you consider exposing them?
### Tasks

API has been provided and confirmed to be working


dead link to reference

the link to "Efficient Contextual Bandits in Non-stationary Worlds" is dead

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

ID: 99720662-e492-89fe-3c1a-0531aabd19e6
Version Independent ID: 92b17aee-7355-13c4-08cc-c9e937ffc90d
Content: Reinforcement Learning - Personalizer - Azure Cognitive Services
Content Source: articles/cognitive-services/personalizer/concepts-reinforcement-learning.md
Service: cognitive-services
Sub-service: personalizer
GitHub Login: @edjez
Microsoft Alias: edjez

@wmpauli Thanks for the feedback. We are investigating into the issue and will update you shortly.

@wmpauli The links perfectly fine for me. Could you please check again?

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Move documentation before release tag and deprecation

Issue #, if available:
Internal JS-5074
Currently the documentation is read as part of deprecation
Example: https://github.com/aws/aws-sdk-js-v3/blob/a967bfc08aac5714420bef63c55832da49492d4a/clients/client-qconnect/src/commands/QueryAssistantCommand.ts#L34-L40
This will move the documentation before release tag, so that it's read separately and not as deprecation.
TSDoc references:

https://tsdoc.org/pages/tags/public/
https://tsdoc.org/pages/tags/deprecated/

Description of changes:
Move documentation before release tag and deprecation.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codegen PR in sts for reference: https://github.com/aws/aws-sdk-js-v3/pull/5906
The final PR to be merged https://github.com/aws/aws-sdk-js-v3/pull/5905


RFC: Public API

The goal of the document is to provide context to public api initiative.
Context and goals:
Datagrok currently has a server api and js api, which are not intended for external use. However, there are client needs for integration with datagrok. For example, ability to upload dataframes and set up dashboards programmatically.
We aim to create a public REST API and a wrapper in python so clients are able to include datagrok in their data pipelines.
Use case 1: pipeline-generated dashboards
Tim has a pandas dataframe that he wants to upload to Datagrok, apply some visualization, and share with other users as part of the data pipeline. With python wrapper he will be able to upload the dataframe to Datagrok with his favorite configuration previously exported in “.layout” format.
Use case 2: cross-language scripts
Steve has written a Datagrok R script, and shared it with the users so it can be interactively used via Datagrok. Now, he wants to be able to easily call that script from his Python code.
Use case 3: parameterized queries
Ed has created a connection to the database, and wrote a number of pretty complex parameterized queries. He wants to let data scientists make the same queries from Python.
Use case 4: files
Ability to access and manipulate files in the file shares
Authentication
Authentication will use API key taken from user summary (eg http://localhost:8889/u/admin/summary)
This key will be passed in the Authorization header as a Bearer token.
Routing
All public requests will be going through /public/v1/* endpoints so they can be easily distinguished and versioned.
##Work with files
Tables will use namespaced names for identification. Example can be “project.dashboard.table”
For files we should pass a connection identifier and path to a file. Example can be “System.DemoFiles/chem%2Fsmiles.csv”
In v1, we support single table download/upload, so it can be done with uploading a single csv/parquet file. In future we can extend this with downloading/uploading in zip
When tables are uploaded, a dashboard can be created as a set of tables and a layout file.
Functions
To enable invoking functions, the platform should be able to identify a function by its namespaced name. As for passing arguments, we plan to support primitive data types as well as columns/data frames through their identifiers, matching the upload/download identifiers
OpenAPI
We will expose API with openAPI specification so it can be imported easily to clients projects with codegen.
Planned API v1
HTTP GET /public/v1/tables/{name} - download table by namespaced `name`
HTTP GET /public/v1/tables/{connector}/{path} - download table from `connector` located in `path`
HTTP POST /public/v1/tables/{name} - upload table as csv/parquet body and save it to `name`,
HTTP POST /public/v1/tables/{connector}/{path} - upload table as csv/parquet body and save it to `connector` under `path`,
HTTP POST /public/v1/tables/share/{id}/{group}?mode="view/edit" - share table `id` with `group` and give permission to view/edit based on mode.

HTTP POST /public/v1/dashboards/{name}/{table_id1},{table_id2},{...} - create dashboard `name` that has tables `table_1`, `table_2`, .... Layout can be uploaded in body.

HTTP POST /public/v1/call/{name} - call function `name` with arguments passed in JSON key-value body.

HTTP GET /public/v1/files/{connector}/{path} - download file from `connector` located in `path`
HTTP POST /public/v1/files/{connector}/{path} - upload file to `connector` under  `path`

Python wrapper example
import datagrok as dg
from sklearn.datasets import load_titanic

dg.token = 'Bearer …'
dg.url = 'http://localhost:8082'

### === FILES ===

# identify everything with nqName
# if we do python wrapper, result probably should be pandas
df = dg.download_table('System:DemoFiles/chem/smiles.csv')
# # or
# df = dg.download_table('clinicalcase.clindemofiles2/tv')

# some processing
df[0, 'Severity'] = 'High'

# Upload tables to either personal or public namespace
# Can also be saved to connector
df_id = dg.upload_table(df, 'smiles-new')
titanic_id = dg.upload_table(load_titanic(), 'System:DemoFiles/titanic.csv')

# Create a dashboard from dataframes with a given layout
dashboard_id = dg.upload_dashboard([df_id, titanic_id], prefix_name='core:api_demo',
                        layout='pretty.layout')

# sharing with usergroup or users, specifying namespace if needed
dg.share(dashboard_id, 'Researchers', access='edit')
dg.share(dashboard_id, 'core:Kamelichev', access='view')

### === CALLS ===

# params are serialized as json
dg.call('UsageAnalysis:TestCount', {
 'date': '21-05-2024'
})

# Column, dataframe, column list can be passed as arguments
# We can return dataframes and columns from calls
extracted_df = dg.call('core:ExtractColumns', {
 'df': df_id,
 'columns': ['USUBJID', 'AGE']
})
calculated_column = dg.call('core:ExtractValue', {
 'df': titanic_id,
 'column': 'AGE',
 'function': 'core:Abs'
})

'''
# Some fancy wrappers could also be done
proj = dg.project([df], layout='layouts/pretty_one.layout')
proj.add(datasets.load_titanic())
proj.addViewer(DG.VIEWER.BAR_CHART, {
 "valueColumnName": "SUBJID",
 "valueAggrType": "count",
 "barSortType": "by value",
 "barSortOrder": "desc",
 "splitColumnName": "DTHFL"
})
'''

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-15771

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16189

Is available in 1.19


[chip-tool] The ble-thread pairing is using a hardcoded NetworkID when commissioning

Problem
When doing ble-thread commissioning using the chip-tool the tool uses a default (hardcoded) NetworkID. This causes problems when trying to associate with a Thread network which does not have the Network Extended PAN-ID set to this default value.
This is hardcoded in examples/chip-tool/commands/pairing/PairingCommand.cpp as kTemporaryThreadNetworkId which is set to 0x0123456789ABCDEF. When commissioning a device onto Thread, the operationalDataset contains a TLV for the Network Extended PAN-ID which should be used.
Proposed Solution
In the EnableNetwork() method, one should make use of the operationalDataset and the TLV set during the addition of the actual network.

Doesn't appear to be the case anymore?


PR: for airbnb_alt

need to remove file.json so that checker creates its own file.json in-container.

need to remove file.json so that checker creates its own file.json in-container.


Is there any plan to develop a  cpp client sdk, ex turms-client-cpp?

Which kinds of applications you develop need a C++-based Turms client SDK?
If we think it's a reasonable use case, we can develop one next month.

Which kinds of applications you develop need a C++-based Turms client SDK?
If we think it's a reasonable use case, we can develop one next month.

Which kinds of applications you develop need a C++-based Turms client SDK?
If we think it's a reasonable use case, we can develop one next month.

i am planning to build an IM  client based on duilib, when i checked your repository, i found there is no cpp client sdk.

It's reasonable, and I will publish an SDK for C++ next month.

thanks for your great work!!!


exercises(queen-attack): add stub

Closes #220
The error type is included only with InitializationFailure, to give minimal API between this and tests.

Sure, I only got the info about the pause and blog post after the PR was made.
Thanks for what's already in the track, got me on my feet really quick.


feat: add metadata impl

original bag2 info
❯ ros2 bag info /home/daisuke/rosbag2_2022_03_10-09_05_13

Files:             rosbag2_2022_03_10-09_05_13_0.db3
Bag size:          26.6 KiB
Storage id:        sqlite3
Duration:          5.422s
Start:             Mar 10 2022 09:05:13.710<PHONE_NUMBER>.710)
End:               Mar 10 2022 09:05:19.132<PHONE_NUMBER>.132)
Messages:          46
Topic information: Topic: /chatter2 | Type: std_msgs/msg/String | Count: 6 | Serialization Format: cdr
                   Topic: /chatter | Type: std_msgs/msg/String | Count: 6 | Serialization Format: cdr
                   Topic: /parameter_events | Type: rcl_interfaces/msg/ParameterEvent | Count: 0 | Serialization Format: cdr
                   Topic: /rosout | Type: rcl_interfaces/msg/Log | Count: 34 | Serialization Format: cdr

mcap info
❯ ros2 bag info /home/daisuke/demo.mcap -s mcap

Files:             /home/daisuke/demo.mcap
Bag size:          14.7 KiB
Storage id:        mcap
Duration:          5.422s
Start:             Mar 10 2022 09:05:13.710<PHONE_NUMBER>.710)
End:               Mar 10 2022 09:05:19.132<PHONE_NUMBER>.132)
Messages:          46
Topic information: Topic: /chatter2 | Type: std_msgs/msg/String | Count: 6 | Serialization Format: mcap
                   Topic: /chatter | Type: std_msgs/msg/String | Count: 6 | Serialization Format: mcap
                   Topic: /parameter_events | Type: rcl_interfaces/msg/ParameterEvent | Count: 0 | Serialization Format: mcap
                   Topic: /rosout | Type: rcl_interfaces/msg/Log | Count: 34 | Serialization Format: mcap

Looks good! I found one issue, I can fix it in a follow-up PR.


Can you add zip artefacts for 5.6.8 version

Issue description
I want install sentinl for Kibana version 5.6.8, but no zip archive with plugin for this version on github.
But I can`t find assets for this version. Although a few days ago I downloaded them

https://github.com/sirensolutions/sentinl/releases/download/tag-5.6.2/sentinl-v5.6.8.zip

Thank you!

Added https://github.com/sirensolutions/sentinl/releases/tag/tag-5.6.2

Sergij, thank you very much!


Integrate Toasts

Integrate Toasts on the application to provide user feedback. This would be specially great for when the clipboard's image is captured.
Grab inspo from: https://ui.shadcn.com/docs/components/toast
Context: When the user tries to use an asset that isn't an image from their clipboard, an error is printed to the console from:
https://github.com/ekqt/screenshot/blob/main/src/utils/clipboard.ts
Improve the experience by triggering a success toast instead when the image has been received successfully and a failure toast when no image type has been found

Hi, I have started to check out some solutions to this

I'll assign you to this one then! @alefDev-prog


Widget assets can be missing in some usecase

Encountered issue with SmartMediaField usage on a DjangoCMS plugin form which define an additional css asset in Media.css meta class attribute.
It seems to override the asset definition previously done from widget ClearableFileInputButton and so the image file input is almost broken.
A proper workaround need to be found and documented.

Didn't find anything from admin-style to djangocms that would override the widget medias.
I think this report is almost a mistake resulting from situation as described from #11, keeping it opened until previously cited issue is closed.

Confirmed as a mistaken report, closed issue #11 should help to avoid it again.


Update virtual-machines-common-ppg-overview.md

Typo

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


Wrong report title for expensify card transactions

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction ( don't have expensify card transactions)
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1709735584075159
Action Performed:

Go to a workspace chat as employee
Create expensify card transaction report and submit to approver
Sign in to approver accoun and open the expense report

Expected Result:
Should be "employee email address spent $x.xx"
Actual Result:
Shows "approver email address spent $x.xx"
reportID:<PHONE_NUMBER>469889
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

@grgia have you had a change to look at this?

Closing, should be good now!


Add support edit EXIF description tag

Please add support edit EXIF description tag.

Probably going to support these fields, to de/select when editing:

Exif ImageDescription (0x010e)
Exif UserComment (0x9286)
IPTC Caption-Abstract (120)
XMP dc:description

I changed my mind. It will write:

Exif ImageDescription (0x010e)
XMP dc:description
IPTC Caption-Abstract (120), only if there is already other IPTC metadata

It doesn't write:

Exif UserComment (0x9286)


preconfigured config.json file

https://github.com/iiCe89/PokemonGo-bot-config i upload pre configured config.json file for anybody unsure when using pika-bot application i hope this helps - https://github.com/iiCe89/PokemonGo-bot-config
Issue without proper information won't be answered
Expected Behavior
Actual Behavior
Steps to Reproduce
Information

OS
Git commit ( to get git commit run git log -1 --format="%H")
App's logs

Don't know if coincidence..... but since using your config.json I'm getting this in my log..
listLogs
12:22:58
Setting start location.
12:22:58
Coordinates found in passed in location, not geocoding.
12:22:58
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:22:58
Now at (34.0432108, -118.2675059, 0)
12:22:58
Login procedure started.
12:23:00
Login successful.
12:23:10
Starting bot...
12:23:12
Received level up reward: []
12:23:12
Next egg incubates in 0.54 km
12:23:29
Server is throttling, reconnecting in 30 seconds
12:23:59
Setting start location.
12:23:59
Coordinates found in passed in location, not geocoding.
12:23:59
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:23:59
Now at (34.0432108, -118.2675059, 0)
12:23:59
Login procedure started.
12:24:01
Login successful.
12:24:12
Starting bot...
12:24:13
Received level up reward: []
12:24:32
Server is throttling, reconnecting in 30 seconds
12:25:02
Setting start location.
12:25:02
Coordinates found in passed in location, not geocoding.
12:25:02
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:25:02
Now at (34.0432108, -118.2675059, 0)
12:25:02
Login procedure started.
12:25:03
Login successful.
12:25:13
Starting bot...
12:25:15
Received level up reward: []
12:25:34
Server is throttling, reconnecting in 30 seconds
12:26:04
Setting start location.
12:26:04
Coordinates found in passed in location, not geocoding.
12:26:04
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:26:04
Now at (34.0432108, -118.2675059, 0)
12:26:04
Login procedure started.
12:26:06
Login successful.
12:26:15
Starting bot...
12:26:17
Received level up reward: []
12:26:35
Server is throttling, reconnecting in 30 seconds
12:27:05
Setting start location.
12:27:05
Coordinates found in passed in location, not geocoding.
12:27:05
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:27:05
Now at (34.0432108, -118.2675059, 0)
12:27:05
Login procedure started.
12:27:07
Login successful.
12:27:16
Starting bot...
12:27:19
Received level up reward: []
12:27:35
Server is throttling, reconnecting in 30 seconds
12:28:05
Setting start location.
12:28:05
Coordinates found in passed in location, not geocoding.
12:28:05
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:28:05
Now at (34.0432108, -118.2675059, 0)
12:28:05
Login procedure started.
12:28:08
Login successful.
12:28:17
Starting bot...
12:28:19
Received level up reward: []
12:28:36
Server is throttling, reconnecting in 30 seconds
12:29:06
Setting start location.
12:29:06
Coordinates found in passed in location, not geocoding.
12:29:06
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:29:06
Now at (34.0432108, -118.2675059, 0)
12:29:06
Login procedure started.
12:29:08
Login successful.
12:29:18
Starting bot...
12:29:20
Received level up reward: []
12:29:38
Server is throttling, reconnecting in 30 seconds
12:30:08
Setting start location.
12:30:08
Coordinates found in passed in location, not geocoding.
12:30:08
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:30:08
Now at (34.0432108, -118.2675059, 0)
12:30:08
Login procedure started.
12:30:09
Login successful.
12:30:19
Starting bot...
12:30:21
Received level up reward: []
12:30:39
Server is throttling, reconnecting in 30 seconds
12:31:09
Setting start location.
12:31:09
Coordinates found in passed in location, not geocoding.
12:31:09
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:31:09
Now at (34.0432108, -118.2675059, 0)
12:31:09
Login procedure started.
12:31:11
Login successful.
12:31:22
Starting bot...
12:31:23
Received level up reward: []
12:31:42
Server is throttling, reconnecting in 30 seconds
12:32:12
Setting start location.
12:32:12
Coordinates found in passed in location, not geocoding.
12:32:12
Location found: 34.0432108, -118.2675059 (34.0432108, -118.2675059, 0.0)
12:32:12
Now at (34.0432108, -118.2675059, 0)
12:32:12
Login procedure started.
12:32:14
Login successful.
12:32:24
Starting bot...
12:32:26
Received level up reward: []
12:32:26
Next egg incubates in 0.54 km

Do you think it's a ban?

seems to be working now :)

Can we get the config to do the following?

Keep the highest IV pokemon when there are duplicates, but transfer this highest IV too if a higher IV pokemon is found. Isn't IV a better setting to be transferring as opposed to CP? I mean some Pokemon are low CP but high IV. And how does this work with regards to Magicarp too.. if we want to evolve to a Gyarados, Magicarps are always under 350 CP?

Also what is the current evolve setting based on? Under what conditions will it evolve the Pokemon? And what if there are duplicates? Is it evolving the best IV out of them all?

will work on Tommorow for you

its just a balancing game because in order to clear pokemon you have to log into app it cant be done in game so this can cause pokémon to fill up super fast

also any future issues post on my repo as i will get them faster as i get notified 👍

@iiCe89 please notice the pen at the top right of your comments, that's an edit button.

@Outpox apologies i was using Mobile app that didnt give me the option :)

I know your pain, I switch to the desktop version on my phone since the mobile is limited in functionalities >.>


How to increment version numbers

We should dicuss how we want to increment the version numbers for each package. A discussion has already been started below:
Andy:

Is there anything to be gained by having all the container-api-* packages on the same version (i.e. put api-browser up to 0.0.3 to match the others)?

Ben:

I think that should be the case for major/minor changes, but im not sure for patch changes (although we aren't really following semantic versioning at the minute). I think in future, we should be able to have different patch versions for each api (bug fixes etc) but them all be on the same minor version (i.e. all are on v1.1.*). Might be easier to have a more general 'API version' though, were any change increments the patch number in all packages? @ColinEberhardt do you have a preference?

As per discussions offline, we will continue with independent versioning of the packages, unless we change the major version of the packages.


Incorrect treatment of object subtypes (cast & intersection with union typed properties)

Flow version: v0.111.1
Expected behavior

{ x : number } is a subtype of { x : number | string }
The intersection thereof is commutative and equivalent to { x : number }.

Actual behavior

{ x : number } is not a subtype of { x: number | string }
The intersection thereof is not commutative and is not always equivalent to { x: number }.

Link to Try-Flow or Github repo: Try-Flow
type XN = { x: number };
type XNS = { x: number | string };

let n = (5 : number);
(n : number | string); // Correctly doesn't error

({ x: 5 } : XNS); // Correctly doesn't error

let xn = ({ x: 5 } : XN);
(xn : XNS); // Shouldn't errror but does

type XN_XNS = XN & XNS;
type XNS_XN = XNS & XN;

({ x: 5 } : XN_XNS); // Correctly doesn't error
({ x: 5 } : XNS_XN); // Shouldn't errror but does

@tjjfvi that's because of type variance.
Flow doesn't know how xn will be used, for example let's assume you'll then call the following function:
function fn(xn: XN) {
  xn.x = 'hello';
}

This will mutate xn, so it's not safe because xn might be used at other places as XN...
Here, you need to specify the usage as ReadOnly like so: try flow
type XN = { x: number };
type XNS = { x: number | string };

let n = (5 : number);
(n : number | string); // Correctly doesn't error

({ x: 5 } : XNS); // Correctly doesn't error

let xn = ({ x: 5 } : XN);
(xn : $ReadOnly<XNS>); // Shouldn't errror but does

type XN_XNS = XN & XNS;
type XNS_XN = XNS & XN;

({ x: 5 } : XN_XNS); // Correctly doesn't error
({ x: 5 } : $ReadOnly<XNS_XN>); // Shouldn't errror but does

The response above is correct


Check on py-limited-api config is too strict

I am trying to build a non-purelib py3-none-linux_x86_64 wheel. But I get an error. The check on py-limited-api config seems to be too strict.
There are many more possible values for py-limited-api (e.g. cp32dmu according to the documentation). I suggest loosening or removing the check.
Steps to reproduce
$ cat pyproject.toml
[project]
name = "example"
version = "0.1.0"
[build-system]
requires = ["pdm-backend"]
build-backend = "pdm.backend"
[tool.pdm.build]
is-purelib = false

$ pdm build --config-setting="--python-tag=py3" --config-setting="--py-limited-api=none"

Actual behavior
Building sdist...
Built sdist at /tmp/pdm-backend/dist/example-0.1.0.tar.gz
Building wheel...
See /tmp/pdm-build-vp8q4btl.log for detailed debug log.
[BuildError]: Build backend raised error: Showing the last 10 lines of the build output:
    self._write_wheel_file(f, is_purelib=self.config.build_config.is_purelib)
  File "/tmp/pdm-build-env-mnmydywr-shared/lib/python3.10/site-packages/pdm/backend/wheel.py", line 264, in _write_wheel_file
    is_purelib=is_purelib, tag=self.tag, version=version
  File "/tmp/pdm-build-env-mnmydywr-shared/lib/python3.10/site-packages/pdm/backend/wheel.py", line 157, in tag
    self.__tag = self._get_tag()
  File "/tmp/pdm-build-env-mnmydywr-shared/lib/python3.10/site-packages/pdm/backend/wheel.py", line 161, in _get_tag
    impl, abi, platform = self._get_platform_tags()
  File "/tmp/pdm-build-env-mnmydywr-shared/lib/python3.10/site-packages/pdm/backend/wheel.py", line 88, in _get_platform_tags
    raise ValueError(
ValueError: py-limited-api must match 'cp3\d{1,2}'
Add '-v' to see the detailed traceback

Expected behavior
Building sdist...
Built sdist at /tmp/pdm-backend/dist/example-0.1.0.tar.gz
Building wheel...
Built wheel at /tmp/pdm-backend/dist/example-0.1.0-py3-none-linux_x86_64.whl

Environment Information
$ pdm --version
PDM, version 2.4.9

$ pdm info --env
{
  "implementation_name": "cpython",
  "implementation_version": "3.10.10",
  "os_name": "posix",
  "platform_machine": "x86_64",
  "platform_release": "6.2.2-arch1-1",
  "platform_system": "Linux",
  "platform_version": "#1 SMP PREEMPT_DYNAMIC Fri, 03 Mar 2023 15:58:31 +0000",
  "python_full_version": "3.10.10",
  "platform_python_implementation": "CPython",
  "python_version": "3.10",
  "sys_platform": "linux"
}

SGTM, would you like to send a PR?

I will send a PR to remove the check.


Adjust wmware provider page to new insecure feture

a. Add the new insecure option to the vmware provider page
b. add a CA cert input as text (like in ovirt) for the vmware provider page

Refs:
https://issues.redhat.com/browse/MTV-468
https://issues.redhat.com/browse/MTV-469

Refs: https://issues.redhat.com/browse/MTV-468 https://issues.redhat.com/browse/MTV-469

See #191 that correlated to MTV-468


Map patient discharge

In this issue I found out that I couldn't combine all the patient data in one record. I have to split it based on which "event" a variable belongs to. I changed the capacity codebook class so it can easily do that

Pull Request Test Coverage Report for Build 874680075

33 of 36 (91.67%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+9.1%) to 55.357%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

capacity_mapping/mapping.py
12
15
80.0%

Files with Coverage Reduction
New Missed Lines
%

capacity_mapping/mapping.py
1
46.15%

Totals

Change from base Build 874658914:
9.1%

Covered Lines:
89

Relevant Lines:
142

💛  - Coveralls