[Adreno] Fix mem_scope annotations for prim funcs having several heads

decision if function can work with textures. To remove dependency on the order of traversing, we decide to markup function support textures if any input op support textures src/relay/transforms/annotate_texture_storage.cc
fix of injective schedules for non blocking case for performance improvements (python/tvm/topi/adreno/utils.py

@echuraev

@masahi could you please take a look to it?

@tvm-bot rerun


Doubt

I would like to ask the author why the model codes of S2V-DDQN, S2V-DuelDQN and S2V-DuelDDQN are missing for comparison？

Thanks a lot for your interest!
The codes of "S2V_DQN" and "S2V_DUEL" can be viewed at line 21 and line 495 respectively in the file "models.py".
To enable or disable "Double" setting, please set "args.double_dqn" (at line 60 in the file "main.py") to "True" or "False" respectively.
The "Double" setting is processed at lines 45-79 in the file "rl_agents.py" for different models.


Unable to remote server :|

Unable to connect server

error message:
Error: could not update remote scripts

@zaliir this should now be fixed in 0.9.17: https://github.com/TorchStudio/torchstudio/releases/tag/0.9.17


feat: add churn plugin

Resolves #520 .
As with the entropy plugin, this lifts its error::*, types.rs and linguist::{fs.rs, mod.rs} almost directly from Hipcheck core.
The metric.rs file is lifted almost directly from plugins/entropy/src/metric.rs.
The configuration requires langs-file to be present, but also optionally allows two additional args for a custom default query. if either of the args are present, the other is expected and the parsing code reflects that.

Looks good!


Write client/server interop spec

/cc @crwilcox @gurayAlsac @peetsasaki

Currently there is no guide how integrated server with app? Or any other doc that will help integrate app with server.

There isn't a formal spec and different apps or servers may have different needs. But we have made a sample reference app available that integrates with this server:
https://github.com/google/exposure-notifications-android
The gist of it is that this server makes available an index of available export files to fetch, which the app periodically checks. See https://github.com/google/exposure-notifications-android/blob/master/app/src/main/java/com/google/android/apps/exposurenotification/network/DiagnosisKeyDownloader.java


onboard to gallery in national clouds

Docs Build status updates of commit 6a9baa0:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publish service's config file: .openpublishing.publish.config.json is not found. Exception:

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

Docs Build status updates of commit 77d4e3d:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 77d4e3d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publish service's config file: .openpublishing.publish.config.json is not found. Exception:

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


⚠ Samsung has degraded performance

In 4b7852f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2928 ms

Resolved: Samsung performance has improved in cfd0759.


[Docs] mesheryctl system reset page missing

Current State
No page exists for this command in the mesheryctl Command Reference.
Desired State

A subcommand page should be dedicated to mesheryctl system reset.

Implementation

Create an entry for this subcommand in https://github.com/layer5io/meshery/tree/master/docs/_data/mesheryctlcommands/

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

@navendu-pottekkat I would like to work on this.

// @Anita-ihuman Please do refer issue #2943


NPE when running genIntellijRuns on CodeChickenLib

bombcar@lappy386 ~/Documents/GitHub/CodeChickenLib (fixbuild) $ ./gradlew clean setupDecompWorkspace idea genI

> Task :idea
Generated IDEA project at file:///Users/bombcar/Documents/GitHub/CodeChickenLib/CodeChickenLib.ipr

> Task :genIntellijRuns
java.lang.NullPointerException
        at net.minecraftforge.gradle.user.UserBasePlugin.add(UserBasePlugin.java:552)
        at net.minecraftforge.gradle.user.UserBasePlugin.injectIntellijRuns(UserBasePlugin.java:519)
        at net.minecraftforge.gradle.user.UserBasePlugin$3.execute(UserBasePlugin.java:446)
        at net.minecraftforge.gradle.user.UserBasePlugin$3.execute(UserBasePlugin.java:415)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:732)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:705)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:494)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
        at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:479)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:462)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$400(ExecuteActionsTaskExecuter.java:105)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:273)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:251)
        at org.gradle.internal.execution.steps.ExecuteStep.lambda$executeOperation$1(ExecuteStep.java:66)
        at java.util.Optional.orElseGet(Optional.java:267)
        at org.gradle.internal.execution.steps.ExecuteStep.executeOperation(ExecuteStep.java:66)
        at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:34)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:47)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:44)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
        at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:34)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:72)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:42)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:53)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:39)
        at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:44)
        at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:77)
        at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:58)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:54)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:32)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:57)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:38)
        at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:63)
        at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:30)
        at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:176)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:76)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:47)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:43)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:32)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:39)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:25)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:102)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:95)
        at java.util.Optional.map(Optional.java:215)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:83)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:96)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:52)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:83)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:54)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:88)
        at java.util.Optional.orElseGet(Optional.java:267)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:88)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
        at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:46)
        at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:34)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:43)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution$3.withWorkspace(ExecuteActionsTaskExecuter.java:286)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:43)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:33)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:40)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:30)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:54)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:40)
        at org.gradle.internal.execution.impl.DefaultExecutionEngine.rebuild(DefaultExecutionEngine.java:46)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$0(ExecuteActionsTaskExecuter.java:182)
        at java.util.Optional.map(Optional.java:215)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:182)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
        at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:411)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:398)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:391)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:377)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
        at java.lang.Thread.run(Thread.java:748)

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

Now this was run on codechickenlib - which makes sense; a library might not be able to generate runs, but we should detect it's a library and just politely warn out.
Also we should print the "build script" ID when it explodes, mine was 8fa7883b6196c1765266f4e6ddf3118d5043aafb

Even a lib is can be run inside of MC. And it shold be just fine to start minecraft with it added as mod. I have no idea where that comes from as I never use the command line, but rely on the IntelliJ plugin. This happens only with CCC or can you reproduce it elsewhere?
Not sure this is easily possible. We could print the hash at every run of the build script such that it will show up in the logs.

So CCL is strange in that it runs from the 1.7.10 folder on a normal install. Don’t know if that affects it.
but what is crashing here isn’t runClient but gensIntellijruns - the gradle code what sets up running it in the IDE.
Nothing else I’ve seen breaks here

So you cannot get it to run? I have never had any issues with importing the project into IntelliJ directly.

Oh I can load it into intelij - and I don’t use the run from inside it usually. Just surprised that my normal commands caused an NPE.
I suspect it is looking for @Mod or something to know where to “start” and being coreLib it doesn’t have that

Could you verify that? You can use our DeveloperCapes for it. It is a lib-only project as well. Not having a PC for a few days.

Hmm, that one worked perfectly. It's gotta be something about codechickenlib itself.
Let me try some of the others that move into that 1.7.10 folder:

Baubles worked, something it is looking for in CCL it's not finding.
Aha! CCL is not a normal mod nor is it a coreMod in the IFMLLoadingPlugin method, it's basically an extension to CodeChickenCore.
https://github.com/GTNewHorizons/CodeChickenLib/commit/8933d4cf78db58e73a38453e92bd72c5a33f2bbb


[stable/k8s-spot-termination-handler] Add maintainers

