Is this still in maintenance?

Just would like to know if this is still in maintenance, or if there is some future plan.
And can I use 0.7.10 from ariens/Krackle in production env?
Thanks.

                                                                                Hey there, Krackle is still very much in maintenance and a new version is dropping alongside kaboom and klogger imminently. Check back by end of week for the latest releases.                                                                                From: DeanHereSent: Tuesday, April 21, 2015 9:33 PMTo: blackberry/KrackleReply To: blackberry/KrackleSubject: [Krackle] Is this still in maintenance? (#4)Just would like to know if this is still in maintenance, or if there is some future plan.

And can I use 0.7.10 from ariens/Krackle in production env?
Thanks.
—Reply to this email directly or view it on GitHub.

thanks.

Just pushed loads of updates, and included a the JARs in the release.


docs: "Getting Started" docs page not on navigation tree and using pre-v3.0.x API

As of 53226cddfa74d5cbd4f2e1940062c172c20e6489, the "Getting Started" docs page, which includes an example of transforming a PHYS dataset and applying calibrations is not listed anywhere on the docs navigation tree or on a subtree.
https://github.com/ssl-hep/ServiceX_frontend/blob/53226cddfa74d5cbd4f2e1940062c172c20e6489/docs/index.rst?plain=1#L61-L74
This means that the only way to find it is to either already know that it exists, or to search for it.
The information on this page should get added to the navigation tree or should get moved to a new page that is already on the navigation tree.

Also the examples in docs/getting_started.rst aren't using the v3.0.0 API,
https://github.com/ssl-hep/ServiceX_frontend/blob/53226cddfa74d5cbd4f2e1940062c172c20e6489/docs/getting_started.rst#L22-L31
, so they should get updated.

Hi @matthewfeickert - I think page is intentionally not visible and is more of a placeholder for something we might put in later. @kyungeonchoi and @gordonwatts can confirm if we want to keep something like this or just delete the thing. But as you note it is not linked to by anything.

I think page is intentionally not visible and is more of a placeholder for something we might put in later.
...
But as you note it is not linked to by anything.

Thanks for the info. It would be useful to have some information in the public docs on how to use ServiceX to do transformations with PHYS, so regardless of if it is this page or another, it would be great to see this.

Hi @matthewfeickert - that page was intentionally hidden and kept for a while as a reference. I believe the latest client documentation includes the func-adl example for PHYSLITE and a link to the full func-adl documentation. Please feel free to open this ticket again.

@kyungeonchoi My point in https://github.com/ssl-hep/ServiceX_frontend/issues/492#issue-2565142416 is that there isn't anything in the docs that shows how to go about applying calibrations.

@matthewfeickert - that's in the func-adl documentation. IMO, a separate (detailed) documentation for func-adl pro users (who want to do calibration on PHYS with ServiceX) makes more sense.


Bring errors to single format

Currently validation errors and all others very different. We need specify single format and use them.

Also need translation errors feature. Client sends request with language field and backend throws translated error.
Something like this:
{   status: 404,   message: %translated error show to user%,   error: %developer error with details%,   .... }


Issue with k8s.io/docs/tasks/tools/install-minikube/

I installed kubectl and minikube as shown on https://kubernetes.io/docs/tasks/tools/install-minikube/.  When I start minikube with --vm-driver=none (I'm running on a virtual machine) I get this error:
$ sudo minikube start --vm-driver=none
😄  minikube v1.6.2 on Ubuntu 19.10
✨  Selecting 'none' driver from user configuration (alternates: [])
⚠  Specified Kubernetes version 1.10.0 is less than the oldest supported version: v1.11.10
💣  Sorry, Kubernetes 1.10.0 is not supported by this release of minikube
Is this a problem with Ubuntu 19.10, or with running minikube on a virtual machine?

It looks like the problem was that I had an old /root/.minikube directory.  Once I removed that directory minikube tried but failed to start with this error:
Error starting cluster: running cmd: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm init phase certs all --config /var/tmp/minikube/kubeadm.yaml": /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm init phase certs all --config /var/tmp/minikube/kubeadm.yaml": exit status 1
stdout:
[certs] Using certificateDir folder "/var/lib/minikube/certs"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
stderr:
W0110 13:53:06.531592    6051 common.go:77] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta1". Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.
W0110 13:53:06.532094    6051 common.go:77] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta1". Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.
W0110 13:53:06.533419    6051 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0110 13:53:06.533440    6051 validation.go:28] Cannot validate kubelet config - no validator is available
error execution phase certs/apiserver-kubelet-client: [certs] certificate apiserver-kubelet-client not signed by CA certificate ca: crypto/rsa: verification error
To see the stack trace of this error execute with --v=5 or higher
😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose
❌  Problems detected in kube-addon-manager ["c7ccb7eb00cc"]:
error: You must be logged in to the server (error when retrieving current configuration of:
error: You must be logged in to the server (the server has asked for the client to provide credentials)
error: You must be logged in to the server (the server has asked for the client to provide credentials)
❌  Problems detected in kube-apiserver ["c91043e54554"]:
I0110 20:52:44.283421       1 log.go:172] http: TLS handshake error from <IP_ADDRESS>:47838: remote error: tls: bad certificate
I0110 20:52:44.483603       1 log.go:172] http: TLS handshake error from <IP_ADDRESS>:47846: remote error: tls: bad certificate
I0110 20:52:44.549909       1 log.go:172] http: TLS handshake error from <IP_ADDRESS>:47848: remote error: tls: bad certificate

@dwschulze can you please provide these details to replicate the issue further.
The exact minikube start command line used
The full output of the minikube start command, preferably with --alsologtostderr -v=4 for extra logging.
The full output of minikube logs

/triage needs-information


Fix code example

Added missing import.
Just found out... the newline at the end of file was added by vim automatically. Hope this does not matter.
Before submitting a pull request, please make sure the following is done:

Fork the repository and create your branch from master.

Run the build.py and test.py scripts.

If you are fixing something, add tests that fail in the current version and pass in yours.

If you're developing a new feature open an issue first to discuss it. Some features may be useful to you but harmful to others be it because of performance, new dependencies or different perspectives.

One more time: Don't forget to add tests.

Ensure the entire test suite is passing and overral performance is not degraded.

Schemas doc is a bit outdated... so don't worry about it, I'll push updates soon to the schema docs... many thanks for the fast contribution :)

Okay, I will hold on until something really broken.

I found more typos in schemas section, instead wasting your time with trivia PRs, I will mark them here for your later reference.
Extra 'outside' in this line:
https://github.com/vibora-io/vibora/blob/1933b631d4df62e7d748016f7463ab746d4695cc/docs/schemas/fields.md#L14
I think if either 0, 1 or 2 parameters are allowed, "and receive one up to two parameters."  is better wording, if at least one parameter is required (I don't know ATM, haven't read the source code, yet), something like "and receive one or two parameters." might be more clear.
Also spelling out the whole word of 'async' and 'sync' looks better to me here, since you are not referring python keyword.
"async" -> "asynchronous"
"sync" -> "synchronous"
https://github.com/vibora-io/vibora/blob/1933b631d4df62e7d748016f7463ab746d4695cc/docs/schemas/fields.md#L22


Dayemet source in notebook 01-download-Daymet4

@fnattino I want to use the code sample in the notebook 01-download-Daymet4 to download daymet data on my own machine. In the notebook,  ornl_daac_root is set to "https://thredds.daac.ornl.gov/thredds/fileServer/ornldaac/1840/". This returns FileNotFoundError. If I replace 1840 with 2129, it works fine, see data of 2129. I am wondering if we need a login to access 1840? any idea?

