are error messages being suppressed in development?

Why am I seeing this message when bugsnag is running in development and shouldn't be catching errors (according to notifyReleaseStages).
[bugsnag] Session not sent due to releaseStage/notifyReleaseStages configuration

Image to show the lack of context with each log:

Here's how it's configured:
import * as config from "../config";
import bugsnag from "@bugsnag/js";

export let client = bugsnag({
  apiKey: config.BUGSNAG_API_KEY_SERVER,
  releaseStage: config.NODE_ENV, // is "development"
  notifyReleaseStages: ["production"],
});

I might be misunderstanding how notifyReleaseStages works but I don't understand why bugsnag is printing anything at all here. If it's catching an error, it should also be logging the error. If there is no error, it shouldn't be printing anything about not sending the session.
Is there any way to actually just disable bugsnag entirely in development, without having to mock out the entire module so that manual calls to the client won't break?

Hi @danprince
The notifyReleaseStages option is designed to limit what is sent to Bugsnag rather than prevent capture of sessions or errors.
Your screenshot shows the capture of sessions (which are subsequently not sent to Bugsnag due to your configuration) so no error has been caught in that instance:
https://docs.bugsnag.com/platforms/javascript/#session-tracking
With your configuration, when releaseStage is set to development Bugsnag will still capture sessions and errors but the notifyReleaseStages setting will prevent those being reported to Busgnag, and will also prevent any manual calls to notify from reporting to Bugsnag.
In a similar way you can prevent error reports being sent to Bugsnag for more specific criteria by returning false from a beforeSend callback based on properties of the report object:
https://docs.bugsnag.com/platforms/javascript/customizing-error-reports/#disabling-error-reporting
There isn't a way to disable Bugsnag entirely in development other than wrapping the calls to initialize and notify Bugsnag. But Bugsnag is designed to have minimal performance impact and where possible to not modify underlying error handling behaviour, so there should be no issue with enabling Bugsnag and using notifyReleaseStages to prevent delivery of the captured errors.
If the [bugsnag] console logs are too noisy where you're preventing delivery of errors in development you can supply an alternative logger or switch off Bugsnag logging completely as shown here:
https://docs.bugsnag.com/platforms/javascript/configuration-options/#logger
Thanks!

custom logger function receives an event with Event not sent due to releaseStage/enabledReleaseStages configuration
and onError isn't called.
How can I avoid sending all development errors while developing an application to BugSnag, but simply logging them in the console?

Hi @Gregoirevda - rather than using the enabledReleaseStages config option, you could implement your own onError callback. Something like this should work:
Bugsnag.start({
  apiKey: 'YOUR_API_KEY',
  releaseStage: 'development',
  enabledReleaseStages: ['development', 'production'], // don't exclude `development` events!
  onError: (event) => {
    if (event.app.releaseStage === 'development') {
      console.debug(event.errors[0]) // or whatever is of interest about the event
      return false; // discard the error
    }
  },
  // other config options
})


Integration with Science Server

A ScienceServerApi class was created that allows interaction with ScienceServer, at the moment it is possible to register a target list, retrieve information from a list and remove a list from the user.
OBS: Precisa de um update no ambiente do Science Server para que seja possível criar o token de acesso.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
246

Relevant Lines:
246

💛  - Coveralls


Update dependencies and workflows

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

Project coverage is 100.00%. Comparing base (4635b0e) to head (338db28).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #348   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           87        87
  Lines         2281      2281
  Branches       209       209
=========================================
  Hits          2281      2281

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


chore: update renovate config

:tada: This PR is included in version 1.27.1 :tada:
The release is available on:

v1.27.1
GitHub release

Your semantic-release bot :package::rocket:


Update Galaxy image version to 21.05

Also:

Drop non-org team from Codeowners so we don't annoy them since only .org is using this repo currently.
Update Chip-SEQ section on test.org to test the version change.

@galaxybot deploy this


Improve API to allow for better reuse.

I am getting my video buffers through a different way than through http. I have been working a bit on thisi, and it's a bit annoying to have to hack it together with the current api (I am currently matching the api of Websocket.
It would be nice to be able to use a method like jsmpeg.addData(BUFFER).
Unless I am missing something?

Agreed. The new codebase should address this. Let me know if you have any further suggestions!


Interface

What feature or improvement do you think would benefit Files?
First of all, I would like to congratulate you on making Files better every day.
It is without a doubt an excellent application.
I would like to suggest an improvement to make it even better than it already is.
In the current version, <IP_ADDRESS>, in the top right corner there are 3 dots with the following options: "new panel, new window, compact overlay".
I would like to request that you leave these 3 options visible, instead of leaving these options within a context menu, since I use these 3 options a lot and they are always hidden in the context menu, somewhat hindering the experience and usability of the application.
Thank you ever since for the excellent application and never stop perfecting or improving what already exists.
Grateful.
Requirements
Visibility of context menu options.
Files Version
<IP_ADDRESS>
Windows Version
Windows 11  22H2
Comments

Small suggestion that can be improved.

Thank you for your kind feedback, we'll keep working on improvements and updates. While we don't have plans to move to move these into the main toolbar area, I want to make sure you're aware of the keyboard shortcuts for those options.

Open New Window - Ctrl + N
Compact Overlay - Ctrl + Alt + Up and Ctrl + Alt + Down
New Pane
Open selected folder in new pane - Ctrl + Shift + Enter
Open new pane - Alt + Shift + Plus
Close right pane - Ctrl + Shift + W

We haven't ruled out a dedicated button for dual pane, but we'd like to make some improvements to the general dual pane experience before moving forward with it.


Recursive application of the mapper

