Server components rendering and streaming

Switch from client side compilation and rendering to React Server Components rendering with experimental support for streaming.
Streaming is disabled by default but can be enabled by setting the RAPIDPAGES_UNSTABLE_STREAMING environment variable to true. Streaming will work only on Vercel serverless and Node.js.
Primary files to review:

pages/api/generate.ts (generation endpoint with authentication)
utils/compiler-mode.ts (compile JSX to React and evaluate)
utils/render.tsx (helpers to render to JSON response or streaming with RSC)
components/PageEditor.tsx + public/g/_client.js where client side rendering happens

Few comments @gsppe

Is there a way to test RAPIDPAGES_UNSTABLE_STREAMING=true locally?
When RAPIDPAGES_UNSTABLE_STREAMING=false, there's no longer a loading splash. We can remove the splash and have a loading indicator on the next screen to simplify the code but we need some indicator.
Is there a way to make it work without npm force install?


Added more failure handlers to basic tests

What this PR does
More debugging if tests fail.
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites

CAPVCD failure known flake, adding skip label


pdf.js coding quote

Hello all.
I have a client that is looking to get a quote for a custom pdf.js plugin for Wordpress.  I was recommended to come to this site by someone in this community.  Is this the appropriate space to ask?  If not, please direct me to the appropriate url to ask this question to pdf.js coders.
Thanks

This issue tracker is only meant for development of the PDF.js library itself, not for third-party plugin development. I think you should ask this in the Wordpress developer community since I don't think anyone here has experience with this. You could also try asking on IRC (irc.mozilla.org, #pdfjs channel).


OpenSCENARIO support - PrivateActions

This issue is meant to track the support of PrivateActions within OSC 1.0:

[x] ActivateControllerAction (Activates CARLA's autopilot)
[x] ControllerAction
[x] LaneChangeAction (Some dynamics are still ignored)
[ ] LaneOffsetAction
[ ] LateralDistanceAction
[ ] LongitudinalDistanceAction
[x] SpeedAction
[ ] SynchronizeAction
[x] TeleportAction
[ ] VisibilityAction
[x] AcquirePositionAction
[x] AssignRouteAction
[ ] FollowTrajectoryAction

Thanks for working on improving support for OSC1.0! :+1:
I am especially interested in support for the LaneOffsetAction.

As of #628, AcquirePositionAction is now supported at the Story part

As of #689, SynchronizeAction is now supported


Ft/add sourceAfrica documents to datasets page CMS setup

Description
This PR implements the ability to add documents on the datasets page.
This change includes introducing a new field in the datasets block showDocuments which allows the configuration of the sourceAfrica group to fetch the documents.
Fixes
This is a partial fix for #441
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Screenshots

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

@kilemensi This is ready for review

Why can I set document group but not dataset group?

@kilemensi This is because the datasets group/organization is set in the globals section, but we can definitely let it be set in this block. One of the reasons why we set it in the globals was because of the flourish charts section where we had to develop a CRON job to update datasets statistics.

Why can I set document group but not dataset group?

@kilemensi This is ...

Thanks @kelvinkipruto ... Since we no longer need datasets statistics, removing it from global seems like the logical next step, no?

@kilemensi After reviewing Pesayetu, we may have to rethink this slightly. I thought they would all be on one page /resources/datasets. With the current implementation, we're managing which tab is active
I really like Pesayetu's approach where we can use /resources/datasets and /resources/documents. This will require that I refactor this a little bit but it should work well.

@kilemensi After reviewing ...

Cool @kelvinkipruto, I also like the PesaYetu approach. Let me let you cook. Ping me when it's ready for 👀 .

QQ @kelvinkipruto : Looks like you've separated Datasets and Documents block. Where the tap/button switching info come from?

@kilemensi The buttons will switch between two pages resources/datasets and /resources/documents. This will also require the creation of two pages in the CMS with parent resources. The /resources/datasets page will continue to be handled as before, and /resources/documents will be handled by a new function processPageDocuments.

I meant as far as the CMS is concerned, where does the content team see this button that switches between datasets and documents pages @kelvinkipruto .

@kilemensi If in the CMS this has to be visible, then the best approach would be to manage the state of which tab is active instead of using different pages.

@kilemensi If in the CMS this has to be visible, then the best approach would be to manage the state of which tab is active instead of using different pages.

@kilemensi If in the CMS this has to be visible, then the best approach would be to manage the state of which tab is active instead of using different pages.

Why? In datasets block, you can have a show documents checkbox and if selected, we show a dropdown with a list of pages for editors to select the documents page to switch to. We do the opposite in documents block.
No state management necessary.

In datasets block, you can have a show documents checkbox and if selected, we show a dropdown with a list of pages for editors to select the documents page to switch to. We do the opposite in documents block.

@kilemensi I'm a little bit lost here. Why would they need to select a page? The data required for both the resources/datasets and resources/documents are all in the DatasetsAndDocuments block.
Here are two approaches I'm thinking about:

(Current Implementation) In the CMS, the editors will create a resources/datasets page and add the DatasetsAndDocuments block as is currently. This allows them to configure both datasets and documents in a single block. This is then processed in the processPageDatasets function. The only issue I have with this is that the editor will have to create an empty resources/documents page in the CMS if we're to go with Pesayetu's approach and not the state-managed way.
In the CMS, the user will have to create two pages, resources/datasets and resources/documents. We then split the DatasetsAndDocuments block into two, one for datasets and another for documents. These pages will then be processed independently of each other.

@kilemensi I'm a little bit lost here. Why would they need to select a page? The data required for both the...

Because clicking show documents/datasets will then load that page that they've selected @kelvinkipruto. You're assuming pages have to always be named resources/datasets and resources/documents but if we switch to block-based rendering, this block can be added into any page linking into any other page.
On the approach:
I prefer the stateless approaches i.e. everything you need is rendered on the server and you just get a page so approach 2 is more to my liking.

Ok @kilemensi I maybe get you a little bit
Here is how I'm interpreting it:
First, the editors create two pages in the CMS, say datasets and documents. These are the pages to be rendered when the user clicks the switch button.
They then create a third page and add the DatasetsAndDocuments block, from where they can select the two created pages as pages for datasets and documents.

No @kelvinkipruto . Based on approach 2 you outlined above:

In the CMS, the user will have to create two pages, resources/datasets and resources/documents. We then split the DatasetsAndDocuments block into two, one for datasets and another for documents. These pages will then be processed independently of each other.

We have a Datasets block with ability to link to documents via showDocuments, and
We have a Documents block with ability to link to datasets via showDatasets.

Content editors can choose to have these in any page that they want (for now of course it will be /datasets and /documents page until block-based rendering is fully implemented). The Datasets block can even be used in the consultation page by toggling showDocuments to false.

@kilemensi Yes. Now Cooking...

@kilemensi It is now ready for re-review

How can you say this is ready for review @kelvinkipruto when I still see tabs are still there?
Have you actually fully tested it or you expect others to do that for you?

@kilemensi I have tested it. I have used the tabs to separate the datasets and the pages to link to. See the above screenshots.

@kilemensi I have tested it. I have used the tabs to separate the datasets and the pages to link to. See the above screenshots.

Good thinking but (my thoughts are) tabs are for showing multiple independent things on the same window @kelvinkipruto. What we're going for is more of "would you like a coke with your fries?" i.e. if in documents, we're saying datasets would go well with documents. Hence they should be in the same panel, probably as a group.
... what do you think? (@koechkevin also if you have any thoughts).

@kilemensi I have removed the tabs.


Notify the claimant of their application

So that a user has confidence that they have finished a thing, and so they have a record of having completed their application, we will send the user an email confirming their claim.
We want to include a reference number so that it is easy to find their claim if they need support.

Que to process background jobs
GOV.UK Notify for sending ActionMailer emails

The content used is just temporary and is from the confirmation page.
Also updated the confirmation page to show the reference number as well.

 Notify the claimant of their application

I need to add some instructions to the readme. If you need an invite to Notify let me know

@erbridge I've made those changes, ready for another look

@mec I must've missed that first time round reading the docs, it isn't as obvious on the pre 1.0 branch. 1.0 as still in beta: https://github.com/chanks/que/tree/0.x
It says it's highly recommended that we switch. We'll have to make sure we're all on the same version of Postgres or we'll get issues like we saw before. Maybe Que isn't the right solution?

@robbiepaul we should all talk, like we did last time. It seems like we will always use PG so it's a given, but the version problems might be an issue, I'd want to know more before we made any jump?

It does say 'You can use schema_format as :ruby if you want but keep in mind this is highly advised against, as some parts of Que will not work.' – worth understanding which 'parts' first?

@tekin I've changed the request spec to check the contents of ActionMailer::Base.deliveries
I've set up a new API key for staging that will only send to 'Team and whitelist' and I've put the environment variables in to Heroku


Add support for conda

Will soon be available in release 0.30.x. See:
https://github.com/nextflow-io/nextflow/blob/master/docs/conda.rst
https://github.com/nextflow-io/nextflow/blob/master/docs/process.rst#conda
https://github.com/nextflow-io/nextflow/blob/master/docs/config.rst#scope-conda

Yes - it ties in perfectly with what we're doing. Basically we should be able to add one extra line to the config with a reference to the environment.yml file that we already have, then people can use -with-conda when they run the pipeline, in addition to -with-singularity and -with-conda.
So basically, just add this I think:
process.conda = 'environment.yaml'

But needs testing etc. For example, I have no idea if the relative file path works.
Phil

Yes, it can be integrated in the current structure we already have. But then we will lose reproducibility, as people can run software outside of a container environment for nf-core pipelines. And I thought we wanted to encourage people to use either Docker or Singularity (for HPC) in the first place.
So we might need to add a warning in the doc then, if the -with-container or -with-docker flag is omitted, the reproducibility of the results is not likely anymore.
What do you think?

Yes. I think that having it optionally available and then e.g. use it for testing purposes and make a Container later for production would be quite fancy ! So we should make it available and test it quickly whether this works !

Ok, I got your point :)

