Appstudio update test-custom-default-branch-hlde

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-imlj-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Add type parameters for types used in df.merge

[x] Closes https://github.com/pandas-dev/pandas-stubs/issues/946
[ ] Tests added: Please use assert_type() to assert the type of any return value

Closes: https://github.com/pandas-dev/pandas-stubs/issues/946
I verified that the df.merge parts of this test fail in pyright strict mode without these changes, and do not after these changes.

Looks like since I merged your first MR, you'll have to merge in main then push to resolve conflicts. @JanEricNitschke


kubevirt, ci: add GitHub issue template for flaky tests

What this PR does
Before this PR:
Flaky tests had to be reported with the standard issue templates.
After this PR:
Adds a template with which flaky tests can be reported.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer
/cc @brianmcarey @xpivarc

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/release-note none

/release-note-none

This PR is waiting for three weeks now.
@xpivarc may I kindly ask for a review of this one?

Looks good @dhiller - I just have a couple of questions inline.

@brianmcarey thank you for the review, I addressed your comments. PTAL, thanks a lot!

Required labels detected, running phase 2 presubmits: /test pull-kubevirt-e2e-windows2016 /test pull-kubevirt-e2e-kind-1.27-vgpu /test pull-kubevirt-e2e-kind-sriov /test pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-storage /test pull-kubevirt-e2e-k8s-1.29-sig-compute /test pull-kubevirt-e2e-k8s-1.29-sig-operator /test pull-kubevirt-e2e-k8s-1.30-sig-network /test pull-kubevirt-e2e-k8s-1.30-sig-storage /test pull-kubevirt-e2e-k8s-1.30-sig-compute /test pull-kubevirt-e2e-k8s-1.30-sig-operator

I think running CI here is a complete waste :-1:


Fix require statement for clark

See also: https://github.com/github/hubot-scripts/issues/1255

We are actually moving away from adding scripts to repository in favor of separate npm packages per scripts. We have already stopped accepting new scripts, and will stop accepting pull requests on this repository after hubot 3.0.
See #1113 for details. If you are interested in maintaining this longer term, check npm in case someone already made a package for it, and if not, check out https://hubot.github.com/docs/scripting/ for creating a package of your own.


test: add tests for submitter input validation

Fixes: N/A
What was the problem/requirement? (What/Why)
There is no test to verify the input of the submitter has been validated
What was the solution? (How)
Use the Qt pytest to verify the input in the submitter has been validator
What is the impact of this change?
Submitter input will be verified to be validated
How was this change tested?
See DEVELOPMENT.md for information on running tests.

Have you run the unit tests?  No
Have you made changes to the download or asset_sync modules? If so, then it is highly recommended
that you ensure that the docker-based unit tests pass. No

Was this change documented?

Are relevant docstrings in the code base updated? No
Has the README.md been updated? If you modified CLI arguments, for instance. No

Does this PR introduce new dependencies?
This library is designed to be integrated into third-party applications that have bespoke and customized deployment environments. Adding dependencies will increase the chance of library version conflicts and incompatabilities. Please evaluate the addition of new dependencies. See the Dependencies section of DEVELOPMENT.md for more details.

[X] This PR adds one or more new dependency Python packages. I acknowledge I have reviewed the considerations for adding dependencies in DEVELOPMENT.md.
[ ] This PR does not add any new dependencies.

Is this a breaking change?
A breaking change is one that modifies a public contract in a way that is not backwards compatible. See the
Public Contracts section
of the DEVELOPMENT.md for more information on the public contracts.
If so, then please describe the changes that users of this package must make to update their scripts, or Python applications.
This change may break the hatch run test for ubuntu users if they don't have the required libs on their os
Does this change impact security?

Does the change need to be threat modeled? For example, does it create or modify files/directories that must only be readable by the process owner?

If so, then please label this pull request with the "security" label. We'll work with you to analyze the threats.

This change does not impact security

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Added the notes in the uni tests section of development document


Add downsampling tool(s)

cc @low-sky, re: conversation yesterday
I can't promise yet that the WCS is correct or even that the code works... but I'll be trying soon?

Coverage increased (+0.2%) to 75.419% when pulling 4bcf66d3261de20aebcb46e9f52ec7501960cd03 on keflavich:downsample_axis into 110bd3c23baa2841d5af83dac88f437d652fe98c on radio-astro-tools:master.


[tensor] argmax bugfix

Apply memory allocation bugfix to argmax
where a empty vector is being addressed
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #828. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


flutter project doesn't run or build apk

at first I have a problem with my project which occur surprisal,
then I found some solution which advise to update my flutter sdk
after this, i have this problem ..
/C:/flutterOperand of null-aware operation '!' has type 'SchedulerBinding' which excludes null/.pub-cache/hosted/pub.dartlang.org/flutter_math_fork-0.5.0/lib/src/widgets/selection/overlay.dart:141:26: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.  - 'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('/C:/flutter/packages/flutter/lib/src/scheduler/binding.dart').

Hi @hashem7mohammed,
Please provide the output of flutter doctor -v  and flutter run -v (the output may be huge so kindly put it into a .txt file and attach it here).
Please also provide your pubspec.yaml
Thank you

thanks for your email,
I'm downgrade my flutter sdk from 3.0.5 to 2.10.5 after that my app is run
normal but i still have a problem when build apk,
this problem occur in my to projects,
I attach two files one for every project,every file have the message after
trying to build apk, and the flutter doctor -v message
Sent from Mail https://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Daniel Agbemava @.>
Sent: Wednesday, July 27, 2022 12:40 PM
To: flutter/flutter @.>
Cc: Hashem Hejazy @.>; Mention
@.**>
*Subject: *Re: [flutter/flutter] flutter project doesn't run or build apk
(Issue #108426)
Hi @hashem7mohammed https://github.com/hashem7mohammed,
Please provide the output of flutter doctor -v and flutter run -v (the
output may be huge so kindly put it into a .txt file and attach it here).
Please also provide your pubspec.yaml
Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/108426#issuecomment-1196500410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7QYGC3KZGILBXGWFG5QJTVWD7XJANCNFSM54YWZJLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
terminal build apk
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\firebase_messaging-11.4.4\android\src\main\java\io\flutter\plugins\firebase\messaging\JobIntent
Service.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\printing-5.6.5\android\src\main\java\net\nfet\flutter\printing\PrintingPlugin.java uses or over
rides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:lintVitalRelease'.

Lint infrastructure error
Caused by: java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.android.tools.lint.gradle.api.ReflectiveLintRunner.runLint(ReflectiveLintRunner.kt:38)
at com.android.build.gradle.tasks.LintBaseTask.runLint(LintBaseTask.java:117)
at com.android.build.gradle.tasks.LintPerVariantTask.lint(LintPerVariantTask.java:67)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:555)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:540)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:523)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$300(ExecuteActionsTaskExecuter.java:108)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecut
er.java:271)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:260)
at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:34)
at java.base/java.util.Optional.orElseGet(Optional.java:369)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:34)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:67)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:36)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:49)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:34)
at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:43)
at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:44)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:54)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:38)
at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:42)
at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:159)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:72)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:43)
at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:44)
at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:33)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:92)
at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:85)
at java.base/java.util.Optional.map(Optional.java:265)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:94)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:49)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:79)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:53)
at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:78)
at java.base/java.util.Optional.orElseGet(Optional.java:369)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:78)
at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:39)
at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:40)
at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:28)
at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:187)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:179)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: com.android.builder.errors.EvalIssueException: Failed to parse XML in C:\Users\HP\OneDrive\Desktop\New folder\triumph\android\app\src
main\AndroidManifest.xml
ParseError at [row,col]:[8,9]
Message: expected start or end tag
at com.android.builder.errors.IssueReporter.reportError(IssueReporter.kt:106)
at com.android.builder.errors.IssueReporter.reportError$default(IssueReporter.kt:102)
at com.android.builder.errors.IssueReporter.reportError(IssueReporter.kt)
at com.android.build.gradle.internal.ide.ModelBuilder.inspectManifestForInstantTag(ModelBuilder.java:541)
at com.android.build.gradle.internal.ide.ModelBuilder.createVariant(ModelBuilder.java:696)
at com.android.build.gradle.internal.ide.ModelBuilder.buildAndroidProject(ModelBuilder.java:374)
at com.android.build.gradle.internal.ide.ModelBuilder.buildAll(ModelBuilder.java:194)
at com.android.build.gradle.internal.AppModelBuilder.buildAll(AppModelBuilder.kt:63)
at org.gradle.tooling.provider.model.internal.DefaultToolingModelBuilderRegistry$LenientToolingModelBuilder$1.create(DefaultToolingModelBui
lderRegistry.java:121)
at org.gradle.api.internal.project.DefaultProjectStateRegistry.allowUncontrolledAccessToAnyProject(DefaultProjectStateRegistry.java:157)
at org.gradle.tooling.provider.model.internal.DefaultToolingModelBuilderRegistry$LenientToolingModelBuilder.buildAll(DefaultToolingModelBui
lderRegistry.java:118)
at com.android.build.gradle.internal.plugins.LintModuleLoader.createAndroidProject(LintModuleLoader.kt:70)
at com.android.build.gradle.internal.plugins.LintModuleLoader.createLintBuildModel(LintModuleLoader.kt:51)
at com.android.build.gradle.internal.plugins.LintModuleLoader.getModule(LintModuleLoader.kt:44)
at com.android.tools.lint.gradle.ProjectSearch.createLintBuildModel(ProjectSearch.kt:371)
at com.android.tools.lint.gradle.ProjectSearch.getBuildModule(ProjectSearch.kt:60)
at com.android.tools.lint.gradle.ProjectSearch.getProject(ProjectSearch.kt:77)
at com.android.tools.lint.gradle.LintGradleClient.configureLintRequest(LintGradleClient.kt:194)
at com.android.tools.lint.LintCliClient.createLintRequest(LintCliClient.kt:476)
at com.android.tools.lint.LintCliClient.run(LintCliClient.kt:236)
at com.android.tools.lint.gradle.LintGradleClient.run(LintGradleClient.kt:255)
at com.android.tools.lint.gradle.LintGradleExecution.runLint(LintGradleExecution.kt:259)
at com.android.tools.lint.gradle.LintGradleExecution.lintSingleVariant(LintGradleExecution.kt:275)
at com.android.tools.lint.gradle.LintGradleExecution.analyze(LintGradleExecution.kt:62)
... 112 more

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

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

