Change message footer for bot messages

Rather than say "I am a bot, bsoyka made me." at the bottom of all bot messages, it should say (for example) "I am a bot made by the community."
This is set in the send_message function in utils.py and shouldn't be difficult to update.

I have updated the message in send_message, as mentioned in the issue. 👍🏻


Client Allocation Request for: Alyale Philippines, Inc.

Client Allocation Questions
Core Information

Name: Alyale Philippines, Inc.
Website / Social Media: https://www.alyale.com/
DataCap Requested: 100GiB
Addresses to be Notarized: f3qqhbwhgorbtymzhq5wxnointwl4tl5riqvxv35utyuhlisbz4247io32oshff2emysu5fzc2t4msh64ahlpq
Notary Requested: philippbanhardt

Closing this issue as it appears to be a duplicate to https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/3

Closing this issue as it appears to be a duplicate to https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/3


impeller: opengles backend doesn't render lines

The tests introduced in https://github.com/flutter/engine/pull/55717 don't render the lines in the opengles backend.
seen result

expected result

The line rendering behavior changed with https://github.com/flutter/engine/commit/19ef4a9c0c1129ef7dcf3f8848f70842a946228f
This renders consistently on Vulkan and GLES if I patch LineGeometry::ComputePixelHalfWidth to set min_size = 1.0 / max_basis


fix: #5779 FP

Fixes Issue
#5779
Description of Change
Suppress CVE-2023-35116  for jackson-databind as it is a false positive.

The finding by DC is not a false positive. The CVE is getting disputed in the tickets. Resolution should be with the vulnerability sources - OSSIndex and NVD.
Whether or not it is a vulnerability of the library is open for interpretation. From the ticket it is clear that chances for exploitability of it can be considered very low.
As an attacker you would need some other attack vector to coerce an application into the creation of a cyclic Map that you know to be subsequently serialized by Jackson. When you manage to do so you would be able to break the application on a StackOverflow, which could be classified as a vulnerability against the availability of the application.
Note: I tend to agree with cowtowncoder that for similar behaviour Map's hashCode should also be considered vulnerable if the authorities in charge decide to not withdraw the CVE for this issue. Especially since the cyclic nature of the Map is explicitly allowed (though discouraged) in Map's Javadoc, with no mention whatsoever on the fatal consequences for hashCode ('no longer well-defined' is something else then 'calling the method is guaranteed to throw a StackOverflowException'):

While it is permissible for a map to contain itself as a value, extreme caution is advised: the equals and hashCode methods are no longer well defined on such a map

Already delisted by Sonatype OSSIndex


[DO NOT MERGE] - Mark service manual formats as migrated

https://trello.com/c/qcUsJJci

@suzannehamilton Thanks have changed the format 👍


[Frontend] Source field in NodeSearchComponent should filter both literal and class nodes.

The current implementation of the source filed in NodeSearch component filters only the class nodes, it needs to be updated to filter both literal and class nodes.

Duplicate of #18


Occasion title too close to previous field.

@lcoenen @buckwierd
The Occasion title is too close to the field above. All the other titles have a proper spacing from the previous field. Please allow that space for the Occasion title.

This have been fixed and pushed to master


FileNotFoundException is throw during the project build task

When I upgraded the plugin to version 1.18.6, the task generateGraphQLSchema threw a FileNotFoundException exception because the specified directory '/generated-resources/graphql-maven-plugin_generate-relay-schema' does not exist, but the build.gradle doesn't define this task, so it should not run.
I suspect it happens during Gradle configuration step.
It's important to emphasize that we have only generateClientCodeConf configuration block and no generateGraphQLSchema section at all, and the failure is during the project build task while running the generate code task explicitly work fine
generateClientCodeConf {
    schemaFileFolder = '../../../project/src/main/resources'
    packageName = 'com.myproject.gql.client.project'
    // The parameters below change the 1.x default behavior. They are set to respect the default behavior of the future 2.x versions
    generateDeprecatedRequestResponse = false
    separateUtilityClasses = true
    templates = [
		OBJECT: "./src/main/resources/gql/templates/object_type.vm.java"
	]
    customScalars = [
            [
                    graphQLTypeName: "DateTime",
                    javaType: "java.time.OffsetDateTime",
                    graphQLScalarTypeStaticField: "graphql.scalars.datetime.DateTimeScalar.INSTANCE"
            ]
    ]
}

It passes if we run just generateClientCode, so I think the only problem is that the task generateGraphQLSchema has to be skipped.
From version 1.18.6, a dependency was added for the compileJava and processResources tasks in the plugin.
The exception:
2023-01-25T11:26:43.961+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.961+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
2023-01-25T11:26:43.961+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.961+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] A problem was found with the configuration of task ':services:myproject:shared:client:project:generateGraphQLSchema' (type 'GenerateGraphQLSchemaTask').
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   - Type 'com.graphql_java_generator.gradleplugin.GenerateGraphQLSchemaTask' property 'targetFolder' specifies directory '/generated-resources/graphql-maven-plugin_generate-relay-schema' which doesn't exist.
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Reason: An input file was expected to be present but it doesn't exist.
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Possible solutions:
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]       1. Make sure the directory exists before the task is called.
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]       2. Make sure that the task which produces the directory is declared as an input.
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Please refer to https://docs.gradle.org/7.0.1/userguide/validation_problems.html#input_file_does_not_exist for more details about this problem.
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
2023-01-25T11:26:43.962+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]  Run with --scan to get full insights.
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Exception is:
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] org.gradle.internal.execution.WorkValidationException: A problem was found with the configuration of task ':services:myproject:shared:client:project:generateGraphQLSchema' (type 'GenerateGraphQLSchemaTask').
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   - Type 'com.graphql_java_generator.gradleplugin.GenerateGraphQLSchemaTask' property 'targetFolder' specifies directory '/generated-resources/graphql-maven-plugin_generate-relay-schema' which doesn't exist.
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Reason: An input file was expected to be present but it doesn't exist.
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Possible solutions:
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]       1. Make sure the directory exists before the task is called.
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]       2. Make sure that the task which produces the directory is declared as an input.
2023-01-25T11:26:43.963+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]     Please refer to https://docs.gradle.org/7.0.1/userguide/validation_problems.html#input_file_does_not_exist for more details about this problem.
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.WorkValidationException$BuilderWithSummary.build(WorkValidationException.java:109)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.WorkValidationException$BuilderWithSummary.get(WorkValidationException.java:91)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:97)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:50)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:86)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:86)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:32)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:43)
2023-01-25T11:26:43.964+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:31)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution$2.withWorkspace(ExecuteActionsTaskExecuter.java:283)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:49)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:35)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:184)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
2023-01-25T11:26:43.965+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
2023-01-25T11:26:43.966+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
2023-01-25T11:26:43.967+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:408)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:395)
2023-01-25T11:26:43.968+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:388)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:374)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
2023-01-25T11:26:43.969+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
2023-01-25T11:26:43.970+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.970+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
2023-01-25T11:26:43.970+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Get more help at https://help.gradle.org
2023-01-25T11:26:43.970+0200 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger]
2023-01-25T11:26:43.970+0200 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 23s

Thanks for the detailed report
Did you achieve a build, or are you stuck with this issue ?

Yes the build failed because generateGraphQLSchema throws exception

@etienne-sf Do you have any updates about the issue?

Not yet.
At first, I couldn't repeat it.
I'm finishing some other stuff, and I'll get back to this one.

Hello,
I did a new test today, and I was not able to repeat it.
I've updated the gradle client tutorial back to release 1.18.6, as yours.
Can you test it, and confirm the build is ok for you ?

If yes, then there should be a difference between the tutorial gradle.build file and yours
If no, then the issue is probably linked to the gradle version

Etienne

Any update on this issue ?
If it's still an issue, can you provide the gradle build file ?

We use Gradle version 7.0.1
We use the same version 1.18.6 in the plugin com.graphql_java_generator.graphql-gradle-plugin and in the dependency graphql-java-server-dependencies.

I can't provide the Gradle build file because we use it in our organization,
But I can provide the part we config the plugin in the Gradle file.
Another option is to take it in a session and I will show you the problem.

@etienne-sf any update?

Sorry, I missed your message.
Yes, if you can provide the part of the gradle build file for the plugin, I'll probably be able to repeat, then correct it.
Etienne

Closed, as I could not repeat this issue.
It can be reopened, of course. But please provide enough information.