This issue was moved to nf-core/tools#91


try & except when doing the API call.

try & except when doing the API call. Returns success False if request failed!

see #67


⚠ Bofrost.es has degraded performance

In 855803b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1527 ms

Resolved: Bofrost.es performance has improved in c783134 after 13 minutes.


NIFI-751 Add Processor To Convert Avro Formats

Implemented a new NiFi processor that allows avro records to be converted from one Avro schema
to another. This supports..

Flattening records using . notation like "parent.id"
Simple type conversions to String or base primitive types.

Alan,
Thanks for contributing!  We'll work with you to get this promptly merged.  Here are some findings of an initial review:

Please run the build with 'mvn clean install -Pcontrib-check'.  You'll find there many formatting issues.  It appears that many of the lines have had extraneous newlines and tabs added to them.  Please take a look and tweak until the contrib check runs cleanly and that you still think the code looks good.

There do not appear to be any unit tests for the processor itself.  I do see a couple unit tests for the converter class/logic which is good but it is best to also have a test or two, particularly for something that seems as easily tested as this one is.  You can find lots of examples throughout the codebase including in this kite bundle.

The conversion routines for Long, Double, Float, etc.. you really should consider adding regex checks before calling those methods.  Since the Java methods use exception handling for flow control the performance penalty can be extremely severe compared to simply doing a regex check beforehand.  In the event that the data is clean you'll be good to go but when it isn't the impact to the system as a whole can be dramatic.  Given the nature of this sort of processor that is probably something to tackle right away.

This processor is probably a great candidate to use the 'Advanced Documentation' feature.  Users will need this to understand the schema/syntax of the conversion configuration and examples would go a long way for that.  You can see more about this here http://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#advanced-documentation and there are some examples in the existing standard processors to consider.

There are a couple of copy/paste errors in the processor from the CSV/Avro converter.  Look for these "Failed to convert {}/{} records from CSV to Avro" and "Failed to convert {}/{} records from CSV to Avro"

I realize this looks like a lot of stuff but it should be pretty easy to address and is a good first step.  If you have any questions on it just let us know.
Thanks
Joe

Made many changes here, including I believe all of Joe's suggestions and the majority of Ryan's. A few little notes:

I wound up using Scanner to do the text parsing. I figured Scanner probably knows better how to parse numbers than I do. However, that does mean that text like "123 Fake Street" will convert to int which is a little questionable. Should be easy to write up a full-regex version if we decide we want that.
The code for sending just the failed records down the error relationship got a little nasty. It calls session.write on a copy of the incoming flowfile, then completely ignores that flowfile and uses the failed records it collected during the first pass through the input data.

Alan - excellent and thanks!  Do you mind providing a rebased/squashed commit?

rebased to upstream/develop and squashed into one commit.

@rdblue You might want to double check the CSV and JSON to Avro processors and add documentation to them like Alan has done here (additional documentation).  Providing an example of usage could be a big help to folks.   Also please verify whether your processor needs to accept the hadoop configuration.  If not you can simply remove it from the properties being added.
@jackowaya Great job!  I've made a small change to remove the pulling in of the hadoop configuration property.

i just want to add how easy this was to test.  We're definitely going to build an avro viewer like we have for JSON, XML, etc.. because of this cool use case.
I setup a 'generate flow file' and replace text to make some CSV lines then ran that into "Convert CSV to Avro" and a "ConvertAvroSchema" all using Alan's example schemas.  And i didn't have it right at first because my id wasn't a long and my revenue wasn't a double.  But that was obvious as it told me right in context.  So i could just easily iterate and go.
It is a good example of taking a cool project, Kite, and combining it with the power NiFi has to make these things interactive to quickly iterate and building something useful.
Nice job Alan and Ryan!

Hey @joewitt somehow I dont see AvroRecordConverter in NiFi's available Processors. I need to be able to convert an incoming source file (CSV/XML/JSON) to a generic schema. However, the problem is I am not sure how to - 1. Convert a AVRO 'record'  type to another and 2. When using ConvertAvroSchema how do we specify the dynamic properties as specified in the NiFi documentaion here - https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.kite.ConvertAvroSchema/index.html
Please advice. Thank you.


Invalid picture dimensions / size?

Hi,
various 3rd party clients seem to stumble upon this error:
[MessagesManager33.cpp:247][#1][!Td] Failed to send yet unsent message 3775.25 in chat -955389183 with the error [Error : 400 : PHOTO_INVALID_DIMENSIONS]
https://github.com/zhukov/webogram/issues/726
https://github.com/majn/telegram-purple/issues/79
https://github.com/nickoala/telepot/issues/135
https://forum.sailfishos.org/t/the-volla-22-gigaset-gs5-thread/12939/288?u=jcoder
Can you elaborate a bit what are the rules for pictures? One user mentiones a file of 4,5MB or so, it does not sound too big these days ;)

The restrictions are described in the documentation of inputMessagePhoto:
//@photo Photo to send. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20


Add Blox higher ed institution

Blox is a Brazilian EdTech company founded in 2018, focused on introducing a new concept of modularity in higher education. We have served dozens of Higher Education Institutions.
In 2021, we made the decision to become a higher education institution ourselves. After more than three years of rigorous review, we received approval from the Ministry of Education in Brazil.
You can find Blox’s listing on the Ministry of Education’s website here: https://emec.mec.gov.br/emec/consulta-cadastro/detalhamento/d96957f455f6405d14c6542552b0f6eb/MjU1MzY=
In Brazil, the “edu.br” domains are reserved exclusively for registered higher education institutions. You can find the approval for our domain here: https://registro.br/tecnologia/ferramentas/whois?search=blox.edu.br
Blox will offer distance learning programs specializing in IT, Programming, Data Science, and Business (all tech-related fields).
We can provide any extra legal documents necessary to prove our status as a fully accredited higher education institution, including translations if needed.

@bruno-berchielli Thank you for your request. As far as I understand, your core business is not teaching per se, but providing different educational organizations with a software platform enabling online education.
This kind of platforms are not eligible for JetBrains free educational subscriptions, because even there are some full-time students studying at your platform, they usually have an affiliation with traditional university, and therefore can get a free license there.
If you think that I misunderstood the purpose and operational details of your organization, please send us an email to<EMAIL_ADDRESS>for further discussion.
Your students also can try and enroll to GitHub Student Developer Program at https://education.github.com/discount_requests/application. Then they can apply for JetBrains educational subscription with their GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).
I have to close this request without merging.
Thank you for your understanding!


feat(upload): support rtl

Codecov Report
Base: 62.49% // Head: 62.52% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (28b0d8b) compared to base (fa74061).
Patch coverage: 93.10% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4371      +/-   ##
==========================================
+ Coverage   62.49%   62.52%   +0.02%
==========================================
  Files        1069     1073       +4
  Lines       22420    22443      +23
  Branches     5882     5884       +2
==========================================
+ Hits        14011    14032      +21
  Misses       6881     6881
- Partials     1528     1530       +2

Impacted Files
Coverage Δ

src/transfer/src/Transfer.tsx
58.20% <75.00%> (-0.26%)
:arrow_down:

src/upload/src/Upload.tsx
60.08% <75.00%> (-0.10%)
:arrow_down:

src/styles.ts
100.00% <100.00%> (ø)

src/transfer/src/styles/rtl.cssr.ts
100.00% <100.00%> (ø)

src/transfer/styles/index.ts
100.00% <100.00%> (ø)

src/transfer/styles/rtl.ts
100.00% <100.00%> (ø)

src/upload/src/styles/rtl.cssr.ts
100.00% <100.00%> (ø)

src/upload/styles/index.ts
100.00% <100.00%> (ø)

src/upload/styles/rtl.ts
100.00% <100.00%> (ø)

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.


Run app through quality gate

Run app through a static code analyzer to find issues.

@Sheeri
Now we are able to run Static Analyzers any time. Should we close this ticket and create a new one with CI / CD flow ?

Yes, please do.


The registration ID is alphanumeric, case insensitive, ...

The description for the registration id states

The registration ID is alphanumeric, case insensitive, and may contain special characters including colon, period, underscore and hyphen.

