Why is 'thumbnails' property in metadata a string? [Question]

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question
I'm coming from youtube-dl and when trying to parse the metadata json, it broke my old code, because from youtube-dl the field thumbnails is a list, but in yt-dlp it is a string.
Just curious about why that is, as the string still contains a valid json list.
Thanks for the great tool!

Sorry, it's a bug and is closed by https://github.com/yt-dlp/yt-dlp/commit/8012d892bd38af731357a61e071e0a0d01bc41b4


Add dark-mode and neon-theme.

Added the night-mode feature along with the neon-theme which works with both the modes ( light and dark ). Made the app responsive along with the new features.
Please review the changes.
Thanks

Awesome @JilsT


Run with Parameters doesn't check Notebook kernel

Currently we only support Python3 for parameterized notebooks (in terms of the syntax we expect for this to function), but we never check that so users can run a parameterized notebook as any kernel they want and while it may sometimes work generally they'll probably hit some issue along the way.
We should display an error or even just hide the "Run with Parameters" action when the kernel isn't Python3.

Run with Parameters can be used on all Spark kernels, Python Kernel, PowerShell, and the .Net Interactive Kernels as they support the passing of parameters. We can document this to ensure that users who click the run parameters action can learn more Parameterization and ensure we document that we currently are focused on Python kernel parameterization first and will work toward supporting all other kernels as well.


How to remove mobile phone verification?

Hi,
I open a new membership, the phone wants verification. How to remove mobile phone verification
Thank you.

@UfukAntep you can delete phone verification in Barong configs not in Peatio.


Remove major params from things that are not top level resources

This should be removed from wrappers. This shouldnt cause too many issues atm

Not sure if this is actually a issue.

Not sure if it was valid to begin with, but wont be a issue now due to the removal of http wrappers. #201


fix sorting with undefined values

Issue #4289 describes a sorting issue with undefined values.
Right now in the getAutoSortDir function, the value of the first row is used to determine the (first) sort direction. If it's a string, sorting is asc, otherwise desc.
The problem with this is:
If the value of the first row happens to be undefined, than the getAutoSortDir will return desc because of the typeof value === 'string' check.
So the items are sorted descending (putting the undefined ones at the bottom) after the first sort click event.
When you click sorting again, the getNextSortingOrder function will get called and getAutoSortDir function will be called again, but now the first row is no longer an undefined value, but a string, so it will return asc.
Making the following statement evaluate to true
https://github.com/TanStack/table/blob/423d46ecce8d1f3f02c78e5d833b54112c21136c/packages/table-core/src/features/Sorting.ts#L298-L304
and thus returning false when called in the setSorting function, making it remove the sorting state
https://github.com/TanStack/table/blob/423d46ecce8d1f3f02c78e5d833b54112c21136c/packages/table-core/src/features/Sorting.ts#L235-L238
So what I've done now is iterated over all rows to verify if the type of the column is a string.
I'm not so sure about this implementation as this will for sure impact performance (if the column is for example a number, than all rows will be iterated before hitting the final return statement...).
A performance optimization could be to also check for additional types (date, number...) so the function can return early.
I noticed getAutoSortingFn uses .slice(10), not sure where this number comes from?
The same could be used in getAutoSortDir, but the issue will of course still occur if you have more than 10 rows with undefined values.
https://github.com/TanStack/table/blob/423d46ecce8d1f3f02c78e5d833b54112c21136c/packages/table-core/src/features/Sorting.ts#L139
This technique of using the value of the first row is for example also used to determine the filter function, so this might cause issues here as well
https://github.com/TanStack/table/blob/423d46ecce8d1f3f02c78e5d833b54112c21136c/packages/table-core/src/features/Filters.ts#L207
Fixes #4289

Maybe with a max of 10 rows being checked, we could do this. Also consider you can the sortDescFirst and sortUndefined column options manually yourself if your data has null or undefined values.

Closing in favor of sortDescFirst and sortUndefined

Closing in favor of sortDescFirst and sortUndefined

Did those solve all of the use cases you have?

Closing in favor of sortDescFirst and sortUndefined

Did those solve all of the use cases you have?

It solves mine, but won't solve the case metioned in the issue.


proposal: cmd/vet: printf: warn about verbs that don’t match a type parameter’s type set

As a spin-off of the discussion in #48971, I propose to have cmd/vet report diagnostics for printf verbs that don’t match every element of a type parameter’s type set.
For example, consider the following:
func F[P ~int](p P) {
  fmt.Printf("%s", p)  // int is in the type set of P, and does not match %s
}

func G[Q any](q Q) {
  fmt.Printf(“%d”, q)  // many types in the type set of Q do not match %d
}

In this example, the type set of P is all types with int underlying. There are types in that type set (such as int itself) that do not match the verb %s, so we would report a diagnostic – something like fmt.Printf format %s does not match type int in the underlying type set for P.
Similarly, the type set of Q is all types, and there are of course many types in this type set that do not match %d, so we would report something like fmt.Printf format %d does not match constraint type ‘any’.
In these examples we might have false positives: it could be the case that F is only ever instantiated with arguments implementing fmt.Stringer. It could be the case that G is only ever instantiated with integral types.  By comparison, we explicitly do not report such diagnostics for most arguments of interface type:

// Whether any particular verb is valid depends on the argument.
// The user may have reasonable prior knowledge of the contents of the interface.