Add maintainers as per #13867
Chart had no OWNERS file, adding myself and @KierranM
Signed-off-by: Frode Egeland<EMAIL_ADDRESS>Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @scottrigby

@maorfr , any chance of approving this one?

@egeland hey!
thanks for volunteering ;)
i'd like to get @KierranM 's lgtm on this

Thanks for doing this @egeland

/ok-to-test
/lgtm


Multilng client generator

rake task for generating client in more languages, defaulting ruby

@abellotti please review

Thanks @slemrmartin for the update 👍
/cc @agrare can you take a 👀

Love the flexibility, is there anything we should add to the openapi config json slash do we need different config files per language?

@agrare I tried only bash client, it works correctly generated with the same json config

Okay, something we should keep in mind if we go to generate e.g. python/go clients...they might need different json config.


COMP: Added GTRACT as an option in cmake

GTRACT is important in DWI data processing, especially gtractResampleDWIInPlace is a very important tool in DWI processing pipeline.

@hjmjohnson Please check this pull request.


Wrapper offline 1.2.3 download is corrupted

When i try to download the newest version of wrapper it always says that i have an older version of node.js that could cause problems and the start.bat file is nowhere to be found.
an automatic update also broke it previously please fix this as soon as possible so that i can upload other videos on my main channel.

1.2.3 is not the latest version.


81 refactor frame menubar

would you say it would overall help for not having duplicate logic to have a helper class that has all these methods that use a complex submorph hierarchie. E.g. the canteen name has been commented here two times in two different methods which do the same.

Actually I wouldn't say we need to have that, as long as the individual tests are readable


Wont Post The downtime

Hi the bot wont post when a bot goes offline can i get some help please

do yours post when th bots come online or just dont it post at all

I'm gonna close this as it seems to be a duplicate of #22. Please check the solution suggested in that issue.
If you feel like this issue is not a duplicate of the aforementioned one, feel free to re-open it.


Catalog accessor

This is the reduced interface for the catalog that should make it easier for other parts of the system to use the catalog without becoming tightly coupled to the internal implementation of the catalog (i.e. all of the Postgres-isms).
The intent is that reading and including catalog/catalog_accessor.h is sufficient for people learning the system to interface with the catalog enough to support their future projects.
What is complete:  The API should be mostly stable.  People who need to interface with the catalog (to include touching a Schema object in any way) should review catalog_accessor.h and make sure that the functions there support everything they need to do in the catalog.  If not, they should start a review and request a change detailing exactly what they need and why they need it.
Work that still needs to be completed:

[x] Remove need for namespace_oid_t when we have an OID to something in pg_class table
[ ] Improve fine-grained access into pg_attribute for supporting column addition, deletions, and modifications
[x] Add support for storing indexes
[ ] Fill in stubbed out implementations
[ ] Use indexes rather than table scans

The current state of this PR should make the overall catalog API stable with the exception of how to pass and store expressions inside of default values and index key schemas.  Additionally, none of the operations that modify the catalog are thread safe, but concurrent lookups (without modifications) should be thread safe.
This should be able to support end-to-end testing of static schemas like TPC-C, while we write tests for the catalog's API and then refactor the backend.

While trying to switch the catalog test over to GC and the accessor, several memory leaks deep inside the implementation appeared.  These appear to be caused by a call to BeginTransaction inside the catalog logic that is not paired with a call to Abort or Commit and instead manually delete TransactionContext.  This effectively disables GC by causing the transaction manager to have a hung transaction.

Closed in lieu of #392.


Its possible to compile for freebsd?

Im wondering to deploy onlyoffice in companion with nextcloud on freebsd

Hello
Unfortunately Document Server cannot be installed on freebsd
Anyway, if you are interested in using Document Server with Nextcloud we would recommend to try working with our Integration application that will allow you to connect Document Server to your Nextcloud.
Please feel free to post the question in the appropriate section


Print warnings for odd restriction relations, handle no_exit, only_u_turn and multiple from-members

When I started to review #2673 I revisited the OSM wiki for turn restrictions and noticed a few discrepancies in our implementation. With this PR we now:

support restriction=only_u_turn. For example this relation: https://www.openstreetmap.org/relation/12938700 and this route (watch out this opens the new maps client :partying_face:)

support restriction=no_exit, which can use multiple from members like here and the according route. This also closes #2136.

log warnings about restriction relations that are broken in some way or another. For Germany I got around 300 warnings most of them which can be easily fixed or are already fixed in the meantime (my OSM file was created in January).

This PR still does not fix #446, so we are still missing restrictions with multiple via-members and we also ignore restriction:conditional or restriction:vehicle:conditional tags. There are some that aren't about time restrictions (like in #374), but rather restrictions like weight > 3.5, which we could also convert to restriction:hgv maybe (or print a warning). But that is for another issue.

