[BUG]: Block not treated as Ground

Which Mod?
Utility Glass
Description of the bug/crash
It's not a crash, but when you try to use this glass as a floor objects built on top of it don't recognize it as a valid location/tile.
Steps To Reproduce
lay down some of these tiles and try to build structures on top, they show as invalid locations, although dupes WILL build them. they are not usable while on top of these tiles.
Player.log
NA-Not a crash issue.

liquid pumps do not require floor, your issue is somewhere else.
also not reproducable

Not the pump it was the water drop off, not sure why it's giving me an issue since I see it's visually fine for you.


Style players in scorecard.

Highlight current player, and show eliminated players. Added an empty style if we want to style players any further.

fixed


How to upload image

I created my server and I have a request for uploading images, but I can’t send a request using this library. I'll post screenshots with Postman, please tell me how to solve this problem.

Whatever I do, I always get an error -

Current request is not a multipart request","path":"/gallery/.

Please can someone write an example of how to create such a query using Dio

https://github.com/flutterchina/dio/blob/master/example/formdata.dart

`    Dio dio = Dio();
FormData formData = FormData.from({
"file":UploadFileInfo.fromBytes(utf8.encode("hello world"), "word.txt")
});
dio.post(APIClient().galleryUrl+path(APICatalogPaths.upload), data: formData, options: Options(
  method: "POST",
  responseType: ResponseType.JSON,
)).then((response){

  print(response.data.toString());

}).catchError((err){
  print((err as DioError).response.toString());
})`

"timestamp":"2019-02-15T16:22:36.344+0000","status":500,"error":"Internal Server Error","message":"Current request is not a multipart request"

I think the library incorrectly builds the request, because through the postman everything works, please tell me what the problem is, I specifically put the data from the example, my server would have given another error if there were not valid data.

Is the problem solved?
:octocat: From gitme Android


RJSF Styling changes for Meshery extenstions

Description
This pr introduces some styling changes to the rjsf form rendered for Meshmap extension
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3879 (3b1d620) into master (c8dd33a) will decrease coverage by 7.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3879      +/-   ##
==========================================
- Coverage   25.17%   18.15%   -7.02%
==========================================
  Files          63       63
  Lines        4787     4787
==========================================
- Hits         1205      869     -336
- Misses       3221     3661     +440
+ Partials      361      257     -104

Flag
Coverage Δ

gointegrationtests
?

integrationtests
∅ <ø> (?)

unittests
18.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-62.83%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.15% <0.00%> (-55.00%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.90% <0.00%> (-39.10%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
1.78% <0.00%> (-32.15%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
0.00% <0.00%> (-21.60%)
:arrow_down:

Continue to review full report at Codecov.

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


Mechanism for adding/removing "tags" to/from tensor names, after changes to the tensor

Fixes #454

@ritzvik @shreyasbapat Sorry for the other PR. I could not rebase properly. Please review this PR.

Hello @JeS24! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/einsteinpy/symbolic/helpers.py:

Line 201:1: W293 blank line contains whitespace
Line 205:1: W293 blank line contains whitespace

If possible add a test for _change_name here
https://github.com/einsteinpy/einsteinpy/blob/master/src/einsteinpy/tests/test_symbolic/test_helpers.py

If possible add a test for _change_name here
https://github.com/einsteinpy/einsteinpy/blob/master/src/einsteinpy/tests/test_symbolic/test_helpers.py

test for both string parameter and Nonetype

@ritzvik Done.

For quality checks
https://docs.einsteinpy.org/en/latest/dev_guide.html#code-linting

For quality checks
https://docs.einsteinpy.org/en/latest/dev_guide.html#code-linting

I keep forgetting to run tox before committing. 😞


[performance] Improve the performance of FastCounter

⚠ This PR relies on Keyword.replace!/3 which was added in Elixir 1.5.0, the mix.exs has been updated to indicate this but this would effectively be a major version breaking change since the current library supports down to Elixir 1.3 ⚠
FastCounter, as the name implies, provides a fast counter.  Since the FastCounter is used in very hot paths, optimizing its performance can yield system wide improvements for any systems using Instruments.
This PR is mostly supporting data and analysis of the best strategy for Instruments.FastCounter.increment/3
The previous strategy attempts to generate stable ETS keys by normalizing the incoming options, in practice the use of Keyword.merge/2 means that the keys end up semi-stable since the documentation provide the following caveat:

There are no guarantees about the order of keys in the returned keyword.

So while the previous strategy would ensure the order of the :tags key, it does not guarantee the order of the options after the merge and therefore does not guarantee the stability of the key.
This actually doesn't really seem to matter because the duplicate keys are all processed and the stats will be aggregated by the metrics processor.
I'm inclined to actually just remove the sorting of the tags altogether, but this is a slightly less drastic change that continues the current strategy but adds a few special cases to improve performance.

A special increment/3 arm was added for when no options are passed.  This arm can skip all table_key calculation for the common case of simple non-tagged metric increments.
Two special cases were added to the case statement for when options are present, one for when tags is an empty list, and one for when tags is a list of exactly 1 element.  In both cases the sorted version of these tags values is identical to the provided value so the Enum.sort/1 and Keyword.replace!/3 calls can be completely obviated.
Finally Keyword.merge/2 was replaced with Keyword.replace!/3 which proved to have better performance characteristics under benchmarking.  Merge is not really necessary here as only a single key in the Keyword needs to be updated and that key is known and known to exist at the point where the write is executed.

@mezz I probably should have pointed out in the PR body that tag_handling/analysis.txt and fast_increments/version-2.txt were the condensed benchmarking results to look at.

@mezz I extracted the table_key calculation out into a private function and inlined it back in.  Performance results are even better somehow https://github.com/discord/instruments/pull/15/files#diff-9c54a5f146104f4018bcc45c11179bb0

Magic!

@ihumanable is this good to merge now?
I'd like to have it in any push deploys I do in the future, they have a lot of increments.


fix: move update package to internal packages

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (38eb6e0) to head (33d7c29).

Files
Patch %
Lines

internal/update/getting.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #24   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          5       5
  Lines        212     213    +1
=====================================
- Misses       212     213    +1

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


[Enhancement][opensearch/opensearch-dashboard] switch from image/imageTag to a different (helm default) formatting of YAML keys/values

Is your feature request related to a problem? Please describe.
I would like that both helm charts, for opensearch and opensearch-dashboard, changed how they work with image and imageTag keys.
So instead of current way of:
image: "opensearchproject/opensearch"
imageTag: "1.11.0"

I would like this to become, more helm-native, to:
image:
  repository: "opensearchproject/opensearch"
  tag: "1.12.0"
  pullPolicy: "IfNotPresent"

I am fully aware that there are helm charts which vary in how they approach things, however, I working with many charts (vast majority) which have the suggested format of YAML, instead of image+imageTag.
The larger reason is our use of renovate project which does dependency updates (of docker images) and current YAML format causes us to create and maintain hard to navigate regexes.
I could provide you a PR, if the project would be willing to consider it, i.e. accept a breaking change.
What do you think?

I am not afraid of breaking changes, as long as it is in good faith.
My concern is how urgent or needed is this change?
I would get more opinions on community members on this.
@smlx @mprimeaux @DandyDeveloper that are your thoughts on this?
Thanks.

@peterzhuamazon I'm all for it but it is a frustrating breaking change.
I'm not sure why we didn't use the standard convention in the first place.

 It is breaking in the sense that people have to restructure their values files but not in the sense that it will make it impossible to upgrade an existing installation.

I'm not sure why we didn't use the standard convention in the first place.

I'm guessing helm chart create wasn't used.

Thanks everyone for quick responses.

urgend/needed

Not urgend, but the change would be very welcome. The opendistro helm chart had also the same structure, and with the switch to opensearch project, this is the time (being still quite young) that we could make a good and reasonble (breaking) change as well.

Likewise, I am in favor of the change to align with the standard Helm way of structuring that specific stanza.  Granted, we could make the change in a backward-compatible manner in the spirit of a deprecation policy.
Regardless, I don't perceive this breaking change as requiring a material effort for consumers.

I have created a PR for my proposed changes - see #184


Fix demo.py bug of arg --save_result

For demo.py, if arg --save_result didn't be added, the program will report an error:
Traceback (most recent call last):
  File "demo.py", line 296, in <module>
    main(exp, args)
  File "demo.py", line 289, in main
    imageflow_demo(predictor, vis_folder, current_time, args)
UnboundLocalError: local variable 'vis_folder' referenced before assignment

After the bug fixed, there is another problem #379

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


Update monitor ctx variables doc

Issue opensearch-project/alerting#200
Make documentation consistent with code

Signed-off-by: Petar Partlov<EMAIL_ADDRESS>Description
Update documentation of ctx variables to be consistent with code.
This PR must be merged after opensearch-project/common-utilsGH-318
Issues Resolved

opensearch-project/alerting#200

Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@partlov: Which version of OpenSearch do these changes apply to?

@partlov: Which version of OpenSearch do these changes apply to?

As mentioned in description this will go with PR opensearch-project/common-utilsGH-318. I'm not aware in what version this will go, probably responsible person for merging this PR will have more info.

@Naarcha-AWS can you review this?

I'm going to go ahead and take over this PR to make sure it gets merged in.

This is blocked until https://github.com/opensearch-project/common-utils/pull/318 is merged in. With that in mind, I'm going to close this for now. We can reopen if the PR in common-utils is merged.


Support for Android Gradle Plugin Version 3.0.0

The plugin is not compatible with the last Android Gradle Plugin Version (3.0.0-rc1)
Seems that on that version they remove some method and the plugin fails when trying to access to the Kotlin output directory.
I have added more tests that reproduce the error, but I don't know how to fix it maybe with some help ;)
You can see the branch that I have created with that tests: https://github.com/JcMinarro/groovy-android-gradle-plugin/tree/tests-that-fail-with-android-plugin-version-3.0.0-rc1
And here is the failure log:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':myosn:compileExternalTestingDebugUnitTestGroovyWithGroovyc'.
> Cannot get property 'kotlinOutputDir' on null object

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':myosn:compileExternalTestingDebugUnitTestGroovyWithGroovyc'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
        at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:59)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:128)
        at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
        at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)
        at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)
        at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:46)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)
        at org.gradle.initialization.DefaultGradleLauncher$ExecuteTasks.run(DefaultGradleLauncher.java:314)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.initialization.DefaultGradleLauncher.runTasks(DefaultGradleLauncher.java:204)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:134)
        at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:109)
        at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:78)
        at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:75)
        at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:152)
        at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:100)
        at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:75)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
        at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$1.run(RunAsBuildOperationBuildActionRunner.java:43)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:40)
        at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:47)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
        at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39)
        at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25)
        at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80)
        at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53)
        at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:57)
        at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:32)
        at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
        at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
        at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
        at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
        at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:64)
        at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:29)
        at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59)
        at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44)
        at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:45)
        at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30)
        at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
        at org.gradle.util.Swapper.swap(Swapper.java:38)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:82)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
        at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: java.lang.NullPointerException: Cannot get property 'kotlinOutputDir' on null object
        at groovyx.GroovyAndroidPlugin.getKotlinClassFiles(GroovyAndroidPlugin.groovy:282)
        at groovyx.GroovyAndroidPlugin$_processVariantData_closure3$_closure8.doCall(GroovyAndroidPlugin.groovy:164)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:700)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:673)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:121)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:110)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)
        ... 102 more

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

