primordic/IssueDupesLite huggingface dataset:
Repository: nrwl/nx-console

Issue #1731: VSCode: background resources consuming even after quit VSCode
Created: 2023-05-15T08:32:22Z
Current Behavior
When I completely quit the editor, seems that NX plugin continue to run in the background. I've tried to disable all the plugins one by one, and only NX plugin still continue to run after quit VSCode (cmd+q). If I disable this plugin, it doesn't appear in the running processes anymore after quit the editor.
Expected Behavior
It shouldn't be alive after quitting the editor.
Steps to Reproduce
Just enable this plugin and completely quit VSCode, then open Activity Monitor and in the Memory tab type "code" to find the running process.
Failure Logs / Images / Videos

Environment
MacOS: 13.3.1 2023 M2

Nx Console version: 18.1.1
VSCode version: 1.78.2

Duplicate issue #1801: VSCode extension stays in memory after VSCode is closed
Created: 2023-07-04T03:28:45Z
Current Behavior
I'm using NX Console VSCode extension, and whenever I close my VSCode, I see an orphan process in Activity Monitor. Quick check on empty profile (with only NX Console installed) shows, that the issue has to be in NX Console extension.
Expected Behavior
NX console should completely quit and free resources when VS Code exits. Not sure if that was regression.
Steps to Reproduce

Create a project with npx create-nx-workspace@latest myorg --preset=ts
Open the project in VS Code.
Close VS Code.
See 1 Code Helper process in Activity Monitor.

Repro video:

  
    
    

    Screen.Recording.2023-07-03.at.8.18.11.PM.mov
    
  

  

  


VS Code profile that can be used for repro:
nx-repro.code-profile.zip
Failure Logs / Images / Videos
Environment
NX Console extension version: v18.3.0
VS Code about info:
Version: 1.79.2 (Universal)
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:58:52.392Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin arm64 22.5.0
NX report:
▶ nx report

 >  NX   Report complete - copy this into the issue template

   Node   : 16.16.0
   OS     : darwin-arm64
   npm    : 8.11.0

   nx             : 16.4.2
   @nx/js         : 16.4.2
   @nx/workspace  : 16.4.2
   @nx/devkit     : 16.4.2
   @nrwl/tao      : 16.4.2
   typescript     : 5.1.6

Closing comment (2023-07-04T07:39:20Z): Thanks for reporting this, @akv-mshin! I'll close it as a duplicate of #1731 but I'll have a deeper look, this really sucks.
Repository: nrwl/nx-console

Issue #257: Provide a UI for running background tasks
Created: 2018-10-11T20:06:29Z
Will be closed by #251

Duplicate issue #81: task-runner component: Need more of an affordance when a task is running vs complete
Created: 2018-08-06T17:00:12Z

Closing comment (2018-10-11T20:09:38Z): Dup #257
Repository: nrwl/nx-console

Issue #194: windows download url link is broken
Created: 2018-09-08T04:14:11Z
cannot download from this link https://github.com/nrwl/angular-console/releases/download/v6.0.0-beta.2/AngularConsole-Setup-6.0.0-beta.2.exe.

Duplicate issue #197: Windows Version Download Link on Main Site gives 404
Created: 2018-09-09T23:42:05Z
The windows download link on https://angularconsole.com/ takes me to:
https://github.com/nrwl/angular-console/releases/download/v6.0.0-beta.2/AngularConsole-Setup-6.0.0-beta.2.exe
but the download link is
https://github.com/nrwl/angular-console/releases/download/v6.0.0-beta.2/Angular.Console.Setup.6.0.0-beta.2.exe

Closing comment (2018-09-10T05:19:16Z): Seems like a dupe of: #194
Repository: nrwl/nx-console

Issue #257: Provide a UI for running background tasks
Created: 2018-10-11T20:06:29Z
Will be closed by #251

Duplicate issue #13: Prompt when leaving schematics generate form
Created: 2018-07-06T19:08:55Z
If a user clicks away while they're in the middle of generating, prompt them to make sure.

Closing comment (2018-10-11T20:08:47Z): Dup #257
Repository: nrwl/nx-console

Issue #1197: Nx Console is empty
Created: 2021-12-15T16:03:05Z
i am using nx console on vscode, it stopped working recently after the recent changes of using nx tools to parse nx.json
my vscode is installed on windows 10 and my project is on wsl2
everything was working fine till the recent updates of nx console
see image below for the error i am getting on the output tab as well as the error popup window on the bottom right

Duplicate issue #1270: Better error reporting?
Created: 2022-04-15T15:05:11Z
This is both a feature request and a bug report I guess, but the focus is on providing better errors for users to debug their issues. I'll just use my current unsolved bug as a case.
Description
When NX Console fails it suggests checking the console outputs.
Since I updated to 13.10 nx console is not working anymore, and I really have no idea what it could be.
I don't mind opening the hood when necessary, but it's very hard when you can't get the root cause.
This is what I got:
Error loading Nx from the workspace. Falling back to extension dependency
local Nx dependency not found
    
Nx Console encountered an error when activating
Error: ENOENT: no such file or directory, stat '/Volumes/gits/mtb/node_modules/abortable-iterator'
I can't find any reference to this package, maybe some more context here would help.
Motivation
Debugging simple issues on your own, as I said this is not a bug report, as soon as I finish writing this I will just clone the repo and run the extension locally to get the stack trace.
Suggested Implementation
There a many ways to go about it when it comes to actually delivering meaningful informations and I guess maintainers/contributors would better know how to answer implementation details.
Settings interface
// settings.json
{
    ...
    "nxConsole.loggingLevel": "verbose"; // 

}
enum LoggingLevel {
  Never = "never",
  Default = "default",
  Verbose = "verbose"
}

Closing comment (2022-04-27T15:13:02Z): @Cammisuli Btw my error seems to be solved in master...
I tried on different OSes and computers, and I have the same error on each with the marketplace version.
But I cannot reproduce by running the extension locally from master.
I have this strange report in the debug:
Using local Nx package at /Users/mel/Desktop/gits/mtb/node_modules/@nrwl/workspace/src/core/file-utils.js
But everything is back to normal. Probably related to #1197 and #1155
Repository: nrwl/nx-console

Issue #2337: Nx console stuck on refreshing workspace on Intellij
Created: 2024-12-02T16:31:19Z
Current Behavior
Intellij is stuck on "Refreshing workspace"
Expected Behavior
The refresh workspace either errors out, or actually finish
Steps to Reproduce