Here are the warnings I got when I imported the most recent Germany OSM file from Geofabrik:

 Restriction relation 103243 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 109980 has a member with an unknown role 'location_hint': {restriction=only_straight_on, type=restriction, source=Schild besichtigt (siehe Mitglieder)}. Relation ignored.
 Restriction relation 251946 has a member with an unknown role 'location_hint': {restriction=no_right_turn, type=restriction, except=psv;bicycle}. Relation ignored.
 Restriction relation 251947 has a member with an unknown role 'location_hint': {restriction=no_left_turn, type=restriction, except=psv;bicycle}. Relation ignored.
 Restriction relation 255108 has a member with an unknown role 'location_hint': {restriction=only_right_turn, type=restriction}. Relation ignored.
 Restriction relation 335288 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 898742 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 1019933 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 1101374 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_right_turn, type=restriction, except=destination}. Relation ignored.
 Restriction relation 1101375 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_left_turn, type=restriction, except=destination}. Relation ignored.
 Restriction relation 1136101 has a member with an unknown role 'location_hint': {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 1274233 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 1459753 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 1666387 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 1783943 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 1830919 is missing a member with role 'from' or 'to': {restriction=only_left_turn, type=restriction}. Relation ignored
 Restriction relation 1853892 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 1908298 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 1908301 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 1908303 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 1950053 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 2050160 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 2113153 has no member with role 'via': {restriction=no_entry, type=restriction}. Relation ignored
 Restriction relation 2153441 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 2198414 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_right_turn, restriction:motorcycle=no_right_turn, type=restriction, restriction:motorcar=no_right_turn}. Relation ignored.
 Restriction relation 2253506 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 2253507 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 2580515 has a member with an unknown role 'tr_source': {restriction:hgv=no_right_turn, type=restriction}. Relation ignored.
 Restriction relation 2749985 is missing a member with role 'from' or 'to': {restriction=only_left_turn, type=restriction}. Relation ignored
 Restriction relation 2887352 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_straight_on, type=restriction, restriction:motor_vehicle=no_straight_on}. Relation ignored.
 Restriction relation 2903722 has no member with role 'via': {restriction=no_straight_on, except=bicycle, fixme="no_straight_on" kann eigentlich nur so gemeint sein, Bitte vor Ort prüfen, type=restriction}. Relation ignored
 Restriction relation 2910883 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 2914936 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 2951411 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 3066555 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 3066556 has a member with role 'to' and type 'RELATION', but it should be of type 'way': {restriction=no_right_turn, type=restriction}. Relation ignored.
 Restriction relation 3066557 has a member with role 'from' and type 'RELATION', but it should be of type 'way'{restriction=no_u_turn, type=restriction}. Relation ignored.
 Restriction relation 3069515 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3069516 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3069517 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 3079087 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 3133529 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 3144284 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 3150946 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3150950 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3161237 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 3244419 has a member with an unknown role 'forward': {restriction=no_left_turn, type=restriction}. Relation ignored.
 Restriction relation 3299971 has multiple members with role 'from' even though it is not a 'no_entry' restriction: {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 3330912 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3337540 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_right_turn, restriction:hgv=no_right_turn, except=bicycle;moped;motorcar;psv, type=restriction}. Relation ignored.
 Restriction relation 3342365 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 3391122 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {type=restriction, restriction:tourist_bus=only_right_turn, except=bicycle;hgv;motorcar;psv}. Relation ignored.
 Restriction relation 3399812 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 3482291 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 3482293 is missing a member with role 'from' or 'to': {restriction=only_left_turn, type=restriction}. Relation ignored
 Restriction relation 3509783 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 3554215 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {type=restriction, restriction:tourist_bus=only_right_turn, except=bicycle;hgv;motorcar;psv}. Relation ignored.
 Restriction relation 3650110 has a member with an unknown role '': {restriction=no_left_turn, type=restriction}. Relation ignored.
 Restriction relation 3696207 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 3827586 has a 'restriction' tag, but also 'restriction:' tags: {restriction=only_right_turn, restriction:hgv=only_right_turn, type=restriction}. Relation ignored.
 Restriction relation 3948850 neither has a 'restriction' nor 'restriction:' tags: {note:restriction=no_straight_on, type=restriction, fixme=check}. Relation ignored.
 Restriction relation 3987044 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 4027715 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 4256838 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 4264433 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 4264434 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 4264435 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 4264436 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 4429061 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 4429062 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 4437663 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 4449103 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 4520658 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 4520659 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 4520660 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 4681218 has a member with an unknown role 'location_hint': {restriction=no_left_turn, type=restriction}. Relation ignored.
 Restriction relation 5255268 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 5490513 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_left_turn, restriction:hgv=no_left_turn, note=gilt nur für LKWs (hgv) - für eine breitere Abdeckung durch Router aber restriction neben restriction:hgv belassen., except=bicycle;mofa;moped;motorcycle;motorcar;bus;taxi;emergency, type=restriction}. Relation ignored.
 Restriction relation 5597863 has a member with an unknown role 'nach Koblenz': {restriction=only_right_turn, type=restriction}. Relation ignored.
 Restriction relation 5702769 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 5719328 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_left_turn, type=restriction, restriction:bus:conditional=no_left_turn @ (05:00-24:00)}. Relation ignored.
 Restriction relation 5752654 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 5821651 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 5880210 has no member with role 'via': {restriction=no_right_turn, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 5880211 has no member with role 'via': {restriction=no_left_turn, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 6190970 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {type=restriction, except=bicycle;hgv;moped;motorcar;psv, restriction:hgv:trailer=only_straight_on}. Relation ignored.
 Restriction relation 6219283 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 6229297 has a member with an unknown role 'location_hint': {restriction:hgv=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 6521961 is missing a member with role 'from' or 'to': {restriction=no_straight_on, type=restriction}. Relation ignored
 Restriction relation 6534103 has a member with an unknown role 'location_hint': {restriction=no_left_turn, type=restriction}. Relation ignored.
 Restriction relation 7138038 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 7147255 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 7352080 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 7398762 has a 'restriction' tag, but also 'restriction:' tags: {restriction=only_right_turn, restriction:hgv=only_right_turn, note=Beschränkung gilt nur für LKW über 3,5 t (heavy goods vehicle - hgv), except=bicycle;bus;tourist_bus;emergency;motorcar;motorcycle;mofa;moped;taxi, type=restriction}. Relation ignored.
 Restriction relation 7562549 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 7619341 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {except=psv, restriction:bus=only_left_turn, type=restriction, restriction:tourist_bus=only_left_turn}. Relation ignored.
 Restriction relation 7642878 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_right_turn, restriction:hgv=no_right_turn, description=Diese Beschränkung gilt nur für LKW über 3,5t (hgv).  Relation ignored.
 Restriction relation 7747281 has no member with role 'via': {restriction=only_straight_on, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 7747282 has no member with role 'via': {restriction=only_straight_on, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 7822197 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 8117215 has a 'restriction' tag, but also 'restriction:' tags: {restriction=only_left_turn, restriction:hgv=only_left_turn, description=gilt nur für "Kraftfahrzeuge mit einer zulässigen Gesamtmasse über 3,5 t einschließlich ihrer Anhänger und Zugmaschinen, ausgenommen Personenkraftwagen und Kraftomnibusse", except=bicycle;bus;emergency;mofa;moped;motorcycle;motorcar;taxi, traffic_sign=DE:209-10,DE:1010-51, type=restriction}. Relation ignored.
 Restriction relation 8117243 has a 'restriction' tag, but also 'restriction:' tags: {restriction=only_straight_on, description=LKWs (bzw. alle Fahrzeuge) mit einer Länge von mehr als 10 Metern dürfen vom Bahnübergang kommend hier nicht in die Königstraße einbiegen., except=bicycle;moped;motorcar, restriction:conditional=only_straight_on @ (length>10 m), except:conditional=vehicle @ (length <= 10 m), type=restriction}. Relation ignored.
 Restriction relation 8152540 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_left_turn, note=Modelliert eine unechte Einbahnstraße mit Fahrrad frei, restriction:motor_vehicle=no_left_turn, except=bicycle, type=restriction}. Relation ignored.
 Restriction relation 8320620 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 8320621 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 8426594 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 8636495 has a member with an unknown role 'tr_source': {restriction=only_left_turn, type=restriction, except=psv;bicycle}. Relation ignored.
 Restriction relation 8636496 has a member with an unknown role 'tr_source': {restriction=no_right_turn, type=restriction, except=bus}. Relation ignored.
 Restriction relation 8656232 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 9282263 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 9351170 has a member with an unknown role 'location_hint': {restriction=no_entry, type=restriction}. Relation ignored.
 Restriction relation 9420246 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 9457172 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 9554688 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 9554689 has a member with an unknown role '': {restriction=only_right_turn, type=restriction}. Relation ignored.
 Restriction relation 9591736 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_straight_on, type=restriction, except=destination}. Relation ignored.
 Restriction relation 9591737 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_left_turn, type=restriction, except=destination}. Relation ignored.
 Restriction relation 9949439 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 10022842 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 10185562 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_entry, except=bicycle, restriction:conditional=none @ bicycle, type=restriction}. Relation ignored.
 Restriction relation 10219770 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 10253292 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 10399792 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction:hgv=no_right_turn, type=restriction}. Relation ignored.
 Restriction relation 10631276 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 10674112 has a 'restriction' tag, but also 'restriction:' tags: {restriction=only_straight_on, type=restriction, restriction:conditional=none @ delivery}. Relation ignored.
 Restriction relation 10715913 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction:hgv=no_straight_on, type=restriction}. Relation ignored.
 Restriction relation 10715914 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction:hgv=no_left_turn, type=restriction}. Relation ignored.
 Restriction relation 10715915 has multiple members with role 'to' even though it is not a 'no_exit' restriction: {restriction:hgv=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 10765320 has multiple members with role 'from' even though it is not a 'no_entry' restriction: {restriction:hgv=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 11082596 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11082597 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11082598 is missing a member with role 'from' or 'to': {restriction=no_straight_on, type=restriction}. Relation ignored
 Restriction relation 11082623 is missing a member with role 'from' or 'to': {restriction=no_straight_on, type=restriction}. Relation ignored
 Restriction relation 11082996 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11082997 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11082998 is missing a member with role 'from' or 'to': {restriction=no_straight_on, type=restriction}. Relation ignored
 Restriction relation 11083001 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11083002 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11083003 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11083004 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11083009 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11170337 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 11283424 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11332870 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11379476 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11379477 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 11650632 has a member with role 'to' and type 'NODE', but it should be of type 'way': {restriction=no_u_turn, type=restriction}. Relation ignored.
 Restriction relation 11723567 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 11723568 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 11770950 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 11783319 has no member with role 'via': {restriction=no_right_turn, type=restriction, note=Ist wirklich so ausgeschildert}. Relation ignored
 Restriction relation 11783320 has no member with role 'via': {restriction=no_right_turn, type=restriction, note=Ist wirklich so ausgeschildert}. Relation ignored
 Restriction relation 11788484 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 11856938 neither has a 'restriction' nor 'restriction:' tags: {type=restriction}. Relation ignored.
 Restriction relation 11856939 neither has a 'restriction' nor 'restriction:' tags: {type=restriction}. Relation ignored.
 Restriction relation 11856940 neither has a 'restriction' nor 'restriction:' tags: {type=restriction}. Relation ignored.
 Restriction relation 11856941 neither has a 'restriction' nor 'restriction:' tags: {type=restriction}. Relation ignored.
 Restriction relation 11940858 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 11973659 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 12117079 is missing a member with role 'from' or 'to': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 12117080 is missing a member with role 'from' or 'to': {restriction=no_straight_on, type=restriction}. Relation ignored
 Restriction relation 12376668 has a 'restriction' tag, but also 'restriction:' tags: {restriction=no_u_turn, restriction:hgv=only_left_turn, type=restriction}. Relation ignored.
 Restriction relation 12532031 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 12830797 has no member with role 'via': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 12895402 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 12895405 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 12997230 is missing a member with role 'from' or 'to': {restriction=no_entry, type=restriction}. Relation ignored
 Restriction relation 13049800 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 13070727 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 13454597 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13454598 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463694 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463695 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463696 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463697 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463698 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463699 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463700 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463701 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463702 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463703 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13463704 has an 'except', but no 'restriction' or 'restriction:conditional' tag: {restriction:hgv=no_entry, type=restriction, except=destination}. Relation ignored.
 Restriction relation 13567067 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13567068 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 13573355 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 13573356 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 13608518 is missing a member with role 'from' or 'to': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 13679537 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13679538 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13679539 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13764093 has no member with role 'via': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 13923818 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13923834 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 13940204 is missing a member with role 'from' or 'to': {restriction=only_right_turn, type=restriction}. Relation ignored
 Restriction relation 14020030 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction, except=bicycle}. Relation ignored
 Restriction relation 14057077 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 14329359 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 14411734 has a member with an unknown role '': {restriction=only_right_turn, type=restriction, except=bicycle}. Relation ignored.
 Restriction relation 14448499 is missing a member with role 'from' or 'to': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 14490173 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 14499678 has no member with role 'via': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 14499679 has no member with role 'via': {restriction=no_left_turn, type=restriction}. Relation ignored
 Restriction relation 14499680 has no member with role 'via': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 14499681 has no member with role 'via': {restriction=no_right_turn, type=restriction}. Relation ignored
 Restriction relation 14503064 has no member with role 'via': {name=Einfahrt verboten in verkehrsberuhigten Bereich, restriction=no_entry, except=bicycle, type=restriction}. Relation ignored
 Restriction relation 14522951 is missing a member with role 'from' or 'to': {restriction=no_u_turn, type=restriction}. Relation ignored
 Restriction relation 14539839 has a member with an unknown role '': {restriction=no_straight_on, type=restriction}. Relation ignored.
 Restriction relation 14551314 has a member with an unknown role '': {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 14600543 has a member with an unknown role '': {restriction=no_straight_on, type=restriction}. Relation ignored.
 Restriction relation 14611429 has a member with an unknown role '': {type=restriction, restriction:bicycle=no_left_turn}. Relation ignored.
 Restriction relation 14632144 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 14632145 has no member with role 'via': {restriction=only_straight_on, type=restriction}. Relation ignored
 Restriction relation 14671438 has a member with an unknown role '': {restriction=only_straight_on, type=restriction}. Relation ignored.
 Restriction relation 14703633 has a member with an unknown role '': {restriction=no_left_turn, type=restriction}. Relation ignored.

I checked some of them and almost all of them actually looked like they need to be fixed.


Not published on bower

Not published on bower - could ya publish this? Thanks!

I have published, I thought it is...
Please see https://github.com/epoberezkin/ajv-i18n#install
It could be easier to use with npm, if the bundle were published there (it's not at the moment). Using with browserify/webpack seems better though, as you can inlude only the languages you need, rather than loading all of them in a separate bundle.

Whats the expected way to use this?
If I pull it in with npm or bower ("ajv-i18n": "epoberezkin/ajv-i18n#^1.3.0") it still needs to be built with 'npm install && npm run bundle-all'.
At that point, it's been browserified, and I can use it in my project by doing a require('/localize/index'). Can you explain why the require doesnt follow the example require('ajv-i18n')?


(re-4451) Do not override main-namespace for pe builds

The ezbake pe profile is currently overriding the main-namespace
for the project.
This removes that variable definition, taking the default for the
project.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1145/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1159/


chore: update dependencies for react 18

📝 Description
Bumping all dependency versions to match React 18. Thanks to the brain @TimKolberger who thought about doing so :D
🚀 New behavior
Major bumps to React, Chakra and contentlayer. Smaller bumps for other dependencies.
💣 Is this a breaking change (Yes/No):
Yes
📝 Additional Information
Open todos:

[x] Fix component overview error with hydration -> edit: seems to onyl be happening on the dev server we can check this later.
[x] Update component types that have currently FC
[x] Check all pages and examples
[x] Fix contentlayer build errors (local build is doing fine)

Next steps

to make it less painful next time we should check some of our dependencies I didn't bump and bump them. Especially "@docsearch/react": "^1.0.0-alpha.27" latest beeing 3.0.0
See if we can simplify code base and reduce dependencies
remove babel ? There is no superjson support right now for swc but do we really need it

@TimKolberger I've added the changes :) Let me know if you think we are good to go here.


Fully-Backed Bids Spec

@SamDelaney I like it, well done! I think we are ready to finalize the whole spec.

@euonymos this should be ready for merge


Infobip Client does not work with Infobip

After upgrading to the latest Infobip client we're seeing errors returned from Infobip that seem to be caused by this commit: https://github.com/infobip/oneapi-python/commit/3e36f8e0b0718f4130cd14405bd57c7d2d6f66cc
While that commit brings oneapi-python up to OneApi standards, it seems to be breaking it's support of Infobip's smsmessaging/outbound endpoint:
https://oneapi.infobip.com/1/smsmessaging/outbound/xxxx/requests

Error:
{"clientCorrelator":null,"serviceException":{"messageId":"MISSING_PARAMETER","text":"Missing parameter","variables":["binary or message"],"additionalDescription":null},"variables":null}}

It seems this endpoint expects message to be at the top level and not nested under outboundSMSTextMessage.

The message element should be nested in a outboundSMSTextMessage as specified by GSMA. See http://www.gsma.com/oneapi/sms-restful-netapi/ for examples.

While that is true for the OneApi standard, it does not appear that Infobip supports message nested inside of outboundSMSTextMessage.
Their docs state that message should be top level and includes nothing about outboundSMSTextMessage.

message (string, optional): The text message content.,

We had no problems with the oneapi-python client until upgrading to a version that contained https://github.com/infobip/oneapi-python/commit/3e36f8e0b0718f4130cd14405bd57c7d2d6f66cc.
Once reverting as well as cURLing the endpoint manually with message nested and message not nested, it was clear that MISSING_PARAMETER was returned when nested.

@dentafrice You were right. messageshouldn't be nested inside of outboundSMSTextMessage  object. This problem was occurring when json was used as data format. After latest commit everything should be working like before mentioned pull request.
We deeply apologize because you had to wait for answer. If you have any other question please contact our support<EMAIL_ADDRESS>or post your question on github repository.
Best regards,
Milos


Add types of grazing management

Even though the current focus of AgrO appears to be crops, this is the correct ontology for grazing techniques.
I would model this as 'regulation of grazing', where grazing is from an ontology like NBO, and the management is done by humans. We would have different subtypes for different practices, e.g. so called holistic grazing.

Sounds right, similar to ecosystem processes vs ecosystem services in EnvO
and SDGIO, resp.
On 12 Dec 2016 17:06, "Chris Mungall"<EMAIL_ADDRESS>wrote:

Even though the current focus of AgrO appears to be crops, this is the
correct ontology for grazing techniques.
I would model this as 'regulation of grazing', where grazing is from an
ontology like NBO, and the management is done by humans. We would have
different subtypes for different practices, e.g. so called holistic grazing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AgriculturalSemantics/agro/issues/16, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACK7Mut35m-F856VTJKFlkYtNYGanzfNks5rHXEOgaJpZM4LKtvA
.

regulation of grazing has been added in agro-edit.owl as AGRO_00000426 with the data-cross-reference to AGROVOC : http://aims.fao.org/aos/agrovoc/c_3367.
 I think a processual representation is better for us, but just throwing this out as an option, cc @pbuttigieg


WARNING: linker:unused DT entry:  in android 5.1

I am facing this issue in Video Merging in android 5.1
WARNING: linker: /data/data/com.example.myvideo/files/ffmpeg: unused DT entry: type 0x6ffffffe arg 0x25bc

Warnings can be ignored most of the times. Does the command still execute properly?


Fix(sql-docs): Fixing the misaligned column and row in sql-docs

Fixes issue #116307
Fixed the misaligned column and row of Identification and Authentication IA2 in the FedRAMP section of microsoft.sql.md  file.

@Jak-MS  I don't work in the SQL docs repo so a writer for that team will need to review. This file was copied from azure-docs and the SQL writers should change the metadata to an author in their repo.

Looks good to me, thanks @Yash-Ambekar and @SiebeDev!
#sign-off


Missing Step in Movement Sequence

https://github.com/alpakadev/robot-ludens/blob/5c7092939e745c69379a6883da219f0dd8aa8d79/PythonScripts/Movement/robot_movement.py#L73-L77
Currently, there is a step missing in the movement sequence: Rising the Object above.
Without this additional movement, there is a risk of dropping or damaging the items on the way during the transfer process,

Also instead of a general POS_ABOVE_BOARD_COODINATES it should move above the position where the item will be placed


Question: Avalonia Port

Hi! Thanks for reporting this feature/bug/question!
Please keep / fill in the relevant info from this template so that we can help you as best as possible.
Type (choose one):

Question

NPE version: N/A
OS version: N/A
Installed from: N/A
Is it possible to have an Avalonia port of the Package Explorer? This would allow native running on Mac/Linux.

That's not very likely at this point, but there are Uno head's for Mac/Linux that need some work to finish up and contributions are welcome!

@clairernovotny @jeromelaban I will try it out.

Browsing for packages and opening them works. I could not navigate to dependency packages directly since NPE seems to be probing for packages in the wrong directory.

@clairernovotny In case I manage to fix the above, is this project open to PRs?

I have tried to find where NPE generates the file path for packages but could not find anything. For some reason it is trying to access "/packages" which does not exist on linux systems. NuGet packages are downloaded to "$HOME/.nuget/packages".

All PR's can be opened against this project.

@clairernovotny Do you know where the paths to linked dependencies get generated?

what dependencies, what paths, not sure what you're referring to?

@clairernovotny When in the package details screen there is a tab with a list of dependencies for each TFM. The dependencies are shown as Hyperlink Buttons. When I click on them NPE is trying to probe for packages in the wrong directory.

Those should be triggering the Select Package dialog by ID that's filtered to that package; it's not supposed to open another file directly.

Ok, I will look into the source code for the Select Package dialog to see where it probes for packages.

@clairernovotny I could not find the code I was looking for. However, I foudn out that the "/packages/*" paths are used by the WASM version of NPE. It looks like the GTK version is behaving as it were in a browser.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-suite-rbac-auth

prow/e2e-cluster_wide-auth.sh
f03e4fa3dfdbce0c8d0413f3627771c7a7568a75
link
/test e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Save process in Module instead of env.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1480  👈 (View in Graphite)
#1475
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 2, 8:41 PM EST: A user started a stack merge that includes this pull request via Graphite.


Improve functionality of the Metadata Server (WIP)

Desired features

Pub/Sub mechanism
Add / remove blocks
Update block location
Store the entire object as a fixed size.

ToDo

How to implement CoW?
How to enable sharing of blocks between different objects?
Should an append always create a new block?
How to handle contiguous objects for Python Serialization/Deserialization?

Data structure for each object
{
     blocks: [
          {
               range: str         # Denote start/end
               location: str      # s3://bucket/key or geds://host/block_id
          }
     ],
     backingStore: Optional[str]  # Indicate whether the file has an authoritative source (blocks can be empty)
     size: int,
     sealedSize: int   # Indicate caching
}

Interface

Create Bucket

createBucket(bucket: str)

Delete Bucket

deleteBucket(bucket: str)

List Buckets

listBuckets()

Create

create(bucket: str, key: str, size: int, sealedSize: int, blocks = None, backingStore = None)

Update

update(bucket: str, key: str, obj = ....)
blockAdd(bucket: str, key: str, blocks = ...., size: Optional[int])
blockRemove(bucket: str, key: str, blocks = ....)
seal(bucket: str, key: str, sealedSize: int) - Precondition: sealedSize > this.sealedSize

List

list(bucket: str, key: str, delimiter='/')

Delete

remove(bucket: str, key: str)
removePrefix(bucket: str, prefix: str)

Subscribe

subscribe(bucket: str)
subscribe(bucket: str, key: str) - Exact
subscribe(bucket: str, prefix: str) - Use pattern

Unsubscribe

unsubscribe(bucket: str)
unsubscribe(bucket: str, key: str) - Exact
unsubscribe(bucket: str, prefix: str) - Use pattern

huh?
Interface
Create Bucket
    createBucket(bucket: str)
Create Bucket
    deleteBucket(bucket: str)

Delete Bucket..?

I fixed it :)


Pod is not working in m1 chip system

Pod is not working in m1 chip system
I have project in intel system.now i want to use that project in m1 chip system but i am getting errors regarding this pod.Please help me

Can you tell me what errors you're seeing and how you generate them?


access to vm for deployment

wiki.tum.de -> seach 03 VPN
Use EduVPN

I try to describe the way that I got access to the VM:

You got a got a mail with a TUMonline-Pincode

Open the browser at  https://campus.tum.de/
Click on PIN-Code einlösen (Mitarbeitende)
Login with the credentials they sent you
Change the password in the webui

Login at https://tum.eduvpn.lrz.de/ with the username from the mail & the password that you set

Create and download a openvpn config file

Go to Einstellungen
Expand the "weiter" under "Erstellen"
Select MVN Split-Tunnel (Standard)
Give it a name
Click on "Erstellen und Herunterladen"

Add a openvpn script

It could look like this:
#!/bin/bash

# Connect to the TUM eduvpn
# For more details see: https://doku.lrz.de/pages/viewpage.action?pageId=87425299
sudo openvpn --verb 3 --config ${PATH_TO_CONFIG_FILE}

(with the path to the file that you downloaded right now).

Run the script

Try to access the VM

you can access it with root and the password that hugo shared by mail

ssh<EMAIL_ADDRESS>

Create your own account and put it into the docker & sudo group

adduser fancynewuser
adduser fancynewuser docker
adduser fancynewuser sudo

Optional: Switch user and upload your public key

# on the VM
su fancyuser
cd ~
mkdir .ssh

# on your local computer
scp ~/.ssh/id_rsa.pub fancyuser@<IP_ADDRESS>:/home/fancyuser/.ssh/authorized_keys

Further documentation:

https://doku.lrz.de/pages/viewpage.action?pageId=87425299

An alternative way to access:

Go to the following website: https://vm.lrz.de/
Click on "vSphere Client"
Log in with the credentials of the functional account I shared per email
The VM riesgos should be visible once you log in. Otherwise, you can search for it at the search bar on the top left, by typing "riesgos"
You should be able to launch the VM and log in as root (or any) user

Works great for me! Thanks a lot @nbrinckm and @HugoRosero !


Allow Setting filename and inmemory config options

This allows passing in filename or if null or empty then use appSettings.json.
For existing customers using appSettings.json when no filename is passed.
Anyone who want to use InMemory can call SettingsManager.CreateSettingsInMemory() which return same object that is returned by appSettings.json file.

This has now been merged (This was done manually as testing/exception handling was required)


No items added item to Inbox in Omnifocus

The extension is not working. I have just installed it in Firexfox and restarted Omnifocus and Firefox multipe time. Whenever I click on the button "Add to Omnifocus" no items are added to the Inbox in Omnifocus
For example, when I click on the button while I am on https://www.thetimes.co.uk/ I receive this messagen in the debug console:
OmniFocus.Added task “The Times & The Sunday Times” to OmniFocus. background.js:29:13
but I have no such task in Omnifocus and
I am using Omnifocus 3.9.1 (v144.4.0), Firefox 79.0 (64-Bit) and macOs Version 10.15.5

This might be the same problem as in #2. Try clicking on an omnifocus:// link somewhere, that should fix it.

I tried it again but found only two lines like these in the debug console:

Added task “Some title of some page” to OmniFocus. background.js:29:13
Changed to omnifocus:///add?name="some url encoded title"&note="some url encoded url"

But I could not click on the Omnifocus link. I had to copy the entire like to the clipboard and paste it into a new tab. Only the message pops up asking me if I want to open those omnifocus links with Omnifocus.
Now it seems to work. But I don't like the solution. I reckon most users the extension that run into the same problem won't raise an issues here but will simply the assume the extension is not working properly.

There’s a new release, v1.1.1, pending review by Mozilla, that should help this.


react key prop not working, still have "Each child in a list should have a unique "key" prop."

i need help plz ,
this is my attached code :
New Text Document.txt

This is react-native repo

Whatever you JSX you map needs an id. In this case, you are mapping the Loader as well which is missing the id.
It's better to map over your items only when loading is completed. That would uncomplicate things

thank you :)

