Allow supplying ExecutorService for SystemWriteSide

The recent change done in https://github.com/SpineEventEngine/core-java/commit/174cc7cd437e763a41741e4d0954303bff6c2c39 introduced an issue in AppEngine standard environments for event handlers for system events that use any AppEngine-specific APIs (com.google.appengine.api.*).
The reason is that AppEngine still restricts usage of the APIs from threads created with new producing e.g. the following exceptions for TaskQueue API:
com.google.apphosting.api.ApiProxy$CallNotFoundException: Can't make API call taskqueue.BulkAdd in a thread that is neither the original request thread nor a thread created by ThreadManager

But, there still is a way to benefit from the parallel execution and use AppEngine Standard: create an ExecutorService with the AppEngine's ThreadFactory.
Workaround
The currently applied workaround is to disable parallel posting using bounded context's system features configuration:
context
    .systemFeatures()
    .disableParallelPosting();

Spent another couple of hours debugging the issue related to the usage of the default fork-join pool in the App Engine environment.

Spent couple more hours resolving issues related to the usage of parallel delivery by default.
In one of our projects, we rely on the usage of the same thread for deliveries. And during upgrade to a newer version of the framework System deliveries started to fail, cause they are by default delivered from different threads.


fix: floor price and count not show in search suggestion

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #7059
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[x] I've tested it at landing page search box
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Ecosystem Telegram?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Copilot Summary

🤖 Generated by Copilot at 7cec571
Added initialCollectionStats object to collectionWithImages object in SearchSuggestion.vue to enable async fetching and displaying of collection statistics in search suggestions.

🤖 Generated by Copilot at 7cec571

initialStats set
Async fetch from blockchain
Loading in winter

@newraina thank you for properly checking and fixing it.
seems that i had stuff on my cache and it did load properly for me first time i've tried, but not the second one hehe.


HADOOP-17471. ABFS to collect IOStatistics

Tested by: mvn -T 16 -Dparallel-tests=abfs clean verify
Region: East US
[INFO] Results:
[INFO]
[INFO] Tests run: 95, Failures: 0, Errors: 0, Skipped: 0

[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testCheckAccessForNonExistentFile »  Unexp...
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionALL:293->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionEXECUTE:218->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionNONE:204->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionREAD:233->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionREADEXECUTE:263->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionWRITE:248->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[ERROR]   ITestAzureBlobFileSystemCheckAccess.testFsActionWRITEEXECUTE:278->checkPrerequisites:306->setTestUserFs:88->checkIfConfigIsSet:319 » IllegalArgument
[INFO]
[ERROR] Tests run: 512, Failures: 0, Errors: 8, Skipped: 67

Illegal argument due to not using oauth config for these tests.
[INFO] Results:
[INFO]
[WARNING] Tests run: 256, Failures: 0, Errors: 0, Skipped: 77

Need to remove DurationTrackers from streams, since now I am collecting them from AbfsRestOperation.

Looks great!
My main production suggestion is to make the counters a DurationTrackerFactory, giving us the option of feeding it in to anything we add in Hadoop common &c to take one.
test code: can you use assertThatStatisticMean() for your stats asserts -and if not, are changes needed?

Extended AbfsCounters.java interface with DurationTrackerFactory.java, and converted the try-with-resources DurationTracking into
try {
      IOStatisticsBinding.trackDurationOfInvocation(abfsCounters,
          AbfsStatistic.getStatNameFromHttpCall(method),
          () -> completeExecute());
    } catch (IOException e) {
      throw new RuntimeException("Error while tracking Duration of an "
          + "AbfsRestOperation call", e);
    }

in the execute() method of AbfsRestOperation.java class, but I am facing this exception now:
java.lang.RuntimeException: Error while tracking Duration of an AbfsRestOperation call

	at org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.execute(AbfsRestOperation.java:192)
	at org.apache.hadoop.fs.azurebfs.services.AbfsClient.getAclStatus(AbfsClient.java:767)
	at org.apache.hadoop.fs.azurebfs.services.AbfsClient.getAclStatus(AbfsClient.java:749)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.getIsNamespaceEnabled(AzureBlobFileSystemStore.java:295)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.getFileStatus(AzureBlobFileSystemStore.java:786)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.getFileStatus(AzureBlobFileSystem.java:506)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.tryGetFileStatus(AzureBlobFileSystem.java:1035)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.initialize(AzureBlobFileSystem.java:135)
	at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3460)
	at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:172)
	at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3565)
	at org.apache.hadoop.fs.FileSystem$Cache.getUnique(FileSystem.java:3518)
	at org.apache.hadoop.fs.FileSystem.newInstance(FileSystem.java:592)
	at org.apache.hadoop.fs.FileSystem.newInstance(FileSystem.java:604)
	at org.apache.hadoop.fs.azurebfs.AbstractAbfsIntegrationTest.createFileSystem(AbstractAbfsIntegrationTest.java:271)
	at org.apache.hadoop.fs.azurebfs.AbstractAbfsIntegrationTest.setup(AbstractAbfsIntegrationTest.java:146)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:748)
Caused by: Operation failed: "The specified filesystem does not exist.", 404, HEAD, https://abfstorageacc.dfs.core.windows.net/abfs-testcontainer-72fd54ec-fe7b-42bc-a21c-61a175de9286/?upn=false&action=getAccessControl&timeout=90
	at org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.completeExecute(AbfsRestOperation.java:225)
	at org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.lambda$execute$0(AbfsRestOperation.java:190)
	at org.apache.hadoop.fs.statistics.impl.IOStatisticsBinding.trackDurationOfInvocation(IOStatisticsBinding.java:454)
	at org.apache.hadoop.fs.azurebfs.services.AbfsRestOperation.execute(AbfsRestOperation.java:188)
	... 29 more

Requests seem to return 404 with FileSystem not found exception. Tried to debug didn't get much info with that as well. Have you faced this issue before with DurationTrackingFactory @steveloughran ?

My mistake. I was translating IOException into RuntimeException when it was expected to throw IOException while setup.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 6 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 36s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m  9s

trunk passed

+1 :green_heart:
compile
22m 38s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
19m 18s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
4m  1s

trunk passed

+1 :green_heart:
mvnsite
2m  9s

trunk passed

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m  4s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
3m 24s

trunk passed

+1 :green_heart:
shadedclient
16m 47s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 23s

the patch passed

+1 :green_heart:
compile
21m 55s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 55s

the patch passed

+1 :green_heart:
compile
19m 16s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
19m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  2s

the patch passed

+1 :green_heart:
mvnsite
2m 10s

the patch passed

+1 :green_heart:
javadoc
1m 33s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m  3s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
3m 47s

the patch passed

+1 :green_heart:
shadedclient
17m  5s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 36s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m  2s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

208m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2731

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 8b5358ce85a7 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 16d11277eeb86d0dbe6a423f9464f7e09227bf93

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/5/testReport/

Max. process+thread count
1274 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-azure U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

+1, merging. Thanks!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 6 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 38s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 22s

trunk passed

+1 :green_heart:
compile
21m 35s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
17m 58s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
3m 52s

trunk passed

+1 :green_heart:
mvnsite
2m 21s

trunk passed

+1 :green_heart:
javadoc
1m 48s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m 16s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
3m 31s

trunk passed

+1 :green_heart:
shadedclient
14m 22s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 21s

the patch passed

+1 :green_heart:
compile
20m  4s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
20m  4s

the patch passed

+1 :green_heart:
compile
18m  5s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
18m  5s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 44s

the patch passed

+1 :green_heart:
mvnsite
2m 21s

the patch passed

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m 16s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
3m 54s

the patch passed

+1 :green_heart:
shadedclient
14m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 26s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 12s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 57s

The patch does not generate ASF License warnings.

197m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2731

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 22858ad1a3f8 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 665a0af1fae0fb664a9cbc088bced0a30bdb4d45

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/6/testReport/

Max. process+thread count
3158 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-azure U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2731/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Uncaught ReferenceError: Cannot access 'WEBPACK_DEFAULT_EXPORT' before initialization

Bug report
I saw the issue https://github.com/webpack/webpack/issues/13411. This talks about the circular dependencies.
But in my case the only change is webpack upgrade from 4 to 5.

webpack version:  5.40.0
Node.js version: v14.17.2
Operating System: windows OS

Please do not ignore the issue template, fix it and I will reopen

Fill out all fields from https://github.com/webpack/webpack/issues/new?assignees=&labels=&template=Bug_report.md

But in 99% cases you have circular dependencies

I can see a difference in the file generated before and after upgrade from v4 to v5.

__webpack_require__.d(__webpack_exports__, {     /* harmony export */     "default": ()=>(__WEBPACK_DEFAULT_EXPORT__)/* harmony export */ });
This is the extra line of code getting generated and is causing the issue.

Because you have circular deps

how can you identify circular dependencies. any suggestions ?

You can try https://github.com/aackerman/circular-dependency-plugin


Support for service resources using virtual private endpoints, public access, and service-to-service controls

Original title:
Support of Services as Communicating Endpoints via VPC Endpoints (a.k.a. Virtual Private Endpoints)

