pypi license reported as Modified BSD License when it should be Proprietary

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] badge-maker NPM package

:beetle: The URL https://img.shields.io/pypi/l/nrfutil.svg gives Modified BSD License but:

PyPi reports Other/Proprietary License
The license itself is clearly not FOSS

:link:
https://img.shields.io/pypi/l/nrfutil.svg

Any help is much appreciated :)

Hi! Thanks for the question. I suspect that’s coming from the legacy license field:
https://github.com/NordicSemiconductor/pc-nrfutil/blob/master/setup.py#L140

Thank you very much for the fast response :)
I've filed a pull request to correct this here: https://github.com/NordicSemiconductor/pc-nrfutil/pull/325

Ok, pull request successful, but I am still currently seeing the incorrect badge.
See https://github.com/NordicSemiconductor/pc-nrfutil/blob/a0034f28359deda020632d64d71d8e15938a4082/setup.py#L140
Is this just a matter of waiting a day or so?

It needs to be published to PyPI as well.

Ah, gotcha. Thank you :)


TryUpdateModelAsync not working in ASP․NET Core 3.1

Describe the bug
The TryUpdateModelAsync not working as expected in ASP․NET Core 3.1.
To Reproduce

Setup demo project
git clone https://github.com/doggy8088/TryUpdateModelAsyncProblem.git
cd TryUpdateModelAsyncProblem
dotnet run

Send HTTP request to the demo action
curl --location --request POST 'https://localhost:5001/WeatherForecast' --header 'Content-Type: application/json' --data-raw '{"Date": "2019-12-01", "TemperatureC": 1, "Summary": "N/A"}' -k -D -

Expected result:
HTTP/2 201
date: Sat, 14 Dec 2019 11:19:38 GMT
content-type: application/json; charset=utf-8
location: https://localhost:5001/WeatherForecast
server: Kestrel

{"date":"2019-12-01T00:00:00+08:00","temperatureC":1,"temperatureF":33,"summary":"N/A"}

Actual result: ( The TryUpdateModelAsync is not working. )
HTTP/2 201
date: Sat, 14 Dec 2019 11:19:38 GMT
content-type: application/json; charset=utf-8
location: https://localhost:5001/WeatherForecast
server: Kestrel

{"date":"2019-12-14T00:00:00+08:00","temperatureC":100,"temperatureF":211,"summary":""}

Further technical details

ASP.NET Core version: 3.1
Include the output of dotnet --info: See below
The IDE (VS / VS Code/ VS4Mac) you're running on, and it's version: VSCode 1.39.2

.NET Core SDK (reflecting any global.json):
 Version:   3.1.100
 Commit:    cd82f021f4

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /usr/share/dotnet/sdk/3.1.100/

Host (useful for support):
  Version: 3.1.0
  Commit:  157910edee

.NET Core SDKs installed:
  2.1.802 [/usr/share/dotnet/sdk]
  3.0.100 [/usr/share/dotnet/sdk]
  3.1.100 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.14 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.14 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.14 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

It looks like ASP․NET Core missing a JsonValueProviderFactory implementation.

If I use the following cURL request, then it works fine. It use application/x-www-form-urlencoded content-type in the HTTP request.
curl --location --request POST 'https://localhost:5001/WeatherForecast' --header 'Content-Type: application/x-www-form-urlencoded' --data-raw 'Date=2019-12-01&TemperatureC=1&Summary=N/A' -k -D -

Thanks for contacting us. @javiercn can you please look into this? Thanks!

Hi @doggy8088
I’ve tried to understand this bug.
As mentioned in the attached bug and post.
It is by design we aren’t  supporting application/Json content type for POST.

TryUpdateModelAsync is using value providers and checking can we read from query or HasFormContentType

[Frombody] using input formaters using JsonSerializer.DeserializeAsync binding the model.
Framework supported media types are application/json , text/json , and text/plain.

With these points I’m feeling it isn’t a bug...
Correct me if am wrong..
//cc @dougbu @mkArtakMSFT @pranavkm

@kishanAnem It works in ASP․NET MVC 5. So I expected it should works in ASP․NET Core.

@doggy8088 yeah it’s right working MVC 5. In Asp.net community standup I think @DamianEdwards said “ removed that feature consciously”.

Thanks @kishanAnem for the investigation. This is not a feature ASP.NET Core MVC has. https://github.com/aspnet/Mvc/issues/5659#issuecomment-270717629 goes in to some details as to why along with possible solutions to this.


Step down as maintainer

I will be stepping down as maintainer for this repo.
@arjungarg07 afaik from different discussions you also cannot longer work on this repo
@magicmatatjahu I believe you also have different responsibilities

My proposal:

Rename this but to "Looking for new maintainers"
Pin this issue so it is visible to anyone looking into Issues tab
Add note in readme that we are looking for maintainers
Create a discussion in community that this project will be archived in 1 month unless someone is interested to take this over and maintain forward

must have at least 2 new maintainers
maintainers should have some company support or at least provide a proof that they use the project or have a use case for it, therefore they have interest in maintaining the project long term. Basically make sure that we do not get just students volunteers that would treat this project as path to TSC. We basically need experience folks with use cases that can drive project forward independently

Ask Thulie to share discussion on AsyncAPI social media and newsletter so potential users of cupid know about it. At the moment we are getting only 24 weekly downloads

After a month from publishing the discussion in social media, if there is noone to take over, we will archive repo and move to https://github.com/asyncapi-archived-repos

Thoughts?

Hey @derberg, Thanks for creating this. Due to some circumstances I won't be able to contribute to the project. Apologies for the delay in response from my side 🙏🏽
As a result, I would be stepping down as a maintainer and hope for someone to take this project forward for the good of the community.

@arjungarg07 thanks for clarification. So now let's execute the plan and make sure we did everything possible to keep the project alive.

I still believe in what it can offer in the tooling ecosystem when working with multiple AsyncAPI documents

just to be clear, nobody says the tools is not useful - it is just not maintained and need new maintainers or we should archive it. Npm package is still there if somebody wants to use current version.
@jonaslagoni didn't you just describe a completely new project? also parser rewrite needs to be done here. The only sense to preserve this repo for your purpose is maybe the name and already existing stars - is that what you are looking for?

Until v1, I want to enforce 0 reviews for maintainers to speed up development time. Once v1 is reached we switch over to a similar contribution guide as Modelina currently has: https://github.com/asyncapi/modelina/blob/master/docs/champions.md#merging-a-pr (don't get the wrong idea, the top priority is onboarding contributors and maintainers in the long run, but staying agile in the beginning)

sounds to me like you probably want to start new project on personal account, like with EDAVisualizer and then donate once ready?

@derberg it's a complete rewrite of the project, yes, but it does not overwrite what the library currently offers nor its purpose. So re-creating it completely makes no sense to me 🤔

sounds to me like you probably want to start new project on personal account, like with EDAVisualizer and then donate once ready?

Why? 🤔

Why? 🤔

you mentioned 0 reviews for maintainers - so basically one maintainer, cause why would 1 maintainer agree that the other one push to master without review - at least that is how I understand it 🤷🏼
anyway, in the end it is up to maintainers to decide who they run stuff, if they want PR approval before merge or not. Maintainers manage branch protection, so maintainers decide if codeowner PR approval is required or not. We're not gonna tell maintainers how to run things, we can only educate on best practices.

@jonaslagoni so before we start executing the plan, I understand I can mention you there already as one of volunteers, or will you do it under the open discussion?

you mentioned 0 reviews for maintainers - so basically one maintainer, cause why would 1 maintainer agree that the other one push to master without review - at least that is how I understand it 🤷🏼
anyway, in the end it is up to maintainers to decide who they run stuff, if they want PR approval before merge or not. Maintainers manage branch protection, so maintainers decide if codeowner PR approval is required or not. We're not gonna tell maintainers how to run things, we can only educate on best practices.

Its not gonna be a solo show, but once the roadmap is laid with however many maintainers there are, it should be easier for the maintainers to evolve the library so early in its life.
Important changes, etc, will of course need to be discussed first.

@jonaslagoni so before we start executing the plan, I understand I can mention you there already as one of volunteers, or will you do it under the open discussion?

What open discussion? 🤔 But yea, if no one else have a strong desire 🙂

I mean this part of plan

Create a discussion in community that this project will be archived in 1 month unless someone is interested to take this over and maintain forward

do you want to be already mentioned there as one of maintainers?

Up to you 😄

discussion created: https://github.com/orgs/asyncapi/discussions/1074
I also asked @thulieblack for social media share

doesn't look like anyone can pick it up. Will proceed with archiving

done - more in https://github.com/orgs/asyncapi/discussions/1074


Auto generate sitemap

What is the URL of the generated sitemap? I can add it to the webmaster console.

It will be cockroachlabs.com/docs/sitemap.xml once @jseldess pushes the new build up.

Pushed new build to dreamhost server. sitemap.xml is there now.
http://www.cockroachlabs.com/docs/sitemap.xml

Google's parser complains about the use of relative urls in the sitemap; looks like these need to be changed to absolute.

I think we can add some options to our _config.yml to have it do that: https://github.com/jekyll/jekyll-sitemap/blob/master/lib/sitemap.xml#L3.

Yep, I think this is fixed by adding url: http://cockroachlabs.com to _config.yml. Please take a look at PR #75.

@bdarnell, just pushed back up to dreamhost. sitemap.xml now has absolute urls. Can you check again?

OK, submitted the new sitemap and it looks like it's working. We should start to see some results later today.

Nice. Results are already better. Thanks, Ben.
On Fri, Feb 26, 2016 at 2:31 PM, Ben Darnell<EMAIL_ADDRESS>wrote:

OK, submitted the new sitemap and it looks like it's working. We should
start to see some results later today.
—
Reply to this email directly or view it on GitHub
https://github.com/cockroachdb/docs/pull/73#issuecomment-189444781.


🚀 [Feature Request] - Adding hover effects with linkedIn urls over the team section

Is your feature request related to a problem ? Please describe. ✍
There is no way to reach the creative team of the website. This gives more opportunities and reach to the team!
Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Step 1: Adding hover effects with the LinkedIn URL of the respective team member.

Additional context or screenshots

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

We need a grabtern community page... as of now we hv a section will move to this page.. if you are up for desinging it lemme know.

