Material radio component traps focus

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior
The implementation of Material radio button/radio group traps focus within the form control. This happens because the containing element passes on the focus to the firstmost radio option in the group. Line 32 in src/material/radio/src/radio.type.ts:
onContainerClick(event: MouseEvent): void {
  if (this.radioGroup._radios.length && !this.radioGroup.selected) {
    this.radioGroup._radios.first.focus();
  }
  super.onContainerClick(event);
}

The focus does not update correctly until an option has been selected two times. This can be the same option or two different options. I suspect that the line this.radioGroup._radios.first.focus() or indeed the condition for the if statement above is the culprit.
The problem with this behavior is that when the user fills out a form, selects a radio option and moves on to the following field(s), the radio group remains in focus—i.e. keeps its 'active'—styling even though focus has moved to another field.
Expected behavior
The focus of the radio group should be correctly tracked. Further, I don't see any particular reason why focus should be automatically moved to the firstmost radio option, as this is usually handled simply by pressing the Tab key an extra time.
Minimal reproduction of the problem with instructions

Click anywhere within the containing element of a radio group. The firstmost radio option receives focus
Now click anywhere outside this containing element. The entire form group should lose focus (i.e. lose 'active' styling), but does not
Select an option in the radio group
Click outside the containing element. Still no focus change.
Select another (or the same) option in the radio group
Click outside the containing element. Focus now correctly updates.

StackBlitz: https://stackblitz.com/edit/ngx-formly-ui-material-h8udre?file=app/app.component.ts
Please tell us about your environment:
macOS 10.14.5
Firefox 68.0.1
Angular 7.0.3
ngx-formly 5.3.0
rxjs ^6.2.2

The same seems to apply for multicheckbox. Focus is kept even after clicking outside the containing element.

checked on my side and it seems the previous fix also fixed the multicheckbox issue too (2 in 1 😄).

@aitboudad that's wonderful :) I am on version 5.3.0, how can I get a hold of your fix?

the fix should be landed in v5.4, I'll try my best to make it available next Monday.
if you can't wait until then, let me know to provide you a workaround.

Next Monday would be brilliant, no need for a workaround.

released in 5.4 version.


Create new issue templates for bug and features

We can add more focused issue templates instead of one single one for bugs and features.

@youdz I've created a separate 'contribution proposal' from the 'feature request'. thoughts?


Changed workflow image config to relative paths, added scripts for do…

…wnload of file and creation of rawfileparser singularity image.

workflow/mzqc-implementationcases-local.yml got removed because we removed the nextflow bits. Can you easily update?


Spreadsheet input values validation - back into UI?

I think in the process of designing the UI, we lost the original validation steps. E.g., checking that seasonality added to 1, that growth rates weren't extraordinary, etc. Can we bring that back as a step in the UI validation process?

@BHagedorn-IDM
I think we previously discuss not to show all the detailed validation report because UI users are not savvy about the data validation process but let's discuss what plots that we would like to bring back and add them

the validation report is not available in step 2


Timer state doesn't change when it is started [Salesforce]

OS version: macOS Monterey
Browser version: Chrome Version 97.0.4692.99 (Official Build) (x86_64) ; Firefox 96.0.2 (64-bit)
Extension version: 2.0.1

Relevant integration (if any):
Salesforce lightning: ..lightning.force.com
🐛 Describe the bug
When starting the timer in track extension on Salesforce Lightening page, the timer starts, but button remains blue and with text "Start timer", as if it hasn't really been started:

Expected behaviour
Button turns green, with text 'Stop timer':

Steps to reproduce

Click 'Start timer'
Timer starts, popup opens, add details, close popup
--> button stays blue with text 'Start timer'

This also happens with Firefox extension for JIRA and Gitlab integrations.
Workaround: click on extension button. Once menu is shown, the state (both button and page) is updated.


Flatten versioned .so.x.y.z files so they can be included in an apk

The termux library dependencies include various shared object files that utilize the convention of having the base .so link to a version-suffixed file name. This works fine when running command-line executables on an Android device, but embedding the files in an Android apk will fail, both because the Android Gradle Plugin and the ART ignore everything not matching "lib*.so" in the .apk file's JNI libraries.
The error will look something like this when using a native Swift library that uses FoundationNetworking:
java.lang.UnsatisfiedLinkError: dlopen failed: library "libz.so.1" not found: needed by /data/app/~~W13d9DU_6Dw1D9JyCFe4Qg==/skip.droid.app-WSsoFlAqxhPx6In_xOnoGg==/base.apk!/lib/arm64-v8a/libcurl.so in namespace clns-6
    at java.lang.Runtime.loadLibrary0(Runtime.java:1082)
    at java.lang.Runtime.loadLibrary0(Runtime.java:1003)
    at java.lang.System.loadLibrary(System.java:1661)
    at skip.droid.AndroidAppMain.onCreate(Main.kt:78)
    at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1316)
    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6998)
    at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2236)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:205)
    at android.os.Looper.loop(Looper.java:294)
    at android.app.ActivityThread.main(ActivityThread.java:8177)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)

This solution walks through each of the termux libraries and identifies which ones are version-suffixed, and moves them to the non-version suffixed base name. It also uses patchelf to update the soname for the renamed files, as well as update the needed sections for any peer libraries so they point to the correct names.
For more information and other approaches, see https://stackoverflow.com/questions/62450784/link-in-android-studio-with-shared-libraries-with-versioning and https://gist.github.com/Sotatek-TuyenLuu/2f89b2a6690989b0550ea7d409d4e9f3.

Thanks for fixing this. With my two suggestions above and once I push this through the CI to check the results, I think we can get this in.

Hmm, this cannot really be checked without getting #167 in first.

Alright, rebased and checking the results...

Thanks, this works well.


Date Picker (with Disabled Date Ranges) - disabled dates are not indicated to the user in Windows HCM with keyboard-only operation

In the ARIA Date Picker (with Disabled Date Ranges)/demo.htm example, color is used to "gray out" dates which are disabled, and they also have title="Disabled" and aria-disabled="true".
If I use IE's Accessibility Settings to "Ignore colors specified on webpages" (to simulate Windows High Contrast Mode), and then use keyboard-only access to open the Date Picker and move focus to a disabled date, the title tooltip is not displayed and the date is not visually different from other dates. The only difference is that it cannot be activated/selected.
I think there needs to be another visual indication that this date is not valid - that indication should not depend on CSS, ARIA or the title attribute tooltip for operation.
Thoughts?

It's an interesting idea, but extremely challenging to implement for what seems to be little in the way of gain for accessibility.
For example, if CSS can't be used to provide a visual difference between enabled versus disabled dates, and the only purpose is to convey this information visually for people who are not using CSS and who are not using a screen reader and who are not also using a mouse, then the JavaScript would need to be changed to first detect when CSS is disabled, then manually replace all disabled dates with something else such as a special character written directly into the DOM, or an image would have to be inserted programmatically into all of these dates instead.
If using the special character injection, it's not certain that the person would know what the symbol meant either, resulting in the same problem, and an injected image would not be scalable because it would require a server side dependency that could easily be forgotten when developers implement this widget within enterprise apps.
So it would take a huge amount of reengineering and bloat the code significantly to accomplish this, when it doesn't really address an accessibility issue exactly. E.G The user can still choose the date they wish, it simply won't do anything when Enter is pressed on a disabled date.
Hopefully this makes sense. Please let me know your thoughts. :)

Makes sense!


bump version in package.json to v2.27.11

release version v2.27.11

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


kafka binder should set autoCommitOnError to true on kafka listener container

When a kafka consumer throws an error, s-c-s retries 3 times then either discards the message (enableDlq = false) or publishes the message to error.. (enableDlq = true), but because the message listener container used has the default autoCommitOnError value of false, the consumer offset does not get updated, which causes the consumer to reprocess the message on restart, until another message is processed on the same topic successfully and the offset is updated past the failed message.
Given the consumer processing expectations here, the listener container autoCommitOnError should be set to true so that after retries, the offset will be updated.

See: http://stackoverflow.com/questions/37282045/spring-cloud-stream-kafka-error-handling

Thanks - this looks like an oversight. We should make this property configurable and set it to true by default.

Suggested fix is here: https://github.com/spring-cloud/spring-cloud-stream/issues/550.
Basically by default we will follow the state of enableDlq - if DLQ is enabled, then we will always autocommit, if there is no DLQ, then we autocommit only on success. Then autocommitOnError can also be enabled/disabled explicitly.

