DRILL-8188: Convert HDF5 format to EVF2

DRILL-8188: Convert HDF5 format to EVF2
Description
Use EVF V2 instead of old V1.
Included two bug fixes with the V2 framework :
1. Projected an unprojected column error in array object
2. IndexOutOfBoundsException at add column
Note, these items were fixed in the context of DRILL-8375
Documentation
N/A
Testing

Use the CI.
Add the tests for the bugfix.

This PR is getting a bit complex with the bug or two that this PR uncovered. Iexplain a bit about how EVF2 works. There are two case: wildcard projection (SELECT *) and explicit projection (SELECT a, b, c). The way EVF2 works is different in these two cases.
Then, for each reader, there are three other cases. The reader might know all its columns before the file is even opened. The PCAP reader is an example: all PCAP files have the same schema, so we don't need to look at the file to know the schema. The second case are files were we can learn the schema when opening the file. Parquet and CSV are examples: we can learn the Parquet schema from the file metadata, and CSV schema from the headers. The last case is where we don't know the schema until we read each row. JSON is the best example.
So, now we have six cases to consider. This is why EVF2 is so complex!
For the wildcard, EVF2 "discovers" columns as the reader creates them: either via the up-front schema, or as the reader reads data. In JSON, for example, we can discover a new column at any time. Once a column is added, EVF2 will automatically fill in null values if values are missing. In the extreme case, it can fill in nulls for an entire batch. Because of the wildcard, all discovered columns are materialized and added to the result set. If reading JSON, and a column does not appear until the third batch, then the first two won't contain that column, but the third batch will have a schema change and will include the column. This can cause a problem for operators such as joins, sort or aggregation that have to store a collection of rows, not all can handle a schema change.
Now, for the explicit schema case, EVF2 knows what columns the user wants: those in the list. EVF2 waits as long as it can, hoping the reader will provide the columns. Again, the reader can provide them up front, before the first record, or as the read proceeds (as in JSON.) As the reader provides each column, EVF2 has to decide: do we need that column? If so, we create a vector and a column writer: we materialize the column. If the column is not needed, EVF2 creates a dummy column writer.
Now the interesting part. Suppose we get to the end of the first batch, the query wants column c, and the reader has never defined column c? What do we do? In this case, we have to make something up. Historically, Drill would make up a Nullable Int, with all-null values. EVF added the ability to specify the type for such columns, and we use that. If a provided schema is available, then the user tells us the type.
Now we get to another interesting part. What if we guessed, say, Varchar, but the column later shows up as a JSON array? We're stuck: we can't go back and redo the old batches. We end up with a "hard" schema change. Bad things happen unless the query is really simple. This is the fun of Drill's schemaless system.
With that background, we can try to answer your question. The answer is: it depends. If the reader says, "hey Mr. EVF2, here is the full schema I will read, I promise not to discover more columns", then EVF2 will throw an exception if later you say, "ha! just kidding. Actually, I discovered another one." I wonder if that's what is happening here.
If, however, the reader left the schema open, and said, "here are the columns I know about now, but I might find more later", then EVF2 will expect more columns, and will handle them as above: materialize them if they are projected or if we have a wildcard, provide a dummy writer if we have explicit projection and the column is not projected.
In this PR, we have two separate cases in the reader constructor.

In the if path, we define a "reader schema", and reserve the right to add more columns later. "That's what the false argument means to tableSchema().
In the else path, we define no schema at all: we don't all tableSchema().

This means the reader is doing two entirely different things. In the if case, we define the schema and we just ask for column writers by name. In the else case, we don't define a schema, and we have to define the column when we ask for the column writers.
This seems horribly complicated! I wonder, are we missing logic in the then case? Or, should there be two distinct readers, each of which implements one of the above cases?

Found the bug. It is in ColumnBuilder which seems to be missing code to handle an unprojected repeated list. This bug then caused the other "bugs" that we discussed in the review: those bits of code are working as they should. The problem is that the result set loader is materializing a vector when it should not. It will take some time to remember how all this stuff works. Stay tuned.

Found the bug. It is in ColumnBuilder which seems to be missing code to handle an unprojected repeated list. This bug then caused the other "bugs" that we discussed in the review: those bits of code are working as they should. The problem is that the result set loader is materializing a vector when it should not. It will take some time to remember how all this stuff works. Stay tuned.

@paul-rogers Great! Thank you for the quick work.
From the end of the most recent discussion, I completely rejected my previous code revision, guess that the unprojected handle might have been lost. Actually, I've added this function locally, but I'm not sure it's correct. Would you mind checking mine before you submit the new revision?

Hi @luocooong Thank you for this PR.  Where are we in terms of getting it merged?

Hi @cgivre Thank you for paying attention to this PR.
The pull request cannot be merged now, and Paul is going to re-review the V2 section code. and we're going to fix the bugs above from the framework.

Converted to draft to prevent merging.

Hey @luocooong @paul-rogers I hope all is well.  I wanted to check in on this PR to see where we are.  At this point, nearly all the other format plugins have been converted to EVF V2.
The other outstanding ones are the image format and LTSV.  I'd really like to see this merged so that we can remove the EVF V1 code.
Do you think we could get this ready to go soon?

I think I hosed the version control somehow.... This PR should only modify a few files in the HDF5 reader.

It seems you did this work on top of the master with my unsquashed commits. When you try to push, those commits come along for the ride. I think you should grab the latest master, then rebase your branch on it.
Plan B is to a) grab the latest master, and b) create a new branch that cherry-picks the  commit(s) you meant to add.
If even this doesn't work, then I'll clean up this branch for you since I created the mess in the first place...

@paul-rogers I attempted to fix.  I kind of suck at git, so I think it's more or less correct now, but there was probably a better way to do this.

@paul-rogers I attempted to fix. I kind of suck at git, so I think it's more or less correct now, but there was probably a better way to do this.

I think you still want something like
git pull --rebase upstream master
git push --force-with-lease

I see Git's "patch contents already upstream" feature doesn't automatically clean up the unwanted commits. I've dropped them manually in a new branch in my fork and now suggest
git reset --hard origin/master
git pull --rebase https://github.com/jnturton/drill.git 8188-hdf5-evf2
git push --force # to luocooong's fork

@jnturton I did as you suggested.  Would you mind please taking a look?

@paul-rogers I attempted to fix. I kind of suck at git, so I think it's more or less correct now, but there was probably a better way to do this.

Just workng through the review comments that @paul-rogers left (the ones unrelated to the needed functionality that was missing from EVF2).

Did the recent EVF revisions allow the tests for this PR to pass? Is there anything that is still missing? Also, did the excitement over my botched merge settle down and are we good now?

Did the recent EVF revisions allow the tests for this PR to pass? Is there anything that is still missing? Also, did the excitement over my botched merge settle down and are we good now?

All the unit tests pass.... whether that means that everything is working.... this plugin has a decent amount of tests, so I'd feel pretty good.


Bundle size after installing the plugin

Hi folks!
I want it to know if someone has this unexpected increase of the bundle size,
My app size was ~18Mb and after adding this plugin went to ~30Mb. (apk)
Is that normal?

please provide reproduction examples


add support for SHOW BUILTINS syntax.

What problem does this PR solve?
add support for SHOW BUILTINS syntax.
Issue: https://github.com/pingcap/tidb/issues/12372
What is changed and how it works?
add a new syntax and display all supported builtin functions.
Check List
Tests

Unit test

Related changes

Need to update the documentation
Need to be included in the release note

Thank you!


Restructure benchmark YAML

Fixes #54
Done Will also push the new benchmarks in this PR when they are ready.

CC @trashvisor @cjx10 We now have more structured benchmarks as discussed.
Please adapt the code generation / fixing infrastructure to this.
You can base your PR on this and merge your PR to here once finished.
We will test our code together before merging into main.

Close and reopen to enable building image for this PR.

@oliverchang  This PR is ready to merge.
If you are happy with this report, could you please approve this PR? I need at least one approve to merge it : )
Follow-up work are:

Reduce the size of the comparison benchmark set to make the experiment quicker (#90).
Capture more corner cases in function name parsing and fix them (#89).

They are lower priorities for now and can be done later.


Does this project support compiling on the windows platform? Or whether to support msvc compiler？

Yes. You can use both Bazel and CMake.


Confusion about whether 2.2 behaviour produces ProblemDetails or ValidationProblemDetails

In the section headed "Default BadRequest response", it says:
"With a compatibility version of 2.2 or later, the default response type for an HTTP 400 response is ValidationProblemDetails."
However, under the heading "Problem details for error status codes", it says:
"When the compatibility version is 2.2 or later, MVC transforms an error result (a result with status code 400 or higher) to a result with ProblemDetails."
Is there some subtle difference in circumstance here that I'm not seeing, or is one of those statements wrong?

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

ID: b391017f-25e1-d5e1-c4f7-020408ade7b5
Version Independent ID: 263a7b64-2e42-bbfc-c1d3-61680438e1e4
Content: Create web APIs with ASP.NET Core
Content Source: aspnetcore/web-api/index.md
Product: aspnet-core
Technology: aspnetcore-webapi
GitHub Login: @scottaddie
Microsoft Alias: scaddie

Consider:
public IActionResult Post(MyModel model)
{
   var storedModel = store.Find(model.Id);
   if (storedModel == null) return NotFound();
   ....
}

When model validation fails when deserializing the model instance, MVC returns a 400 response with ValidationProblemDetails.

"With a compatibility version of 2.2 or later, the default response type for an HTTP 400 response is ValidationProblemDetails."

^ This statement clarifies this behavior and is part of this section https://docs.microsoft.com/en-us/aspnet/core/web-api/?view=aspnetcore-2.2#automatic-http-400-responses.
For the return NotFound() in the action, MVC will transform it to a ProblemDetails response. The latter statement is talking about this.
Does this help?

Does this help?

I'm afraid not.
My situation...
We've a REST API that's annotated:
        [ProducesResponseType(StatusCodes.Status400BadRequest)]
with a parameter (that's a member of a class that's passed to the API) that has a StringLength annotation.
If our client (a PowerShell cmdlet) passes too long a string then it rightly fails the validation.
However the nswag generated code produces an ApiException.
If I change our annotation to specify the type:
        [ProducesResponseType(typeof(ValidationProblemDetails), StatusCodes.Status400BadRequest)]
the nswag generated code produces an ApiException - which is what I'd expected by default from the initial documentation reference - until I encountered the second reference and got totally confused!

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.

@Rick-Anderson I'd already replied that the reply from @pranavkm didn't help, so I fail to see why you've closed this as answered. The answer may make sense to you from the inside, but it's still inconsistent from my perspective.


Unable to prepare setup for platform iotawatt.sensor: Platform not found (cannot import name 'VOLT' from 'homeassistant.const'

Logger: homeassistant.setup
Source: setup.py:311
First occurred: August 3, 2021, 10:43:34 AM (2 occurrences)
Last logged: 12:19:05 PM

Unable to prepare setup for platform iotawatt.sensor: Platform not found (cannot import name 'VOLT' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

I'm getting the following error when loading the iotawatt integration. This has started occurring since the core-2021.8 update.

Yeah it appears HA 2021.8 renamed the VOLT constant to ELECTRIC_POTENTIAL_VOLT
The issue is how to make the IoTaWatt integration work with <2021.8 and >=2021.8 versions?
Maybe use my own constants?

@djhampson Can you update the Integration through HACS? Two changes have been made, so it should work with HA 2021.8
and previous HA versions now.

Thanks you @gtdiehl - working again. appreciate it!


No prices for currencies change since 29/11/22

Hello,
Since the 29 November we don't have any values from your api for everything related to the currencies change.
For example nasdaqdatalink.get("ECB/EURGBP", start_date="2022-12-05", api_key=...)
does not return anything.
Can you enlighten me on the subject ?
Regards,

-- Please reply above this line --
Thank you for contacting the Client Success Team at Nasdaq Data Link.
Your email is very important to us and we will respond to you within 1
to 2 business days.

-- Please reply above this line --
        Hi there,

Thank you for reaching out.
Kindly be advised that the free ECB database has been deprecated.
Moving forward, the data will no longer be updated and may no longer
be accessed. We're very sorry for any inconvenience caused by the
deprecation this database and we don't have an equivalent database
available on Nasdaq Data Link at the moment.
Please note that free data feeds may get deprecated at any time for
various reasons eg. they may no longer meet our quality standards,
they get copyrighted, technical issues prevent us from obtaining the
data, etc.
Unfortunately, we do not have a similar database on Nasdaq Data Link
that may serve as an alternative.
We hope this information helps. Please let us know should you have any
questions.
Thank you and kind regards,
Kim
KIM LIRA
Client Success
Nasdaq Data Link
How would you rate my reply?
Great [1]    Okay [2]    Not Good [3]
Links:
[1]
https://secure.helpscout.net/satisfaction/584492073/record/6213437555/1/
[2]
https://secure.helpscout.net/satisfaction/584492073/record/6213437555/2/
[3]
https://secure.helpscout.net/satisfaction/584492073/record/6213437555/3/
    > On Tue, Dec 6, 2022 at 11:16 AM EST, Nasdaq/data-Link-Python<EMAIL_ADDRESS>wrote:

WARNING - EXTERNAL EMAIL; EXERCISE CAUTION.
Hello,
Since the 29 November we don't have any values from your api for
everything related to the currencies change.
For example nasdaqdatalink.get("ECB/EURGBP", start_date="2022-12-05",
api_key=...)
does not return anything.
Can you enlighten me on the subject ?
Regards,

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

CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments
are for the exclusive and confidential use of the intended recipient
and may constitute non-public information. Personal data in this email
is governed by our Privacy Policy at
https://www.nasdaq.com/privacy-statement [3] unless explicitly
excluded from it; please see the section in the policy entitled
"Situations Where This Privacy Policy Does Not Apply" for
circumstances where different privacy terms govern emailed personal
data. If you received this e-mail in error, disclosing, copying,
distributing or taking any action in reliance of this e-mail is
strictly prohibited and may be unlawful. Instead, please notify us
immediately by return e-mail and promptly delete this message and its
attachments from your computer system. We do not waive any work
product or other applicable legal privilege(s) by the transmission of
this message.

Links:
[1] https://github.com/Nasdaq/data-link-python/issues/32
[2]
https://github.com/notifications/unsubscribe-auth/AWYQ645CSJZWIZZ2XD6PXUTWL5RETANCNFSM6AAAAAASVWLDE4
[3] https://www.nasdaq.com/privacy-statement


Fix/hdfs and s3

Description and related tickets, documents
This PR fixes the some bugs related to s3/hdfs.
It:
(1) Add credential validation step in the initialization step
(2) polish up the list_files behavior of s3
(3) fix some bugs and error message related to uploading
Reviewers: @lebinh @hai-adatao @Huandao0812 @nhanitvn
How to test
UT is added. Client Test.
PR Progress
Make sure all checkboxes below are checked before merged

[x] Branch is in format prefix/description (see this)
[ ] Merge check has no conflicts. PR checks passed.
[ ] Code review is done.

@hai-adatao


Add LDAP users button disabled

Describe the bug
After upgrading to 8.1.2, existing users are able to log in using ldap credentials, but the button to add new LDAP users under Administration -> Users is disabled.
To Reproduce
Steps to reproduce the behavior:

Set up an 8.1.2 instance
Configure LDAP in the config.xml
Try to add a new LDAP user from your chosen directory

Expected behavior
The Add LDAP users button should be enabled when LDAP is configured

@matomario8 Was able to reproduce this on 8.1.3 dev branch, Server Admin is unaffected but the CMS UI user import feature is not enabling like it should.


DCOS-10991 [4 of 4]: Volumes form section

This adds the form component to add volumes.

Ok, going to merge this in. I added a parser to make sure we are parsing integers for sizes.
A few follow-ups:

We are missing the option to add a "Host" container, which in the old create form was referred to as "Docker Container Volumes". See image:

External volumes can take size, but let's handle that in a separate issue (created a JIRA), which we can prioritise and add after the release.
Since there is only one selection for external volumes, let's remove the select box, with only one option


Refresh project.

Refreshing project on top of commits at PR from https://github.com/dashed/shallowequal/pull/6

Revert the 'meat' of shallowequal. I'd like to avoid old-style JS. The 'meat' largely mirrors: https://github.com/facebook/fbjs/blob/b00c419adcf89950a76d5fc119fa152e6902dbab/packages/fbjs/src/core/shallowEqual.js

Drop lodash dep. Already done at https://github.com/dashed/shallowequal/pull/6

Object.keys will be used in favour of lodash.keys. Rationale: users consuming the module may use polyfills (e.g. https://github.com/zloirock/core-js) when their projects need it. It shouldn't be the module's responsibility to provide this.

Remove build step (e.g. rollup or babel). Rationale: want to avoid adding unnecessary amounts of boilerplate code that may unintentionally be added.

The module will be targeted for users of node v4+, which afaik, has ES6 support. So there is no need for a build step.

These changes will be released in v1.0.0.

@dashed any reason this was not rolled out?

@gajus got sidetracked 😅
I did few more maintenance commits; will roll out soon. 👍

@gajus published v1.0.0. Let me know if there are any issues.

Thank you

@dashed Is there a reason for releasing this as a v1?
This will make it really hard to propagate the update.

@gajus I think there were sufficient changes between this PR and v0.2.2 to warrant releasing this as v1. Especially for change in supported node.js version (node.js v4+).
The previous version of shallowequal, v0.2.2, was published sometime around August 2015. At the time, node.js was io.js (see: https://nodejs.org/en/download/releases/).

Unfortunatlely, this means the shallowequal dep will have to be updated downstream.


WIP: Testing behavior with undefined nodeset

Implementing negative tests in kuttl appears to be overly complicated with only limited support. Furthermore, given the status of kuttl project, we can't expect a significant change on their side.

Implementing negative tests in kuttl appears to be overly complicated with only limited support. Furthermore, given the status of kuttl project, we can't expect a significant change on their side.


kubectl exec -ti $POD_NAME -- nginx -v results in Error from server (NotFound): deployments.apps "nginx" not found

Following the steps from https://github.com/jamesward/kubernetes-the-easy-way/blob/master/docs/13-smoke-test.md I get:
❯ kubectl expose deployment nginx --port 80 --type NodePort

Error from server (NotFound): deployments.apps "nginx" not found

Fixed it by running kubectl create deployment nginx --image=nginx instead of kubectl run ... as described in previous steps. I guess kubectl run ... is kind of deprecated or something.

Thanks for reporting this. I've made updates to resolve this.


Add yashwanth0203

Sorry i didn't get it where should I edit in Readme file can you please
send any screenshot I am literally confused on instructions.
On Sat, 11 Sep 2021, 17:52 Adarsh Navneet Sinha, @.***>
wrote:

@.**** requested changes on this pull request.
Hey there, you have to add your details here
https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants--
or
https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants--
and your profile will be added there.
Thank you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/geeky01adarsh/DSA-Marathon/pull/6#pullrequestreview-751914936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASY7Q7TNQXI2UGSCOJUBUZTUBNCW3ANCNFSM5D24T5FA
.

Sorry i didn't get it where should I edit in Readme file can you please send any screenshot I am literally confused on instructions.
…
On Sat, 11 Sep 2021, 17:52 Adarsh Navneet Sinha, @.> wrote: @.* requested changes on this pull request. Hey there, you have to add your details here https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants-- or https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants-- and your profile will be added there. Thank you! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASY7Q7TNQXI2UGSCOJUBUZTUBNCW3ANCNFSM5D24T5FA .

Change it here https://github.com/geeky01adarsh/DSA-Marathon/blob/main/Git_and_Github/README.md i.e., the readme in Git_and_Github section

i am getting error page not found!!
On Sun, 12 Sept 2021 at 14:03, Adarsh Navneet Sinha <
@.***> wrote:

Sorry i didn't get it where should I edit in Readme file can you please
send any screenshot I am literally confused on instructions.
… <#m_-6209118351067537149_>
On Sat, 11 Sep 2021, 17:52 Adarsh Navneet Sinha, @.*> wrote: @.**
requested changes on this pull request. Hey there, you have to add your
details here
https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants--
or
https://github.com/geeky01adarsh/DSA-Marathon/tree/main/Git_and_Github#participants--
and your profile will be added there. Thank you! — You are receiving this
because you authored the thread. Reply to this email directly, view it on
GitHub <#6 (review)
https://github.com/geeky01adarsh/DSA-Marathon/pull/6#pullrequestreview-751914936>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASY7Q7TNQXI2UGSCOJUBUZTUBNCW3ANCNFSM5D24T5FA
.
Change it here
https://github.com/geeky01adarsh/DSA-Marathon/blob/main/Git_and_Github/README.md
i.e., the readme in Git_and_Github section
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/geeky01adarsh/DSA-Marathon/pull/6#issuecomment-917589892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASY7Q7Q4XJBXPJYPIH3SCE3UBRQVDANCNFSM5D24T5FA
.

It is changed to https://github.com/DSA-Marathon/DSA_Marathon/tree/main/Git_and_Github
I am closing this PR, open a new one, or if you have any doubt then ping us on discord.


chore(main): release 0.2.1

:robot: I have created a release beep boop
0.2.1 (2024-08-20)
Features

parse namespace k8s objects (#158) (cd0cef7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kurtosis-tech/kardinal/releases/tag/0.2.1 :sunflower:


Add the translation contribution guideline

Adding this guideline so translators will be able to find the Crowdin project and translate there. Also, translators can request a new language or discuss any other topics related to localization.
I would recommend also enabling the Badges & Status Images app that will allow generating a "localized" badge that also can be added to the Readme.

Codecov Report

Merging #328 (3b3f154) into master (9fb1eea) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #328   +/-   ##
=======================================
  Coverage   13.89%   13.89%
=======================================
  Files          16       16
  Lines         763      763
  Branches      103      103
=======================================
  Hits          106      106
  Misses        657      657

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


version: bump to 1.0.4

release notes draft:

fixed a bug in digitalocean provider where private ip attributes would be improperly indexed if there were also public ips

\cc @bgilbert


64bit support

Was wondering what your thoughts are on how it should work. There seems to be a lot of different approaches that kind of work and it's not clear what is the most sensible one. Some options are listed below:

add a ptr type to WasmType that generates an isize with corresponding load/store instructions

the abi has hard coded offsets so it seems that the parser crate needs to know if it's 32/64bit

add a parameter to the abi

the abi is currently hardcoded for every function, so it's not clear how to inject the pointer width

add a configurable pointer width in addition to Interface and AbiVariant, the Generator trait passes an enum WasmPtr { I32, I64 }

dealing with handles:

it is not clear if the handle index should always be an i32 on 64bit platforms, or if this is an additional configuration option (as on native it is just a ptr)
the handle cannot be an isize as the host ptr width is irrelevant, so it probably has to be generic. making it generic leaks abi details, as the handle is part of the public api

I don't think much thought has gone into the specifics of what this would look like in the code itself, but naively I would expect that the WasmType enum would change but instead there'd be some sort of configuration passed in when generating bindings whether it's for 32-bit or 64-bit. There aren't a ton of 64-bit use cases right now so this is still up-in-the-air.
As for handles I don't believe there has been much discussion about whether they should always use 32-bit indices or 64-bit indices.

I'm going to close this in favor of https://github.com/WebAssembly/component-model/issues/22 since memory64 hasn't been defined relative to the component model yet and that will need to happen before support can be implemented here.


Line/column information for productions

I have very little idea of what this means for the API, but it would be super handy to retain the line/column from which a given production was parsed.
This has applications for reporting parse errors, naturally, but I think this is even broader—for example, tools could use this information to pretty-print what they actually parsed, or instruct users on where a certain behavior is coming from.

Given #43, I think this’ll come down to returning the index in a CollectionType. That’ll give you enough to recover the line/column info (and we could provide conveniences for that), while still allowing other collections to be parsed naturally, e.g. trees would return a Zipper.
As to the API beyond error reporting, that’s a tricky one. I think we should try to write a couple of motivating examples.

cf #68, which is prerequisite to this.

With #70 in, I’ve been thinking about this a little further. I think it’s as simple as extending/augmenting the map operator (-->) such that the function receives the entire result of the parser:
(Input, Input.Index) -> (Tree, Input.Index)
                         ^^^^^^^^^^^^^^^^^
                          THIS RIGHT HERE

If we change -->, we break all existing uses of it except e.g. x --> const(…).
If we overload -->, we break all x --> const(…), and we make the type inferencer’s job harder, and it’s already n² or even 2ⁿ in a few places AFAICS.
If we add another operator then there are two ways to map things, which is gross.


javadoc 4.1.0

generated javadoc for 4.1.0 release since the github action is not working at the moment

this is the result of running "mvn javadoc:javadoc" using the artifact from https://dist.apache.org/repos/dist/release/datasketches/memory17/4.1.0/


StylesProvider's injectFirst option not working for the server-side rendering

Using injectFirst prop of StylesProvider does not change the injection order when render by server-side, especially in next.js example.
Expected Behavior 🤔
By using injectFirst, MUI styles should be injected faster then other styles (styled-component in my case)
Current Behavior 😯
Style injected first on the client side but not on the server side.
Steps to Reproduce 🕹
As I'm not sure if this is bug or is intended behavior, I'm not created the codesandbox yet. But if someone can tell it's a bug I'll create the codesandbox reproduction later.

@ScripterSugar The injectFirst option has no impact on the initial response from the server. With Next.js, you should make sure the serialization order of the CSS is correct, it's in those lines:
https://github.com/mui-org/material-ui/blob/22ea5ae3b435f6a16b902c8621544b3e08a20783/examples/nextjs/pages/_document.js#L72

@oliviertassinari
That resolved my issue. Thank you for the answer :)

I find that if I use injectFirst , it would make css blinking


Return a task when queueing chargeback report generation for services

When chargeback report generation is queued, it should send back a task. This is being added to the API, and the task needs to be returned to allow the user to see the status of it.
Needed for https://github.com/ManageIQ/manageiq-api/pull/301
@miq-bot add_label enhancement, services

I'm good with this.

Thanks @gmcculloug for your 👀 !!


Support editor to return PromiseLike object

Enable editor to return Promise object which contains new JSON object as its value

@rejas hello there, can you please checkout this pull request for me, I really need this feature in my own project

@superfreeeee Unfortunately I dont have project anymore where I use this so you have to tell me if is this a breaking change or do have existing projects adjust if I merge this?

@superfreeeee Unfortunately I dont have aproject anymore where I use this. So you have to tell me please: is this a breaking change or do existing projects have to adjust if I merge this?

This will be no breaking change, but enable developers to return PromiseLike object and fit into node Readable stream created by gulp.
After this update, those who use this plugin won't need to change there code, but they can change editor function to async if they need it

Thanks for the PR!


BUG: Error collecting tests due to inconsistent parameterization order in test_b_orthonormalize

Describe your issue.
Test collection in pytest-xdist may fail due to inconsistent parameterization order in test_b_orthonormalize.
The problem is that test_b_orthonormalize is parameterized over REAL_DTYPES,
https://github.com/scipy/scipy/blob/f990b1d2471748c79bc4260baf8923db0a5248af/scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py#L103-L105
which is a set:
https://github.com/scipy/scipy/blob/f990b1d2471748c79bc4260baf8923db0a5248af/scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py#L24
The pytest-xdist documentation explains why this is a problem, and the surrounding context shows that this is known:
https://github.com/scipy/scipy/blob/f990b1d2471748c79bc4260baf8923db0a5248af/scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py#L22-L28
There are a couple of questions I have before opening a PR to fix this:

Is REAL_DTYPES (vs. say VDTYPES) indeed the correct set of types over which to parameterize all three of Vdtype, Bdtype, and BVdtype?
What would be an appropriate name for a sorted-tuple version of REAL_DTYPES to go alongside VDTYPES and MDTYPES?

Reproducing Code Example
Simply build and run the tests—but the failure seems to be environment-dependent and is not guaranteed to be reproducible. This doesn’t matter, as the root cause can be found by inspection of the relevant test code.

Error message
==================================== ERRORS ====================================
_____________________________ ERROR collecting gw1 _____________________________
Different tests were collected between gw0 and gw1. The difference is:
--- gw0

+++ gw1

@@ -33386,84 +33386,84 @@

 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float32-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float32-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float64-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float64-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float32-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float32-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float32-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float64-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float64-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-float64-longdouble-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float32-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float32-longdouble-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float32-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float32-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float64-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float64-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float32-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float32-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float32-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float32-10-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-1-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-2-50]
+scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float64-1-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float64-2-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-float64-longdouble-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float32-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[float64-longdouble-longdouble-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float32-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float32-longdouble-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float32-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-float64-longdouble-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float32-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-float64-10-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-1-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-2-50]
-scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_b_orthonormalize[longdouble-longdouble-longdouble-10-50]
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_nonhermitian_warning
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_regression
 scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py::test_diagonal[30-4-3]
To see why this happens see Known limitations in documentation
=========================== short test summary info ============================
ERROR gw1
============================== 1 error in 15.68s ===============================

SciPy/NumPy/Python version and system information
I can’t reliably reproduce this, so I haven’t been able to collect this information,
but it shouldn’t be relevant since the root cause is clear. The first line of output
should look  like:

1.11.3 1.26.0 sys.version_info(major=3, minor=12, micro=0, releaselevel='final', serial=0)

cc @lobpcg

I have used this setup with REAL_DTYPES in several PRs. If this is a problem, it better be fixed everywhere.

I have used this setup with REAL_DTYPES in several PRs. If this is a problem, it better be fixed everywhere.

I looked for other instances of the same problem. I didn’t find anywhere else in main that a set (or dict) was used for a parameterized/“parametrized” test.
I found some cases like this, which are OK because the order is consistent:
REAL_DTYPES = [float32, float64]

[…]
    @pytest.mark.parametrize("FOOdtype", REAL_DTYPES)

And something like this is not as good—and should be changed—because the test execution will vary based on set iteration order, but it wouldn’t cause an error with pytest-xdist. However, I didn’t find any actual cases like this.
REAL_DTYPES = {float32, float64}

[…]
    for i, dt in enumerate(REAL_DTYPES):
        # do something that depends on i and dt
        assert_allclose(...)

And finally, there are some very similar cases where a consistently-ordered tuple or list is formed from a set before using it to paramet(e)rize a test, e.g.:
https://github.com/scipy/scipy/blob/f990b1d2471748c79bc4260baf8923db0a5248af/scipy/sparse/csgraph/tests/test_graph_laplacian.py#L163-L167
https://github.com/scipy/scipy/blob/f990b1d2471748c79bc4260baf8923db0a5248af/scipy/sparse/csgraph/tests/test_graph_laplacian.py#L316
So far, test_b_orthonormalize is the only one I found that uses a set directly for paramet(e)rization without first forming a consistently-ordered tuple or list.

@musicinmybrain

Is REAL_DTYPES (vs. say VDTYPES) indeed the correct set of types over which to parameterize all three of Vdtype, Bdtype, and BVdtype?

with

scipy/scipy/sparse/linalg/_eigen/lobpcg/tests/test_lobpcg.py

Lines 22 to 28 in f990b1d
 INT_DTYPES = {np.intc, np.int_, np.longlong, np.uintc, np.uint, np.ulonglong}
 # np.half is unsupported on many test systems so excluded
 REAL_DTYPES = {np.single, np.double, np.longdouble}
 COMPLEX_DTYPES = {np.csingle, np.cdouble, np.clongdouble}
 # use sorted tuple to ensure fixed order of tests
 VDTYPES = tuple(sorted(REAL_DTYPES ^ COMPLEX_DTYPES, key=str))
 MDTYPES = tuple(sorted(INT_DTYPES ^ REAL_DTYPES ^ COMPLEX_DTYPES, key=str))

Yes, I actually now recollect writing this sorted(tuple after hitting an error just taking the union. I do not recall getting errors just from using REAL_DTYPES without  sorted(tuple .
Let me now answer your question:
in test_b_orthonormalize all the data generated for testing is actually real so I probably only used REAL_DTYPES because of that. Using instead
 VDTYPES = tuple(sorted(REAL_DTYPES ^ COMPLEX_DTYPES, key=str))

for all three of Vdtype, Bdtype, and BVdtype is a good idea - hopefully it passes.  I think that it should pass, but I do not remember trying this.
Additionally, it would be even nicer to add a complex-only test using COMPLEX_DTYPES = {np.csingle, np.cdouble, np.clongdouble} for all three of Vdtype, Bdtype, and BVdtype with the actual complex-valued generated data, i.e., adding the imaginary component.  Possibly/likely
vals = np.arange(1, n+1, dtype=float) in the definition of 'B' should be left as is without adding the imaginary component, since B represents a Hermitian matrix so its diagonal must be real.
I probably just ran out of steam to do all this at the end of my PR.

Thank you; that’s a very helpful response.
I tried using VDTYPES locally, and all of the parameterizations involving complex dtypes failed with large absolute and relative errors.
For now, I think I’ll just offer a minimal fix by introducing a new sorted-tuple variable called RDTYPES and use that for paramet(e)rization. Let me know if you think there is a better name for this than RDTYPES.

Thank you; that’s a very helpful response.
I tried using VDTYPES locally, and all of the parameterizations involving complex dtypes failed with large absolute and relative errors.
For now, I think I’ll just offer a minimal fix by introducing a new sorted-tuple variable called RDTYPES and using that for paramet(e)rization. Let me know if you think there is a better name for this than RDTYPES.

Maybe please file an issue that complex types fail? I'll try to look at it. It should have passed, so something may be not right.
V name is used because it's the type of the parameter V. Maybe don't introduce new names but just use inline tuple(sort

V name is used because it's the type of the parameter V. Maybe don't introduce new names but just use inline tuple(sort

Amended.
I ended up just dropping the tuple() for the inline expressions; sorted() returns a list, which is just fine as-is. I didn’t go and change any of the other sorted tuples, though.

It would be nicer if you make all occurrences consistent including even those you have already located in other test modules IMHO.

It would be nicer if you make all occurrences consistent including even those you have already located in other test modules IMHO.

Since that change is independent, I chose to open a separate PR: https://github.com/scipy/scipy/pull/19445


[Bug] name your bug

hi, sorry for my bad English I'm French
My issue : Terminal says : No such file or directory
I've read somewhere that "be sure to be in the spleeter folder if you are using cloned repository or replace audio_example.mp3 by a valid path to an audio file)", but I can't find where is the spleeter folder
Many thanks in advance !

Please follow the documentation for detailed installation. Closing the issue as it does not respect issue templating.


Where are file downloaded?

I downloaded someones IG photos and cant find where they where saved to?

According to the readme:
By default, downloaded media will be placed in <current working directory>/<username>.
Do you have write permissions to the current folder that the program is in?

By default, it saves in C:\Users\User
or just search username in this folder and you will find it


Fixed broken link to v0.10 migration guide

Before submitting a pull request, please make sure the following is done...

Fork the repo and create your branch from master.
If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure that:

The test suite passes (npm test)
Your code lints (npm run lint) and passes Flow (npm run flow)
You have followed the testing guidelines

If you haven't already, complete the CLA.

Please use the simple form below as a guideline for describing your pull request.
Thanks for contributing to Draft.js!

Summary
Fixed broken link to v0.10 migration guide
Test Plan
None

Thanks @wchaering ! It isn't clear to me if you've signed the CLA - if so then this is good to go. Usually the bot adds a tag once it's signed.

@flarnie Just signed it--should be good to go now.


Add a link to instructions for getting zone_id

This adds a link to instructions for getting zone_id.

Created based on the feedback on #166


As a router operator I want to easily spin up a router

Problem
Router docker-compose file needs to be recreated for new architecture.
Ideas to solve this
Fix docker-compose file.
Acceptance Criteria

[ ] docker-compose up spins up file.

Impact

What OKR goal does this align to?
Migrate users to Amarok

Provide Impact estimate = ideally quantitative forecast, if not then qualitative description of impact

Other Notes
A clear and concise description of what the problem is

P0


Use local resolver settings instead of google DNS

Use the local DNS settings saved in /etc/resolv.conf instead of using <IP_ADDRESS> when not specifying an ip address from the CLI.
Note, on Windows systems this is not available. In those case you can still use the tool with the --dns-server-ip flag.
Closes #1

Thanks for your contribution @mmourick 👏🏼


Json compiling errors

Hello lewisxhe, just found your library and look awesome for one of me projects, I'm looking forward to test it! In my first verify, I got the following errors:
Arduino: 1.8.7 (Mac OS X), Board: "ESP32 Dev Module, Disabled, Default, QIO, 80MHz, 4MB (32Mb), 921600, None"
Compiling sketch...
/Users/mau/Library/Arduino15/packages/ArduCAM_ESP32S_UNO/tools/xtensa-esp32-elf-gcc/1.22.0-80-g6c4433a-5.2.0/bin/xtensa-esp32-elf-g++ -DESP_PLATFORM "-DMBEDTLS_CONFIG_FILE="mbedtls/esp_config.h"" -DHAVE_CONFIG_H -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/config -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/bluedroid -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/bluedroid/api -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/app_trace -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/app_update -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/bootloader_support -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/bt -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/driver -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp32 -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp_adc_cal -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp_http_client -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp_https_ota -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp-mqtt -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/esp-tls -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/ethernet -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/fatfs -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/freertos -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/heap -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/http_server -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/jsmn -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/log -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/mdns -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/mbedtls -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/mbedtls_port -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/newlib -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/nvs_flash -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/openssl -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/spi_flash -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/sdmmc -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/smartconfig_ack -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/spiffs -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/tcpip_adapter -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/tcp_transport -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/ulp -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/vfs -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/wear_levelling -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/xtensa-debug-module -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/lwip -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/coap -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/console -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/expat -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/json -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/newlib -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/nghttp -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/soc -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/tools/sdk/include/wpa_supplicant -std=gnu++11 -fno-exceptions -Os -g3 -Wpointer-arith -fexceptions -fstack-protector -ffunction-sections -fdata-sections -fstrict-volatile-bitfields -mlongcalls -nostdlib -Wno-error=unused-function -Wno-error=unused-but-set-variable -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-sign-compare -fno-rtti -MMD -c -DF_CPU=240000000L -DARDUINO=10807 -DARDUINO_ESP32_DEV -DARDUINO_ARCH_ESP32 "-DARDUINO_BOARD="ESP32_DEV"" "-DARDUINO_VARIANT="esp32"" -DESP32 -DCORE_DEBUG_LEVEL=0 -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/cores/esp32 -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/variants/esp32 -I/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/src -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/libraries/WiFi/src -I/Users/mau/Developer/Arduino/hardware/espressif/esp32/libraries/WiFiClientSecure/src -I/Users/mau/Developer/Arduino/libraries/ArduinoJson/src /var/folders/yf/kz_kxlh972n4jdvjn7tcd2cc0000gn/T/arduino_build_150314/sketch/BIGIOT_UpdateImage.ino.cpp -o /var/folders/yf/kz_kxlh972n4jdvjn7tcd2cc0000gn/T/arduino_build_150314/sketch/BIGIOT_UpdateImage.ino.cpp.o
/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/examples/BIGIOT_UpdateImage/BIGIOT_UpdateImage.ino:57:22: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
String request = "POST /pubapi/uploadImg/did/"BIGIOT_DEVICE_ID"/inputid/"BIGIOT_INTERFACE_ID" HTTP/1.1\r\n";
                  ^

/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/examples/BIGIOT_UpdateImage/BIGIOT_UpdateImage.ino:57:67: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
String request = "POST /pubapi/uploadImg/did/"BIGIOT_DEVICE_ID"/inputid/"BIGIOT_INTERFACE_ID" HTTP/1.1\r\n";
                                                               ^

/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/examples/BIGIOT_UpdateImage/BIGIOT_UpdateImage.ino:20:25: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
"Content-Type: image/jpeg\r\n\r\n";
                     ^

/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/examples/BIGIOT_UpdateImage/BIGIOT_UpdateImage.ino:22:21: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
char *request_end = "\r\n--------------------------ef73a32d43e7f04d--\r\n";
                 ^

BIGIOT_UpdateImage:27:1: error: 'StaticJsonBuffer' does not name a type
StaticJsonBuffer<512> jsonBuffer;
^
/Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master/examples/BIGIOT_UpdateImage/BIGIOT_UpdateImage.ino: In function 'void update_image()':
BIGIOT_UpdateImage:125:24: error: 'jsonBuffer' was not declared in this scope
JsonObject &root = jsonBuffer.parseObject(start);
                    ^

BIGIOT_UpdateImage:126:15: error: 'class ArduinoJson660_0_0::JsonObject' has no member named 'success'
if (!root.success())
           ^

Multiple libraries were found for "WiFi.h"
Used: /Users/mau/Developer/Arduino/hardware/espressif/esp32/libraries/WiFi
Not used: /Applications/Arduino.app/Contents/Java/libraries/WiFi
Using library ESP32-Camera-Arduino-master at version 0.1.0 in folder: /Users/mau/Developer/Arduino/libraries/ESP32-Camera-Arduino-master
Using library WiFi at version 1.0 in folder: /Users/mau/Developer/Arduino/hardware/espressif/esp32/libraries/WiFi
Using library WiFiClientSecure at version 1.0 in folder: /Users/mau/Developer/Arduino/hardware/espressif/esp32/libraries/WiFiClientSecure
Using library ArduinoJson at version 6.6.0-beta in folder: /Users/mau/Developer/Arduino/libraries/ArduinoJson
exit status 1
'StaticJsonBuffer' does not name a type
Could you help with this one? Don't know what I am doing wrong. Thanks a lot in advance!
Arduino IDE 1.8.7
MacOS 10.14.1

The problem is that the code you're compiling is not compatible with the version of the ArduinoJson library you have installed.
There are two solutions:

Update the code to work with the 6.x ArduinoJson API: https://arduinojson.org/v6/doc/upgrade/
Roll back the ArduinoJson library version to the last one with a compatible API: 5.13.2.

Reference: https://arduinojson.org/v5/faq/error-jsonbuffer-was-not-declared-in-this-scope/

Thanks you so much for your time and prompt response per1234, indeed that was the problem, I downgraded to Arduinojson 5.13.2 and compiling is ok now! Just another quick question:
How could I change the image size and frame rate? I’m in no way a proficient programmer so I digged a little bit into the files in the src folder and found some lines related with them, I changed nothing there, I just changed line 100 of ESP32_SoftAP_cam to CAMERA_FS_VGA and got an garbage SVGA image in the browser.  With respect to the frame rate, I also have no idea : (
Please let me know if I should close this issue and contact you somehow to solve this question because it is really not an issue? Your help is being much appreciated
Regards!

Hi, mau-lopez, thank you for the answer to per1234，the test before changing the image resolution will not work for a while, change the frame rate and although there is an interface, but it is not perfect, recently too busy, there is no time to perfect this code

Lewis, thanks a lot for the information! I will be following your code for any updates, I think it is great to have the camera functionality in Arduino. Thanks again and have a great one!

Lewis, thanks a lot for the information! I will be following your code for any updates, I think it is great to have the camera functionality in Arduino. Thanks again and have a great one!
Mauricio López V
On Nov 14, 2018, at 20:11, lewis he <notifications<EMAIL_ADDRESS>wrote:
Hi, mau-lopez, thank you for the answer to per1234，the test before changing the image resolution will not work for a while, change the frame rate and although there is an interface, but it is not perfect, recently too busy, there is no time to perfect this code
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/lewisxhe/ESP32-Camera-Arduino/issues/1#issuecomment-438890142, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqhrZt2imbcv296FjQ7vZtVPNENEq72kks5uvM1LgaJpZM4Ycyzq.


Add documentation tool

Implements #8276
Example connected to development version of vscode extension

I want to be able to provide documentation for macros but can't seem to figure out a way to do that currently, not as familiar with the compiler as I want to be. Something like this, which currently fails:
  it "find documentation of macro" do
    assert_documentation %(
      # ༓foo docs
      macro foo
        def bar
        end
      end

      f‸oo
      bar
    ), check_lines: false
  end

Thank you for this contribution. But I think we'll need to talk a bit more about the details of this feature though, before we can commit to a specific implementation.
We ask all major feature contributions to go through a discussion of the general design first.
#8276 is merely a thin idea with very little details. That's hardly a design spec.
And actually I don't think this PR has much in common with that idea. I understand #8276 is mainly a command line interface to query contents from the documentation dump (index.json). While this is a tool for IDE integration.
IMO the main functionality of this PR is identifying the target def (or path) for a given source code location. Fetching the documentation for that is just a small extra on top, but wouldn't be necessary. Given the name of the target def/path, it's easy to fetch the documentation from index.json.
Considering that, I believe it would be quite reasonable to achieve the same result with a combination of crystal tool implementations to query the target def and crystal doc to fetch the focumentation.
This of course requires two separate compiler instances, doing double work (and taking double time). So it's not ideal. https://github.com/crystal-lang/crystal/issues/14705 would be an improvement for that.
Thinking about crystal tool implementations, maybe we could add an alternative output format for documentation to this command? It seems like this would be pretty similar to the proposal in this PR except that it's not a completely new tool but enhancing an existing one.

I think that makes sense to me. Apologies for going through with an implementation before having more discussion.
I'll try seeing how well crystal tool implementations + crystal doc works and report back, don't want redundant tooling if we can't help it. Otherwise a --with-doc flag for the implementations command should be fairly easy to add.

No need to apologize. The purpose of having a discussion fist is to protect you from wasting effort on working out an implementation if it gets rejected.


[BUG] Nextjs 14 run test with erro "SyntaxError: Cannot use import statement outside a module"

Are you using the latest version of this library?

[X] I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

[X] I have searched the existing issues and found nothing that matches

Describe the bug
First of all, I would like to thank you for the excellent work you have been doing with this library. However, I am facing an issue in my new project.
When I try to run my tests (just a simple test), it returns this error within the dist of safe-action. I noticed that a similar issue was opened in the past and resolved, but the problem seems to have returned:

These are the dependencies I am using:

Reproduction steps

add the library
try to run a base unit test

is also important to say that the page.tsx is a server component and the SearchArea.tsx is a client component.
this the unit test that is breaking:

Expected behavior
the test should pass
Minimal reproduction example
private repo
Operating System
macOS
Library version
7.8.0
Next.js version
14.2.5
Node.js version
21.7.3
Additional context
No response

Hi, please set up a public repo or a CodeSandbox project with a minimal reproduction of the issue so I can investigate the problem, thanks.

@TheEdoRan https://github.com/freirepaulo/next-safe-action public repo that has the issue - to reproduce is just run yarn and yarn test

If I change all the imports and exports in the hook.mjs and index.mjs resolves the problem, but I don't know what will impact the library structure....

Thank you for providing the repro. I solved the issue on my end by setting this option in next.config.mjs:
const nextConfig = {
+  transpilePackages: ["next-safe-action"],
};

Vitest should be a better testing framework though, if you can switch to it. Let me know if setting that option fixes the issue for you as well, thanks!


Fix Apdex score example in Histograms page.

I noticed the mistake comparing it to the formula in Wikipedia: https://en.wikipedia.org/wiki/Apdex

Good catch, thanks!

Noooo! This is frequently confused so it should be explained, but the original formula is correct. The reason is that the histogram buckets are cumulative; the le="0.3" bucket is also contained in the le="1.2" bucket; dividing by 2 corrects for that.

@matthiasr  Oh boy, sorry.
Mind reverting and adding a brief explanation? – I probably should not stack up my incompetence here :)

@fabxc yep, was already on it


Signed Integers TwosComplement fix to WrappingNeg

Type of change

Bug fix

Changes
The following changes have been made:

The TwosComplement trait was not correctly implemented. To stay in line with Rust's practices, the WrappingNeg trait now replaces it with the original desired functionality of the TwosComplement trait.
Bits for I128 and I256 are now correct
The indent for I128 and I256 are now correct

Notes

This PR changes the folder names in the tests from iX_twos_complement_test to iX_wrapping_neg_test.

Breaking Changes
The following demonstrates the breaking change. While this example code uses the I8 type, the same logic may be applied to the I16, I32, I64, I128, and I256 types.
Before:
let my_i8 = i8::zero();
let twos_complement = my_i8.twos_complement();

After:
let my_i8 = i8::zero();
let wrapping_neg = my_i8.wrapping_neg();

Checklist

[x] I have linked to any relevant issues.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation where relevant (API docs, the reference, and the Sway book).

[ ] If my change requires substantial documentation changes, I have requested support from the DevRel team

[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.
[x] I have updated the changelog to reflect the changes on this PR.

Dependent on https://github.com/FuelLabs/docs-hub/pull/340


Once enabled, the fragmenting process runs on all subsequent slides

The new fragment syntax described on the wiki is very nice.  The ability to embed other special markup within bulleted items will be very handy.
One issue that I have discovered with it is that once the fragmenting process is enabled on a slide, the bullets on all subsequent slides are fragmented.  It seems like the @ulend is not having the anticipated effect.
See https://gitpitch.com/DSpace-Labs/DSpace-rel-demo/webinar?grs=github
Note the behavior after Slide number 6.

Hi Terry, thanks for the feedback. And I'm glad to hear you like the new list fragment syntax.
You have indeed uncovered a bug. Which I have been able to reproduce. And I have a local patch that fixes it. But I do need to do some additional testing. So you can expect the patch to go live on gitpitch.com within about 24 hours. I'll bump this thread once that happens.

A patch for this issue has been pushed live on gitpitch.com. Can you please test and verify. Let me know if you find any problems. If not, you can go ahead and close out this thread.

Works just as I hoped.  Thanks for the quick fix and the great service.


A few key build fixes

These fix issues #5 and #6

The changes are integrated into repository as part of v0.1.4-beta


Fields lists and field ranges

Adds support for field ranges as part of a field list. For example:
$ tsv-select --fields 1,2,17-35  data.tsv

Available anywhere a list of fields can be entered.

Codecov Report

Merging #77 into master will increase coverage by 0.25%.
The diff coverage is 99.4%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
+ Coverage   97.25%   97.51%   +0.25%
==========================================
  Files          15       15
  Lines        3356     3618     +262
==========================================
+ Hits         3264     3528     +264
+ Misses         92       90       -2

Impacted Files
Coverage Δ

tsv-select/src/tsv-select.d
96.66% <100%> (-0.16%)
:arrow_down:

tsv-join/src/tsv-join.d
93.66% <100%> (ø)
:arrow_up:

tsv-uniq/src/tsv-uniq.d
97.33% <100%> (ø)
:arrow_up:

tsv-summarize/src/tsv-summarize.d
97.43% <100%> (+0.35%)
:arrow_up:

common/src/tsvutil.d
99.54% <99.3%> (-0.46%)
:arrow_down:

Address issue #71


Vulnerability roundup 73: qemu-4.0.0: 1 advisory

search, files

[ ] CVE-2019-13164 (nixos-unstable)

Scanned versions: nixos-unstable: 239fffc90d7. May contain false positives.

See also #64184

This will be fixed by https://github.com/NixOS/nixpkgs/pull/66775.


Review

https://stackoverflow.com/questions/34304833/failed-building-wheel-for-psycopg2-macosx-using-virtualenv-and-pip

brew install postgresql
and add /usr/local/opt/postgresql/bin to PATH (depending on your shell)

also, sidenote, you could use docker to keep your host system clean


App is crashing when clicked on Received credentials

Describe the bug
App is crashing when clicked on Received credentials
To Reproduce
Prerequiste: VC is downloaded and stored in sharing device and downloaded VC should contain photo of resident.
Device A - Requesting device (iOS)
Device B - Sharing device (Android)
steps:

open qr code in Device A
open scanner in Device B
scan the qrcode from Device B
select VC to share and click on "Accept request and verify".
camera opens up - captures photo of resident sharing initiated
Accept incoming VC in Device A

Current behavior
App crashes when clicked on any VC which is received from resident.
Expected behavior
We should be able to click and view received VC.
Screenshots
https://user-images.githubusercontent.com/79500509/206624024-27fa793d-8c3b-4065-a080-418b8c8f64b4.MP4
Smartphone (please complete the following information):

Device: iPhone 8 , One plus Nord 2
OS: 16.0.2, 12
Inji app version: 0.4.1 (5)->testflight
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa5.mosip.net

Additional context
Able to replicate this issue in iOS -> iOS and iOS -> Android as well
Android apk: https://github.com/mosip/inji/actions/runs/3626503207

Verified in
wallet:
iPhone 8
iOS version 16
BLE 5.0
Inji app version: 0.4.1 (29)->testflight
app version:

verifier
One plus Nord 2
OS version:  12
BLE 5.2
Commit id of the app: 4c2ca4b
APK link: https://github.com/mosip/inji/actions/runs/4447486079

Able to view the received cards , crashing issue is resolved.
iOS <-> iOS cannot be verified as iOS cannot be a verifier.


Why does the sdk create uls_scratch directory?

I am a bit confused. I am trying to create a new dat with via the promise syntax and it is creating a directory uls_scratch within my current working directory, but apparently not creating a folder for storing the dat data.
const { DatArchive, destroy } = require("dat-sdk/auto");

async function main() {
  const archive = await DatArchive.create({ title: "My Archive" });
  await archive.writeFile("/example.txt", "Hello World!");
  destroy();
}
main();

What is this directory and why is it not cleaned up? Where is the actually data getting stored?
Or does this use RAM?

Oh dang. The folder is created as part of universal-localstorge I was trying to figure out a unified API for tracking saved keys between the browser and Node.
The actual Dat data storage is using universal-dat-storage. It uses the env-paths module to find storage on your platform for the app. On Windows it's inside ~/AppData/Roaming/Dat, on MacOS it's on ~/Library/Application Support/dat, and on Linux it should be somewhere in ~/.local. You can find more details in the source of that module. :) https://github.com/sindresorhus/env-paths/blob/master/index.js

It might be worth forking that module in this case. It looks relatively simple, and also kind of unmaintained. That would enable this SDK to have more control over the generation of temp files, and most importantly also clean up after itself.

I might have time to do it next week, but in the meantime, a PR with a forked version of the module would be very much appreciated. 💜

Is the fork necessary? Because it would be another module to maintain. env-paths has a property to access a temporal directory. Maybe the only thing to consider is the portability of using something like this. But this would only be a concern if we consider other dat ports like datcxx or the rust version (which are on an early stage).
Why it's not being cleaned after use it is because it's not treated as a temporal directory. dats are being stored in the user's home and the home dir is obtained by using env-paths.
:v:

@dpaez  I think what @e-e-e meant was that they'd fork the universal-localstorage module to prevent it from creating this uls_scratch directory, not that they'd fork env-paths.

alright, that is way better ^_^


[2pts] Create the ER diagram - Group task

Create the ER diagram displaying the tables & relationship between them.

It looks like the relations between tables are made well 👍


Namespace refactoring Scenario tests

PR at initial review to get feedback from all languages.
https://github.com/Azure/cadl-ranch/pull/775


Add 5000 nodes scale test

Add a new Github Actions workflow to run a performance scale test on a cluster with 5000 nodes.
Fixes: #33778

/scale-5000


Properly parse multi-digit Python "versions".

The main focus of the PR is the helpers needed to fix the situation where the version for Anaconda is getting reported as "38.0.0".
Note that, from the related bug report, the underlying cause is unclear.  This PR will only help if the relevant code is using the helpers from the new component.  Given that we're dealing with conda, that might not be the case.  There may need to be some tweaks in src/client/pythonEnvironments/discovery/locators/services/condaLocator.ts to address that.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
~[ ] Has a news entry file (remember to thank yourself!).~
[x] Appropriate comments and documentation strings in the code.
~[ ] Has sufficient logging.~
~[ ] Has telemetry for enhancements.~
[x] Unit tests & system/integration tests are added/updated.
~[ ] Test plan is updated as appropriate.~
~[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).~
~[ ] The wiki is updated with any design decisions/details.~

Note that all the tests passed on Thursday and the only change to the PR since then is to a doc comment.  So the latest failures are not a concern.


On Windows: ImportError: No module named win32api

While running the example ui_in_gui I got this error
import win32api
ImportError: No module named win32api

It seems the dependency pypiwin32 is needed on Windows and it has to be installed as administrator even if a virtual environment is being used (dll involved.

@krishna664 try pip install pypiwin32 instead and make sure you have administrative rights on the CLI you're running it from

Hi, I am working on windows with python 2.7.x and i have already installed pypiwin32 showing requirement already satisfied on the command Line , how ever the python script shows error saying No module named win32api when i  import winspeech
for text to speech

If the suggestions already provided does not solve your problem, then have a look at stackoverflow, where this question has been asked and answered multiple times, or use the link given above, which leads to the official forum for the package in question.
I am closing this issue since it is attracting a lot of traffic unrelated to Calvin.


Add extracting/publishing feature of API tags, schemas & backends

Hello,
I have noticed that changes in the API tags, schemas & backends are not being detected by the current release of this software. Therefore, I would like to request a feature for this.
Overall a great tool which I will continue to use in the future!

Thanks @sweco-nltbim. Glad to hear that you found the tool useful. We are planing to incorporate backends as tracked in #56. We will create a feature request for the API tags and schemas

This has been released as part of Release v1.0.0


Fix a bug due to missing overloads in ordered_map container

This PR adds some missing overload to the ordered_map container to fix issue #2315.
Closes #2315

Coverage remained the same at 100.0% when pulling e590604822b6a62fb8555fd0f6da3fc82da9bc20 on issue2315 into 1b8efed06f04a0b2ff612d55263c0496b527c00d on develop.


🎉 3.0.0

ℹ About this release

Version: 3.0.0
Type: major
Last Release: 2.0.1 (2/8/2023, 8:20:14 PM) [?]
Commits to merge: 20 [?]

Build System

Deprecate node.js 12 (426588b)

chore

Remove cjs (c8da1df)

⚡ BREAKING CHANGES

Removed cjs, so this module is now pure ESM. See also https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
From now on, only node.js ^14.8.0 || >=16.0.0 are supported

📦 Dependencies

Update got from ^11.8.6 to ^12.5.3

📦 Development Dependencies

Added tsup ^6.7.0

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

npm package (@latest dist-tag)
GitHub release
v3.0.0

Your semantic-release bot :package::rocket:


Function Worker - kubernetesContainerFactory

Describe the bug
I managed to bring my pulsar cluster up using this helm chart and some modifications to enable mTLS authentication.
This part is working and I plan to make a PR to help get this upstream. However, when I run pulsar functions with the kubernetesContainerFactory the config state is not inherited from the broker to the workers that get created via the kubernetesContainerFactory.  The following files are default and not configured:

certs/*
function_worker.yml
client.conf

I see that a StatefulSet is created, and I can modify that to do some hackery, but I am wondering if I missed something or is this a bug in the way the functions workers are spawned when TLS is enabled.
To Reproduce
Steps to reproduce the behavior:

enable TLS
modify broker, proxy, toolset, bookkeeper, zookeeper-configmap.yaml to include tls authentication bits
Enable function worker
Deploy helm chart.

Expected behavior
I would think that the function workers would inherit their config state from the brokers:  From the documentation:
In this mode, most of the settings are already inherited from your broker configuration (for example, configurationStore settings, authentication settings, and so on) since functions-worker is running as part of the broker.
Unless I have missed a step that I can't find any documentation on, I think this part is needed.
Additional context
I am using a fork from Master and my functions works do work correctly with no TLS and not authentication. Once I add authentication they do not work as they do not have any configs.

#435 solves the problem. However there's no mTLS between Function worker and Broker. A new issue can be opened to cover that. Closing this issue.


single shards limit error

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?

3.1.0

Which project did you use? Sharding-JDBC or Sharding-Proxy?

sharding-jdbc-core

Expected behavior
Actual behavior

分页查询路由到单表后，ParsingSQLRouter对limit做了改写（不需要改写limit语句），但是又没有做归并。

Reason analyze (If you can)

路由到单表本来不需要做sql改写，3.0.0.M1这个版本是正确，对比代码如下：

3.0.0.M1

 private void processLimit(List<Object> parameters, SelectStatement selectStatement, boolean isSingleRouting) {
        if (isSingleRouting) {
            selectStatement.setLimit((Limit)null);
        } else {
            boolean isNeedFetchAll = (!selectStatement.getGroupByItems().isEmpty() || !selectStatement.getAggregationSelectItems().isEmpty()) && !selectStatement.isSameGroupByAndOrderByItems();
            selectStatement.getLimit().processParameters(parameters, isNeedFetchAll);
        }
    }

3.1.0

   private void processLimit(final List<Object> parameters, final SelectStatement selectStatement) {
        boolean isNeedFetchAll = (!selectStatement.getGroupByItems().isEmpty() || !selectStatement.getAggregationSelectItems().isEmpty()) && !selectStatement.isSameGroupByAndOrderByItems();
        selectStatement.getLimit().processParameters(parameters, isNeedFetchAll, databaseType);
    }

For English only, other languages will not accept.

same problem


Cannot delete folders

The delete button is hidden when a folder is selected.

Looking at this now. I think we have a policy that says that students cannot create or delete folders but that is not being strictly adhered to because we allow students to upload a zip file that we unzip, and create folders in the process.
We should revisit this policy to see if it still makes sense. If it does then we should also prevent students from uploading zip files in this way. If it does not, then we should remove this policy altogether instead of half applying it like we do now.

For me, the upload zip functionality is very important, especially when I have a lot of project files. Finding the changed files is a hassle, and updating every single file manually takes a lot of time. So I created a script that will automatically pack my project files into a zip file so that it can make sure every submitted file is up to date without unnecessary effort.
The folder was created because I forgot to test the packing script before I submitted the first zip file, and I can't delete the folder afterwards.

That makes sense. We are going to go with the following changes:

Update the policy so that all roles (including students) can create/destroy directories in the file viewer
Ensure that parent directories can still be created when strict required files are enforced. For example, if a student must submit a file subfolder/example.py then the student will be able to create subfolder/ before creating/uploading example.py into that directory.


Baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions

Follow https://github.com/opensearch-project/.github/issues/125 to baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions.
Close this issue when:

MAINTAINERS.md has the correct list of project maintainers.
CODEOWNERS exists and has the correct list of aliases.
Repo permissions only contain individual aliases as collaborators with maintain rights, admin, and triage teams.
All other teams are removed from repo permissions.

If this repo's permissions was already baselined, please confirm the above when closing this issue.

@dblock since you're admin can you check internally if point 3 and 4 are correctly set up and then close this issue?

Confirmed that this is aligned

Verified, thanks.


Ts rewrite

Rewrite of lunch.chalmers.it in typescript, may have forgotten some functionality though

Also please install git in the repo :')

LGTM


StackView and Grouped Buttons not showing the icon.

Hello!
I'm having some troubles using a group of radiobuttons that is inside of a Stackview. I'm hidding the stack view and when unhide the stack, button names appear but not the icon of the multiple selection. This just appear when i select a button and then toogles normally. What i'm doing wrong?
Thanks!

try setNeedsDisplay before unhide the stack?