I can't have a clear reproduction, as it's a random issues. It happens on any nx monorepo that uses inference, and maybe others that don't
I would love to have more logs (or know how to access them) to have a better idea of what is going on
Failure Logs / Images / Videos

Environment




Nx Console version: Intellij 2024.3 on 1.33.0


 NX   Report complete - copy this into the issue template

Node           : 20.11.1
OS             : darwin-arm64
Native Target  : aarch64-macos
yarn           : 4.3.1

nx                 : 20.1.2
@nx/js             : 20.1.2
@nx/jest           : 20.1.2
@nx/eslint         : 20.1.2
@nx/workspace      : 20.1.2
@nx/cypress        : 20.1.2
@nx/devkit         : 20.1.2
@nx/eslint-plugin  : 20.1.2
@nx/playwright     : 20.1.2
@nx/plugin         : 20.1.2
@nx/react          : 20.1.2
@nx/storybook      : 20.1.2
@nx/vite           : 20.1.2
@nx/web            : 20.1.2
@nx/webpack        : 20.1.2
typescript         : 5.5.4

---------------------------------------
Nx Powerpack
Licensed to Payfit for 90 users in 1 workspace until 4/30/2025


---------------------------------------
Registered Plugins:
./tools/nx-tools/src/plugins/main.ts
---------------------------------------
Community plugins:
rxjs : 6.6.7
---------------------------------------
Local workspace plugins:
	 @payfit/nx-tools

Duplicate issue #2379: Refreshing Nx workspace just reloading
Created: 2025-01-09T13:21:40Z
Current Behavior

Expected Behavior


Steps to Reproduce





Failure Logs / Images / Videos

Environment




Nx Console version:
VSCode version:

Closing comment (2025-01-10T06:13:04Z): duplicate of #2337
Repository: nukeop/nuclear

Issue #1008: Unable to open local files
Created: 2021-07-07T03:42:48Z
Platform:
Arch Linux - Linux workstation 5.12.14-arch1-1 #1 SMP PREEMPT Thu, 01 Jul 2021 07:26:06 +0000 x86_64 GNU/Linux.
WM: i3wm - i3 version 4.19.1 (2021-02-01) © 2009 Michael Stapelberg and contributors
please let me know if you need any more information
Nuclear version:
version 0.6.16 - Got this version through snap installer
Description of the issue:
Unable to open the files from local storage.
When I click on the "Local Library" from the left pane, I see the following message.

Duplicate issue #1304: cannot open local library - snap 
Created: 2022-08-03T11:21:44Z
This happens when I click on it.
It also needs ages to start.

Closing comment (2022-08-30T12:40:50Z): I can't open the local library at all. But other than that, this seems to be a duplicate of #1008.

It only happened on the snap version...
Repository: nukeop/nuclear

Issue #1629: Nuclear won't play and skip all tracks.
Created: 2024-07-09T23:36:02Z
Platform:
Fedora 40
Nuclear version:
v0.6.30
Description of the issue:
Nuclear won't play any track. It just removes the current track from list and skip to next and it does this for all tracks.

It looks like it can't fetch the data it needs.
Request URL: https://nuclear-verification-service.fly.dev/stream-mappings/top-stream
Request Method: POST
Status Code: 404
Remote Address: 66.241.124.185:443
Referrer Policy: strict-origin-when-cross-origin

Request URL: https://rr4---sn-3u-bh2z6.googlevideo.com/videoplayback?expire=1720589138&ei=8saNZvqdHM3j2roPnviM0Ak&ip=14.39.5.206&id=o-AKlnGcS2CMs_QqFdCc-isO3CVALXkTNgZk_L4EB1xPp6&itag=251&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=me&mm=31%2C26&mn=sn-3u-bh2z6%2Csn-oguelnzl&ms=au%2Conr&mv=m&mvi=4&pcm2cms=yes&pl=19&gcr=kr&initcwndbps=627500&bui=AXc671Itnj0TirNqBdwfWBl-WZ0ThWqWaZLUX-W0OaFuGuIUZe7ggznIf9f3Su11FOvotQjeFnECN_Nb&spc=NO7bAakf_HTSaH9uArxtgZDbyq1ER7Vo2r5eSyYgPFDOF5n2YQzuqqG1FMe3&vprv=1&svpuc=1&mime=audio%2Fwebm&ns=Bn7rryCuhzoq074ylJGRyqYQ&rqh=1&gir=yes&clen=3064603&dur=189.361&lmt=1714613339134523&mt=1720567028&fvip=1&keepalive=yes&c=WEB&sefc=1&txp=5532434&n=zFlc6XkvqV2eGaIAY&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cgcr%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRQIhAJJOKnCm_UNFMWyVhJt3pWjK4n_A-xFmKh6-CDuEHZQmAiAZ6c3ZnNN609Fkuw2HhfUdiY3HMQOTZIvIAwrW3iGVFg%3D%3D&sig=AJfQdSswRQIgeL74KOWb1Hk7tR2n4f1YASq-PdJewVTBuDgNtTVK8LQCIQCcCiR7QjQiVGxot_YnIdWRE_pySZhhOb6ndR-Ndd4UMw%3D%3D
Request Method: GET
Status Code: 403 Forbidden
Remote Address: 211.114.67.143:443
Referrer Policy: strict-origin-when-cross-origin

Duplicate issue #1634: No se reproduce ningún audio
Created: 2024-07-12T16:05:54Z
Hola
Me acabo de descargar NUCLEAR 0.6.30 y no se reproduce ningún audio.
He importado alguna lista de reproducción desde SPOTIFY y tampoco se oye nada.
Ayuda, por favor
Platform:
Nuclear version:
Description of the issue:

Closing comment (2024-07-12T16:43:36Z): This is a duplicate of #1629. Next time when reporting bugs, don't ignore the fields in the template. They're there for a reason.
Repository: nukeop/nuclear

Issue #1629: Nuclear won't play and skip all tracks.
Created: 2024-07-09T23:36:02Z
Platform:
Fedora 40
Nuclear version:
v0.6.30
Description of the issue:
Nuclear won't play any track. It just removes the current track from list and skip to next and it does this for all tracks.

It looks like it can't fetch the data it needs.
Request URL: https://nuclear-verification-service.fly.dev/stream-mappings/top-stream
Request Method: POST
Status Code: 404
Remote Address: 66.241.124.185:443
Referrer Policy: strict-origin-when-cross-origin