@Majdewave Would you mind closing this issue if your issue is resolved?


Document recommended way for running tests

Fixes #3084.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 5c793a2 has been approved by alexcrichton

:hourglass: Testing commit 5c793a2 with merge 7f642f5...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing 7f642f583bf71796d3137df19f0316468aba5fc0 to master...


[AMHACK]UI is showing two "valid" message for in url validation

Description:
UI is showing two "valid" message for in url validation
Suggested Labels:
API creation
Suggested Assignees:
Affected Product Version:
WSO2 APIM 2.1.0
OS, DB, other environment details and versions:
OS-ubuntu14.04
DB-Mssql 14
Userstore-JDBC
20th Nov WUM updated Pack
Steps to reproduce:
Go to the implementation tab
Enter production and Sandbok url
Click on test button twice

You will be able to see two valid message for two clicks.(Attached a screenshot)
Expected results
It should be one valid message for any number of clicks.

fixed in https://github.com/wso2/carbon-apimgt/pull/4869


MCEdit doesn't open commands

Running Linux 16.04, no Mods and Minecraft 1.10, MCedit v<IP_ADDRESS>.
'Error during <function openCommands at 0x7fd879048050>: RuntimeError('maximum recursion depth exceeded',)> - I simply selected the command blocks and clicked CB Commands.
The issue was previously about it not starting, but that was fixed by updating Ubuntu.

