mesa: 20.3.4 -> 20.3.5

Motivation for this change
Yay :) (it's been almost two months since 20.3.4 which was a bit concerning since stable releases are normally tagged every two weeks).
The release notes aren't up yet: https://docs.mesa3d.org/relnotes/20.3.5.html
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] 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 nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg eval

/rebase staging

Merged but immediately bumped to 21.0.1?  😄

Yeah, IIRC I didn't check my update feeds between opening and merging this PR so I wasn't aware that 21.0.1 was already released in the meantime but I'd've likely merged this PR regardless (or should I try to avoid that in the future? AFAIK it has both advantages and drawbacks). Anyway, I'm glad that 21.0.1 is finally out :)

Not a problem;  I just found found it funny to see those two merges so close together.


Setting "repositories.default" breaks the IntelliJ Idea integration

Versions
Scala CLI version: 1.3.2
Scala version (default): 3.4.2
IntelliJ IDEA 2024.1.3 (Ultimate Edition)
Build #IU-241.17890.1, built on June 4, 2024
Description
We used company artifactory to resolve/cache artefacts. Therefor I have to set up environment varianble COURSIER_REPOSITORIES to handle it right. Because we are using self signed certificate on server there is problem with resolving artefacts directly using coursier (upgrades scala-cli, scala or java).
I realized that there is config repositories.default that seems to me to fulfil the same thing but only for scala-cli (not system wide). So I started using it. It works well but breaks the integration with IDE.
After starting using repositories.default instead of COURSIER_REPOSITORIES I can't build in IDEA via BSP. In BSP window there has been no tree under the root of project. The problem is with our artifactory server with self signed certificate because using maven central causes everything works fine.
To Reproduce

scala-cli config repositories.default ivy2local https://our-server/with-self-signed-certificate/repo --power
create directory test
in it create file test.sc with content

//> using scala 3.3

println(sum(2, 3))

def sum(a: Int, b: Int) = a + b

in the directory test run scala-cli setup-ide test.sc
open IDEA and File / New / Project from Existing Sources - choose folder test and in following dialog choose model BSP

In BSP window there is no tree and println is marked as uknown symbol.
Expected behaviour
There should be dependencies in BSP window and println shoul be known.

And now it is not working with artifact proxy with self-signed certificate via https at all. Neither COURSIER_REPOSITORIES environment variable nor repositories.default scala-cli config. I don't know what to do :-(

I don't know what to do :-(

Hey, I'll try to tackle this soon (likely won't be this week, however).
I'd suspect something is wrong with the config sub-command's repositories.* settings, but COURSIER_REPOSITORIES is known and proven to be reliable... 😕
Can't tell you much until I take a closer look.

Hi @Gedochao,
I have been a little more investigating and it looks that problem is with https protocol with artifact proxy (not with its setting via COURSIER_REPOSITORIES or repositories.default). I have to restart cmputer between tests because I can't reset the envirement well (killing all java processes have not been enough).
scala-cli works great with http and https too (for https I have to use -Djavax.net.ssl.trustStore). But the IDEA is not able to resolve using https at all (not possible to validate server certificate - I have imported it into IDEA's store - it looks like idea is using coursier under the hood too but I can't specify  -Djavax.net.ssl.trustStore). To resolve dependendencies is job of IDEA or bloop?

From my point of view it directs to coursier that is run under the hood to resolve artifacts. But when run via scala-cli I can add -Djavax.net.ssl.trustStore but when run in IDEA it is not possible and therfore not working.

To resolve dependencies is job of IDEA or bloop?

Definitely Scala CLI/Bloop, depending on which dependencies. Both use Coursier under the hood.
However, I can't be sure what IDEA does in the background.

From my point of view it directs to coursier that is run under the hood to resolve artifacts. But when run via scala-cli I can add -Djavax.net.ssl.trustStore but when run in IDEA it is not possible and therfore not working.

@jiramares Can you raise a corresponding ticket on the JetBrains issue tracker?  (https://youtrack.jetbrains.com/issues)
So that we can establish this works as expected on the IDEA side of things.

I have already raised one an the result is - it is not IDEA problem (https://youtrack.jetbrains.com/issue/SCL-22728/scala-cli-project-not-working)](https://youtrack.jetbrains.com/issue/SCL-22728/scala-cli-project-not-working)

But .. who starts the bloop server, from mine point of view it is started by scala-cli and IDEA in calling it via BSP? Therefore if the bloop is responsible for resolving why it is run okay through scala-cli and not running via IDEA? I am confused....

One extra question - have you tried running it in Metals?
I just want to confirm this isn't IDEA specific, since from what I understand it works when run outside of IDEA.
I'd theorise maybe some coursier instance ran inside of IntelliJ is using a JVM without the cert flag.
I hope we won't end up bouncing this back and forth...

No, I haven't ... be honest don't know how to make it. Just install Metals into VSC and run scala-cli setup-id . and open it in VSC? Or it is necessary to do something more?

Exactly this.

start the Metals server and check if everything works.

I try to make it but I am sorry not to test it now ... hope to make it this week. j

I have installed metals into VSC and have same result as in IDEA:
024.06.28 15:33:28 INFO  BSP server: [error]   download error: Caught javax.net.ssl.SSLHandshakeException (PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target) while downloading https://ids/artifactory/repo/org/typelevel/cats-core_3/2.12.0/cats-core_3-2.12.0.pom

@jiramares do you use cats within your project?

My guess is that we are not adding the certs when downloading sources somehow, but it seems unexpected :thinking:

@jiramares are you still encountering this issue with Scala CLI v1.5.1?
I suspect we may have fixed it in #3169.

It is still not working. If I repeat the steps in issue description I am getting following stacktrace:
java.lang.Exception: Error getting Bloop class path
  bloop.rifle.BloopRifle$.startServer(BloopRifle.scala:51)
  bloop.rifle.BloopServer$.startBloop$1(BloopServer.scala:77)
  bloop.rifle.BloopServer$.ensureBloopRunning(BloopServer.scala:108)
  bloop.rifle.BloopServer$.bsp(BloopServer.scala:156)
  bloop.rifle.BloopServer$.buildServer(BloopServer.scala:186)
  scala.build.bsp.BspImpl.$anonfun$10(BspImpl.scala:424)
  scala.build.compiler.BloopCompiler.<init>(BloopCompiler.scala:15)
  scala.build.bsp.BspImpl.newBloopSession(BspImpl.scala:429)
  scala.build.bsp.BspImpl.run(BspImpl.scala:465)
  scala.cli.commands.bsp.Bsp$.runCommand$$anonfun$1(Bsp.scala:185)
  scala.runtime.function.JProcedure1.apply(JProcedure1.java:15)
  scala.runtime.function.JProcedure1.apply(JProcedure1.java:10)
  scala.build.bsp.BspThreads$.withThreads(BspThreads.scala:23)
  scala.cli.commands.bsp.Bsp$.runCommand(Bsp.scala:174)
  scala.cli.commands.bsp.Bsp$.runCommand(Bsp.scala:76)
  scala.cli.commands.ScalaCommand.run(ScalaCommand.scala:390)
  scala.cli.commands.ScalaCommand.run(ScalaCommand.scala:371)
  caseapp.core.app.CaseApp.main(CaseApp.scala:166)
  scala.cli.commands.ScalaCommand.main(ScalaCommand.scala:356)
  caseapp.core.app.CommandsEntryPoint.main(CommandsEntryPoint.scala:370)
  scala.cli.ScalaCliCommands.main(ScalaCliCommands.scala:125)
  scala.cli.ScalaCli$.main0(ScalaCli.scala:320)
  scala.cli.ScalaCli$.main(ScalaCli.scala:124)
  scala.cli.ScalaCli.main(ScalaCli.scala)
scala.build.errors.FetchingDependenciesError: Error downloading ch.epfl.scala:bloop-frontend_2.12:2.0.2
  not found: /home/jmares/.ivy2/local/ch.epfl.scala/bloop-frontend_2.12/2.0.2/ivys/ivy.xml
  download error: Caught javax.net.ssl.SSLHandshakeException (PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target) while downloading https://our-server/with-self-signed-certificate/repo/ch/epfl/scala/bloop-frontend_2.12/2.0.2/bloop-frontend_2.12-2.0.2.pom
  scala.build.Artifacts$.toFetchingDependenciesError(Artifacts.scala:723)
  scala.build.Artifacts$.fetchCsDependencies$$anonfun$1$$anonfun$2(Artifacts.scala:697)
  scala.util.Either$LeftProjection.map(Either.scala:622)
  scala.build.Artifacts$.fetchCsDependencies$$anonfun$1(Artifacts.scala:691)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Artifacts$.fetchCsDependencies(Artifacts.scala:671)
  scala.build.Artifacts$.fetchAnyDependenciesWithResult$$anonfun$1(Artifacts.scala:590)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Artifacts$.fetchAnyDependenciesWithResult(Artifacts.scala:569)
  scala.build.Artifacts$.fetchAnyDependencies$$anonfun$1(Artifacts.scala:555)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Artifacts$.fetchAnyDependencies(Artifacts.scala:546)
  scala.build.Artifacts$.artifacts$$anonfun$1(Artifacts.scala:486)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Artifacts$.artifacts(Artifacts.scala:484)
  scala.build.Bloop$.bloopClassPath$$anonfun$1(Bloop.scala:74)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Bloop$.bloopClassPath(Bloop.scala:72)
  scala.build.Bloop$.bloopClassPath$$anonfun$2(Bloop.scala:105)
  scala.build.EitherCps$Helper.apply(EitherCps.scala:19)
  scala.build.Bloop$.bloopClassPath(Bloop.scala:95)
  scala.cli.commands.shared.SharedCompilationServerOptions.$anonfun$13(SharedCompilationServerOptions.scala:265)
  bloop.rifle.BloopRifle$.startServer(BloopRifle.scala:50)
  bloop.rifle.BloopServer$.startBloop$1(BloopServer.scala:77)
  bloop.rifle.BloopServer$.ensureBloopRunning(BloopServer.scala:108)
  bloop.rifle.BloopServer$.bsp(BloopServer.scala:156)
  bloop.rifle.BloopServer$.buildServer(BloopServer.scala:186)
  scala.build.bsp.BspImpl.$anonfun$10(BspImpl.scala:424)
  scala.build.compiler.BloopCompiler.<init>(BloopCompiler.scala:15)
  scala.build.bsp.BspImpl.newBloopSession(BspImpl.scala:429)
  scala.build.bsp.BspImpl.run(BspImpl.scala:465)
  scala.cli.commands.bsp.Bsp$.runCommand$$anonfun$1(Bsp.scala:185)
  scala.runtime.function.JProcedure1.apply(JProcedure1.java:15)
  scala.runtime.function.JProcedure1.apply(JProcedure1.java:10)
  scala.build.bsp.BspThreads$.withThreads(BspThreads.scala:23)
  scala.cli.commands.bsp.Bsp$.runCommand(Bsp.scala:174)
  scala.cli.commands.bsp.Bsp$.runCommand(Bsp.scala:76)
  scala.cli.commands.ScalaCommand.run(ScalaCommand.scala:390)
  scala.cli.commands.ScalaCommand.run(ScalaCommand.scala:371)
  caseapp.core.app.CaseApp.main(CaseApp.scala:166)
  scala.cli.commands.ScalaCommand.main(ScalaCommand.scala:356)
  caseapp.core.app.CommandsEntryPoint.main(CommandsEntryPoint.scala:370)
  scala.cli.ScalaCliCommands.main(ScalaCliCommands.scala:125)
  scala.cli.ScalaCli$.main0(ScalaCli.scala:320)
  scala.cli.ScalaCli$.main(ScalaCli.scala:124)
  scala.cli.ScalaCli.main(ScalaCli.scala)
coursier.error.ResolutionError$CantDownloadModule: Error downloading ch.epfl.scala:bloop-frontend_2.12:2.0.2
  not found: /home/jmares/.ivy2/local/ch.epfl.scala/bloop-frontend_2.12/2.0.2/ivys/ivy.xml
  download error: Caught javax.net.ssl.SSLHandshakeException (PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target) while downloading https://our-server/with-self-signed-certificate/repo/ch/epfl/scala/bloop-frontend_2.12/2.0.2/bloop-frontend_2.12-2.0.2.pom
  coursier.Resolve$.$anonfun$validate$1(Resolve.scala:403)
  scala.collection.immutable.List.map(List.scala:247)
  scala.collection.immutable.List.map(List.scala:79)
  coursier.Resolve$.validate(Resolve.scala:401)
  coursier.Resolve.validate0$1(Resolve.scala:160)
  coursier.Resolve.$anonfun$ioWithConflicts0$4(Resolve.scala:210)
  coursier.util.Task$.$anonfun$flatMap$extension$1(Task.scala:14)
  coursier.util.Task$.$anonfun$flatMap$extension$1$adapted(Task.scala:14)
  coursier.util.Task$.wrap(Task.scala:82)
  coursier.util.Task$.$anonfun$flatMap$2(Task.scala:14)
  scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470)
  java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
  java.base@17.0.6/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
  java.base@17.0.6/java.lang.Thread.run(Thread.java:833)
  com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:775)
  com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:203)

