Corrupt serialized resolution result/Problems reading from Binary store when executing dependencies tasks or build scans

When executing ./gradlew dependencies --write-locks, the build fails with this error:
integrationStubImplementation - Implementation only dependencies for compilation 'integrationStub' (target  (jvm)).

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':dependencies'.
> Could not resolve all dependencies for configuration ':integrationStubImplementation'.
   > Problems reading data from Binary store in /tmp/gradle15135648821751580614.bin offset 221374 exists? true

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.6/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 3s
1 actionable task: 1 executed

When attempting to generate ./gradlew dependencies --scan, I receive this output:

> Task :dependencies FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':dependencies'.
> Could not resolve all dependencies for configuration ':integrationStubImplementation'.
   > Problems reading data from Binary store in /tmp/gradle13858920095948672727.bin offset 261444 exists? true

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.6/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 31s
1 actionable task: 1 executed

A build scan cannot be produced as an error occurred gathering build data.
Please report this problem via https://gradle.com/help/plugin and include the following via copy/paste:

----------
Gradle version: 6.6
Plugin version: 3.4

org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ':integrationStubImplementation'.
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.wrapException(ErrorHandlingConfigurationResolver.java:104)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.access$000(ErrorHandlingConfigurationResolver.java:48)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:203)
        at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:116)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:70)
        at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:149)
        at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:135)
        at com.gradle.scan.plugin.internal.j.a.f.a(SourceFile:12)
        at com.gradle.scan.plugin.internal.j.a$c.finished(SourceFile:154)
        at com.gradle.scan.plugin.internal.j.a.a(SourceFile:65)
        at com.gradle.scan.plugin.internal.j.k.a(SourceFile:58)
        at com.gradle.scan.plugin.internal.j.c.a(SourceFile:103)
        at com.gradle.scan.plugin.internal.j.g.a(SourceFile:48)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
        at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.RuntimeException: Problems reading data from Binary store in /tmp/gradle13858920095948672727.bin offset 261444 exists? true
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:132)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.lambda$create$0(StreamingResolutionResultBuilder.java:187)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory$SimpleStore.load(CachedStoreFactory.java:101)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:185)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:157)
        at org.gradle.api.internal.artifacts.result.DefaultResolutionResult.getRoot(DefaultResolutionResult.java:48)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:201)
        at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:116)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:70)
        at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:149)
        at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:135)
        at com.gradle.scan.plugin.internal.j.a.f.a(SourceFile:12)
        at com.gradle.scan.plugin.internal.j.a$c.finished(SourceFile:154)
        at com.gradle.scan.plugin.internal.j.a.a(SourceFile:65)
        at com.gradle.scan.plugin.internal.j.k.a(SourceFile:58)
        at com.gradle.scan.plugin.internal.j.c.a(SourceFile:103)
        at com.gradle.scan.plugin.internal.j.g.a(SourceFile:48)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
        at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected module (889) for constraint integrationStubImplementation -> com.vmware.carbonblackcloud:exekute:1.0.0
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.DefaultResolutionResultBuilder.visitOutgoingEdges(DefaultResolutionResultBuilder.java:82)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:237)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:130)
        ... 21 more
----------

Could this be a weird local dependency problem?
Also, I did successfully run  ./gradlew classes --update-locks com.vmware.carbonblackcloud:exekute. So I'm not 100% sure if that's just a red herring here or not.
Expected Behavior
I would like for all of my dependencies to resolve, basically, or flag an actionable error that indicates what is the problem on my end.
Current Behavior
See the above output, it's pretty much "I can't update my lockfiles using the global command".
Context
We're using version locking, and I have several libraries I'm using, and I want to update all dependencies, to look for updates, typically to the AWS library.
Steps to Reproduce
This is challenging, because it's in a project with a whole bunch of company IP. And I can't provide a build scan for this task since that part fails, though I'm game for adding any other tasks, debugging, etc., though I bet the debug output would be ok.
Your Environment
Linux (Ubuntu 18.04), using JDK 14.0.2, and Gradle 6.6.

This morning, I actually removed that internal project, exekute that was listed in the build scan output, and removed some kotlin dependencies from the project. The scan still fails, but with a publicly available POM:
BUILD FAILED in 28s
1 actionable task: 1 executed

A build scan cannot be produced as an error occurred gathering build data.
Please report this problem via https://gradle.com/help/plugin and include the following via copy/paste:

----------
Gradle version: 6.6
Plugin version: 3.4

org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ':integrationStubImplementation'.
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.wrapException(ErrorHandlingConfigurationResolver.java:104)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.access$000(ErrorHandlingConfigurationResolver.java:48)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:203)
        at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:116)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:70)
        at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:149)
        at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:135)
        at com.gradle.scan.plugin.internal.j.a.f.a(SourceFile:12)
        at com.gradle.scan.plugin.internal.j.a$c.finished(SourceFile:154)
        at com.gradle.scan.plugin.internal.j.a.a(SourceFile:65)
        at com.gradle.scan.plugin.internal.j.k.a(SourceFile:58)
        at com.gradle.scan.plugin.internal.j.c.a(SourceFile:103)
        at com.gradle.scan.plugin.internal.j.g.a(SourceFile:48)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
        at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.RuntimeException: Problems reading data from Binary store in /tmp/gradle1615510607535013790.bin offset 220456 exists? true
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:132)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.lambda$create$0(StreamingResolutionResultBuilder.java:187)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory$SimpleStore.load(CachedStoreFactory.java:101)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:185)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:157)
        at org.gradle.api.internal.artifacts.result.DefaultResolutionResult.getRoot(DefaultResolutionResult.java:48)
        at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:201)
        at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:116)
        at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:70)
        at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:149)
        at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:135)
        at com.gradle.scan.plugin.internal.j.a.f.a(SourceFile:12)
        at com.gradle.scan.plugin.internal.j.a$c.finished(SourceFile:154)
        at com.gradle.scan.plugin.internal.j.a.a(SourceFile:65)
        at com.gradle.scan.plugin.internal.j.k.a(SourceFile:58)
        at com.gradle.scan.plugin.internal.j.c.a(SourceFile:103)
        at com.gradle.scan.plugin.internal.j.g.a(SourceFile:48)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
        at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected module (1650) for constraint platform-runtime -> com.rabbitmq:amqp-client:5.9.0
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.DefaultResolutionResultBuilder.visitOutgoingEdges(DefaultResolutionResultBuilder.java:82)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:237)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:130)
        ... 21 more
----------

I'm still zeroing in on what triggers this. I think it may be a platform dependency in a custom source set.

I've only ironed out that it only occurs when the --write-locks option is enabled for the dependencies task. I've had to disable version locking, and everything resolves now.

Today I went through, and eventually figured out there were three transitive dependencies that had to be declared as implementation dependencies in the main source set, and that bypassed the resolution problems. I can't for the life of me, understand what these had to do with anything, I suspect it's just a hidden timing issue.
It makes no sense otherwise that these dependencies would have caused any particular harm:
implementation("com.rabbitmq:amqp-client:5.9.0")
implementation("net.bytebuddy:byte-buddy-agent:1.10.13")
implementation("commons-logging:commons-logging:1.1.3")

I'll also note: we are using an internal artifactory server to both cache maven central deps (and where we host internal projects). I'm not seeing anything weird with it, so I really am not sure if it's somehow also causing issues.

Thanks for the report and attempts at reproducing.
These issues are usually caused by corner cases in the dependency graph computation. That's why changing declaration order or adding / removing dependencies can make the problem go away.
Unfortunately, these issues are hard to track without an isolated reproducer.
#14229 fixes such a corner case. Once a nightly with the fix is available, I'll ask you to test it to see if it fixes this issue.

Can you try with a nightly and let us know how it goes?
https://gradle.org/nightly/

No, unfortunately it still had a problem:
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected module (1345) for constraint platform-runtime -> com.rabbitmq:amqp-client:5.9.0
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.DefaultResolutionResultBuilder.visitOutgoingEdges(DefaultResolutionResultBuilder.java:83)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:238)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:130)
        ... 113 more

This was using this version:
$ ./gradlew --version

------------------------------------------------------------
Gradle 6.7-20200824220048+0000
------------------------------------------------------------

Build time:   2020-08-24 22:00:48 UTC
Revision:     1c64c1d968445857daf8b3d630f22d20b938fce8

Kotlin:       1.3.72
Groovy:       2.5.12
Ant:          Apache Ant(TM) version 1.10.8 compiled on May 10 2020
JVM:          14.0.2 (Oracle Corporation 14.0.2+12-46)
OS:           Linux 5.4.0-42-generic amd64

Unfortunately we can't figure out what's going on without a reproducer, as it's a particularly difficult thing to debug. We'd appreciate if you can trip down your project/anonymize to a minimal reproducer.

Unfortunately, we have a lot of internal dependencies here (with different build approaches, etc), and figuring out a reproduction case wasn't getting anywhere quickly.
What I may end up doing is learning how to actually build/debug Gradle itself, so I can just locally debug this. But that's not exactly my highest priority, so I can't you when I'd get around to this.
Basically, I think it's probably valid to just say "can't reproduce" and close this issue. If I actually am able to figure out what's going on, I'll re-open it with reproduction details, or reference a new ticket with a reproduction case.

I just had the same problem but with org.postgresql:postgresql. I added an explicit implementation dependency and that fixed things, very weird

@shmish111 Any chance that you are using replacement rules?
We are about to fix an issue for Gradle 7.3 rooted in replacement rules that ends up causing this kind of problems.
See #18079

Not that I'm aware of but I will try to remember to try this out once that is released.

