Add -o json  flag to odo app delete

What is the purpose of this change? What does it change?

adding -o json flag to odo app delete
Was the change discussed in an issue?

https://github.com/redhat-developer/odo/issues/1383
How to test changes?

odo app create myapp
odo app delete myapp -o json
and check its exist code is 0 and not asking for user inputs

:white_check_mark: odo build 2074 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/711e73d017 by @syamgk)

:white_check_mark: odo build 2080 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/f040ecc801 by @syamgk)

:white_check_mark: odo build 2090 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/05b1e319ee by @syamgk)

:white_check_mark: odo build 2097 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/bf19460979 by @syamgk)

/retest

Missing documentation. Please add those supported documentation for -o json.

its self explanatory
If you do odo app --help you will get all the options

@syamgk Some changes are added to OpenShift CI. Can you please rebase the pr to avail those changes and avoid prow failure.

@syamgk Some changes are added to OpenShift CI. Can you please rebase the pr to avail those changes and avoid prow failure.

rebased!!!

:white_check_mark: odo build 2131 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/f99fd62b11 by @syamgk)

3 approves, but no lgtm :-(

/lgtm

@syamgk Seems you need to rebase it again as source issue on 4.0 went in few moments ago

/refresh

/lgtm

/lgtm
/hold
Let CI go green. Then use /hold cancel to allow merge

:white_check_mark: odo build 2147 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/d51708b0a5 by @syamgk)

/retest

/retest

/retest

/lgtm

:white_check_mark: odo build 2152 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/de94ad0bf4 by @syamgk)

CI is green. 3 approvals.
/hold cancel


Migrate Color.toString() test, improves equalsIgnoringHashCodes

This migrates the last failing test for https://github.com/flutter/engine/pull/54981.  In order to effectively resolve that test I had to make equalsIgnoringHashCodes more usable by printing out the line that differs instead of just a huge blob of "expected" vs "actual.
example
Here's the output after the change.
test
  test('equalsIgnoringHashCodes - wrong line', () {
    expect(
      '1\n2\n3\n4\n5\n6\n7\n8\n9\n10',
      equalsIgnoringHashCodes('1\n2\n3\n4\n5\n6\na\n8\n9\n10'),
    );
  });

output
Expected: normalized value matches
          '1\n'
            '2\n'
            '3\n'
            '4\n'
            '5\n'
            '6\n'
            'a\n'
            '8\n'
            '9\n'
            '10'
  Actual: '1\n'
            '2\n'
            '3\n'
            '4\n'
            '5\n'
            '6\n'
            '7\n'
            '8\n'
            '9\n'
            '10'
   Which: Lines 7 differed, expected:
          'a'
          but got
          '7'

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks like some checks are unhappy on this one.

Looks like some checks are unhappy on this one.

@goderbauer It was a bad rebase, it missed my last PR that landed somehow.  It should be good now.

LGTM, but can you add a test to test the new matcher output?

None of the output for matchers are tested because there's no way to grab the text.  I think we'd have to make the Matcher exported in order to be able to test the output text.  I figured that was by design.  Let me know if there is another way.

LGTM, but can you add a test to test the new matcher output?

I found a way to do it by catching the exception, done.


Minor typos and clarifications

Asking for @yukis4san's review as the original author of these lines, to confirm that I understood correctly 🙏


[Regression]Default values are no more added on attribute completion

when calling completion for instance on "timer:timerName?" and choose "period"
it should end up with "timer:timerName?period=1000" but it currently completes with ""timer:timerName?period" only

introduced with https://github.com/camel-tooling/camel-language-server/issues/55

another related issue detected:
when the uri is empty, there is no completion

verified in Eclipse (standalone) - Tooling for Apache Camel based on Apache Camel implementation of Language Server Protocol <IP_ADDRESS>809120921


Overlays: allow overlays to be specified as a file

Motivation for this change
This allows overlays to be specified as a file containing a list of overlays in two ways:

<nixpkgs-overlays> can point to a file.
~/.confix/nixpkgs/overlays.nix can be used.

This enables two use-cases which have bothered me (and several other people on IRC):

It allows you to specify overlays for Nixpkgs with an explicit order. Currently you can do this on NixOS with the nixpkgs.overlays option, but Nixpkgs has to use the directory method, which cedes control over what order the overlays are applied in.
It allows you to conveniently share an overlays specification between a NixOS system configuration and user nixpkgs, by both importing a file as nixpkgs.overlays and symlinking it to ~/.config/nixpkgs/overlays.nix. Currently NixOS uses an explicit list and Nixpkgs uses a directory, which is annoying. (You can use NIX_PATH, but I prefer doing it more explicitly.)

This is the same approach that you can use for config.nix, which makes things nice and consistent.

Based on https://github.com/NixOS/nixpkgs/pull/28082 for documentation.
@nbp
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks for the comments!

I do not like the idea of ~/.config/nixpkgs/overlay.nix , as this defeat the purpose of having overlays.

Could you expand on this comment a bit? I don't quite understand how it defeats the point of having overlays.
To guess a bit: currently the selection of which overlays to use is implicit in the filesystem, rather than explicit in the config (except in NixOS). This means that you can alter which overlays you use without having to change your configuration.
The alternative is to configure the list of overlays explicitly (like in NixOS). Personally, I prefer this approach, but I can see the attraction of the implicit version. It's also more consistent with config.nix - the configuration is just a file.
However, this PR merely adds the option of providing the overlays explicitly, you can still use a directory if you want. The use cases that I mentioned seem to mostly bother people who want to be explicit about everything (like me!).

NixOS gives you the ability to set the environment variable, thus you could technically define from NixOS the NIX_PATH environment variable with the extra overlays.

Firstly, without the ability to set <nixpkgs-overlays> to a file this solves only the second use-case, not the first.
Secondly, I think there are actually three logically distinct ways of setting things. Let's compare with config.nix:

For the NixOS system Nixpkgs: nixpkgs.config
For the user Nixpkgs: ~/.config/nixpkgs/config.nix
For the user NIxpkgs of all users of a NixOS system, by the globally set NIXPKGS_CONFIG variable (set to /etc/nix/nixpkgs-config.nix).

Note that I think this should be like <nixpkgs-overlays> and come from NIX_PATH instead, see https://github.com/NixOS/nixpkgs/issues/28085.

This gives you a couple of options to solve the second use case for config.nix:

Use one file for config.nix and then either:

Symlink it to ~/.config/nixpkgs/config.nix; or
Symlink it to /etc/nix/nixpkgs-config.nix.

Now, I don't think that either of these is obviously superior to the other. The former will work also on non-NixOS systems, but the latter will work for all users. So I think there's a case for supporting both.
Setting NIX_PATH on NixOS to include <nixpkgs-overlays> would let us use the second approach, which I'm in favour of, but I think it's worth having both.

Other proposal ....

I think this would work, but I'm not a huge fan, since (among other things) it makes the types of overlays files more complex. We would also need to carefully specify how the "flattening" takes place.
I think I might understand better if I understood why you don't like the file-based approach :)

I do not like ~/.config/nixpkgs/overlay.nix because it implies that a file should be modified, and I am less convinced that we would have tools to handle the content of a file compared to having tools handle the content of a directory.
For example, the rust-overlay can be install with the following script:
https://github.com/mozilla/nixpkgs-mozilla/blob/master/rust-overlay-install.sh
In the Nixpkgs argument, there is a different way of calling Nixpkgs which makes it clear that this is not the ordinary Nixpkgs.
With the NIX_PATH, or -I, there is a deliberate configuration setup by the user.
With the file and the directory, external tools can been adding both of these, without the user noticing the fact that it might be using both.  I think we should probably support both at the same time, where for example the content of the directory is appended to the list provided by overlay.nix or the opposite.

Don't these arguments apply equally to config.nix? That's not easy for tools to manage either.
As I said, I can see the value in having the imperative style around - it works nicely for users who are using nixpkgs primarily through nix-env. Arguably having to edit config.nix is also a bad workflow for those people.
However, there are also people who want to write down everything explicitly, even for their user configuration (look at the excitement over NixUP!). overlays.nix won't be used unless it's present, so you have to opt-in, at which point you should know what you're doing. I don't think it's too awkward for the rust-overlay installation instructions to say "Run this script; or, if you're using an explicit overlays.nix, add the overlay to it".
In short, perhaps this is a feature that's not going to be used by everyone, but I think there are a lot of people around who will want to use it.

Don't these arguments apply equally to config.nix? That's not easy for tools to manage either.

Yes, and that's not a reason to keep making the same mistakes.
My problem is about having precedence between the imperative (overlay directory) vs. the declarative (overlay.nix file) approaches.  This will add more confusion to any user who only wants to use nix in both ways at the same time, and I think we should aim for the least surprises, i-e merging the overlay directory with the overlay.nix file.

FWIW, I found it very surprising that overlays.nix didn't already exist, because it seemed very natural to me to want to specify my overlays declaratively, like config.nix. Otherwise the symmetry between the two is very straightforward, and makes me expect a simple file next to config.nix.
While I don't like the idea of actually putting the overlays.nix file in the overlays directory, I do think that merging the two sounds plausible. I think it would be reasonable to concatenate:

<nixpkgs-overlays>
overlays.nix
The overlays in overlays
in that order, since that corresponds to roughly the precedence I'd expect (global -> declarative -> imperative). I notice that you discussed this a bit already https://github.com/NixOS/nixpkgs/pull/21243#issuecomment-276750798.

(Maybe we could merge the attribute sets for the various sources of config.nix too.)
If we did that, then I think this PR would look very similar to your suggestion of putting overlays.nix inside the overlays directory, except with more control over ordering (it makes more sense for the declarative overlays to go before all the imperative ones, rather than just before those that come after 'o'!).
I also note that nix files that evaluate to lists are going to be awkward for tools no matter where they are - in your alternate suggestion, what does the tool do with such a file in overlays? It seems just as stuck as if it were in overlays.nix.

[…] I do think that merging the two sounds plausible […]

  (if pathExists overlayNix then import overlayNix else []) ++
  (if pathExists overlayDir then overlays overlayDir else [])