it looks like the problem is with coursier that is running its own JDK and we have to somewhere specify -Djavax.net.ssl.trustStore=/opt/jdk/lib/security/cacerts' but I don't know where :-(
PS. The JAVA_HOME jdk and IntelliJ IDEA JDK cacerts contains imported certificate to verify self-signed server certificate.
PS2. I am a little bit confused because the file .scala-build/ide-envs.json contains  value:
"COURSIER_REPOSITORIES":"ivy2local|http://our-server/with-self-signed-certificate/repo"
that is specified using ENV variable COURSIER_REPOSITORIES but coursier loads artefacts from repository specified in scala-cli config.
PS3. If I removed this environment variable the value COURSIER_REPOSITORIES has been missing in .scala-build/ide-envs.json file.

Did you do scala-cli setup-ide -Djavax.net.ssl.trustStore=/opt/jdk/lib/security/cacerts  .  ? It should then use that property while downloading.

@tgodzik That's it ... it works. Great .... I am going to try to finalize solution based on it.


"waiting for git blame response" flashes very quickly whenever editing a file

I have the extension in my status bar. However, whenever I'm editing a file and the editor autosaves, the text "waiting for git blame response"  pops up and disappears immediately, triggered by the autosave. This is distracting to me and bothers me more than it should haha, so I would like to suggest that this text is only shown if the git blame response takes longer than ~500ms? Thank you. :)

Hey Jasper! Thanks for the feature request.
I fear that it would need to be implemented the other way around: Forcing a minimum time the "processing"-message is displayed.
Would that still be interesting?

@Sertion I share the same issue, wouldnt the easiest be to provide a setting for defining for how this message should appear:

And then I could just put in an empty string to hide it?

Thanks for the input Benjamin! Sadly hiding the status bar text will not mitigate the blinking issue. It can even make it worse as when an element gets more narrow other information that was previously hidden in the status bar gets shown.
This is why I ask about setting a minimum time shown value instead. This has a few side effects:

The user still gets feedback on what is going on
The blinking will be mitigated (and can be regulated by the user (if it becomes a setting))
The chance that other status bar messages pop in and out is also mitigated

I've not yet implemented this as I do not exactly know when the implemented features is resolving the issue.

Hm, so today there is an immediate progress indicator in the status bar as soon as I make changes to a line:

I am just asking for a setting to not show this in-progress message at all. Simply leave the last blame info you had at the line and transition to the "Changed by you" when you figure out it was changed by me.
So in other words, I am just asking for not showing the in-progress animation which is also spinning.

I've implemented something based on the discussion here and made a preview version: gitblame-10.9.0-preview.zip.
It moves the "Waiting for git blame response"-message to the tool tip and removes the spinning from the icon. It has the issue of other status bar items now being able to pop in and out, but I don't know how common that is. Please, if you have time, have a look and report back!

Yeah that feels already a lot better to me, thanks! I personally still do not mind to not be notified that the info is computed because its obvious when the label is not there to me at least.


 Thank you!

In the next update, column alignment will be supported, but all columns are in the same player order.

Column alignment mode has been supported. To switch, you need to modify the configuration file HUD.hurt.HUDRankMode = 1. Can display up to 8 player, but I recommend not exceeding 4 in the settings.


Supplemental fix for issue 14860

https://issues.dlang.org/show_bug.cgi?id=14860
Required by: https://github.com/D-Programming-Language/dmd/pull/4856
task[] = RTask.init; has two bugs:

RTask is a nested struct, so RTask.init contains null context pointer.

Fixed to use emplaceRef on each elements.

Auto-merge toggled on

Please do not merge your own PRs.


AXML/ARSC UTF-8 string decoding improvements

I noticed androguard doesn't handle all the oddities of AXML/ARSC UTF-8 string decoding (specifically, the presence of surrogate pairs and strings with a length that doesn't fit into two bytes); you might want to take a look at how my parser handles those.

Hi @obfusk thanks for pointing this out. Indeed I had noticed that the case when the length does not fit into two bytes for both utf8 and utf16 is not covered as this is one of the 'tricks' used by some malware to attempt to break static analysis tools.
Though I did not even know about the surrogate pairs and that they should be supported.
Will try to take a look in the upcoming days/weeks

Though I did not even know about the surrogate pairs and that they should be supported.

I think it's because Java uses UTF-16 internally and somehow they end up used in UTF-8-encoded strings as well even though they should not be used there and will result in something lke UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position 20: invalid continuation byte in Python by default.
For example, the NewPipe APK contains a UTF-8-encoded string containing the 🔍 emoji (encoded as \xed\xa0\xbd\xed\xb4\x8d) in its resources.arsc. But I've seen those pairs show up in many APKs having emoji in a string (as those are not part of the Basic Multilingual Plane and thus encoded as a surrogate pair in UTF-16).
An example of the "length overflow" occurring in a non-malware APK is e.g. this APK.
Looking at it again now I just realised my linked code had a bug which I just pushed a fix for :sweat_smile:


proxified objects should not cache values returned by getters

Consider this code:
const list = proxify(PyObject.list([1]));
console.log(list.length); // displays 1
list.append(2);
console.log(list.length); // still displays 1, stored in __pymport_proxy__

Fixed by #7


transparent windows is work in windows but fail in android

Godot version
4.0 dev
System information
source code 4.0 version on github
Issue description
set Per Pixel Transparency ->Allowed is enable.
and add fellow code in script
'''
extends Node
func _ready():
DisplayServer.window_set_flag(DisplayServer.WINDOW_FLAG_TRANSPARENT,true)
'''
it's ok windows

fail in android mobile

Steps to reproduce
....
Minimal reproduction project
.....

I do not think that android support for transparent windows is implemented. Here is the quote from the docs. Thank you.
"Note: Transparency support is implemented on Linux (X11), macOS and Windows, but availability might vary depending on GPU driver, display manager, and compositor capabilities."

Know the reason why android is not supported？

I do not think that android support for transparent windows is implemented. Here is the quote from the docs. Thank you.
"Note: Transparency support is implemented on Linux (X11), macOS and Windows, but availability might vary depending on GPU driver, display manager, and compositor capabilities."

Do you have a link to the article? I did not find it

Have you tried to use the search function of the online docs?
You can find it mentioned in different places:

https://docs.godotengine.org/en/latest/classes/class_window.html#class-window-property-transparent
https://docs.godotengine.org/en/4.0/classes/class_displayserver.html#enumerations

Thank you. Yes, I have searched for it. I just found out that you need to add a colon when searching for godot. Otherwise, the search will not be correct.

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/36860.


Grid sizing is broken with Grid.ColumnSpan.

The following code:
        new Grid
        {
            ColumnDefinitions = new ColumnDefinitions
            {
                new ColumnDefinition(GridLength.Auto),
                new ColumnDefinition(new GridLength(4, GridUnitType.Pixel)),
                new ColumnDefinition(GridLength.Auto),
            },
            RowDefinitions = new RowDefinitions
            {
                new RowDefinition(GridLength.Auto),
                new RowDefinition(new GridLength(4, GridUnitType.Pixel)),
                new RowDefinition(GridLength.Auto),
                new RowDefinition(new GridLength(4, GridUnitType.Pixel)),
                new RowDefinition(GridLength.Auto),
                new RowDefinition(new GridLength(4, GridUnitType.Pixel)),
                new RowDefinition(GridLength.Auto),
            },
            Children = new Controls
            {
                new TextBlock
                {
                    Text = "Log In",
                    FontSize = 24,
                    HorizontalAlignment = HorizontalAlignment.Center,
                    [Grid.ColumnSpanProperty] = 3,
                },
                new TextBlock
                {
                    Text = "Username",
                    VerticalAlignment = VerticalAlignment.Center,
                    [Grid.RowProperty] = 2,
                },
                new TextBox
                {
                    MinWidth = 120,
                    [Grid.ColumnProperty] = 2,
                    [Grid.RowProperty] = 2,
                },
                new TextBlock
                {
                    Text = "Password",
                    VerticalAlignment = VerticalAlignment.Center,
                    [Grid.RowProperty] = 4,
                },
                new TextBox
                {
                    MinWidth = 120,
                    [Grid.ColumnProperty] = 2,
                    [Grid.RowProperty] = 4,
                },
            },
        };

Produces this:

The central column should be 4 pixels, but it's being stretched by the first row's Grid.ColumnSpan property. Grid was ported from Moonlight so I have no idea why it's not working.

Fixed by https://github.com/Perspex/Perspex/pull/396


Failed to execute goal on project com.vmturbo.mediation.azure: Could not resolve dependencies for project com.vmturbo:com.vmturbo.mediation.azure:jar:6.0.2-SNAPSHOT: Could not find artifact com.microsoft.azure:azure-client-authentication:jar:1.1.2-SNAPSHOT in ossrh (https://oss.sonatype.org/content/repositories/snapshots/) -> [Help 1]

[WARNING] Could not validate integrity of download from https://oss.sonatype.org/content/repositories/snapshots/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata.xml: Checksum validation failed, no checksums available
[WARNING] Checksum validation failed, no checksums available for https://oss.sonatype.org/content/repositories/snapshots/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://oss.sonatype.org/content/repositories/snapshots/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata.xml (0 B at 0.0 KB/sec)
[WARNING] The metadata /Users/imranbijapuri/.m2/repository/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata-ossrh.xml is invalid: input contained no data
[WARNING] The metadata /Users/imranbijapuri/.m2/repository/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata-ossrh.xml is invalid: input contained no data
[INFO] Downloading: http://build.vmturbo.com:8081/nexus/content/repositories/vmturbo/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/azure-client-authentication-1.1.2-SNAPSHOT.pom
[INFO] Downloading: http://build.vmturbo.com:8081/nexus/content/repositories/snapshots/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/azure-client-authentication-1.1.2-SNAPSHOT.pom
[INFO] Downloading: http://repo2.maven.org/maven2/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/azure-client-authentication-1.1.2-SNAPSHOT.pom
[INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/azure-client-authentication-1.1.2-SNAPSHOT.pom
[INFO] Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/azure-client-authentication-1.1.2-SNAPSHOT.pom
[WARNING] The POM for com.microsoft.azure:azure-client-authentication:jar:1.1.2-SNAPSHOT is missing, no dependency information available
[WARNING] The metadata /Users/imranbijapuri/.m2/repository/com/microsoft/azure/azure-client-authentication/1.1.2-SNAPSHOT/maven-metadata-ossrh.xml is invalid: input contained no data

probably due to a temporary network issue when publishing snapshots. See if you still run into this problem.


Sorting for multiple fields not working in json-server v1

Hi @typicode,
I see that in json-server v1, sorting for multiple fields is not working. It just works for firstfield. Documentation shows the following example:
GET /posts?_sort=id,-views
But in this example sorting only sorts in ascending order by id. Second sorting by views in descending order doesn't work.

My bad, is working as expected. Closing issue! Sorry for the mistake


Press Key Native   517     failed due to invalid key code

Originally submitted to Google Code by zwb0... on 22 Oct 2012

Hi,
When I try to use "Press Key Native  517" to press Exclamation mark !, I always got "ERROR: Problem during keyDown: Invalid key code". But it works with numbers, letters and some special keys like tab, enter.
Best regards,
Weibin
library version: robotframework-seleniumlibrary-2.9.1.win-amd64 + robotframework-2.7.4.win-amd64
Python:  python-2.7.3.amd64
operating system: windows 7

Originally submitted to Google Code by @pekkaklarck on 13 Jan 2013

Key pressing is handled outside this library so there isn't anything we really could do to it. If I remember correctly, it is actually handled also outside Selenium itself and done fully on Java. If I, again, remember correctly, these key codes changed slightly in Windows 7 for some reason.


Added support for zimop extension

Added support for Zimop extension.
For both open-source compilers: GCC and Clang already prepared corresponding patches. Going to publish them.
cc: @kito-cheng

@kito-cheng, any objections?

Squashed and merged.
Thanks!

Since these maybe ops can be used to implement real operations like Zicfiss, I think we need to define some additional behavior.
Can they be reordered with loads/stores? Can they be moved across calls? Can they be speculated? Can they be duplicated?

I'm not sure it makes sense to have 32 bit forms of mop intrinsics on RV64? What is the compiler supposed to put in the upper bits? For the bitmanip intrinsics that we did this for, we knew that the upper 32 bits of the input only affected the upper 32 bits of the result or we defined rev8_32 as rev8+sraiw.
For the may-be-ops we don't know what the real instruction will be so we don't know how to treat the upper bits.

What is the actual use case for these existing, rather than giving named ones for specific ones?


go-toml: invalid key type at baseURL: string

Using hugo v0.19 on linux and trying to create a new site, will generate an empty config.toml:
hugo new site .
I investigated the problem a little bit and it turned out that the a recent commit in go-toml broke the backward compatibility https://github.com/pelletier/go-toml/commit/7e6e4b1314c49d42d1bff74c340894921f0ccfac
They changed the tree.String function and it now calls ToWrite which asserts each config value against tomlValue type that will fail.
I am not sure what is the correct way to fix it, but I like help if you give me some hints. For instance maybe change the default config defined in createConfig before sending it to TreeFromMap

Looksl like it is Windows only? See #3146

@bep I ran the same test on my Debian machine and here is the result (Well, part of it):
--- FAIL: TestNewContent (0.02s)
        content_test.go:68: [0] "title = \"Post Arch title\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [1] "test = \"test1\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [2] "date = \"2015-01-12T19:20:04-07:00\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [0] "title = \"Empty Date Arch title\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [1] "test = \"test1\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [0] "title = \"sample 2\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [0] "title = \"sample 3\"" missing from output:
                "+++\n\n+++\n\n"
        content_test.go:68: [0] "title = \"sample 4\"" missing from output:
                "+++\n\n+++\n\n"
FAIL
exit status 1
FAIL    github.com/spf13/hugo/create    0.029s

OK, I'll assume you're not vendoring (i.e. using govendor and make check), which we also seem to have some issues with on the Windows build. The related PR also fails in the referenced PR, but now with an actual error message.


Jenkins backend

Extract an entity-oriented Jenkins Backend
Originally, the jenkins plugin was frontend-only. This PR extracts a separate backend plugin with an entity-oriented API which allows the creation of a jenkins-backend plugin which provides a hook to allow Integrators to customise how jenkins instances (and the jobs for entities) are discovered.
Examples are provided and documented in the backend plugin readme
This was mainly done to focus discussion on https://github.com/backstage/backstage/issues/5518 but may also prove to be an alternative to https://github.com/backstage/backstage/pull/5016
An entity has an array of associated projects each of which has a number of builds. This is a filtered and augmented view of the upstream jenkins project and build models. This model is used as the response objects from the API but also throughout the UI.
Apart from moving some functionality into the backend, the intermediate model CITableBuildInfo (which represented a build with some project info) has been removed in favour of using Project and Build throughout.
TODO

[x] Support retry
[x] Add changesets

Route change for specific builds
New backend plugin needed (incl. config)
New annotation name and possible values

[x] Remove all ts-ignore
[x] config schema
[ ] Render errors (particularly from invalid config) in UI
[x] update microsite
[ ] tests

There are some more refactoring / improvement which could be done but I'm not sure if including it here would make this PR too complicated.

rename useBuilds hook to useProjects, useBuildWithSteps to useBuild and generally make sure we are consistent with jenkins terminology
Support an entity having multiple associated jenkins jobs

In router.ts and internal backend APIs generally
in DefaultJenkinsInfoProvider

Support more possible jenkins layouts (in both the code in router.ts and the UI)
Move off of the jenkins client library and just use direct REST calls.

The client library is <1.0 and the typings are out of date

How do we generically reference a specific project. Currently this is entity + jobName but that doesn't scale to allow an entity to have jobs on multiple jenkins instances (build + deploy for example)

Questions

The documentation feels a bit split across the READMEs in frontend and backend plugin, would it be better merged into one place
I have change the id of the jenkinsApiRef. Is this needed as this is only used in the frontend plugin itself so doesn't need to be versioned particularly.
I have included support for a simpler configuration scheme if you only have 1 instance (jenkins.baseUrl) and have described it as "deprecated" which I don't think is right as we only introduced it in this PR! How do we feel about the simplest possible config being:

jenkins:
  instances:
    - name: default
      baseUrl: https://jenkins.example.com
      username: backstage-bot
      apiKey: 123456789abcdef0123456789abcedf012

instead of:
jenkins:
  baseUrl: https://jenkins.example.com
  username: backstage-bot
  apiKey: 123456789abcdef0123456789abcedf012

The latter is more expressive but adds complexity in having to explain 2 config layouts.

Is the route change in the UI too big a change?
Should the frontend plugin expost an API for extensibility or is the backend ones enough?

closes #5016 #5518

I think this is ready for another review if you'd be so kind (@Rugvip @freben).
I might add some more UI tests and error handling but nothing which will affect the overall implementation.
P.S. there is an API failure which is probably legit for the jenkins plugin but seems to e complaining about auth? I will have a look at that another day.
CC @jot-hub @goober @adamdmharvey @Fox32

@ashirley friendly ping here 👍

I have worked on some of the comments. I still have some to go.
RE the jobName vs. jobSlug, if I'm honest the more I say jobSlug to myself the more I think that isn't the right name and that jobFullName would be better (more descriptive of it being a path through the folders to the job and closer to the language of jenkins itself). If no one objects I might rename to be consistent with that rather than jobSlug

RE the jobName vs. jobSlug, if I'm honest the more I say jobSlug to myself the more I think that isn't the right name and that jobFullName would be better (more descriptive of it being a path through the folders to the job and closer to the language of jenkins itself). If no one objects I might rename to be consistent with that rather than jobSlug

The argument of being close to the terminology of the system at hand, weighs heavier than being consistent with other annotations, at least in my personal opinion :)
I bet these have some technical name in the Jenkins API. That might be something to copy.
Also remember that the annotation should be kebab-case in the end, not camelCase.

Is this doc relevant to the discussion?
https://www.jenkins.io/doc/book/using/referencing-another-project-by-name/

Does anyone know why api-reports is failing because of this diff
-import { Logger } from 'winston';
+import { Logger as Logger_2 } from 'winston';

I can just commit it but it seems wrong

Yeah don't worry about that right now. Those discrepancies are annoying but semantically the result is the same. We're working on upgrading these libs and hopefully getting it on better order

@ashirley when this happens to me I usually delete the reports file that exists and rerun the yarn build:api-reports command

Is this doc relevant to the discussion?
https://www.jenkins.io/doc/book/using/referencing-another-project-by-name/

Sort of (Jenkins isn't very consistent with their domain models :-( )
While it appears definitive, path name doesn't feature in the JSON api at all and even inn the Java API, it looks like fullName is synonymous with an absolute path name ( https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L2964 ) So I have gone for job-full-name

@ashirley I'm happy to merge this now @freben's comments have been implemented not to block this for too long and to get some more feedback from users. Can you fix up the api-report last time as we've got a conflict. We've updated the formatting of the api-reports now so they're more standardised. :D


Questions regarding the Workbook...

Hello @dolevshor
I want to verify if the Workbook located at https://github.com/dolevshor/azure-orphan-resources/tree/main/Workbook contains any commands that will retrieve data from the Azure Environments in which it is utilized, allowing you to view the data.
I want to confirm with you before configuring this workbook in my environments. I hope in this workbook you haven't configured to pull information on which azure environments it was configured.
If you can able to confirm that I can able to configure this in my environment and test it out . As I need to be save as the code is in Public Repos and other security reasons.
Please confirm Awaiting your valuable feedback..
Thank You....

Hello @Anto4595 ,
This Workbook doesn't contain any commands that will retrieve or pull data from your Azure environment.
You can find all the queries that included in this Workbook here.

Hello @dolevshor
Thank You for the Reply...
I checked the Workbook seems to be fine. I found something that is in Overview I can see the Subnets and some values.
But When I try to check the values under Networking Subnets are not available is there any issue ?

Can you clarify ?

Hi @Anto4595 ,
You can find the Subnets in Networking --> Virtual Networks --> Subnets.
These is 2 close issues with the same topic:

https://github.com/dolevshor/azure-orphan-resources/issues/28
https://github.com/dolevshor/azure-orphan-resources/issues/37


Remove OpenSeaDragon

User story
Currently we use OpenSeaDragon for visualizing the tiled OME-TIF files.  There is, however, considerable lag between it and the deck.gl layers.  In addition, we need deck.gl's ability to handle different data formats/views easily.
Preferred solution
Implement tile viewing in deck.gl.

@ilan-gold : The demo you showed me earlier looked good -- I would encourage you to merge it to master soon, and make a new release, and push a demo to vitessce.io. With more people working on it, we need to be really careful about letting master get too stale.


Jenkinsfile: archive artifacts before junit step

Sometimes, junit step does not find reports and this
causes break of execution and some artifacts may get lost.
Let's archive artifacts before junit step.

positive-result testing can't show the effect of this change


DHCP offer does not get delivered to docker container

I have below configuration.
VM1 : Rest2DHCP API server with 2 interfaces, eth0 (<IP_ADDRESS>) and eth1 (<IP_ADDRESS>)
VM2 : Running ubuntu DHCP Server
I am running  rest2dhcp server as, "docker run  -e SERVER="<IP_ADDRESS>" -e RELAY="<IP_ADDRESS>" -e MODE=udp -p 8080:8080 -p 67:67/udp  zauberhaus/rest2dhcp".
I see the DHCP offer coming to eth1 but it does not get delivered to docker0 interface.
Am I missing some configuration to get this working?

This sounds like a problem with the docker configuration.
Is docker really listening on the eth1 interface?
Which DHCP server are you using on the Ubuntu server? Some DHCP servers have special implementations of the relay mode. This varies from incorrect ports for the response (not UDP port 67) or missing response to DHCP request.
For example, dnsmasq only works if the flag dhcp-authoritative is set.


dropdown and desc input type validation is not here.

There are validators for text. I want to use these validator for select, desc and other input type along with text type. I am not getting what should I do.

Validator checks the value of component props. You should just pass it. What problem do you have?

I am not able to get whole form validity and use form validator in select input type.

can you reproduce your issue here?

Yeah, Finally I have added https://codesandbox.io/s/4q0ynm2or4?fontsize=14 I applied validator for input type text but for type select, desc, and others it is not working and I am not able to use form methods means hot to disable button if a form is invalid.

You're using this library wrong. You should create your own SelectValidator component in the same way as TextValidator in readme. Also there is no <input type="select">, but <select>

yeah I did as you said above but it did not work i will share the code and I am not able to use forms method to disable submit button when form invalid.

you should use options={this.options()}

https://codesandbox.io/s/v6n31l8700


"Valid Column Types" wrote twice in documentation.

As the title says, I find the same heading in the documentation.
https://book.cakephp.org/phinx/0/en/migrations.html#valid-column-types
https://book.cakephp.org/phinx/0/en/migrations.html#id3
Furthermore, their contents are not the same.
I don't know which one should follow.

Can we update the docs here maybe?


NO-JIRA Clean up pom.xml files

Duplicated dependency declarations were causing the following Maven warning.  These duplicated dependencies were removed.
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.apache.activemq.tests:integration-tests:jar:1.4.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.activemq:artemis-proton-plug:test-jar -> duplicate declaration of version ${project.version} @ org.apache.activemq.tests:integration-tests:[unknown-version], /x1/jenkins/jenkins-slave/workspace/ActiveMQ-Artemis-Nightly-Regression-Test/tests/integration-tests/pom.xml, line 148, column 19
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

File server-start-stop-backup-jms-config1.xml was malformed. A missing quotation mark was added.

I don't get this PR. you have one commit reverting your own change. So this is a null PR. What do you want to be done here?
Did you push the revert by accident?

@jdanekrh I am ammending your commit description as following (during merge):
    NO-JIRA Clean up pom.xml files

    Duplicated dependency declarations were causing the Maven warnings.  These duplicated dependencies were removed.
    File `server-start-stop-backup-jms-config1.xml` was malformed. A missing quotation mark was added.

Let me know if you have issues with it? just tried to simplify it.

Sure. I should've probably aimed for brief commit message and put the details only in the PR.

No problem at all. thanks a lot for the PR 👍

The missing quote is quite funny, esp. how long it was missing ;)

I don't think that file is being used actually. it was imported from the activemq5 openwire testsuite. I don't think it's being used. I couldn't find anywhere with a git grep.


Life calculation

Total life value differs from the one in game after importing character. Can't seem to find what is causing the difference.
PoB version: 1.4.64
You can try it yourself:
Login: willnotsustain
Character: Buerno
Pastebin: https://pastebin.com/PknX8agv
Screen shot from game: https://i.imgur.com/2LOtt3G.png (7256 total life)
Screenshot from PoB: https://i.imgur.com/9n21WgF.png (6939 total life)
If there is any additional information required for localizing the issue, please let me know.

The Pariah mod +100 maximum life per red socket is currently not supported.
Mods on items or tree that have a red color are currently not supported. PoB only supports calculations for mods with green colors.
Since this issue is submitted quite often (#428, #304, #207, #107) it might be time to think of a better way of displaying unsupported mods. A striket hrough the text might be better suited. Red/green are already used for changes in calculated values. Little tooltip note might also help.

I don't know why I didn't think about it.
Maybe it'd be a good idea to treat Pariah as Variant unique depending on socket colour.
Thanks for the heads up.

Socket color isn't supported at the moment (see #353). You could just manually add a line by editing the item that just adds +100 life.

Duplicates #353, as per @eps1lon's comment.


How to enable soft deletes?

Hi there,
Is there any way to enable the soft delete functionality? I am checking the tables, there is a column of deleted_at but I couldn't find how to enable it. I have also checked the configuration file. How can we add configurable variable for it?

Yes we have that field deleted_at added into database table, but this functionality wasn't tested on this package before. You'll need to check Laravel documentation and possibly override the model if any custom logic is needed. https://laravel.com/docs/8.x/eloquent#soft-deleting

Yes we have that field deleted_at added into database table, but this functionality wasn't tested on this package before. You'll need to check Laravel documentation and possibly override the model if any custom logic is needed. https://laravel.com/docs/8.x/eloquent#soft-deleting


jsonSerialize() method made compatible with PHP 8.1

This library fails to work in PHP 8.1 environment because signatures of internal methods has changed
(see https://wiki.php.net/rfc/internal_method_return_types).
This PR adds #[ReturnTypeWillChange] attribute to jsonSerialize() methods to suppress deprecation warning on PHP 8.1.

This will not be merged before the arrival of PHP 8.1, and not before PHP 8.1 has been added to the CI environment (Github Actions).

I'll close this in favor of the PR by @driesvints that addresses more 8.1 issues, and has another fix for the serialization problem.


Document not defined in worker import

Describe the bug
While running in dev mode and importing a worker that has dependency on a css file. The worker fails to start with document not defined

I have created a minimal reproduction of the issue on stackblitz
worker.ts
import styles from './worker.module.css';

self.onmessage = () => {
  console.log('hello world', styles.container);
};

imported in
App.tsx
import * as React from 'react';
import reactLogo from './assets/react.svg';
import viteLogo from '/vite.svg';
import './App.css';
import worker from './worker.ts?worker';

function App() {
  const [count, setCount] = React.useState(0);
  React.useEffect(() => {
    const w = new worker();
    w.postMessage('hey');
  }, []);
  return (
    <>

Vite + React

        <button onClick={() => setCount((count) => count + 1)}>
          count is {count}
        </button>

          Edit src/App.tsx and save to test HMR

        Click on the Vite and React logos to learn more

    </>
  );
}

export default App;

Reproduction
https://stackblitz.com/edit/vitejs-vite-t1i3lx
Steps to reproduce
Run npm install then run npm run start
Expected:
console log of Hello world hash
Actual:
Console throws errors and webWorker fails to start.
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1
    vite: ^5.3.1 => 5.3.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This minimal reproduction included React and that is not necessary. https://stackblitz.com/edit/vitejs-vite-lblszh

I am running into a similar issue after upgrading to vite 5. It could be a similar error to one that was fixed in vite 4 https://github.com/vitejs/vite/issues/12611

Importing CSS files without ?url or ?raw in workers doesn't make sense as it's not possible to modify/inject CSS from workers directly. What is the expected behavior?

Importing CSS files without ?url or ?raw in workers doesn't make sense as it's not possible to modify/inject CSS from workers directly. What is the expected behavior?

I would expect the CSS to be omitted with a warning during build time.


useAsyncList needs to be improved to better handle paging use cases

🙋 Feature Request
useAsyncList's API could be improved when it comes to dealing with paging and common use cases within an app.

🤔 Expected Behavior
An improved API for handling ComboBox use cases, particularly when dealing with async paging.

😯 Current Behavior
Take this example sandbox: https://codesandbox.io/s/combobox-with-default-based-on-first-loaded-item-forked-v5j0k (the sandbox manages selectedKey separately from useAsyncList because of https://github.com/adobe/react-spectrum/issues/1923)
Select Sly Moore. Select the Moore text inside the input and hit delete. Now blur off the field. It’s able to restore the filter text back to Sly Moore because Sly Moore is in the page of results for the Sly query. That’s good.
Now select Sly Moore again, clear the input and type D. Now blur off the field. In this case, it can’t restore the filter text back to Sly Moore because Sly Moore is no longer in the loaded page of items.
In other words, I also need to manage caching the filter text and restoring it rather than leveraging list.getItem(key), because nothing guarantees that my item will still be in list.items.
Also, if the app is loading a list of Star Wars characters through useAsyncList, and the user selects one of the characters, very often the app needs access to the character object itself rather than just the key. If the prescribed way of accessing the character object is by doing list.getItem(key), then that can fail whenever list.items doesn’t contain the item matching the selected key.
So, for example, in the Star Wars case described above, when you type D and then blur off the field, the ComboBox calls our onSelectionChange handler with a key of Sly Moore. Since ComboBox said the selection changed and that the selected key is Sly Moore (even though the selection didn’t really change since Sly Moore was previously selected as well), the natural thing to do is to access the object for Sly Moore by doing list.getItem(key), but that returns undefined because Sly Moore isn’t in items.list. This forces us to add additional logic to deal with the situation that ideally wouldn't be necessary.
Another thing worth considering is that when the user manually opens the menu, we want to load the first page of unfiltered items and not the items that match the current filter text. We can accomplish this by managing a showAll state as described in https://react-spectrum.adobe.com/react-spectrum/ComboBox.html#custom-filtering, but it seems like this could be managed by useAsyncList or, maybe more appropriately, a higher-level useComboBox hook that would provide a function that we could pass to ComboBox's onOpenChange. A higher-level hook might be more appropriate for handling some of the other logic I've described in this issue as well.
Something else to consider is that in our app, sometimes we know the selected key that should be selected by default in a ComboBox, but we don't know its label. If, on the first time load is called, we were to just load the first page of items, the page of items may not contain the item corresponding to the key we want selected by default. As such, we wouldn't have access to the item label we need to set the filter text. The way we handle this situation currently is that, before using useAsyncList, we load the default item from the server. Once we have the default item loaded into the app, we start using useAsyncList and we can set the filter text properly. This could very well be the most appropriate approach, but it's possible that useAsyncList could better accommodate the situation somehow. Of the things I've brought up in this issue, this one is the least of my concerns.
Anyway, thanks for considering.

💁 Possible Solution
I haven't thought through a proper API at this point, but an API that's less reliant on using list.items (which represents the list of items in the menu) for accessing the selected item (which may not be in the menu) would be an improvement. Also, it may make sense to build a higher-level hook that's more accommodating to the type of ComboBox use cases we commonly run into could help reduce the amount of logic in our apps.

🔦 Context
Trying to implement a ComboBox with async paging has been quite complex and could probably be simplified.

💻 Examples

🧢 Your Company/Team
Adobe, Data Collection

🎁 Tracking Ticket (optional)

FWIW, we ended up writing our own usePagedComboBox hook instead of using useAsyncList. It might provide some ideas: https://github.com/adobe/reactor-extension-alloy/blob/84a061595f557cda77d0f0f6d82d15f083e90368/src/view/utils/usePagedComboBox.js


[ALLUXIO-2365] Parameterize the returned type Inode in TempInodePathForDescendant.getInode

https://alluxio.atlassian.net/browse/ALLUXIO-2365

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14099/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. thanks!


[Beta] Challenge - Install and Set Up Mongoose test fails to pass

Challenge Name

https://beta.freecodecamp.org/en/challenges/mongodb-and-mongoose/install-and-set-up-mongoose
Issue Description

When I submit the glitch app I receive a timeout. I checked what is being tested here and when I extended my Glitch url with _api/file/package.json in the browser as a test, I received the following error message. Cannot GET /_api/file/package.json. I had to use the following code I am posting underneath to get it to work. I found that code on issue #16761.
Nowhere can I find in the challenges where freeCodeCamp goes into setting up that CORS code to GET that file. Did I completely miss it or did glitch update so that CORS needs to be allowed?
This is the Glitch url here and the Glitch url when I append the _api call is here. It is currently not working. When I did have this CORS code underneath posted in my server.js file it passed the test. It could GET the file and parse it. It also then displayed in the browser.
As a last note. I am testing some of the beginning backend challenges in Managing Packages with npm and they fail with the same error where it cannot GET files from the Glitch url.
Browser Information

Browser Name, Version: Firefox Developer Edition, 59.0b9 (64-bit)
Operating System: Manjaro Deepin Linux
Mobile, Desktop, or Tablet: Desktip

Your Code

var express = require('express');
var app = express();
try{
  var mongoose = require('mongoose');
} catch (e) {
  console.log(e);
}
var fs = require('fs');
var path = require('path');
var bodyParser = require('body-parser');
var router = express.Router();

var enableCORS = function(req, res, next) {
  if (!process.env.DISABLE_XORIGIN) {
    var allowedOrigins = ['https://marsh-glazer.gomix.me','https://narrow-plane.gomix.me', 'https://www.freecodecamp.com'];
    var origin = req.headers.origin;
    if(!process.env.XORIGIN_RESTRICT || allowedOrigins.indexOf(origin) > -1) {
      console.log(req.method);
      res.set({
        "Access-Control-Allow-Origin" : origin,
        "Access-Control-Allow-Methods" : "GET, POST, OPTIONS",
        "Access-Control-Allow-Headers" : "Origin, X-Requested-With, Content-Type, Accept"
      });
    }
  }
  next();
};

// global setting for safety timeouts to handle possible
// wrong callbacks that will never be called
var timeout = 10000;

app.use(bodyParser.urlencoded({extended: 'false'}));
app.use(bodyParser.json());

app.get('/', function(req, res) {
  res.sendFile(path.join(__dirname, 'views', 'index.html'));
});

router.get('/file/*?', function(req, res, next) {
  if(req.params[0] === '.env') { return next({status: 401, message: 'ACCESS DENIED'}) }
  fs.readFile(path.join(__dirname, req.params[0]), function(err, data){
    if(err) { return next(err) }
    res.type('txt').send(data.toString());
  });
});

app.use('/_api', enableCORS, router);

var listener = app.listen(process.env.PORT || 3000 , function () {
  console.log('Your app is listening on port ' + listener.address().port);
});

Screenshot

I'm posting a working url here. It passes the Challenge and it also displays the file in the browser. But I need to setup the server.js to look like the code I posted above to work.


issue with checkpoint saving

The error arise from:
transfusion.py:779---->  if learned_value_residual_mix else (lambda _: 0.5)
Error:
rank0:   File "/ccs/home/palashmr/packages/miniconda/pyt_env/transfusion/lib/python3.12/site-packages/torch/serialization.py", line 780, in save
rank0:     _save(
rank0:   File "/ccs/home/palashmr/packages/miniconda/pyt_env/transfusion/lib/python3.12/site-packages/torch/serialization.py", line 1004, in _save
rank0:     pickler.dump(obj)
rank0: AttributeError: Can't get local object 'Attention.init.locals.lambda"
Potential solution:
to replace lambda function with a regular function.

@mijanur132 ah, how about after upgrading to 0.6.5?


Como criar um endereço TRC20?

Hi,
This package is supposed to interact with Tron blockchain and does not support wallet creation and transaction signing. I have another package which will help you: wallet.


[Bug Report] el-select component selection after value has not changed

Element UI version
1.2.9
OS/Browsers version
win7
Vue version
2.3.0
Reproduction Link
https://jsfiddle.net/ggxajuoc/
Steps to reproduce

What is Expected?
选择后 input的value应显示出来
What is actually happening?
选择后 input的value没有显示出来

ran to the same situation. After update to 1.2.9, the el select won't work. I mean, the value is there, just not displayed. same as your example one jsfiddle here:  https://jsfiddle.net/api/post/library/pure/
Just try it.

Some extra infomations:

Worked well when multiselect is on.
Fall back too 1.2.8/7/6, the problem still exstis. I also updated other node_modules, no clue if that will make this issue happen.

it seems it is the problem of<EMAIL_ADDRESS>you can install<EMAIL_ADDRESS>temporarily. https://jsfiddle.net/ggxajuoc/1/

Yes, that fix the issue. When fallback vue, just remember to fallback vue-template-complier eigther.

vue and vue-template-complier versions are consistent, that fix the issue

vue and vue-template-complier，需要保持一直吗？

@zkeyword 如果vue是2.2.6，是不是vue-template-complier也必须是2.2.6的吗

@mehooo yes

the same to you ,
i just change the version of vue and vue-template-complier,
i',m waiting for the result

i set the version all of vue and vue-template-complier to 2.2.6,
but it does not work

@LXMin  me too

All right, I'm already on it.

hey ,guys ,i have sole the problem, you need to set the package.json ,
like this:
vue: 2.2.6
not this:
vue:^2.2.6
because the<EMAIL_ADDRESS>is not suitable for the<EMAIL_ADDRESS>so that we have to drop down the version of vue ,
waiting for the element team to resolve the bug

Fixed in 1.3.0-beta.1.
Please note that 1.3.0-beta.1 requires Vue 2.3.x.

this is bug,you should use "vue": "2.2.6", not "vue": "^2.2.6",


Search page filter a11y

Filters on the search page are showing a11y errors incl:

missing form label on search bar
multiple form labels on the checkbox

Also alerts on the checkboxes not being in fieldsets - can we please add those for the 3 filter types
Possibly look at how IDs are handled on the input component
Acceptance Criteria:

[ ] No issues when you run pa11y on search
[ ] Search still works

also seen here: https://github.com/oaknational/Oak-Web-Application/issues/1608

moved to notion


[SPARK-49300][CORE]Fix Hadoop delegation token leak when tokenRenewalInterval is not set.

When tokenRenewalInterval is not set, HadoopFSDelegationTokenProvider#getTokenRenewalInterval will fetch some tokens and renew them to get a interval value.
https://github.com/apache/spark/blob/dd259b0b27841e6dd7c07f8ca3cc05d275863dd5/core/src/main/scala/org/apache/spark/deploy/security/HadoopFSDelegationTokenProvider.scala#L60-L64
These tokens do not call cancel(), resulting in a large number of existing tokens on HDFS not being cleared in a timely manner, causing additional pressure on the HDFS server.

Not sure why there is one method named getTokenRenewalInterval, seems that it only wants to get the renewal interval about tokens, right? If true, it has been got when invoke fetchDelegationTokens, and don't need to fetchDelegationTokens again. So IMO, it is enough to fetch delegation tokens at L57-L58.
https://github.com/apache/spark/pull/47800/files#diff-f7ab3d8ae8c3483d5207277bd592b7193e139edae25e111fce88a902b6b77a05L57-L58
Another one choice, give pass credentials to getTokenRenewalInterval, then it will not request again if exists for one nameservice.  tokenRenewalInterval = getTokenRenewalInterval(hadoopConf, sparkConf, fileSystems, creds).
Please correct me if something I missed. Thanks.

it has been got when invoke fetchDelegationTokens, and don't need to fetchDelegationTokens again. So IMO, it is enough to fetch delegation tokens at L57-L58.

@Hexiaoqiao I believe it gets explained in L135-L137

// We cannot use the tokens generated with renewer yarn. Trying to renew
// those will fail with an access control issue. So create new tokens with the logged in
// user as renewer.

Well, for non-YARN mode, e.g.(K8s mode), we do have a chance to save one fetchDelegationTokens call.
https://github.com/apache/spark/blob/79aeae1a9aaa2e9cfaf03a1f5d88e1447a3f9b19/core/src/main/scala/org/apache/spark/deploy/security/HadoopFSDelegationTokenProvider.scala#L93-L99

Well, Got it. If that I think @zhangshuyan0 's PR should be one direct solution. Thanks again.

Hi All, any progress here? Thanks.

+CC @attilapiros, @tgravescs

Thanks! Merged to master

@zhangshuyan0 do you think we should backport this to branch-3.5 too? if so, feel free to create another PR for the backport. (I tried to just cherry-pick this commit but there are some conflicts)

@zhangshuyan0 do you think we should backport this to branch-3.5 too? if so, feel free to create another PR for the backport. (I tried to just cherry-pick this commit but there are some conflicts)

I think so. I'll create another PR for it.

@sunchao, if there are additionally folks tagged for review, it would be good to give them a chance to get to the PR - given Apache Spark has a distributed community.


Keywords should be reserved in Stan

Summary:
Currently, various keywords can be used as variable names in Stan. This seems like a bad idea from a PL perspective.
Description:
For instance, lower and upper can be used as variable names.
Reproducible Steps:
The following is a valid Stan program, currently:
transformed parameters {
  real lower;
  real<lower=lower> upper;
  real<lower=upper, upper=lower> imconfusednow;
  print(imconfusednow);
}

Current Output:
No error.
Expected Output:
Syntax error on line 2.
Additional Information:
This is currently exploited in rstanarm.
Current Version:
v2.18.0

For instance, lower and upper can be used as variable names.

I agree---these should've been excluded as possible variable names.

This is also true with i - if you declare int i and use it as a dimension in a matrix such as matrix[i,2], you received a dimension mismatch error, whereas int I works. This is potentially because it's interpreted as the iterator in a loop?

@stnorton --- can you provide a Stan program where the problem you mention comes up?  I couldn't quite see the issue.

@bob-carpenter I created a gist. Naming one of the dimensions i (as in the provided code) produces the following error:
Error in new_CppObject_xp(fields$.module, fields$.pointer, ...) :
  Exception: mismatch in dimension declared and found in context; processing stage=data initialization; variable name=Z; position=0; dims declared=(8,1); dims found=(100,1)  (in 'model21b73681761c_norton_lab6' at line 8)

Changing the declaration on line 4 to int I and all the references to I fixes the error. Effectively, Stan seems to be interpreting i as being equal to 8, even though it is being passed as 100 with the data.

Thanks so much for the reproducible example.  I verified it's a bug.
I'm guessing there's some internal use of the variable i that's conflicting.  We try to avoid that, but something must've slipped into the generated code.  I'm going to rename and edit the issue to make it clearer to the devs what is going to need to be fixed.  This may already be fixed in 2.19, in fact, as a lot of the code generation changed there.

I verified this is fixed in 2.19 as a pleasant side effect of rebuilding the generator.


Implementation for POSIX-like signals

This PR is supposed to add signal support to HermitCore. It adds a new entry to the process control block to handle incoming signals and exposes two new system calls: sys_kill() and sys_signal(). Since newlib is supposed to manage POSIX-conform signal handling, these are only the under-the-hood changes and not POSIX conform itself, i.e. only one signal handler can registered that has to handle different signal numbers.
There are still many TODOs and this is considered work-in-progress.

@stlankes
I will test some more corner cases tomorrow, but this is basically done now.

Please do not merge yet, there's still a problem when delivering multiple queued signals I just found :/

@stlankes
This is now finally done and can be merged if Travis agrees. It now includes a bugfix for the task management that was caused by not updating the APIC timer when a task was removed from the timer queue in certain circumstances.


Link of the organization "GeoMc" is not functional

In "https://openstreetmap.community/" there is in DC this community called "GeoMc". When you click on its link, it sends you to an email called<EMAIL_ADDRESS>I am part of Montgomery College, and this email does not seem to exist or is not accessible for some reason; for all the given reasons, it would probably be better to delete "GeoMc" from the osm-community-index database.

Thanks @Fchl3001 , I removed it 👍


Flag helper

It would be great to have a helper, that displays flag image for specified language
e.g.
<%= flag(:en) %>

Implement helper:
<%= locales([:en, ru]) %>
render links for reloading page with required locales by adding current path with params "/locale=en"


node seems ok but logs show many: rpc error: code = NotFound desc = unable to find node

Background
Describe your issue here.
Logs show a bunch of
[ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
yet all my channels are active.
Your environment

version of lnd v0.15.5-beta
which operating system (uname -a on *Nix) 5.15.0-58-generic
version of btcd, bitcoind, or other backend 24.0.1
any other relevant environment details

Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
Expected behaviour
Tell us what should happen
LND shouldn't be complaining
Actual behaviour
Tell us what happens instead
mimimi all day

It looks like your node has no information about the pubkey you are searching for (in your graph). What pubkey are you looking up?

That's the thing, I'm not looking for a pubkey and all my channels are fine.
At first I thought it was a watchtower, but they also seem to be ok.

Do you run any UI software? Like RTL or Thunderhub? It's probably some kind of management software that queries for nodes that don't exist.

Zeus and RTL.
Thx for clearing that up.


Refactor and simplify Storage.put

This PR is related to user story DST-382
Description
This PR moves all "put" logic to storage.Storage.put. In addition, storage.Storage.put is made to work with urls ++ only! All API calls moved to client methods.
We should abandon the use of REST api abstractions in the long run. So, new api calls are implemented directly in client.
Checklist

[ ] PR title is descriptive and fit for injection into release notes (see tips below)
[ ] Correct label(s) are used

PR title tips:

Use imperative mood
Describe the motivation for change, issue that has been solved or what has been improved - not how
Examples:

Add functionality for Allan variance to sensor_4s.simulate
Upgrade to support Python 9.10
Remove MacOS from CI

Have a look at my comments, other than that it looks good.


display-dependency-updates with processDependencyManagementTransitive = false ignores dependencyManagement in enabled profiles

When running display-dependency-updates with processDependencyManagementTransitive is disabled (i.e. false), dependencyManagement in enabled profiles is not checked for updates.

From what I see, this has never worked correctly since the introduction of processDependencyManagementTransitive.
Reproduced.


Cannot find on Obsidian Community Plugin list.

First thanks for your interest in my first little Obsidian plugin.
My pull request to add this plugin to the list of official community plugins is still in review and will hopefully be available soon.

Closed as it's not merged and listed


ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork.

All of my nodes died with a same error below at different transaction checkpoint.

Restart didn't work, so I wiped the whole data and started from the scratch. -> Now it works.

It seems like the data is corrupted. However, it's unusual for data to get corrupted like this. Do you know why this might be happening?

Here are the errors that occurred on different nodes below.

2023-04-04T16:37:46.143850Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(DbGSLoHEWxhC5CDaacTYvVBAA7WhfYPeDjWiHquLCqZr). Non-quorum effects: {TransactionEffectsDigest(3t1QX5WG8W9GogAC5zsMN7b7UUxF9Sj5WZG5Geiz9JF4): ([k#aa73f44eb9d4d2ee4396ecf563bf0f3a2d3753bd82e8d4fdfc05d6887804ab0cc8376263e304643f91c133354bfa5e970be6b60938bcd899034eef74e127b27441b2a20c6206a2284551036dc0ffb224a9c9d96f97f3a09d2dc5b98032245fdf], 42)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(DbGSLoHEWxhC5CDaacTYvVBAA7WhfYPeDjWiHquLCqZr). Non-quorum effects: {TransactionEffectsDigest(3t1QX5WG8W9GogAC5zsMN7b7UUxF9Sj5WZG5Geiz9JF4): ([k#aa73f44eb9d4d2ee4396ecf563bf0f3a2d3753bd82e8d4fdfc05d6887804ab0cc8376263e304643f91c133354bfa5e970be6b60938bcd899034eef74e127b27441b2a20c6206a2284551036dc0ffb224a9c9d96f97f3a09d2dc5b98032245fdf], 42)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

2023-04-04T19:46:56.055459Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(Cjxkcgw4xAhosQdXopKn9s5TtGs39uQBo87JAFaChQ2S). Non-quorum effects: {TransactionEffectsDigest(Em6R8wZzJuytEkXaDB7d9L1AVNdDJyvn8Fc2NApzdY9H): ([k#ab781b5ae9601318a07aa3571e3276d4b5000e162b13b330c97b5caf178873ceda08889bc27dcb8041c0ea9efc3c2cc7105ded7ef862a20180c75acf7570cfffd1708b70c337aedc4af8c8fe8caad19453e532042a2224f753e9232443e014e1, k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#94d322542b897222c9dbc1d7f5f057d66398c7146c25d48cccb1af91974103953575169d33b202a8ae90172c6382a13e04b12fd98412a644af21d656016f66d48391947d20bfb89a6ed9d5b15ca33c33f2b9787017d8ea50303eaa46cf50305e, k#99ba4edabd780dff8ee9f2783aed86ac5e036d38794c101a64f9979b728badf1c1d4bac1b92f7bd890c6a80774742e9e152ba5832b50cf06cb7f982a29556419bd85b51b441cdf06e99e2df4efacfa4f4cdb37008d53b9061feb749e880bad79, k#b310bc25db27d02a1ca8ead7ff8f43ecf4525d21286985d395b027a295976553a584e33e0767ab2aac674aa3d042a588138fdeeb8b0ccac70d53e3e8ca651dc7fc0e441db1ee72e9b676ae4f96f6f79d211cf6741be86403cdfa0cce15c04934], 490)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
thread 'tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(Cjxkcgw4xAhosQdXopKn9s5TtGs39uQBo87JAFaChQ2S). Non-quorum effects: {TransactionEffectsDigest(Em6R8wZzJuytEkXaDB7d9L1AVNdDJyvn8Fc2NApzdY9H): ([k#ab781b5ae9601318a07aa3571e3276d4b5000e162b13b330c97b5caf178873ceda08889bc27dcb8041c0ea9efc3c2cc7105ded7ef862a20180c75acf7570cfffd1708b70c337aedc4af8c8fe8caad19453e532042a2224f753e9232443e014e1, k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#94d322542b897222c9dbc1d7f5f057d66398c7146c25d48cccb1af91974103953575169d33b202a8ae90172c6382a13e04b12fd98412a644af21d656016f66d48391947d20bfb89a6ed9d5b15ca33c33f2b9787017d8ea50303eaa46cf50305e, k#99ba4edabd780dff8ee9f2783aed86ac5e036d38794c101a64f9979b728badf1c1d4bac1b92f7bd890c6a80774742e9e152ba5832b50cf06cb7f982a29556419bd85b51b441cdf06e99e2df4efacfa4f4cdb37008d53b9061feb749e880bad79, k#b310bc25db27d02a1ca8ead7ff8f43ecf4525d21286985d395b027a295976553a584e33e0767ab2aac674aa3d042a588138fdeeb8b0ccac70d53e3e8ca651dc7fc0e441db1ee72e9b676ae4f96f6f79d211cf6741be86403cdfa0cce15c04934], 490)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

2023-04-04T19:20:14.661006Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(2uiTFQfuT8sQt55BB3JUAYw9eHxLcSgnsRVaeog5kYmE). Non-quorum effects: {TransactionEffectsDigest(AnArud9FpkVMZQFQyUqWL3thftVtNPwczJU8WPXHAuX7): ([k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#84ddf75f5b98a8437d21c94132cd7f9c80063d06ac65e3c1e591979647ce477ba12d063c3aee7bbbdbbabc49e446cab816c8a6d193de5c13331b8fa549ac0c4c14ce4d147645785fce9d1ce70ad159ed29ca5d718ccfbbc138741689a38268cf], 96)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
thread 'tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(2uiTFQfuT8sQt55BB3JUAYw9eHxLcSgnsRVaeog5kYmE). Non-quorum effects: {TransactionEffectsDigest(AnArud9FpkVMZQFQyUqWL3thftVtNPwczJU8WPXHAuX7): ([k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#84ddf75f5b98a8437d21c94132cd7f9c80063d06ac65e3c1e591979647ce477ba12d063c3aee7bbbdbbabc49e446cab816c8a6d193de5c13331b8fa549ac0c4c14ce4d147645785fce9d1ce70ad159ed29ca5d718ccfbbc138741689a38268cf], 96)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

System Information

OS: Ubuntu 20.04
Compiler: rustc 1.68.0

It's difficult to say for sure what caused the error without more information, but it could be due to a number of different factors. Here are a few possibilities:

Hardware failure: Sometimes hardware can fail, leading to data corruption. If all of your nodes experienced the same error, this could be a possibility. You might want to check your hardware for issues, such as failing hard drives, faulty RAM, or overheating.
Network issues: If your nodes are communicating over a network, it's possible that there was a network issue that caused the corruption. For example, if there was a network outage or a switch malfunction, it could have caused data to be lost or corrupted.
Software bugs: It's possible that there was a bug in the software you're using that caused the error. If this is the case, you might want to check with the software vendor to see if there are any known issues or patches that could fix the problem.
Human error: It's also possible that the error was caused by human error, such as accidentally deleting or overwriting data.

In any case, since wiping the data and starting over seems to have resolved the issue, it's likely that the problem was related to the data itself, rather than the hardware or software. To avoid this problem in the future, you might want to consider implementing a backup and recovery plan, so that you can easily restore your data if something goes wrong. Additionally, you might want to consider implementing some kind of data integrity checking mechanism to catch any data corruption issues early on.
Windows için Postahttps://go.microsoft.com/fwlink/?LinkId=550986 ile gönderildi
Kimden: Jiwon @.>
Gönderilme: 5 Nisan 2023 Çarşamba 12:34
Kime: @.>
Bilgi: @.***>
Konu: [MystenLabs/sui] ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. (Issue #10424)

All of my nodes died with a same error below at different transaction checkpoint.
Restart didn't work, so I wiped the whole data and started from the scratch. -> Now it works.
It seems like the data is corrupted. However, it's unusual for data to get corrupted like this. Do you know why this might be happening?

2023-04-04T16:37:46.143850Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(DbGSLoHEWxhC5CDaacTYvVBAA7WhfYPeDjWiHquLCqZr). Non-quorum effects: {TransactionEffectsDigest(3t1QX5WG8W9GogAC5zsMN7b7UUxF9Sj5WZG5Geiz9JF4): ([k#aa73f44eb9d4d2ee4396ecf563bf0f3a2d3753bd82e8d4fdfc05d6887804ab0cc8376263e304643f91c133354bfa5e970be6b60938bcd899034eef74e127b27441b2a20c6206a2284551036dc0ffb224a9c9d96f97f3a09d2dc5b98032245fdf], 42)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(DbGSLoHEWxhC5CDaacTYvVBAA7WhfYPeDjWiHquLCqZr). Non-quorum effects: {TransactionEffectsDigest(3t1QX5WG8W9GogAC5zsMN7b7UUxF9Sj5WZG5Geiz9JF4): ([k#aa73f44eb9d4d2ee4396ecf563bf0f3a2d3753bd82e8d4fdfc05d6887804ab0cc8376263e304643f91c133354bfa5e970be6b60938bcd899034eef74e127b27441b2a20c6206a2284551036dc0ffb224a9c9d96f97f3a09d2dc5b98032245fdf], 42)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
2023-04-04T19:46:56.055459Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(Cjxkcgw4xAhosQdXopKn9s5TtGs39uQBo87JAFaChQ2S). Non-quorum effects: {TransactionEffectsDigest(Em6R8wZzJuytEkXaDB7d9L1AVNdDJyvn8Fc2NApzdY9H): ([k#ab781b5ae9601318a07aa3571e3276d4b5000e162b13b330c97b5caf178873ceda08889bc27dcb8041c0ea9efc3c2cc7105ded7ef862a20180c75acf7570cfffd1708b70c337aedc4af8c8fe8caad19453e532042a2224f753e9232443e014e1, k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#94d322542b897222c9dbc1d7f5f057d66398c7146c25d48cccb1af91974103953575169d33b202a8ae90172c6382a13e04b12fd98412a644af21d656016f66d48391947d20bfb89a6ed9d5b15ca33c33f2b9787017d8ea50303eaa46cf50305e, k#99ba4edabd780dff8ee9f2783aed86ac5e036d38794c101a64f9979b728badf1c1d4bac1b92f7bd890c6a80774742e9e152ba5832b50cf06cb7f982a29556419bd85b51b441cdf06e99e2df4efacfa4f4cdb37008d53b9061feb749e880bad79, k#b310bc25db27d02a1ca8ead7ff8f43ecf4525d21286985d395b027a295976553a584e33e0767ab2aac674aa3d042a588138fdeeb8b0ccac70d53e3e8ca651dc7fc0e441db1ee72e9b676ae4f96f6f79d211cf6741be86403cdfa0cce15c04934], 490)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
thread 'tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(Cjxkcgw4xAhosQdXopKn9s5TtGs39uQBo87JAFaChQ2S). Non-quorum effects: {TransactionEffectsDigest(Em6R8wZzJuytEkXaDB7d9L1AVNdDJyvn8Fc2NApzdY9H): ([k#ab781b5ae9601318a07aa3571e3276d4b5000e162b13b330c97b5caf178873ceda08889bc27dcb8041c0ea9efc3c2cc7105ded7ef862a20180c75acf7570cfffd1708b70c337aedc4af8c8fe8caad19453e532042a2224f753e9232443e014e1, k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#94d322542b897222c9dbc1d7f5f057d66398c7146c25d48cccb1af91974103953575169d33b202a8ae90172c6382a13e04b12fd98412a644af21d656016f66d48391947d20bfb89a6ed9d5b15ca33c33f2b9787017d8ea50303eaa46cf50305e, k#99ba4edabd780dff8ee9f2783aed86ac5e036d38794c101a64f9979b728badf1c1d4bac1b92f7bd890c6a80774742e9e152ba5832b50cf06cb7f982a29556419bd85b51b441cdf06e99e2df4efacfa4f4cdb37008d53b9061feb749e880bad79, k#b310bc25db27d02a1ca8ead7ff8f43ecf4525d21286985d395b027a295976553a584e33e0767ab2aac674aa3d042a588138fdeeb8b0ccac70d53e3e8ca651dc7fc0e441db1ee72e9b676ae4f96f6f79d211cf6741be86403cdfa0cce15c04934], 490)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
2023-04-04T19:20:14.661006Z ERROR telemetry_subscribers: panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(2uiTFQfuT8sQt55BB3JUAYw9eHxLcSgnsRVaeog5kYmE). Non-quorum effects: {TransactionEffectsDigest(AnArud9FpkVMZQFQyUqWL3thftVtNPwczJU8WPXHAuX7): ([k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#84ddf75f5b98a8437d21c94132cd7f9c80063d06ac65e3c1e591979647ce477ba12d063c3aee7bbbdbbabc49e446cab816c8a6d193de5c13331b8fa549ac0c4c14ce4d147645785fce9d1ce70ad159ed29ca5d718ccfbbc138741689a38268cf], 96)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17 panic.file="/root/temp/sui/crates/sui-core/src/authority_aggregator.rs" panic.line=1369 panic.column=17
thread 'tokio-runtime-worker' panicked at 'We have violated our safety assumption or there is a fork. Tx: TransactionDigest(2uiTFQfuT8sQt55BB3JUAYw9eHxLcSgnsRVaeog5kYmE). Non-quorum effects: {TransactionEffectsDigest(AnArud9FpkVMZQFQyUqWL3thftVtNPwczJU8WPXHAuX7): ([k#b7aa36227ca2601a673c83b21172e6586ecc725859aa52dcc2a34b50a963e4fed934bdbe2d3d23505bb090708aafa245124a4e3fa34dac6e010afd842416585b0d79861dc31b17793518d5258f65a24d89233df9cbd0cccae8f3b6458195f2d4, k#84ddf75f5b98a8437d21c94132cd7f9c80063d06ac65e3c1e591979647ce477ba12d063c3aee7bbbdbbabc49e446cab816c8a6d193de5c13331b8fa549ac0c4c14ce4d147645785fce9d1ce70ad159ed29ca5d718ccfbbc138741689a38268cf], 96)}.', /root/temp/sui/crates/sui-core/src/authority_aggregator.rs:1369:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
System Information

OS: Ubuntu 20.04
Compiler: rustc 1.68.0

—
Reply to this email directly, view it on GitHubhttps://github.com/MystenLabs/sui/issues/10424, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2RKOYCUQKZNQ2CJFUEPO6DW7U4AZANCNFSM6AAAAAAWT2KJKY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


feature:  提供 Agent 包管理后台接口 (closed #1683)

PR
CheckList（PR Assigners）
确认已完成以下操作：

[ ] 已将分支与当前合入分支同步
[ ] 已在关联 Issue 中补充「功能自测」部分内容
[ ] 已更新关联 Issue 的状态 backlog -> todo -> for test -> tested（需通过测试同学测试） -> done
[ ] 将 PR 添加上 pr/reviewable

CheckList（PR Reviewers）
确认已完成以下操作：

[ ] 检查关联 Issue 「功能自测」部分内容
[ ] 必要时打回 pr/reviewable，要求重新修改
[ ] 及时 Approve

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

Comparison is base (2a7ec66) 74.71% compared to head (1b0d11c) 74.70%.
Report is 2 commits behind head on feature/package_manage.

Files
Patch %
Lines

common/utils/drf_utils.py
53.74%
68 Missing :warning:

apps/node_man/views/package_manage.py
64.40%
21 Missing :warning:

...ackend/subscription/steps/agent_adapter/adapter.py
84.31%
8 Missing :warning:

apps/node_man/handlers/meta.py
25.00%
6 Missing :warning:

apps/node_man/serializers/package_manage.py
93.50%
5 Missing :warning:

apps/node_man/permissions/package_manage.py
72.72%
3 Missing :warning:

apps/node_man/serializers/job.py
66.66%
2 Missing :warning:

apps/node_man/utils/filters.py
85.71%
2 Missing :warning:

apps/backend/subscription/views.py
50.00%
1 Missing :warning:

Additional details and impacted files
@@                    Coverage Diff                     @@
##           feature/package_manage    #2052      +/-   ##
==========================================================
- Coverage                   74.71%   74.70%   -0.01%
==========================================================
  Files                         404      411       +7
  Lines                       28246    28698     +452
==========================================================
+ Hits                        21103    21439     +336
- Misses                       7143     7259     +116

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


Hide impossible district builds

If I have a city that has no lake or see anywhere within its workable tile range, it will never be able to build a harbour.  Similarly if I have a city with no flat ground that is not otherwise already occupied by a district or wonder, it will never be able to build an aerodrome.
That said, I like that a city that can't ever build a particular wonder shows that it is still available to be built somewhere.  I'd like that to still be visible.   (Hey, speaking of which, is there a list that shows what wonders are in what cities?  I vaguely remember seeing one but now can't find it.)

I'll see about adding this as an option, as for that list thing, I don't think one currently exists

This isn't trivial to implement and has a lot of potential for confusing people. I think I'm going to be axing this idea


Localization [Feature Request]

Hi there!
Thanks for building this gem!
Would it be possible to add the ability to use the "locale" option provided in FullCalendar?
Here is the link to the FullCalendar Docs:
https://fullcalendar.io/docs/text/locale/
It would be much appreciated!

Nevermind.
I found the locale-all.js file in your repo
Thanks!


212 refactor models folder

I have two questions about your decisions and thus some suggestions.
1. Why did you decide to keep the `utils` folder?

2. Since you created the `differentiable/flux` directory why you didn't create something similar for the `laplace_redux.jl` file? I had a similar discussion with Rauno about this categorization and maybe you can create another directory e.g., `differentiable/laplace_redux` or `differentiable/custom`? Thanks to that the `differentiable` folder would have a cleaner structure.

I think you mean utils.jl, not utils folder. I decided to keep it because I couldn't think of a good way to separate those functions that would be meaningful and not completely arbitrary.
a custom folder is undescriptive and if more models are created, then a more relevant structuring can be created. For now, it can stay there.

I have two questions about your decisions and thus some suggestions.
1. Why did you decide to keep the `utils` folder?

2. Since you created the `differentiable/flux` directory why you didn't create something similar for the `laplace_redux.jl` file? I had a similar discussion with Rauno about this categorization and maybe you can create another directory e.g., `differentiable/laplace_redux` or `differentiable/custom`? Thanks to that the `differentiable` folder would have a cleaner structure.

1. I think you mean `utils.jl`, not `utils` folder. I decided to keep it because I couldn't think of a good way to separate those functions that would be meaningful and not completely arbitrary.

2. a `custom` folder is undescriptive and if more models are created, then a more relevant structuring can be created. For now, it can stay there.

Yes, I meant utils.jl and after going through this file once again it makes sense to leave it the way it is.
I'd still create one of those folders to keep this stuff separate, I'd argue that leaving a random laplace_redux.jl file could be even more confusing and creating one more folder wouldn't hurt.


Total recovered cases are more than the confirmed cases.

Describe the bug
Recovered cases can not be more than confirmed cases.
To Reproduce

Go to 'https://www.covid19india.org/'
Click on 'Kerala'
Scroll down to 'Kozhikode'
See error

Expected behavior
Recovered cases should always be less than then confirmed cases.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This seems to be a duplicate of https://github.com/covid19india/covid19india-react/issues/1765

Duplicate of #1765


Adding deepEqual in utils to use as equalityFn in useSelector()

I needed to use a deep equal comparison in one project Im doing and I wrote it based on the shallowEqual from this lib. Just added a recursion to go deep in the nested objects.
I think it would be helpful to have this built in.
Here is a sample of the code:
  for (let i = 0; i < keysA.length; i++) {
    const value = keysA[i]

    if (!Object.prototype.hasOwnProperty.call(objB, value)) return false

    const valueA = objA[value]
    const valueB = objB[value]

    if (typeof valueA === 'object') {
      if (!deepEqual(valueA, valueB)) {
        return false
      }
    } else if (!is(valueA, valueB)) {
      return false
    }
  }

Do you guys thinks this is useful for the project?

Appreciate the suggestion, but I don't feel a need to include this.  Part of the reason we exposed shallowEqual was that we already had it in the codebase and used it.  Given that there's many other existing equality comparison implementations out there, there's not a good reason to add that when we don't use it ourselves.  Thanks anyway!


TouchBackend does not work at all?

Describe the bug
Because the HTML5Backend does not work in iOS 14 (as expected), I tried using the TouchBackend, but it also appears to not work.
Reproduction
https://codesandbox.io/s/laughing-kapitsa-yb0znj?file=/src/index.tsx
Steps to reproduce the behavior:
Visit the above sandbox link on a mobile device, try to drag.
(Note that switching the above example to the HTML5Backend will allow it to work in iOS 15)
Desktop (please complete the following information):

OS: iOS 14, iOS 15

HTML5Backend  does not work on mobile devices. You need to see react-dnd-multi-backend.
codesandbox

HTML5Backend does not work on mobile devices. You need to see react-dnd-multi-backend. codesandbox

multibackend does not work either, at least on chrome android


When loading the object's size before the object's position , the position seems go off the screen

If I move the object towards the top left hand side and save it and open it up again, it is fine. however when I suddenly change the size of the object, and save and reopen again, the shape goes off the screen, even though the value of the position is the same. It seems like 5.9 on the y axis is something different if I load the size and the size is different from the default.
Have a look at the gif:

Changing the size back to its original size, saving it and reopening it puts the shape back to its original place.

@rustylabs have this been resolved on the pull requests I've made, or is it still an issue?

Fixed a little while ago


How to align map with Google Earth

Hi:
Thank you for sharing your work!
I've noticed that in your paper you align the map with Google Earth like the following figure, could you tell me how to do that?

@Tompson11
I used PowerPoint for that.

@TixiaoShan
Thank you for your reply! So It's just the alignment of 2D images instead of 3D models?

Yes.

Got it, thank you!

@Tompson11
Hello. May I ask if you have successfully achieved the effect of this map display? If it is convenient, I hope you can share your specific operation. Thank you so much!

@Tompson11 Hello. May I ask if you have successfully achieved the effect of this map display? If it is convenient, I hope you can share your specific operation. Thank you so much!

Sorry, I haven't tried yet. 😂

have you tried rviz_satellite?


Prepare release 0.6.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: sandorkertesz:x: iainrussellYou have signed the CLA already but the status is still pending? Let us recheck it.


Testing the new support bot

This issue should be automatically closed if you add a support label:
https://github.com/jupyterhub/.github/pull/1

It's still open 😞

@GeorgianaElena Can you check the bot?

@manics, I just sent a request to enable it for three repos in the jupyterhub organization:

binderhub
jupyterhub
the-littlest-jupyterhub

Not sure how or if I have the right permissions to accept the request. This is how it looks like:

Oh OK, I though it was added to all repos automatically.

It can be added to all the repos (there was a checkbox there) but I just thought we should see how it goes for these three repos first and then extend it to the others.
Either way, I believe it has to be accepted from the jupyterhub account for it to work.

Let's keep just those three for now then? I've added an item to the team meeting agenda https://github.com/jupyterhub/team-compass/issues/273
Please feel free to add to it 😀

Boom! Now that the robot has been installed it is onto us :)

Reopening this issue to test yet again :-)

nice - label gets auto-removed

🤩


5 checkpoint file limitation

Hi, all.
When I using this code to train my model, I find a weird problem about the checkpoint. I save the model every 20 epoch and after 200 epoch, I only find 5 model files. For example, when the training is run and I have got the model data for epoch 9,19,29,39,49. After epoch 59 is done, I will get model data for epoch 59 but the data for epoch 9 is missing. It seems that there is a limitation that I can only save 5 model data. I read the code several times but I can not find where the limitation lies.
I only use tensorflow for only a short time so I'm not sure whether it is limited by tensorflow itself. Thank you for your answering.

@BestJuly, This issue is related to Tensorflow tf.train.Saver()
In the model.py#L143 line you change like this:
self.saver = tf.train.Saver(max_to_keep=5)
Default value of checkpoint to keep is 5, you can change this value.
Reference: https://www.tensorflow.org/api_docs/python/tf/train/Saver

@asispatra Thank you very much. It seems that I need to read the official document and learn more details about the tensorflow.


Kotlin 1.3.71

This should be merged when #824 is merged and nuget Xamarin.Kotlin.BindingSupport version 0.7.0-preview is published

I think this is a good time as any to see if we can drop the kotlin binding support nuget and use the new generator. Need to check which version of VS has it...

@mattleibow did you start with this? do you want me to checkout?
Here is docs

Hey there @antonioseric! You can go right ahead. Sorry for taking months to get back to you.

@mattleibow i remove Xamarin.Kotlin.BindingSupport now it is buildin tooling. Can we also release 1.3.61 version?

@antonioseric I updated the 1.3.61 version in master to use the new tooling before I release. Do you have some real-world app/library that can test it out?
https://github.com/xamarin/XamarinComponents/pull/964
EDIT
I just see that you also did the same to your PR. I'll merge mine then and release since the changes are the same. Have you tested your packages and confirm they work as expected?

Could you please also add support for Kotlin 1.4.0?

@4brunu could you open an new issue so we can track this?
I'd like to keep this PR for the last v1.3.x

Sorry, I opened https://github.com/xamarin/XamarinComponents/issues/965.

Thanks! I'll have a look and see what it takes to get that out soon. Unless @antonioseric already started on that?

@antonioseric thanks for the work on this and the other PRs. I have merged this and once CI is done, a release will go out 😄


[AutoDiff] Not checkpoint inactive values from the original function

Teach AD not to checkpoint inactive values from the original function.
Refactor activity analysis lookup to produce an option set.

Resolves SR-8685.

@swift-ci please test tensorflow