Support communicating across VPCs using Virtual Private Endpoints. Initially, support this in the same cloud across different regions. At the second stage, support this across clouds.
Detailed proposition is here.

Triage: Made some updates to the title to use this issue to track general support for PaaS resources in Paraglider, within and across clouds.

Some minor feedback on the one pager:

I agree we should tackle this on Paraglider and I like the general approach.
I would prefer us to adopt the term PaaS resources instead of services when we talk/think about this. On one hand, "services" is a bit too overloaded and the items that we want customers to be able to connect to using Paraglider are not the services themselves but the individual instances, such as a cloud database server, a cloud storage account, or a cloud AI services account. I find that the common word of "resources" makes sense because it provides conceptual unification: From the perspective of Paraglider/connectivity intent, they are just resources in the same way that VMs and K9s clusters are resources.
For both K8s clusters and VMs we have the same createResource API, so maybe we can get away on API and CLI with keeping only minimal differences and just infer what needs to happen under the hood from the resource type rather than requiring users to differentiate.
Besides providing private connectivity via virtual private endpoints, I think setting up PaaS resources with public connectivity (and firewall rules to control that traffic) or both private and public should be in scope.
I know from working on related technologies that supporting controls for PaaS services doesn't stop at the private endpoint but also requires controls for PaaS-to-PaaS communication.
Technologies such as VPC service controls offer uniform (within cloud) solutions for (4) and (5). I think it would be good to keep this in picture for Paraglider, at least for the clouds that have a way to express it.

Thanks for the feedback.

Great!
I see the value of a unifying "resource" concept and I actually thought about service as another type of resource. I don't think "PaaS resources" captures it, because (1) people often debate what cloud services are in terms of IaaS, PaaS, and SaaS. And VPC Endpoint (i.e., VPE) are used in all three of these contexts, because the unifying theme is "as-a-Service". To exemplify:

IaaS context: instead of connecting a Consumer instance (say, a VM) to an individual Producer instance (say, a VM), one uses LB at the Producer side as a front-end and Producer VM  is a back-end. This is useful when you need migrate a VM, create a horizontal auto-scaling group, take a VM off for maintenance swapping it by a another one transparently to Consumer, and allow local IP address space that can overlap with that of the Consumer. In a private case there is just LB and a single VM instance registered with it.
PaaS context: is what you write
SaaS: one uses VPC Endpoints also in the SaaS context (see: https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-saas.html)

In all three cases, there is the same underlying structure: a frontend (LB) and (possibly a number) of backend instances. "Service" captures exactly this structure.
The value proposition of the VPC Endpoint is that it is not just a private endpoint address, but a fully managed network with all the good properties mentioned in the design note
I think that down the road Paraglider needs to support all three use cases to merge seamlessly with the ecosystem.
(a) VPE for IaaS use case: Pros: see above; Cons: additional cost for LB, which is not warranted if you are not connecting an auto-scaling group, but indeed a single VM. However, if you want control over the underlay in all circumstances, you might wish to pay the cost of LB even when connecting two individual VM instances.
(b) VPE for PaaS use case: pros, no cons(?)
(c) VPE for SaaS use case: the same.
The beauty of using it across the board when you need control over underlay and want the cloud provider manage the connectivity, is that VPE is exactly the same API in all three UCs.

I agree. It would be good to keep the changes to the minimum and I think that for the use cases (b) and (c) above, this is entirely possible. However, in the case of connecting a resource instance to an auto-scaling group of VMs as described above, I currently do not see how you can preserve the current  createResource API that currently simply unmarshals JSON stanza and applies it as-is to a respective cloud. The problem is that in this case, we need a composition capability that would execute a mini-flow of creating a few resources: VM, LB, autoscaling group, and configuring them. But this might be a natural and even nice extensions so that the plugin is execution part of the flow "by delegation" resulting in a hierarchical structure.

Agree, but given what I wrote above, I would rather call them "service resources" :)) that can be accessed privately or publicly. It would be a matter of the connectivity rules that you set.

This is true, but then we need to decide what is the Paraglider's scope in the short term, medium term, and long term and what are specific PaaS resources that you want to interconnect. E.g., if this is about K8s to K8s cluster interconnectivity then it's a whole bunch of work on top of VPE. Think ClusterLink, Skupper, Istio. IMHO, they all can leverage private connectivity offered by VPE, but they also do their own things w.r.t. networking on top of the provider network. Makes sense?

Are VPC Servce Controls - like offering also provided in AWS and Azure? This is very interesting. In GCP, VPC Service Control is already integrated with Google Private Access, which is the Google name for the VPE functionality: https://cloud.google.com/vpc-service-controls/docs/private-connectivity I think we definitely need to to take a look at this and if this is something supported universally, then this will make the value proposition even stronger.

@smcclure20 , @praveingk , what do you think?

@davidbreitgand, thanks for the writeup, and sorry I didn't catch up with it earlier. You make good points.
I will try to explain my point of view, hoping it will help address some conceptual or terminology gaps:
On Azure, private endpoints can be used in two ways:

To access cloud provider-owned PaaS resources that have built-in "private link" capabilities.
To access customer-owned private link services.

In my day-to-day, PaaS generally implies that there is a multi-tenant service running on the cloud provider's shared infrastructure. The unit of consumption is a resource, but generally, that resource is not associated with a unique customer-usable IP address unless they use a private endpointto connect a virtual network to it.
This contrasts with my use customary of the term "IaaS resource" to describe customer-owned compute resources that are simply and directly connected to a customer-owned virtual network.
My knowledge of private link services (2 above) is limited, but I believe on Azure, private link services would be used in both the scenario you describe as private endpoints to IaaS and private endpoints to SaaS. The main difference is that in a SaaS offering, the private link service belongs to a different tenant who built it for consumption by other customers on the same cloud.
Although I see the commonality between (1) and (2) (i.e., they both use private endpoints) and would be happy to have Paraglider leverage that commonality to get "more bang for the buck," I am simply having a hard time seeing how.
For (1), my main focus is on solving what I see as an impedance mismatch between "IaaS" and "PaaS" that forces customers to deal with too many moving parts to achieve otherwise simple intent. For example, "my application on 'vm1' needs access to my database 'sql2' and my cloud storage 'blob3'" should be easily expressed in Paraglider. This maps directly to the scenario in which you would use private endpoints with PaaS resources. In these scenarios, the existence of a load balancer and the backend architecture is already abstracted away by the cloud platform, and I would love to see Paraglider also abstract away the usage of private endpoints.
Although I hope that Paraglider can also be used model the customer-owned private link service case (2 above), I don't see a similar opportunity to abstract away much of the complexity: If a customer wants to use Paraglider to define their service, I expect them to need #274 to model the load balancer explicitly and other Paraglider functionality to model the topology of their backend. The opportunity seems to be in specifying that this entire thing should be "packaged" as a service and that access to it should happen without going through the internet. Will this require Paraglider customers to explicitly add private endpoints as a network function? I don't know. It would be good to brainstorm or hear how you imagine the Paraglider story for it looking.
Regarding GCP's VPC service controls, I mentioned this because the intent often also involves PaaS-to-PaaS: "my application on 'vm1' needs access to my database 'sql2', and both my application on 'vm1' and my database 'sql2' need to access my cloud storage 'blob3'." I told @smcclure20 that although we might initially not support this (e.g., only support "IaaS-to-IaaS", "IaaS-to-PaaS", but not "PaaS-to-PaaS", always using these terms in the sense I explained above), it feels quirky to not allow certain combinations in rules. Also, what is the defined behavior when you can't specify PaaS-to-PaaS controls? Should 'sql2' and 'blob3' be able to communicate or be isolated by default? We can talk in person about options here. I am not aware of what AWS offers on this.

Thanks for the discussion on this! I will try to quickly summarize how I see this issue and how Paraglider should tackle it.

PaaS resources (or whatever we would like to call them :) ). The defining feature of these that (regardless of their name) delineates them from other resources are their multitenancy. Using this as the definition, I think there are only two interesting sub groups: public and private. For public multitenant services, Paraglider can use these today (barring maybe some additions like using a FQDN in rules and resources having public IPs). You just add a permit list rule allowing traffic to the service from your private endpoint and the connection will work. The more interesting part is when they are private. And how these services are exposed privately varies greatly across clouds. But the minimal requirement that Paraglider needs is true regardless of the implementation: the service is reachable via a private IP connected to your virtual network. I think, at least as a first cut, everything beyond this can be hidden from the user. Now, I do think there are interesting questions about how to integrate more tightly with these private link-like services and the policy they expose. But, we are then moving increasingly into the application layer, which Paraglider does not necessarily have to do. As we've discussed in other design meetings, I think it is okay if each cloud takes its own stance on where this line is drawn for Paraglider.

In the above discussion, I saw some mention of services created by the tenant. These fall into a different category for more than the PaaS resources for the reasons given above. I agree that the CreateResource operation today would not immediately work for such services. But, I tend to think about this more in alignment with what we proposed in the paper. We can (and do intend to) support in-network functions like load balancers. Then, all that's left is to support VM scale sets and expose an API to connect the load balancer to the VMs (which we proposed in the paper and have ideas for how to do in this new implementation). I don't see a strong need to immediately jump to exposing an API that just provisions an entire "service" for the user. In fact, I might argue that is outside the scope of Paraglider, which should only do the networking side. But, I could see a longer-term goal where we have some nice API on top that uses all the steps I just mentioned to create a basic setup for you.