I still think that this is nicer to have <nixpkgs-overlays> take precedence.
The problem I see with the introduction of the overlay.nix file, is that <nixpkgs-overlays> was made to be able to just have another directory and use it as a replacement.  Having both sources, i-e overlay.nix and overlay directory, implies that one cannot replace one directory by just another directory with <nixpkgs-overlays>.
Thus, maybe, instead of merging them, we should make them exclusive, in a way that we get an error if both the overlay.nix file, and the overlay directory are present at the same time.

Okay, leaving the merging to one side because it's tricky and we can do it later.
What do you think about this point that I made?

I also note that nix files that evaluate to lists are going to be awkward for tools no matter where they are - in your alternate suggestion, what does the tool do with such a file in overlays? It seems just as stuck as if it were in overlays.nix.

If that's true then it looks like your alternative has the same problem with tools, in which case I think my suggestion is the simplest thing that gets us some of what we want.

You consider the aggregate as a single unit, which can be installed/removed. For example nixpkgs-mozilla repository would benefit from becoming such aggregate in the future, instead of doing complex work-around to redo the extend logic for such aggregation of overlays.

Right, but consider our example use case. As I understand it, you suggested that you create a file overlays/nixos-overlays.nix containing the overlays used in NixOS. But then these overlays can only be managed as a unit, even if they are logically separate (which they might well be, there is no particular reason why the set of overlays used in your NixOS configuration should be monolithic). But then this can't be managed. So a user who wants to have the same set of overlays in NixOS and outside isn't going to be able to use the tool to manage them, regardless.
Although, I wonder if it would be so hard to manage overlays.nix files if they were in a relatively simple format. I'm thinking of how Emacs will manage some parts of your init.el for you, despite that being code.
I actually find the argument about overlays being annoying to compose quite convincing. If it were easy to compose them then the mozilla overlay could just do that, but since we're pre-nixpkgs we can't provide an nice library function. So I guess it's somewhat nice to be able to distribute a list of overlays as well.
However, that's an argument for allowing files that are lists of overlays in overlays, I don't think it's necessarily an argument for not having overlays.nix. overlays.nix is still the only thing that gives you complete control over what overlays are used, and what order they're applied in. Anything that uses the directory sacrifices that.

I actually find the argument about overlays being annoying to compose quite convincing. If it were easy to compose them then the mozilla overlay could just do that, but since we're pre-nixpkgs we can't provide an nice library function. So I guess it's somewhat nice to be able to distribute a list of overlays as well.

This is not actually true, because we can already use super, but this far from being easy to understand.

However, that's an argument for allowing files that are lists of overlays in overlays, I don't think it's necessarily an argument for not having overlays.nix. overlays.nix is still the only thing that gives you complete control over what overlays are used, and what order they're applied in. Anything that uses the directory sacrifices that.

As I mention, my issue is that they are both controlled with the file system, and every program can mutate it without approval.  Having one way being added which takes precedence over the other will lead to weird errors, which after installing an overlay, a user will not see the previously installed overlays.
This, alone, leads to either merging them or have exclusively only one of them.
Then, the idea of , was to be able to replace one directory by another. Merging overlay.nix with the overlay directory implies that the promise of  no longer hold.
Thus, we should accept one (x)or the other, but not both.

As I mention, my issue is that they are both controlled with the file system, and every program can mutate it without approval. Having one way being added which takes precedence over the other will lead to weird errors, which after installing an overlay, a user will not see the previously installed overlays.

This isn't true with my original proposal, I think? Either you're using overlays.nix, in which case imperative overlays management is effectively "off" (and the tool can know this), or you're not, and installation is never going to create it.

Then, the idea of , was to be able to replace one directory by another. Merging overlay.nix with the overlay directory implies that the promise of no longer hold.

Yeah, I'm not sure about the merging, which is why I'd like to focus on the original proposal. Note that <nixpkgs-overalys> can still be a directory, so you can still replace a directory with a directory (or file) in that way.

Either you're using overlays.nix, in which case imperative overlays management is effectively "off" (and the tool can know this), or you're not, and installation is never going to create it.

And my point is, that we should raise an error if both exist, such that if a bad install script create the other  file, the user can blame the script for introducing such error instead of blaming Nixpkgs for not reading the installed files.

Okay, I admit that I can't think of a good reason to have both overlays.nix and an overlays directory.
So the proposed logic would look like this:

First, <nixpkgs-overlays> if it exists, is used. The path can be either a file or a directory.
Then we look to see if overlays.nix or overlays exists. If both do then it's an error. If exactly one exists, then it is used.

Does that look right?

That sounds good to me.
Thanks for this discussion.

Likewise, very productive :)
I'll implement that and get back to you.

Updated as discussed.

Thanks for your comments, I've applied them.
Do you think this should be announced on the mailing list or mentioned in the release notes?

Looking at the number of likes , feel free to announce.
I think adding it to the release notes of 17.09 would be good.

I've added a release note.


Add ability for SourceModel subclasses to register themselves

#159 provided some prefactoring to make it easier to add a new SourceModel subclass.
When adding a new SourceModel subclass a developer still needs to

add the source_type to the SourceCollection.model function switch
add the icon action event handler to SourcePanel and specify a widget
add itself to the dictionary of sourcetypes held in SourcePanel
add its creation widget to the dictionary in AddSourceWidget