Sure, I can


Remove LAST_NAMES env variable in docker-compose.yml

Remove LAST_NAMES in docker-compose.yml

Issue was fixed in PR#3


Why put closed connection into the pool in NewCustom

When err occurs, redis-client is closed, why still put those clients into the pool
if err != nil {
for _, client = range pool {
client.Close()
}
pool = pool[0:]
break
}
Is that you want to return an empty pool, should the code be as below
pool = pool[:0]

Great catch, thanks!


Wrapped VST3s not showing up in Ableton Live

Tested on macOS Monterey 12.6.1 with a 2020 M1 Silicon MacBook Pro using Ableton Live 11.2.
Wrapped VST3 plugins are being scanned, but then do not show up in Live's VST3 plugin list.
If you replace them with the real VST3 versions, they show up.
Put the wrapped version back in place, and they will vanish from the plugin list again.
Tested with multiple u-he Plugins, same for all of them.
The same wrapped VST3s show up and load without problems in Bitwig 4.4, Reaper and Cubase 12.

I've tried to reproduce this with the plugin you've mentioned, and it looks like it is a simple naming issue. The wrapper binary and the CLAP binary do really need the exact same filename stem.
I will add a feature to display a real error when the underlaying CLAP is not being found at all, so it gets more obvious instead of just returning a nullptr.
Additionally, Ableton Live seems not to follow the symlinks the VST3 SDK does create. All other hosts do that.
To test this, I removed the symlinks and copied the actual binary into the VST3 folder and Ableton Live then scans and opens the plugins.
So, this is more an issue with Ableton Live and the way the SDK works. Nevertheless, I will add some better ways to debug this.

Very happy to say that it's now working, Live 11 is recognizing the  wrapped VST3s. Tested on M1 Sonoma.


The difference between the paper and the implementation in R-MVSNet

@YoYo000
Hello. Let me ask a few questions to clarify on the differences between your R-MVSNet paper and the implementation of this repository.
I know that the following points were mentioned in Changelog

Network change: enable scale and center in batch normalization
Network change: replace UniNet with 2D UNet
Network change: use group normalization in R-MVSNet

I saw that these changes are differences between your paper and the implementation.
Now, I have three questions.

The order of the convolutional layer and GRU in the cost regularization seems to be different between the paper and the implementation. Was the cost regularization described in the paper used in the experiments?

If the one in the paper was used, I am uncomfortable with the fact that Softmax's input is the output (-1 to 1) of the last GRU cell through tanh. This is because many classification networks do not apply activation to limit the value range before Softmax's input. Did you apply output activation to the third GRU cell in the paper?

On GRU, the paper discusses the nonlinear functions of R(t) and U(t)

The nonlinear σg(-) is the hyperbolic tangent

It also says

σc(-) is the nonlinear mapping, which is the element-wise sigmoid function

But the implementation seems to be σg(-) is sigmoid, σc(-) is tanh. I think the implementation is a more general activation of GRU. Is the one in the paper a misdescription?
I'm sorry if I misread the paper and the code.
It would be helpful if you could reply.

@tfj-dot The model used in the R-MVSNet paper is exactly the same model implemented in this repository.
Some minor modifications were made after we finish the paper writing. Sorry for making the implementation detail ambiguous.

@YoYo000
I understand.
Thank you for your prompt replying!


Add custom time formats

The format patterns from Time::Format allow to define simple date formats but they are quite limited in flexibility. Many standardized formats include slight variations which must be taken into account for parsing such formats in a standards-compliant way.
This PR reorganizes Time::Formatter and introduces custom format definitions for some well-used time formats.
This accompanies #4729 which improves the external API using fixed formats.

@luislavena The reasoning behind HTTP::HTTP_DATE was that this is a very specific combination of certain formats which doesn't have a real usecase outside HTTP protocols. Please see #4729 (issuecomment) ff.
In this PR the discussion was about the accessor methods HTTP.http_date and HTTP.parse_date. We could still keep these and move the format to Time::Format::HTTP_DATE.
I think itmakes sense to keep all format descriptions in one place.

I think it makes sense to keep all format descriptions in one place.

I will have no problem with HTTP.http_date and HTTP.parse_date become small shims/wrappers that access the specific Time::Format 😄
Definitely will make things more cleaner and easier to follow if all time related formats lives in the same space.
Thank you for taking the time to respond my comment and your continuous contributions to Crystal! ❤ ❤ ❤

Strong 👎  from me. This introduces a lot of new types, destroys the existing code, and I don't understand the purpose. If RFC_3339 needs a custom parser, write a custom parser (we can add it to the std), but I can't see why the whole Time formatting/parsing code has to change.
If it's just to reuse a bunch of small parsing methods (like, parse a day or a month) then I'd like to apply one of Go's proverbs here:

A little copying is better than a little dependency

It's better to duplicate a bit of code here. Otherwise I can't understand the code anymore with so much dependency, changes and indirections.

@asterite Thanks for the review. I don't like this complicated structure any more than you do.
The problem is: Duplicating all this parser and formatter code doesn't feel like a good solution either. There are not just small independent parsing methods but some are quite complex through combinations. And many are used by different parsers. So we'd really have to copy lots of code.
But I think I'll try to do it in a less invasive and more duplicating way and then we can see what can perhaps be improved.

Also, maybe this doesn't need to exist in the standard library. People can create shards for parsing specifying "dynamic" time formats.

Well these are really very common formats that should be fully supported by stdlib. The ISO 8601/RFC 3339 format is the most common format and in stdlib used by the JSON serializer. "Http date" is used for HTTP cookies. They are currently implemented only with limited, pattern-based support but it should be standard-compliant. This can only be achieved by a custom parser, which was as I understand it, consensus in #4729.

Golang has a huge standard library and these formats are not supported.

Yes they are: time.Parse and time Constants. They have also a few more which I think we shouldn't need to support.

So let's add those constants too, and problem solved. Just note that those constants have a fixed format, not a dynamic one like the ones you are proposing.
And that's what I'm saying: if you want a dynamic format, it can be provided by an external shard, or if the std needs it for something (like for parsing a specific YAML time format, or HTTP date) we can implement those specific parsers. But there's no need to make everything more complex and generic for that.

I feel uneasy merging something that doesn't cover 100% of the spec just because it works for 99% of applications.

I know. I wouldn't like adding those constants like it's done in Go. But I also don't want to maintain this and this is one of those things that can be just fine in an external shard.
In fact, I've been thinking that maybe it would be a good idea to move XML, YAML, maybe also Big to external shards so they can evolve faster and independent of the compiler. Maybe also JSON,, except that the compiler uses that.

I found a much easier solution which neither creates any more types nor duplicated code (except a few boilerplate methods) by just reopening the existing classes. #5123


Implementation app features

@tananaev , i want to suggest the escoder feature the app (traccar-client-android) the list of installed apps, and this setting was alternative in the app settings, or that there was need for a password to access the settings or uninstall smartphone app.

Can you please write in English and clearly separate the features that you are requesting.

It would be possible to add an option for the app to stay hidden from the list of installed apps? or password to change or remove it from your smartphone.

No, it's not possible, but have you looked at the hidden version of the app:
https://www.traccar.org/client/

The source code available on github is the hidden version?

Thank you, I understand now!

Source code is for both.


Meta startup process problem

Describe the bug
If an mp fails to start during meta startup, the listen process will be blocked, while other mps that have been successfully started by raft can participate in the election and become the leader, causing other mps to be unserviceable to the outside world.
Adjust the startup process. After the meta service is up, it will listen to the service port 17210, and then load the mp asynchronously. If the timeout fails to load, then panic

Reslove in V3.0.0。


Add pipeline for running tests and linting

Which CICD tool you are planning to use for the pipeline?

Which CICD tool you are planning to use for the pipeline?

Probably just GitHub Actions, I've done it before with my voxel engine repo.


Backchannels Moved to Framework Repos

Backchannels are moved out of AATH repo.
Follow the pattern of the Aries-VCX backchannel

Thoughts on the backchannel migration to aca-py, and a few questions.  @swcurran @nodlesh @jamshale
For Aca-py, I suggest we support 3 builds for the backchannel:

main, built off the github main branch (existing)
latest, built from the latest aca-py release (existing)
local, built from the local source code (for developer testing prior to check-in)