I was able to use the plugin with beta6. I'll look into it but sounds like RC2 is going to hit sometime next week so not going to spend a lot of time on it.

Ok, we can update the test cases when RC2 and Final version where published, then try to sopport them

So this issues is specifically with kotlin correct?
I just tested on my project (java only) and it's working fine.

Yes, it is when you have kotlin source on your code, but with the new version of the Android Build Plugin

I have been reading the Android Build Plugin migration guide and they have removed certain functionalities to obtain the output directories, and I think that it could be de problem.
https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html#variant_api

Looking into this along with #155 . I have a project that's using both Kotlin and Groovy so I should be able to upgrade using that to look at what's going on.

This issue still exists with Android Studio 3.0. The specific line of code is here:
def kotlinCopyTask = project.tasks.findByName("copy${variantName.capitalize()}KotlinClasses")
return kotlinCopyTask.kotlinOutputDir

kotlinCopyTask is null.
When I look for tasks, these are the only ones with "[Kk]otlin" in the name
Finding Kotlin-related tasks
task ':app:compileRegularDebugAndroidTestKotlin'
task ':app:compileRegularDebugKotlin'
task ':app:compileRegularDebugUnitTestKotlin'
task ':app:compileRegularLccOldDebugAndroidTestKotlin'
task ':app:compileRegularLccOldDebugKotlin'
task ':app:compileRegularLccOldDebugUnitTestKotlin'
task ':app:compileRegularLccOldReleaseKotlin'
task ':app:compileRegularLccOldReleaseUnitTestKotlin'
task ':app:compileRegularReleaseKotlin'
task ':app:compileRegularReleaseUnitTestKotlin'

An ugly workaround for this, until the new version is released:
// Ugly workaround for incompatibility between Groovy Android Gradle Plugin 1.2.0 and Android Gradle Plugin 3.0.0
// Should be fixed with Groovy Android Gradle Plugin 1.3.0. https://github.com/groovy/groovy-android-gradle-plugin/pull/155
task copy[<Flavor>]DebugUnitTestKotlinClasses(type: CopyKotlinClasses)
class CopyKotlinClasses extends DefaultTask {

    def kotlinOutputDir = ["$project.rootDir/app/build/tmp/kotlin-classes/regularDebugUnitTest"]

    @TaskAction
    def doNothing() {
    }
}

This provides the "missing" task the Groovy plugin is looking for, with a non-null kotlinOutputDir pointing at the correct output path (for my project, at least).

When do you plan to release 1.3.0?

@autonomousapps When it's complete 😀.
Here's an update of what's going on.
3.0.0 source code didn't get released until over the weekend, and due to some changes the unit tests seem to have problems running all at once (they are fine run individually) due to an issue with com.android.build.gradle.internal.BuildSessionImpl, annotation processor implementations seem to have changed, and kotlin doesn't work with api level of 26+. Also some issues with invokedynamic, which can easily be solved for applications using proguard, but pose a larger problem with library projects.
I will push my progress today to 1.3.0 branch if anyone wants to take a look.

I see! I'm so very glad Google declared AGP 3.0.0 stable!

Snapshot released (2.0.0). Please report any issues you have. The plan is to release it after I update some tests so they are more robust and easier to maintain, as well as figure out a solution to a better solution than progaurd for #145, and of course updating the docs.

Hi @AndrewReitz I couldn't find the version 2.0.0-SNAPSHOT, The last one that I found was 1.3.0-SNAPSHOT, but it seems to be old because I get the same error "Cannot get property 'kotlinOutputDir' on null object" and I can see that you have removed that code on #158
Did you push the proper version?
I am using the following repository, Should I use another one?
http://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/groovy-android-gradle-plugin/

@JcMinarro There's an issue with gradle 4.3 and the maven-plublish plugin. I'm trying to upload one manually now.

