Fix argument name in README.md, section "extractor arguments"

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information
Fixes argument name in README.md, section "EXTRACTOR ARGUMENTS", where player_client was misspelled player-client. It still appears to work (short logs below), but it's inconsistent with the rest of the page.

Extractor argument player_client for extractor youtube was mis-punctuated as player-client. This still works to call the argument on the command line, but it's inconsistent with the rest of the docs, and youtube.py states its canonical name with the underscore.
$ yt-dlp https://youtu.be/dQw4w9WgXcQ --skip-download --extractor-args "youtube:player_client=ios"                               [youtube] dQw4w9WgXcQ: Downloading webpage                        [youtube] dQw4w9WgXcQ: Downloading ios player API JSON            [youtube] dQw4w9WgXcQ: Downloading m3u8 information               [info] dQw4w9WgXcQ: Downloading 1 format(s): 248+140

is the same as
$ yt-dlp https://youtu.be/dQw4w9WgXcQ --skip-download --extractor-args "youtube:player-client=ios"                               [youtube] dQw4w9WgXcQ: Downloading webpage                        [youtube] dQw4w9WgXcQ: Downloading ios player API JSON            [youtube] dQw4w9WgXcQ: Downloading m3u8 information               [info] dQw4w9WgXcQ: Downloading 1 format(s): 248+140

Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[x] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Both are supported in CLI. The canonical names have _ since - does not work in API. But I originally wrote the example using - intentionally since that is what is commonly used for switches in CLI. Instead of changing the example, I'd rather add a line explaining that both are supported


Improve formulation of master branch description

In the CONTRIBUTING.rst the description of the master branch as required target branch is not very clear and has a typo. I tried to improve the sentence.

Contributor (creator of pull-request) checklist

[ ] ~Tests updated (for new features and bugfixes)?~
[ ] ~Documentation updated (for new features)?~
[ ] ~Issue referenced (for PRs that solve an issue)?~

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Documentation preview 📚: https://metatensor--462.org.readthedocs.build/en/462/

Thanks @Luthaf and @jwa7 for the review! 🎉


feat: extend information returned by GET /stamps

On top of the current information, the returned data are
extended by: Label, Depth, Amount, and CreatedAt.
#1971

This change is

@agazso


allow more flexible math between Rainbow objects

Closee #236 .

Now, r1/r2 should work, even if r1 and r2 have slightly different wavelength and/or time arrays. It will throw a warning if they don't match exactly, but it will still do the calculation and return a new Rainbow.


Add Yr Weather sensor device classes

Breaking Change:
None
Description:
The yr weather monitoring component should set device classes for the sensors it reports.
This is usually not obvious but can be seen in the UI if humidity is monitored.  Instead of the correct humidty symbol (raindrop with '%'), a generic eye symbol is displayed.
In addition, I have referenced the unit constants where they exist.
This PR adds the device class to each sensor where a suitable one exists.
Checklist:

[x ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]

Hello @davet2001,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

a2b7d2b37205198fed2c87f7bcb7d11c9b5493c4 - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @davet2001,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

13a79d0b09ca245fb68b573f50bdf861ee74db64 - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.
a2b7d2b37205198fed2c87f7bcb7d11c9b5493c4 - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @davet2001,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

