Operation timed out (Read failed) during push to us.gcr.io

Environment:

Jib version: 1.6.1
Build tool: Maven 3.6.1
OS: macOS 10.14.6

Description of the issue:
I tried building an image for the first time for a new project. It failed thrice in a row with Operation timed out (Read failed). I increased the timeout to 60 sec but it failed again.
I then used dockerBuild that built to docker daemon and tried pushing using docker push. It took very long time (~ 13 minutes) and reattempted after a failure in middle but was able to successfully push. The image size showed by docker is 169MB, GCR shows virtual size 86.5MB.
After docker successfully pushed to GCR, I executed jib buildagain with default timeout and surprisingly it succeeded and pushed in no time (32 sec) (as there was no change to project) whereas it was timing out just before docker pushed the image.
Expected behavior:
I believe jib should've pushed it without any exception.
Steps to reproduce:

It's a private project, thus I can't share the project to build the image from, but if there is something I should check configuration wise, please let me know.
I just executed mvn -X -Djib.serialize=true -Djib.console=plain compile jib:build with the given configuration.
I've given the log output post processing of project classes that may be helpful.

jib-maven-plugin Configuration:
    <plugin>
        <groupId>com.google.cloud.tools</groupId>
        <artifactId>jib-maven-plugin</artifactId>
        <version>1.6.1</version>
        <configuration>
          <from>
            <credHelper>gcloud</credHelper>
          </from>
          <to>
            <image>us.gcr.io/${projectId}/zl-wzgp:0.1.0-SNAPSHOT</image>
            <credHelper>gcloud</credHelper>
            <tags>
              <tag>latest</tag>
            </tags>
          </to>
          <container>
            <jvmFlags>
              <jvmFlag>-Xms512m</jvmFlag>
              <jvmFlag>-XX:+UnlockExperimentalVMOptions</jvmFlag>
              <jvmFlag>-XX:+UseCGroupMemoryLimitForHeap</jvmFlag>
              <jvmFlag>-Dspring.profiles.active=production</jvmFlag>
            </jvmFlags>
            <mainClass>com.zl.wzgp.Launcher</mainClass>
            <ports>
              <port>4000</port>
            </ports>
          </container>
        </configuration>
     </plugin>

Log output:

[DEBUG] TIMING  Building and pushing image
[INFO] Retrieving registry credentials for us.gcr.io...
[DEBUG] TIMING  Retrieving registry credentials for us.gcr.io
[DEBUG] Using credentials from docker-credential-gcloud for us.gcr.io
DEBUG] TIMING  Retrieving registry credentials for us.gcr.io
[DEBUG] Using credentials from docker-credential-gcloud for us.gcr.io
[DEBUG] TIMED   Retrieving registry credentials for us.gcr.io : 1161.0 ms
[DEBUG] TIMING  Authenticating push to us.gcr.io
[DEBUG] TIMED   Authenticating push to us.gcr.io : 1923.0 ms
[INFO] Getting base image gcr.io/distroless/java:8...
[DEBUG] TIMING  Pulling base image manifest
[DEBUG] TIMED   Pulling base image manifest : 6022.0 ms
[DEBUG] TIMING  Preparing base image layer pullers
[DEBUG] TIMED   Preparing base image layer pullers : 0.0 ms
[DEBUG] TIMING  Pulling base image layer sha256:e8d8785a314f385d3675a017f4e2df1707c528c06e7a7989663fdab4900bd8ff
[DEBUG] TIMED   Pulling base image layer sha256:e8d8785a314f385d3675a017f4e2df1707c528c06e7a7989663fdab4900bd8ff : 714.0 ms
[DEBUG] TIMING  Pulling base image layer sha256:e005d777a298a3529b1c8cf890883359e050cc966089ce84fea4d17b111907db
[DEBUG] TIMED   Pulling base image layer sha256:e005d777a298a3529b1c8cf890883359e050cc966089ce84fea4d17b111907db : 709.0 ms
[DEBUG] TIMING  Pulling base image layer sha256:3e010093287c245d72a774033b4cddd6451a820bfbb1948c97798e1838858dd2
[DEBUG] TIMED   Pulling base image layer sha256:3e010093287c245d72a774033b4cddd6451a820bfbb1948c97798e1838858dd2 : 717.0 ms
[DEBUG] TIMING  Pulling base image layer sha256:408ad02cbf46b38f36ac42c09d911cf359a5be4dc3fee6e5956b1e4f96e98bdf
[DEBUG] TIMED   Pulling base image layer sha256:408ad02cbf46b38f36ac42c09d911cf359a5be4dc3fee6e5956b1e4f96e98bdf : 964.0 ms
[DEBUG] TIMING  Preparing application layer builders
[DEBUG] TIMED   Preparing application layer builders : 1.0 ms
[INFO] Building dependencies layer...
[DEBUG] TIMING  Building dependencies layer
[DEBUG] TIMED   Building dependencies layer : 16.0 ms
[INFO] Building resources layer...
[DEBUG] TIMING  Building resources layer
[DEBUG] Building resources layer built sha256:40230baf97c5b3d6f026fc9f734a12b9b485c7337d15c5c35e8a3e3ba7eab64f
[DEBUG] TIMED   Building resources layer : 56.0 ms
[INFO] Building classes layer...
[DEBUG] TIMING  Building classes layer
[DEBUG] TIMED   Building classes layer : 3.0 ms
[DEBUG] TIMING  Building container configuration
[INFO]
[INFO] Container entrypoint set to [java, -Xms512m, -XX:+UnlockExperimentalVMOptions, -XX:+UseCGroupMemoryLimitForHeap, -Dspring.profiles.active=production, -cp, /app/resources:/app/classes:/app/libs/*, com.zl.wzgp.Launcher]
[DEBUG] TIMED   Building container configuration : 1.0 ms
[DEBUG] TIMING  Preparing layer pushers
[DEBUG] TIMED   Preparing layer pushers : 0.0 ms
[DEBUG] TIMING  Preparing layer pushers
[DEBUG] TIMED   Preparing layer pushers : 0.0 ms
[DEBUG] TIMING  Pushing BLOB digest: sha256:8b37076acdbeb0264388f03aefe4a023d47fc59c426df22c6a4268ae07b5d280, size: 39479382
[DEBUG] BLOB : digest: sha256:8b37076acdbeb0264388f03aefe4a023d47fc59c426df22c6a4268ae07b5d280, size: 39479382 already exists on registry
[DEBUG] TIMED   Pushing BLOB digest: sha256:8b37076acdbeb0264388f03aefe4a023d47fc59c426df22c6a4268ae07b5d280, size: 39479382 : 1143.0 ms
[DEBUG] TIMING  Pushing BLOB digest: sha256:40230baf97c5b3d6f026fc9f734a12b9b485c7337d15c5c35e8a3e3ba7eab22f, size: 4250
[ERROR] I/O error for image [us.gcr.io/zl-ln-wz/zl-wzgp]:
[ERROR]     Operation timed out (Read failed)
[DEBUG] TIMED   Pushing BLOB digest: sha256:40230baf97c5b3d6f026fc9f734a12b9b485c7337d15c5c35e8a3e3ba7eab22f, size: 4250 : 43745.0 ms
[DEBUG] TIMING  Pushing BLOB digest: sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6, size: 45543
[DEBUG] TIMING  pushBlob
[DEBUG]         TIMING  pushBlob POST sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6
[DEBUG]         TIMED   pushBlob PATCH sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6 : 427.0 ms
[DEBUG]         TIMED   pushBlob PUT sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6 : 3646.0 ms
[DEBUG]         TIMED   pushBlob POST sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6 : 8499.0 ms
[DEBUG] TIMED   pushBlob : 12572.0 ms
[DEBUG] TIMED   Pushing BLOB digest: sha256:c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a99c6, size: 45543 : 54100.0 ms
[DEBUG] TIMING  Pushing container configuration
[DEBUG] TIMING  Pushing BLOB digest: sha256:dff9b703c0343d28d384747d74159f1a57cd947bd0abebc09d138ab6f448602f, size: 1736
[DEBUG] BLOB : digest: sha256:dff9b703c0343d28d384747d74159f1a57cd947bd0abebc09d138ab6f448602f, size: 1736 already exists on registry
[DEBUG] TIMED   Pushing BLOB digest: sha256:dff9b703c0343d28d384747d74159f1a57cd947bd0abebc09d138ab6f448602f, size: 1736 : 678.0 ms
[DEBUG] TIMED   Pushing container configuration : 715.0 ms
[DEBUG] TIMED   Building and pushing image : 112051.0 ms
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:54 min
[INFO] Finished at: 2019-09-21T22:51:52+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.6.1:build (default-cli) on project us.gcr.io/zl-ln-wz/zl-wzgp: Operation timed out (Read failed) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.6.1:build (default-cli) on project us.gcr.io/zl-ln-wz/zl-wzgp: Operation timed out (Read failed)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Operation timed out (Read failed)
at com.google.cloud.tools.jib.maven.BuildImageMojo.execute (BuildImageMojo.java:158)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.net.SocketException: Operation timed out (Read failed)
at java.net.SocketInputStream.socketRead0 (Native Method)
at java.net.SocketInputStream.socketRead (SocketInputStream.java:116)
at java.net.SocketInputStream.read (SocketInputStream.java:171)
at java.net.SocketInputStream.read (SocketInputStream.java:141)
at sun.security.ssl.InputRecord.readFully (InputRecord.java:465)
at sun.security.ssl.InputRecord.read (InputRecord.java:503)
at sun.security.ssl.SSLSocketImpl.readRecord (SSLSocketImpl.java:975)
at sun.security.ssl.SSLSocketImpl.readDataRecord (SSLSocketImpl.java:933)
at sun.security.ssl.AppInputStream.read (AppInputStream.java:105)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer (AbstractSessionInputBuffer.java:161)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer (SocketInputBuffer.java:82)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine (AbstractSessionInputBuffer.java:278)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead (DefaultHttpResponseParser.java:138)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead (DefaultHttpResponseParser.java:56)
at org.apache.http.impl.io.AbstractMessageParser.parse (AbstractMessageParser.java:259)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader (AbstractHttpClientConnection.java:286)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader (DefaultClientConnection.java:257)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader (AbstractClientConnAdapter.java:230)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse (HttpRequestExecutor.java:273)
at org.apache.http.protocol.HttpRequestExecutor.execute (HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute (DefaultRequestDirector.java:684)
at org.apache.http.impl.client.DefaultRequestDirector.execute (DefaultRequestDirector.java:486)
at org.apache.http.impl.client.AbstractHttpClient.doExecute (AbstractHttpClient.java:835)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute (CloseableHttpClient.java:56)
at com.google.api.client.http.apache.ApacheHttpRequest.execute (ApacheHttpRequest.java:65)
at com.google.api.client.http.HttpRequest.execute (HttpRequest.java:1011)
at com.google.cloud.tools.jib.http.Connection.send (Connection.java:197)
at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call (RegistryEndpointCaller.java:270)
at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.callWithAllowInsecureRegistryHandling (RegistryEndpointCaller.java:186)
at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call (RegistryEndpointCaller.java:163)
at com.google.cloud.tools.jib.registry.RegistryClient.callRegistryEndpoint (RegistryClient.java:474)
at com.google.cloud.tools.jib.registry.RegistryClient.checkBlob (RegistryClient.java:330)
at com.google.cloud.tools.jib.builder.steps.PushBlobStep.call (PushBlobStep.java:81)
at com.google.cloud.tools.jib.builder.steps.PushLayerStep.call (PushLayerStep.java:95)
at com.google.cloud.tools.jib.builder.steps.PushLayerStep.call (PushLayerStep.java:34)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly (TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:69)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run (TrustedListenableFutureTask.java:78)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute (MoreExecutors.java:322)
at java.util.concurrent.AbstractExecutorService.submit (AbstractExecutorService.java:134)
at com.google.common.util.concurrent.AbstractListeningExecutorService.submit (AbstractListeningExecutorService.java:66)
at com.google.common.util.concurrent.AbstractListeningExecutorService.submit (AbstractListeningExecutorService.java:36)
at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:193)
at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:948)
at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:482)
at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:472)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:566)
at com.google.cloud.tools.jib.builder.steps.StepsRunner.scheduleCallables (StepsRunner.java:423)
at com.google.cloud.tools.jib.builder.steps.StepsRunner.lambda$pushApplicationLayers$11 (StepsRunner.java:360)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly (TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run (InterruptibleTask.java:69)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run (TrustedListenableFutureTask.java:78)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute (MoreExecutors.java:322)
at java.util.concurrent.AbstractExecutorService.submit (AbstractExecutorService.java:134)
at com.google.common.util.concurrent.AbstractListeningExecutorService.submit (AbstractListeningExecutorService.java:66)
at com.google.common.util.concurrent.AbstractListeningExecutorService.submit (AbstractListeningExecutorService.java:36)
at com.google.cloud.tools.jib.builder.steps.StepsRunner.pushApplicationLayers (StepsRunner.java:358)
at java.util.ArrayList.forEach (ArrayList.java:1257)
at com.google.cloud.tools.jib.builder.steps.StepsRunner.run (StepsRunner.java:175)
at com.google.cloud.tools.jib.api.Containerizer.run (Containerizer.java:324)
at com.google.cloud.tools.jib.api.JibContainerBuilder.containerize (JibContainerBuilder.java:496)
at com.google.cloud.tools.jib.api.JibContainerBuilder.containerize (JibContainerBuilder.java:477)
at com.google.cloud.tools.jib.plugins.common.JibBuildRunner.runBuild (JibBuildRunner.java:226)
at com.google.cloud.tools.jib.maven.BuildImageMojo.execute (BuildImageMojo.java:108)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Hi @praveen4463.  This is a known issue (#691).  Your Jib build works after a docker-push as Jib skips layers that already exist in the remote registry.
Duplicate of #691

Hi @briandealwis, do you really think its a duplicate of #691? That issue is relates to expired credentials and 'unauthorized' exception while I am 'operation time-out'. Also, I am using the default distroless OpenJDK image not any large image like the other issue originally states.
How come it's a duplicate? I am curious.

I apologize: I leapt to a conclusion as you posted that the docker push took 13 minutes, and the common failure case there is credential expiry.
We know that Jib needs to be more robust in the face of network failures such as timeouts like you're reporting.  We have an issue open to retry pushes in the face of timeouts (#1409).  I'll add a note there that we should also investigate using chunked uploads.

Just wanted to answer your question below, just in case you didn't realize:

I am not able to understand the cause of this issue ... Can you please explain what could have made my build fail as everything look normal?

When a Java application makes network connections and/or read/write data, the application may set some timeout values for such network operations at the JVM level. And if such a network operation does not progress by the set timeout, the JVM network stack cuts off the operation. In your case, a simple HTTP GET connection to GCR (not even uploading anything) timed out at the socket level after Jib was not able to read any data from the GCR server in a "timely" fashion, hence the following failure:
Caused by: java.net.SocketException: Operation timed out (Read failed)
at java.net.SocketInputStream.socketRead0 (Native Method)
...
at com.google.cloud.tools.jib.registry.RegistryClient.checkBlob (RegistryClient.java:330)

From your accounts and logs, looks like it is your network that is universally slow, not that Jib's network operations are unexpected slow.
You can increase the Java net timeout values to whatever you want for Jib (for example, -Djib.httpTimeout=600000 for 10 minutes). However, your OS kernel may impose various additional network timeouts at the operating system level (outside a JVM).
BTW, it is a bit surprising that a simple HTTP GET may actually time out in your environment. If I were you, I would avoid using GCR, given the extreme degree of unreliability.

I think @chanseokoh specifically means network unreliability.

@chanseokoh Thanks for looking into it, I agree with some of your observations regarding the read operation failure but its worth noting from the logs that jib was able to push all layers except just one 40230baf97c5b3d6f026fc9f734a12b9b485c7337d15c5c35e8a3e3ba7eab22f where an I/O error occurred and due to that it termed the whole operation as a failure. Let me explain this in detail:
There were 4 layers and jib tried to push them one by one to GCR, it first read the registry to see if a layer exists, if exist and same, it skips the push otherwise it tries to push. Here are those layers as per my log,
8b37076acdbeb0264388f03aefe4a023d47fc59c426df22c6a4268ae07b5d280 - already exists on registry (pushed successfully by last build failure), size 39479382
40230baf97c5b3d6f026fc9f734a12b9b485c7337d15c5c35e8a3e3ba7eab22f - I/O error, Operation timed out, after spending 43745.0 ms (over 43 seconds), size 4250
c6c66cab87735c35fa5845823954ed52b01d1df7c7a064a655ae98eb1f2a11c6 - pushed  successfully during the build, size 45543
dff9b703c0343d28d384747d74159f1a57cd947bd0abebc09d138ab6f448602f - already exists on registry (pushed successfully by last build failure), size 1736
so the layer starting with '402' specifically was the one that failed. Let's now work on why that layer failed. Please read the exception from the bottom to see what was on the stack before the I/O exception occurred. I can read that jib invoked GCR to check the layer, it got a response, but probably that response was not what jib expected leading to failure in reading within allotted time.
`at com.google.cloud.tools.jib.registry.RegistryClient.checkBlob
at com.google.cloud.tools.jib.registry.RegistryClient.callRegistryEndpoint
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer
at sun.security.ssl.SSLSocketImpl.readRecord (SSLSocketImpl.java:975)
at sun.security.ssl.InputRecord.readFully (InputRecord.java:465)
at java.net.SocketInputStream.socketRead0 (Native Method)
Caused by: java.net.SocketException: Operation timed out (Read failed)`
So, it seems the issue is not with the network but with the code that reads the response from registry, probably some encoding issue, wrong calculation of input stream size or something else that's causing the read failure after a response is received. There doesn't really seems anything with the network to me.
Also, looks like there is no retry mechanism in jib after such a failure where jib try to read from the registry again in hope of getting expected response just like docker did. if you read my comments regarding docker push, you will note that I said docker got stuck on a particular layer for several minutes, it failed on that and reattempted as well, before it was able to push it.
So my observation says, it is not my network fault really or something that I and GCR has any connectivity issues (cause I do lot of stuff on GCR only, for example starting tens of VM's together, sql operations, pushing big files to buckets etc. without any issue). It could be something within the 'layer read operation within jib' that might need to be fixed.
Regarding increasing the timeout, I had already made it to 10 minutes that day but it failed around the same time when it was 1 minute, which tells that it's something within the 'response read' operation of jib and not related with network.
please let me know what you think. Can this be reopened and looked into?

@praveen4463 at this point, the evidence points at network issues:

Your docker push encountered a failure mid-way.  Jib's jib:build does not use Docker, so Docker encountering a failure in push is a red flag.
Your push took 13 minutes.  I just pushed a test app based on distroless/java to GCR and it took 7s.
You are using Jib 1.6.1, which uses versions of Google HTTP Client and Apache HTTP Client that have been well-tested and validated by us.
We test Jib against GCR extensively and do not see similar issues.

If you can provide a reproducible test case we can definitely look at it more.  It might be better to try using Wireshark or some other networking tool to to investigate underlying network reports.

@briandealwis I heard you there, I'll try do investigate that way and inform if something is worth sharing.
Thanks for your time

@chanseokoh

It is unclear to me from which part of the log above or by what kind of reasoning you came to the conclusion that Jib got some kind of "response"
Sorry, I think its clear now that it failed before a chunk was filled into buffer, I read readLine/fillBuffer and came to conclusion that a response was received but it seems those several method calls during socket read operation that were on stack before the exception.

The blob check HTTP GET is only for checking if a layer exists on the registry. The server does not return any content but rather just returns an HTTP code. There isn't a layer or something else to read. Jib just checks the return code.
Oh, I got you, didn't know it checks just the return code, but I was also not specifically expecting it to read a returned layer, I thought it matches the hash of it that was returned by the server to see whether its stale or latest.

Thanks for those insights, I'll try some more build and let you guys know if anything is reproducible given I get a similar issue.
Thanks for the workarounds as well, I'd implement the first one to invoke jib in a loop.

As I said, often you need to lift the timeouts imposed by the kernel. On my machine for example, I found the connection timeout is set to 30 seconds, so setting the timeout over 30 seconds at the JVM level is meaningless.
Yeah I remember you said that in last post, that's a good piece of information. I'll bump that too.

Thanks again!


[WIP] Make the generic composition details relative addresses

Marking this as WIP because eventually I'll need to submit this through the TFS side and update rhbind as well. I would like to do most of the code review through Git though because CoreRT is just a nicer place to prototype in.
I'm looking at size regressions between .NET Native 1.7 and the current mainline branch. A thing that stood out is universally bigger EETypes. A contributor to this was getting rid of GenericInstanceDescs between 1.7 and 2.0 and replacing them by direct references to generic composition details from the EEType. Size-wise, this was mostly a wash, but we can actually do better - these new fields are not critical to be pointer-sized.
This change turns them into relative pointers. This saves 33 kB on a hello world app. I expect around 100 kB savings on the UWP People app based on my back-of-the-envelope calculation.
We could apply the same treatment to the optional fields pointer and the generic composition data.

I like it. I think its worthwhile doing the rest of the changes through the tfs side.

Will need to check in through TFS.


Introduce ConsumerGroups

Hi,
I've been trying to extract some of the lessons from https://github.com/bsm/sarama-cluster into a general purpose, low-level consumer group and would like to get some feedback on the approach.
An implementation of sarama-cluster with the proposed API would look something like this:
func main() {
	config := NewConfig()
	config.Version = V0_10_1_0

	// Init client
	client, err := NewClient(kafkaBrokers, config)
	if err != nil {
		log.Fatalln(err)
	}
	defer client.Close()

	// Init consumer manager
	consumerManager, err := NewConsumerFromClient(client)
	if err != nil {
		log.Fatalln(err)
	}
	defer consumerManager.Close()

	// Init offset manager
	offsetManager, err := NewOffsetManagerFromClient("my_group", client)
	if err != nil {
		log.Fatalln(err)
	}
	defer offsetManager.Close()

	// Init consumer group
	group := NewConsumerGroupFromClient("my_group", client)
	defer group.Close()

	// Start rebalance/consume loop
	wg := new(sync.WaitGroup)
	for {
		sess, err := group.Subscribe([]string{"topic-a", "topic-b"})
		if err != nil {
			log.Fatalln(err)
		}

		// Consume each partition in a separate goroutine
		for topic, partitions := range sess.Claims() {
			for _, partition := range partitions {
				offsets, err := offsetManager.ManagePartition(topic, partition)
				if err != nil {
					log.Fatalln(err)
				}

				offset, _ := offsets.NextOffset()
				consumer, err := consumerManager.ConsumePartition(topic, partition, offset)
				if err != nil {
					log.Fatalln(err)
				}

				wg.Add(1)
				go func() {
					defer wg.Done()
					consume(sess, consumer, offsets)
				}()
			}
		}
		wg.Wait()
	}
}

func consume(sess ConsumerGroupSession, consumer PartitionConsumer, offsets PartitionOffsetManager) {
	defer sess.Release()
	defer offsets.Close()
	defer consumer.Close()

	for {
		select {
		case msg := <-consumer.Messages():
			log.Printf("%#v", msg)
			offsets.MarkOffset(msg.Offset, "")
		case <-sess.Done():
			return
		}
	}
}

What do you think?

Perhaps I'm missing a use case, but why distinguish ConsumerGroup from ConsumerGroupSession when you can only ever have one session anyway? I would think you could merge those and have NewConsumerGroup take the list of topics.

Also feel free to split the JoinGroup api updates into a separate PR, they're useful regardless of what happens here.

So actually, I can see no better way. The consumer group is effectively an iterator over sessions. Obviously, I could move the topics argument to NewConsumerGroup, but I have been frequently asked for a new feature on sarama-cluster to allow users to change the topic subscriptions without restarting the (cluster) consumer, that's why I have decided to put it on the session initialiser.

allow users to change the topic subscriptions without restarting the (cluster) consumer

Are there actually benefits to doing this in terms of connection/metadata setup or whatever?
reads...
Oh, the memberID is persisted in the Group itself. I didn't realize that the Group carried any state between sessions. That makes sense.
Wait, is it even possible to change the topic subscriptions broker-side without introducing a whole new group ID? How can the broker coordinate if the different group members subscribe to different topics entirely?

Close() the session

In your sample this is called Release I think? And if I'm reading properly, it's wrong because it will get called for every partition (including the first), instead of only when all partition consumers are done?

The consumer group is effectively an iterator over sessions.

So I suppose the issue with something like func (*ConsumerGroup) Sessions() <-*Session is that you can't subscribe to the next session until the previous one is closed, which must be manually called anyway once all the various partition-consumers are shut down and offsets committed.

I wonder if it makes sense to have ConsumerGroupSession.Release(topic, partition) and track final state internally instead of making the caller use a WaitGroup?
And then ConsumerGroup.Subscribe could return a <-Session you can actually range over. If you really want to support switching up the set of topics you could add a ConsumerGroup.Unsubscribe() which closes that channel?
I'm not sure if these ideas actually end up making sense in practical usage, but I think they would make your sample sarama-cluster implementation a little simpler and more robust.

One idea is to make Subscribe this the previous session, if one exists. It would make things more fluid but also less obvious. I thought about exposing the iterator via a Sessions() channel before, but yes, error handling would be quite annoying.

... make Subscribe close/release...

@eapache I have created a high-level consumer (which would be sarama-cluster v3) on top of this patch - https://github.com/bsm/sarama-cluster/pull/234. What do you think?

here's the CLI example
and the README

NewOffsetManagerFromClient
hi dim，whereit

Closing in favour of #1099


jetpack-4.4 for jetson tx2 :run     sudo python3 trt_mtcnn.py --xxx  error

AttributeError: 'Camera' object has no attribute 'open'

HI,
After my test, GoogleNet can run normally. But MTCNN failed to run, and the error message is as shown in the figure above. The version is already up to date

This is indeed an oversight on my part.  I forgot to update "trt_mtcnn.py".
Thanks for reporting this issue.  I have fixed the code now.


refactor auth context and navigator

app using only 1 store for storing user data:
token is stored in user device
user status and user data is stored in app state


It is impossible to unfocus a client properly

This behaviour would be expected when you switch to a screen, which doesn't display any clients (and whose current tagset's clients aren't displayed anywhere else). However, if you now press keys not grabbed by the window manager, they get passed to the client previously focused on the other screen.

This is due to mouse focus, at least partly.


Improve form-for documentation (model vs controller)

What is the difference between calling {{form-for model}} and {{form-for controller}}?
Some examples use model and some use controller.  I have found that validations don't work properly when you use model.  Is there any reason to use model over controller?

In previous versions, the context of the form was not very clear. In the most recent version it will always use the model passed to the form-for component.

You can get the most recent version of ember-easy-form on the branch 1-0-stable or as an ember-addon here.
Make sure to read the README and CHANGELOG on the 1-0-stable branch.


Make readPlaylist method usable from other JVM languages

Currently it's not possible to call the readPlaylist method from Clojure and possibly from other JVM languages because the AbstractPlaylistParser class is package private.
Would it be possible to make it public?

Hi!
Why do you want to use the AbstractPlaylistParser directly? Have you tried
to use MasterPlaylistParser and MediaPlaylistParser?

Hi!
Actually I'm just trying to use MasterPlaylistParser as described at https://github.com/carlanton/m3u8-parser#parse-master-playlist - executing the following code
(let [player (MasterPlaylistParser.)]
    (.readPlaylist
      player
      (Paths/get (URI. "file:///./manifest.m3u8"))))

throws:
Execution error (IllegalArgumentException) at clj-carlanton-m3u8-parser-test.minimal-repro/eval1577 (minimal_repro.clj:2).
No matching method readPlaylist found taking 1 args for class io.lindstrom.m3u8.parser.MasterPlaylistParser

For this specific case, making AbstractPlaylistParser public will fix the
problem. This should have no impact on other code. The class will
still not be instantiable because it is also abstract.
Please see more details about this issue at https://github.com/netty/netty/issues/1780 and https://stackoverflow.com/a/36999820/9615

Well that's a weird bug! Fixed in 0.11 which should be on maven in ~1 hour or so.
Thanks,
Anton

Thank you!


minor bug fix

fixed issue with opening body files

Codecov Report

Merging #13 (2314c0f) into main (35d522b) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main     #13   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          4       4
  Lines        553     551    -2
=====================================
+ Misses       553     551    -2

Impacted Files
Coverage Δ

vspace/vspace.py
0.00% <0.00%> (ø)

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 35d522b...2314c0f. Read the comment docs.


Profile - Messaging an account not created will display an unconfirmed time zone

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app and login
Start a chat with an account not created yet
Tap on its profile icon

Expected Result:
Profile is opened and only confirmed information is shown
Actual Result:
Profile tab is opened and it shows PST time zone, which is an information not known nor confirmed
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.16-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/143069648-49d48994-a73f-4b26-a45c-7a4f588184ee.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

I would say that I already raised it here https://github.com/Expensify/App/issues/4771 but CME was not able to reproduce it at that time. Probably we can now with these steps.
So I suggest opening that issue and adding this info to that issue.

Just tried to reproduce, couldn't reproduce on dev, staging, or prod. Could have been fixed?


ParseBoxes length checks should occur before callback and ParseHeader

Was reviewing ParseBoxes()
https://github.com/takakia/lovok/blob/5feb55f85afcf401d7c261c461a6f1bea944ad78/src/lovok_handle_internal.cpp#L71
length is unsigned, so length < 0 will never occur.
https://github.com/takakia/lovok/blob/5feb55f85afcf401d7c261c461a6f1bea944ad78/src/lovok_handle_internal.cpp#L74
I think we need to do size checks to verify ParseHeader is safe here and doesn't exceed length.
https://github.com/takakia/lovok/blob/5feb55f85afcf401d7c261c461a6f1bea944ad78/src/lovok_handle_internal.cpp#L80
The AddOverflow and SubtractOverflow will cover the case where the callback read more than it can chew ...  But I think those length checks should occur first, before calling the callback.
Stretch goal: Actually, I think the safest bet would be if the callback got a restricted file stream that doesn't even let it read past the end of a box ...  This could be enforced with the I/O callback mechanism.

Seems like pull request #93 moves the overflow check before the callback as I've suggested.

I will take up the remaining work for this in a separate PR from #93.


Update testing SQL commands for deploying to GCE

Update command to show correct SQL query for testing correct GCE deployment.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7b81029d3f9977f9e725070238528c54e25d5aa9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7b81029d3f9977f9e725070238528c54e25d5aa9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7b81029d3f9977f9e725070238528c54e25d5aa9/


Fix log message for integration test when env is not found

The correct log message appears now when env file not exists

Test Comment


Dropdown stick to bottom

Select dropdown stick to bottom positioned incorrectly if page will be scrolled

maybe i don't understand something but i just comment this stuff in line 691
// if the dropdown's bottom border is beyond window's edge then move the dropdown to the top so that it fits
if (dropdownOffset.top + dropdownOuterHeight > windowScroll + windowHeight) {
    dropdownOffset.top = windowScroll + windowHeight - dropdownOuterHeight;
}


WslRegisterDistribution failed with error: 0x80370102

Version
Microsoft Windows [Version 10.0.22000.282]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Start PowerShell (Admin).
Run "wsl --install -d ubuntu"
Expected Behavior
Install successfully.
Actual Behavior
It shows:
"Ubuntu is already installed.
Launching Ubuntu..."
Then in a new command window:
"Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.
Press any key to continue..."
Diagnostic Logs
No response

try to create any virtual machine via hyper-v

is virtual machine platform enabled?

try to create any virtual machine via hyper-v

Creating any virtual machine via Hyper-V also fails, with error "The Virtual Machine Management Service failed to start the virtual machine 'New Virtual Machine' because one of the Hyper-V components is not running".

is virtual machine platform enabled?

Yes, it is enabled.

try to create any virtual machine via hyper-v

Creating any virtual machine via Hyper-V also fails, with error "The Virtual Machine Management Service failed to start the virtual machine 'New Virtual Machine' because one of the Hyper-V components is not running".

bro i have literally the same problem and also don't know how to fix that. are u using win11 or 10? did u do some kind of system optimizations?

try to create any virtual machine via hyper-v

Creating any virtual machine via Hyper-V also fails, with error "The Virtual Machine Management Service failed to start the virtual machine 'New Virtual Machine' because one of the Hyper-V components is not running".

bro i have literally the same problem and also don't know how to fix that. are u using win11 or 10? did u do some kind of system optimizations?

I am using win11, version 10.0.22000.282. I am not aware of any system optimizations.

try to create any virtual machine via hyper-v

Creating any virtual machine via Hyper-V also fails, with error "The Virtual Machine Management Service failed to start the virtual machine 'New Virtual Machine' because one of the Hyper-V components is not running".

bro i have literally the same problem and also don't know how to fix that. are u using win11 or 10? did u do some kind of system optimizations?

I am using win11, version 10.0.22000.282. I am not aware of any system optimizations.

Hmm, interesting. I thought the reason was that I used to disable various unnecessary services, including through the registry, and the problem is that. but since you say that you didn’t do that, then I’m not sure anymore.

I'm having similar problems, but not sure if our sysadmins have some sort of setting that is blocking it. All Virtual settings are turned on, I followed the command line commands for older versions of Windows, and triple checked my bios settings.

Make sure virtualization is enabled in BIOS firmware.

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

interesting.  this may be true, since I was updating Windows 11 over Windows 10, and therefore vbs should have remained off for me

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

Nah, still doesn't work

I also have this problem. WslRegisterDistribution failed with error: 0x80370102
wsl --install -d Ubuntu-20.04
I am running AMD Ryzen 5 3600 (has support for AVX, AVX2).
With ROG STRIX B450-F GAMING. The feature SVM MODE is enabled.
Windows 11 64bit (upgraded from windows 10 64 bit) Swedish language pack installed.
And everything is up to date (atleast via windows update and wsl --update)

@Holight @rickhenderson @blixten85 I solved the problem for myself. in the device manager in the system devices section, some devices associated with virtualization and hyper-v were turned off. I turned them on and ubuntu started working

@Holight @rickhenderson @blixten85 I solved the problem for myself. in the device manager in the system devices section, some devices associated with virtualization and hyper-v were turned off. I turned them on and ubuntu started working

Thanks for sharing!
I solved my issue by turning on Hyper-V in windows feature section of the controll panel (under applications). It was not named Hyper-V though. It's a swedish transnaltion but it reads translated directly to english, "Windows-Hypervision platform and Platform for virtual computers).
It would be handy though if the operatingsystem itself could recognize the error and where the solution lies. After all, it's 2021 and this should have been mandatory for the past 25 years, in my holy opinion.

Resolved for me by enabling in BIOS: Intel Virtualization and Intel VT-D

I turned on

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

you are my personal hero, I've been trying to fix this problem for 8 hours straight, you are the first person actually fixing the problem!

I had the same problem.
Then I uninstalled and re-installed following this tutorial and it worked.
To follow this tutorial, your OS build number must be higher than 22000 (Windows menu > about your PC > OS build), otherwise, you should follow this one instead.

Reg hack worked for me, thank you folks, been doing my head in for ages
Windows Registry Editor Version 5.00
; Created by: Shawn Brink
; Created on: April 11th 2018
; Tutorial: https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity]
"Enabled"=dword:00000001

For me this actions worked

settings -> search "device security" -> Core isolation -> turn on
Added Windows component: Virtual machine platform (settings/applications/additional components/other components) on Win11 or try Hyper-V on Win10

I can't believe that actually worked for me!  I lost hours on this. thank you

I am getting the same error for different reasons, Actually, I had ubuntu installed and it was working fine. I just forget the admin user password after many failed reset attempts, I decided to uninstall. Now when I am trying to reinstall I am getting the same error mentioned in the thread title. I tried all Solutions mentioned above and still can't be able to proceed with the installation.
Bios checked: Hyper V Enabled and Core Isolation checked.

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

This didn't work for me, but for some reason the future kept turning off when I restarted...

It worked for me when I set both "Enabled" values to 1:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\KernelShadowStacks
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Okay so I've tried few tips from here on how to resolve the problem.
I've got this issue "please enable the virtual machine platform windows feature and ensure virtualization is enabled in the bios ".
Let me guide you the steps that I've done.

Open "windows feature", activate "Windows Subsytem for Linux" --> will need to restart pc.
Install Ubuntu from this link https://ubuntu.com/wsl.
Open the Ubuntu and it will give the link to update wsl. Open the link.
After finished installing/updating, open the Ubuntu and it will show this problem "please enable the virtual machine platform windows feature and ensure virtualization is enabled in the bios " (even though your system already enabled both).
Search for Windows for "Core isolation" and activate "Memory Integrity". If cannot turn on, then open this link "https://www.windowsdigitals.com/memory-integrity-cant-be-turned-on-windows-11/". --> will need to restart pc.
After that, Open "windows feature", activate "Windows Hypervisor Platform" & "Virtual Machine Platform". --> will need to restart pc.
Open Ubuntu and it should be running smoothly.

I found a too simple solutions that somehow works.
So, If you already:

enabled Virtualization on Bios and on Windows Features.
enabled Windows Hypervisor Platform or Hyper-V
enabled Windows Subsystem for Linux

just disable all of the above on Windows Features. Not BIOS. Then restart. now open the Windows Features and enabled all of these options again. Restart.
And now you can just wsl --install or wsl --install -d Ubuntu_of_your_choice and it should work. Also make sure you run the Terminal as Admin

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".

 This article shows that workaround and this is also the thing that ended up fixing the issue for me.
Not speaking to anyone in this thread specifically, just leaving this here in case this ends up helping someone

Everyone suggests the items that are in the standard instructions. I had the exact same problem and today I found out it was related to Virtualization Based Security (VBS). Search Windows for "Core isolation" and activate "Memory Integrity".
Worked perefectly for me (Windows 10).

Thank you so much. I saved tonns of hours for me


Unmanaged pod failure reason is missing

Example: Pod/db-migrate-215a39ad-e344fa2b failed to deploy with status 'Failed (Reason: )

Fixed in passing in https://github.com/Shopify/kubernetes-deploy/pull/116. (We only add "Reason:" if one is available)


fix(types): fix global namespace declaration for UMD bundle

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
In the current declaration, index.d.ts has export as namespace Vue which exposes all exported types in index.d.ts in global namespace. So the user can access them by just writing like Vue.ComponentOptions without import statement.
But this declaration is actually not correct because the Vue constructor type is declared under default which is correct in ESModule bundle but UMD bundle.
new Vue({}) // This provides compilation error in current type.

new Vue.default({}) // No compilation error.

To declare Vue constructor as just Vue in global namespace, we need to write export as namespace Vue with a common js export. So I've add umd.d.ts and do that in that file.

This should not affect existing usage with ES modules right?

Right, it should not affect. The entry point (index.d.ts) exports are the same and if a file is ES module, global Vue is not available.


.clone() fix both parent and clone for session hash

with threading.Lock():
when clone

client = self.clone()


Packages renaming & multiple fixes

Renames FPA to FFS.
Renames FastAPI to API with api as shorthand.
Rename repo to Powergate

Repo name changed from .texfc to .powergate
Binaries changed from fil-tools(d) to pow(d)
Env var prefix changed from TEXFILTOOLS_ to TEXPOWERGATE_

Closes #169
Closes #170
Closes #171
Closes #173

There are some actual bug fixes and/or improvements in here, right? Can you point those out with a few comments just to make sure they don't get lost in the naming refactor changes?

@asutula , I left some extra comments about the fixes.
I'll merge just to unblock @andrewxhill , but feel free to take a look and I'll address if something pops up.


Dimensional array read/write support

I was facing an issue to read/write dimensional array in the variant variable with direct node access.
It looks like there was a TODO placeholder for dimensional arrays in the decoder. But encoding is also missing it.
https://github.com/awcullen/opcua/blob/387afc92a5036be1746dc5de147326c147efcf2e/ua/binary_decoder.go#L1294-L1296
I have made a comit https://github.com/awcullen/opcua/commit/348ab93c9d0ed861a744aed323758bca6dc952c1 in a forked branch with read/write example working.
It would be useful to have some kind of a structure to keep the information about additional properties of the Variant like this to be part of the variant.:
type VariantMetadata struct {
	//mask contains the type and the array flags
	//bits 0:5: built-in type id 1-25
	//bit 6: array dimensions
	//bit 7: array values
	EncodingMask          byte
	ArrayLength           int32
	ArrayDimensionsLength int32
	ArrayDimensions       []int32
}

I looked into https://github.com/gopcua/opcua library as alternative solution and used some of its array reconstruction method as well as flattened array read/write.
I hope my fork can help to add it here to the master branch eventually.
What do you think?
Let me know how you see it in the end, so I can adapt it for merging...

That TODO placeholder has been there for years.  Thank you for working out a solution.
Why would it be useful to add the metadata fields to Variant?
If we did would users need to use methods like ua.NewVariant() and value.Value() to wrap and unwrap a Variant?
I think your solution is elegant.

Hi Andrew,
@awcullen, you did a commit, did you fix this?

I added support to encode a Variant with a 2D or 3D matrix value (from 2D or 3D slices).
I still need to support encoding Structure with a matrix property.
And then I would consider adding more dimensions.


[VM] Implement function tearoff equality corner cases

This is the VM specific version of https://github.com/dart-lang/sdk/issues/46834, which has the details.

//cc @alexmarkov


[BUG] - GPT-4 turbo not available anymore

Hi, i tried to deploy GPT-4 turbo in a number of regions but it seems unavailable.  I'm not sure if it is related but the indexing process keeps failing at 12,5%.
Can/should i use GPT-4o instead?

same issue with me

Same here

You can use GPT-4o, and you can also request a quota increase for GPT 4-turbo.
In Azure OpenAI Studio, under Quotas (left side) there is a column on the far right for "Request Quota" in a provided region.

Please create the Azure OpenAI service in a different region.


[Bug] [Operation and Maintenance Center] There is a problem with step reading and it is not accurate

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
运维中心获取的step不准确，我作业进入维护或者发布了或者上线了，在运维中心界面，生命周期的数据一直没变。因为他读取的dlink_job_instance里的step这个字段，但是这个字段在作业维护的时候没做维护。
What you expected to happen
我希望我作业维护的时候，生命周期的状态需要跟着走。
我自己修改了代码
task.setStep(JobLifeCycle.DEVELOP.getValue());
            this.updateTaskAndJobInstanceById(task);

private boolean updateTaskAndJobInstanceById(Task task) {
        boolean flg = updateById(task);
        if (flg) {
            JobInstance jobInstance = jobInstanceService.getJobInstanceByTaskId(task.getId());
            if (jobInstance != null) {
                jobInstance.setStep(task.getStep());
                jobInstanceService.updateById(jobInstance);
            }
        }
        return false;
    }

不知道是否正确
How to reproduce
在数据开发模块，对作业发布、维护。再去运维中心看。
Anything else
No response
Version
0.7.3
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The task of the operation and maintenance center is to Flink job instances rather than data development jobs.


Indication for Drag'n'Dropping multiple files

Is your feature request related to a problem?
It isn't clear that Files has the ability to drag and drop multiple files to the user, when he can only see one file following the mouse cursor while drag and dropping.
Describe the solution
An indication of having multiple files in the drag and drop
For Example by doing one or more of these things:

Doing it like a web browser with a transparency gradient
Showing a fading stack of files (the dragged file looks different according to view in files in contrast to windows explorer where it always is just a square, so maybe the appearance of the stack would have to adjust to that?)
Showing a number with the amount of files, for example where the "blocked" symbol is or beside

(I believe the blocked symbol should appear while just having the files in the same folder, because this isn't a illegal operation it just does nothing and the user expects it to be this way?)
Scope

Capability
Priority

This proposal will give users an indication that multiple files are getting moved
Must

This proposal will show users how many files are getting moved
Could

This proposal will disable the illegal action symbol while staying in the same folder with drag and drop
Could

Additional comment

App Version: <IP_ADDRESS>

@winston-de can we change the icon to indicate multiple items are selected?

@yaira2 Which icon?

If you mean the 🚫 icon, I don't believe you can because that's managed by the system. There is a count already shown, however.

File Explorer shows an icon of the item being dragged.

I'm sure with WinUI 3 you could find some other API to use for drag and drop to make it more customizable. But unfortunately with the UWP APIs we are currently using the options are very limited.

Thank you for your feedback, the latest version of Files displays a number indicating how many items are being dragged..


Update: Turkish translations.

Translations will be updated in this PR until completely done.

Could you submit those directly on our Weblate instance? https://hosted.weblate.org/projects/godot-engine/godot/
The translations in git are then synced every now and then from Weblate, so merging PRs directly would make this workflow a bit harder.

Also, unless Turkish from Turkey is very different from "global" Turkish, I would advise to drop the _TR part and let this be the global Turkish translation. It's a lot of work if different translators have to maintain tr_TR, tr_IR, tr_BG, tr_DE, etc. If those distinctions are important, they could then be created by copying the "global" Turkish one and adapting what needs to be.

I changed it to global within second 10% of all lines. I don't have Weblate account so if it wouldn't be problem, i want to continue translate it within this pr. (10% by 10%)

Well as you can see on Weblate there's already a work-in-progress Turkish translation, so it would be really best to handle it all here. It's an open source hosted service so you can make an account for free.
I'm not particularly looking forward to having to merge manually conflicts between your translation in git and that of the other translators in Weblate :)


add a drop down menu for a table of contents at the top of an article similar to the categories ones

add a drop down menu for a table of contents at the top of an article similar to the categories ones like this:

heres my attempt at adding a table of contents on one of my articles but it takes up more than an entire page

damn


Create an API for search members in a team which are not exists into the team.

We need a new Member module.
Route: /api/v1/member/teamId?search=USER_EMAIL&is-member=false
Method: GET
In response list the active users of Sprint Planner who are not part of this team.

Issue is covered in ticket #2


add demo

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs update
What is the current behavior? (You can also link to an open issue here)
simple demo
What is the new behavior (if this is a feature change)?
detailed demo
Does this PR introduce a breaking change?
(what is "breaking change")
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
Add a more clear demo for the usage.

On Apr 28, 2016 8:27 AM, "Weijing Jay Lin"<EMAIL_ADDRESS>wrote:

What kind of change does this PR introduce? (Bug fix, feature, docs
update, ...)
docs update
What is the current behavior? (You can also link to an open issue here)
simple demo
What is the new behavior (if this is a feature change)?
detailed demo
Does this PR introduce a breaking change?
(what is "breaking change")
Please check if the PR fulfills these requirements
The commit message follows our guidelines:
https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
Tests for the changes have been added (for bug fixes / features)
Docs have been added / updated (for bug fixes / features)
Other information:
Add a more clear demo for the usage.

You can view, comment on, or merge this pull request online at:
https://github.com/angular/angular.js/pull/14528
Commit Summary
add demo
File Changes
M src/Angular.js (8)
Patch Links:
https://github.com/angular/angular.js/pull/14528.patch
https://github.com/angular/angular.js/pull/14528.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub


Fix provider for slice arguments. fix #8

Fix provider for slice arguments. This bug cause changes for variadic methods.
$ go test ./...
?       github.com/karlkfi/inject       [no test files]
ok      github.com/karlkfi/inject/test  0.007s
?       github.com/karlkfi/inject/test/variadic [no test files]

@karlkfi Would you be able to review this?

fmm...

I’m not sure I understand what bug this fixes. Can you add a test case?

Bug description is here.
Add support for variadic arguments on provider constructor by mumia · Pull Request #7 · karlkfi/inject
Example
func NewSomething(a, b int, c []int) Something

something.graph.Define(
        &something.Something,
        inject.NewProvider(
            something.NewSomething,
            0,
            1,
            []int{2,3,4,5},
        ),
    )

panic: arg 3 of type "[]int" cannot be assigned or converted to type "int" for provider constructor ...

It cause misunderstanding of slice to variadic arguments.
I'll try add test.

@karlkfi It was veeeeeeeeeeery late (sorry!!) but I added tests. 😄

Thanks!
Passed manual tests.
Got Travis working again (it's been a while).
Passed tests on Travis.


Example "esp-idf/examples/protocols/sockets/tcp_server" stops after accepting first connection (IDFGH-2002)

Environment

Development Kit:      [ESP32-Wrover-Kit]
Kit version (WroverKit): [v1]
Module or chip used:  [ESP32-WROOM-32]
IDF version: v4.1-dev-141-ga7e8d87d3
Build System: [CMake]
Compiler version: 8.2.0
Operating System:     [Linux]
Power Supply:  [USB]

Problem Description
After first connection from a client the example can not accept further bind on socket.
Detailed problem description
After first connection it is not possible to bind on the same socket.
The statement with accept() function should be moved into the inner while (1) as for the final if statement controlling the socket status.
Instead of:
static void tcp_server_task(void *pvParameters){
.....
while(1){
......
listen_sock=socket();
bind(listen_sock);
listen(listen_sock);
sock=accept(listen_sock);
while(1){
......
}
if (sock != -1) {
ESP_LOGE(TAG, "Shutting down socket and restarting...");
shutdown(sock, 0);
close(sock);
}
}
}
I would go like this:
static void tcp_server_task(void *pvParameters){
.....
while(1){
......
listen_sock=socket();
bind(listen_sock);
listen(listen_sock);
while(1){
sock=accept(listen_sock);
......
if (sock != -1) {
ESP_LOGE(TAG, "Shutting down socket and restarting...");
shutdown(sock, 0);
close(sock);
}
}
}
}
Expected Behavior
I (3017) example: Socket created
I (3017) example: Socket bound, port 3333
I (3017) example: Socket listening
I (5667) example: Socket accepted
I (5667) example: Received 14 bytes from <IP_ADDRESS>:
I (5667) example:  whatever....
E (5667) example: Shutting down socket and restarting...
I (12607) example: Socket accepted
I (12617) example: Received 18 bytes from <IP_ADDRESS>:
I (12617) example:  whatever 2nd....
E (12617) example: Shutting down socket and restarting...
Actual Behavior
I (3017) example: Socket created
I (3017) example: Socket bound, port 3333
I (3017) example: Socket listening
I (5667) example: Socket accepted
I (5667) example: Received 14 bytes from <IP_ADDRESS>:
I (5667) example:  whatever....
I (6997) example: Connection closed
E (6997) example: Shutting down socket and restarting...
I (6997) example: Socket created
E (6997) example: Socket unable to bind: errno 112
Steps to reproduce

build flash monitor example tcp_server
echo -ne "whatever........\r\n" | nc -w1 <IP_ADDRESS> 3333
echo -ne "whatever 2nd........\r\n" | nc -w1 <IP_ADDRESS> 3333

Code to reproduce this issue
original code on repository tcp_server.c

Thanks, this has been resolved recently, the fix should be in master branch soon.

Thank you

I have the same problem with tcp socket.

Once my client disconnects, or somekind of sending error occurs, socket fails to bind. I need to restart ESP to fix it.

Did you try to move into the inner while(1){ } cicle the accept() statement? Also the final if (sock != -1) { } statement should be placed there.
More recent versions of esp-idf fix the issue.

I have managed to make it work with moving while cycle according to master branch example.
Now it is like this
while{
Init address
call socket function
//Added from neweer exampele
int opt = 1;
setsockopt(listen_sock, SOL_SOCKET, SO_REUSEADDR, &opt, sizeof(opt));
///
bind
listen
while{
accept socket
while{
receive functions}
catch socket error and shutdown socket.
}


configure circulation

[x] Define get_document_by_item_pid, etc.
[x] Add a new endpoint to retrieve the loan status of an item

Loan status item can be retrieved from the item endpoint as it has information if a loan attached.


Gallery:  cannot upload package via drag-and-drop in Edge

async-file-upload.js uses FormData.set(…), which is not yet supported in Edge.
Analytics query:
exceptions
| where timestamp > ago(30d)
| where type == "Object doesn't support property or method 'set'"
    and assembly == "https://www.nuget.org/Scripts/gallery/async-file-upload.js"

This is a duplicate: https://github.com/NuGet/NuGetGallery/issues/5735


SProp compatibility

Cool!

Thanks!
 Why is the relevance attached to the name?
It doesn't really make sense to me, is it to limit the amount of changes required?
Is it following the Coq implementation in that respect?

Well, in some version (and that was my first attempt to port Template Coq) the relevance was an argument of the constructors of the term type. But later on, exactly as @TheoWinterhalter says, to make the changes less invasive, Gaëtan changed it to attached to names. That's how it worked when I ported it the second time before I left Nantes. I guess, it still stays the same, but I have not checked this.

I see. Thanks for the clarification. :)

This has now been merged through PR #511


07/09/2018 00:58 : Create Pull Request for branch master -> prTesting1_2018070900

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.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.


vdk-jupyter: make run before deploy optional

What: Added a checkbox button that determines whether the job will be run once before deployment.

Why: Currently, the job is always running but in some use cases the users might not want it.
Testing: modified the jest tests
Signed-off-by: Duygu Hasan<EMAIL_ADDRESS>

As usual for new UI elements, please provide a screenshot

Does this run it locally?
why would you want to run before deployment?
If you wanted to run it before deployment would you not just run it using the start button?

Does this run it locally? why would you want to run before deployment? If you wanted to run it before deployment would you not just run it using the start button?

Mainly to ensure that the deployed job will be green. Yes, it is always an option for them to run it manually like that this option is added just for convenience.
Imagine doing some config.ini changes, not changes in the code u might actually forget about running it again, this works both as reminder and if the run fails u get an error message and the job is not deployed, but if it is green u get no update on the run but directly the jo bis deployed


No events listeners appears

I don't if I'm doing it wrong or something is not good, but when Oh dear pushes webhook to the site nothing happens. Then I looked at Laravel Telescope Request and I see that it fires ohdear-webhooks::uptimeCheckFailed event, but it says that there is no event listeners.
So I added these two events listeners to my EventServiceProvider to temporary fix this issue:
Event::listen('ohdear-webhooks::uptimeCheckFailed', '\Spatie\OhDearUptimeTile\OhDearWebhooksEventSubscriber@onUptimeCheckFailed');
Event::listen('ohdear-webhooks::uptimeCheckRecovered', '\Spatie\OhDearUptimeTile\OhDearWebhooksEventSubscriber@onUptimeCheckRecovered');

Do you reach this code? (maybe put a dd statement there)
https://github.com/spatie/laravel-dashboard-oh-dear-uptime-tile/blob/master/src/OhDearWebhooksEventSubscriber.php#L33
If not, could you check if the service provider of the package gets loaded?

No, I can't reach this dd statement at this place
If I put dd statement here, I reach it
https://github.com/spatie/laravel-dashboard-oh-dear-uptime-tile/blob/master/src/OhDearUptimeTileServiceProvider.php#L16

I've found the problem, and fixed it in 1.0.2


perlPackages: MIMEtools and MIMETools

Motivation for this change
"MIME-tools" is duplicated as perlPackages.MIMEtools and perlPackages.MIMETools
@rycee this confuses the auto-updating script :)

Yeah, makes sense to remove one of them. I'm thinking the MIMEtools one should stay since the release is called MIME-tools.
At least MIMEtools is the attribute name that nix-generate-from-cpan produces.

also https://github.com/NixOS/nixpkgs/pull/36667 https://github.com/NixOS/nixpkgs/pull/36670

closed as being a part of https://github.com/NixOS/nixpkgs/pull/36147


Cannot clone nerdpack in NR1?

Description
I've been continuing to see an error when attempting to use the clone command within the repo:
›   Error: Cannot destructure property 'path' of 'flags' as it is undefined.
›   Code: UNKNOWN
This is from the command to clone the nerdpack:
nr1 nerdpack:clone -r https://github.com/newrelic/nr1-cloud-optimize.git
I've also confirmed NPM and Git are installed on the AWS Linux instance I'm using this on.  I've also been able to create a basic nerdpack of my own without issue, so it appears to be something odd with the sync process
Steps to Reproduce
On a Linux EC2 instance running Amazon Linux, begin by SSH'ing into the instance and ensuring git/npm are installed. Once complete run the command and you will see the resulting error above.
Expected Behaviour
For it to clone the repository and allow deployment deployment.
Relevant Logs / Console output
See above
Your Environment

NR1 CLI version used:   @datanerd/nr1/2.83.5 linux-x64 node-v16.11.1
Browser name and version:  none
Operating System and version: AWS Linux 2

Additional context
I was able to clone the repo with git, but it still errors out complaining of various fields not existing. when attempting to serve it to the new relic environment.

When you are local serving the app, you should do it from your local machine. The CLI will open a port that your local browser must interact with, as well as setup certs for security. So doing this on a headless linux EC2 over ssh won't really yield any result.
If you want to add this application to your account it is easier to just simply add it from the catalog.
However if you still do want to locally serve it, you should be doing it from you local machine, this method is typically used when developing or debugging or perhaps you have made some tweaks and then chosen to deploy your own modified version into your account.

Hi, I'm getting the same error when attempting to clone locally as well!
Command that I have run nr1 nerdpack:clone -r https://github.com/newrelic/nr1-cloud-optimize.git
Operating System - MacOS
Doing a clone via git clone also causes alot of npm errors when trying to serve


fixed LoadIdentity constructor

Fixed exception due to property expectation of dictionary instead of string. It seems that was a typo.

Hello. Are there any updates about this pull request? This fix is very simple and still actual (fixed small typo).

replaced by #3750


Lint for nameConstraints for dNSName and iPAddress

Presently, there are not lints on the well-formedness of the dNSName and iPAddress nameConstraints. There are lints for other name types, such as https://github.com/zmap/zlint/blob/fd40f579253ea1ebfb18a585ab5cd8e7dcde61aa/v2/lints/rfc/lint_name_constraint_on_edi_party_name.go or https://github.com/zmap/zlint/blob/fd40f579253ea1ebfb18a585ab5cd8e7dcde61aa/v2/lints/rfc/lint_name_constraint_on_x400.go , but none for dNSName or iPAddress.
Broadly, many of the dNSName checks applied to the SAN would also apply to the nameConstraints.
For example, see this discussion in the CA/B Forum, which pointed out that https://github.com/awslabs/certlint correctly detects the malformed name constraint on https://crt.sh/?sha256=A56C1BD2C47FFC701023FAD8F65CBE794946B779475848DCA30760A06DD72FD9 but ZLint does not

Erp, I missed the similarity to #136 due to also mentioning iPAddresses here.
I'm ok duping them, or keeping this separate to also lint the well-formedness of IP addresses.

Looks like zmap/zcrypto/x509 is already enforcing IP constraint validity during parsing.
Stdlib crypto/x509 does its own DNS name validity check, but disagrees that leading periods are invalid. See https://github.com/golang/go/issues/16347 for discussion of why this was allowed in stdlib.

@rolandshoemaker Thanks for pointing out the iPAddress. While that makes sure that the base value is parsable, I was thinking about other checks, such as making sure it's not an internal IP address. I filed https://github.com/cabforum/documents/issues/160 so that these requirements could be made more explicit, where they are presently implicit.
That said, the Golang change seems to be about compatibility with existing misissuance, while given ZLint's concern on correctness, seems not to be too compelling. That said, I filed https://www.rfc-editor.org/errata/eid5997 to try and clarify.

@sleevi while digging into this I found your filing at https://github.com/cabforum/servercert/issues/160 which brings up...

The existence of the "or" clause leaves it ambiguous...

Which screams of the same confusions brought up in https://github.com/zmap/zlint/issues/553 last month.
I may be a bit green WRT to what RFCs are out there, but I'm beginning to wonder if an RFC 2119 type document for boolean expressions in plain English prose would be a good idea. Because English is...painful.


feat(FTL-5593): add origin support

What changed

@affinidi/internal-api-clients:

Add origin support so that when making requests to Registry, it is passed;

@affinidi/wallet-core-sdk:

Update SdkOptions adding new optional field origin;
Pass origin to @affinidi/internal-api-clients;

Anton, thanks I'll address this in a separate PR in the Registry service.


Enhance GFList tile to include a row of optional text buttons at the bottom

Is your feature request related to a problem? Please describe.
This is just a suggest enhancement on the GF List tile
Describe the solution you'd like
Would like to have an option on the GFList tile to have a row of at least two text button or tags in the bottom row
Describe alternatives you've considered
I have explored using the card, option and I still find/think it would be neater to have this functionality has party of the GF List tile
Additional context

@ivansempijja
Thank you for your suggestion.

@ivansempijja ,Please use the latest version, we have included two optional buttons for GFList tile


Allow privileged ports in data types

502ff38c8c035fa143e32dd4ee61b3ec68db461c tightened the data types, but there's no reason to only allow unprivileged ports.

Updated. Now also updated instance.pp and regenerated REFERENCE.md.


Temporal Extent filter is not working correctly

When a user sets the Temporal Filter extent filter to a range with no metadata records (e.g. 07/12/2022), two unmoderated DCPR records that should not be public show up in the search results while the site says "0 metadata records found":

Fixing this issue will also fix an issue where Anonymous Users get asked to log in to view the two unmoderated records that show up when the site returns "0 metadata records found".

This issue has been fixed. When a user sets the Temporal Filter extent filter to a range with no metadata records (e.g. 07/12/2022), the unmoderated DCPR requests no longer appear (0 metadata records found and 0 records appear):


SSL error when trying to download artifacts with agent version [2.188.3]

Agent Version and Platform
2.188.3
OS of the machine running the agent?
Windows Server 2019
Azure DevOps Type and Version
dev.azure.com
What's not working?
With version 2.188.3, as soon as agents automatically upgraded we get an SSL error during artifact download.
Agent and Worker's Diagnostic Logs
2021-06-29T20:58:30.2172776Z ##[debug]Processed: ##vso[task.logissue type=error;]The SSL connection could not be established, see inner exception.
2021-06-29T20:58:30.2183518Z ##[debug]Processed: ##vso[task.complete result=Failed;]
2021-06-29T20:58:30.2280828Z ##[debug]   at Microsoft.VisualStudio.Services.Common.VssHttpRetryMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Location.Client.LocationHttpClient.GetConnectionDataAsync(ConnectOptions connectOptions, Int64 lastChangeId, CancellationToken cancellationToken, Object userState)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.GetConnectionDataAsync(ConnectOptions connectOptions, Int32 lastChangeId, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.ConnectAsync(ConnectOptions connectOptions, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.EnsureConnectedAsync(ConnectOptions optionsNeeded, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.CheckForServerUpdatesAsync(CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.FindServiceDefinitionAsync(String serviceType, Guid serviceIdentifier, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.VssServerDataProvider.LocationForCurrentConnectionAsync(String serviceType, Guid serviceIdentifier, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.LocationService.ResolveLocationDataAsync(Guid locationAreaIdentifier, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.Location.LocationService.GetLocationDataAsync(Guid locationAreaIdentifier, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssConnection.GetClientInstanceAsync(Type managedType, Guid serviceIdentifier, CancellationToken cancellationToken, VssHttpRequestSettings settings, DelegatingHandler[] handlers)
   at Microsoft.VisualStudio.Services.WebApi.VssConnection.GetClientServiceImplAsync(Type requestedType, Guid serviceIdentifier, Func`4 getInstanceAsync, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssConnection.GetClientAsync[T](CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.TaskExtensions.SyncResult[T](Task`1 task)
   at Microsoft.VisualStudio.Services.WebApi.VssConnection.GetClient[T]()
   at Agent.Plugins.BuildServer..ctor(VssConnection connection)
   at Agent.Plugins.PipelineArtifactServer.DownloadAsyncV2(AgentTaskPluginExecutionContext context, ArtifactDownloadParameters downloadParameters, DownloadOptions downloadOptions, CancellationToken cancellationToken)
   at Agent.Plugins.BuildArtifacts.DownloadBuildArtifactTaskV1_0_0.ProcessCommandInternalAsync(AgentTaskPluginExecutionContext context, CancellationToken token)
   at Agent.PluginHost.Program.Main(String[] args)

Hi @craigeaw could you please make sure that all domains specified in docs are allowed for your agent's environment - specifically for *.blob.core.windows.net?

Hi @craigeaw could you please make sure that all domains specified in docs are allowed for your agent's environment - specifically for *.blob.core.windows.net?

I checked with our network security team, and none of the domains in the document are being blocked. Our configuration has not changed since before agent version 2.188.3 was released, so I think it's an issue with the agent code or configuration.

Could you please try to set up DISABLE_BUILD_ARTIFACTS_TO_BLOB environment variable as 'true' before agent configuration? This will disable new blob storage functionality introduced by task update.

I set this as a variable on the release. It did not seem to make a difference. See my environment variable output below (some output has been removed by me).
2021-06-30T18:04:17.7297981Z Environment variables available are below.  Note that these environment variables can be referred to in the task (in the ReleaseDefinition) by replacing "_" with "." e.g. AGENT_NAME environment variable can be referenced using Agent.Name in the ReleaseDefinition:
				[AGENT_DEPLOYMENTGROUPID] --> [221]
				[AGENT_DISABLELOGPLUGIN_TESTFILEPUBLISHERPLUGIN] --> [true]
				[AGENT_DISABLELOGPLUGIN_TESTRESULTLOGPLUGIN] --> [true]
				[AGENT_ENABLETASKRESTRICTIONSTELEMETRY] --> [true]
				[AGENT_HOMEDIRECTORY] --> [C:\azagent\A1]
				[AGENT_ID] --> [78]
				[AGENT_JOBNAME] --> [Release]
				[AGENT_OS] --> [Windows_NT]
				[AGENT_OSARCHITECTURE] --> [X64]
				[AGENT_RELEASEDIRECTORY] --> [C:\azagent\A1\_work\r1\a]
				[AGENT_RETAINDEFAULTENCODING] --> [false]
				[AGENT_ROOTDIRECTORY] --> [C:\azagent\A1\_work]
				[AGENT_SERVEROMDIRECTORY] --> [C:\azagent\A1\externals\vstsom]
				[AGENT_TASKRESTRICTIONSENFORCEMENTMODE] --> [WarningOnly]
				[AGENT_TEMPDIRECTORY] --> [C:\azagent\A1\_work\_temp]
				[AGENT_TOOLSDIRECTORY] --> [C:\azagent\A1\_work\_tool]
				[AGENT_VERSION] --> [2.188.3]
				[AGENT_WORKFOLDER] --> [C:\azagent\A1\_work]
				[AZURE_HTTP_USER_AGENT] --> [VSTS_64bf1ad0-199a-44bf-8c53-ba6a223b94ff_release_20_1260_3048_6]
				[BUILD_BUILDID] --> [8325]
				...
				[BUILD_TYPE] --> [Build]
				[DISABLE_BUILD_ARTIFACTS_TO_BLOB] --> [true]

@craigeaw could you please share what was the previous agent version which worked for you?

@craigeaw could you please share whole agent logs for your case? You can send them to my email -<EMAIL_ADDRESS>

We're also facing the exact same issue auto-upgraded to version 2.188.3

@anatolybolshakov How is DISABLE_BUILD_ARTIFACTS_TO_BLOB flag supposed to help? If the agent crashes much earlier on:
Agent.Plugins.BuildServer..ctor(VssConnection connection)

   at Microsoft.VisualStudio.Services.WebApi.Location.LocationService.GetLocationDataAsync(Guid locationAreaIdentifier, CancellationToken cancellationToken)

@anatolybolshakov - also all logs are aready sent as part of<PHONE_NUMBER>001198 SR.

@alex-peck could you please take a look? Do you know maybe if it's some known issue?

This is almost definitely due to a misconfigured firewall. You are failing to reach out to the location service.

This is almost definitely due to a misconfigured firewall. You are failing to reach out to the location service.
Can you try the agent in a different environment to confirm you are still having this issue?

Our firewall configuration has not changed since the previous working version. I confirmed with our network security team that there is no traffic being blocked by the firewall when these requests are being made by the agent. Did the firewall configuration requirements for the agent change on 6/28?

This is almost definitely due to a misconfigured firewall. You are failing to reach out to the location service.
Can you try the agent in a different environment to confirm you are still having this issue?

Our firewall configuration has not changed since the previous working version. I confirmed with our network security team that there is no traffic being blocked by the firewall when these requests are being made by the agent. Did the firewall configuration requirements for the agent change on 6/28?

Are you using a proxy of any kind?
The change that happened was we moved from DownloadBuildArtifactsV0 (which was a JavaScript task) to DownloadBuildArtifactsV1 (which is a C# task included in the agent).

This is almost definitely due to a misconfigured firewall. You are failing to reach out to the location service.
Can you try the agent in a different environment to confirm you are still having this issue?

Our firewall configuration has not changed since the previous working version. I confirmed with our network security team that there is no traffic being blocked by the firewall when these requests are being made by the agent. Did the firewall configuration requirements for the agent change on 6/28?

Are you using a proxy of any kind?
The change that happened was we moved from DownloadBuildArtifactsV0 (which was a JavaScript task) to DownloadBuildArtifactsV1 (which is a C# task included in the agent).

No proxy. We're trying something with the FW configuration. I'll get back to you with our findings.

@alex-peck You are correct that is was misconfigured FW. It was that coupled with me misinterpreting a deployment process. Ian IP was being blocked in the <IP_ADDRESS>/24 range. We allowed it for one server, but failed to do so for another server in the deployment group. We'll be revisiting our configuration next week to ensure the entire range is covered. Thank you for your help!

Customer confirmed this was an issue with their firewall. Closing this for now. If anyone else experiennces a similar error, please validate that your firewall is correctly configured with the allow-list here.

Hi @alex-peck i have the same problem in the download of universal package but i use proxy and agent in with version 2.213.2


Tabular: Fallback to bag fold model for refit if out-of-memory / not-enough-memory error occurs when fitting _FULL model.

Fallback to bag fold model for refit if out-of-memory / not-enough-memory error occurs when fitting _FULL model.
This will safeguard against low-memory scenarios where there isn't sufficient memory to train the _FULL model, but refit_full is specified. Currently this will lead to a later exception. Instead, we can fallback to the first fold model trained in the bag to ensure it doesn't crash.
Related: This issue is a band-aid solution to #3935, which is the overarching memory error problem.

Resolved by #3977


Upgrade tensorflow

Description
The current version of TF (1.3) is getting old and SCT would benefit from using latest version (speed, features, etc.). However, the upgrade will cause loss of compatibility with older OS.
Currently, we deal with those issues by installing from Pipy instead of Conda, but doing the upgrade will probably induce additional complexity and we will likely lose users who are running old OS.
We should upgrade TF version after we move SCT to Py3k. Related to https://github.com/neuropoly/spinalcordtoolbox/issues/1527.

We are now using TF 2.0 and everything works fine, so we can close this issue


Allow setting 0 replicas to autoscaling machine pool (Not default)

This is blocked until this is supported in CS backend

@vkareh @nimrodshn PTAL

/hold until https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/2844 is merged

/hold
until https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/2844 is merged

/lgtm

@vkareh this is now ready to be merged

/hold cancel

/lgtm


windows compilation + better types

First of all this pull request adds windows compilation support thanks to cross-env (dev dependency)
Also I fixed more typing issues, the only new thing is that in order to get proper typings PixiComponent has to be used like this in TS:
interface CircleProps { radius: number; }
const Circle = PixiComponent<CircleProps, PIXI.Graphics>(...)

The good thing is that now lifecycle methods are properly typed with the given Props interface, get the proper PIXI display object type and also when such component is used inside JSX the properties are properly validated.
PS: withPixiApp type as a decorator is still kind of broken, but it works properly as a function (this is, the wrapped class can accept a mandatory app prop and it won't be asked when using the wrapping element)
Also, changes in style are because of prettier.
Btw, options are now typed as  PIXI.ApplicationOptions, should the shape be updated or was there any reason for the custom type (which if needed could be changed to a Pick<PIXI.ApplicationOptions, "a"|"b"|...)?

Ah, Omit was changed to
type Omit<T, K> = Pick<T, Exclude<keyof T, K>>
which is better than the old method, but requires TS 2.8

Oh and also added all possible canvas props to stage to the types

Looks good! Will merge it now, thanks!


[staging] Configure download dialog is closed when clicking outside dialog

Steps to Reproduce

Click on "Download..." button in Single Run page
Click outside dialog

Actual Results
Dialog closes
Expected Results
Dialog should not close until clicking on [X]
Design

Evidence
https://github.com/chanzuckerberg/cryoet-data-portal/assets/63799148/92dea85e-ed8b-46d9-8b05-8b0ca450f720

modal remains now opened when clicking outside of it... thank you!!!


Don't share self-replacing abilities

Reported here (and with a couple of followup posts).
When these abilities replace themselves with another Ability, that will then get shared as normal.
I've implemented this by not cloning the effects for those Abilities (resulting in dummy no-op effects instead) so that the code dealing with adding and removing shared abilities is unaffected.

I have no idea what pic is, but I'll trust you that this is a desirable fix.


Update apache2 dependency and testing tools

depends 'apache2', '>= 2.0.0'

This also needed a rebase so I pulled in the same changes.  Specs pass now which is great.  Thanks


Update Generator.cs

Make Handle public to make it usable for other libraries.

Hello! I'm the build bot for the Mono project.
I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.
Contributors can ignore this message.

I am sorry for late my reply. Thank you for the patch!
The patch doesn't work though, as the Handle is defined explicitly and we would get CS0106 errors. Luckily we don't need to define it explicitly (anymore?), so we just need to modify you patch slightly to:
IndentWriteLine ("public {0} Handle {{", handleType);
Could you please fix your PR? (make sure it still has 1 commit)

Sure @radekdoulik :smiley:!
The fix was a guess afterwards I looked into the sourcecode. However it already looked to easy to be correct.
Nevertheless of course I'll fix it.

I'm sorry now too @radekdoulik I had a lot to do and forgot making the small edit. Please excuse this!

The linked issue says I cannot access the handles of the classes without using ... reflection but if it's just explicit interface implementation you need neither public nor reflection.
var handle = ((IMarshalling) instance).Handle;


Fix for WFCORE-3637, upgrade to aesh-readline 1.4

Hold until Feb 26 to give Stale a chance to check the release.

@wildfly/mergers-core, we need to upgrade to aesh-readline 1.5, nexus had some issues this WE, we have been not able to release it then upgrade yet.


Job events are now sent by Gitlab as build event payload

https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#job-events
Request Body:
...
  "object_kind": "build",
...
  "build_id": 1977,
  "build_name": "test",
  "build_stage": "test",
  "build_status": "created",
  "build_started_at": null,
  "build_finished_at": null,
  "build_duration": null,
  "build_allow_failure": false,
  "build_failure_reason": "script_failure",
...

Also typo JSON tag: https://github.com/go-playground/webhooks/blob/v5/gitlab/payload.go#L252
	AuthorName  string     `json:"auuthor_name"`


Permission denied when executing /vmwrapper

I have manually deployed a k8s cluster on three ubuntu 16.04 VMs running on vcenter. I would like to try virtlet, so I follow the guide in real-cluster.md to configure one of the node as a virtlet node. Everything goes well until I try to create a VM, I get the following error showed by "kubectl get pod" command:
rpc error: code = 2 desc = "/run/virtlet.sock": rpc error: code = 2 desc = virError(Code=1, Domain=0, Message='internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOME=/root /vmwrapper -help) unexpected exit status 126: libvirt:  error : **cannot execute binary /vmwrapper: Permission denied** ')
I guess that's because apparmor is not disabled so I follow the ubuntu official guide to disable apparmor
sudo systemctl stop apparmor.service
sudo update-rc.d -f apparmor remove
and try to create the VM again, but I get the same error.
I try to list the files in virtlet pod
sudo kubectl -n kube-system exec virtlet-m5pfz -- ls -l /
-rwxr-xr-x   1 root root  4617264 Aug 15 21:54 vmwrapper
still no hints for the error.

You need to do /etc/init.d/apparmor teardown and then remove apparmor package.

https://support.plesk.com/hc/en-us/articles/213909965-How-to-disable-AppArmor-
As Ivan said - there is additional step.
Btw. dealing with apparmor/selinux can require reboot at the end.

Thanks for the quick reply, I will try your suggestions.

Also adding apparmor=0 to kernel command line (in grub configuration) can be useful ;)

Great, as suggested, after running the following commands and restart my ubuntu virtual machine, I can successfully create a VM via virtlet.
service apparmor stop
service apparmor teardown
update-rc.d -f apparmor remove
apt-get remove apparmor
so I close this issue myself?

Glad it helped :)


Branch user guide

Codecov Report

Merging #37 (3cdb0a8) into master (f2aa460) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #37   +/-   ##
=========================================
  Coverage     70.96%   70.96%
  Complexity      429      429
=========================================
  Files            73       73
  Lines          1326     1326
  Branches        146      146
=========================================
  Hits            941      941
  Misses          344      344
  Partials         41       41

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 f2aa460...3cdb0a8. Read the comment docs.