Hey @SarahAlidoost ! I suspect this has to do with the fact that new versions of the Daymet dataset have been published - I have downloaded version 4.2 (https://doi.org/10.3334/ORNLDAAC/1840), while version 4.4 seems to be available from November 1 (https://doi.org/10.3334/ORNLDAAC/2129). Apparently the older versions of the dataset are not kept online - which might be an additional reason in favour of making a "local" copy of the dataset.


.Net: Add a function that accepts a chat history (or group chat) object and takes the last N messages

The following handlebars template should be possible...
{{messages (topNMessages chatHistory 20)}}
This would render the top 20 messages in the prompt template

I saw handlebars was deprecated, and also now all of use use native model plugins, I think we need a pass to pass history into plugin. And also system message

This can be done by creating a method and registering with the Kernel


/signin-cas?state=xxx

.net core 3.1
Jump after authentication / sign CAS? State = XXX what's wrong with this address?

You're going to have to give us more information.  I have no clue what you just typed in.

.cn/signin-cas?state=CfDJ8FlcKjJTmoxCjlUlBq-h_aO8hVRppinBN07tRW
return
Status Code: 404; Not Found      Do you have a. Net core SDK?
------------------ 原始邮件 ------------------
发件人:                                                                                "apereo/dotnet-cas-client"<EMAIL_ADDRESS>发送时间: 2020年10月16日(星期五) 下午3:11
收件人<EMAIL_ADDRESS>抄送: "Always"<305353941<EMAIL_ADDRESS>主题: Re: [apereo/dotnet-cas-client] /signin-cas?state=xxx (#113)
You're going to have to give us more information.  I have no clue what you just typed in.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

This specific project does not work with .NET Core projects.


Improve error messages around part discovery

One particular error message gets improved.
Other error messages now get wrapped in another InnerException layer so that more context is available in the overall error message. Specifically, an error while scanning a member now reveals which member was being scanned.

Codecov Report

Merging #288 (1a6e182) into main (7205d37) will decrease coverage by 0.42%.
The diff coverage is 92.59%.

@@            Coverage Diff             @@
##             main     #288      +/-   ##
==========================================
- Coverage   89.65%   89.22%   -0.43%
==========================================
  Files          87       87
  Lines        6088     6096       +8
==========================================
- Hits         5458     5439      -19
- Misses        630      657      +27

Impacted Files
Coverage Δ

...mposition/Configuration/AttributedPartDiscovery.cs
95.91% <91.66%> (-0.91%)
:arrow_down:

...osoft.VisualStudio.Composition/Strings.Designer.cs
69.04% <100.00%> (+0.37%)
:arrow_up:

....Composition.AppDomainTests/OpenGenericExport`1.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...mposition.AppDomainTests/ExternalExportOnMember.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...mposition.AppDomainTests/ExternalExportWithLazy.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...osition.AppDomainTests2/CustomMetadataAttribute.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...dTypeReceiver/PartThatImportsLazyOfEmbeddedType.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...rtThatLazyImportsExportWithMetadataOfCustomType.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...atLazyImportsExportWithTypeMetadataViaTMetadata.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...tLazyImportsExportWithTypeMetadataViaDictionary.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


zsh: use .zshenv for env vars

Turns out zsh uses .zshenv file to set environment variables, the previous approach didn't work. Tested on zsh v5.4.1.

Rebased into master in 910cdc0537d7ed3482a77e89756de36ddfccd300. Thanks for fixing the problem!


about cGAN

in this book chap 6,The dcgan,I try to change it to cDGCAN  that can generate different food image
the code is wrong,do you have the cDCGAN code?

Hey @kunal-savvy, @Dheeraj-Arremsetty would you guys be able to assist our reader regarding this problem?


Proposal to add query filters : includeFields and excludeFields

Even if it is possible to restrict what fields to display through the schema (aka api: false), sometimes a query needs a whole document, and sometimes another query needs only a few fields from the same document.
For performance reason, I suggest to add a query filter includeonly.
Example: /api/v1/products?includeonly=type,slug,excludedFieldInSchema will return
[
  {
    _id: 'whatever_id',
    type: 'product',
    slug: 'product-key-product',
    _originalWidgets: {}
  }
]

(that is to say required fields but not previously excluded fields in the schema).
I added a test and updated the documentation too.

@boutell Yes, I thought the same about GraphQL 😄

Sorry for the late reply. I applied self.apos.launder.string to req.query.includeFields and req.query.excludeFields

Thanks!


How to generate predicted frame?

I understand the ground truth frame is generated by taking the two nearest neighbors of each atom. How is the predicted frame generated? Do you perform two nearest neighbors on the predicted coords?

Please see: https://github.com/lucidrains/alphafold3-pytorch/blob/e54c050ce62c449a720ec0cbe327c3da670b9573/alphafold3_pytorch/alphafold3.py#L5860


Support handling of "unwrapped" POJOs

(note: copied from https://github.com/FasterXML/jackson-databind/issues/271)

For example :
class A { public String text = "text"; }
class B { public @JsonUnwrapped A a = new A(); }
would serialize as :
{"text":"text"}
and the schema would be :
{"type":"object","properties":{"a":{"type":"object","properties":{"text":{"type":"string"}}}}}
but, this is not consistent with the serialized form, the schema should be this :
{"type":"object","properties":{"text":{"type":"string"}}}

Ok: should all be fixed now, as per #61, thanks to @ciderale. Will be in 2.5.2 (and, if it gets released, 2.4.6).


[ConstraintSystem] Fix the ordering of functions with optional parame…

…ters.
Treat non-optional generic parameters as being more specialized than
optional generic parameters, and penalize any solutions that involve
generic arguments that are themselves Optional.
By doing these things, we can remove the special-cased code for the
two overloads of ?? in the stdlib, instead treating the (T?, T)
overload as better than the (T?, T?) overload except where a user
actually passes an optionally-typed value as the second parameter.
Fixes: rdar://problem/19748710

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

As my latest test update shows, the change for Any vs. Any? introduces another change, which is that we now prefer f<T>(x: T) over f(Any), which seems to me like a reasonable choice since you can select the second overload by doing f(arg as Any) but under the old scheme you can never select the f<T>(x: T) variant.
@DougGregor what do you think?

@swift-ci Please test source compatibility


Nested navigation menu

Feature Requests
I'd like to create nested navigation menu with MDL like Google Analytics provides. Any plan to support nested navigation menu?
Example

While it's a nice feature it's been stated that they don't plan to add to MDL and Google Analytics online really isn't a good example of Material Design


trunc(vector_type) broken in shaders (causes runtime GLSL compile failure)

Operating system or device - Godot version:
Godot 2.2a linux x11 AMD FX8320 (8-core) 16GB RAM
Issue description (what happened, and what was expected):
The following code fails to compile in a shader:
F-shader (also triggers on V-shader - I never tested with L-shader):
vec3 vector_with_floaties=vec3(1.41421,2.71828,3.14159);
vec3 integral_vector=trunc(vector_with_floaties); // <-- fails to compile
// workaruond: vec3 integral_vector=vector_with_floaties-fract(vector_with_floaties);
No errors occur in the editor but the scene will have the tell-tale dull-grey shade (indicating shader didn't run) errors messages will have logged in Debug and the errors are visible in full when using the console (it's not possible to read the error in the Debug window due to the huge one-liner error message in a view that has no scrollbar).
Steps to reproduce:
See above.
Link to minimal example project (optional but very welcome):
See above.

The full error can be seen by hovering over the message:
Type: Error
Description:
Time: 0:00:00:0400
C Error: MaterialShaderGLES2: Fragment Program Compilation Failed:
0(857): error C7532: global function trunc requires "#version 130" or later

C Source: drivers/gles2/shader_gles2.cpp:491
C Function: ShaderGLES2::get_current_version

Godot Engine uses #version 120.
GLSL 1.30 was released later than OpenGL ES 2, so I'm not sure if trunc can be made available before Godot 3.0 with OpenGL ES 3

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

@vnen @akien-mga This issue is fixed in latest master, should be closed.

I just ran into this issue today on 3.2.1.stable, but only on the HTML5 build. Should I create a new issue for it?

@kcaze Since this issue is very old, I'd create a new issue for it.


[utility] scp/rsync glob local paths but don't glob remote paths

Adds a function which wraps rsync and scp so that remote paths are not globbed
but local paths are globbed. This is because the programs have their own
globbing for remote paths. The wrap function globs args starting in / and ./
and doesn't glob paths with : in it as these are interpreted as remote paths
by these programs unless the path starts with / or ./
Fixes issue #1125

Black magic! But pretty awesome black magic. Nice improvement over the samples I've seen elsewhere as well!

Yeah, I saw some alternatives but they had the issue that they would glob when anything had a : colon in it, so I played around with the commands and it seemed they recognized : specially as well, but having ./ or / overrode that. Wanted it to work in practically all conditions instead of just most all.

I just hit this very problem. After searching around for a better solution than having to remember \scp when I wanted globbing on local paths, I found this PR and realised that I last fetched prezto 3 days ago and must have just missed out on this merge.
Anyway, long story short, thanks for this, it's a great fix :D


[Bug] Play from context menu doesn't work in TV Shows library

The bug
In TV Shows library, when choose "Elementum Play" in the context menu, it raises an error notification with the message: "Elementum - Not Found".
Expected Behavior
It should run the search and open the results screen as usual.
Current Behavior
It raises an error notification with the message: "Elementum - Not Found".
Steps to Reproduce (for bugs)

Go to TV Shows library in kodi
Stand on an episode
Open the context menu and choose "Elementum Play"

Notes:

In the Movies library it's ok without an error.
The library based on another addon, I'm just trying to run it with the Elementum context menu option.

Your Environment

Version used: 0.0.70
Environment name and version: Kodi 17.6
Operating System and version: Win10
Link to Kodi debug log: https://paste.ubuntu.com/p/DdGZVNfjs6/
--- In the log there is example with an episode of the TV Show "Blindspot"
--- In the log there is example with a the movie "Truth or Dare"
--- Focus at this time stamp: 20:54:30.401 T:19152

To search for movie/episode we first need to find it's TMDB id. In case shows were scraped not by TMDB and strm file not generated by Elementum - it will likely fail to find correct TMDB id.

So we actually back to this old issue with TMDB, again.
Most of the the people and other addons are using TVDB or IMDB for tvshows.
But we already discussed a lot on this issue in another issue before.
I'm using The TVDB addon as my tvshows info provider.
If you could put in as a future plan to add additional support also for tvdb for TV Shows it could be nice.

maybe it could be ported from https://github.com/scakemyer/plugin.video.quasar/blob/126b5b36982603640ad6b8d041ce208de4cdcfe4/resources/settings.xml#L8

Most of the the people and other addons are using TVDB or IMDB for tvshows.

I would be much glad if you just you your favourite addons and won't force this addon to be like any other.

I don't understand why you always think I'm against you or something.
I'm not trying to force you to anything. This is not was the purpose of my words. I want to use Elementum, and I'm sure there is a reason why the others are preferring using TVDB.
It would be nice if you could explain from your side why it's a problem (Complexibility in development or something else) instead of just giving an answer like "This is what I want and that's it".


fix: Disable dynamic page validator tests

Disables the above tests even earlier, speeding up the process.
They aren't running in CI/CD pipelines anyway as:

They need updating
The data export is a manual process

@jimwashbrook - I think this is the right decision for now

@jimwashbrook - I think this is the right decision for now

I agree but my concern is that it won't actually fix the problem but we'll see!


Create meta schema for ABI

To be able to clearly indicate what the ABI can look like, it would be beneficial to have some schema that describes the format.
Low priority, especially until things are fully stabilized, but opening to track.
cc @itegulov @zcstarr

This will be great, I think with a metaschema, it'll allow the ecosystem to build around it. You could also assuming it's JSON just apply the meta schema to schemas to do abi validation, on the consumer side.
So in the event that the ABI lives outside of the wasm, building a validator just becomes reading the schema file and applying with the json schema validation tool of your choice.
ex. would be using AJV to validate ABIs uploaded to a block explorer(something an etherscan would do)


JSON parser has problem with parsing array of elements with key equal "properties"

From<EMAIL_ADDRESS>on April 21, 2015 11:07:36

Prepare JSON like:
{
"features": [
{
"type": "Feature",
"geometry": {
"type": "GeometryCollection",
"geometries": [
{
                 "type": "Point",
                 "coordinates": [
                     19.883992823270653,
                     50.02026203045478
                 ]
             }
         ]
     },
     "properties": {
         "gridId": 6
     }
 },
 {
     "type": "Feature",
     "geometry": {
         "type": "GeometryCollection",
         "geometries": [
             {
                 "type": "Point",
                 "coordinates": [
                     19.901266347582094,
                     50.07074684071764
                 ]
             }
         ]
     },
     "properties": {
         "gridId": 7
     }
 }

]
} 2. Here are two examples of code. First one is working, second is not.
List typeList= JSON.jsonPath().get("features.geometry.type"); //It's working
List gridIdList= JSON.jsonPath().get("features.properties.gridId"); //It's not working

In second case I should get list of all gridIds but its not working, it returns null. I
assumed it is connected with property name = "properties". The example above is valid GeoJson format.
What is more interesting I can do something like that and it's working:
Integer gridId = JSON.jsonPath().get("features[0].properties.gridId");
Version: 2.4.0
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=397

From<EMAIL_ADDRESS>on June 07, 2015 09:49:23
As a workaround I think you can do "features.'properties'.gridId"

This is now fixed in master


new feature eventReminder added

Added new feature to send an event reminder to a thread. It only creates a new event, but does not update an old one, if there already is an event under the same name.

This doesn't work in python2.7, but I've merged it anyways, because I don't have an easy (nor a hard) fix


Include NotFoundError in type definition file

The NotFoundError that is currently exported in the source file, but not from the type definition file

Pull Request Test Coverage Report for Build 23

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

Totals

Change from base Build 22:
0.0%

Covered Lines:
77

Relevant Lines:
78

💛  - Coveralls

@kelvien, thank you for your contribution.

@nareshbhatia, thank you for the great library!
Should I also include version upgrade in the package.json for the next release?

@kelvien did that already - v1.1.2 published


Search Failed: Make sure that your index has a 'default' sementic configuration.

Deployed using redis openai template and followed every step from the 4th video, and getting the same response for every request - 'Search Failed: Make sure that your index has a 'default' sementic configuration'. Why is this happening and how can I fix it?

Deployed everything once again using vector store deployment template, used pre-built vector search pipeline, uploaded document.

From the screen shot it looks like the pipeline name is blank?  Are you internal MS?  It's hard to tell from the screen.  Maybe we could do a screen share.

Hi James, we can certainly try screen share and maybe you can see where's the problem coming from.
About the blank pipeline it is one the pre-built pipeline which is in three stages and it's last stage name is '-stage3' which you can see is selected as the vector index in the screenshot

The intention is that you put a name into the input before creating the pipeline.  it uses that name in several places.  It should create "example-stage1, example-stage2...."
I'm having capacity issues today and not able to test all of the templates.  It looks like there was another round of model additions and deletions.  When they remove one it breaks the deployment templates.


DXCDT-515: Client grants resource export support

🔧 Changes
Introducing support for exporting the auth0_client_grant resource with the reverse terraform functionality.
The output will appear like this:
import {
  id = "cgr_1WD0mr76sNmRi0Hq"
  to = auth0_client_grant.BZRIum1HFFj1x_httpstravel0usauth0comapiv2
}

import {
  id = "cgr_OqbXFjrBsN1qSwty"
  to = auth0_client_grant.hvxA5ojdxUw_httpstravel0usauth0comapiv2
}

Admittedly, the formatting of the audience, usually a URL, is not pleasant but this will be corrected in a follow-up PR which will clean-up all resource names.
📚 References
Related PRs: #808, #797, #810, #809 #812 #811
🔬 Testing
Adding unit tests, manually verified.
📝 Checklist

[x] All new/changed/fixed functionality is covered by tests (or N/A)
[x] I have added documentation for all new/changed functionality (or N/A)

Codecov Report
Patch coverage: 89.47% and project coverage change: +0.08% :tada:

Comparison is base (062091f) 72.10% compared to head (56119fb) 72.18%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #815      +/-   ##
==========================================
+ Coverage   72.10%   72.18%   +0.08%
==========================================
  Files          91       91
  Lines       11474    11531      +57
==========================================
+ Hits         8273     8324      +51
- Misses       2696     2702       +6
  Partials      505      505

Files Changed
Coverage Δ

internal/cli/terraform.go
65.51% <0.00%> (-1.55%)
:arrow_down:

internal/cli/terraform_fetcher.go
100.00% <100.00%> (ø)

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


ocr click

hello
is it possible to execute the click command with ocr?
an example is from the ui.vision tool

thanks

Hi @marcelocecin, yes this can be done in TagUI, without the file or OCR or actions limit in UI.Vision free version.
Here's the example on the TagUI GitHub page - https://github.com/kelaberetiv/TagUI#click-text-using-ocr
And here's a video with a couple of demos of using this feature - https://www.youtube.com/watch?v=hQ1TZv7BjAk

perfect
thanks !


"Failed to execute" error when calling contract method

I am trying to implement a Proxy contract that uses delegatecall to proxy method calls to a proxied contract. When I attempt to call one of the proxied method await proxyContract.synthetixProxy().call();, tronweb returns "Failed to execute" and its transaction object looks like:
{ visible: false,
  txID:
   'ca5bc1666d60656d245379fe54336a2e17950963d5c5f5a0b4cc6627650d2e51',
  raw_data:
   { contract: [ [Object] ],
     ref_block_bytes: '3f09',
     ref_block_hash: '3ac9c15edcb67855',
     expiration:<PHONE_NUMBER>000,
     fee_limit:<PHONE_NUMBER>,
     timestamp:<PHONE_NUMBER>105 },
  raw_data_hex:
   '0a023f0922083ac9c15edcb6785540d0b8ed9a8b2e5a6d081f12690a31747970652e676f6f676c65617069732e636f6d2f70726f746f636f6c2e54726967676572536d617274436f6e747261637412340a1541a8a07f09def5e6a4462df90068c11abf6224e865121541337f3081a1fd68f222ccc0c398691ccf811e734b2204bdd1248270a9f4e99a8b2e90018094ebdc03' }

I am not sure how to further debug this issue. From what I understand, the problem is that the transaction does not contain a constant_result property. Why not? How can I debug this issue... I'm lost.
I could provide full code to reproduce if it helps.

I think I figure the issue.

could you give the solution pls ?

If the ABI isn't published, we should use triggerConstantContract instead of triggerSmartContract. right?
https://github.com/tronprotocol/tips/issues/31
https://stackoverflow.com/questions/64121820/how-to-call-balanceof-method-for-non-published-abi

Just add  a { _isConstant: true } using call()
await proxyContract.synthetixProxy().call({ _isConstant: true });


add colors and transparency based on pose confidence scores

updates to simple_2d_detection_overlay.cxx to visualize the confidence values as transparency and sets colors for joints

I'm not sure how this change has pushed the docker image size above build-able, so I'm going to assume that's an external issue and not consider that as part of this PR.


Exception IOError: (9, 'Bad file descriptor')

go 1.3.3 linux/amd64 python 2.7.8.
On exit, novm create spits out lots of errors.
$ novm create --name test --nofork --terminal --com1 --nic tapname=pw-tap,ip=<IP_ADDRESS>/24
[... snip ...]
Exception IOError: (9, 'Bad file descriptor') in <bound method _TemporaryFileWrapper.__del__ of <closed file '<fdopen>', mode 'w' at 0x7fc81c4a8d20>> ignored
close failed in file object destructor:
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
IOErrorclose failed in file object destructor:
IOError: [Errno 9] Bad file descriptor:
[Errno 9] Bad file descriptor
close failed in file object destructor:
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
IOError: [Errno 9] Bad file descriptor
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor
close failed in file object destructor:
IOError: [Errno 9] Bad file descriptor

Apologies, the original post missed out some details. I've edited it to add the command run and a description of the bug.

More details that I neglected to mention.
I was trying to run novm as a user. I now think this error is likely happening because dnsmasq is failing and its stdin/stdout/stderr are set to PIPEs which are never used:
https://github.com/google/novm/blob/master/novm/net.py#L188-L190
It may be desirable to see if dnsmasq exits, and if so, show some sort of warning/error.

Hm, I take it back. It happens even if I'm not using dnsmasq.
It always seems to be fd number 9 when it happens.

Tidying up my personal issues list, so closing this. Please create a new issue if you're still interested in tracking it.


Fix cache-hit output when cache missed

Description

fix https://github.com/actions/cache/issues/1334
According to the README, if the cache was not found, the output should be 'false'. However, it actually returned an empty string. This seems to be due to the behavior of GitHub Actions to return an empty string if the output is not defined. Please see these conversations.
I would like to change the code to return 'false' when the cache is not found, per the README.
Motivation and Context

In PR #1263, a README correction is suggested. This is a great initiative, thank you. However, to avoid confusion, how about changing the implementation instead?
How Has This Been Tested?

The issue was caused by not defining an output for cache-hit when the cache was not found, and then returning. Therefore, I will set the output before returning.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (add or update README or docs)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hi, @bethanyj28
I would like to request a reviewer for this pull request. If you are not the maintainer, could you please recommend a suitable reviewer?
Thank you very much!

@joshmgross
I would like to request a reviewer for this pull request. If you are not the reviewer, could you please recommend a suitable reviewer?
Thank you very much!

I tested the implementation of this PR by actually using it. As expected, it was confirmed that ‘false’ is returned when the cache is not found.
v4 test : https://github.com/fchimpan/cache-pr-1404-test/actions/runs/9606510227
This PR test : https://github.com/fchimpan/cache-pr-1404-test/actions/runs/9606510228

Hi @joshmgross ,
I’ve made the necessary changes. Could you please review the code?
Thank you!

Comment: The ternary logic which this patch removes was a useful (but -granted- undocumented and broken) API to detect whether restore-keys was used.
E.g.,
steps:
- name: Restore Cache
  id: restore
  uses: actions/cache/restore@v4
  with:
    path: ...
    key: abc-${{ github.sha }}-${{ github.run_id }}-${{ github.run_attempt }}
    restore-keys: |
      abc-${{ github.sha }}-${{ github.run_id }}
- name: Run if any cache was restored
  if: steps.restore.outputs.cache-hit != ''
  ...

The correct way to get the same check seems to be
if: steps.restore.outputs.cache-matched-key != ''.
Maybe it makes sense to add that use-case in the README?

I think it would have been better to change the documentation. This was a major breaking change.

Before landing this type of change, it would be useful to check how it is used:
https://github.com/search?q=.cache-hit+language%3AYaml+&type=code

This was a major change and should have been released as such.
The change in return value cause several critical steps in our workflows to be skipped and caused them all to fail.
This change could have potentially disrupted development for my whole team had I not caught it before going on vacation.
We rely heavily on actions from this organization because we perceive them be stable and professionally maintained.

The readme says that chache-hit is a boolean value: https://github.com/actions/cache?tab=readme-ov-file#outputs
The string 'false' is not a boolean value (and it is a truthy value). Please revert this broken change

The readme says that chache-hit is a boolean value: https://github.com/actions/cache?tab=readme-ov-file#outputs
The string 'false' is not a boolean value (and it is a truthy value). Please revert this broken change

In that sense the API was inconsistent with the docs already before.
When a restore-keys entry was found instead of the primary key, 'false' was already returned before and a falsy value was only returned in case neither key was found.

Then the readme correction proposed in https://github.com/actions/cache/pull/1263 is still relevant, even though the description of this PR says that it is meant to fix the implementation instead of having to clarify the readme (the PR of course needs to be adapted to account for the change done here)

This broke our CI.
Should have been major release.
Its a breaking change.

This basically broke all of my composite actions.
It's sad that it's 2024, and GitHub Actions still can't make their type system right!
true and false are booleans, not strings!

👋 I will work on reverting this change


short vs. long names within *master files?

Hi Oleg,
Thank you for creating and posting this function, it's very appreciated. I'm using your utility to read the Norgate Premium Database, which uses the Metastock file format. I noticed that your read*Master functions are often returning truncated values for the 'name' field. It appears that those functions are hard-coded to look for a 16-character wide field.
I touched base with Norgate tech. support on this. The rep suggested that you may have coded metastockread to an older version of the Metastock format, which only provides for a 16-character name field. There is apparently a newer version of the standard, which also includes a 45-character name field. Please see attached screen snip and emaster file below.
The snip shows the provided emaster file, opened in a programming editor. As you can see, there are 2 names stored internally per symbol. For example:
S&P 1500 Aerospa
S&P 1500 Aerospace & Defense SubInd
May I ask for your assistance please, to read the longer name? I understand that you may not wish to modify your release code to handle the additional complexity. In this case, do you have a suggestion please, how to modify the relevant line to read the longer name? For example, in readXmaster on line 11:
names      = cellfun(@(x) char(x(1:find(x == 0,1,'first'))), num2cell(tmp(17:39,:).',2),'un',0) ;
I have to admit, I don't understand the math here. (How are 16 characters being read? 17 + 16 - 1 = 33)
Please let me know your thoughts?
Thanks,
Brad
2 Files attached:

emaster.zip

@Brad-Stiritz I pushed the change, thanks for reporting

Thank you for the quick update, I appreciate your help with this. I'm sorry not to have been thinking ahead, and for the inconvenience: would you mind please taking a look at the master and xmaster file formats as well? Please see attached examples from the same folder as the emaster above.
Also, would you mind please updating the change log at the top of the file, to indicate the present modifications? This will be helpful in keeping track of your latest code version.
(x)master.zip

@Brad-Stiritz checked the other master files, they do not have a long name there.
With respect the log, I have not been using it for a while. Usually, with git you keep track with release tags, but this is a very small contribution and not really worth the effort. I guess just download the most recent release from the master branch.


Handle max read and write batch sizes

It would be great to handle max read and write batches size limitations as https://github.com/awslabs/dynamodb-data-mapper-js do that...
When you are trying to get more than 100 items it put the rest into the pending list which is processed together with unprocessed keys automatically.

This would be awesome, reduce the complexity for end users.


FCM "Messaging: We are unable to register the default service worker. The operation is insecure. (messaging/failed-serviceworker-registration)."

Help,
would like to ask, why i am getting this error, but in my local it's working fine.
I check my firebase-messaging-sw.js and it's there. what would be the cause?
error message:
code: "messaging/failed-serviceworker-registration"
Messaging: We are unable to register the default service worker. The operation is insecure. (messaging/failed-serviceworker-registration).
thanks

this file is missing firebase-messaging-sw.js.
please add firebase-messaging-sw.js  file in root folder.

it's in my root, when i type http://.com/firebase-messaging-sw.js it shows the file content. but it didn't work for me

can you check in dev-tools--->application-->service-workers is any worker is active.
like above image

// Give the service worker access to Firebase Messaging.
// Note that you can only use Firebase Messaging here, other Firebase libraries
// are not available in the service worker.
importScripts('https://www.gstatic.com/firebasejs/4.8.1/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/4.8.1/firebase-messaging.js');
// importScripts('/__/firebase/init.js');
// Initialize the Firebase app in the service worker by passing in the
// messagingSenderId.
firebase.initializeApp({
'messagingSenderId': 'SENDER_ID'
});
// Retrieve an instance of Firebase Messaging so that it can handle background
// messages.
firebase.messaging();
firebae-messing-sw.js file

You can only use service workers if you're serving your code via HTTPS, except when you're serving from localhost. See here for more details.
"You’ll also need to serve your code via HTTPS — Service workers are restricted to running across HTTPS for security reasons." and "In order to facilitate local development, localhost is considered a secure origin by browsers as well."

It does not work with Firefox or Safari, just Chrome supports localhost:"ANYPORT". If you try to substitute with ngrok it does not work either, and you get the error stated in the issue.

Please check:

https://bugzilla.mozilla.org/show_bug.cgi?id=1429714

If cookies are "Keep until I close Firefox" it will not work. You need to check if the option is switched on, but what I don't understand is why I need the option if I get a new token every time when I start a session?

@dkdndes please open a new issue if you're having this problem!

Unable to get permission to notify. FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script. (messaging/failed-serviceworker-registration).
Any one got solution for this ???

Where did you put your firebase-messaging-sw.js?

Unable to get permission to notify. FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script. (messaging/failed-serviceworker-registration).
Any one got solution for this ???

You need to make sure the firebase-messaging-sw.js has existed in your public folder

Unable to get permission to notify. FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script. (messaging/failed-serviceworker-registration).
Any one got solution for this ???

yea have you found the solution??

Why does it not say anything about the
firebase-messaging-sw.js
Here ->
https://firebase.google.com/docs/cloud-messaging/js/client?authuser=0

hi in localhost i got both foreground and background notification but in production (https) i only got the background notification using FIREBASE 7.6.0
service worker also same

Works like a charm. Thanks @parth181195. 👍

For any one else stuck on this, my error was similar to this but slightly different stemmed from the a problem with the firebase-messaging-sw.js file not being publicly accessible. This comment explains it clearly.
I fixed mine by moving the firebase-messaging-sw.js file up one folder so it was accessible via http://localhost:<PORT NUMBER>/firebase-messaging-sw.js instead of http://localhost:<PORT NUMBER>/messaging/firebase-messaging-sw.js

@parth181195 @mmermerkaya
I ve placed my  service worker file in root folder and it s accessible in http://localhost:<PORT NUMBER>/firebase-messaging-sw.js also I ve passed the whole project config .
Unlike Chrome and Edge , it worked only in Firefox browser
Any Solution ??

If you are using typescript with React, just put your firebase-messaging-sw.js in your public folder. And remember to turn  "allowJs": true, in your tsconfig.json under compilerOptions.
Your firebase-messaging-sw.js should look like this:
`// Scripts for firebase and firebase messaging
importScripts('https://www.gstatic.com/firebasejs/8.2.0/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/8.2.0/firebase-messaging.js');
// Initialize the Firebase app in the service worker by passing the generated config
var firebaseConfig = {
apiKey: "YOUR_API_KEY",
authDomain: "YOUR_AUTH_DOMAIN",
projectId: "YOUR_PROJECT_ID",
storageBucket: "YOUR_STORAGE_BUCKET",
messagingSenderId: "YOUR_MESSAGING_SENDER_ID",
appId: "YOUR_APP_ID"
};
firebase.initializeApp(firebaseConfig);
// Retrieve firebase messaging
const messaging = firebase.messaging();
messaging.onBackgroundMessage(function(payload) {
console.log('Received background message ', payload);
const notificationTitle = payload.notification.title;
const notificationOptions = {
body: payload.notification.body,
};
self.registration.showNotification(notificationTitle,
notificationOptions);
});`

The script has an unsupported MIME type ('text/html').
==> Service worker registration failed, error: DOMException: Failed to register a ServiceWorker for scope ('http://localhost:3000/') with script ('http://localhost:3000/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html').
Getting this error

If you are using typescript with React, just put your firebase-messaging-sw.js in your public folder. And remember to turn "allowJs": true, in your tsconfig.json under compilerOptions.
Your firebase-messaging-sw.js should look like this:
`// Scripts for firebase and firebase messaging
importScripts('https://www.gstatic.com/firebasejs/8.2.0/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/8.2.0/firebase-messaging.js');
// Initialize the Firebase app in the service worker by passing the generated config
var firebaseConfig = {
apiKey: "YOUR_API_KEY",
authDomain: "YOUR_AUTH_DOMAIN",
projectId: "YOUR_PROJECT_ID",
storageBucket: "YOUR_STORAGE_BUCKET",
messagingSenderId: "YOUR_MESSAGING_SENDER_ID",
appId: "YOUR_APP_ID"
};
firebase.initializeApp(firebaseConfig);
// Retrieve firebase messaging
const messaging = firebase.messaging();
messaging.onBackgroundMessage(function(payload) {
console.log('Received background message ', payload);
const notificationTitle = payload.notification.title;
const notificationOptions = {
body: payload.notification.body,
};
self.registration.showNotification(notificationTitle,
notificationOptions);
});`

This solved my problem. But why wasn't it included in the guide itself at https://firebase.google.com/docs/cloud-messaging/js/client?authuser=0?

@horlarme firebase works different on version 9.0

same problem here

put your firebase-messaging-sw.js in the root directory same folder where index.html exist and make sure
your ``firebase-messaging-sw.js is empty it does not contain any code
this worked on firestore v9

what about run PWA with path like /app/?

if anybody is using this in react  then just add file  "firebase-messaging-sw.js" in public folder because public folder is your root folder.

if anybody is using this in react then just add file "firebase-messaging-sw.js" in public folder because public folder is your root folder.

Thanks, it helped

Im facing this issue with my sevice worker in my nuxt 2 production app. Anyone to help me out?

@Owura-Kwaku  Place your firebase-messaging-sw.js file in the static folder.

I ran into this with the service worker file existing, being accessible etc. but using wrong URLs in importScript. I needed to add the -compat suffixes like here:
https://github.com/firebase/firebase-js-sdk/issues/5403#issuecomment-908024147

@AustinMusiku My sw file is in the static folder. On localhost the sw file registers successfully but on my remote server the sw fails to register due to an insecure connection. I'm using HTTPS on my remote server too

An error occurred while retrieving token.  FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:3001/firebase-cloud-messaging-push-scope') with script ('http://localhost:3001/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). (messaging/failed-service-worker-registration).
at registerDefaultSw (registerDefaultSw.ts:43:1)
at async updateSwReg (updateSwReg.ts:28:1)
at async getToken$1 (getToken.ts:43:1)
at async Object.onSuccess [as current] (Login.page.jsx:59:1)

here

@TausifM would you be able to help with a similar issue I'm having?
https://stackoverflow.com/questions/75785205/unable-to-register-the-default-service-worker-failed-to-register-a-serviceworke

You can only use service workers if you're serving your code via HTTPS, except when you're serving from localhost. See here for more details.
"You’ll also need to serve your code via HTTPS — Service workers are restricted to running across HTTPS for security reasons." and "In order to facilitate local development, localhost is considered a secure origin by browsers as well."

Would be able to help with a simliar issue I'm having?

This

Mine is in the src directory.  Did you move it up one level above that?
https://stackoverflow.com/questions/75785205/unable-to-register-the-default-service-worker-failed-to-register-a-serviceworke

The solution for a react application is to move your firebase-messaging-sw file to the public folder

I have just commented out my code for firebase-messaging-sw.js and I have placed this code in a script tag in my index.html file and I have received the token successfully on localhost.

place this code ins cript tag in index.html file under body tag.

i have the same problem


npm run dev and some error

$ npm run dev

node scripts/watch.mjs

file://vite-react-electron-main/scripts/watch.mjs:6
import { createServer, build as viteBuild } from 'vite'
^^^^^
SyntaxError: The requested module 'vite' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'vite';

node version must be >= "14.7.0"


[Proposal] Improve CSV support for the Engine

Tested versions
All versions
System information
Windows 11
Issue description
Currently if a CSV file is imported it is imported as translation. Import configuration could not be changed to be used as data file. the only way it can be done is by ignoring/skipping the import file and accessing the file through scripts.
Steps to reproduce
Create a CSV file containing game data which is not translation and try to import the file. it will only be recognized as translation.
Minimal reproduction project (MRP)
N,A
I created this issue as there is no proposal mechanism in Blazium.

hmm can you provide a example project, with steps to reproduce? Pretty please?

It does not require a project, but here is the proposal I created in Godot, and I was frustrated with the discussion and closed it.
https://github.com/godotengine/godot-proposals/issues/7321
Note: I am also working on it, so I have not added many details. I will add the way of working in the PR and in documentation.


Describe EC2 availability zone IDs at most once per refresh (#9142)

This was an oversight on my part. If Prometheus is missing ec2:DescribeAvailabilityZones, the SD will attempt to refresh for every target, resulting in lots of 403s:
level=warn ts=2021-08-02T12:17:48.880Z caller=ec2.go:245 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2a err="could not describe availability zones: UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: b9c37a4b-789a-4963-8655-db4671bf8cf4"
level=warn ts=2021-08-02T12:17:48.884Z caller=ec2.go:245 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2c err="could not describe availability zones: UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: efc89d50-fbf9-43a2-9b63-c527dcffccf5"
level=warn ts=2021-08-02T12:17:48.889Z caller=ec2.go:245 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2a err="could not describe availability zones: UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: 1d55608a-def0-4757-b401-be726630031d"
level=warn ts=2021-08-02T12:17:48.893Z caller=ec2.go:245 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2c err="could not describe availability zones: UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: b197e921-af02-4320-b950-c98f43c2d542"

This PR caps this to a single request per refresh(), turning the above into this:
level=warn ts=2021-08-02T12:54:44.102Z caller=ec2.go:256 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2a err="could not describe availability zones: UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: e1086f51-d8fd-4383-b1e7-814e167c5caf"
level=warn ts=2021-08-02T12:54:44.102Z caller=ec2.go:256 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2c err="no availability zone ID mapping found for eu-west-2c"
level=warn ts=2021-08-02T12:54:44.102Z caller=ec2.go:256 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2a err="no availability zone ID mapping found for eu-west-2a"
level=warn ts=2021-08-02T12:54:44.102Z caller=ec2.go:256 component="discovery manager scrape" discovery=ec2 msg="Unable to determine availability zone ID" az=eu-west-2c err="no availability zone ID mapping found for eu-west-2c"

It would be good to integrate this before v0.29.0 final.

Thanks, one last small thing :)

Thanks, I will merge on green!


Collision avoidance constraints in trajectory optimization

This PR adds collision avoidance to kinematic trajectory optimization, per these resources:

https://typeset.io/pdf/a-collision-free-mpc-for-whole-body-dynamic-locomotion-and-1l6itpfk.pdf
https://laas.hal.science/hal-04425002

It seems to correctly enforce the constraint (traj opt won't succeed unless the waypoints/collocation points are collision free), but it doesn't work that well when the initial guess is in collision...
I suspect the same HPP-FCL Limitation where we're not getting the collision distance points is at play here... so I'm inclined to merge this as-is and fix once Pinocchio 3.0 is out.

How much more do you want to poke at this?

I don't know... it really doesn't work well enough for me to be happy with it, but at the same time I've been seriously spinning my wheels and am close to giving up and just merging what is there.

I added a fallback that I'm more satisfied with in the "optimize RRT path example". It will now do:

Plan an RRT
Try do a full optimization using the RRT waypoints only as initial conditions
If 2. fails, do another optimization, this time constraining the RRT waypoints and only optimizing trajectory segments in between them.


select search reset

Describe the bug
when using select with search on a livewire component, search box does not clear until page is refreshed.
To Reproduce
use any select with search
Additional context
Recommend either:

add search: '' to closePopover()

closePopover() {
    this.popover = false
    search: ''
    this.$refs.select.dispatchEvent(new Event('close'))
},

watch for a emit('clear') from livewire.

nonetheless Great work! I have used a number of the available components, with little to no issues. although bit more documentation on some of them would be beneficial!

Maybe be more convenient to clear search when select/unselect option.

Thanks for your report

It is now fixed


Request For One Line Comment

In Sublime you can type
/**[space]

Which becomes
/** [cursor] */

It's really nice for one line comments. Any chance you can add this?

This is already supported in docblockr. It just works a little differently. Enter /** and press shift+enter


awslogs: Fix a race in collectBatch()

- What I did
Fixed a race found in #22963 differently than #22971
- How I did it
Instantiate a new slice for each batch instead of truncating the existing slice
- How to verify it
TESTDIRS=daemon/logger/awslogs BUILDFLAGS=-race TESTFLAGS="-test.count 100" make test-unit

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "awslogs-logging-driver" git@github.com:samuelkarp/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Is that race is real for a real client? Because I think it's pretty the same as copy and even slightly worse, because not preallocating anything :(

@LK4D4 I'm not sure there's really a race in the driver as opposed to the test, but this does avoid a (potentially large) copy.  To answer your question on #22971, PutLogEvents is indeed a blocking call.
Preallocation can be changed, but what I have now is fairly similar behavior to the truncation that was already occurring.

If it's blocking then let's make mockClient blocking and avoid allocations at all :)

@LK4D4 Making mockClient block doesn't seem to make the race detector happy by itself.  I'm not sure exactly what the race detector is unhappy about; the slice element contents are never modified concurrently and the PutLogEventsInput struct gets an independent copy of the slice header.  The only modification of the slice itself happens with sort.Sort, but nothing is concurrently modifying the slice during that operation.

@samuelkarp could you post race detector output pls?

https://github.com/samuelkarp/docker/commit/21a51896f7c6851a40c6e1f8fe7a03d80a4cc055 shows the mockClient with zero-length channels so that it blocks.  Race detector output is here.

Ok, mockClient code is confusing, but as I understand issue we need to make copy of events inside func (m *mockcwlogsclient) PutLogEvents( or test itself will mess with events after this call returns (it returns because we're sending result in channel at the beginning)

@LK4D4 That seems to work too.  I'll update this PR with that change.

(Also, if Docker has picked a mock generation tool, I'd be happy to switch away from this confusing, hand-written mock.)

@LK4D4 PTAL

LGTM

LGTM


UDT named items not present in reference documentation "Syntax" block

Describe the bug
The syntax block in reference documentation for UDTs does not include named items, instead providing the declaration of a UDT that can only be used by unwrapping.
Screenshots
The reference documentation for Microsoft.Quantum.Math.Complex does not agree with its declaration as newtype Complex = (Real: Double, Imag: Double) in the runtime source file Math/Types.qs.

Additional context
This is related to but distinct from #113 in that this issue prevents the syntax block from appearing correctly, while #113 tracks the ability to provide additional information about named items in a fashion similar to inputs.

@cgranade Do you want to pick it up then?


Do not enforce numeric IDs and enforce RootQuery

Numeric IDs are very artificial and not meaningful at all.
I wouldn't enforce them in the linter.
Also, the linter wasn't enforcing RootQuery, but it is mandatory.

This generally looks good to me!
Is there anything currently checking that rules defined in the policy manifest have corresponding rules in Rego?
I wonder if the IDs should just be int, rather than the 1.2.3 format. Then referring to rules in sections in packages can be done using that notation implicitly. E.g. rule with ID 3 in section with ID 2 in package with ID 1 could be referred to in text as 1.2.3.

This generally looks good to me!
Is there anything currently checking that rules defined in the policy manifest have corresponding rules in Rego?

Not at the moment. But it is good to have. For now, if Preflight cannot find a result for a rule in the manifest it marks it as missing in the final report.

I wonder if the IDs should just be int, rather than the 1.2.3 format. Then referring to rules in sections in packages can be done using that notation implicitly. E.g. rule with ID 3 in section with ID 2 in package with ID 1 could be referred to in text as 1.2.3.

What's the value on that? I personally prefer to use meaningful IDs, so I can have an idea of what it is just by looking at it. I think it is more natural and easier deal with for humans. In case of a machine, it really does not make a difference if it is a number or not.

My original thoughts were that the meaningful part was the name, and the main value of numeric IDs would be to make referring to things more concise: You could say "1.1.1 and 1.1.2 failed" rather than "pods_basic. resources. container_cpu_limit and pods_basic. resources.container_mem_limit failed".
But I don't know if that has much value, and the other terms are a lot more immediately descriptive. So we probably are better to drop the requirement for numeric IDs.
@charlieegan3 What are your thoughts?

I guess the value in a semantic-style id (1.2.3) was the hierarchy? I'd hope we could achieve this with OPA packages (e.g. package pods.containers.resources.requests if we had so many rules it was worth breaking down of course)
When I saw those versions initially (some months ago) I figured it was related to the k8s version the rules were used for.


duplicate outputs

Description
When a process has a complex output then the output file is duplicated in the outputs folder:
$ ls outputs:
out.txt
out_vsor6v25.txt

The file with the _ extension (out_vsor6v25.txt) is referenced as output.
Environment

operating system:
Python version:
PyWPS version:
source/distribution
[ ] git clone
[ ] Debian
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):
web server
[ ] Apache/mod_wsgi
[ ] CGI
[ ] other (please specify):

Steps to Reproduce
Run a process with a complex output.
Additional Information

fixed by PR #399.


Add more data to player events and fire more of them

This PR adds more metadata to the PlayerEvents. I also added some comments that explain which PlayerEvent is fired when.
More PlayerEvents are now exposed through the --onevent script and the additional meta data is made available through additional environment variables.
Currently the additional metadata that is being exported is the title of the current track and its length.
It would be nice to add the Artist and maybe the cover art URL as well but this requires loading of additional information from the server. At this stage I'm only making available what's already there. So that's half of #439.
(Loading the Artist info shouldn't be too difficult, but there doesn't seem to be an interface for the cover art yet - at least I couldn't find it in the code or protobuf definition).
While doing so I realised that a growing set of metadata variables is getting passed around within the player. Thus I decided to refactor this and bundle them into a TrackMetaData struct. This should make it much easier to add more fields in the future.
The events that trigger the --onevent script are:
start
change
stop
playing
paused
volume_set
The first three events are as before and the last three are new.
Only playing and paused provide the additional meta data. The reason is that start and change are fired before the track has been loaded, so the data isn't available.
The volume_set event solves one half of #410. (the second half is suppressing the volume change within librespot).

I'm really looking forward to seeing this merged - I previously had hacked in my own volume handler and will be happy to give up my ugly patch in favour of this PR. 👍

There has been discussions on and off about more metadata, and it normally ends with "it should go in the daemon". The player thread should technically not have to deal with these things, but just fire events and move on.  That being said, lets expose what the player already knows (for now at least) to bridge the gap, and refactor it out when we have the daemon..
See https://github.com/librespot-org/librespot/pull/190, https://github.com/librespot-org/librespot/issues/25 and the meta * cough * issue https://github.com/librespot-org/librespot/issues/7 for some history :

(Loading the Artist info shouldn't be too difficult, but there doesn't seem to be an interface for the cover art yet - at least I couldn't find it in the code or protobuf definition).

You only can get the file_id of the covers, they are then fetched from a regular cdn (open.spotify.com/image/ or i.scdn.co/image/)

@ashthespy I can't test this atm, so feel free to test and merge. I'm also going to re-read over the previous issues wrt the daemon - it's been longer than i would have liked, and I've forgotten a bunch of stuff, but we should just get on with biting the bullet and splitting stuff out - am conscious this library is gradually accumulating functionality that doesn't really belong in it.

I wasn't aware of the politics behind metadata. But after reading the older discussions I understand the goal to keep the player thread uncluttered from it - after all it is complicated enough already. This PR assumes that more metadata is handled within the player in the future, so maybe it's not optimal for moving forward.
Here's a suggestion for an alternative approach:

Create a caching MetaDataManager as a separate component. Separate in the sense that it lives in its own file and the player doesn't depend on it. Thus it can easily be moved to another repository if desired (even though I feel it shouldn't, but I don't want to start this discussion here).
The MetaDataManager would at its core be a key-value store (keys and values are not necessarily of string type).
It provides an async api to retrieve meta data. If the requested data isn't available it loads it from the server.
It also allows to store incidental meta data that hasn't yet been requested. Such data will then be put into the cache in case it gets requested later.
The player is set up to provide all incidental metadata it comes across on the PlayerEvent stream.  The MetaDataManager listens to this stream and stores the information it sees.

The advantages of this approach are:

there's an easy api for library users to retrieve metadata.
incidental meta data is preserved which brings a performance benefit because it doesn't have to be requested and waited for later on.
it doesn't clutter the player thread.
it's a somewhat optional component that can be moved around repositories easily.

Let me know if this sounds like a good idea. If so I might re-evaluate this PR to see whether things should be done differently.

I'd also favor this to be merged as there seems to be a regression where events are not getting fired anymore on a pause without disconnecting (maybe this is not a regression but wanted, as I was looking for stop and not paused, so the stop event should not have been fired in the first place?).
With this PR I could get the old behavior back.

I just rolled back all the internal changes related to metadata.
All the events I described earlier still fire the same way, but the track name is no longer exposed.
Dealing with metadata the right way is probably better done in a separate PR.

I just rolled back all the internal changes related to metadata

Darn. Would your changes have allowed playback backends to get access to the song metadata (artist and track name at least?) That could potentially be useful with Gstreamer, as gst pipelines are able to handle metadata in the form of "tags," and certain sinks and intermediate processing elements will actually do stuff with it.

This PR has been sitting there for over a month now. Just making sure it's not forgotten. From my side it's good to be merged.


Fix mistake

Description

Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Wrote unit tests.
[x] Wrote integration tests (simulation & CLI).
[x] Updated the documentation.
[x] Added an entry to the CHANGELOG.md file.
[x] Re-reviewed Files changed in the Github PR explorer.

Thanks for your contribution. However, that one is not an error, there is no such command as desmos stop


print(df.to_markdown(index=False))

          I was going to create a similar request but to have the output displayed as Markdown. As a temporary workaround I'm storing the dataframe into a variable and then using the `print(df.to_markdown(index=False))` which gives me the desired output to copy into to a markdown cell.

Rendered in the markdown:

If I don't include the print it the output can't be directly copied into the cell.

Originally posted by @dmcmurchy in https://github.com/iqmo-org/magic_duckdb/issues/18#issuecomment-1942912196

Yup, I can add a df_markdown or something mode.
Curious why you use this, is this to copy/paste elsewhere? Or are you rendering the notebook from MD?

Yeah, I'm usually copying the output elsewhere, sometimes into another file or just a different spot in the same notebook. I find the markdown cleaner than the HTML output especially when looking at the unrendered cell (looks nearly identical to the rendered output). What takes 7 lines in markdown ends up being 69 lines in formatted HTML so I would end up scrolling a lot if just using the HTML output.

Could you check it out? Install from git, it's not built.
See formatting_notebooks.

So I ran that on my side, but the output is this but wrapped:
'|   employee_id |   deal_size |\n|--------------:|------------:|\n|           101 |      400000 |\n|           101 |      300000 |\n|           201 |      500000 |\n|           301 |      500000 |\n|           405 |      100000 |\n|           405 |       35000 |\n|             1 |      150000 |\n|             1 |      600000 |\n|             1 |      250000 |\n|             1 |       99000 |'

And if I do a print on the output I get the easy to copy paste output.
|   employee_id |   deal_size |
|--------------:|------------:|
|           101 |      400000 |
|           101 |      300000 |
|           201 |      500000 |
|           301 |      500000 |
|           405 |      100000 |
|           405 |       35000 |
|             1 |      150000 |
|             1 |      600000 |
|             1 |      250000 |
|             1 |       99000 |

The desired output is the output from print.

Try the latest commit plz: in this version, an IPython.display.Markdown object is returned. ipython then renders it properly, but instead of a string, it returns a Markdown object... so use the a.data property

Hmm, not sure I like this version... ipython is rendering the markdown into HTML. Let me know what you think.

I actually like it!  It threw me off at first when I saw it, but the output copies correctly.

Nice, thanks!
Just to document the alternative, instead, could render the str using HTML wrapped in a <pre/>:
mdd = HTML(f"<pre>{md}</pre>")

The result would render as:


Release latest master to Rubygems?

Hi folks,
Can you push the latest to Rubygems? 1.6.0 doesn't support Rails 5.1
Thanks.

1.7.0 is out :)

Amazing - thanks!


Fix ja-JP contexts.md layout

Why:
Closes #20026

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

The page layout is fixed.

current page layout.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@bells17 Thanks for submitting a PR and linking it to your issue. ✨
Unfortunately, we are not able to accept changes for translated content. Our translation process involves an integration with an external service, where all translation activity happens. This includes issues with the markdown. We hope to eventually open up the translation process to the open-source community, but we’re not there yet.
See https://github.com/github/docs/blob/main/contributing/types-of-contributions.md#earth_asia-translations.
We appreciate you bringing this to our attention. I've submitted an internal issue to fix this. 💛


Can not add inline styles in ts files

Versions
Angular CLI: 1.7.1
Node: 9.5.0
OS: darwin x64
Angular: 5.2.5
... animations, common, compiler, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router

@angular/cli: 1.7.1
@angular/compiler-cli: 5.2.6
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.1
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

Repro steps

Step 1:
Starting with new sass project add app-inline.component.scss file. With something obvious like:

body {
  background-color: red;
}

Step 2
In the app.component.ts file add import './app-inline.component.scss';
Step 3
View app using ng serve and the body should be red.

Observed behavior
The styles are not applied.
Desired behavior
The styles should be added like they are when included in the styles.scss file.
Usually when I work on angular projects outside the cli I can import global styles into a component using inline style imports via the style-loader defined in the webpack.config. This is really helpful when a component wraps a 3rd party library that doesn't play nicely with angular's styleUrls field. I may need to add styles to the global scope in order to affect the elements this library adds, but I don't want to add them as globals in the styles.scss since they are part of this component and should only be loaded if this component is imported. It also makes for cleaner code since the styles are contained in the code to where they are used.
In my example I have a component that wraps a QuillJs text editor and I have a few custom styles I want to add to it as well as I would like to import their styles inside this component.
Mention any other details that might be useful (optional)
I wanted to make sure this wasn't intentionally before digging into the issue on my own.
Thanks!

Hi,
The body is defined on a higher level: usually index.html this is why the CSS selector for body isn't applied on root component level.

In angular one of the best things (imo) is that the styles are applied to the component itself and won't leak outside.

As you said, if you want to style the body element src/styles.scss is the right place.
on the other hand if you want to style the root component or its children elements then you need to specify app-root or your custom selector; but not body as there is no body in the root component.

I hope this will help.

Hi @CodySchaaf, the syntax you are describing (import './app-inline.component.scss';) is not something we support at all. That is why it's not working as you expect.
To use global styles you should use the the styles array in .angular-cli.json (see https://github.com/angular/angular-cli/wiki/stories-global-styles for more information). For component styles you have to add them in the stylesUrl array of the component.

Hey @filipesilva Thanks for the response. I understand how it is intended to work, but that won't help me for my use case. Affecting the body was just a simple example and not how I would use this in reality.
In my real situation I'm using a component to wrap the https://quilljs.com/ library. Quill adds a div with the class ql-editor inside my component.
I start with this view:

Which then compiles to something like:
<my-app-editor _ngcontent-c0="" _nghost-c1="">

</my-app-editor>

Of course I have custom styles I assign to the stylesUrl, but if I were to add
.ql-editor {
  background-color: red;
}

To those rules the compiled styles would look like:
.ql-editor[_ngcontent-c1] {
  background-color: red;
}

Which won't work since quill doesn't add _ngcontent-c1 class to the element.
This is not a global style and so shouldn't be included in the global styles array, since it is restricted to the scope of the component it should be able to be included there. Since angular doesn't use the real shadow dom and just simulates it by adding generated class to the styles the easiest way to achieve this is with an inline import that gets hoisted to the global once it is imported.
Me end component definition would look something like this:
import './my-quill.scss';

@Component({
  selector: 'my-app-editor,
  templateUrl: './editor.component.html',
  styleUrls: ['./editor.component.scss']
})
export class EditorComponent implements OnInit, AfterViewInit {}

Thanks!

The view encapsulation option is designed to support scenarios such as this.
Try adding the following to the component decorator:
encapsulation: ViewEncapsulation.None
This will cause the component to not use shadow DOM emulation and not alter the styles rules.  For more information, the documentation is here: https://angular.io/guide/component-styles#view-encapsulation

This is great thanks! Also seems like ::ng-deep would have been useful here although it has now been deprecated :-/


[Hub Generated] Review request for Microsoft.Devices to add version preview/2020-07-10-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/openapi pipeline

according to mail discussion from PR auther:
These fields are already part of our API but they were missing from the swagger files which is why this PR was created to add them to our latest Preview version but we are now getting a validation error since this is identified as a breaking change:
so approve breaking change


This is a test PR to try making a PR from a fortk

There's 1 commit
I have uncommited changes locally
The branch and commit have been pushed to the fork's remote.

comment

comment

test


Temporary fix for https://github.com/jetty/jetty.project/issues/11841

https://github.com/jetty/jetty.project/issues/11841 has an NPE when using 100-Continue. This hack is a workaround.

Create a new module that generates a JAR that will sort first in the classpath
Put a hacked version of Jetty's HttpSender in this module that has a fix
The Java classloader will load this version of the class first, thus working around the problem

This hack should be removed as soon as possible

Damn - we just got TestGenericRestRequests.testPutObject:206->doPutObject:273 » NullPointer Cannot invoke "org.eclipse.jetty.client.transport.HttpExchange.getRequest()" because "this.exchange" is null on this. I need to spend more time on this.


RTIRQ 2018 version isn't available anymore on RNCBC.

As the link is broken, rtirq installation fails.
The site now contains a new version exclusively:
https://www.rncbc.org/archive/rtirq-20190129.tar.gz

I realized the default.nix file in the os-specific module points to the right link, probably some file in my sistem was outdated.
I did a channel update and rebuilding.
By the way, thanks for making this tool. It is an amazing way of using nixos advantages to turn the pc into a great audio workstation.


j.clients.google_compute has no unit tests

and also doesn't work properly.  and apparently can only be run inside the google compute engine.

disabling from dynamic test walker needed as just walking the properties of j.clients.google_compute throws exceptions


Restores use_adal.md file.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Closing this for now, still discussion with product team on whether this should be restored. @SerdarSoysal just FYI in case you need it.


[WebExt] User Scripts docs tasks, Fx 70 (high priority)

Trello: https://trello.com/c/vsKZdybA/115-page-actions-and-userscripts-fx-70
Acceptance criteria

[ ] [Enable userScripts API on release channels](Enable userScripts API on release channels) (https://bugzilla.mozilla.org/show_bug.cgi?id=1437098) (see comment 26 - there is an existing doc, but it's not good enough - needs to be expanded upon)

[ ] [META] Implement a userScripts API (the same docs need, but needs DDC'ing once work is done).

Notes
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts definitely needs improvement:

missing a page for onBeforeScript
Many of the descriptions seem to be about contentScripts, on both this page and the subpages.
The page needs an example, shown here and added to the webextensions examples repo. The subpages also need examples.
BCD is missing from all pages
You could probably do with writing a tutorial to show how to use userScripts, in a similar style to https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts

Acceptance criteria

[x] BCD PR created, reviewed and merged
[x] onBeforeScript page created
[ ] All pages reviewed and edited to remove any inappropriate reference to contentScripts
[ ] Tutorial created and reviewed
[ ] Example extension created and added to web extension example repo

BCD PR #4768 Approved and merged.

Resolving missing sidebar entries for userScripts methods, events, and types

Tutorial created but not reviewed. The single task that has not been done at all is the PR for adding the new example.

Created this PR for the new example: PR 426

My tutorial page didn't update properly. The page Working with userScripts not only is only a skeleton but there is no history on the finished article. (How that can happen, I don't understand.)
Recreating...

@irenesmith are you going to finish off this tutorial any time soon?

@irenesmith What still needs to be done on this to remove the Draft banner?

Irene will create a new issue for replacing the example. Otherwise, this is done.


[#noissue] Update merge condition of server-map

remove 'isQueue' option when check mergeable node.

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


Are min/max values for filters documented anywhere?

Hi, don't know if I am being stupid but are the values for the filters listed anywhere in documentation or source code?
For example if I want to find the min/max value for the Saturation filter so that I can apply these values to slider where can I find them? Had a look through the Filters folder in the framework but was unable to find any info.
Thanks
Checklist

[x] I've read the README
[x] I've searched for existing GitHub issues

Currently no. You'll need to read the source code for min/max values.


Complement to CONTRIBUTING.md required

The CONTRIBUTING.md divide the installation process into two steps:
1 - pip install -e .
2 - make test
It could misslead contributors. The comand pip install -e . install the dependences described in requirements.txt and under the setup.py install_requires atribute:

requests
click
beautifulsoup4

Ain't nothing wrong until here. But when you move to the next step (make test) the test suit doesn't run properly. The majority of the tests rely on the responses module but this module would not be installed by running pip install -e .
The responses dependency is under setup.py > tests_require but pip install -e . won't reach that line. To properly run the make test I need to pip install -r requirements-dev.txt.
Should this be described at CONTRIBUTING.md or there's some other way to install everything at once.

The CONTRIBUTING.md divide the installation process into two steps:
1 - pip install -e .
2 - make test
It could misslead contributors. The comand pip install -e . install the dependences described in requirements.txt and under the setup.py install_requires atribute:
* requests

* click

* beautifulsoup4

Ain't nothing wrong until here. But when you move to the next step (make test) the test suit doesn't run properly. The majority of the tests rely on the responses module but this module would not be installed by running pip install -e .
The responses dependency is under setup.py > tests_require but pip install -e . won't reach that line. To properly run the make test I need to pip install -r requirements-dev.txt.
Should this be described at CONTRIBUTING.md or there's some other way to install everything at once.

I think it's possible to setup.py install requirements and requirements-dev, I'll test it before doing a PR

So, what we can do here is to use pip install -e .[test] instead pip install -e ., this way we need to do:
pip install -e .[test]
make test
and all will run fine. But, looking at CONTRIBUTING.md I realize that we don't use requirements-dev.txt any moment in instalation step, but we require to contributors to use pre-commit that is in requirements-dev.txt.
So, we need to delete requirements-dev.txt and put all this requirements in setup.py or we to continue using just pip install -e . and put pip install -r requirements-dev.txt as a step before make test
I would like @aguimaraesduarte  or @dmvieira give us an opinion about it before making my pull request.
If we remove requirements-dev.txt, setup.py will look like this:
# -*- coding: utf-8 -*-

'''
Created on 2018-03-22

@author: gustavo.alves
'''
from setuptools import setup, find_packages
from azkaban_cli.__version__ import __version__

test_deps = [
    'responses==0.10.5',
    'twine',
    'sphinx',
    'pre-commit'
]
extras = {
    'test': test_deps,
}

setup(
    name='azkaban_cli',
    version=__version__,
    author = "Gustavo Alves",
    author_email =<EMAIL_ADDRESS>    description = ("Azkaban CLI"),
    packages=find_packages(exclude=['contrib', 'docs', 'tests']),
    py_modules=['azkaban_cli'],
    classifiers=[
        "Development Status :: 3 - Alpha",
        "Environment :: Console",
        "Intended Audience :: Developers",
        "Operating System :: POSIX",
        "Programming Language :: Python :: 3.7",
    ],
    install_requires=[
        'requests<2.30.0',
        'click<8.0',
        'beautifulsoup4<=4.7.1'
    ],
    tests_require=test_deps,
    extras_require=extras,
    entry_points='''
        [console_scripts]
        azkaban=azkaban_cli.azkaban_cli:cli
    ''',
)

I would like to know what do you think about it too @Perkles, particularly I prefer to use requirements-dev, sounds more 'clean' to me, but with pip install -e .[test] we do the same thing with a command.

Hey @LeonardoFurtado

I would like to know what do you think about it too @Perkles, particularly I prefer to use requirements-dev, sounds more 'clean' to me, but with pip install -e .[test] we do the same thing with a command.

I agree with you. This looks fine to me:

...or we to continue using just pip install -e . and put pip install -r requirements-dev.txt as a step before make test

Yeah, I would rather add the pip install -r requirements-dev.txt step before make test. It makes it more declarative and transparent in my opinion.

Can we close this issue @aguimaraesduarte ?

@Perkles Yes. Thank you


syz-ci: add flag to enable debug mode for testing

Signed-off-by: Alexander Egorenkov<EMAIL_ADDRESS>
Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

You will only need this for manual debugging, right?
I would expect a -debug flag to work better, leaving debug enabled in config is never a good idea.
Users come to us with problems and then it turns out they run production with -debug flag which is not going to work well.
Will a -debug flag work for your case?

You will only need this for manual debugging, right?
I would expect a -debug flag to work better, leaving debug enabled in config is never a good idea.
Users come to us with problems and then it turns out they run production with -debug flag which is not going to work well.
Will a -debug flag work for your case?

Correct, i'll rework it to a flag then.

Thanks for bearing with me.

Now I remembering that when I needed to debug manager in syz-ci setup, I stopped syz-ci and then run syz-manager manually with -debug flag. All binaries and configs should be on the disk under managers/, so it just boils down to passing right flags.

No problem :) I'm always on board for a good solution and not just hacks.
I'm debugging corrupted reports problem on s390x and find out that all kernel messages on s390x have CR at the beginning.
Is there already a proper way to handle it in syzkaller ? I saw something like decoder in code for output.
Regards
alex


Added Peculium contract ABI

PECULIUM - First Saving System in Crypto Driven by AI
Peculium is a platform which uses the power of AI to bring liquidity and the dawn of financial markets 2.0
Making it possible for everyone to start their #cryptosavings secured by the Blockchain
www.peculium.io

this is already integrated


hostctl: init module

Fixes #227
Config looks like
hosts = [
    "<IP_ADDRESS> foo.de"
    "<IP_ADDRESS> bla.de"
];

It will be setup by entering the shell. I did add a proper "caching" so it's calling only hostctl when required because we need to run sudo.
To deactivate, the user has to run deactivate-hosts in the shell and leave the shell. Next opening of the shell readds them

I guess I would add this to devenv up and call the hostctl remove when the command gets canceled using a trap

@domenkozar are you okay with the Idea to add pre and post scripts to devenv up. So we are able to start hostctl and stop it after running the processes. I guess without processes there is not usecase for custom hosts 🤔

@domenkozar are you okay with the Idea to add pre and post scripts to devenv up. So we are able to start hostctl and stop it after running the processes. I guess without processes there is not usecase for custom hosts thinking

It's still better to always set the hosts, as someone might rely on that as part of the scripts, etc.

The problem is when do we remove the hosts. Currently, I am adding a new command. Feels wrong and can be easily forgotten and then the hosts entries says there😅

@roberth could you cover this one for the next Nix team meeting?

Not sure what you'd like me to cover. Do you have a nix issue for it?
------- Original Message -------
On Monday, December 26th, 2022 at 12:16, Domen Kožar @.***> wrote:

@.***(https://github.com/roberth) could you cover this one for the next Nix team meeting?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Not sure what you'd like me to cover. Do you have a nix issue for it?
…
------- Original Message -------
On Monday, December 26th, 2022 at 12:16, Domen Kožar @.> wrote: @.(https://github.com/roberth) could you cover this one for the next Nix team meeting? — Reply to this email directly, [view it on GitHub](#249 (comment)), or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Sorry, I wrote this to the wrong browser tab :)

I'm still unsure how to handle the unloading correctly.
Ideally we'd set a trap function in bash and expose that via exitShell for cleanup.
We'd need to fix the whole env loading business, so probably after #191 and #237

Even that would not work. When you have two shells inside it and one leaves the hosts are gone for all 🙈
I still somehow like the Idea to couple it with devenv up

:+1: let's couple it with devenv up

@shyim would be great if you plan to finish :partying_face:

Had no time to look currently in 🙈 . maybe weekend

Nice! Looks good 👍 I was wondering whether an attrset has been considered for configuration?
{
  hosts = {
    "myhost" = "<IP_ADDRESS>";
  };
}

So that it is easier to override/remove. Or are there features of /etc/hosts that I'm overlooking?

The only problem is that you want to merge all entries by ip to one line as multiple domains with same IP for some reason slow down DNS resolving on Mac

This should be able to convert the structure to a hosts file conent.
let
  hosts = {
    "myhost" = "<IP_ADDRESS>";
    "otherhost" = "<IP_ADDRESS>";
    "anotherhost" = "<IP_ADDRESS>";
  };
  entries = lib.mapAttrsToList (hostname: ip: { inherit hostname ip; }) hosts;
  entriesByIp = builtins.groupBy ({ ip, ... }: ip) entries;
  hostnamesByIp = builtins.mapAttrs (hostname: entries: builtins.map ({ hostname, ...}: hostname) entries) entriesByIp;
  lines = lib.mapAttrsToList (ip: hostnames: "${ip} ${lib.concatStringsSep " " hostnames}") hostnamesByIp;
in
  lib.concatStringsSep "\n" lines

Sooo I have updated it. First of all @bobvanderlinden thanks <3 it works flawlessly
hosts = {
    "foo" = "<IP_ADDRESS>";
  };

processes.test.exec = "ping foo";

That was my example nix file.

We can use the same base to support mkcert to add like SSL to caddy


Bruno 1.34.1 fails to install on Windows

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
I attempted to install the official built version of Bruno 1.34.1 via winget and from installer downloaded from github. I get the same error.
.bru file to reproduce the bug
No response
Screenshots/Live demo link

Hi @tilagnes - sorry to see you're experiencing this. We're investigating. What version of Windows are you on?

I am on Windows 11 Version 24H2

I am getting the same issue with the 1.37.0 installer on Windows 11 24H2 (Build 26100.2605).
Here is the error event logged in the  Windows application event log:
- EventData

  AppName bruno_1.37.0_x64_win.exe
  AppVersion <IP_ADDRESS>
  AppTimeStamp 5c157f86
  ModuleName System.dll
  ModuleVersion <IP_ADDRESS>
  ModuleTimeStamp 5c157efa
  ExceptionCode c0000005
  FaultingOffset 00001581
  ProcessId 0xc194
  ProcessCreationTime 0x1db5b5bbbf114ed
  AppPath C:\Users\user\Downloads\bruno_1.37.0_x64_win.exe
  ModulePath C:\Users\user\AppData\Local\Temp\nsjC0CA.tmp\System.dll
  IntegratorReportId ebe37c50-d3e6-4014-8740-320179b7422d
  PackageFullName
  PackageRelativeAppId

I deleted the weird System.dll from the temp path and then the installer completes successfully.


Comments in English

Please, give comments in English.

Use mine fork https://github.com/skoky/goscan/tree/english

@skoky  thanks

Thanks