d5e19e321a489aa81ffef720dc046a6e73ced10a - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.
13a79d0b09ca245fb68b573f50bdf861ee74db64 - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.
a2b7d2b37205198fed2c87f7bcb7d11c9b5493c4 - This commit has something that looks like an email address (davet2001@github.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Ok.  What a mess.  Obviously got some email address wrong somewhere.  Will delete the PR and create a new one.


Feature: Changed image endpoint to allow image type

The image type is needed so we can load category images and product images from magento.
Related PR in Vue-storefront PR 3224

When i am on it should i change the logic for it so we can proxy every image that is under /media in magento?

Thanks this is really nice. The only thing is that it should be backward compatible

By the way - can you please check if the SHARP library used for thumbnails is caching images properly? I heard it's not - which can be a huuge performance bottleneck. All the thumbnails in the end should've been cached and proper http headers should beeen set (it can be configurable the time to live for http headers and for disk cache)

By the way - can you please check if the SHARP library used for thumbnails is caching images properly? I heard it's not - which can be a huuge performance bottleneck. All the thumbnails in the end should've been cached and proper http headers should beeen set (it can be configurable the time to live for http headers and for disk cache)

I have just checked the documentation for SHARP and the only caching it has is libvips' operation cache. So for a real caching of the images we would need to have like a config value with a time, maybe an endpoint to remove cached images  and a location where we want to save the images.
Here I would say redis or filesystem could be used, both then maybe with an limit of size when it is not to hard to implement.
What do you say to that solution? @pkarw

Makes sense. By default It should probably be just the ‚/tmp’ disk cache - this is how it was done before introducing sharp
Thanks!

This will increase the performance a lot!

This now getting closed as we don't need this and for the caching there is now this PR where I need some feedback of what can be improved.


[merge after https://github.com/openshift/odo/pull/2009] change .gz to .tar.gz in docs

What is the purpose of this change? What does it change?
change .gz to .tar.gz in docs.
This is a follow up PR after https://github.com/openshift/odo/pull/2009 as it changes the doc references.
As per https://github.com/openshift/odo/pull/2009#issuecomment-523481624
Was the change discussed in an issue?
part of #1994
How to test changes?
check the docs for the change

/test v4.2-integration

quick docs fix
/approve
/lgtm


Shouldn't the form action be configurable?

If a user goes to a specific page for the first time, the consent form will POST to that url, so in order to work all routes have to accept POST.
Wouldn't it be better to have a configurable path for the form action?
And have the save action point to a controller action instead of the listener building the form on every request?

That's indeed a valid issue I haven't thought of. I'll make these changes when I get the chance

I have cloned your repo and made the changes already, I jusst need to clean up and do a PR if that's ok.

That would be great, thanks!

Hi All, Any progress on the PR? Thanks

Hello, and thank you for your work !
Just had the same problem. I'd love an update on this issue :)

Same here.

PR has been merged, thanks for the contribution!


Cross-platform support

I found this module and tried to use it.
However I am using Powershell 7 with macOS and there the DNS Client module is not available that contains Resolve-DnsName cmdlet.
I found that there is a cross-platform DNS client module in the powershell gallery
https://www.powershellgallery.com/packages/DnsClient-PS/1.1.0
Would it be possible to make this module compatible with this module and use it if DNS Client Module is not available?

Hi @joergrenn,
Thanks for this issue.  I will go through it and see if it is possible to make the script cross-platform.I will go through it and see if it is possible to make the script cross-platform.


Catch exceptions on sending data/close

On IO error we pessimistically assume that we're in a bad state and
fail the socket. This is the only practical option to ensure invariants.
We must catch here otherwise the exception bubbles up leaving the
socket in a bad state but the application doesn't get notified. This
was the root cause of running out of connections when we should not.
Why do we get IO exceptions? Because undertow is badly designed. If
the client exits quickly it closes the TCP socket before we've had a
chance to gracefully close the muxed socket, websocket, etc. This
should be fine, it's half-closed and so we should be allowed to send
our closing messages even though the client is not reading them. But
undertow throws exceptions in this state even though there's nothing
exceptional about this.

This takes care of the infamous:
Exception in thread "pool-3-thread-1" java.nio.channels.ClosedChannelException

or
java.io.IOException: UT002002: Channel is closed

This was a harmless race but turns out we weren't handling the exceptions well and this was messing up the socket accounting, wrongly running us out of available connections, not logging, etc.

Nice! LGTM


move Twitter app from whit537 account to Gratipay account

Twitter's contact doesn't have a relevant funnel. Do they have a support email address?

I sent a mail to<EMAIL_ADDRESS>Hasn't bounced yet. :-)

Oh well. :-/

https://twittercommunity.com/t/how-can-i-move-a-deployed-app-to-a-different-developer-account/13823

I submitted transfer requests for both the gratipay and gratipay-dev apps.

re: Gratipay:

For security reasons, we can only process this request if the email address you’re using to file this ticket belongs to a domain affiliated with the organization which registered your application. Could you please refile or respond to this ticket from a company account?

and re: gratipay-dev:

Thanks for reaching out. For security purposes, we require that developers write in from the Twitter account and email address that currently owns the API key. Please file a new request from that account.

I replied to both cc'ing<EMAIL_ADDRESS>and then replied from there. Hopefully that's sufficient.

https://gratipay.freshdesk.com/helpdesk/tickets/1586
https://gratipay.freshdesk.com/helpdesk/tickets/1587

Re: gratipay-dev:

Thank you for writing in. We have transferred ownership of the app to the designated account.

Didn't receive anything re: Gratipay, and gratipay-dev is still showing up under whit537 and not Gratipay.

Thanks for the update. However, I'm still seeing gratipay-dev connected to @whit537 instead of @Gratipay. Is there a time lag for this transfer?

Time lag. Check again?

Bump. Can you please help me move the Gratipay app from @whit537 to @Gratipay? Thanks! :-)

D'oh!

Hello,

You tried to update a case that has been closed. Please submit a new case at http://support.twitter.com/forms. You can also visit our help center at http://support.twitter.com for self-help solutions to common problems.

Thank you!

Wait so they closed it without responding or doing anything?

@clone1018 Sort of. They moved gratipay-dev but ignored Gratipay. :-/

I submitted a new transfer request.

Yea, decomposition is the stuff that modern trackers lack.

Thank you for writing in. We have transferred ownership of the app to the designated account.

Confirmed, and signing in with Twitter still works. Huzzah!

!m @whit537


[TC-IDM-6.1]-SDK support required for test step 12  to read event Interaction from TH to DUT

Test case ID
[TC-IDM-6.1] Events Read Interaction from TH to DUT
Issue:-
As per Test-Plan, test step 12 is expecting to Set or Indicate the event number less than
the EventMin field in EventfilterIB.  Do we have the SDK developed to support these steps?
If it is, please share the verification steps for the same.
Test-Plan Reference:-
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/interactiondatamodel.adoc#tc-idm-6-1-events-read-interaction-from-th-to-dut
Spec Reference
https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/data_model/Interaction-Model.adoc#event-information-blocks-and-paths

https://github.com/project-chip/connectedhomeip/pull/16867 has landed for this purpose.


Migrate TDWG site to new logo and brand

TDWG presented a new brand at the 2022 conference. The site should be migrated. Contributions are most welcome.
Main website theme

[ ] Integrate blue #043B58
[ ] Integrate green #709147
[ ] Make sure links are readable in text
[ ] Add logo to footer

Satellite website theme

[ ] Integrate blue #043B58
[ ] Integrate green #709147
[ ] Make sure links are readable in text
[ ] Add logo to footer

Working on it 👌

This is a version with only the green and blue. The green makes links hard to read in text, so they need to be underlined:

Alternatively, we use a brighter (closer to original orange) colour for the links, which then don't require underline:

Feedback welcome

I like the orange on linked text -- enhanced contrast improves readability!
On Tue, Oct 18, 2022 at 5:22 AM Peter Desmet @.***>
wrote:

Feedback welcome
—
Reply to this email directly, view it on GitHub
https://github.com/tdwg/website/issues/462#issuecomment-1282298367, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKZUDOSJWIJMRPJAVLFAWLWD2JATANCNFSM6AAAAAARH3INEU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have tested the green link and orange link versions on https://pilestone.com/pages/color-blindness-simulator-1# and both work fine.
Note that adding orange to the mix makes it a bit more challenging to have a consistent theme though. 😄

I've also experimented with an another theme. Here I have not underlined the green links, how unreadable are they?

Thanks, Peter!
The green links on white are very readable.  I think the green links on a
dark background (e.g., over the banner image at the top) were hard to
read.  Would you be inclined to washout (de-contrast) the banner image?
Curious to hear what others think of all these options.
-Stan
On Thu, Oct 20, 2022 at 12:02 AM Peter Desmet @.***>
wrote:

I've also experimented with an another theme. Here I have not underlined
the green links, how unreadable are they?
[image: Darwin-Core-TDWG (2)]
https://user-images.githubusercontent.com/600993/196878687-d2bbd180-d85a-47b6-bc09-c1d76ff7c174.png
—
Reply to this email directly, view it on GitHub
https://github.com/tdwg/website/issues/462#issuecomment-1285042229, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKZUDPUSDWESKUFLC75UMDWEDVBVANCNFSM6AAAAAARH3INEU
.
You are receiving this because you commented.Message ID:
@.***>

Ah, if you think the green on white (in regular text) works fine, then it's fairly easy to use another approach in the theme for links on dark. I suggest white underline for those:

The advantage is that we don't have to introduce orange then.

I'm all for washout the background and leave the colors as they were.I'd say these images are too dark and taking prese(de)nce from our content.
Regards,
William.
On Thursday, October 20, 2022 at 10:08:39 AM GMT+3, Stan Blum @.***> wrote:
Thanks, Peter!
The green links on white are very readable. I think the green links on a
dark background (e.g., over the banner image at the top) were hard to
read. Would you be inclined to washout (de-contrast) the banner image?
Curious to hear what others think of all these options.
-Stan
On Thu, Oct 20, 2022 at 12:02 AM Peter Desmet @.***>
wrote:

I've also experimented with an another theme. Here I have not underlined
the green links, how unreadable are they?
[image: Darwin-Core-TDWG (2)]
https://user-images.githubusercontent.com/600993/196878687-d2bbd180-d85a-47b6-bc09-c1d76ff7c174.png
—
Reply to this email directly, view it on GitHub
https://github.com/tdwg/website/issues/462#issuecomment-1285042229, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKZUDPUSDWESKUFLC75UMDWEDVBVANCNFSM6AAAAAARH3INEU
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I would also like to stick to blue and green only when possible and wash out colors where needed!

@peterdesmet where you have the DwC website button in dark green with black text, you could try white text, as the reverse of the GitHub button, and it would make that more readable.  Saturating or desaturating colors to provide contrast helps. BTW, I find orange (and worse, red) text very hard to read, even though the contrast stands out. I hope we can find a compromise as @mhirschfeld indicates that would work.

@gkampmeier thanks for the input. Seems like the consensus is to go with new green and blue 👍. White vs black text on the buttons is automatically detected. Apparently the new TDWG green (#709147) is right on the cusp to show black text (which I still find readable), while a slightly darker green (#617E3E) switches to white text.
Here's a new version with that green and a washed out banner (as in the original website), as suggested by @mhirschfeld (and addressing the dark images comment by @WUlate). I think this works well.


Add sidecar containers

Closing, as #68 provides the requested functionality (scheduled garbage collection) more directly, as a CronJob.

@canterberry in order to clean garbage with CronJob in most cases your job pod should be scheduled to same node as registry (not always possible). Also there are other usecases, Please merge this functionality - there are recent PR https://github.com/twuni/docker-registry.helm/pull/101


NormalizeDate: idlab-fn:normalizeDateTime doesn't work with X pattern, grel:toDate doesn't work with yyyy-MM-dd HH:mm:ss'+00:00',

I have the following csv data where the second column is  close to an xsd:dateTimeStamp format.
rowId,timestamp,data_source,index,modality,count,locationrange,speed,measurement_type,refRoadSegment
2880,2021-09-30 22:00:00+00:00,cropland,schoolstraat,,2865.9627,"POLYGON ((4.472119613057031 51.0207367817    8503, 4.479745501704901 51.02015981281664, 4.481188984378538 51.01915526700179, 4.481395603399528 51.01491    440180675, 4.482127375233162 51.0126494593307, 4.478332541440828 51.00987874451822, 4.471306586318185 51.0<PHONE_NUMBER>209, 4.469785136941451 51.01107192511326, 4.461581573935097 51.01126112376583, 4.460354540525603     51.01217411043578, 4.46032051949892 51.01700860830363, 4.468571374013287 51.01807235138044, 4.47211961305    7031 51.02073678178503))",,,
2881,2021-09-30 22:15:00+00:00,cropland,schoolstraat,,3788.4589,"POLYGON ((4.472119613057031 51.0207367817    8503, 4.479745501704901 51.02015981281664, 4.481188984378538 51.01915526700179, 4.481395603399528 51.01491    440180675, 4.482127375233162 51.0126494593307, 4.478332541440828 51.00987874451822, 4.471306586318185 51.0<PHONE_NUMBER>209, 4.469785136941451 51.01107192511326, 4.461581573935097 51.01126112376583, 4.460354540525603     51.01217411043578, 4.46032051949892 51.01700860830363, 4.468571374013287 51.01807235138044, 4.47211961305    7031 51.02073678178503))",,,

To map the second column I have written the following mapping rule
@base <http://example.org/> .  ## see issue https://github.com/RMLio/rmlmapper-java/issues/178

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix rml: <http://semweb.mmlab.be/ns/rml#> .
@prefix rr: <http://www.w3.org/ns/r2rml#> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix fnml: <http://semweb.mmlab.be/ns/fnml#> .
@prefix grel: <http://users.ugent.be/~bjdmeest/function/grel.ttl#> .
@prefix fno: <https://w3id.org/function/ontology#> .

<#allDataMap> rr:predicateObjectMap [
    rr:predicate sosa:resultTime ;
    rr:objectMap [
        rr:datatype xsd:dateTimeStamp;
        fnml:functionValue [
                rr:predicateObjectMap [
                    rr:predicate fno:executes ;
                    rr:objectMap [ rr:constant grel:date_toDate ]
                ];
                rr:predicateObjectMap [
                    rr:predicate  grel:valueParameter;
                    rr:objectMap [ rml:reference "timestamp"]
                ];
                rr:predicateObjectMap [
                    rr:predicate grel:p_string_pattern;
                    rr:objectMap [ rr:constant "yyyy-MM-dd HH:mm:ssX"];
                ];
            ];
       ];
] .

Given the other turtle files, which I will append to this report I get the following output.
It seems to be able to find the right function and the apply the right methods, but it does not seem to understand how to map a Date object to return an xsd:dateTimeStamp (or any other value) and so the result is empty.
$ rmlmapper   -m awv.sources.ttl -m column1.ttl -m column2.v2.ttl -v |& tail
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(66) - Getting instantiation for http://users.ugent.be/~bjdmeest/function/grel.ttl#date_toDate
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getClass(110) - Trying to find a Class for io.fno.grel.DateFunctions
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(79) - Found class class io.fno.grel.DateFunctions
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(165) - Trying to find method with name toDate
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(172) - Found method with matching name toDate and matching parameter count (2)
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(222) - Found method by name and expected arguments. Checking return type...
10:05:55.403 [main] INFO  b.u.i.k.f.a.d.DefaultDataTypeConverter.isSuperTypeOf(27) - Omitting supertype check in DefaultTypeConverter
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(225) - Found method!
10:05:55.403 [main] DEBUG b.u.i.k.f.a.f.Instantiator          .getMethod(87) - Found method toDate
10:05:55.404 [main] ERROR be.ugent.rml.cli.Main               .main(404) - null

This seems somewhat similar to issue https://github.com/RMLio/rmlmapper-java/issues/142
all data and code: example.tar.gz

Hmmm, for some reason grel:toDate doesn't work. However, we have another function that should do smth similar, however it doesn't seem to handle the X pattern too well, the RML below seems to work at my end:
@base <http://example.org/> .  ## see issue https://github.com/RMLio/rmlmapper-java/issues/178

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix rml: <http://semweb.mmlab.be/ns/rml#> .
@prefix rr: <http://www.w3.org/ns/r2rml#> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix fnml: <http://semweb.mmlab.be/ns/fnml#> .
@prefix grel: <http://users.ugent.be/~bjdmeest/function/grel.ttl#> .
@prefix fno: <https://w3id.org/function/ontology#> .
@prefix idlab-fn: <http://example.com/idlab/function/> .

<#allDataMap> rr:predicateObjectMap [
    rr:predicate sosa:resultTime ;
    rr:objectMap [
        rr:datatype xsd:dateTimeStamp;
        fnml:functionValue [
                rr:predicateObjectMap [
                    rr:predicate fno:executes ;
                    rr:objectMap [ rr:constant idlab-fn:normalizeDateTime ]
                ];
                rr:predicateObjectMap [
                    rr:predicate  idlab-fn:strDate;
                    rr:objectMap [ rml:reference "timestamp"]
                ];
                rr:predicateObjectMap [
                    rr:predicate idlab-fn:pattern;
                    rr:objectMap [ rr:constant "yyyy-MM-dd HH:mm:ss'+00:00'"];
                ];
            ];
       ];
] .