Gradle 7.3 RC1 is out already, could you check with that version?

Having this problem even with 7.3.1

`----------
Gradle version: 6.9.2
Plugin version: 3.7.1
org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ':ads-engagement-summary-report-job-azkaban_2.11:compileClasspath'.
at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.wrapException(ErrorHandlingConfigurationResolver.java:106)
at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.access$000(ErrorHandlingConfigurationResolver.java:49)
at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:215)
at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:113)
at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:66)
at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:47)
at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:147)
at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:137)
at com.gradle.scan.plugin.internal.l.a.f.a(SourceFile:12)
at com.gradle.scan.plugin.internal.l.a$c.finished(SourceFile:154)
at com.gradle.scan.plugin.internal.l.a.a(SourceFile:65)
at com.gradle.scan.plugin.internal.l.l.a(SourceFile:58)
at com.gradle.scan.plugin.internal.l.c.a(SourceFile:98)
at com.gradle.scan.plugin.internal.l.g.a(SourceFile:51)
at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.RuntimeException: Problems reading data from Binary store in /private/var/folders/ft/b5jkwn010tj3llqw2ljgx1h0001dc1/T/gradle6382969199485670936.bin offset 682978 exists? true
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:132)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.lambda$create$0(StreamingResolutionResultBuilder.java:189)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory$SimpleStore.load(CachedStoreFactory.java:101)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:187)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:159)
at org.gradle.api.internal.artifacts.result.DefaultResolutionResult.getRoot(DefaultResolutionResult.java:48)
at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver$ErrorHandlingResolutionResult.getRoot(ErrorHandlingConfigurationResolver.java:213)
at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:59)
at com.gradle.scan.plugin.internal.b.f.a.h$a.b(SourceFile:113)
at com.gradle.scan.plugin.internal.b.f.a.h$a.a(SourceFile:66)
at com.gradle.scan.plugin.internal.b.f.a.h.a(SourceFile:47)
at com.gradle.scan.plugin.internal.b.f.a.g.a(SourceFile:147)
at com.gradle.scan.plugin.internal.b.f.c.a(SourceFile:137)
at com.gradle.scan.plugin.internal.l.a.f.a(SourceFile:12)
at com.gradle.scan.plugin.internal.l.a$c.finished(SourceFile:154)
at com.gradle.scan.plugin.internal.l.a.a(SourceFile:65)
at com.gradle.scan.plugin.internal.l.l.a(SourceFile:58)
at com.gradle.scan.plugin.internal.l.c.a(SourceFile:98)
at com.gradle.scan.plugin.internal.l.g.a(SourceFile:51)
at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected module (2241) for default -> com.linkedin.container-core:container-ic-impl:1.2.14
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.DefaultResolutionResultBuilder.visitOutgoingEdges(DefaultResolutionResultBuilder.java:83)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:239)
at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:130)
... 21 more
`
Cannot do a successful build anymore after this.

I have the same problem

Here is a reproducer for the problem in an error case when dynamic versions are involved.
reproducer-14220.zip
In the attached example:

Run gradle resolveArtifacts to get a proper error:

Execution failed for task ':resolveArtifacts'.
> Could not resolve all files for configuration ':implementation'.
   > Could not find any version that matches test:module1:11.2.0.+.
     Versions that do not match: <IP_ADDRESS>
     Searched in the following locations:
       - file:/C:/SPU/pwe/tkeasy/default/git-repos/gradle-plugins/reproducer-14220/repo/test/module1/maven-metadata.xml
     Required by:
         project :

Run gradle dependencies, or any build with --scan, and you get

> Could not resolve all dependencies for configuration ':implementation'.
   > Problems reading data from Binary store in .gradle\.tmp\gradle2620150027837008206.bin offset 0 exists? true
...
  Corrupt serialized resolution result. Cannot find selected module (8) for constraint runtimeElements -> test:module1:<IP_ADDRESS>

This is also a problem if you write tasks that take resolution results with errors as input (using configuration.getIncoming().getResolutionResult().getRootComponent() as task input). Instead of getting a proper result to  inspect the error, the build fails.
A workaround to at least keep the build working (with an empty resolution result though) is to use the following as task input:
project.provider(() -> {
  try {
    return configuration.getIncoming().getResolutionResult().getRootComponent().get();
  } catch (ResolveException e) {
    project.getLogger().lifecycle("Bug https://github.com/gradle/gradle/issues/14220");
    project.getLogger().lifecycle(e.getCause().getCause().getMessage());
    // empty result
    return project.getConfigurations().detachedConfiguration().getIncoming().getResolutionResult().getRootComponent().get();
  }
});

Another reproducer, this time for a successful resolution:

clone https://github.com/jjohannes/java-ecosystem-capabilities
cd samples/sample-all
gradle dependencies -s -> build successful
Do this change in samples/sample-all/build.gradle.kts (moves dependency up) - https://github.com/jjohannes/java-ecosystem-capabilities/commit/89f2ba222f8a845ad94d78826eba4a5eea76deb9
gradle dependencies -s -> ERROR  Corrupt serialized resolution result. Cannot find selected module (101) for compile -> jakarta.activation:jakarta.activation-api:2.1.0

We had this issue trigger because of the following dependency substitution rule:
module("org.hamcrest:hamcrest-core") {
    replacedBy("org.hamcrest:hamcrest", "`hamcrest-core` migrated to `hamcrest`")
}

Due to the project's upgrade strategy using shim jars (see https://hamcrest.org/JavaHamcrest/distributables#previous-versions-of-hamcrest), hamcrest-core now depends on hamcrest.
It seems using replacement rules triggers corruption of the serialised dependency graph in this case.

Follow up to my previous comment: After adding even more capability rules and dependencies to the sample in https://github.com/jjohannes/java-ecosystem-capabilities , I can trigger this in more than one way there now (for resolutions that should succeed). Also, in the resolution result, certain entries are missing. Usually, the result should show at least all direct dependencies and what they are substituted with.
Reproducer:

clone https://github.com/jjohannes/java-ecosystem-capabilities
cd samples/sample-all
gradle dependencies --scan
Inspect dependency report or build scan. Entry for org.bouncycastle:bcprov-jdk18on:1.71, and other org.bouncycastle:bcprov-* dependencies, are missing. Although they are declared as direct dependency in the build.gradle.kts

This is an artificial example that would not exist like this in a real build. Still the result should not be this incomplete and this might be an indication that too much information is discarded during resolution.
This is with Gradle 8.0 RC2

I experienced a similar issue in a multi-module project, with the capabilities of the Java Ecosystem Capabilities plugin activated together with an extra (own) Hibernate capability.
To reproduce:

Clone https://github.com/kmoens/gradle-corrupt-serialization-issue-14220
Run ./gradlew module-a:dependencies

For me the problem was that a custom build plugin dependency pulled in an apparently JEE-only library, namely  jakarta.activation:jakarta.activation-api. After I removed this specifically from the build plugin via exclude, the issue vanished.

It seems there are a number of different issues in this thread (and related threads). There are several ways to get to a corrupt serialized resolution result. This error just means there was some bug in resolution. Furthermore, some of the errors don't produce corrupt results, but instead produce either missing dependencies, fail to detect capability conflicts, or silently fail in other ways.
I am currently working on a PR that consolidates all of the reported reproducers into Gradle integration tests -- and making them as minimal as possible. This is the first step to discovering the issue(s) we have to solve.
@jjohannes Your first issue seems easy to reproduce and seems to have a relatively easy fix. This seems unrelated to the later reproducers.
@jjohannes I've managed to reduce your second reproducer to a minimal reproducer. Minimal reproducers are much more helpful for debugging these issues. This is included in the above-noted PR.
@jjohannes I am having trouble reproducing your third reproducer. Would you be able to put together a reproducer showing the missing first-level dependencies in the resolution result? (The bouncycastle one)
@kmoens I tried reproducing your issue, but I cannot resolve your settings script.
Please provide a standalone reproducer that does not apply a script from a remote URL.
This is indeed a problem that we need to fix. We should not have reliability/correctness issues in the Gradle resolution engine. However, this issue is related to incredibly complicated code in the resolution engine. It may be very difficult to both track down and fix. These bugs in capability conflict resolution were likely present since the introduction of the feature.

Thank you for looking into this @jvandort. I stripped down the disappearing dependencies reproducer to the following. I think this has something to do with the combination of version upgrades and capabilities. It actually reproduces two (probably related) problems:

If you keep implementation("org.bouncycastle:bcprov-jdk14:1.70") you get the disappearing nodes
(https://scans.gradle.com/s/bevefyii5imiq/dependencies?toggled=W1swXSxbMCwwXV0)
If you remove that line, you get a capability conflict between two versions of the same (!) module which should not be possible:
Cannot select module with conflict on capability 'org.bouncycastle:bcprov-jdk18on:1.72' also provided by [org.bouncycastle:bcprov-jdk18on:1.71(runtime)]
(https://scans.gradle.com/s/4q6sisa23lbni/dependencies?toggled=W1swXSxbMCwwXV0)

Reproducer build.gradle.kts
plugins {
    id("java-library")
}

dependencies.components {
    listOf("bcprov-jdk14", "bcprov-jdk18on").forEach {
        withModule("org.bouncycastle:$it") { allVariants { withCapabilities { addCapability("foo", "bcprov", id.version) }}}
    }
    listOf("bctls-fips", "bctls-jdk14", "bctls-jdk18on").forEach {
        withModule("org.bouncycastle:$it") { allVariants { withCapabilities { addCapability("foo", "bctls", id.version) }}}
    }
}

configurations.all {
    resolutionStrategy.capabilitiesResolution {
        withCapability("foo:bcprov") { selectHighestVersion() }
        withCapability("foo:bctls") { selectHighestVersion() }
    }
}

dependencies {
    implementation("org.bouncycastle:bcprov-jdk14:1.70") // keep for nodes disappearing / remove for weird conflict error
    implementation("org.bouncycastle:bcprov-jdk18on:1.71")
    implementation("org.bouncycastle:bctls-fips:1.0.9")
    implementation("org.bouncycastle:bctls-jdk14:1.70")
    implementation("org.bouncycastle:bctls-jdk18on:1.72")
}

Hey thanks for listing a bunch of repros
I think here's another one in case it's interesting: https://github.com/gradle/gradle/issues/26145#issuecomment-1957776331

@mathjeff Yeah I think I’ve got that one in the PR. Ideally we’d be able to simplify this reproducer enough to not need to apply the android plugin.

@jvandort
The reproducer is back available. I made a wrong commit there which caused it to become unusable, this is now reverted and it is back in the original state: i.e. the reproducer for this issue.

gradle-problems-reading-binary-store also reproduces the problem. There, the problem disappears by switching the order of the only two dependencies declared in the build.gradle.

Any ideas about things that users might be able to do to help out with this?

I'm facing an issue while working on converting the AndroidX library lifecycle-viewmodel-compose to Kotlin Multiplatform. The problem appears to be related to the library being KMP, with the Android source set depending on livedata-core (Java).
For reference, here are the AOSP changes:

CLs: vm-compose-kmp
Reverted CLs: revert-vm-compose-kmp

We think we found a workaround in the case of the previous comment, which is to explicitly add a transitive dependency to the androidMain sourceset from the project encountering the error (:lifecycle:lifecycle-viewmodel-compose) to the project providing the artifact that failed to resolve (:lifecycle:lifecycle-livedata-core).
Also interesting, if we instead add the transitive dependency to the commonMain sourceset instead, then we get a resolution ambiguity error

Thank you all for your patience on this issue. We have been working hard on these reported problems, many of which are quite complex and trigger edge cases in the resolution engine.
We have a PR, https://github.com/gradle/gradle/pull/29853, which should resolve a number of the problematic builds reported in this thread. Unfortunately, since the corrupt resolution result error message is a symptom and not a problem itself, this message can appear as a result of different bugs. The linked PR does not solve all the problems reported here.
We will continue to work through the reproducers submitted here until there are no outstanding issues that cause corrupt graphs. Correctness and stability are a very high priority for Gradle, and we intend to ensure these issues are resolved.

@marcellogalhardo it seems both links you posted require internal google sign-on
@mathjeff Is this the same underlying issue as https://github.com/gradle/gradle/issues/26145#issuecomment-1957776331?

I think this is the same as https://github.com/gradle/gradle/issues/26145#issuecomment-1957776331, yeah.
Thanks!

Unfortunately the above linked PR has been reverted due to a regression it introduced. The fix will not be included with Gradle 8.10. We will work to include the change in 8.11

We are once again introducing the bugfix in 8.11 with https://github.com/gradle/gradle/pull/30363

I am getting the same error after upgrading to latest gradle version 8.11.1. Let me know if there is any other details I can provide:
Internal error in Develocity Gradle plugin: finished notification
com.gradle.develocity.DevelocityException: Internal error in Develocity Gradle plugin: finished notification
        at com.gradle.develocity.DevelocityException.a(SourceFile:25)
        at com.gradle.scan.plugin.internal.operations.d.a(SourceFile:138)
        at com.gradle.scan.plugin.internal.operations.h.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:31)
        at com.gradle.scan.plugin.internal.q.a$a.a(SourceFile:20)
        at com.gradle.scan.plugin.internal.q.a.c(SourceFile:67)
        at java.base@17.0.13/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.RuntimeException: Problems reading data from Binary store in /Users/crogoz/.gradle/.tmp/gradle14438152719818265448.bin offset 5535372 exists? true
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:137)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.lambda$create$0(StreamingResolutionResultBuilder.java:184)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory$SimpleStore.load(CachedStoreFactory.java:101)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.create(StreamingResolutionResultBuilder.java:182)
        at org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationResult.getRootComponent(ResolveConfigurationResolutionBuildOperationResult.java:60)
        at java.base/java.util.Optional.map(Optional.java:260)
        at com.gradle.scan.plugin.internal.c.i.a.e$a.b(SourceFile:115)
        at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:72)
        at com.gradle.scan.plugin.internal.c.i.a.e.a(SourceFile:51)
        at com.gradle.scan.plugin.internal.c.i.a.d.a(SourceFile:232)
        at com.gradle.scan.plugin.internal.c.i.c.lambda$attach$2(SourceFile:138)
        at com.gradle.scan.plugin.internal.operations.b$c.finished(SourceFile:154)
        at com.gradle.scan.plugin.internal.operations.b.a(SourceFile:65)
        at com.gradle.scan.plugin.internal.operations.n.a(SourceFile:56)
        at com.gradle.scan.plugin.internal.operations.d.a(SourceFile:136)
        ... 5 more
Caused by: java.lang.RuntimeException: Problems loading the resolution results (0.001 secs). Read 2810 values, last was: 5
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:239)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.DefaultBinaryStore$SimpleBinaryData.read(DefaultBinaryStore.java:135)
        ... 19 more
Caused by: java.lang.IllegalStateException: Corrupt serialized resolution result. Cannot find selected component (346934) for constraint runtimeElements -> <placeholder_groupName>:<placeholder_name>:<version>
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.ResolutionResultGraphBuilder.visitOutgoingEdges(ResolutionResultGraphBuilder.java:144)
        at org.gradle.api.internal.artifacts.ivyservice.resolveengine.result.StreamingResolutionResultBuilder$RootFactory.deserialize(StreamingResolutionResultBuilder.java:231)
        ... 20 more

A build scan cannot be produced as an error occurred gathering build data.
Please report this problem via https://gradle.com/help and include the following via copy/paste:

----------
Gradle version: 8.11.1
Plugin version: 3.18

@crogoz can you provide a reproducer?
Also what happens if you try the 8.12 nightly? We implemented a fix in 8.12 that resolves this bug in some cases

thanks for the quick reply! I tried now on the nightly version: gradle-8.12-20241210012659+0000-bin and I can still see the error.
I'll try to get a reproducer for you, this is one of the complicated repos with a lot of dependencies.


My first Rust post!

Please add this post:
Post URL: https://amanjeev.com/blog/rust-document-macro-invocations/
Blog Homepage: https://amanjeev.com/blog/
Author Name: Amanjeev Sethi
Categories: one or more of: Getting Started, Language,
Optional:
Blog RSS/Atom/JSON Feed: https://amanjeev.com/atom.xml
Providing a feed will help with discovering new posts in the future.

Thank you! Sorry for taking so long to publish your post.


heading containing ahsan  in dark mode  mob view fixed

@usman008 closing due to no activity.
Please raise a new PR with the fix if you're still interested 🙂


Adjust modulefile according to the latest requirements

Description
The PR aims to address issues with the modulefile discovered within the latest test sessions.

/intelci: run

@mergify backport rls/2024.6.0-rls


Swith HTTP client from HTTParty to Faraday

I realized that HTTParty is making requests with Content-Type: x-www-form-urlencoded rather than Content-Type: application/json, and this bothers me.
I also realized that the "User-Agent" for requests made by HTTParty is just "Ruby", which is also a bit lame (very generic).
I also realized that we are already requiring faraday implicitly as a dependency of oauth2.
Faraday didn't end up working out quite as well as I would have liked, but at the end of the day I think it's a bit of an improvement.

Because we are posting to the Travis build log as JSON now (rather than x-www-form-urlencoded), we see that the data param is correctly being provided/parsed as a number now.
Before

After


Update graylog.replicas customization example

What this PR does / why we need it:
Fixes incorrect example command in graylog helm chart.

/assign @kongz

@inthecloud247 please bump chart version

@KongZ bump'd

going to close this and open a clean PR

looks like my change was already merged in a diff PR, so this is unnecessary.


cannot parse stem inside param

cannot parse
其中，stem[R] 为关系名

The problem is a unicode problem. It need a external scanner?
the leading char for a inline_macro can be any [^a-zA-Z]


Update Azure links

Addresses Part 4 of #2580

@mairaw Ah ... yes ... np. These were all handled by script, and another little script will do the job. I'll take care of it. :cake:

@mairaw Script only found four lines in four files with this. Did I catch all of them looking for ...
azure.microsoft.com/documentation/services

There are still a couple left such as https://azure.microsoft.com/documentation/articles/websites-webjobs-resources/

I see. I only checked with a "services" segment ... I didn't address an "articles" segment. I'll get that on the next pass.

@mairaw I've added relative links as an action item on the main issue: https://github.com/dotnet/docs/issues/2580. I'll do those on a new PR after these go in.

@GuardRex do you mean changing the docs.microsoft.com links to /azure? If so, these are ok like this because they're part of the microservices book. if we change them to relative links, then they can't use that as a source for a new edition as-is.


Updating fork from original

Automated message from Dropbox CLA bot
@GedLawrenson, it looks like you've already signed the Dropbox CLA. Thanks!

Sorry - please ignore.


Makefile: allow installation of debug binaries

Distro packaging needs unstripped binaries to create its debuginfo
packages.
Signed-off-by: Lokesh Mandvekar<EMAIL_ADDRESS>@flouthoc @mheon @baude @Luap99 PTAL

@cevich will this cause any trouble in CI?