Ideally some registration method should be provided that can set all of these properties at one time.
Maybe a method on the minerva application object?  And when a developer defines a new SourceModel subclass, in that same source file there could be an immediate that registers the subclass with the minerva application object.  This provides some ability to define client side code outside of minerva and have it imported into minerva simply by enabling another girder plugin (assuming minerva's core template loads only client side code from enabled plugins, which is a good change anyway).
I'd love to hear any other good ideas or potential problems with this approach.

A required part of this will be updating the "add a source" documentation.

I think this is the sort of approach we've been thinking about for all of the client-side code in Minerva (read: plugin system), not just source models.
I think using the Minerva application object as a sort of registry makes sense. In fact, other girder plugins could have their own gruntfile namespacing jade/stylus files as my_own_plugin.templates so all the client-side code could be self-contained.

I think this is the sort of approach we've been thinking about for all of the client-side code in Minerva (read: plugin system), not just source models.

Agree. @mgrauer your approach sounds good to me. Having registry within the minerva application object is good as well. I don't have much to add.

I agree this is desirable for all the client-side code, but sources are closest to having the api defined cleanly enough.  What's nice is by making it easier to add new sources within Minerva this way, we also enable the ability from plugins.
Analyses would probably be next.
Datasets would be harder, as you'd have to also add some ability to render a new type that Minerva wasn't aware of.  Changes to support #157 can enable this.

Analyses would probably be next.

I was thinking the same that Analysis can be dealt in very similar way.

Datasets would be harder, as you'd have to also add some ability to render a new type that Minerva wasn't aware of. Changes to support #157 can enable this.

I think what we need is readers that can read datasets and convert them into features or layers. For example, a GeoJSON can be read by geojson reader and coverts them into features which then can be added a a new layer or existing layer. In case of WMS dataset, it is mostly likely be a new layer altogether.

Two other approaches to consider

wrapping views from plugins
responding to UI issued events

Related, see this comment from @danlamanna .

This is moot now, Sources are being killed off, at least in terms of the client side Source Model and Source Panel.
see https://github.com/Kitware/minerva/issues/275


Error attempting to install mssql-tools on Ubuntu Docker 'Unable to locate package mssql-tools'

I'm attempting to install full text support alongside mssql-tools into an Ubuntu based Docker container. I'm using the Dockerfile provided at

# Install prerequistes since it is needed to get repo config for SQL server
RUN export DEBIAN_FRONTEND=noninteractive && \
    apt-get update && \
    apt-get install -yq curl apt-transport-https && \
    # Get official Microsoft repository configuration
    curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add - && \
    curl https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list | tee /etc/apt/sources.list.d/mssql-server.list && \
    apt-get update && \
    # Install SQL Server from apt
    apt-get install -y mssql-server && \
    # Install optional packages
    apt-get install -y mssql-server-ha && \
    apt-get install -y mssql-server-fts && \
    # Cleanup the Dockerfile
    apt-get clean && \
    rm -rf /var/lib/apt/lists

# Run SQL Server process
CMD /opt/mssql/bin/sqlservr```

@paulspencerwilliams Hi Paul, This Issues website is for reporting errors in the documentation under
https://docs.microsoft.com/sql/.
If you are reporting a documentation error, can you please include a link (or exact web URL) for the offending documentation article.  That URL will help us understand and react.
I will leave this Issue 1828 open for a day or two, to give you time to add another comment with the URL.
I will check back into this Issue to monitor, but even better is if you can include an @ notify to me in your new comment.
Thanks a lot.

I have not seen the additional info from the original poster that we would need to proceed.
It is time for me to Close this Issue 1828.

Got the same error:
FROM ubuntu:16.04

RUN apt-get update && apt-get install -y openssh-server
RUN mkdir /var/run/sshd
RUN echo 'root:THEPASSWORDYOUCREATED' | chpasswd
RUN sed -i 's/PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config

# SSH login fix. Otherwise user is kicked off after login
RUN sed 's@session\s*required\s*pam_loginuid.so@session optional pam_loginuid.so@g' -i /etc/pam.d/sshd

ENV NOTVISIBLE "in users profile"
RUN echo "export VISIBLE=now" >> /etc/profile

EXPOSE 22
CMD ["/usr/sbin/sshd", "-D"]

and than run container and execute following:
#https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools?view=sql-server-ver15
apt-get -y install curl
curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add -
curl https://packages.microsoft.com/config/ubuntu/16.04/prod.list | tee /etc/apt/sources.list.d/msprod.list
apt-get update
apt-get install mssql-tools unixodbc-dev


Add docs for project and cluster catalogs

can you rebase off of staging branch? @mrajashree

LGTM

LGTM again! :)


Migrate @metamask/eth-json-rpc-provider to core monorepo

As part of Shared Libraries Q3 OKRs, the team would like to migrate @metamask/eth-json-rpc-provider libraries into this monorepo to make it easier to maintain.
See #1079 comment for instructions on accomplishing this.

Hey team! Please add your planning poker estimate with Zenhub @cryptodev-2s @Gudahtt @kanthesha @MajorLift @mikesposito


Not working with Comforts mod sleepbags

I'll look into it tomorrow

I'll look into it tomorrow

He said tomorrow at Februrary 11, now its 2024 xD


getting client IP if client is behind many proxies

Hi guys,
we have a small issue using socketio lib.
If client is behind load balancer clientIp is in some of the http message headers. Most often it is 'X-Forwarded-For' header or some custom one. This is covered setting remoteAddressHeader in configuration of ServerConfiguration.
Our problem is when client is behind many proxies - e.g two load balancers. In this case default behavior of load balancer is to append IPs to the header. For example if client IP is <IP_ADDRESS> and LB1 IP is <IP_ADDRESS> in 'X-Forwarded-For' we will have:
1st LB -> add <IP_ADDRESS> in 'X-Forwarded-For' header
2nd LB -> appends LB1 IP to the header
so we receive
HEADER: X-Forwarded-For = <IP_ADDRESS>, <IP_ADDRESS>
The general format of the field is:
X-Forwarded-For: client, proxy1, proxy2
(wikipedia: [https://en.wikipedia.org/wiki/X-Forwarded-For])
So is it possible to modify PipelineUtils.getHeaderClientIPParamValue to handle this case.
Thanks in advance,
Daniel

@antonkharenko   Privet

Hello and privet :)
Yes, it is possible to modify behavior, but what is the expected one in such case? I mean that then to get client IP you use Session interface getRemoteAddress() method, so should it return first address in the coma-separated list? should there be a possibility to get the full value of 'X-Forwarded-For' header? WDYT?

Since the final value will be in the following format:
X-Forwarded-For: client, proxy1, proxy2
You should know exactly the client IP, it's the first one.
But maybe you can add additional method that will return the whole thing also... not that I understand much, I'm just a manager ;)\

We now use it like this:
if (ip != null) {
ip = ip.split(",")[0];
}

this will keep current functionality as is and if header contains many IPs comma separated will return correct one.
Getting full value of specific header also will do the work.
Thanks,
Daniel

@dankata please check PR: https://github.com/scalecube/socketio/pull/42

Great,
we're waiting for the release :)

Fixed by PR https://github.com/scalecube/socketio/pull/42. And released new version 2.3.2 which contains following fix.

@armangal and @dankata this project is open source everyone are free to suggest a pr and fix
your contribution is more than welcome we need your support :)


[4.0] (Label/RichTextLabel) Spaces don't display after newline.

Godot version
v4.0.alpha.custom_build
System information
Windows 11, Vulkan, RTX 2060 Super (516.59)
Issue description
This is not reproducible in 3.x
If you put spaces after a newline, they don't get drawn. No errors in the console though.
I don't know if it's intended (probably isn't) and I haven't seen anyone report this.

No matter how many spaces are, it won't draw. This happens both in Label and RichTextLabel.
Restarting both Godot and the project doesn't fix the issue.
Steps to reproduce

Open a project
Place a Label node
Attempt the process from Issue Description
Check if the spaces render

Minimal reproduction project
None

I remember there was a trim_edges() somewhere in there in the text rendering code itself that prevented me from adding extra spaces when I tried to in https://github.com/godotengine/godot/pull/65140.
Yyeah, this didn't happen before, essentially voiding https://github.com/godotengine/godot/pull/64733.

I guess https://github.com/godotengine/godot/pull/65073 is trimming is too aggressively, should not do it after \n break.


iOS badge notifications don’t disappear after viewing posts

Describe the bug
The iOS badge counter doesn’t reset to zero (disappear) after viewing notifications: it only disappears after at least one post/reply/follow has been actively tapped.
To Reproduce
Steps to reproduce the behavior:

Do or post something that other users find engaging/encourages them to follow you
Note badge counter on iOS device
Open Bluesky app, tap on bell icon for notifications, but DON’T interact further with notifications
Close Bluesky app
Note that iOS badge counter is unchanged (even though you’ve “seen” the notifications)

Expected behavior
Badge counter resets to zero after opening the app and simply viewing notification list.
Details

Platform: iOS
Platform version: 16.6
App version: 1.42

Handing to @ansh 💪

This also happens in my browser as well.

Should be fixed with #1095

Same in Chrome on desktop (supposing the fix is not live yet).
Also: When I click on the notification in the left column, this should automatically show me the new notifications, without an additional click.

Should be fixed @ChronicleFlask
@stefanmve The issue you are mentioning is different. Since this issue talks about the native iOS badge. Please open a new issue if you are still facing the problem on browser/web.

I’ve just installed the latest iOS version (1.48 on iOS 16.6) and it isn’t fixed – the behaviour remains the same.

This isn’t fixed on iOS. The behaviour remains the same with the latest update.

Reopening because we're reverting the change that was made for this


Using brush for fine-grained zooming

I have implemented a complex raw signal data viewing application with D3. There is timeseries data visualized spanning up 15 hours with length and having definition of up to 200 Hz, meaning there is a data point for each 5ms period.
Measures have been taken that not too many datapoints are drawn in the browser at a time by reducing the amount of datapoints displayed.
This data series is using d3-brush to show a timeline for the full length of the period, while in the main screen there is a chart showing a window of the curve that can be zoomed inwards down to the definition of showing 10s or 5s time period.
Zoom is triggered by brushElem.call(brush.move, brushRange);
With this approach I'm hitting a limit in fine-grained zooming, where the brushRange, say [333, 334] would equal down to 1px width of the timeline. So basically with a common dataset scenario I'm limited to zooming in only down to 30s time period... Any less would amount to less than 1px width dimension on the timeline and it doesn't work anymore.
How to overcome this limitation?

Is it something similar to https://blockbuilder.org/Fil/076415313a08e76ae60d468e2cb25909 ?

@Fil yes it's very much similar implementation.
That example is triggering zoom in similar fashion by context.select(".brush").call(brush.move, x.range().map(t.invertX, t));
Trying out zooming there with dragging by mouse I can narrow down the zoom level to 4 days span, and then on it jumps somehow to a kind of zero span with label showing ':24' and no actual data drawn... Weird.

when you are brushing the selection s can be [387, 387] (it will be nulled when you release the mouse). At this point the code uses x.domain(s.map(x2.invert, x2)); and d3.zoomIdentity.scale(width / (s[1] - s[0])) and everything breaks on NaN.
A solution is to add a small value to the right-hand-side of the selection so that it's never 0 pixel wide
  var s = event.selection || x2.range();
+  s[1] += .5;

or more precisely
  var s = event.selection || x2.range();
+  if (s[1] === s[0]) s[1] += .5;


Can't see App Service variables for OAuth App configuration

As part of the environment set up, we have to update the following variables:

However I can't see these variables on my web app resource

Any help would be appreciated, thanks

If you don't see an existing one to edit, you can click "new" at the top to add it.

Thanks @jorupp, its fixed now and the solution works


bug: some snippets don't work.

Did you check docs and existing issues?

[x] I have read all the LazyVim docs
[x] I have updated the plugin to the latest version before submitting this issue
[x] I have searched the existing issues of LazyVim
[x] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.2
Operating system/version
Ubuntu 24.04
Describe the bug
I have searched through nvim-snippets, LazyVim and friendly-snippets for this issue.
https://github.com/user-attachments/assets/f84ef187-6a9a-4e77-9598-cf031f595788
In this video I deleted everything inside nvim/lua/plugins/
us is not my snippet. It's supposed to open useState snippet but instead it is giving me that error.
https://github.com/user-attachments/assets/a6f50609-c195-4122-b8ae-da4d6878c492
This is another weird behavior. this is after I ran
rm -rf ~/.local/share/nvim && rm -rf ~/.local/state/nvim && rm -rf ~/.cache/nvim and clean started with my config. same stuff.
Doesn't happen with my own snippets I use via nvim-snippets though.
here is my nvim config
Steps To Reproduce

use some snippet.
some work, some don't, some are "fixed automatically".

Expected Behavior
This didn't used to happen before 14'th update. Maybe blink or nvim-snippets is at fault? I don't have luasnip anymore.
Repro

Pretty sure this is Neovim's vim.snippet limitation. They only support LSP grammar-specific snippets and also not nested snippets (although I don't follow Neovim that close and maybe there's been changes regarding this). I tested with Luasnip and those 2 snippets of yours seem to work correctly. So, either use Luasnip or report this to Neovim if you want such features added. Not a LazyVim issue from what I've observed with my limited knowledge as a user.


Bump patch version

to release fixes for creating the cover with grid image.

could you add a note to the changelog in the readme?


fix bug pull model

Proposed changes:

rasa.core.agent._pull_model_and_fingerprint return None instead of Etag if model's fingerprint is identical
temp directory is created only when there is new model to pull

Fixes https://github.com/RasaHQ/rasa_nlu/issues/3086
Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

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

Thanks for submitting this PR, we'll give it a review as soon as possible

@jeanveau what is the bug you are trying to fix?

Hi,
here is the issue
https://github.com/RasaHQ/rasa_nlu/issues/3086

Yifan ZHANG
Tel: +(33) 6 26 12 72 21
On Mon, Apr 15, 2019 at 4:10 PM Tom Bocklisch<EMAIL_ADDRESS>wrote:

@jeanveau https://github.com/jeanveau what is the bug you are trying to
fix?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RasaHQ/rasa_nlu/pull/3248#issuecomment-483267396, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFU_HPgPX6gayPxwh07uJRWPKg-Btusqks5vhIhhgaJpZM4cryq6
.

https://github.com/RasaHQ/rasa/issues/3372

https://github.com/RasaHQ/rasa/issues/3372

Please review this https://github.com/RasaHQ/rasa/issues/3372

@manslogic it is on our list, @ricwo will look into it once he is back. We need to to test this, as there are no added tests this takes some more time.

@tmbo you guys doing great job, accept my gratitude.

@jeanveau thanks a lot for your contribution, I've addressed the review comments so we can get this fix into the next release :tada:


fix typo in romana-network-policy.md

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

lgtm

/lgtm
@@zhangxiaoyu-zidif please help review and approve

This PR touches two languages. It would be more typical to change just the English localization and then let localization teams pick up the updates.

This PR touches two languages. It would be more typical to change just the English localization and then let localization teams pick up the updates.

@sftim thanks for your suggestion, i have modified it.

Thanks for your PR @mysunshine92 !!!
/approve


gallery.removeEventListener

There should probably be a removeEventListener function. Currently I have a listener that I only want to fire the first time the event happens (after the first image has loaded). It would be nice to be able to clean up after myself.

Instead of removeEventListener, I'd recommend exposing the underlying options as seen below. That gives the possibility to use once, or signal which is the superior way to remove an event listener nowadays.
- public addEventListener(name: [...], callback: [...]): void {
-     this.elementRef.addEventListener(name, callback);
+ public addEventListener(name: [...], callback: [...], options?: AddEventListenerOptions): void {
+     this.elementRef.addEventListener(name, callback, options);

@PowerKiKi even better! Thanks, I didn't know you could do all those things with options.


Create quote_app.md

This adds a description for adding a quote app
📝 Description
This PR adds an app for random quote generation to motivate you anytime anywhere.
Add a brief description.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Dear user,
Thanks for your contribution. We found some problems in your app, as the screenshot shows. If there is any problem when using the data of the action, please feel free to contact us. Looking forward to your update.


Integration isn't picking up the yaml as envisalink_new

          Integration isn't picking up the yaml as envisalink_new. Renaming back to envisalink allows the integration to read the config on startup.  Here's the integration shown on the Devices&Services screen:

Needed to comment out the envisalink config and restart to allow me to add the envisalink_new integration. Once added, the yaml config needs to be in place for HA to load envisalink_new at startup. I haven't found the config entity.
I haven't been able to get envisalink_new to create the devices and services provided by the old envisalink component.
Originally posted by @garyak in https://github.com/ufodone/envisalink_new/issues/1#issuecomment-1424553863

How did you install this manually?  In config/custom_components/ or directly into the HA installation?
Are there any errors in your log file?  If not, can you try turning on debug logging:
logger:
  default: info
  logs:
    custom_components.envisalink_new: info

(The logging setup will likely only work if you installed it in config/custom_components/)
Do you have a firewall or anything that might be blocking access to the EVL?  The new integrating uses both port 4025 (for the main connection) but also port 8080 to interrogate the device to obtain the MAC address and some other info.
The intent is certainly that you only need to rename envisalink: to envisalink_new: in your configuration.yaml and restart HA.

I think I've got it working now. I Deleted the integration shown above, renamed the header back to envisalink_new, and restarted again. This is the result:

it seems, I had two, overlapping integrations installed. Not certain how, but deleting the one shown on the Devices&Services page exposed this one.
I captured some data before I deleted the integration with the header envisalink_new.
alarmlogging.txt

I installed into config/custom_components, left original envisalink config header, and restarted HA. I thought the new component would read the existing envisalink config and adopt the config for itself. No go. Next, I commented out the envisalink header and restarted, but still no devices/service. I then rechecked the Add Integrations to find that Envisalink_new had appeared in the list, so I installed the integration from Devices&Services page. Following that, the configure dialog was requesting the Host IP, credentials, and other items. It was clear it hadn't discovered the existing configuration.

Right, it can't automatically pull from envisalink: in your config because you can't have two integrations with the same domain (name) and it's that domain that determines what to look for in configuration.yaml.  I had to create a new name to avoid the conflict which means you need to rename your configuration entry (for now).
Because the changes are quite substantial, I wanted a way to allow volunteers to help me test in a safe way that allowed an easy way to switch back if there were problems.  Once I'm comfortable that things are solid, I'll be submitting the changes back to HA to replace the existing envisalink integration - at which point the _new naming will go away.

I'll run with your new code and report any irregularities. Sorry for the distraction. I misinterpreted the simple instructions given. It's been quite awhile since this component has been looked at. Thanks for taking this update on. It's one of the most valuable components at my house.

Thanks for testing!

FWIW - I see this issue is closed, but I'm not drawing a conclusion from reading this.
Is the answer that manual YAML configuration (at least of the connection details like host, user, password) won't work at this point because of the envisalink: vs envisalink_new: integration/config block naming?

Manual YAML configure does work and will continue to work (assuming I don't break anything accidentally).  The issue is that you cannot have entries for both envisalink and envisalink_new in your configuration.yaml because they will both be imported automatically and both try to connect to the same device.
So if you are using envisalink_new, all you should have to do to switch to it is rename envisalink: to envisalink_new: and restart HA.
Once I feel it's ready, my plan is to submit this integration as a PR into Home Assistant to replace the existing envisalink integration.  At that point, I will switch it to pick up envisalink: from configuration.yaml.  I just can't do that right now because the integration needs to have a unique name so it doesn't create a conflict.

So if you are using envisalink_new, all you should have to do to switch to it is rename envisalink: to envisalink_new: and restart HA.

   Sorry about that.
Now that I fixed that and restarted, but there is still a problem that the integration isn't configured.
I just see now that you created #18.  I'll reply there.


Missing deployment variables/Data type for TenantId

TenantId
A globally unique identifier (GUID), without curly braces ( { , } ), that is used as part of Windows Hello for Business provisioning and management.
There is no Deployment data on this?  I used String and "guid" however that wont work.
Can someone provide Syntax for this Passport for work CSP policy, TenantID?
Thanks,

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

ID: f4180b6e-2786-ffb0-8f92-e4456dc343c9
Version Independent ID: 7722d866-c095-b806-1da8-17e00cfe9a0a
Content: PassportForWork CSP
Content Source: windows/client-management/mdm/passportforwork-csp.md
Product: w10
GitHub Login: @MariciaAlforque
Microsoft Alias: maricia

@Heidilohr
Any updates with this issue? We would like to follow up and assist with content updates if necessary.
Thanks.

@officedocsbot assign @e0i

@Heidilohr Any updates?

Not sure, but would it help to check with @brianlic-msft or @nickbrower if there are anyone else available for follow-up to this issue ticket?

@manikadhiman Would you be able to provide assistance and direction regarding this issue as the new owner of content? Thanks.

Hi @e0i, I have reached out to the product team for this issue and issue#2522. I will update the status as soon as I hear from them. Thanks!

Hi @e0i, Here's the response from the product team:
The CSP documentation has information on how to retrieve the GUID, and the examples at the bottom of the page show the GUID being used. The following section shows the GUID for this case.

2

                    ./Vendor/MSFT/PassportForWork/5NEMDU42-45CC-8CBL-8BPF-D7092646325F

Hope this helps!

@ManikaDhiman Thank you for taking the time to follow-up.
@Tdiwestyguy
The issue is being closed since your question seems to be answered. Feel free to re-open this issue if you feel that it hasn't been answered or that there are further suggestions to improve the documentation itself.
Thanks.


Could not convert to geojson::Geometry

First of all, thanks for this library.
I am experimenting an issue converting from geos::Geometry to geojson::Geometry type. It looks like the readme has not been updated since this commit https://github.com/georust/geos/commit/1614a49deedc01b2f0cd4de24852105ba9cabe2f makes use of the std TryFrom trait.
I have this sample code:
    let pt = "POINT(1.0 1.0)";
    let pt = geos::Geometry::new_from_wkt(pt).unwrap();

    let geom: geojson::Geometry = pt.try_into().unwrap();

and the compiler shows this error:
error[E0277]: the trait bound `Value: From<geos::Geometry<'_>>` is not satisfied
  --> src/main.rs:79:38
   |
79 |     let geom: geojson::Geometry = pt.try_into().unwrap();
   |                                      ^^^^^^^^ the trait `From<geos::Geometry<'_>>` is not implemented for `Value`
   |
   = note: required because of the requirements on the impl of `Into<Value>` for `geos::Geometry<'_>`
   = note: required because of the requirements on the impl of `From<geos::Geometry<'_>>` for `geojson::Geometry`
   = note: required because of the requirements on the impl of `Into<geojson::Geometry>` for `geos::Geometry<'_>`
   = note: required because of the requirements on the impl of `TryFrom<geos::Geometry<'_>>` for `geojson::Geometry`
   = note: required because of the requirements on the impl of `TryInto<geojson::Geometry>` for `geos::Geometry<'_>`

I have the geos library with json feature enabled.
[dependencies]
geos = {version = "7.0.0", features = ["json"]}
geojson= {version = "0.20.1"}

Curiously, the code compiles by first doing a conversion to geo_types and then to geojson
    let geotypes_obj: geo_types::Geometry<f64> = pt.try_into().unwrap();
    let geometry = geojson::Geometry::new(geojson::Value::from(&geotypes_obj));

I found here https://github.com/georust/geos/blob/0a4862d722b593e7dbb60311e8a58e0e724ae13a/src/enums.rs#L5 that the crate has its own TryFrom trait, but I am not sure if it is related.
It looks like the geojson::Geometry type has not implemented the TryFrom crate within to_geojson.rs file.
Let me know your opinion

Thanks for the bug report! This is likely because of mismatched versions between dependencies. Can you cargo-tree to ensure all your geo-types and geojson dependency versions match?

@frewsxcv Thank you! Running cargo tree saw a mismatch between geojson (0.20.1) and the geojson crate used in geos (0.19.0). changing the version in Cargo.toml file worked perfectly

Glad that worked! I created a new issue for tracking the version mismatch: https://github.com/georust/geos/issues/82

For new users coming into this issue, please check https://github.com/rust-lang/rust/issues/22750


awesome/build: rebuild when a wayland protocol changed or added

It's a small change, but I think it's pretty useful nevertheless.

TIL about that flag.
Thanks!


Jest times out

First of all great example! 😉
In my machine, the test times out and the test fails. Maybe it would be good to set a longer time out.
test('performance audit', async () => {
 // tests happening
}, 20000) // longer time out

Yeah good idea! Would you want to PR this?


safe-cast repo disappearing act

Hi was attempting to package this at https://build.opensuse.org/package/show/home:jayvdb:py-new/python-pyfortified-requests
It depends on safe-cast
https://build.opensuse.org/package/show/home:jayvdb:py-new/python-safe-cast
When trying to get the real code for the tests of safe-cast, I wasnt able to find them.
https://pypi.org/project/safe-cast/ links to 404 https://github.com/TuneLab/safe-cast , the closest I can find is https://github.com/TuneLab/safe-cast but that looks like a much earlier and incompatible version.  And that repo has issues disabled.  Apologies for raising the issue here instead; if the real source repo isnt available any more, distros get concerned about the viability and licensing of it, so that dependency would need to be removed/replaced before a distro would accept my package for pyfortified-requests.
ping @StasTune and @jefftune

Same problem with pyhttpstatus-utils https://github.com/jefftune/pyhttpstatus-utils/releases


[WFCORE-6240] Upgrade Bouncycastle OpenPGP from 1.72.1 to 1.72.2

Jira issue: https://issues.redhat.com/browse/WFCORE-6240

Merged it since this is completely optional for WildFly


Can't get mouse events to pass through

Maybe I'm doing something wrong? Just running ttystudio, then running my CLI app (slap) in the new shell. Seems like mouse events are just being ignored. iTerm2 2.1.1 on OSX 10.10.4.

@dbkaplun, all mouse events, or just "all motion"/"mousemove events"? Tmux 2.0 no longer supports "all motion" so I had to add a strange workaround for it, but I'm still not sure it works 100% of the time.
What happens when you go to the blessed directory and run: $ node example/multiplexer.js and then inside the multiplexer run $ node test/program-mouse.js? When you move your mouse or start clicking, do you see any output?

Also, make sure you have the latest blessed (that includes the tmux 2.0 workaround if you're using it).

Nope, nothing. With just a bare shell inside ttystudio, I can't scroll the window at all, but without ttystudio I can scroll fine. (I don't expect the newly scrolled buffer to be picked up by ttystudio as this is handled by the terminal itself from what I understand but this may help debug the issue.)

Alright, I'll have to play around with this on iTerm2 right quick.


Added data connection check name availability operation

Added data connection check name availability operation as part of swagger operations completeness.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5798
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5798/commits/8404cd0bf7f330df146b1ea7c09719ba24d53cd8

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

@liatbezalel  kindly take care of the merge conflicts

Automation for azure-sdk-for-java

@RyanBensonMSFT did the latest changes take care of your requested changes?

@RyanBensonMSFT did the latest changes take care of your requested changes?

@praries880 @RyanBensonMSFT after discussion we decided to change the structure of the ckuck name availability as @RyanBensonMSFT  suggested.
We'll add a new iteration for that

@RyanBensonMSFT we are now aligned with the check name pattern. Can you please review the latest changes?


KeyError: 'in_scope'

If i comment bugcrowd from main.py and config.yml it is perfectly running...

It's because this script get data from somewhere else which has bug:
https://github.com/Osb0rn3/bugbounty-targets/issues/6

is there a fix for it ?
@Sh4d0wHunt3rX
@sohanatrana
@Alikhalkhali


Message to scalar flexibility

Likely, different applications will need different ways to map messages to scalars.
Things to consider:
How flexible we want to be?
The most flexible option would be to allow the position of a message to affect its encoding i.e., first message using hash-to-scalar, second message is zero centered etc. One way to do this would be with some short of a "schema". However an easier way could be to update the MapMessageToScalar interface to accept all the messages (instead of having to call that operation for each message separately). Specifically, the generic MapMessageToScalar will be defined as,
MapMessageToScalar(messages, dst)

An application can then define,
AppX_MapMessageToScalar(messages, dst)

Deserialization:

1. (msg_1, msg_2, ..., msg_L) = messages

Procedure:
1. scalar_1 = hash_to_scalar(msg_1)
2. scalar_2 = OS2IP(msg_2) mods r
3. ....

The MapMessageToScalarAsHash operation will then be defined as,
MapMessageToScalarAsHash(messages, dst)

Deserialization:

1. (msg_1, msg_2, ..., msg_L) = messages

Precondition

1. If length(msg_i) > 2^64 - 1 for i in (1, ..., L), return INVALID
2. if length(dst) > 255, return INVALID

Procedure:

1. for msg in (1, ..., L)
4.     msg_scalar_i = hash_to_scalar(msg_i, dst)
5.     if msg_scalar_i is INVALID, return INVALID
6. return (msg_scalar_1, ...., msg_scalar_L)

This will allow for that level of flexibility without having to define "schemas".
Who can define a MapMessageToScalar operation
Assuming that we would require every MapMessageToScalar operation to have a unique ID, there are going to be 2 options here:
A. Any application can define a new MapMessageToScalr operation.
The operations ID would then be added as a parameter to each of the core operations, and then passed to the domain value.
B. Only ciphersuites can define a new MapMessageToScalar opeartion.
The operations ID would then just be added to the end of the ciphersuite ID.
IMO, option B is better. If an application "needs" to define a new MapMessageToScalar procedure, its likely that they will use it for some cryptographic functionality (like predicate proofs) that would be best to be defined in some document either way (and define its own ciphersuites). The MapMessageToScalar operation needs to be defined in a way that would guarantee consistency as much as possible and option B is IMO the best for that.

Hope this captured our discussion on the call. Please correct me @tplooker, @andrewwhitehead if I missed anything

Discussed on WG call on 20th of Mar. Will ask feedback from IETF and re-visit.


extra is now an object {re: string, optional: boolean}

extra is now an object, full BW compatibility retained
Close #40, Close #39

@mosheBelostotsky can we rename extra to regex_suffix. I think it is more self-explanatory. What do you think?

@mosheBelostotsky looking good... please read the comments and make the appropriate changes. Thanks! 👍

@rqc I prefer to preserve extra for BW compitability...

@mosheBelostotsky we can still support extra, but start migrating to using something more readable like regex_suffix. That way it will be backwards compatible and forward readable 😉

@rqc WILCO :wink:

Looks great. I am merging.


Remove blue highlight and add right-facing caret in pregnancies/_menu.html.erb

From @mebates in #195 -
Currently, in the pregnancy edit view, you can see a full blue highlight over Abortion Information:

We should adjust this to match the designs, which feature a purple caret instead and no blue highlight:

(See also https://github.com/colinxfleming/dcaf_case_management/blob/master/_design/DCAFwireframe020816.pdf ).
Probably this involves busting into pregnancies.scss and editing the .abortion-left-menu.li.active styling.

Let's feel free to use the chevron-right glyphicon here - http://getbootstrap.com/components/#glyphicons

Added 'backlog' label as this is non-essential for first release.

The left navigation should also be a larger font-size; it is 17 px now and it should be 22 px. Users aren't noticing the left navigation very well.


Fix manpage: warning: macro `NP' not defined.

The lintian QA tool reported an issue with the nccopy.1 manpage for the Debian package build of 2.3.1:
warning: macro `NP' not defined.

Fixed by replacing .NP with .LP.
As I'm will not deal with legal documents like a CLA for such a trivial change, you can get the patch from the Debian source package if you will not merge this change without a signed CLA:
https://salsa.debian.org/debian-gis-team/netcdf/blob/debian/1%254.6.2_rc1-1_exp1/debian/patches/manpage-has-errors-from-man.patch

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

Odd. I just ran
nroff -man nccopy.1
and it did not complain.
If memory serves, .NP provides numbered paragraphs.
Does your lint tool take arguments like -man ?

You can reproduce the issue lintian reports with:
LC_ALL=en_US.UTF-8 MANROFFSEQ='' MANWIDTH=80 \
man --warnings -E UTF-8 -l -Tutf8 -Z ncdump/nccopy.1 > /dev/null

There is no .NP documented in groff_man(7)

Interesting. I did some searching and you are correct. The .NP macro is nowhere
defined. The notion of a numbered paragraph seems so basic that I am
very surprised that it does not (or no longer) exists.
So, the question is: how to do numbered paragrapsh in roff? The .LP
is not numbered, so that is not the best choice.

So this will work:
.IP "1."
.IP "2."
...
Can you submit a change to your PR to use that instead of .LP?

Can you submit a change to your PR to use that instead of .LP?

Not if merging it requires signing a CLA.
You're probably better of committing the changes yourself.

Ok, without the CLA, we will have to close this pull request.
I suggest that in the future you submit bug reports as issues
rather than pull requests. That way you will not be asked to sign
the CLA.

I forgot about your contributor unfriendly policies, because none of the other upstreams for which I maintain the Debian packages have a CLA.

Well you are not the first person to object to our CLA :-)

Superceded by pull request https://github.com/Unidata/netcdf-c/pull/1155


Use closing paren as a trigger character

This seems counter-intuitive based on the concept of "trigger character" but it provides a better function signature experience.

bors r+


Fails to build on i386: error: constructor cannot be redeclared

Component
n/a
Describe the bug
In file included from /wrkdirs/usr/ports/graphics/diplib/work/diplib-3.5.0/src/analysis/chord_length.cpp:31:
In file included from /wrkdirs/usr/ports/graphics/diplib/work/diplib-3.5.0/include/diplib/regions.h:26:
In file included from /wrkdirs/usr/ports/graphics/diplib/work/diplib-3.5.0/include/diplib/measurement.h:30:
/wrkdirs/usr/ports/graphics/diplib/work/diplib-3.5.0/include/diplib/label_map.h:62:16: error: constructor cannot be redeclared
      explicit LabelMap( std::vector< dip::uint > const& labels ) {
               ^
/wrkdirs/usr/ports/graphics/diplib/work/diplib-3.5.0/include/diplib/label_map.h:54:16: note: previous definition is here
      explicit LabelMap( std::vector< LabelType > const& labels ) {
               ^
6 warnings and 1 error generated.

log
To Reproduce
regular build
System information:

What OS do you have? FreeBSD 14.1
If PyDIP, what version of Python do you have?
If DIPimage, what version of MATLAB do you have? (type ver at the MATLAB command prompt, and copy-paste the result here).
If compiled from sources, what compiler and version did you use? clang-18

I'm guessing you have a 32-bit system? I hadn't thought of that... We should add a 32-bit build on the CI.

i386 is 32-bit system.

There seems to be a similar issue with the two definitions of GetLabelBoundingBox(). I'll look into that one in the morning.

@yurivict Thank you for reporting this!
The library now builds on with gcc -m32 on GitHub CI. I'm expecting you'll be able to build on your machine now.
There are a few tests that are failing now. I will look into that over the coming days.

@crisluengo
Thanks! I will test it once the next version would come out.

@yurivict I've made a new release.


Fix incorrect year

While reading "A Brief Breakdown of Monero's Ongoing Network Attacks", I noticed in the timeline section that the dates for the events of "PR7250" and "Monero v<IP_ADDRESS> released" has the incorrect years. I'm assuming that the correct year is 2021, with evidence from the Monero v<IP_ADDRESS> release.

Thank you so much for the fix, it's a huge help to have people assist in keeping these posts fresh and correct!


Update adopters.md

Adding adopter alauda.io, please refer to https://www.alauda.io/ai-machine-learning for more details of alauda.io

@typhoonzero Thanks for adding !

@typhoonzero Hey good to see you here!


Suggestion: On how to handle player radiation protection.

Rather than making armor that players would have to tediously change into every time they handled the yellorium, an extra nuisance if they need to clime up the reactor with out a jet pack, you could make it an enchantment.
It could be applied to most armors and even jetpacks.
And preferably be applied by crafting the armor surrounded by reactor casing blocks.
A simple system that could be configured to make it much harder to make if needed.

I personally like the idea of stand alone armour.

Climes up to the top of the reactor top put in the yellorium. Hay look a zombie. Dies.
In 1.10 we need armor. And jetpacks will also be very important.
When I was playing Inf Skyblock I spent so much time switching back and forth between the rad suit, jetpack, and dieing that I was sick of it.
Besides there are already 1000+ armors. I want to see a new idea.

i would lean on the side of an enchantment.

I'd say more enchantment then actual item.
Reason being is that (slowly) mods are either being caught up to 1.9.4/1.10.2 they themselves are in effect taking over from other mods that never went further then 1.7.10.

@NJM1564 have you actually worn a radation suit before?  I have.  Movement is very difficult.  "Flying" is the same to expect pigs to fly backwards.
All comes down how realistic this is to be.

Have you ever worn a jet pack before? Kappa
Or directly carried radioactive material? Moving radioactive material around bin any significant quantity should be never done by hand. Automated carts and heavy shedding should be the only except able method. So yah if you wanted to go mineing in only a paper thin armor that when breached will lead to certion death then yah lets go with realism.
Now if you like adding some balance you could add a slow effect to the player when he has the radiation protect enchant and is exposed to radiation. IE carrying refined yellorium. Being a bit slow instead of poisond seems like a good trade off.
Unrefined yellorium IE yellorium ore would only really require any random armor to stave off the minor radiation. So iron armor would be enough for protection.
And a low chance of poison and the chance increasing over time if not wherein anything at all would all be a nice and interesting mechanic set of mechanics.
Nothing to frustrating just a step in the posses of making a mid to end tear power source.

If i can add some insight from the perspective of a player/modpack author of 1.9+ clears throat
Radiation was always just a hassle we had to deal with on a side-note not as a serious issue since at the point where we were dealing with uranium and such we had either ridiculous regen values applied to us by botania/beacons/rftools/etc... that we could just shrug it off ezpz  or we had such armor/extra hearts that the damage values from the poison were more or less nothing and the only problem was the player getting hurt sound that was merely an annoyance so if you accept suggestions heres mine:
-Slowness is a good trade off as NJM mentioned
-Armor values should be looked at instead of armor materials if youre going for that because of the custom armors of 1.9+,  currently we encountered about 60+ armor types from various mods and im consciously avoiding adding more but some still slip in every now and then.
-Radiation resistance could be applied by two means if not by armor and those would be potion or enchantment. You could even add levels to these so for example Rad Res 1 would protect you from radiating ores but not ingots...2 from ingots and 3 from refined cunterparts like liquids or high-end stuff like blutonium and ludicrite or you could just add level 4 and move some stuff up there idk.
Reasons to pick this method:
With the current setup of my modpack for example if i were to equip myself with your armor which lets say has 7 armor 2 armor toughness on the chestpiece - about eq to dia - i would be killed by any zombie that wonders into my reactor area and hits me about 2-3 times...yes theyre buffed af.
Also if you had a potion effect registered to protect from radiation that could be used in custom maps as a pre-req quest reward so a player could advance tru an area for example: "You've been trapped in this underground nuclear facility, coolant-leak detected in zones H,J and R, find the antidote(your potion)/the special gear(enchanted armor thats capable of protecting you from both the enemies and the radiation) to survive out there while you battle the infected personnel(zombies most likely)".
What Im trying to say here is if you separate armor and protection from radiation it opens up possibilities for authors like me and would be greatly appreciated!
Anyyywaaay, thanks for continuing this awesome mod! Hope to see it out soon :)
Thanks for reading my "little" suggestiony thing :D heres an ascii potato-head
.-"'"-.
|       |
(-._____.-')         ..  -.____.-'  ..
.', :./'.== ==.\.: ,.
: (  :   ___ ___   :  ) ;
'..:    |0| |0|    :..'
/     -'_-'
.|       / \       |.
.'.-|      (   )      |-..    //'  |  .-""-'""-.  |  \\    ||    |  ~":-...-:"~ |    ||   ||     \.   ---'    ./     ||
||       '-._     .-'       ||
/  \       / ~:~ _       /
||||)   .-'    / \    -.   (/|||| \|||    (..')-(.___.')    |||/  '"' jgs -----'   `-----'     '"'

Guys, it seems that some of you don't know it yet, but I quit the work on this mod as there is already another port in work which is much closer to releasing then mine was...
That is the theard to it: http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/mods-discussion/2693080-big-reactors-port-for-1-9-0-anyone-interested
Please read the suggestions there and add your own ones if there isn't already something like it :)
Thank you


Error "java.lang.AbstractMethodError: Receiver class .. does not define or inherit an implementation of the resolved method 'abstract void upickle$implicits$Readers$setter$JavaBooleanReader_$eq(upickle.core.Types$Reader)"

I'm using your (excellent, btw) library from inside the Couchbase Scala SDK library for JSON duties.  And I'm hitting an obscure runtime error that's not meaning much to me:
java.lang.AbstractMethodError: Receiver class com.couchbase.client.scala.util.CouchbasePickler$ does not define or inherit an implementation of the resolved method 'abstract void upickle$implicits$Readers$_setter_$JavaBooleanReader_$eq(upickle.core.Types$Reader)' of interface upickle.implicits.Readers.
	at upickle.implicits.Readers.$init$(Readers.scala:370)
	at com.couchbase.client.scala.util.CouchbasePickler$.<clinit>(CouchbasePickler.scala:22)
	at com.couchbase.client.scala.manager.bucket.CreateBucketSettings$.<clinit>(BucketSettings.scala:280)
	at com.couchbase.situational.SituationalRunner$.createBucket(SituationalRunner.scala:341)

The line that's throwing the runtime error:
val settings = CreateBucketSettings(rp.bucketName, 1000)

Some of the other relevant code:
// Contents omitted as probably not relevant?
case class CreateBucketSettings(...)

object CreateBucketSettings {
  implicit val rw: CouchbasePickler.ReadWriter[CreateBucketSettings] = CouchbasePickler.macroRW
  implicit val rwd: CouchbasePickler.ReadWriter[Durability] = BucketSettings.rw
}

object CouchbasePickler extends upickle.AttributeTagged {
  // upickle writes Options as [] and ["value"] by default
  override implicit def OptionWriter[T: Writer]: Writer[Option[T]] =
    implicitly[Writer[T]].comap[Option[T]] {
      case None    => null.asInstanceOf[T]
      case Some(x) => x
    }

  override implicit def OptionReader[T: Reader]: Reader[Option[T]] =
    implicitly[Reader[T]].mapNulls {
      case null => None
      case x    => Some(x)
    }
}

The odd thing is, I have other Scala Junit tests that create and use CreateBucketSettings without issues.  I'm only hitting problems now I'm trying to use it from another project.  This project mixes Scala and Java, which might be relevant going from the JavaBooleanReader in the error.
I'm not sure what the error is trying to tell me.  Are there any clues you could provide to point me in the right direction?
Uisng upickle 1.6.0.  Which I appreciate is a year old now and I should upgrade - I'll give that a try, in fact.

Seems like a version conflict between your libraries. Going to close this for now since it's unlikely to be a code issue, but feel free to post your dependency tree (including evictions) and maybe I can see where the conflict is


Make the .phpbrewrc feature work with ZSH

Hi @marcioAlmada ,
I don't have experience with phpbrewrc, maybe you can try this PR a little bit?

hmm... I'm not using ZSH anymore, anyone? xD

ok syntax verified, this PR fixes the incorrect boolean syntax. I think merging it is fine.


CollectionView cell flicking

when i try to add new data in existing array and than i call performBatchUpdates, it loads new data but the existing data flicking..
i try to invalidate layout with context but nothing happened.
CGFloat bottomOffset = self.collectionView.contentSize.height - self.collectionView.contentOffset.y;
NSArray *newData = media;
[self.searchCollectionView performBatchUpdates:^{
int resultsSize = (int)[popularPostArr count]; //data is the previous array of data
[popularPostArr addObjectsFromArray:newData];
NSMutableArray *arrayWithIndexPaths = [NSMutableArray array];
        for (int i = resultsSize; i < resultsSize + newData.count; i++) {
            [arrayWithIndexPaths addObject:[NSIndexPath indexPathForRow:i
                                                              inSection:0]];
        }
        [self.searchCollectionView insertItemsAtIndexPaths:arrayWithIndexPaths];
    } completion::^(BOOL finished) {
                    if (isChangeContentSize) {
                        self.collectionView.contentOffset = CGPointMake(0, self.collectionView.contentSize.height - bottomOffset);
                    }
                    else {
                        isChangeContentSize = true;
                    }];

Thanks in advance..

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Better Documentation

Self-explanatory title

:trollface:

Would be cool if you help on docs. I don't have time and it would be great for help but yeah i will slowly improve wiki.


Remove mock.shop from .env

❗ This PR is not required for 2024.4, feel free to postpone the review.

Removes mock.shop from the templates .env
Use mock.shop as a default value when nothing is passed to createStorefrontClient

It should have the same effect, but now when you h2 link your store, the domain coming from Admin will be used. Previously it was overwritten by .env.

nice


When viewing live data, data file gets blocked.

When setting the refresh rate of the live update on a currently recording data file the following error appeared.

This should have gotten fixed with PR #350


Added StringArray Function

This PR adds a StringArray() []string function to each value.  I will make a PR to viper after this is merged, so that the StringArray variables use this new function.  This is needed since binding to pflag prevents the use of values that can't be packed/unpacked using CSV.  With this function, viper can pull array values directly from pflag maintaining the original values.

The specific CLI command using cobra/viper/pflag` that I needed to run was:
go run main.go serve -d '{name:dc_amenities, uri: `"data/" + @z + "-" + @x + "-" + @y + "/dc_amenities.geojsonl"`}'

It works with the fix.  I first tried a quick fix in viper using reflection to handle this case; however, it was not feasible without refractoring.  You can't type cast to access fields from un-exported structs.  All the values are un-exported types.  I'm happy to consider other potential ways.

Are there any outstanding questions that I can help answer?  Thanks for consideration.

@pjdufour is this change still of interest to you?  I am bumping up against similar limitations, and I'm considering creating something like a SliceValue and ArrayValue interface to export list-specific functions for Viper to consume.  Interested in collaborating?


centos 7.8 fail to install requirements

following doc: https://github.com/phpbrew/phpbrew/wiki/Requirement#centos-requirement
# cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)

# rpm -Uvh https://mirror.webtatic.com/yum/el7/webtatic-release.rpm
Retrieving https://mirror.webtatic.com/yum/el7/webtatic-release.rpm
warning: /var/tmp/rpm-tmp.8GXhJ2: Header V4 RSA/SHA1 Signature, key ID 62e74ca5: NOKEY
error: Failed dependencies:
        epel-release >= 7 is needed by webtatic-release-7-3.noarch

after yum install epel-release, it fixed
# wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
--2020-10-03 19:54:25--  http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
Resolving pkgs.repoforge.org (pkgs.repoforge.org)... <IP_ADDRESS>
Connecting to pkgs.repoforge.org (pkgs.repoforge.org)|<IP_ADDRESS>|:80...

pkgs.repoforge.org cannot be opened by my browser neither

It's a sad news that webtatic is not updated actually. Personally I suggest to change to remi repo instead. Here is a quick guide: https://blog.remirepo.net/post/2018/12/10/Install-PHP-7.3-on-CentOS-RHEL-or-Fedora

It's a sad news that webtatic is not updated actually. Personally I suggest to change to remi repo instead. Here is a quick guide: https://blog.remirepo.net/post/2018/12/10/Install-PHP-7.3-on-CentOS-RHEL-or-Fedora

I've updated for the CentOS 7 and CentOS 8 streams. And I also test them in these Linux distributions.
Please feel free to refer the CentOS/Fedora requirements to setup and install required packages.
Thanks.


Licence mention shaders that are not part of this project

I think the licence was copied from Inferno, since this project doesn't use shaders I found it wired to include the licences for shaders that are not part of this project
Just wanted to bring it to your attention, feel free to close if

Oops – thank you!


Stakenet 8 staging

Preparing for release of stakenet v8.

Codecov Report
Attention: 323 lines in your changes are missing coverage. Please review.

Comparison is base (67a7050) 37.33% compared to head (fb9fb1a) 36.22%.

Files
Patch %
Lines

src/bin/nomic.rs
0.00%
187 Missing :warning:

src/app/migrations.rs
0.00%
53 Missing :warning:

src/app.rs
0.00%
30 Missing :warning:

src/bitcoin/signer.rs
22.22%
28 Missing :warning:

src/bitcoin/mod.rs
27.27%
16 Missing :warning:

src/bitcoin/relayer.rs
0.00%
5 Missing :warning:

src/bitcoin/checkpoint.rs
90.90%
1 Missing :warning:

src/bitcoin/threshold_sig.rs
66.66%
1 Missing :warning:

src/cosmos.rs
0.00%
1 Missing :warning:

src/utils.rs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #281      +/-   ##
===========================================
- Coverage    37.33%   36.22%   -1.11%
===========================================
  Files           26       26
  Lines         9372     9633     +261
===========================================
- Hits          3499     3490       -9
- Misses        5873     6143     +270

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


iOS 10-10.2 jailbreaks

There are jailbreaks available for iOS 10.0-10.2, and it disappoints me to see that they are not listed on this site.

Sorry, 10.0.1-10.2

Hi,
I’m aware of these jailbreaks.
See rule 1 in contributing guidelines and various other issues/pull requests.


[SPARK-39616][BUILD][ML] Upgrade Breeze to 2.0

What changes were proposed in this pull request?
1, Upgrade Breeze to 2.0
2, import a implict breeze.stats.distributions.Rand.FixedSeed.randBasis in ML for this upgrade: there are two options: FixedSeed and VariableSeed, I took a quick look and choose FixedSeed for reproductivity
Why are the changes needed?
since 1.3, breeze has replaced com.github.fommil.netlib with dev.ludovic.netlib
after upgrade to 2.0:
1, breeze should be faster because of this replacement;
2, completely resolve the license issue related to com.github.fommil.netlib:all
Does this PR introduce any user-facing change?
No
How was this patch tested?
existing UT

Looks good if it works; I kinda thought it would break more

there are some failures in pyspark, I think I need some more time.

Looks OK pending tests

@dongjoon-hyun @HyukjinKwon -Xss4M also works, the javaoptions in PySpark and SparkR are different, but here I only set stack size.

Thank you, @zhengruifeng , @srowen , @HyukjinKwon . Merged to master for Apache Spark 3.4.

@zhengruifeng seems like there's one test flaky presumably after this:

File "/__w/spark/spark/python/pyspark/mllib/linalg/distributed.py", line 859, in __main__.IndexedRowMatrix.computeSVD
Failed example:
    svd_model.V # doctest: +ELLIPSIS
Expected:
    DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, 0.0], 0)
Got:
    DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, -0.0], 0)
**********************************************************************
File "/__w/spark/spark/python/pyspark/mllib/linalg/distributed.py", line 426, in __main__.RowMatrix.computeSVD
Failed example:
    svd_model.V # doctest: +ELLIPSIS
Expected:
    DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, 0.0], 0)
Got:
    DenseMatrix(3, 2, [-0.4082, -0.8165, -0.4082, 0.8944, -0.4472, -0.0], 0)
**********************************************************************
   1 of   6 in __main__.IndexedRowMatrix.computeSVD
   1 of   6 in __main__.RowMatrix.computeSVD
***Test Failed*** 2 failures.
Had test failures in pyspark.mllib.linalg.distributed with python3.9; see logs.

Mind taking a look please?

Thank you for reporting that, @HyukjinKwon .

@HyukjinKwon @dongjoon-hyun let me take a look, thanks

shall we also delete the license file LICENSE-netlib?
@srowen @dongjoon-hyun @HyukjinKwon

I believe you could. Check the license of the ludovic package to make sure we haven't missed something there, and that the fommil package isn't in the build now


Make sure the spell UI works properly through transitions in and out …

…of battle.

Works better but there are missing spell level labels - missing I, III and IV here - this is out of battle

and here with different spell selection missing I, IV and VI - this is the same in and out of battle

Same issue without mod (different spells again) but VI is missing

Tried on DLC.  The spell level labels seemed to be ok out of battle, but got exception in battle.

Now works fine. However there is a problem with missing spell level labels - I, III and IV here - this is out of battle

and here with different spell selection missing I, IV and VI. Exactly the same in and out of battle.

Same issue without mod (different spells again) but VI is missing

I'm not sure why the spell level numbers sometimes don't show up. As you noted it happens without the mod (though maybe a little less). I don't think anything in this change effects those numbers.

Tried on DLC. The spell level labels seemed to be ok out of battle, but got exception in battle.

After this is in dev I can investigate what might be going on in beta. I haven't downloaded the latest patch yet, so I don't know what they've changed there.


Add parameter to replace remaining hard-coded 'd'

Description
Missed adding the parameter in 2 other places in the previous PR. Adding it here. @mohit-sheth can you please review.

Can one of the admins verify this patch?


Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.

Trying to add the second device to TUYA local, but I have issues getting the message "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect."
Describe the bug
I added already one device. In the same way, trying to add 2 others. It is WI-FI thermometer.
The local key doesn't have any specific symbols (5da979fbcb2f621e)
Logs from TUYA:
2023-09-28 15:25:13.543 DEBUG (MainThread) [custom_components.tuya_local.helpers.device_config] StarLight heatpump: Mapped dps 105 value from off to Off
2023-09-28 15:25:13.544 DEBUG (MainThread) [custom_components.tuya_local.helpers.device_config] option values: ['Off', 'Standard', 'Elderly', 'Child']
2023-09-28 15:25:51.231 ERROR (MainThread) [custom_components.tuya_local.device] <class 'Exception'>: Unable to find device on network (specify IP address) while initialising device bff223b9717b2e0297aoea
2023-09-28 15:25:51.236 WARNING (MainThread) [custom_components.tuya_local.config_flow] Connection test failed with <class 'Exception'> Unable to find device on network (specify IP address)
2023-09-28 15:25:51.391 DEBUG (MainThread) [custom_components.tuya_local.device] Kondicionierius received {"1": false, "2": 260, "3": 27, "4": "hot", "5": "low", "18": 0, "20": 0, "101": 0, "105": "off", "110": 4330047, "113": "0", "114": "0", "116": 8, "119": "0", "120": "off", "123": "0008", "125": "great", "126": "0", "127": "0", "128": "0", "129": "1", "130": 26, "131": false, "132": false, "133": "0", "134": "{"t":7,"s":false,"clr":true}", "135": 1, "full_poll": true}
2023-09-28 15:25:51.392 DEBUG (MainThread) [custom_components.tuya_local.helpers.device_config] No mapping for dpid 18 (sensor), unable to determine valid values

Restarted HASS and in the logs I got this message:
Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for tuya_local doing blocking calls at custom_components/tuya_local/device.py, line 76: self._api = tinytuya.Device(dev_id, address, local_key)

The solution is in the log message


fix: add files and folders

Need your input about this one guys:
We can now add files and folders through the + Add to IPFS button, I did that by saying if it's files or folders depending on what option we clicked on the dropdown. So far so good.
The problem is when we drag and drop. It seems there is not a standard way of checking if we're dropping a file or a folder in react-dnd.
I did this (it's not pretty, I know):
https://github.com/ipfs-shipyard/ipfs-webui/blob/11710148d1aba2f91106ca1d7722e896bcbe30ad/src/files/files-list/FilesList.js#L343
but after searching a bit and testing with some files I found that some file types will fail this check. This issue talks about this.
So, what options do we have?

Disable drag and drop for folders
Keep the code this way, knowing that some files may fail if dragging and dropping
?

We'll need to refactor + Add to IPFS dropdown and the drag and drop in the Files List, that will be a good time to think about how to circumvent this.
Thoughts? (we need to ship the fix for adding files ASAP)
Fixes https://github.com/ipfs-shipyard/ipfs-webui/issues/928.

Any solution to this issue?


Fix missing TypeError on invalid arg count to range

Cython generated the same optimized C code for
for i in range(1,2,3,4) and for i in range(1,2,3).
This PR deactivates this optimization when to many arguments are
provided to match the behavior of Python.

This is a re-implementation of the fix in #4080 with a proper test (I mistakenly deleted the original branch)

It's relatively easy to check out an old PR (either yours or someone elses): https://stackoverflow.com/a/30584951 - (just posting this for future information, I don't think it matters here)

It's relatively easy to check out an old PR (either yours or someone elses): https://stackoverflow.com/a/30584951 - (just posting this for future information, I don't think it matters here)

Good to know :+1:

Thanks. I applied a slightly different change in https://github.com/cython/cython/commit/43b245137e141f9c35dc3d59a41aad426247d508. Hope that's ok for you.

Thanks. I applied a slightly different change in 43b2451. Hope that's ok for you.

Sure, that's fine with me.


Amumu?

The release was called Amumu? Was it on purpose?

Amumu is a character in my favorite videogame. I'm planning name each release
with one of the LoL characteres.

I feel to grow up :-)


Update BuildHandlerUtilsTest.java

Please Make sure these boxes are checked before submitting your pull request - Thanks ahead!

[ ] Proper pull request title - concise and clear for others.
[ ] Proper pull request short description - clear and concise (as it should appear in the Jira ticket) for other developers and users.
[ ] Proper Jira ticket - Number, Link in pull request description.
[ ] The PR can is merged on your machine without any conflicts.
[ ] The PR can is built on your machine without any (new) warnings.
[ ] The PR passed sanity tests by you / QA / DevTest / Good Samaritain.
[ ] Add unit tests with new features.
[ ] If you added any dependency to the POM - Please update @YafimK

approved for test build

:white_check_mark: Build hpe-application-automation-tools-plugin latest.53-phbxdptn completed (commit https://github.com/hpsa/hp-application-automation-tools-plugin/commit/7aeeaf07d0 by @YafimK)

:x: Build hpe-application-automation-tools-plugin latest.54-jgotsfkk failed (commit https://github.com/hpsa/hp-application-automation-tools-plugin/commit/7aeeaf07d0 by @YafimK)


Missing policy creation for Facebook auth

This help doc on Facebook auth should include the steps that are required to configure a policy; otherwise, auth isn't configured properly and it doesn't work.  Also, when following the current set of instructions, it's not necessarily apparent that these steps are missing.  I also noticed that another dev encountered this same issue and added a comment to this page.  This same issue exists across all of the guides for configuring social auth.
If this change is approved, we should look at making this across all of the social auth guides.

@nicolehaugen79,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@nicolehaugen79 : Thanks for your contribution to the Azure documentation! The author, @parakhj, has been notified to review your proposed change.

@nicolehaugen79 : Thanks for your contribution to the Azure documentation! The author, @parakhj, has been notified to review your proposed change.

@nicolehaugen79 : Thanks for your contribution to the Azure documentation! The author, @parakhj, has been notified to review your proposed change.

@nicolehaugen79 : Thanks for your contribution to the Azure documentation! The author, @parakhj, has been notified to review your proposed change.

@PatAltimore

#hold-off we like the change, but need to implement it for all identity provider articles

Are you asking me to make the change for all providers or do you plan to do that?

@nicolehaugen79 Hi Nicole, We're working on some updates to the B2C content.  @parakhj  is asking that I do this as part of  that effort.  We'll incorporate your change as part of the effort.  Would it be okay to close the pull request?

Sounds great - thanks!

Hi @nicolehaugen79, @PatAltimore, To resolve this pull request, please add an appropriate comment so that automation can take appropriate action. In this case, please-close. Thanks

#please-close  @nicolehaugen79 I'll close this and add the changes to other planned revisions.  Thanks!


Reproducing NLL on QM9

Hi,
Great paper, and really appreciate how well-documented the code is! I'm trying to run the discrete model on QM9 (just python main.py), but my validation NLL seems to get stuck around 68-69 during training, and my test NLL is similarly high. Is this something you observe? Is there a different config / parameter values I should run in order to obtain ~23?
Thank you!

Hello Peter,
there was some bugs in the likelihood computation at the time of the submission, please refer to the latest version or Arxiv.
We have a likelihood of 69.6 on QM9, so your results look correct.
Clément

Le 14 févr. 2023 à 23:13, Peter Mikhael @.***> a écrit :

Hi,
Great paper, and really appreciate how well-documented the code is! I'm trying to run the discrete model on QM9 (just python main.py), but my validation NLL seems to get stuck around 68-69 during training, and my test NLL is similarly high. Is this something you observe? Is there a different config / parameter values I should run in order to obtain ~23?
Thank you!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Ah I see, thank you!!
 No worries if not!

I've not compute it, sorry. Could you tell me exactly how you define it? I've seen it used for normalizing flows, but never for diffusion models.

In this case, since the objective is predicting the correct node and edge class for each molecule, I was considering to check how often all nodes and edges are correctly predicted, averaged across molecules rather than total number of nodes/edges (and for any time step).

In would be easy to compute indeed, but I don’t have it, sorry.
Clément

On 15 Feb 2023, at 17:56, Peter Mikhael @.***> wrote:
In this case, since the objective is predicting the correct node and edge class for each molecule, I was considering to check how often all nodes and edges are correctly predicted, averaged across molecules rather than total number of nodes/edges (and for any time step).
—
Reply to this email directly, view it on GitHub https://github.com/cvignac/DiGress/issues/6#issuecomment-1431682911, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEJOOTS33NKT6G5KTCD3FPLWXUDFNANCNFSM6AAAAAAU4DN7DI.
You are receiving this because you commented.


Mavlogd assumes the vehicle is a Copter

Mavlogd assumes the vehicle is a Copter. This leads to erroneous flight-mode reporting when analyzing logs from other vehicle types.
Ideally, Mavlogd would identify the vehicle type to associate the mode enums appropriately.

Ah very good point.  Would you have a plane or other vehicle log you could attach here for me to work with?


Angular position model

Summary

This PR addresses Jira ticket CISLUNAR-###  (TODO: lookup ticket number)
This PR implements the dynamics of our angular position. Angular velocity dynamics will be the next PR.
This PR changes the derived state model implementation to use State objects instead of dicts and overhauls the organization of the repo to enable this.
Testing

Ran main, ran profiler. Quaternion and related derived states got updated.
Notes

doesn't really work yet - is super slow and I'm not sure if it's accurate either.
Comments

[x] Add an x between the brackets if you commented your code well!

Plot of the attitude quaternion - the quaternion propagation seems to work based off eyeballing. Still working on confirming wthe vector and azimuth/elevation angles


Make the kola test workflow reusable

Adds a reusable workflow that can run tests
Adapts the ci.yaml to use reusable workflow
Creates a new workflow that helps trigger tests using an arbitrary workflow run.

In this PR, the artifact download action is from my own fork, because it includes a fix that streams the artifact directly to disk. The upstream action downloads to memory and also un-archives the artifact in memory, which leads to huge memory usage in our case. I created a PR for this with the upstream project here:
https://github.com/dawidd6/action-download-artifact/pull/175
Signed-off-by: Gabriel Adrian Samfira<EMAIL_ADDRESS>

Looks good, thanks! For cherry-picking the changes in ci-automation/* should be done in a separate commit. I'll look into the kola VM profile RAM situation - why was 8 GB swap chosen?

A little over what 3 VMs of 2.5 GB memory would consume. It gives a chance for tests to finish before an out of memory condition is reached. Hitting swap will slow down newly spawned tests to allow already spawned tests to finish and free up memory.
Without swap, some VMs will be killed when memory is exhausted.

A fix for the failed test is prepared in https://github.com/flatcar-linux/bootengine/pull/47
I just realize that we even should backport the .github changes (and before that the previous PR), otherwise the a PR against an older scripts branch like flatcar-3227 would run without the changes done here, or?

I just realize that we even should backport the .github changes (and before that the previous PR), otherwise the a PR against an older scripts branch like flatcar-3227 would run without the changes done here, or?

Yes. The workflows would need to be backported to branches where you push PRs to as well as far as I remember.

He, I was a bit late with picking #356 and it already started the workflow builds for all branches :D

no worries. They can easily be canceled in the "Actions" tab of the repository. :D


Inability to Hide Three Dots Menu in Announcements Page When No Edit or Delete Permissions

📜 Description
The AnnouncementsPage component in the backstage-plugin-announcements plugin always displays the three dots (menu) option. This behavior is implemented in AnnouncementsPage.tsx, around line 161. There is no current way to hide this menu based on user permissions.
Problem:
The menu is visible regardless of user permissions. This can be problematic in cases where the user does not have permissions to edit or delete announcements, as the menu still appears.
References:
Link to AnnouncementsPage.tsx file
👍 Expected behavior
The three dots menu should be hidden if the user does not have permissions to edit or delete announcements. This would make the component more intuitive and cleaner in scenarios where the menu options are not relevant to the user.
👎 Actual Behavior with Screenshots

👟 Reproduction steps
Steps to Reproduce:

Navigate to the AnnouncementsPage.tsx file in the source code.
Locate the code around line 161 where the menu is implemented.
Observe that the menu is always visible and cannot be hidden through configuration or styling.

📃 Provide the context for the Bug.
Suggested Solution:
To address the issue of hiding the three dots menu, consider implementing a conditional rendering approach.
For example:
{canUpdate && canDelete && <Menu ... />}
&
{canUpdate && canDelete && <IconButton ... />}
This code snippet ensures that the menu is only displayed when both canUpdate and canDelete conditions are true. Alternatively, if the menu should be entirely hidden, implementing a configuration option or prop that allows for toggling its visibility based on user needs would be ideal.
Additional Context: Attempts to customize or hide the menu through existing configuration options have not been successful. A more flexible solution is required to adapt the component to different user scenarios.
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
Yes I am will to submit a PR!

thank you for your contribution @belurepavan71 !