Can't get client certificate authentication working

It appears the certs in the repo are inconsistent, both in the Certs folder, and in the respective projects' folders. Initially I've tried to get it running on macOS but have switched to Windows with the same results.
I've slightly modified the certificate generation Powershell steps to be able to fully execute them without manual intervention here: https://github.com/sourishkrout/AspNetCoreCertificateAuth/blob/master/Certs/README.md
Here are more concrete problems/questions:

In the chained example, why is the root ca cert being used as the server's cert?
Why is the root cert not set to CA=1 and define a pathlength=1 which would allow an intermediate cert to be used?
Is it generally required to install the generated root/intermediate cert into the local trust store? I couldn't find an option to specify a root cert pool for private CA usage which is a common use case.
Following code appears to have no effect... any idea why? https://github.com/damienbod/AspNetCoreCertificateAuth/blob/master/AspNetCoreCertificateAuthApiChained/Startup.cs#L53-L75
When a server cert is specified it appears IIS Express/Kestrel serves the auto-provisioned self-signed dev-cert irrespective of the cert in Program.cs?

Overall I found the implementation of TLS in .NET Core to be incompatible with established best practices including the inability to use intermediate certs for server auth in Kestrel.
Any help and pointers would be much appreciated. We'd love to add .NET Core to the Hello mTLS documentation: https://smallstep.com/hello-mtls
Thanks @damienbod!

•	In the chained example, why is the root ca cert being used as the server's cert?
This is just an example, you could use the intermediate or a self signed directly.
•	Why is the root cert not set to CA=1 and define a pathlength=1 which would allow an intermediate cert to be used?
Need to check this, not sure why
•	Is it generally required to install the generated root/intermediate cert into the local trust store? I couldn't find an option to specify a root cert pool for private CA usage which is a common use case.
If you’re using self signed, yes. If you create your certs from a cert which is trusted, ie from a CA, then this should just work. A lot of these configurations are because we use self signed certs
•	Following code appears to have no effect... any idea why? https://github.com/damienbod/AspNetCoreCertificateAuth/blob/master/AspNetCoreCertificateAuthApiChained/Startup.cs#L53-L75
This is the code used for custom validation. If the cert is accepted, then this code will execute.
•	When a server cert is specified it appears IIS Express/Kestrel serves the auto-provisioned self-signed dev-cert irrespective of the cert in Program.cs?
This does not make sense to me, or I don’t understand this or have this problem. I need to check this.
‘It appears the certs in the repo are inconsistent, both in the Certs folder, and in the respective projects' folders. Initially I've tried to get it running on macOS but have switched to Windows with the same results.’
Should not be, but I need to clean this up and reuse the same instance of the cert. Thanks for the pointer.
‘Overall I found the implementation of TLS in .NET Core to be incompatible with established best practices including the inability to use intermediate certs for server auth in Kestrel.’
Could you help me here? I would like to understand this better. Thanks
After testing again and validating the git repo should work as it is. All certs are trusted on my operating system.
I have added 3 examples which work as expected
https://github.com/damienbod/AspNetCoreCertificateAuth/blob/master/AspNetCoreCertificateAuth/Pages/Index.cshtml.cs#L65-L72
When the example doesn’t work for you, some of the runtime logs give extra info why the cert validation failed. If the certs fail, the validation part never runs.
Hope this helps, looking forward to your feedback
Greetings Damien


Reopening #9665 (TIA running tests when Total files changed = 0)

Trying to reopen #9665 fails as I wasn't the one that closed it.
@prawalagarwal can you please take a look?
Thanks

Hey @strosu, sorry about that. I've reopened #9665 for you
Closing this issue.


Upgrade gem

Change old gems to new one.
Refactoring using the ruby styleguides
Make compatible with ruby >=2

Thanks @alexwbuschle

You're welcome @felipero . I'm doing more changes. Tomorrow I'll be doing a new PR ;)


Check-in generated Go files

Reasoning

No need to generate the code when checking out the repo.
We will be able to remove annoying code generation steps from the build and tests.
Other types of generated code are already checked-in, so it's not like our repository is "normalized".

DoD

Generated Go files are checked in.
Tests do not pass if these files are not up to date.
"Generate code" step is removed from Esti tests.
Any documentation explaining how/when to generate code reflects the new situation.

tl;dr:
I am split on this.  I think we should list pros and cons, it's non-trivial.  It makes life easier for casual readers, it probably makes test actions run faster.  It makes life for some developers (for instance, this one) harder.
+++
Most of the above:

Easier to checkout and Go
Slightly faster build

And we probably also get:

Improved vulnerability scanning
Slightly improved semantic linking (click symbol to go to its definition)
webui/ is already not autogenerated
Faster test actions!  This step can be measured (hint hint) ⏱

000

We're halfway there (Other types of generated code are already checked-in, so it's not like our repository is "normalized".): so not an argument in favour of going either way. :-/

---

Harder to push code: We already have missing "make gen" calls on pushed codes.  These fail checks-validator during our checks action, and need to be re-pushed after a few minutes.
Conflicts from Hell when generated code on trunk has changed since branching out to a dev branch.  checks-validator makes these less dangerous to trunk, but don't help programmers remain sane.
webui/ is already not autogenerated, BUT we cannot check it with checks-validator!
Increased confusion with the Python and Java client codes: these are auto-generated but because of the way non-Go dependencies work any using code does not see the generated code.
Denormalization makes it more likely to have inconsistency in built code!  We now rely on an action running successfully rather than on a complete build

Adding a possible pro and a possible con:
Pro: This should make lakeFS go get-able, so we also win a Go SDK?
Con: To avoid inconsistencies, you'd still want to make sure there's no diff between generated code and whatever is checked in.. this might reduce any potential gain in build / test speed?


Implement a pool function similar to airflow to limit the number of "task instances" that are executed simultaneously（实现类似于airflow的pool功能, 来限制同时执行的"任务实例"个数）

airflow's documentation on the pool is at: https://airflow.apache.org/concepts.html#pools
Mainly some tasks can be time consuming, so you need to use pool to limit the number of tasks that are executed at the same time.
In addition, for SQL Task, it is generally necessary to limit the number of databases connected at the same time.
Preliminary ideas:
  1. Add a pool configuration interface, (this is a different concept from "Worker grouping")
  2. The user can create a new pool and specify the number of "task instances" that it can execute at the same time, such as: Pool: GPU, the number of tasks is 1.
  3. For all "Task/Task" nodes, after the "Worker Grouping" is specified, add a "Pool" selection. The default may be the Unlimited Default Pool. Here you can select the GPU Pool you just created. *Note: * To avoid problems such as deadlocks, each Task node can only be bound to at most one Pool!
  4. When the Worker takes the task from the Queue, it checks if there is a Pool and whether the Pool exceeds the limit.
At the same time, you need to improve the management interface of the Pool, for example: For each Pool, you should be able to find all Process/Tasks that reference this Pool. At the same time, # need to show the current real-time pool usage.

airflow的关于pool的文档在: https://airflow.apache.org/concepts.html#pools
主要是一些任务可能很耗时, 所以需要用pool来限制同时执行的任务数.
另外, 对于SQL Task, 一般也是要限制同时连接的数据库数量.
初步思路:

增加一个Pool配置界面, (这个和"Worker分组"是不同的概念)
用户可以创建一个新的Pool, 并指定其同时执行的"任务实例"个数限制,  比如:  Pool: GPU, 任务个数为1
对于所有的"Task/任务"节点, 在指定 "Worker分组"后面, 增加一个"Pool"选择, 默认可能是不限制的 Default Pool. 这里可以选择刚才创建的GPU Pool.   注意: 为了避免死锁等问题, 每个Task节点, 最多只能绑定一个Pool!
当Worker从Queue取任务时, 会检查是否有Pool, 并是否Pool是否超过限制.

同时, 需要完善Pool的管理界面, 比如: 对于每个Pool应该能找出所有引用了这个Pool的 Process/Task,   同时,  #需要展示出当前实时的Pool使用情况.

very cool！

very cool！
刚好满足我的需求：
比如说我们有十几台服务器，都会定时执行shell，这些不需要限制。
但当访问我们hive集群时候，由于资源有限，我们想限制这部分任务实例个数。

+1

+1

+1


feat(material-experimental/mdc-list): add test harness

Note: This PR is based on #20510, rebased with fixes for a few things that changed since it was created.

@jelbourn addressed your feedback in a new commit. This PR is marked as preserve commits so I'll manually merge it into the previous commit once you OK it.


Increasing HTTP connection timeouts

When uploading larger projects, some connections would be terminated unexpectedly.
I believe that it is related to https://blog.cloudflare.com/the-curious-case-of-slow-downloads/
and so I have increased the timout to work around that. If it is the linked issue, then a 5 minute timeout should be sufficient to allow arbitrary uploads.
Fixes #291

Looks good to me!


”Buza Cătun”, ”Chețiu”, ”Jimbor” are listed in the drop-down menu