Paas to Paas connectivity. This one is far less clear to me, even though I do understand it is a problem. I think I need to better understand what the status quo is on this front before proposing what Paraglider's role in it is.

Updating the thread with slides from our TSC meeting today: https://docs.google.com/presentation/d/1UOTN5ONsOdcPaS_g_FTNbYKclwVMRbEuxb3pr61PXTQ/edit?usp=sharing

@smcclure20 would it make sense to split this issue into multiple subtasks so we can mark some as done soon and move others to backlog?

Yeah, we should create one for each cloud, especially since this is partially implemented already.


Missing installation dependency for Linux

This is needed to be able to run on Linux (Ubuntu 16.04)
sudo apt install gir1.2-webkit-3.0

or it will fail with
/home/me/.local/lib/python2.7/site-packages/application/server/static/
WARNING:webview.qt:PyQt4 is not found
WARNING:webview.qt:PyQt5 is not found
WARNING:webview:QT not found
/home/me/.local/lib/python2.7/site-packages/webview/gtk.py:15: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk as gtk
WARNING:webview.gtk:PyGObject is not found
Traceback (most recent call last):
  File "/home/me/.local/lib/python2.7/site-packages/webview/gtk.py", line 17, in <module>
    from gi.repository import WebKit as webkit
ImportError: cannot import name WebKit
Traceback (most recent call last):
  File "/home/me/.local/bin/hogwatch", line 24, in <module>
    window('hogwatch','http://<IP_ADDRESS>:6432/index.html')
  File "/home/me/.local/lib/python2.7/site-packages/application/view/window.py", line 5, in window
    webview.create_window(title,location, resizable=True,width=480,height=720);
  File "/home/me/.local/lib/python2.7/site-packages/webview/__init__.py", line 94, in create_window
    gui.create_window(_make_unicode(title), _transform_url(url), width, height, resizable, fullscreen, min_size)
  File "/home/me/.local/lib/python2.7/site-packages/webview/gtk.py", line 116, in create_window
    browser = BrowserView(title, url, width, height, resizable, fullscreen, min_size)
  File "/home/me/.local/lib/python2.7/site-packages/webview/gtk.py", line 51, in __init__
    webview = webkit.WebView()
NameError: global name 'webkit' is not defined

You might want to add that to the README. I also installed sudo apt install python-webkit but I'm not sure it's needed.

I needed python-gi as well, in a clean Xubuntu 16.04 VM. It still had other issues though, while open in windowed mode (icons/graphics were not displayed) so I ended up just using it from the browser.

Thanks. I have linked this issue in the readme and will report it to pywebview's maintainer.


Change paths from absolute to relative

This change allows to use the container with a reverse proxy in front with custom path.
Lets consider the following nginx reverse-proxy configuration:
location /dissect-tester/ {
            proxy_pass http://<IP_ADDRESS>:8002/;
        }