Thanks for the help.
I saw test cases using idlab-fn , but as the ontology is on the domain example.com I was not sure if that should be used. Perhaps it would be worth publishing those ontologies with descriptions of how they work at a place you own?

The idlab-fn are functions used for internal purposes and research projects, they are not standardized in any case and may change at any time, that's why they are not published.


Microtubule dynamics - phenotype ontologies

Based on the following issue:
https://github.com/manulera/discussions_curation/issues/4

Proposed changes

Rename FYPO:0000901 to abnormal microtubule dynamics during vegetative growth. Then make four children:

Abnormal microtubule depolymerisation rate:

This can already become the parent of the terms that were specific and mentioned depolymerisation rate, such as FYPO:0003194.
I can revisit the annotations of the others, and re-assign them.

Abnormal microtubule polymerisation rate:

Same
Terms from my paper specific to anaphase B should come as children

Abnormal microtubule growth event duration:

Since what is measured to calculate catastrophe rates is the duration of the growth events, the phenotype should be that.
In addition, the term "rescue rate" is problematic, since the use of "rate" kind of implies that the rate is constant, while in reality the catastrophe rate increases with microtubule age in the absence of other proteins, and even more so in the cell with the action of molecules such as kinesins-8 (klp5/klp6).
Terms from my paper specific to anaphase B should come as children (klp5/klp6 phenotype)

Abnormal microtubule rescue:

A bit similar to the catastrophe, rescue cannot really be measured directly, but it's distribution (ase1D perturbs distribution of rescue) or total absence can be (cls1/peg1 thermosensitive mutant prevents rescue during anaphase B). peg1 overexpression causes superstable microtubules due to excess rescue, but it's hard to provide "direct evidence" or a measurement (Bratman and Chang 2007).

The annotations from terms that are not specific and just say "decrease depolymerisation" should be revisited and assigned to the right term (depending on whether they affected shrinkage speed or growth event duration). Same applies to others like FYPO:0005463 (decreased spatial extent of interphase microtubule polymerization), they probably can be pinpointed to increased/decreased growth/shrinkage speed or duration. I can do this in the future.

Rename FYPO:0007111 to depol. rate, since the child is specific to that

Adding "during vegetative growth" to FYPO:0003193 and FYPO:0003225, since they are children of "FYPO:0000899", "normal microtubule cytoskeleton organization during vegetative growth "

Linking FYPO:0006040 to the child of FYPO:0000901 with decrease microtubule depolymerisation rate.

Edit the synonyms as well.

Requested terms - MT dynamics

For the "abnormal" microtubule polym. and depolym. rates, I don't know if the default is to already add the increased/decreased children. I guess there will be annotations for both cases, and they are typically regulated by different proteins, so probably there will not be terms without annotations.

Term name/ id
Request
New definition
New name
Child of (if added)

FYPO:0000901
Change name and definition
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which microtubule dynamics are abnormal.
abnormal microtubule dynamics during vegetative growth

Abnormal microtubule depolymerisation rate
Addition
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which the rate, or speed, of microtubule polymerization, i.e. the addition of tubulin dimers to a microtubule, is abnormal (matching FYPO:0003225)

FYPO:0000901

Abnormal microtubule polymerisation rate
Addition
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which the rate, or speed, of microtubule depolymerization, i.e. the removal of tubulin dimers to a microtubule, is abnormal (matching FYPO:0003193)

FYPO:0000901

Abnormal microtubule growth event duration
Addition
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which the duration of microtubule growth events is abnormal

FYPO:0000901

Abnormal microtubule rescue
Addition
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which microtubule rescue (the transition from shrinkage to growth) is abnormal. The frequency of rescues as well as the organisation can be affected.

FYPO:0000901

FYPO:0007111
Change name and definition
A cellular process phenotype in which the rate, or speed, of microtubule polymerization, i.e. the addition of tubulin dimers to a microtubule, is abnormal (matching FYPO:0003225)
Abnormal microtubule depolymerization rate

Requested terms - My paper
Change in synonyms
These are either for FYPO:0000901, or for the terms that were already specific and mentioned growth/shrinkage rate.

Term name/ id
Existing synonym
Proposed change
Reason

FYPO:0000901
all
None
I guess they can be left like this, since they mention both growth and shrinkage

FYPO:0003193
normal rate of microtubule catastrophe
remove
Catastrophe, not depolymerisation.

FYPO:0003194
The ones that mention stability and catrastrophe
remove
Catastrophe, not depolymerisation.

FYPO:0003190
The ones that mention stability and catrastrophe
remove
Catastrophe, not depolymerisation.

FYPO:0007111
catastrophe
remove
Catastrophe, not depolymerisation.

revised:
FYPO:0000901 new def
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which microtubule growth (polymerization), catastrophe (the transition from growth to shrinkage), shrinkage (depolymerization), or rescue (the transition from shrinkage to growth) is abnormal.
Usually we would need to obsolete a term if we change the meaning of the definition, but here since the change is subtle, and  was encapsulated by annotations to this term, I have altered the def.

I could not add an equivalence axiom for "abnormal rate"
but he child terms have them:
'has part' some
('increased rate'
and (happens_during some 'mitotic interphase')
and (happens_during some 'single-celled organism vegetative growth phase')
and ('inheres in' some 'microtubule polymerization'))
@nicolevasilevsky @matentzn  how do I get "abnormal rate" for this grouping term for rate phenotypes? For I request this from PATO, or somewhere else?
It seems odd not to be able to create an equivalence axiom for the parent went he children have them.

the abnormal part goes in the EQ, not the PATO class:
'has part' some
('increased rate'
and (happens_during some 'mitotic interphase')
and (happens_during some 'single-celled organism vegetative growth phase')
and ('inheres in' some 'microtubule polymerization')
and ('has modifier' some 'abnormal')
)

Why is it necessary to have 2 'happens during' clauses? There should be just one ideally.. Do these phases happen at the same time?

the abnormal part goes in the EQ, not the PATO class:

OK that part makes sense.
So probably I cant create a definition for a grouping term for "increased or decreased" rate?

Why is it necessary to have 2 'happens during' clauses? There should be just one ideally.. Do these phases happen at the same time?

I have no idea why there are 2, this was an existing logical def I am copying and adjusting.
I don't really understand their construction....
Looking at this the
and (happens_during some 'single-celled organism vegetative growth phase')
looks as though it is redundant with
and (happens_during some 'mitotic interphase')
I think what has likely happened is that the 'single-celled organism vegetative growth phase' has been retained when a more specific term and equivalence axiom has been added. We can look for logical defs with 2 happens_during and revise.
In the meantime I removed the redundant looking one from FYPO:0004615. to see what happens.

So probably I cant create a definition for a grouping term for "increased or decreased" rate?

of course, just use rate in the grouping term, increased rate in the child, then you have the grouping! Or did you mean something else?

doh, got it !
Thanks.


Sentinel UniFi Solution is not accepted on CSP subscriptions

Is your feature request related to a problem? Please describe.
The Azure Sentinel solution for Ubiquiti UniFi (preview) is not allowing deployments to CSP subscriptions in Azure.

Describe the solution you'd like
Allow the Ubiquiti UniFi (preview) solution to be deployed in CSP subscriptions.

External links
https://www.microsoftpartnercommunity.com/t5/Microsoft-AppSource-and-Azure/Error-This-offer-is-not-available-for-subscriptions-from/m-p/22881
https://docs.microsoft.com/en-us/partner-center/azure-plan-available

@s3bast1aan, we have enabled the csp for this solution, can you please if the issue still persists. Thanks.

@s3bast1aan, please let me know if we can close this issue, thanks.

@s3bast1aan, please let me know if we can close this issue, thanks.

Hi @v-sabiraj , yes I can confirm that the deployment is working now.
Thank you. :-)


Colorize entire split input header instead of just the channel name

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
Having a lot of splits open in one tab currently results in a really frustrating experience when trying to navigate between them using keyboard shortcuts, since the only way of telling which split is currently active is the small colorized channel name in the split header.
This PR adds the option to draw the entire split header in a blue tint instead of just the channel name text. Adding a new setting for this is imo a good idea here, since there is no need for, what I am guessing is probably the majority of chatterino users, those who mostly have a single split in a tab to have their entire header colorized.
Screenshots
White