Description:
When user writes ”Buza Cătun”, ”Chețiu”, ”Jimbor” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Buza Cătun"

Expected results
The location appears in the drop-down menu as "Buza Cătun, Bistrița-Năsăud (Chiochiș)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 1
Write in the search bar "Chețiu"

Expected results
The location appears in the drop-down menu as "Chețiu, Bistrița-Năsăud (Chiochiș)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Jimbor"

Expected results
The location appears in the drop-down menu as "Jimbor, Bistrița-Năsăud (Chiochiș)".


Can`t make pubsub work — any tips to debug?

Hi! First of all thank you for go-micro. After go-kit its dramatically reduce amount of service code you should write before writing your business logic itself. Right now im trying to test pubsub part of go-micro and can`t make my subscriber part to receive messages.
The config

RabbitMQ as broker
Consul as discovery
gRPC as transport

Proto part
syntax = "proto3";

message Event {
    // unix timestamp
    int64 timestamp = 1;

	// message
    string payload = 2;
}

The publisher part looks like this
type Application struct {
	service micro.Service
	publisher micro.Publisher
}
...
app.service = micro.NewService(
		micro.Name("go.p1.glutton.core-app"),
		micro.Version("latest"),
	)
app.service.Init()
app.publisher = micro.NewPublisher("glutton.topic.event-stream", app.service.Client())
ev := &proto.Event{
		Timestamp: time.Now().Unix(),
		Payload:  "some string",
	}
log.Printf("publishing %+v\n", ev)
app.publisher.Publish(context.Background(), ev)

and subscriber part
type EventApplication struct {
}
func (app *EventApplication) Process(ctx context.Context, event *proto.Event) error {
	md, _ := metadata.FromContext(ctx)
	log.Logf("[pubsub.1] Received event %+v with metadata %+v\n", event, md)
}

service := micro.NewService(
		micro.Name("go.p1.glutton.event-subscriber"),
		micro.Version("latest"),
)
service.Init()
micro.RegisterSubscriber("glutton.topic.event-stream", service.Server(), app, server.SubscriberQueue("queue.pubsub"))
...

I cant find any active connections to RabbitMQ server after client and server applications start. And not any error of Publish call. Could you please give some tips whats wrong and there i can get more information about this?

So In the subscriber case, have you stared the service? e.g service.Run(). The service will subscribe once you run it. The messages should then be received.

Other issue could be that docker is not allowing connections to rabbitmq, this may be blocking

Closing as solved in Slack.

So how was this solved? Ran into the same issue.


Native build broken with main due to OpenTracing 0.33.0 upgrade

The native build with main got recently broken:
com.oracle.svm.core.util.UserError$UserException: com.oracle.graal.pointsto.constraints.UnresolvedElementException: Discovered unresolved method during parsing: io.opentracing.Scope.span(). To diagnose the issue you can use the --allow-incomplete-classpath option. The missing method is then reported at run time when it is accessed the first time.
Detailed message:
Trace:
	at parsing datadog.opentracing.TypeConverter$CustomScope.span(TypeConverter.java:161)
Call path from entry point to datadog.opentracing.TypeConverter$CustomScope.span():
	at datadog.opentracing.TypeConverter$CustomScope.span(TypeConverter.java:161)
	at datadog.opentracing.OTScopeManager$OTScope.close(OTScopeManager.java:69)
	at com.oracle.svm.core.posix.NativeSecureRandomFilesCloserShutdownHook.close(PosixSunSecuritySubstitutions.java:86)

The issue is that the Datadog OpenTracing library (dd-trace-ot) is still depending on a method io.opentracing.Scope.span() that has been removed in OpenTracing API 0.33.0. I don't see a lot of things we can do to fix this except bugging Datadog to upgrade to 0.33.0 and adjust.
@nvivot Do you have any relations with Datadog or know where we could ask?

Hi @gsmet
Yep i've seen that before going on weekend.
I will submit a request for that and pass through my company support to request them to work on it asap.

Opened issue on their repo.

How would I reproduce this issue from this repo's point of view. I'm trying to understand how the CustomScope class is getting invoked, normally it shouldn't be invoked at all so that caught my attention

@devinsba
The issue here is not at runtime but at compile time.
Not sure if you are familiar with Quarkus, but in native mode it runs on GraalVM.
The build of this extension is currently failing (https://github.com/quarkiverse/quarkus-datadog-opentracing/runs/4614614894?check_suite_focus=true) when compiling the extension in native to be able to run the integration tests in native mode.
During the compilation, there is a scan phase and graal reports that it find the use of an unknown class and therefore report it and stop the compilation.
At this point, there are two options:

either we fix the source code (the reason why i opened the issue on Datadog since it's your source code)
either we use an option in this extension to tell to graal to ignore such unknown class discovery and report it at runtime instead of at build time

Option 1 is by far the best (and should be the priority), but option 2 can be used to unlock the situation. The problem i have with option 2 is that it would potentially break at runtime which is really bad thing.
Now, if you says that this CustomScope should not be used:

why is it here ? what for ? (just for my understanding of DD lib)
is there a way to quick fix this one only since it appears to be only that class that is affected?

Here is what i will do (while waiting for your answer / investigation):

i will add an option to ignore & report at runtime such issue and build the extension with the latest version of Quarkus
test the updated extension on one of my service and run load tests on it to see whether this would have an impact at runtime

So, i have performed some functional and load tests within an application and there does not seems to have any runtime issue while ignoring this reported issue at build time.
But as i explained, this will force users to add the --allow-incomplete-classpath option to their builds, which is not great at all.
@gsmet
For now, i will add the --allow-incomplete-classpath to this extension integration tests configuration to avoid the build to fail for that reason and will follow the fix on Datadog.
I will also add some notes on the documentation to warn about this.
@devinsba
Would be nice if you can find a way to patch the CustomScope inner class to comply with version 0.33.0 without upgrading.
I will keep this issue opened until it's fixed on datadog side.

Another option and probably safer than the --allow-incomplete-classpath option is to downgrade the opentracing library version to 0.32.0 in the applications.
Both temporary solution are provided on the release note here:
https://github.com/quarkiverse/quarkus-datadog-opentracing/releases/tag/1.1.3

The following pull request will fix the issue on datadog library
https://github.com/DataDog/dd-trace-java/pull/3299
Release 0.93.0 should then be compatible with the latest versions of Quarkus.

Thanks for following up :).

Fixed with release 1.1.4


[BUG] : start server on the map isntead of switching it

https://github.com/5stackgg/game-server/commit/7d85873ddb5d0c374b4d5df2989d800c82c09d23


WIP vgsc median joining networks

The clusters have been generated, this PR is just awaiting the hierarchical clusters to be named so we can examine concordance with median joining.

Hi @alimanfoo,
This is ready for review - we will need to come back to which 'non-KDR' clusters/networks to investigate and take downstream to other analyses.

Hi @alimanfoo - this is ready for review


Use cookiecutter hook and tfvar validation to limit service account characters

This PR limits the number of characters which may be used for the service account name to help abide Google service account constraints (link). It might result in some odd looking names so I also added a comment above the entry within the TF to ensure understandability.
Thanks for any feedback!
Closes #17

Thanks @falquaddoomi, I incorporated in your feedback and going to merge now!


link for tx at drop minting

it lead me here

https://assethub-polkadot.subscan.io/extrinsic/0100000cc74fbfe00000

It‘s the same as https://github.com/kodadot/nft-gallery/issues/8857


Updated Ops compatibility list with new api

Replaced  old api
tf.check_numerics
with new api
tf.debugging.check_numerics
in ops compatibility list.

Can you squash these commits please? It doesn't make sense to have 5 commits for a line change and one extra empty line

Sorry @mihaimaruseac !
Actually, I was trying to follow spacing style suggested by editor. Closing this PR because of conflicts in merge.


Puppeteer button click is not working when tests are run in parallel

I use the code below to click the login button, and it works perfectly on a single browser. When the code is executed simultaneously in several browsers the login button is clicked, however navigation doesn't occur in some browser instances.
 try {
      const login = await page.waitForSelector(loginButton, { visible: true });
      await login.click(loginButton);
      console.log('Login button clicked');

    } catch (err) {
      console.log('Login button Not clicked');
     }

Could you please provide the entire script to reproduce the issue? Also, please specify all the version information (OS, node, npm, puppeteer, browser versions).


@mui/system style function type errors and documentation in v5

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
After upgrading to v5 my custom @mui/system style functions started giving error Property 'theme' is missing in type ... on every component created with styled that has the style composed in. After searching in new documentation, I wasn't able to find any mention of style function.
My current workaround is to use a cast that provides the expected type.
export const gap = style({
	prop: 'gap',
	themeKey: 'spacing'
}); as SimpleStyleFunction<'gap'>;

Expected Behavior 🤔
If this is not a but provide info about how to migrate @mui/system's style function to v5. Either way there should be some mention of how to handle this in documentation instead of any mentions of style just vanishing.
Steps to Reproduce 🕹
Sandbox: https://codesandbox.io/s/trusting-robinson-pwgvv?file=/src/Demo.tsx
Steps:

Create custom style function
Compose it to a styled component
TS shows error on usage of that component Property 'theme' is missing in type ...

Context 🔦

Before upgrading I was using multiple custom style functions in my components which are broken because of the update. Any mentions of creating your own style functions disappeared from documentation.
Your Environment 🌎

`npx @mui/envinfo`
System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 3.41 GB / 15.80 GB
  Binaries:
    Node: 12.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
  Managers:
    pip2: 19.2.3 - C:\Python27\Scripts\pip2.EXE
  Utilities:
    Git: 2.33.0. - /cmd/git
  Virtualization:
    Docker: 20.10.5 - C:\ProgramData\DockerDesktop\version-bin\docker.EXE
  IDEs:
    VSCode: 1.60.2 - C:\Program Files\Microsoft VS Code\bin\code.CMD
  Languages:
    Java: javac 11 - /c/Program files/Java/jdk-11/bin/javac
    Perl: 5.34.0 - C:\Program Files\Git\usr\bin\perl.EXE
    Python: 2.7.17 - /c/Python27/python
  Browsers:
    Chrome: 94.0.4606.71
    Edge: Spartan (44.19041.1023.0), Chromium (94.0.992.31)
    Internet Explorer: 11.0.19041.1202

@Haaxor1689 thanks for the report. We updated the style function not to require the theme, but didn't update the typings. This diff should do it:
index 1b4cdd77ff..e1b361a0aa 100644
--- a/packages/mui-system/src/style.d.ts
+++ b/packages/mui-system/src/style.d.ts
@@ -12,4 +12,4 @@ export interface StyleOptions<PropKey> {
 }
 export function style<PropKey extends string, Theme extends object>(
   options: StyleOptions<PropKey>,
-): StyleFunction<{ [K in PropKey]?: unknown } & { theme: Theme }>;
+): StyleFunction<{ [K in PropKey]?: unknown } & { theme?: Theme }>;