Without the change, static content is redirected to servername/static/* instead of servername/dissect-tester/static/*.
This prevents styles, images and scripts to load properly.
The change makes the webpage use relative path and operate normally.

@disaderp Thanks for the PR!


Option to disable filter

{
"url": "...",
"enabled": false (true by default)
}
This is so we can easily remove a filter from our profile, but only temporarily.

I like it. This makes sense to me I've already run into the situation where I had to add/remove filter that I just use for testing

Done


New Post: Lavamoat

idea: how to secure nextjs/trpc/create-t3-app with lavamoat?
These are the steps we need to integrate.

disable/allow dependency lifecycle scripts (eg. "postinstall") via @lavamoat/allow-scripts
run your server or build process in lavamoat-node
build your ui with LavaMoat for Browserify

In node20 there are now some experimental runtime permissions. You can limit the access to file reads/writes for the program as a whole.
Lavamoat is still more fine-grained here, as it allows package-specific rules. Also with the node20 features it will take a while until they are available in AWS to a broader audience.
Lavamoat still doesnt support webpack or esbuild, so I suppose this means I can only run it in the lavamoat runtime, for which I will create an example in a custom lambda runtime.


Support building on MacOS aarch64 devcontainer

Building Envoy on MacOS M1/2/3 fails with the bazel toolchain not supporting the aarch64 target in Devcontainers.
I'm opening this issue here, to track progress.

the issue here is actually the cc toolchain, i think we need to define a aarch64 version over here to start https://github.com/envoyproxy/envoy-build-tools/blob/main/toolchains/configs/linux/clang/cc/BUILD
im not going to dig into this one anymore right now though

Originally posted by @keith in https://github.com/envoyproxy/envoy/issues/23239#issuecomment-1332783412

FYI: https://github.com/envoyproxy/envoy/issues/23239#issuecomment-2089609237


NASCAR and Web Access Control

LDP Options and HEAD can return an Allowed-Methods header. It is not clear from the specs if this shows
a. the methods the agent who is accessing the resource with the credentials he has provided can see
b. if these are the methods the agent with the most privileges can use - ie what methods the resource CAN Allow.
• If a server interprets the spec as a. then a client that does not see a method will have to wonder if it would be able to get that method were it to authenticate.
• If a server interprets the spec as b then a client that gets 401ed on trying to use a mehtod will want to find out whether it is even worth its authenticating. Will I get access if I try one of my many credentials?
This is where we then hit the NASCAR problem. Unless the client reads the WAC file it won't know what types of credentials required to be able to act on the resource. So it would have to ask the user to try out all possible ways to authenticate, and none of them may actually be the right ones. This would be

very inconvenient for the user as he'd have to try logging in, in many different ways
a big source of privacy leaks, as the user would have to try many different credentials before being able to authenticate, and so give away more information about himself than needed.

There was an interesting thread on the Credentials CG, about the NASCAR problem for which we actually have a very useful answer with WAC. I gave an answer that showed how we can solve the problem:

initial detailed answer
email rectifying some typos in the original mail detailing the distinction between Authentication and Authorization

See wiki page https://github.com/solid/solid/wiki/Client-Authentication-Discovery

Closing issue. Discussion moved to:

solid/#61-all resources MUST have at least one "acl" Link relation
solid/#45-No way to find out if user is authorized to write to a container


standard deviation over one dimension of a chunked DataArray leads to NaN

What happened?
When computing the standard deviation over one dimension of a chunked DataArray, one may get NaNs.
What did you expect to happen?
We should not have any NaNs
Minimal Complete Verifiable Example
x = (np.random.randn(10,10) + 1j*np.random.randn(10,10))
da = xr.DataArray(x).chunk(dict(dim_0=3))

da.std("dim_0").compute() # NaN
da.compute().std("dim_0") # no NaNs

### MVCE confirmation

- [X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
- [X] Complete example — the example is self-contained, including all data and the text of any traceback.
- [X] Verifiable example — the example copy & pastes into an IPython prompt or [Binder notebook](https://mybinder.org/v2/gh/pydata/xarray/main?urlpath=lab/tree/doc/examples/blank_template.ipynb), returning the result.
- [X] New issue — a search of GitHub Issues suggests this is not a duplicate.

### Relevant log output

_No response_

### Anything else we need to know?


Update googleauth dependency

Allow the dependency to use the 0.7.x releases.

@landrito do you know if this version was pinned for any reason?
@blowmage I assume that you've already tested this with the cloud apis?

I remember no reason why it was pinned so strictly. Sorry! LGTM assuming some hand tests show nothing breaks.

Codecov Report

Merging #138 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #138   +/-   ##
=======================================
  Coverage   99.27%   99.27%
=======================================
  Files          19       19
  Lines        2058     2058
=======================================
  Hits         2043     2043
  Misses         15       15

Continue to review full report at Codecov.

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

@blowmage I assume that you've already tested this with the cloud apis?

Not yet. This PR is part of incorporating some new functionality released in the latest version of googleauth into the cloud gems.

@blowmage have you been able to test it with this updated auth version?

No, I have not. Isn't making the change and running this repo's existing CI sufficient?

That's sufficient to merge but I don't think the existing CI runs any real tests so I would like to verify before releasing it. Do you need one soon?

I've tested this against google-cloud-ruby with googleauth 0.7.1 and everything works as expected.

I noticed this PR was out of date. I have updated it to the latest master. Can someone take a look?

Thanks for verifying with google-cloud-ruby @blowmage! I'll merge it now.


One should be able to set negative numbers for required rating

I'm actually against this enhancement. There's no consensual opinion if negative rating should even be displayed.

But if they are then players with negative rating are theoretical unwanted
in any game... As it is always 0+
Am 17.01.2017 9:34 PM schrieb "Geosearchef"<EMAIL_ADDRESS>I'm actually against this enhancement. There's no consensual opinion if
negative rating should even be displayed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FAForever/downlords-faf-client/issues/474#issuecomment-273291334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATEgKW2COOW89CKqxyWQfyj9Epfj2_a1ks5rTSXRgaJpZM4Lj6dp
.

That's true, so there is a solution needed, I would suggest not displaying ratings below 0 (showing and treating them like they are 0), so that those players who often have a very large deviation due to loosing their first games have a chance to increase the rating again.

But that's probably a decision that goes beyond the client... One thing we
might also think about in this context is if payers with negative ranking
do also get a waring if the game is 0-(to) whatever.
Am 18.01.2017 10:50 PM schrieb "Geosearchef"<EMAIL_ADDRESS>
That's true, so there is a solution needed, I would suggest not displaying
ratings below 0 (showing and treating them like they are 0), so that those
players who often have a very large deviation due to loosing their first
games have a chance to increase the rating again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FAForever/downlords-faf-client/issues/474#issuecomment-273612790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATEgKaelYQNO6a4lRtDy8EvZ85Pc4MEDks5rToktgaJpZM4Lj6dp
.

Just had the same problem/question.

I see no advantage in not allowing negative numbers

well this needs server support


Update README.md

markup sucks...
fixed some list indentations

Update with a comment from @dralabeing that I need to follow up on, where to add some more timing analysis: Timing analysis is generally done at different stages- first time pre-layout after CTS, post-global-routing, after detailed routing and chip finishing. So this topic can be introduce sooner.


[5.1][ConstraintSystem] Improve @escaping parameter diagnostics

Detect difference in escapiness while matching function types
in the solver and record a fix that suggests to add @escaping
attribute where appropriate.
Also emit a tailored diagnostic when non-escaping parameter
type is used as a type of a generic parameter.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - e2634abfc3e60243ae0393b06868484e1db3708b

Build failed
Swift Test OS X Platform
Git Sha - e2634abfc3e60243ae0393b06868484e1db3708b

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - e2634abfc3e60243ae0393b06868484e1db3708b

Build failed
Swift Test Linux Platform
Git Sha - e2634abfc3e60243ae0393b06868484e1db3708b


Where are the problems over 1250?

Before you submit an question we recommend you to check out the DOCUMENT first.
You can also find more information in:

TROUBLESHOOTING
FAQ

💬 Questions and Help
After 1250. Check If It Is a Good Array
Where are the problems over 1250, such as 1252. Cells with Odd Values in a Matrix

I have a problem exactly like you. Your problem list got cached.
Try to remove this file and then refresh the list by clicking the icon.

rm ~/.lc/leetcode/cache/problems.json

location of the cache files in Windows (10): C:\Users\USERNAME.lc


live server not opening chrome

I look some settings file but i couldnnt figure it out.. live server works in visual studio code but doesnt work in browser

Hello!  I have a similar problem - the browser after starting Live Server does not open the file!  Did you find a solution?

I look some settings file but i couldnnt figure it out.. live server works in visual studio code but doesnt work in browser

Yes, I have the same thing!  I worked with Chrome when there was a problem with Live Server.  I changed all the settings in Live Server to Edge, installed Edge as the default browser on the computer, but Live Server continued to launch Chrome, which did not open the file.  I deleted Chrome from the computer, but Live Server still did not open Edge, and wrote that it could not find Chrome ... The problem has not been resolved ...

@OldIngvar, @roshansap -  Live Server will always use your system's default browser.
If you want to use a different browser, you have to tell it where it's located on your system.
To do so on Windows for example, do the following:
In VS Code:

File > Preferences > Settings
Now use this keyboard shortcut: Ctrl + shift + p
Select Preferences: Open Settings (JSON)
Do a search for the following property: "liveServer.settings.AdvanceCustomBrowserCmdLine"
If you have it, change the value of the property to "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe"
If you don't find it, create the property and value in the object like this:
"liveServer.settings.AdvanceCustomBrowserCmdLine": "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe"


WIP Fix #6690 'Bad token in signature' with @guvectorize where bad token is NUMBER

WIP Fix #6690
Currently it is not possible to use constants when defining the dimensions signature of a gufunc, i.e. nothing like "(x),(5)->(x,5)"
This PR enables tokenize.NUMBER as a valid token type in the signature parser, which is enough to propagate these signatures through numba.
Since numpy supports frozen dimensions (as far as I can tell its documented since version 1.16), this luckily just seems to work out of the box for sufficiently new numpy versions.
It's a fairly blunt solution for now:

No optimisation to the IR generation yet. It seems like frozen dimensions should technically allow exchanging some variables for constants, but I would need help with that.
Using numbers for describing the array dimensions currently still follows the same rules as with symbols. I.e. a constant output dimension must have previously been declared in one of the input arrays, too. I am not sure if numpy generally forsees gufuncs that do not follow this rule, and if it should be possible to do so (ex. "(n), (20)->(10)"). I can think of this being useful, but I don't know what behind the scenes implications a signature like this could have.

Useful links:
https://numpy.org/doc/stable/reference/c-api/generalized-ufuncs.html?highlight=generalized universal function api#details-of-signature

Thanks for labelling @esc
This is titled WIP since I am not certain whether the PR is sufficient in its current rudimentary form or if you would expect a more elaborate fix.
I would appreciate some comments on the current state from either you or @stuartarchibald or @sklam .
Cheers! :)

Hi :)
Sorry for being quiet on this for a while.
As far as I can tell it works on CPU single threaded and parallel targets (also covered by the tests).
Besides that vectorize seems to support the CUDA but not the ROC target.
I doubt that I would be able to implement the CUDA side myself without help, I had a look at it last week and was a bit overwhelmed :-P
So the best I could offer to do by myself at the moment is to block these signatures if the CUDA target is chosen, but that might of course introduce an annoying divergence between CPU and GPU usage.

Hello, I believe this PR is still worth it.

gpuci run tests

I've just merged main and resolved conflicts so this can have a test on gpuCI, to see if it breaks anything CUDA-related. The ROC target no longer matters, as it's been removed.

Since CUDA seems to be OK with this, I think it might as well be thought of as ready for review.


" Allow for floating windows #10121 " should be open because it wasn't implemented

https://github.com/microsoft/vscode/issues/10121 should be open as it is a very useful feature and is not yet implemented, i.e. Problems panel can't be moved to it's own window.

/duplicate of #193267


Bug: How to $compile transclude for tests?

I want to test behaviour with transcluded content.
I expect similar results in this cases
http://codepen.io/TrySound/pen/WwOaKa
But I get

  <app class="ng-isolate-scope">

      <app-title class="ng-scope">Title</app-title>

  </app>

and

<app class="ng-scope">

</app>

Am I doing something wrong?

Hm.. it works. Sorry. I just foget about $compile carrying.


undefined widget error on profile widgets page

So I noticed this issue using Firefox, I can't reproduce it in Chrome.
I get the following error in the js console:
TypeError: Gratipay.widgets is undefined

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

same

Seems to be not reproducible.


[V6] Fix v6 documentation

Information
For the hacktoberfest and to prepare the v6, you can easily find typo on this branch/PR:
https://github.com/TypedProject/tsed/pull/941/files
If you find typo, create branch from https://github.com/TypedProject/tsed/tree/v6-update-documentation, then create PR on
this branch. I'll merge it quickly :)
Pages can be reviewed

[x] Getting started
[x] Create your first controller
[x] Start from scratch
[x] Start with the CLI
[x] Migration guide
[ ] Models
[ ] Swagger
[ ] Serve files
[ ] Templating
[ ] Uploading files
[ ] Exceptions
[ ] Controllers
[ ] AWS

Acceptance criteria

[ ] Your PR start from the rc branch

Deployment starting to ephemeral!

Deployed to ephemeral!


Create a documentation on how to connect Arduino and Raspberry PI

Add clear documentation on how to connect Raspberry and Arduino

@williamtoll Migrated documentation #17


reactive => toRef => reactive chain leads to dev tools incorrectly saying ref value is undefined

Vue devtools version
6.5.0
Link to minimal reproduction
https://play.vuejs.org/#eNp9kjFPwzAQhf/KyQupFKWVKpbSVgLUAQZApaOXkF6KS2JbtlOqRv7vnB2SFgl1Svzue3fvErfsXuvs0CCbsbktjNAOLLpGL7kUtVbGQQsG88KJA6bg1BpL8FAaVcMN2W645LJQ0joolYLFwCZtEGbAGT04Az+668GP3BAYWyVUTHvmkjj9bRUssQNl24gaVeOSZASLJbRcQpiUdeM5I5QzIn0Kt5PJJJjm424z2okODmtd5Q7pBNDGmNHs/a8Qh50Pp6wX5uPBy1LmLIUtxS7bWyXp88UknBWq1qJC86qdoGU4m3UZQy2vKvX9HDVnGkx7vfjE4usffW+PQePszaBFc0DOhprLzQ5dV169v+CR3odirbZNRfSV4hqtqpqQscMeGrml2BdcTPsUL4GQu41dHR1K2y8VggbSR54zugyPV1Y/x51m0+ijX8T8D/VF0/g=
Steps to reproduce & screenshots
Observe the state of foo, bar and baz in the devtools. foo.foo will initially have the value "foo" and so will bar.value, but baz.bar will show as undefined, despite the fact that in the template they all show as "foo". After 5 seconds, we change the value to "bar", and this is reflected in the template and in the devtools for foo and bar, but baz.bar is still shown as undefined.

What is expected?
foo.foo, bar.value and baz.bar should all show as "foo" at first and then "bar"
What is actually happening?
baz.bar is shown as undefined both before and after the change.
System Info
System:
    OS: Linux 6.2 Ubuntu 23.04 23.04 (Lunar Lobster)
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
    Memory: 9.27 GB / 31.24 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.asdf/installs/nodejs/18.17.1/bin/node
    npm: 9.6.7 - ~/.asdf/plugins/nodejs/shims/npm
    Watchman: 4.9.0 - /usr/bin/watchman
  Browsers:
    Chromium: 116.0.5845.187
  npmPackages:
    vue: ^3.3.4 => 3.3.4

Any additional comments?
No response

hello 👋
I think I'm also facing this issue. I managed to reproduce it with the following code

any update on this? I have encountered the same problem

I have the same problem and here is the code to simulate it. Link code
App.vue
`

`
useCounter.js
`
import { reactive, toRefs } from "vue";
export default function usePaginator() {
const state = reactive({
count1: 0,
count2: 10,
count3: 20,
});
const incrementCount1 = () => {
state.count1++;
console.log(state.count1);
};
const incrementCount2 = () => {
state.count2++;
console.log(state.count1);
};
const incrementCount3 = () => {
state.count3++;
console.log(state.count1);
};
return {
...toRefs(state),
incrementCount1,
incrementCount2,
incrementCount3,
}
};
`

Seems like this was a bug in Vue, as it works fine with Vue 3.5. No idea which commit fixed it.


Colorize not working properly in 1.21

Colorize Version 1.10.3 Neoforge 1.21 Minecraft

Fixed in 1.10.4, released on Modrinth, waiting for approve on CurseForge


Experiment with react-intl

see also #1794

Add dependencies
Simple first version
Use formatjs extraction-distribution workflow

Closing since associated ADR has been merged. This PR shall be revisited when implementation is due (however agreement is to use react-i18next, not react-intl).


Get secure session expiry timer less verbose

Problem
Periodically Secure session check if any session has expired. This is nice, and especially when there is an effective expiry. But otherwise it basically just tell you that it is checking and it happens quite often.
It would be better to just keep the effective session expiry logging. Pretty sure the other log is not really helpful in any way.
Summary of Changes

The current PR just remove the chatty log

@jelderton @hawk248 @robszewczyk ?


[KOGITO-4789] BDD tests: Don't fail step in case pod is in ErrImagePu…

…ll state
https://issues.redhat.com/browse/KOGITO-4789
Signed-off-by: Karel Suta<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test


Add diagnostics graphs for client frame timing telemetry and average FPS.

Add a graph for average FPS and another for client frame timings (render, ui, begin, end, client, server) to the Timings tab.

Do you bump versions for these changes, or are you waiting for a couple of changes to come in first?

Do you bump versions for these changes, or are you waiting for a couple of changes to come in first?

Nope, forgot. Thanks.


Test to ensure StaleReferenceException is raised

I was curious what the response looked like from PhantomJS when we get a StaleReferenceException found out we didn't have a test triggering it.

If the sleep does cause the test to become flaky then I think we can fix it by using refute_has(session, Query.css("#removed-node")) to force the test to block until the node is removed from the DOM.


404 on fonts.css

Failed to load resource: the server responded with a status of 404 (Not Found) https://cloud.typography.com/6144452/633342/css/fonts.css

I'm going to close this, it's still the case on warehouse.python.org, but the master branch has diverged from that (and once it's ready will be deployed to warehouse.python.org).


[Feature Request] jupyter-style autocomplete in the editor (provide column names for dataframes for instance)

When typing in the main editor, there are no completions for column names but there are completions when using the input windows in interactive windows:

The method completions (e.g., .dropna()) in the interactive windows only show up for DataFrame not Series. Meanwhile, the editor does not seem to have completions for those common methods at all.

Version: 1.34.0 (user setup)
Python Extension: 2019.5.17517
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:59:37.030Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

not sure if this is directly related the python extension issue but I couldn't find the IntelliSense repo on GitHub.

The column names do not show in the editor at the moment because the intellisense for the editor doesn't have a connection to the running jupyter instance. Not sure if we should add it or not. Maybe?
For the series problem, what's missing? It seems to work for me? Or are you referring to like double completion? (Where you type a . at the end of a return value)
Something like:
df.iloc[0].
Unfortunately, that isn't currently supported.
The intellisense repo is here:
https://github.com/Microsoft/python-language-server

Not sure if we should add it or not. Maybe?

Would be great if I don't have to type them every time. lol...

Or are you referring to like double completion? (Where you type a . at the end of a return value)

When I use dot notion or brackets to select a column and then apply a method on it.

When I use dot notion or brackets to select a column and then apply a method on it.

That would be a feature request on the language server. Feel free to add issues there too.

I should have explained more why I was hesitant to include column names in the editor intellisense.
The question is do they actually apply to the active file or not. I think we can figure that out based on if the active file ever sent a cell, but what if two files sent the same variable name? Okay then we have to parse variable creation and figure out which one was the last one. At that point we're writing another language server (right now the column names come from Jupyter's auto completion).
So it's possible, it's just a lot of work. Hence the maybe.

@rchiodo thanks for the explanation. btw, this little input window at the bottom really grows on me!
btw, is there any way to edit those read-only:

If so, it would make it feel like writing a jupyter notebook XD... and also I found that sometimes I had a typo and need to copy and paste the code to input windows again. Would be easier if I can just correct them right away.

Our intent with the interactive window is that it's a history, not a notebook. It's like a terminal (or what Spyder has).
Many people actually do generate notebooks though (instead of just python code), and have been asking for a way for the window to behave more like a notebook.
With that in mind, what would you want?

An interactive window that keeps in sync with the code (maybe something like this: #5880)
Inline output in the python editor, but keep the interactive window the same. This would be like hydrogen.
A hybrid approach where the interactive window is still used, but you can edit the last cell
A hybrid approach where the interactive window is in sync with the code, but removes old outputs and reorders them (basically what @gramster asked for in #5880)
Something else?

@rchiodo those are pretty much what I want. and also some better markdown support I guess?, It's something I have logged before but maybe was closed for some reasons like change font size of the markdown text.

Sorry I should have asked for a priority or which one you liked best.
Your markdown bug is still active. We just haven't gotten to it yet. #4042

@rchiodo thanks... I was confused I guess.
I think I really gotta like this on:

removes old outputs and reorders them

I used to miss inline output since I was using Atom + Hydrogen before. But right now I think the current vs code model is better since it keeps my code clear.

May not be technically feasible to support the jupyter autocomplete in the editor, but we'll take a look. This seems to be a reasonable expectation.
@StevenLi-DS, can you open separate issues for your other suggestions?  This will help us make sure we don't miss any of the feedback you've been giving us. Thanks!

But I remember that we could actually close cells in the interactive windows right? Why can I no longer see that button anymore?

@rchiodo I was trying to reproduce the issue and then realized that I make a mistake. It is because I had a wide dataframe:

Yeah I've always felt like those buttons should be on the left. You shouldn't have to scroll to get to them.

@greazer for:

Btw, I really wish you guys can toggle run below and run above in CodeLens. I can't remember how many times I accidentally clicked them.

There is a closed issue: https://github.com/microsoft/vscode-python/issues/5128 and I also mentioned it here: https://github.com/microsoft/vscode-python/issues/4259 . Both of them were closed and maybe reopen them? This really bothers me.
I saw that @rchiodo has logged some of the ideas above. Should I open one for adding availability to reordering the cell or something?

Those other two issues were about turning all codelens off. We don't have a setting for specific ones.
Were also talking about changing them again to support debugging. I think we need a way for the user to pick what code lens they see. I'm going to enter an issue for that.

The new issue is #5946. Please feel free to comment there if I missed anything.

The column names do not show in the editor at the moment because the intellisense for the editor doesn't have a connection to the running jupyter instance. Not sure if we should add it or not. Maybe?

Yes, you definitely should add this. One of the main purposes of Jupyter notebooks is to do exploratory data analysis, so for our team it is crucial to have autocomplete for pandas columns.

I should have explained more why I was hesitant to include column names in the editor intellisense. The question is do they actually apply to the active file or not.

Our intent with the interactive window is that it's a history, not a notebook. It's like a terminal (or what Spyder has). Meaning once you type something in, it can't be changed or you'd be traveling through time :)

I like the idea that interactive window is a history and it shouldn't be changed, but it should be connected to only one file. If you run a cell from another file, it should be a separate interactive window (like you create a new jupyter notebook). This way there won't be mix between variable names of different files and autocomplete will apply to only one file variables.

Btw, the column name completion in jupyter works with both dot notion and break.

@StevenLi-DS what's break? CTRL+C?

@Stanpol 	I'm going to add another issue to see how many people use multiple files per interactive window now. Not sure if people would want to have 1 per file or not.
https://github.com/microsoft/vscode-python/issues/6373

@rchiodo sorry I mean brackets...
df.col_name or df['col_name']

Not sure if people would want to have 1 per file or not.

I think one interactive window per file would be a good start! Later on, one might look at merging two interactive windows or running cells from another file in an existing window.

There are at least two people in this thread that are complaining about the inability to autocomplete columns. Jupyter itself supports this. The debug console of VSCode supports it. I ran across this same issue mentioned in another bug by a different customer, and when I tried it myself I got confused as to how the debug console could "do the right thing" but not in the editor. Finally, now that we have debug cell, there's yet another entry point for more people noticing.
Therefore, I think we need to seriously consider doing something to address this. Moving to re-triage.

Let's do this. We will assume that most people are using one file with the interactive window. Try to make it work when debugging a cell too.

Moving back to triage, had another request for this.

I was looking forward to just using Jupyter in vs code and not the web browser now that notebooks are supported but this is definitely a unexpected experience to find autocomplete not working when running the notebook in vs code.

@damienrj they should be working in notebooks. (This bug is about files, not notebooks).
You do have to connect to the server first though (by running a cell).

@rchiodo It turns out that it was a combination of the problem https://github.com/microsoft/vscode-python/issues/8171 and https://github.com/microsoft/vscode-python/issues/12655 that made me thing that it wasn't working. So nevermind.

@rchiodo and @greazer - I see this was on the Q1 Release and then removed.  Do you have any idea when this will make it back onto the roadmap?  This seems like a very standard workflow for DS teams that are working interactively in python files, and prefer that workflow vs. using the full Jupyter notebook.  Thanks!

Sorry but there are no plans for this at the moment. @greazer, we really should publish our roadmap.

...we really should publish our roadmap.

That'd be great!

Sorry but there are no plans for this at the moment. @greazer, we really should publish our roadmap.

Ok, thanks for the update.  Appreciate it!

Is there any way to achieve such autocomplete (for the dataframe column names) ? It is really helpful (and much needed) while cleaning the data. Thanks

Dataframe column name auto complete is only available within the notebook editor or within the interactive window.


Swap configs

https://github.com/user-attachments/assets/9f9af1ed-5f81-4bd1-9367-ac3e20c37f38
/claim #1035
/closes #1035

Interesting
I originally thought the issue was just for recording settings but I know for example cursor let you define a list of models to use in their drop down that I think we should do too (eg too much friction to change models in search atm)
Is the account switch useful though? Might cause issues
Any thoughts?

About the model list, it might be better to address in a separate issue/PR since it's not really in the scope of this issue.
This approach basically creates a entirely new settings by creating a new store=${name}.bin file, much more safer and isolated and less prone to errors and edge cases.
We could copy over old settings to new store file except recording settings and it will achieve the same thing.

okay yeah
could it be possible to have a shortcut to switch configs?

nice!!
/approve


Need a method that will interrupt or terminate the com.google.cloud.pubsub.v1.Publisher immediately

Currently in PubSub there is only Publisher.shutdown() which sends any pending requests in the buffer and then clear the resources and then exits.
/**
   * Schedules immediate publishing of any outstanding messages and waits until all are processed.
   *
   * <p>Sends remaining outstanding messages and prevents future calls to publish. This method
   * should be invoked prior to deleting the {@link Publisher} object in order to ensure that no
   * pending messages are lost.
   */
  public void shutdown() throws Exception {
    if (shutdown.getAndSet(true)) {
      throw new IllegalStateException("Cannot shut down a publisher already shut-down.");
    }
    if (currentAlarmFuture != null && activeAlarm.getAndSet(false)) {
      currentAlarmFuture.cancel(false);
    }
    publishAllOutstanding();
    messagesWaiter.waitNoMessages();
    for (AutoCloseable closeable : closeables) {
      closeable.close();
    }
    publisherStub.shutdown();
  }