Can you give us a screenshot of the entire console window?

Sorry, I have been having computer troubles recently, so all I have access to a windows machine. However, it seems to happen here as well!

Hmmm...
Looks like the code is calling itself endlessly.
We'll have a look to that :)

It's an issue with the CB Commands feature when ordering is "chain". Right click the CB Commands button and change the order to something other than "chain" I hope I'll fix it for the next release but I can't promise anything. If you can send us your map and tell us what coordinates you selected to cause this issue, it will help us find the issue and try to fix it.


Fix name parameter jsdoc type

Small fix for jsdoc type of name, which should be type string instead of type name

Deploy preview failed.
Built with commit 9f97324c953aed08afcd6999247fc08012d6aaa1
https://app.netlify.com/sites/react-boilerplate/deploys/5a386dd9a114771019485d50

Coverage remained the same at 100.0% when pulling 9f97324c953aed08afcd6999247fc08012d6aaa1 on mjbvz:fix-name-jsdoc into 96000340a3cffaccefa215d91daaa0f2927a2b93 on react-boilerplate:dev.

Coverage remained the same at 100.0% when pulling ae2e0dfdaf9e97f19ab580410cbe4bd246830632 on mjbvz:fix-name-jsdoc into 5fdf7a485ba83284219238fbde4b20a37702eae3 on react-boilerplate:dev.