In the meantime, you can add generics props on the components in order to fix the type error. See https://codesandbox.io/s/zealous-bogdan-2tjld?file=/src/Demo.tsx

@Haaxor1689
Thanks for the report! I created a pull request to fix this issue.

Thanks for the quick response and fix. What about the documentation though? Was there no documentation in v4 docs either?


Add support for CI and VI

This is exactly what I was looking for. Similar to sublime vim mode.
We just need Change Inner(ci) and Visually select Inner (vi)
Thanks for your great work.

New version 0.5.0 supports ci' ci( .

Wow, just got the update.
Thanks, Now i can switch from Sublime Text.

but not supprt vi( , ciw yet


docs: optionally add a description to plugins

This adds the description field to the nixvimInfo attrs.
If not empty, it is then used in the documentation generation.

IDK if third-party reviews are welcome here, but this lgtm.

Of course they are !
Btw if would encourage you to join our matrix channel to chat about development if you are interested :)


[Question] Page refresh after changing language

Hi, just had this use case and couldn't figure out how I would do this.
Before I turn on locale subpath, I basically just did location.reload() to reload the page after changing the language, but after I turn on locale subpath, I am no longer able to do that, as reloading the current url would simply revert the changed locale. And using Router is only doing a client side router push.
The reason why I needed to reload the page is because I have some locale specific content that gets fetched on SSR, and that content will need to be refetched after the locale is changed, and refreshing the page is the easiest way

One solution I can think of is to get the locale before changing the locale, swapping the old locale in the url with the new locale, and replacing location.href. Seems a bit hacky to me, just wondering if there is a more elegant way

I'm looking for a different solution. Instead to reload the whole page I would like to rerender getInitialProps on language change.
Your issue describes a race condition because you didn't wait for the locale change. Execute window.location.reload() in the callback of the i18n.changeLanguage(locale, cb) and it should work.

Unrelated to this package. Please post on StackOverflow for general React questions.

@StarpTech Thanks for the help that did the work

Unfortunately location.reload() didn't work as I thought it was when locale subpath is used. The old locale will simply be reloaded and set to the cookie after triggering location.reload()

The reason why I needed to reload the page is because I have some locale specific content that gets fetched on SSR, and that content will need to be refetched after the locale is changed, and refreshing the page is the easiest way

@mengqing which version do you use? In the latest version, a locale change will always result in a refresh of getInitialProps.

is there way to change language without reloading whole page, client side only, i.e. react-way?

@denisix

is there way to change language without reloading whole page, client side only, i.e. react-way?

Did you find a way? My shopping cart state gets reset whenever I change language :|

https://nextjs.org/docs/advanced-features/i18n-routing#transition-between-locales


Add: nushell detection

Just a smell addition, for "nushell" to be detected.

Hey! Thank you very much for your contribution! :)

My pleasure, thanks to you for this crate!


Inconsistency on doc Distance Matrix API Service

The Distance Matrix API documentation has a class called DistanceMatrixService on section Build that don't exist in the library.
Could someone fix it, please?

Hum, the class exists: https://github.com/egeloen/ivory-google-map/blob/master/src/Service/DistanceMatrix/DistanceMatrixService.php What version of the library do you use? 1.x or 2.x (the online doc is the 2.x one).

I'm using version 1.x. It'd be good to mention what version the documentation is about.
Thanks.

Fixed by d7d8bd07e099a32afbfe92a91c0b57afe664727a.


⚠ ClamAV has degraded performance

In 2350f47, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: ClamAV performance has improved in 32479d3.


STATS: Re-running program efficiently

This ticket outlines the motivation and proposed strategy behind adding in the ability to re-run the codes efficiently without restarting from scratch everytime. E.g. if a user specifies all of the same input arguments the second time, but the only difference is that the input csv has been expanded to include 2 more months of data, just append to existing output csv (outlined in more detail below) without re-running the entire analysis. In the end, we should only start regenerating outputs from scratch when the user specifies a new spatiotemporal argument (i.e. different bounding box, different grid spacing, different time-span, etc.).
For each new statsclass call, I propose writing the following files to an output subdirectory: (1) the modified pandas dataframe i.e. the primary output CSV (which is currently passed around in memory anyways), (2) the dictionary of user input arguments, (3) a duplicate input CSV, and (4) a CSV record of variogram fits for each given given timeslice and  gridcell.
Once a user relaunches the statsclass, the logic follows as so:

Compare new user inputs with the record of user input arguments from the previous run. If they are the same then continue, if different then generate all outputs from scratch.
Then examine difference between new input CSV and duplicate input CSV from the previous run. If they are the same then continue, if spatiotemporal sampling differs as described above, then re-grid and regenerate the primary output CSV and duplicate input CSV, and restart the variogram analysis. But if the record has just been expanded in time, then just append to the primary output CSV and start off the variogram analysis from where the user had left off.
If no differences are flagged, then just print a message stating input CSV/arguments haven't changed, thus outputs have not been modified.

This is the cleanest logic I could formulate at the moment, and indeed perhaps it would make more sense once I have a working version implementing such proposed changes. But if any of you have specific comments and requested features/adjustments of relevance to these efforts, please discuss them here.
Furthermore, this conceptualization should no longer necessitate the need to separate the stats class from plotting, as if this is executed properly, then the logic of the code should handle such checks and plotting seamlessly under one primary code

Storing a physical dictionary of inputs arguments would not require much overhead. However a clean, yet less transparent alternative would be to generate a unique hash and store it to a hash file that may be referenced vis-a-vis successive user inputs.
Just as a note, from what I've seen it is recommended that such a dictionary of input arguments is to be serialized as JSON before hashing. E.g.:
import hashlib
import json

a={'intputfile':'/path/to/file', 'bbox':'-9 9 10 12'}
print(hashlib.sha1(json.dumps(a, sort_keys=True).encode()).hexdigest())

Any strong feelings one way or the other? I.e. for storing hash files as opposed to a full dictionary of input arguments (which should be very small anyways).

I think an HDF5 file with a specified set of attributes would work well. This is similar to what Mintpy does, where it queries several HDF5 file at each step to decide what to run. It could store the 'intermediate' data such as grid bins, analysis attributes, etc. then the plotting routine could simply query the file.


REFACTOR: Leaf requests information spaghetti

Right now we send the IndexConfig with leaf request.
Ideally, the leaf requests should not require the index config.
The root should use the index config to interpret the user query and send this interpreted query to the leaf.
If index information (schema for instance) is still needed to interpret and execute the query, it should be extracted from the split.
The logic here is that we want to be able to handle change of configurations.
A leaf request should be something that applies to a split.
This also mean that we should probably ship more information within the split.

Pinging @fmassot for awareness.


Update Flowzone to kyle/job-cleanup

Auto-generated by https://github.com/product-os/flowzone/pull/450
Will be closed automatically once the PR is merged.

Auto-closing pull request


Explicitly set contract version and name in examples

Closes #44

Needs #70 to fix the linting errors.


Scrub BoundaryManager TODOs re: Unity 2017.2 MRTP