Request URL: https://rr4---sn-3u-bh2z6.googlevideo.com/videoplayback?expire=1720589138&ei=8saNZvqdHM3j2roPnviM0Ak&ip=14.39.5.206&id=o-AKlnGcS2CMs_QqFdCc-isO3CVALXkTNgZk_L4EB1xPp6&itag=251&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=me&mm=31%2C26&mn=sn-3u-bh2z6%2Csn-oguelnzl&ms=au%2Conr&mv=m&mvi=4&pcm2cms=yes&pl=19&gcr=kr&initcwndbps=627500&bui=AXc671Itnj0TirNqBdwfWBl-WZ0ThWqWaZLUX-W0OaFuGuIUZe7ggznIf9f3Su11FOvotQjeFnECN_Nb&spc=NO7bAakf_HTSaH9uArxtgZDbyq1ER7Vo2r5eSyYgPFDOF5n2YQzuqqG1FMe3&vprv=1&svpuc=1&mime=audio%2Fwebm&ns=Bn7rryCuhzoq074ylJGRyqYQ&rqh=1&gir=yes&clen=3064603&dur=189.361&lmt=1714613339134523&mt=1720567028&fvip=1&keepalive=yes&c=WEB&sefc=1&txp=5532434&n=zFlc6XkvqV2eGaIAY&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cgcr%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRQIhAJJOKnCm_UNFMWyVhJt3pWjK4n_A-xFmKh6-CDuEHZQmAiAZ6c3ZnNN609Fkuw2HhfUdiY3HMQOTZIvIAwrW3iGVFg%3D%3D&sig=AJfQdSswRQIgeL74KOWb1Hk7tR2n4f1YASq-PdJewVTBuDgNtTVK8LQCIQCcCiR7QjQiVGxot_YnIdWRE_pySZhhOb6ndR-Ndd4UMw%3D%3D
Request Method: GET
Status Code: 403 Forbidden
Remote Address: 211.114.67.143:443
Referrer Policy: strict-origin-when-cross-origin

Duplicate issue #1628: queue deleting itself
Created: 2024-07-09T20:31:19Z
Windows 11
0.6.30
Every time I try to play my playlist the song tries to play, and the millisecond the song starts playing the song deletes from the queue. This happens with every playlist. please help

Closing comment (2024-07-10T11:44:35Z): Duplicate: #1629
Repository: nukeop/nuclear

Issue #1629: Nuclear won't play and skip all tracks.
Created: 2024-07-09T23:36:02Z
Platform:
Fedora 40
Nuclear version:
v0.6.30
Description of the issue:
Nuclear won't play any track. It just removes the current track from list and skip to next and it does this for all tracks.

It looks like it can't fetch the data it needs.
Request URL: https://nuclear-verification-service.fly.dev/stream-mappings/top-stream
Request Method: POST
Status Code: 404
Remote Address: 66.241.124.185:443
Referrer Policy: strict-origin-when-cross-origin

Request URL: https://rr4---sn-3u-bh2z6.googlevideo.com/videoplayback?expire=1720589138&ei=8saNZvqdHM3j2roPnviM0Ak&ip=14.39.5.206&id=o-AKlnGcS2CMs_QqFdCc-isO3CVALXkTNgZk_L4EB1xPp6&itag=251&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=me&mm=31%2C26&mn=sn-3u-bh2z6%2Csn-oguelnzl&ms=au%2Conr&mv=m&mvi=4&pcm2cms=yes&pl=19&gcr=kr&initcwndbps=627500&bui=AXc671Itnj0TirNqBdwfWBl-WZ0ThWqWaZLUX-W0OaFuGuIUZe7ggznIf9f3Su11FOvotQjeFnECN_Nb&spc=NO7bAakf_HTSaH9uArxtgZDbyq1ER7Vo2r5eSyYgPFDOF5n2YQzuqqG1FMe3&vprv=1&svpuc=1&mime=audio%2Fwebm&ns=Bn7rryCuhzoq074ylJGRyqYQ&rqh=1&gir=yes&clen=3064603&dur=189.361&lmt=1714613339134523&mt=1720567028&fvip=1&keepalive=yes&c=WEB&sefc=1&txp=5532434&n=zFlc6XkvqV2eGaIAY&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cgcr%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRQIhAJJOKnCm_UNFMWyVhJt3pWjK4n_A-xFmKh6-CDuEHZQmAiAZ6c3ZnNN609Fkuw2HhfUdiY3HMQOTZIvIAwrW3iGVFg%3D%3D&sig=AJfQdSswRQIgeL74KOWb1Hk7tR2n4f1YASq-PdJewVTBuDgNtTVK8LQCIQCcCiR7QjQiVGxot_YnIdWRE_pySZhhOb6ndR-Ndd4UMw%3D%3D
Request Method: GET
Status Code: 403 Forbidden
Remote Address: 211.114.67.143:443
Referrer Policy: strict-origin-when-cross-origin

Duplicate issue #1639: Can't play any songs
Created: 2024-07-13T16:07:04Z
Platform:
-Window
Nuclear version:
-0.6.30
Description of the issue:
I simply can't get any songs to play, I tried changing the main plugin source(from youtube to soundcloud) but it didn't change anything and it still didn't work.

Here is the screen I get when I attempt to play a song("Accordion" in this case)

Closing comment (2024-07-13T16:08:32Z): Duplicate of #1629, we're working on it.
Repository: nukeop/nuclear

Issue #1671: Better handling of albums with multiple CDs
Created: 2024-08-15T21:19:13Z
When an album has multiple CDs the current display of them is a bit visually unpleasing.
All tracks are displayed in a list where multiple tracks have the same number:

Screenshot


Possible improvements I can imagine:

Keep a single list and prepend the CD number to the track number, maybe something like this: 1#01
One list for each CD



Lollypop example using multiple lists

Duplicate issue #1168: Don't attempt to play section titles
Created: 2022-01-31T00:40:40Z
Platform: Linux (Arch, using flatpak install)
Nuclear version: 0.6.16 (according to flatpak info org.js.nuclear.Nuclear)
Description of the issue:
Nuclear attempts to play section titles as if they were songs. For example:

Set the metadata provider to Discogs
Search for "Requiem", then find and click on this result
Hit play, the "tracks" Requiem D-Moll KV 626, I. Introitus, II. Kyrie, etc. will be included in the queue

The issue with this is that these are not real tracks, but rather just section titles. In the Discogs page of this album they show up as bold with a darker background to show that. I have only tested this problem on with the Discogs provider, though it may also be present on others.