The release binary is still contains all the debug info AFAIK. If I run strip on the release binary it shrinks by almost 50% so I would think it is not striped by rust. Do you have any source why you would need the debug binary?

will this cause any trouble in CI?

I don't think so, and especially not if you're talking about RPMs.  RN all operations are using builds from the CI system - given how much churn there is here and in aardvark.  We can/should move downstream CI to use packages only after the churn dies down, and packages have been released in "the wild" for a little bit (few weeks).  Otherwise downstream testing will suffer from the delay in waiting for packages to build (it's also another point of potential failure/flakes).
More you your question though...CI is currently archiving both the "normal" binary and a separate .debug binary.  So if the "normal" binary is stripped, it's probably fine.  If downstream debugging is needed, there's a way it can be told to switch to using the .debug binary.  So we're all set there I think, so long as both are produced.
HTH

The release binary is still contains all the debug info AFAIK. If I run strip on the release binary it shrinks by almost 50% so I would think it is not striped by rust. Do you have any source why you would need the debug binary?

Ack. rpmbuild refused to generate debuginfo package for me with --release, while it worked with debug. Anyway, let me get back on this. There's another lingering issue that's causing koji builds to fail though it works locally.

@lsm5 LGTM but i guess we are waiting for you to confirm @Luap99 's  doubt right.  Same goes for : https://github.com/containers/aardvark-dns/pull/44

Thanks all. I tried with and without debug flag. Only thing that comes to mind is that rpmbuild isn't able to strip the release binary. And, stripping the debug binary only reduces size from 91M to 16M which isn't right for shipping in rpms anyway. I'm gonna close this and the aardvark PR.


Fix outdated links

Two project file references found, I converted them to schema file references, please double check.

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

Thanks for the PR @glitchperfect 🙌


AUI-2094 Remove feedback added by Form Validator when the field is not required and empty

The code lgtm, but it's missing a test for this use case that's being fixed. It will even help me understand what's being fixed, I'm not sure I see it at the moment. Can you add the test?


pull request for e2e test at 11/24/2016 18:26:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Cannot start nginx-lb

I have checked out your code and tried starting with docker-compose up. But it fails saying
ERROR: for nginx-lb  Cannot start service nginx-lb: driver failed programming external connectivity on endpoint compose_nginx-lb_1 (45fe13a6dd43c580f6bf946ee14ba0630cfca2ae3c73ce23e3b712a5a1ac5a75): Bind for <IP_ADDRESS>:8443 failed: port is already allocated

Make sure port 8443 is not already being used by another process (ie, another Kong running locally).

Hey to confirm port 8443 was not used by any other process

This is a Docker problem with your host and configuration - you can try to assign different ports in the docker-compose.yml file to see if it works (or disable port 8443 completely just for the sake of testing).


Pin 'current sequence stat chart', and update it with every screenshot

https://core.telegram.org/bots/api#editmessagemedia
This can be the API we should use

Implemented with latest commit


26294 - Feature - Accelerator Pipelines and Scripts

Overview/Summary
AB#26294
Added necessary pipelines and associated scripts for the ALZ Bicep Accelerator feature.
This PR fixes/adds/changes/removes

Adds required GitHub Action workflows for MVP
Adds PowerShell scripts which either integrate with the GitHub Action workflows or assist with the end-user automation.

Breaking Changes

No breaking changes as this is a new feature separate from all other aspects of ALZ-Bicep.

Testing Evidence

Pipelines and associated scripts have been tested in the following repository: https://github.com/oZakari/ALZ-Bicep-Accelerator/actions
As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[x] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues
[x] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated one or more of the following tests (if required)

Unit
Linting
E2E (End-To-End)
ValidateAzCloud (Base validation in Azure Cloud)
ValidateMcCloud (Base validation in Azure China Cloud)

[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
[x] If relevant, created or updated Code Tours here

/azp run validateazcloud

/azp run validateazcloud


Navbuddy can't find nvim navic after nvim update

Hello, after updating everything, i can't get navbuddy to work anymore.
Posting my configs here and the stack, hoping to find a way to get it back up, this plugin is insanely good.
neovim version: NVIM v0.10.0-dev-1911+g104565909
OS: arch
Lunarvim version:  master-b124e8c3
    {
        "SmiteshP/nvim-navbuddy",
        dependencies = {
            "neovim/nvim-lspconfig",
            "SmiteshP/nvim-navic",
            "MunifTanjim/nui.nvim",
            "numToStr/Comment.nvim",         -- Optional
            "nvim-telescope/telescope.nvim", -- Optional
        },
        opts = { lsp = { auto_attach = true } },
    },

it looks like it can't find nvim-navic. Using lazy nvim.
nvim-navic looks like disabled.
I also tried installing only nvim-navic, it looks like it lazy.nvim won't install it. the plugin is not even in the pack folder
   Error  17:19:13 notify.error lazy.nvim Failed to run `config` for nvim-navbuddy

...e/pack/lazy/opt/nvim-navbuddy/lua/nvim-navbuddy/init.lua:1: module 'nvim-navic.lib' not found:
	no field package.preload['nvim-navic.lib']
cache_loader: module nvim-navic.lib not found
cache_loader_lib: module nvim-navic.lib not found
	no file './nvim-navic/lib.lua'
	no file '/home/runner/work/neovim/neovim/.deps/usr/share/luajit-2.1/nvim-navic/lib.lua'
	no file '/usr/local/share/lua/5.1/nvim-navic/lib.lua'
	no file '/usr/local/share/lua/5.1/nvim-navic/lib/init.lua'
	no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/nvim-navic/lib.lua'
	no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/nvim-navic/lib/init.lua'
	no file './nvim-navic/lib.so'
	no file '/usr/local/lib/lua/5.1/nvim-navic/lib.so'
	no file '/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/nvim-navic/lib.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'
	no file './nvim-navic.so'
	no file '/usr/local/lib/lua/5.1/nvim-navic.so'
	no file '/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/nvim-navic.so'
	no file '/usr/local/lib/lua/5.1/loadall.so'

# stacktrace:
  - /nvim-navbuddy/lua/nvim-navbuddy/init.lua:1
  - .local/share/lunarvim/lvim/lua/lvim/plugin-loader.lua:106
  - .local/share/lunarvim/lvim/lua/lvim/plugin-loader.lua:104 _in_ **load**
  - .local/share/lunarvim/lvim/init.lua:17

adding to this,
if i try to install only nvim-navic, it looks like it stays disabled. it won't install it and create its folder in the plugins dir
{
        "SmiteshP/nvim-navic",
        opts = { lsp = { auto_attach = true } },
    }

  Disabled (3)
    ○ bufferline.nvim
    ○ nvim-navic
        dir /home/wolf/.local/share/lunarvim/site/pack/lazy/opt/nvim-navic
        url https://github.com/SmiteshP/nvim-navic

if i ls -la into .../opt/ i see nvim-navbuddy but not nvim-navic.
I tried a clean reinstall of all plugins. what is happening?

I manually git cloned nvim-navic into the plugins folder and navbuddy works.
For some reason i can't seem to debug, lazy is not installing nvim-navic (every other plugins get installed) and it's always disabled (nvim-navic)

Found the issue, not related to navbuddy.
Lunarvim builtin breadcrumbs ( which i disabled ) depends on navic and disables it too.


pulumi keeps deleting the existing s3 bucket eventhough the name has not been changed

File: content/docs/iac/get-started/aws/deploy-changes.md
// Create an AWS resource (S3 Bucket)
var bucket = new Bucket("my-bucket", new()
{
Website = new BucketWebsiteArgs
{
IndexDocument = "index.html",
},
});
If you run pulumi up after creating the above object, pulumi tries to delete the above bucket and then creates it again.

hi @sunmiller ; glad your giving Pulumi a try! While I see about reproducing what you see, if you set verbose logging, can you share more detail as to what you're seeing? https://www.pulumi.com/docs/iac/support/troubleshooting/#verbose-logging
We also have a great group of community members in our slack community: https://slack.pulumi.com/


Error response from daemon: Cannot start container c4262f07e8511b8fd988cc5f61072c9c5141dd86afeef09c80760108e5aa302b: device or resource busy

Description of problem:  I was running an openmediavault server and I thought that it would be a nice platform for docker also, so I installed it a per the instructions on this page.(http://docs.docker.com/linux/started/).  After following all of the steps exactly I went to execute "docker run hello-world", and while it seemed to download fine it gives me the below error.

Error response from daemon: Cannot start container c4262f07e8511b8fd988cc5f61072c9c5141dd86afeef09c80760108e5aa302b: device or resource busy
docker version:
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64
docker info:
Containers: 6
Images: 2
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 14
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.2.0-4-amd64
Operating System: Debian GNU/Linux 7 (wheezy)
CPUs: 4
Total Memory: 3.627 GiB
Name: SuperServer
ID: ELVA:EM5W:ZA3Q:DDLP:H73K:A2MU:PGNH:BNLY:AMGD:RTVA:JO4Y:DPBE
WARNING: No memory limit support
WARNING: No swap limit support
uname -a:
Linux SuperServer 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.): Physical, AMD PhenomII Desktop
How reproducible:  As said above I did not do anything outside of the initial setup and a basic test.  Other than openmediavault/nginx itself I am running and AFP server, an Apache2 server on port 8000, a tftp server, and a Samba server.
Steps to Reproduce:  I simply followed the tutorial on the step where you attempt to run the hello-world docker program it fails.
Actual Results:
Error response from daemon: Cannot start container c4262f07e8511b8fd988cc5f61072c9c5141dd86afeef09c80760108e5aa302b: device or resource busy
Expected Results: No error and the hello-world package to proceed normally
Additional info:

dup of https://github.com/docker/docker/issues/14540 ?

Yes, or very close to that issue.
I'm going to close this issue as a duplicate of https://github.com/docker/docker/issues/14540. Please read the comment on that issue; https://github.com/docker/docker/issues/14540#issuecomment-120549968 for more info


Default to pwsh.exe then powershell.exe for cli app profiles

Description of the new feature/enhancement

If you create a custom profile for running a cli app such as the SSH profile, default to using pwsh.exe for running that cli app. If it's not installed, then default to powershell.exe.
Proposed technical implementation details (optional)
Looks like cli apps such as SSH are registered to CMD automatically by WIndows Terminal. So change this to powershell.exe instead and add logic to prioritize use of pwsh.exe if installed before attempting to use powershell.exe.

An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it).

Terminal does not launch CLI applications using another shell; it launches them directly using CreateProcess. I do not think that we should add powershell's start-up time to the start-up process for every profile; it would waste time and confer no benefit.

You can tell this by looking at Process Explorer -- the spawned CLI application has no parent process other than WindowsTerminal.exe. :smile:

An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it).