but what's really implemented is:
The registration ID is alphanumeric, lower case, and may contain special characters including colon, period, underscore and hyphen.
If you try to enroll a device with the certificate containing CN=ABCD123, it will fail, because the registration id can only contain lower case characters.

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

ID: 99cde61d-0cab-c249-4a33-ab8d49105ceb
Version Independent ID: 16535131-6077-d876-da32-f1c755a9629a
Content: Device concepts in Azure device provisioning
Content Source: articles/iot-dps/concepts-device.md
Service: iot-dps
GitHub Login: @nberdy
Microsoft Alias: nberdy

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

@smstuebe Can you please provide more details on how you are enrolling the device? The registration IDs are case-insensitive, but it may be that the tool you are using to enroll devices does a case-check that is blocking enrollment.

@nberdy
I just wanted to show you my code and the exception details and then I noticed, that the validation came from the sample code I copied 🤦♂ I removed the validation and I could successfully register a device with a registration id containing upper case letters. So the docs are fine. Sorry 😔
But if this is allowed: Why does the sample contain this validation? Or is this not in your responsibility?
Sample code:
https://github.com/Azure-Samples/azure-iot-samples-csharp/blob/master/provisioning/Samples/device/Common/ProvisioningDeviceClientSample.cs#L70-L77

No worries, I'm glad you got it working!
I don't maintain the sample code, and sometimes samples get missed when we make service changes. Could you please file an issue on the sample asking them to remove the validation? That would be a big help towards making sure others don't hit the same problem you encountered.

kk. will do. thanks for the quick response.


MM-35674 Detox/E2E: Add e2e for autocomplete and at-mention

Summary

Added tests for MM-T168, MM-T169, MM-T170, MM-T171, MM-T172, MM-T1798, MM-T2349 in

detox/e2e/test/autocomplete/autocomplete.e2e.js
detox/e2e/test/messaging/at_mention.e2e.js

Fixed duplicate name issue
Added new testIDs, added new helper functions modified generateRandomUser to have shorter values, modified getAtMentionItem to return child elements and updated affected tests

Note: @anurag6713 I added you in this PR because I had to remove the dupe name in the autocomplete. Not sure if you're already fixing it on another PR but just making you aware that I'm removing the dupe to make the tests pass.
Ticket Link
JIRA tickets:

https://mattermost.atlassian.net/browse/MM-35674

Zephyr cases:

MM-T168
MM-T169
MM-T170
MM-T171
MM-T172
MM-T1798
MM-T2349

Screenshots

Release Note
NONE

/cherry-pick release-1.44

Cherry pick is scheduled.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-mobile
 * [new branch]          build-pr-5409-cdebf29 -> upstream/build-pr-5409-cdebf29
   2e6470ac8..49e29790f  post-list             -> upstream/post-list
   32a353bd9..cf88a2ae8  release-1.44          -> upstream/release-1.44
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-mattermost-mobile-#5404-upstream-release-1.44-1622743618
Switched to a new branch 'automated-cherry-pick-of-mattermost-mobile-#5404-upstream-release-1.44-1622743618'
Branch 'automated-cherry-pick-of-mattermost-mobile-#5404-upstream-release-1.44-1622743618' set up to track remote branch 'release-1.44' from 'upstream'.

+++ About to attempt cherry pick of PR #5404 with merge commit 19196170dc78751b553030a1a4be99acaa6d3663.

The previous cherry-pick is now empty, possibly due to conflict resolution.

Joseph mentioned that this PR fixes https://mattermost.atlassian.net/browse/MM-36110, so this can be cherry-picked to v1.44. @anurag6713 @enahum

@josephbaylon please do a manual cherry-pick for this PR


Baking chunk size for sequences

Changelog Description
Supporting deadline rendering of Nuke baking jobs (Extract Review Intermediate) with multi chunks.
The Chunk size is copied from the ayon+settings://deadline/publish/NukeSubmitDeadline/chunk_size
Additional info
Might close https://github.com/ynput/ayon-nuke/issues/3
Testing notes:

Set Extract Review Intermediate to jpg
Make sure you do not have Nuke Slate present (see bug)
Publish Nuke render on Deadline
Check Number of tasks for baking job in Deadline Monitor, it should be > 1

If this PR is about to have chunk size dynamic for Baking job, it will be obsolete by https://github.com/ynput/ayon-deadline/pull/49 where it will be controlled by Profile/could be overridden by artist.
Would it be important to separate chunks/other JobInfo fields per render vs baking job (eg. have different chunk for render, different one for baking)? Currently it is not possible, not sure how the model in Setting would like for that.

If this PR is about to have chunk size dynamic for Baking job, it will be obsolete by https://github.com/ynput/ayon-deadline/pull/49 where it will be controlled by Profile/could be overridden by artist.

Actually - I think what the intent is.. is that if you were to write out a video file you want the chunk size to be infinitely large because multiple machines couldn't render out to the same file. Something tells me - that is what this is trying to solve.
If media has # in it - allow chunk size to be configurable.
If media does not have # it's a single file, and we assume multiple machines can't simultaneously write to.
To easily support that in an abstract plug-in we may need some way to identify that a job MUST be one task or not due to that. Like "singleTaskOnly" or "forceSingleTask" or whatever.

Actually - I think what the intent is.. is that if you were to write out a video file you want the chunk size to be infinitely large because multiple machines couldn't render out to the same file. Something tells me - that is what this is trying to solve.

Correct. Of course, having confugurable chunk size for baking sequences would be great. Possibly even Deadline Frame Dependencies, so baking can start right even frame finishes. Just taking the same chunks as the render is easy and should already help quite a bit.
I am trying to solve very slow publishing of long highres shots. Sometimes, particullarly for episodic vfx, we have shots that are one, or two minutes long. Production get gray hair when publish is on the farm one more hour just to produce baking mov.

I am trying to solve very slow publishing of long highres shots. Sometimes, particullarly for episodic vfx, we have shots that are one, or two minutes long. Production gets gray hair when publish is on the farm one more hour just to produce baking mov.

Valid use case - and has come up before. I think there was an epic description about that some time ago @antirotor? But definitely quite some dev work.

Closing in favor of https://github.com/ynput/ayon-deadline/pull/49


OAuth Prompt should NOT send 200 if its DOESN'T find the magic code

Currently the JavaScript OAuth Prompt always sends a 200 as follows:
else if (this.isTeamsVerificationInvoke(context)) {
const code: any = context.activity.value.state;
await context.sendActivity({ type: 'invokeResponse', value: { status: 200 }});
token = await this.getUserToken(context, code);
}
However, ideally if should not send the 200 if it didn't find the magic code, in this case it should send 404 or if there was a failure in the call, in this case it should send 500.
Refer to the C# for the details of the fix @mingweiw made. And refer to https://github.com/microsoft/botbuilder-dotnet/issues/1913

@mingweiw fix in C# is here:
https://github.com/microsoft/botbuilder-dotnet/pull/1979


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
7.0.5 -> 7.0.6

terraform-ibm-modules/transit-gateway/ibm (source)
module
patch
2.3.0 -> 2.3.1

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v7.0.6
Compare Source
Bug Fixes