Here example of http request:
(new SecurityRunHuntingQueryRequestBuilder("https://graph.microsoft.com/beta/security/runHuntingQuery", getSdk().me().getClient(),null, SecurityRunHuntingQueryParameterSet
.newBuilder()
.withQuery("DeviceProcessEvents | where Timestamp <= datetime(2023-06-15T11:15:49.226113400Z) | limit 10")
.build()).buildRequest().post()
Sdk result:
{"results":[{},{},{},{},{},{},{},{},{},{}],"schema":[{"name":"Timestamp","type":"DateTime"},{"name":"DeviceId","type":"String"},{"name":"DeviceName","type":"String"},{"name":"ActionType","type":"String"},{"name":"FileName","type":"String"},{"name":"FolderPath","type":"String"},{"name":"SHA1","type":"String"},{"name":"SHA256","type":"String"},{"name":"MD5","type":"String"},{"name":"FileSize","type":"Int64"},{"name":"ProcessVersionInfoCompanyName","type":"String"},{"name":"ProcessVersionInfoProductName","type":"String"},{"name":"ProcessVersionInfoProductVersion","type":"String"},{"name":"ProcessVersionInfoInternalFileName","type":"String"},{"name":"ProcessVersionInfoOriginalFileName","type":"String"},{"name":"ProcessVersionInfoFileDescription","type":"String"},{"name":"ProcessId","type":"Int64"},{"name":"ProcessCommandLine","type":"String"},{"name":"ProcessIntegrityLevel","type":"String"},{"name":"ProcessTokenElevation","type":"String"},{"name":"ProcessCreationTime","type":"DateTime"},{"name":"AccountDomain","type":"String"},{"name":"AccountName","type":"String"},{"name":"AccountSid","type":"String"},{"name":"AccountUpn","type":"String"},{"name":"AccountObjectId","type":"String"},{"name":"LogonId","type":"Int64"},{"name":"InitiatingProcessAccountDomain","type":"String"},{"name":"InitiatingProcessAccountName","type":"String"},{"name":"InitiatingProcessAccountSid","type":"String"},{"name":"InitiatingProcessAccountUpn","type":"String"},{"name":"InitiatingProcessAccountObjectId","type":"String"},{"name":"InitiatingProcessLogonId","type":"Int64"},{"name":"InitiatingProcessIntegrityLevel","type":"String"},{"name":"InitiatingProcessTokenElevation","type":"String"},{"name":"InitiatingProcessSHA1","type":"String"},{"name":"InitiatingProcessSHA256","type":"String"},{"name":"InitiatingProcessMD5","type":"String"},{"name":"InitiatingProcessFileName","type":"String"},{"name":"InitiatingProcessFileSize","type":"Int64"},{"name":"InitiatingProcessVersionInfoCompanyName","type":"String"},{"name":"InitiatingProcessVersionInfoProductName","type":"String"},{"name":"InitiatingProcessVersionInfoProductVersion","type":"String"},{"name":"InitiatingProcessVersionInfoInternalFileName","type":"String"},{"name":"InitiatingProcessVersionInfoOriginalFileName","type":"String"},{"name":"InitiatingProcessVersionInfoFileDescription","type":"String"},{"name":"InitiatingProcessId","type":"Int64"},{"name":"InitiatingProcessCommandLine","type":"String"},{"name":"InitiatingProcessCreationTime","type":"DateTime"},{"name":"InitiatingProcessFolderPath","type":"String"},{"name":"InitiatingProcessParentId","type":"Int64"},{"name":"InitiatingProcessParentFileName","type":"String"},{"name":"InitiatingProcessParentCreationTime","type":"DateTime"},{"name":"InitiatingProcessSignerType","type":"String"},{"name":"InitiatingProcessSignatureStatus","type":"String"},{"name":"ReportId","type":"Int64"},{"name":"AppGuardContainerId","type":"String"},{"name":"AdditionalFields","type":"String"}],"@odata.context":"https://graph.microsoft.com/beta/$metadata#microsoft.graph.security.huntingQueryResults"}


Update to new hpp-fcl namespace wrapping

Namespaces in hpp-fcl are now encapsulated inside hpp namespace (hpp-fcl commit [https://github.com/humanoid-path-planner/hpp-fcl/commit/788afa0de437cb5f7587f974dd60cc411367f47e] )

Good to see you here.
I think this PR is worth to combine with topic/fcl-release branch. Can you rebase on it or see with @jmirabel?

I think that there is no issue with the hpp-fcl namespace, and that #645 was enough, especially with the namespace fcl = hpp::fcl;in src/multibody/fcl.hpp.

But yes, @olivier-roussel you should use the topic/fcl-release branch if you want to use hpp-fcl v1.0+

My bad, trying to catch your workflow. Thanks, I guess we can close the PR.


ERROR: 403: Services '[admin-json.googleapis.com]' not found or permission denied. - forbidden

The issue tracker is for reporting product deficiencies. "How do I?" questions should be posted to the discussion forum at https://groups.google.com/group/google-apps-manager. When in doubt, start at the discussion forum and return here only when instructed to do so.
Please confirm the following:

I have upgraded to the latest GAM release from https://git.io/gamreleases and I still have this issue.
I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/gam/wiki

Full steps to reproduce the issue:

start the batch file game-setup.bat
login as a super-admin
start creating a project

Expected outcome (what are you trying to do?): install GAM
Actual outcome (what errors or bad behavior do you see instead?):
got this message :
Authentication successful.
Creating project "GAM Project"...
Checking project status...
Project still being created. Sleeping 1 seconds
Checking project status...
enabling API admin-json.googleapis.com...
ERROR: 403: Services '[admin-json.googleapis.com]' not found or permission denie
d. - forbidden

Jay has identified this problem and has corrected it; his fix has not been
published however.
This version will get you going for now:
https://github.com/taers232c/GAM-B/releases
Ross
On Tue, Jan 17, 2017 at 6:32 PM, arouthier<EMAIL_ADDRESS>wrote:

The issue tracker is for reporting product deficiencies. "How do I?"
questions should be posted to the discussion forum at
https://groups.google.com/group/google-apps-manager. When in doubt, start
at the discussion forum and return here only when instructed to do so.
Please confirm the following:

I have upgraded to the latest GAM release from
https://git.io/gamreleases and I still have this issue.
I am typing the command as described in the GAM Wiki at
https://github.com/jay0lee/gam/wiki
https://github.com/jay0lee/gam/wiki

Full steps to reproduce the issue:

start the batch file game-setup.bat
login as a super-admin
start creating a project

Expected outcome (what are you trying to do?): install GAM
Actual outcome (what errors or bad behavior do you see instead?):
got this message :
Authentication successful.
Creating project "GAM Project"...
Checking project status...
Project still being created. Sleeping 1 seconds
Checking project status...
enabling API admin-json.googleapis.com...
ERROR: 403: Services '[admin-json.googleapis.com]' not found or
permission denie
d. - forbidden
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/390, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIU8L45YRRf7Awt2TAe2h-cUAeetLRM4ks5rTXnOgaJpZM4LmaQq
.

--
Ross Scroggs
<EMAIL_ADDRESS>

Thanks a lot Ross!
FAST!!!
The version you sent me is working.
Keep up the good work boys!


Hotfix/2020.2.1

Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
This is the first hotfix for 2020.2, including the fix for #3657 .

Ah! This has the nvm issue on CodeBuild.

And 5 tests failed...I will run the tests locally.


Update GoogleTest to latest version

Import latest version of GoogleTest from upstream and adjust build accordingly.
Tracking issue: https://github.com/gazebosim/gz-sim/issues/1537
Signed-off-by: Michael Carroll<EMAIL_ADDRESS>

@chapulina Is jammy expected to work here?


Add test case to validate if anonymous delete request returns 200

The test case validates the case where the requesting user does not have access to the bucket they are attempting to delete objects from and should receive a response 200 and an 'Access Denied' error for each object they are attempting to delete rather than the generic 403 AccessDenied error response.
AWS S3 reference doc: http://docs.aws.amazon.com/AmazonS3/latest/API/multiobjectdeleteapi.html#multiobjectdeleteapi-examples
Fixes: https://github.com/minio/mint/issues/115

Done @krisis


Decoding code crashes

The decoding code is full of unwraps, which means that even the smallest decoding failure will result in a crash, instead of (at least) partially decoded stack trace.
For me, it crashes here.
I can provide you with an .ELF file and a stacktrace if necessary, but in general I believe (a) some of these errors (like unable to find a line and file) should be recoverable and (b) the others should probably be errors instead of panics.

One problem I've found is that Context.find_frames() often doesn't return anything

Do you have an example? The results I got for Arduino FW was on par with the outputs from the Java decoder that is using GDB

What do you think about PR #2 as a fix @ivmarkov ? Still a bit fresh on anything Rust, I think those modifications make sense but I'm not sure if it can be done better

Look quite OK to me in general. I have a few minor nits, probably not worth mentioning.
A question: what is the format of the stack trace that can be parsed? Is the tool also accepting standard ESP32 Xtensa "Backtrace" formatting, generated either programmatically or on panics? I.e. Backtrace:0x40183f44:0x3ffbaca0 0x400dfc16:0x3ffbacc0 0x400e3dd5:0x3ffbad30 0x400d787b:0x3ffbada0 0x400d61c1:0x3ffbb048 |<-CORRUPTED?

At the moment it's only trying to parse any address in the 0x40xxxxxx range, like the Java thing is doing. I didn't even bother looking at the memory mappings for the ESP8266/32 since the code was supposedly working for both.  Also I couldn't find the format used for of the stack trace generated by the Arduino tool chain at least.
Definitely not the best solution I guess, but this started like a PoC to rewrite the thing in Rust and WASM, but I'd gladly make it more robust with your inputs.
Also it was a bit late and I totally forgot to fix the WASM build...

Sorry, I did not have time to follow up with the original backtrace. I tried it with a few new ones, and I don't see any problem now (that is, with the command line executable).
For the wasm, what I would suggest is an error reporting when pressing the "Run" button, that I have not uploaded an elf file. It took me quite a few clicks on the Run button to realize that...


Preparing for a v0.6 release

I'd like to cut a release for v0.6 soon -- say, by the end of this week (June 25). Are there any changes that anyone would like to get in before the cut?
The last version (v0.5) was released on March 1, 2021, and since then:

The draft spec was updated twice (v0.5 was synced with draft-irtf-cfrg-opaque-03, and the latest is now draft-irtf-cfrg-opaque-05 which we are synced with)
Various security improvements: (https://github.com/novifinancial/opaque-ke/commit/98f1821897cd2800e5bffb2a70541056145e99cc), (https://github.com/novifinancial/opaque-ke/commit/468e0690d7f2ae91c9a55474fcf40b0457519385), (https://github.com/novifinancial/opaque-ke/commit/940d1dcdb29e9de45a5123adab578b3446502b72)
Serde support behind a feature
Supporting common traits (https://github.com/novifinancial/opaque-ke/commit/eb59676a940b15f77871aefe1e46d7b5bf85f40a)
Swapping out scrypt for argon2 (https://github.com/novifinancial/opaque-ke/commit/535b9b8ee41392c2a0c100f71f5cd04497a61817)

#191 and #193 are the last ones we need.

FYI: I will likely be delaying this release until after the holidays, unless there is an urgent need for publishing earlier.

I'm not sure what holidays, but we do "need" a release before the 10th of July. I already planned to release a fork on crates.io, but I prefer not to.
On the other hand it's no problem, releasing a fork is a viable option :slightly_smiling_face:.

Ah, sorry -- I was referring to July 4th as the holidays. Anyway, given your restraints, I will aim publish the next version tomorrow, after some small updates to the changelog and documentation. Thanks for the feedback!

Published


ERROR: list index out of range

(UPDATED for most recent version involving commits to .../create_db.py + I simplified the initial setup)
Hello!
I try to create a data set from about 100 JPEG files (colored. And I get this error message:
ERROR: list index out of range

Traceback (most recent call last):
  File "/home/ubuntu/digits/digits/scheduler.py", line 394, in task_thread
    task.run(**options)
  File "/home/ubuntu/digits/digits/task.py", line 196, in run
    if not self.process_output(line):
  File "/home/ubuntu/digits/digits/dataset/tasks/create_db.py", line 167, in process_output
    data = self.distribution_data()
  File "/home/ubuntu/digits/digits/dataset/tasks/create_db.py", line 243, in distribution_data
    titles.append(labels[int(key)])
IndexError: list index out of range

This is what my list looks like (I use \t to separate):
/home/ubuntu/data/train0_small/10_left.jpeg 1
/home/ubuntu/data/train0_small/10_right.jpeg    1
/home/ubuntu/data/train0_small/13_left.jpeg 1
/home/ubuntu/data/train0_small/13_right.jpeg    1
...

The images are already sized 256x256. If I reduce the images then the loading succeeds. For that purpose I also split the pictures into two sets of size 10 and size 90. Both were separately loaded successfully. But all 100 together failed.
Any ideas what might be the issue here or how to further troubleshoot the problem?
Kind Regards
Raffael

I think I found it. The tooltip for the labels file field was misleading.
https://github.com/NVIDIA/DIGITS/pull/83

I had the same error, my numeric labels were in the range [1,N]. I couldn't solve it by moving the labels file 1 line down. I had to shift numeric labels to the range[0,N-1], and that solved the problem.


Make Slicer interface more generic

closes #442

im a bit confused that we require to pass object.Object: imo this can complicate the code of a simple data uploading applications.
how about provide both raw interface (current) accepting object.Object and the sugared (previous) one requiring min input? @smallhive @carpawell @roman-khimov

I consider, it doesn't make sense. User has to pass all required parameters for the header object (signer neofscrypto.Signer, cnr cid.ID, owner user.ID) and we create it inside.
Passing object.Object gives a flexible way to configure the header. In this case, the user creates the header itself with the same data.
For comparison, we manipulate the same data, but with different ways:
Before
slicer := new(signer neofscrypto.Signer, cnr cid.ID, owner user.ID, w ObjectWriter, opts Options)
slicer.Slice(data io.Reader, attributes ...string)

After
var hdr object.Object
header.SetContainerID(cnr)
header.SetOwnerID(&owner)
header.SetAttributes(...)
header.///

slicer := new(w ObjectWriter)
slicer.Slice(header object.Object, data io.Reader, signer neofscrypto.Signer, opts Options)

Yes, the code longer for header creation, but it is deadly simple

header.///

that's what exactly bothers me. How user will undestand which fields must be explicitly set and which are optional or event must not be set?
accepting cid.ID, user.ID, neofscrypto.Signer, string attibutes and io.Reader covers most of the external uploader's needs imo. And accepting header structure (object.Object as done in this PR) is good for system needs and small part of deeply understanding users. Simple splitted input can call header one within package (from simple to flexible).
i can also suggest to implement customization through optional header construction callback that is going to be called during object formation if set:
var opts Options
opts.SetCustomHeaderConstructor(func(obj *object.Object) {
  obj.SetType(object.Tombstone)
  obj.SetWhatever()
})

slicer := new(signer neofscrypto.Signer, cnr cid.ID, owner user.ID, w ObjectWriter, opts Options)
slicer.SliceData(bytes.NewReader(tombstone.Marshal()))

header.///

that's what exactly bothers me. How user will undestand which fields must be explicitly set and which are optional or even must not be set?

It's not a problem. We can create a helper function inside the slicer package. For instance:
func PrepareHeader(cnr cid.ID, owner oid.ID) object.Object

Also, we will mention it inside the Slicer constructor/Slice method. Any simple upload application will manage to call the func for header construction. This will be a good starting point for them, to touch our product. But, as practice shows, latter they would want to dive deeper. In this case they shouldn't rewrite a lot their code, because PrepareHeader is just 2 rows function.

accepting cid.ID, user.ID, neofscrypto.Signer, string attibutes and io.Reader covers most of the external uploader's needs imo. And accepting header structure (object.Object as done in this PR) is good for system needs and small part of deeply understanding users. Simple splitted input can call header one within package (from simple to flexible).

I don't agree with strings attributes. Regular client and node already use object.Attribute and have to reconvert existing attributes to string. Me and @carpawell faced the situation.

i can also suggest to implement customization through optional header construction callback that is going to be called during object formation if set:
var opts Options
opts.SetCustomHeaderConstructor(func(obj *object.Object) {
  obj.SetType(object.Tombstone)
  obj.SetWhatever()
})
slicer := new(signer neofscrypto.Signer, cnr cid.ID, owner user.ID, w ObjectWriter, opts Options)
slicer.SliceData(bytes.NewReader(tombstone.Marshal()))

One more option var :smiley: Passing a fully prepared header eliminates all misunderstandings. This callback, we would
only call for the header, because all other parts are TypeRegular. Thus, such a callback looks excessive.

P.S. me personally completely okay with raw API, but I'm not sure if it will be convenient and understandable for simple data upload applications. I'd provide helpers that transform what they have to required stuff like hdr object.Object.

Even the current SDK interface is quite clear and understandable. The slicer improves these factors, but I tend to think it shouldn't make such far abstraction from SDK types

@smallhive i understand and agree with almost all ur points. Let me summarize my own
in my mind, slicer space is intended to simplify data upload. The min required set to upload the data into NeoFS is container ID, Signer and data itself encapsulated in io.Reader primitive. So, i'd like to provide API which allows to use this small input and perform uploading by min num of instructions (ideally - by 1 instruction). If we also want to support some more specific needs like tombstone formation, it's better to add specific API it next to the simple one, implement the simple API through the specific one and not force the user to understand the specifics (if he wants to, he will figure it out and use).
to sum it up,
s := slicer.New(signer, objectWriter, opts)
err := slicer.Slice(slicer.RequiredFields(cnr, owner), strings.NewReader("Hello, world!"))

looks pretty good to me. If this is the approach u suggested, i agree with it

Maybe
s/ObjectPutter/ObjectClient/
s/NetworkedWriter/NetworkedClient/
s/Write/Put/
s/InitWrite/InitPut/

For better names and consistency with client.

According to the comment, completely rewrite the solution

I've made some optimizations and divided each into separate commits.
I've rewritten object.Object to the regular struct type. All setters and getters worked with internal fields. Just like example:
type Object struct {
	v2 *object.Object
	isSet     bool
	id        oid.ID
	signature *neofscrypto.Signature
	version   *version.Version
	payloadSize uint64
	containerID      cid.ID
	isSetContainerID bool
	owner *user.ID
	epoch uint64
	chsum      checksum.Checksum
	isSetChsum bool
	homo   checksum.Checksum
	isHomo bool
	attributes []Attribute
	prevID *oid.ID
	children []oid.ID
	splitInfo *object.SplitHeader
	sess *session.Object
	tp Type
}

Converting to v2/fromV2 and working with api-go object.Object was only in marshaling methods and in some places where it was required to save some stability.
And eventually the result of the bench with these changes:
slice_1-128/reader-16        22546             53294 ns/op            5293 B/op         65 allocs/op
slice_1-128/writer-16        21884             53806 ns/op            5172 B/op         64 allocs/op
slice_4-128/reader-16        22683             52308 ns/op            5549 B/op         69 allocs/op
slice_4-128/writer-16        21963             54744 ns/op            5428 B/op         68 allocs/op
slice_16-128/reader-16       22779             52688 ns/op            5292 B/op         65 allocs/op
slice_16-128/writer-16       22020             53704 ns/op            5172 B/op         64 allocs/op
slice_64-128/reader-16       22689             52312 ns/op            5292 B/op         65 allocs/op
slice_64-128/writer-16       22120             54532 ns/op            5172 B/op         64 allocs/op
slice_256-128/reader-16              22698             52703 ns/op            5549 B/op         69 allocs/op
slice_256-128/writer-16               5796            201214 ns/op           14979 B/op        208 allocs/op
slice_1024-128/reader-16             22813             52194 ns/op            5294 B/op         65 allocs/op
slice_1024-128/writer-16              2508            468130 ns/op           33266 B/op        467 allocs/op
slice_4096-128/reader-16             22807             52623 ns/op            5553 B/op         69 allocs/op
slice_4096-128/writer-16<PHONE_NUMBER> ns/op          113465 B/op       1607 allocs/op
slice_16384-128/reader-16            22594             52474 ns/op            5310 B/op         65 allocs/op
slice_16384-128/writer-16<PHONE_NUMBER> ns/op          411857 B/op       5812 allocs/op
slice_65536-128/reader-16            18676             53830 ns/op            5379 B/op         66 allocs/op
slice_65536-128/writer-16               50          23695444 ns/op         1623365 B/op      22901 allocs/op
slice_262144-128/reader-16           19968             57536 ns/op            5622 B/op         70 allocs/op
slice_262144-128/writer-16              12          95210776 ns/op         6579025 B/op      91271 allocs/op
slice_1048576-128/reader-16          12870             86426 ns/op            7677 B/op         99 allocs/op
slice_1048576-128/writer-16              3         428006130 ns/op        27349832 B/op     381077 allocs/op

Of course, it is just for comparison and to think in the future to manage something with this (or not).
Making such changes right now will lead to disaster

Almost there.
@carpawell, does it work API-wise for node?
@smallhive, it'd be nice to have benchmark diff (as in benchstat output) in commit messages.

Added results to commits.


The license of sciglass database

Can anyone tell me how to get license for sciglass database? I contact EPAM support a few days ago but no one replied

Hello @Jeff-oakley. As far as I know, SciGlass is not commercialized anymore. You can download the database from this git repository and use it following this license: https://github.com/epam/SciGlass/blob/master/LICENSE
You will find all the SciGlass files in plain text in this fork: https://github.com/drcassar/SciGlass

Got it. Thanks. I will check it out.

BTW, is there anyway to open this in mac os Monterey 12.1? I tried app store and did not find anything works. If there is any python library that works, it should be great.

Hi @Jeff-oakley. The files in the repository that I sent you are plain text (some of them are compressed). You should have no problem oppening them in Libreoffice Calc or any other spreadsheet app. You can use GlassPy (https://github.com/drcassar/glasspy) if you want a Python library that has a portion of SciGlass data. Please note that GlassPy is still in development (a bit slower now because of work).


terra-table hover styling is not adjusted for lowlight

Bug Report
Description
Run the terra-table in a lowlight application/page adding multiple rows that are selectable.
Hover over any row.  The background changes to a off-white color, making it difficult to see gray text.
The lowlight setting of the --terra-table-row-hover-background-image variable is identical to the default value.
Comparing the default and lowlight values, it seems many (if not all) of the *hover-background-image values are identical between the 2 themes.  I suggest reviewing all of them when making the correction.
Additional Context / Screenshots

The dotted line around the row was added by my debugger when trying to capture the hover state. It is not there in an actual table.  The point of the picture is the light colored background.
Expected Behavior
Hover color should be specified for the lowlight theme.
Possible Solution
Modify the --terra-table-row-*-hover-background-image variables in the lowlight file to be appropriate values for lowlight.
Environment
I tested in the following.

Component Name and Version: terra-table 4.19.0
Browser Name and Version:  Chrome
Node/npm Version: [e.g. Node 8/npm 5]
Webpack Version:
Operating System and version (desktop or mobile): Mac

@ Mentions
@neilpfeiffer

@jeremyfuksa we will need some input on this.

@jeremyfuksa we will need some input on this.

Active/Hover color is specified as #1e3a49.

Active/Hover color is specified as #1e3a49.

Thanks for the color input @jeremyfuksa , Can I get some more input on which variables the color is to be applied.

Thanks for the color input @jeremyfuksa , Can I get some more input on which variables the color is to be applied.


The requirement of  cityscapes RGBD dataset

First thank you for sharing the excellent work for us. And for the RGBD segmentation research, we really need the cityscapes RGB-D dataset or the method to get depth map, would you share that in recent times?

Thanks for your attention.
You could get the depth map from the official disparity map (in '.png' file) and camera parameters (in '.json' file).
Here we show some example codes:
disp = cv2.imread(disp_file, cv2.IMREAD_UNCHANGED)    # read the 16-bit disparity png file
disp = np.array(disp).astype(np.float)
disp[disp > 0] = (disp[disp > 0] - 1) / 256    # convert the png file to real disparity values, according to the official documentation.
# you could also refer to https://github.com/mcordts/cityscapesScripts/issues/55#issuecomment-411486510

# read camera parameters
camera_params = json.loads(camera_file)

depth = camera_params['extrinsic']['baseline'] * camera_params['intrinsic']['fx'] / disp
depth[depth == np.inf] = 0
depth[depth == np.nan] = 0

@charlesCXK  hha = getHHA(camera_matrix, D, RD)
what are the RDs for Cityscapes?

@Serge-weihao In Cityscapes, we only have raw depth maps, so D == RD.

Thanks for your attention.
You could get the depth map from the official disparity map (in '.png' file) and camera parameters (in '.json' file).
Here we show some example code:
disp = cv2.imread(disp_file, cv2.IMREAD_UNCHANGED)    # read the 16-bit disparity png file
disp = np.array(disp).astype(np.float)
disp[disp > 0] = (disp[disp > 0] - 1) / 256    # convert the png file to real disparity values, according to the official documentation.
# you could also refer to https://github.com/mcordts/cityscapesScripts/issues/55#issuecomment-411486510

# read camera parameters
camera_params = json.loads(camera_file)

depth = camera_params['extrinsic']['baseline'] * camera_params['intrinsic']['fx'] / disp
depth[depth == np.inf] = 0
depth[depth == np.nan] = 0

The final depth map is in 'meters'. Its median value is around 10 m.
After you obtain the depth map, you could use Depth2HHA-python to generate HHA map. Note that some hyper-parameters in that repo are designed for NYU Depth v2 dataset and we need to change something.

We should clip the depth value because the 'sky' pixels has too large depth values.
depth = np.minimum(depth, 100)      # maximum value is 100 m.
In function getHHA(C, D, RD), some hyper-parameters need to adjust according depth ranges of CityScapes dataset.

I[:,:,2] = 20000/pc[:, :, 2]*6 # 31000/pc[:,:,2]
I[:,:,1] = h/20       # height for cityscapes
I[:,:,0] = (angle + 128-90) + 10

Thank you very much for your help, I will continue to pay attention to your follow-up work . Furthermore, we collected some out door datasets, how should I adjust the hyper-parameters in the Depth2HHA-python to fit our dataset?  I would be very grateful if you could solve my problem.

@SunXusheng5200 Hi, if you could understand Chinese, please refer to this issue:
https://github.com/charlesCXK/RGBD_Semantic_Segmentation_PyTorch/issues/2

@SunXusheng5200 Hi, if you could understand Chinese, please refer to this issue:
#2

十分感谢您的回答，这对我的研究很有帮助！再次感谢！

hi，you paper of the RGB-D can not be opened from the link ???

Hi @charlesCXK  ,
The generated depth img from disparity img exists many unfilled values, have u used some  algorithm to fill in the missing value first or directly trained without processing the missing value?  If yes , could you share the filling algorithm?  Thanks very much !

@TXH-mercury Hi, we didn't use any algorithm to fill in the missing values.

@xiaojiangjiangjinger
Sorry, we haven't planned to upload the HHA maps of Cityscapes online for the time being. Maybe you could try to convert them following https://github.com/charlesCXK/RGBD_Semantic_Segmentation_PyTorch/issues/1#issuecomment-684875832 😄

  好的，谢谢你的回复哦，我可以再问你几个问题吗？我按照GitHub上的提示转HHA后，转出来HHA只有一种颜色，与“Bi-directional Cross-Modality Feature Propagation with Separation-and-Aggregation Gate for RGB-D Semantic Segmentation”论文中的HHA结果图有较大的差异，然后我将cityscapes的深度图线性映射到你给的样例图的深度范围，最终转出来结果还是不对。

  请问你之前对cityscapes转HHA时，对深度图做了处理吗？或者说cityscapes的深度图转HHA有什么要求吗？

  另外，cityscapes的相机参数是否只用到了extrinsic中的baseline和intrinsic中的fx？

  最后，如果没有相机参数的深度图可以直接转HHA吗？

  期待你的回复，谢谢
------------------ 原始邮件 ------------------
发件人:                                                                                "charlesCXK/RGBD_Semantic_Segmentation_PyTorch"<EMAIL_ADDRESS>发送时间: 2020年11月21日(星期六) 下午5:59
收件人<EMAIL_ADDRESS>抄送: "souvenir。"<781131634<EMAIL_ADDRESS>主题: Re: [charlesCXK/RGBD_Semantic_Segmentation_PyTorch] The requirement of  cityscapes RGBD dataset (#1)
@xiaojiangjiangjinger
Sorry, we haven't planned to upload the HHA maps of Cityscapes online for the time being. Maybe you could try to convert them following #1 (comment) 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


OCPBUGS-2083: set default list of TLS ciphers for Kube RBAC sidecars

https://issues.redhat.com/browse/OCPBUGS-2083
Setting this to the same list that was used in Manila:
https://github.com/openshift/csi-driver-manila-operator/pull/145
I don't want to have this string copied in 20 different repos though, it seems better to set a default once in library-go and add a placeholder to the manifests where we want to use it.
/cc @openshift/storage

/jira refresh

/retitle OCPBUGS-2083: set default list of TLS ciphers for Kube RBAC sidecars
The deployment for vmware-vsphere-csi-driver-controller in CI from https://github.com/openshift/vmware-vsphere-csi-driver-operator/pull/117 looks correct:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_vmware-vsphere-csi-driver-operator/117/pull-ci-openshift-vmware-vsphere-csi-driver-operator-master-e2e-vsphere-csi/1587458087034294272/artifacts/e2e-vsphere-csi/gather-extra/artifacts/deployments.json
"--tls-cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
This PR will need to merge first so I can bump library-go in the vmware-vsphere-csi-driver-operator PR.

/lgtm

/cherry-pick release-4.12

/cherry-pick release-4.11
/cherry-pick release-4.10

/cherry-pick release-4.10


Ask the user for the correct command to their script if it is neither a python file or a Jupyter notebook

Part of #3058
https://user-images.githubusercontent.com/3683420/217886002-271eb284-2bb5-498f-b9ae-780645a34b83.mov

Thanks @sroy3 ! One thing to double check - let's make sure that the second step is optional (I think DVC can run a shell script let's say w/o specifying sh). And update the copy if needed.

Thanks @sroy3 ! One thing to double check - let's make sure that the second step is optional (I think DVC can run a shell script let's say w/o specifying sh). And update the copy if needed.

It is you don't have to enter anything for that and it won't block adding the script.


Add an accelerator key for the shell extension

Adds an accelerator key for the shell extension: T for stable, P for preview and D for dev.
Validation
Ran a dev build and saw the keyboard accelerator assigned.
Closes #13061

How do I appease the spelling bot? I don't think adding iew as an allowed word is the right approach. Ideally there would be some way of stating this is OK for this one file, but I don't see how you do that.

Hokay so some notes from discussion:

We like the idea
I think we liked (W, P, and D) as characters anyways - there's always gonna be conflicts with these letters, so might as well go with sensible options.
Localization for this might be Hard. We're gonna look into it on our end and see what the right way to markup these strings is. We need to make sure the translators know that the & identifies the leading character as an accelerator, and for non-latin-character-based languages, the localizations have a trailing latin character for loc purposes.

So we're gonna hold this for 1.15, while we sort out that loc issue. Thanks for your patience!

So to confirm, you'd like D for dev, P for preview and W for stable? i.e. for English:
Open in Terminal (&Dev)
Open in Terminal &Preview
Open in Terminal (&w)

Oh my god I'm so sorry, I clearly didn't even read that comment before I posted it. I meant T, not W. 🤦
Open in Terminal (&Dev)
Open in Terminal &Preview
Open in &Terminal

The action item is still on me to follow up with the File Explorer team (or someone...?) to figure out the right way to express these for future localization. Sorry for the delays, releasing 1.14 has been a persistent fire drill

Yeah I figured it was probably a typo - hence why I questioned it rather than blindly applying it 😛

Thanks @ianjoneill  :)

/azp run

The CI officially hates me - if I merge main into this branch will it still auto-merge, or is it better for you to re-trigger the build yourself?

Just triggered a rerun of the feature tests, they've been flaky all day, sorry 😕

Thanks! I don't know why, but I seem to be particularly unlucky with build flakes.


Not working at all with SpongeForge

No errors are shown in the console, I'm using the server.properties to generate an empty overworld, but when I go to the nether it is normal like if YUNMGM was not installed. Any ideas?
1.10.2
Latest YUNMGM and latest SpongeForge

Talk to the Sponge people.


Distribute on npm

Version and release the library on npm:

[ ] adopt conventional changelog

Using verdaccio to test locally: https://verdaccio.org/docs/installation


I run the bert e2e example, if batch is not 1, I get an error!!!

Description
I run the bert e2e example in the tutorial , i meet a runtimeError.
When I run the original code, it's ok, but if i change  batch dim from 1 to 4 in this line :' shapes = [(1, w) for w in range(8, 128 + 8, 8)] ' ,  I got an error as below:
RuntimeError: unsupported operation: more than one element of the written-to tensor refers to a single memory location. Please clone() the tensor before performing the operation.
example code as below
from kernl.model_optimization import optimize_model

optimize_model(model_opt)
start = time.perf_counter()
shapes = [(1, w) for w in range(8, 128 + 8, 8)]    ## when i change 1 to 4， I got an error!!!
with torch.inference_mode(), torch.cuda.amp.autocast(enabled=True, dtype=torch.float16, cache_enabled=True):
    for s in shapes:
        inputs = {
            "input_ids": torch.ones(s, device="cuda", dtype=torch.long),
            "attention_mask": torch.ones(s, device="cuda", dtype=torch.long),
        }
        _ = model_opt(**inputs)
        _ = model(**inputs)

print(f"{time.perf_counter() - start:.0f}s")

Steps to reproduce
all in description
Expected Behavior
all in description
Actual Behavior
all in description
Your environment

Operating system and version (e.g. Ubuntu 20.04.2 LTS):
Python version (e.g. Python 3.9):
3080Ti
docker run

Self-service

[ ] I would be willing to help fix this bug myself.

Code of Conduct

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

It happens inside CG pool management, during the copy of input tensors.
After debugging, it appears that for some unrelated reason, one of the dim of the stride of input tensor is 0.
It doesn't matter as the related shape dimension is 1, so no one will iterate over it...
But we use those strides (including the 0) to create a view of the pool tensor and PyTorch raise the issue.
Seems to be related to a dimension having a 1 size, and the related stride being 0.
During the creation of a view of the CUDA pool, PyTorch don't like the 0 and makes some crazy stuff.
Same kind of behaviour is happening here: https://github.com/pytorch/pytorch/issues/33812#issuecomment-593127474
Just removing 0 by something else fix it.
@lichun-wang can you try #291 and report here?
On my side, notebook works e2e


New article "Style editing for CSS-in-JS frameworks"

This is a preliminary PR review.  Not shippable yet.  Needs reviewer input on the direction to take this.
Is the TOC title ok?
Is the top-of-page title ok?
Omitted the video/image that's in the blog post, ok?
This draft has ## Blog heading.  Above that, is derived from What's New.  Below that, is from the blog post.

Docs Build status updates of commit e74c9f4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c6a9f8f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f716472:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6765a10:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 96b93e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Language and technical explanation is sound here, but I'm confused about the goal of this article. In essence it says that you can apply CSS to elements in different ways and that DevTools then shows the CSS as it is changed. But that's the same if we manipulated the styles object in JavaScript directly. The original article explains how that was done in devtools, which was the news at the time and it is in there since Chrome 85
That said, we have a new feature in there right now that allows you to copy styles as JS which would tie in much nicer to this story and bring it more up-to-date.

Docs Build status updates of commit 01be40e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/images/copy-declaration-as-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/css-in-js.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2020/06/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@codepo8 @zoherghadyali Please re-review this PR regarding the positioning of these capabilities in the Styles pane in the case of css-in-js libraries/frameworks.  I added a section about Copy declaration as JS.


Vue asset images not loading

Laravel Mix Version: 6.0.9
Node Version: 15.5.1
NPM Version: 7.3.0
OS: Mac OS Big Sur 11.1

Description:
After upgrading to Laravel Mix 6 my build runs successfully but images referenced from the assets folder no longer are loading.
Steps To Reproduce:
Running an existing Laravel v8.21.0 project with Laravel/UI Vue auth scaffolding, after upgrading Laravel Mix to version 6 images referenced from the assets folder in Vue don't err out on build but display as broken images in the browser.
Referencing images as such:

When I inspect the image I see this:

Any help would be greatly appreciated.  Thanks!

Hi,
I faced a similar issue yesterday.
The assets were copied successfully but the src path were not correctly rendered (object instead of a string)
It turned out this was caused by the embedded file-loader, which by default output files with ES6 syntax.
So I had to override the original configuration
mix.override(webpackConfig => {    // Firstly try to find the rule(s) where the file-loader is implyed     console.log(webpackConfig.modules.rules)    // Then modify the loader configuration     webpackConfig.module.rules[2].use[0].options.esModule = false; });
Hope it can help.

Hi,
I faced a similar issue yesterday.
The assets were copied successfully but the src path were not correctly rendered (object instead of a string)
It turned out this was caused by the embedded file-loader, which by default output files with ES6 syntax.
So I had to override the original configuration
mix.override(webpackConfig => {    // Firstly try to find the rule(s) where the file-loader is implyed     console.log(webpackConfig.modules.rules)    // Then modify the loader configuration     webpackConfig.module.rules[2].use[0].options.esModule = false; });
Hope it can help.

@Aiwings Thanks for the response.
I was also able to get the image loaded by doing this:

Both of these solutions feel kinda ugly to me tbh.

@Aiwings Thanks for the response.
I was also able to get the image loaded by doing this:

Both of these solutions feel kinda ugly to me tbh.

Apparently its a bug with vue-loader which Mix uses. Here is my workaround solution. This only sets esModule to false on the images file-loader.
mix.override(webpackConfig => {
  // BUG: vue-loader doesn't handle file-loader's default esModule:true setting properly causing
  //  to be output from vue templates.
  // WORKAROUND: Override mixs and turn off esModule support on images.
  // FIX: When vue-loader fixes their bug AND laravel-mix updates to the fixed version
  // this can be removed
  webpackConfig.module.rules.forEach(rule => {
    if (rule.test.toString() === '/(\\.(png|jpe?g|gif|webp)$|^((?!font).)*\\.svg$)/') {
      if (Array.isArray(rule.use)) {
        rule.use.forEach(ruleUse => {
          if (ruleUse.loader === 'file-loader') {
            ruleUse.options.esModule = false;
          }
        });
      }
    }
  });
});

Apparently its a bug with vue-loader which Mix uses. Here is my workaround solution. This only sets esModule to false on the images file-loader.
mix.override(webpackConfig => {
  // BUG: vue-loader doesn't handle file-loader's default esModule:true setting properly causing
  //  to be output from vue templates.
  // WORKAROUND: Override mixs and turn off esModule support on images.
  // FIX: When vue-loader fixes their bug AND laravel-mix updates to the fixed version
  // this can be removed
  webpackConfig.module.rules.forEach(rule => {
    if (rule.test.toString() === '/(\\.(png|jpe?g|gif|webp)$|^((?!font).)*\\.svg$)/') {
      if (Array.isArray(rule.use)) {
        rule.use.forEach(ruleUse => {
          if (ruleUse.loader === 'file-loader') {
            ruleUse.options.esModule = false;
          }
        });
      }
    }
  });
});

@tinyfly you have a link to an open issue for that?

@ethanclevenger91 Here you go: https://github.com/vuejs/vue-loader/issues/1612

Apparently its a bug with vue-loader which Mix uses. Here is my workaround solution. This only sets esModule to false on the images file-loader.
mix.override(webpackConfig => {
  // BUG: vue-loader doesn't handle file-loader's default esModule:true setting properly causing
  //  to be output from vue templates.
  // WORKAROUND: Override mixs and turn off esModule support on images.
  // FIX: When vue-loader fixes their bug AND laravel-mix updates to the fixed version
  // this can be removed
  webpackConfig.module.rules.forEach(rule => {
    if (rule.test.toString() === '/(\\.(png|jpe?g|gif|webp)$|^((?!font).)*\\.svg$)/') {
      if (Array.isArray(rule.use)) {
        rule.use.forEach(ruleUse => {
          if (ruleUse.loader === 'file-loader') {
            ruleUse.options.esModule = false;
          }
        });
      }
    }
  });
});

I had this issue when i've updated laravel mix from 5 to 6
Got some [object Module] urls for thirds libraries like trumbowyg or remixicons and this solved the issue
Thanks, i hope there will be a fix for this or an option to set the esModule option for file-loader !

@tinyfly I finally got around to implementing your solution and it works great!  Thank you for that and for linking to the issue in vue-loader.

Was the only thing which worked for me. Without the @assets (custom alias in my project) it would not get copied to the public folder and without the .default it would show [object Module] in the html and not render at all.
But I dont feel like this is a definitive solution, it shouldnt be necessary to add .default OR use require at all in my opinion.

Overriding the file-loader via mix.webpackConfig() worked for me:
mix.webpackConfig(webpack => {
    return {
        module: {
            rules: [{
                test: /(\.(png|jpe?g|gif|webp)$|^((?!font).)*\.svg$)/,
                use: [{
                    loader: require.resolve('file-loader'),
                    options: {
                        esModule: false
                    }
                }]
            }]
        }
    };
});

The test regex has to match the default Webpack config in order to override the rule. I used mix.dump() to find out the
default Webpack config.
The config set using mix.override() seemed to be ignored in Mix 6.

Overriding the file-loader via mix.webpackConfig() worked for me:

@321zeno I like this solution better than mine. I'm going to give it a shot. Thanks!

@321zeno Implemented your solution, works great!

@321zeno This solution randomly stopped working for me today.  I initially thought this was due to Laravel Mix updating from 6.0.31 to 6.0.39 but reverting didn't seem to help.  I also thought maybe file-loader was removed as a sub-dependency somewhere but that doesn't seem to be the case.  Anyone else having this issue?

Yes, the same happened for me (although I never had it working before).
The reason seems to be that Mix added support for AVIF images in the loader, altering the regular expression used. Updating the override accordingly made the fix work again:
mix.webpackConfig(webpack => {
    return {
        module: {
            rules: [{
-                test: /(\.(png|jpe?g|gif|webp)$|^((?!font).)*\.svg$)/,
+                test: /(\.(png|jpe?g|gif|webp|avif)$|^((?!font).)*\.svg$)/,
                use: [{
                    loader: require.resolve('file-loader'),
                    options: {
                        esModule: false
                    }
                }]
            }]
        }
    };
});

@loilo and mix also updated the loader from loader: 'file-loader' using path project/node_modules/file-loader/dist/cjs.js'
for me instead of comparing regex strings or writing your own rules i used this solution
const mix = require('laravel-mix')

mix.extend('disabledEsModule', (config) => {
  config.module.rules.forEach((rule) => {
    let regex = new RegExp(rule.test)

    // why .jpg? because it's one of those file extensions that is someone never left him behind.
    if (regex.test('.jpg')) {
      rule.use.forEach((use) => {
        if (use.loader.includes('file-loader')) {
          Object.assign(use.options, { esModule: false })
        }
      })
    }
  })
})

or use this package for more simple https://www.npmjs.com/package/laravel-mix-fileloader

I have faced with the same issue during update from v4 to v6. @321zeno thank you!

@fylzero Yes, the same happened for me (although I never had it working before). The reason seems to be that Mix added support for AVIF images in the loader, altering the regular expression used. Updating the override accordingly made the fix work again:
mix.webpackConfig(webpack => {
    return {
        module: {
            rules: [{
-                test: /(\.(png|jpe?g|gif|webp)$|^((?!font).)*\.svg$)/,
+                test: /(\.(png|jpe?g|gif|webp|avif)$|^((?!font).)*\.svg$)/,
                use: [{
                    loader: require.resolve('file-loader'),
                    options: {
                        esModule: false
                    }
                }]
            }]
        }
    };
});

it is work in my project. @Aslam97 thanks.


this project keeps breaking

Things were working fine until about a week ago when i guess everything was overhauled
I followed the documentation which itself was broken and had fixed in a separate issue.
Now it looks like the date formatting requires leading zeros in the dates, which a few days ago it was required to not have leading zeroes in the dates.
Does anyone know of any other sources I can cURL to get exchange rates because this project has been creating way too much grief for no reason....

Per the documentation, this link works:
https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>But... this does not:
https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>Couldn't find the requested release version '2024-03-14'.
nor does this:
https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>Couldn't find the requested release version 2024-3-2.
nor does this:
https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>Couldn't find the requested release version '2024-3-14'.

OK, I will give this one more try then.
I think what was screwing me up was the back and forth between using leading zeroes and not using leading zeroes in the date, however using latest circumvents this confusion.


[FLINK-19170] fix parameter naming error

What is the purpose of the change
fix parameter naming error
Brief change log
fix parameter naming error
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): ( no)
The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
The serializers: ( no)
The runtime per-record code paths (performance sensitive): ( no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: ( no )
The S3 file system connector: ( no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks ThunderSuuuuuu for looking into that. FYI: There's no need to create FLINK Jira issues for typo fixes. Instead, write [hotfix][<component>] as a prefix to your commit message.

Thanks for your reply. Should I renaming this PR's title?

Thanks ThunderSuuuuuu for looking into that. FYI: There's no need to create FLINK Jira issues for typo fixes. Instead, write [hotfix][<component>] as a prefix to your commit message.

Thanks for your reply. Should I renaming this PR's title?

Hi @ThunderSuuuuu , you don't have to change it now since FLINK-19170 is already created.  And I realized that it does not match the commit guidelines. The commit message should be prefixed with the Jira issue in the following way: [FLINK-XXXXX] ... Feel free to change that.

Thanks a lot for reviewing this @XComp! Merging ... (and closing the JIRA & changing the commit msg)


Helm multicluster deployment artifacts missing on ArtifactHub

Bug Description
Some properties are needed by multicluster deployment and the gateway chart published doesn't support it, but the chart under gateways directory on GitHub supports.
Some examples are injectionTemplate and global.network properties that are required for multicluster and the existing chart doesn't support.
It would be nice to have ingress-gateway chart on ArtifactHub
Version
Latest

Additional Information
No response

Multinetwork is supported: https://artifacthub.io/packages/helm/istio-official/gateway#multi-network-vm-gateway.
Injection template is not needed as its the only method for that chart.
istio-ingressgateway chart is the legacy chart and intentionally not published.


Error: getaddrinfo

I'm getting the following in my console output
[2019-3-12 08:19:28] [Front Door] refresh2 { username<EMAIL_ADDRESS>  diagnostic: 'Error: getaddrinfo ENOENT api.ring.com:443' }

It seems since I'm getting that in my console Homebridge is no longer responding in HomeKit as well.

I'm getting the same error too, and is causing the rest of Homebridge to become non-responsive in HomeKit.

This plugin is now DEPRECATED... you will find a vastly superior plugin here!


Wemake Python Styleguide

Try and evaluate: https://wemake-python-styleguide.readthedocs.io/en/latest/index.html#

Too strict, too many rules to override.


Reflect actual PowerShell invocation necessary in README

It is necessary to pass -ExecutionPolicy Bypass before the script filename if the script is not signed by a code signing certificate.

 I don't think we should be mentioning this, much less mindlessly suggesting to bypass it.

To be fair, you do have a point at that, that any developer able to contribute could probably find -ExecutionPolicy Bypass afrter 1-2mins of searching, and remember it for life.
Although looking into InspectCode.ps1, it could be simply renamed to .bat, after changing $LASTEXITCODE into %ERRORLEVEL%, and then I could just do InspectCode instead of powershell -ExecutionPolicy Bypass .\InspectCode.ps1.
If I added InspectCode.bat which just invocated the PowerShell script, or renamed the .ps1 to .bat, would it be rejected?

Batch scripts are rather antiquated in this day and age, all things considered. I personally much prefer a powershell script even if it doesn't do much. Not sure about other opinions.

Would agree with sticking to powershell rather than downgrading to batch.

To be fair, considering the "feature set" of Batch, bash, and PowerShell, Batch is definitely not known for its ease of use or rich feature set, so me suggesting a downgrade to Batch was perhaps a bit foolhardy of me. Who knows when in the future we might need to find a file programatically in these scripts, but if we had to, it would be painful to do in Batch.
Although I'd still love to have a "launcher" .bat script which launches the PowerShell script with -ExecutionPolicy Bypass, so I wouldn't have to type it out all the time. It's fine typing it out a few times, but when the time you execute it manually becomes multiple digits, then it does get annoying.

You can set powershell execution policy to always allow running local scripts in windows dev settings.

If this is to be added, it should be a line above the script linking to documentation on changing the system execution policy, not attached to the command.
Conflicted to whether we need this though. May be best to leave that for the dev to figure as a bar-of-entry since it's basically something you need to do to dev on windows?

Let's just close this for now, I don't think it's going to go anywhere since we all agree this is not the correct direction.


what's going on here?

the badges have not loaded.. try refreshing the page, it should look like this:


[App]: wandb.Table column of wandb.Images not appearing (possible 0.15.8 regression)

Current Behavior
When logging a wandb.Table that has a column of wandb.Images to a run or artifact, the Web UI omits that column from the table view. This appears to be a regression in 0.15.8, because tables of this kind created using <=0.15.7 appear to work as expected.
Expected Behavior
The image column should appear in the Web UI table view.
Steps To Reproduce

Install 0.15.8
Create a pandas.DataFrame containing a column of wandb.Images
Construct a wandb.Table from the dataframe and log it to a run
View the table from the web UI

Screenshots
No response
Environment
OS: macOS-13.5-arm64-arm-64bit
Browsers: Chrome 115.0.5790.114
Version: 0.15.8
Additional Context
No response

Hello @schmidt-ai !
I did some testing and ran the following code:

run = wandb.init()

img = wandb.Image('image.jpg')
img2 = wandb.Image('image_2.jpg')
img3 = wandb.Image('image_3.jpg')
my_table = wandb.Table(columns=["a", "b"], data=[[img, img3], [img2, img3]])
run.log({"table_key": my_table})

# Pandas
import pandas as pd
df = pd.DataFrame([[img, img3], [img2, img3]])
pd_table = wandb.Table(columns=["a", "b"], data = df)
run.log({"pd_table": pd_table})

The following screenshot was my result. I made sure I am using wandb==0.15.8 so this seems to be working unless I am misunderstanding the steps that was taken.

This looks the same on my end. I am getting the same result either way. Perhaps its the columns=["a", "b"] that is helping with the rendering?

Hello! I went ahead and looked around some more and I am not sure which "table columns" you are referring to in the UI. Are you attempting to visualize the table columns in the runs table?

Thanks for the update! I will make a bug report on this behavior and let the engineers know about it.


[gwctl]Optimize Print in backends

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Optimize print and reduce repeated logic. Maintain agreement with print methods of other resources

/assign

/ok-to-test

Thanks @yeedove!
/lgtm
/approve

/retest

/retest

This requires some lint fixes to pass

/lgtm


Encode String in error message

Description
Encode string in error message to prevent cross scripting attacks
Related issues
#AB105701
Testing
Describe how this change was tested.

Could you elaborate more about this PR and how it prevents a vulnerability?

Could you elaborate more about this PR and how it prevents a vulnerability?

We return the output message without encoding, so because of that, anyone can inject a custom javascript to route to any url or make the customer click any button in their website. Encoding the output string is one way of preventing this reflected XSS attack

Could you add a unit test in the controller code?


Requesting good first issues to contribute

Hi @vvatanabe ,
I hope you are doing well. I found this project fascinating and would like to contribute towards bug fixes, enhancements.
Can you guide me towards working on potential issues so I can start contributing?
Thanks! ☺

@RahulDubey391
I'm delighted to know that you're interested in contributing to the DynamoMQ project. We are planning to officially release the project next month. Once it's released, we will prepare documentation for those who wish to contribute. Please refer to it for guidance on how to get involved. Thanks!

Thanks @vvatanabe , meanwhile I'll have a look into repo and will raise PR for any potential bug fixes or enhancements!

I'll consider closing this since the contributing documents will be provided!


Whitespace, comments etc. tidy up before migration to JUnit 5

Formatting/tidy up PR, before committing for review JUnit 5 work.
Sorry it's so long but it the JUnit 5 changes touch a lot of files and don't want these changes causing and confusion or delay.

I wonder if "remove optional semicolon in Groovy" can be configured with Spotless.

@ham1 , do you really intend to touch *.groovy files in JUnit5?
Even though the changes you propose look good, and they improve things, it is tricky that current Spotless/Checkstyle are happy with the current code.
That means new contributions might easily add code with the same formatting that you have just removed. Are you going to continuously format incoming code?
For instance: "optional semicolons in Groovy". I see you removed certain items, however, you don't seem to add the relevant Spotless configuration.
PS. It looks like you've committed Before->BerforeEach which caused Travis failure.

I didn't intend to touch Spock tests, however I did accidentally when changing @Ignore to @Disabled and while fixing that issue I also tidied up some of the files.
You are correct, I'm not going to continually format the code, but I can't not do it when I see it :smile: and I think it's better to make changes for the better so that:

others see it and might also learn/follow and
it's better than giving up and making the entropy continually worse

I will have a look into the Groovy-Eclipse formatter for Spotless.

Codecov Report

Merging #514 into master will decrease coverage by <.01%.
The diff coverage is 72.13%.

@@             Coverage Diff              @@
##             master     #514      +/-   ##
============================================
- Coverage     55.96%   55.96%   -0.01%
  Complexity     9949     9949
============================================
  Files          1018     1018
  Lines         62734    62736       +2
  Branches       7057     7057
============================================
+ Hits          35111    35112       +1
  Misses        25161    25161
- Partials       2462     2463       +1

Impacted Files
Coverage Δ
Complexity Δ

...mple/src/main/java/test/Junit4AnnotationsTest.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...-sample/src/main/java/test/DummyAnnotatedTest.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...org/apache/jmeter/report/core/CsvSampleWriter.java
90.24% <100%> (ø)
12 <0> (ø)
:arrow_down:

...ain/java/org/apache/jorphan/util/JOrphanUtils.java
81.53% <71.66%> (+0.14%)
85 <24> (ø)
:arrow_down:

...a/org/apache/jmeter/timers/PoissonRandomTimer.java
72.97% <0%> (-5.41%)
9% <0%> (-1%)

...n/java/org/apache/jmeter/reporters/Summariser.java
86.25% <0%> (+0.76%)
19% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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

LTGM

I've just rebased, is someone ok to merge this so I can show the JUnit 5 migration? :smile:

@ham1 , I see you contribute a lot. This is nice.
I have a lifehack for you: you can unlock Travis in your own JMeter fork https://travis-ci.org/ham1/jmeter
It might provide you with a faster turnaround.
The thing is all Apache projects have a limited set of Travis runners, and it often happens that it takes a lot to wait for Travis job to even start (because the runners are busy with building other ASF projects).

That is a good tip, thanks, I hadn't realised that was possible.


The return from  az repos pr create  does not show the commits or number of commits in source branch not in targetbranch

Describe the bug
in the return from
$return = az repos pr create     --project $project
--repository $repository     --source-branch $sourcebranch
--target-branch $targetbranch ` |
ConvertFrom-Json;
the return does not have  commits populated and shows 0 or null.
artifactId            : vstfs:///Git/PullRequestId/a66dd09e-1cf1-4979-af37-7a9440d4f98d%2f06ec5fd1-a2bf-44c3-9c71-0a8edbf2e922%2f15700
autoCompleteSetBy     :
closedBy              :
closedDate            :
codeReviewId          : 15700
commits               :
completionOptions     :
completionQueueTime   :
createdBy             :
creationDate          : 2023-10-03T15:52:18.402373+00:00
description           :
forkSource            :
isDraft               : False
labels                :
lastMergeCommit       :
lastMergeSourceCommit : @{author=; changeCounts=; changes=; comment=; commentTruncated=;
commitId=e45c7f46b4dfa50b15a4815cc04a7abe621a2839; committer=; parents=; push=; remoteUrl=; statuses=; url=https://
dev.azure.com/sdfsdfsdf/a66dd09e-1cf1-4979-af37-7a9440d4f98d/_apis/git/repositories/06ec5fd1-a2bf-44c3-9c71-0a8e
dbf2e922/commits/e45c7f46b4dfa50b15a4815cc04a7abe621a2839; workItems=}
lastMergeTargetCommit : @{author=; changeCounts=; changes=; comment=; commentTruncated=;
commitId=111e3f98890ccaf65185f6d1774bfd0df6614ae8; committer=; parents=; push=; remoteUrl=; statuses=; url=https://
dev.azure.com/sdfsdfsdfs/a66dd09e-1cf1-4979-af37-7a9440d4f98d/_apis/git/repositories/06ec5fd1-a2bf-44c3-9c71-0a8e
dbf2e922/commits/111e3f98890ccaf65185f6d1774bfd0df6614ae8; workItems=}
mergeFailureMessage   :
mergeFailureType      :
mergeId               : 08d33003-6d98-4088-8939-6e1b02d6443a
mergeOptions          :
mergeStatus           : queued
pullRequestId         : 15700
remoteUrl             :
repository            :
reviewers             :
sourceRefName         : refs/heads/PDM-513
status                : active
supportsIterations    : True
targetRefName         : refs/heads/development
title                 : update and add dummy change for testing prs
url                   : https://dev.azure.com/sdfsdfdsfsf/a66dd09e-1cf1-4979-af37-7a9440d4f98d/_apis/git/repositories/06ec5fd1-a2bf-44c3-9
c71-0a8edbf2e922/pullRequests/15700
workItemRefs          :
Related command
NA
Errors
NA
Issue script & Debug output
NA
Expected behavior
I would expect the return  of new PR creation to have some details on number of commits relative to the target branch.
Environment Summary
azure-cli                         2.52.0 *
core                              2.52.0 *
telemetry                          1.1.0
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                            1.24.0b1
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Lance_Lyons.azure\cliextensions'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
We are trying to make sure a completed   PR from $sourcebranch to $targetbranch doesnt have additional commits not merged before deleting the PR branch.
sometimes a PR branch is used for several commits into the target branch.

Thank you for opening this issue, we will look into it.

I upgraded to 2.53 and get the same bug.  No commit is shown in the return even though there is a commit that has not been merged.
azure-cli                         2.53.0
core                              2.53.0
telemetry                          1.1.0
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Lance_Lyons.azure\cliextensions'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.

Any update on this issue? I have a use case where I would like to create a PR only if there's change between the source and target branches (git). However the az repos pr create will create a PR despite there's no changes between the branches.
I am trying to get around this by listing only the repos has changed commits az repos pr list however, I was unable to filter due to all "commits" properties are null


Deployment Documentation

Would be great if there could be some documentation on how to deploy a local WP Docker setup to the cloud like Digital Ocean or Amazon Web Services.

This project is really agnostic to deployment methodology.

I see. Sorry to hear that. But will check out other options then.

Found https://github.com/fabrica-wp/fabrica-dev-kit that may work for me. Also Docker based. They use Wordmove for deployment.

@jasperf another option is Laradock


[dev/flutter2] Local view is broken on iOS (RtcLocalView.TextureView from example)

Describe the bug
On iOS the local view doesn't work as expected. Testing the example from latest dev/flutter2 branch.

On iPhone (running 14.7.1), the local view is unproportionally scaled and video remote streams do not show up.
On iPad (running 13.5.1), the local view is incorrectly rotated. The transmitted video is correct though. Using the back camera causes the local view to disappear.

Screenshots
You get to see my happy face:

Smartphone (please complete the following information):

Device: iPhone XS
OS: iOS 14.7.1
Version dev/flutter2

This is a known issue, you can keep using the SurfaceView.

FWIW, this seems to be fixed now.


Bert Slice Support

Sprint on making sure all slice configs are supported in Bert.
These are the shapes, I think they should be supported but please can we check and report any issues.
Update the Status column for the shapes that are supported and add these shapes to unit test.
As a side also make sure these shapes are swept on as we already have a sweep test for slice
CC: @ayerofieiev-tt
aten.slice.Tensor

ATen Input Variations
Status

0
Tensor<[1, 1, 1, 256]> self = ?,int<> dim = 3,Optional[int]<> start = 0,Optional[int]<> end = -1
Unknown

1
Tensor<[1, 256]> self = ?,int<> dim = 0,Optional[int]<> start = 0,Optional[int]<> end = -1
Unknown

2
Tensor<[1, 512]> self = ?,int<> dim = 0,Optional[int]<> start = 0,Optional[int]<> end = -1
Unknown

3
Tensor<[1, 512]> self = ?,int<> dim = 1,Optional[int]<> start = 0,Optional[int]<> end = 256
Unknown

These work but only for tiled as they need padding.
https://github.com/tenstorrent/tt-metal/pull/12469 this change should make them work.

They work for row major with the float32 datatype

Closing this as I copied it into the proper project (tt-metal)


Intrinsics calls in nmodl (from eigen) when nmodl and gpu are enabled lead to compilation error

"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1056: error:
          function "_mm_castpd_ps" has already been defined
  static inline __m128  _mm_castpd_ps   (__m128d x) { return reinterpret_cast<__m128&>(x);  }
                        ^
"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1057: error:
          function "_mm_castpd_si128" has already been defined
  static inline __m128i _mm_castpd_si128(__m128d x) { return reinterpret_cast<__m128i&>(x); }
                        ^
"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1058: error:
          function "_mm_castps_pd" has already been defined
  static inline __m128d _mm_castps_pd   (__m128  x) { return reinterpret_cast<__m128d&>(x); }
                        ^
"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1059: error:
          function "_mm_castps_si128" has already been defined
  static inline __m128i _mm_castps_si128(__m128  x) { return reinterpret_cast<__m128i&>(x); }
                        ^
"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1060: error:
          function "_mm_castsi128_ps" has already been defined
  static inline __m128  _mm_castsi128_ps(__m128i x) { return reinterpret_cast<__m128&>(x);  }
                        ^
"/gpfs/bbp.cscs.ch/project/proj16/cattabia/coreNeuronIssue269/nmodl/build/insta
          ll/include/Eigen/src/Core/arch/SSE/PacketMath.h", line 1061: error:
          function "_mm_castsi128_pd" has already been defined
  static inline __m128d _mm_castsi128_pd(__m128i x) { return reinterpret_cast<__m128d&>(x); }

it is related to this nmodl issue.

This was closed by https://github.com/BlueBrain/CoreNeuron/pull/286.