I have tried with the new build that you have pushed and It works like a Charm ;)
Good Job

Glad to help. Few more things I want to update and then I'll get 2.0.0 out!

@AndrewReitz any update on this? When can we expect 2.0.0 to be published? :)


Umbrel Home: Keine Verbindung zum Backend: The server reported a problem: 502 Bad Gateway.

Expected behavior
JAM up and running
Actual behavior
After installing the JAM App on a brand new umbrel home server, I am getting the message:
No Connection
Keine Verbindung zum Backend: The server reported a problem: 502 Bad Gateway.
Steps to reproduce the problem

Tried reinstalling JAM
Tried installing Electrs before installing JAM
Only apps running on my Umbrel Home right now are Bitcoin Node (finished syncing), Electrs and Jam.

Specifications

Version: Jam v0.2.0
Platform: Umbrel Home
Browser: Google Chrome Version 123.0.6312.86

Additional context
Pretty self explanatory error message.
Any ideas how to fix this? The Umbrel Home server is brand new and was just set up yesterday.

hi @fsm247
is it your first time trying Jam?
Did you try adding deprecatedrpc=create_bdb to your bitcoin.conf file?
see https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260
FYI, someone on telegram had the same problem with the new Umbrel 1.0, adding it to the config didn't work AFAIK. then I'm not sure how to fix it sorry

Link to issue on the umbrel repo: https://github.com/getumbrel/umbrel/issues/1736
Let's hope this will be resolved soon.

hi @fsm247
is it your first time trying Jam?
Did you try adding deprecatedrpc=create_bdb to your bitcoin.conf file? see https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260
FYI, someone on telegram had the same problem with the new Umbrel 1.0, adding it to the config didn't work AFAIK. then I'm not sure how to fix it sorry

Unfortunately this hasn't fixed my problem.
Hopefully there will be a fix soon.
Jam was one of the main reasons why I got the Umbrel Home in the first place.

hi @fsm247
is it your first time trying Jam?
Did you try adding deprecatedrpc=create_bdb to your bitcoin.conf file? see https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260
FYI, someone on telegram had the same problem with the new Umbrel 1.0, adding it to the config didn't work AFAIK. then I'm not sure how to fix it sorry

Unfortunately this hasn't fixed my problem. Hopefully there will be a fix soon. Jam was one of the main reasons why I got the Umbrel Home in the first place.

Just to be sure.. did you restart your node after the config change?

hi @fsm247
is it your first time trying Jam?
Did you try adding deprecatedrpc=create_bdb to your bitcoin.conf file? see https://jamdocs.org/FAQ/#jam-doesnt-work-anymore-after-updating-bitcoin-core-to-v260
FYI, someone on telegram had the same problem with the new Umbrel 1.0, adding it to the config didn't work AFAIK. then I'm not sure how to fix it sorry

Unfortunately this hasn't fixed my problem. Hopefully there will be a fix soon. Jam was one of the main reasons why I got the Umbrel Home in the first place.

Just to be sure.. did you restart your node after the config change?

Yes I did.

Just to be sure.. did you restart your node after the config change?

Yes I did.

Can you double-check that the config changes are still present? Node is synced? Please forgive the annoying follow-up questions..

Just to be sure.. did you restart your node after the config change?

Yes I did.

Can you double-check that the config changes are still present? Node is synced? Please forgive the annoying follow-up questions..

Will do after dinner. Give me a few hours.
I appreciate the follow-up.

Just to be sure.. did you restart your node after the config change?

Yes I did.

Can you double-check that the config changes are still present? Node is synced? Please forgive the annoying follow-up questions..

Ok I removed the deprecatedrpc=create_bdb line from bitcoin.conf
Restarted.
Added the line back in. Saved. Restarted.
Now Jam seems to be working.
No idea what I did wrong in the first attempt.
Thanks anyway :-)

Now Jam seems to be working.

Nice! That's great :pray:


env level configuration support

This change adds Linux environment variables as an additional level of configuration between cmdline (deprecated from now on) and trail config. It also adds a fully new set of config key to make its syntax compatible with env, while keeping backwards compatibility of the old config keys.
These are the main points of action:

New env friendly config key format, making it case insensitive and eliminating "." characters. For example, "debug.ssh" would be now "debug_ssh" or "DEBUG_SSH".
Add new aliases to keep backwards compatibility. For example, "debug.ssh" would be still supported but deprecated.
Keep the old format for pvcontrol config ls. A new command will be issued in the future with the new one while keeping support for the old one.
Change all index names to be equivalent to the upper case version of the new keys.

TODO:

Set configuration from Linux environment variables, following the new key syntax format.
What to do about sysctl config keys? We cannot switch "_" with "/" in this case.
Test and debug.
Documentation.

Looks promising.

For sysctl we might need to stick to old way for now. And later introduce a sysctl.XXXX.XXXX.XXX parsing option (without pv_ prefix) which we would offer for kernels < 5.8 (since 5.8 kernel will parse such cmdline options directly). We wont need them in envs then anymore. By offering sysctl... option will help folks transition to the pure kernel approach without pantavisor ....


EvalBoolean returns true on NaN-compare

Steps to reproduce

Create following expression: "1 / 0 > 2"
Evaluate boolean (expr.EvalBoolean())

Result
This returns true
Expected Result
NaN or an Exception should be returned

The reason it happens is this line:
(Real reLeft, Real reRight) => reLeft > reRight,

there should be checks on NaN
Thanks for the report, I'll soon it fix

Fixed, thanks for reporting! The fix will be available since 1.4.0-preview.2


Adding Metaplex Core support

Thanks for all the hardwork here Keith! Can you provide some sample accounts & screenshots for me to validate?
There's some stuff to nit over, but want to get the big stuff done first.


mp4upload final url uses www4. but some embed sourfe requires www14

https://www14.mp4upload.com:282/d/qwx2hqpdz3b4quuor6qaqoqxcmpxvjg24jimyi3bvte25akjslogcthk/video.mp4
this is url i got latest
but still it isnt streaming tried on vlc or mpv but unable to stream also tried in browser but failed

The web page at https://www14.mp4upload.com:282/d/qwx2hqpdz3b4quuor6qaqoqxcmpxvjg24jimyi3bvte25akjsjyqogxs/video.mp4' might be temporarily down or it may have moved permanently to a new web address.
obtained using devtools

Probably fixed in #12.


Not sure how to use field with type "bytes"

I am sending requests using a protobuf message which has a field with type bytes - specifically image bytes. I convert the image to bytes using a Python script and get the following output:
\xff\xd8\xff\xe0\x00\x10JFIF[...]
This, I then input to the bytes field in Protoman:

I would expect that exactly the same \xff\xd8\xff\xe0\x00\x10JFIF is transferred to the server, but what I get at the server side is:
\xc5\xf7\xf1w\xcc_\x7f\x17\xb4\xc7M1\xd7BE
I assume this has to do with the representation the data is in, I am inputting a byte string. What does the byte type actually expect?

I encountered a similar issue when sending image bytes using protobuf. I resolved it by converting the image into a base64 string before sending it. This approach worked for me, and it might solve your problem as well.


Cannot Select Python Interpreter

** I tried to search for an existing issue and failed to find one. Apologies if you are tracking this elsewhere**
Environment data