deps: update terraform-module (#468) (2419d7e)

terraform-ibm-modules/terraform-ibm-transit-gateway (terraform-ibm-modules/transit-gateway/ibm)
v2.3.1
Compare Source
Bug Fixes

prefix has random bit now (#419) (ee34e28)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 7.13.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Performance analysis on 2.13

The client noticed a problem a loss of performances between the version 2.12 and 2.13.

After analysis no visible performance loss has been seen in real case.


Bug?: SqlException: Incorrect syntax near ')'

Greetings.
I came across this error/bug (?) a few times already:
When I call Query() in BaseRepository<TEntity, TDbConnection>:
var collection = new List<int>(); // Count = 0
return Query(e=> collection.Contains(e.Attribute));

If the collection is empty it throws this exceptions:
SqlException: Incorrect syntax near ')'.
Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, bool breakConnection, Action<Action> wrapCloseInAction)

The SQL code (grabbed from SQL Server Profiler) being generated is:
SELECT [Attribute], [OtherAttribute] FROM [Table1] WHERE ([Attribute] IN ()) ;

Had this issue in March and took this screenshot back then: https://i.imgur.com/ekmP9RS.png
Is there any solution other than this:
var collection = new List<int>(); // Count = 0
if(!collection.Any())
    return Enumerable.Empty<T>();
return Query(e=> collection.Contains(e.attribute))

Thanks!

Never I simulated this one yet, but it seems that the collection is empty, so the array parameter is not constructed properly during the query statement creation of the query builder.
The fix is to add a condition in your side before you call the method, however a proposal would be good for this as you are the actual user with real use-case (itself).
Do you want the library to throw you an empty exception or should I skip the execution?

I don't mind adding the condition.
But I think the library should skip the query execution since it would prevent this situations.
The code should have the same behavior with or without items.
Skip would be ideal.
Thanks!

Thank you for your answer and also for reporting this case. We will assess how to fix this together with your proposed solution. For now, just leave this open.

The fix: It would throw an exception if the list is empty. By having this behavior, we are ensuring that the invalid call will be noticed and fixed by the developer itself, rather than silently skipping the execution. I hope this would work on your end.

I will better assume that the RpoDb is enought smart to not append the 'WHERE ([Attribute] IN ()) ' if the list is empty.
It's not an error from the developer.

@sellig - thank you for the push back. Without appending the supposed WHERE would trigger an unexpected behavior (i.e: it will return all the records). If we are to call the BETWEEN, we are also throwing an exception if the value of the array is more than 2. In anyway, I think, I will just ignore the execution or will just execute it but by having a 'FALSE' expression like (WHERE 1 = 0) or something like that.

Btw, just to let you know, EF is doing exactly the same as I tested it now.
> SELECT [p].[Id], [p].[Age], [p].[CreatedDateUtc], [p].[DateOfBirth], [p].[ExtendedInfo], [p].[IsActive], [p].[Name] FROM [Person] AS [p] WHERE CAST(1 AS bit) = CAST(0 AS bit)

I will prefer your implementation having a 'FALSE' expression and so return no record.

I had issued a beta release for you at RepoDb 1.11.4-beta3. Kindly upgrade your copy by simply installing such version.
> Install-Package RepoDb -version 1.11.4-beta3

@nunomcardoso and @sellig , I am closing this issue now. Please revert if you have questions with regards to this issue. Thanks


Add @deprecated filter to Setting GUI search input

Currently there seems to be only 3 predefined filters @ext / @modified / @tag:usesOnlineServices
It might be useful to get all deprecated settings.

Deprecated settings are not even shown in the settings UI at all. I'm not sure we want to make them more discoverable. Why would this be useful for you?

Why would this be useful for you?

They are often deleted/renamed before I notice them.

I was just scrolling and there was a flash of a different color:

I think it would be better if all of the deprecated settings were shown in Settings GUI.

I still don't know, typically we deprecate settings but still respect them if they are set. We aren't expecting anyone to have to keep on top of deprecated settings to migrate them every month, or anything like that. If there is something important that people need to know about a setting, it is typically in the release notes and I think that is a better place for info like that.


KAFKA-4555: Using Hamcrest for expressive intent in tests

Adding hamcrest in gradle files
Using hamcrest in couple of tests - SourceTaskOffsetCommitterTest, MetadataTest

Not sure again whats up with jdk 7 on jenkins. Unrelated to this PR. Please review. @ijuma thanks

If you could also review this one @ijuma would be great.thanks!

Thanks for the PR. Not sure about it though. It seems to conflate two separate notions: using Hamcrest and checking the message of the exception in a couple of tests.

Yes intentionally, to get it in and in the bloodstream @ijuma - What do you suggest? Please let me know. thanks!

@rekhajoshm I think @ijuma is getting at the fact that Hamcrest is probably more useful for replacing some assertions that aren't related to messages -- probably the extent of asserting things about messages that I'd expect is to include important parameters like timeout values, not very specific strings for the messages.
A more realistic use that could be used as a test is to replace some assertEquals, assertNull, and assertNotNull with assertThats using Hamcrest matchers. These are probably our most commonly used assertions. We obviously wouldn't want to convert everything, but they will validate the introduction of Hamcrest and allow us to start using other matchers as well.

thanks @ewencp for your comments. updated few more tests for illustration purpose.will create another PR for bulk changes on hamcrest eventually. the idea is once this PR is in, people can start using hamcrest in their tests as well.thanks, and a happy new year!

Thanks @rekhajoshm. Unfortunately, these updates don't seem to improve the code. As far as I can tell, Hamcrest is beneficial when assertions like contains and such are needed. For simple equals and null, the simple methods are actually more concise.

One other thing: I think it may be better to go directly to JUnit 5 (once we move to Java 8) instead of introducing Hamcrest right now.


For version 2.54, there are no download builds for linux amd64.

Hello
For version 2.54, there are no download builds for linux_amd64.tar.gz
https://github.com/chrislusf/seaweedfs/releases/tag/2.54
there is only the source code of the zip file
can you fix that ?

this is caused by the migration of travis-ci.org to travis-ci.com
Adding a version 2.55 to resolve this.

Thank you.


[DATA REQUEST] 20km regional projections for CORDEX-CMIP6 from the Queensland Future Climate Science Program

Description of the data product
This dataset includes projections at 20km, formatted to meet the CORDEX-CMIP6 data standards. The 20km projections were derived from the 10km projections.
Location of the data product on Gadi
Catalog available in /g/data/ig45
Checklist
Add a "x" between the brackets to all that apply

[X] This data product is stable (unlikely to change substantially or move)
[X] This data product is of use to the broader community
[X] This data product is documented: link
[X] This data product is licensed under Creative Commons Attribution 4.0 International
[X] Those who want to access this data can be added to the project that houses it

Have requested membership of this project to investigate.

Please confirm this YAML is suitable for the dataset:
name: cmip6_ig45
experiment_uuid: c7021d1e-7ba2-11ef-beb5-000007d3fe80
description: 20km regional projections for CORDEX-CMIP6 from the Queensland Future Climate Science Program
long_description: >-
  This dataset includes projections at 20km, formatted to meet the CORDEX-CMIP6 data standards.
  The 20km projections were derived from the 10km projections.
model:
- CMIP6
frequency:
-
variable:
-
nominal_resolution:
-
version:
contact: NCI
email<EMAIL_ADDRESS>reference:
license:
url: https://geonetwork.nci.org.au/geonetwork/srv/eng/catalog.search#/metadata/f7465_8388_5100_7022
parent_experiment:
related_experiments:
-
notes:
keywords:
- cmip

I had a look at the esm catalog... It has not been generated properly.
I'll raise an issue with NCI

Contacted NCI today 02/10/2024

The catalog has been fixed.

I've just noticed when building the metadata.yaml file that this dataset contains the 10km projections in addition to the 20km projections (see attached image).
I'm not sure if this is intentional or the 10km projections are just being brought along for the ride, so to speak? I've included reference to them in metadata.yaml but kept the focus on the 20km dataset

I guess it doesn't really hurt to have them both? Given that the 20km projections are derived from the 10km, I'm assuming there's probably someone who wants to do comparisons/sanity checks between the two.

Sounds sensible. I'm ready to drop the PR in on this one but will wait until later today - I've layered these changes on the type annotations I added in #212 - can cherry pick out the translators if it seems sensible.

@charles-turner-1 I think cherry-pick out the type annotations - that'll get them into main faster, as well as reduce #212 to being only directly relevant changes.

This will also require adding an xfails marker to the CordexTranslator test in our end to end tests until fixed - working on that now


No stacktrace on error when using the spec reporter

What is your Scenario?
When an assertion goes wrong the line number of the assertion is not always printed when using the spec reporter as shown in the README: https://github.com/DevExpress/testcafe-reporter-spec. Some examples of my outputs:
      1) AssertionError: expected false to deeply equal true
         + expected - actual
         -false
         +true

    1) Cannot obtain information about the node because the specified selector does not match any node in the DOM tree.
          > | Selector('#send-reply-component')
            |   .find('#send-reply-ack-text')

What is the Current behavior?
Stacktrace is not always printed
What is the Expected behavior?
Stacktrace should always be printed
What is your public website URL? (or attach your complete example)
N/A
What is your TestCafe test code?
import { Selector } from 'testcafe';

fixture `Fixture`
  .page('http://example.com');

test('test', async t => {
await t.expect(true).eql(false)
});

Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce

Run code snippet

TestCafe version
3.0.0
Node.js version
16.17.0
Command-line arguments
none
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

Just updated the simple example await t.expect(true).eql(false)

I ran your test with await t.expect(true).eql(false) and got the following result:

I'm not sure that I understand the issue. Do you expect that the report should have the following line?:
 > | await t.expect(true).eql(false)

Alright, let me explain more. Here is a more thorough example:
fixture("Stack trace").page("https://google.com");

test("Should show stack trace", async (t) => {
  await t.expect(true).eql(false);
});

When running this code I don't get the stack trace you do. Here is a screenshot:

I am here running testcafe v.3.3.0 and nodejs nodejs 16.17.0. Here is a screenshot when running in a docker container (however this time I am running Testcafe v.3.0.0):

I only get the indication of which tests have failed not which assertions

Hello @ChristianThingKnudsen ,
I did not manage to reproduce the issue with TestCafe v3.0.0 and the test example you shared. I'm using Ventura 13, Chrome 116, and NodeJS version 16.17.0. This is my output:

Could you please share with us the entire project? Possibly there are customizations in it that prevent the spec reporter from outputting the stack trace

That is weird. I can reproduce it just by running it without any customization however my chrome version seems slightly different than yours.
christianthingknudsen@MBPtilhhristian functional-tests % ./node_modules/.bin/testcafe chrome testcafe/fixtures/test-fixture.ts
 Running tests in:
 - Chrome <IP_ADDRESS> / Ventura 13

 Stack trace
 ✖ Should show stack trace

   1) AssertionError: expected true to deeply equal false

      + expected - actual

      -true
      +false

      Browser: Chrome <IP_ADDRESS> / Ventura 13

 1/1 failed (3s)