However, with the new interface syntax in Go 1.18, we are able to express restrictions on both the method set and underlying type of a type parameter.  If arguments of type parameter type are being passed to a %d verb, we can prove that this is OK if the type set is restricted to integral underlying types. On the other hand, if the type set is not restricted to integral underlying types, it is highly likely that this is a user error.  Specifically, it is more likely than in the case of interface types, because users could have specified structural restrictions on the type parameter.
There is precedent here.  In the initial implementation of printf checks for %w, it was decided that all arguments must be convertible to error (including, for example, arguments of type interface{}).  The rationale behind this is similar to above: the user is able to express an ‘implements’ relationship between interface types, and if they did not it is likely a user error.  [see also #48931].
Generics will be used to add type safety to existing code that previously used interfaces. By flagging potentially incorrect printf verbs, we can help users identify potential runtime errors and add accurate type restrictions to their type parameter constraints.
I have prototyped this feature, and think it is do-able for 1.18, though producing great diagnostic messages might be a bit tricky. I think it’s OK if we wait for 1.19.
CC @timothy-king @neild @bcmills @mvdan

There are two possible ways to extend the printf(format, arg) check for generics:

Complain if at least one possible type for arg does not match format.
Complain only if all possible types for arg do not match format.

So for example if you have a constraint int|string and format %d, then
in (1) vet would complain because the string case doesn't work with %d,
while in (2) vet would not complain because the int case is OK and maybe it's an int.
It sounds like you are suggesting (1).
That seems more in keeping with the rest of the generics rules.
Does anyone object to (1)?

Also, we may find that (2) is better by trying (1) and realizing we are getting too many errors.
If we don't do (1) now, we will not be able to switch to it easily later.
So that suggests we should do (1).

I did not see where the proposal states this explicitly or not so I'm going to just ask. Do we need to take the method set into account for some of the verbs? Stealing an example from https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md :
type StringableSignedInteger interface {
	~int | ~int8 | ~int16 | ~int32 | ~int64
	String() string
}

It seems like this should never complain about "%s". Maybe "%w" also needs to take this into account? Any other verbs?

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

Whoops, forgot to close this. This is done.


Implement GitHub Actions

Added support for windows & android binaries, now they're available in each build as artifacts.
In the future an automated release ci will be implemented

Added support for windows & android binaries, now they're available in each build as artifacts.
In the future an automated release ci will be implemented.
PRs about adding iOS / Linux / MacOS support are appreciated

I have a linux appimage github ci.

@Hexer10  Linux support for workflows is addressed in #11


Review fligh mode parameters

replace extra flight modes with precision
change speed for 2

Awaiting test in the granite lab

I tested this in the lab, basically replaced all of the special behaviors flight modes with a PRECISION to be easier to manage. The PRECISION is the same as nominal, but with fan speed of 3

@kbrowne15 can you double check this and then we can merge


Font size bug

The default button for font-size seems to not work. Also, a custom font-size causes the font-family default button to not work.
The video below shows the font-family button working correctly, then the font-size button not working, then the font-family button not working.
https://user-images.githubusercontent.com/51394257/116770802-1875ce00-aa3e-11eb-9e5a-0c2078f5d3f5.mov

@ScottWager This issue is not reproduced.
Please tell me more detail.
Tested browser, suneditor version, etc.


Reimplement the svf method based on the PFENet code and the result is inferior than original PFENet.

Thanks for your nice work. I implement the svf method based on the PFENet code and the result is inferior than original PFENet. I followed the parameter setting in PFENet. And I used the same dataset and parameter setting in both original PFENet and PFENet with SVF. But the performance of PFENet with SVF performs worse than original PFENet. Could you please share your full-training code  rather than svf module code? Thanks a lot!

@lyphui The reason for this is detailed in this issue _https://github.com/syp2ysy/SVF/issues/3_  and the code of FSSS is  https://github.com/zechao-li/SVF-few-shot-segmentation


An error happened while trying to locate the file on the Hub and we cannot find the requested files in the local cache. Please check your connection and try again or make sure your Internet connection is on.

Error occurred when executing PulidEvaClipLoader:
An error happened while trying to locate the file on the Hub and we cannot find the requested files in the local cache. Please check your connection and try again or make sure your Internet connection is on.
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\execution.py", line 69, in map_node_over_list
results.append(getattr(obj, func)())
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\custom_nodes\PuLID_ComfyUI\pulid.py", line 230, in load_eva_clip
model, _, _ = create_model_and_transforms('EVA02-CLIP-L-14-336', 'eva_clip', force_custom_clip=True)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\custom_nodes\PuLID_ComfyUI\eva_clip\factory.py", line 377, in create_model_and_transforms
model = create_model(
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\custom_nodes\PuLID_ComfyUI\eva_clip\factory.py", line 279, in create_model
checkpoint_path = download_pretrained(pretrained_cfg, cache_dir=cache_dir)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\custom_nodes\PuLID_ComfyUI\eva_clip\pretrained.py", line 328, in download_pretrained
target = download_pretrained_from_hf(model_id, filename=filename, cache_dir=cache_dir)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\custom_nodes\PuLID_ComfyUI\eva_clip\pretrained.py", line 300, in download_pretrained_from_hf
cached_file = hf_hub_download(model_id, filename, revision=revision, cache_dir=cache_dir)
File "", line 52, in hf_hub_download_wrapper_inner
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\python\lib\site-packages\huggingface_hub\utils_validators.py", line 118, in _inner_fn
return fn(*args, **kwargs)
File "P:\ComfyUI-aki-v1.3\ComfyUI-aki-v1.3\python\lib\site-packages\huggingface_hub\file_download.py", line 1371, in hf_hub_download
raise LocalEntryNotFoundError(

duplicate https://github.com/cubiq/PuLID_ComfyUI/issues/7

我也是这个问题请问怎么解决？我的微信：1197646846


Generate coverage reports

Our one test does not give what you might call comprehensive coverage. We should persuade Travis or a sister service to give us test coverage reports.

We want to use the Jest coverage tool: https://create-react-app.dev/docs/running-tests#coverage-reporting
I had problems configuring it correctly though.

Closed in #11


Add linux compatible GenProjects file

Description
I've added a Linux GenProjects file called Lnx-GenProjects.sh in the scripts folder and the premake executable  premake5-linux in vendor/bin/premake/.

Since making the workflow on all platforms is cherno's priority, i'll leave this up to him for now. Leaving this here for the future.

I noticed the pull request #156 (Made Win-GenProjects.bat work from every directory) that was suppose to make the bat file work no matter what directory you were in. I looked for a linux alternative and found one here. This is what I used:
dp0=$(dirname $(readlink -f $0))
cd "$dp0/.."

You can now run Lnx-GenProjects.sh from any location in the terminal


Add "Beta" label back to Custom Terms of Service feature

Add beta label back to Custom ToS until the following two bugs are fixed.
https://mattermost.atlassian.net/browse/MM-13349
https://mattermost.atlassian.net/browse/MM-13509
Both are bugs, but they are edge cases where keeping the "Beta" tag is okay. However, we should fix the issues and doc as known issues until we have the two bugs fixed.

FYI I cancelled the first three builds to free up jenkins slots since we didn't need them


Error

app.js:1 Uncaught ReferenceError: webpackJsonp is not defined
at app.js:1
(anonymous) @ app.js:1

Is this from a fresh install?

I'm closing this because I cannot recreate and there is no context information provided.


Add Navigation Bar

Description of Issue
We want to add a navigation bar on each page similar to the functional testing site. http://engineering.cerner.com/terra-core/#/site

Resolved in #23


Mesh won't connect after upgrade - Auth error

After upgrading HA and this AwoX intergration I can't seem to connect to the mesh anymore. In the logs it shows me
2022-09-22 09:02:56.869 INFO (SyncWorker_1) [custom_components.awox.awoxmeshlight] Auth error : check name and password.
To try and resolve this I've:

deleted the integration and deleted the files from the custom_components folder, just to be sure
in the Smart Control app I've deleted all lights, changed my account password (just to be sure there was no conflict with the newer AwoX app)
rebooted Home Assitant
added all the lights in the Smart Control app
reinstalled the integration and logged in with the new credentials
rebooted yet another time

But all to no avail...
I've had this same issue (Auth error) with a previous HA upgrade (> 2021.12) as well, but simply reverted to a backup since I hadn't the time to look into it.
Can you advice?

@JoeyGnarf that message implies that the used info fetched from Awox when you setup the integration is outdated. Did you use the same credentials in HA when you re-installed the integration as you used to login to the Awox app?
note: Will improve the logged message

Yes. Even removed all lights and remotes from the app, manually reset all of them, power cycled the entire house, created a new account with different credentials, added them to the new account, clean installed the integration and I still get the same thing :-(
PS. Thanks for your help and for your work on updating the integration.

If you change the name of one of the lights in the Awox app and then reinstall the integration in HA is this new name visible in HA?
Could you enable debug logging before you install the integration and share that log with me?

I'm afraid I can only let you know in a few months. I was so fed up I've replaced all AwoX BT controlled lights and stored those to try again later if and when we can use them again in a new karate studio we're hoping to open in January.
Again, many thanks for your efforts and support while I had them in use!


Oops

{int ch; if ((ch=getchar()) == EOF) break; m[p]=ch;}
Okay, that's a pretty good idea ... but what's supposed to happen if the , command isn't in a loop?

@rdebath ping
May I close the issue?

Of course you may, you have answered the question and given a reasonable response, but most importantly this is your repository.


Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose, on an Virtual Machine encrypted using BEK "without AAD".

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Related command

Extension name (the extension in question)
Vm-repair
Description of issue (in as much detail as possible)
Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose --debug, on an Virtual Machine encrypted using BEK "without AAD".
We are getting the error:
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/invocation.py", line 111, in _validation
self._validate_cmd_level(parsed_ns, cmd_validator)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 849, in _validate_cmd_level
cmd_validator(**self._build_kwargs(cmd_validator, ns))
File "/home/divyam/.azure/cliextensions/vm-repair/azext_vm_repair/_validators.py", line 64, in validate_create
encryption_type, _, _, _ = _fetch_encryption_settings(source_vm)
File "/home/divyam/.azure/cliextensions/vm-repair/azext_vm_repair/repair_utils.py", line 355, in _fetch_encryption_settings
if enabled.tolower() == 'false':
AttributeError: 'bool' object has no attribute 'tolower'
I suspected that this problem is related to:
https://github.com/Azure/azure-cli-extensions/commit/f2096071c968406896fab1dd806c2ff6882449bf
https://github.com/Azure/azure-cli-extensions/pull/6238
Can you please check if this problem is related to da code change?

Thank you for opening this issue, we will look into it.

@Diofe Thanks for reporting. This bug has been addressed by PR https://github.com/Azure/azure-cli-extensions/pull/6326
Please check if it works for you now.


zpool-auto-expand-partitions: 0.1.0 -> 0.1.1

Description of changes
Package bump. This is needed because the build was failing before.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Duplicate of https://github.com/NixOS/nixpkgs/pull/268562


Where can I find .editorconfig for C# Coding Conventions ?

@vitaliizabolotnyi you may see these examples

runtime
asp.net
entity framework

Closing this now. Let us know if you need anything else.


Bring back the Cakefile

Cakefile's and the cake CLI were one of my favorite things about CoffeeScript, and Civet just happens to have a name that also starts with C. What would you think of reclaiming cake? :)

These days I'd probably recommend https://github.com/casey/just or adding scripts to package.json. But if anyone wants to remake cake in Civet I'd add it to my list of recommendations 😸

I've never used cake but https://coffeescript.org/v2/annotated-source/cake.html is impressively simple. It'd certainly be possible to make a separate CLI tool/NPM package for this (civet-cake or some more clever combination?) that instead loaded using Civet. Maybe it'd be better to allow Cakefile, Cakefile.coffee, or Cakefile.civet so you can specify the language? Could be nice for backward compatibility with existing CoffeeScript projects that want to migrate to Civet.


GradleRoboSpecification fails to load project resources

Hi,
I have tested 0.7 and 1.0 version and the same issue occurs. When I am using GradleRoboSpecification only Android system resources are loaded and ResourceNotFound error is raised during tests. I have fixed this issue by falling back to RoboSpecification with manifest path specified (standard location). After upgrading to 1.0 I saw RoboSpecification is Deprecated. I do not know what is causing the issue, a hint is that I have multimodule project with both java and android libraries.
Any ideas what is causing this issue?

did you try to place configuration in src/test/resources/robolectric.properties ?
it is the best way to configure test env. Please mind the fact that AndroidStudio uses other root dir for project than gradle does


Some records were missing when I scrolled to bottom with the modified "$prompt".

Windows Terminal version
1.16.10262.0
Windows build number
10.0.22621.1194
Other Software
cmd.exe in Build 22621.1194
Steps to reproduce
Use "setx" command to set "$prompt"
Run commands as "ping -t" or long press Enter make commands records to scroll to bottom
Expected Behavior
Usually, the scroll bar should be appeared when a command runs to bottom, make sure the earlier records still exist when the history records was 9001 in default althougth the "$prompt" was set to other.
(Legacy cmd and WT v1.17.1023)

Actual Behavior
The scroll bar didn't appear when the command records over to bottom although 9001 in default and fix or reset the WT application.

Haha that prompt looks familiar 😉

Can you share what exactly you've set %PROMPT% to?
Also, could you share your settings.json file/?

This is %PROMPT%

[19:55:58.42]>C:\Users\Briar>
Briar@LXH-PC>echo %PROMPT%
$e[30;47m[$T]$G$e[37;46m$P$G$e[0m$_$e[34mBriar$e[0m@$e[32mLXH-PC$e[0m$G

The PC name(LXH-PC) and user name(Briar) were from %computername% and %username%
setx prompt $e[30;47m[$T]$G$e[37;46m$P$G$e[0m$_$e[34m%username%$e[0m@$e[32m%computername%$e[0m$G

And this is settings.json
settings.json.txt

Others

The same WT version ,$PROMPT$ and settings.json in a Beta Build

Hi @Briar-CatHei. Are you launching CMD directly (i.e. cmd.exe from Run) or inside Terminal?

Both, but I solved that by reinstalling the whole OS
I was wondering that how to cause that bug before...

Great! Closing as no repro then. Thanks!


chore(deps): :arrow_up: update nx monorepo to v17 (major)

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@nx/angular (source)
16.6.0 -> 17.0.0

@nx/cypress (source)
16.6.0 -> 17.0.0

@nx/eslint-plugin (source)
16.6.0 -> 17.0.0

@nx/jest (source)
16.6.0 -> 17.0.0

@nx/linter (source)
16.6.0 -> 17.0.0

@nx/workspace (source)
16.6.0 -> 17.0.0

nx (source)
16.6.0 -> 17.0.0

Release Notes

nrwl/nx (@nx/angular)
v17.0.0
Compare Source
17.0.0
🚀 Features

angular: switch default to typescript configuration for module federation (#18998)
angular: support generating artifacts using options as provided (#19527)
angular: add federate-module generator (#19523)
angular: use consistent artifact generation for generators (#19601)
core: accept various task runner options from root of nx.json (#19243)
core: read cloud url from nx.json (#19468)
core: add --type for nx show projects (#19358)
core: add NX_PARALLEL env var (#19488)
core: generate new workspaces without tasks runner options (#19483)
core: update default cache directory to .nx/cache (#19536)
core: migrate existing workspaces to slimmer tasks runner options config (#19570)
core: add the outputs of a task onto the task (#19561)
core: remove deprecated workspace generator command (#19541)
core: add nx task planner (#19233)
core: Allow specifying daemon socket dir (#17870)
core: allow using Nx Cloud without nx-cloud installed (#19553)
core: remove deprecated workspace-lint (#16212)
core: add batch flag to run (#19575)
core: update version of axios used (#19607)
core: add standard way to pass plugin options (#19589)
core: generate standalone projects with scoped package names (#19662)
core: allow specifying cacheability per target (#19672)
core: remove deprecated defaultCollection and npmScope nx.json … (#19708)
devkit: remove backwards compatibility for Nx 15 (#19572)
graph: display expanded task inputs (#19597)
js: add @swc-node/register and @swc/core to JS projects by default (#19453)
js: remove options to update package.json dependencies and peerDependencies (#19543)
linter: remove tslint logic (#19002)
linter: update eslint-config-prettier to v9 (#19232)
linter: rename @nx/linter to @nx/eslint (#19515)
misc: remove migrations for v14 and under (#19552)
misc: remove deprecated Angular CLI usage of schematics and builders (#19557)
misc: remove deprecated code from @nx/workspace (#19588)
nest: update nest generators to support name and directory format option (#19668)
nuxt: init, app, component, page generators (#19509)
nuxt: storybook generators (#19529)
nx-dev: statically highlight lines in code (#19703)
nx-dev: mark internal properties (#19659)
nx-plugin: add as provided prompt for executor generator (#19602)
nx-plugin: add as-provided mode for generator and migration gen… (#19614)
react: Add federate-module generator (#19286)
react: Add support for promise based remotes (#19566)
react: use TS config files for module federation (#19455)
react: remove stylus option from generators (#19441)
react: support generating components using the path as provided (#19608)
react: add recursive remote serve (#19638)
vite: future-proof Vite plugin to support ESM-only version of Vite (#19533)
vue: set @nx/vue as public (#19582)
vue: support generating components using the path as provided (#19609)

🩹 Fixes

angular: install swc/helpers when generating remote applications (#19686)
angular: fix usage of internal generators and prevent usage of deprecated project option (#19697)
angular: federate-module should support as-provided for new remotes (#19731)
core: register transpiler should setup loading for node code (#19454)
core: use typescript to get compiler options for ts-node (#19480)
core: hash the same environment as the tasks are run with (#19487)
core: set prerelease on GitHub release API request (#19532)
core: typo in cache error message (#19547)
core: notify life cycles that tasks are scheduled after they are… (#19610)
core: fix verification of non-existent cloud client (#19613)
core: correct windows path for native watcher (#19646)
core: support prettier v3 when run nx format (#19207)
core: setup the nx cloud client during postinstall (#19658)
core: removes formatting from show command when using --json flag (#19583)
core: remove -d alias because it conflicts with --dry-run (#19664)
core: always hash runtime input (#19670)
core: ensure CNW works without .yarnrc with custom registry (#18937)
core: only show cloud messaging when migrating if not using cloud (#19709)
core: check nxjson cli exists before looking for keys (#19730)
core: fix convert to monorepo eslint issue (#19713)
devkit: pass filepath to ejs for include statements (#19517)
devkit: correct nx-json typing after plugin tweaks (#19706)
js: remove deprecated babel transform (#19671)
js: update esbuild version (#19728)
js: Avoid @babel/preset-env warning in js/babel.ts (#14772)
js: use normalized tsConfig path for generating tmpTscConfig (#18794)
linter: fix validateDependenciesSectionExistance fixer (#19512)
linter: fix linter standalone patterns in Js and Next (#19508)
linter: remove consistent-type-assertions rule from config (#19549)
linter: add missing entry to migrations.json (#19641)
linter: add @nx/linter in nx packageGroup (#19654)
linter: handle string extends property in config (#19674)
linter: add migration for eslint config prettier (#19732)
misc: don't interpolate arg as undefined (#18666)
misc: pass full path to tsconfig when registering transpiler (#19451)
misc: remove projectNameAndRootFormat from nx.json schema (#19623)
misc: do not normalize project name and root when using as-provided format (#19651)
misc: update re-exports when updating imports during move (#19637)
nest: add deprecated messages to generator js schema and fix casing (#19678)
nextjs: Add missing environment variables for Nx 18 environment variables (#19585)
nextjs: Library generator should not add cypress dependency (#19587)
nx-cloud: fix nx connect throwing if run twice (#19729)
nx-dev: video cards formatting (#19449)
nx-dev: fix internal link checker (#19606)
nx-dev: fix broken linter icon (#19735)
nx-plugin: enable prompt for generator and migration generators (#19675)
nx-plugin: add nameAndDirectoryFormat to schema for generator,ex… (#19710)
react: Add missing Nx Welcome for styled-jsx (#19474)
react: storybook plugin tsconfig resolution (#19631)
react: update usage of deprecated "project" option in generators (#19696)
react: respect unitTestRunner none and inform about vitest (#19676)
react: Error when invalid path is provided to federate-module generator (#19720)
react: fix creating a react library with cwd (#19721)
storybook: cleanup v17 tasks (#19560)
storybook: default ignore .stories. files (#19699)
storybook: do not restrict to components dir for vue (#19680)
storybook: update to patch 7.5.1 webpackStatsJson fix (#19736)
testing: fix flaky test (#19625)
vite: configuration generator fixes (#19628)
vue: ensure standalone has proper lint rule (#19505)
vue: enforce multiword component name (#19507)
vue: replace className with class on html (#19500)
vue: turn multi-word component lint rule off since there is always one for restricted HTML elements (#19645)
vue: update standalone setup so tsconfig.base.json is not generated (#19660)
vue: remove unitTestRunner option from component generator (#19667)
vue: make sure project is in normalizedOptions (#19690)
vue: comment out unused defineProps function (#19695)
vue: downgrade @vue/eslint-config-prettier to work with prettier v2 (#19741)
vue: default unit test to vitest (#19746)
webpack: add guard around onListening call (#19363)
webpack: only register TS transpiler for config files ending with .ts, .mts, or .cts (#19579)

❤  Thank You

Abel @abel1105
Andrew Ovens @107420510+aovens-quantifi
Caleb Ukle
Colum Ferry @Coly010
Craigory Coppola @AgentEnder
Emily Xiong @xiongemi
Isaac Mann @isaacplmann
Jack Hsu @jaysoo
Jacob Ley @37151850+JacobLey
James Henry @JamesHenry
Jason Jean @FrozenPandaz
Jonathan Cammisuli
Justin Dietz
Katerina Skroumpelou @mandarini
Leosvel Pérez Espinosa @leosvelperez
MaxKless @34165455+MaxKless
Miroslav Jonaš @meeroslav
Nicholas Cunningham @ndcunningham
Phillip Barta @Phillip9587
Rik Smale @13023439+WikiRik
Sam Y @996939+mauris
Tomasz Kasowicz @TomaszKasowicz
Travis Cline @tmc

v16.10.0
Compare Source
16.10.0
🚀 Features

angular: support incremental TypeScript semantic diagnostics in ng-packagr executors (#19405)
core: add NX_IGNORE_CYCLES environment variable (#18708)
core: switch nx release changelog to offline first with CHANGELOG.md files (#19327)
js: upgrade @swc-node/register to 1.6.7 (#19429)
linter: add app import exception for remotes (#19301)
nuxt: add private Nuxt plugin (#19420)
nx-dev: add the new Nx blog home (c2297297c)
nx-dev: add link to AI Chat beta in docs header (#19261)
nx-dev: only show the first 5 sources in ai chat (#19331)
react: add remote to tspaths for typing (#19276)
react: update @types/react and @types/react-dom versions (#19442)
react: use JS webpack config files for module federation (#19452)
vue: storybook configuration generator for vue (#19141)
vue: update generated file setup for apps (#19428)

🩹 Fixes

angular: throw an error when generating a component and the specified module can't be found (#19324)
angular: remove leftover code causing duplicated route config when generating a library (#19326)
angular: update tsconfig included and excluded files when generating a library secondary entry point (#19366)
angular: do not set less math option in ng-packagr executors (#19402)
core: generate permissions on github ci workflow (#19357)
core: set prerelease on Github request for nx release changelog (#19343)
core: include client env when hashing tasks in the daemon (#19422)
core: adjust how findMatchingProjects works when provided additive patterns after an exclusion to be more intuitive (#19295)
core: cache runtime hashes with the env as part of the key (#19426)
core: add vue to cnw implicitDependencies (#19443)
linter: fix rule typings (#19294)
linter: add schema for nx plugin checks rule (#19447)
misc: properly add extra dependencies to packages (#19334)
misc: fixing discord link in npm page (#19372)
misc: report should not throw when no nx.json file is present (#19333)
repo: ensure cypress is installed on agents (#19430)
testing: install devkit when init playwright (#19406)
web: disable tsnode service after loading config (#19387)

❤  Thank You

Caleb Ukle
Colum Ferry @Coly010
Craigory Coppola @AgentEnder
Emily Xiong @xiongemi
Jack Hsu @jaysoo
James Henry @JamesHenry
Jason Jean @FrozenPandaz
Jonathan Cammisuli
Juri @juristr
Katerina Skroumpelou @mandarini
Leosvel Pérez Espinosa @leosvelperez
Miroslav Jonaš @meeroslav
Tim Fisher
Zachary DeRose @ZackDeRose

v16.9.1
Compare Source
16.9.1
🩹 Fixes

angular: throw an error when generating a component and the specified module can't be found (#19324)
misc: properly add extra dependencies to packages (#19334)

❤  Thank You

Jason Jean<EMAIL_ADDRESS>Leosvel Pérez Espinosa @leosvelperez

v16.9.0
Compare Source
16.9.0
🚀 Features

vue: add private Vue plugin (#19009)
js: support finding imports in .vue files (#19048)
webpack: move module federation utils to webpack (#18996)
repo: add cloud workflows (018d9972e)
linter: update version of tslint-to-eslint (#19065)
repo: enable agents" (#19112)
devkit: update parseTargetString to allow referencing targets on the current project (#19109)
js: warn users when additionalEntryPoints do not match any files (#19107)
core: add WorkspaceContext class (#18999)
vue: init, app, component and lib generators (#19130)
react: allow setting react preset to production when using custom BABEL_ENV (#19148)
core: hide vue preset options from create-nx-workspace (#19155)
devkit: add method for tree-aware glob search (#19128)
react: Add versioning for workspace libraries (#19063)
nx-dev: add embeddings for community plugins (#19168)
nx-dev: add "new chat" button to AI page (#19150)
vue: add setup-tailwind generator (#19147)
nx-dev: change "New chat" to "Clear chat" to avoid confusion, and open links in new tab (#19190)
nx-dev: remove emojis from heading ID (#19194)
nx-dev: improve auto-scrolling so it does not interfere with users reading the content (#19196)
react: switch default to typescript configuration for module federation (#19031)
core: initial implementation of nx release (#19110)
react: Support loading remotes via library: var (#19192)
core: include non-project files on fileMap and filesToProcess (#19217)
misc: do not prompt for project name and root format when they produce the same result (#19221)
react-native: upgrade react-native to 0.72.4 (#19160)
nx-dev: improve initial prompt of the AI Chat to remove bad responses (#19244)
repo: enable agents" " (#19112)
repo: remove projectNameAndRoot nx.json option (#19218)
core: run createDependencies plugins concurrently (#19176)
core: allow multiple targets in show projects commmand (#18506)
misc: prepend cwd to directory in project generators when using as-provided format (#19227)

🩹 Fixes

linter: fix dep-checks projPackageJsonDeps caching for IDE (#18935)
linter: handle non-JSON eslintrc files when updating overrides (#19026)
misc: calculate cwd relative path correctly for generators and executors (#18933)
react: fix createGlobPAtternsForDependencies path (#18546)
webpack: enable in memory caching when building for node in watch mode (#18348)
core: register ts transpiler when running .ts backed plugins (#19027)
js: workspace lib devDependencies should not be added to package.json (#17802)
misc: nx view-logs should open the nx-cloud link when connected … (#17808)
nx-dev: menu chevron alignment (f994f54c5)
linter: ensure config manipulations are run only if config is supported (#19035)
vite: check for undefined and create types array (#19045)
angular: keep dependency-checks enabled for buildable libraries (#19047)
node: explicitly check that project is a library before updating imports (#19040)
core: do not prompt, only warn when projectNameAndRootLayout is … (#19037)
core: prettier 3 shouldn't cause errors due to esm + compile cache (#19042)
misc: use preset apps instead of empty (#19051)
react: set "watch: false" on module federation serve-static options (#19052)
js: handle nested wildcard imports and paths that start with # (#19056)
core: do not validate remote cache validity (#19059)
js: esbuild should not throw when a project depends on non-js dependencies (#19057)
core: prettier 3 shouldn't cause errors due to v8 compile cache (#19075)
linter: add @eslint/js with correct package version (#19077)
core: detect dependencies in .cjs and .cts files (#19127)
node: set x-dropdown in app generator to enable autocomplete in console (#19105)
angular: dont add .angular/cache to prettier again if existing (#19183)
webpack: set module: true for swcMinify (#19213)
core: handle negative single directory globs (#19235)
core: allow parallel and output-style on publish target (#19242)
core: support dry-run on nx release publish (#19228)
core: handle negative star glob better (#19241)
core: set SWC_NODE_PROJECT before registering @swc-node/register (#19239)
nextjs: do not warn on NX_INVOKED_BY_RUNNER and only show warning once (#19254)
core: update the native runtime input to include the cpu architecture (#19263)
misc: adds nx cloud access token to agent workflow (#19264)
nx-plugin: pass full context into parseTargetString (#19154)
core: ensure target-only argument is rewritten correctly to be forwarded (#17971)
repo: add native packages to the release group (#19289)
js: update generated .swcrc file to align with<EMAIL_ADDRESS>(#19214)
nextjs: Add missing env to base Nx Env (#19201)
core: unregister in-process ts transpilers when projectGraph is created (#19187)
vite: provide correct root directory when building a root project (#19298)
core: do not attempt to publish private npm packages (#19299)

❤  Thank You

James Henry @JamesHenry
Jack Hsu @jaysoo
Jonathan Cammisuli<EMAIL_ADDRESS>Leosvel Pérez Espinosa @leosvelperez
Nicholas Cunningham @ndcunningham
Jason Jean<EMAIL_ADDRESS>Mark McCulloh @MarkMcCulloh
Jay Bell<EMAIL_ADDRESS>Craigory Coppola @AgentEnder
Simon Critchley @scritchley
Emily Xiong @xiongemi
Colum Ferry @Coly010
Miroslav Jonaš @meeroslav
MaxKless @34165455+MaxKless
Katerina Skroumpelou @mandarini
Victor Savkin<EMAIL_ADDRESS>Guy Senpai<EMAIL_ADDRESS>Juri @juristr
Adam Wootton<EMAIL_ADDRESS>Matt Lewis @mattlewis92
Nadav Shatz<EMAIL_ADDRESS>
v16.8.1
Compare Source
Bug Fixes

angular: keep dependency-checks enabled for buildable libraries (#19047) (58b13a2)
core: do not prompt, only warn when projectNameAndRootLayout is … (#19037) (18acd9a)
core: do not validate remote cache validity (#19059) (1f9dc40)
core: prettier 3 shouldn't cause errors due to esm + compile cache (#19042) (ac2bea7)
core: register ts transpiler when running .ts backed plugins (#19027) (22dadbc)
js: handle nested wildcard imports and paths that start with # (#19056) (2194422)
js: workspace lib devDependencies should not be added to package.json (#17802) (14a4ef4)
linter: ensure config manipulations are run only if config is supported (#19035) (85b03c2)
linter: fix dep-checks projPackageJsonDeps caching for IDE (#18935) (2e1d48e)
linter: handle non-JSON eslintrc files when updating overrides (#19026) (4365c01)
misc: calculate cwd relative path correctly for generators and executors (#18933) (24de089)
misc: nx view-logs should open the nx-cloud link when connected … (#17808) (2e0b09a)
misc: use preset apps instead of empty (#19051) (655a0a7)
node: explicitly check that project is a library before updating imports (#19040) (6ac6473)
react: fix createGlobPAtternsForDependencies path (#18546) (62f526a)
react: set "watch: false" on module federation serve-static options (#19052) (2e52c14)
vite: check for undefined and create types array (#19045) (143b223)
webpack: enable in memory caching when building for node in watch mode (#18348) (1f10398)

v16.8.0
Compare Source
Bug Fixes

core: apply target defaults properly for executors defaults (#18655) (f670e74)
core: fix ghost alias when parsing yarn lockfile (#18646) (43b802d)
core: fix schema links (#18395) (ded1543)
core: handle symlinks on debian for watch events (#18636) (cf0b2fd)
core: improve error handling for copy and remove (#18656) (13925ba)
core: name collisions during project inference should not error out if corrected by a project.json's name (#18665) (94cc716)
core: nx should not break if packages were not installed (#18687) (20acfbe)
core: set consistent working directory when calculating runtime hash inputs (#18643) (e2ac4e3)
core: use Date.now() everywhere for tasks start and end times to avoid negative durations (#18595) (98a7477)
core: use existing version when calling "yarn set version" (#18669) (7d55f49)
devkit: convert-nx-executor should read projectNodes (#18684) (2ff1364)
js: expose schematic using the generator function with a default for the project name and root format (#18681) (61d73fc)
linter: Normalize paths when in getSourceFilePath (#18601) (1f9b3c4)
nextjs: make next build package manager agnostic (#18661) (2e1bccd)
core: ensure preinstall is only run once on repo (#18671) (adb39c4)
core: handle symlinks better for watch events on arch (#18743) (f230078)
core: load .env after .env.local (#18746) (4a25576)
core: projects within folders that start with a . should be found (#18748) (9548714)
core: skip local yarn patches for lock file pruning (#18700) (97c5ecf)
devkit: await prettier format for v3 compatibility (#18664) (2638bb0)
js: fix swc opens swc.js instead of compiling on windows (#18723) (078cf9a)
misc: fix import path to project name and root helper (#18711) (195c5bf)
nx-dev: include section slug in ai source links (#18722) (5ff8722)
nx-dev: reverse sort indicators (#18706) (d3b4c70)
react: fix remote generation devServerPort (#18603) (1a0962f)
storybook: dont fail if targets dont exist (#18745) (0448317)
testing: fix outputs for vitest generator (#18709) (7900d56)
testing: make playwright nxE2EPreset options optional (#18729) (7024108)
angular: add @angular/pwa to migrations #18731 (#18736) (791171e)
angular: mark esbuild as optional peer dep #18526 (#18771) (1440f5c)
angular: normalize remote directory correctly when using new project root format (#18765) (9123271)
core: fix wrong yarn patch key mapping (#18759) (42d93b0)
linter: error on dependencies that are only in devDependencies instead of production dependencies (#18780) (9ffea2b)
linter: fixes usages of lintProjectGenerator without eslintFilePatterns provided (#18741) (34f4148)
misc: fix normalizing e2e project name and root (#18757) (b3a0c0e)
misc: format must exclude ignored patterns (#18670) (c479a54)
react: normalize remote name and directory correctly when using new project root format (#18770) (d1da057)
storybook: install nx/vite for non-buildable libs (#18778) (57463ed)
storybook: re-enable angular e2e build test (#18764) (5389397)
web: generate .swcrc file with modern defaults when creating new webapps (#18749) (750f485)
core: bring back setWorkspaceRoot util (#18811) (a146fcc)
core: do not use joinPathFragments for generating files (#18753) (bbae14b)
devkit: show example in deprecation message (#18823) (02c5aeb)
linter: enable analyzeSourceFile as needed when generating new lint project (#18769) (4846ae5)
testing: improve error message for ct generators (#18597) (f5d55e3)
vite: support incremental building when running 'serve' (#18797) (14506d2)
angular: buildable libs should lint correctly #18802 (#18837) (889f315)
angular: style=none should not create file #18785 (#18836) (577f820)
angular: use the correct output path for mf ssr #18849 (#18906) (5a06343)
bundling: fallback to manual file resolution if tsconfig-paths fails (#18477) (e3b513b)
core: check for lerna before parsing lockfiles to prevent errors (#18884) (e188775)
core: convert to monorepo generator should respect nested libs (#18795) (413e57f)
core: Ensure when converting to monorepo standalone libs have a readable name (#18887) (c48f3aa)
core: handle empty lines in dotenv files (#18829) (aa9526f)
core: keep existing name when converting project to a monorepo (#18910) (ec647e7)
core: load core plugins as part of loading plugins (#18826) (cf1175f)
core: merge implicit project dependencies only if found on new and matching projects (#18896) (7e50274)
core: sort objects when hashing them instead (#18897) (db31f30)
core: use correct break line char in deprecated generator message printed by the generate command (#18879) (86c21c6)
linter: do not break migration if eslint file is missing (#18762) (9fe9afd)
nextjs: Deprecate adding NX_ vars to Webpack Define (#18892) (da2a08e)
nextjs: improve e2e test by reusing the project (#18827) (34a7279)
node: pass projectNameAndRootFormat to js lib generator from nest lib generator (#18891) (74e5879)
nx-dev: fix intro page icons on safari (#18877) (00f68a9)
nx-dev: improve button shadow handling in nx-dev (#18870) (53da4e6)
nx-dev: improve mobile documentation header (#18871) (2383f7d)
nx-dev: rspack link in getting-started section (#18908) (45ec8ba)
nx-plugin: fix explicity obsolete type (#18888) (759c5e1)
nx: correct the message for the removal of a project that is still a dependency of other projects. (#18903) (70d3728)
storybook: increase timeout of angular e2e (#18831) (a009523)
testing: omit indexHtmlFile option for cy >12.17.0 for ng ct (#18839) (829076d)
webpack: use new watcher for webpack build coordination plugin (#18822) (c175f9b)
webpack: WebpackNxBuildCoordinationPlugin cancels inflight builds on new changes detected (#18883) (b5380d0)
angular: ngrx-feature-store should respect paths in names #18905 (#18913) (818d04c)
bundling: add faux-ESM files so "import" in Node works with both named and default exports (#18916) (99c44f9)
js: set external nodes when lockfile is not reprocessed ([#18944](https://togithub.com/nrwl/n

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-10-19T23_55_00_511Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-10-19T23_55_00_511Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_03_747Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/angular --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_06_070Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_06_826Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_09_146Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_09_936Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/cypress --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_12_013Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_12_764Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_15_091Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_15_872Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/eslint-plugin --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_17_789Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_18_511Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_20_767Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_21_554Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/jest --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_23_472Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_24_200Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_26_548Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_27_335Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/linter --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_29_418Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_30_196Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_33_337Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/workspace --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_35_348Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_36_129Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_38_553Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_39_408Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate nx<EMAIL_ADDRESS><EMAIL_ADDRESS>npm WARN cli npm v10.2.1 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/nx
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer nx@">= 15 <= 17" from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/devkit
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nx-squeezer/workspace
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx-squeezer/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/ubuntu/.npm/_logs/2023-10-19T23_55_42_253Z-eresolve-report.txt

npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR!  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-10-19T23_55_44_621Z-debug-0.log


test(ws): add e2e tests

This PR makes the following changes to the workspace controller:

Remove the +kubebuilder:validation:XValidation:rule="self == oldSelf" annotations for image config and pod config.
Comment out probes as they prevent pod creation when empty:probes:
  # startupProbe: {}
  # livenessProbe: {}
  # readinessProbe: {}

Fix typo in extraEnv NB_PREFIX value from "juptyerlab" to "jupyterlab".
Remove installation and uninstallation of Prometheus Operator and Cert Manager in e2e tests - before and after each test.
Create the default-editor service account and delete it after testing.
Create home PVC and data PVC, and delete them afterwards.
Apply some WorkspaceKind samples.
Apply some Workspace samples.
Check if the workspace pod is running.
Test if the pod is exposed correctly through the service and path generated from the NB_PREFIX environment variable.

@Adembc I have done the following changes in https://github.com/kubeflow/notebooks/pull/30/commits/61c85fa0c88149706f7a255f69ad6b4ed6723552

Auto detect the current kind cluster name for the kind load docker-image ... command.

@Adembc I have done the following changes in https://github.com/kubeflow/notebooks/pull/30/commits/16886cededb63db5f815f554fc85de69089597e5

Removed the tests which were failing because +kubebuilder:validation:XValidation:rule="self == oldSelf" was removed
Made the default image ghcr.io/kubeflow/notebooks/workspace-controller:latest (as this will be the image name once we release)
Grouped the samples under ./workspaces/controller/config/samples better to separate the "common" ones like ServiceAccount/default-editor and PVC/workspace-home-pvc from our actual custom CRDs.
Introduced a system to get Warning type Events from the StatefulSet and use them to pouplate the Workspace status.stateMessage when the Pod is missing.

note, this required adding a new Kubebuilder index on the .involvedObject.uid field of Events

Introduced new Workspace status.stateMessage information for cases when the Pod is unschedulable (e.g. due to no node meeting the CPU/RAM request)
Refactored the ./workspaces/controller/test/e2e/e2e_test.go:

to not run tests in the default namespace
to check that the Workspace status.state is Running
to properly run a curl pod that checks the service is up

Removed the now unused methods from ./workspaces/controller/test/utils/utils.go:

InstallPrometheusOperator()
UninstallPrometheusOperator()
UninstallCertManager()
InstallCertManager()


network_adapter_device_key option

Versions:

chef (13.5.3)
chef-provisioning (2.5.0)
chef-provisioning-vsphere (2.0.6)

Platform Details

Version of vSphere/vCenter: <IP_ADDRESS>00
Version of ESXi:

Scenario:
In an old version of kitchen-vsphere, it was possible to specify a network_adapter_device_key. I'm trying to upgrade our automation from kitchen-vsphere to kitchen-provision-vsphere , and I can't find the network_adapter_device_key option.
Is this a missing feature?
The issue we solved with the network_adapter_device_key option is described in this ticket.
Steps to Reproduce:
Try to converge  an osx vm.
Expected Result:
VM should create and become available for SSH
Actual Result:
Our machine starts just great, but never connects to the network because it doesn't see any network devices. Instead, I get a message which looks like
Power on VM [vm/node1-osx-10-9-75a3c422]
waiting for node1-osx-10-9-75a3c422 (50111929-da10-1cfc-b95e-ecc3b26e268b on
vsphere://vcenter-ci-dev.company.us/sdk?use_ssl=true&insecure=true) to be ready ...
....................................................................
# eventually timeout occurs

I think I answered where the device_key is being set, but not why my machines still fail to converge.
Apparently the network device is available, but doesn't have an IP address.

I solved the issue....sort of.
When I set a network_name to a network adapter on an OSX vm, it disconnects all network adapters. Apparently, I am able to clone an image and it will have an adapter by default, so a workaround is to just not set any adapters and let it figure itself out.
driver:
  name: vsphere
  driver_options:
    host: vcenter-ci-5.domain.us
    user: your_name
    password: your_mothers_maiden_name
    insecure: true
  machine_options:
    bootstrap_options:
      network_name: # if this is set, no network adapters will be set
        - 'VM LAN 10.0.x.x' # can't set this
      use_linked_clone: true
      datacenter: ci
      resource_pool: esxi-ci-14.domain.us


DirectConsumptionRate & SelfConsumtpionRate Anzeige mit zuviel Nachkommastellen

Describe the bug what do have
Guten Morgen,
die beiden im Titel genannten Entitäten werden mit mehr als 10 Nachkommastellen angezeigt.

Log details
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service gridboxconnector: starting
s6-rc: info: service gridboxconnector successfully started
s6-rc: info: service legacy-services: starting
[08:35:45] INFO: Starting GridboxConnector...
s6-rc: info: service legacy-services successfully started
total 12K
   4.0K drwxr-xr-x    2 root     root        4.0K Jul 10 08:35 .
   4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 08:35 ..
   4.0K -rw-------    1 root     root         114 Jul 10 08:35 options.json
{
  "username": "XXX",
  "password": "XXX",
  "wait_time": 10,
  "log_level": "INFO"
}total 16K
   4.0K drwxr-xr-x    1 root     root        4.0K Jul  9 14:16 .
   4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 08:35 ..
   4.0K drwxr-xr-x    3 root     root        4.0K Jul  9 14:15 GridboxConnector
   4.0K -rw-r--r--    1 root     root         494 Jul  9 14:15 cloudSettings.json
/build
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/build/GridboxConnector/__main__.py", line 31, in <module>
    options_json = json.load(options_file)
                   ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/__init__.py", line 293, in load
    return loads(fp.read(),
                 ^^^^^^^
AttributeError: 'str' object has no attribute 'read'
[08:35:49] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-linux-init-shutdown: fatal: unable to talk to shutdownd: Operation not permitted
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: Viessmann Gridbox Connector (edge)
 Viessmann Gridbox Connector (edge)
-----------------------------------------------------------
 Add-on version: 2.7.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.4  (aarch64 / yellow)
 Home Assistant Core: 2024.7.1
 Home Assistant Supervisor: 2024.06.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service gridboxconnector: starting
s6-rc: info: service gridboxconnector successfully started
s6-rc: info: service legacy-services: starting
[08:36:31] INFO: Starting GridboxConnector...
s6-rc: info: service legacy-services successfully started
total 12K
   4.0K drwxr-xr-x    2 root     root        4.0K Jul 10 08:36 .
   4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 08:36 ..
   4.0K -rw-------    1 root     root         114 Jul 10 08:36 options.json
{
  "username": "XXX",
  "password": "XXX",
  "wait_time": 10,
  "log_level": "INFO"
}total 16K
   4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 06:56 .
   4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 08:36 ..
   4.0K drwxr-xr-x    3 root     root        4.0K Jul 10 06:56 GridboxConnector
   4.0K -rw-r--r--    1 root     root         494 Jul 10 06:56 cloudSettings.json
/build
2024-07-10 08:36:35,824 __main__.py:61 INFO - {'batteries': [{'applianceID': 'a1731af4-0399-495b-92c2-523fd61ab681', 'capacity': 10000, 'nominalCapacity': 10000, 'power': -1626, 'remainingCharge': 4200, 'stateOfCharge': 0.42}], 'battery': {'capacity': 10000, 'nominalCapacity': 10000, 'power': -1626, 'remainingCharge': 4200, 'stateOfCharge': 0.42}, 'consumption': 628, 'directConsumption': 628, 'directConsumptionEV': 0, 'directConsumptionHeatPump': 0, 'directConsumptionHeater': 0, 'directConsumptionHousehold': 628, 'directConsumptionRate': 0.2747156605424322, 'grid': -32, 'gridMeterReadingNegative':<PHONE_NUMBER>, 'gridMeterReadingPositive':<PHONE_NUMBER>, 'heaters': [{'applianceID': '12bdd8ec-9b1e-465e-8f26-feae00e5af0f', 'power': 0, 'temperature': 51.5}], 'heating': 0, 'measuredAt': '2024-07-10T06:36:35Z', 'photovoltaic': 2286, 'production': 2286, 'selfConsumption': 2254, 'selfConsumptionRate': 0.9860017497812773, 'selfSufficiencyRate': 1, 'selfSupply': 628, 'totalConsumption': 628}

Version
No response

ne habs nur auch immer wieder vergessen das endlich mal gerade zu machen, danke für den hinweis.

2.7.4 auf edge

Jetzt bricht er nach dem Start wieder ab.
`  "username": "XXX",
"password": "XXX",
"wait_time": 10,
"log_level": "INFO"
}total 16K
4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 10:27 .
4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 10:42 ..
4.0K drwxr-xr-x    3 root     root        4.0K Jul 10 10:26 GridboxConnector
4.0K -rw-r--r--    1 root     root         494 Jul 10 10:26 cloudSettings.json
/build
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/build/GridboxConnector/main.py", line 59, in
viessmann_gridbox_connector.update_sensors(result)
File "/build/GridboxConnector/ha_viessmann_gridbox_connector.py", line 124, in update_sensors
self.direct_consumption_rate_sensor.set_state(round(float(measurement.get("directConsumptionRate", "0"))*100),2)
TypeError: Sensor.set_state() takes 2 positional arguments but 3 were given
[10:42:16] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Viessmann Gridbox Connector (edge)
Viessmann Gridbox Connector (edge)
Add-on version: 2.7.4
You are running the latest version of this add-on.
System: Home Assistant OS 12.4  (aarch64 / yellow)
Home Assistant Core: 2024.7.1
Home Assistant Supervisor: 2024.06.2
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service gridboxconnector: starting
s6-rc: info: service gridboxconnector successfully started
s6-rc: info: service legacy-services: starting
[10:43:23] INFO: Starting GridboxConnector...
s6-rc: info: service legacy-services successfully started
total 12K
4.0K drwxr-xr-x    2 root     root        4.0K Jul 10 10:43 .
4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 10:43 ..
4.0K -rw-------    1 root     root         114 Jul 10 10:43 options.json
{
"username": "XXX",
"password": "XXX",
"wait_time": 10,
"log_level": "INFO"
}total 16K
4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 10:27 .
4.0K drwxr-xr-x    1 root     root        4.0K Jul 10 10:43 ..
4.0K drwxr-xr-x    3 root     root        4.0K Jul 10 10:26 GridboxConnector
4.0K -rw-r--r--    1 root     root         494 Jul 10 10:26 cloudSettings.json
/build
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/build/GridboxConnector/main.py", line 59, in
viessmann_gridbox_connector.update_sensors(result)
File "/build/GridboxConnector/ha_viessmann_gridbox_connector.py", line 124, in update_sensors
self.direct_consumption_rate_sensor.set_state(round(float(measurement.get("directConsumptionRate", "0"))*100),2)
TypeError: Sensor.set_state() takes 2 positional arguments but 3 were given
[10:43:27] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`

ach mist, ich glaub ich muss echt mal 2 tage investieren in unit tests.
sorry,

Es läuft.

2.7.5 Commit 0191245


Dialogs theming wrong

Latest version (didnt test previous one) does the theming wrong.
When setting the Theme to dark (Theme.AppCompat instead of Theme.AppCompat.Light.DarkActionBar), the dialogs get weridly themed. Elements (like seekbar etc get the correct theme, but background and mainelements (Title, buttons etc) contain their LightTheme color.
AlertDialog.Builder themes correctly. Attached a screenshot showing an AlertDialog build by the builder ontop of a Material Dialog

For now you have to explicitly set the dialog dark theme through global theming or the Builder method.

Do you know how to retrieve the necessary values from the AppCompat theme?

I don't know of any good way to check for a light or dark theme. The accent
colors are already retrieved from your theme, the title and content should
be.
Feel free to make attempts yourself. I'm a little busy at the moment.
On Wed, Mar 18, 2015, 11:39 AM Paul Woitaschek<EMAIL_ADDRESS>wrote:

Do you know how to retrieve the necessary values from the AppCompat theme?
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/344#issuecomment-83050898
.

Themes are auto detected with the new release: https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


Allow for ApplicationSystemTest driver to be provided by CLI

As the developer I want to be able to override the default ApplicationSystemTestCase driver via an environment variable so that I can temporarily use the browser in non-headless mode in conjunction with debugger statements for troubleshooting.
# will run with default :headless_chrome driver
rails test:system

# will run with chrome
BROWSER_TEST_DRIVER=chrome rails test:system

Example to use: Configuring Rails system tests for headless and headfull browsers

Resolved by #12


ASR platform manager synchronization seems to be completely broken

See https://github.com/project-chip/connectedhomeip/pull/26361#pullrequestreview-1431308530
@tx2rx @andy31415

Note that I only reviewed PlatformManager and TimeSupport from https://github.com/project-chip/connectedhomeip/pull/26361 and both were broken.  I have extremely low confidence in any of the rest of it...

Also, where is _TryLockChipStack implemented for ASR? I don't see it.

Because in src/ , that is not used before. Just in case ,we will add it soon later

src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp may cause the same problem.

In addition, src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp may cause the same problem:
    BaseType_t eventReceived = pdFALSE;
    {
        // Unlock the CHIP stack, allowing other threads to enter CHIP while
        // the event loop thread is sleeping.
        StackUnlock unlock;
        eventReceived = xQueueReceive(mChipEventQueue, &event, waitTime);

StackLock lock; // should it open lock again? @bzbarsky-apple
}

refer https://github.com/project-chip/connectedhomeip/pull/19470

// should it open lock again?

It does, in the destructor of the StackLock.


In page Select Vega key - inconsistency

The designs include an in page select for the Vega key you are interested in.
This is something that is in the design system but none of the other pages include this, instead the user changes the active key in the wallet sidebar.
This ticket to make the pattern consistent across the site

suggest fix

withdraws: remove in page key select
rewards:  remove in page key select

Alternative: go through all other forms and update pattern

if we go with just withdraws and rewards:
this pattern exists that just confirms what key rather than giving you a select.


Crash when dragging lanes if there are two boards on screen

I noticed that the Board component crashes when the MOVE action is performed on a Lane.
This only happens when two different Boards are on screen at the same time.
The error I received is the following
BoardContainer.js:195 Uncaught TypeError: Cannot read property 'id' of undefined
    at BoardContainer.js:195
    at Array.map (<anonymous>)
    at BoardContainer.render (BoardContainer.js:194)
    at finishClassComponent (react-dom.development.js:8389)
    at updateClassComponent (react-dom.development.js:8357)
    at beginWork (react-dom.development.js:8982)
    at performUnitOfWork (react-dom.development.js:11814)
    at workLoop (react-dom.development.js:11843)
    at renderRoot (react-dom.development.js:11874)
    at performWorkOnRoot (react-dom.development.js:12449)
    at performWork (react-dom.development.js:12370)
    at performSyncWork (react-dom.development.js:12347)
    at requestWork (react-dom.development.js:12247)
    at scheduleWorkImpl (react-dom.development.js:12122)
    at scheduleWork (react-dom.development.js:12082)
    at Object.enqueueSetState (react-dom.development.js:6644)
    at Connect../node_modules/react/cjs/react.development.js.Component.setState (react.development.js:238)
    at Connect.onStateChange (connectAdvanced.js:205)
    at dispatch (createStore.js:173)
    at redux-logger.js:1
    at Object.moveLane (bindActionCreators.js:3)
    at BoardContainer._this.onLaneDrop (BoardContainer.js:130)
    at index.js:1
    at index.js:1
    at Object.handleDrop (index.js:1)
    at index.js:1
    at Array.forEach (<anonymous>)
    at index.js:1
    at t (index.js:1)
    at index.js:1

Fixed in the latest release...


Various issues with cell merging

When merging cells and in doing so creating overlapping merges ( i.e:  Merging A1:B2 and B2:C3 --> overlapping in B2 ) we don't get an exception but the writer will create a corrupt file that Excel then marks with "unreadable content found".
Solution:  Raise an exception if the new merge is overlapping with an existing merge

Further issues:

Method SET_MERGE: all input parameters are marked as optional - but omitting any will lead to unreadable content
Method SET_MERGE:  Input parameters for columns are typed strictly.  We should use type "simple" like in almost all other methods where we can pass the column either in character or in integer format
the way merges are stored is interesting but not very intuitive.  Unfortunately the relevant table holding the merge information is declared as "public".   Still I don't see anyone using that attribute directly instead of using method GET_MERGE or IS_MERGED.  Any vetos from the community before I switch that parameter to private and change the way merges are stored internally
Method DELETE_MERGE has no parameters and deletes the first merge???  What is that good for?  I propose to add an optional input parameter where a cell can be passed and the merge containing that cell will be removed.   Not passing anything or an empty cell should then delete all merges
Merging Cells will keep all information from the merged cells in the ouput-xlsx.  Opening that file will show the merged cells and the content from the top-left cell.  But when unmerging the cells the output is somewhat indifferent:
Example:
Merging A1:D4 and setting data into A1,B2,C3,D4 - Unmerging will show all 4 values
Merging A1:D4 and setting data into A1,B2,C3,D4 - Unmerging will put the value from B2 into A1
We should match EXCEL behaviour and save only the top-left cell-value when creating the output in ZCL_EXCEL_WRITER_2007

Thank you Stefan to point out these issues...
I'm agree on your comments, I haven't check the code, but they make absolutely sense.