VS Code version: 1.56.2
Extension version (available under the Extensions sidebar): v2021.5.842923320
OS and version: Windows 10 Enterprise (21H1)
Python version (& distribution if applicable, e.g. Anaconda): 3.7.8
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: N/A
Relevant/affected Python-related VS Code extensions and their versions: N/A
Value of the python.languageServer setting:  Pylance (obvs 🙂 )

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
When I select my interpreter, it applies to my workspace.
Actual behaviour
When I select my interpreter, it applies to my project.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Create new project (new workspace)
Create virtual environment
Install whatever packages
Reload (because I know better haha)
No interpreter selected (as indicated by status bar)
Click status bar
Dialog opens
Select interpreter (note that the virtual environment is in my workspace; I'm doing something weird to make extraPaths mad)
See that nothing happened and status bar still says "No interpreter selected"
Reload + repeat steps 5 through 9

On the fourth try, the virtual environment's interpreter was removed from the list of options. Here's a GIF:

Logs
User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'PythonPyTorchProfiler'
User belongs to experiment group 'ShowExtensionSurveyPrompt - enabled'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'DeprecatePythonPath - experiment'
> /home/saostrow/.pyenv/versions/3.9.0rc1/envs/trends/bin/python c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> /home/saostrow/.pyenv/versions/3.9.0rc1/envs/trends/bin/python c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> /home/saostrow/.pyenv/versions/3.9.0rc1/envs/trends/bin/python c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> /home/saostrow/.pyenv/versions/3.9.0rc1/envs/trends/bin/python c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
Error 2021-05-20 13:07:18: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): Unable to read file 'c:\Users\saostrow\Documents\code\extra-paths-repo\.vscode\settings.json' (Error: Unable to resolve non-existing file 'c:\Users\saostrow\Documents\code\extra-paths-repo\.vscode\settings.json')
	at _handleError (c:\Users\saostrow\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:156171)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async y.readText (c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\out\client\extension.js:9:344717)
	at async p.doesFileNeedToBeFixed (c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\out\client\extension.js:59:581560)
	at async c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\out\client\extension.js:59:580687
	at async Promise.all (index 1)
	at async p.getFilesToBeFixed (c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\out\client\extension.js:59:580633)
	at async p.updateTestSettings (c:\Users\saostrow\.vscode\extensions\ms-python.python-2021.5.842923320\out\client\extension.js:59:580260)] {
  code: 'FileNotFound'
}
Starting Pylance language server.
> conda --version
Python interpreter path: c:\Users\saostrow\Documents\code\extra-paths-repo\packages\venv\Scripts\python.exe

I have the same issue for a log time(about two months ago). When I first hit this issue, I cleaned the cache at %user%\AppData\Roaming\Code\User\globalStorage, then the python extension can find all the miniconda python environment in my machine.
It works about two months and today the bug happens again.
I am just guessing it is related to the cache and remote to ssh.

@guotuofeng Can you please open a new issue filling the issue template? Your issue seems different.

@savannahostrowski I'm not able to exactly reproduce the issue. But I do see that the Interpreter selected is not retained similar to https://github.com/microsoft/vscode-python/issues/16291 when in deprecatePythonPath experiment. Can you add the following to your user settings and see if it helps,
"python.experiments.optOutFrom": ["DeprecatePythonPath - experiment"]

@guotuofeng Can you please open a new issue filling the issue template? Your issue seems different.

https://github.com/microsoft/vscode-python/issues/16322 is created.
Please let me know if there is more information needed.