We checked it one more time on different machines with a different NodeJS version. It works as expected in our case. Unfortunately, we cannot do much, since the information is not sufficient to reproduce the issue.


Update index.md

The H1 for "Big Data, Big Compute" didn't register. My guess is that it's because it's after a  tag. Weird. This extra space should fix it.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guide/architecture-styles/index.md
:white_check_mark:Succeeded
View

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


ImageTexture doesn't load images anymore

Operating system or device, Godot version, GPU Model and driver (if graphics related):
macOS 10.13.1, Godot 3.0.beta.build1
Issue description:
In Godot < 3 in the ImageTexture, the load button accepted loading image files. This is not working anymore in Godot 3. Only resources are available there.
If this is the expected behaviour now: How can I create an image texture using the editor and set flags like repeat? StreamTexture doesn't have that option and I can not load an StreamTexture as a ressource in an ImageTexture. If that should work, I will create a separate bug for that.
Steps to reproduce:

Create a new Sprite
Select Texture
Select "New ImageTexture"
Select Image
Select Load

➡ Only .res and .tres-files are accepted, no image files.

The image flags are now specified in the import tab. Just select the image in the Filesystem dock, then open the Import tab.


Question: Could Nodehun performance increase if there was a Readonly Dictionary Option?

I was looking at the Nodehun binding code and noticed that in Nodehun::SpellDictionary::checkSuggestions() it sets a lock on the dictionary - before it looks up the word.
In my case, I'm only using the dictionary as read-only, it never changes. So if the dictionary never changes, technically, we don't need a lock on the dictionary and theoretically improving performance.
What I was thinking was that I could provide an option to make the dictionary read-only when you create the dictionary object and then you can just put an if-statement around the locks.
Thoughts?
Jason

If you look carefully you'll see that it's a readwrite lock, which means that if all you're doing is reads then the lock won't do anything.


MSYS2 Windows Text Looks Weird

Current behavior
As seen in the screenshot, it looks quite weird to me.
Expected behavior
It should look like the screenshots in the wiki.
Relevant Zsh configuration (.zshrc)
ZSH_THEME="spaceship"

Environment
Spaceship version: 3.11.2
Zsh version: 5.8
Zsh framework: oh-my-zsh
Terminal emulator: Tried on Hyper and Windows Terminal. Same.
Operating system: Windows
Screenshot
Provide a screenshot that shows your issue.

Windows is not officially supported.


[SPARTA-739]: Show the short description and name in Inputs/Outputs

Changes Unknown when pulling a8e0c797129b3662c3c22d23dcb5cba678541b46 on EvaMGC:SPARTA-739 into ** on Stratio:master**.

Coverage decreased (-0.02%) to 52.902% when pulling dcd02f5d5123d5d60cbd114dc893e42c7711501a on EvaMGC:SPARTA-739 into 7614d76f3e6f580f13d5f45837dbe66d2eaee39a on Stratio:master.


Improve nil pointer checks and consider VPC overlay networks for Nutanix

What this PR does / why we need it:
Our Nutanix provider implementation assumed that all networks would have a cluster reference. That does not seem to be the case, as e.g. VPC overlay networks do not have one (also see https://github.com/nutanix/terraform-provider-nutanix/pull/328).
This PR includes that as a possible scenario when checking the cluster reference on a discovered subnet.
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #1192
Special notes for your reviewer:
Optional Release Note:

Support VPC overlay network types in Nutanix

Signed-off-by: Marvin Beckers<EMAIL_ADDRESS>

/hold
I'd like to test this, but we do not have a VPC overlay network yet.

/hold cancel


Add field/message/service options support

In our proto files we make extensive use of option parameters on messages, fields and services, for example for https://github.com/grpc-ecosystem/grpc-gateway or https://github.com/mwitkow/go-proto-validators.
It would be fantastic if the custom moustache templates supported accessing options so we could, for example, list the RESTful URLs of our services.

Please see my recent addition to the README.md, copied below. My sincerest apologies for this.
To all users of `protoc-gen-doc`: This project is now unmaintained and
seeking a new maintainer. The reason for this is two-fold:

1. I'm not using Protocol Buffers myself anymore, and haven't done so
   for years.

2. I'm too busy with work and other projects to keep developing
   the tool, deal with feature requests and PRs.

Too all those who have outstanding pull requests and/or issues filed:
I'm really sorry, and thank you so much for your contributions, but I
simply don't have time for the project anymore, even if it is quite
low-maintenance.

Are you a user of `protoc-gen-doc` who feel you could take over? Great!
Please get in touch with me privately and we can discuss how to best
proceed (GitHub forking and transferring of Travis CI / AppVeyor / Open
Build Service accounts). The code is quite simple and only moderate C++
skills and some familiarity with Qt is needed.

Again, to all users: I'm sorry for this inconvenience, but it would be
dishonest of me to continue claiming maintainership of this project
when I don't have the time anymore.

I'll take this 👍 first part is in https://github.com/pseudomuto/protokit/pull/2

I've been trying to follow along in the protokit code, but just to make sure: would this also make things like [deprecated=true] available to render in protoc-gen-doc?

Hi, so Is there support for custom (user-provided) extensions/options for services and messages? I can't seem to land on the relevant doc and the templates wiki is marked "outdated".


HDDS-11200. Hsync client-side metrics

What changes were proposed in this pull request?
Add detailed client-side hsync metrics, including:

Time to compose and send writeChunk/putBlock.
Time spent in the synchronize work. This is just a wrap around 1. plus any waiting time on the monitor lock.
Time to wait for the acshyncrhous work (writeChunk/putBlock and watchForCommit).
Time to wait for watchForCommit.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11200
How was this patch tested?
Standard CI.

Thanks @jojochuang  for reviewing.


How to get the result from getAccessToken?

How to get the result from getAccessToken?
eg:
var result = OAuth.getAccessToken({username: $scope.data.email, password: $scope.data.password});

To get the return webservice messages...

Hi @fndmiranda.
getAccessToken is a promise, so you can do
OAuth.getAccessToken(data)
  .then(function(response) {
    // ...
  })
  .catch(function(response) {
    // ...
  });

The token will be stored on success and we are also emitting an event oauth:error when errors occurred - take a look at oauth-interceptor.js.
I hope this helps.

Hi @ruipenso
Thank you, it worked, taking advantage, how could I get the user information authenticated? Type the first name.
Its authenticate using only the username and password with OAuth2?

Hi @fndmiranda,
This module is only responsible for oauth. Once you get the access_token, every call send the Authorization header.
To get any private information about the user, you'll need to make the respective a call to your API.


Feature/resource admin

Adds in Resource Form that allows admin users to add, edit, and delete resources.
Still missing:
Nested display for Topic selection (Categories)
Option to add Topic to hierarchy.
Option to search for and add Organization, rather than simply choosing from existing list.
Currently one backend test is failing (category depth) because I took out the depth limit on the category list endpoint, and I'm not sure how I'm going to handle that list yet in order to address the above issues.
I would also love to refactor so that there isn't so much duplication between actions for Resource, Location, and Event.

Merging without the nested multi-select for Categories/Topics. This does include some of the refactor I mentioned in the initial comment as well as the Organization autocomplete/select and/or add. We also put in a little fix for the search paginator.


return _nvisii.mesh_create_from_data(*args, **kwargs) RuntimeError: Error: No indices provided, and length of positions (7838688) is not a multiple of 3.

I have been able to run all the examples up until 16 so I thought to report the package.
It is possible I have a different version of HW/SW causing this?
(nvisii) mona@ard-gpu-01:~/NVISII/examples$ pip freeze | grep nvisii
nvisii==1.1.72
(nvisii) mona@ard-gpu-01:~/NVISII/examples$ pip freeze | grep open3d
open3d==0.16.0
(nvisii) mona@ard-gpu-01:~/NVISII/examples$ python --version
Python 3.9.16

(nvisii) mona@ard-gpu-01:~/NVISII/examples$ python 16.create_mesh_from_data.py
Found 1 GPUs available for rendering.
Traceback (most recent call last):
  File "/home/mona/NVISII/examples/16.create_mesh_from_data.py", line 53, in <module>
    mesh = nvisii.mesh.create_from_data(
  File "/home/mona/anaconda3/envs/nvisii/lib/python3.9/site-packages/nvisii/__init__.py", line 21960, in create_from_data
    return _nvisii.mesh_create_from_data(*args, **kwargs)
RuntimeError: Error: No indices provided, and length of positions (7838688) is not a multiple of 3.
CUDA call (cudaFree((void*)d_pointer)) failed with code 4 (line 94): driver shutting down
terminate called after throwing an instance of 'std::runtime_error'
  what():  fatal cuda error
Aborted (core dumped)

$ lsb_release -a
LSB Version:	core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

$ uname -a
Linux ard-gpu-01 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I will look into the example today. Maybe o3d changed the behavior of loading a mesh. The logic is still the same though.


Add Safety comment line and Copy/Clone on Allocation

Thanks for the great Fork of vk-mem-rs !
Two small but useful changes had been made on the vk-mem-rs crate.
The Clone and Copy on Allocation would save so much time and make it more usable.
The second change was just a "# Safety" line missing in the comment, always a good thing to have.

@msuess Can you please review this PR when possible ?
I just want to know if this crate will keep being maintained.
Thanks

@msuess A release for crates.rs would be great ! Currently I use the forked git repo as the crate but if that crate can be updated it would be better.


resolving multiple tasks with type npm and same script fails

Issue Type: Bug
Create 2 tasks with "type": "npm" and same "script"
Expected both tasks to be resolved by their label

VsCode will list only one of those tasks when listing available tasks with "Tasks: Run Task".
Depending tasks will fail with "Couldn't resolve dependent task 'x' in workspace folder 'y'" in the "Tasks" output.

tasks.json:
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "start_both",
            "type": "shell",
            "dependsOn": [
                "start_nr_1",
                "start_nr_2"
            ],
            "problemMatcher": []
        },
        {
            "label": "start_nr_1",
            "type": "npm",
            "script": "start",
            "problemMatcher": []
        },
        {
            "label": "start_nr_2",
            "type": "npm",
            "script": "start",
            "options": {
                "env": {
                    "SOME": "option"
                }
            },
            "problemMatcher": []
        },
    ]
}