Light

Dark

Black

I advocate for making this standard behavior and removing the option to switch to the old behavior.

Should this really be an option? I'd rather just have the behavior changed.

Agree with Leon and mm2; I don't see a reason to keep the old behaviour around. I would like a single split to not have a colour though, maybe I'm special.

I would like a single split to not have a colour though, maybe I'm special.

No, I feel the same way, its mainly why I made it a setting.
Maybe make it the default whenever there is more than one split currently opened in a tab?

I agree with whichever consensus does not like this change, but I also understand the reasoning for it.

I changed the behaviour to be on by default but only show the colorized header if there is more than one split in the containing tab, retaining the previous behaviour for single splits.

I don't know if I am testing this wrong or misunderstanding the Pull Request, however - when there's only 1 split in the tab, it keeps the old behaviour; as in, the split header is still as it was before

Found another regression:

I don't know if I am testing this wrong or misunderstanding the Pull Request, however - when there's only 1 split in the tab, it keeps the old behaviour; as in, the split header is still as it was before

See my reply above, I agree with jammeh's take that coloring the entire header is unnecessary for a single split and more distracting than adding any additional value, so I added a check to retain the old behaviour for single splits.

Found another regression:

That one is definitely not intended though, I'll take a look at that tomorrow.

I agree that there should not be a setting for this, if we wanted this user-customizable imo we would support it through custom themes (which isn't off the table).
I don't think we should change the behaviour depending on the amount of splits in a tab - if it looks off with just one split I think it means that the behaviour might need tweaking.
With this information, I set off to tweak some things, and came up with this solution: Just change the focused background color of the split, but leave the color roughly the same as it was before this PR.
Multi split

Single split

Single split window not focused

Light mode single split focused

Light mode multi split with focus

Had absolutely no time over the last few days, but I integrated pajladas patch now.

however if you want to make further changes later on, feel free to.

Dont have anything further to add to this PR either.


Strange behavior with Import / Export on Ansible plugin

Hello,
i faced an issue that got finally solved with the help of @yassineazzouz.
I have two instance of Rundeck, the first instance use rundeck as user and the second use rundeck-project as user.
For some reasons i had to export from the first instance a project and import it in the second instance.
Till here no problem when i change the path of the YML inside the second instance as i have a different user (/var/lib/rundeck-projects/projects//.....yml) i got this error : {2=Dispatch failed on 1 nodes: [localhost: AnsibleNonZero: Error running Ansible Node Step.]}, Node failures: {localhost=[AnsibleNonZero: Error running Ansible Node Step.]}, flow control: Continue, status: failed].
Finally the way to resolve it was to recreate the job in the second instance.
Hope this is something that can be fixed or will help someone else.
Regards
DF

Thanks @fossouo for sharing this, Exporting and Importing projects is not always straightforward:

The paths of the exported and imported projects need to match
If your configuration is referencing some keys in the storage path they need to be created manually or adjusted in the Exported file.


[DSEP-131] Separate demo scripts from flexsea lib

Summary
Refactors all Python scrips. Makes flexsea installable with pip and documents all changes.
See published package here: https://pypi.org/project/flexsea/
(If you make an account at Pypi I can add you as a maintainer of the package)
Changes

flexsea and all its dependencies are installable via pip
All python scripts can be run standalone.
Refactors all scripts to follow pep8
Cleans up all files and changes all indents to tabs
ports.yaml replaces com.txt
Documentation updated in the readme and added to the flexsea package.
All demo scripts and run_demos.py (formerly fxMain.py) are now in the flexsea_demos folder
Removes deprecated files

Test Plan

Read the README.md and follow the instructions to install flexsea and run the scripts
cd flexsea_demos  and run run_demos.py and try the scripts
Try the script on their own e.g. ./high_speed_test.py /dev/ttyACM0
In python import flexsea should work form any folder as long as the lib is installed

Expected Results

All scripts run as before (or better since many bugs are gone)
It is much easier to install and use flexsea

I added all the feedback from JF:

Move bootloader and poles to Utilities section,
Dephy logo centered and tm
fxMain dummy execulable

I added all the feedback from JF:

Move bootloader and poles to Utilities section,
Dephy logo centered and tm
fxMain dummy execulable


SDC : Some properties of Questionnaire are not accessible for custom components

Describe the bug
Some properties are not accessible of Questionnaire object for custom components (Eg, orientation, answerOption). While creating custom components like BooleanType, orientation, answerOption properties have private access to the library and due to that we can't achieve functionalities like flexible orientation or custom text for radio buttons.
Component
SDC library
Expected behavior
Each property of the Questionnaire which is required for component behavior should have public access.
cc @jingtang10

Kind of makes sense, because it will be very useful if we can use those features in our custom widgets.
Seconding this :D

@khyativyasargus @FikriMilano please feel free to send a pr. thanks for raising this issue!


Need some observables to listen Scene/AbstractMesh/Material objects creation event

Our team write a mixin library to improve and extend babylon builtin Class functions, such as Scene/AbstractMesh/Material, because wirting extension for builtin Class used XXX.prototype is so tedius.
the mixin is used as follows:
RegisterMixin(AbstractMesh, class extends AbstractMesh {
     private _castShadow = false;
     public get castShadow() {
          return this._castShadow;
     }
     public set castShadow(v: boolean) {
          this._castShadow = v;
          // xxxx
     }
});

But, the implementation of mixin library need to observe builtin type object creation, to copy property descriptors.
Now, we are using apis Engine.onNewSceneAddedObservable, Scene.onNewMeshAddedObservable, Material.OnEventObservable to achieve the goal. But these apis are not perfect:
Engine.onNewSceneAddedObservable can not be used observing non-virtual scene creation, so we hacked engine._virtualScenes to listen the calling of engine._virtualScenes.push.
Scene.onNewMeshAddedObservable can not be used observing abstract mesh creation when importing gltf file, because babylon need to create and collect all entities from gltf first, and then add them into current scene.
Material.OnEventObservable is closed to perfect,  but only emit one event MaterialPluginEvent.Created. Name of th event is not perfect.
So, we want  some perfect observables to exactly observe Scene/AbstractMesh/Material objects creation, like Material.OnEventObservable, but has more appropriate event name.
for example

Scene.OnEventObservable.add(() =>, Scene.Created);

AbstractMesh.OnEventObservable.add(() =>, AbstractMesh.Created);

Material.OnEventObservable.add(() =>, Material.Created);

It would be nice if there were other observables to notify other type objects creation, such as PBRMaterial, Mesh, InstancedMesh.

@Starryi - Let's discuss on the Forum first, please.

discussion in form is here  https://forum.babylonjs.com/t/need-some-observables-to-listen-scene-abstractmesh-material-objects-creation-event/49057


Transparent PNG imported into SVG gives black background on laser

I've noticed this yesterday. I have this SVG created with Inkscape and it contains an imported PNG image that has a transparent background. When I open it in Meerk40t it correctly classifies it as image and shows ok on screen but when I send it to the laser it engraves a black square where the background should be transparent.
Running on Linux Mint 20.2.
Image attached
Viking Runestone 02.svg.zip

I've noticed this issue has already been reported. Sorry

NP. This made me revisit and publish the correction.


[QUESTION] IDEA StatiCa RCS:  return checks for reinforcement + corresponding stresses etc.

Is it possible to return not only the overall unity check for fatigue but also the other values (checks for reinforcement + corresponding rebar stresses etc).
(application: check of Markov matrix with 500-1000 unique load values)

No, the other values are not available yet.

Hi,
Any status update regarding this functionality?


Missing GPU implementation

System information

Have I written custom code: Yes
OS Platform and Distribution: Linux Kubuntu 18.04
TensorFlow installed from: binary (with pip3)
TensorFlow version: 1.14.0 (v1.14.0-rc1-22-gaf24dc91b5)
Python version: 3.6.8
CUDA/cuDNN version: 10.0.130
GPU model and memory: NVidia Titan Xp

Describe the current behavior
The op tf.norm cannot be assigned to the GPU in all configurations (see minimal example below).
Describe the expected behavior
I see no theoretical reason for the tf.norm op not to be fully portable to the GPU. I suspect this is a bug, not an intended behavior.
Code to reproduce the issue
import tensorflow as tf

b = 10
width = 16
height = 16
channels = 3

def norm_simple(X):
  return tf.norm(X,axis=[1,2],ord=2)

def norm_custom(X):
  X_r = tf.reshape(X,shape=[b,width*height,channels])
  return tf.norm(X_r,axis=1,ord=2)

s = tf.Session()

A = tf.ones(shape=[b,width,height,channels])

with tf.device('/cpu:0'):
  n1_cpu = norm_simple(A)
s.run(n1_cpu)
print(" === norm_simple works on CPU")

with tf.device('/cpu:0'):
  n2_cpu = norm_custom(A)
s.run(n2_cpu)
print(" === norm_custom works on CPU")

with tf.device('/gpu:0'):
 n2_gpu = norm_custom(A)
s.run(n2_gpu)
print(" === norm_custom works on GPU")

with tf.device('/gpu:0'):
 n1_gpu = norm_simple(A)
s.run(n1_gpu)
print(" === norm_simple works on GPU")

Other info / logs
Execution of the above code on my machine:
 === norm_simple works on CPU
 === norm_custom works on CPU
 === norm_custom works on GPU
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1356, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1339, in _run_fn
    self._extend_graph()
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1374, in _extend_graph
    tf_session.ExtendSession(self._session)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation norm_3/map/TensorArray: Could not satisfy explicit device specification '' because the node {{colocation_node norm_3/map/TensorArray}} was colocated with a group of nodes that required incompatible device '/device:GPU:0'. All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_GPU:0, /job:localhost/replica:0/task:0/device:XLA_GPU:1, /job:localhost/replica:0/task:0/device:XLA_CPU:0, /job:localhost/replica:0/task:0/device:GPU:0, /job:localhost/replica:0/task:0/device:GPU:1].
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=-1 requested_device_name_='/device:GPU:0' assigned_device_name_='' resource_device_name_='' supported_device_types_=[CPU, XLA_CPU, XLA_GPU] possible_devices_=[]
Switch: GPU CPU XLA_CPU XLA_GPU
TensorArrayScatterV3: CPU XLA_CPU XLA_GPU
TensorArrayReadV3: CPU XLA_CPU XLA_GPU
Enter: GPU CPU XLA_CPU XLA_GPU
TensorArrayV3: CPU XLA_CPU XLA_GPU
Const: GPU CPU XLA_CPU XLA_GPU

Colocation members, user-requested devices, and framework assigned devices, if any:
  norm_3/Const (Const) /device:GPU:0
  norm_3/map/TensorArray (TensorArrayV3)
  norm_3/map/TensorArrayUnstack/TensorArrayScatter/TensorArrayScatterV3 (TensorArrayScatterV3) /device:GPU:0
  norm_3/map/while/TensorArrayReadV3/Enter (Enter) /device:GPU:0
  norm_3/map/while/TensorArrayReadV3 (TensorArrayReadV3) /device:GPU:0
  norm_3/map/while/cond/Switch_1 (Switch) /device:GPU:0
  norm_3/map/while/cond/add/Switch (Switch) /device:GPU:0

         [[{{node norm_3/map/TensorArray}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bugreport.py", line 36, in <module>
    s.run(n1_gpu)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 950, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1173, in _run
    feed_dict_tensor, options, run_metadata)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1350, in _do_run
    run_metadata)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/client/session.py", line 1370, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation norm_3/map/TensorArray: Could not satisfy explicit device specification '' because the node node norm_3/map/TensorArray (defined at bugreport.py:9) placed on device No device assignments were active during op 'norm_3/map/TensorArray' creation.  was colocated with a group of nodes that required incompatible device '/device:GPU:0'. All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_GPU:0, /job:localhost/replica:0/task:0/device:XLA_GPU:1, /job:localhost/replica:0/task:0/device:XLA_CPU:0, /job:localhost/replica:0/task:0/device:GPU:0, /job:localhost/replica:0/task:0/device:GPU:1].
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=-1 requested_device_name_='/device:GPU:0' assigned_device_name_='' resource_device_name_='' supported_device_types_=[CPU, XLA_CPU, XLA_GPU] possible_devices_=[]
Switch: GPU CPU XLA_CPU XLA_GPU
TensorArrayScatterV3: CPU XLA_CPU XLA_GPU
TensorArrayReadV3: CPU XLA_CPU XLA_GPU
Enter: GPU CPU XLA_CPU XLA_GPU
TensorArrayV3: CPU XLA_CPU XLA_GPU
Const: GPU CPU XLA_CPU XLA_GPU

Colocation members, user-requested devices, and framework assigned devices, if any:
  norm_3/Const (Const) /device:GPU:0
  norm_3/map/TensorArray (TensorArrayV3)
  norm_3/map/TensorArrayUnstack/TensorArrayScatter/TensorArrayScatterV3 (TensorArrayScatterV3) /device:GPU:0
  norm_3/map/while/TensorArrayReadV3/Enter (Enter) /device:GPU:0
  norm_3/map/while/TensorArrayReadV3 (TensorArrayReadV3) /device:GPU:0
  norm_3/map/while/cond/Switch_1 (Switch) /device:GPU:0
  norm_3/map/while/cond/add/Switch (Switch) /device:GPU:0

         [[node norm_3/map/TensorArray (defined at bugreport.py:9) ]]Additional information about colocations:No node-device colocations were active during op 'norm_3/map/TensorArray' creation.
No device assignments were active during op 'norm_3/map/TensorArray' creation.

Original stack trace for 'norm_3/map/TensorArray':
  File "bugreport.py", line 35, in <module>
    n1_gpu = norm_simple(A)
  File "bugreport.py", line 9, in norm_simple
    return tf.norm(X,axis=[1,2],ord=2)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/linalg_ops.py", line 600, in norm
    ops.convert_to_tensor(axis))
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/map_fn.py", line 228, in map_fn
    for elem in elems_flat]
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/map_fn.py", line 228, in <listcomp>
    for elem in elems_flat]
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/tensor_array_ops.py", line 1086, in __init__
    name=name)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/tensor_array_ops.py", line 164, in __init__
    self._handle, self._flow = create()
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/tensor_array_ops.py", line 161, in create
    name=scope)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/gen_data_flow_ops.py", line 8085, in tensor_array_v3
    tensor_array_name=tensor_array_name, name=name)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/ops.py", line 2005, in __init__
    self._traceback = tf_stack.extract_stack()