LGTM. It is just a small jsdoc type fix i will merge it this without others approve. :v:
Thanks @mjbvz :)


Replitでdiscord-ext-uiがインストールできない

Replit: Updating package configuration
--> python3 -m poetry add discord-ext-ui
Using version ^2.1.2 for discord-ext-ui
Updating dependencies
Resolving dependencies...
SolverProblemError
The current project's Python requirement (>=3.8,<4.0) is not compatible with some of the required packages Python requirement:
- discord-ext-ui requires Python >=3.8.2, so it will not be satisfied for Python >=3.8,<3.8.2
Because no versions of discord-ext-ui match >2.1.2,<3.0.0
and discord-ext-ui (2.1.2) requires Python >=3.8.2, discord-ext-ui is forbidden.
So, because repl-python3-stetusplay-61 depends on discord-ext-ui (^2.1.2), version solving failed.
at /opt/virtualenvs/python3/lib/python3.8/site-packages/poetry/puzzle/solver.py:241 in _solve
237│             packages = result.packages
238│         except OverrideNeeded as e:
239│             return self.solve_in_compatibility_mode(e.overrides, use_latest=use_latest)
240│         except SolveFailure as e:
→ 241│             raise SolverProblemError(e)
242│
243│         results = dict(
244│             depth_first_search(
245│                 PackageNode(self._package, packages), aggregate_package_nodes
• Check your dependencies Python requirement: The Python requirement can be specified via the python or markers properties
For discord-ext-ui, a possible solution would be to set the `python` property to ">=3.8.2,<4.0"

https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
https://python-poetry.org/docs/dependency-specification/#using-environment-markers

exit status 1
Replit: Package operation failed.
と出てdiscord-ext-uiがインストールできません

replitのPythonのバージョンの問題かと。
ここで言うことではない気がします。


Added Disney Plus Implementation

Description
Fixes #789
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

Screenshots

@Ayush7614 Please review

@gurjeetsinghvirdee Please review this. No Response from quite some time

Copied from here https://www.youtube.com/watch?v=ZeY9RicS2js&t=1s

Copied from here https://www.youtube.com/watch?v=ZeY9RicS2js&t=1s

But if a person have implemented it, how does that count for Plagiarism.
In that case, everyone should be booked for plagiarism for copying the tags and syntax from official documentation of that programming language.
I seriously didn't find this to be a justified action on this particular PR.

Everyone sees tutorials, takes some help, and implements the things. In today's scenario, clone of everything is either available on Youtube as a video or in form of code in some Github repository. Then how does is it fair to count this PR for Plagiarism ?

then mention that you take reference how could we know that you are taking reference


Upgrade axum integration to Axum 0.2.0

I'm not an experienced Rust developer yet, so this is mostly just some brute-force follow-the-compiler changes that I can build and test successfully and incorporate into a personal project with successful build and test. Please feel free to keep or discard anything you like, I just wanted to offer a starting point and volunteer to try to see it through with some guidance. I'll gladly follow any contributor guidelines you can point me to, as well.

I also referred to https://github.com/tokio-rs/axum/pull/234 for the trait bounds change.

Thank you for your PR👏, if you are done, please let me know.
There are examples for testing in the examples directory.

@sunli829 I've opened https://github.com/async-graphql/examples/pull/41 to address the CI failure. Other than potentially you or I updating the submodule rev, I think I'm done making changes pending any incoming feedback, so I'll take this PR out of draft status. Thanks for your attention!

Thank you for your excellent work! @shanesveller

Looks like CI is failing now?

He knows, It's not related: https://github.com/async-graphql/async-graphql/pull/615#issuecomment-909736947

I'm working on it.

Async-graphql-axum has been released. https://crates.io/crates/async-graphql-axum
Many thanks! @shanesveller 👏🏻


outsourcing

hey @Mrredstone5230 and @ireneybean i was looking for a way to outsource at least the special_pages like PV and Fuel. i think this is a great way. Especially since I actually have a lot of special pages on the todo list and so we can avoid a lot of "IFs".

I mean, that's a good idea... But I think Irene was sort of already working on it (take a look at ad9355f, very interesting stuff!)

I am, but this is still a good idea. Don't wait on me :-) i think this will fit in fine with my approach.


Data Load Error

Hello, I am trying to run the demo but the code fails on the model load, here is the last lines of the log:
I0422 05:05:37.127264 11607 net.cpp:274] Network initialization done.
I0422 05:05:37.197033 11607 upgrade_proto.cpp:66] Attempting to upgrade input file specified using deprecated input fields: colorization_release_v0.caffemodel
I0422 05:05:37.197067 11607 upgrade_proto.cpp:69] Successfully upgraded file specified using deprecated input fields.
W0422 05:05:37.197072 11607 upgrade_proto.cpp:71] Note that future Caffe releases will only support input layers and not input fields.
F0422 05:05:37.197129 11607 net.cpp:765] Check failed: target_blobs.size() == source_layer.blobs_size() (5 vs. 3) Incompatible number of blobs for layer conv1_2norm