BUILD FAILED in 2m 17s
Running Gradle task 'assembleRelease'...                          138.8s
Gradle task assembleRelease failed with exit code 1
doctor -v
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1826], locale en-US)
• Flutter version 2.10.5 at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (3 months ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc5)
• Android SDK at C:\Users\HP\AppData\Local\Android\sdk
• Platform android-33, build-tools 31.0.0-rc5
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
• All Android licenses accepted.
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 4.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
[√] VS Code (version 1.69.2)
• VS Code at C:\Users\HP\AppData\Local\Programs\Microsoft VS Code
• Flutter extension can be installed from:
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (3 available)
• SM A225F (mobile) • RR8RC07JBDL • android-arm64  • Android 12 (API 31)
• Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.19044.1826]
• Edge (web)        • edge        • web-javascript • Microsoft Edge 103.0.1264.71
[√] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 2 categories.
Terminal message:
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:lintVitalRelease'.

Could not resolve all artifacts for configuration ':image_picker_android:debugUnitTestRuntimeClasspath'.
Failed to transform bcprov-jdk15on-1.68.jar (org.bouncycastle:bcprov-jdk15on:1.68) to match attributes {artifactType=processed-jar, org.gradle
.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-runtime}.
Execution failed for JetifyTransform: C:\Users\HP.gradle\caches\modules-2\files-2.1\org.bouncycastle\bcprov-jdk15on\1.68\46a080368d38b428d
237a59458f9bc915222894d\bcprov-jdk15on-1.68.jar.
Failed to transform 'C:\Users\HP.gradle\caches\modules-2\files-2.1\org.bouncycastle\bcprov-jdk15on\1.68\46a080368d38b428d237a59458f9bc9
15222894d\bcprov-jdk15on-1.68.jar' using Jetifier. Reason: IllegalArgumentException, message: Unsupported class file major version 59. (Run with --
stacktrace for more details.)
Suggestions:
- Check out existing issues at https://issuetracker.google.com/issues?q=componentid:460323&s=modified_time:desc, it's possible that thi
s issue has already been filed there.
- If this issue has not been filed, please report it at https://issuetracker.google.com/issues/new?component=460323 (run with --stacktr
ace and provide a stack trace if possible).

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

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

BUILD FAILED in 16s
Running Gradle task 'assembleRelease'...                           17.7s
Gradle task assembleRelease failed with exit code 1
doctor-v
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1826], locale en-US)
• Flutter version 2.10.5 at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (3 months ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc5)
• Android SDK at C:\Users\HP\AppData\Local\Android\sdk
• Platform android-33, build-tools 31.0.0-rc5
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
• All Android licenses accepted.
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 4.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
[√] VS Code (version 1.69.2)
• VS Code at C:\Users\HP\AppData\Local\Programs\Microsoft VS Code
• Flutter extension can be installed from:
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (3 available)
• SM A225F (mobile) • RR8RC07JBDL • android-arm64  • Android 12 (API 31)
• Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.19044.1826]
• Edge (web)        • edge        • web-javascript • Microsoft Edge 103.0.1264.71
[√] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 2 categories.

Hi @hashem7mohammed, it would be best if you reply on github instead of through email as the attachments are not forwarded to github and the messages cannot be properly formatted.
Please also only provide the information for the issue that was initially filed.
The two projects may have different issues so kindly file a new issue for whatever issue it is that your other project is facing.
Please provide the information requested in the issue template when you are filing the new issue.
That aside please provide the full output of flutter run -v  and your pubspec.yaml on this thread
Thank you

I added following lines in the android section of app level build.gradle of my project.
lintOptions {
disable 'InvalidPackage'
disable "Instantiatable"
checkReleaseBuilds false
abortOnError false
}

Thank you ..
I found this somewhere in the internet before and it's work done ..
Thank you for your email
On Thu, Aug 4, 2022, 10:09 AM Subin Suresh @.***> wrote:

I added following lines in the android section of app level build.gradle
of my project.
lintOptions {
disable 'InvalidPackage'
disable "Instantiatable"
checkReleaseBuilds false
abortOnError false
}
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/108426#issuecomment-1204854549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7QYGERVWFZ35DYJUXZTZ3VXNUDNANCNFSM54YWZJLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @hashem7mohammed, has this issue been resolved?

Yes ..
Thank you
On Thu, Aug 4, 2022, 2:12 PM Daniel Agbemava @.***>
wrote:

Hi @hashem7mohammed https://github.com/hashem7mohammed, has this issue
been resolved?
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/108426#issuecomment-1205112896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7QYGGF4J7JF6KR6ILHCW3VXOQQLANCNFSM54YWZJLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing as solved.
Thank you

Yes .. Thank you
…
On Thu, Aug 4, 2022, 2:12 PM Daniel Agbemava @.> wrote: Hi @hashem7mohammed https://github.com/hashem7mohammed, has this issue been resolved? — Reply to this email directly, view it on GitHub <#108426 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK7QYGGF4J7JF6KR6ILHCW3VXOQQLANCNFSM54YWZJLQ . You are receiving this because you were mentioned.Message ID: @.>

how do you solve this problem?


Add NOTICE and DISCLAIMER.

@brennonyork please review