Due to this the shutting down the publisher takes a while when there is huge number of requests pending in the buffer. There can be "n" batches pending to sent. This can be easily simulated by having a simple Publisher code which calls publish.send() based on the flow controller settings (since this is not honoured by the API, assume it was done by the client side code).
//Create publisher with default instance that picks up
             Publisher publisher = Publisher.newBuilder(topic)
                     .setBatchingSettings(batchingSettings)
                     .setRetrySettings(retrySettings)
                     .setExecutorProvider(executorProvider)
                     .build();

               PubsubMessage pubsubMessage = PubsubMessage.newBuilder()
                       .setData(data) // bytes to be sent
                       .build();
               /*
		* code to throttle when the limit is exceeding - this block will prevent adding more event to the API
		*/
		…

               ApiFuture<String> future = publisher.publish(pubsubMessage);
               RecoveryHandlingCallback callback = new RecoveryHandlingCallback(pos, event, sequence_no, future, receiptCallback, dataSize);

               ApiFutures.addCallback(future, callback, MoreExecutors.directExecutor());

           if (publisher != null) {
            publisher.shutdown();
	   }

Let us assume the MaxOutstandingRequestBytes was 100Mb (assume the user had enough network bandwidth and machine capabilities like mentioned here - https://cloud.google.com/pubsub/docs/troubleshooting#client-libraries-issue-tracker-java) and the user have a very high retry setting to avoid crashes due to network glitches etc. The shutdown won't return until it is done with the whole lot of pending requests either successfully or with an exception.
For a service like Publisher it is always good to have two ways of shutting down

A graceful shutdown() which try to clear the existing buffer and then return (Publisher has this already)
A shutdownNow() which will terminate the process immediately  and clear all the depending resources cleanly and return. This is required when a PubSub's Publisher is used to build application that works on data pipelining and the application demands an immediate shutdown of all components in it.

Since this request is not specific to Java, we will track it via the public issuetracker: https://issuetracker.google.com/issues/289267759.


Lacking installDir doesn't seem to work

MicroCabal is passing -Q without installDir, which should work, but for me, it calls head (pkgPath flags) which seems to error (applying the patch at the end of the post)
 % mhs -Q parsec-<IP_ADDRESS>.pkg
mhs: error: pkgPath is empty: []

Apparently this is because the pkgPath setting in the beginning of the main function didn't work, so it fell back to the line ending with [] -- No package search path.
It works if I pass use mhs -Q parsec-<IP_ADDRESS>.pkg -a /home/janus/.mcabal/mhs-<IP_ADDRESS>.
Reporting this because it took a while to debug so I am wondering whether the following patch with an error message might make sense to add.
diff --git a/src/MicroHs/Main.hs b/src/MicroHs/Main.hs
index 122b11b..cff9f8b 100644
--- a/src/MicroHs/Main.hs
+++ b/src/MicroHs/Main.hs
@@ -257,7 +257,10 @@ mainInstallPackage flags [pkgfn, dir] = do
         createDirectoryIfMissing True d
         writeFile fn pkgout
   mapM_ mk (pkgExported pkg)
-mainInstallPackage flags [pkgfn] = mainInstallPackage flags [pkgfn, head (pkgPath flags)]
+mainInstallPackage flags [pkgfn] =
+  case pkgPath flags of
+    [] -> error $ "pkgPath is empty: " <> show (pkgPath flags)
+    first:_ -> mainInstallPackage flags [pkgfn, first]
 mainInstallPackage _ _ = error usage

Thanks.  I've made the change.


Delete ecosystem.config.js

You guys don't need this

Metal protecc
Metal attacc
But when Metal approves the PR yet doesn't merge it into main, it's kinda wack


Added modification of the virtuoso exposed port until it is ready to …

…receive incoming connections

merged on master, will update specific virtuoso versions once we get some more feedback

Thanks 👍


IMPORTANT: Equivalent GP path, GP name, GP Element is missing for every setting in this document

We should add the equivalent GP information for every setting, just like settings in PolicyCSP have equivalent GP information. It will help to find the respective intune setting for GP.
We should add both the GP path for the setting
Computer config -> Windows setting -> Security setting -> Windows firewall with advanced security
Computer config -> Administrative templates -> Network -> Network connections -> Windows defender firewall
The absence of the GP paths makes the system impossible to decide whether the conflict is happening when same setting configured via Intune and GP.

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

ID: bfea4e59-ec8c-cbdf-a039-23612c2266a5
Version Independent ID: 7058544b-7ef2-a398-366a-cf71520aa9d8
Content: Firewall CSP - Windows Client Management
Content Source: windows/client-management/mdm/firewall-csp.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

@yogeshasalkar Thank you for providing feedback.
Please consider opening a product feedback ticket for any of your suggestions or feature requests to help Microsoft improve your experience, you could add your feedback via the Microsoft Windows 10 Feedback Hub. You might find others have made a similar request that you can add to, or you can open a new one.
Thank you for your contribution to make the docs better! Much appreciated!


Can I use ncls to calculate the intersection/union number between ranges?

Is there any method to return the intersection and union between two range in ncls?
For instance, range(1,10) and range(5, 15) would return (5,10) and (1,15).
Or just simply return the length of intersection and union like the bedtools jaccards? [https://bedtools.readthedocs.io/en/latest/content/tools/jaccard.html]

I’ll reply more in depth on monday, when I’m back at work :) Pyranges should be able to do this. The repo is on my github :)