Closing comment (2024-08-18T22:44:23Z): Going to be tracked in #1671 from now on
Repository: nukeop/nuclear

Issue #1629: Nuclear won't play and skip all tracks.
Created: 2024-07-09T23:36:02Z
Platform:
Fedora 40
Nuclear version:
v0.6.30
Description of the issue:
Nuclear won't play any track. It just removes the current track from list and skip to next and it does this for all tracks.

It looks like it can't fetch the data it needs.
Request URL: https://nuclear-verification-service.fly.dev/stream-mappings/top-stream
Request Method: POST
Status Code: 404
Remote Address: 66.241.124.185:443
Referrer Policy: strict-origin-when-cross-origin

Request URL: https://rr4---sn-3u-bh2z6.googlevideo.com/videoplayback?expire=1720589138&ei=8saNZvqdHM3j2roPnviM0Ak&ip=14.39.5.206&id=o-AKlnGcS2CMs_QqFdCc-isO3CVALXkTNgZk_L4EB1xPp6&itag=251&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=me&mm=31%2C26&mn=sn-3u-bh2z6%2Csn-oguelnzl&ms=au%2Conr&mv=m&mvi=4&pcm2cms=yes&pl=19&gcr=kr&initcwndbps=627500&bui=AXc671Itnj0TirNqBdwfWBl-WZ0ThWqWaZLUX-W0OaFuGuIUZe7ggznIf9f3Su11FOvotQjeFnECN_Nb&spc=NO7bAakf_HTSaH9uArxtgZDbyq1ER7Vo2r5eSyYgPFDOF5n2YQzuqqG1FMe3&vprv=1&svpuc=1&mime=audio%2Fwebm&ns=Bn7rryCuhzoq074ylJGRyqYQ&rqh=1&gir=yes&clen=3064603&dur=189.361&lmt=1714613339134523&mt=1720567028&fvip=1&keepalive=yes&c=WEB&sefc=1&txp=5532434&n=zFlc6XkvqV2eGaIAY&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cgcr%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRQIhAJJOKnCm_UNFMWyVhJt3pWjK4n_A-xFmKh6-CDuEHZQmAiAZ6c3ZnNN609Fkuw2HhfUdiY3HMQOTZIvIAwrW3iGVFg%3D%3D&sig=AJfQdSswRQIgeL74KOWb1Hk7tR2n4f1YASq-PdJewVTBuDgNtTVK8LQCIQCcCiR7QjQiVGxot_YnIdWRE_pySZhhOb6ndR-Ndd4UMw%3D%3D
Request Method: GET
Status Code: 403 Forbidden
Remote Address: 211.114.67.143:443
Referrer Policy: strict-origin-when-cross-origin

Duplicate issue #1633: Mejor
Created: 2024-07-12T14:40:41Z
Toda la musica

Closing comment (2024-07-12T14:48:11Z): I assume this is a duplicate of #1629
Repository: nukeop/nuclear

Issue #112: Crash with SIGSEGV on start on Debian Sid
Created: 2019-01-15T17:56:51Z
Tried to run with both the .AppImage and the .deb, even installed 410 packages of node to build it myself. All crash on start with SIGSEGV. I'm not sure how to get any extra info from the crashes so let me know what you need me to do.

Duplicate issue #117: Segfault on start
Created: 2019-01-16T08:17:16Z
Starting the AppImage for the first time shows the usual "do you want to integrate ... with your desktop environment" modal. After that, it consistently crashes. The deb release shows the same issues.
Platform: Ubuntu 18.10 64-bit
./nuclear-0.4.3-x86_64.AppImage
[1]    5067 segmentation fault (core dumped)  ./nuclear-0.4.3-x86_64.AppImage

Closing comment (2019-01-16T08:23:32Z): Pretty sure this is a duplicate of #112
Repository: nukeop/nuclear

Issue #1297: GPU process isn't usable. Goodbye.
Created: 2022-06-30T20:01:55Z
Platform:

Pop!_OS 22.04
NVIDIA MX150
NVIDIA driver 455

Nuclear version:
3f9007
Description of the issue:
Nuclear process crashes because of GPU process apparently, appimage & deb.
Using --no-sandbox as an argument seems to work to prevent this issue.
(node:54514) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `nuclear --trace-deprecation ...` to show where the warning was created)
[54514:0630/205745.096138:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

Searching this up online shows that it may be fixable by upgrading Electron.
Edit: Flatpak works

Duplicate issue #1320: nuclear-player-bin not launching and working in arch
Created: 2022-09-12T17:51:28Z
Platform:
Arch Linux x86_64
Nuclear version:
nuclear-player-bin 1662247798134:202293_9bf1a4ce1070f344d3a7a7195428aff0-2
Description of the issue:
Nuclear player is not launching when I try to launch it from menu.
[rounak@archissexy 23:20 ~]$ nuclear
      main › (node:31750) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `nuclear --trace-deprecation ...` to show where the warning was created)
Gtk-Message: 23:20:52.014: Failed to load module "colorreload-gtk-module"
Gtk-Message: 23:20:52.014: Failed to load module "window-decorations-gtk-module"
[31750:0912/232053.821168:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)
[rounak@archissexy 23:20 ~]$

Closing comment (2022-09-12T18:00:25Z): Duplicate of #1297 and #1268.  Try running with --no-sandbox, and please reopen if it doesn't help.
Repository: nukeop/nuclear

Issue #1310: Tauri
Created: 2022-08-19T19:17:53Z
have you ever consider using Tauri?
I think it is one of the alternatives that has more performance since Qt is not an option
In it you can use React too

Duplicate issue #1652: Rewrite: A big rewrite in Rust
Created: 2024-07-21T14:50:53Z
Dear coders, I'm a big fan of optimized, memory safe apps. so I would think its necessary to rewrite the backend(the electron part) in rust using Tauri framework.
I would prefer Tauri framework instead of Electron.
Consider checking out the benchmark: https://www.levminer.com/blog/tauri-vs-electron.
Checkout these: https://aptabase.com/blog/why-chose-to-build-on-tauri-instead-electron.

Closing comment (2024-07-21T15:10:29Z): This is a duplicate of #1310
Repository: nunit/nunit