Given this error from travis
[ERROR] Failed to execute goal on project dt-api: Could not resolve dependencies for project com.datatorrent:dt-api:jar:3.1.0: Failed to collect dependencies at com.datatorrent:netlet:jar:1.2.0-SNAPSHOT: Failed to read artifact descriptor for com.datatorrent:netlet:jar:1.2.0-SNAPSHOT: Could not transfer artifact com.datatorrent:netlet:pom:1.2.0-SNAPSHOT from/to codehaus-snapshots (https://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]

I have a feeling its because we don't have com.datatorrent:netlet:jar:1.2.0-SNAPSHOT in the datatorrent releases repo. We also set the snapshots: false as well so I'd assume, even if it were there, if wouldn't pull it down. Does that make sense?
Not sure what's going on here, but it also looks like we've updated the japicmp to compare against 3.1.0 rather than 3.0.0 which is that it was when Travis was working.

That's a bug. Thanks for bringing it up. Will have a fix ready shortly.

Good now. The problem was a goof with the version number replacement in the 3.1.0 release, which was eventually propagated to the master branch. Tracked in https://malhar.atlassian.net/browse/APEX-34

@tweise looks good! I'll merge this into master.


Add Support for Volumes (docker-compose.uffizzi.yml)

Add Uffizzi Compose support for volumes (short and long syntax) as define by Docker Compose here:
https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes

@zipofar Please see this example for generic ephemeral volumes.
To support the ./healthchecks example, assume:

Volume type ephemeral (Generic).
Storage is local (Assume the volume to mount exists as a local directory in the git repo — similar to how we use config files).
Volume max size is 500MB

@gadkins What do you think about this method of determining volumes:
For example user have compose file like this:
services:
  web:
    image: my_web_service

  nginx:
    image: nginx
    volumes:
      - ./images:/image_volumes

Our idea is that the user add rules like this:
x-uffizzi-volumes:
  - target_service: nginx
    source_service: web
    source_root_dir: /app

Why we should use some additional things for volumes.
There are three types of volumes:

Anonymous volumes - /var/some_folder - it's very easy
Named volumes - data:/var/some_folder - this is use the persistent volumes (we don't want to support this)
Bind mounts:

- /source_host_folder:/target_container_folder
- ./source_host_folder:/target_container_folder
- ~/source_host_folder:/target_container_folder

For Bind mounts case we should deliver files from host folder to k8s container folder.
Let's consider a scenario when we upload some files from a host to the our uffizzi database. Next we send these files to the uffizzi controller(it's in k8s). In this case there is no way to load these files into container, that locate in a different pod.
That's why we offer the solution above with additional tag x-uffizzi-volumes:
In this case user create the image my_web_service from his project. Add tag x-uffizzi-volumes to compose file. Into k8s we start the two containers web and nginx in single pod and share the folder /app/images between this containers.

Waiting for controller update


Adds Gradle cache and Ktlint to Github actions

The Gradle cache actions have been taken from @chrisbanes 's Tivi project:
https://github.com/chrisbanes/tivi/blob/master/.github/workflows/build.yml


Unsupported Core Version 0.14.2

Found a bug? Maybe our Slack Community can help.

Describe the Bug
Initializing modules...

Error: Unsupported Terraform Core version

  on .terraform/modules/ec2-bastion-server.dns.this/versions.tf line 2, in terraform:
   2:   required_version = ">= 0.12.0, < 0.14.0"

Module module.ec2-bastion-server.module.dns.module.this (from
git::https://github.com/cloudposse/terraform-null-label.git?ref=tags/0.19.2)
does not support Terraform version 0.14.2. To proceed, either choose another
supported Terraform version or update this version constraint. Version
constraints are normally set for good reason, so updating the constraint may
lead to other errors or unexpected behavior.

Expected Behavior
I expected the terraform init to setup the ec2-bastion-server module successfully.
Steps to Reproduce
Steps to reproduce the behavior:

Use terraform 0.14.2
Use the cloudposse/ec2-bastion-server module
Perform terraform init

Screenshots
Initializing modules...

Error: Unsupported Terraform Core version

  on .terraform/modules/ec2-bastion-server.dns.this/versions.tf line 2, in terraform:
   2:   required_version = ">= 0.12.0, < 0.14.0"

Module module.ec2-bastion-server.module.dns.module.this (from
git::https://github.com/cloudposse/terraform-null-label.git?ref=tags/0.19.2)
does not support Terraform version 0.14.2. To proceed, either choose another
supported Terraform version or update this version constraint. Version
constraints are normally set for good reason, so updating the constraint may
lead to other errors or unexpected behavior.

Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:

OS: MacOS
Version 10.15.7

Additional Context
Add any other context about the problem here.

Hi @sfc-gh-pkommini this is not a bug it is just that the constraints in the module do not support 0.14.2 but you can send a PR to fix that.
you can follow this doc : https://docs.cloudposse.com/community/updating-modules-for-terraform-14/

@jamengual I was able to get to this step:
If you have made any changes, run make pr/auto-format to rebuild the README
What does it mean to check in the changes? I am unable to do a git push on the feature branch that I'm working on at this time.

after you run the commands then you need to push the changes upstream ( git add, git commit, git push)

I understood my issue now. I created a fork. Now I should be able to make
the changes and push a PR.
On Tue, Dec 22, 2020 at 10:32 PM PePe Amengual<EMAIL_ADDRESS>wrote:

after you run the commands then you need to push the changes upstream (
git add, git commit, git push)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudposse/terraform-aws-ec2-bastion-server/issues/50#issuecomment-749965258,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARJIDHXO4RW57IZJ2IXKPO3SWGFGDANCNFSM4VGPYWQA
.

--
Regards,
Prasanth. K.

@sfc-gh-pkommini sorry but the module that is failing is cloudposse/route53-cluster-hostname/aws but that module was just updated to support 0.14 so you just need to update the module version instantiation

this line https://github.com/cloudposse/terraform-aws-ec2-bastion-server/blob/master/main.tf#L131 to 0.9.0 but please do the commands in the guide plus this change

I've made the changes here.

I am able to perform terraform init now. Thank you!


Switching browser windows on non-angular pages

I was wondering if I could get some more information about switching windows in chrome. I have to non-angular pages and after a submit a form another window opens and I am trying to access that window. I have tried just getting getting all the handles and just accessing handles[1], but it seems to just stall on trying to get this handle and gives me a Failed: timeout: Timed out receiving message from renderer: 10.000. I do see the second window open and it seems to be accessible. The handles.length I get it 2 so I know it sees something. I just don't know why I can't access that second handle.
I thought maybe it would be linked to this issue, but my code does pass once in a while: https://bugs.chromium.org/p/chromedriver/issues/detail?id=817
I apologize if this should be in stackexchange. I do have a question posted there with my detailed code: http://stackoverflow.com/questions/36271826/switching-windows-and-focus-in-webdriver-with-non-angular-pages/36285686#36285686
Selenium standalone version: 2.52.0
Chromedriver version: 2.21
Chrome: 49.0.2623.110
Protractor version: 3.2.2

Hi there!
You did the right thing by asking on StackOverflow. The protractor issue queue is not for debugging questions. It looks like you are dealing with a lot of waiting for pages to load. I'd recommend narrowing down your question to the smallest possible reproducible example to get help.
I'm going to go ahead and close this issue because StackOverflow or Gitter are the right places to proceed.
Thanks!


Context Menu unintentionally disabled by default

In Item.js, the context menu handler has an if statement checking for whether there is a handler passed in as a prop:
https://github.com/namespace-ee/react-calendar-timeline/blob/9182d7eb9a1cef7027dae26c4ceb485ed7cf4b07/src/lib/items/Item.js#L499-L505
However, the condition is superfluous because a handler is always passed in to the <Items> component, starting in Timeline.js:
https://github.com/namespace-ee/react-calendar-timeline/blob/9182d7eb9a1cef7027dae26c4ceb485ed7cf4b07/src/lib/Timeline.js#L824
https://github.com/namespace-ee/react-calendar-timeline/blob/9182d7eb9a1cef7027dae26c4ceb485ed7cf4b07/src/lib/Timeline.js#L606-L611
Because it will never be undefined, context menu click event handlers will be passed into the <div> but will be defaultPrevented automatically, meaning that we aren't able to open the default browser context menu in any case.
Would it be possible to set the onItemContextMenu prop for the <Items> component conditionally, only if an actual handler is defined? Such as the following:
<Items
  ...
  onItemContextMenu={ this.props.onItemContextMenu ? this.contextMenuClickItem : undefined }
  ...
  />

@aigyptios I have refactored this in beta I think. Could you check the develop branch?

Hi @Ilaiwi, I'm not seeing the changes you're referring to on the develop branch. Could you send me a link? Thank you!

@Ilaiwi is this still being maintained? If not, can I be added as a maintainer so we can keep updating various pieces of it.

@Ilaiwi ping

released in 0.28.0


generated documentation is not always valid rst

For example, ## this is not *valid rst while ## this is * valid rst, and this creates problems for nim doc which result in no documentation being generated at all.

It should be word-wrapped, too.


The type initializer for 'Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration' threw an exception.

If you are reporting bug/issue, please provide detailed Repro instructions.
Repro Steps

Add ApplicationInsights package to the project.
Use TelemetryConfiguration.

Note; this is likely related to the actual project (I don't believe something like this would slip through if not). I'm trying to use this in an Azure Function project, but I'm unfortunately unable to produce a reduced example.
Actual Behavior
During application startup I get the following exception:
System.TypeInitializationException: The type initializer for 'Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration' threw an exception. ---> System.MissingMethodException: Method not found: 'Boolean System.Diagnostics.Activity.get_ForceDefaultIdFormat()'.
   at Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.<>c.<.cctor>b__11_0()
   at Microsoft.ApplicationInsights.ActivityExtensions.TryRun(Action action)
   at Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.CreateDefault()
   at Microsoft.Extensions.DependencyInjection.TelemetryConfigurationOptions..ctor(IEnumerable`1 configureOptions)
   at lambda_method(Closure , IResolverContext )
   at DryIoc.Factory.<>c__DisplayClass26_1.<ApplyReuse>b__2() in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6596
   at DryIoc.Scope.TryGetOrAdd(ImMap`1 items, Int32 id, CreateScopedValue createValue, Int32 disposalOrder) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7840
   at DryIoc.Scope.GetOrAdd(Int32 id, CreateScopedValue createValue, Int32 disposalOrder) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7825
   at DryIoc.Factory.ApplyReuse(Expression serviceExpr, Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6595
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6555
   at DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7074
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.WrappersSupport.GetArrayExpression(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 2894
   at DryIoc.ExpressionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7690
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7074
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7074
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7074
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 7074
   at DryIoc.Factory.GetExpressionOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6545
   at DryIoc.Factory.GetDelegateOrDefault(Request request) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 6625
   at DryIoc.Container.ResolveAndCacheDefaultFactoryDelegate(Type serviceType, IfUnresolved ifUnresolved) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 210
   at DryIoc.Container.DryIoc.IResolver.Resolve(Type serviceType, IfUnresolved ifUnresolved) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\DryIoc\Container.cs:line 195
   at Microsoft.Azure.WebJobs.Script.WebHost.DependencyInjection.JobHostServiceProvider.GetService(Type serviceType, IfUnresolved ifUnresolved) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\JobHostServiceProvider.cs:line 101
   at Microsoft.Azure.WebJobs.Script.WebHost.DependencyInjection.JobHostServiceProvider.GetRequiredService(Type serviceType) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DependencyInjection\JobHostServiceProvider.cs:line 84
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at Microsoft.Azure.WebJobs.Script.WebHost.DefaultScriptHostBuilder.BuildHost(Boolean skipHostStartup, Boolean skipHostConfigurationParsing) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\DefaultScriptHostBuilder.cs:line 59
   at Microsoft.Azure.WebJobs.Script.WebHost.WebJobsScriptHostService.BuildHost(Boolean skipHostStartup, Boolean skipHostJsonConfiguration) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\WebJobsScriptHostService.cs:line 397
   at Microsoft.Azure.WebJobs.Script.WebHost.WebJobsScriptHostService.UnsynchronizedStartHostAsync(CancellationToken cancellationToken, Int32 attemptCount, JobHostStartupMode startupMode) in C:\azure-webjobs-sdk-script\src\WebJobs.Script.WebHost\WebJobsScriptHostService.cs:line 188

Expected Behavior
It should not throw an exception.
Version Info
Microsoft.ApplicationInsights : 2.11.0
Microsoft.ApplicationInsights.AspNetCore : 2.8.0
Microsoft.NET.Sdk.Functions : 1.0.29
SDK Version : .NET Core SDK 3.0.100
.NET Version : .NET Core 2.2
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : Nuget Package
OS : Windows 10
Hosting Info (IIS/Azure WebApps/ etc) : Running locally, from visual studio using F5,

The exception is System.MissingMethodException referring to Activity.ForceDefaultIdFormat.
Here's the constructor referenced in that call stack:
https://github.com/microsoft/ApplicationInsights-dotnet/blob/69639b40a38ca5f7e79639a3da42c30db2291ea6/src/Microsoft.ApplicationInsights/Extensibility/TelemetryConfiguration.cs#L57-L67
Looks like this was added recently: https://github.com/microsoft/ApplicationInsights-dotnet/pull/1201
This compiles, which would suggest that the method does indeed exist.
@lmolkova, could there be a version mismatch with what Functions are using?
https://github.com/microsoft/ApplicationInsights-dotnet/blob/69639b40a38ca5f7e79639a3da42c30db2291ea6/src/Microsoft.ApplicationInsights/Microsoft.ApplicationInsights.csproj#L48

@TimothyMothra I did some more digging. Assembly.Load("System.Diagnostics.DiagnosticSource") gives me 4.0.something (going off memory here, left work a few hours ago). The location was part of the function host though.

@Alxandr  can you check that your binding redirects use latest DiagnosticSource package? 4.0.4.* eems like you use old diagnostic source

Not sure you can do binding redirects on azure functions, as you don't own the host? Nor where you'd find them. The issue is that azure functions bundles their own diagnosticsource, which as far as I know is already loaded by the time it runs any app code (where I call app insights).

yes, azure functions still depend on older diagnosticsource. For now, you cannot update ApplicationInsights in functions, we are working on updating version in Functions to solve this issue.

Do you know which version of appinsights will work in functions?

2.10 should work fine.

Remember DLL hell?  Seems now it's Azure NuGet Version Hell.

I had the same problem with latest Azure Functions runtime v2.0.12742.0 and the latest Microsoft.ApplicationsInsights nuget (v2.11). I downgraded to v2.10 of Microsft.ApplicationInsights package and seems to be working fine.

I have some function apps that I still need to run at version 1 because of .NET framework dependencies. This exception suddenly popped up the other day. Downgrading to v2.10 of Microsoft.ApplicationInsights worked for us.


Question: interest on adding artifacts support to exisiting CI?

Hi,
don't know if requested before by me (bad memory :-)) or others, but can't seem to find a similar open or closed issue so just asking.. MoltenVK supports Travis since a while ago (https://github.com/KhronosGroup/MoltenVK/pull/63) so asking if it's possible for MoltenVK to add artifacts support to Travis CI? don't know much about Travis CI and if it's free to support artifacts for open source projects like these.. or if other CI systems can support this (AppVeyor for ex.)..
for example wanted the artifacts of recent build for quick testing:
https://travis-ci.com/github/KhronosGroup/MoltenVK/builds/194818878
thanks..

wanted the artifacts of recent build for quick testing

What artifacts are you looking for...and why?

Hi,
TLDR: really all I need is libMoltenVK.dylib file...
as this is what Wine MacOS builds with Vulkan support enabled need.. (for example precompiled recent ones are: https://github.com/Gcenx/macOS_Wine_builds )
I believe this builds ship also with libMoltenVK.dylib but removing the included library then you can use updated/desired custom MoltenVK ones putting this file (libMoltenVK.dylib) on /usr/local/lib an they will use it..
then you can do quick testing and track status of MoltenVK on VKD3D and/or DXVK having also prebuilt (crossplatform) d3d12.dll (from VKD3D) and d3d11.dll and others form DXVK..
so what I'm saying is all pieces of the puzzle are already precompiled (really VKD3D-Proton still has no releases but much easier to build as no Xcode required) so no need for Xcode excepting MoltenVK which you have to wait roughly two months between Vulkan SDK releases if lazy to built for yourself..
also I asked a while before but would make me completely happy is if we can add some enviroment variable toggle that controls reporting all currently MoltenVK unsupported Vulkan features required by DXVK like geometry shaders for DXVK to work..
for example setting env. variable MVK_dxvk_hacks=1 could allow running DX11 binaries via DXVK and don't require having to rebuild the library for testing DXVK..
thanks..

a quick update:
*just confirm https://github.com/Gcenx/macOS_Wine_builds include libMoltenVK.dylib for example latest 5.20 in:
Wine Staging.app/Contents/Resources/wine/lib64/libMoltenVK.dylib
so we could test the eventual CI artifact libMoltenVK.dylib by overwriting this file..
*really comparing MoltenVK.dylib shipped by Crossover 20 (which has DXVK support) vs standard shows all needed to fakely expose is:
geometryShader                 = true
shaderCullDistance           = true
as said a custom enviroment variable could do the job of forcely reporting this two caps or not..

Hi,
altough little unrelated, just seen MetalAngle project has done a new release and includes as an artifact a compressed dylib file:
https://github.com/kakashidinho/metalangle/releases/tag/gles3-0.0.3
perhaps also future MoltenVK releases could have similar artifacts in addition to source code only, or download the Vulkan SDK MacOS release.. I think MetalAngle devs see their project more as an end user upgradeable runtime library and as such their releases include a dylib..
just saying.. no pressure to implement any ofmy wishes.. :-)


Are there any plans to add MQTT Protocol?

RT:Are there any plans to add MQTT Protocol?

I have a prototype of it but it's not on the top of the priorities list right now. Are you looking for a service side programming model for MQTT? Are you looking for a way to use Hubs as MQTT? That would help us understand what the intended usage is.

Use in IoT devices, which is the advantage of MQTT

@gujunxiong I get that, I'm asking what exactly you are looking for. What sorta code do you want to write on both the client and the server?

Client：

Communication using the class library of the MQTT standard protocol
Through SIGNALR Client Agent to MQTT server
Server：
Handling the message event, authentication, agent to MQTT server;
is itself a MQTT server

Sorry, my English is very bad.
--from Microsoft translation

RPC over MQTT doesn't seem like a great fit so I'm not sure if it would match SignalR semantics. We could look at what it would take regardless to see if it makes sense.

That will be compatible with mixed protocols. Automatically identify the content of the protocol and handle it accordingly

I'm not sure what you mean. I'm sure it could be done but I don't know if it makes sense. The calling pattern for SignalR Hubs isn't pub/sub though I'm sure it could be made to work.

Using SIGNALR client or MQTT client, send message to SIGNALR server,
If SIGNALR server is not MQTT server, you can let it do proxy services to MQTT server,
So Signalr Clinet and MQTT client can receive messages at the same time.

Supports both IoT and web。

@gujunxiong if you'd like to contribute that would be great. Here's the hub protocol https://github.com/aspnet/SignalR/blob/dev/specs/HubProtocol.md. A good first step would be helping us figure out what it would look like using MQTT. What do each of the frames look like, and how would they be interpreted by the MQTT client and SignalR server.

Some inspiration http://docs.gadgetkeeper.com/display/docs/JSON-RPC+over+MQTT

Mainly according to the protocol header for processing adaptation, through the server middleware to identify the protocol forwarded to the Hub.
Unfortunately, I don't have the ability to do this right now.

No problem. Helping us brainstorm would be good enough. I don't think it needs to be a separate middleware but we'd need to figure out what messages would look like. Maybe it's just PUBLISH both ways with a JSON/Binary payload saying which hub to invoke. SUBSCRIBE doesn't seem to make much sense.

Subscription is still necessary, after all, this is an advantage on the IoT, just request the message on demand.
SIGNALR already supports HTTP, WebSocket, and if it supports MQTT, it's a very powerful service.

look here， Using WebSocket as a network transport
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718127

What would you be subscribing to? Specific client method callbacks? The hub itself?
MQTT and websockets aren't in the same category. Mqtt is framing on top of a steam of bytes. You can do mqtt on top of web sockets so bringing that up kinda confuses the discussion.
So here's a strawman:

mqtt Client subscribes to a specific hub
method invocations are handled by bidirectional  Publish (same for results?)

In fact, we can use the Android message to do a case, based on MQTT implementation or SIGNALR implementation, they ultimately want to get the result is only the content of the message, as well as the specific protocol header. It is not possible to use Google's messaging service in China (China Network firewall GFW), so it is based on pub, or duplex protocol.

At a later time, we should look into writing a sample showing this.

@davidfowl You subscribe to topics (more on this here: http://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices and https://mosquitto.org/man/mqtt-7.html or http://www.ev3dev.org/docs/tutorials/sending-and-receiving-messages-with-mqtt/)
This might be similar to callbacks that are currently in SignalR, but MQTT has ability to subscribe using special characters '#' or '+'.
Ideally using SignalR we could create hubs that would allow us to use MQTT to build IOT solutions.
So for example when we create a hub called GreenhouseHub with method Temperature You could publish to it using greenhouse/temperature and also You could subscribe to that topic using same path.
As @milenstack mentioned this would be nice addition, especially for IOT.

There's no disagreement that "it would be nice", it just needs to be designed.

@davidfowl I've started looking at LoraWan software gateways (see https://github.com/Lora-net/packet_forwarder) I've start a proof of concept .net core LoraWan gateway that will make use of MQTT in hope that signalr would be able to send small messages across LoraWan to IoT devices ;)

[ ] **`[

[[](url)]([url]([url]( @

_`[url]([url]([url]([url]([url]([url]([url](

url

)))))))`_
)))
](url)`**

@davidfowl Iooking as repo I noticed these branches:
https://github.com/aspnet/SignalR/tree/pawelka/mqtt
https://github.com/aspnet/SignalR/tree/davidfowl/mqtt
and also I noticed that https://github.com/aspnet/SignalR/pull/933 is merged. Does it means that MQTT support is coming?

Those are prototypes. At some point in the future.

just to let you know im planning to implement mqtt:

tcp based transport
HubLifetimeManager that maps mqtt topics to groups and handles wildcards @davidfowl it would be nice if this is completely handled by IGroupManager but currently it all seems to be in HubLifetimeManager
some hub dispatching fixups (as mqtt is not aware of hubs).

it will  be a new package on top of signalr and https://github.com/chkr1011/MQTTnet.
I will just wait for the final transport abstraction before i begin work

Is there any mileage in looking at https://github.com/Azure/azure-iot-sdk-csharp/tree/master/device/Microsoft.Azure.Devices.Client/Transport and seeing if the AMQP & MQTT code could be wrapped/adapted for SignalR?

Any leads on this? @muratg . I've been following this conversation for a while.
As someone working with MQTT from a hardware perspective, it'd be definitely be interesting to see SignalR clients being able to ingest data from MQTT sources.

@TheBeachMaster You mean a new sample demonstrating this? It's currently in our backlog with no definite plans/dates.  Shouldn't be too hard to write the sample once we stabilize a little bit more.
cc @anurse

This is unlikely to happen in the first release. We've got a pretty large backlog of worked queued up for the first release. If folks in the community are interested in writing it, we're happy to take a look at provide feedback!

It's okay @muratg  and @anurse  I understand... I've seen work  by @moozzyk  and @davidfowl  on this. I'll try them out and see if I can get something to experiment with. Could be interesting.

I stitched something together at
https://github.com/JanEggers/Playground/tree/SignalR/MQTT
Retain, Qos and unsubscribe is not yet implemented, but basic publish subscribe is working so id like some feedback. Basic design is:

MqttHubConnectionHandler handles the protocol specifics
in the hub you can specify with an attribute which methods should be called.

@JanEggers can you separate your MQTT protocol parser and POCOs into a separate assembly. I think that alone can boostrap tons of efforts. Once we begin to see protocol parsers like that target ReadOnlySequence<byte>, it'll be good for everyone trying to build programming models on top.

Basically this folder https://github.com/JanEggers/Playground/tree/SignalR/MQTT/Playground.core/Mqtt

will do once signalr is 1.0


Add SubjectConfirmationData to response

Firstly, thanks for creating a nice and simple tool for this purpose.
We had been using it to test SAML login via AWS Cognito User Pools, however they have the following requirement -

https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-saml-idp.html
This pull request adds an SubjectConfirmation/SubjectConfirmationData node to the response data that meets their requirements. I've tested the change locally and it is accepted by Cognito.
I am relatively new to the SAML world so am unsure if this would create incompatibilities with other systems, I thought perhaps a checkbox configuration option on the login page would be a good way to make this (along with other features) optional, however I did not implement that.

Thank you 🙌 @rjohnsonbade for the PR. Will take a look soon.

That's great news. We have found an alternative to our immediate testing requirements, however once this is merged we would for sure use this for local development testing again.


Poor quality streams and depth measurement R200/F200 legacy Python UP2

Required Info

Camera Model
R200

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
4.15

Platform
UP2

SDK Version
legacy

Language
python }

Segment
others

Issue Description
Hi guys I am doing a couple of legacy projects to make use of my R200 and F200. The projects do facial recognition and calculate the distance using depth.
On the F200 the RGB streams are not amazing but can detect my face about a meter away, however I cannot get a measurement unless I am about 3-6cms away from the camera. When using in Skype on Windows the RGB stream is a million times better and same with the depth stream,

On the R200, the RGB stream is terrible on Linux, really bitty and it is very hard for it to detect my face, the depth measurements don't work at all when it does recognize my face. On Windows, the IR and depth streams are really bad, but the RGB stream is a lot better.

I am figuring as they work a lot better on Windows, that it must be possible to fine tune them but I have played around with the device options for the cameras and am getting no where. Could you suggest the best settings to get these cameras working at least like they are on Windows, if I can get that quality on the UP2 it will be a lot better.
TIA.

Hi @AdamMiltonBarker  I would not honestly recommend using librealsense1 (Legacy Librealsense) for facial landmark detection as it was not designed to support that feature.  At the time that this SDK was in common use, dedicated facial detection features were provided by Intel's RealSense SDK For Windows, also known as the '2016 SDK'.
For face processing applications for RealSense users who could not use the Windows SDK, use of third-party libraries such as dlib was recommended instead.  So I would recommend exploring whether dlib can provide better results.
https://github.com/IntelRealSense/librealsense/issues/456
Some historical background: around the time of 2016-2017, the Windows SDK was Intel's official closed-source RealSense SDK and the original librealsense was an open-source SDK.  There was also a third Linux-based Intel SDK for the ZR300 stereo camera model called 'RealSense SDK For Linux' that added a range of extra features not available in librealsense1.  When the 400 Series camera generation debuted, librealsense (now known as librealsense2 / RealSense SDK 2.0) became the single official SDK.

Hi mate thanks for the reply. I don't use the librealsense for the actual facial recognition or identification I am using dlib/Facenet and NCS1. The issue I am trying to solve is the very low quality RGB stream and the really bad depth measurement.

I get the sense that the cameras are being treated by dlib as ordinary RGB webcams rather than using RealSense depth functions.  Your mention of the very short range of detection for F200 reminds me of using a crude detection technique in 2015 called blob tracking with the F200.
If the cameras are operating in terms of RGB webcams instead of RealSense cameras, that may provide some insight about why there is a quality difference between Windows and Linux.

Hi mate, Dlib is not used with the depth stream, the raw stream without anything is red as in the photo, on both cameras even before I add the facial rec in (which only uses the RGB stream) they are terrible, you have to be within 3-6 cm on the F200 to get any depth. I took a photo the other day where there was nothing at all but writing the depth frames to screen:

This is also the same if I dont merge the two streams into one image.
I will try break it down in simpler terms mate.
UP2 without additional processing, out of the box grab the frames and display with opencv:

F200 without any additional processing at all, depth stream is bright red (First photo), you have to be within 3-6cms before the sensors pick you up.
F200 without any additional  processing at all, RGB stream is pretty bitty (First photo), not the best quality but a lot better than R200.

R200 without any additional  processing at all, RGB stream is terrible, as in the image above.

UP2 with facial recognition (dlib) and identification (Facenet/NCS1) only on RGB stream, coordinates come from RGB stream and are used to index into the depth camera readings:

F200, depth stream is bright red (First photo), you have to be with 3-6cms before the sensors pick you up.
F200, RGB stream is pretty bitty (First photo), not the best quality but a lot better than R200.
R200 depth stream is bright red with dots everywhere, doesn't pic me up sat in front of it, hand or face has to be very very close, although you will see some shapes on the red screen, cannot get measurements always 0.0.
R200, RGB stream is terrible, as in the image above.

In short I can survive with the F200 I was just looking to improve it as when I plug both cameras into windows and use them in skype they are a million times better. Code for F200  is here: https://github.com/AdamMiltonBarker/TassAI/tree/master/UP2/NCS1/Realsense/F200
R200 is the major problem, for reasons I mentioned above. Hope this helps mate.

I tested the RGB of the R200 and F200 in the Windows Camera app to compare the quality to your own images.  The first image is R200 and the second is F200.  They seem to have about the same quality and are similar to your facial image in the opening comment

The link below demonstrates a typical depth map quality that can be expected from an R200 when used with OpenCV:
https://answers.opencv.org/question/167445/r200-depth-stream-on-opencv/?answer=167458

Something may therefore be incorrect in the code that is being used in your project to capture the depth frame in OpenCV.

Hi thanks, the code form the hand is literally the provided code from the example, there is no difference between the hand example and the version I have integrated the facial recognition and identification in. Also when using in Windows they are pretty much perfect, I will take screen shots now of that. Thanks for the replies will check your links out, but the point I was trying to make was that the issues exist out of the box with both cameras.

So the F200 is undoubtedly a lot better, with both depth and RGB on Windows.

The R200 mostly has not improved on Windows, but the RGB stream is a million times better, again, if I were to use the example code on the UP2 with both cameras I would experience the same issues. Are there any specific options that can be set to improve the issues I am having ?

Just to mention this is the code used in the hand example above: https://pyrealsense.readthedocs.io/en/master/examples.html

I went over your project again carefully but I cannot see much potential for improving the results.  The R200 does have a calibrator app for Windows though (the F200 does not have an equivalent app), so you may be able to achieve some improvement if you use it on your R200.
https://downloadcenter.intel.com/download/24958/Intel-RealSense-Camera-Calibrator-for-Windows-

Hi thanks for the reply. So the bitty images shown in the first post and the requirement to be within 6cms of both cameras to detect depth are expected results ? Doesn't feel right to me especially when the cameras are better in Windows.

The R200 is nearly six years old now so its hardware capabilities and supported resolution modes are very limited.  Having said that, it is certainly capable of better depth images, like the one that I linked to earlier, and it is capable of depth sensing up to 4 meters range (the F200 depth-senses over about 1 meter range).
In Windows there is a Virtual Driver that enables the camera to be accessed by non-RealSense applications, such as Skype.  I am not certain how access is handled on Linux, but I recall it may be based on V4L2 / Video4Linux.  If that is the case, that may account for some of the difference in rendering between Windows and Linux.


how to change border color programmatically ?

Use setBorderColor(@ColorInt int borderColor) on your CircleImageView instance.


Fix past dates not being localized

This partially addresses #43, specifically this part:

My additional observation is that the datetime format is not localized based on UI language setting.

Tested this with every available locale, past video dates are now localized properly.

nice catch, merged


Support bevy_xpbd as a backend

It would be nice to support bevy_xpbd as a backend.

I am currently implementing the xpbd backend and it is working so far (https://github.com/Affinator/bevy_mod_picking/tree/xpbd). But I have one question:
The SpatialQueryFilter of xpbd raycasts does not support predicates like rapier. Therefore it is more expensive to filter the entities regarding having a component like Pickable::IGNORE or a marker component.
Instead of only calculating the closest hit, I would need to get all hits and filter them accordingly to the different conditions.
I assume to be consistent we should take this performance hit until the needed functionality is implemented in xpbd?
What would be the correct approach to be in line with the rest of the crate?

I just send a pull request to bevy_xpbd (https://github.com/Jondolf/bevy_xpbd/pull/297) to implement a ray cast with a predicate, which would close the functionality gap to bevy_rapier. If it is accepted I will update my fork and send a pull request to implement a xpbd backend.


Add UI to Donate Animals page

The UI attracts the user and also leaves an impact on the users.I  don't like websites that are blank or just white.If we add a good ui up to a minimum and related to the theme it would look attractive .
Look this is how it looks earlier.

after adding the feature definitely, the website will look good .
look here are some examples of how adding ui just to the simple white can make the website look beautiful.

assign this to me @akshitagupta15june i will do it better

I want to work on this issue as a contributor.
Pleasure Assign so that I can show my skills under GSSoC'23.


Update TlaType1Gen with monotype-restricted generators

Currently genPrimitive is allowed to construct VarT1(_) types, and all the complex-type (Set, Seq, Fun, etc.) generators recursively have mutual dependencies with genTypeTree, which uses genPrimitive.
We need generators for complex types, which forbid type variables.

What is the motivation for this issue? I don't know into which box it should go :)

After inlining we expect all types to be monotypes. Therefore, if we want to use generators to test components that use the monotype assumption, we need to be able to avoid producing type variables.

IIRC I originally opened this issue because the builder used to do signatures differently, which didn't work for polytypes. We've since changed the way the builder handles signatures, so this issue has changed from "required" to "nice-to-have".
Though TBF, I'd potentially consider it required for future testing.


Animation ideas

have the dials accelerate and decelerate so it feels more natural
dials should spin a little faster
have the dials overshoot and snap back to chosen emoji
some way of drawing attention to the emoji and description while the dial is paused
some animation that indicates that the dial is about to spin again
have a running tally of emoji?

I'm breaking these out into individual issues


Blocking 3 mirror IP addresses

These IP addresses are mirroring a news site as well as Mastadon.

Thanks @Morty-Feldman !


python3Packages.univers: init at 30.7.0

Description of changes
This adds the univers python module as part of the Summer of Nix. Fixes #172454.
@armijnhemel I also added you as a maintainer, since you requested this package to be added to nixpkgs and I don’t know if I will be able to maintain it.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 182562 run on x86_64-linux 1

2 packages built:

python310Packages.univers
python39Packages.univers

Result of nixpkgs-review pr 182562 run on aarch64-darwin 1

2 packages built:

python310Packages.univers
python39Packages.univers

@ofborg build python310Packages.univers


Update API to 2.8.1e (add phone number verification)

Yik Yak pushed a new update today (7/15) that implements new anti-spam features. To push adoption, they're disabling mutable actions (i.e. posting, voting) on 7/19 for all older clients. This includes Yodel, since it mimics the previous version of their Android app.
A new update will be out soon that's compatible with Yik Yak's changes. Hold in there!

R.I.P Anonymity

I know right 😒

It would've been easier for them to implement CAPTCHA instead of phone numbers and affect anonymity.

Strongly agreed. But obviously, calling it "spam protection" was a cover. They realized what they created was more harmful than Reddit, and they wanted users' identities so they could easily report illegal activity and cover their asses legally. Spam & bots can be caught with heuristics and CAPTCHA's, like you said.
Sent from my Windows Phone
-----Original Message-----
From: "Joe"<EMAIL_ADDRESS>Sent: 7/18/2015 3:23 PM
To: "soren121/yodel"<EMAIL_ADDRESS>Cc: "Nicholas Narsing"<EMAIL_ADDRESS>Subject: Re: [yodel] Update API to 2.8.1e (add phone number verification)(#100)
It would've been easier for them to implement CAPTCHA instead of phone numbers and affect anonymity.
—
Reply to this email directly or view it on GitHub.


[Feature] Support Label Assignment Distillation (LAD)

Motivation
Add a new label assignment method LAD into mmdetection.
Modification

LAD detector inherits from KnowledgeDistillationSingleStageDetector.
LAD head inherits from PAAHead.

Checklist

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

Hi alls, I use the code to train two models in the configs/lad/README.md file and can reproduce results in the paper. I would like to share checkpoints and training logs here: https://www.dropbox.com/sh/kdqp1zyt5vtjqzz/AABJ1j_xUd--p_rwzJ3ZZ86ca?dl=0 Thank you!

Thank you for your contribution, we will organize a review immediately.

@thuyngch I think the code quality is very good. You may need to add unit tests and try not to use abbreviations for variable names.

Hi @hhaAndroid and @RangiLyu ,
Thanks for feedbacks from you guys.
I push a commit to avoid abbreviations in variable names.
Now I am writing unit tests.

Hi @hhaAndroid and @RangiLyu ,
I added the unit test for LADHead.
Is it enough or needed to add more?

Hi, we have fixed the compatibility with MMCV in v2.18.1. Now the CI can work normally. Please pull the latest master and re-run the unit tests.

@thuyngch I ran configs/lad/lad_r50_paa_r101_fpn_coco_1x.py, and found that the performance is 38.4, there should be problems with the code, can you check it?

I will check it soon.

Hi alls,
I use the code to train two models in the configs/lad/README.md file and can reproduce results in the paper.
I would like to share checkpoints and training logs here: https://www.dropbox.com/sh/kdqp1zyt5vtjqzz/AABJ1j_xUd--p_rwzJ3ZZ86ca?dl=0
Thank you!

I downloaded checkpoint from this site, then run the evaluation with the following command, and I can reproduce the result:
#!/usr/bin/env bash
set -e
export GPUS=2
export CUDA_VISIBLE_DEVICES=0,1

CFG="configs/lad/lad_r50_paa_r101_fpn_coco_1x.py"
CKPT="work_dirs/epoch_12-c2880474.pth"
tools/dist_test.sh $CFG $CKPT $GPUS --fuse-conv-bn --eval bbox

CFG="configs/lad/lad_r101_paa_r50_fpn_coco_1x.py"
CKPT="work_dirs/epoch_12-1d8d48d4.pth"
tools/dist_test.sh $CFG $CKPT $GPUS --fuse-conv-bn --eval bbox

The evaluation output for configs/lad/lad_r50_paa_r101_fpn_coco_1x.py:
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.416
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=1000 ] = 0.598
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=1000 ] = 0.456
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.239
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.455
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.550
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.597
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=300 ] = 0.597
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=1000 ] = 0.597
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.398
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.647
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.760

The evaluation output for configs/lad/lad_r101_paa_r50_fpn_coco_1x.py:
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.432
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=1000 ] = 0.615
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=1000 ] = 0.472
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.254
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.477
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.568
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.610
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=300 ] = 0.610
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=1000 ] = 0.610
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.406
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.662
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.772

Ah I just found that in my config file, I use 8 imgs/gpu and I train the model with 2 GPUs.
https://github.com/open-mmlab/mmdetection/blob/dev-v2.19.0/configs/lad/lad_r50_paa_r101_fpn_coco_1x.py#L118
I guest that you use 8 GPUs to train the model, is it right?

Ah I just found that in my config file, I use 8 imgs/gpu and I train the model with 2 GPUs. https://github.com/open-mmlab/mmdetection/blob/dev-v2.19.0/configs/lad/lad_r50_paa_r101_fpn_coco_1x.py#L118
I guess that you use 8 GPUs to train the model, is it right?

oK


Need table with stemming

Add code to create a new dictionary that stems all of the words and tokenizes all the words.

Table is implemented with stemming.


Network protocol error

Modloader
Fabric
Minecraft Version
1.21.1
Modloader Version
Fabric: Loader 0.16.7 + API 0.107.0
No Chat Reports Version
1.21.1-v2.9.0
Modpack Info
Additive 1.31.0+1.21.1 Fabric
The latest.log File
https://mclo.gs/LbKoAGO
Bug Description
Joining summitofficial.minecraft.best gets me a network protocal issue
Steps to Reproduce
Join
see issue
Other Information
I know others had made an issue like this, but in case my issue is somehow different or unique I posted it
I also used the following mods on their latest version:
Chat Heads
MacOS Input Fixes
WaveyCapes
Better Add Server
Footprint Particle
CraftPresence
Architectury
Bobby
AppleSkin
Chat Patches
Controlling
CustomHud
No Chat Reports
Searchables
Keybind Fix
Presence Footsteps
UniLib
Placeholder API
ChatNotify
Xaero's Minimap
Xaero's World Map

Can confirm, even with the NCR "enable mod" option set to OFF. However, the stack trace is identical to #492, so closing as duplicate.


Add tool to generate HTML page with overview on failed tests

Add tool to generate HTML page with overview on failed tests
This webpage will be published in Gitlab Page

The all subcommand was added to generate a JSON to be used in Gitlab Pages.


replaced AlertDialog without AppCompatAlertDialog

See https://github.com/pockethub/PocketHub/issues/818 too

https://github.com/pockethub/PocketHub/pull/896 well :( Should not be merged right?

@StefMa I'd like to use appcompats AlertDialogs, but @hzsweers and @Meisolsson don't

Ok, let us discuss :+1:
@Meisolsson want to stay on the MaterialDialogLib without a reason.
@hzsweers want to stay on this lib because of:

We should be moving all the dialogs to material dialogs then. There are
features of it that don't exist in the appcompat's dialogs as well, such as
sensible widths on tablets and more customizability. I don't know who did
the original addition of it here, but I very much prefer them to
appcompat's.

So currently we don't need the "more features" which the MaterialDialog-Lib brings on. So, actually it is only overhead on source code.
Also, but this is my opinion, we don't need "more features" on dialogs. Dialogs are only "simple" information "things".
According to Design Guid Dialogs are:

Dialogs inform users about critical information, require users to make decisions, or encapsulate multiple tasks within a discrete process. Use dialogs sparingly because they are interruptive in nature. Their sudden appearance forces users to stop their current task and refocus on the dialog content. Not every choice, setting, or detail warrants interruption and prominence.

Alternatives to dialogs include menus or inline expansion within the current content area. Both approaches present non-interruptive options while maintaining the current context.

Expect of "dialogs include menus" all features will be supported from the AppCompatDialog.
So. In my opinion we could stay on AppCompatsDialog and drop MaterialDialogLib...

So currently we don't need the "more features" which the MaterialDialog-Lib brings on. So, actually it is only overhead on source code.

Run the app on a tablet and suddenly we do.
This is not a discussion, we're not going to switch to it. In the future, please abide by the rules we've laid out in our CONTRIBUTING.md about infrastructure changes like this and discuss with us first before assuming anything. Especially considering this was already discussed and decided before.


Feature: Website content on starting page

For web searching and for general help there should be some traditional website content for people to read.
https://jackbox.tv/#/
doesn't need content on its login page, but that game doesn't rely on search engines for traffic

Closing in favor of both an instruction page and metadata in the html for search engines.


Made get_gacha_types use an authkey.

If an authkey wasn't set it would always try to search the logfile, which caused problems.

looks good, thanks for the help


DebugVertex: fix ShaderObject debugging

m_SPIRV was empty because of wrong ShaderModule

I think the same fix needs to be applied to the other debug functions.

If I will need to use other shader debug functions and I will have fix for them, I will make PR for sure

That's fine if you don't want to iterate on this PR, but in that case can you please close this and file an issue so it can be tracked for a full fix? As a reproducible test case it sounds like you could provide any shader object demo such as Sascha Willems' rather than yours specifically.

What do you mean with don't want to iterate on this PR? Scope of this PR is fix debugging of vertex shader objects, not all shaders, not all issues in this repository. If it is not enough, sure I can close this PR or you can close it for me please.
Segfault can be reproduced by starting debugging of any vertex shader object which produces vertices, just click on any vertex in Mesh View and select Debug Vertex. You do not need to have special code, any example with shader objects should be enough.

OK then, that's fine. I would appreciate if you could open an issue for this bug so that it can be properly tracked and a full fix made.


implement testing from command line

I wanted to be able to test new plugins while my slackbot is deployed. I couldn't quite see how to do that without creating a new bot, but this code allows testing from the command line.
Usage:
python slask.py -t \!help
will output the !help command (backslash to escape ! and $ from the shell)

Nice! Hope to be able to review tonight.
This used to be easier when slask was a flask program, now you're right that it's harder since it's using the websocket API. I keep a personal slack instance, and test by connecting to that, but this could shorten the dev cycle.

I made some changes and committed this in 0abf1d4 . Thank you so much!
I added the ability to enter a slask repl with slask -t, and moved the ability to run a command to slask -c '<your command here>'. Hope that's OK with you!


Sync option to mirror source -> target

Which version of the AzCopy was used?
10.7.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
azcopy sync [https://blob URL] [C:\LocalPath] --delete-destination
What problem was encountered?
Unable to truly sync a source -> target.
Files modified in the destination are ignored without any notification. They are not overwritten, copied, updated or logged as being different.
Business impact being that we cannot ensure the source matches the target, nor can we provide a list of files that are different.
How can we reproduce the problem in the simplest way?

Upload any number/type of files to an empty Blob container.
Create a empty target folder on a local file system.
azcopy sync the blob to the local folder.
Confirm that all blob files have been copied to the local folder.
Modify a local file in any way. e.g. add a new line to a TXT file.
Re-run the same azcopy sync command.
Observe that no new/updated files have been copied.
Observe that the modified TXT file has NOT been over-written.
Observe that Open the azcopy log file does not show any skipped/ignored files.

Have you found a mitigation/solution?
Only semi-viable work-around is to run an azcopy copy [source] [destination] --overwrite:true command to re-copy the entire source directory to the target, however this overwrites all files, not just differences, causing issues with very large file sets.
The azcopy copy [source] [destination] --overwrite=ifSourceNewer switch is not viable because the Destination is newer than the Source.
Other potential work-around is to azcopy sync to a safe staging location, then use robocopy to truly mirror the staging Source -> final Destination.
The AZCopy Sync Wiki Page describes this behaviour as being by design - Unfortunately this leaves us with very few options to properly sync a folder pair.

Thanks @phrak for reaching out! We are aware of this scenario and it is being tracked here. It does sound like a valid scenario and we hope to support it soon.

To clarify, the blob service does not support storing an exact lmt; the time when the blob is created/modified is automatically the lmt. To avoid re-transferring the same files in a download situation, we can first preserve the source lmt locally (which needs to be added) in previous run, and then compare the lmts during sync and transfer the source files if the corresponding local lmt is different. However, in a copy situation (blob -> blob), this does not work since we cannot preserve the lmts of blobs and rely on it as an accurate indicator of the file's "version".
Thus, the best approach (that we can think of right now) for the mirroring scenario is to simply copy over all the source files, and delete all extra files at the destination.
Please let us know if you have any other thoughts about this.

Hi @zezha-msft , thanks for replying. I hope a solution can be found soon too.
An option to force-overwrite the destination only if it's different from the source would be very useful to avoid re-copying identical files again.
Another thought - Would it be possible to use the MD5 hash property to compare the objects and overwrite if different?
In the mean-time, it sounds like the best work-around is to use azcopy sync to sync the blob to a safe, dedicated staging location, then use robocopy to properly mirror the staging directory Source -> final Destination.

Hi @zezha-msft , thanks for replying. I hope a solution can be found soon too.
An option to force-overwrite the destination only if it's different from the source would be very useful to avoid re-copying identical files again.
Another thought - Would it be possible to use the MD5 hash property to compare the objects and overwrite if different?
In the mean-time, it sounds like the best work-around is to use azcopy sync to sync the blob to a safe, dedicated staging location, then use robocopy to properly mirror the staging directory Source -> final Destination.

Hi @phrak, the MD5 value can be stored on the service side, but it is not validated against the data, so it'd be hard to use MD5 values as an indication of file content, since they could easily become out of date if the user changed the content but didn't update the MD5 value. More often, there could be files that got uploaded without a stored MD5.
Sorry for the inconvenience. We are aware of this problem, and will look into solving it with a good UX.

Hi @phrak, the MD5 value can be stored on the service side, but it is not validated against the data, so it'd be hard to use MD5 values as an indication of file content, since they could easily become out of date if the user changed the content but didn't update the MD5 value. More often, there could be files that got uploaded without a stored MD5.
Sorry for the inconvenience. We are aware of this problem, and will look into solving it with a good UX.


Compile UE 4.26

Great plugin! As the compile process from 4.26 it wont let me compile without any "Category" tag given. I fixed that easily:
UPROPERTY(Category=General, Config, EditAnywhere, BlueprintReadWrite, meta=(ConfigRestartRequired = 1.0f, UIMin=0.5f, UIMax=3.0f))
float UIScale;

@ixsolve
Thanks for the issue, I was using 5.x and forgot about that problem. Please wait a bit while we address it.

@ixsolve
Hi, I have addressed this issue. I hope you can take a look at it when you have time.
Thanks.

Great! Thank you, now it can easily compile with 4.26 for everyone that is using it for that version.