I would guess that you are using a 32-bit version of pwsh. If you leave 'closeOnExit' set to its default setting, you will get to see the error message.


Flutter + Firebase | java.lang.IllegalStateException: FirebaseApp with name [DEFAULT] doesn't exist

I am trying to complete a very simple exercise by connecting my basic Flutter app to Cloud Firestore (in Firebase).
I have followed the instructions with regards to setup from codelab and Youtube videos from the Google Developers channel. However, I am getting the following error.
E/MethodChannel#plugins.flutter.io/cloud_firestore(13217): Failed to handle method call E/MethodChannel#plugins.flutter.io/cloud_firestore(13217): java.lang.IllegalStateException: FirebaseApp with name [DEFAULT] doesn't exist.

I have added the detailed info in SO thread https://stackoverflow.com/questions/54707794/flutter-firebase-java-lang-illegalstateexception-firebaseapp-with-name-def
High level config done

Updated the android build.gradle file
Updated the android\app build.gradle file
Added dependency to pubspec.yaml
Placed the google-services.json file

Am I missing something in the steps? Please advise
Logs
Output of flutter run -verbose
Attaching as a file
flutter run --verbose.txt
Output of flutter analyze
playground>flutter analyze
Analyzing playground...
No issues found! (ran in 4.4s)