There are three instances of TODO comments (as well as some disabled code) re: Unity 2017.2 MRTP5.

Assets\HoloToolkit\Boundary\Scripts\BoundaryManager.cs(115):            // TODO: BUG: Unity: configured bool always returns false in 2017.2.0p2-MRTP5.
Assets\HoloToolkit\Boundary\Scripts\BoundaryManager.cs(162):            // But this always returns false with in 2017.2.0p2-MRTP5.
Assets\HoloToolkit\Boundary\Scripts\BoundaryManager.cs(180):            // But this always returns false with in 2017.2.0p2-MRTP5.

MRTK no longer supports MRTP builds. These TODOs should be removed and the code updated, as appropriate.

It has nothing to do with the MRTP builds, it was the last time that feature was tested is all the comments mean.

So we need to re-test those features with other editor versions.

@StephenHodgson, yes. we definitely will need to retest.

Also, our TryGetGeometry calls need to be updated. Unity exposes WMR's boundary with UnityEngine.Experimental.XR.Boundary.Type.TrackedArea as the boundary type, but it's not the default, so we need to explicitly pass it in.


fix: do not lock guest after lock eip, to prevent possible dead lock

这个 PR 实现什么功能/修复什么问题:
修正：锁住eip之后就不锁guest，避免出现死锁

是否需要 backport 到之前的 release 分支:

release/3.4

/cc @zexi @yousong
/area region

Codecov Report

Merging #8361 into master will decrease coverage by 0.73%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #8361      +/-   ##
=========================================
- Coverage    6.12%   5.38%   -0.74%
=========================================
  Files         762     525     -237
  Lines      118376   91669   -26707
=========================================
- Hits         7245    4939    -2306
+ Misses     110476   86321   -24155
+ Partials      655     409     -246

Flag
Coverage Δ

#aFlag
5.38% <ø> (-0.74%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/cloudcommon/db/quotas/errors.go

pkg/multicloud/aws/host.go

pkg/cloudcommon/db/quotas/lock.go

pkg/baremetal/tasks/base.go

pkg/webconsole/command/ipmi_command.go

pkg/cloudcommon/validators/validators_actor.go

pkg/hostman/guestfs/fsdriver/drivers.go

pkg/compute/guestdrivers/aliyun.go

pkg/compute/guestdrivers/zstack.go

pkg/hostman/guestfs/fsdriver/nicteaming.go

... and 228 more

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 db9872e...0466b2c. Read the comment docs.

/lgtm
/approve


Stream Filtering using Lambda Expressions in Java

Proposed title of article
Stream Filtering using Lambda Expressions in Java
Introduction paragraph (2-3 paragraphs):
The Java stream's filter() function allows you to filter stream components based on a given criterion. As a result, this method takes a predicate as an input and returns a stream of result elements.
We will look at how to use the Stream. filter() function in Java while working with Streams in this tutorial. We will also look at how to use Stream Filter in Java and how to deal with checked exceptions in lambda expressions and specific instances.
Key takeaways:
The reader will learn the following;

Overview of Stream Filter in java.
Collection filtering.
How we use Stream.filter().
Using Multiple criterial to filter collection.
Ways of handling exception.

References:
N/A

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

This topic was suggested here -> https://github.com/section-engineering-education/engineering-education/issues/3891. She will cover it in future. Feel free to suggest a new topic.


[Feature]-[800]:Server-side filtering for Tables

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Binding of the data from the Filter fields to the data sources.
Why should this be worked on?
Currently, the filtering is client-side.
Especially with large amounts of data, I use serverside pageination.
But now it would be practical to integrate the data in sql as with serverside pagination. Table.filterJson next to Table.search and Table.pageNo would be really nice.
 Front conversations

@lublak sort is already available. You can bind {{Table1.sortOrder.column}}. Server-side filtering is still missing today

@lublak this might be possible today even on the server side using the onSort event, which can be used to call an api, We also have an internal property {{Table1.sortOrder}} which gives you the column name and the order in which the user is asking you to sort, this is set to null when no column is set on sort.

@Nikhil-Nandagopal do you think this solves the problem? This is not well documented though. cc @Pranay105 @dilippitchika

@somangshu it does but the same needs to be possible for filters as well

@Nikhil-Nandagopal agreed, we have an open issue for that, not yet prioritised, we might we able to get it up once we have the v2 for table.

@Tooluloope I remember you working on the earlier feature set, Any comments on this, What is the effort required? Did we push this back for a reason?

Yes for sorting there is it available (but are we missing the serverside switch like the serverside pagination to disable all client side searching?)
Filtering is still completely missing.

Hey @lublak could you expand on the switch part? You have events called onSearchTextChanged and onSort.
If you bind a query to it, it will be triggered with the events making it server side, if you don't it will be done on the client side.  Is this part of the table events unclear?
Agreed on the filtering part.

@dilippitchika

the Sort switch is also missing

Hey @lublak the reason we have "Server side Pagination" as a switch is because it needs extra properties for it to be configured and used.
For server side sort, we don't have a switch because once you configure the onSort action to bind to a query it is server side sort. You don't need an extra switch for it. When there is no query bound to onSort it uses client side sort.
The switch is only needed for server side if there are some extra properties which are needed to be filled.

@dilippitchika and what about "Enable client side search"? Why is this needed?

@lublak that is used to disable the client-side search when server-side search is applied way so that the client-side does not override the server-side search

@lublak Here's the issue to understand why we added the property
https://github.com/appsmithorg/appsmith/issues/5444

Today, we already expose all the filter properties using Table1.filters, we need to add a new onFilterUpdate action to support this.

@Nikhil-Nandagopal @Tooluloope thanks for the answer :) i understood now.
It's just a bit confusing when it's there for searching and not for sorting. I'm sorry I didn't understand it right away.

@dilippitchika in case there is enough clerity here with what needs to be implemented, Please move this to the backlog and unassign yourself

Action items for this feature

Add .filters into the autocomplete for users to know it can be accessed.
Add a new onFilterUpdate which detects the changes made in the filters and triggers this action.

@somangshu now that we have 2 versions of tables how to uptake this change?

Should this be moved to Table WIdget V2 or remain in Enhancement?

Will check and get back tomorrow, @Tooluloope

@Tooluloope we should do this in V1 as well, checked with @sbalaji1192. Please discuss with him before picking it up.

@dilippitchika considering the previous discussion, can you drop the summary here and add what is required to resolve the actionable, We will resolve this internally.

Action desired behavior for this feature

Add .filters into the autocomplete for users to know it can be accessed.
Add a new onFilterUpdate which detects the changes made in the filters and triggers this action.

@somangshu @Tooluloope please review and move this to product backlog if clear

@dilippitchika instead of a new property, can we just rename "Enable client side search" to "Enable client-side filtering" and use it for both search and filter because I don't see much of a use case to have search on and filter off.

Stats

Stat
Values

Reach
200

Effort (months)
0.5

Will be handled after #9135 release

This is a deal breaker for us, unfortunately. Any ideas when it might come around?

Hey @acron0, The dependency on this have been cleared, but we still havent prioritized this.
While I talk about this internally, can you explain your use case, Maybe we can suggest some workaround.
cc @dilippitchika

[Internal] PRD -https://www.notion.so/appsmith/Supporting-server-side-filtering-445d8f060bf14c5b98e62dcbcd835162

TL;DR
The design task was to accommodate for:

Switching On Server-Side Filtering property
Allowing a Column to be filterable or not.
Filterable Property reflected in Filter Dialog.

Screens Design

Prototype

Hi, is there any progress about the issue? I would like to use it too

Hey @m1ker1n, today we expose a field called as filters in the table widget that allows you to get the filters that are applied and maybe also use that in queries if required.

Hey @m1ker1n, today we expose a field called as filters in the table widget that allows you to get the filters that are applied and maybe also use that in queries if required.

How should I observe filters change to run new query with new parameters?

@m1ker1n apologies for the confusion, discussed this internally and found out that we need an action like onFilterUpdate on the table widget to complete this loop. This will not work as expected otherwise.

@somangshu any upcoming news about the issue in near future

@eyyupguner can you please help me understand what you are looking for.
We haven’t yet prioritized this issue internally.

@somangshu i have implemented the same logic with input boxes for my all columns but its hard to implement if you have lots of tables in your project and hard to manage their names etc.

We created button "apply filters" which takes these filters and handles them. So user must click one more time after he chose them in popup to receive filtrated data from server

@rahulbarwal @carinanfonseca Do we have an ETA for this?

Hey @rahulbarwal  @carinanfonseca  , we'd very much like to utilize your built-in filters and connect them to our APIs for backend functionality - developing our own filters with "select" widgets creates a very high complexity and a UI which is not clean. It adds an additional level of maintenance and a complex UX. Also - this is for the most simple "AND" use case with exact match - for "contains" and "OR" conditions we'll need an even more complicated UI.
Your built-in filters are very user friendly and we'd like to utilize them with server side pagination. Using them today with server-side is unusable since they only filter the current page.
Same goes to other capabilities such as "download", but filters is our current focus.
It'll be very appreciated if you can provide an ETA.
An alternative can be an ability to "fork" your table as a custom component and a full control over its code.
Thanks!