I think there should be a way to apply the deriving-mapper to expression-valued attributes. Maybe as an alternative Arg.expr or by exposing the mapper as a global?
My motivation is that I wrote a syntax extension to generate random instances of types.  The derived-from type takes an attribute [@random ...] to override with custom generator code, where I need reliable way to refer to generators for parameters or the type itself, e.g. in
type 'a term =
  | Var of 'a
  | App  [@weight 0.5] of 'a term * 'a term
  | Lam of ('a * 'a term) [@random random_lambda [%random: 'a term]]
  [@@deriving random]

In other cases random_lambda might use just [%random: 'a].  The internal name poly_a is needed in either case, which makes me think the best way to refer to it is to use [%random: ...].  I could systematically apply all parameter generators to the custom generator and use:
  | Lam of ('a * 'a term) [@random random_lambda random_term]

In my opinion, explicit arguments are nicer.

Nice syntax extension!
I agree that the mapper should be exported. Would you make a PR?

Thanks!
Sure, though I can't think of a nice way to do it without breaking backwards compatibility.  If doing it from scratch I would have replaced the ~option ~path parameters with a single private record for extensibility.  To keep backwards compatibility exposing it as a global seems the best option.  I think it needs to be a reference set by the mapper function, may disguised as a function:
val get_mapper : unit -> mapper
(** [get_mapper ()] is the current deriving-mapper.  This must be called from a deriving plugin. *)

Any other suggestion?

I think a (more) elegant solution would be moving Ppx_deriving_main.{derive,derive_type_decl,derive_type_ext,module_from_input_name,mapper} into Ppx_deriving. mapper would be just a field, since it's almost stateless*. Ppx_deriving_main would only consist of code that does plugin loading and maintaining the Ast_mapper cookie.
(*) It has implicit state in form of module_nesting. It could be tempting to make that state local to the mapper, but in fact it /should/ be global, since the whole compiler-libs are global, and I can't really envision using the mapper outside of a compiler-libs context. It has to rely on Location.input_name anyway.

I don't understand where you suggest where you suggest putting the mapper field.  The only record I can see is deriver, but that is constructed before the mapper.  We could create a new record, as I suggested, but how can we pass it to the deriver implementations without breaking backwards compatibility?

Exporting it as Ppx_deriving.mapper. (Deriver plugins can't, or shouldn't even if they somehow can, directly refer to Ppx_deriving_main.

Aha, we're going for a global then. But it still needs to be a ref, since mapper is only defined after processing the arguments passed by PPX.  We can expose it as a function if you prefer, and then I see the need for moving the code from main.

No, no need to be a ref. This code is the only part that depends on argv, and it should be left in Ppx_deriving_main. It would process argv, then just return Ppx_deriving.mapper.

Aha, registry is mutable, so mapper can be constructed before loading the plugins.  I'll seen a PR shortly.

The local structure function uses add_plugins, so it seems I have to move pretty much all code to Ppx_deriving, leaving only
let mapper argv =
  get_plugins () |> List.iter dynlink;
  add_plugins argv;
  Ppx_deriving.mapper

let () =
  Ast_mapper.register "ppx_deriving" mapper

But then, do we wish to expose the plugin-related functions to the user, or do we move that code, as well?
BTW, any preference for where the mapper should be put in the interface?  I've put it at the bottom, and left out the other from the interface.

If it's okay to load the plugins before Ppx_deriving_main.mapper is called, then I'd move the get_plugins () |> List.iter dynlink to a module level init, which means the only plugin-related function we need to expose is Ppx_deriving.add_plugins.
Sorry you have to spell things out.  I'm just familiarising myself with PPX, using deriving as a soft introduction to the topic.

get_plugins () can't be moved into module level dynlink since it depends on Ast_mapper cookie being set, and it is only set after Ast_mapper.register starts executing.
Otherwise you pretty much nailed it in the previous comment.


changed latest stable to 0.4.5 on travis CI

Can one of the admins verify this patch?

test this please (for CI)


More intuitive default tagging when building images

When building a modified version of an image from a dockerfile, thereby replacing the previous version with something new, I feel like there is something that can be done about the HEAD^n containers that are now a type of "intermediate" and untagged container. Perhaps for a couple of generations they should follow the git nomenclature and actually be renamed like this:
image-name:latest
image-name:latest^2
image-name:latest^3

and then just start removing them past a certain generation? Keep the naming going forever?
or perhaps something more "common speak"
image-name:latest
image-name:previous
image-name:old
image-name:old+1
image-name:oldest

Also on failed builds, the last successful commit is already visible in docker images, but a half-run Dockerfile doesn't help very much, so why not just tag it what it is as "image-name:failed" so there is no question?
Another thing, right now referencing an image that has only 1 tag needs to be explicit unless that tag is "latest". In the spirit of tagging commits, shouldn't they just behave like true tags and point to the same commit if no other tags exist? image-name is hardwired to always be image-name:latest instead of just image-name:whatever_tag_is_left. And for those that use tagging for versioning, the word "latest" might not ever be used. But it would still be nice to have image-name always reference the newest image no?
lastly, image/tag wildcard support!
$ docker images
REPOSITORY            TAG
image-name                latest
image-name                previous
image-name                oldest
image-name                failed
$ docker rmi image-name:*
Deleted: as;dlfjas;ldfjas;ldfjas;a;slfd
x4
$ docker images
REPOSITORY              TAG

or
REPOSITORY            TAG
image-name1                latest
image-name1                oldest
image-name2                latest
image-name2                oldest
$ docker rmi *:oldest
Deleted: as;dlfjas;ldfjas;ldfjas;a;slfd
x2
$ docker images
REPOSITORY              TAG
image-name1                latest
image-name2                latest

and for the quitters!
$ docker rmi *:*

see also https://github.com/docker/docker/issues/5603 https://github.com/docker/docker/issues/9641

we need a way to merge all those

It's interesting, tagging has remained sort of untouched for a long time because there are two conflicting uses for them: to show a history of an image, and to show types of an image. Technically, as with git, they are one in the same. But that, I feel, is the main reason defining "default" tag behavior has been difficult to nail down. I tend to favor tags as history rather then type. If tagging assumptions are to be made and defaults implemented, then I think the only way that can be done is to really bias tagging as history instead of type.
At first glance, I think the TAG directive in the dockerfile (#5603) is the best idea to implement first. Because, you can just leave it out if you don't want it. But it still allows for all the custom tagging one desires. #9641 actually appears to be solvable by the first. It seems OP's priority would be to have consistent default tagging behavior in a development environment with multiple parties involved so that a single docker build will produce the appropriate tagging for that project without the need for an outside script or makefile just to store the tag name. Embedding those tags in the Dockerfile can keep track of that on a per Dockerfile/project basis, which I think is better then an additional file.
My concern in this report is this: on any typical day, what does the output of your docker images show in the tag column? For me right now, it was 95% "latest". In my experience, when information is that repetitive, it means it's not being used properly, or rather, I don't know how I want to use it.
Also for this discussion, I think we need to get specific about terms, so I'll give specific examples of workflow so we can all reproduce the same behavior and determine better what we're talking about. I feel like we are mixing "intermediate containers" and "untagged" and "replaced" etc.
Case 1
The default tag. What happens when we build an image with no tag?

make a dockerfile that does something

FROM busybox:latest
RUN touch /tmp/one

docker build -t app . with no tags produces this:

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
app                 latest              4dd4ff70965a        44 seconds ago      2.433 MB
busybox             latest              4986bf8c1536        8 weeks ago          2.433 MB

This is version 1 of our app, and it is the latest version.
3. modify our dockerfile
FROM busybox:latest
RUN touch /tmp/one
RUN touch /tmp/two

docker build -t app.  with to tags does this:

Sending build context to Docker daemon 2.048 kB
Sending build context to Docker daemon
Step 0 : FROM busybox:latest
 ---> 4986bf8c1536
Step 1 : RUN touch /tmp/one
 ---> Using cache
 ---> 4dd4ff70965a
Step 2 : RUN touch /tmp/two
 ---> Running in 203202f0a51f
 ---> 373ac626bfc2
Removing intermediate container 203202f0a51f
Successfully built 373ac626bfc2

and shows this:
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
app                 latest              373ac626bfc2        30 seconds ago      2.433 MB
busybox             latest              4986bf8c1536        8 weeks ago         2.433 MB

What happened to version 1? (image 4dd4ff70965a) Why is it being treated as trash by default? My ideas initially were to make it logical to see the succession. Calling something "latest" by default is useless if there is no history that's readily accessible. If I keep modifying my dockerfile and building again with no tag, that app:latest just keeps replacing my previous images; no easily reachable or obvious history or succession of that image.
I would love this in this situation:
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
app                 latest              373ac626bfc2        30 seconds ago      2.433 MB
app                 previous            4dd4ff70965a        44 seconds ago      2.433 MB

and over time
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
app                 latest              45c118bb2039        8 seconds ago       2.433 MB
app                 previous            373ac626bfc2        30 seconds ago      2.433 MB
app                 oldest              4dd4ff70965a        44 seconds ago      2.433 MB

Or something similar.
Case 2
The rename. What happens to previous images when we replace the image:tag?
Start with busybox:latest
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
busybox             latest              4986bf8c1536        8 weeks ago         2.433 MB

docker run busybox:latest touch /tmp/one
docker commit 615ba2ffc860 busybox:latest then shows:

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
busybox             latest              36c74cf9cccc        About a minute ago       2.433 MB

Why is the original image trash? Again, my same reasoning and proposed solution as in case 1. I'd like to see succession and non-clobbering by default.
Case 3
The upgraded tag via pull. What happens to old images when replaced with a newer one via docker pull?
Here we fake a new version of busybox by doing the same thing we did in case 2:

docker run busybox:latest touch /tmp/one
docker commit 615ba2ffc860 busybox:latest
docker pull busybox:latest will pull the original image back, stealing the tag and will untag the image that owned that before, ie. the previous version.

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>              <none>              ee2d0a2735fc        About a minute ago   2.433 MB
busybox             latest              4986bf8c1536        8 weeks ago         2.433 MB

Same situation, different path to it.  Overwriting latest I understand for sake of automation (always run "latest" tag in production etc.), but keeping a history doesn't negate that feature.
Case 4
The upgrade tag via build. What happens to old images when replaced with a newer one via build?
It's pretty much the same as case 1 and 2: our new image replaces the old in docker images. This case has some more variability though if you incorporate the tagging via TAG directive within the dockerfile (which I +1 btw). So there has to be a priority within this case as well between:

TAG directive in dockerfile
no TAG in dockerfile, and no tag from the CLI
Conflict between TAG in dockerfile and tag via CLI
If you do supply a tag via CLI or TAG in dockerfile, do you double tag by default the newest image with "latest"? So that we keep a history going?

General Comments
Of course we can always tag beforehand, but that is very dependent on your orchestration tool keeping track of that history for you. Why should docker care about it? Because I've heard talk of garbage collection at some point, and being conservative about image history and removing tags (so that it can be gc) makes docker a cordial custodian of your images that automatically keeps track of history by default instead of a more cutthroat purging of all that is old. This is especially handy for CLI usage without orchestration tools. I should just keep building, tagging, committing, pulling my images and the entire history be preserved via tags. On massive scale, with many individuals and programs manipulating the same images, the history could be very welcome. What about reverting back from latest in emergency? A history could encourage this behavior by default. Why do I have to dig around docker history for some image ID instead of a very easy "busybox:previous" tag for example that I can be confident about?

I have the same complaint as the top post.  Googled to try to find a solution, found this issue -- which is still open with no activity for a while.
Is there anything new on this front in the last year?
Wouldn't it be easy to just add an option to docker build to tell it you don't want the previous version of the image kept?

@aaronlehmann @tonistiigi @stevvooe Is this possible without major changes in design?

There's already a lot of detailed discussion in the issue about the pros and cons. I'm not sure I have anything to add.
I don't think it's technically difficult to make the changes suggested here, but it's more of a design question.

@aaronlehmann @stevvooe I wonder who can do design decision. Issue is pretty old, so if nobody will come with arguments I will close it.

@LK4D4 In general, I agree with the sentiment, but I am not sure it is worth the engineering effort and compatibility breaks this would incur.
There is nothing wrong with the ideas here other than that tags don't really work anything like git tags. For this to work, we'd really need to introduce some sort of first-class tag concept, separate from what we call a tag today, which is just a name, really.
There are really two departures from the git data model:

There is non-zero cost to each revision in docker, unlike git.
The behavior of tags like latest is more akin to a branch, which requires another level of change history.

We can see this, somewhat, in features like docker history.  Each tree is wholly independent and calculating diffs requires two trees. In docker, we are storing actual deltas, where each "tree" requires the tree before it to calculate the whole result and the links between these deltas are a part of the image config, which sits above everything.
Not to mention that each changeset has a runtime cost. This feature provides docker fast commit and startup, at the cost of a less rich history model. In git, one can look at merely the commit and tree to get at the content. Because each changeset in docker is pushed to the original change and each mounted layer has runtime cost, maintaining the history of all changes for an image isn't possible without drastic breaks.
The missing component here is lineage. In git, you have lineage of commits, maintained by a hard hash linked relationship. In docker, the naming lives outside this hash chain. We'd really have to bring it into that system to make this work in the same way.
The key change would be to have something similar to a commit object that tracks the tree at each image level. That tree could be represented by a set of layers, or whatever. The operation of pushing would be to then push this lineage (just hashes, not even names at this point) to "branches". These lineage objects (commits, really) could then be tagged and we'd have something very close to how git behaves.
TL; DR Docker tags are git-inspired but lack the internal data structures to achieve some of the more advanced git-style features.

I think the original issue could be easily achieved with a script / external tooling

I think the original issue could be easily achieved with a script / external tooling

How would such a script maintain the relationship between the current version of latest and the last version of latest? How could these reconcile when latest forks on two separate machines? This behavior requires a three-way merge semantic with history of the reference, not the image.

@stevvooe I was thinking of docker tag myimage:latest my image:latest-1, or  docker tag myimage:latest my image:previous before running a build, or am I being naive?

@thaJeztah Sure, that would provide a similar behavior but the result is shallow. It will break down when two nodes disagree on what latest-1 is.
Git's data structures really enable some cool stuff and reproducing that behavior cannot be done with data structures that support these operations under all conditions.


Pull to refresh

This article may help.
But, ...
NO SOLUTION NOW.

But someone could do this with Cupertino.

Done.


JetBrains IDEs Plugin

Clear and concise description of the problem
Currently, there are plugins available for VSCode and Visual Studio, but it'd be great if there was an official plugin for the JetBrains suite of IDEs
JetBrains IDEs support Microsoft's LSP, so hopefully an official plugin would require minimal work on Microsoft's part
Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Thanks for submitting the request. Further investigation needed in this area.

Current workaround: Use TextMate bundle (example: IntelliJ’s documentation).

Download TypeSpec grammar: https://github.com/microsoft/typespec/blob/main/grammars/typespec.json
Create directory named typespec where you want to store the TextMate bundle
Move typespec.json into the directory named typespec
Rename typespec.json to typespec.tmLanguage
Open JetBrains IDE preferences, go to Text Mate
Click add (+) and select the typespec directory created in (2)

JetBrains IDE will now syntax highlight and given basic token autocomplete. A proper plugin would still provide more value and better auto-complete, but I do not know the effort to do that.

/assign


Understanding Graph Database and Cypher Dataset currently not working in AGViewer

Describe the bug
AGViewer is not showing one of the four datasets available: Understanding Graph Database and Cypher
To Reproduce
Steps to reproduce the behavior:

Go to Add New Project
Click on Understanding Graph & Cypher
Click Create New Project
Launch AGViewer

Expected behavior
See dataset in AGViewer, which currently is not available.
Screenshots

Desktop (please complete the following information):

Browser [chrome]

AG Cloud Express's "Understanding Graph & Cypher" creates an empty DB when creating a project.
Execute the create statement in the 4th tutorial and execute refresh.
You can see 2 nodes and 1 edge.


You seem to do not care about this repo!

Please give 57 open Pull Request a chance to make this cool piece of software better. Even more I would suggest to migrate over to React Hooks.
Thanks!

Even more I would suggest to migrate over to React Hooks.

In terms of performance, I would not recommend this

In terms of performance, I would not recommend this
Sauce ?

In terms of performance, I would not recommend this
Could you elaborate?

@TimSusa
A few days ago there was a reply in this thread: https://github.com/STRML/react-grid-layout/issues/1040
It was mentioned that next release would happen "soon". As per milestone, there seems to be one issue open for that to happen:
https://github.com/STRML/react-grid-layout/milestone/1
However, I do agree that progress is slow and 56 open PRs just doesn't give enough trust or confidence on the projects' future.

I have this working with hooks, retrieving a layout via an api call. Works with both the latest version and the previous.

Re-open?


add regex as words in dictionnary

Good evening,
I write report in markdown using pandoc references system which are in the format @article_id. As the article id is usually a surname followed by a year, it is always taken as misspelled word. I tried to add @\w* in the github dictionnary but it did not work. Is it possible to use regex as word? Or to make @bla not checked by linter-spell?
The same thing happens for '---------------------------' used as title. for me
Introduction
----------------

the '---' are considered as a misspelled word. adding '-*' in the dictionnary did not work.
Thank you for your help!

I agree with Paul, in many texts I use md5 or sha sums, and sometimes is tedious mark all this with ignore option.

Thanks for the feedback. I'll look into what it would take to accomplish this.

This is best covered by the grammar package, which should label such constructions as a specific scope. The language specific linter-spell package can then be told to blacklist these scopes from spell checking. I am not sure why this is not already the case, unless this is an odd usecase.
Also, @PaulEcoffet, dictionary entries are covered by hunspell or aspell (whichever you use), so here is not really the place to ask. From my (brief) look at these, it appears they don't support regex. Regex can be used in the grammar files, to scope these constructions.


Local communication protocol

How can I use AF_UNIX (unix://) for gateway and business worker communications?
In case of Distributed Deployment , how can I config gateways that only connect to local business workers?

Currently not  support AF_UNIX (unix://) for gateway and business worker communications.
You can use router callback to connect to local business workers like this.
$gateway = new Gateway("Websocket://<IP_ADDRESS>:8585");
$gateway->router = function($worker_connections, $client_connection, $cmd, $buffer)
{
    //var_dump($worker_connections);
    $local_worker_process_count = xx;
    $local_worker_ip = 'xx.xx.xx.xx';
    $local_worker_name = 'xxx';
    return $worker_connections["{$local_worker_ip}:{$local_worker_name}:".rand(0, $local_worker_process_count-1)];
};

Here is docs for router.  Sorry, there is no English version of the docs currently.


java.lang.NoClassDefFoundError: com/google/gson/internal/reflect/ReflectionAccessor

Describe the bug
java.lang.NoClassDefFoundError: com/google/gson/internal/reflect/ReflectionAccessor
 at com.ibm.cloud.sdk.core.util.DynamicModelTypeAdapterFactory.(DynamicModelTypeAdapterFactory.java:77)
 at com.ibm.cloud.sdk.core.util.GsonSingleton.registerTypeAdapters(GsonSingleton.java:77)
 at com.ibm.cloud.sdk.core.util.GsonSingleton.createGson(GsonSingleton.java:53)
 at com.ibm.cloud.sdk.core.util.GsonSingleton.getGsonWithoutPrettyPrinting(GsonSingleton.java:102)
 at com.ibm.cloud.sdk.core.http.RequestBuilder.bodyContent(RequestBuilder.java:417)
 at com.ibm.cloud.cloudant.v1.Cloudant.postDocument(Cloudant.java:825)

To Reproduce
call com.ibm.cloud.cloudant.v1.Cloudant.postDocument() using
<dependency>
     <groupId>com.ibm.cloud</groupId>
     <artifactId>cloudant</artifactId>
     <version>0.0.36</version>
</dependency>

and
<!-- https://mvnrepository.com/artifact/com.google.code.gson/gson -->
<dependency>
    <groupId>com.google.code.gson</groupId>
    <artifactId>gson</artifactId>
    <version>2.9.0</version>
</dependency>

Unfortunately I can't use an earlier version of GSON because of this:
https://github.com/google/gson/issues/1875
and this
https://github.com/google/gson/pull/1902
Must gather (please complete the following information):
$ java --version
openjdk 16.0.2 2021-07-20
OpenJDK Runtime Environment Temurin-16.0.2+7 (build 16.0.2+7)
OpenJDK 64-Bit Server VM Temurin-16.0.2+7 (build 16.0.2+7, mixed mode, sharing)

Additional context

You can track https://github.com/IBM/cloudant-java-sdk/pull/236 for our update to support GSON 2.9, we are waiting on a fix in https://github.com/IBM/java-sdk-core.
FWIW the GSON problems you link to are caused by changes in visibility to internal classes in Java 9+, that were warnings prior to Java 16. This is exact reason why we declare support for running only on Java 8 and 11 currently.
It is possible to use this library with Java 16 and GSON 2.8.9 by supplying the JVM option to switch the error back to a warning or by breaking encapsulation - see https://github.com/IBM/java-sdk-core/issues/127#issuecomment-978069664. It is worth noting that Java 16 is not a maintained Java version anyway; in Java 17 the option to switch the error back to a warning has been removed and breaking encapsulation is the only workaround.

@ricellis Excellent.  Thank you!


fix prefix and typo

Hi @yjxiong ,
I found a prefix setting error and a typo in tools/build_file_list.py. Please check it, thanks!

Thanks for your contributions!

Great honor to improve this project 😄


StatusBar background not being set & translucent=false not working

Is this a bug report?
Yes, re-filing https://github.com/facebook/react-native/issues/15301 with proper format

Have you read the Contributing Guidelines?
yes
Environment
Packages: (wanted => installed)
react-native: 16.0.0-beta.5 => 16.0.0-beta.5
react: 16.0.0-alpha.12 => 16.0.0-alpha.12
Target Platform: Android 4.4+
Environment:
OS:  Windows 10
Node:  8.4.0
Yarn:  0.19.1
npm:  5.4.2
Watchman:  Not Found
Error: unable to print environment info
{ Error: not found: xcodebuild
at getNotFoundError (C:\Users\Mercurius\Documents\GitHub\zindex\node_modules\which\which.js:13:12)
at Function.whichSync [as sync] (C:\Users\Mercurius\Documents\GitHub\zindex\node_modules\which\which.j
s:134:9)
at getXcodeVersion (C:\Users\Mercurius\Documents\GitHub\zindex\node_modules\envinfo\envinfo.js:17:25)
at Object.module.exports.print (C:\Users\Mercurius\Documents\GitHub\zindex\node_modules\envinfo\envinf
o.js:136:28)
at Object.info (C:/Users/Mercurius/Documents/GitHub/zindex/node_modules/react-native/local-cli/info/in
fo.js:17:13)
at Promise.resolve.then (C:/Users/Mercurius/Documents/GitHub/zindex/node_modules/react-native/local-cl
i/cliEntry.js:109:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:611:11)
at startup (bootstrap_node.js:158:16) code: 'ENOENT' }

Steps to Reproduce

(Write your steps here:)
People had different steps
My steps:

On Android of course, testing StatusBar.translucent on device is also giving undefined:

import { StatusBar } from 'react-native'

console.log('StatusBar.translucent:', StatusBar.translucent); // should be false - is undefined
StatusBar.setTranslucent(true);
console.log('StatusBar.translucent:', StatusBar.translucent); // should be true - is undefined

@markentingh steps

I tried posting a comment to closed bug #12618, but there is more to the bug than just background color. The translucency is not being set as well.
Running React Native 0.46.4 on Windows 10 in an Android emulator, emulating a Google Pixel phone with Android version 7. Also tested on Moto E 2nd Gen phone running Android 5.1
In the first screenshot, you can clearly see a translucent StatusBar with no background color, even though I set the translucent property to false & backgroundColor to "blue".
In the second screenshot, I set hidden to true, and the StatusBar did infact hide, so the component is working (somewhat).

@ArvoGuo steps:

Device: MIX 2
System Version: MIUI 8.5
only prop hidden work well
prop backgroundColor and barStyle doesn't work
code:
<View>
   <StatusBar
        backgroundColor="green"
        barStyle="dark-content"
   />
</View>

nothing happend!!!
Expected Behavior

StatusBar.translucent should return proper value
Actual Behavior
StatusBar.translucent should returns undefined

(Write what happened. Add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Same here.
Is this a bug?

Iissue is related with devices whose use app compact an do not support this clase of styles.

Thanks @dann1609 for the confirmation of that. I didn't know that detail.

I'm facing the same problem on Android 6.0.1. The following snippets of code reproduce the same behavior, that is they have no effects on the status bar.
Only backgroundColor
render() {
    return (
      <View>
        <StatusBar hidden={false} backgroundColor="blue" />
        <Text>Hello World!</Text>
      </View>
    );
  }

Only translucent
render() {
    return (
      <View>
        <StatusBar hidden={false} translucent={true} />
        <Text>Hello World!</Text>
      </View>
    );
  }

Both backgroundColor and translucent
render() {
    return (
      <View>
        <StatusBar hidden={false} backgroundColor="blue" translucent={true} />
        <Text>Hello World!</Text>
      </View>
    );
  }

And this is what I get on my Android device:

It seems like the backgrounColor and translucent props are't working.

If you're using Expo, try configuring it in app.json instead: https://docs.expo.io/versions/latest/guides/configuring-statusbar


Full Stage View icon's background is not transparent

IIRC it comes from a Pipeline Plugin

Duplicate of https://github.com/jenkinsci/dark-theme/issues/4

oops


the script doesn't work smtimes

Here is sm buttons not responding to the script at all and when you click download it tells me to subscribe
and the green buttons is working fine

How to install the script?

fixed in 3f6753b11919858a3c19a45be93aadf0af32ab5d


Set OPOST on bsd

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>(cherry picked from commit 17ec46a24316f59c808c112e3ca46d7c442a785a)

Cherry pick of moby/moby#33502
NOTES:

This manually vendors github.com/docker/docker to get the associated changes in github.com/docker/docker/pkg/term/termios_bsd.go

This PR brings in change in moby/moby: https://github.com/moby/moby/pull/33502
And also a related re-vendor in docker/cli https://github.com/docker/cli/pull/59

LGTM
integration and unit tests are green


Pass directories to the upload command

Hi, it'd be great to be able to pass a directory to the upload command to only upload the files in that directory instead of listing all files explicitly or all files in the entire theme.
I could see it working something like this:
theme upload snippets/*
What do you think?

you can run theme upload snippets


Add changelog entries

@mulimoen I can publish 0.7.1 I guess?

@mulimoen I can publish 0.7.1 I guess?

@aldanor Would be nice to have both a release of hdf5=0.7.1 and of hdf5-types=0.7.1

@aldanor Would be nice to have both a release of hdf5=0.7.1 and of hdf5-types=0.7.1

It's easier to just bump everything (see .version_bump.sh in the repo root). Ok, just a sec.

It's easier to just bump everything (see .version_bump.sh in the repo root). Ok, just a sec.


Pinterest extension in Chrome browser

Prerequisites

[X] I am a GSSoC-22 Participant
[X] I checked to make sure that this issue has not already been filed

Description
Here I intend to create a Pinterest extension in Chrome browser using html, css and js.
It helps us collect, organize, save and revisit our inspiring ideas whenever we wish to.
Please assign me this issue, I'm a Gssoc'22 participant.
Tech Stack
Web Development

@manisha-27 pls review my PR....


How do I pass an empty timeout to batch submit_job in batch?

client.submit_job(
  ...
  timeout={}
)

gives
botocore.errorfactory.ClientException: An error occurred (ClientException) when calling the SubmitJob operation: Error executing request, Exception : At least one attribute in Timeout must be specified, RequestId: <redacted>

client.submit_job(
  ...
  timeout=None
)

gives
    raise ParamValidationError(report=report.generate_report())
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter timeout, value: None, type: <class 'NoneType'>, valid types: <class 'dict'>

This applies to nodeOverrides and retryStrategy too.  I am not sure what the defaults are (None, empty dictionary?) for those arguments, or if the method is just a kwargs.  For the latter, I guess it could just be looking for the existence or non-existence of the given keyword argument (ex. timeout).  So I could come up with a way to not specify timeout if the value is None or an empty dictionary.  But that feels very brittle and puts extra burden on the caller to groom the kwargs passed to the submit.job.
I would recommend supporting None as "this keyword argument should be ignored" and an empty dictionary as "this keyword argument is to be used, and its value is empty".

@nh13 - Thank you for your post. According to documentation the minimum value for the timeout is 60 seconds.
And you have to pass the timeout in a dictionary format. Something like this:
timeout={'attemptDurationSeconds':65}

This parameter is not required so you can omit this parameter during the api call and in that case the task will not be timed out. But as far as supporting the None value or the empty value concerned, we can't change the shape of a parameter on the client side. It has to be first supported by service.

If timeout is given as None, then boto should not specify the parameter in the JSON passed to the underlying service.  I think that supporting None for these keyword arguments removes a significant burden on the caller of boto, where currently we have to have either conditional logic to omit the timeout  keyword argument (and others!), or we have to build our own kwargs dictionary.  When wrapping the boto API, this becomes very burdensome, and replicated across all users of boto.

Currently we are not thinking of supporting argument value passed as None at least not in the sense that passing None is the same as not passing it. Technically lack of presence and null are different and i don't think we want to conflate them.

I am disappointed by this decision but I'll add the following for posterity and continue on my way.
This adds burden to ALL clients who use botocore to make sure that if no timeout is desired, then the timeout parameter isn't added as a keyword argument. In contrast, if None was supported as I describe, then this is (IMHO properly) centralized into botocore.  This decision forces client implementations that wrap a submit_job call to either contain this conditional logic (ex. 1)( or use kwargs similar to botocore (ex. 2)
def ex1(timeout: Optional[int] = None) -> None:
  kwargs = {}
  if timeout is not None:
    kwargs["timeout"] = timeout
  submit_job(**kwargs)

^ Ugly, since every user of botocore has to wrap it this way
def ex2(**kwargs: Dict[str, Any] = {}) -> None:
  submit_job(**kwargs)

^ just pushes the problem to the user of this method

Thanks for providing your detailed analysis. At this moment we are not going to change this behavior so i am closing this issue. But in future if we change the behavior then will reopen the issue and update.

Let's track this feature request under boto3 issue https://github.com/boto/boto3/issues/2667


:seedling: Add validation to deviceSelector.

What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds a validating webhook, so that invalid deviceSelectors can't be created.
Which issue(s) this PR fixes
Fixes #142
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:

[ ] squash commits
[ ] include documentation
[x] add unit tests

my idea was to include tests for GetLabelSelector, instead of the webhooks. Since this is the actual function that you test behind the scenes. Right now you still test the webhooks!

This webhook is the public API. We could test the GetLabelSelector. But imagine somehow the call to GetLabelSelector gets lost in the code of ValidateCreate(). Then the unit-test would be fine, but the result would be broken.


🐛 [firebase_messaging] iOS App does not receive notifications

Bug report
Describe the bug
My app does not receive notifications when it's terminated or in the background, however it does receive them when in foreground.
I also noticed that the app does receive notifications correctly when being completely restarted (terminated and opened again).
Steps to reproduce
Steps to reproduce the behavior:

Install and configure the firebase_messaging: ^7.0.3 plugin as per documentation and examples.
Send a push notification to an iPhone via FCM HTTP API.

Expected behavior
I expect my app to always receive notifications independent from it's state.

Additional context

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 1.22.6, on Mac OS X 10.15.7 19H15 darwin-x64, locale de-DE)
    • Flutter version 1.22.6 at /Documents/Developer/Flutter Installations/flutter
    • Framework revision 9b2d32b605 (3 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/marcel.opitz/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.53.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.19.0

[✓] Connected device (1 available)
    • iPhone XR (mobile) • 00008020-001D05611131002E • ios • iOS 14.1

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.10.5
Flutter SDK 1.22.6
snkra 1.2.5

dependencies:
- animations 1.1.2 [flutter]
- app_review 2.0.1 [http intl package_info url_launcher flutter]
- cockpit_base 1.0.5 [flutter http rxdart intl timezone tracking_client]
- dart_notification_center 1.0.0+1 [meta]
- deal_client 1.3.1 [flutter rxdart cockpit_base tracking_client]
- firebase_dynamic_links 0.6.3 [flutter firebase_core]
- firebase_messaging 7.0.3 [meta flutter firebase_core]
- flare_flutter 2.0.6 [flutter flare_dart meta]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_common 1.0.5 [flutter shared_preferences rxdart flare_flutter flutter_swiper share intl firebase_dynamic_links tracking_client cockpit_base like_client]
- flutter_facebook_sdk 0.0.1 [flutter]
- flutter_html 0.11.1 [html flutter]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- like_client 1.0.3 [flutter shared_preferences cockpit_base tracking_client]
- package_info 0.4.3+4 [flutter]
- push_messaging_client 1.2.1 [flutter firebase_core firebase_messaging http shared_preferences cockpit_base tracking_client flutter_notification_channel]
- release_client 1.0.6 [flutter cockpit_base]
- shared_preferences 0.5.12+2 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]
- story_client 1.1.1 [flutter rxdart cockpit_base]
- story_view 0.12.6 [flutter flutter_cache_manager rxdart video_player]
- tracking_client 1.0.2 [flutter http firebase_analytics firebase_core firebase_crashlytics sentry firebase_performance]
- url_launcher 5.7.8 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- mockito 4.1.3 [analyzer build code_builder collection dart_style matcher meta source_gen test_api]

transitive dependencies:
- _fe_analyzer_shared 11.0.0 [meta]
- analyzer 0.40.4 [_fe_analyzer_shared args charcode cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 2.0.13 [crypto args path]
- args 1.6.0
- async 2.5.0-nullsafety.1 [collection]
- boolean_selector 2.1.0-nullsafety.1 [source_span string_scanner]
- build 1.5.0 [analyzer async convert crypto logging meta path glob]
- built_collection 4.3.2 [collection quiver]
- built_value 7.1.0 [built_collection collection fixnum quiver]
- characters 1.1.0-nullsafety.3
- charcode 1.2.0-nullsafety.1
- cli_util 0.2.0 [path]
- clock 1.1.0-nullsafety.1
- code_builder 3.5.0 [built_collection built_value collection matcher meta]
- collection 1.15.0-nullsafety.3
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.5 [collection convert typed_data]
- csslib 0.16.2 [source_span]
- dart_style 1.3.8 [analyzer args path source_span]
- fake_async 1.2.0-nullsafety.1 [clock collection]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase 7.3.2 [http http_parser js]
- firebase_analytics 6.3.0 [meta flutter firebase_core firebase_analytics_web firebase_analytics_platform_interface]
- firebase_analytics_platform_interface 1.0.3 [flutter meta]
- firebase_analytics_web 0.1.1 [flutter flutter_web_plugins firebase firebase_analytics_platform_interface meta]
- firebase_core 0.5.3 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_core_platform_interface 2.1.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.1+1 [firebase_core_platform_interface flutter flutter_web_plugins meta js]
- firebase_crashlytics 0.2.4 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]
- firebase_crashlytics_platform_interface 1.1.4 [flutter meta collection firebase_core plugin_platform_interface]
- firebase_performance 0.4.3 [flutter firebase_core]
- fixnum 0.10.11
- flare_dart 2.3.4
- flutter_cache_manager 2.1.1 [flutter path_provider uuid http path sqflite pedantic clock file rxdart image]
- flutter_notification_channel 0.0.1 [flutter]
- flutter_page_indicator 0.0.3 [flutter]
- flutter_swiper 1.1.6 [flutter transformer_page_view flutter_page_indicator]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- html 0.14.0+4 [csslib source_span]
- http 0.12.2 [http_parser path pedantic]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- image 2.1.19 [archive xml meta]
- intl 0.16.1 [path]
- js 0.6.2
- logging 0.11.4
- matcher 0.12.10-nullsafety.1 [stack_trace]
- meta 1.3.0-nullsafety.3
- mime 0.9.7
- node_interop 1.1.1 [js]
- node_io 1.1.1 [node_interop path]
- package_config 1.9.3 [path charcode]
- path 1.8.0-nullsafety.1
- path_provider 1.6.27 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4+8 [flutter]
- path_provider_platform_interface 1.0.3 [flutter meta platform plugin_platform_interface]
- path_provider_windows 0.0.4+1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.9.2 [meta]
- petitparser 3.1.0 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.3 [meta]
- process 3.0.13 [file intl meta path platform]
- pub_semver 1.4.4 [collection]
- quiver 2.1.4+1 [matcher meta]
- rxdart 0.24.1
- sentry 3.0.1 [http meta stack_trace usage pedantic]
- share 0.6.5+3 [meta mime flutter]
- shared_preferences_linux 0.0.2+2 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 0.0.1+10 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 1.0.4 [meta flutter]
- shared_preferences_web 0.1.2+7 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 0.0.1+1 [shared_preferences_platform_interface flutter ffi file meta path path_provider_platform_interface path_provider_windows]
- sky_engine 0.0.99
- source_gen 0.9.7+1 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.0-nullsafety.2 [charcode collection path term_glyph]
- sqflite 1.3.2+3 [flutter sqflite_common path]
- sqflite_common 1.0.3+1 [synchronized path meta]
- stack_trace 1.10.0-nullsafety.1 [path]
- stream_channel 2.1.0-nullsafety.1 [async]
- string_scanner 1.1.0-nullsafety.1 [charcode source_span]
- synchronized 2.2.0+2
- term_glyph 1.2.0-nullsafety.1
- test_api 0.2.19-nullsafety.2 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.5.9 [path]
- transformer_page_view 0.1.6 [flutter]
- typed_data 1.3.0-nullsafety.3 [collection]
- url_launcher_linux 0.0.1+3 [flutter]
- url_launcher_macos 0.0.1+8 [flutter]
- url_launcher_platform_interface 1.0.9 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.5 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- url_launcher_windows 0.0.1+1 [flutter]
- usage 3.4.2 [path]
- uuid 2.2.2 [crypto convert]
- vector_math 2.1.0-nullsafety.3
- video_player 1.0.1 [meta video_player_platform_interface video_player_web flutter]
- video_player_platform_interface 2.2.0 [flutter meta]
- video_player_web 0.1.4+1 [flutter flutter_web_plugins meta video_player_platform_interface]
- watcher 0.9.7+15 [async path pedantic]
- win32 1.7.3 [ffi]
- xdg_directories 0.1.2 [meta path process]
- xml 4.5.1 [collection convert meta petitparser]
- yaml 2.2.1 [charcode collection string_scanner source_span]

Hi @MaciDE
Please consider upgrading to the latest non-null version firebase_messaging: ^8.0.0-dev.14. The version you are using is outdated and will be completely replaced soon. The new version is a lot more stable and reliable. You can take a look at the migration guide https://firebase.flutter.dev/docs/migration#messaging and the new official example https://github.com/FirebaseExtended/flutterfire/tree/master/packages/firebase_messaging/firebase_messaging/example/lib and the Apple integration guide https://firebase.flutter.dev/docs/messaging/apple-integration
I've seen multiple similar issues get solved just by switching to the new version.
Thank you

Did you follow all the steps listed under the documentation for iOS specific?
**

Especially this step => Enable capability of push notification.

**
I had similar kind of issue in one of my apps, i had followed above step and also double checked the firebase configuration for ios app. Well firebase looks fine in your case, as you're receiving push in foreground.

@markusaksli-nc Thanks for your reply. For now it looks like 8.0.0-dev.13 performs significantly better than the older versions and indeed fixes my issue. I think ^7.0.3 should be replaced by ^8.0.0-dev.14 in all documentation to prevent more people to suffer from the old, broken and now deprecated version.


Bump version 0.14

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

I think this needs another re-render.

Conflicts resolved!


Remove up to 49 obsolete CSS classes

The following CSS classes from zulip.css are probably, but not definitely, obsolete:
.actions_hovered
.actions_link
.bookend_tr
.edit-profile
.edit_content
.hidden-filter
.icon-vector-heart
.label_for_text
.loading_indicator_spinner
.loading_indicator_text
.logout
.message-edit-tooltip-inner
.message-pane
.message-right
.message_data
.message_inline_image
.messagebox-bottom
.messagebox-bottom-colorblock
.messages-collapse
.messages-expand
.open
.pointer
.position-relative
.private_message
.ps-scrollbar-y
.ps-scrollbar-y-rail
.root
.sender_name-in-status
.settings_committed
.sidebar-nav
.skinny-user-gravatar
.sp-container
.sp-palette-container
.sp-preview
.sp-replacer
.sticky
.stream
.streamname
.summary_colorblock
.summary_row
.summary_row_private_message
.tiny
.tooltip
.user-with-mobile
.user_idle
.user_offline

We should try to remove these from our CSS.  For each one the process is something like this:

grep the code to make sure it's not referenced
if it's a compound thing like message-collapse, see if you can find code that builds it up
do git blame on the zulip.css file to get some context on when the class was introduced

If you are 95% confident the class is really obsolete, submit a PR with just removing the one class, so it's easy to revert.
If the class is valid, but the code that refers to it is hard to track with grep, see if there is an easy fix to the code to make it more obvious that the class is used by either the JS code or our templates.
Otherwise, update the ticket with any info you came up with in terms of tracking down the class.

Many of these things, like message_inline_image, twitter_avatar, etc. are all generated by bugdown.

Ah, makes sense.  I can sweep that code.

Ok, I accounted for 6 of the class in bugdown, so I'm going to edit the original post's list of classes and titles.

Some of these obsolete classes probably come from before we did the big rewrite of the message view (tables -> divs).

see #1556 for unpolished code that hunts these downs (see tools/analyze-css-coverage in that branch)

Added the "bite size" label here.  Fixing all 49 of these is some work, but if folks want to take a nibble at a small task, you can try to pick one of these and track its git history with something like git log -S to see if something obviously got deprecated.

Hello Showell and Tim, I hope you are good.
I'm an Outreachy participant and I would like to remove this classes or fix it.
Can you please guide me?

Hello @alanaschueroff!   I am glad you are interested in working on this.  I think the trickiest part about this project is just making sure we don't delete anything that is still in use.
I mentioned a little bit of the strategy at the top of the ticket, and I'll repeat it here for convenience:

grep the code to make sure it's not referenced
if it's a compound thing like message-collapse, see if you can find code that builds it up
do git blame on the zulip.css file to get some context on when the class was introduced

Before diving into deep, though, I think it's worthwhile for you to start a conversation on the frontend channel of our Zulip instance:  https://zulip.tabbott.net/#narrow/stream/frontend
You can announce to folks that you were working on the project, and we can hopefully guide you along from there.  You will eventually get responses from me and Tim, plus a couple of our designers are on that stream, so they may have insights about possible pitfalls.

I think this one is in line with splitting CSS and creating a linter.

@zulipbot  claim.

@zulipbot  PR waiting for review.

@zulipbot  Already sent a PR, Waiting for Review.

@Balaji2198 did you determine the other class are or aren't being used?  I think probably some others are.  If you want to work on this, include the git grep output you used to determine things are unused in the commit messages.

@timabbott  Sorry for the late reply. Somehow missed this message. So, for the reference, these classes have been removed till now. Will start working on others soon.
 .edit-profile
 .message-pane
 .message-right
 .messagebox-bottom
 .messagebox-bottom-colorblock
 .position-relative
 .sidebar-nav
 .hidden-filter
 .ps-scrollbar-y-rail
 .ps-scrollbar-y
 .user_offline

Just done with my mid-semester exams. Will start working on this now.
@zulipbot  claim

After researching about all the classes found that few of them are still valid classes in the code base. Listing them down with the relevant file for reference
.loading_indicator_spinner  --> Used in static/js/loading.js
.loading_indicator_text     --> Used in static/js/loading.js
.message-edit-tooltip-inner --> static/js/message_edit.js:
.sender_name-in-status      --> static/templates/single_message.handlebars
.settings_committed         --> static/js/unread_ui.js

I'm closing this, since we've made some progress, and the above lists are now certainly obsolete, and lots has happened since then, such as moving to scss and adding dark mode.


ConnectionPoolTimeoutException in HttpSender when response is not consumed

Describe the bug
The ApiListener test scenarios in iaf-test fail after having been executed a number of times, because the response of the HttpSender "callApiListener" in it is not consumed.
Reporter
Gerrit
Category

Frank Framework

To Reproduce
Steps to reproduce the behavior:

Start iaf-test
Execute the scenario 'ApiListener01'
See that it passes
Execute it another 10 times
See that it fails after the 10th time
Execute it another time
See that it keeps failing

Expected behavior
The framework should make sure that the http connection is released eventually, either by:

making use of outputstreaming, allowing the connection to close by itself (same pattern as JdbcSenders)
making sure each Pipe / Sender consumes its input, or passes it on to the next Pipe
add option 'consumeOutput' to httpSender to silently consume the output, for cases where the output is not needed.
provide a facility in the PipeLineSession to register resources that will be closed at PipeLine exit

Screenshots
Environment:

Application server (f.e. Tomcat/WebSphere/JBOSS/Jetty)
Browser [e.g. chrome, safari]
IAF Version [7.5, 7.6]

Additional context

Fixed with PR #1423


Common problem when adding user commands

Maybe we should write somewhere explicitly that you need to restart the Watch when adding user commands? Myself and others have gotten stuck on this.

If you are using mage-console and are referring to its watch feature, then this should be reported on the mage-console repository https://github.com/mage/mage-console.
Could you also please describe the problem itself? Why is adding a user command an issue?

moving issue to mage-temples


Plugin / StreamingPlugin use in node.js results in TypeError

After session.attachPlugin("janus.plugin.streaming") gives me a Plugin Object, I can successful call functions like plugin.getId(). But functions like create() and list() that are only defined in StreamingPlugin and not in Plugin return an error:
[TypeError: plugin.create is not a function]
What do I need to do here?
This is not really a bug, so I am not sure if it is ok to put this here.

Well, it's an undocumented behaviour. All plugins that are implemented for now are webrtc dependant. We are using module webrtcsupport to detect whether we have WebRTC. This module does not work in node https://github.com/HenrikJoreteg/webrtcsupport/blob/master/index-node.js. So, currently we don't provide those plugins in node environment and throw if no WebRTC is supported https://github.com/cargomedia/janus-gateway-js/blob/master/src/webrtc/media-plugin.js#L14.
@petergerten Does node have a module to support WebRTC? If yes, shall we use it? If no, shall we strip out the logic of non-WebRTC out of webrtc package?
cc @tomaszdurka @njam

I see. What I am trying to do is to use node.js to mediate the signaling and session establishment between Janus GW and a Kurento Media Server WeRTC endpoint. So theoretically there is no WebRTC logic needed in node.js. I haven't thought it through completely though, as some wrappers seem to rely on it.

Well. It was our restriction to forbid usage on node but I think it is wrong. We should provide those functionality and just state in documentation that any WebRTC logic will fail. I think we should remove this restriction.
If no one is against this removal then I will do it.

I interpret silence here as "Yes" :D. Implementing

@zazabe please review

lgtm

@petergerten Try 0.4.0


Update bear extension

Description
Similar to the Apple notes Ai extension this options will allow users to generate a note directly into their bear app utilizing Ai.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Do you think it's possible @bradenschiller

@bradenschiller are you still around?

There are merge conflicts on this branch that are stopping it from being merged. Is it still being worked on?

Calling a last time @bradenschiller - do you want to get this merged 🙂


[JENKINS-51574] Pom input support

JENKINS-51574
Supersedes #34
@oleg-nenashev @kuisathaverat

Should I release it?

Not in a hurry, I can locally build it, maybe is better to just wait for
the 1.0 release.
El mié., 11 jul. 2018 18:24, Oleg Nenashev<EMAIL_ADDRESS>escribió:

Merged #35 https://github.com/jenkinsci/custom-war-packager/pull/35.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/custom-war-packager/pull/35#event-1728379400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnN45Tw8FcfCUj2yRN4BfdRM_CEJfXAks5uFia0gaJpZM4VLZOR
.


Images not displayed

Hi, I have done several tests with the images sent, I noticed that they are never displayed in Discord.
assets = Assets(                 largeImage = "https://i.ytimg.com/vi/${mediaItem.mediaId}/maxresdefault.jpg",                 smallImage = "https://i.ytimg.com/vi/${mediaItem.mediaId}/maxresdefault.jpg",                 largeText = mediaItem.mediaMetadata.title.toString(),                 smallText = mediaItem.mediaMetadata.artist.toString(),             ),
or
assets = Assets(                 largeImage = "mp:largeimage_name",                 smallImage = "mp:smallimage_name",                 largeText = mediaItem.mediaMetadata.title.toString(),                 smallText = mediaItem.mediaMetadata.artist.toString(),             ),
in both method image on Discord is not displayed.
Could you help me figure out what I’m doing wrong?
Thanks in advance

You can only use discord assets links so you have to

Upload an image to any discord channel and grab it's link
remove everything before attachments/____/_____ and
Use it like this mp:attachments/____/_____

Eg:
https://media.discordapp.net/attachments/1009061802593763398/1292336417795604571/1728187411154.png?ex=67035d94&is=67020c14&hm=3a94a5566e39b798089350e140e239ceec6c099f7bab4e6bdfa8f5547c2b6b40&
Will be converted to
mp:attachments/1009061802593763398/1292336417795604571/1728187411154.png?ex=67035d94&is=67020c14&hm=3a94a5566e39b798089350e140e239ceec6c099f7bab4e6bdfa8f5547c2b6b40&

Thanks


Can't re-register with CasJobs account if existing password isn't strong enogh

Hi Mitya,
I used to have a fairly simple 4-character password for casjobs and the login portal won't let me re-register with the error message:
The Password must be at least 5 characters long.
If I enter a new password, it says my account already exists which is correct behavior.
-L

I think Ani has to reset your password.
Bonnie Souter PhD
Associate Research Scientist
Institute for Data Intensive Engineering and Science
3200 N Charles Street
Baltimore, MD 21218
(w)<PHONE_NUMBER>
(c)<PHONE_NUMBER>
<EMAIL_ADDRESS>On Sun, May 15, 2016 at 5:39 AM, László Dobos<EMAIL_ADDRESS>wrote:

Hi Mitya,
I used to have a fairly simple 4-character password for casjobs and the
login portal won't let me re-register with the error message:
The Password must be at least 5 characters long.
If I enter a new password, it says my account already exists which is
correct behavior.
-L
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/sciserver/login-portal/issues/15

I can take care of it. I'll send Laszlo his new password.


sorting imports with ruff

This MR enables the "I" set of rules. Three commits here:

update configuration
apply auto-fix (large diff)
add the second commit to .git-blame-ignore-revs

Oof.. this is going to take me a while to get through! I'll try to do it ASAP though, to reduce the number of conflicts that will show up if we start merging other PR's first.

If you'd prefer, I think I can set it incrementally and break this up into a bunch of different MRs by sub-module, so it can get a little more spread out over time.
I will admit that I did not review every line of the diff in here before pushing up the MR...

No probs @tungol. I've gone through half of it so far without finding any issues, so with a little luck I can finish the review either tomorrow or the day after.


added МОБУ ФТЛ им. В. П. Ларионова

@timur612 This domain does not belong to a particular school. It seems to belong to an umbrella institution (such as Ministry of Education or similar government body). We cannot add umbrella institutions domain to this repository. Please apply for free educational license with an official document that proves your student status. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students. Thank you for your understanding!


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.7.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove white bar under MiniMap

Before:

After:

By changing the display from the svg from the default "inline" to "block", the svg and parent div get the same height (which I think is the intended behaviour + less ugly because of the removal of the white bar)

Thanks @OrhanTozan . This already part of the v12 base css.


makerst: Add descriptions to method qualifiers

This works successfully when building documentation locally:

Hovering virtual will display a tooltip.
That said, we may want to refactor it to make use of reusable blocks placed at the bottom of the generated class. This would avoid bloating the generated rST files.
Edit: I'm not sure if the above is possible, as the following substitution declarations are considered "empty or invalid" by Sphinx:
.. |virtual| :abbr:`virtual (This method should typically be overridden by the user to have any effect.)`

.. |const| :abbr:`const (This method has no side effects. It doesn't modify any of the instance's member variables.)`

.. |vararg| :abbr:`vararg (This method accepts any number of arguments after the ones described here.)`

Edit 2: It might be possible using an alternative syntax: https://github.com/sphinx-doc/sphinx/issues/203#issuecomment-68532109
Edit 3: The alternative syntax works :slightly_smiling_face:
This closes https://github.com/godotengine/godot-docs/issues/1753.

@akien-mga I refactored the PR to avoid duplicating abbreviation descriptions more than once per file.

Thanks!

Cherry-picked for 3.2.3.


Roll Flutter Engine from 433d360eee11 to ad80c4e828ff (1 revision)

https://github.com/flutter/engine/compare/433d360eee11...ad80c4e828ff
2024-07-02<EMAIL_ADDRESS>Roll Skia from 7f2094d4cf43 to 42fad315c162 (1 revision) (flutter/engine#53684)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


784 | Letter Case Permutation | Java

Letter Case Permutation -
What will change -
Type of Issue -

[x] Adding New Code

Programming Language

[x] Java

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign this issue to me.

please assign this to be i can explain better


Possible to add license?

Would it be possible to add a license file?

Sure, may I ask why? (I'll do it, just curious!)

Done: https://github.com/vvo/sourcekarma/blob/main/LICENSE

Thanks. No special reason. I think most of us just prefer any license over no license at all. At least that way we know what we can, and cannot do with the code.


Hotfix fastboot

I pulled in version 1.0.1 to TheDyrt and found some fastboot errors.
This pull request represents everything I had to do to get it running in fastboot again.
Here is a bare bones ember-cli app that uses fastboot and ember-cli-imgix. https://github.com/Duder-onomy/fastboot-ember-cli-imgix-test-app
If you pull that down and run the command in the readme you can see that ember-cli-imgix fails in its current configuration.
If you update your package-lock.json to pull this PR's commit hash, you will see everything working again.
I think I am going to work on #35 tomorrow and see if I can get some fastboot end to end tests running.

Awesome, Once the tests pass, I will merge this in.
Can you publish a new version tomorrow or early next week?

Yep, I'll publish a new version by early next week.

Published in 1.0.2


Monorepo race condition running for multiple components

[NOTE: Originaled posted here semantic-release/issues/1628]
We are using semantic-release with the plugin semantic-release-monorepo. Our configuration for each component is fairly simple (see below):
The problem comes when running this on CI pipelines for multiple components of the monorepo. If you run this in parallel for component A, B and C, when component A push a tags (and notes) to git, component B and C fails to push due to being outdated.
I'm calling it a "race condition" because it only happens when some commits trigger more than one component at the same time. On these cases, the firsts components (maybe one or two, depending how long each one takes) get published correctly, and all others after that fails. But it fails on pushing git notes (not release notes) and not on pushing tags.
Is there anything that can be done at the plugin level to fix this race condition?
Config:
"dependencies": {
  "semantic-release": "17.1.1",
  "semantic-release-monorepo": "7.0.2"
},
"release": {
  "extends": "semantic-release-monorepo",
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator"
  ]
}

Logs:
[semantic-release] An error occurred while running semantic-release: { Error: Command failed with exit code 1: git push<EMAIL_ADDRESS>refs/notes/semantic-release
To https://github.com/MY_USER/MY_REPO.git
 ! [rejected]          refs/notes/semantic-release -> refs/notes/semantic-release (fetch first)
error: failed to push some refs to<EMAIL_ADDRESS>hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
    at makeError (/builds/__MY_REPO__/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/builds/__MY_REPO__/node_modules/execa/index.js:114:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  shortMessage:
   'Command failed with exit code 1: git push<EMAIL_ADDRESS>refs/notes/semantic-release',
  command:
   'git push<EMAIL_ADDRESS>refs/notes/semantic-release',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr:
   'To https://github.com/MY_USER/MY_REPO.git\n ! [rejected]          refs/notes/semantic-release -> refs/notes/semantic-release (fetch first)\nerror: failed to push some refs to<EMAIL_ADDRESS>Updates were rejected because the remote contains work that you do\nhint: not have locally. This is usually caused by another repository pushing\nhint: to the same ref. You may want to first integrate the remote changes\nhint: (e.g., \'git pull ...\') before pushing again.\nhint: See the \'Note about fast-forwards\' in \'git push --help\' for details.',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false }

[UPDATE: We are not using lerna and it doesn't apply to our case because we are not publishing js modules]

Hi @guumaster 👋

it only happens when some commits trigger more than one component at the same time

This is an interesting problem, but I would think it would happen regardless of whether a single build pushed tags/notes for just one or multiple components? If parallel builds are running, and one of them makes updates to the remote, the local copies of all parallel builds would be out-of-sync.
To make it work, I suppose you'd have to refetch the repo prior to each time semantic-release runs a git command that would get rejected due to a out-of-sync local copy, but even then I'm not sure it's guaranteed to work (a parallel build could be pushing tags at the same time as another build refetches). Another (rough) idea would be to put the parallel builds into a holding pattern prior to running semantic-release to try to enforce that they each run in sequence.

Hi @pmowrer thanks for your reply. It is in fact an interest problem. Our pipeline works partially, It doesn't fail to create the tag, only fail to push notes on the tag, so it does the main job, but leaves the pipeline as failed.
Changing our pipeline to a sequence is not an option because it'll make the process excessively long.

@guumaster
There are two problems currently here. One problem is, that semantic-release is not doing an atomic git operation. Each semantic-release boils down to:

pushing a tag
pushing git notes

This could be changed in semantic-release; they introduced using git notes not so long ago, before that they were using git tags solely. So while this could potentially be alleviated, the other problem is bigger:
Running semantic-release takes time, if you happen to have changes to the same component, it will create a race condition. This is a conceptual problem and you will stumble upon this problem pretty fast. If semantic-release were to use an atomic git operation, you could come up with a recover strategy (pull, merge, run semantic-release again).
However, after having spent quite some days the last weeks with implementing semantic-release for a rather small monorepo, it is not worth the effort. If you are optimizing you pipeline you are better off with (as @pmowrer suggested) a serialized approach; each pipeline job, that does the actual release must run serialized. In typical CI systems you can optimize this pretty easily by using pipeline artifacts and some locking feature. If you happen to use Azure DevOps, you can trivially come up with a serialized pipeline concept via either exclusive locks on environments or dedicated batched pipelines.

Serializing is not an option for our setup. I'd prefer some configuration flag to remove git notes altogether

if anyone has any further ideas around this, feel free to repoen with your thoughts.

FWIW the actual problem lies within semantic-release. Using it in a monorepo simply makes the race condition more likely to happen.


[3.x] Alpha channel indicates opacity, not transparency

3.x version of #56214.

Thanks!

Cherry-picked for 3.4.3.


pdf2txt.py -t xml, get words/lines instead of chars

I'm using pdf2txt.py -t xml to dump the coordinates of each character of a pdf.
Is there a way to get coordinates about words and lines (instead of individual characters)?
I tried with -A and -M -L -W but those don't seem to take any effect when the output is XML.

Is this the right place to ask questions?

When you look at the 'textline' tag in the output xml , you should be able to get the coordinates for the word or the sentence. Alternatively you can construct the coordinates of a word by taking the min and max coordinates of the characters


[update title and doc]

Hey Solomon. Thanks for the PR. I am not using node-sass for the project so I cant add it to readme. Please take a look at the issues created, if you can

When i tried to run it after cloning the project it demanded to install
node-sass...

SignInModal its passing an error, until you change it to SigninModal,
check the SignInModal import and and SignInModal.js they differ at the
middle the file name as 'in' and the imported as 'In'

On Mon, 7 Oct 2019, 22:21 Wilfred<EMAIL_ADDRESS>wrote:

@WillzMu commented on this pull request.
added a few comments. hope you can have a look. Plus can you point this to
the dev branch and not master
In public/index.html
https://github.com/WillzMu/projectZed/pull/34#discussion_r332214730:

@@ -20,7 +20,7 @@
work correctly both with client-side routing and a non-root public URL.
Learn how to configure a non-root public URL by running npm run build.
-->

Project Zed

Zed Projects

going to keep the title as Project Zed for now
In src/App.jsx
https://github.com/WillzMu/projectZed/pull/34#discussion_r332215011:

@@ -2,7 +2,7 @@ import React, { Component } from 'react'
import firebase from './config/firebase'
import Card from './components/Card'
import Navbar from './components/Navbar'
-import SignInModal from './components/Modals/SignInModal'
+import SignInModal from './components/Modals/SigninModal'

lets keep this as SignInModal for now please
In package.json
https://github.com/WillzMu/projectZed/pull/34#discussion_r332216714:

@@ -16,7 +16,7 @@
"react-dom": "^16.6.3",
"react-modal": "^3.9.1",
"react-redux": "^7.1.0",

"react-scripts": "^2.0.0",

"react-scripts": "^3.2.0",

thanks. would definitely want to update this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WillzMu/projectZed/pull/34?email_source=notifications&email_token=AE7L5SJ6F2MSJYQ6V4VMSC3QNOK5RA5CNFSM4I6JETDKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCHEPPFY#pullrequestreview-298383255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE7L5SPFJPZEB756XR6PC5TQNOK5RANCNFSM4I6JETDA
.

will close this PR as it hasnt been updated for some time


Multiple inline mathematical expressions fails to render

Working Markdown example:
Here is some math that will work: `$x^2$`
This math will render, too: `$z^3$`

Generated RST:
Here is some math that will work: :math:`x^2`
This math will render, too: :math:`z^3`

Broken Markdown example:
But only the first math (`$x^2$`) in this line will render. This one (`$x^2$`) will not.

Generated RST:
But only the first math (\ :math:`x^2$`) in this line will render. This one (`$z^3`\ ) will not.

I've incorporated these examples as tests and should be fixed in the next release.


@ and ~ keys are still on mac layout

@ is still on Alt-L
~ is still on Alt-N
It would be super nice to get that too <3

Hi @lenalebt, sorry for not getting back to you sooner. Could you explain a bit more what you mean by this? (I no longer have a Mac, so I am unsure exactly what you're asking for, sorry.)
Thanks.

So on a UK keyboard the @ symbol is just above the right shift key, and double quotes " should be shift + 2
Is there a way to add that? Perhaps there needs to be US/UK keyboard layout files?
Thanks for putting this together btw, it's just saved my life.

Sorry @rux616 that I did not come back earlier. I have my setup changed by quite a bit since I opened the issue and am unsure where what setting exactly comes from.
The original issue was about that I now have e.g. the @ sign on AltGr+Q, but you can still type it with Alt+L. Any way to disable that? I have the same problem with a bunch of other keys as well. Main reason is that I cannot use Alt-L for other keybindings anymore now. Same is true for Alt-N (~).


feat: LDK gateway supports setting an LSP for LSPS2 (JIT Channels)

After talking with tnull, it sounds like LSPS2 (JIT Channels) isn't a good fit for the lightning gateway use-case. This is because one of the two trust models of LSPS2 states:

The LSP trusts the client to actually claim their payment once the channel is opened and the payment is forwarded.

Since this is in the hands of the fedimint user who initiated the inbound payment rather than the gateway itself, the gateway could involuntarily breach the trust of the LSP.
LSPS1 (Channel Request) appears to be more well-suited for the gateway. Channels can be requested from the LSP at any time, without needing an inbound payment.
'm hesitant to close this PR just yet. I'll keep it as a draft for now in case we might want LSPS2 support for the gateway operator to send funds from elsewhere to the gateway.

LSPS1 is what we actually want


Updated App install banners samples for #128

cc @addyosmani @jeffposnick

Can you add a reference to https://github.com/GoogleChrome/samples/blob/gh-pages/styles/main.css to all three index.html files?

Thanks for making these updates, Paul! There are a few inline comments that apply to all three index.htmls if you keep the current structure. (I probably should have caught some of them from the initial review.)
I'm wondering whether you want to consider structuring this slightly differently—instead of moving the existing https://github.com/GoogleChrome/samples/blob/gh-pages/app-install-banner/index.html file to a basic-banner directory (and potentially breaking any sites that link to that old URL), what about just adding in the functionality from the useraction-banner sample into the existing file? Then you can do away with the useraction-bannerdirectory.
Keeping the new canceable-banner in a separate directory is fine by me.

Hmm, I could do.  I did what I did so that in theory links would still point to a root directory and I can disambiguate there (which I think I should sort out).
I'll deal with all the other comments first.

@jeffposnick a bunch of updates:

added a new index file for all existing links
fixed comments
can't undo the autocaptilaize (which needs to be pushed up anyway).

Okay, looks good in general, and I don't have objections to creating an index that points to the other samples. I had two additional comments after going over the revised code.

:+1:


Swagger API page is empty

After deploying superset in docker, the swagger page(/swagger/v1) displayed nothing except the superset menu header.
The configuration FAB_API_SWAGGER_UI has been set to True in config.py.
Expected results
All superset APIs should be listed.
Actual results
An empty page.
How to reproduce the bug
Go to https://host:port/swagger/v1
An empty page was displayed

@kgabryje I checked and it seems CSP is blocking the Swagger inline scripts.

Thank you for reporting this issue. A fix was done on FAB to support nonce's also, currently release on 4.3.4rc1. Hope to publish a final release soon

FAB 4.3.4 is out and considered a new minor version on Superset

Hi. I still get an empty page for /swagger/v1 when using the latest-dev image. I built from that image 6 days ago. Any help would be appreciated.

As of 3.0.0, I also get an empty page.

Disabling Talisman fixed this issue for me. I am not sure how the two should be related. Logging in as the administrator from the UI should give you access to Swagger's UI.

Disabling Talisman fixed this issue for me. I am not sure how the two should be related. Logging in as the administrator from the UI should give you access to Swagger's UI.

Talisman sets CSP that is currently preventing a swagger css and a js code block from running

I still have an empty page with v3.0.0. Should I still need to disable Talisman for this?


Add IP address in ERROR [Controller:CheckLogin] log messages

Might it be possible to add IP address in these log messages in order to be combined with fail2ban ?
[ERROR] [Controller:CheckLogin] unable to find this user: foo
[ERROR] [Controller:CheckLogin] invalid password for "foo" (crypto/bcrypt: hashedPassword is not the hash of the given password)

@rickhub666,
The initial changes have been merged, which addresses your suggestion for reporting the IP address. I have another pull request to also add the IP address to API login failures.
I'm mentioning it here because if you update your fail2ban settings, make sure to include the API failures as well, otherwise bad actors will still be able to brute force.


how to use registerFilter or the range sliders together with Mixitup Multifilter

We are trying to implement the range sliders in our website that is using the multifilter plugin.
We implemented it according to this demo:
https://demos.kunkalabs.com/mixitup/filtering-by-range/
But when we use the registerFilter the entire multifilter stops working. We can't filter with the other filters anymore. The new range filter is the only one that works.
On the live website we are using the filter() method, but this doesn't work in combination with the other filters.
https://cultuurenschoolutrecht.nl/voor-leerlingen-po/
On the test server we have added the function registerFilter() with the date range filter, but now the other filters don't do anything anymore.
https://csu.studionaam.com/voor-leerlingen-po/

Hi! Were you able to find a solution to this? I'm having the same issue when having range sliders and multifilter.

No, we ended up creating our own javascript for this specific website. Not as fancy, but it works :)

It also seems that mixitup.registerFilter is not documented..


Question: How to add shortcut to Vue Router Link?

I'm trying to add a shortcut to a vue router link but I can't figure out what I need to do to get it working:
<router-link v-shortkey.once="['ctrl', 'shift', 't']" @shortkey="navigate" to="/items/add">
   Add Item
</router-link>

The "navigate" method referenced in the "shortkey" event handler is never called. What do I need to do to get this to work?

Hi,
You should use the native modifier to catch the event, see https://github.com/iFgR/vue-shortkey#using-on-a-component

@CalebKester sorry after struggling with this issue I gave up on the problem so I don't have a solution to share. Let us know if you found a working solution.

@ncjones I realized my solution was simple. I wanted to reuse the same route, so i just did this:
		<router-link
			v-shortkey.once="['k']"
			v-if="$slots.left"
			:to="left.to"
			:class="[$style.link, $style.linkLeft]"
			title="hotkey: [ k ]"
			@shortkey.native="navigate(left.to)"
		>Back</router-link>```
...

methods: {
	navigate(to) {
		this.$router.push(to);
	},
},```


Add support for calculating the cyclomatic complexity for cobertura output

See https://en.wikipedia.org/wiki/Cyclomatic_complexity.
According to 1 this is "just"

It will begin by adding 1 point for the function declaration, after that it will add 1 point for every if, while, for and case.

It will begin by adding 1 point for the function declaration, after that it will add 1 point for every if, while, for and case.

I don't want to just accept this solution (it seems more like a hack), so I will try to prove it. According to your Wikipedia link the cyclomatic complexity is calculated like this:
M=E-N+2P

where,

M: cyclomatic complexity
E: number of edges in the graph
N: number of nodes in the graph
P: number of connected components

The directed graph contains all single instructions including function definition as single nodes and the possible control flow is represented as directed edges between these nodes. An empty function has only a single node and one connected component: M=0-1+2*1=1. Fine.
All of our instructions does only change the number of nodes and edges and do not add more connected components. In the result we will only have one connected component so we can fix the number P at 1.
All normal instructions that have no influence to the control flow introduces one node and one edge into the graph which results in no difference to M. We can ignore them.
The atomic if instruction introduces three nodes (if-statement, true-case, false-case) and four edges (from if to true/false, from true/false to next node). This will change M by 4-3+2*0=1.
An atomic while instruction introduces two nodes (while, body) and three edges (from while to body, from body to while, from while to next node). This will change M by 3-2+2*0=1
An atomic do-while instruction introduces three nodes (do-statement, body, while-check) and four edges (do-statement to body, body to while-check, while-check to do-statement, while-check to next node). This will change M by 4-3+2*0=1.
An atomic for instruction introduces two nodes (for, body) and three edges (from for to body, from body to for, from for to next node). This will change M by 3-2+2*0=1.
A switch instruction is like a list of n if-instructions. n is the same number of the case instructions. So, we only need to count the number of case and add one for each.
A normal if, while, do-while and for statement can contain more than one conditions combined with && or ||. Each condition has to be counted separately as they can be rewritten as nested if-statements. The number of conditions is the same number of atomic if-statements.

From Wikipedia:
However, this is true only for decision points counted at the lowest, machine-level instructions.[4] Decisions involving compound predicates like those found in high-level languages like IF cond1 AND cond2 THEN ... should be counted in terms of predicate variables involved, i.e. in this example one should count two decision points, because at machine level it is equivalent to IF cond1 THEN IF cond2 THEN ...

In the result. I mostly agree with your simplification but we need to count the number of conditions inside if, while and for. As long as there is no better solution we can hack this by counting the number of && and || and add one to it.

We also need to count the ternary operator cond ? a : b as they can be rewritten to an if-statement.

Very nice derivation! There is also SelectNumber btw.

Thinking about this, this can be done with a set of regular expressions. There is no need for an Igor parser & lexer. To prevent wrong matches with strings we can add a preprocess to remove the content of strings:
// original line
string op = SelectString(condition, "||", "&&")
// preprocessed line
string op = SelectString(condition, "", "")

We are only interested in the number of if\s*\(, while\s*\(, for\s*\(, case\s*:, &&, \|\|, \?, (?<!\w)SelectString\s*\(, (?<!\w)SelectNumber\s*\( matches and therefore is the content of strings irrelevant.

I would think that try/catch also is a condition or?


JSON to TOML jobs for advanced-tutorial.md

Adding @PatrickAlphaC  feedback here:
docs/Introduction/tutorials/advanced-tutorial.md:
1b. Initiators
Initiators are what start, or initiate, a job inside an Oracle. In the case of a Request and Receive job, the RunLog initiator monitors the blockchain for a request from a smart contract. Once it catches a request, it initiates the job. This runs the adapters (both core and external) that the job is configured to run eventually returning the response to the requesting contract.
Internal Initiators have been "sort of" replaced by "type" of jobs. And "runlog" type/initiator has is now direct request jobs. https://docs.chain.link/docs/jobs/types/direct-request/ as runlog has been deprecated.

Could we add this context here?

1c. Core Adapters
Could we point everything to tasks instead of adapters? Maybe a callout saying that adapters are no longer supported?
https://docs.chain.link/docs/tasks/
Each oracle job has a configured set of tasks it needs to carry out when it is run. These tasks are defined by what Adapters they support. For example: if a job needs to make a GET request to an API, find a specific unsigned integer field in a JSON response, then submit that back to the requesting contract, it would need a job with the following Core Adapters:

HttpGet - Call the API

swap these for their task counterparts

HttpGet - Calls the API and returns the body of an HTTP GET result for ETH/USD pair.  Example:
Let's walk through a real example, where you will retrieve 24 volume of the ETH/USD pair from the cryptocompare API.

HttpGet calls the API and returns the body of an HTTP GET result for ETH/USD pair.  Example:

Could we use the TOML version of this?

It looks like:
type = "directrequest"
schemaVersion = 1
name = "Get > Uint256"
contractAddress = "ORACLE_CONTRACT_ADDRESS"
maxTaskDuration = "0s"
observationSource = """
    decode_log   [type=ethabidecodelog
                  abi="OracleRequest(bytes32 indexed specId, address requester, bytes32 requestId, uint256 payment, address callbackAddr, bytes4 callbackFunctionId, uint256 cancelExpiration, uint256 dataVersion, bytes data)"
                  data="$(jobRun.logData)"
                  topics="$(jobRun.logTopics)"]

    decode_cbor  [type=cborparse data="$(decode_log.data)"]
    fetch        [type=http method=GET url="$(decode_cbor.get)"]
    parse        [type=jsonparse path="$(decode_cbor.path)" data="$(fetch)"]
    multiply     [type=multiply input="$(parse)" times=100]
    encode_data  [type=ethabiencode abi="(uint256 value)" data=<{ "value": $(multiply) }>]
    encode_tx    [type=ethabiencode
                  abi="fulfillOracleRequest(bytes32 requestId, uint256 payment, address callbackAddress, bytes4 callbackFunctionId, uint256 expiration, bytes32 data)"
                  data=<{"requestId": $(decode_log.requestId), "payment": $(decode_log.payment), "callbackAddress": $(decode_log.callbackAddr), "callbackFunctionId": $(decode_log.callbackFunctionId), "expiration": $(decode_log.cancelExpiration), "data": $(encode_data)}>
                 ]
    submit_tx    [type=ethtx to="ORACLE_CONTRACT_ADDRESS" data="$(encode_tx)"]

    decode_log -> decode_cbor -> fetch -> parse -> multiply -> encode_data -> encode_tx -> submit_tx

externalJobID = "19747015-6833-40e7-b3fe-0fa1e76b843b"
Perhaps I'm scope creeping requesting this... Maybe it's a bigger project to update all JSON job samples to TOML.

let me know what you think.

solved by https://github.com/smartcontractkit/documentation/pull/669