(Question - There are 2 other supported builds - acapy-redis and dev-acacpy-main, which I'm not sure we actually need or use?)
(There is also remote, which is coded in the OATH manage script, but doesn't have a supported aca-py build, which I don't think we need to the aca-py repo side of things, so I'll leave that in the OATH repo scripts.)
In the aca-py repo, the build scripts will build a local image, same as the OATH script currently does.  So to run tests locally, you can run the build scripts in the aca-py repo, and then just build and run the test harness in the OATH repo (no need to build the backchannels twice).
(Question - in the OATH ./manage build script, if you leave out the -a argument to build a specific agent, it will build all agents.  I think this is incorrect and if -a isn't specified it should build the test harness only and no backchannels?)
(If you are running OATH without building any local images, you will need to run the local OATH build script, which will download the necessary published images.)
In the aca-py repo, building the backchannel images will be supported by local scripts, and publishing the images will be supported by github actions.  The main image should be published each time the main branch is updated, and the latest image should be published each time a new version of aca-py is released.
(Question - is it better to publish a new main backchannel each time the main branch is updated, or is it sufficient to publish on a schedule, e.g. nightly?)
(Question - do we need to maintain a history of aca-py backchannels, so that new versions can be regression-tested against previous versions?)

Some thoughts in response:

I would hope that we don’t add builds to ACA-Py, since we already have the nightly and release builds.  I don’t think we need more artifacts.  Unless we eliminate the nightly, we don’t want to publish new artifacts on updating main.
I’m assuming that if you want to run the OATH tests, you would do so from the OATH repo — not from ACA-Py. Is that aligned with what you are thinking?
In OATH, there are two scenarios:

The automated GHA ACA-Py runs
A developer wanting to use a particular version of ACA-Py (perhaps from their own branch), ideally with debug access.

The two scenarios would be handled in OATH as we do today, with a separate “dockerfile.acapy-xx” for each scenario.
What I was wondering if we could have the OATH “./manage build -a acapy-XX” have:

Both scenarios use the “nightly” artifact as the docker FROM image (vs. using a Ubuntu Python image)
Both Dockerfiles pull in the ACA-Py backchannel code from GitHub (default — using the “main” branch).
The “developer run” Dockerfile would also bring in ACA-Py itself from GitHub (default to the “main” branch, but editable as we can today to use other repos and branches). Loading that would “override” the ACA-Py code already present from the nightly image.

I think that would give us the nightly runs — that would be faster because we wouldn’t be repeating the build process — plus the control needed when a developer needs to run specific tests in OATH against specific versions of the code.
Regards your questions:
Question - There are 2 other supported builds - acapy-redis and dev-acacpy-main, which I'm not sure we actually need or use?
My $0.02CDN — they can be ditched in favour of the “customizable” dockerfile that can be used by a developer.  Documentation could help to define scenarios that could set up.
Question - in the OATH ./manage build script, if you leave out the -a argument to build a specific agent, it will build all agents. I think this is incorrect and if -a isn't specified it should build the test harness only and no backchannels?
My $0.02CDN — A long standing bug from when I first created the script. Yes — the lack of a “-a” option should print the usage message and terminate.
Question - is it better to publish a new main backchannel each time the main branch is updated, or is it sufficient to publish on a schedule, e.g. nightly?
My $0.02CDN — We already publish a nightly image and we shouldn’t be publishing other ones. As noted — I would encourage we use the nightly one for OATH automated runs.
Question - do we need to maintain a history of aca-py backchannels, so that new versions can be regression-tested against previous versions?
My $0.02CDN — It’s a pretty obscure edge case. I think if we have the ability to edit the dockerfiles for a specific run, we can do a regression run of the current nightly (one Dockerfile) with an older version by branch/tag/commit (the other Dockerfile). That should be sufficient.

@swcurran  we should chat about this next week.  In the original comment Follow the pattern of the Aries-VCX backchannel - VCX builds and publishes the backchannel image from the VCX repo.  (The OATH tests are still run from the OATH repo.)  I expected we'd do the same with aca-py - move the backchannel code, and build (and publish) the backchannel image from the aca-py repo.
If we want to continue to do all the backchannel builds from the OATH repo I'm not sure the value of moving the backchannel code to the aca-py repo.

(Question - There are 2 other supported builds - acapy-redis and dev-acacpy-main, which I'm not sure we actually need or use?)
dev-acapy-main is the base container for the VSCode Dev Container for the ACAPy Backchannel. I use it all the time. Not sure where the dev container fits if the backchannel moves to the acapy repo. Maybe the dev container is useful to move there as well?
Will I, or any other test harness developer, loose access, or make it tedious to update the acapy backchannel if it moves to the acapy repo? During test development and backchannel development I'm switching between the OATH test dev container and the ACAPy Backchannel dev container constantly.

Will I, or any other test harness developer, loose access, or make it tedious to update the acapy backchannel if it moves to the acapy repo? During test development and backchannel development I'm switching between the OATH test dev container and the ACAPy Backchannel dev container constantly.

TBD, depending on how the move is done.  I think it will be easier for aca-py developers to test/update the backchannel, but more difficult for test harness developers.
We should chat to determine exactly what we need to do and why.  It sounds like the approach taken by VCX is not what we want for aca-py.

After some discussion, we'll leave the backchannel code in the OATH repo (for now anyways) and update the aca-py backchannel builds as follows:

add a new acapy-nightly build to build based on the nightly published aca-py image (to speed up build time)
change the scheduled test runs to use acapy-nightly instead of acapy-main (to speed up the nightly test runs)
update the acapy build to build based on the latest release docker image (instead of building from the pypi image) (to speed up build time)
add a new acapy-local build, to build based on local source code (rather than a github project) (so code can be tested locally before committing to github)

Overall this shouldn't impact any work that has to be done in the OATH repo, but will speed up our scheduled tests and make it a bit easier for aca-py developers to manually test with OATH.

FYI it looks like the acapy backchannel image build only takes about a minute, so making the above changes isn't going to shave more than a minute off our build times.
Unless I'm missing something?  I purged my local cache and did a few local builds ...

Sounds good.  Let’s leave it.

I was realizing as I looked at a test run this morning — the build takes 99% of the log — probably not 90% of the time.  So when I go to look at the results, I have to scroll down to find anything.  But I’m sure you are right — it won’t save that much time.  Sorry about that.
No need to change — we won’t get a lot of value out of that.

Just did another test with a more thorough purge of local images and cache, and the build took about 2 minutes (including about 30 sec for the test harness).  So agree not worth pursuing.
I'll take a look at adding a new build for acapy-local using local source code tho.


Adding zendesk honeypot

What's this PR do?
This pr adds a simple honeypot for some dork that's spamming our Zendesk tickets. If they keep persisting after this we'll look into something more advanced like this
How should this be reviewed?
Submit the Zendesk form, everything should work normally. Then try again, but fill-out the value of the honeypot input.

Any background context you want to provide?
I was originally going to implement our own shitty captcha, but this is a bit easier and doesn't impact the user at all.

 (4) As Hannah, I don't want folks to be able to submit a Zendesk ticket if they're a spamming robot


Issue with k8s.io/docs/concepts/workloads/controllers/cron-jobs/

Problem:
The 5 fields of the cronJob schedule format are not described on the page - there is only a link to some external documetation (https://pkg.go.dev/github.com/robfig/cron?tab=doc#hdr-CRON_Expression_Format). This documentation however is for a 6 field format which include an extra seconds field at the start.
Also the use of */1 in the examples isn't required because * already means every minute.
Proposed Solution:
Linking to a page which describes the 5 field version of the cron format e.g. the Wikipedia page: https://en.wikipedia.org/wiki/Cron
Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/

/kind bug
/priority important-longterm
/language en


Add link example to base button docs

[x] I have followed (at least) the PR section of the contributing guide.

This issue resolves #36933

@ZeeshanTamboli I went ahead and made the requested changes since the original author hasn't been here in awhile. Hopefully it's good to go now!


Percentage median BMI implementation

Percentage median BMI is used widely in child and adolescent eating disorders, and may have some utility in obesity, though SDS in obesity seems to be a more commonly used measure.
The RCPCHGrowth package reports %mBMI for both corrected and chronological ages, so should be included, perhaps in the tool tips against BMI.

Implementation here:


Emulated Hue/Alexa Not Adding Template Light without "set_level:" attribute even if blank

HA 0.98.1
Apologies if not doing this properly, first issue submission....  but it seems the fix in https://github.com/home-assistant/home-assistant/pull/26055/commits/8c8ad3cd02451a0abbbf0f93cd9c6bbf5d3b43d9 causes exposed template lights to not be available to Alexa unless they contain the "set_level:" configuration line... even if it does not contain an action.
It is listed in api/pi/lights but shows up as model "HASS321" when it does not contain "set_level:" and then never actual populates when Alexa is discovering devices, or says "the device is not responding" if it is still listed from an old discovery.  Simply adding the "set_level:" configuration line without an option makes it show up as a dimmable "HASS123" light and it then populates in the Alexa App. and works properly.
In my case my template light controlled an input_boolean, and the turn_on and turn_off actions turned the input_boolean on and off so I never had "set_level:" Removing the "set_level:" line again caused the light to "not respond" and show as unavailable/unreachable to Alexa, adding set_level: fixed the issue.
I see that it is listed as a breaking change but it says removing and re-discovering will add the light back without brightness... this does not seem to work.
Please let me know if I need to provide more information or anything.

Which Alexa do you have?
can you please try to reset your Alexa? How to reset
after that try to re-discovering the light and check if you see the light with the model HASS321 in the app.

@bryeartem Please edit your issue and fill out the template -- there's important details that would help us triage and troubleshoot this problem.

Apparently some changes were made in recent Alexa firmware updates... im thinking I should close this until that’s resolved as that may be the actual root cause.  https://community.home-assistant.io/t/emulated-hue-suddenly-stopped-working-with-echo-dot-v2/133956/42?u=bartem


AttributeError: type object 'neuralcoref.neuralcoref.array' has no attribute 'reduce_cython'

Happens when I do:
pip uninstall neuralcoref
pip install neuralcoref --no-binary neuralcoref

# Load your usual SpaCy model (one of SpaCy English models)
import spacy
nlp = spacy.load('en')

# Add neural coref to SpaCy's pipe
import neuralcoref
neuralcoref.add_to_pipe(nlp)

# You're done. You can now use NeuralCoref as you usually manipulate a SpaCy document annotations.
doc = nlp(u'My sister has a dog. She loves him.')

doc._.has_coref
doc._.coref_clusters

Have you tried starting from a new virtual environment ?

Happens when I do:
pip uninstall neuralcoref
pip install neuralcoref --no-binary neuralcoref

# Load your usual SpaCy model (one of SpaCy English models)
import spacy
nlp = spacy.load('en')

# Add neural coref to SpaCy's pipe
import neuralcoref
neuralcoref.add_to_pipe(nlp)

# You're done. You can now use NeuralCoref as you usually manipulate a SpaCy document annotations.
doc = nlp(u'My sister has a dog. She loves him.')

doc._.has_coref
doc._.coref_clusters

Hey,
Did you find a solution for this problem?

I was recently getting this error when I try to use neuralcoref on Colab (Python 3.7).
If I reinstalled neuralcoref (like @stephenmathew suggests) and then restarted the runtime, I kept getting the spacy.strings.StringStore size changed error. If I restarted the runtime after reinstalling, I would get this no attribute '__reduce_cython__' error.
The solution was using spacy 2.1: python -m pip install spacy==2.1.0

@fbottazzoli , read @lara-martin's message carefully... use spacy 2.1

I'm facing the same issue:
spaCy version 3.2.3 Location C:\Users\botti\anaconda3\envs\tesienv\lib\site-packages\spacy Platform Windows-10-10.0.22000-SP0 Python version 3.7.11 Pipelines en_core_web_md (3.0.0), en_core_web_sm (3.2.0), it_core_news_md (3.0.0)

I was recently getting this error when I try to use neuralcoref on Colab (Python 3.7). If I reinstalled neuralcoref (like @stephenmathew suggests) and then restarted the runtime, I kept getting the spacy.strings.StringStore size changed error. If I restarted the runtime after reinstalling, I would get this no attribute '__reduce_cython__' error.
The solution was using spacy 2.1: python -m pip install spacy==2.1.0

Nope it didn't work


Github Release Drop cant be 'triggered'

It seems doing a release whenever a new 'GitHub Release' isnt supported

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

ID: d9e313c5-9120-9172-bc27-c21d10fcd5ae
Version Independent ID: 1a837182-591f-3cbc-1632-7b50d857b13c
Content: Release triggers for stages, branches, and pipelines - Azure Pipelines
Content Source: docs/pipelines/release/triggers.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

@danpetitt -- Dan, thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please let us know which topic you’re referencing, or provide more context around the general task.

@danpetitt -- Dan, thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please let us know which topic you’re referencing, or provide more context around the general task.

Sorry, what additional information do you need other than what has been detailed in the ticket ... this gives the documentation page I was commenting on.
Basically I would like to use a GitHub Release to 'trigger' an Azure DevOps Release Pipeline, but currently I cannot. The little lighting icon overlay on the GitHub Release Artifact task does not exist like it does on other Artifact Drop tasks.

@danpetitt - Thanks for the feedback. Today we don't have automated trigger support for github release artifact. However, we have it in our backlog. We will update you once the support is available.

Thank you for your feedback. The updated article will go live shortly.


Listing Actions very slow when there are more than 10K actions

Cannot show actions in action page
Data Sync page becomes very slow.

Should add paging support. Or paging with filtering for reducing amount of data retrieved. This can becomes a denial of service attack. Caching results locally could help speed things too.

Thanks @mkbhanda for your advice. :)
Actually, paging support of SSM is a work in progress. The main task has already been assigned to @zhiqiangx . @duzhen1996 and I will support he to finish this task. We will break down this task in the future.

#1314

Already done. Issue closed.
Thanks @zhiqiangx @littlezhou @duzhen1996 .


upgrade dapr to v1.6.0

Upgrade dapr to v1.6.0 for it is already published.
ref: https://github.com/dapr/go-sdk/issues/245

Thanks @wongoo


Error in output - unable to run

Dear Rob,
I recently attempted to run the new version of the script on  Python 3.6.2 and Python 2.7.13; every time it would just print an error message saying:
File "GoodVibes.py", line 374
if all_same(l_o_t) == True:
IndentatonError: unexpected indent
This issue seemed to be fixed after I simply deleted two spaces before "if" on line 375 to bring the string to the same block level. However, output still gave an error in both versions of Python but from that point, different versions gave different errors.
I managed to get the script running on Python 2.7.13 (but not on Python 3.6.2) by additionally adding "# -- coding: utf-8 -" at the top to enforce UTF-8 and fix the default ASCII encoding problem that caused errors with Python 2.7 (it reported SynthaxError because line 372 apparently contained a non-ASCII '\xc2' character - probably from copy-paste).
Many thanks,
Nik

Nik,
Fixed as per your request. Tested with python 2.7 and 3.6 without problem.
Thanks


Bump image from 0.24.9 to 0.25.2

Breaking changes from 0.24 to 0.25 are described in https://github.com/image-rs/image/blob/main/CHANGES.md#version-0250.
This PR includes the following changes to adapt to image 0.25:

Replace ImageOutputFormat, previously deprecated and removed in 0.25, with ImageFormat
Require the color_quant crate feature (for impl ColorMap for NeoQuant)

Can we disable default features? This is bringing in a lot of new dependencies and I'm not sure if we need them all.

Can we disable default features? This is bringing in a lot of new dependencies and I'm not sure if we need them all.

Sure, that’s feasible.
As of 0.24.9, the default features were:
default = ["gif", "jpeg", "ico", "png", "pnm", "tga", "tiff", "webp", "bmp", "hdr", "dxt", "dds", "farbfeld", "jpeg_rayon", "openexr", "qoi"]

As of 0.25.2, they are
default = ["rayon", "default-formats"]
default-formats = ["avif", "bmp", "dds", "exr", "ff", "gif", "hdr", "ico", "jpeg", "png", "pnm", "qoi", "tga", "tiff", "webp"]
avif = ["dep:ravif", "dep:rgb"]

So what I notice, looking at the above and at the diff https://github.com/image-rs/image/compare/v0.24.9...v0.25.2#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542L63, I notice:

avif was added to the default features, bringing in the ravif crate (which has some new dependencies like loop9, imgref, avif-serialize, rav1e)
the jpeg_rayon feature is gone and jpeg now brings in zune-core and zune-jpeg – nothing to be done about this if you need JPEG support
rayon was added to the default features, which enables multithreading

It seems like rayon is worthwile, because this is likely to speed up loading of images and therefore perceived responsiveness. The biggest way you could prune the dependency tree would be by omitting support for the AVIF format. I’ll add that to this PR. Let me know what you think.

Rebased on main with the image crate features reduced as suggested.


Exclude attribute and find logging from activity

This type of filesystem activity is common and introduces lots of noise
in wash history. It's also rare that anyone except a Wash core
developer cares about these things. Exclude them from activity and log
directly to debug.
Fixes #323.
Signed-off-by: Michael Smith<EMAIL_ADDRESS>

The intention is specifically to leave it out of the history. Debug logs are where you could go if you really cared about what all's querying the filesystem.


non-interactive mode for migrations

Hi,
I have an automatized deploy for my development environment.
So I have to launch migrate task in my deploy process.
But deploy:migrate always asks for a validation (yes or no?).
So it should be great to add a "interactive_mode" parameter and change migrate method :
if !interactive_mode || Capistrano::CLI.ui.agree("Do you really want to migrate #{symfony_env_prod}'s database? (y/N)")

Thanks for your great gem !

Thanks for your add.
But this doesn't fix my problem : Capistrano still ask for a confirmation. The no-interactive mode should be for capistrano, in addition to doctrine... (like in my example).

It is probably you capistrano setting, because it works well for me. Same code as I posted is already in task deploy.migrate in symfony2.rb. I am using capifony (2.1.4) and capistrano (2.9.0).

but what if I need to automatically "yes" the migrations, but interactively add new parameters.yml parameters?

@velikanov did you find a way around that?


[feature/loaders] html-loader strips  when minimizing

If you use the html-loader (that minimizes per default), the regexes to inject tags will break as html-loader uses the removeOptionalTags option from html-minimizer, which removes </body> etc.
One has to be careful and explicitly set html?removeOptionalTags=false!<my-template>.
We should emit a warning if the option is not explicitly set to true.

Probably the same as #135 and #128.
I also opened an issue for the html-loader: https://github.com/webpack/html-loader/issues/40

Looks like the html-loader might fix this soon: https://github.com/chrisnicola/html-loader/commit/b797acf13765c425836588f4fa4d24ac942db730

Fixed: https://github.com/ampedandwired/html-webpack-plugin/commit/68428b583f359849c798f71e64855613b67ae4e8


Add retriable for retrying hooks during deploy

Why we need to retry hooks?

Robustness.
During testing I encountered a situation where the first step of auth provider config passed and the second one gave some weird timeout error and so the rest of the steps were not run since one of them raised.
Of course it would be possible to just retry X times using plain rescue.

Ok, just thought if there are any side-effects. It seems that retrying these hooks is safe.

Rebase, pls.

LGTM


Add property as IPC interface capability.

lgtm. make sure the command_index/property_index problem on clang and osx is addressed before merging.


How do I use the OnResult function correctly?

Hello!
Sorry I'm back with another question, so I want to use the onResult function to send the payload to a Lambda function so I have done this in CDK.
    const clamScanDeleteLambda = new lambda.Function(this, 'clamscan-delete-file', {
      runtime: lambda.Runtime.NODEJS_14_X,
      code: lambda.Code.fromAsset('lambda'),
      handler: 'index.handler',
    });

    const sc = new ServerlessClamscan(this, 'Clamscan', {
      resultDest: new destinations.LambdaDestination(clamScanDeleteLambda)
    });

However it doesn't seem to like the destination defined in this way?
Object literal may only specify known properties, and 'resultDest' does not exist in type 'ServerlessClamscanProps'.ts(2345)
Am I doing this wrong?

The property is call onResult not resultDest. This example may help with that

Interesting @dontirun I actually had is as onResult in my original code. But it didn't send across the event to my Lambda functions so I presumed I did it wrong and it should be resultDest.
I originally had this
    const clamScanDeleteLambda = new lambda.Function(this, 'clamscan-delete-file', {
      runtime: lambda.Runtime.NODEJS_14_X,
      code: lambda.Code.fromAsset('lambda'),
      handler: 'index.handler',
    });

  const sc = new ServerlessClamscan(this, 'Clamscan', {
      acceptResponsibilityForUsingImportedBucket: true,
      onResult: new destinations.LambdaDestination(clamScanDeleteLambda)
    });
    sc.infectedRule?.addTarget(
      new SnsTopic(infectedTopic, {
        message: RuleTargetInput.fromEventPath(
          '$.detail',
        ),
      }),
    );

I can see the destination was added on the ClamScan Lambda Function, but when I uploaded an infected file into S3, it marked it as infected correctly, but no logs indicated that the Lambda function was actually called. My Lambda function is just this for testing reasons right now.
Lambda Function
exports.handler = async (event) => {
  // TODO implement
  const response = {
      statusCode: 200,
      body: JSON.stringify('Hello from Lambda!'),
      event
  };
  return response;
};

Anything obvious I am missing? I can't see why this wouldn't work.

That's strange. Does the scan lambda have proper permissions to invoke your lambda function?

Good point @dontirun is there a way I can even add that, because the scan lambda is inside your module? 🤔

Good point @dontirun is there a way I can even add that, because the scan lambda is inside your module? 🤔 Edit: Actually it added the permissions automatically to my function (this is from the function its sending from)
So the ClamscanServerlessClamscan is being called, I can see the cloudwatch logs but its not calling the Lambda function at the same time, I'm thinking maybe I should put an SNS Queue before the Lambda function to see if that fixes this, its a bit strange though. 🤔
Maybe the destination bucket needs permissions!?

@dontirun Okay so, im wrong it is being invoked, for some reason if you don't log anything with console.log() it doesn't log any logs to say the Lambda function ran 🤔 I'm not sure if thats by design or not, but I am now receiving the payload so I can handle it.
Example Payload:
{
  version: '1.0',
  timestamp: '2022-10-06T07:19:38.972Z',
  requestContext: {
    requestId: '3be2dc97-c8da-4495-9636-6da14aa924ea',
    functionArn: 'arn:aws:lambda:us-east-1:983324074397:function:clamscan-development2-ClamscanServerlessClamscan66-Aoox7o5tESer:$LATEST',
    condition: 'Success',
    approximateInvokeCount: 1
  },
  requestPayload: { Records: [ [Object] ] },
  responseContext: { statusCode: 200, executedVersion: '$LATEST' },
  responsePayload: {
    source: 'serverless-clamscan',
    input_bucket: 'saas-upgrade-bucket-development',
    input_key: 'dangerousfile (1).com',
    status: 'INFECTED',
    message: 'Scanning /mnt/lambda/3be2dc97-c8da-4495-9636-6da14aa924ea/dangerousfile (1).com\n' +
      '/mnt/lambda/3be2dc97-c8da-4495-9636-6da14aa924ea/dangerousfile (1).com: Win.Test.EICAR_HDB-1 FOUND\n' +
      '\n' +
      '----------- SCAN SUMMARY -----------\n' +
      'Known viruses: 8638808\n' +
      'Engine version: 0.103.7\n' +
      'Scanned directories: 1\n' +
      'Scanned files: 1\n' +
      'Infected files: 1\n' +
      'Data scanned: 0.00 MB\n' +
      'Data read: 0.00 MB (ratio 0.00:1)\n' +
      'Time: 26.368 sec (0 m 26 s)\n' +
      'Start Date: 2022:10:06 07:19:12\n' +
      'End Date:   2022:10:06 07:19:38\n'
  }
}```

@dontirun I have a quick question for you, sorry to be a pain!
So in our use case here, we are scanning the S3 bucket which is great, is it technically possible for us to call this Lambda function inside our application code? I'm guessing its not?
So for example, when someone is uploading a file in our code, our developer wants to invoke this lambda function with the file and see if its infected, I am not sure what inputs the lambda requires, and if this is at all possible?

Not with how the solution is currently designed.
Additionally lambda destinations (so the infected file delete you have set up) doesn't run if the scan lambda is invoked synchronously, lambda destinations only work on asynchronous invokes


Ecobee hold_temp true not setting permanent temp holds

I'm reopening issue #6743 as the ecobee hold_temp setting is currently not working as documented.
Home Assistant release (hass --version):
0.52.1
Python release (python3 --version):
Python 3.5.2
Component/platform:
Ecobee
Description of problem:
Previously, and as outlined in 0.38, doing a climate.set_away_mode would mimic the Ecobee functionality of Away and hold putting the device into a permanent Away state until it was removed. Currently any hold change is done until the next scheduled change (Next Transition).
Expected:
set_away_mode should set a permanent hold.
Problem-relevant configuration.yaml entries and steps to reproduce:
What I noticed with the recent change is that when doing a turn_away_mode_on it just calls up set_hold_mode:
def turn_away_mode_on(self):
    """Turn away on."""
    self.set_hold_mode('away')

In turn calling up set_climate_hold that has a fixed hold_type of nextTransition
def set_climate_hold(self, index, climate, hold_type="nextTransition"):
    ''' Set a climate hold - ie away, home, sleep '''
    url = 'https://api.ecobee.com/1/thermostat'
    header = {'Content-Type': 'application/json;charset=UTF-8',
              'Authorization': 'Bearer ' + self.access_token}
    params = {'format': 'json'}
    body = ('{"functions":[{"type":"setHold","params":{"holdType":"'
            + hold_type + '","holdClimateRef":"' + climate + '"}}],'
            '"selection":{"selectionType":"thermostats","selectionMatch"'
            ':"' + self.thermostats[index]['identifier'] + '"}}')
    request = requests.post(url, headers=header, params=params, data=body)
    if request.status_code == requests.codes.ok:
        return request
    else:
        logger.warn("Error connecting to Ecobee while attempting to set"
              " climate hold.  Refreshing tokens...")
        self.refresh_tokens()

Previously turn_away_mode_on did not call up set_climate_hold and would set hold_type as indefinite:
def turn_away_mode_on(self):
    """Turn away on."""
    self.data.ecobee.set_climate_hold(self.thermostat_index,
                                      "away", 'indefinite')
    self.update_without_throttle = True

Since most changes seem to be configured for nextTransition it would appear to ignore the optional hold_temp for the component
hold_temp (Optional): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to False.
Should probably remove from the Docs if depreciated.
Traceback (if applicable):
Additional info:
I know this issue has been talked about and debated a few times before, and probably still ongoing:
https://community.home-assistant.io/t/this-service-has-been-deprecated-use-climate-set-hold-mode/10949/37
#5832
It might also be worth investigating being able to ad_hoc set holds as indefinite as opposed to doing two modes or having a hold_temp overall settings. Just a thought.
The documentation is here: https://home-assistant.io/components/ecobee/

I am seeing this behavior as well. +1

OK,
I have tested a few things just to see if I can get any indefinite hold to work and everything seems to get reset at the next scheduled event.
I set my configuration.yaml to have hold temp as 'True':
ecobee:
  api_key: !secret ecobee_api_key
  hold_temp: True

I then spun up a quick automation to just set the temperature on my Ecobee.  When the automation fired it set the temp, but with an end time of the next scheduled event.
I them changed my Ecobee Hold Action settings to "Until I Change It":

I reset the tests and fired the automation again.  Same result.  Temperature is set, but with an end time of the next event.
I fully agree with @chilicheech, the set_away_mode should be an indefinite hold to mimic the behavior of pressing the "Away for Now" button on your Ecobee thermostat.
I know there are many discussions about this on the boards, and @geekofweek has been active in many of those.  I am not sure if I am just missing some part of the config to enable these indefinite holds.  Or maybe an understanding of how things should flow within HASS.
@Duoxilian did a lot of work on the hold function, so I am not sure if they would be able to provide some insight.  Any help would be greatly appreciated.
Thanks,
Dan W.

This commit is what stopped the use of the hold_temp config setting.
We could update the hold_preference method to honor the hold_temp config. That way any temperature change in HASS would be indefinite, if that's what the user wants. Might be too extreme, but I'm ok with it.
Another option is to make set_away_mode set an indefinite hold and still allow you to set the temperature and keep the indefinite hold. In other words, when I turn on set_away_mode it would put the Ecobee on away mode indefinitely. If I make any changes to the temperature it would also be indefinite while on away mode. Turning off away mode would resume the program, thus removing the indefinite hold.
Another option is to create a set_indefinite_hold service/toggle that allows the user to turn on when they want indefinite hold, instead of using the hold_temp config.
Whatever we do, my end goal is to be able to set a temperature and hold it indefinitely.
Cheers,

Here are my thoughts on this:
I agree with you concerning the global hold_temp config.  I believe it is too rigid.
This weekend I tried clearing the schedule on my Ecobee to see if I could just run without anything and therefor there would never be a "next event".  Unfortunately, there is still an underlying schedule for whatever your single comfort setting is, home for example.  That means that although there is not a daily change, there will be a time that the schedule comes into play.  At default this is midnight on Monday it would seem.
I think that set_indefinite_hold service/toggle is a great idea.  That way you can use it for different events as you see fit.  If this option is not set in the service it defaults to whatever you have set in your Ecobee preferences (2 hours, 4 hours, next event, etc.).  I think this would allow the most flexibility for the end user and overcome any random schedule issues, even when using the default schedule.
Thoughts?
This next bit is a little off topic, but is in the line of climate holds and I thought I would include it here.
Today I configured a new comfort setting within the Ecobee system name Home Weekend'.  Even though this new comfort setting showed up under the thermostat entity in Home Assistant (climate_list: Away,Home,Sleep,Home Weekend) I was continuously receiving an error when attempting to set the hold.  Upon further investigation I found that Ecobee does not honor the name you give the comfort setting.  The system gives them a generic name starting at smart1` and going up from there.  The name you put into the config on the Ecobee site is just a friendly name for you to recognize.  See URLs below:
Ecobee Home Setting URL: https://www.ecobee.com/consumerportal/index.html#/devices/thermostats/999999999999/climate/home/name
Ecobee Home Weekend Setting URL: https://www.ecobee.com/consumerportal/index.html#/devices/thermostats/999999999999/climate/smart1/name
Once I noticed this I set the hold using smart1 and things were set properly.  I do not know how to overcome this in a programmatic fashion without setting up some sort of translation list outside of interacting with the API.


Adds requests/second rate limiter

Needed one of these for a project, figured I'd toss it up as a pull request.

Thanks!

Please consider also amending the README accordingly.

No problem, I'm also writing a spec for it and will push that up shortly :)


Implement Strelka support (resolves #73)

resolves #73

Jenkins, test this please.

Jenkins, test this please.


There is no "load more" after uploading 100 files for a blob container of Local Emulator

OS: Win10
Build Version: 20201129.1
Repro Steps:

Expand "Local Emulator" node.
Right click the Blob Containers --> Create a new blob container --> Upload 100 files to it --> Refresh.
Check whether display the "Load more".

Expect:
Display the "load more" after uploading 100 files.

Actual:
There is no "load more" after uploading 100 files.
More Info:
This issue doesn't reproduce for the attached storage accounts or common storage accounts.

Tracking this issue here: https://github.com/microsoft/vscode-azurestorage/issues/659
Azurite handles the load blobs response differently from Azure which is what's causing this bug.


add elv-live installer

will put a valid elv-live in /opt/homebrew/bin/ (or equiv) when running npm i -g
not sure if this is the appropriate thing to do or not, for getting elv-live in people's path (for use in scripts)
"worksforme"

updated to share the same script

ah would have been happy to apply them if i had seem the comments in time..
yea if i had written it i'd have used "$@" --missed updating that
exec i'm not as clear on -- doesn't that have potentially bad interactions with re-globbing?


Add an options argument to the getResponse provider method

To solve the issue https://github.com/thephpleague/oauth2-client/issues/863 I propose the following PR
I wanted to write some tests but feel a bit struggled because i don't know Mockery.

I think you also need to add the $option to getParsedResponse() and pass it to getResponse(). For example if you want to pass a json body to the server.

Closing this in favor of focusing on https://github.com/thephpleague/oauth2-client/pull/1032 for the next major version of this library.
Thank you for contributing! 🎉


Tedious sproadically stops working with Azure v12 DB

After we upgraded to v12, our SQL queries periodically stop working, returning following message on every query:
{"RequestError\",\"message\":\"Requests can only be made in the LoggedIn state, not the Final
state\",\"code\":\"EINVALIDSTATE\"}

The only way to resolve this is restarting the node process.
Is there a way to cause Tedious to reconnect to Azure DB, other then restarting node?
I've looked through documentation, however didn't find any reconnection parameters.
We use version 1.11.0 of Tedious.

Can you see if the changes in this pull request solves your issue?

@bretcope Haven't encountered it on development machine with the patch, however I need to test it on staging to be sure. Any idea what would be the best way to ensure the prebublish runs after npm install from github?

@bretcope Any idea?

Unfortunately the pull request has not helped, we need to stop the Node and restart it via watchdog for the time being


Ingested Docs only search?

Is it possible to set a flag to only search against documents ingested ie if I search for Bill Shakespeare I don't want to return info on shakespear unless it's in my ingested Docs.

So there is a file in application/prompt/chat_combine_prompt.txt
What you can do here is change it to something that sounds like this

You are a DocsGPT, friendly and helpful AI assistant by Arc53 that provides help with documents. You give thorough answers with code examples if possible.
Use the following pieces of context to help answer the users question, if you dont know the answer or its not mentioned here, repsond with I don't know.
----------------
{summaries}

It will make llm more strict


Rename Navigation Drawer items

Chore
Chore Description
Few menu items in the Drawer layout should be renamed so that the Drawer layout of Orga App looks similar to EventBrite app. This will help users to make the transition smooth for users who choose to migrate to Orga app from EventBrite app.
Attendees    ->     Check In
Also change the Date format displayed in Drawer to DAY, MONTH-DATE, TIME
Would you like to work on the issue?
Yes

@Masquerade0097 Can I take this issue up?

@sridharjajoo Sorry, I intend to work on it.


Different labs solutions

There can be multiple solutions for the exercises. Sometimes they are more efficient.
I have solved the exercises using different logic/algorithms and many of them are efficient as well, I want to add these solutions to the solution folder in this repository. Please grant me permission to do that.
Thank you
Sincerely
AzizMaz7

Not in charge but out of curiosity could you describe the more efficient solutions? Most ex solutions were often the most efficient.

Yes, but there can be different ways to solve a problem, eg. lab 4 ex2 and ex3, lab5 ex 1, ex 2, lab 3 ex 3 etc etc...

However could you provide a representiative example? This could help the administrators to better accept your request. Lab 3 ex3 for example has no other solution, that is how the algorithm is carried out.

Like, eg: For lab4 ex2 you can use ccx gates instead of cx gates, lab5 ex1, and ex2 different ways to get the answer.
And yes for lab3 ex3 there is only one solution, that's my bad in the previous comment.
And I already pulled up a request where I submitted my codes so that they can verify it.

Thanks for the details, these solutions do not seem optimal (ccx is harder to implement than cx, lab5 has a transpiled depth of almost 2000 > 54). Nevertheless, I hope the curators might find it interesting to allow for participant solutions for the challenges.

Thanks for your interest! The solutions we published are just examples, and we don't intend to publish any others here. Feel free to publish your solutions in your own personal repository.


Unable to get specified ApplicationGateway

Running Brownfield Deployment on existing Kubernetes cluster.
Getting below error in ingress pod:

E0318 20:27:15.462952       1 main.go:83] unable to get specified ApplicationGateway [aks-dev-gateway], error=[azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions/xxxx-xxxx-xxxx-xxxx/resourceGroups/aks-dev-gateway/providers/Microsoft.Network/applicationGateways/aks-dev-gateway?api-version=2018-06-01: StatusCode=400 -- Original Error: adal: Refresh request failed. Status Code = '400'. Response body: {"error":"invalid_request","error_description":"Identity not found"}]
I0318 20:27:15.463055       1 main.go:86] Retrying in 10s

helm-config.yaml
appgw:
    subscriptionId: xxxx-xxxx-xxxx-xxxx
    resourceGroup: aks-dev-gateway
    name: aks-dev-gateway

armAuth:
    type: aadPodIdentity
    identityResourceID: "/subscriptions/xxxx-xxxx-xxxx-xxxx/resourceGroups/MC_aks-dev_aks-dev_canadacentral/providers/Microsoft.ManagedIdentity/userAssignedIdentities/aks-dev-identity"
    identityClientID:  aaaa-aaaa-aaaa-aaaa

rbac:
    enabled: true

aksClusterConfiguration:
    apiServerAddress: <IP_ADDRESS>:443

An application gateway exists in the mentioned resource group. What am I missing?

Looking at the error, you missed the step to create the identity in the MC_aks-dev_mts-aks-dev_canadacentral resource group. Can you check this resource group to make sure the identity exists ?

@akshaysngupta Yes. Identity exists.

Also, check your identityClientID. Make sure that it matches the Client ID of  userAssignedIdentities/aks-dev-identity on portal or use az identity show -g MC_aks-dev_aks-dev_canadacentral -n aks-dev-identity

@akshaysngupta It's exactly the same. Again, it looks like the error is with app-gateway and not the identity.

@akshaysngupta At one of our customers we are experiencing the same issue.

@rnkhouse does the identity have contributor rights to the application gateway resource group?

@asridharan It worked after I added contributor rights to Identity. I think it's good if it's part of helm config.

@rnkhouse not sure what it means to add this to the helm config? This is an ARM configuration.

@asridharan It worked after I added contributor rights to Identity. I think it's good if it's part of helm config.

Closing this out, since the issue seem to be resolved and for brown field deployments we can't modify the identity from the helm config.


See if it's possible for avatars (descriptor) to not be on a root-level object

Since this would solve the issue around storing EZFXLayer configuration in prefabs, which wouldn't normally be possible because they of course refer to other objects in the scene.

Closing because we probably won't do this for EZFXLayer, but instead of another eventual tool. This would be too-heavy of a violation of the principle of least surprise.


Close producer no matter if @producer_enabled or not

Hi phobos team,
By reading the current code, it would only close the producer when @producer_enable:
https://github.com/phobos/phobos/blob/c9534923d0eb7460ecf74fba34526545c4220e90/lib/phobos/listener.rb#L115-L118
This assumes we have a class that extends both Listener and Producer. In our code, we have something like:
class KafkaProducer
  include Phobos::Producer
end

..and it has been used in the consumer/listener, but didn't get closed when we reboot the consumer.

What's the problem that if we don't close the producer connection during deployment?
Could we go through OpenSpace find all the classes that inherit Phobos::Producer and close them?

Thanks!

For other application rails/sinatra, we handled it by puma on_worker_shutdown hook and it works fine.

btw, I reviewed this today and realize I made a mistake:  on_worker_shutdown only has access to worker context, each worker could have multiple threads and seems impossible to shutdown the producer in this case


Connection error while fetching messages: Connection error Errno::EBADF: Bad file descriptor

Simply start a consumer. Lets say for the sake of simplicity that there is nothing to consume. When I shutdown a consumer I get the following error in my logs.
D, [2018-06-13T11:01:18.380510 #23536] DEBUG -- : Closing socket to x.x.x.x:9092
D, [2018-06-13T11:01:18.380584 #23536] DEBUG -- : Closing socket to x.x.x.x:9092
E, [2018-06-13T11:01:18.380668 #23536] ERROR -- : Connection error while fetching messages: Connection error Errno::EBADF: Bad file descriptor
Version of Ruby:2.3.1
Version of Kafka:0.5.2
Version of ruby-kafka:0.3.7

Is this causing a functional problem? We log all sorts of errors, but when shutting down you might get false positives due to the async nature of ruby-kafka.

I dont think it is causing any functional issue. Will let you know if I find something


Link to old reference site

Located at: https://quickstarts.sigmacomputing.com/guide/administration_api_code_samples/index.html?_gl=11qlr87k_gcl_auOTk4MzA4NDAxLjE3MTM1NTA5Njg._gaMTQyMjgxMTk2MS4xNzA1NDQ3NjAx_ga_PMMQG4DCHC*MTcyMDIxODA4OS4yMDYuMS4xNzIwMjE5MzY4LjU0LjAuMA..#2
The "located here" link in the introduction points to the old API reference site:

This section demonstrates the code that was provided on the API Code Samples > Authentication: Get Access Token page, located here.

This has been corrected. Thanks for reporting it Colin.


feat: add subscriptionMaxEvents for maximum number of notifications (geofencing)

What type of PR is this?
Add one of the following kinds:

enhancement/feature

What this PR does / why we need it:
Based on the updated guidelines the subscriptionMaxEvents is added as an optional parameter to define after how many events the subscription will end.
Which issue(s) this PR fixes:
Fixes #111

@bigludo7 v0.2.0 for DeviceLocation was released yesterday.
This is the new version for Geofencing API, which will be v0.2.0 for this API, but v0.3.0 for DeviceLocation release.
That's why I used here v0.2.0-wip.

thanks for the review.
I will adapt the changes and close the other one


[JENKINS-65398] Terminology update

Terminology update as part of JENKINS-65398.

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your master branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

@twasyl thanks for doing this. Would you mind applying gradlew spotlessApply to format the code so that the build passes?

@twasyl thanks for doing this. Would you mind applying gradlew spotlessApply to format the code so that the build passes?

@jeschkies Yes sure, I've done that and pushed


Specify Embulk-Plugin-Main-Class at execution time

@muga Found one problem -- it fails even if embulkPluginJar is not specified to run (./gradlew embulkPluginJar).
mainClass may be empty, but the mainClass was evaluated anytime, not only when embulkPluginJar is run.

Thanks!


In list-items, better support icons as illustrations, non-link-styled links, empty actionHref, and skeletons

When icons are used as illustrations, match text color and remove border-radius
Allow the default text color to be overridden without affecting hover text color (also, per design docs*, I believe the default should be ferrite instead of celestine, but I did not make that change here... yet)
If actionHref is an empty string, treat it as null
Don't change the background-color on hover of skeletons and hide the primary action link (this may be off-base if skeletons are not standardized this way)

* Design docs say:

Primary Text - ... This text can styled as a link if the purpose of the list is unclear, or for visual variety in complex list items."

Oh for...

Allow the default text color to be overridden without affecting hover text color (also, per design docs*, I believe the default should be ferrite instead of celestine, but I did not make that change here... yet)

I think we'd definitely want to review that with Jeff or whomever "owns" the list design.  I know he has a lot of things in the works for changes to lists.  I think the rationale was that list-item-links should be celestine like standard links, and they also get the underline when hovering/focusing.  The celestine provides the user a hint that they are links before hovering or focusing. I don't necessarily think the design doc is up to date.

Oh for...

Allow the default text color to be overridden without affecting hover text color (also, per design docs*, I believe the default should be ferrite instead of celestine, but I did not make that change here... yet)

I think we'd definitely want to review that with Jeff or whomever "owns" the list design.  I know he has a lot of things in the works for changes to lists.  I think the rationale was that list-item-links should be celestine like standard links, and they also get the underline when hovering/focusing.  The celestine provides the user a hint that they are links before hovering or focusing. I don't necessarily think the design doc is up to date.


Relative import path in workerHelpers.js is wrong?

I've got the following minimal project set up:
Cargo.toml
[package]
name = "rayon-test"
version = "0.1.0"
edition = "2018"

[lib]
crate-type = ["cdylib"]

[dependencies]
wasm-bindgen = "0.2"
wasm-bindgen-rayon = "1.0"
rayon = "1.5"
console_error_panic_hook = "0.1.6"

lib.rs
use wasm_bindgen::prelude::*;
use rayon::prelude::*;
use console_error_panic_hook;
pub use wasm_bindgen_rayon::init_thread_pool;

#[wasm_bindgen]
pub fn sum_of_squares(input: Vec<i32>) -> i32 {
    console_error_panic_hook::set_once();
    input.par_iter().map(|&i| i * i).sum()
}

index.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <title>rayon test</title>
  </head>
  <body>
    <script type="module">
      import init, {initThreadPool, sum_of_squares} from "/rayon_test.js";
      await init();
      await initThreadPool(2);
      console.log(sum_of_squares([1,2,3]));
      </script>
  </body>
</html>

But I got an "invalid mime type" error at this module import line in workerHelpers.js:
const pkg = await import('../../..');

I changed it to this:
const pkg = await import('../../../rayon_test.js');

and now it works fine. Not exactly sure what went wrong there, and whether it was my fault, but reporting in case this is a bug.
Thanks!

Which bundler did you use? Did you check instruction sections under https://github.com/GoogleChromeLabs/wasm-bindgen-rayon#usage-with-various-bundlers?

If you didn't use an bundler, in particular check out https://github.com/GoogleChromeLabs/wasm-bindgen-rayon#usage-without-bundlers - you need to use no-bundler feature.

@RReverser That was the problem, thank you!


MRG: Remove pytest-sugar

Since pytest 3.10 came out, pytest-sugar is broken:
https://github.com/Frozenball/pytest-sugar/pull/160
For now let's not bother installing it. Once they fix the bug and cut a new version we can add it back. (Seems better than the alternative, namely to pin pytest < 3.10.)

Merging to get things green again


Add (re-implement) "export document(s)" feature

I have dropped this feature when porting Thinlet UI to JavaFX (later, replaced by Swing.)
Thinlet Lule has "Tools > Export" menu. This wiki describes the feature.
https://github.com/DmitryKey/luke/wiki/Exporting-index-to-xml
I would like to re-think this feature (but cannot take enough time for this now.)
When (re)implementing this feature, file format selection (e.g. export to xml, json or csv/tsv) would be desirable.

For contributors: Now Luke is a part of Apache Lucene. Please create an issue (if there is not exist) to Lucene Jira if you want to help with this.


First steps in creating a v2 API

Idea
There are a number of elements of the current RDKit API which I would really like to change. Given that we want to maintain backwards compatibility (and not break people's code) this is impossible with the current API. However, we can start to create a new RDKit API, v2, which addresses some of the irritations while still allowing existing code to work.
Two API things that I would very much like to address are:

Lifetime safety: get rid, to the extent possible, of ownership transfer via naked pointers (i.e. taking/returning a naked pointer and requiring the caller to read the docs in order to know whether or not they own that pointer). I would like the API to follow some simple rules: ownership is transferred via unique_ptrs, ownership is shared via shared_ptrs, and naked pointers are just used when there's no ownership transfer
Functions which take 47 arguments, 45 of which are optional. I would like to bundle all of the optional arguments in some kind of parameters object and  just use that. We have examples where we've done this, like in SmilesToMol(), but I would also like to remove all of the overloads.

Combining those two in a concrete manner, v2 of the API would have a single function named SmilesToMol():
std::unique_ptr<RWMol> SmilesToMol(const std::string &smiles,const SmilesParserParams &ps=SmilesParserParams());

Note that these initial steps are not looking at changing behavior of the underlying code; they just focus on making it easier to use safely.
I'd like to get v2 of the API out there soon, with the clear statement that it will evolve for a bit and so there will be breaking changes for the next couple of releases, so that we can use it within the RDKit itself and start collecting feedback.
Implementation
This particular PR demonstrates how to solve the two problems I listed above while making v2 of the API "opt-in" (maintaining backwards compatibility by default). In order to demonstrate the ideas and still have a manageable chunk to review, this PR only adds the v2 API for the SMILES and SMARTS parsers.
The solution I've arrived at is to add two new namespaces - RDKit::v1 and RDKit::v2 - and to make the v1 version inline so that it is used by default.
As a simple illustration, code which currently looks like this:
namespace RDKit {
 RWMol *MolFromFoo();
}

Turns into something like this:
namespace RDKit {
inline namespace v1{
 RWMol *MolFromFoo();
}
namespace v2{
 std::unique_ptr<RWMol> MolFromFoo();
}
}

Existing code which does: RDKit::MolFromFoo() will continue to work without any modification, but users can opt to use the new API by either being explicit: RDKit::v2::MolFromFoo(), or including using RDKit::v2 at the top of their file and then MolFromFoo() will use the v2 version.
Within this PR all of the v1 functionality is implemented by simply calling the corresponding v2 code and releasing things from the smart pointers
Next steps
If we all agree that this is the way to approach things, I will add something in the documentation as part of this PR and then we can merge this.
The next step would be to take all the other parsing functions and create a form of them which returns unique_ptrs instead of bare pointers. I think that would be a reasonable place to land for the 2024.03 release. A stretch goal for 2024.03 would be to figure out how to do the same thing with the Suppliers.

I will fix the problems with the SWIG builds; they should not prevent the review

@bp-kelley @ptosco @ricrogz @d-b-w   Your feedback and thoughts on this would be great to hear

@greglandrum I very much the RDKit::v2 namespace solution - it is a really neat way to keep backwards compatibility thanks to the v1 namespace inlining. Moving away from naked pointers to unique_ptr and shared_ptr is a great improvement. I do not see problems with the approach that you followed in this PoC, so I may only thank you for the effort you put into this, and sorry for being so late in reviewing!

I have a couple of general questions about the V2 API scheme.

Is this only a C++ thing? Or do we expect Python interfaces to change?

At the moment I would like to limit it to the C++ side. The number of affected users is smaller and Python doesn't have (most of) the memory safety problems anyway because of the way the wrappers are done.

Do you want to restrict this to memory safety, or will other changes happen, too? I've pointed out a couple of places in which an interface change might be helpful.

I think we should feel ok about making interface changes here when it makes sense. I'm starting with the memory safety stuff because I think it's more important and because the fixes make it so much easier to use the code.
We'll have to be careful with behavioral changes since I believe that something very close to 100% backwards compatibility is mandatory here.

@greglandrum I very much like the RDKit::v2 namespace solution - it is a really neat way to keep backwards compatibility thanks to the v1 namespace inlining. Moving away from naked pointers to unique_ptr and shared_ptr is a great improvement. I do not see problems with the approach that you followed in this PoC, so I may only thank you for the effort you put into this, and sorry for being so late in reviewing!

Thanks for the feedback @ptosco !

Ok, looks like we're all at least agreed that this isn't a terrible idea and some of us even think it's a good one. :;-)
I'll merge this to get the ball rolling and then start doing a couple of PRs to apply this type of change to the FileParsers and the reaction processing code. That will be more of the same style change.
I'd love to hear suggestions as to what the next big thing to look at should be. I'm leaning towards ChemicalReaction and/or MolStandardize, but can easily look elsewhere


Low FPS and camera twitch

Hi, I appreciate your great work! But when I tried to run and evaluate the pre-trained model on my PC. I faced low FPS and camera twitch, the running FPS is lower than 10 FPS while facing complex situation.

Also the camera faced frequently twitch during the running. (Means when the vehicle is accelerating, the camera would have a sharp backward blow)

My device is I9-14900k & RTX4090. I would like to ask you if you face this problem too? I would really appreciate your help.

Simulation around 10 FPS is not that unusual I think.
You can measure but TF usually uses in the order of 50ms, and you needs to add CARLA simulation on top of that, which can easily go in the range of 100ms / 10 FPS.
TransFuser is a comparatively fast architecture since it is single frame and uses low resolution cameras.
You second problem is also normal if what you show is the spectator camera.
The spectator camera is not attached to the vehicle and is readjusted after the vehicle moved leading to this twitch.
This should not happen with the cameras mounted on the car.

Simulation around 10 FPS is not that unusual I think. You can measure but TF usually uses in the order of 50ms, and you needs to add CARLA simulation on top of that, which can easily go in the range of 100ms / 10 FPS. TransFuser is a comparatively fast architecture since it is single frame and uses low resolution cameras.
You second problem is also normal if what you show is the spectator camera. The spectator camera is not attached to the vehicle and is readjusted after the vehicle moved leading to this twitch. This should not happen with the cameras mounted on the car.

Thank you for your reply, I appreciate your reply. I am just wondering if I can use more powerful CPU to get higher FPS. AND for my second question, I think the camera in your demo.gif is very stable, did you use the attached camera on car?

CPU performance has not increased much in the recent years and you already seem to have a very good CPU so probably not. Maybe you can buy a better CPU but you also already have a very good GPU so, you would need a server grade GPU.
Don't think that is worth it.
You can use the build in visualization function, to generate stable frames and then convert them to a video with ffmpeg or so.
You need to set debug and save_path to use the visualization here.


Use pretrained models

Is there any way to use pretrained models like fx those from Huggingface?

Not models built with anything but Rubix ML, but you can use shared models that have been trained with Rubix ML.
See this section of the docs for caveats https://docs.rubixml.com/2.0/model-persistence.html#caveats
Starting in ML 3.0, you will be able to save/load any model from the same major version of the library

I'd love it if we can support models exported in the ONNX format: https://onnx.ai/
But we'll need much more contributors to achieve that.

Definitely @DrDub, ONNX support would enable a ton of possibilities for PHP Machine Learning engineers


Functional tests for Semantic Kernel

Closes #766
Purpose

Adds functional tests for semantic kernel

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x] Other... Please describe: Tests

How to Test

pytest -m functional

What to Check

Tests pass

@adamdougal, @cecheta and I had a discussion about the possibility of running the orchestrator tests for all three orchestrator types - langchain, openai_functions and semantic kernel, rather thn just for sematntic kernel.
But at the moment we're spinning up a new mock server instance for each config combination - making it hard to test lots of them. After discussing possible solutions, I opened (an issue)[https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/issues/801] to solve this.


Update changelog for 1.1.3 [skip-ci]

Coverage increased (+4.3%) to 35.694% when pulling 7c74b2c159e7287a81ce27c41de7b48750a32ff7 on fcastilloes:master into 19efff5f50ebdce0f6181a0dec43ce26200cc973 on kusanagi:master.


a) Update to the latest SharpFont code. b) Use structs instead of classes for perf.

Please see the individual commits for detailed notes.

Looks good! Thanks!


feat: Add templates to the wesbite

Currently we are functioning on a single resume template. We need to provide users multiple templates to choose from.

[ ] Design templates on figma
[ ] Provide working code for the design

i am interested in contributing in your project .i think your project has great potential

i have done UI-UX before and i also have  the experience of working with figma and i have made one website focusing on resume maker so i know the different designs of resume so do let me know if it finds you suitable

Sure @ShubhiGulati go ahead and give some mockups then we can code it.

@ShubhiGulati You on it?

yes sir i can do it

This issue has been automatically closed because it has been inactive for more than 30 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you!

Hello @ashutosh-rath02! Your issue #2 has been closed. Thank you for your contribution!


Musik-Videos doesnt work

Hey guys,
I found this tool to download youtube videos, and for the most its working, but when I want to download a Musik-Video this happens:
youtube-dl -F --no-check-certificate  --verbose https://www.youtube.com/watch?v=r0J-vNlgWic
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-F', '--no-check-certificate', '--verbose', 'https://www.youtube.com/watch?v=r0J-vNlgWic']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.03.14
[debug] Python version 3.6.7 (CPython) - Linux-4.20.0-042000-generic-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: ffmpeg 3.4.4-0ubuntu<IP_ADDRESS>, ffprobe 3.4.4-0ubuntu<IP_ADDRESS>, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] r0J-vNlgWic: Downloading webpage
[youtube] r0J-vNlgWic: Downloading video info webpage
[youtube] r0J-vNlgWic: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {18} signature length 40.41, html5 player None
[youtube] r0J-vNlgWic: Downloading player https://www.youtube.com/yts/jsbin/player_ias-vflSzU_20/en_US/base.js
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by RegexNotFoundError('Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 785, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 440, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1899, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1201, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
youtube_dl.utils.ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by RegexNotFoundError('Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
but others works fine:
youtube-dl -f 299 --no-check-certificate https://www.youtube.com/watch?v=Db-tuTCsoWU&t=15s
[youtube] Db-tuTCsoWU: Downloading webpage
[youtube] Db-tuTCsoWU: Downloading video info webpage
[youtube] Db-tuTCsoWU: Extracting video information
WARNING: Unknown codec av01.0.05M.08
WARNING: Unknown codec av01.0.05M.08
WARNING: Unknown codec av01.0.05M.08
WARNING: Unknown codec av01.0.05M.08
[download] Destination: Game Theory - Fortnite is Stealing...AGAIN!! (The Fortnite Dance Controversy)-Db-tuTCsoWU.mp4
[download] 100% of 298.23MiB in 03:23
Why does youtube-dl want to download "js player vflSzU_20" but not when its working. how can I forbid the use of the js player, its seems to create this issue.
Thank you for your help.

It seems that it cant get the player, so it cant get the download URL. But with this script, found earlier, I where able to get the download URL. I cant use it because

403 Forbidden

`#!/usr/bin/perl
use strict;
use warnings;
Two arguments
$1 YouTube URL from the browser
$2 Prefix to the file name of the video (optional)

Collect the URL from the command line argument
my $url = $ARGV[0] or die "\nError: You need to specify a YouTube URL\n\n";
Declare the user defined file name prefix
my $prefix = defined($ARGV[1]) ? $ARGV[1] : "";
Download the HTML code from the YouTube page
my $html = wget -Ncq -e "convert-links=off" --keep-session-cookies --save-cookies /dev/null --no-check-certificate "$url" -O-  or die  "\nThere was a problem downloading the HTML file.\n\n";
Collect the title of the page to use as the file name
my ($title) = $html =~ m/(.+)</title>/si;
$title =~ s/[^\w\d]+/_/g;
$title =~ s/youtube//ig;
$title =~ s/^//ig;
$title = lc ($title);
Collect the URL of the video
my ($download) = $html =~ /"url_encoded_fmt_stream_map"([\s\S]+?),/ig;
Clean up the URL by translating Unicode and removing unwanted strings
$download =~ s/:\ "//;
$download =~ s/%3A/:/g;
$download =~ s/%2F///g;
$download =~ s/%3F/?/g;
$download =~ s/%3D/=/g;
$download =~ s/%252C/%2C/g;
$download =~ s/%26/&/g;
$download =~ s/sig=/signature=/g;
$download =~ s/\u0026/&/g;
$download =~ s/(type=[^&]+)//g;
$download =~ s/(fallback_host=[^&]+)//g;
$download =~ s/(quality=[^&]+)//g;
Collect the URL and signature since the HTML page randomizes the order
my ($signature) = $download =~ /(signature=[^&]+)/;
my ($youtubeurl) = $download =~ /(http.+)/;
$youtubeurl =~ s/&signature.+$//;
Combine the URL and signature in order to use in Wget
$download = "$youtubeurl&$signature";
A bit more cleanup
$download =~ s/&+/&/g;
$download =~ s/&itag=\d+&signature=/&signature=/g;
Print the file name of the video collected from the web page title for us to see on the CLI
print "\n Download: $prefix$title.webm\n\n";
Download the file using Wget and background the Wget process
system("wget -Nc -e "convert-links=off" --load-cookies /dev/null --tries=50 --timeout=45 --no-check-certificate "$download" -O $prefix$title.webm &");
EOF #####`
I get :
--2018-12-31 22:23:20--  https://r1---sn-oxujvavbox-jboe.googlevideo.com/videoplayback?clen=12290315&mime=video%252Fmp4&ipbits=0&fvip=1&requiressl=yes&ratebypass=yes&txp=5431432&mm=31%2C29&pl=47&sparams=clen%2Cdur%2Cei%2Cgir%2Cid%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cexpire&source=youtube&c=WEB&id=o-AH_qxQHp8VJKQ1xaIpg24vnQmFcS0iQ1NPgDeHvQF1LZ&expire=1546313006&ip=2001%253A4dd7%253A3c2b%253A0%253A1939%253Aa5af%253A85fa%253A5956&lmt=1546240551163818&ei=zogqXPXKGdCsgQeXoImAAg&dur=213.832&mt=1546290375&mv=u&ms=au%2Crdu&key=yt6&mn=sn-oxujvavbox-jboe%2Csn-5hne6nsd&itag=18&gir=yes&s=6F26204FE8195BA8AB30F5E0616D058743C11CB8.0053E5805D6927E949E1BA7C336DA8455B0F1A2B3&sp=signature&
Auflösen des Hostnamens r1---sn-oxujvavbox-jboe.googlevideo.com (r1---sn-oxujvavbox-jboe.googlevideo.com) … 2001:4dd0:200:310::c, <IP_ADDRESS>
Verbindungsaufbau zu r1---sn-oxujvavbox-jboe.googlevideo.com (r1---sn-oxujvavbox-jboe.googlevideo.com)|2001:4dd0:200:310::c|:443 … verbunden.
WARNUNG: Das Zertifikat von r1---sn-oxujvavbox-jboe.googlevideo.com kann nicht geprüft werden, ausgestellt von »CN=Google Internet Authority G3,O=Google Trust Services,C=US«:.
Die Autorität des Ausstellers des Zertifikates kann lokal nicht geprüft werden. (
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 403 Forbidden
2018-12-31 22:23:20 ERROR 403: Forbidden.

``

Update youtube-dl with youtube-dl -U (or if you used a package manager use its update function).

I have just installed it, so its up-to-date, checked it before i posted it.

Your output says [debug] youtube-dl version 2018.03.14, so it's not up to date. The current version is 2018.12.31. Try running youtube-dl -U.

Your output says [debug] youtube-dl version 2018.03.14, so it's not up to date. The current version is 2018.12.31. Try running youtube-dl -U.

Hmm so

youtube-dl: error: youtube-dl's self-update mechanism is disabled on Debian.
Please update youtube-dl using apt(8).
See https://packages.debian.org/sid/youtube-dl for the latest packaged version.

Its an old version in the Ubuntu repro

You might have to update apt.
sudo apt update
Then run sudo apt install youtube-dl again.

If that doesn't work uninstall from apt and try installing with pip.

updated apt, but the version didnt changed.
 Ubuntu wants that I install it first via snap or apt.
How can I use pip installed applications?

It's located in ~/.local/lib/python2.7/site-packages, so either run it with ~/.local/lib/python2.7/site-packages/youtube-dl or add ~/.local/lib/python2.7/site-packages to your path.
Or just install it directly:
sudo wget https://yt-dl.org/downloads/latest/youtube-dl -O /usr/local/bin/youtube-dl
sudo chmod a+rx /usr/local/bin/youtube-dl

Ok downloaded it:
Thank you very much! Now it works!

``