@karrtikr I cannot no longer repro :(. Seemed like it was just an issue for a day or so.


Add look up symbol shortcut for script editor

Fixes https://github.com/godotengine/godot/issues/86773

This seems to do the same as #91500


feat: Generic OAuth - Give the possibility to use the access_token in headers section

Solving #756
This PR gives flexibility to the Generic OAuth Flow when using a provider that accepts authorized API calls using the retrieved access_token via Authorization header instead of URL parameters.

So, after your comments, I think we can make it by default to be in the header.
I don't have any other case where we could use a different authorization prefix beyond 'Bearer'. I just made it flexible because I did not know if it would break anyone's integration.

Version is bumped, lint fixed and breaking_changes note added.

Great thank for working on this!


[Bug] are the workflow ID's correct?

Describe the bug
noticed an issue in the scripts:
https://github.com/temporalio/subscription-workflow-project-template-go/blob/93ce85b52b8c610c21a96f3397bef5b419047e11/cancelsubscription/main.go#L23
this uses "SubscriptionsWorkflowId-"+strconv.Itoa(i)
but the starter uses
https://github.com/temporalio/subscription-workflow-project-template-go/blob/88abd696b0fe6e627b91d8e0924575beb9770fe6/starter/main.go#L42
is this on purpose?

i see that Id is added in the id section... confusing :(


r2.0 windows build ProtoCompile issue

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from: source
TensorFlow version: 2.0
Python version: 3.6.5
Installed using: Visual studio
Bazel version (if compiling from source): 0.26.0
GCC/Compiler version (if compiling from source): Visual Studio 2017
CUDA/cuDNN version: 10, 7.1
GPU model and memory: NVIDIA 1080

Building under windows (following https://www.tensorflow.org/install/source_windows) I have an issue (or possibly 2) with compiling XXX.pb.h and XXX.pb.cc files.

Get errors about certain ones not being build (see below)
Bazel just sits there for hours with lines like :
ProtoCompile tensorflow/core/protobuf/autotuning.pb.h

It seems like different files each time but always these two issues. Killing, re-booting machine and starting build again sometimes gets you a bit further in terms of bazel actions completed.
c:\Software\tensorflow>bazel build --config=opt --config=cuda --config=monolithic --config=v2 --define=no_tensorflow_py_deps=true //tensorflow:tensorflow.dll
Starting local Bazel server and connecting to it...
... still trying to connect to local Bazel server after 10 seconds ...
... still trying to connect to local Bazel server after 20 seconds ...
... still trying to connect to local Bazel server after 30 seconds ...
WARNING: The following configs were expanded more than once: [cuda, using_cuda, monolithic]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Options provided by the client:
Inherited 'common' options: --isatty=1 --terminal_columns=120
INFO: Options provided by the client:
'build' options: --python_path=C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python36_64/python.exe
INFO: Reading rc options for 'build' from c:\software\tensorflow.bazelrc:
'build' options: --apple_platform_type=macos --define framework_shared_object=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone --strategy=Genrule=standalone -c opt --announce_rc --define=grpc_no_ares=true --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include
INFO: Reading rc options for 'build' from c:\software\tensorflow.tf_configure.bazelrc:
'build' options: --action_env PYTHON_BIN_PATH=C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python36_64/python.exe --action_env PYTHON_LIB_PATH=C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python36_64/lib/site-packages --python_path=C:/Program Files (x86)/Microsoft Visual Studio/Shared/Python36_64/python.exe --action_env CUDA_TOOLKIT_PATH=C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.0 --action_env TF_CUDA_COMPUTE_CAPABILITIES=3.5,7.0 --config=cuda --config monolithic --copt=-w --host_copt=-w --copt=-DWIN32_LEAN_AND_MEAN --host_copt=-DWIN32_LEAN_AND_MEAN --copt=-DNOGDI --host_copt=-DNOGDI --verbose_failures --distinct_host_configuration=false --define=override_eigen_strong_inline=true --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:cuda in file c:\software\tensorflow.bazelrc: --config=using_cuda --define=using_cuda_nvcc=true
INFO: Found applicable config definition build:using_cuda in file c:\software\tensorflow.bazelrc: --define=using_cuda=true --action_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain
INFO: Found applicable config definition build:monolithic in file c:\software\tensorflow.bazelrc: --define framework_shared_object=false
INFO: Found applicable config definition build:opt in file c:\software\tensorflow.tf_configure.bazelrc: --copt=/arch:AVX --define with_default_optimizations=true
INFO: Found applicable config definition build:cuda in file c:\software\tensorflow.bazelrc: --config=using_cuda --define=using_cuda_nvcc=true
INFO: Found applicable config definition build:using_cuda in file c:\software\tensorflow.bazelrc: --define=using_cuda=true --action_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain
INFO: Found applicable config definition build:monolithic in file c:\software\tensorflow.bazelrc: --define framework_shared_object=false
INFO: Found applicable config definition build:v2 in file c:\software\tensorflow.tf_configure.bazelrc: --define=tf_api_version=2
INFO: Analyzed target //tensorflow:tensorflow.dll (122 packages loaded, 9152 targets configured).
INFO: Found 1 target...
INFO: Deleting stale sandbox base C:/users/derek/_bazel_derek/fesmau5k/sandbox
Slow read: a 67402971-byte read from C:/users/derek/_bazel_derek/fesmau5k/execroot/org_tensorflow/bazel-out/x64_windows-opt/bin/external/local_config_cuda/cuda/cuda/include/sobol_direction_vectors.h took 13946 ms.
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/output.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/extension.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/float_conversion.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/arg.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/bind.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
INFO: From Compiling external/com_google_absl/absl/strings/internal/str_format/parser.cc:
cl : Command line warning D9025 : overriding '/w' with '/W3'
Slow read: a 67402971-byte read from C:/users/derek/_bazel_derek/fesmau5k/execroot/org_tensorflow/bazel-out/x64_windows-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual/third_party/gpus/cuda/include/sobol_direction_vectors.h took 23140 ms.
Slow read: a 50122658-byte read from C:/users/derek/_bazel_derek/fesmau5k/execroot/org_tensorflow/bazel-out/x64_windows-opt/bin/external/protobuf_archive/libprotoc_lib.a took 8412 ms.
INFO: From Linking external/grpc/libgrpc++_base.a:
server_posix.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
rpc_method.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
create_channel_posix.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
INFO: From ProtoCompile tensorflow/core/framework/tensor.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/saved_object_graph.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/device_properties.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/queue_runner.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2743:1: output 'tensorflow/core/protobuf/queue_runner.pb.h' was not created
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2743:1: output 'tensorflow/core/protobuf/queue_runner.pb.cc' was not created
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2743:1: not all outputs were created or valid
[3,342 / 5,505] 3 actions running
ProtoCompile tensorflow/core/protobuf/autotuning.pb.h; 11649s local
ProtoCompile tensorflow/core/profiler/op_profile.pb.h; 11648s local
ProtoCompile tensorflow/core/protobuf/debug.pb.h; 11648s local

@dmagee Can you tell us, Which protobuf version are you using?

I didn't install protobuf (https://www.tensorflow.org/install/source_windows doesn't mention installing protobuf, so assumed it came with the distribution. I fetched r2.0). Maybe that's the issue?

Update: I installed all the python modules from the linked :
"The dependencies are listed in the setup.py file under REQUIRED_PACKAGES."
[https://www.tensorflow.org/install/source_windows]
Python now has protobuf 3.9.0. I'm still getting similar errors:
....
INFO: From Linking external/grpc/libgrpc++_base.a:
server_posix.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
rpc_method.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
create_channel_posix.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
INFO: From Linking external/protobuf_archive/libprotobuf.a:
error_listener.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
INFO: From ProtoCompile tensorflow/core/debug/debugger_event_metadata.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
ERROR: C:/software/tensorflow/tensorflow/core/debug/BUILD:64:1: output 'tensorflow/core/debug/debugger_event_metadata.pb.h' was not created
ERROR: C:/software/tensorflow/tensorflow/core/debug/BUILD:64:1: output 'tensorflow/core/debug/debugger_event_metadata.pb.cc' was not created
ERROR: C:/software/tensorflow/tensorflow/core/debug/BUILD:64:1: not all outputs were created or valid
[3,710 / 6,123] ProtoCompile tensorflow/core/profiler/tfprof_log.pb.h; 562s local

Are you trying to build the 2.0 branch? What configuration options did you use?
What exact hash are you building?
@goldiegadde do we have a prebuilt binary for windows for 2.0 beta?

Are you trying to build the 2.0 branch?
It did "git checkout r2.0"

What configuration options did you use?
Basically default, except specifying to use CUDA 10 (see below)

c:\Software\tensorflow>python configure.py
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
You have bazel 0.26.0 installed.
Please specify the location of python. [Default is C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\python.exe]:
Found possible Python library paths:
C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\lib\site-packages]
Do you wish to build TensorFlow with XLA JIT support? [y/N]:
No XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]:
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: Y
CUDA support will be enabled for TensorFlow.
Found CUDA 10.0 in:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.0/lib/x64
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.0/include
Found cuDNN 7 in:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.0/lib/x64
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.0/include
Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 3.5,7.0]:
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:
Would you like to override eigen strong inline for some C++ compilation to reduce the compilation time? [Y/n]:
Eigen strong inline overridden.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
--config=mkl            # Build with MKL support.
--config=monolithic     # Config for mostly static monolithic build.
--config=gdr            # Build with GDR support.
--config=verbs          # Build with libverbs support.
--config=ngraph         # Build with Intel nGraph support.
--config=numa           # Build with NUMA support.
--config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.
Preconfigured Bazel build configs to DISABLE default on features:
--config=noaws          # Disable AWS S3 filesystem support.
--config=nogcp          # Disable GCP support.
--config=nohdfs         # Disable HDFS support.
--config=noignite       # Disable Apache Ignite support.
--config=nokafka        # Disable Apache Kafka support.
--config=nonccl         # Disable NVIDIA NCCL support.
NOTE: Many c/cpp files are built fine, it's just the ProtoCompile and XX.pb.h/XXX.pb.cc files that it is having issues with.

do we have a prebuilt binary for windows for 2.0 beta?
I wasn't aware of prebuilt libraries/DLLs for use with the C++ API. I'm sure I read you had to build from source for this. I'd be very happy to hear otherwise!

Thanks

I just tried this with the r1.14 version and am encountering the same issue(s).
INFO: From Linking external/protobuf_archive/libprotobuf.a:
error_listener.o : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
INFO: From ProtoCompile tensorflow/core/grappler/costs/op_performance_data.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/conv_autotuning.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/worker.pb.h:
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
bazel-out/x64_windows-opt/bin/external/protobuf_archive/src: warning: directory does not exist.
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2280:1: output 'tensorflow/core/protobuf/worker.pb.h' was not created
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2280:1: output 'tensorflow/core/protobuf/worker.pb.cc' was not created
ERROR: C:/software/tensorflow/tensorflow/core/BUILD:2280:1: not all outputs were created or valid
Target //tensorflow:tensorflow.dll failed to build
INFO: Elapsed time: 866.684s, Critical Path: 88.69s
INFO: 1136 processes: 1136 local.
FAILED: Build did NOT complete successfully

Closing as there has been no activity on this issue and the 2.0 branch has been fast forwarded past the time the comments are.
Please open a new issue if the problem persists.

@dmagee did u find any solutions to this problem ? it still occurs while building r2.5 from source

Please open a new issue, filling in the bug template as most likely the environment has changed in the last 2 years.

@mihaimaruseac i have opened a new issue , thanks


Syntax highlighting broken after member function with requires clause with less comparison