@kvanhoey, Thanks for reporting this issue.
I could reproduce the reported issue in TF1.x. Its fixed in TF 2.0.0rc2.
Please take a look at colab gist. You might want to give it a try instead. Thanks!

Thank you for getting back to me. Glad it's fixed in 2.0.
I have a big project that I don't want to move to TF 2.0 yet, so I'll stay with my workaround (reshape first, then tf.norm on one dimension only).


add folding by braces

like in javascript

Hey @oryband, this is supported in a new, maintained fork- check it out. https://github.com/thesis/vim-solidity/issues/1


DayPickerRangeController not selecting

Hi,
Trying to set up a basic DayPickerRangeController. I'm able to toggle the arrows between months just fine, but not able to select a range of dates for some reason:

import React, { Component } from 'react';
import { DayPickerRangeController } from 'react-dates';

class DatePicker extends Component {
    constructor(props) {
        super(props);

        this.state = {
            startDate: null,
            endDate: null,
            focusedInput: null
        };
    }

    render() {
        return (
            <DayPickerRangeController
                startDate={this.state.startDate}
                endDate={this.state.endDate}
                onDatesChange={({ startDate, endDate }) =>
                    this.setState({ startDate, endDate })}
                focusedInput={this.state.focusedInput}
                onFocusChange={focusedInput => this.setState({ focusedInput })}
                numberOfMonths={2}
            />
        );
    }
}

export default DatePicker;

Any and all help is greatly appreciated.

Hi @hidace, you need to focusedInput to be non-null in order to select things. When using the DayPickerRangeController without inputs, I'd probably default to:
this.state = {
  ...
  focusedInput: START_DATE,
};

and
onFocusChange={focusedInput => this.setState({ focusedInput: focusedInput || START_DATE })}

That way, dates are always selectable. Probably I should set more reasonable default to support this.

@majapw Thanks so much, that was it! Appreciate the help!

@majapw I just wanted to mention that I used this post to solve a similar issue I was having, but it came up short.
Unfortunately, it seems like there's an extra level of abstraction in my environment from the constants file which leads START_DATE to be flagged as undefined (likely the case that we're use styled-components, though I'm not positive).
Digging through DayPickerRangeController.jsx, I found where START_DATE was being imported and discovered it's original string definition of startDate. Setting my environment up like below solved the issue I was having:
state = {
  focusedInput: 'startDate'
}

<DayPickerRangeController
  startDate={this.state.startDate}
  endDate={this.state.endDate}
  onDatesChange={({ startDate, endDate }) =>
  this.handleDateChange(startDate, endDate)
  }
  focusedInput={this.state.focusedInput}
  onFocusChange={focusedInput =>
    this.setState({ focusedInput: focusedInput || 'startDate' })
  }
/>

Hopefully, this helps someone if they run into a similar issue. If you'd like me to open a bug, I'd be happy to, though I chalked this up to our project necessitating styled-components 😄

@majapw tried assigning focusedInput a Non-Null value as you said. But still, dates are not getting change.
here the state object..
import React from 'react';
import moment from 'moment';

import 'react-dates/initialize';
import { DayPickerRangeController } from 'react-dates';
import 'react-dates/lib/css/_datepicker.css';

import Button from '@material-ui/core/Button';
import { COLORS } from '../constants';

const componentStyles = {
  selectRoot: {
    padding: '5px 30px 5px 10px',
    background: '#e5e6e7',
    color: COLORS.DARK_NAVY_BLUE,
    fontFamily: 'Montserrat'
  }
};

// NOTE: default form values
const START_DATE = moment().subtract(1, 'month');
const END_DATE = moment();

const STYLES = {
  FILTER_CONTAINER: {
    display: 'flex',
    justifyContent: 'flex-end',
    paddingRight: '50px'
  },
  FILTER_ACTION_WRAP: {
    margin: '0px 5px 0px 5px',
    backgroundColor: '#e5e6e7',
    padding: '2px 10px',
    color: COLORS.DARK_NAVY_BLUE,
    cursor: 'pointer',
    display: 'flex',
    alignItems: 'center',
    borderRadius: '0px'
  },
  APPLY_BUTTON: {
    padding: '10px 20px',
    textAlign: 'right',
    color: '#0062f7',
    fontWeight: '600',
    fontFamily: 'Montserrat',
    textTransform: 'uppercase',
    cursor: 'pointer'
  }
};