Output of flutter doctor -v
playground>flutter doctor -v
[√] Flutter (Channel stable, v1.0.0, on Microsoft Windows [Version 10.0.17134.523], locale en-GB)
    • Flutter version 1.0.0 at C:\flutter
    • Framework revision 5391447fae (3 months ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[!] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at C:\Users\sanjose\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    X Android license status unknown.

[√] Android Studio (version 3.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

! Doctor found issues in 1 category.

#27485, #18405 are similar but no feedback what fixed it for them.
All others are just about ensuring the steps in the README were followed correctly.
You could try flutter clean, but not too optimistic this changes anything.

@zoechi Thank you so much! Actually flutter clean and then re-running did help!

#27485, #18405 are similar but no feedback what fixed it for them.
All others are just about ensuring the steps in the README were followed correctly.
You could try flutter clean, but not too optimistic this changes anything.

brooooo thank u very much
I tried flutter clean and it worked like magic

flutter clean did not work for me
PlatformException (PlatformException(error, FirebaseApp with name [DEFAULT] doesn't exist. , null))

I tried flutter clean and it didn't work for me.

@zoechi thank you .. I faced the same problem , and I did clean for project  flutter clean ,the error gone  .
Thank you

I fix this problem, in my case I open the folder android in Android Studio. He download any libs.

Flutter clean didn't solved the problem

fsef

Step 1 : Close the android emulator or disconnect the device.
Step 2 : Run flutter clean in the terminal.
Step 3 : Connect the device.
Step 4 : Run your app.
Worked for me :)


[Bug] MQTT subscription does not work as expected

The bug
If a device profile for MQTT is created with any customized topic, it is possible to send data to the topic but subscribing fails.
Server Environment
Docker Setup on Ubuntu Server on RaspberryPi
Docker image:  volodymyrbabak/tb-cassandra <IP_ADDRESS>
Edge Environment
Docker Setup on Ubuntu Server on RaspberryPi
Docker image: thingsboard/tb-edge 3.3.4EDGE
To Reproduce failed subscription
Steps to reproduce the behavior:

Create device profile
Create user defined topics for telemetry and attributes
Try to subscribe to this topics
Screenshot documentation:
Device profile:

MQTTX client try to subscribe:

Log message from docker container:

@ricktauss
hello, could you please specify details on the MQTT client host - are you connecting to TB edge or to TB server?

@volodymyr-babak
Hello,
as MQTT Client Software i use MQTTX on Windows PC for testing publishing and subscribing.
I have created a device once for the ThingBoard Plattform and once for the ThingsBaord Edge. For both variants it is possible to publish to the telemetry and the attribute topic which was defined in the device profile. But subscribing doesn't work on any plattform or topic.

@ricktauss
I believe this is covered in the answer https://github.com/thingsboard/thingsboard-edge/issues/10#issuecomment-1135039863
Please let me know if you are interested in any additional details.

@volodymyr-babak
Yes this covers both. I will also close this issue as completed


Ensure the thing works with v19.x and later.

This will fix the madness in the crdb CI.

I've added a commit to this branch to update the version number for release.


Fix handling of whitelisted property names

Closes #96

@mkulak I incorporated your points. :)

Codecov Report

Merging #289 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #289   +/-   ##
=======================================
  Coverage   91.27%   91.27%
=======================================
  Files          36       36
  Lines         344      344
  Branches       15       15
=======================================
  Hits          314      314
  Misses         27       27
  Partials        3        3

Flag
Coverage Δ

#webui
91.27% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

👍


bpf-loader: virtual workspace warning

$ cargo build
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions

Hi @cppcoffee, could you help me solve the conflits and rebase on the latest master branch? It seems I cannot push to your repo.

The CI may be failed https://github.com/actions/upload-artifact/issues/610

Sorry, I closed PR by mistake and create new PR to resolved the conflict:
https://github.com/eunomia-bpf/eunomia-bpf/pull/358


ISSUE WITH Xiaomi Redmi Note 12 Pro Ultra Mega Dark Killer Ultimate Superphone Deluxe Special Edition with 5G Network and AI-Enhanced Camera, The Grand Master of All Smartphones, The Ultimate Flagship Phone of the Decade, The Most Powerful Device with Lightning-Fast Octa-Core Processor, Massive 16GB RAM and 2TB Storage, The Device with Stunning 7.5-inch QHD+ Super AMOLED Display with HDR and Dolby Vision Support, The Most Durable Phone with IP68 Rating, The Masterpiece of Photography with 108MP Ultra-Premium Main Lens, 64MP Ultra-Wide-Angle Lens, 32MP Super Zoom Lens, and 16MP Macro Lens, The Phone with Insane Battery Life of 8000mAh, The Most Advanced Phone with Facial Recognition, Fingerprint Scanner, Wireless Charging, and 5G Connectivity.

НЕ ЗАПУСКАЕТСЯ НА МОЁМ Xiaomi Redmi Note 12 Pro Ultra Mega Dark Killer Ultimate Superphone Deluxe Special Edition with 5G Network and AI-Enhanced Camera, The Grand Master of All Smartphones, The Ultimate Flagship Phone of the Decade, The Most Powerful Device with Lightning-Fast Octa-Core Processor, Massive 16GB RAM and 2TB Storage, The Device with Stunning 7.5-inch QHD+ Super AMOLED Display with HDR and Dolby Vision Support, The Most Durable Phone with IP68 Rating, The Masterpiece of Photography with 108MP Ultra-Premium Main Lens, 64MP Ultra-Wide-Angle Lens, 32MP Super Zoom Lens, and 16MP Macro Lens, The Phone with Insane Battery Life of 8000mAh, The Most Advanced Phone with Facial Recognition, Fingerprint Scanner, Wireless Charging, and 5G Connectivity.
Требую деньги обратно!

It isn't delightful. After all, we conducted manual tests on all models of Xiaomi phones. Could you describe the problem in more detail?
Sincerely, Mykhailo Chirozidi
(razrab pidoras)


Fixes current tab logic for main card

 Evo: Hotfix changing tabs on another panel causes update issues on main panel


What's the meaning of Frames, Crops, and Clips reqpectvely?

Hi, I am currently applying your method for very large-scale micro-video classification.
However, I am a little confused about the Frames, Crops, and Clips in your paper, since I am a green hand.
May I check their meanings with you?

Frame: the number of segments sampled from a video, and a segment may have lots of frames?
Crop: the number of cropped images in a single frame?
Clip: I don't know. It cannot be the number of frames in a segment because i's fixed to 5?

You are right.
You are right. 3 crops is  just used during testing Kinetics 400.
Here Clip means 'perfom testing for 10 times' which has been mentioned in the  README here


TokenInvalid error

Hi again,
While starting the bot it gives a TokenInvalid error, While I entered the right token inside .env, which is inside dist.
/srv/bots/invite# npm start

><EMAIL_ADDRESS>start
> node dist/src/index.js

/srv/bots/invite/node_modules/discord.js/src/client/websocket/WebSocketManager.js:136
    const invalidToken = new DiscordjsError(ErrorCodes.TokenInvalid);
                         ^

Error [TokenInvalid]: An invalid token was provided.
    at WebSocketManager.connect (/srv/bots/invite/node_modules/discord.js/src/client/websocket/WebSocketManager.js:136:26)
    at Client.login (/srv/bots/invite/node_modules/discord.js/src/client/Client.js:226:21)
    at Object.<anonymous> (/srv/bots/invite/dist/src/index.js:59:8)
    at Module._compile (node:internal/modules/cjs/loader:1233:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1287:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'TokenInvalid'
}

Node.js v20.5.1

Generated a fresh pair two times, without any luck.

Hello,
Could you try launching the bot with the .env file placed outside of the dist/ folder? In this project, the path to the .env file isn't explicitly configured, which means that the dotenv library may default to looking for it at the root of the project, especially if it's not in a production environment (where it would be dist/ only). The behavior of dotenv can vary based on its configuration and the environment in which it's running.
If this adjustment doesn't solve the problem, may I please see the structure of your dist folder? This will help me understand if there are any other configuration issues or path discrepancies affecting the bot's operation.
And yes, I know, I really need to change this method of starting the bot.  Sorry for the inconvenience. 🙄
Kind regards,
Enes Tahiri

Hi,
I don't mind for the inconvenience, atleast this helps the project! :D
So far I saw this is the only decent selfhosted discord invite tracker bot out there so happy to help.
These are my ls outputs:
/srv/bots/invite# ls
LICENSE  README.md  config.ts  dist  node_modules  package-lock.json  package.json  src  tsconfig.json

/srv/bots/invite/dist# ls
config.js  src

/srv/bots/invite/dist/src# ls
buttons  client.js  commands  events  index.js  types.js  utils

After npm install I used npm run build and after just pasted de .env in every folder you see. and I tried to start the bot from all three folders with npm start and also with node path/index.js. all six tries without luck.

Hello,
I don't see any .env file in srv/bot/invite/. Can you create it and complete the information in the format of the .env.example?
# Discord Bot Info
TOKEN=

# MySQL Server Info
HOST=
PORT= # default 3306
USERNAME=
PASSWORD=
DATABASE=

Let me know if this solved the problem.
Kind regards,
Enes Tahiri

Oops well yes ls doesn't show files which start with a dot. but the file is in there, in all three folders.

Can you do an ls -a?
And can you also check that your .env looks like this

I've found the issue. Apparently, I was using an older generated token. Some .env files had a different token, so I replaced them all with a new one. Now, it gets past the token check.
However, the MySQL database connection doesn't seem to be working. Connecting to the database from the command line with the same user and password works. Also, other bots are able to connect using this user (though they use a different database).
error:
/srv/bots/invite# npm start

><EMAIL_ADDRESS>start
> node dist/src/index.js

/srv/bots/invite/node_modules/mysql/lib/protocol/Parser.js:437
      throw err; // Rethrow non-MySQL errors
      ^

Error: ER_ACCESS_DENIED_ERROR: Access denied for user 'bot'@'localhost' (using password: YES)
    at Sequence._packetToError (/srv/bots/invite/node_modules/mysql/lib/protocol/sequences/Sequence.js:47:14)
    at Handshake.ErrorPacket (/srv/bots/invite/node_modules/mysql/lib/protocol/sequences/Handshake.js:123:18)
    at Protocol._parsePacket (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:291:23)
    at Parser._parsePacket (/srv/bots/invite/node_modules/mysql/lib/protocol/Parser.js:433:10)
    at Parser.write (/srv/bots/invite/node_modules/mysql/lib/protocol/Parser.js:43:10)
    at Protocol.write (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:38:16)
    at Socket.<anonymous> (/srv/bots/invite/node_modules/mysql/lib/Connection.js:88:28)
    at Socket.<anonymous> (/srv/bots/invite/node_modules/mysql/lib/Connection.js:526:10)
    at Socket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:343:12)
    --------------------
    at Protocol._enqueue (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:144:48)
    at Protocol.handshake (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:51:23)
    at Connection.connect (/srv/bots/invite/node_modules/mysql/lib/Connection.js:116:18)
    at Connection._implyConnect (/srv/bots/invite/node_modules/mysql/lib/Connection.js:454:10)
    at Connection.query (/srv/bots/invite/node_modules/mysql/lib/Connection.js:196:8)
    at initDatabase (/srv/bots/invite/dist/src/utils/mysql.js:58:19)
    at Object.execute (/srv/bots/invite/dist/src/events/ready.js:22:34)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Emitted 'error' event on Connection instance at:
    at Connection._handleProtocolError (/srv/bots/invite/node_modules/mysql/lib/Connection.js:423:8)
    at Protocol.emit (node:events:514:28)
    at Protocol._delegateError (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:398:10)
    at Handshake.<anonymous> (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:153:12)
    at Handshake.emit (node:events:514:28)
    at Sequence.end (/srv/bots/invite/node_modules/mysql/lib/protocol/sequences/Sequence.js:78:12)
    at Handshake.ErrorPacket (/srv/bots/invite/node_modules/mysql/lib/protocol/sequences/Handshake.js:125:8)
    at Protocol._parsePacket (/srv/bots/invite/node_modules/mysql/lib/protocol/Protocol.js:291:23)
    at Parser._parsePacket (/srv/bots/invite/node_modules/mysql/lib/protocol/Parser.js:433:10)
    at Parser.write (/srv/bots/invite/node_modules/mysql/lib/protocol/Parser.js:43:10) {
  code: 'ER_ACCESS_DENIED_ERROR',
  errno: 1045,
  sqlMessage: "Access denied for user 'bot'@'localhost' (using password: YES)",
  sqlState: '28000',
  fatal: true
}

Node.js v20.5.1

and ofcourse mariadb gives the following error: [Warning] Access denied for user 'bot'@'localhost' (using password: YES)

The MySQL error 1045 is primarily related to authentication issues. It typically indicates a problem with the setup or configuration of your MySQL database, specifically concerning the credentials – the username and password used for accessing the database.
This error is not about the bot itself but points to an issue in your database configuration. The most common cause for this error is incorrect login details. To resolve it, you should verify and ensure that the username and password you are using are correct and match the credentials set for the database user in the MySQL server configuration.
cf. https://kinsta.com/knowledgebase/mysql-error-1045/

I already know what the issue is, but can't seem to fix it.
The issue is that I configured require-secure-transport = on in mysql. which states that a ssl connection in mandatory.
another selfhosted bot works perfectly fine with this setup, I have changed some of the code of this bot so it should connect with ssl:
.env
# MySQL Server Info
HOST=localhost
PORT=3306
USERNAME=bot
PASSWORD=password
DATABASE=invitetracker
VARIABLES=sslidentity=/etc/ssl/bots/ticketsystem.p12&sslpassword=password&sslcert=/etc/ssl/bots/ca.pem

mysql.js
const options = {
    host: process.env.HOST,
    port: process.env.PORT ? Number(process.env.PORT) : 3306,
    username: process.env.USERNAME,
    password: process.env.PASSWORD,
    database: process.env.DATABASE,
    variables: process.env.VARIABLES,
};
const uri = `mysql://${options.username}:${options.password}@${options.host}:${options.port}/${options.database}?${options.variables}`;


Bank Accounts and Other Taxes fields don't appear on pdf

We used to have this same issue until we re-worked the PDF to match the variables in the code. Either the variables were changed back, or the incorrect pdf is being used. Likely, it's the latter and we need to match the code variables in "bank accounts" and "other expenses type" to the PDF.

Bank accounts now prints, other taxes does not


Bubble indicator follow mouse on desktop

I have been playing around with trying to have a desktop feature in which when you mouse over the indicator will automatically pop up and follow the mouse without having to click and hold. I added a bool called mouseHover = false by default. I almost have it working, but its behavior is quite peculiar, as you can see in the link below.
In this gif I am not clicking the mouse at all, the bubble keeps going up and down on its own, I am simply moving the mouse with snap off. At first when I mouseover, it goes at probably 20 times a second quickly than repeats slowly
https://i.imgur.com/1bLcMuc.gifv
I am not quite sure what needs to be changed. This is my first project trying to learn Dart/Flutter, I only started using them a week or two so ago, so I feel I just don't have the experience yet to narrow it down. Any input on it would be greatly appreciated.
Thanks,
-MH
:671   child: Listener(
        onPointerHover: (_displayIndicator && widget.config.mouseHover)
            ? (PointerHoverEvent details) =>
                _refreshPosition(LongPressMoveUpdateDetails(
                  globalPosition: details.localPosition,
                  offsetFromOrigin: Offset.zero,
                ))
            : null,
        onPointerEnter: (!_displayIndicator && widget.config.mouseHover)
            ? (PointerEnterEvent details) =>
                _onDisplayIndicator(LongPressStartDetails(
                  globalPosition: details.localPosition,
                ))
            : null,

is this an issue about the current library?

Technically no, the code above was code I was trying to implement myself, but was hoping perhaps you might have some insight as to what I might be able to do to keep the bubble from repeatedly appearing and disappearing on its own. If not, I understand, this is something custom I really wanted personally.
I was just trying to use the listener that you already had in the graph code to listen for OnMouseEnterEvenet and make the bubble appear and then follow the mouse the entire time until OnMouseExitEvent is called, then it would hide it.

if you check the code, the method _onDisplayIndicator  has the _animationController.forward , for that reason you see the animation of the bubble, you can create another method and remove that line.


Node.js 12 deprecation

We're seeing the following warnings on our backport actions. I assume this is something in the action itself, so reposting it here:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: zeebe-io/backport-action

Thanks for raising this @mweinelt 🙌
This must be completed before Summer 2023, but I plan to update it before that.

We plan to migrate all actions to run on Node16 by Summer 2023

Fixed with #295

@korthout need a new release to put it into effect, thanks.

I've released https://github.com/zeebe-io/backport-action/releases/tag/v0.0.9


Internal Validation Error in Modal with RichTextInputElement

It seems that passing RichTextSectionElement.Text to the initialValue of RichTextInputElementBuilder as shown below results in a validation error within Slack’s modal after this change.
val richTextSectionElement = RichTextSectionElement.Text(
    text,
    RichTextSectionElement.TextStyle(false, false, false, false, false, false, false)
)

BlockElements.richTextInput { rti: RichTextInputElement.RichTextInputElementBuilder ->
    rti.actionId(SOME_ACTION_ID).initialValue(richTextSectionElement)
}

(Sorry for the Kotlin code examples.)
I believe the fields "highlight": false, "client_highlight": false, and "unlink": false are not allowed in the modal, which is likely causing this issue.
To work around this, you can create the elements using:
RichTextSectionElement.Text.builder().text(
    text
).build()

RichTextSectionElement.Link.builder().url(
    url
).build()

This issue does not occur in version 1.40.2, and it seems to be related to the changes in version 1.40.3.
The Slack SDK version
1.40.3 and above
Expected result:
The expected behavior is that either no implicit validation error occurs, or a clear validation error is explicitly shown.
Actual result:
At first glance, everything seems fine, but no action can be performed unless the initial value is changed (this appears to be a validation error).

I have registered the issue, including sharing it with other users. Thanks.

Hi @azihsoyn, thanks for writing in.

RichTextSectionElement.TextStyle(false, false, false, false, false, false, false)

Indeed, a few more arguments were added and some of them may not work for modals. The allowed properties can be changed over time, so we hesitate to add more sub classes specifically for modal views. My recommendation is to avoid using the all-arg constructor. You can use TextStyle's builder method as an easy way to construct a valid object.
If you mean that not only the all-arg constructor use case but also other code patterns do not work, please share code snippets demonstrating it. Either Kotlin or Java is fine.

@seratch Thank you for the quick response!

TextStyle’s builder method

I wasn’t aware of the TextStyleBuilder. It seems that this will work well on my side as well.

If you mean that not only the all-arg constructor use case but also other code patterns do not work

The issue I found is only with the all-arg constructor case.

I got it. Let me close this issue now, but please feel free to write in whenever you have follow-up comments. thank you again for taking the time to share this!


Make go's build flags a variable

This allows the user to specify build flags from the make command
line. For example to force a complete rebuild one could use:
make BUILD_FLAGS='-v -a' TAGS="sqlite"

Thanks!


Add support for git tokens, to be used for python dependencies from private git repos, in the main python template.

Description
This change adds the ability to provide a GIT_TOKEN as a build argument. This git token is then set as an environment variable.
Also the pip install code is moved to a builder stage.
Motivation and Context
The reason to make this GIT_TOKEN environment variable available, is so that it can be used when adding the following kind of dependency to requirements.txt:
git+https://${GITHUB_TOKEN}@github.com/user/project.git@{version}

[x] I have raised an issue to propose this change (required)

Which issue(s) this PR fixes

Fixes openfaas/faas#1723
How Has This Been Tested?
It has been tested by creating a python module in a private github repo (using this video as an instruction). Then I created a python project with a requirements.txt file that uses this private git repo as a dependency.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Version change (see: Impact to existing users)

Impact to existing users
This doesn't have any direct impact on the end users, as the resulting image will contain the same files. The image layers are slightly different though, due to the pip install commands being moved to a builder stage. This has a very small impact on how the layers are cached, but since the the default requirements.txt in the template doesn't have any dependencies, this doesn't matter all that much.
Checklist:

[x] My code follows the code style of this project. (I think? Is there such a thing as a Dockerfile code style?)
[ ] My change requires a change to the documentation. (Though explaining the ability to use the GIT_TOKEN would be nice)
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes. (Not applicable I think?)
[x] All new and existing tests passed.

Hmm, I found this article: https://pythonspeed.com/articles/docker-build-secrets/

Unfortunately build arguments are also embedded in the image [...] Technically you can work around this leak by using multi-stage builds, but that will result in slow builds, so I don’t recommend it.

So it would be safe with a multi-stage build like in this pull request, but it is recommended to use Buildkit's --secret feature instead...
I'm going to look into this, because this will also make sure that C/C++ dependencies like numpy and pandas work out of the box, because there is no need for a builder stage.

I think that for now it is not really feasible to use Buildkit secrets. For that to work, the faas-cli would first need to add support for enabling buildkit and allowing --secret commandline arguments here. See here for how to enable buildkit and here for how to use secrets (and here for how to use them in environment variables).

Thanks for the suggestions.
We had a customer ask for this, and we implemented it in OpenFaaS Pro
Introducing our new Python template for production.
See also: Private npm modules

/lock: resolved


Upgrade libraries for all projects

to remove latent, though unreachable, vulnerabilities in 3rd party code

Good call. fixed


Removed 'APPLICATION_JSON_UTF8_VALUE' as it is deprecated.

code smell:
"@deprecated" code should not be used.
Explanation:
Once deprecated, classes, and interfaces, and their members should be avoided, rather than used, inherited, or extended. Deprecation is a warning that the class or interface has been superseded, and will eventually be removed. The deprecation period allows you to make a smooth transition away from the aging, soon-to-be-retired technology.
Solution:
To solve the above code smell I removed "APPLICATION_JSON_UTF8_VALUE" as it is deprecated and replaced it with "APPLICATION_JSON_VALUE".

Looks good.


[BUG] Excel generated with Blade template displays raw CSS in A1 if it's empty

Package version: 1.3.7
Laravel version: 4.2.18
Expected behaviour: rows 1 and 2 should display empty cells for merged columns A to E
Actual behaviour: row 1 incorrectly displays raw CSS from the Blade template; row 2 correctly displays empty cells. The same thing happens when cells are not merged, and when both rows are stripped of all formatting; and regardless of whether A1 contains 1) an empty space, or 2)   or 3) an empty PHP string.