Hello @yonatang-cyera! I would love to have a short call with you about this topic to better understand how critical this topic is for you and to discuss some key points. Is this possible?
If yes, feel free to book a time that works best for you here.
I am looking forward to speaking with you!


how to add marker and polyline between 2 marker

can you please add full documentation how to add marker .  and the line between the 2 markers.  and event event if the marker changes

how to use latitude longitude marker from reactive() in solara


remove trailing commas for functions

They're not supported in ES5, which is tested against in the node
versions included by the styled-components CI. Also disabled an
eslint rule that was conflicting with what prettier was doing.

Cheers for the changes :) I think it’s already covered though by https://github.com/styled-components/styled-components/pull/1376
It adds the configs that should disable conflicting rules. The trailing comma change shouldn’t be necessary though since everything is being transpiled 😊

It matters for the rollup config though, which is evaluated as es5 but
still run through prettier
On Wed, Dec 27, 2017 at 7:03 PM Phil Plückthun<EMAIL_ADDRESS>wrote:

Cheers for the changes :) I think it’s already covered though by #1376
https://github.com/styled-components/styled-components/pull/1376
It adds the configs that should disable conflicting rules. The trailing
comma change shouldn’t be necessary though since everything is being
transpiled 😊
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/pull/1392#issuecomment-354198560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1tflAW_ry6hx9aBvtku_cgrkzXh-ks5tEtrrgaJpZM4RN2MO
.

@probablyuphm that’s true; but we weren’t running it through prettier before. 🤔
Mind checking whether only src is being targeted and fixing it up if it isn’t? 😬 I just merged the aforementioned PR


trajectory state not received for 1.000000 seconds

When I set a new pose in rviz and push the button of plan & execute, the real robotic arm does not move. In a moment, the system said "trajectory state not received for 1.000000 seconds". How to fix it? Looking forward to your reply as soon as possible.

我也遇见这个问题，出现在我在虚拟机内安装了aubo虚拟机，然后ros远程连接，sim:=false,robot_ip:=xxx.xxx.xxx.xxx就会一直报这个问题


[BUG] Doesn't work with Next.js

If I try and use this in a brand new Next.js (11) app, I get a rendering error:
Server Error
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Steps to reproduce:

Create brand new Next.js app: npx create-next-app react-svg-worldmap-test
Install react-svg-worldmap
Add pages\map.js:

import WorldMap from 'react-svg-worldmap';

export default function Map() {
  const data = [
    { country: 'cn', value:<PHONE_NUMBER> }, // china
    { country: 'in', value:<PHONE_NUMBER> }, // india
    { country: 'us', value: 331883986 }, // united states
    { country: 'id', value: 264935824 }, // indonesia
    { country: 'pk', value: 210797836 }, // pakistan
    { country: 'br', value: 210301591 }, // brazil
    { country: 'ng', value: 208679114 }, // nigeria
    { country: 'bd', value: 161062905 }, // bangladesh
    { country: 'ru', value: 141944641 }, // russia
    { country: 'mx', value: 127318112 }, // mexico
  ];

  return (
    <div className='App'>
      <WorldMap
        color='red'
        title='Top 10 Populous Countries'
        value-suffix='people'
        size='lg'
        data={data}
      />
    </div>
  );
}

Start dev server and visit http://localhost:3000/map

Versions:
    "next": "11.1.2",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-svg-worldmap": "^1.1.0"

Hello, Next.js uses SSR, and I did address this issue in #91. However the owner hasn't released a new version yet.
Meanwhile, you need to make this component BrowerOnly.

Your JSX is wrong:
    <WorldMap
        color='red'
        title='Top 10 Populous Countries'
        valueSuffix='people'
        size='lg'
        data={data}
      />

This should work; if it still doesn't, it may be because of SSR (which won't happen in dev because dev is CSR, you can try building your site). I did address that in #91 but the owner hasn't released a new version. So you may have to wrap it in BrowserOnly.

Thanks for the quick reply, @Josh-Cena! The problem was indeed that I wasn't using a named import.
I had the valueSuffix prop correct in my main app, just hadn't fixed it in the boiled down sample that I pasted here.
Super happy that I can keep coding away thanks to your help! 😃

Welcome :D It's okay to close this?


Refactor get_cache_key()

Replace snprintf with std::string constructs
Add documentation for get_cache_key
Remove reimplementation of function block

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

To be eligible for swag, please sign-up for Yahoo Hack Together, if you have not done so, yet.


How does one refer to the library in a native kotlin project?

I'm starting a new project to try and learn kotlin native and have tried to import the ktxml library into a template project (you can see here the commit). However, after using
kotlin {
    …
    dependencies {
        commonMainImplementation("org.kobjects.kxml3:core:0.1.2")
    }
}

instead of the mentioned implementation("org.kobjects.kxml3:core:0.1.2") from the README, I try to sync gradle and get lots of errors, probably because this is not really how you refer to a project (using implementation aborts with Unresolved reference: implementation):
Execution failed for task ':compileKotlinNative'.
> Could not resolve all files for configuration ':nativeCompileKlibraries'.
   > Could not resolve org.kobjects.kxml3:core:0.1.2.
     Required by:
         project :
      > No matching variant of org.kobjects.kxml3:core:0.1.2 was found. The consumer was configured to find a usage of 'kotlin-api' of a library, preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native', attribute 'org.jetbrains.kotlin.native.target' with value 'macos_x64' but:
          - Variant 'commonMainMetadataElements' capability org.kobjects.kxml3:core:0.1.2 declares a usage of 'kotlin-api' of a library:
              - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
                  - Doesn't say anything about org.jetbrains.kotlin.native.target (required 'macos_x64')
          - Variant 'iosArm64ApiElements-published' capability org.kobjects.kxml3:core:0.1.2 declares a usage of 'kotlin-api' of a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':
              - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_arm64' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'macos_x64'
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
          - Variant 'iosArm64MetadataElements-published' capability org.kobjects.kxml3:core:0.1.2 declares a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':
              - Incompatible because this component declares a usage of 'kotlin-metadata' of a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_arm64' and the consumer needed a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'macos_x64'
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
          - Variant 'iosX64ApiElements-published' capability org.kobjects.kxml3:core:0.1.2 declares a usage of 'kotlin-api' of a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':
              - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_x64' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'macos_x64'
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
          - Variant 'iosX64MetadataElements-published' capability org.kobjects.kxml3:core:0.1.2 declares a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':
              - Incompatible because this component declares a usage of 'kotlin-metadata' of a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_x64' and the consumer needed a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'macos_x64'
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
          - Variant 'metadataApiElements' capability org.kobjects.kxml3:core:0.1.2 declares a library:
              - Incompatible because this component declares a usage of 'kotlin-metadata' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
                  - Doesn't say anything about org.jetbrains.kotlin.native.target (required 'macos_x64')

When I tried to simply copy all the project files into mine then everything worked so I guess the instructions are not as clear for newbies:
$ ./gradlew linkDebugExecutableNative && ./build/bin/native/debugExecutable/Kasha.kexe
…
BUILD SUCCESSFUL in 377ms
2 actionable tasks: 2 up-to-date
Hello, Kotlin/Native!
START_DOCUMENT
START_TAG
Hello World
END_TAG
END_DOCUMENT

Hi, sorry for the trouble with the maven artifact.
It had added this quite a while ago and need to set this up again for a project that I am using in a different project and confirm there that everything is working, then get back here.
For now, please use a local checked out copy.

P.S. Which "kind" of native are you working on? Linux or iOS?

Ok.
I'm aiming for a native MacOSX/Windows binary, but running jvm would be fine too, just want to experiment.

I have wired up ktxml to be used in the konsole project and made sure it compiles for iOS, please take a look at the updated README.md...


Add votes key in comments response

Add number of votes in comment http json response

https://github.com/meschac38700/Test-FastAPI/commit/260e83559a70e0baa59785042a5aaa47ec02e1be


the image can not be displayed for ios 14.

the image can not be displayed for ios 14. How to resolve ?
some suggestion :

(void)displayLayer:(CALayer*)layer

insert into the code:
if(@available(iOS14.0, *)) {
        [superdisplayLayer:layer];

    }

But, it did not work.

I also experienced the same situation.

I also experienced the same situation.

你怎么解决的？