class FilterHeader extends React.Component {
  constructor(props) {
    super(props);

    this.state = {
      filterBy: DEFAULT_SORT_TYPES,
      datePickerFlag: false,
      startDate: START_DATE,
      endDate: END_DATE,
      focusedInput: END_DATE
    };

    this.onFocusChange = this.onFocusChange.bind(this);
    this.handleOnDateChanges = this.handleOnDateChanges.bind(this);
  }

  componentDidMount() {}

  toggleDateRange = () => {
    const { datePickerFlag } = this.state;
    this.setState({ datePickerFlag: !datePickerFlag });
  };

  render() {
    const { startDate, endDate, datePickerFlag, focusedInput } = this.state;
    const { classes } = this.props;
    const { selectRoot } = classes;

    const formatStartDate = startDate.format('Do MMM');
    const formatEndDate = endDate.format('Do MMM');
    const BUTTON_TEXT = [formatStartDate, formatEndDate].join(' - ');
    return (
      <React.Fragment>
        {!!datePickerFlag && (
          <DayPickerRangeController
            startDate={startDate}
            endDate={endDate}
            withPortal={true}
            onDatesChange={({ startDate, endDate }) => this.setState({ startDate, endDate })}
            focusedInput={focusedInput}
            onFocusChange={focusedInput => this.setState({ focusedInput })}
            numberOfMonths={2}
          />
        )}
        <section style={STYLES.FILTER_CONTAINER}>
          <Button
            ariaHaspopup="true"
            ariaExpanded="true"
            ariaControls="menuItemComponent-date_picker"
            className=""
            onClick={this.toggleDateRange}
            style={STYLES.FILTER_ACTION_WRAP}
          >
            {BUTTON_TEXT}
          </Button>
        </section>
      </React.Fragment>
    );
  }
}

export default FilterHeader;


Display 'published' for live specialist-documents on index page

Paired with @Rosa-Fox
Previous fix for the show page calls document#live? in the state helper
method. However, the index page loads OpenStruct objects instead of
Document objects and will always return nil for document#live?.
Before:

After:

This still makes the "live" => "published" change work on the show pages, so it looks fine to me.


Fix tag filtering

Tag filtering is broken.
In the tag tree, tag hashes are stored as uint32_t's, but during capture loading (Capture::loadBin()), only the low 16 bits of the tag are stored in each MemoryOperation. Tag filtering is performed on the full 32-bit value in Capture::isInFilter(), and unless the first two MSBs of the tag are 0, it will fail.
To fix this I extended the tag field in MemoryOperation to a full uint32_t. This will increase the size of each MemoryOperation by 2 extra bytes, so I don't know if that's the fix you'll prefer. Another fix would be to modify the tag test in isInFilter() to only test the low 16 bits, at the cost of an increased false positive risk. Feel free to implement the fix you like best :)
Cheers!

ooops! I'll merge this but need to make MemoryOperation structure more compact later. Extending the tag to 32 bits actually increases the structure size by 8 bytes due to alignment :/


sync with juicefs without mount point

This PR allow us sync with JuiceFS without mount point:
juicefs sync   a/path/   jfs://meta-url/path/

Since meta-url is used as host, so it should be escaped twice, for example, sqlite3://a.db should be
juicefs sync   a/path/   jfs://sqlite3%253A%252F%252Fa.db/path/

To simplify this, we could use environment variable to pass meta-url, for example
myfs=sqlite3://a.db juicefs sync  a/path/   jfs://myfs/path/

Codecov Report
Base: 56.01% // Head: 55.98% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (5ea4b46) compared to base (f5ed1a1).
Patch coverage: 44.52% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3161      +/-   ##
==========================================
- Coverage   56.01%   55.98%   -0.04%
==========================================
  Files         141      142       +1
  Lines       32513    32848     +335
==========================================
+ Hits        18213    18389     +176
- Misses      12371    12526     +155
- Partials     1929     1933       +4

Impacted Files
Coverage Δ

cmd/mdtest.go
26.70% <ø> (+0.13%)
:arrow_up:

pkg/object/sftp.go
52.34% <0.00%> (ø)

pkg/chunk/cached_store.go
73.14% <33.33%> (+1.35%)
:arrow_up:

cmd/object.go
38.38% <38.38%> (ø)

cmd/sync.go
51.57% <50.00%> (-0.17%)
:arrow_down:

pkg/utils/utils.go
64.23% <66.66%> (+1.89%)
:arrow_up:

pkg/fs/fs.go
75.19% <70.00%> (+0.94%)
:arrow_up:

cmd/objbench.go
58.01% <100.00%> (+0.11%)
:arrow_up:

pkg/object/file.go
65.31% <100.00%> (ø)

pkg/object/file_unix.go
100.00% <100.00%> (+29.41%)
:arrow_up:

... and 10 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

mark


Add Rust package

This PR adds a Rust package for tree-sitter-rust grammar.
This makes it easier to use the Rust tree-sitter bindings with a statically known set of languages, since you can just list them as normal Rust dependencies, instead of having to embed the grammar and set up a build.rs file yourself.
I don't know how to handle the author field of Cargo.toml, for now I added myself, but I guess I should add the main maintainer of this repository. Let me know what I should do, I'm willing to completely remove myself, no problem at all :smile:
Thanks in advance for your review! :)

@maxbrunsfeld
Could you please merge this one also?

Thank you! :)


Ensure that not internet connection is needed.

The default reader settings tries to download the DTD from the network, that in our case, makes no sense.

@spouliot objc branch is fully merged into master branch. I suggest you start working on master going forward.

Closing since it was easier to create a new PR. @spouliot you can find the new one here: https://github.com/mono/Embeddinator-4000/pull/551


chore(jupytext)

In some pipelines, especially complex ones, it makes sense to use modules (.py) instead of notebooks, but it would be great to still be able to leverage the power of Jupyter Notebooks.
jupytext is a nice way to interact with plain text (i.e. .py) using Jupyter Notebooks.

It looks like it's already there as a dev dependency. You can try it out with make lab, then browse to a python file, then you need to right-click on it and open it with jupytext

Totally missed that. Thanks, @larsyencken


New version: BrazilFinancialData v0.1.2

Registering package: BrazilFinancialData
Repository: https://github.com/Thiago-Simoes/BrazilFinancialData.jl
Created by: @Thiago-Simoes
Version: v0.1.2
Commit: 48d09d1bf6da70a89496fe470a205ff84076e57f
Reviewed by: @Thiago-Simoes
Reference: https://github.com/Thiago-Simoes/BrazilFinancialData.jl/issues/8#issuecomment-1287250370

@Thiago-Simoes please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]


dependabot requests

Hello.
What should we do with #1267, #1285, #1290, #1298, #1299 and #1300?

PromiseKit 6.21.0.
SPM.

I have tried to merge these before and it just breaks the tests.
It only effects tests so it's not in fact important.
If you close them they just come back… so basically I dunno what to do about it bar turning dependabot off. Which we probably can do, we have no deps really. Just in the tests.


Kim edit: customize.adoc

Kim edit: customize.adoc

PR to address these changes: https://github.com/mulesoft/docs-api-community-manager/pull/98

Resolved in https://github.com/mulesoft/docs-api-community-manager/pull/98 .


[WIP] setup.py: install_requires: remove versions

I am trying to install pylama system-wide on Arch Linux, which has
pyflakes 1.1.0 already, and running pylama fails with:

pkg_resources.ContextualVersionConflict: (pyflakes 1.1.0
(/usr/lib/python3.5/site-packages),
Requirement.parse('pyflakes==1.0.0'), {'pylama'})

pkg_resources.DistributionNotFound: The 'pyflakes==1.0.0' distribution
was not found and is required by pylama

This commit fixes it by only using the package name from
requirements.txt, but not the version.
Alternatively I could imagine replacing the '==' with '>=' to ensure the
minimum requirements are met, which is probably better?!
On the other hand this might not be useful altogether, and instead tools
like pipsi or virtualenvs should be used for pylama only?!

Coverage remained the same at 77.292% when pulling b63be42c3d23e28c7ee9656c4d1a12dc13cb04e9 on blueyed:unpin-install-requires into 8248cda64d1f0af41d02b1e36733d530c883338c on klen:develop.

I've pushed an alternative commit to use >= instead of ==.

Coverage remained the same at 77.292% when pulling 2aba255170f049bb0a793ac6904051a8bacc2e05 on blueyed:unpin-install-requires into 8248cda64d1f0af41d02b1e36733d530c883338c on klen:develop.

Thank you!