Code:

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

        Planned

        In
        Out (Break)
        In (Break)
        Out
        Total

@agadenis how did you fix it eventually? I am having the same problem. Thank you.

@agadenis how did you fix it eventually? I am having the same problem. Thank you.

Please open a new topic, using the issue template, if you're having issues. You're replying on a very old topic about a very old version which is no longer supported.

I use 2.1.30 which has the same issue. I cannot use 3.x because the loadView function is not available.
For anyone who has the same problem, my solution is to store the file in server first, and then set the first cell value to empty string.
            Excel::load($fileName, function ($file) {
                $sheet = $file->getExcel()->getActiveSheet();
                $sheet->setCellValue('A1', '');
            })->download('xlsx');

What do you mean? loadView is not available? Have you read the docs of version 3? https://laravel-excel.maatwebsite.nl/3.1/exports/from-view.html

Sorry I meant the css in loadView function.

You cannot style it via CSS.
See example in docs: https://laravel-excel.maatwebsite.nl/3.1/exports/extending.html#customize

Yep, that's the reason why I cannot switch to 3.x. I tried 3.1 and really like the new structure, but our system uses css in the views heavily, so upgrading is really hard.


Add eslint and remove tslint

Closes #97
Add eslint configs and remove tslint configs. There may still be some remnants to clean out, but that will require some more investigation/help (@waxlamp)

Could you edit the description to explain what's different and/or better about using ESLint?

It's in the issue, but I'll quote it up top for ease of reviewing.

Also, you mentioned there are some remnants to clean up--what did you mean?

I didn't remove any of the plugins, and I was concerned that means that tslint is still in there as a dependency. I feel like that could be cleaned up a bit, but I'd need to explore what can be removed.


[layer] backwarding of embedding layer

Unlike other layers, embedding layer uses specific form of Tensor called IndexedSlices and this data contains the specific indicies of the Tensor that we are interested in.
Thus, during the backwarding process, we do not have to set all the value-tensor-shaped gradient in VarGrad, but we can optimize in by formulating the specific part for the Gradient Tensor.
In current NNTrainer code, there is no such consideration like above, but using same-shaped but zero-filled Tensor for un-interested-indexed part of the Tensor.
As far as I am concerned, we should work on this part in the near future for the memory optimization purpose.

:octocat: cibot: Thank you for posting issue #2289. The person in charge will reply soon.


[SPARK-28057][SQL] Add method clone in catalyst TreeNode

What changes were proposed in this pull request?
Implemented the clone method for TreeNode based on mapChildren.
How was this patch tested?
Added new UT.

@hvanhovell

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11770/
Test PASSed.

Test build #106529 has started for PR 24876 at commit 7f1cd35.

Test build #106529 has finished for PR 24876 at commit 7f1cd35.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merging to master. Thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106529/
Test PASSed.


props in the data of a vnode will not be resolved into the $attrs of the component instance of the vnode

Version
2.6.10
Reproduction link
https://jsfiddle.net/fubai7/a2znbx94/
Steps to reproduce
Vue.component('test', {
  inheritAttrs: false,
  template: '<div>{{$attrs.content}}</div>'
})

Vue.component('container0', {
  template: '<test content="container0"></test>'
})

Vue.component('container1', {
  render (h) {
    return h('test', {
      props: {
        content: 'container1'
      }
    })
  }
})

Vue.component('container2', {
  render (h) {
    return h('test', {
      attrs: {
        content: 'container2'
      }
    })
  }
})

new Vue({
  el: '#app'
})