Thank you very much! I am now using pybedtools to calculate the intersection between ranges. However, the intersection matrix between 300 mRNA tracks (each contains around 15 ranges) would cost me 400 seconds in a 32 core server. I will try Pyranges first and give you some feedback.

It is still largely unused. I have passing unittests, but it might still have bugs. I would also look into this potential error in bedtools jaccard: https://github.com/arq5x/bedtools2/issues/645 Whether it is a bug and whether it matters I dunno' :)

Also, if you use pybedtools, it is advisable to presort the data first. It is much faster then.


fix(material-experimental/mdc-slider): init step on thumb inputs

@mmalerba Small fix here. It seems in refactoring the slider thumb input initialization logic I overlooked the step property altogether


Mixed positive and negative numbers don't sort correctly for "en-US" at least

Hi! New to this project. Very nice and lightweight...thanks!
I notice that the list of numbers (3, -2, 1) sorts ascending as (1, -2, 3), rather than (-2, 1, 3) as I think would be more expected.
It looks like this is the result of including the ignorePunctuation parameter to localeCompare. Naively, if we just eliminated ignorePunctuation, it would work as expected, in at least this case. But I'm sure this was done for a reason. Can you let me know why so I can see if I can propose a solution?
Thanks again!

Hi @CrozierSOS
I don't recall the rationale for ignorePunctuation. I would speculate it's for if you have numbers that are encased as a string "1", or maybe if you have numbers that have a hashtag on the front #1 , or perhaps encased/surrounded by parenthesis (1) (which is another way to show negative numbers (which currently also wont work with this library :sweat_smile:). These are just examples...etc
We should probably handle being able to have negative numbers though :sweat_smile: . I think the default should be to ignore punctuation :thinking:  and then have a boolean flag (className) for either negative numbers, or preferably not ignoring punctuation :thinking: . Or if you have a better solution, feel free to share.
Either way, I should probably have tests setup for ignoring punctuation and also for sorting negative numbers. I don't think negative numbers has ever come up, which is somewhat surprising; so thank you for raising it :+1:
Cheers.