(Note: This was originally submitted to the cpp-tools repo as https://github.com/microsoft/vscode-cpptools/issues/11100)
Consider the following snippet:
template <int n>
struct S{
    int foo() requires(n == 2)
    {
        return 2;
    }

    int foo() requires(n < 2)
    {
        return 2;
    }

private:
    int b;
};

The syntax highlighting is completely broken after the second requires clause:

Expected behavior:
The syntax highlighting should continue to work as normal, as it does if you replace the < with >:

Version: 1.79.2
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/114.0.1823.51
Embedder: vscode.dev

I've moved this issue to https://github.com/jeff-hykin/better-cpp-syntax/issues/638, which is the repo that well pull our C++ syntax highlighting grammar from. Sorry for the repo ping pong!


Remove async_trait fron actors implementation.

Check to run make fmt again. Tests are green

Have fixed it in fd4a3255b4658a3dde0d1e15cb806ffb4245fe00


cleanup import sections in all modules, remove unused imports

Coverage decreased (-0.3%) to 79.286% when pulling efabc02cc0d95e5d2bc765f959ca6f55cd1996fa on import-cleanup into 16861ba322ed2f73b96c530f21bb271463a8b7b6 on master.


Inconsistent references when loading the checkpoint

Bug description
Hi,
I want to use the recognition_predictor but I get some errors when loading it.
I tested my code on a Colaboratory notebook so the environnement is clean.
Here is my code :
!pip install "python-doctr[tf]"
and then
from doctr.models import recognition_predictor
model = recognition_predictor('sar_resnet31', pretrained=True)

but I get :
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<keras.layers.normalization.batch_normalization.BatchNormalization object at 0x7f3fe0e70dd0> and <keras.layers.pooling.MaxPooling2D object at 0x7f3fe0e77510>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e96650> and <doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e236d0>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e236d0> and <doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e32710>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e32710> and <keras.layers.convolutional.Conv2D object at 0x7f3fe0e41790>).

I tried also with the master model, but I get the same kind of warnings.
Code snippet to reproduce the bug
from doctr.models import recognition_predictor
model = recognition_predictor('sar_resnet31', pretrained=True)

Error traceback
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<keras.layers.normalization.batch_normalization.BatchNormalization object at 0x7f3fe0e70dd0> and <keras.layers.pooling.MaxPooling2D object at 0x7f3fe0e77510>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e96650> and <doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e236d0>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e236d0> and <doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e32710>).
WARNING:tensorflow:Inconsistent references when loading the checkpoint into this object graph. Either the Trackable object references in the Python program have changed in an incompatible way, or the checkpoint was generated in an incompatible program.

Two checkpoint references resolved to different objects (<doctr.models.classification.resnet.tensorflow.ResnetBlock object at 0x7f3fe0e32710> and <keras.layers.convolutional.Conv2D object at 0x7f3fe0e41790>).

Environment
DocTR version: 0.5.0
TensorFlow version: 2.6.3
PyTorch version: 1.10.0+cu111 (torchvision 0.11.1+cu111)
OpenCV version: 4.1.2
OS: Ubuntu 18.04.5 LTS
Python version: 3.7.12
Is CUDA available (TensorFlow): No
Is CUDA available (PyTorch): No
CUDA runtime version: 11.1.105
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.0.5

Hi @LCMA7 :wave:
Those are only warnings, and we do experience that on a few models. It's hard to get to the bottom of this, as PyTorch doesn't operate the same way. In a nutshell, TensorFlow does Lazy initialization by default (meaning the kernel are not initialized when you instantiate the model, but after the first forward pass)
So when we load the checkpoint into the model, if some kernels are not yet initialized, it throws those warnings. But we have to clean the SAR & MASTER architecture implementations soon anyway, so I'll check if there is any more troublesome causes behind this :+1:

#925 will fix this for SAR :)

@felixdittrich92 are you positive? because that's a frequent warning for TF when all the layers are not built exactly as it expects it before loading a checkpoint 😅

@felixdittrich92 are you positive? because that's a frequent warning for TF when all the layers are not built exactly as it expects it before loading a checkpoint sweat_smile

@frgfm it will fix the inconsistent results not the warnings :sweat_smile: i have tested my PR several times and was not able to see any inconsitent results

@frgfm wdyt can we close this ? There are only warnings left (models works fine) which we can't avoid i think

I agree :+1:


No support for tasks

When can we expect support for tasks in the SDK?

What's the status on support for tasks related to contacts?
When trying to add a task with ownerType = contact I keep getting the following error:
The task deal id was not provided.
Not sure why the API is requiring a deal id (when relid is referencing a contact, not a deal)?

Confirmed that the endpoint is working via curl:
curl \
  -d '{"dealTask":{"title":null,"ownerType":"contact","relid":"7","status":0,"note":"Testing Task","duedate":"2017-02-25T12:00:00-06:00","edate":"2017-02-25T12:15:00-06:00","dealTasktype":"1","assignee":2}}' \
  -H "Api-Token: YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -X POST https://youraccountname.api-us1.com/api/3/dealTasks/
Would be nice if this functionality could be incorporated into class AC_Contact


Can I configure syslog to get local7.debug and kern.everything using the above ARM template

I have a log analytics work space and I configure syslog to collect kern and local7 logs but I have do it through the log analytics portal after deploying the log analytics in all the subscriptions. Can I configure syslog with ARM Template so i can avoid doing it manually everytime.
I need to collect kern logs and local7 logs.
Let me know if you have a example template to follow. above one looks little complicated for starters.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e7651b7e-278e-2839-e9f4-cee3d8c8d60b
Version Independent ID: 45386b9f-a8e3-a398-c0da-880fbdd76abb
Content: Use Azure Resource Manager templates to Create and Configure a Log Analytics Workspace
Content Source: articles/log-analytics/log-analytics-template-workspace-configuration.md
Service: log-analytics
GitHub Login: @richrundmsft
Microsoft Alias: richrund

@akramwaseem Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@MGoedtel can you or someone from the Log Analytics team look at this request? thanks.

@akramwaseem, @richrundmsft, and @vasivara-MSFT - I will identify the right person from the LA team to review this and provide a response.  #in-progress.

@MGoedtel -- I looked at the document and seems like a bit complicated for starters.
Lets say , I have a log analytics workspace which is already deployed with a template and some alerts.I am wondering whether I can configure it to collect kern log and local7 logs using the above mentioned examples.  Let me give it a try and see how it goes.

@akramwaseem - Agreed this article, which was originally written by someone else, is not well structured and I plan on re-writing it as soon as I can get some other priorities off my plate.  Let me check with someone to see if you can use the template to configure post-deployment of a workspace (I believe you can but not 100% certain) and get back to you.

@ MGoedtel -- Well, I tried and there are lot of things which are missing .
I am not sure that the API version is still used or there is a updated API version. and Type: datasources is not how it works , it should be something like "Microsoft.OperationalInsights/workspaces/dataSources" and name : is not easy as it is mentioned above. we have concat it with the workspace like ""name": "[concat(parameters('workspaceName'), '/dataSources')]",".
I think you need to re-write whole documentation and with better and working examples.
After all this , I was able deploy the template but it was successful, but it stuck is deploy state forever. Not sure why ?
Will get back to you if I found why it is in deploying state forever.

@akramwaseem - The API version is still used and I'm working on verifying a few things related to that before I update this article and others that leverage the API to complete a task.  In the meantime, you can refer to this reference as the authoritative source on the Log Analytics API version - https://dev.loganalytics.io/documentation/Tools/Api-Specifications.
Like I originally said, I agree the article needs to be re-written and that's something I am plan to work on soon.

@vasivara-MSFT - I have an open work item for this and also have some changes coming to this content. I'm going to go ahead and close this issue since we're tracking this separately. Thanks for identifying it. #please-close.

@akramwaseem We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Deprecated create_function

create_function is deprecated in PHP 7.2
http://php.net/manual/en/function.create-function.php

Please add this one!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:19: uses_setup_py: python setup.py install is deprecated.
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:30: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_feyvc7p36x/clone/recipe/meta.yaml:40: http_url: http://yapsy.sourceforge.net is not https
Errors were found


[0.46] Packager fails: Unknown plugin "transform-runtime"