package.json:
{
  "scripts": {
    "start": "echo running 'start' script"
  }
}

VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:01:20.184Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 x 3592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (8.47GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Workaround would be to simply define a separate script in package.json for each task

This is by design. An extension provided task, such as a task of "type": "npm" is identified by it task-type-specific properties (for npm tasks, this is script). Tasks are not identified by label, a label is just a nice human readable string.
Since this is very easily worked around by having a separate npm script in your package.json I wouldn't make any changes in the behavior. However, it is not nice that the first time you learn that you can't have two of the same task is when you try to run a task that depends on it. I will add an error earlier, so that it's clear what's happening when the task list shows.

@alexr00 I just hit this today as well, in my situation both script calls had different working directories:
		{
			"label": "server tsc watch",
			"type": "npm",
			"script": "compile-watch",
			"options": {
				"cwd": "web/server"
			},
			"problemMatcher": [
				"$tsc-watch"
			],
			"presentation": {
				"group": "group-build"
			}
		},
		{
			"label": "client tsc watch",
			"type": "npm",
			"script": "compile-watch",
			"options": {
				"cwd": "web/client"
			},
			"problemMatcher": [
				"$tsc-watch"
			],
			"presentation": {
				"group": "group-build"
			}
		},

In my case I don't really have ownership of the web/client and web/server package.json files, so renaming or adding script sections is not an option...

Workaround: add a path property and use '.', or './.' or '././.' etc.

@alexr00 would it be possible to include the options (particularly cwd) in the unique identification of a task? I just ran into this while trying to configure build tasks in an npm workspace where the sub-workspaces had identically named scripts with different cwds. As you note, it's easy to work around this, but it was definitely surprising behavior and I wasted time trying to figure out what I'd misconfigured.

After a lot of digging, it seems npm tasks aren't considered CustomTask objects, so it uses the TaskRegistry to build the identifier. If it was a CustomTask, then it works by label.
https://github.com/microsoft/vscode/blob/4a130c40ed876644ed8af2943809d08221375408/src/vs/workbench/contrib/tasks/common/taskConfiguration.ts#L1409
Basically, it creates an identifier, and then a keyed one based on its properties:
https://github.com/microsoft/vscode/blob/fb4c12bfff2710e00eabac84d63bb304ea184574/src/vs/workbench/contrib/tasks/common/taskConfiguration.ts#L1425
Since the fields passed aren't unique enough, the key is duplicated and only the last entry will persist when it eventually moves to a Map. One solution is to move to entry tuples (eg: [key, value][]), or increase uniqueness by uses more fields in the npm identifier. I think just including options property is enough.

Workaround of using spaces no longer works as of v1.66.2 :(

I just hit this in the TS repo, where I'm changing our build but leaving some tasks behind for backwards compat. I had:
        {
            "label": "npm: build:tests",
            "type": "npm",
            "script": "build:tests",
            "group": "build",
            "problemMatcher": [
                "$tsc"
            ]
        },
        {
            "label": "gulp: tests",
            "type": "npm",
            "script": "build:tests",
            "group": "build",
            "hide": true,
            "problemMatcher": [
                "$tsc"
            ]
        },

We don't commit launch.json, but we do commit tasks.json, so I was leaving an old task behind as to not cause breakage for the people on my team with old launch configs. But, when I opened the task menu, I only saw the latter open.
The "fix" for me was to move the deprecated gulp task to the top (with a big explanatory comment), as the last use of a script is the one that appears to win. Obviously, this only works because I am content with just one of the scripts showing up, and we don't set cwd or anything.

Related on Stack Overflow: Why does only the last NPM task in VS Code of several that only vary by label and options (and not the script) get picked up?

@alexr00 @meganrogge If an external contributor wanted to try and fix this what would be the next steps?


showing haproxy logs in stdout and stderr

rancher/rancher#6504
To test,

Enable logging by adding this in custom haproxy.cfg -
defaults log <IP_ADDRESS>:8514 local0 debug
Hit load balancer. View Logs.
Observe events and traffic getting logged in Standard Out. Errors in Standard Error.

To look out for only haproxy related logs, check /var/log/haproxy/errors|events|traffic.

@cloudnautique do you see any implications that the fix can cause? The issue we are trying to solve is following:

lb-controller service logs to stdout
haproxy logs to socket. Rsyslog listens to haproxy logging events, and writes the logs to the haproxy/error, events, traffic files.

we need to redirect logs from haproxy/* to stdout so user can see it when he does docker logs

The /etc/haproxy/rsylogd.conf is also logging everything to /var/log/messages. We should change that behavior so we don't fill up the disk.
Also, it seems like we should enable this by default? If that is the case, then we should set reasonable defaults in global, default and on the backend types. It also looks like we are not configuring it to get the client IP.
If it is not the default setting, we need a detailed doc with examples on how to configure it for primary use cases. Otherwise, we need to document our syslog server address since it appears to be a non-standard port.
We should also consider launching our LB with log driver opts so that it auto rotates the docker json logs now that we are going to stderr/stdout. Unless daemon logs exist... a busy site could create a lot of logs pretty quick.

@cloudnautique for the first run, do you think it's ok if we:

Disable logging to /var/log/messages
Keep logging disabled by default and document the log on how to enable it + syslog server address/port.
Enable log rotation by adding log driver to lb container start (that change will most likely require cattle changes)

In the future:

Enable logging by default and revise the defaults in global/default/backend types.

@alena1108 sounds like a good path forward.
On number 3, if we needed to hold off we could note in the docs that turning on logging would also require setting up driver opts at the daemon level. You might need agent changes as well to detect if the daemon has default drivers going to syslog or elasticsearch or something. At that point we wouldn't want to launch with json drivers we would want the users default.

@cloudnautique sounds good, thank you! @kinarashah so we just have to do 1) and document 2) and 3)


Update travis configuration

Previously travis build was broken
no refs

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f99e143). Click here to learn what that means.
The diff coverage is 80%.

@@          Coverage Diff           @@
##             master    #2   +/-   ##
======================================
  Coverage          ?   65%
======================================
  Files             ?     7
  Lines             ?    80
  Branches          ?     7
======================================
  Hits              ?    52
  Misses            ?    24
  Partials          ?     4

Impacted Files
Coverage Δ

city-infrastructure-platform/settings.py
83.92% <ø> (ø)

city-infrastructure-platform/urls.py
0% <0%> (ø)

tests/test_dummy.py
100% <100%> (ø)

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 f99e143...fee3c3b. Read the comment docs.


Hide entities in er-diagram

It would be nice to have the possibility to hide entities in the er-diagram.
I use hibernate-envers to create audit-tabes in my system but I don't want to see this in the diagram ;-)

You can just use custom ER diagrams (from context menu on Diagrams folder or thru Ctrl+N).
Then you can drag-n-drop any number of tables you need. And even make your custom connections.

:+1:
works for me, thanks


[security] adding checked arithmetic to the coding guidelines

rationale: it is undeniable that every time we perform an integer operation, there are implied edge-cases that we MUST think about, and I think we can also agree that not everybody thinks about integer overflows when they write code. Rust gives us a great tool, checked operations, which forces us to explicitly document how we want to handle these edge cases.

Adding more people to give their opinions.

we want to enforce the lint!

Ok, I didn't have the context of the other PR. Sorry.

do we consider the perspective of developer experience/velocity? the syntax is much less friendly than +, -
is there any other open source projects adopt such a lint rule?

do we consider the perspective of developer experience/velocity? the syntax is much less friendly than +, -

I had a private convo on this subject, my point of view is the same as the reason we adopted rust over go or python. Even though there is a learning curve, we're writing high-assurance software and we need to accept this friction if we want to write secure code. (Maybe it looks a bit uglier, but if it's worth it in terms of security then it's a no-brainer.)

generally acceptable approach

You're looking for something that doesn't exist unfortunately : o
I understand that it's not great to have to think about how you want to handle edge cases EVERY TIME you use integer arithmetic, but again this is not new and this is already something you had to do before.

also wrapping is what happens by default without any of this magic

this might be surprising as I think rust is the only language that actually specifies the behavior. I think the idea is still that a wrapping around is a programmer error, unless it was explicitly defined to do so (in other words, if you didn't use the wrapping_add function then it means you did not think of edge-cases)

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - Build images and run cluster test

/land
We need a way to skip cluster test for doc only changes :/

We need a way to skip cluster test for doc only changes :/

Can we do this with target determinator?

Yeah should be possible. (also e2e test). Will work on this today.

:broken_heart: Test Failed - Build images and run cluster test

/land


obs-studio: include plugins in wrapper again

If the user asks for a plugin that does come with their own binaries or other
files to be included in their OBS installation, it should include those files. A
good example is obs-vkcapture which /requires/ system-wide files to have any use
whatsoever.
Plugins' paths were removed from the wrapper in step with preventing OBS from
loading plugins twice but wasn't actually required because the env variables
already point at the one and only location for plugins. The plugins' share dirs
don't get put in the system-wide share by default on NixOS but I decided to
remove the directory anyways for clarity.
Partially reverts 593d64f975e4e7d9439562d3f857d85e8be66012
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Thanks!


Added Space website

Description
Added Space tourism Website
Fixes #678
Type of change
Please delete options that are not relevant.

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

Checklist:

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

Please Review my PR @Ayush7614


Build errors when using dependencies from git paths.

Current Behavior
nx run test-package-django:build
  Building project  test-package-django ...

  Copying project files to a temporary folder
  Resolving dependencies...
    • Adding asgiref==3.6.0  dependency
    • Adding boto3==1.26.51  dependency
    • Adding botocore==1.29.51  dependency
    • Adding certifi==2022.12.7  dependency
    • Adding charset-normalizer==3.0.1  dependency
    • Adding django-storages==1.13.2  dependency
    • Adding django==3.2.16  dependency

  ERROR  must pass in a file:// URI to convert to a file path

Expected Behavior
I expect the build to succeed.
Steps to Reproduce
Add a dependency with a git url in the pyproject.toml e.g.
[tool.poetry.dependencies.django]
git = "https://github.com/django/django.git"
rev = "d54717118360e8679aa2bd0c5a1625f3e84712ba"

Nx Report
yarn nx report
yarn run v1.22.19
$ node_modules/.bin/nx report

 >  NX   Report complete - copy this into the issue template

   Node : 19.4.0
   OS   : darwin arm64
   yarn : 1.22.19

   nx : 15.4.5
   @nrwl/angular : Not Found
   @nrwl/cypress : Not Found
   @nrwl/detox : Not Found
   @nrwl/devkit : 15.4.5
   @nrwl/esbuild : Not Found
   @nrwl/eslint-plugin-nx : 15.4.5
   @nrwl/expo : Not Found
   @nrwl/express : Not Found
   @nrwl/jest : 15.4.5
   @nrwl/js : 15.4.5
   @nrwl/linter : 15.4.5
   @nrwl/nest : Not Found
   @nrwl/next : Not Found
   @nrwl/node : Not Found
   @nrwl/nx-cloud : Not Found
   @nrwl/nx-plugin : 15.4.5
   @nrwl/react : Not Found
   @nrwl/react-native : Not Found
   @nrwl/rollup : Not Found
   @nrwl/schematics : Not Found
   @nrwl/storybook : Not Found
   @nrwl/web : Not Found
   @nrwl/webpack : Not Found
   @nrwl/workspace : 15.4.5
   @nrwl/vite : Not Found
   typescript : 4.8.4
   ---------------------------------------
   Local workspace plugins:
         @mediasuitenz/poetry-version
   ---------------------------------------
   Community plugins:
         @nxlv/python: 15.1.0

✨  Done in 4.07s.

Failure Logs
No response
Additional Information
As far as I can tell its the check that resolves local dependencies is failing using uri2path. The solution would be to only perform this resolution if the line starts with file://. This would filter out any that start with git+http:// as git repositories do.

@niall-mediasuite thanks for the report, I'm going to have a look at this as soon as possible


Add on_table_exists 'replace' option to Starburst/Trino

Added on_table_exists 'replace' option to Starburst/Trino
Added new author of Starburst/Trino

CC: @hovaesco @findinpath


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106458

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106822

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106831

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107971

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108418

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111846


add coverage

[ ] docstrings
[ ] Jest tests
[x] linting

Simplest way to go about increasing coverage with jest is making snapshots of your components
I'm used to writing jest tests with Enzyme, quite simple to use:

For unit tests, use shallow. It will only create a snapshot of the top component, hence you can test your top components attributes for example. Note that in addition, you can use .find() and other properties to search for children.
For slower tests, use mount. This will save the full rendered version of all components including the top component. I usually try to avoid mounting, but for this plugin, this sounds like a good idea.

@Fandekasp so as i understand it the __tests__ folder should go in the examples folder ya?

It should go in src/components/. You can create fake components in your tests if your components cannot be tested by themselves.
If you want to test your examples, you can also add examples/__tests__, but I wouldn't spend time on this.

also, how to you get enzyme to generate snapshots?

alright i think i got it, the toMatchSnapshot creates the snapshots


Forward onclick event for HeaderActionLink

All of the UIShell components that wrap the anchor element forward the anchor element's on:click event (SideNavMenuItem, HeaderNavItem, SideNavLink, etc.). However, the HeaderActionLink component does not forward the on:click event for the anchor element that it wraps. Is it possible to update the library so that the HeaderActionLink forwards the on:click event? If desired, I'm happy to attempt a pull request for this feature.

That makes sense – a Pull Request would be appreciated.

Released in v0.80.0

Thanks for the release, much appreciated!


html and message formatters are not compatible with AfterStep hooks

Describe the bug
The html and message formatters cause Cucumber to crash when an AfterStep hook is defined.
To Reproduce
Steps to reproduce the behavior:

In a Cucumber 4 project

Define an AfterStep hook
AfterStep do
  # noop
end

Run cucumber --format html --out index.html

See error
No hook found for 6c61579a-e729-4d9a-988c-fa8bc282a9a4 }. Known: ["e2c27447-c655-4aae-a248-c4bb90bc7e84"] (Cucumber::Formatter::TestStepUnknownError)
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/query/hook_by_test_step.rb:16:in `hook_id'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:115:in `hook_step_to_message'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:102:in `test_step_to_message'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `block in on_test_case_ready'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `map'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `on_test_case_ready'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `block in broadcast'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `each'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `broadcast'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:40:in `method_missing'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/configuration.rb:34:in `notify'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/broadcast_test_case_ready_event.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_around_hooks.rb:10:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_after_hooks.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_before_hooks.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_after_step_hooks.rb:10:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/activate_steps.rb:12:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:18:in `block in done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:17:in `each'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:17:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/tag_filter.rb:18:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/compiler.rb:31:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/gherkin/parser.rb:46:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core.rb:35:in `parse'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core.rb:24:in `compile'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/runtime.rb:78:in `run!'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/cli/main.rb:29:in `execute!'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/bin/cucumber:9:in `<top (required)>'

Run cucumber --format message

See error
No hook found for 5c4f5cbb-3ebd-408f-92c8-6298854ebdf0 }. Known: ["685158b4-219c-4a64-9b8b-e9c09d769145"] (Cucumber::Formatter::TestStepUnknownError)
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/query/hook_by_test_step.rb:16:in `hook_id'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:115:in `hook_step_to_message'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:102:in `test_step_to_message'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `block in on_test_case_ready'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `map'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/formatter/message_builder.rb:94:in `on_test_case_ready'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `block in broadcast'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `each'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:34:in `broadcast'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/event_bus.rb:40:in `method_missing'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/configuration.rb:34:in `notify'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/broadcast_test_case_ready_event.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_around_hooks.rb:10:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_after_hooks.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_before_hooks.rb:7:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/apply_after_step_hooks.rb:10:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/filters/activate_steps.rb:12:in `test_case'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/case.rb:28:in `describe_to'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:18:in `block in done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:17:in `each'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/locations_filter.rb:17:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/test/filters/tag_filter.rb:18:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/compiler.rb:31:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core/gherkin/parser.rb:46:in `done'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core.rb:35:in `parse'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-core-7.0.0/lib/cucumber/core.rb:24:in `compile'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/runtime.rb:78:in `run!'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/lib/cucumber/cli/main.rb:29:in `execute!'
/usr/local/bundle/ruby/gems/2.6.0/gems/cucumber-4.0.1/bin/cucumber:9:in `<top (required)>'

Expected behavior
Cucumber should run successfully and format output in HTML and JSON respectively.

This should be fixed with the 4.1.0 release of cucumber-ruby

Thanks @vincent-psarga. It sure is 🎉


Is this repo dead?

Sorry, just checking in 2 years after the last commit and seeing the great works of @ravinkohli
Will this repo get a revamp and a library version update to continue?
Side note: AutoKeras seems to be having install issues for Windows, so if there are other deep learning options it would be great.

A breakdown on forks:
Those that just update scikit-learn

https://github.com/automl/Auto-PyTorch/compare/master...8W9aG:Auto-PyTorch:master
https://github.com/automl/Auto-PyTorch/compare/master...dustinblackman:Auto-PyTorch:master

This guy is adding time series to AutoPyTorch https://github.com/automl/Auto-PyTorch/compare/master...LuciusMos:Auto-PyTorch:master
This guy adds NLP into the equation https://github.com/automl/Auto-PyTorch/compare/master...ParisaSafikhani:Auto-PyTorch_autoNLP:master
IDK what this is doing https://github.com/automl/Auto-PyTorch/compare/master...harel-coffee:Auto-PyTorch-auto:master

Same question.  Is this repo dead?


Recommended way to install tool for all users on system

I have CLI package foo that is published to PyPi. At work, we have a few servers that many users use for one off tasks. I want to distribute foo on these servers.
The tools section of the docs seems to be uv's answer for this, but I'm not sure how to install a tool system wide. For my use case, all it would take is allowing uv tool install to install to /usr/local/bin.
A workaround for now is to manually manage a script in /usr/local/bin called foo:
#!/usr/bin/env bash

uv pipx foo "$@"

However, the CLI will be run many times and upgraded only once a day. The docs indicate that uv pipx isn't good for a tool run many times.
Any suggestions?

So you can do this with
UV_TOOL_BIN_DIR=/usr/local/bin uv tool install foo

For most purposes uvx foo is probably fine too.  I was able to test this in a python container.


Update htsjdk dependency version to 2.24.0

@lbergelson Would it be ok to cut a 0.3.8 release with this and #151 (Spark to 3.0.2)?  We just cut ADAM and related releases at these versions and will be bumping Spark to 3.1.1 soon

@heuermh I'm actually doing a point release of htsjdk to 2.24.1 today to fix a bug.  We should wait and update to that instead.  Then I think a release would be a great idea.

Sorry I've been extremely slow lately.  The pandemic has not been good for my productivity.

Sorry I've been extremely slow lately. The pandemic has not been good for my productivity.

No problem at all!  Same goes for most of us 😉

@heuermh 2.24.1 is available now.


Is there a way to block apparatus value override?

At current, with mods like 'Balanced_Items' alongside this one, very unpredictable results have been happening because this one forces an apparatus value on sell, is there a way to not have it patch a value in, so other mods don't have issues? I actually want this to run alongside LethalMeltdown, the blur and slight damage are a great touch, but the apparatus patching is fighting other things, Meltdown has an option to set a 'False' flag for 'OverrideApparatusValue'
Do you support anything like a '-1' value to bypass your forced price assignment? It's causing things like apparatus showing a generated value of 88, 102, 116, but then once on the company desk, sells for your priced over-ride instead, which is always a static amount unfortunately.
Just curious, I understand this mod hasn't been touched in 2 months, still think it's visually great otherwise!

Hi Roobotics. Since that is a fairly simple fix, I might be able to quickly create an update for that feature.

Added in commit 4aa05ed4f8865859b190b5aed15232c73cc58468.

Added in commit 4aa05ed4f8865859b190b5aed15232c73cc58468.

Awesome! Thanks for adding this intercompatible feature in so quickly.
I've tested that selling at the company, functions as desired now as well.

No a problem. Thanks for using the mod!


x/tools/refactor/rename: TestMoves is failing on Windows

--- FAIL: TestMoves (0.01s)
	mvpkg_test.go:403: -from "b" -to "x/a": unexpected warnings:
		\go\src\conflict\0.go:4:8: renaming this imported package name "b" to "a"
		\go\src\conflict\0.go:3:8: 	conflicts with imported package name in same block
		\go\src\conflict\0.go:3:8: skipping update of this file
		want:
		/go/src/conflict/0.go:4:8: renaming this imported package name "b" to "a"
		/go/src/conflict/0.go:3:8: 	conflicts with imported package name in same block
		/go/src/conflict/0.go:3:8: skipping update of this file
	mvpkg_test.go:418: -from "b" -to "x/a": rewritten file /go/src/ok/0.go does not match expectation; got <<<package ok

		import a "x\\a"

		var _ a.B
		>>>
		want <<<package ok

		import "x/a"

		var _ a.B
		>>>
	mvpkg_test.go:418: -from "b" -to "x/a": rewritten file /go/src/conflict/0.go does not match expectation; got <<<package conflict

		import "a"
		import a "x\\a"

		var _ a.A
		var _ b.B
		>>>
		want <<<package conflict

		import "a"
		import "x/a"

		var _ a.A
		var _ b.B
		>>>
	mvpkg_test.go:395: -from "x/foo" -to "y/foo": unexpected error: invalid move destination: y/foo; package or subpackage x/foo already exists
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 3 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 2 files in 2 packages.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 4 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 3 occurrences in 2 files in 2 packages.
Renamed 5 occurrences in 1 file in 1 package.
Renamed 5 occurrences in 1 file in 1 package.
Renamed 3 occurrences in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
Renamed 1 occurrence in 1 file in 1 package.
Renamed 2 occurrences in 1 file in 1 package.
FAIL
FAIL	golang.org/x/tools/refactor/rename	0.213s

/cc @quentinmit (feel free to file bugs like this for all subrepo failures if none exist)

I'm interested in doing this. It could be useful for a project I'm working on. Before I get started, I'd like to work out API details. I'm currently thinking of just adding a single, top-level function that returns both a Listener, for use in an httptest.Server, and an http.Transport.Dial implementation. From my understanding of the code, that should be feasible. Does that sound like a good way of doing it?

@DeedleFake wrong issue?

Yep. Woops. Sorry.

Looks like two separate issues, both related to forward vs. backslashes as directory separators:

the import declaration uses backslashes (a bug in the package)
the actual warnings in the test use backslashes (a bug in the test)


fix(deps): update all non-major

This PR contains the following updates:

Package
Type
Update
Change

actix-web (source)
dependencies
minor
4.4.1 -> 4.5.1

tokio (source)
dev-dependencies
minor
1.35.1 -> 1.36.0

tokio (source)
dependencies
minor
1.35.1 -> 1.36.0

ureq
dependencies
patch
2.9.1 -> 2.9.4

Release Notes

tokio-rs/tokio (tokio)
v1.36.0: Tokio v1.36.0
Compare Source
1.36.0 (February 2nd, 2024)
Added

io: add tokio::io::Join (#6220)
io: implement AsyncWrite for Empty (#6235)
net: add support for anonymous unix pipes (#6127)
net: add UnixSocket (#6290)
net: expose keepalive option on TcpSocket (#6311)
sync: add {Receiver,UnboundedReceiver}::poll_recv_many (#6236)
sync: add Sender::{try_,}reserve_many (#6205)
sync: add watch::Receiver::mark_unchanged (#6252)
task: add JoinSet::try_join_next (#6280)

Changed

io: make copy cooperative (#6265)
io: make repeat and sink cooperative (#6254)
io: simplify check for empty slice (#6293)
process: use pidfd on Linux when available (#6152)
sync: use AtomicBool in broadcast channel future (#6298)

Documented

io: clarify clear_ready docs (#6304)
net: document that *Fd traits on TcpSocket are unix-only (#6294)
sync: document FIFO behavior of tokio::sync::Mutex (#6279)
chore: typographic improvements (#6262)
runtime: remove obsolete comment (#6303)
task: fix typo (#6261)

algesten/ureq (ureq)
v2.9.4
Compare Source
Fixed

MSRV 1.61 with CI tests

v2.9.3
Compare Source
Fixed

docs.rs docs

v2.9.2
Compare Source
Added

Replace dependency on httpbin.org for tests/doc-tests. (#703)

Fixed

Remove Header struct that never should have been exported. (#696)
Update deps (rustls 0.22) (#690)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.2.13 :tada:
The release is available on:

GitHub release
v1.2.13

Your semantic-release bot :package::rocket:


Wiremock extensions plugin parameter/extensions from Maven classpath

Would you consider merging this? I use the extensions in Wiremock quite a lot, and I think it's a nice addition to your plugin. The addition of a new plugin parameter isn't strictly necessary, but I feel it makes for a cleaner POM.

Unless I missed something, extensions can be configured in as-is version the plugin, using .... Your pull request extracts this to a separate cfg parameter stored within pom.xml.
The reason why I decied to keep nearly all config within ... is simplicity and flexibility. If new version of WireMock gets released with some now config params, nothing needs to be updated in the plugin. Except the dependency version of course.
Unless there is a good reason to merge it, i.e. currently plugin doesn't offer you what you need, I'd prefer not to merge it in.

You're right in that extensions can be configured perfectly well with the current version of the plugin. I just thought the syntax would be cleaner with the addition of a new param.
What however doesn't work with the current version of the plugin is loading extension classes from the Maven project classpath. Because every plugin gets its own classloader, Wiremock execution will fail with a ClassNotFoundException if you provide any classes from your project with --extension.
If you want I can make a separate PR with just the classpath changes.

To be honest I didn't play with extensions a lot, therefore I didn't come across this problem. Please feel free to submit a pull request for what cannot be achieved with the current version of the plugin. I'll look into this and release it if it will all make sense. I'll most likely sync plugin with the most recent version of WireMock in the same release.