@klen
Thanks for merging, but it was not meant to be..!
(there's a commit that's meant to be squashed and I've added WIP to the title)
So I assume that you prefer the ">=" approach then?!


Deleting connected keys does not update cspr.live

Describe the bug
When an account is connected to cspr.live and the same account is deleted in signer - cspr.live is still connected and usable with the same account
To Reproduce
Identify if any Prequisites:
Installed version 1.2.0 or 1.3.0
Steps to reproduce the behavior:

Go to 'cspr.live and login with signer successfully
From signer now delete the same account

Expected behavior
Since the account is deleted, Cspr.live should be logged out as the account does not exist on signer
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Defect Type

[ ] Regression
[ ] New
[x] Escape

It is very possible that thiss will be fixed when CSPR.live will start utilizing Signer's event bus, am I right @piotrwitek ?

Just tested and this is resolved as of 09d909e in PR #123

Tested this as well and it works for me now.

Tested Fixed


fix: update minimum supported version of VS Code

Fixes #381

Version 1.82.0 is from August 2023 and is the oldest minor-version the tests pass with.

What about running the extension? Does it work?

As far as I can tell, yes.


deprecate gil-refs in from_py_with

This deprecates the use of gil-refs in from_py_with. This PR implements it only for #[pyfunction] arguments. While it would be easily possible to generate the same code for #[derive(FromPyObject)] the warning gets eaten by #[automatically_derived]. I don't see a good way around that, but I'm happy to adapt if someone has an idea.

Deref coercion is not allowed in consts 😢

Ah 😢. I wonder if there's some dirty hack like packaging into a non-const function, given this code doesn't need to run:
const _: () = {
    fn check_from_py_with() {
        let e = pyo3::impl_::pymethods::Extractor::new();
        inspect_fn(function_to_inspect, &e);
        e.extract_from_py_with();
    }
}

... from a quick test in the playground, this sort of structure can still trigger deprecation warnings: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=fac5238c3e4fdd1ce0da0b2209a64b6c
(and because each anonymous constant block is its own scope, all these functions can share a common name, I think they won't conflict.)

Ah 😢. I wonder if there's some dirty hack like packaging into a non-const function, given this code doesn't need to run:

Hmm, it seems like this only works if the constant (anonymous or not) lives in the source itself, if it is generated by the macro it does not trigger. Are these const generated by proc macros handled specially by the compiler :thinking:

Eurgh, I have no idea 😂
I guess unless we find new tricks, we have to accept that we can't deprecate that case.

Hmm, it seems like this only works if the constant (anonymous or not) lives in the source itself, if it is generated by the macro it does not trigger.

I actually got it to work 🎊 I forgot to set a span for the const _: () = {} and it seems like the compiler just throws the warning in the void in that case. I kind of expected it to show on the derive but I guess that's not how it works. I'll prepare the PR with the followup.

Great!


How should I update my branch after the upstream code is updated?

There are two approaches.

Use Git on your computer to pull my repository (upstream) and merge it into your own. Refer to: https://stackoverflow.com/questions/56577184/github-pull-changes-from-a-template-repository
Backup your current uptime.config.ts, delete your current repository, recreate the repository from the template, set the environment variables, restore the config file and you're done!

Just choose the one you find more convenient :)

Added in Wiki, thanks for your advice!


[Snyk] Upgrade ch.qos.logback:logback-classic from 1.4.8 to 1.4.11

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade ch.qos.logback:logback-classic from 1.4.8 to 1.4.11.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-08-09.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #77 (d25df85) into main (659356f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #77   +/-   ##
=========================================
  Coverage     50.00%   50.00%
  Complexity       76       76
=========================================
  Files            19       19
  Lines           596      596
  Branches         56       56
=========================================
  Hits            298      298
  Misses          277      277
  Partials         21       21

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add a wrapper script to preprocess the arguments when invoking packcheck elsewhere.

The wrapper script should quote the arguments accordingly.

This is related to #52

Can't we use "$@" to pass the arguments quoted?


Refactoring

Visual code improvement according to PEP8 and Dockerfile optimization

@rliskunov maybe it will be good to add pep8 call to Makefile in order to avoid future problems of the same type?

@yegor256 thanks for the idea! I added two popular linters flake8 and pylint. I successfully solved all the problems that the first analyzer showed. But now pylint demonstrate that code has been rated at 6.30/10. Please see what warnings I can add to the ignore section.

@rliskunov I believe there are merge conflicts :( Please, merge master branch into your branch and resolve them. Then, push your branch to GitHub and let me know.

@yegor256 hope i was able to resolve conflicts. See the changes, please

@rliskunov thanks!


Only manipulate headers if not already sent

When you want to send headers before request finishes via
class MyController  {
  public function myAction() {
      $response = new Response();
      $response->headers->set(
          'Content-Disposition',
          HeaderUtils::makeDisposition(
              HeaderUtils::DISPOSITION_ATTACHMENT,
              'file.txt
          )
      );

      $response->sendHeaders();
      ob_flush();
      flush();

      // do some work to populate response
      sleep(5); // this is only for demonstraton purposes

      return $response;
  }
}

I get a warning error

E_WARNING: Cannot modify header information - headers already sent in [Root folder]/vendor/symfony/http-foundation/Session/SessionUtils.php, line 54

With this PR the headers get only manipulated during kernel.response event if the headers have ot already been sent.

Closed in favor of https://github.com/symfony/symfony/pull/45434


Use official openwhisk/kube-couchdb image

resolves issue #28

@csantanapr -- switching to using the images you started publishing in #74


Few points to fix in docu

Hi there,
Thanks for this awesome project :)
Just a few things that I've found using https://github.com/Zendro-dev/ZendroStarterPack

Useful but not too dramatic that repo https://github.com/Zendro-dev/graphql-server had an .env in its root.

Remove .gitkeep in https://github.com/Zendro-dev/ZendroStarterPack/tree/master/data_model_definitions as this produces errors when executing graphql-server-model-codegen

Change number 3 in https://github.com/Zendro-dev/Zendro-dev.github.io/blob/master/setup_data_scheme.md as for Data Model Definition for table B we need a many to many relation:

Data Model Definition for table B:
{
    "model": "department",
    "storageType": "mongodb",
    "attributes": {
        "department_id": "String",
        "department_name": "String",
        "employee_ids": "[String]"
    },
    "associations": {
        "employees": {
            "type": "many_to_many", ####change one_to_many to many_to_many
            "implementation": "foreignkeys",
            "reverseAssociation": "departments",
            "target": "employee",
            "targetKey": "department_ids",
            "sourceKey": "employee_ids",
            "keysIn": "department",
            "targetStorageType": "mongodb"
        }
    },
    "internalId": "department_id",
    "id": {
        "name": "department_id",
        "type": "String"
    },
    "useDataLoader": false
}

Thank you for compiling this issue
.env file in gql-server
Generally you don't want to commit .env files since those are local environt variables that the user specifically has to set himself. There is a note in the starterPack README for that, but I added it to the graphql README
fixed in: #310583af
Remove .gitkeep
The problem here is that to have an empty folder commited to a git repository this is the default way to do it. However that leads to the problem you mentioned.
Solution
Only process .json files in the codegeneration step
fixed in : #e425338
many-to-many documentation data-model
That is indeed wrong in the documentation
fixed in: #8f17cae

Great.
Thanks @coeit for the support


How to specify an override for the default serial port used for flashing firmware via flash_firmware.sh?

Issue template

Hardware description: Ubuntu 20.04 (Agent), ESP32 (Client)
RTOS: FreeRTOS
Installation type: micro_ros_setup flash_firmware.sh
Version or commit hash: galactic

Steps to reproduce the issue
Running ros2 run micro_ros_setup flash_firmware.sh defaults to the first available USB serial port. However, if I have a few MCUs connected -- say USB0, USB1, USB2 -- and I only want to flash the one connected to USB1, how would I go about doing this?
Expected behavior
flash_firmware.sh should offer an option (eg, --dev /dev/ttyUSB1) to flash to a particular port
Actual behavior
No such option exists. flash_firmware.sh flashes to the first available USB port
Additional information

Hello @safdark, micro_ros_setup has those kinds of limitations because it is just a set of functionalities for getting started with micro-ROS.
If you have a patch or a solution it would be great if you open a pull request with those changes in order to allow selecting the flashing port.
If not, I strongly recommend using micro-ROS component for ESP-IDF to integrate micro-ROS in your ESP32 project.


add subscription discount feature

how can we add discount on recurring charge ?
shopify has given this capability
https://shopify.dev/apps/billing/purchase-adjustments/subscription-discounts#creating-discounts

Hi, any update on this one?

hello, is there anyone working on discount feature?


Spike: Can we use immutables with hibernate?

For non-tenant tables, it would be nice if we could use hibernate for the data access. But initial impression is
there is not a good way to map immutables and hibernate entity classes.

Workin the issue...
Hibernate won't really work because the table names are tied to the classes. The tenant tables created
will use the same object, but whatever name. So I figure I'd try to do a minor ORM. This may be a mistake so I'm' willing to backtrack.

Closing. Talked to JNG and moving to jdbi instead.


Rethinking the dependencies badge

Let us know any feedback and ideas about our proposal for a new dependencies badge.
Try the new badge quickly by pasting your gemspec in our preview tool.

I think you have a good idea, and agree that the implied insistence on all dependencies being the latest at any given time is both unrealistic and counter-productive.  There are often quite reasonable and good reasons not have 100% of your dependencies being the very latest release.  Yet on the other hand, the generate state of dependency up-to-date-ness is a useful signal in evaluating software.  I like that you are trying to find a better way to communicate this signal, hard to say how will it will succeed without seeing it in practice.

@jrochkind thanks for the input!
I'm also curious about pursuing the score, but I was thinking it would lead towards somehow scoring the health of the library itself: is it well maintained, how many releases, open bugs, along those lines.

I looked at https://github.com/jaredbeck/libyear-bundler recently – it will tell you “how out-of-date your Gemfile is, in a single number”. A number like that (perhaps divided with the total number of gems in the application being checked) might be useful in your dependency badge.
Just ensure it works with private gem servers too, which I think libyear-bundler doesn’t. 😉

Thanks @bquorning, I didn't know about libyear, that's a very interesting approach.

Additionally it would be great to have badges per branch. I.e. development and release branches might differ a lot.


Split builder from operator

TODO:

[ ] Add a Build CRD controller to manage the build pod lifecycle
[ ] Polish the reconciliation with the IntegrationContext and Integration CRs lifecycle
[ ] Restore support for attaching resources to the build
[ ] Check / add compatibility with Knative build

https://github.com/knative/docs/blob/master/docs/build/creating-builds.md

[ ] Support concurrent builds
[ ] Support for concurrent-safe cached local Maven repository

https://issues.apache.org/jira/browse/MNG-2802
http://takari.io/book/30-team-maven.html#concurrent-safe-local-repository

About "Support concurrent builds" we need to be careful as this may end up not reusing a context or ot having a base image to reuse for incremental build.

I'll continue working on improvements but I think that PR has met the original requirement and grown large enough for it to be reviewed.

Love the pod mode, that is compatible with knative build..
I wonder if we should provide also a always-up build operator mode, to speed up builds also in kubernetes-without-knative-build environments

Love the pod mode, that is compatible with knative build..
I wonder if we should provide also a always-up build operator mode, to speed up builds also in kubernetes-without-knative-build environments

+1

Love the pod mode, that is compatible with knative build..
I wonder if we should provide also a always-up build operator mode, to speed up builds also in kubernetes-without-knative-build environments

Agreed. It should be quite straight forward with the existing building blocks. With that new builder service strategy, a deployment would be created, configured to delegate to the routine build strategy.


Checkpoints google drive link not working

Hello
The google drive link for the checkpoints shown in this message:
Google Drive applies a restriction on public large file downloading, if you find the checkpoint downloaded if None or small, please download it via browser: https://drive.google.com/file/d/10TQGpYnQqry9uGDPvSKkVPdieRhycnAh/view?usp=sharing
is not working. I navigated to the given gdrive link but it shows a Page Not Found error.

Hi,
Sorry for your inconvenience. I made some changes trying to fix the automatic downloading, but I failed.
Which checkpoints can not be found? Can you test and report to fix them?

Hi, @AdLucem
I made some updates to the checkpoint URLs; Please have a check.


[WIP] Test SearchEventListener method (task #8424)

This PR adds tests for the class SearchEventListener.
To achieve this we've introduced a new Fixture ThingsFixture and a new Table ThingsTable, which are only available in testing mode.

Codecov Report

Merging #697 into master will increase coverage by 0.14%.
The diff coverage is 70.58%.

@@             Coverage Diff              @@
##             master     #697      +/-   ##
============================================
+ Coverage     33.77%   33.91%   +0.14%
- Complexity     1213     1215       +2
============================================
  Files           108      108
  Lines          4089     4095       +6
============================================
+ Hits           1381     1389       +8
+ Misses         2708     2706       -2

Impacted Files
Coverage Δ
Complexity Δ

...t/Plugin/Search/Model/SearchableFieldsListener.php
28.3% <70.58%> (+28.3%)
37 <6> (+2)
:arrow_up:

src/Swagger/Annotation.php
81.77% <0%> (-10.84%)
57% <0%> (ø)

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 78d2117...da72a4a. Read the comment docs.


Fix archive all button at bottom

Describe your changes and why you are making these changes
Make archive all button visible at all times in the notifications list.
Linear: https://linear.app/aqueducthq/issue/ENG-1199/make-archive-all-button-visible-at-all-times-in-the-notifications-list
Loom: https://www.loom.com/share/b6e87652b77c4d8fa4606fbf99d2975f
Related issue number (if any)
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[x] If this is a new feature, I have added unit tests and integration tests.
[x] I have manually run the integration tests and they are passing.
[x] All features on the UI continue to work correctly.

Wrong branch


Remove unneeded comment

I tried re-running CI a couple of times without success. It seems that #64 introduced some instability in the test suite:
=========================== short test summary info ============================
FAILED tests/func/test_quaternion.py::test_quaternion_from_axis_angle_roundtrip - hypothesis.errors.FailedHealthCheck:
It looks like your strategy is filtering out a lot of data. Health check found 50 filtered examples but only 9 good ones.
This will make your tests much slower, and also will probably distort the data generation quite a lot.
You should adapt your strategy to filter less. This can also be caused by a low max_leaves parameter in recursive() calls
See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more information about this.
If you want to disable just this health check, add HealthCheck.filter_too_much to the suppress_health_check settings for this test.
================== 1 failed, 62 passed, 60 warnings in 11.06s ==================

@Korijn Ah damn. I thought we could run a stricter unit test in #64 but it looks like hypothesis is too good at finding values that produce large numeric errors.
I will have a look.

@Korijn CI is passing now. I separated two test scenarios to make it easier to generate valid example inputs (hypothesis was complaining that it was too hard to find good inputs), and now it seems that hypothesis is happy again.


Migration seeds

Add pragma seed command that takes a GraphQL document and executes it.
We also need to add a config seeds which is a path pattern such as ./seeds/*.gql and takes all of these documents and executes them on the first migration (every run in dev mode, and only once in production mode)

This is not very important now, because you can solve any problem that this feature solves with super user (root user) access. Checkout #67.


EC:<IP_ADDRESS> / EC:<IP_ADDRESS> / EC:<IP_ADDRESS>

Looking at these three ECs (following on from #28243):
EC:<IP_ADDRESS>
malate dehydrogenase (oxaloacetate-decarboxylating)
(S)-malate + NAD(+) <=> CO2 + NADH + pyruvate
H(+) + oxaloacetate <=> CO2 + pyruvate
EC:<IP_ADDRESS>
malate dehydrogenase (oxaloacetate-decarboxylating) (NADP(+))
(S)-malate + NADP(+) <=> CO2 + NADPH + pyruvate
H(+) + oxaloacetate <=> CO2 + pyruvate
EC:<IP_ADDRESS>
oxaloacetate decarboxylase
H(+) + oxaloacetate <=> CO2 + pyruvate
They are term/def xrefs on the following 3 GO terms - I've suggested what needs to be done to make the relationships clearer. Let me know if you agree @pgaudet (this issue is on the #26235 list/spreadsheet, marked as 'to discuss')
id: GO:0008948
name: oxaloacetate decarboxylase activity
def: "Catalysis of the reaction: oxaloacetate = pyruvate + CO2." [EC:<IP_ADDRESS>, EC:<IP_ADDRESS>, EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: EC:<IP_ADDRESS>
xref: EC:<IP_ADDRESS>
xref: RHEA:15641

[ ] xref: EC:<IP_ADDRESS> -> make broadMatch
[ ] xref: EC:<IP_ADDRESS> -> make broadMatch
[ ] xref: EC:<IP_ADDRESS> -> make exactMatch
[ ] Replace def xref with RHEA:15641

id: GO:0004471
name: malate dehydrogenase (decarboxylating) (NAD+) activity
def: "Catalysis of the reaction: (S)-malate + NAD+ = pyruvate + CO2 + NADH + H+." [EC:<IP_ADDRESS>, EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: EC:<IP_ADDRESS>
xref: RHEA:12653

[ ] xref: EC:<IP_ADDRESS> -> make broadMatch
[ ] xref: EC:<IP_ADDRESS> & xref: RHEA:12653 -> make exactMatch
[ ] Replace def xref with RHEA:12653

id: GO:0004473
name: malate dehydrogenase (decarboxylating) (NADP+) activity
def: "Catalysis of the reaction: (S)-malate + NADP+ = pyruvate + CO2 + NADPH + H+." [EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: RHEA:18253

[ ] xref: EC:<IP_ADDRESS> -> make broadMatch

We should also look at phosphoenolpyruvate carboxylase activity when lookin at this group. phosphoenolpyruvate carboxylase activity seems to be under the wrong parent.

Not sure about this but as the malate reaction is the predominante one could
xref: EC:<IP_ADDRESS> -> make ExactMatch
in

id: GO:0004473
name: malate dehydrogenase (decarboxylating) (NADP+) activity
def: "Catalysis of the reaction: (S)-malate + NADP+ = pyruvate + CO2 + NADPH + H+." [EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: RHEA:18253
xref: EC:<IP_ADDRESS> -> make broadMatch

and
xref: EC:<IP_ADDRESS> -> make ExactMatch
in

id: GO:0004471
name: malate dehydrogenase (decarboxylating) (NAD+) activity
def: "Catalysis of the reaction: (S)-malate + NAD+ = pyruvate + CO2 + NADH + H+." [EC:<IP_ADDRESS>, EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: EC:<IP_ADDRESS>
xref: RHEA:12653
xref: EC:<IP_ADDRESS> -> make broadMatch
xref: EC:<IP_ADDRESS> & xref: RHEA:12653 -> make exactMatch
Replace def xref with RHEA:12653


Is there a way to proceed or revert a destructive action based on dialog?

I would like to know if it's possible to begin a swipe or click on the button and show a dialog, upon which the swipe would conclude if the user taps on "Yes" while revert it back if the user cancels/dismiss it.
So, basically:

If the user taps on the delete button on the indented cell, the dialog should appear.
If the user swipes until the end, it should revert to the indented or initial state and present the dialog as well.

If the users taps "yes", I should call some method to delete the cell from the tableview, (the destructive action). Otherwise, the cell would stay as it is and the dialog would just be dismissed.
Since I know how to handle the dialog, I would just like guidance on whether this is possible and what I should do on the swipe cell delegate methods to achieve this behavior.

Hey Luke, thanks for the answer.
I had figured out the action.fulfill(with: .delete). I tried your approach to hidesWhenSelected = false but it was quite bad to get the cell back.
I figured out the best way to do what I want is to have expansionStyle = .none such that the cell can never leave the screen by a swipe, but rather be at maximum at the indentation point where "cancel order" button appears. By clicking on "cancel order" the dialog appears, by which if the user dismiss it by swiping or clicking on "dismiss". If the user clicks on "yes", then I fulfill the deletion with self.arr.remove(at: indexPath.row) and action.fulfill(with: .delete). The deletion doesn't play as nice as a destructive action though.
If you can come up with a way to have a destructive action that can at most be indented (cell never leaves screen until action.fulfill: is called), that would be great