Thanks for the reply, @LeeWannacott
I think you're probably right. Assuming the need for backward compatibility, making ignorePunctuation: true the default (as it is now) and allowing a <table> class like ignore-punctuation-false or do-not-ignore-punctuation would solve my problem...I think.
Would you like me to do a pull request for this?
Cheers!

Hey @CrozierSOS

allowing a <table> class like ignore-punctuation-false

I think it would be better to put the class on <th> (users might not want the functionality on all of the <th>) and naming it a double negative probably isn't the best (I know I suggested it); I think we could probably name it sort-punctuation (might be confusing for a developer, but should be more straight forward from a user perspective) and then mention that it allows sorting of negative numbers in the description...

I think you're probably right. Assuming the need for backward compatibility

npm packages have versioning, so it's not the end of the world. However personally I find it annoying when libraries have a lot of churn.

Would you like me to do a pull request for this?

Sure and if you need any help; feel free to ask.
Script: https://github.com/LeeWannacott/table-sort-js/blob/master/public/table-sort.js
Tests: https://github.com/LeeWannacott/table-sort-js/blob/master/test/table.test.js
Thanks.

Hi @LeeWannacott
OK, so I gave this some more thought and tried out a few approaches. I don't think we can get the desired results using localeCompare, since it compares strings, so I took the approach of coercing the data to JavaScript Number values to sort. The whole concept of "punctuation" then is not relevant, so I landed on bare-numbers as an idea for the th class, but something else (bare-number-sort?) might be more consistent with existing classes. Let me know what you think about the approach, and I'll revise or add documentation and tests.
I don't do a lot of this, and none any more on GitHub, so I'm not sure I did things right, but I think you'll see it as a pull request to the main project, from my fork branch.
Thanks!

Hey @CrozierSOS
Left some comments on the PR. https://github.com/LeeWannacott/table-sort-js/pull/65
I think in this case it might be a good idea and easier to write the tests first and then the solution; so you know if the test is handling edge cases, such as passing something to Number() that returns NaN (this is just an example) etc.
Cheers.

@CrozierSOS Done by scodes73 in PR https://github.com/LeeWannacott/table-sort-js/pull/87; release: 1.16.0 better late than never :sweat_smile: should infer the class automatically which is pretty cool. Still need to handle currency and percentages in numeric sort. https://github.com/LeeWannacott/table-sort-js/issues/97

@LeeWannacott Hi! FWIW, we decided to "fix" this issue by simply not including currency and other symbols in the actual cells. Instead we put a "legend" in the column header, like "Amount ($)".

@LeeWannacott Hi! FWIW, we decided to "fix" this issue by simply not including currency and other symbols in the actual cells. Instead we put a "legend" in the column header, like "Amount ($)".

Buffalo Springfield - For What It's Worth 1967 . That is one way to do it!, Shouldn't be too much work though to do currency as well; just need to modify the regex and strip the currency sign... famous last words...
p.s that reminds me I don't think this class handles number with commas in them; that's not ideal...

@LeeWannacott And handle multiple currencies....


Update dependencies in both sample app and library

Updated versions of all dependencies in  below modules levels
0⃣  project
1⃣  app
2⃣ library module
Some more version increments
✔  AGP (Android Gradle Plugin)
✔ Kotlin gradle plugin
✔ Fixed sample app (using different quotes API)

Here's the snapshot of current status
Endpoint of new quotes API is https://quotesondesign.com/wp-json/wp/v2/


Improve hubble exporter configuration error handling and logging

Log errors when reloading hubble exporter configuration dynamically and do not attempt to close os.Stdout

I'm noticing a few more possible issues, gonna iterate a bit and do a bit more manual testing as well.

/test

/test


Response from /ga4gh/trs/v2/tools/{id} API  uses toolName instead of name in json

Describe the bug
The TRS specification requires a Tool object to have a name attribute, but when retrieving a single tool from the API, this attribute is named toolName in the response.
To Reproduce