[#161146691] Split kick-off wait task from main one

What
Now the automatic kick-off is an opt-in feature[1], and our
environments won't we started unless the developer actively
sets it so.
But now we want to be able to trigger the kick-off to start
the DBs and the deployment without having to wait the
safe sleep time added to prevent all environments starting
at the same time and avoid rate limits.
To do so, we split the two parts: await and perform the kick-off.
The developer can trigger the kick-off at any time of the day.
The only restriction, due how concourse dependencies work,
is that the await-kick-off job has to be execute at least
once since the first bootstrap, but we can accept that.
[1] https://github.com/alphagov/paas-cf/pull/1583
How to review
Code review
Who can review
Not me

LGTM. Merging.


Isosurface: rendering disappears after resizing window

Still exists: require a scene move to bring it back. I suspect there's no repaint issued to the isosurface render.


Linting support

Just starting this for finding out what is needed for linting support... (there was a recent discussion which I can't find anymore). I recall:

Structured output: like json
line numbers.

Guess line numbers would be difficult, since we have only the lxml representation of the tool XML while linting. So how about the XPath?

Question is also if one would rely on the output of planemo lint or call the functions in the tool-util package directly.

So the initial idea about linting in the GLS extension was to reuse as much as possible what planemo lint already does. Many other extensions (like the Python extension) rely on other CLI tools for linting. They usually just run the tool in the background and parse the standard output to get the following basic information for each issue found by the linter:
{
    "line": int,
    "column": int,
    "message": string,
    "severity": string,
}

Since planemo was already integrated to run the tests and display the results directly on VSCode with https://github.com/galaxyproject/galaxy-language-server/pull/110 we just thought of doing the same for linting whenever your tool XML source is saved. But instead of just parsing the standard output of planemo, maybe trying to get the information from a structured output file (ideally JSON but XUnit also was considered, see https://github.com/galaxyproject/planemo/issues/1139) since it will be easier and less error-prone.

Question is also if one would rely on the output of planemo lint or call the functions in the tool-util package directly.

Back then, I had no idea that all this linting functionality was actually part of the galaxy-tool-utils package which we already depend on so I guess directly using this will be much more convenient and faster than actually running planemo lint and then either parsing output or read a file from disk to get the linting information. So I think this is definitely the direction to go.

Guess line numbers would be difficult, since we have only the lxml representation of the tool XML while linting. So how about the XPath?

Yeah, that was one of the main reasons this feature was pushed into the future :laughing: I started using lxml too at the beginning of the project but was frustrated because it was very limited for getting this file positions and also it just didn't work with XML files "under construction", so in the end, I had to use a custom parser that doesn't choke on incomplete or broken XML and also provides accurate document position for each token.
Another concern about line positions is that (I'm not really sure right now) the linting is done after macro expansion, so these positions (if we could actually get them) are relative to the expanded version of the document and not the tool XML original source which is the one in which we need to display the squiggles for the linting errors. I guess if we can get the XPath for each linting error or warning will be of help, basically, anything that helps to point out where the issue is in the document and finally translate it to a [line, position].
@bernt-matthias thanks so much for lighting up the discussion. I think integrated support for linting will be a huge addition to the extension so any help or ideas on that would be awesome to have.

Just found out that element.sourceline is a thing, but you are right this probably won't work with macros.
But also locating an xpath in a tool with macros might be tricky.
I researched a bit what actually happens in planemo lint: https://github.com/galaxyproject/planemo/blob/b96b1bb07726ec64eea7433d0571bdf771639507/planemo/tool_lint.py#L46
calls
https://github.com/galaxyproject/galaxy/blob/38a69b19b55b41e2fc079de94a94eee5c1c6a9f5/lib/galaxy/tool_util/lint.py#L14
which then calls all linters in https://github.com/galaxyproject/galaxy/tree/dev/lib/galaxy/tool_util/linters
The function (lint_tool_source) works with a LintContext object which contains the outputs of the linters (currently only the messages sorted in warn, error, ...). Should be easy to extend this to contain more info like line numbers or xpath (or maybe just a reference to the lxml object causing the linter error ..).

also it just didn't work with XML files "under construction"

Maybe the recover mode might be of help: https://lxml.de/parsing.html#parser-options

The function (lint_tool_source) works with a LintContext object which contains the outputs of the linters (currently only the messages sorted in warn, error, ...) .. but it does not return this object (ie planemo only gets the final status). Should be easy to extend this to make the LintContext contain more info like line numbers or xpath (or maybe just a reference to the lxml object causing the linter error ..). And maybe also return the LintContext

That is starting to sound like a plan :)

Maybe the recover mode might be of help: https://lxml.de/parsing.html#parser-options

I vaguely recall trying that option back then, but it was actually modifying the source XML to try and fix it (or was it beautifulsoup? :thinking: ) so it was even worse :disappointed:. But I think this is ok, we probably don't want to lint other stuff unless the XML is completely well-formed, so the linter on saving will fire only for well-formed documents, that way the Problems tab will first show the syntax errors which are of high priority and then other galaxy tools specific linting issues.

Here is something to play with https://github.com/galaxyproject/galaxy/pull/12978

Waiting for the new version of galaxy-tool-util to be released


imports with baseURL

Hi @taniarascia , as you're moving with Typescript, why not do imports using baseURL. Just a suggestion else would be great for me to work on this project and learn from it, on both client and server side.

Hi there. Thanks for the suggestion. I personally do not like using any import like:
import { PrivateRoute } from 'routing/PrivateRoute'

as it can be ambiguous. However, with moduleAlias and TypeScript paths, you can set up:
import { PrivateRoute } from '@routing/PrivateRoute'

Where @routing redirects to ./src/routing. and that would be more explicit and therefore preferred.

Hi there. Thanks for the suggestion. I personally do not like using any import like:
import { PrivateRoute } from 'routing/PrivateRoute'

as it can be ambiguous. However, with moduleAlias and TypeScript paths, you can set up:
import { PrivateRoute } from '@routing/PrivateRoute'

Where @routing redirects to ./src/routing. and that would be more explicit and therefore preferred.

So we change it moduleAlias or we should close this PR to keep what it's already setup?

I think the current setup is fine since it's so small and simple, moduleAlias would be a step if the app was a lot bigger, but it's kind of annoying to set up for both client and server, since it needs to be written in 4 places(Jest, ESLint, TSConfig, package.json).


Naming clash

I posted this on twitter but I figured a GH issue was much more conducive for discussion
The project seems like a nice idea - a framework for plugins is nice!
However the name is very confusing in my opinion (and based on the likes on twitter - others agree too).

tsslint is just one character different to tslint and reads like a typo.
It's also pretty similar to typescript-eslint which is often abbreviated to ts-eslint or tseslint - again tsslint looks like a typo.
tsslint is very similar to eslint

Given you've just announced this project and it's in its very, very early stages - now is the best time to look to choosing a new name. Disambiguating this project and making it its own, distinct thing would be good to clarify things and help establish its own ecosystem.

Now this project has been renamed to tsl. 🙌

Hi @johnsoncodehk was there a reason you undid this in june?

I find that "tsl" is not a good project name, naming with that word makes this project almost unrecognizable.


standard-library version: 1.3 or 1.6 ?

In Readme :
git clone https://github.com/agda/agda-stdlib.git --branch v1.6 --depth 1 agda-stdlib
But if we use
 git clone --depth 1 --recurse-submodules --shallow-submodules https://github.com/plfa/plfa.github.io plfa
It will switch to 1.3.

Thanks. Wen will need to comment, it may take her a while to get around to it.

I believe it should be 1.6, but if either works, that should be fine as well.
We're planning to upgrade shortly either way, and this'll be fixed in the process.


feat: 👍 prepare API definitions

Describe the PR
To close #24
Define in OpenAPI YAML format the external APIs that will be used in YomuTube.
Screenshots
(T. B. D.)
Detail of the change
(T. B. D.)

[x] YouTube Data API v3
[ ] Google Birds API

Anticipated impacts
(T. B. D.)
To reproduce
See ./api.
Appendix
(T. B. D.)

Summary by CodeRabbit

Documentation

Updated the recommended extensions list to include "42crunch.vscode-openapi" for enhanced API development support.

Chores

Enhanced editor configuration by adding new file associations for better syntax highlighting and file recognition.

@coderabbitai help


Error: Dart library 'dart:ui' is not available on this platform

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I create the Application using flutter create command in cmd
in vs code
I didn't write any code yet and if I run it I have this error

Expected results
run successfully
Actual results
Error: Dart library 'dart:ui' is not available on this platform
Code sample
Code sample
[
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a blue toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        //
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        //
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          //
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}
]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[[log .txt](https://github.com/flutter/flutter/files/12241468/log.txt)
]

Flutter Doctor output
Doctor output
[[√] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.22000.2176], locale en-US)
    • Flutter version 3.10.6 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (3 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\lenovo\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2022.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)

[√] VS Code (version 1.80.2)
    • VS Code at C:\Users\lenovo\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.70.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22000.2176]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 115.0.5790.110
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 115.0.1901.188

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.]

@DanTup

In the terminal it shows that the dart command was used to try and run the file. Assuming you didn't do this manually, my guess is that you have Code Runner installed and you are clicking the "Run" button that it adds, which does not know how to run Flutter applications.
I've filed https://github.com/formulahendry/vscode-code-runner/issues/674 to see whether Code Runner could be updated to handle this better (perhaps by hiding its own Run button for Dart/Flutter projects) but in the meantime you'll need to use the little drop-down arrow next to that button to choose the Run/Debug entries added by the Dart/Flutter extension.
Alternatively, you can start the app by pressing F5 or clicking the Debug link above the main() function, or click the Run -> Start Debugging menu entries.