Here is the full log output if you need it. Gist
I am using the latest Caffe with cuDNNv5 on Ubuntu 16.04. Also, my Caffe is compiled from this PR for the cuDNNv5 support.
Update: I suppose that PR adds some breaking changes in the batch normalization (now, cuDNN do that) that raise this issue.
Update #2: I think, the issue in this change.

Thanks for your interest in the code! Unfortunately, I'm not too sure what's going on. Perhaps consult with the caffe-users group for help.


[FLOC-2671] Release/flocker 1.1.0dev1

Waiting for tests to pass due to "no space" problem.
There is one error with the link check:
reference/api.rst:1: [redirected with Found] https://clusterhq.atlassian.net/browse/FLOC-2044 to https://clusterhq.atlassian.net/login?dest-url=%2Fbrowse%2FFLOC-2044&permission-violation=true

This is a JIRA link redirecting to the login page so will happen with all JIRA links. Does the filter need to be updated?

@zubron Is that a local error? The docs build is successful on Buildbot. Also, you can write :issue:`2044` and it'll work and be neater.

The NEWS file and the release notes changes are suitable (with one optional comment).

The review process says:

The build should be passing to the team's satisfaction.

Usually with a dev release some tests don't really matter - we are testing the release process and not the software (most of the time), but in this case the packages are not being built, so the release scripts will fail. This release should therefore, unfortunately, be blocked on the build issues being fixed. Or if rebuilding works, do that and resubmit.