Visit any tool (this one for example: https://dockstore.org/api/api/ga4gh/v2/tools/%23workflow%2Fgithub.com%2Fabelhj%2Fsv-pipeline%2FPre_Merge_SV_v2_terra)
Compare the returned json against the TRS spec

Expected behavior
To see a name attribute in the top level tool object
Actual behaviour
See a toolName attribute instead
┆Issue is synchronized with this Jira Story
┆friendlyId: DOCK-2157
┆sprint: Backlog
┆taskType: Story

I think you're looking for https://dockstore.org/api/ga4gh/trs/v2/tools/%23workflow%2Fgithub.com%2Fabelhj%2Fsv-pipeline%2FPre_Merge_SV_v2_terra  (2.0.0 final) rather than https://dockstore.org/api/api/ga4gh/v2/tools/%23workflow%2Fgithub.com%2Fabelhj%2Fsv-pipeline%2FPre_Merge_SV_v2_terra (2.0 beta.2 )
Or use https://dockstore.org/api/static/swagger-ui/index.html#/GA4GHV20 rather than https://dockstore.org/api/static/swagger-ui/index.html#/GA4GH
This was changed in the standard in https://github.com/ga4gh/tool-registry-service-schemas/pull/92

Thanks @denis-yuen for the clarification. I think where I got confused is the fact that the self url in the tool json from the url you suggest above has the link to the /api/api/ga4gh endpoint, and no the /api/ga4gh endpoint.

Makes sense, we had an internal bug ticket for this for 1.13
(https://ucsc-cgl.atlassian.net/browse/SEAB-3936 for others)


Newline in vars:pre-request blocks loading file

Hey, I was creating a new request and was copy/pasting an array of values into the VAR field.
During implementation everything was working. But when Bruno wants to load the file after it was closed it is not showing up in bruno anymore. After some debugging I figured out it was the newline. Here is an example of a not working file
TEST.bru
meta {
  name: TEST
  type: http
  seq: 1
}

get {
  url: http://www.example.com
  body: none
  auth: none
}

vars:pre-request {
  var: ["A", "B",
  "C"]
}

I have also hit this issue.
To add just a bit, I specifically observed that the request refuses to properly mark as saved if a var has a newline in it (such as copy-pasting some json from some other tool's output as mentioned).
The request does run at least, but the newline data must be purged before saving the request.


Create omarsotom.yml

Hi @omarsotom it looks like you followed the steps correctly to request the certificate, but I do not see that you have enrolled in the course and completed the tests as required. If you enroll and complete the tests, you can repeat the same steps to receive a certificate. Please let me know if you have questions about the process, thanks!


Add more specific error classes

We shouldn't raise bare errors as it forces the client to rescue RuntimeErrror, it's bad practice and bad design.
This PR adds specific error classes that can be rescued more cleanly.
This may be a breaking change since people rescuing RuntimeError to catch exceptions raised from rbi won't catch anything now since RBI::Error is a StandardError and will need to update their rescues.

Feels like a bare raise (outside of a rescue block) is something that RuboCop should complain about, but I couldn't find a cop for it.

@egiurleo:

I feel like the names of the errors are inconsistent. Some of them are specific (e.g. ReplaceNodeError), and some are more general (e.g. GroupNodes::Error). I think it would be more consistent to give them all specific names. What do you think?

Indeed, I like the GroupNodes::Error scheme as the error gets nested in the rewriter class it belongs to. The issue is with errors coming from the model, there is no namespace to define them into.
I could just use a base Model::Error if you prefer? But the ReplaceNodeError seemed more specific.
Another way would be to create a namespace for errors:

RBI::Errors::ReplaceNodeError
RBI::Errors::UnknownGroupError
RBI::Errors::UnknownNodeError
...


[FLOC-3012] Pin Ubuntu version for dependencies, to prevent apt conflicts

Currently, trying to run the client or acceptance tests for Flocker versions other than the latest version fails on Ubuntu, due to apt wanting to install the latest dependency rather than the requested dependency. e.g. running admin/run-client-tests --distribution ubuntu-15.04 --flocker-version=1.2.0.dev1 fails with:
The following packages have unmet dependencies:
 clusterhq-flocker-cli : Depends: clusterhq-python-flocker (= 1.2.0-0.dev.1) but 1.4.0-0.dev.1 is to be installed
E: Unable to correct problems, you have held broken packages.

This PR pins the version for any dependencies starting with clusterhq- to the same as the top-level package. Currently, the only such dependency is clusterhq-python-flocker which always must match the version number of the top-level packages.
As well as working for the above release version, it also works for branches: admin/run-client-tests --distribution ubuntu-14.04 --branch master --flocker-version=1.4.0.dev1+10.gf9dea05 installs an previous version of the client from Buildbot.

Dude John,
The tests are failling in the vagrant builds
==> default: No package clusterhq-flocker-node-1.4.0-0.dev.1.64.g56cb8ae available.
==> default: Error: Nothing to do
==> default: Traceback (most recent call last):
==> default:   File "/tmp/vagrant-shell", line 64, in <module>
==> default:     check_call(['yum', 'install', '-y'] + branch_opt + [package])
==> default:   File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
==> default:     raise CalledProcessError(retcode, cmd)
==> default: subprocess.CalledProcessError: Command '['yum', 'install', '-y', '--enablerepo=clusterhq-build', 'clusterhq-flocker-node-1.4.0-0.dev.1.64.g56cb8ae']' returned non-zero exit status 1
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Failed 1: vagrant up

but this change also breaks the client tests on Jenkins
see:
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/
in detail:
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/job/run_client_installation_on_Ubuntu_Trusty/1/console
and
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/job/run_client_installation_on_Ubuntu_Vivid/1/console

18:52:06 ++ flocker-deploy --version
18:52:06 + test 1.4.0.dev1+77.ga9de306 = 1.4.0.dev1
18:52:06 + return 1

I don't see how this one could be related, it looks like the acceptance.yaml has changed, but I will post it here:
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/job/run_acceptance_on_AWS_CentOS_7_for_flocker.acceptance.integration.test_postgres/1/console
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/job/run_acceptance_on_AWS_Ubuntu_Trusty_for_flocker.acceptance.endtoend.test_dataset/1/console
http://<IP_ADDRESS>:8080/job/ClusterHQ-flocker/job/check-release-packages-FLOC-2770/job/run_acceptance_on_AWS_Ubuntu_Trusty_for_flocker.acceptance.integration.test_mongodb/1/console

18:44:53 main function encountered error
18:44:53 Traceback (most recent call last):
18:44:53   File "admin/run-acceptance-tests", line 14, in <module>
18:44:53     react(main, (sys.argv[1:], BASEPATH, TOPLEVEL))
18:44:53   File "/tmp/v/lib/python2.7/site-packages/twisted/internet/task.py", line 875, in react
18:44:53     finished = main(_reactor, *argv)
18:44:53   File "/tmp/v/lib/python2.7/site-packages/twisted/internet/defer.py", line 1253, in unwindGenerator
18:44:53     return _inlineCallbacks(None, gen, Deferred())
18:44:53 --- <exception caught here> ---
18:44:53   File "/tmp/v/lib/python2.7/site-packages/twisted/internet/defer.py", line 1107, in _inlineCallbacks
18:44:53     result = g.send(result)
18:44:53   File "/tmp/workspace/ClusterHQ-flocker/check-release-packages-FLOC-2770/run_acceptance_on_AWS_CentOS_7_for_flocker.acceptance.integration.test_postgres/admin/acceptance.py", line 921, in main
18:44:53     yield runner.ensure_keys(reactor)
18:44:53   File "/tmp/workspace/ClusterHQ-flocker/check-release-packages-FLOC-2770/run_acceptance_on_AWS_CentOS_7_for_flocker.acceptance.integration.test_postgres/admin/acceptance.py", line 534, in ensure_keys
18:44:53     key = self.provisioner.get_ssh_key()
18:44:53   File "/tmp/workspace/ClusterHQ-flocker/check-release-packages-FLOC-2770/run_acceptance_on_AWS_CentOS_7_for_flocker.acceptance.integration.test_postgres/flocker/provision/_libcloud.py", line 185, in get_ssh_key
18:44:53     raise CloudKeyNotFound(self._keyname)
18:44:53 flocker.provision._libcloud.CloudKeyNotFound: vagrant-buildbot

The tests on Jenkins might need to be changed similarly to https://github.com/ClusterHQ/build.clusterhq.com/pull/140

Resubmitting this, as none of the tests noted as failing appear to be due to this patch.
On OS X, the client tests may fail due to https://clusterhq.atlassian.net/browse/FLOC-3044 but this is also the case for master.

:+1:

@jongiddy can this also close https://clusterhq.atlassian.net/browse/FLOC-2923?

@adamtheturtle I believe it should, as Buildbot tests are always runs with the Flocker version specified. Even if a new build gets triggered, the previous test should use the earlier dependency.

great


Initialize feedstock

Jira ticket: https://anaconda.atlassian.net/browse/PKG-701
Upstream repo: https://github.com/pdm-project/pdm

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_132093u9ow/clone/recipe/meta.yaml:69: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_132093u9ow/clone/recipe/meta.yaml:69: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_5679tc4ab9/clone/recipe/meta.yaml:69: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_5679tc4ab9/clone/recipe/meta.yaml:69: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f6sbvwjobn/clone/recipe/meta.yaml:46: missing_python: For pypi packages, python should be present in the host and run sections
WARNING: /tmp/abs_f6sbvwjobn/clone/recipe/meta.yaml:66: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f6sbvwjobn/clone/recipe/meta.yaml:66: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d55y2x3n9i/clone/recipe/meta.yaml:46: missing_python: For pypi packages, python should be present in the host and run sections
WARNING: /tmp/abs_d55y2x3n9i/clone/recipe/meta.yaml:66: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_d55y2x3n9i/clone/recipe/meta.yaml:66: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_27lkdnexws/clone/recipe/meta.yaml:46: missing_python: For pypi packages, python should be present in the host and run sections
WARNING: /tmp/abs_27lkdnexws/clone/recipe/meta.yaml:66: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_27lkdnexws/clone/recipe/meta.yaml:66: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c4bi2keph5/clone/recipe/meta.yaml:47: missing_python: For pypi packages, python should be present in the host and run sections
WARNING: /tmp/abs_c4bi2keph5/clone/recipe/meta.yaml:67: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c4bi2keph5/clone/recipe/meta.yaml:67: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_besh2_dws_/clone/recipe/meta.yaml:50: missing_python: For pypi packages, python should be present in the host and run sections
WARNING: /tmp/abs_besh2_dws_/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_besh2_dws_/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_3e6w8k3_61/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_3e6w8k3_61/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_9fb1_uet5e/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_9fb1_uet5e/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_40p_s_mtt5/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_40p_s_mtt5/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_14yfj2w4g7/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_14yfj2w4g7/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_6ezqtmj98u/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_6ezqtmj98u/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_a4xuudlpbw/clone/recipe/meta.yaml:71: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_a4xuudlpbw/clone/recipe/meta.yaml:71: missing_license_url: The recipe is missing a license_url
Warnings were found


Support overriding the helm-sync container's resource requirements (#380)

Removed setUID("1"), setResourceVersion("3"), setGeneration(4) from the cherrypick to avoid cherrypicking more unrelated changes (https://github.com/GoogleContainerTools/kpt-config-sync/pull/331 and etc.) to the release branch.
https://github.com/GoogleContainerTools/kpt-config-sync/compare/f72f4a38f7d1d774ded609d765d1fbc4b89edce1..9add614076125202bb942744a44531772ca414ea

/lgtm
/approve


[Bug] In the ATM8 modpack thunderstorm ritual only causing snow

currently in a snow biome and I have summoned 3 different Afrit thunderstorm spirits using the Abaras' Conjure Thunderstorm ritual and each time he spawned It began to snow but no lightning was spawned at all. The afrit himself just punches the air from the moment he spawns to his death and has smoke particles at his feet, the smoke makes me think I need to throw him something but the Dictionary of Spirits doesn't say anything of the sort.

Hmm I am not sure if that can be fixed. If the weather changes then the code is running as intended ( you do not need to give him additional items ).  What happens if you run the command to summon a thunderstorm?
I am using the same code, so unless vanilla changed it on their end both should produce the same result

Closed as stale