I didn't put it in this issue, but the referenced stackoverflow question describes some weird behavior that I think will still be present if the user doesn't use enableDlq. If the consumer throws an exception for the initial call and all 3 retries, and the message is not committed, the message doesn't get processed again immediately (at least with my configuration where I had 3 partitions and a single consumer group with concurrency set to 3). On restart the message will be reprocessed, unless another message on the same partition is successfully processed, which commits and sets the consumer offset past the failed message.  Is this how it's expected to work?

@gadams00 Yes, but that behaviour can be now disabled explicitly (or disabled by default false if that is too confusing). The intent is to help with the specific case when a partition starts throwing errors consistently and all the messages since the last successful one would need to be replayed on restart. If the errors are sporadic then the listener will make progress as they handle successful messages.

That sounds good.

@gadams00 Thanks for the feedback. Just to clarify - any objections on the current approach of following the state of enableDlq ?

No objection.
I think it makes sense. If you need reliable messaging, set enableDlq to true and the consumer will always commit, either resulting in successful consumer processing, or a message on the dlq. If you don't need reliable messaging, set enableDlq to false (the default), and when there's a bug in the consumer, you'll be able to fix that and all failed messages since the last success will be reprocessed on restart. For the "poison message" case (where the problem is with the message content and not a consumer bug, resulting in sporadic consumer success and failure), the failed messages will be discarded once the consumer processes another message successfully. If that's not acceptable for some use case where enableDlq is false, users can set autoCommitOnError to true in kafka consumer properties, but that's potentially a dangerous thing to do, since a bug in the consumer would result in all messages being lost until the bug is corrected, hence the default of autoCommitOnError to false when enableDlq is false.
Does that match the intent?

Yes, that's summarizing it quite well. The only thing to add is that even in worst case scenarios full replay is always available via the resetOffsets/startOffset consumer properties (but that could be fairly inconvenient if a lot of data is retained).

Is there any properties which stops 3 retires in case of error in consumer? I want to make sure each message is consumed only once irrespective of error. enableDLQ sends the message to error topic, but still consumer the message thrice.

@HariharanThirumeni - see the documentation for consumer properties.
maxAttempts
If processing fails, the number of attempts to process the message (including the first). Set to 1 to disable retry.
Default: 3.

What if there is a bug on the producer side? Do we have an option like enableDlq for the producer side as well or should we use a try-catch block and handle the error explicitly?  @gadams00

@garyrussell  I i produce messages and i don't want to use a dead letter queue, i want to retry every 10 seconds and max 3 times (and if finally want to handle the exception (timeout, whatever) in case was not (auto commited by the consumer) received successfully - how can i do that? IM my case especially the error is already n the connection producer to broker (not up or to slow).

@cforce Please don't ask questions on old, closed, issues. In any case, GitHub issues are not for asking questions. Ask question on Stack Overflow, tagged with spring-cloud-stream.


chore(release) : cutting release v0.8.3

Description:
This PR cuts release v0.8.3
[X] I have cherry-picked any changes

[X] I have made all of the following version and patch updates:

Updated the container image tag in charts/osm/values.yaml
Updated the chart and app version in charts/osm/Chart.yaml
Updated the default osm-controller image tag in osm cli
Updated the image tags used in the demo manifests
Regenerated the Helm chart README.md

[X] I have checked that the base branch for this PR is correct as defined by the release guide

Codecov Report

Merging #3203 (55280d4) into release-v0.8 (4da887b) will increase coverage by 0.08%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-v0.8    #3203      +/-   ##
================================================
+ Coverage         64.80%   64.88%   +0.08%
================================================
  Files               153      153
  Lines              6949     6949
================================================
+ Hits               4503     4509       +6
+ Misses             2431     2425       -6
  Partials             15       15

Flag
Coverage Δ

unittests
64.88% <ø> (+0.08%)
:arrow_up:

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

Impacted Files
Coverage Δ

cmd/cli/install.go
65.62% <ø> (ø)

pkg/endpoint/providers/kube/client.go
79.00% <0.00%> (+1.00%)
:arrow_up:

pkg/configurator/validating_webhook.go
80.00% <0.00%> (+3.44%)
:arrow_up:

Continue to review full report at Codecov.

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


Start player from specific time

Hey, Great work!
How can I make the player start from a specific time?
Thanks =)

See https://github.com/CookPete/react-player/issues/115, although the config example is outdated:
<ReactPlayer
  url='https://youtu.be/qv6UVOQ0F44'
  config={{
    youtube: {
      playerVars: {
        start: 33
      }
    }
  }}
/>

Thank you!

No problem!

how can i write the config for  a normal file?

how can i write the config for a normal file?

I am wondering about this too. Tried a couple of ways, for example seeking when onReady, but the player just resets played to zero.

for me as well, how I can set a starting time? seeking onStart and onReady will be start from 0 once is loaded
Thanks