Thanks for your input @DanTup.

I uninstalled the code runner
still, nothing changes

@deemKhlaed can you provide an updated screenshot of what you see, and confirm exactly how you're starting the app? What are you clicking/typing that triggers this error?

I clicked on debug

Thank you very much
It works on an emulator but it is very slow.

Thanks @DanTup
Hi @deemKhlaed. By being slow, I guess you mean the time it takes the app to come up which might be because its first run. You can try running on a real device as well and all should work very fine.
Closing this as all seems to be working fine now, if you disagree, kindly comment and I'd reopen this.
Thank you!


Update conanfile.txt for conan 2.0

Addressing issue described here: https://github.com/zethon/CCCBTemplate/issues/3

@makru86 I just now noticed this PR was even opened. I will look and merge soon!


Update DetailsComponent summary to be a slot

We wanted to have btn-sm as our trigger to DetailsComponent, but the button was too strict and didn't accept any changes.
This PR updates the summary to be a slot that could either be a ButtonComponent or a BaseComponent

I liked this idea so much I wrote my own implementation of it before finding this pull request. 😅 See https://github.com/primer/view_components/pull/57.
I opted to make both summary and body into slots instead of content areas; I was thinking slots were going to replace content areas eventually. May I ask why you kept body as a content area?

@cheshire137 @joelhawksley I think we reached a stable version here, do you mind taking a final look at it? :)


Add support for torch.set_detect_anomaly

What does this PR do?