Create a fresh app with: react-native init rn46 --version "0.46.0-rc.2", then CMD+R in Xcode which attempts to fire up the packager, but immediately bombs with:
ReferenceError: Unknown plugin "transform-runtime" specified in "/rn46/node_modules/regenerator-transform/package.json" at 0, attempted to resolve relative to "/rn46/node_modules/regenerator-transform" (While processing preset: "/rn46/node_modules/babel-preset-react-native/index.js")
    at /rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
    at Array.map (native)
    at Function.normalisePlugins (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
    at OptionManager.mergeOptions (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
    at OptionManager.init (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at compile (/rn46/node_modules/babel-register/lib/node.js:103:45)
    at loader (/rn46/node_modules/babel-register/lib/node.js:144:14)
    at Object.require.extensions.(anonymous function) [as .js] (/rn46/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)

Since it's a reference error, I add the dependency npm i babel-plugin-transform-runtime --save-dev and rerun, which now bombs with:
Error: Couldn't find preset "env" relative to directory "/rn46/node_modules/regenerator-transform" (While processing preset: "/rn46/node_modules/babel-preset-react-native/index.js")
    at /rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:293:19
    at Array.map (native)
    at OptionManager.resolvePresets (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
    at OptionManager.mergePresets (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
    at OptionManager.mergeOptions (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
    at OptionManager.init (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at compile (/rn46/node_modules/babel-register/lib/node.js:103:45)
    at loader (/rn46/node_modules/babel-register/lib/node.js:144:14)
    at Object.require.extensions.(anonymous function) [as .js] (/rn46/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:488:32)

Okay, let's now try npm i --save-dev babel-preset-env, which bombs with:
Error: Options {"loose":true} passed to /rn46/node_modules/babel-preset-env/lib/index.js which does not accept options. (While processing preset: "/rn46/node_modules/babel-preset-env/lib/index.js") (While processing preset: "/rn46/node_modules/babel-preset-env/lib/index.js") (While processing preset: "/rn46/node_modules/babel-preset-react-native/index.js")
    at /rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:314:17
    at Array.map (native)
    at OptionManager.resolvePresets (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
    at OptionManager.mergePresets (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
    at OptionManager.mergeOptions (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
    at OptionManager.init (/rn46/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at compile (/rn46/node_modules/babel-register/lib/node.js:103:45)
    at loader (/rn46/node_modules/babel-register/lib/node.js:144:14)
    at Object.require.extensions.(anonymous function) [as .js] (/rn46/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:488:32)

Something has definitely gone wrong down this rabbit hole. I noticed that @davidaurelio just upgraded babel-preset-react-native with commit bc22a4d, not sure if it's related but the update is already showing up in the initialized package.json:
	"devDependencies": {
		"babel-jest": "20.0.3",
		"babel-preset-react-native": "2.0.0",
		"jest": "20.0.4",
		"react-test-renderer": "16.0.0-alpha.12"
	}

I've got the exact same problem after upgrading to 0.46.0-rc.2, @sjmueller have you managed to sort that out?

Ok @sjmueller  rm -rf .babelrc solved that problem for me. No idea why.

I haven't been able to sort it out yet. Tried a bunch of different things, but reverted and now stuck on 0.44 until this can be fixed.

Why don't you just delete the .babelrc file @sjmueller ?

@SudoPlz because I'm using transform-decorators-legacy in my project, and I have decorators all over the place.
However just to check, I did try deleting my .babelrc just to see if it get passed the problem; it does, but unfortunately I just get slammed with Unable to resolve module 'AccessibilityInfo' that everyone is dealing with on #14209. Yes I tried:
rm -rf node_modules
rm -rf $TMPDIR/react-*
watchman watch-del-all
npm i
npm start -- --reset-cache

So gracious for what react-native and the core team, but honestly the amount of instability over the past few releases is pretty staggering -- 0.44.2+, 0.45+, and 0.46 rc all have their own set of problems. We really need the bug fixes in FlatList and NativeAnimated in the past two months, but can't get at them no matter how hard we try...

Just to put more context here:
Looks that the problem is React Packager trying to transpile regenerator-transform that has been already transpiled before publishing to npm. It still defines transform-runtime in its package.json, however it's under dev dependencies.
Another explanation of similar issue from another repository: https://github.com/tommikaikkonen/redux-orm/issues/24#issuecomment-228623502

Currently getting this error as well...
ReferenceError: Unknown plugin "transform-runtime" specified in "/../node_modules/regenerator-transform/package.json"

on version 0.46.0 of react native

Also getting this error in 0.46.0

@joriswa I just tried this and it works. Any insight as to why that fixed the issue or if that fix will cause any other issues down the road?

@nprz I got no idea whatsoever.

Also got this error after upgrading from 0.45 to 0.46
I resolved it by adding babel-plugin-transform-runtime & regenerator-transform to dev dependencies.
Then running ./node_modules/react-native/scripts/packager.sh --reset-cache

Dong this rm -rf .babelrc resolved the issue for me as well. However, I'm concerned whether this will create more problems ahead?

I deleted .babelrc, then I encountered this problem #14209.

As a quick workaround, you can use haul which works just fine.

deleted .babelrc also works for me. But I am also using babel transform-decorators-legacy plugin, did anyone know how could I use decorators without .babelrc settings? thanks.

The same issue here, wanted to start a new project :(

I noticed doing (cd node_modules/react-native && node "./local-cli/cli.js" start) repros the error, but doing node node_modules/react-native/local-cli/cli.js start shows no error and packager starts seemingly correctly. I didn't expect the working directory to have effect, something is anormal.

rm -rf .babelrc works, but when I try to run npm install --save redux react-redux in the project directory it causes this error:

I'm assuming this is related to the problem w/ upgrading from 0.45 -> 0.46?

I found a solution. This is due to what I think is a kinda-bug in Babel, but I have a workaround anyway. Sending a PR soon.

@thechee514 try resetting the packager cache
./node_modules/react-native/scripts/packager.sh --reset-cache

@cmdshepard it gives me this error:
no such file or directory: ./node_modules/react-native/scripts/packager.sh
Could this be because I have yarnpkg installed? So instead of entering: npm install --save redux react-redux I should enter yarn add redux?

@thechee514 what version of react-native are you using?

@cmdshepard 0.46

@thechee514 try /Users/thechee514/Documents/workspace/test/node_modules/react-native/scripts/packager.sh --reset-cache

downgrade babel-preset-react-native 2.1.0  to 2.0.0  is working fine in my case.

@cmdshepard I'm still getting the same error, here is the output after attempting to install redux:

@thechee514 You're using react-native 0.45.1 - On this version, the packager is located in a different directory. Try running ./node_modules/react-native/packager/react-native-xcode.sh from your project directory.

@cmdshepard, I'm getting a slightly different error now: ./node_modules/react-native/packager/react-native-xcode.sh must be invoked by Xcode. I was actually running the code you sent earlier on 0.46.

@thechee514 yes. yarn add redux will do the same thing although if you initialized your project using yarn, you should stick to using yarn

Okay, I initialized the project with react-native init project, but I think it just uses yarn. Thanks for the help though @cmdshepard!

I don't know why Facebook releases RN with bug which is so obvious. User reported this issue in rc and the bug still exists in the stable release. User even couldn't run a react-native init
and make it run straightforward. Similar packager issue was found in 0.45. So disappointing.

So, the original problem "Unknown plugin "transform-runtime"" should now be fixed for v0.46 if you do a clean set-up, or if you upgrade the metro-bundler package to 0.7.8 in your repo/lockfile. I'll wait for confirmation this looks fixed for you folks before closing.
Creating a project from scratch with v0.46 worked for me, and the simulator loads the app correctly. For the other problems that may still happen, please open new issues :)

@jp928 Facebook doesn't manage open source releases for react-native, and we are probably not as actively involved as we should be. There are probably ways we can get better at this, but if this is a huge problem for you, it would be awesome if you could step up and help us avoid this class of problems in the future by helping us straighten out the release cycle.

@jp928 I am really sorry for the inconvenience. The "RC" bug report somewhat got lost in my inbox full of notifications. During manual testing that I usually do (as well as testing on the CI) the bug wasn't revealed. Sometimes not every single issue can be reproduced, but I think we did our best to fix it as soon as possible post the release.

So is a minor release fix coming? I'm working around with a manual react-native start, as run-ios result in the babel related packager errors. Other workarounds haven't worked for me on getting run-ios to work.
A side question is this: does this affect production releases, which wouldn't be tied to a running instance of the packager?
Repasting from the other issue, my package.json:
{
  "name": "<name>",
  "version": "0.0.1",
  "private": true,
  "eslintConfig": {
    "parserOptions": {
      "ecmaVersion": 6,
      "sourceType": "module",
      "ecmaFeatures": {
        "jsx": true,
        "experimentalObjectRestSpread": true
      }
    },
    "env": {
      "browser": true,
      "node": true
    },
    "plugins": [
      "react",
      "react-native"
    ],
    "rules": {
      "comma-dangle": [
        2,
        "always-multiline"
      ],
      "semi": [
        2,
        "never"
      ],
      "react-native/no-unused-styles": 2,
      "react-native/split-platform-components": 2
    }
  },
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "babel-plugin-idx": "^1.1.0",
    "bugsnag-react-native": "^2.2.3",
    "he": "^1.1.0",
    "lodash": "^4.17.2",
    "moment-timezone": "^0.5.10",
    "node-summary": "file:../node-summary/",
    "react": "16.0.0-alpha.12",
    "react-native": "0.46.0",
    "react-native-blur": "^3.1",
    "react-native-code-push": "3.0.1-beta",
    "react-native-firebase-analytics": "^3.0.0",
    "react-native-fit-image": "^1.4.8",
    "react-native-highlight-words": "^1.0.0",
    "react-native-keep-awake": "^2.0.4",
    "react-native-linear-gradient": "^2.0.0",
    "react-native-modalbox": "^1.3.8",
    "react-native-notification": "^2.0.0",
    "react-native-orientation": "file:../react-native-orientation-RN0.40/",
    "react-native-parallax-scroll-view": "^0.19.0",
    "react-native-safari-view": "^2.0.0",
    "react-native-status-bar-size": "^0.3.2",
    "react-native-swiper": "^1.5.4",
    "react-native-tooltip": "^5.0.0",
    "react-native-tts": "^1.3.0",
    "react-native-vector-icons": "^4.1.1",
    "react-native-webview-bridge": "file:../react-native-webview-bridge-RN0.40/",
    "react-redux": "^5.0.1",
    "realm": "^1.3.1",
    "redux": "^3.6.0",
    "redux-thunk": "^2.1.0"
  },
  "devDependencies": {
    "redux-logger": "^3.0.6"
  }
}

.babelrc:
{
  "presets": ["react-native"],
  "plugins": ["idx"]
}

0.46.1 is coming with a fix for different issue. Fix for this issue was
released to metro-bundler package directly. Metro-bundler is React Native
dependency "^0.7.6" meaning that you will get latest patch version every
time you do a fresh install. Since they released 0.7.8 with a fix, no React
Native update is required.
On Fri, 7 Jul 2017 at 18:58 Gary F<EMAIL_ADDRESS>wrote:

So is a minor release fix coming? I'm working around with a manual react-native
start, as run-ios result in the babel related packager errors. Other
workarounds haven't worked for me on getting run-ios to work.
A side question is this: does this affect production releases, which
wouldn't be tied to a running instance of the packager?
Repasting from the other issue, my package.json:
{
"name": "",
"version": "0.0.1",
"private": true,
"eslintConfig": {
"parserOptions": {
"ecmaVersion": 6,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true,
"experimentalObjectRestSpread": true
}
},
"env": {
"browser": true,
"node": true
},
"plugins": [
"react",
"react-native"
],
"rules": {
"comma-dangle": [
2,
"always-multiline"
],
"semi": [
2,
"never"
],
"react-native/no-unused-styles": 2,
"react-native/split-platform-components": 2
}
},
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start"
},
"dependencies": {
"babel-plugin-idx": "^1.1.0",
"bugsnag-react-native": "^2.2.3",
"he": "^1.1.0",
"lodash": "^4.17.2",
"moment-timezone": "^0.5.10",
"node-summary": "file:../node-summary/",
"react": "16.0.0-alpha.12",
"react-native": "0.46.0",
"react-native-blur": "^3.1",
"react-native-code-push": "3.0.1-beta",
"react-native-firebase-analytics": "^3.0.0",
"react-native-fit-image": "^1.4.8",
"react-native-highlight-words": "^1.0.0",
"react-native-keep-awake": "^2.0.4",
"react-native-linear-gradient": "^2.0.0",
"react-native-modalbox": "^1.3.8",
"react-native-notification": "^2.0.0",
"react-native-orientation": "file:../react-native-orientation-RN0.40/",
"react-native-parallax-scroll-view": "^0.19.0",
"react-native-safari-view": "^2.0.0",
"react-native-status-bar-size": "^0.3.2",
"react-native-swiper": "^1.5.4",
"react-native-tooltip": "^5.0.0",
"react-native-tts": "^1.3.0",
"react-native-vector-icons": "^4.1.1",
"react-native-webview-bridge": "file:../react-native-webview-bridge-RN0.40/",
"react-redux": "^5.0.1",
"realm": "^1.3.1",
"redux": "^3.6.0",
"redux-thunk": "^2.1.0"
},
"devDependencies": {
"redux-logger": "^3.0.6"
}
}
.babelrc:
{
"presets": ["react-native"],
"plugins": ["idx"]
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/14530#issuecomment-313736819,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWcxv389Y11Am5kDH9bEwivUW-bylj0ks5sLmPLgaJpZM4N65Yi
.

Can you clarify on "you will get latest patch version every time you do a fresh install"? Does it include running a react-native-git-upgrade?

Does it include running a react-native-git-upgrade?

I believe not. The action necessary depends on what package manager you use. For yarn, you have to upgrade the version of metro-bundler used in the lockfile. I believe yarn upgrade can be used for that. For npm 5, there should be a similar command to upgrade the locked dependencies, but I'm not familiar. For npm 4, deleting node_modules and running npm install again should do the deal, or upgrading the shrinkwrap file if any.

Confirm fixed with yarn upgrade, and yarn.lock file went from version "0.7.6" to version "0.7.8", under the line metro-bundler@^0.7.4:. Thanks for the clarification!
A side issue I noticed now on React Packager's terminal below. Does this warrant a new issue?
Loading dependency graph...jest-haste-map: @providesModule naming collision:
  Duplicate module name: base64-js
  Paths: /Users/<user>/Documents/code/<project>/node_modules/react-native/node_modules/base64-js/package.json collides with /Users/<user>/Documents/code/<project>/node_modules/react-native/node_modules/simple-plist/node_modules/base64-js/package.json

A side issue I noticed now on React Packager's terminal below. Does this warrant a new issue?

I believe it's the issue reported in https://github.com/facebook/metro-bundler/issues/18. We have a fix that's been landed, not sure when we'll make it spread through react-native yet.

That's fine, shouldn't be a blocker as it's just a console warning.

Going to close it as it looks like the issue has been resolved :)