What is expected?
props in the data of a vnode will be resolved into the $attrs of the component instance of the vnode
What is actually happening?
props in the data of a vnode will not be resolved into the $attrs of the component instance of the vnode

The props of the component is extracted from vnode.data.props and vnode.data.attrs, after extracted (some data in data.attrs may be deleted according to component props you have defined) the data.attrs will be assigned to the $attrs in the component instance. @AllenField

I'd call that working as intended, otherwise props is just an alias for attrs.

As mentioned, this is working as intended


Report is counting errors as warnings

Results show 5 errors, but summary shows 0 errors and 5 warnings.

I've submitted a PR for this. #90


Some cmake changes for Linux

These all revolve around dropping some hard dependencies and allowing more flexibility when building from source
Let me know if you would rather have them as individual MRs

This is a nice cleanup, thank you.
Do you know why OpenBSD and NetBSD would have problems with pkg_check_modules for the curses library in this case? I've tried to use it before, but seems to always fail on those systems. FreeBSD is fine... I think.

Sorry for the extreme delay here, but our CMake system was really gross and needed to be cleaned up. It's still not perfect, but it's much better now as of the 0.96.11 release. I'll be looking to integrate the changes in this PR in the near future.

Cleaned up conflicts and opened a new PR with some other community contributions.
Your change will be merged today as part of this PR: https://github.com/clangen/musikcube/pull/504
Closing this one.
Thanks again!


Annoying Failed to save project keep popping up

Describe the bug
Working on a project keep getting hundreds of Failed to save projects popping up on the right side.

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-vleyjr
Steps to reproduce
No matter what i do, they keep popping up.
Expected behavior
Just working on the project with bolt
Screen Recording / Screenshot
No response
Platform

OS: Windows
Browser: Opera
Version: Latest version

I have tried on Chrome but it does the same
Additional context
No response

TLDR: download the project to ensure you don't lose your work
I had a similar experience thrice in the last 24 hours with a project I had previously started.
I downloaded the project and then went to Stackblitz to continue from wherever it had stopped -- and was shocked to see it had reverted to code from hours earlier in the day.  I was admittedly less panicky the second and third time. ;)
I have that code in the zip file I downloaded ... is my conversation history lost in this update then?  Do I just push the unzipped project to the stackblitz repo directly or via github or something? What's the easiest way to recover from this?  A zip file import tool would be helpful right now.  Thanks for your help!!

Appreciate the feedback! We are aware of this issue and are tracking is here: https://github.com/stackblitz/bolt.new/issues/2762.
The best workaround right now would be to open a project in StackBlitz and drag and drop the files into the StackBlitz filesystem to continue to development. From there, you should be able to open the StackBlitz project in Bolt.


Carousel indicators not relevant

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When applying custom interval to .carousel-item (example), the indicators of the remaining time before the next slide isn't relevant (e.g. for the one with 10s interval : 2 laps are completed)
Reduced test cases
Go to the carousel page and watch for the first slide.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Firefox, Microsoft Edge
What version of Boosted are you using?
5.2.0 (current_main_branch)

I don't know if we have the information somewhere but we should know if the indicator:

have its own tempo for the loop: fixed duration whatever the custom interval used for the transition between the slides
must reflect the custom interval = always one loop


Create partitions

PR Description
Type of change

[x] New feature

Summary of the change and which issue is fixed
Main changes:

use partitionId as loggroup name
implement createPartitionsV1

Checklist

I have run format.sh under script
I have commented my code, particularly in hard-to-understand areas
New and existing unit tests pass locally with my changes

Closed via #1757


Add xenial to supported release list.

Summary
Adds xenial to the releases this check can look at.
Motivation
We've got some xenial boxes that are currently peacefully erroring this out. We should be reading for them!
r? @stripe/observability

lgtm


spawn worker processes and send them the required data instead of forking for each target

Required data includes:

updated state of the DAG
fs cache
which node to execute


./phpactor  PHP Fatal error:  Uncaught Error: Undefined class constant 'PARAM_STUB_PATHS' in .vim/plugged/phpactor/lib/Phpactor.php:89

Hello
phpactor is installed via vimplug. Cannot run the PHPActor bin command and in VIM autocompletion doesn't work as well.
~/.vim/plugged/phpactor/bin$ ./phpactor
PHP Fatal error:  Uncaught Error: Undefined class constant 'PARAM_STUB_PATHS' in /home/work/.vim/plugged/phpactor/lib/Phpactor.php:89

Fixed by running composer install in /home/work/.vim/plugged/phpactor folder


Disabled days problem

Hi.
How I make to disable all day??
The events get from Google Calendar
In image set disabled days: 2021-01-02, 2021-01-03, 2021-01-04 but in image only block day: 2021-01-02 and it's available to select 3 and 4 day but it's not correct can't choose day 3 and 4

If set true halfDay block date 2021-01-01 automatic, why it's block??

What version are you using?

vue-hotel-datepicker Package
SO
Browser

Please provide me with a working example and indicate your local time zone.

What version are you using?

vue-hotel-datepicker Package
SO
Browser

Please provide me with a working example and indicate your local time zone.

Chrome

And the versions of those?
Which version of this package are you using?

Ahhh and don't forget to tell me you local time zone.

Ahhh and don't forget to tell me you local time zone.

Version: "vue-hotel-datepicker": "^4.0.0-beta.9"
Time zone: America/Mexico_City
Another thing it's in this case, when set :firstDayOfWeek="1" the days move but at the top days not move, for example Thursday it's Friday because Friday I set require min 2 nights

Thanks!
Can you provide me with an Vue example of the code?
Maybe an unique Vue component file with your configuration hardcoded in data in order to be able to reproduce it?

Thanks!
Can you provide me with an Vue example of the code?
Maybe an unique Vue component file with your configuration hardcoded in data in order to be able to reproduce it?

Component:

disabledDates:Array[3]
0:"2021-01-02"
1:"2021-01-03"
2:"2021-01-04"

Find into the demo the same bug
Url demo https://github.com/krystalcampioni/vue-hotel-datepicker/tree/v4.0.0-dev/src
Without halfDay

With halfDay

Check the last version please... did you notice a change?

I will check this issue before release the next beta (The next is 14)

Check the last version please... did you notice a change?

Hi.
Update de package using: "vue-hotel-datepicker": "^4.0.0-beta.13" but have a problem not find file "vueHotelDatepicker.css"
I check in dist folder not exists

Check that now! Sorry for the inconvinience

Check that now! Sorry for the inconvinience

I solve the extra day, but not the first. I think this issue is related to local timezone. I am conducting some tests

I solve the extra day, but not the first. I think this issue is related to local timezone. I am conducting some tests

Excelent good job thank very much

Excelent good job thank very much


Can't build with make

We use GitHub issues for development related discussions.
Please use the forum to ask questions.
Describe the issue
Can't build using make, I got the error below.
Code to reproduce the issue
Clone the current master and run make.
Expected Results
Being able to build the project using make
Actual Results
ESP32 Chip version
ESP32
ESP-IDF version
4.2
Development kit used
None
Development machine OS
Ubuntu (WSL)
Compilation warnings/errors (if available)
Toolchain path: /home/dev/.espressif/tools/xtensa-esp32s2-elf/esp-2020r3-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
Toolchain version: esp-2020r3
Compiler version: 8.4.0
Python requirements from /home/dev/esp/esp-idf/requirements.txt are satisfied.
CC build/bootloader/esp_hw_support/compare_set.o
CC build/bootloader/esp_hw_support/cpu_util.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_pm.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_wdt.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_init.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_clk_init.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_sleep.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_time.o
CC build/bootloader/esp_hw_support/port/esp32/rtc_clk.o
AR build/bootloader/esp_hw_support/libesp_hw_support.a
CC build/bootloader/bootloader_support/src/bootloader_random_esp32.o
CC build/bootloader/bootloader_support/src/bootloader_efuse_esp32.o
CC build/bootloader/bootloader_support/src/bootloader_flash.o
CC build/bootloader/bootloader_support/src/flash_qio_mode.o
CC build/bootloader/bootloader_support/src/bootloader_init.o
CC build/bootloader/bootloader_support/src/bootloader_mem.o
/home/dev/esp/esp-idf/components/hal/esp32/include/hal/cpu_ll.h: Assembler messages:
/home/dev/esp/esp-idf/components/hal/esp32/include/hal/cpu_ll.h:60: Error: invalid register number (97) for 'wsr' instruction
make[2]: *** [/home/dev/esp/esp-idf/make/component_wrapper.mk:292: src/bootloader_mem.o] Error 1
make[1]: *** [/home/dev/esp/esp-idf/make/project.mk:635: component-bootloader_support-build] Error 2
make: *** [/home/dev/esp/esp-idf/components/bootloader/Makefile.projbuild:41: /home/dev/lv_port_esp32/build/bootloader/bootloader.bin] Error 2

If possible, copy the compilation log into a file and attach it here

@tore-espressif Should I set the target chip before make? Like this: TARGET=esp32 make? I've never cross this bug before.

First line of your log says that you are using toolchain for esp32s2. It is only weird if you didn't set it yourself: esp32 should be default.
Running idf.py set-target esp32 should fix the problem.
(Since ESP32S2 support was introduced in ESP-IDF 4.2, there is no alternative command for make, AFAIK)

Yep, it's weird because I've never used the esp32-s2 target. I will try your suggestion.

I was able to compile this project using make with the following patch https://github.com/lvgl/lvgl/pull/2108

I was able to compile this project using make with the following patch lvgl/lvgl#2108

Yep, that was the last missing thing :)

Just saw it got merged, will update the lvgl submodule in a bit.