This carries forward #9175 which has gone stale. I'm creating a separate PR because the v1.5 release is coming soon, and I'm unsure whether the OP of #9175 has time to address the reviews before the release.
Fixes #8313
Note to reviewers: This intentionally does not deprecate terminate_on_nan. To ensure this PR only does one thing, I will create a separate PR to deprecate terminate_on_nan  (https://github.com/PyTorchLightning/pytorch-lightning/pull/9849)
Does your PR introduce any breaking changes? If yes, please list them.
No

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Let's keep #9175 and merge it after this one with the remaining changes? I'll assign myself to update the PR if it's ok.


Long project name causes policy problem

User Story
Project ids can be up to 64 characters.
Policy ids can be up to 64 characters.
That presents an integration problem: Creating a project x begets three policies, x-project-owners, x-project-viewers, and x-project-editors.
So if x is longer than 48 characters then you cannot fetch the project.
On the command-line:
$ curl -sSkH "api-token: $TOK" -H "" "https://a2-dev.test/apis/iam/v2/policies/p123456789p123456789p123456789p123456789p123456789p123456789-project-viewers"
{
  "error": "invalid GetPolicyReq.Id: value does not match regex pattern \"^[a-z0-9-_]{1,64}$\"",
  "code": 3,
  "message": "invalid GetPolicyReq.Id: value does not match regex pattern \"^[a-z0-9-_]{1,64}$\"",
  "details": [
  ]
}

On-screen:

Definition of Done
Perhaps limit project names to 48 characters...?
Demo Script / Repro Steps

oh jeez, good catch!

we should probably do this with team names too, since we will be auto-generating the teams as well soon.

notes from standup 04/06

verify that we can update project names with more than 64 characters
limit project ids to 48 characters
re-think validation on fetch
do not worry about anyone who has already created a project id with more than 48 characters


req: add this workflow

Hi,
Not sure if this is the approprite method to request additions to your repo, but the workflow shared here https://www.alfredforum.com/topic/11424-how-do-i-call-for-the-icloud-drive-folder/?tab=comments#comment-62085 could use a home on the repo.

Thank you for the interest, but this repo is for Workflows that I made to help the community. Supporting other people’s Workflows wouldn’t make sense. Not only I it something I can’t do (the code isn’t mine), it’s not something I want to do (I don’t want to take responsibility for malicious actors, or for keeping their code alive).


How to run faster when the map is completely known?

Hi, I have read the paper about this trajectory planning algorithm. I'd like to figure out how to run the faster simulation in ros, when the map and obstacles are completely known. Is there any file or code need to be modified? Thanks for your time!

Hi @YoungCapta1n,
You simply need to publish in the global_mapper_ros/occupancy_grid topic the sensor_msgs::PointCloud2 with the known map. and then the topic global_mapper_ros/unknown_grid should be an empty sensor_msgs::PointCloud2
Hope this helps


Router inserts into outlet second instance of main-menu

[original by @DemiusAcademius, copied from https://github.com/vaadin/flow/issues/8989#issuecomment-693193337]
I use client-side Vaadin router and found small issue.
I use path
{ path: '/(.*)', component: 'main-menu' } for fullscreen menu.
If router show menu for path /ui/billing/production/indications (There is no component for this path yet ) and I use
Router.go("/ui/billing")
for update path in chrome
Router inserts into outlet second instance of main-menu

My client-side code example in https://github.com/sia-interface/common-frontend;
routes in src/app/routes.ts
RouterListenerService in src/app/core/internal/services/router-listener-service.ts
router outlet in component src/app/core/internal/components/main-component/advanced-router.ts
main layout in component src/app/core/internal/components/main-component/main-layout.ts


Implemented an XML serializer

The user can now post data as an XML string or let the serializer parse it to generate a valid XML.
Fixes #14.

Coverage remained the same at 100.0% when pulling f35789f8c9dac78c735f607a714b1b9a28c6c909 on xml-serializer into 2b91ca9fb5bec159b7a6cfec93c3a761e4297a03 on master.

Coverage remained the same at 100.0% when pulling f35789f8c9dac78c735f607a714b1b9a28c6c909 on xml-serializer into 2b91ca9fb5bec159b7a6cfec93c3a761e4297a03 on master.

Coverage remained the same at 100.0% when pulling f35789f8c9dac78c735f607a714b1b9a28c6c909 on xml-serializer into 2b91ca9fb5bec159b7a6cfec93c3a761e4297a03 on master.


Knative (0.21) - though event retries configured to be linear, happening exponentially

Describe the bug
With the latest Knative - 0.21, we see that event retries are following Exponential pattern, though backOff Policy is configured to be Linear.
Our channel is a KafkaChannel and Implementation is of type Consolidated.
Retries are configured on the Channel.
Expected behavior
Event Retries are supposed to happen at the fixed interval that was defined in the channel Spec.
delivery:
backoffDelay: PT15S
backoffPolicy: linear
retry: 28800
But we see them happening as if, back off policy was configured to Exponential.
To Reproduce
Configure event retries as above and configurations as specified above.
Knative release version
Knative 0.21

/assign

remove-lifecycle stale


Search settings in control panels are weird

Tested on volto.kitconcept.com

This is how the screen looks like in Plone classic:

The problem is that the way the information is displayed in Volto is misleading. The readable messages are the complete oposite of what the selected values are actually doing (they act as NOT filters)

Wow, that is really confusing. This text comes from https://github.com/plone/plone.base/blob/main/src/plone/base/interfaces/controlpanel.py#L997
In Plone 5 the screenshot you showed from Plone classic is accurate, and that control panel inverts the selected types when saving, so the existing text is accurate. But in Plone 6 classic, it's a simple multi-choice selection of types not searched, and so the text is wrong there too:

So I'd suggest we simply update the field's title and description to match the UI in Plone 6...
Suggested title: Types Excluded from Search
Suggested description: Choose content types that will be filtered out when searching the site.

haha, wait, I accidentally was looking at the Plone 6 volto demo site when I took that screenshot

Okay, yeah, Plone 6 classic still has the UI that inverts the selection so that the user is choosing which types ARE searched rather than which types are NOT searched.
So we can't use the same text for the field and have it be right in both places.
Probably the simplest solution is to change the classic control panel to remove the inversion logic so it is also choosing types not searched. It doesn't seem like a big UX problem to change it unless I'm missing something.

Fixed in  plone/Products.CMFPlone#3694 and https://github.com/plone/plone.base/pull/24


GEODE-9000: Added logic to avoid NPE during processing Network Partition

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@jujoramos I added a unit test


pick up some easy-to-fix lint warnings

@facebook-github-bot shipit

Thank you for the PR.

no problem :)

merged


chore: refactor workspace members api

Description

Refactor getWorkspaceMember service and api call to introduce a new DTO class to be used in the EE version.

Fixes #17890
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Since no functionality has changed, this doesn't require any new test case.

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=08b4ff9


Added ability to set the escape character in CSV extractor.

Hello again,
A lot of programs use different separators for csv (I personally encountered after I tried to import a csv from tableplus) The default for php is a backslash but it would be nice to be able to set, it this pr solves that.

Awesome, looks good! I think we need to validate that the escape char is non empty to appease Stan though,

Thanks for the fast reply, fixed!

Looks good! We can Ignore PHP 8.1. on MacOS CI run since it's not our issue. Thanks again!


Upgrade MetadataView in web UI to style EML 2.2.0 features

Our MetacatUI MetadataView will need to be upgraded to display all the new data paper layout features built into EML 2.2.0.
This will be focused more on displaying inline images, content formatting, etc.

@amoeba added markdown rendering to the MetadataView in https://github.com/NCEAS/metacatui/pull/1034


Fix issue with named queries, for now just use unnamed

[WIP] still need to update readme and chagelog
This is big change, here we've done following:

Switched to graphql-client which will provide us #2 and also better error handling and also we can use responses with . notation so we can do something like response.data.invoices.first.fee_in_cents
We added named queries in #13 which simplified how we create queries and later parse them, it seems Graphql::Client can't parse named queries and doesn't like the generated AST, since we are not really using the name of the query and currently we don't support query variables its safe to not support name and for now we can just do

client.query do
  query do
    invoices(id: [1]) do
      id
      fee_in_cents
    end
  end
end

Follow up

We are fetching schema inefficiently, we can download and reuse it and have task for reloading it if needed
I think we should rename Graphlient::Client.query method to Graphlient::Client.execute word query is little overloaded in this context.

@dblock @ashkan18 Quick question: is it possible to name queries? I saw the other PR (#13) introducing that behavior and this which (somewhat) removes it again.
Thanks

Reading the description of this PR it sounds like that answer is "no" @antonengelhardt


release 0.7.46

Codecov Report

Merging #70 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #70      +/-   ##
=========================================
+ Coverage    1.95%   1.98%   +0.02%
=========================================
  Files         127     117      -10
  Lines        6034    5947      -87
  Branches      613     614       +1
=========================================
  Hits          118     118
+ Misses       5911    5824      -87
  Partials        5       5

Impacted Files
Coverage Δ

...dmsexplorer/viewmodel/ServerListActivityModel.java
0% <ø> (ø)
:arrow_up:

...net/mm2d/dmsexplorer/settings/SettingsStorage.java
0% <ø> (ø)
:arrow_up:

...lorer/domain/model/control/MediaPlayerControl.java
0% <ø> (ø)
:arrow_up:

...sexplorer/domain/model/ExploreListenerAdapter.java
0% <ø> (ø)
:arrow_up:

.../mm2d/dmsexplorer/domain/model/ThemeModelImpl.java
0% <ø> (ø)
:arrow_up:

...rer/viewmodel/adapter/ImageViewBindingAdapter.java
0% <ø> (ø)
:arrow_up:

...xplorer/domain/model/control/VideoViewControl.java
0% <ø> (ø)
:arrow_up:

...2d/dmsexplorer/view/adapter/ServerListAdapter.java
0% <ø> (ø)
:arrow_up:

...in/java/net/mm2d/dmsexplorer/view/DmcActivity.java
0% <ø> (ø)
:arrow_up:

...main/java/net/mm2d/android/upnp/cds/CdsObject.java
0% <ø> (ø)
:arrow_up:

... and 106 more

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 5f96f39...1e54ae7. Read the comment docs.


PHP extensions (V8Js) don't work

Info:

Docker version ($ docker --version): Docker version 17.09.0-ce, build afdb6d4
Laradock commit ($ git rev-parse HEAD): 05879bdda24080f5eed8e1ff4dc864bcf0034414
System info (Mac, PC, Linux): PC
System info disto/version: Windows 10 LTSB

Issue:
When I use
$ docker-compose exec workspace bash
$ php -m

And I see 56 PHP modules.
But when I use get_loaded_extensions(); in my php file with nginx only 36 modules are working there.
How can I use v8js for examle im my php files?

I have the same issue, the extension is not installed at all.

Extension is not installed at all +++


Feature Request: Logseq fetch captured content automatically (instead of just manaual)

Hey, small request:
Today, to fetch the things I've captured on Phonetonote, I need to manual press:

Is it possible to have a setting to set an automatic pull (every 30 sec/ 1min/ 2min/ 5min/ 15min/ 60min) to pull things into Logseq? That's how it is in Roam Research, but not in Logseq.
(I constantly forget to manually press it, when processing my inbox)

hey @glicksman, v0.3.0 now has an option to auto sync (when logseq opens and every 90 seconds afer). update the plugin and you should be good to go. there's some other nice customization options you might be used to from the roam plugin available in logseq now too. you can see them all in the plugin's settings, which will now open in a much more user-friendly modal!


cURL error 3: Bad URL, colon is first character

Actual Behavior
Mapping in backend and ssh not possible
Errors
Notice: Undefined index: scheme in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: host in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: scheme in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: host in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: scheme in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: host in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: scheme in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
Notice: Undefined index: host in /home/tweeto46/public_html/custom/plugins/PlentyConnector/Adapter/PlentymarketsAdapter/Client/Client.php on line 277
[2018-12-25 15:20:41] plentyconnector.ERROR: cURL error 3: Bad URL, colon is first character
Steps to Reproduce
php bin/console plentyconnector:mapping

your api url seems wrong, please use something like https://your-plenty-domain.de


Workflow marked as finished before tempalte level onExit hooks fisnished when stop workflow

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

Workflow does not wait for template-level onExit hooks to be finished when stopping

onExit hooks for template-level onExit hook is marked as Running Permanently

This might be the root cause of flakiness of TestStopBehavior

https://github.com/argoproj/argo-workflows/blob/d0588ea092012c36ce06f44b008dc057bdf72154/test/e2e/signals_test.go#L27
https://github.com/argoproj/argo-workflows/actions/runs/6288766349/job/17074596262?pr=11839

Condition "to be done" met after 9s
Checking expectation stop-terminate-wpvxk
stop-terminate-wpvxk : Failed Stopped with strategy 'Stop'
    signals_test.go:44:
        	Error Trace:	/home/runner/work/argo-workflows/argo-workflows/test/e2e/signals_test.go:44
        	            				/home/runner/work/argo-workflows/argo-workflows/test/e2e/fixtures/then.go:68
        	            				/home/runner/work/argo-workflows/argo-workflows/test/e2e/fixtures/then.go:43
        	            				/home/runner/work/argo-workflows/argo-workflows/test/e2e/signals_test.go:36
        	Error:      	Not equal:
        	            	expected: "Succeeded"
        	            	actual  : "Running"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1,2 +1,2 @@
        	            	-(v1alpha1.NodePhase) (len=9) "Succeeded"
        	            	+(v1alpha1.NodePhase) (len=7) "Running"

        	Test:       	TestSignalsSuite/TestStopBehavior
=== FAIL: SignalsSuite/TestStopBehavior

Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: stop-terminate-
spec:
  entrypoint: main
  onExit: exit
  templates:
    - name: main
      dag:
        tasks:
          - name: A
            template: echo
            onExit: exit-template

    - name: echo
      container:
        image: argoproj/argosay:v1
        command: [ sleep ]
        args: [ "999" ]

    - name: exit
      container:
        image: argoproj/argosay:v1
        command: [ sleep ]
        args: [ "10" ]

    - name: exit-template
      container:
        image: argoproj/argosay:v1
        command: [ sleep ]
        args: [ "20" ]

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

Wow nice find and good hypothesis! I didn't realize there were two hooks on that Workflow, but that could make a lot of sense if that is root cause. Fairly edge case edge case.
If the controller has marked it as stopped and moved on, then the NodeStatus never gets updated 🤔

Yeah. Truely edge case which might not problem for our users but for us suffered from flakiness :)
For workflow-level hooks, controller will wait for NodeStatus:

https://github.com/argoproj/argo-workflows/blob/6399ac70619ff037793b773d44131c7a1f9e7fb6/workflow/controller/operator.go#L430
But not for template-level hooks for dag?:
https://github.com/argoproj/argo-workflows/blob/6399ac70619ff037793b773d44131c7a1f9e7fb6/workflow/controller/dag.go#L290

same questions. stopped workflow was archived with dag onExit hook running. And the archived worlflow cannot retry again because the running exit hook. Is there any fix processing?

I'm afraid there is no fic processing currently.

Thanks for sharing your use-case.
Can we get over this by checking NodeStatuses recursively? I might know the related logic, so I'll look into it.


accept other raw formats in rows.query()

In support of the of new query inputs for the /v1/rows endpoint that were implemented under internal bug 55547....
Add a constructor function that wraps a raw query with an object that declares its format to be an Optic AST as a stringified or JavaScript literal JSON object, SQL as a string, SPARQL SELECT as a string, or a QBV XML plan as a string.
Modify the rows explain(), query(), and queryAsStream() methods to support any of these wrapped raw queries.

I see from the unit tests that this was implemented but never sent to test:
https://github.com/marklogic/node-client-api/blob/develop/test-basic/rows.js#L159

Tests and QA sanity tests are working as expected.


Fix sorting of highest

Hello again @jonschlinkert,
Sorry for the back and forth, now I think it's working as intended.
I didn't have time to figure out a test case but this definitely fixes my use case.
0.7.2 please ? :p

done! thanks again!