I've found a solution that may help someone using media fragment
Media Fragments
Adding a media fragment to the media URL, you can specify the exact portion you want to play. To add a media fragment, you simply add #t=[start_time][,end_time] to the media URL
<ReactPlayer
ref={this.ref}
url={${source}#t=${this.state.duration * this.props.played}}
/>
I'm passing played as prop to the player component, that I retrieve from the db stored

how can i write the config for a normal file?

I am wondering about this too. Tried a couple of ways, for example seeking when onReady, but the player just resets played to zero.

I've found a solution that may help someone using media fragment
Media Fragments
Adding a media fragment to the media URL, you can specify the exact portion you want to play. To add a media fragment, you simply add #t=[start_time][,end_time] to the media URL
<ReactPlayer
ref={this.ref}
url={${source}#t=${this.state.duration * this.props.played}}
/>
I'm passing played as prop to the player component, that I retrieve from the db stored

hey,

hey,
what is the configuration to start the video at a specific time on Vimeo?


The attribute filter does not work if it contains an asterisk in the path

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.4.3
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
example
.\azcopy.exe copy "D:\dummy\2020*" "SAS" --include-attributes A --recursive --overwrite ifSourceNewer --log-level ERROR
.\azcopy.exe copy "D:\dummy\2019*" "SAS" --include-attributes A --recursive --overwrite ifSourceNewer --log-level ERROR
.\azcopy.exe copy "D:\dummy\2018*" "SAS" --include-attributes A --recursive --overwrite ifSourceNewer --log-level ERROR
-There are many files under the D:\dummy\YYYYMMDD format folder.
-Details are given below
-- Transfer the last 5 years of data to Azure
-- I want to transfer only files with the archive attribute
-- Clear archive attributes after transfer
What problem was encountered?
When the above command was executed, the following alert occurred.
INFO: Skipping file attribute filter for file 20200105/50004512-00340967/dummy-001.jpg due to error: The filename, directory name, or volume label syntax is incorrect.
INFO: Skipping file attribute filter for file 20200105/50004512-00340967/dummy-002.jpg due to error: The filename, directory name, or volume label syntax is incorrect.
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
No error occurs if you do not use an asterisk in the source path
example:
"D:\dummy*"

Sorry.
Some statements were incorrect.

Have you found a mitigation/solution?
No error occurs if you do not use an asterisk in the source path
example:
"D:\dummy*"

Correct
example:
"D:\dummy\*"

Thank you for your support!
I will test it.

Issue has been in v10.5.0
Please reach out to me if the issue persists.


Hai sir  i am unable to get   NEXTAUTH_URL=

Hi sir from where will i get these keys
NEXTAUTH_URL=
NEXTAUTH_SECRE=
NEXT_PUBLIC_API_URL=

Hi, usually there should be comments explaining this, but I have missed that for this project.
NEXTAUTH_URL should be http:\\localhost:3000,
NEXTAUTH_SECRET is whethever, for example my-secret-key,
NEXT_PUBLIC_API_URL should be http:\\localhost:3000\api.
I am going based on memory right now, but this should be right.


Trained models is not exist

Ttrained models from BaiduYun(code: n0ev), seem not exists

It seems that BaiduYun is only avaliable in China Mainland.
Please wait, I would upload models on dropbox later.

@lui-shex Google drive link has been updated. Plz check.


Fix the issue that external account cannot start sagemaker workspace

Issue #, if available:
Description of changes:
This issue should be caused by global repo change from v5.11 to v5.20
Checklist:

[ yes] Have you successfully deployed to an AWS account with your changes?
[ yes] Have you successfully deployed to an AWS China account with your changes?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully tested with your changes locally?
[ ] If new dependencies have been added, have they been pinned to specific versions?
[ ] Is this change also required on the AWS Solution version?
[ ] Have you updated openapi.yaml if you made updates to API definition (including add, delete or update parameter and request data schema)?
[ ] If you had to run manual tests, have you considered automating those tests by adding them to end-to-end tests?
[ ] If you are updating the changelog and vending out a new release, have you updated versionNumber and versionDate in .defaults.yml

AS review ticket id:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #62 (4580497) into develop (4a82306) will increase coverage by 0.61%.
The diff coverage is n/a.

:exclamation: Current head 4580497 differs from pull request most recent head 5b40b54. Consider uploading reports for the commit 5b40b54 to get more accurate results

@@             Coverage Diff             @@
##           develop      #62      +/-   ##
===========================================
+ Coverage    51.89%   52.51%   +0.61%
===========================================
  Files          302      249      -53
  Lines        17169    14770    -2399
  Branches      2648     2390     -258
===========================================
- Hits          8910     7756    -1154
+ Misses        7263     6144    -1119
+ Partials       996      870     -126

Impacted Files
Coverage Δ

...check-launch-dependency/check-launch-dependency.js

lib/utils/get-item.js

lib/helpers/transforms.js

lib/utils/log-prefix.js

lib/steps/internal-auth-dep-check-service.js

lib/helpers/users.js

lib/steps/__tests__/__fixtures__/dynamodb.js

lib/data/key-pairs-transforms.js

lib/helpers/js-yaml-custom-schema.js

src/lambdas/egress-store-object-handler/handler.js

... and 43 more

Continue to review full report at Codecov.

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


error when install apex and compile normalSpeed

Hi all,
I create a conda .yml file and another requirements.txt for creating conda environment because I followed the tutorial of my administrator of GPU cluster to use conda install at first and only use pip when the packages are not available on conda.
However, I got some errors when I install apex as the following:

After that, I add apex into .yml file and install NormalSpeed but I got the same error as this issue.
Could you help me fix it?
These are my .yml and .txt files .

Best,
Min

For the apex installation problem please refer to the apex project, try to raise an issue or search for solutions in the past issues there.
For the NormalSpeed issue try to install opencv3 from the source code as mention in the issue.

For the apex installation problem please refer to the apex project, try to raise an issue or search for solutions in the past issues there.

Hi Yisheng,
Thank you for your reply.
I have already raised an issue and searched for solutions in the past issues for apex. Can I simply install apex by conda?
The problem of NormalSpeed disappeared automatically when I install apex by conda.

Sorry that I didn't try to install apex by conda. You can have a try, see if it works well, and update the issue.

Sorry that I didn't try to install apex by conda. You can have a try, see if it works well, and update the issue.

No it shows the same error - lack of cpp extension.
I tried to install the latest torch version and installed apex successfully.
conda install pytorch torchvision torchaudio cudatoolkit=10.2 -c pytorch
git clone https://github.com/NVIDIA/apex
cd apex
pip install -v --disable-pip-version-check --no-cache-dir --global-option="--cpp_ext" --global-option="--cuda_ext" ./

and then install other packages...


Update google-cloud-bigtable to 2.40.0

About this PR
📦 Updates com.google.cloud:google-cloud-bigtable from 2.5.3 to 2.40.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-bigtable" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-bigtable" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #323.


Files missing

Hi,it seems that there are no requirement.txt or the directory NCBCV in your project to install.

Thank you for letting me know. I will work on it this and next week.


Failed to install ${packageName} in ${cwd}

Version
create-nuxt-app/4.0.0 darwin-arm64 node-v16.14.2
Steps to reproduce

run yarn create nuxt-app test-project
.../yarn/global/node_modules/sao/lib/installPackages.js:108 throw new SAOError(Failed to install ${packageName} in ${cwd})

What is Expected?
Expect nuxt-app to be created successfully.
What is actually happening?
This issue is still occurring for me. I'm using an Apple M1 Max laptop (maybe that has something to do with it for me)
I've tried this with yarn, npm and npx and all result in the same issue. I have the LTS version of node.js installed (16.14.2 as of today) and I have updated and cleaned up all of my global npm modules:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
When I run yarn create nuxt-app test-project I end up with the following:
yarn create v1.22.15
warning package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - create-nuxt-app
[#####################################################################] 342/342
create-nuxt-app v4.0.0
✨  Generating Nuxt.js project in test-project
? Project name: test-project
? Programming language: JavaScript
? Package manager: Yarn
? UI framework: Tailwind CSS
? Nuxt.js modules: Axios - Promise based HTTP client, Progressive Web App (PWA),
 Content - Git-based headless CMS
? Linting tools: ESLint, Prettier
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: jsconfig.json (Recommended for VS Code if you're not using
typescript)
? Continuous integration: None
? Version control system: Git
warning ../../../package.json: No license field
warning ../../../package.json: No license field
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware ><EMAIL_ADDRESS>The q
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware ><EMAIL_ADDRESS>The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser ><EMAIL_ADDRESS>flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware ><EMAIL_ADDRESS>The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser ><EMAIL_ADDRESS>flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning ../../../package.json: No license field
warning @nuxt/content > @nuxt/types > @types/webpack ><EMAIL_ADDRESS>Th
is is a stub types definition. anymatch provides its own type definitions, so yo
u do not need this installed.
warning @nuxt/content > @nuxt/types > @types/autoprefixer > @types/browserslist@
4.15.0: This is a stub types definition. browserslist provides its own type defi
nitions, so you do not need this installed.
warning @nuxtjs/pwa ><EMAIL_ADDRESS>wrong release
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longe
r maintained and not recommended for usage due to the number of issues. Because
of the V8 engine whims, feature detection in old core-js versions could cause a
slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependen
cies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack-hot-middleware ><EMAIL_ADDRESS>The q
uerystring API is considered Legacy. new code should use the URLSearchParams API
 instead.
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url > querystring@0
.2.0: The querystring API is considered Legacy. new code should use the URLSearc
hParams API instead.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to c
hokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > choki
dar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using ins
ecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo >
<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-not
ation > postcss-values-parser ><EMAIL_ADDRESS>flatten is deprecated in favor of
 utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#depre
cated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-re
solve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning vue-jest > babel-plugin-transform-es2015-modules-commonjs > babel-runtim
e ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature dete
ction in old core-js versions could cause a slowdown up to 100x even if nothing
is polyfilled. Please, upgrade your dependencies to the actual version of core-j
s.
warning vue-jest > extract-from-css > css ><EMAIL_ADDRESS>See https:
//github.com/lydell/source-map-resolve#deprecated
warning vue-jest > extract-from-css > css ><EMAIL_ADDRESS>Please see https://githu
b.com/lydell/urix#deprecated
warning "nuxt ><EMAIL_ADDRESS>has unmet peer dependency "consola@*".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@
>=7.11.0".
warning "@nuxtjs/eslint-config ><EMAIL_ADDRESS>has incorrect peer
 dependency<EMAIL_ADDRESS>warning "@nuxtjs/eslint-config ><EMAIL_ADDRESS>has incorrect pe
er dependency<EMAIL_ADDRESS>warning "@nuxtjs/eslint-config > eslint-plugin-jest > @typescript-eslint/experim
ental-utils > @typescript-eslint/utils > @typescript-eslint/typescript-estree >
<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| >= 3.2.0-dev ||
 >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta |
| >= 3.7.0-dev || >= 3.7.0-beta".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@^7
.0.0-0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "babel-jest ><EMAIL_ADDRESS>has unmet peer dependency "@babe
<EMAIL_ADDRESS>warning "babel-jest > babel-preset-jest ><EMAIL_ADDRESS>" has unmet peer dependency "<EMAIL_ADDRESS>warning "babel-jest > babel-preset-jest > babel-preset-current-node-syntax > @ba
<EMAIL_ADDRESS>has unmet peer dependency "@babel/core@^7.
0.0-0".
warning "babel-jest > babel-preset-jest > babel-preset-current-node-syntax > @ba
<EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>.
error /Users/quantumdynamix/QD Shares/Git Shares/test-project/node_modules/deasy
nc: Command failed.
 System Darwin 21.4.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_mod
ules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/quantumdynamix/QD Shares/Git Shares/test-project/node_module
s/deasync
gyp ERR! node -v v16.14.2
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok
Build failed

yarn install v1.22.15
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this
command.

/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in /Users/quantumdynamix/QD Shares/Git Shares/test-project
    at ChildProcess.<anonymous> (/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108:15)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  __sao: true
}
error Command failed.
Exit code: 1
Command: /usr/local/bin/create-nuxt-app
Arguments: test-project
Directory: /Users/quantumdynamix/QD Shares/Git Shares
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.```

Is anyone monitoring these issues? I don't think this is user error and it feels like a pretty critical issue to leave unresolved. Any feedback of any kid would be helpful.

Still having problems with this. I tried upgrading Node.js to 17, and it still happens.
create-nuxt-app v4.0.0
✨  Generating Nuxt.js project in test-project
? Project name: test-project
? Programming language: JavaScript
? Package manager: Npm
? UI framework: Tailwind CSS
? Nuxt.js modules: Axios - Promise based HTTP client, Progressive Web App (PWA),
 Content - Git-based headless CMS
? Linting tools: ESLint, Prettier
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: jsconfig.json (Recommended for VS Code if you're not using
typescript)
? Continuous integration: None
?  Upgrad
e to v2.x.x.
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. anym
atch provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition.
 browserslist provides its own type definitions, so you do not need this install
ed.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and coul
d be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates
 since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not
 recommended for usage due to the number of issues. Because of the V8 engine whi
ms, feature detection in old core-js versions could cause a slowdown up to 100x
even if nothing is polyfilled. Please, upgrade your dependencies to the actual v
ersion of core-js.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not
 recommended for usage due to the number of issues. Because of the V8 engine whi
ms, feature detection in old core-js versions could cause a slowdown up to 100x
even if nothing is polyfilled. Please, upgrade your dependencies to the actual v
ersion of core-js.
npm ERR! code 1
npm ERR! path /Users/quantumdynamix/QD Shares/Git Shares/test-project/no
de_modules/deasync
npm ERR! command failed
npm ERR! command sh -c node ./build.js
npm ERR!  System Darwin 21.4.0
npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm
/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /Users/quantumdynamix/QD Shares/Git Shares/pci-auctions-ph
ase-3/node_modules/deasync
npm ERR! gyp ERR! node -v v17.8.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed

npm ERR!      /Users/quantumdynamix/.npm/_logs/2022-04-07T14_43_55_125Z-debug-0.l
og

/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in /Users/quantumdynamix/QD Shares/Git Shares/test-project
    at ChildProcess.<anonymous> (/Users/quantumdynamix/.config/yarn/global/node_modules/sao/lib/installPackages.js:108:15)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1090:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:527:28)
    at Pipe.<anonymous> (node:net:709:12) {
  __sao: true
}

Node.js v17.8.0

yup i'm getting the same error on node 18
C:\Users\Lemon Rose\Desktop>npx create-nuxt-app melon-nuxt

create-nuxt-app v4.0.0
✨  Generating Nuxt.js project in melon-nuxt
? Project name: melon-nuxt
? Programming language: JavaScript
? Package manager: Yarn
? UI framework: Tailwind CSS
? Nuxt.js modules: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Linting tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Testing framework: None
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Static (Static/Jamstack hosting)
? Development tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? What is your GitHub username? japandotorg
? Version control system: Git
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cau
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cau
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cau
se a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade yo
ur dependencies to the actual version of core-js.
warning nuxt > @nuxt/babel-preset-app ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for
 usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cau
se a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade yo
ur dependencies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 does not receive
security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > chokidar ><EMAIL_ADDRESS>fsevents 1 will
break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo ><EMAIL_ADDRESS>This SVGO version is no lo
nger supported. Upgrade to v2.x.x.
warning nuxt > @nuxt/webpack > postcss-preset-env > postcss-color-functional-notation > postcss-values-parser > flatten
@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon ><EMAIL_ADDRESS>See https://github.com/lyd
ell/source-map-resolve#deprecated
warning nuxt > @nuxt/webpack > webpack > node-libs-browser > url ><EMAIL_ADDRESS>The querystring API is considered
 Legacy. new code should use the URLSearchParams API instead.
warning nuxt > @nuxt/webpack > cssnano > cssnano-preset-default > postcss-svgo > svgo ><EMAIL_ADDRESS>Modern JS already
 guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://d
eveloper.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://gith
ub.com/lydell/resolve-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>See https
://github.com/lydell/source-map-url#deprecated
warning nuxt > @nuxt/webpack > webpack > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://
github.com/lydell/urix#deprecated
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "12 - 16". Got "18.7.
0"
error Found incompatible module.

yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\lib\installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in C:\Users\Lemon Rose\Desktop\melon-nuxt
    at ChildProcess.<anonymous> (C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\lib\installPackages.js:108:15)
    at ChildProcess.emit (node:events:513:28)
    at cp.emit (C:\Users\Lemon Rose\AppData\Local\npm-cache\_npx\ea7c6e7510ea3309\node_modules\sao\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  __sao: true
}

Node.js v18.7.0


Add "generator invariants"

Transferred from http://code.google.com/p/scalacheck/issues/detail?id=85
Make it possible to attach preconditions/invariants to generators so you don't have to add a precondition to the property also.
See http://groups.google.com/group/scalacheck/msg/b563f24c81b22291

I stumbled over this issue today, and it took forever to figure out what was going wrong!
Fortunately I enjoy this kind of detective work.
And I think I have a suggestion for an easier fix... But first let me try to add some clarity to what the problem is.
Some apps use collections of a fixed size. For example, an Array of exactly 3 Doubles to represent a coordinate in space. And these apps want to test their methods that use such collections, and in that example Gen.containerOfNArray,Double seems like an obvious choice.
The funny thing is that when the method being tested is actually correct that Gen works perfectly.
But things go horribly wrong when an app's methods are actually failing. The shrinker mistakenly tries to chop down the size of the collection, but the app is going to reject those collections because they are too short: e.g. obviously an Array of length less than 3 isn't an acceptable coordinate.
But the shrinker thinks it has found a simplified input that causes the problem, so the error reported to the user is "when you call this method with a collection that isn't of the correct size it fails". Well, that's not news to the programmer, and it leads to the incorrect conclusion that the custom Gen isn't producing what it ought to, which makes absolutely zero sense because you can sample the Gen and see that it is!
Also note that an app method may take two parameters, one expecting a fixed-length collection, and the other a variable-length (and therefore shrinkable) collection.
So, here's my suggestion:

Add "def shrinkable = true" to Gen with a doc comment to describe the above scenario.

Clone Gen.containerOfN and give it a name like shrinkableOfN, possibly make it private but fix the doc comment to say the size is "at most n" , and have containerOf and containerOf1 delegate to shrinkableofN

Make the result of Gen.containerOfN "override def shrinkable = false" (so it can live up to the promise given in its doc comment)

Teach the shrinker code to leave any Gen that isn't shrinkable alone (i.e. somewhere near line 542 of Prop.scala)

Now, in my scanning of the code I might have missed other Gen instances that might also need to override shrinkable, but even reading thru the previous complaints about this issue didn't reveal any others.
Thanks for the time you spend on this project! Hope this helps!

Oops: markdown takes precedence over scala syntax: please forgive my stupid link to nowhere!

... in most cases you would still want the values inside the array to be minimized, but that wouldn't happen if you marked the array as "unshrinkable".

Well, that depends on the change to the shrinker behavior (i.e. "near line 542 of Prop.scala")... There is no reason it couldn't leave the unshrinkable container unshrunk and still recurse into the elements of said container to attempt to shrink them, right?
Isn't this what happens with Gen.resultOf currently? Those functions are essentially containers of fixed size, and so the shrinker would never imagine turning a 3-ary into a 2- or 1- or 0-ary function. But the arguments are eligible for shrinking... Or at least I assume they are (I only started learning Scalacheck this week, and I haven't had time to grok the shrinker code).
If my assumption is correct, then you have already implemented the necessary idea and all you need to do is have it apply to the container generators. And if my assumption is incorrect, then there's a bug in the shrinker code that handles functions.
I wish I had time to spend learning the shrinker code so I could be more specific, but I'm really swamped with another project at the moment.

Hmm... in fact I think we've stumbled across an alternative description of the problem:
Gen.containerOfN[Array,Double](3,Gen.choose(-1000d,1000d))

should behave exactly the same as
Gen.resultOf( (x:Double,y:Double,z:Double)=>Array(x,y,z) )( somethin,somethin,somethin )

The latter can be a workaround, but only for containers of size less than ten, and there's probably something tricky about getting the implicits right.

Gen.resultOf does not generate functions, it generates results. In your example above, the type of both your expressions will be Gen[Array[Double]], that is they will both be generators that produces random array of doubles. To the shrinker, they are equal. The shrinker will just try to shrink the produced arrays. The difference is that, for Gen.resultOf, you have no control over which values are fed to the function. ScalaCheck will just use arbitrary[Double] for the inputs.
I'm not saying that it is impossible to implement "def shrinkable", but at least for the shrinker, I just don't think it is simpler to implement that than full-blown generator preconditions (or rather, postconditions, from the generator's point of view).

the type of both your expressions will be Gen[Array[Double]], that is they will both be generators that produces random array of doubles. To the shrinker, they are equal. The shrinker will just try to shrink the produced arrays.

Ah, I see: I really should have learned more about how the shrinker works...

I just don't think it is simpler to implement that than full-blown generator preconditions

I assumed a Boolean flag would be the easiest thing to implement (it so often is), but you would know better than anyone, naturally. It's disappointing when things that sound easy turn out not to be, yes?
Thanks again for the time you put into ScalaCheck: it is a very cool tool!

I accidentally closed this issue earlier, reopening it now.
@JHeiner: I'm very happy for your feedback, it's interesting to hear how ScalaCheck is used by "real" users. You gave me some ideas on how to add preconditions automatically to for example containerOfN. I think I will be able to come up with a solution that is close to what you proposed, although more general. To make it work together with the shrinker, I think the "generator" and "property" concepts must be kind of merged. I actually feel that I have built up enough motivation to actually start implementing this soon :) Thanks for that!

I tried to get a grip on this by adding a canGenerate(t: T): Boolean method on Gen. Then the idea would have been to pass the T => Boolean verifier to the Shrink instances for filtering, possibly via forAllShrink.
But then quickly realized that Gen is covariant in T, which renders my efforts useless. What do you think a feasible approach would be?

You can get around that specific problem by defining canGenerate like this: def canGenerate[U >: T](t: U): Boolean.
My latest thought on this issue has been to merge Prop and Gen by making Prop = Gen[Prop.Result]. That would probably make it easy to handle everything as preconditions. It would also make the implementation a bit cleaner, and maybe I could kill the few ugly mutable vars in both Prop and Gen along the way. However, that change is a bit invasive, and I haven't had time to experiment with it yet.
A canGenerate method that is checked each time shrinking is applied might be a simpler way, and maybe that is a better idea. However, since Shrink today is totally unaware of Gen, you either have to introduce the dual relation (which sounds like an attractive concept), or do the check in forAllShrink and other relevant places. If you come up with some code, I'd be happy to look at it.

Thank you - I was aware of the bound trick, but felt that downcasting the received U to T is a bit dirty (still feel it). Should work given the semantic constraints nevertheless.
You can check out https://github.com/robinp/scalacheck/tree/fenced-shrink, a good place to start is the ShrinkGuardSpecification. Its properties all fail, the interesting thing is that the returned evidence respects the Gen guards. Except for mapped Generators, since we would need a bijection to unmap and verify the values.
object Gen.apply now takes an optional T => Boolean. I added a sample bimap method on˛Gen, and as an example added fencing by default to some variants of choose (the Int variant now uses bimap to get back to the Long variant), suchThat, and listOfN.
Only the T1 => P variant of forAll transforms the shrinker to use the guard yet.
Results more or less satisfy me, however passing down the guard functions may be a bit cumbersome. Also it is worth thinking if a different design is possible to scale better. Polluting the Buildable also seems a bit rude, etc. What do you think?


deleting a rule leaves the cursor in the wrong place

reproducible - happens only when many rows disappear at once.  Need to check if cursor is on button - if not, then reset to initial position.


Use xnbd-client-static

Link: https://github.com/aimxhaisse/xnbd-client-static/blob/dist/bin/xnbd-client-static

we now use a static binary of xnbd-client and send it to /run/sbin of the target system

:ok_hand:


Illegal redefinition of parameter o when using lombok together with Eclipse null check annotation analysis

Migrated from Google Code (issue 753)

Same with Java 1.8.0_51 and Lombok 1.16.4.
@Data
public class FileImporter {

	@Nullable
	private List<String> fileEndings = new ArrayList<String>();
}

Error displayed on the @Data anntation (that adds the equals-method that is unconstrained in Object) is:

Illegal redefinition of parameter o, inherited method from Object does not constrain this parameter

A viable workaround for this error message would be (at least that's what we used to do in Java 1.7):
@Data
@EqualsAndHashCode(onParam = @__(@Nullable))
public class FileImporter {

	@Nullable
	private List<String> fileEndings = new ArrayList<String>();
}

This should add the the @Nullable annotation to the parameter of the equals-method generated by the @Data-annotation.
But it seems that the orX-method of Lombok doesn't work in Java 8 (tested with _25, _45 and _51) since the error message now is still(now on the @EqualsAndHashCode annotation instead of the @Data annotation):

Illegal redefinition of parameter o, inherited method from Object does not constrain this parameter

Implying that the @Nullable annotation hasn't been added to the equals-method.
When we switch to 1.7 this second error vanishes and everything works like expected.

Same problem with this code, using Lombok 1.16.10, Java 1.7, Eclipse 4.6.1:
@Value
@org.eclipse.jdt.annotation.NonNullByDefault
public class Entity {

    String name;
    String code;

}

Note that adding @EqualsAndHashCode(onParam = @__(@Nullable)) on the class removes the compilation error. However, it seems strange to me to have to add a @Nullable annotation when you wan't non-null fields.

We should scan for @NNBD annotation on the class and always generate @Nullable on the equals arg. I don't think that needs to be configurable; if you put NNBD on there, you gotta do it, right?
We should optimally also manually parse package-info.java in the same dir as your source file and check if you have @NNBD in there, and also do it. We already scan dirs (for lombok.config) so we should be able to do this. If you have split packages (the same package in another source root that has a package-info.java with @NNBD: We can't really cater to that one.
We need to code into the system the following:
If the enclosing class has an annotation of type org.eclipse.jdt.annotation.NonNullByDefault:
check if it has no arguments, or, alternatively, DefaultLocation.PARAMETER is in there. If no, we're done. If yes, add the appropriate annotation.
If the enclosing class did not have the annotation, check if the package-info.java file in the same dir has it. Do the same routine for it.
The appropriate annotation is org.eclipse.jdt.annotation.Nullable.
Secondly, if class or package has javax.annotation.ParametersAreNonnullByDefault annotation, then apply annotation javax.annotation.Nullable to the argument.
Anyone know of any other annotations in this vein?

There are the (now deprecated in lieu of javax.annotation) FindBug annotations:
edu.umd.cs.findbugs.annotations.NonNull
edu.umd.cs.findbugs.annotations.Nullable

Before we fix this, we should also fix NNBD effects elsewhere. Specifically:

I think @RequiredArgsConstructor ought to consider all not-@Nullable fields as 'required', assuming that, in the eclipse case, the argslist is empty or includes DefaultLocation.FIELD.
I do not think it is a good idea to generate null checks everywhere; lombok already decided not to do that unless you use lombok's own @NonNull annotation (whereas @RequiredArgsConstructor treats a number of well known non-null annotations as relevant), and I bet some misguided linters will start whining about the null check we gen with an error along the lines of 'paramName can't be null here'.
I do not think it is a good idea to introduce lombok's own @NonNullByDefault annotation.

Thus, the 2 fixes to apply to address this issue would be:

Generate the appropriate @Nullable on the param of the generated equals method, based on checking both the class and the package-info.java file (and this involves writing a parser for package-info.java, so not quite trivial, but doable), and
using the same mechanism to discover a relevant @NNBD annotation, change definition of whether a field is 'required' or not for @RequiredArgsContructor.

@Gaibne: I don't think those are relevant here; is there a NonNullByDefault annotation in findbugs's annotationset which implies @NonNull on all parameters? I don't think there is, in which case, it's not relevant for this issue.

There is, also deprecated:
@edu.umd.cs.findbugs.annotations.DefaultAnnotation(NonNull.class)

So for that one, the rule is: NonNull needs to be part of the argslist. If so, generate e.u.c.f.a.Nullable.

Additional complication: there are now 4 places you can stick an annotation on an equals method: On the method, on the method's return type, on the parameter, and on the type holding the parameter. eclipse's @Nullable MUST appear in the 'on the type holding the parameter' position or it does not work, and lombok can't yet do that. It looks like: java.lang. @org.eclipse.jdt.annotation.Nullable Object.
So, we need to generate the @Nullable there, but this only works in J8+. Can we assume that lombok users have that at this point? Possibly yes if people are fancy enough to use @NNBD.
We also need to make a separate bug/enhancement to add onParamType for @EqAHC and @Setter.

I hope it's not poor form for me to bump this ? Just ran into it again and after googling ended up here, reading my own comments :D
I think two years later we can definitely assume J8+.

I'm going to go for an intermediate solution: I'm not going to write code to do a scan for package-info, that's quite complicated, but I will scan for both common variants of org.eclipse.jdt.annotation.NonNullByDefault (javax.annotation and eclipse's), and if present, add the nullable annotation to the param of the generated equals, in the right place (on the 'type', not the param).


Error creating blob: Parse exception converting JSON to object:

Trying to use this for the first time....
My POM is a little non-standard.  I have a profile named "site" which is bound to the "prepare-package" phase of the Maven build lifecycle.  This generates the site fine.  Then I have another profile i named "site-deploy-try" which is bound to the "verify" phase of the Maven build lifecycle and has the configuration of the github-site-plugin.  I then execute with mvn -Psite,site-deploy-try clean verify
In theory it should work but getting the following error.
--- site-maven-plugin:0.9:site (default) @ ferris-tweial ---
Creating 617 blobs
BUILD FAILURE
Total time: 54.370s
Finished at: Fri Oct 16 16:28:34 CDT 2015
Final Memory: 36M/87M
Failed to execute goal com.github.github:site-maven-plugin:0.9:site (default) on project ferris-tweial: Error creating blob: Parse exception converting JSON to object: java.io.IOException: Premature EOF -> [Help 1]
Any thoughts.

You probably got hit by the rate limiting or a different API change, try with a current release of the plugin.

Thank you for the suggestion.  I will try again with 0.12

@mjremijan were you able to overcome this issue? I've just hit the same problem.


Page not found handler not working in 0.4.0

Steps to reproduce:

clone the repository;
run npm install;
run grunt;
load an URL for which there's no route, e.g. http://localhost:3000/abcdefghijklmnopqrstuvwxyz (why not ;) )

Expected result:

a 404 status code and a redirection to http://localhost:3000/not-found , displaying an error message.

Actual result:

a 200 status code and a redirection to http://localhost:3000 , effectively displaying the root page.

If I remove the "*" from the last route of modules/core/server/routes/core.server.routes.js, the 404 functionality is restored; however, sign up, sign in and pretty much everything else is broken, because of the fallback to the error routes defined in config/lib/express.js. I haven't yet found what the correct fix is.
I noticed the issue on my own testing application, when the server not only produced a 200 status code, but also the HTML content of the root page, when requested an image which wasn't there.

in case we want to keep the redirect to / where it might make sense we could just add this to core.server.routes.js:
// Return a 404 for all undefined api, module or lib routes
app.route('/:url(api|modules|lib)/*').get(core.renderNotFound);

in case we want a 404 for every undefined route we should define the root rout explicitly, by removing the * and our error routes kick in and do the rest for us:
// Define application route
app.route('/').get(core.renderIndex);

Since we are using html5-mode routes, anguler is responsible for showing 404 pages for most routes, right?
so guess we should handle the server side 404s like this:
// Return a 404 for all undefined api, module or lib routes
app.route('/:url(api|modules|lib)/*').get(core.renderNotFound);

and either keep the redirect for everything else or implement angular based 404 logic as well.

I assume we can close this now that we merged #566 ?

I've verified this is working after merging #566. The app is responding with the not-found route on the front-end, when a non existing route is requested.

Verified. Let's close.


No overload matches this call

Hello there,
I'm not very skilled in using classes and types, so I'm quite learning.
Currently with latest nuxt and nuxt-supabase modules.
I'm trying to setup basic stuff and I can't fix a TS error with this code :
export class Chapter {
  id: string;
  text: string;

  constructor(id: string, text: string) {
    this.id = id;
    this.text = text;
  }

  async insert() {
    const supabase = useSupabaseClient()
    const res = await supabase
    .from('chapters')
    .insert({
      text: this.text
    })
  }
}

I have the following TS "error" :

Everything works fine and the chapter is eventually created in the database, but I don't know how I can fix the warning.
Any help ?
Thanks !

Same here (

It works like a charm. Thanks a lot !!!


Skipped describe block is run

🐛 Bug Report

To Reproduce
Steps to reproduce the behavior:

Run the tests below:

describe.skip('a', () => {
    console.log('run a')
    test('1', () => expect(0).toBe(0))
})

describe('b', () => {
    it('2', () => expect(0).toBe(0))
})

Expected behavior

Short version: I expect run a not be logged in output.
Long version:
In my real test cases, I initialize a variable above all tests in the describe block a. This variable is initialized by instantiating a class that ultimately runs a function for caching instances of another class.
This caching function is also involved in the test cases in the describe block b, and they are failing if the variable in the head of the describe block a is not removed.
I tested with several previous versions of Jest (as well as the current latest v26.6.2) and it seems that this behavior has always existed. I couldn't find an existing issue asking for the behavior I'm expecting. The current description in docs is:

You can use describe.skip if you do not want to run a particular describe block

If the behavior I'm expecting couldn't be implement, I think the current behavior should be explicited in the docs, at least.
Link to repl or repo (highly encouraged)

https://github.com/cdoublev/jest-issue
envinfo

  System:
    OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (1) x64 Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
    Memory: 1.05 GB / 1.95 GB
    Container: Yes
    Shell: 5.0.3 - /bin/bash
  Binaries:
    Node: 15.0.1 - /usr/bin/node
    npm: 7.0.3 - /usr/bin/npm
  Managers:
    Apt: <IP_ADDRESS> - /usr/bin/apt
    Composer: 2.0.1 - /usr/bin/composer
    RubyGems: <IP_ADDRESS> - /usr/bin/gem
  Utilities:
    Make: 4.2.1 - /usr/bin/make
    GCC: 8.3.0 - /usr/bin/gcc
    Git: 2.27.0 - /usr/bin/git
  IDEs:
    Nano: 3.2 - /usr/bin/nano
    Vim: 8.1 - /usr/bin/vim
  Languages:
    Bash: 5.0.3 - /usr/bin/bash
    Perl: 5.28.1 - /usr/bin/perl
    PHP: 7.3.19 - /usr/bin/php
    Python: 2.7.16 - /usr/bin/python
    Python3: 3.7.3 - /usr/bin/python3
    Ruby: 2.5.5 - /usr/bin/ruby
  Databases:
    MySQL: 10.3.25 (MariaDB) - /usr/bin/mysql

Yeah, wording is imprecise - we will run the describe, but we won't run any tests inside of it. If you have some setup that should be skipped within the describe, but it in beforeAll or beforeEach within the describe block.
Happy to take a PR specifying this in the docs 👍

Done. But I signed the CLA after my (first) PR, sorry. I'm still wondering why a describe.skip block needs to be run.

I'm still wondering why a describe.skip block needs to be run.

See

we can say test named a 1 is skipped

Essentially, we run all describes and execute their callback (recursively), and collect all tests defined within them. But if skipped, we don't execute the test's callback

Oups, got it, thank you. It looks like that I will now have to copy/paste my tests setup until #10451 is fixed.


nasher skips scripts with errors and stops compiling following scripts

How to reproduce

Get a demo.zip
Run nasher unpack --file:demo.mod
Run nasher compile
Go to .nasher/cache/default and you will see .ncs files only for _valid.nss, but there is no compiled files for valid1.nss and valid2.nss. Compilation stops after trying to compile notvalid.nss script.

I'm tried to compile not valid script inside nasher docker container and getting error as expected.
/usr/local/bin/nwnsc -n /nwn/data -o -i /nasher/.nasher/cache/default /nasher/.nasher/cache/default/notvalid.nss
Loading base game resources...

Home Path - ~/Documents/Neverwinter Nights/

Compiling: notvalid.nss
Illegal instruction

content of notvalid.nss
void main()
{
	AssignCommand(OBJECT_SELF, TRUE);
}

System: nwntools/nasher:latest under Windows 10.

In this case, nwnsc is crashing when it encounters the script, so none of the following scripts are compiled. Nasher's way of calling nwnsc and capturing its output is hacky and doesn't account for these crashes. I'll file an issue with the nwnsc repo, but I'll work on getting nasher to handle this better in the meantime.

Using 0.11.9 under Windows 10 Pro, I attempted to recreate the issue:
PS C:\Users\Ed\Desktop\Git Repositories\_nashertest> nasher unpack --file:demo.mod
 Git Branch: master
  Extracting demo.mod to C:\Users\Ed\Desktop\Git Repositories\_nashertest using target default
  Converting 18 new or updated files
PS C:\Users\Ed\Desktop\Git Repositories\_nashertest> nasher compile
 Git Branch: master
   Compiling target default
    Updating cache for target default
   Compiling 4 scripts
             Home Path - C
      Error: notvalid.nss(3)
         ... NSC1002
         ... Type mismatch in parameter 2 ("aActionToAssign") in call to "AssignCommand"
         ... Expected type "action", but got type "int"
    Warning: Errors encountered during compilation (see above)
    Success: compiled 4 scripts

Looking at the cache, I have .ncs files for _valid, valid1, and valid2, but none for notvalid, as expected.  Issue may have been resolved with the updated nwnsc (this example using nwnsc 1.1.2).  Recommend closure unless it can be reproduced in a different environment.

Still reproducible on Linux with nwnsc 1.1.2. According to the upstream issue, this apparently is a Linux-only problem.

Just a heads up, I fixed this upstream https://github.com/nwneetools/nwnsc/pull/19


building dataset with the size of 1k, 10k, 100k, 1m events from the mixed dataset

These dataset will be used for debugging purposes, regarding dataset size is so large and we need to make sure the code is working already

all permutation of the dataset has been built as shuffled_splitted, shuffled_y_processed, shuffled in 1,10,100,1000k size


Bugfix - don't show empty fields

If a user forks and skips certain fields, they are currently still shown in the summary table. These fields are often irrelevant. Added a filter to check if field value is null, undefined, or ''.
Added fields.{fieldName}.summary key back as breaks previous implementations
Display label from translation if present (radio)

BTW travis integration is trolling us today. It's showing builds as pending looong after they were successful

:trollface:


Extract vmNotRunningError

and make the error message suggest possible action to take
$ $GOPATH/bin/boot2docker-cli ssh
error in run: VM "boot2docker-vm" is not running.

LGTM
cc @gmlewis @Moghedrin

LGTM


Updated architecture with new areas

Documentation update
Basically, replaced an image with an updated structure.
Changes:
Old:

New:

Added Queue (the best I understand it). It was not yet said what technology will be used in it, it will need to be updated once we have some code.
Added names of areas in format of (Area). Areas are outlined in this doc
Basically, trying to keep our naming of things consistent.

If you disagree with where things are placed, please let me know. I'm not very sure on Queue myself.

Awesome diagram. I think it's good to update this PR as decision on queue will be made soon.

Updated queue with technologies mentioned. bullMQ is on Redis, so might as well add that for better understanding.

I'm currently also working on #141. So I'm making labels and this diagram consistent with also this doc. Keep in mind, the label colors are the same as in this image.

Too many changes while I'm doing this, will temporarily make it a draft.


Numbering alphabetically rather than list order

Great script, thanks for your efforts.
I'm running the trending recipe and whilst I can see on the output that it knows the order of the list, the titles are being numbered by reverse alphabetically Z to A.
It seems very similar to closed issue #63.

Once I changed the agent used for all my libraries to legacy in the advance settings for each library, this issue did not appear.


pass scriptdata01.dat

for tests21.dat, the tokenizer need reference parser. I don't have better method for deal with, do you (@jaytaph ) have better method? , Currently modify the pr for ready merge.

for tests21.dat, the tokenizer need reference parser. I don't have better method for deal with, do you (@jaytaph ) have better method? , Currently modify the pr for ready merge.

I don't have a better method right now. But we can look at this later.

@CharlesChen0823 can you rebase the branch onto the main branch?

@CharlesChen0823 can you rebase the branch onto the main branch?

@jaytaph had rebase.

@CharlesChen0823 Thanks for the PR!


Relationship ‘results in maturation of’ may not be optimal for regeneration terms

Hi @cmungall ,
The relationship ‘results in maturation of’ is currently used to define regeneration terms.
Regeneration can occur via renewal, restoration, and/or growth. See https://github.com/geneontology/go-ontology/issues/12589. To me, ‘maturation’ doesn’t quite nail down this complexity. Wouldn’t it be less ambiguous if we re-labeled the relationship as (duh…) ‘results in regeneration of’?
The same relationship is currently used to define real cell and tissue maturation (e.g. seed maturation, hindbrain maturation, oocyte maturation). We probably want to differentiate those processes from the regeneration that occurs say after a spinal injury.
Thanks!

@ukemi What would be a better relation?
The parent is 'results in developmental progression of'
definition
p results in the developmental progression of s iff p is a developmental process and s is an anatomical structure and p causes s to undergo a change in state at some point along its natural developmental cycle (this cycle starts with its formation, through the mature structure, and ends with its loss).
Would this be better ?
Thanks, Pascale


Rescue after_error callback errors

If a job fails currently, it attempts an after_error/2 callback.
If that callback exists it is run. If it doesn't the dispatcher moves
on.
This commit handles the case where the callback is there, but it raises
an error. Previously if this happened, the dispatcher would die and the
job would be put back on the queue and picked up again when a new
dispatcher was created.

Please go ahead and bump version etc @sadir

Yeah that's exactly what would happen

Yup, bump to 1.2.2 and don't forget the changelog.

:shipit:


failing to download behind corporate proxy

When I try to install intellisense support in VS Code (v1.19.3) I get no output messages indicating failure and bakery is not added.
The dev tools show the following in the log >
ERR Failed to download Cake Bakery from NuGet: Error: self signed certificate in certificate chain
which is the proxy doing it's thing.
When this happened with browsing/installing vs code extensions, the following was needed in my settings.json which resolved the issue.
"http.proxyStrictSSL": false,
However the cake plugin for adding both debug or intellisense does not work due to certificate issues and the above setting has no effect.
I've tried uninstalling and reinstalling both cake and c# extensions in case is was anything corrupted but to no avail.

I know, its kind of late but may be will help anyone - you can try to add Cake.Bakery at packages.config like this:
<?xml version="1.0" encoding="utf-8"?>
<packages>
    <package id="Cake" version="0.23" />
    <package id="Cake.Bakery" version="0.2.0" />
</packages>

Then run your build.ps1 and it should work. It's workaround of course, but it works at least for me.


Typo "ArcSight" instead of "Splunk"

@amitchauhan-msgit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; merging. Thanks @amitchauhan-msgit.


Hot Reload not working - Model v4 - Typescript

The hot reload doesn't seem to be working for me. I make changes on a file inside the "functions" folder and nothing happens. It seems like it's not watching for changes. The project and folder structure were automatically created using the Azure Tools for VS Code and it's a very simple project.
Typescript 5.2.2
Core Tools Version: 4.0.5390
Function Runtime Version: <IP_ADDRESS>64
Package.json
{ "name": "americold-integration-api",   "version": "1.0.0",   "description": "",   "scripts": {     "build": "tsc",     "watch": "tsc -w",     "clean": "rimraf dist",     "prestart": "npm run clean && npm run build",     "start": "func start",     "test": "echo \"No tests yet...\""   },   "dependencies": {     "@azure/functions": "4.0.1",     "applicationinsights": "2.8.0",     "moment": "2.29.4",     "mongoose": "7.5.3"   },   "devDependencies": {     "@types/node": "18.x",     "rimraf": "5.0.0",     "typescript": "5.2.2"   },   "main": "dist/src/functions/*.js" }

Are you using TypeScript watch by chance? It's the JavaScript files that actually get run, so making a change in src/functions won't help unless you're running tsc -w or npm run watch in addition to func start
If that doesn't help, please copy the logs of func start here

Oh also double-check you have "extensionBundle" listed in your host.json file. I'm pretty sure VS Code adds this by default so it's probably not your problem, but we recently found a bug where it doesn't work if you don't have an extension bundle. See the issue for more details.

@ejizba thanks for the quick response!
My host.json does have the extensionBundle:
{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "excludedTypes": "Request"
      }
    }
  },
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[3.15.0, 4.0.0)"
  }
}

I wasn't actually running the "tsc -w" in addition to the func start, but even running both at the same time, the hot reload doesn't work. When I save the file, the terminal where the "watch" is running flickers for a second, but the changes are not made in the function. Also, I didn't know that I needed to run both at the same time. I didn't see anywhere saying that I needed that for the hot reload to work. Maybe I didn't research enough, but I spent quite some time looking for this with no success. So maybe it's something that needs to be more clear and easy to find in the documentation.
Here's the func start log from the terminal. If there are other logs that you need, where can I find them?
[2023-10-05T00:54:27.079Z] Worker process started and initialized.
Functions:
        createOrder: [POST] http://localhost:7071/api/order

For detailed output, run func with --verbose flag.
[2023-10-05T00:54:32.112Z] Host lock lease acquired by instance ID '0000000000000000000000004B52C1DB'.

Thank you!

Also, even if I make changes in the .js file inside the "dist/functions" folder, it doesn't seem to get the change. Should it hot reload if I manually change the .js file in the "dist" folder?

Yeah updating the .js file inside the dist/functions folder should work.
Running "tsc -w" (or "npm run watch") is mostly just TypeScript tribal knowledge. It's nothing specific to Azure Functions, but I understand where you're coming from. Let us know where you would expect to find this documented and we can look at adding it
Here's what I see in my logs. You should see the bottom logs duplicated each time you save a file, which is what I was looking for. Make sure "func start" and "tsc -w" are both being run from the same root folder of your app
Azure Functions Core Tools
Core Tools Version:       4.0.5382 Commit hash: N/A  (64-bit)
Function Runtime Version: <IP_ADDRESS>64

[2023-10-05T01:20:31.759Z] Worker process started and initialized.

Functions:

        httpTrigger1: [GET,POST] http://localhost:7071/api/httpTrigger1

For detailed output, run func with --verbose flag.
[2023-10-05T01:20:37.514Z] Host lock lease acquired by instance ID '000000000000000000000000017BE3A8'.
[2023-10-05T01:20:39.670Z] Worker process started and initialized.
[2023-10-05T01:20:44.940Z] Host lock lease acquired by instance ID '000000000000000000000000017BE3A8'.
[2023-10-05T01:20:49.194Z] Worker process started and initialized.
[2023-10-05T01:20:54.467Z] Host lock lease acquired by instance ID '000000000000000000000000017BE3A8'.

I found the issue... I had WEBSITE_RUN_FROM_PACKAGE=1 in my local.settngs.json. By removing it the hot reload works. I just needed to run "npm start" and "npm run watch" simultaneously. Thank you for your help!


close to a school

I keep getting messages that I'm too close to a school and that Yik Yak is for adults only. I can no longer view the feed nor post yaks nor replies

Well, assuming you are not actually close to a K-12 school, have you tried closing the app in the multitasking list and then reopening it to refresh your location?
If you are close to a school, then I can't (and won't) help.

I live 6 blocks from a school. But I was getting the same error even when I'm no where near the school.

And does force-quitting the app and re-opening it help, when you're nowhere near the school?


feat: make Observable class internal

Describe the feature
Check all libraries's exporting API:

Remove all Observable<T> and replace them with AsyncIterable<T>
Remove all Subject<T> and replace them with AsyncIterable<T> and extra next, complete, and error methods to manipulate.

Hint: All Observable<T> can be transformed to AsyncIterable<T>, and back to Observable<T>.
Why do you need this feature?
It might cause compatibility issues.
Confusing when someone is new to development.
Additional context
Observable of rxjs is useful for defining a stream interface.
But, the issue is that when we export an interface with Observable, it will bind the version of rxjs. (because Observable is a class rather than an interface)
We met a compiling error: Observable cannot be assigned to another Observable from a different version of rxjs.
The solutions are:

Keep all related rxjs in the same version. (Hard to ensure when code dispersed in multiple repos)
Make rxjs as a peer-dependency. (Peer dependency has many unresolved issues)
Ensure all Observables are used inside the package, and never export them as Param and Return types.

To introduce the short rule: Never export a class type
In JavaScript & node modules cache & npm:

Class is a named type, not a structured type (duck type), with a more strict compatible issue.
Node.js distinct JS files by its path.
You can install different versions of one node package, but they will be installed in different paths.

So, exporting a class type might cause compatibility issues.

#687 introduces an util to get AsyncIterable from Observable.
from in package rxjs can be used to get Observable from AsyncIterable.

I think Subject<T> is equal to the read-side AsyncIterable<T> and the write-side AsyncIterator<T, void, T>.
Define a type NativeSubject<T>,
type NativeSubject<T> = AsyncIterable<T> & AsyncIterator<T, void, T>;

Transform between native subject and rxjs subject:
const subjectToNativeSubject = <T>(subject$: Subject<T>): NativeSubject<T> => ({
  ...observableToAsyncIterable(subject$),
  next: (value: T) => {
    subject$.next(value);
    return Promise.resolve({ value, done: false });
  },
  return: () => {
    subject$.complete();
    return Promise.resolve({ value: undefined, done: true });
  },
  throw: (e: any) => {
    subject$.error(e);
    return Promise.reject(e);
  },
});

const nativeSubjectToSubject = <T>(asyncIterable: NativeSubject<T>): Subject<T> => {
  const subject$ = new Subject<T>();
  from(asyncIterable).subscribe(subject$);
  return subject$;
};

#693 implemented


Brew upgrade no longer uses the --all option

According to Homebrew/brew#1202, the --all flag for brew upgrade is no longer required.

Duplicates #737


feat: add an option to disable save cursor location

add an option to disable save cursor location.

I Just add the if not and then merged, thank you for the PR :)


Added a portfolio template

#1
Hope you like this theme.
Please give suggestions too.

Looks great!


NestedScrollView and IndexedStack coupled scrolling

When i have a NestedScrollView and the body is an IndexedStack-based tab bar view with a vertical ScrollView per tab, like the one in the example down here, the ScrollViews in the tabs scroll together even though only one tab is active and being scrolled down.

Code to Reproduce
import 'package:flutter/material.dart';

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

class MyApp extends StatefulWidget {
  // This widget is the root of your application.
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> with SingleTickerProviderStateMixin {
  late TabController tabController;

  @override
  void initState() {
    tabController = TabController(length: 2, vsync: this)
      ..addListener(_listener);
    super.initState();
  }

  @override
  void dispose() {
    tabController
      ..removeListener(_listener)
      ..dispose();
    super.dispose();
  }

  void _listener() {
    setState(() {});
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: NestedScrollView(
          floatHeaderSlivers: true,
          body: IndexedStack(
            index: tabController.index,
            children: [
              ListView.builder(
                itemBuilder: (context, index) => Text(
                  index.toString(),
                  style: TextStyle(
                    fontSize: 32,
                  ),
                ),
              ),
              Container(
                color: Colors.yellowAccent,
                child: ListView.builder(
                  itemBuilder: (context, index) => Text(index.toString()),
                ),
              ),
            ],
          ),
          headerSliverBuilder:
              (BuildContext context, bool innerBoxIsScrolled) => [
            SliverAppBar(
              bottom: TabBar(
                controller: tabController,
                tabs: [
                  Tab(text: '1'),
                  Tab(text: '2'),
                ],
              ),
            ),
          ],
        ),
      ),
    );
  }
}

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
If i am in tab 1 and scroll the list, tab 2 should not scroll.
Actual results:
if I am in tab 1 and scroll the list, tab 2 scrolls too.
Note:
This does not happen if the parent is a Scaffold instead of a NestedScrollView or if the body of the NestedScrollView is the default flutter TabBarView (which is based on a PageView).
This always happens whenever the NestedScrollView body's tab bar view is made with a Stack

Logs

output of flutter analyze
Analyzing nested_navigation_cross_fade...
No issues found! (ran in 1.4s)

output of flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.5.2 20G95 darwin-x64, locale it-IT)
    • Flutter version 2.2.3 at /Users/giuseppedimarzo/fvm/versions/stable
    • Framework revision f4abaa0735 (10 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/giuseppedimarzo/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.59.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.25.0

[✓] Connected device (2 available)
    • iPhone SE (2nd generation) (mobile) • FD4340EB-5039-4331-8678-21DB5C522A89 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
    • Chrome (web)                        • chrome                               • web-javascript • Google Chrome 93.0.4577.63

• No issues found!

Hi @Mawrte
I see there's an open issue addressing the case you described.
Please follow up on that issue, Closing as duplicate of https://github.com/flutter/flutter/issues/36419
If you disagree, please write in the comments and I will reopen it.
Thank you


check that stim_channel exists in edf.py

This is a follow-up to an issue raised in https://github.com/mne-tools/mne-python/pull/4205.
In read_raw_edf(), it is possible to specify stim_channel as as str. However, if stim_channel doesn't exactly match one of ch_names (e.g. if you input 'status' instead of 'Status'), the code fails line 517 because stim_channel is a str, instead of an index.
Technically stim_channel should get converted into an index at line 463, but this never happens if the labels don't match exactly.
I suggest the following addition to _get_edf_info() to check that stim_channel is actually found in the data, and output a more helpful error message.
from difflib import get_close_matches

if isinstance(stim_channel, str):
    if stim_channel not in ch_names:
        matches = get_close_matches(stim_channel, ch_names, n=1)[0]
        raise ValueError('Could not find a channel named "%s" in datafile'
                         ', closest match is "%s"' % (stim_channel, matches))

If you think this is a good idea, I can make a PR once #4205 is merged, or squeeze this into #4205.

fine with me but I think that get_close_matches is a too loose check. I
would just check that strings match in lower/upper case eventually omitting
spaces.

Ok, so what about this then?
    if isinstance(stim_channel, str):
        if stim_channel not in ch_names:
            err = 'Could not find a channel named "%s" in datafile.' \
                  % stim_channel
            casematch = [ch for ch in ch_names
                         if stim_channel.lower().replace(' ', '') == \
                         ch.lower().replace(' ', '')]
            if casematch:
                    err += ' Closest match is "%s".' % casematch[0]
            raise ValueError(err)

Is it ok to include this in the open PR?

ok
I would make a tiny private subfunction to do this though

Closed in favour of #4205