Issue #1683: Existence of SerializableAttribute in .NET Core
Created: 2016-07-18T21:32:17Z
I have a question regarding the class SerializableAttribute that is being part of nunit.framework.dll for .NET Core.
I do understand that the class is a shim or polyfill (I don't really know the different) for .NET Core, because I've added the class myself in the assembly I am writing. My problem is that I get a compiler error stating that the class exists both in nunit.framework.dll and in my assembly. I can of course remove my declaration of  SerializableAttribute and reference NUnit from my assembly, but it feels wrong to reference something intended for tests.
That do you propose me to do?

Duplicate issue #1751: Serializable attribute exists in both System.Runtime.Serialization.Formatters and nunit.framework
Created: 2016-08-17T06:51:52Z
Hi I have issue with Serializable attribute
The type 'SerializableAttribute' exists in both 'System.Runtime.Serialization.Formatters, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'nunit.framework, Version=3.4.1.0.

How can I specify the package to use? My project.json :
{
  "version": "1.0.0-*",
  "testRunner": "nunit",
  "buildOptions": {
    "debugType": "portable",
    "allowUnsafe": true,
    "define": [ "WIN64" ]
  },
  "frameworks": {
    "netcoreapp1.0": {
      "buildOptions": {
        "define": [ "NETSTANDARD1_6" ]
      },
      "dependencies": {
        "NETStandard.Library": "1.6.0",
        "System.Runtime": "4.1.0",
        "System.Runtime.Serialization.Formatters": "4.0.0-rc3-24212-01",
        "System.Dynamic.Runtime": "4.0.11",
        "System.Threading.ThreadPool": "4.0.10",
        "System.Reflection.TypeExtensions": "4.1.0",
        "System.Diagnostics.StackTrace": "4.0.1",
        "System.Diagnostics.Process": "4.1.0",
        "System.Threading.Thread": "4.0.0",
        "dotnet-test-nunit": "3.4.0-beta-1",
        "NUnit": "3.4.1"
      },
      "imports": "dnxcore50"
    },
  },
  "runtimes": {
    "ubuntu.14.04-x64": {},
    "win10-x64": {},
    "win7-x64": {}
  }
}

Closing comment (2016-09-15T10:32:17Z): Is this a duplicate of #1683?
Repository: nunit/nunit

Issue #423: Integrate Code Coverage into CI
Created: 2014-12-15T18:43:06Z
I just wanted to put this out there as an idea and possibly a future task. I have been experimenting with OpenCover to run code coverage on the project and used ReportGenerator to generate HTML reports.
So far I've just run one of the framework tests, but we are getting 86.7% coverage which is pretty good. It does highlight some areas that are poorly tested, so I think it is a worthy exercise.
I am using the command line versions of both tools, but they are also available as NuGet packages that add MSBuild tasks.
An alternative might also be to use JetBrains' DotCover. They have a free license for open source teams that we could take advantage of.

Duplicate issue #883: Add code coverage to NUnit Solution
Created: 2015-10-10T02:45:11Z
We should be encouraging best practices, so it would probably be a good idea to determine the code coverage of our tests and automatically publish it in our README.
Some ideas, use OpenCover or Mono Code Coverage (monocov) for coverage and use Coveralls.net to report coverage to Coveralls.io.

Closing comment (2015-12-05T15:20:26Z): Closing as a duplicate of #423
Repository: nunit/nunit

Issue #2286: Add support for custom Task (i.e. ValueTask)
Created: 2017-06-29T07:46:48Z
Can you add support for custom Tasks, i.e. ValueTask (new in C# 7.0).
Right now looking at Assert.ThrowsAsync.

Duplicate issue #3023: NUnit runner fails when test method returns ValueTask<>
Created: 2018-09-18T09:15:46Z
Versions:
Nuget packages:
NUnit 3.10.1
NUnit3TestAdapter 3.10.0
System.Threading.Tasks.Extensions 4.5.1
Environment:
Windows 10.1803 17134.286
Visual Studio 2017 15.8.4
Steps to Reproduce:

Create C# Class Library, .NET 4.7.2
Add Nuget references for NUnit, NUnit3TestAdapter and System.Threading.Tasks.Extensions
Add Test Class:

using System.Threading.Tasks;
using NUnit.Framework;

namespace ClassLibrary1
{
    public class Class1
    {
        [Test(/*ExpectedResult = 100*/)]
        public async ValueTask<int> AsyncGetValueTest()
        {
            return await Task.FromResult(100);
        }
    }
}

Run test "AsyncGetValueTest"

Expected Behavior:
NUnit says "Missed ExpectedResult in Test attribute" or "Test methods with return type ValueTask<> are not supported"
Actual Behavior:
NUnit fails with an internal error:
System.NullReferenceException : Object reference not set to an instance of an object.
at NUnit.Framework.Internal.AsyncInvocationRegion.AsyncTaskInvocationRegion.WaitForPendingOperationsToComplete(Object invocationResult)
at C:\src\nunit\nunit\src\NUnitFramework\framework\Internal\AsyncInvocationRegion.cs:line 109
at NUnit.Framework.Internal.Commands.TestMethodCommand.RunAsyncTestMethod(TestExecutionContext context)
at C:\src\nunit\nunit\src\NUnitFramework\framework\Internal\Commands\TestMethodCommand.cs:line 96

Closing comment (2018-09-18T09:24:44Z): This is related to #2286, but you are right that we at least could give a better exception/warning message instead of a NRE until #2286 is solved.
Repository: nunit/nunit

Issue #3732: C# 9.0 covariant return types break the engine, aboring running the entire test class that contains such code
Created: 2021-01-17T23:01:27Z
I was trying to run tests for one class in my library, and it suddenly threw that issue in a class:
OneTimeSetUp: System.TypeLoadException : Return type in method '<type>.<function>()' on type '<type>' from assembly <assembly> is not compatible with base type method '<baseType>.<function>()'.

I was using NUnit 3.12.0, updated to 3.13.0, and now the tests will not even show a result; I'm assuming the issue silently occurs.
Basically, this issue applies to code of the following pattern:
class BaseClass
{
    virtual BaseClass Function();
}
class InheritingClass
{
    override InheritingClass Function();
}
For the specific case that I encountered, look at this commit's description.

Duplicate issue #3731: C# 9.0 covariant return types break OneTimeSetUp
Created: 2021-01-17T22:37:18Z

Closing comment (2021-01-17T23:33:35Z): @alfasgd Is this a duplicate of #3732?
Repository: nunit/nunit

Issue #2938: Test runner hangs after Assert.Fail in AfterTest
Created: 2018-07-19T21:23:10Z
I'm running an NUnit 3.9 test suite with nunit3-console, with a TestAction which asserts on some state after the fixture finishes. When the assert fails, it throws an exception and the runner hangs indefinitely. Are AfterTest implementations not allowed to assert or throw?
using NUnit.Framework;
using NUnit.Framework.Interfaces;
namespace Tests
{
    [TestFixture]
    [MyTestAction]
    public class MyTest
    {
        [Test]
        public void Pass() { }
    }

    public class MyTestActionAttribute : TestActionAttribute
    {
        public override void BeforeTest(ITest test)
        {
            base.BeforeTest(test);
        }

        public override void AfterTest(ITest test)
        {
            Assert.Fail("A test left resources open");
            base.AfterTest(test);
        }
    }
}

Duplicate issue #4024: Test process won't exit if AfterTest method throws
Created: 2021-12-20T21:11:48Z
If the AfterTest method of a TestActionAttribute throws during execution, the test process will get stuck and never exit. I included a small repro below. I only see this happen on .NET Framework (I'm using 4.7.2), with .NET Core working fine.
I tried running using nunit3-console without passing any argument other than the .dll (nunit3-console.exe Test.dll), and from VS test explorer. Had similar results in both cases.
Versions:

NUnit 3.13.2
NUnit.ConsoleRunner 3.12
NUnit3TestAdapter 4.0

public class ActionAttribute : TestActionAttribute
{
    public override void BeforeTest(ITest test)
    {
    }

    public override void AfterTest(ITest test)
    {
        throw new Exception("Error during teardown");
    }

    public override ActionTargets Targets => ActionTargets.Default;
}

[TestFixture]
[Action]
public class TestClass
{
    [Test]
    public static void Test1()
    {
        System.Threading.Thread.Sleep(1000);
    }
}

Closing comment (2022-04-26T03:19:42Z): I see similar but different behaviour under the following setup:

NUnit 3.13.2
NUnit3TestAdapter 4.0
Visual Studio 2022 17.1.5

With the above snippet and run under net462, net472, and net6, I see netfx tests pass as expected but it's the net6 one which hangs and never finishes. Commenting out the Thread.Sleep() doesn't change this, but commenting out throwing the Exception does allow the runner to see the test has finished. This is when they are all run in the same run in the VS test explorer and "Run All". When run individually it's a little different. net462 will complete, but both net472 + net6 seem to hang.
The same behaviour can also e replicated on the latest versions of each (NUnit 3.13.3 + NUnit3TestAdapter 4.2.1).
While I can't quite explain the difference, it does strike me as a duplicate of #2938 . It's also almost certainly, as described there, an issue with the framework as it is happening in both console runner and the vs test runner.
Repository: nunit/nunit

Issue #1358: TestContext.CurrentContext.Test.Properties does not contain value(s) from PropertyAttribute when using TestCaseAttribute
Created: 2016-03-18T14:43:20Z
NUnit version: 3.2.0 (from NuGet)
Test execution: Visual Studio adapter
Steps to reproduce:

Create a test method marked with [TestCase] and [Property("key", "value")]
Executed the test
Inspect the value of TestContext.Current.Test.Properties - it will be an empty collection, where it should have 1 value

Code example (failing test):
[TestCase(5)]
[Property("Answer", 42)]
public void TestCaseCanAccessItsOwnProperties(int x)
{
    Assert.That(TestContext.CurrentContext.Test.Properties.Get("Answer"), Is.EqualTo(42));
}
Previously reported on LaunchPad
This does not appear to be the same bug as #548 or #796.

Duplicate issue #2999: Unable to use [TestCaseCourse] and [TestOf] or [Category] attribute together in NUnit Test
Created: 2018-09-01T06:34:10Z
Ex::
[Test]
[TestCaseSource(typeof(), "")]
[TestOf("Functionality")][Category("Regression")]
public void TestA(int a, int b)
{
//***********************
//I want to access TestOf / Category Value inside with logic::
var testOf = TestContext.CurrentContext.Test.Properties["TestOf"];
But it is giving me error that Sequence contain no elements.
If i remove TestCaseSource then it works.

Closing comment (2018-09-03T19:56:09Z): This is a duplicate of #1358
Repository: nunit/nunit

Issue #2488: Improve performance of discovery/execution
Created: 2017-10-12T15:33:30Z
@OsirisTerje commented on Thu Sep 28 2017
It has been found that discovery of test cases are slowed down by the processing of traits.

Duplicate issue #2549: Parallel creation of xml result file
Created: 2017-11-09T10:30:33Z
This is a thought issue.
On my users systems, which are very slow, as previously noted (ARM 1Ghz or less), it can take as much as 10x time to build the xml result file as it took to actually run the tests!
Does it make sense to build the xml result file in parallel with the execution of the tests, on a separate thread?  Would this reduce total execution time for other environments as well?
Just interested in thoughts on this for now.

Closing comment (2017-11-12T17:14:26Z): @rprouse I don't see this as being at all the same as #2488. According to Navin's comment, there is a lot of time taken in the cross-appdomain calls for the test started and test finished event. That's actually separate from the generation of the XML, which happens before the events can be transmitted.
I've only been loosely following the discussion, but most of the tests seem to involve other software components, whether the adapter or the console. Granted that our users are affected by the interaction of these components with the framework, I nevertheless think we want to make framework-side-only tests in order to narrow down where the issues are taken.
As mentioned on another issue, I also have a strong suspicion that the adapter, which doesn't need the full XML file, may be inadvertently requesting it anyway by accessing the property that causes it to be generated. The engine design does allow a client that only needs the notifications to get them without ever requesting an aggregated result. Clearly, not doing something that doesn't need to be done is always a good idea when fixing performance issues.
It seems to me that this is easy for us to test because we have an understanding of how the framework works. We also have a strong motivation to make the framework efficient for all use, not just under a particular runner like the adapter.
Repository: nuxt-modules/i18n

Issue #1063: Nuxt@2.15.0 error - Cannot read property 'options' of undefined
Created: 2021-02-15T12:05:34Z
Version
nuxt-i18n: 6.20.0
nuxt: 2.15.0
Nuxt configuration
mode: 

 universal

Nuxt-i18n configuration
i18n: {
        locales: [...],
        defaultLocale: "en",
        vueI18nLoader: true
    }

What is Expected?
Not sure where the issue lies and what could have changed since the previous version of Nuxt, but the description of the issue should be self explanatory about what is failing and where.
What is actually happening?
Error when running npm run dev for Nuxt:

Result of console.log(config.module.rules) above failing line;

hooks.js logic which is looking for vue-loader when on the screenshot above there is an absolute path not equal to but including vue-loader:

Duplicate issue #1065: Error on the latest nuxt 2.15.0
Created: 2021-02-15T13:36:46Z
Version
nuxt-i18n: 6.20.0
nuxt: 2.15.0
Nuxt configuration
mode: 

 universal
 spa

Nuxt-i18n configuration
I don't think that this is relevant since it was perfectly working before but here we are.
[
  'nuxt-i18n',
  {
    defaultLocale: 'fr',
    detectBrowserLanguage: {
      useCookie: true,
      cookieKey: 'detected_locale',
      fallbackLocale: 'fr',
    },
    strategy: 'no_prefix',
    vueI18n: {
      fallbackLocale: 'fr',
      silentFallbackWarn: process.env.NODE_ENV === 'production',
      silentTranslationWarn: process.env.NODE_ENV === 'production',
      warnHtmlInMessage: 'error',
      escapeParameterHtml: true,
    },
    vueI18nLoader: true,
    vuex: {
      syncLocale: true,
      syncRouteParams: false,
    },

    lazy: true,
    langDir: 'locales/',
    locales: [
      {
        code: 'en',
        file: 'en.json',
        iso: 'en',
      },
      {
        code: 'fr',
        file: 'fr.json',
        iso: 'fr',
      },
    ],
  },
],

Reproduction Link
Not sure if it's needed in this case.
Steps to reproduce
I was in nuxt-i18n at 6.13.2, I did upgraded nuxt to the latest version @2.15.0 (from 2.14.6). It's now not working.
I upgraded nuxt-i18n to the latest 6.20.0 but it is not working neither.
What is Expected?
I expected to have it work as before.
What is actually happening?

Closing comment (2021-02-15T13:43:29Z): Duplicate of #1063
Just released https://github.com/nuxt-community/i18n-module/releases/tag/v6.20.1 with a fix.
Repository: nuxt-modules/i18n

Issue #152: Dynamic routes can hijack more specific routes
Created: 2018-11-05T14:42:45Z
Version
v5.3.0
Reproduction link
https://codesandbox.io/s/ly9pnqvp79
Steps to reproduce

Open codesandbox testcase
Add /us to the URL

What is expected ?
Page shows 'US' in big letters
What is actually happening?
Page shows 'FR'
Additional comments?
This error happens with dynamic nuxt routes. Those are named with _.vue (or _slug.vue but I haven't checked those).
The bug seems to be in the order in which routes are generated. For example in this case:
['nuxt-i18n', {
            locales: [
                {code: 'pt', iso: 'pt-PT', file: 'pt.json'},
                {code: 'fr', iso: 'fr-FR', file: 'fr.json'},
                {code: 'us', iso: 'us-US', file: 'us.json'},
                // ...
            ],
            // ...
            defaultLocale: 'fr',
        }],

routes are generated in the order in which languages are defined in locales array. With this setting, generated routes will look like this:
routes: [
        {
                path: "/pt/*",
                component: _865a92ea,
                name: "all___pt"
        },
        {
                path: "/*",
                component: _865a92ea,
                name: "all___fr"
        },
        {
                path: "/us/*",
                component: _865a92ea,
                name: "all___us"
        }
],

As you can see, the 'catch-all' route (default language) was placed before more specific 'us' route. With this setup, 'us' route is inacessible due to routes being matched by iterating routes in the order they are defined.
Problem can be fixed by generating routes in proper order.

This bug report is available on Nuxt community (#c168)

Duplicate issue #463: Index page with dynamic routes corrupt path on any non-default locale with prefix
Created: 2019-09-25T09:07:16Z
Version
6.2.1
Reproduction link
https://codesandbox.io/s/codesandbox-nuxt-y9vve?fontsize=14
Steps to reproduce
Trying to use dynamic routes on index page to apply single page for signin and signup. Just want to provide $route.params.id to  and show user specific data. But path mess up on page reload. Also working well on nested routes like '/about/:id'.
What is expected ?
clean path on index page reload like /ru or /en
What is actually happening?
/ru/ru or /en/en

This bug report is available on Nuxt community (#c308)

Closing comment (2019-10-21T20:19:40Z): Duplicate of #152.
Repository: nuxt-modules/i18n

Issue #1658: Per-component Translations
Created: 2022-11-19T09:59:37Z
In the documentation https://v8.i18n.nuxtjs.org/guide/per-component-translations the example doesn't seem to work. What shoud the configuration be to enable this funationality. setup: Nuxt 3.0.0  i18n v8 beta 4
Component
<template>
    <div>
      <p>{{ $t('welcome') }}</p>
    </div>
</template>

<script setup lang="ts">
const { t } = useI18n({
    useScope: 'local'
})
</script>

<i18n>
{
  "en": {
    "welcome": "Welcome"
  },
  "es": {
    "welcome": "Ola"
  }

}
</i18n>
Nuxt Config
export default defineNuxtConfig({
  srcDir: 'src/',
  typescript: {
    strict: true,
  },
  modules: [
    '@nuxtjs/i18n'
  ],
  i18n: {
    locales: [
      {
        code: 'en',
        file: 'en.json'
      },
      {
        code: 'es',
        file: 'es.json'
      },
    ],
    defaultLocale: 'en',
    lazy: true,
    strategy: 'prefix_except_default',
    langDir: 'locale',
    vueI18n: {
      legacy: false,
      locale: 'en',
    }
  }
});
Error in browser:
[intlify] Not found 'welcome' key in 'en' locale messages.

Duplicate issue #1659: useI18n() does not return locales when you use Per-component translations
Created: 2022-11-19T10:52:15Z
Version
@nuxtjs/i18n: 8.0.0-beta.4-27812700.b832f07
nuxt: 3.0.0
Nuxt configuration
Please change to [x] if relevant for this issue:

 Applies to a site deployed to a static server (site generated with nuxt generate)
 Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration
i18n: {
  locales: [
    {
      code: 'en',
      iso: 'en',
      name: 'English',
    },
    {
      code: 'ja',
      iso: 'ja-JP',
      name: '日本語',
    },
  ],
  vueI18n: {
    legacy: false,
  },
},
Reproduction Link

https://github.com/phanect/repro-nuxt-i18n-lang-switcher
Steps to reproduce
If you use per-component translations (i.e. add <i18n> block in the Vue SFC), useI18n() returns i18n object without locales, therefore the lang switcher does not work.
If you remove the <i18n> block from the SFC, useI18n() works properly and you can access i18n.locales properly, so I think <i18n> block causes this problem.

Create a page component and add following code in <script setup> block:

const { locales, t } = useI18n();
const switchLocalePath = useSwitchLocalePath();

Add <i18n> block in the page component
List available locales as following code:

<a
  v-for="locale in locales"
  :key="locale.code"
  :href="switchLocalePath(locale.code)"
>
  {{ locale.name }}
</a>
What is Expected?
List of available locales are shown
What is actually happening?
List of available locales are not shown

Closing comment (2022-11-19T12:28:17Z): @andreidmour I don't think this issue is a duplicate of #1658.
You didn't extract locales from the return value of useI18n() in #1658. This issue is about missing locales, so I think #1658 is a different problem from this issue.
Repository: nuxt-modules/i18n

Issue #2289: change available languages at runtime
Created: 2023-08-02T10:00:44Z
Describe the feature
there are times when i18n options need to be changed at runtime. now there is no way to do this, or I did not find how to do it. i see this one as Nuxt hook before initialization Vue I18n.
specifically, I need the functionality of limiting available languages based on information from useRequestHeaders
Additional information

 Would you be willing to help implement this feature?
 Could this feature be implemented as a module?

Final checks

 Read the contribution guide (The contribution guideline of nuxt-modules/i18n is compliant with Nuxt too).
 Check existing discussions and issues.

Duplicate issue #2795: How to add langs/locales list in nuxtjs-i18n configuration dynamically.
Created: 2024-02-15T12:16:58Z
Discussed in #2794

Originally posted by seetpalsingh February 15, 2024
Hi Can someone plz guide me , how i can update/add list of locales in i18n configuration.
In nuxt.config.js i don't have list of langs.
but on SSR I get list of locals/langs from strapi, that i want to add in i18 lang options list.
How i can do this.

Closing comment (2024-02-15T12:20:47Z): It's currently not possible to change the configured locales at runtime, closing this as it is a duplicate of #2289.
Repository: nuxt-modules/i18n

Issue #57: Warning vue router
Created: 2018-03-28T03:07:03Z
In all routes with more than one level i have this warning:
[vue-router] Route with name 'usuario-editar-perfil-es-es' does not exist
Examples:
Route: http://localhost:3000/usuario/editar-perfil
[vue-router] Route with name 'usuario-editar-perfil-es-es' does not exist
Route: http://localhost:3000/usuario/mis-anuncios
[vue-router] Route with name 'usuario-mis-anuncios-es-es' does not exist
But in routes with only one level it is okay, for example:
http://localhost:3000/ayuda
http://localhost:3000/quienes-somos
My Nuxt version is 1.4.0 and nuxt-i18n version is 2.9.1.
Configurations:
  defaultLocale: 'es',
  locales: [
    {
      code: 'es',
      iso: 'es-ES',
      name: 'Español',
      langFile: 'es-ES.js'
    },
    {
      code: 'en',
      iso: 'en-US',
      name: 'English',
      langFile: 'en-US.js'
    }
  ],
  loadLanguagesAsync: true,
  langDir: 'locales/'


This question is available on Nuxt.js community (#c46)

Duplicate issue #55: vue router warning
Created: 2018-03-27T05:31:29Z
In all routes with more than one level i have this warning:
[vue-router] Route with name 'usuario-editar-perfil-es-es' does not exist
Examples:
Route: http://localhost:3000/usuario/editar-perfil
[vue-router] Route with name 'usuario-editar-perfil-es-es' does not exist
Route: http://localhost:3000/usuario/mis-anuncios
[vue-router] Route with name 'usuario-mis-anuncios-es-es' does not exist
But in routes with only one level it is okay, for example:
http://localhost:3000/ayuda
http://localhost:3000/quienes-somos
My Nuxt version is 1.4.0 and nuxt-i18n version is 2.9.1.
Configurations:
  defaultLocale: 'es',
  locales: [
    {
      code: 'es',
      iso: 'es-ES',
      name: 'Español',
      langFile: 'es-ES.js'
    },
    {
      code: 'en',
      iso: 'en-US',
      name: 'English',
      langFile: 'en-US.js'
    }
  ],
  loadLanguagesAsync: true,
  langDir: 'locales/'


This question is available on Nuxt.js community (#c44)

Closing comment (2018-03-28T11:46:25Z): Duplicate of #57
Repository: nuxt-modules/i18n

Issue #389: Localized Paths reachable from other languages when using differentDomains
Created: 2019-08-11T19:42:50Z
Version
v5.3.0
Reproduction link
http://jsfiddle.com
Steps to reproduce

Set 'differentDomains' to true in i18n config.
Specify 'domain' for each item in locales
Add page-translations to 'pages'

// nuxt.config.js
{
  i18n: {
    differentDomains: true,
    locales: [
      {
        code: 'de',
        domain: 'de.website.com'
      },
      {
        code: 'en',
        domain: 'en.website.com'
      }
    ],
    parsePages: false, 
    pages: {
      login:{
        de:'/anmelden',
        en:'/login',
      },
}
What is expected ?
de subdomain
http://de.website.com/anmelden -> 200
http://de.website.com/login -> 404
en subdomain
http://en.website.com/login -> 200
http://en.website.com/anmelden -> 404
What is actually happening?
de subdomain
http://de.website.com/anmelden -> 200
http://de.website.com/login -> 200 // should be 404
en subdomain
http://en.website.com/login -> 200
http://en.website.com/anmelden -> 200  // should be 404
Additional comments?
It is working as expected when not using custom domains:
de subdomain
http://website.com/de/anmelden -> 200
http://website.com/de/login -> 404 // works
en subdomain
http://website.com/en/login -> 200
http://website.com/en/anmelden -> 404 // works

This bug report is available on Nuxt community (#c281)

Duplicate issue #980: How can I translate url using differentDomain=true?
Created: 2020-12-03T19:31:14Z
Hi there,
I am using the module with differentDomain=true, but I do not understand how can I do the routing.
I want to solve this problem:

mydomain.es/sobre-nosotros -> pointing to about.vue
mydomain.es/equipo -> pointing to about.vue

and

mydomain.com/about-us -> pointing to about.vue

Thank you in advance
using last version of nuxt and i18n-module

Closing comment (2020-12-14T08:46:39Z): I'll assume it's a duplicate of #389 then and close it.
If you have a more specific issue on top of that then please create a separate issue.