I recon that this should be closed and perhaps we should do 1.1.0dev2. This highlights a release process problem - someone must remember in these failure cases to transfer the release notes / NEWS changes here to the next release. I'll leave what to do with this to you @zubron . Maybe try re-running the test suite but IIRC normal branches are merged with master before BuildBot runs the suite (removing some of the unrelated test failures) but release branches aren't.

Sure, I can close this and make sure the release notes are added to the 1.1.0dev2 release. The docs issue above should no longer be there as the link in question has been made available without a log in. There have been some changes made to the AMIs for building so hopefully we shouldn't run into issues caused by no disk space.


BrowserslistError: Unknown browser query android all

just flower the offical doc to use the create-nuxt-app to create new project
npx create-nuxt-app pc-server

then
cd pc-server
$ npm install
$ npm run dev

after this command, the nuxt occurs the errors

env:
npx ^6.9.0
node v10.8.0
npm ^6.9.0

This question is available on Nuxt community (#c9378)

I have the same issue - please reopen :)

Same here 👍

the same

the same

the same

it is a problem with caniuse-lite https://github.com/browserslist/browserslist/issues/382#issuecomment-503009048

please use +1: reaction in the first comment instead of the same.

Quick fix for now is to add the following to your package.json to revert to an older caniuse-lite version:
  "resolutions": {
    "caniuse-lite": "1.0.30000974"
  },

Only works with yarn, not with npm

Only works with yarn, not with npm if it work in yarn, for npm can try use https://www.npmjs.com/package/npm-force-resolutions

same problem. need to fix

https://github.com/browserslist/browserslist/issues/382#issuecomment-503019002

Try to update Browserlist, it works with 2.8.1

As mentioned by @albertleigh the issue is with the caniuse-lite new version, resolutions fix the issue with yarn and npm install<EMAIL_ADDRESS>--save-dev --save-exact fixes the issue with NPM for now.

We made a dirty fix in Browserslist 4.6.3 to fix the problem:
https://twitter.com/Browserslist/status/1140911400304467968

<EMAIL_ADDRESS>released which prevents lots of warnings in the console:

Does this issue affect the project? How to solve it? My God～！

刚开始使用create-nuxt-app来创建新项目的官方文档
npx create-nuxt-app pc-server

然后
cd pc-server
$ npm安装
$ npm run dev

在此命令之后，nuxt发生错误

env： npx
^ 6.9.0
node v10.8.0
npm ^ 6.9.0
这个问题可在Nuxt社区获得（＃c9378）

The same situation of my project. I don’t know if it will affect the projects that have been deployed online. Only God knows.

just flower the offical doc to use the create-nuxt-app to create new project
npx create-nuxt-app pc-server

then
cd pc-server
$ npm install
$ npm run dev

after this command, the nuxt occurs the errors

env:
npx ^6.9.0
node v10.8.0
npm ^6.9.0
This question is available on Nuxt community (#c9378)

The same situation of my project. I don’t know if it will affect the projects that have been deployed online. Only God knows.

We will have warning until postcss-preset-env will not be fixed properly inside. We need just wait.

@DereKEasH use standard nuxt server yarn nuxt dev instead :) Custom server does not register consola wrapper

@DereKEasH use standard nuxt server yarn nuxt dev instead :) Custom server does not register consola wrapper

I used npm to create the project, but this has not happened in the past few days.

You don't have to downgrade anymore. The latest versions of caniuse-lite now also does no longer show the error. Installing it manually is still required, but you can use the latest version.
Yarn (tested):
Add to package.json.
"resolutions": {
  "caniuse-lite": "1.0.30000977"
}

npm (untested):
Install directly
npm install<EMAIL_ADDRESS>--save-dev --save-exact

Pinning version in package.json (as of browser list maintainer also suggested) is not a good idea. Would be better to recreate lock-file or use yarn/npm upgrade.
Closing as regression is fixed.


colorpicker uses too much memory

Microsoft PowerToys version
0.66.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
ColorPicker
Steps to reproduce
None , just start the PowerToys.
✔ Expected Behavior
In the past version , when ColorPicker runs in the background , it ONLY uses about 1MB memory.
❌ Actual Behavior
When the ColorPicker isn't being used , the process "PowerToys.ColorPickerUI.exe" takes up more than 100MB memory , and sometime even up to more than 200MB.A UI shouldn't take up so much memory when ideling.
Other Software
No response

Seeing the same issue. Running Colorpicker at 215.8 MB.
Win11 Powertoys 0.66.0

Duping to most recent post for this issue. /dup https://github.com/microsoft/PowerToys/issues/33315


fix(primitives): fix polygon gizmo rendering bug

This is just a minor fix extracted from #11697
A logic error. We tried to close the polygon shape, if the user specifies an
unclosed polygon. The closing linestring previously didn't close the polygon
though, but instead added a zero length line at the last coordinate.

CI error seems unrelated and exists in other PRs too

CI please :( Seems to all be failure to fetch networking flakiness.


Question about Plugin Description

Dear Konga team
This is great UI for Kong and I love it.
I extended request-transformer plugin and It works very well.
However, I want to add description in prepath filed but I couldn't find it where i can set the description.
Please see the attached image.

Thank you.

@kakarooky , thanks for the notice. I will document it. Meanwhile you can check the plugin docs at https://docs.konghq.com/plugins/request-transformer/ so that you know what's what.

@pantsel, Thank you for your reply.
My question is that I want to add my own description in Konga (UI).

Ok, now I get it.
No you cannot do that unless you mess with the source code.
Here is the place you can mess with:
https://github.com/pantsel/konga/blob/853518f0675623db61067db93a6d4396a0f98628/assets/js/app/core/services/KongPluginsService.js#L826

@pantsel
Thank you ^^


Is there anybody using fastselect ? and share knowledge here

Is there anybody using fastselect ? and share knowledge here
many question not answered here

Not many people using it. However, It looks like a good plugin.

I've started using it for a new project, impressed so far, but I'm just having an issue with the placeholder text, in that it always defaults to the first option (/)(;,,;)(/)

@Latchy I'm having that same issue as well with the placeholder text. Were you able to find a solution?

@Latchy , I did a little more digging and I found a solution.
The issue is that the fastselect script searches the select options for one with the attribute "selected: true" (line 120 in fastselect.js). By default, this option is set to the first option in a list that's not disabled. In a non-fastselect situation, you could do the trick of adding "disabled selected" to the select option on top, but with fastselect that doesn't help since it seems to ignore the "disabled" status when it generates disabled options as a "fstResultItem".
So, to bypass this I had to change the value of the select element to an empty string prior to fastselect running.
For my situation, the code looked like this:
$("#projectList").val(""); // clear value selected by default to make way for placeholder

$("#projectList").fastselect({
    placeholder: 'Select a Project',
    searchPlaceholder: 'Search...'
});

I hope that helps. Let me know if you have any questions.

@pezmo
Hi there, thanks for the update.
I moved to using the select2 plugin, hacked the CSS and found it to work just as well, if not better?
Though, I tried so many plugins I forgot the issues I was having with either at the time entirely.