primordic/IssueDupesLite huggingface dataset:
Repository: nix-community/home-manager

Issue #1665: Installation failed. 'anything' missing, at ..."programs/matplotlib.nix"
Created: 2020-12-18T21:38:58Z
Issue description
Following the readme, and home-manager fails on installation.

Creating initial Home Manager configuration...

Creating initial Home Manager generation...

error: attribute 'anything' missing, at /nix/store/10p6r10mg4rcjn2y9r3zncxy0y813fqm-home-manager/home-manager/modules/programs/matplotlib.nix:26:28
(use '--show-trace' to show detailed location information)

There are 133 unread and relevant news items.
Read them by running the command 'home-manager news'.


Uh oh, the installation failed! Please create an issue at

    https://github.com/nix-community/home-manager/issues

if the error seems to be the fault of Home Manager.

I have no clue what matplotlib is. It's not being referenced in any config files.
This is on a clean nixos install with minimal packages.
Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.83, NixOS, 20.09.2290.647cc06986c (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.9`
 - channels(root): `"home-manager, nixos-20.09.2290.647cc06986c"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos

Duplicate issue #2072: Installing home-manager fails with "error: attribute 'anything' missing"
Created: 2021-06-05T13:59:03Z
Issue description
I've tried to install home-manager, following the instructions in the README.
When I run the following command:
> nix-shell '<home-manager>' -A install --show-trace
I get the following result:
Creating initial Home Manager generation...

error: attribute 'anything' missing, at /nix/store/ncd2gsy5wdngxk4bi458lg1da8hg191b-home-manager/home-manager/modules/programs/matplotlib.nix:26:28
(use '--show-trace' to show detailed location information)

There are 153 unread and relevant news items.
Read them by running the command 'home-manager news'.

Uh oh, the installation failed! Please create an issue at

    https://github.com/nix-community/home-manager/issues

if the error seems to be the fault of Home Manager.
Meta
Maintainer CC
I'm not sure who to ping.
Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.108, NixOS, 20.09.3684.9cea2bf89b5 (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(olivier-faure): `"home-manager"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Closing comment (2021-06-05T15:59:55Z): Duplicate of #1665, probably.
Repository: nix-community/home-manager

Issue #4313: Make `home.sessionVariables` work with nushell
Created: 2023-08-05T21:21:54Z
Description
Currently i have to set the following:
  home.sessionVariables = {
    SHELL = "nu";
    TERM = "alacritty";
    EDITOR = "vim";
  };

  programs.nushell.extraEnv = ''
    # FIXME(Krey): This should be handled in `home.sessionVariables`
    $env.SHELL = "nu";
    $env.TERM = "alacritty"
    $env.EDITOR = "vim";

    # Include local binaries
    $env.PATH = ($env.PATH | split row (char esep) | append ($env.HOME | path join '.local/bin'));
  ''; 
Because home.sessionVariables doesn't export the variables for nushell -> Make it work with nushell too?
Expected workflow:
  home.sessionVariables = {
    SHELL = "nu";
    TERM = "alacritty";
    EDITOR = "vim";
  };

  programs.nushell.extraEnv = ''
-    # FIXME(Krey): This should be handled in `home.sessionVariables`
-    $env.SHELL = "nu";
-    $env.TERM = "alacritty"
-    $env.EDITOR = "vim";
-
    # Include local binaries
    $env.PATH = ($env.PATH | split row (char esep) | append ($env.HOME | path join '.local/bin'));
  '';

Duplicate issue #4739: Make nushell use home.sessionVariables
Created: 2023-12-05T17:06:25Z
@Philipp-M
Nushell does not load /etc/profile or the local profile, so it is unaware of environment.variables, environment.sessionVariables (not sure whats the difference between the 2) and home.sessionVariables entirely. This breaks stuff like programs.helix.defaultEditor. Could you make it so it uses them by default?

Closing comment (2024-06-04T03:49:33Z): Duplicate of #4313. Closing.
Repository: nix-community/home-manager

Issue #2659: Need mechanism to activate sessionVariables in Wayland sessions
Created: 2022-01-23T06:04:51Z
Description
As far as I can tell there's no way, or workaround, to activate sessionVariables in a wayland session. We should rig something up, if possible. (That way I don't have to remember to start Firefox from a terminal).

Duplicate issue #3100: bug: Session variables are not set in terminal window when logging into Wayland session, but are enabled with Xorg
Created: 2022-07-19T18:55:53Z
Is there an existing issue for this?

 I have searched the existing issues

Issue description
When setting a session variable such as $EDITOR via home.sessionVariables, the variables are loaded in Xorg, but not in Wayland.
I am choosing the session via GDM.
My terminal is kitty.
My shell is nushell.
My home-manager configuration: https://github.com/schuelermine/home-manager-configuration
I have since switched to systemd.user.sessionVariables. The last commit to use home.sessionVariables is 557de379dd0eb144cae5833efc2ad22d43b875bc.
My system configuration: https://github.com/schuelermine/nixos-configuration
Maintainer CC
No response
System information
- system: `"x86_64-linux"`
 - host os: `Linux 5.18.10, NixOS, 22.11 (Raccoon), 22.11.20220712.68c63e6`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos, nixpkgs"`
 - channels(anselmschueler): `""`
 - nixpkgs: `/nix/store/ia11pz7v8wag5gh54bbnl5c87qc9cjm7-source`

Closing comment (2024-01-14T21:03:55Z): This seems to be a duplicate of #2659
Repository: noah-nuebling/mac-mouse-fix

Issue #855: One button on MS Ergonomic Mouse not recognized [bug]
Created: 2024-02-26T15:13:57Z
Description
Hi Noah,
I'm on v3.0.1, and trying to configure the blue "Windows" key of the MS Sculpt Ergonomic Mouse.
MMF shows a middle button, a button 4 and button 5. Middle button is the mouse wheel (works!) and button 4 is the side button below the Windows button, and I can configure that as I wish. But nothing I do for button 5 does anything. It also doesn't reconize an event when I click in the   field above the list for that one...
Any ideas?
Steps to reproduce
–
Context
Mac Mouse Fix Version: 3.0.1
macOS Version: 14.2.1 (23C71)
Mouse Model: Microsoft Sculpt Ergonomic Mouse
Additional Comments
–

Console Logs
–
Crash Reports
–

Duplicate issue #853: MacMouseFix not finding Logitech  M575 3rd and 4th button [bug]
Created: 2024-02-23T15:52:00Z
Description
While I have buttons set up in the app, those buttons don't launch the MMF features expected.  Connected over bluetooth.
Steps to reproduce

Opened MMF
clicked Buttons
3., moved mouse pointer inside the + field
buttons 3 and 4 didnt work
gave up waited til trial expired, realized this was still a problem and whoops here we are.

Context
Mac Mouse Fix Version: 3.0.1
macOS Version: 14.3.1
Mouse Model: logitech m575
Additional Comments
–

Console Logs
–
Crash Reports
–

Closing comment (2024-03-13T13:23:44Z): Potentially duplicate of #855
Repository: noah-nuebling/mac-mouse-fix

Issue #945: Support saved profiles for different mice [enhancement]
Created: 2024-05-09T09:43:16Z
Description
Add the ability to save a 'profile' of customization options to use for different hardware mice
Rationale
I frequently switch between two mice (one for work/general productivity and one for gaming) which have different button configurations and would like for the tool to either:

Detect the current device in use, and recall the last saved customization settings for that device
OR
Allow the saving of customization options into 'profiles' which can be switched between

Additional info
Loving the app so far! Thanks for putting in the time to create this tool :)

Duplicate issue #982: Profile support (support for switching between office/home mouse) [enhancement]
Created: 2024-06-03T17:17:49Z
Description
Support for profiles / different configurations per mouse.
Rationale
I have 2 different mice, 1 at home and 1 at work. I'd like to have different configurations for each mouse.
Ideally if it could auto detect what mouse is connected and automatically select the correct profile.
Additional info
Love the app!

Closing comment (2024-06-03T17:28:26Z): Seems to already exist issues for this. Duplicates:

#945
#864
(#859)
Label: 

  Profiles / Presets / Specific Settings
  Issue Category


You can close this one as a duplicate if you want.
Repository: noah-nuebling/mac-mouse-fix

Issue #413: Mouse scrolling with wheel doesn't work on iTerm2 if Smooth Scrolling is enabled (Beta 4) [bug]
Created: 2022-10-20T10:27:38Z
Description
I think MMF 3.0.0 Beta 3 didn't have this issue, but Beta 4 has.
Steps to reproduce

Enable Mac Mouse Fix 3.0.0 Beta 4 (19384)
Enable Smooth Scrolling
Try scrolling with the wheel on iTerm2

Context
Mac Mouse Fix Version: 3.0.0 Beta 4
macOS Version: 12.0.1 (21A559)
Mouse Model: –
Additional Comments
–

Console Logs
–
Crash Reports
–

Duplicate issue #425: Scrolling bug on Ventura [bug]
Created: 2022-10-26T22:44:12Z
Turning on smooth scrolling actually disables mouse scrolling on Ventura

Closing comment (2022-10-27T00:52:17Z): I think this is the same as #413? I've been using HEAD for a few days and it's been fixed.
Repository: noah-nuebling/mac-mouse-fix

Issue #976: Can't be used offline because it periodically checks the license validity online [other]
Created: 2024-05-30T22:03:49Z
After buying and activating Mac Mouse Fix, it will eventually disable itself and ask for payment if it can't periodically confirm the license online, apparently.
You can't take your computer to your internet-less getaway and keep using Mac Mouse Fix. You'll also need to whitelist it if you use apps like Little Snitch or Lulu to manage your apps' internet access. That's all I wanted to say.

Duplicate issue #1194: Prompt to purchase license after system restart [bug]
Created: 2024-11-20T18:19:00Z
Description
Even though I have already purchased Mac Mouse Fix license, on system restart I sometimes get a notification that trial period is over and I have to purchase license. Furthermore, it disables Mac Mouse Fix toggle. When I check in the app though, it seems to acknowledge that license is purchased and activated by the "Thank you for buying Mac Mouse Fix!" message at the bottom of the About tab.
Steps to reproduce

Enable "Allow in Background" option for Mac Mouse Fix
Restart the system
Observe the notification

Context
Mac Mouse Fix Version: 3.0.3
macOS Version: 15.1.1 (24B91)
Mouse Model: N/A
Additional Comments
There might be some race with license check and message being displayed.
Let me know if you aren't able to reproduce this issue and it's related to my machine configuration, I'll try to attach logs if possible or provide more relevant details.

Console Logs
–
Crash Reports
N/A

Closing comment (2024-11-20T18:25:24Z): Just scrolled through issues and it might be related to or duplicate of #976 or #1136, however the described behavior is slightly different, I never had to reenter the license key. It could be that connecting to Wi-Fi takes some time on my setup, prompting the message
Repository: noah-nuebling/mac-mouse-fix

Issue #661: Support of click and drag with reversed direction [enhancement]
Created: 2023-09-11T06:32:23Z
Description
Hi, this is a letter from the huge fan of the app.
I just wanna say thank you for your efforts and work! I am totally fine with current features, but just a little suggestion, can we make click and drag support reversed direction option on the beta version? Right now I am using beta 6 version, I found there is beta version which is better then the release, but that drag direction thing is different from what I am used to.
Rationale
Because sometimes the drag direction are different based on user's habit.
Say some one is used to the apple's natural direction(like me), and some one is used to Windows direction setting.
Additional info
–

Duplicate issue #705: "Invert" option for "Scroll & navigate" [enhancement]
Created: 2023-11-05T14:31:31Z
Description
Hello, I would like an option to have the "Scroll & navigate" click and drag action invert the movement - so that when I click and drag up, the page actually scrolls up (like if I dragged it with my finger on the iPhone).
Rationale
This feels natural to me, as it would work just on the touchscreen devices.
Additional info
–

Closing comment (2023-11-10T16:29:14Z): Possible duplicate of #661
Repository: noah-nuebling/mac-mouse-fix

Issue #479: Please bring back options for buttons menu
Created: 2023-01-06T16:14:45Z
Removed several options from the "Click", "Click and Hold" and "Click and Scroll" Actions because I thought they were redundant since the same functionality can be achieved otherwise and since this cleans up the menus a lot. Will bring those options back if people complain. So if you miss those options - please complain.

Registering my complain. It is super helpful to see something selected from the app menu than setup individual keyboard shortcuts (which I usually override myself using karabiner anyway) and than indirectly setting them via app. Please bring it back!!

Duplicate issue #580: Beta does not allow Mission Control to be assigned to a click [bug]
Created: 2023-05-23T11:33:36Z
Description
In 2.0 you can assign Mission Control to a button. I use that a lot. Love it.
Steps to reproduce

Install beta.
Try and assign Mission Control to a click.

Context
Mac Mouse Fix Version: 3.0.0 Beta 6
macOS Version: 13.4 (M2 Pro)
Mouse Model: Evoluent VerticalMouse VMDL Large, Right Hand Ergonomic Mouse, Wired
Additional Comments
Love the app. Bought a license for the beta. This is the best in category for sure!

Console Logs
–
Crash Reports
–

Closing comment (2023-05-24T19:20:40Z): Possibly related to - #479
Repository: noah-nuebling/mac-mouse-fix

Issue #1314: blacklist for apps or shortcut [enhancement]
Created: 2025-03-05T11:47:34Z
Description
A blacklist for apps that disables custom buttons and/or scrollwheel enhancement when said App is on top.
As a less ideal solution a keyboard shortcut to enable custom button and/or SW Enhancement could work
Rationale
When using applications that fully uses all the mouse buttons (fps, 3d applications)  the custom buttons becomes a problem
an automatic way to disable the customizations would be fantastic
Additional info
–

Duplicate issue #1327: Option to disable on specific applications [enhancement]
Created: 2025-03-19T03:14:24Z
Description
to upgrade and buy version 3 i need to be able to disable some functions automatically whenever im using blender and moonlight like i do with version2
Rationale
causes issues with scrolling
Additional info
–

Closing comment (2025-03-19T03:15:02Z): duplicate of #1314
Repository: noah-nuebling/mac-mouse-fix

Issue #86: Allow button mapping to horizontal presses of the scroll wheel [enhancement]
Created: 2021-04-14T04:01:03Z
Description
I would like to be able to map actions to horizontal presses of my mouse's scroll wheel. For instance, when I press the scroll wheel left, I would like it to take me to workspace to the left. I know that the beta version of Mac Mouse Fix supports button mapping, but I cannot get it to recognize horizontal presses of the scroll wheel as buttons. I know this is possible because it works in Logitech Options software, but I would prefer to use Mac Mouse Fix because it seems to be more lightweight and supports smooth scrolling which is hard to go without.
Rationale
If I could press my scroll wheel left or right to switch workspaces, then that would free up the side buttons on my mouse. I would then use the side buttons for going back and forward. I have gotten used to using the mouse's side buttons as back and forward buttons while using Windows, and it feels a little weird coming to MacOS and having those buttons control workspaces. I know that I can them to be back and forward buttons, but I cannot go without workspace buttons on my mouse. That is a must. It would be great if I could have both by moving my scroll wheel left and right to change workspaces.
Additional info
If this is too difficult to implement, don't sweat it. I love Mac Mouse Fix and would have a difficult time using a mouse on MacOS if it weren't for the software. Thanks for all the work you've put into it!

Duplicate issue #163: Hi! Can you please add functionality for left and right middle click? [enhancement]
Created: 2021-10-17T05:33:38Z
Description
Thank you for your hard time and community to create and improve the great app.
Rationale
The Logitech mouse has left and right middle click functionality, so I thought it would be great if you did. We can go backward and forward when using Safari, Finder, System Settings.

Closing comment (2021-11-26T10:46:46Z): I think this might be a duplicate of #86
Repository: noah-nuebling/mac-mouse-fix

Issue #162: Side buttons app specific [enhancement]
Created: 2021-10-16T13:49:27Z
Description
Would it be possible to set side buttons option per application?
Rationale
For example option "Back and Forward" works well for Finder and Chrome, but it's not working for other apps (example Football Manager game where only "Side button click" option works.).
Additional info
–

Duplicate issue #193: Different software uses different key bindings [enhancement]
Created: 2022-01-06T07:10:57Z
Description
The app-specific settings have too few controls for different apps, and I hope to have custom button4 button5 function settings
Rationale
I mainly use the side key to switch tab pages in the browser, and set the binding to cmd tab and cmd shift tab in chrome, and I have multiple browsers, I hope this configuration can be copied to firefox for use
Other software cmd tab may be useless. For example, in vscode, I want the side key to control the code jump, and I need to bind ctrl - and ctrl shift -
Additional info
–

Closing comment (2022-09-01T13:14:58Z): +1, very similar to #162
Repository: noah-nuebling/mac-mouse-fix

Issue #661: Support of click and drag with reversed direction [enhancement]
Created: 2023-09-11T06:32:23Z
Description
Hi, this is a letter from the huge fan of the app.
I just wanna say thank you for your efforts and work! I am totally fine with current features, but just a little suggestion, can we make click and drag support reversed direction option on the beta version? Right now I am using beta 6 version, I found there is beta version which is better then the release, but that drag direction thing is different from what I am used to.
Rationale
Because sometimes the drag direction are different based on user's habit.
Say some one is used to the apple's natural direction(like me), and some one is used to Windows direction setting.
Additional info
–

Duplicate issue #707: Add natural direction option for Spaces and Mission Control [enhancement]
Created: 2023-11-14T23:35:15Z
Description
When I configure:
Click and Drag: Spaces and Mission Control
Current behavior:
Click and drag to the right: switching to right space
Click and drag to the left: switching to left space
Desired behavior:
Click and drag to the right: switching to left space
Click and drag to the left: switching to right space
Rationale
Current  click and drag works by switching spaces in the same direction as mouse moves. I think moving through spaces in the opposite direction would make this feature to feel more natural.
I want to switch my spaces by middle clicking and dragging the whole desktop. This will allow the drag and drop feeling of this feature. Imaging the wallpaper to be a canvas in an image editing software and to be able to click and drag the canvas.
Additional info

Closing comment (2023-11-14T23:39:20Z): Related to #661
Repository: node-inspector/node-inspector

Issue #694: ENOENT after uninstalling Chrome Canary
Created: 2015-07-15T10:03:09Z
After the uninstallation, node debug still tries to launch %AppData%\Local\Google\Chrome SxS\Application\chrome.exe. Have tried reinstalling node-inspector.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Duplicate issue #732: new_chrome.exe ENOENT
Created: 2015-08-31T05:19:19Z
Hi all,
I do not know for sure what happened. I installed and used node-inspector without problem until yesterday. And then the Chrome browser lost his icon (but still worked), I uninstalled and reinstalled Chrome. After that whenever I tried to run node-debug my_app.js, I've got this message
_Debugger listening on port 5858
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn C:\Program Files (x86)\Google\Chrome\Application\new_chrome.exe ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
at child_process.js:1144:20
at process.tickCallback (node.js:355:11)
The directory C:\Program Files (x86)\Google\Chrome\Application\ has just chrome.exe
I removed and reinstalled node-inspector and Chrome browser also restarted my PC many times but the error still persists. I made a copy of chrome.exe and renamed it new_chrome.exe, the error's gone but node-inspector doesn't work (no new debug window).
Have anyone any idea of this error or how to config the node-debug to have it run chrome.exe instead of new_chrome.exe ?
Thanks for your help

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing comment (2015-09-06T21:40:11Z): This seems very weird (new_chrome.exe thing), though the file not found error seems a bit similar to #694
Can you open
~/.config/browser-launcher2 in git bash, or
%HOMEDRIVE%%HOMEPATH%/.config/browser-launcher2 in cmd
and delete config.json and check again?
Repository: node-inspector/node-inspector

Issue #903: enter key in console and "add watch expression" performs line-break not execute
Created: 2016-08-11T02:34:20Z
When entering commands/variables in the console (both break-point and non-break-point scenarios) or when specifying a variable under "add watch expression" the "enter" key does not execute the command/variable, but does a line-break instead. I could not find any other way to actually execute the command in the console. How can this behavior be changed or is this a bug? Thank you very much.
node-inspector version 0.12.8
nodejs 5.12.0
chrome Version 54.0.2824.0 dev-m (64-bit)

Duplicate issue #970: Return key just adds newlines in watch or console windows 
Created: 2017-01-24T19:19:11Z
version 0.12.8, Mac OS X Yosemite
Return key in watch expressions just adds a newline in the variable name pane. If I click outside the pane, then the variable is accepted and I get a value.
In the console, same behavior except clicking outside the console window doesn't help; I am unable to evaluate anything in the console.

Closing comment (2017-02-01T18:38:02Z): @JeffML this is a duplicate of #903.
Repository: node-inspector/node-inspector

Issue #29: can't view long strings it is always 'foo ...(253)'
Created: 2010-12-30T23:45:22Z
can't view long strings it is always 'foo ...(253)' everywhere

Duplicate issue #201: Evaluate in console showing truncated string
Created: 2013-08-20T13:32:24Z
Is this a new bug because previously i was able to see long string in console???

Closing comment (2014-01-16T08:10:36Z): Please try the latest version from master, the limit was raised to 10.000 characters in #272.
npm install -g node-inspector/node-inspector

I am closing this issue as a duplicate of #29.
Repository: node-inspector/node-inspector

Issue #823: Complete application crash when console.log()ing an object
Created: 2016-02-10T13:41:00Z
node v4.2.6
Node Inspector v0.12.6
On tracing it the crash occurs in vm.js.
exports.runInDebugContext = function(code) {
  return binding.runInDebugContext(code);
};
Called from util.js:
function ensureDebugIsInitialized() {
  if (Debug === undefined) {
    const runInDebugContext = require('vm').runInDebugContext;
    Debug = runInDebugContext('Debug');
  }
}

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Duplicate issue #807: Node-debug doesn't work
Created: 2016-01-14T05:41:48Z
Node-debug cause error:
$ node-debug test_file.js
Node Inspector is now available from http://127.0.0.1:8080/?ws=127.0.0.1:8080&port=5858
Debugging `test_file.js`

internal/child_process.js:298
    throw errnoException(err, 'spawn');
    ^

Error: spawn ENOTDIR
    at exports._errnoException (util.js:874:11)
    at ChildProcess.spawn (internal/child_process.js:298:11)
    at exports.spawn (child_process.js:339:9)
    at checkOthers (/Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:124:16)
    at checkDarwin (/Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:113:3)
    at next (/Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:185:3)
    at /Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:202:4
    at /Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:105:7
    at Object.getPath [as path] (/Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/darwin/chrome.js:6:10)
    at /Users/mysov/.nvm/versions/node/v4.2.1/lib/node_modules/node-inspector/node_modules/biased-opener/node_modules/browser-launcher2/lib/detect.js:100:21
Debugger listening on port 5858

Node.js v4.2.1
Node Inspector v0.12.5
OS: Mac OS X 10.11.1

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing comment (2016-02-10T21:57:21Z): Curious, try node --debug test_file.js and report if you get a crash with that alone. I'm having issues and tried to run the old way ( with --debug then node-inspector ) and my app is crashing with just --debug meaning is has nothing to do with node-inspector and I'm presently suspecting it's related to #823 since I'm lazy about .dir() vs .log() while in development (rarely use console in production thanks to Winston).
Repository: node-inspector/node-inspector

Issue #220: not working with adblock extension
Created: 2013-09-20T23:50:50Z
hi
i just tried out to debug the hello world program but nothing seems to work. could it be that node v0.10 is not supported?
i tried the npm version.
i would love to integrate node-inspector into node-mirror. but so far i cant seem to get it to work.
best wishes for your awesome attempt.
sol

Duplicate issue #228: Security warning in Chrome
Created: 2013-10-11T23:31:11Z
I wasn't able to get node-inspect to actually run in the browser because of a security exception with one of the included javascript files.
The error I was getting was:
Refused to load the script 'http://www.superfish.com/ws/sf_preloader.jsp?dlsource=wxpifdx&CTID=cool3_measure&userId=ODNGOTU0NzYtMkREMS00OE&ver=12.2.14.62' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval'".
View.js:495
Element.appendChild View.js:495
superfish.b.inj sf_main.jsp:67
loadApp sf_main.jsp:122
run sf_main.jsp:131
(anonymous function) sf_main.jsp:141
(anonymous function)
I was able to get around this by commenting out a line in the html file, https://github.com/node-inspector/node-inspector/blob/master/front-end/inspector.html#L32
I'm sure there is a correct setting to be secure but not cause an error, but I don't know what it should be.
Environment:
red hat linux enterprise 6
chrome 25

Closing comment (2013-10-13T10:08:14Z): Hi @pete-the-pete, thank you for reporting the issue.
How did the superfish.com script get included to your Node Inspector page? It looks like you have a chrome extension that is messing up the content of inspector.html. Can you try to run node-inspector will all chrome extensions disabled to verify this assumption?
This is possibly related to #220.
Repository: node-inspector/node-inspector

Issue #224: Cannot debug CoffeeScript program run with 'coffee' command
Created: 2013-09-29T02:49:06Z
Hi guys,
This is maybe more just a question than a bug. Sorry to ask in the form of an issue; I just didn't see any other better way (e.g. mailing list).
I love that node-inspector now has source map support — great work. I'm just unsure on what exactly triggers it, and what the pre-reqs are.
What I mean is, if I have the following files:

app.coffee
app.js
app.map

Where app.js ends with:
/*
//@ sourceMappingURL=app.map
*/
If I run the source CoffeeScript file (which just compiles it to JS on the fly via a require() hook):
coffee --nodejs --debug app.coffee

Then I'm successfully able to debug the original CoffeeScript source — amazing!
But if run the JS file directly:
node --debug app.js

Then I see only the compiled JS — even though it clearly has the source map declaration at the bottom.
Is that expected? If so, how come? If not, is there something I might be doing wrong? Or is there anything I can do to help you guys debug?
$ node -p 'process.versions'
{ http_parser: '1.0',
  node: '0.10.13',
  v8: '3.14.5.9',
  ares: '1.9.0-DEV',
  uv: '0.10.12',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1e' }

$ npm ls -g
...
coffee-script@1.6.3
node-inspector@0.5.0
...

Thanks much!

Duplicate issue #446: Could not debug coffee-script app
Created: 2014-09-25T18:06:13Z
Hy,
i have troubles debugging a simple express-app written in coffeescript.
Here is the source:

I start the script with coffee --nodejs --debug app.coffee and i can see the script in node-inspector, but the start of the script is different. It is not possible to set a break-point!

If i compile the coffeescript to javascript with following command coffee -c -m app.coffee and start the generated js file with node --debug app.js everything works just fine.
Does anybody has the same problem? Or is that an limitation of node-inspector.
OS: Mac OS X Mavericks
node 0.10.30
node-inspector 0.7.4
coffee-script 1.8.0
express 4.0.0
body-parser 1.0.1
Greetings
Tonka

Closing comment (2014-09-29T11:36:28Z): This is a duplicate of #224, see also #308.
Repository: node-inspector/node-inspector

Issue #188: Debug multiple applications in one debugger
Created: 2013-08-01T14:55:27Z
We should change the local storage used by WebInspector.Settings to be per-debugged-application, so that we do not restore breakpoints from application A when debugging application B.
We could either clear localStorage when switching to a new application (does not support parallel debugging of multiple applications) or override window.localStorage in WebInspector.Settings.prototype.createSetting to use keyed storage (key = application id, probably path to the main js file).

Duplicate issue #190: "Stop on uncaught exception" in node v0.10
Created: 2013-08-04T08:47:11Z
I created a file e.js with a single line:
blabla();

Now I run node 0.10.15 & latest node-inspector
node --debug-brk e.js
node-inspector

Then I go to Chrome, see that the execution is stopped and enable the violet(not blue!) "stop on error" button below http://screencast.com/t/ayFC8O31lVWg
Then I click "continue" and the script dies.
Expected behavior: stop execution on error.
Previous version of node-inspector: works as expected
Chrome built-in: works as expected
Node-inspector 0.3.2: fails.
Important stuff for debugging, it seems.

Closing comment (2013-08-05T15:18:58Z): @iliakan I was able to reproduce the problem. Running this command in DevTools console should fix it:
window.localStorage.clear()

I suspect this is related to #188.
Repository: node-inspector/node-inspector

Issue #224: Cannot debug CoffeeScript program run with 'coffee' command
Created: 2013-09-29T02:49:06Z
Hi guys,
This is maybe more just a question than a bug. Sorry to ask in the form of an issue; I just didn't see any other better way (e.g. mailing list).
I love that node-inspector now has source map support — great work. I'm just unsure on what exactly triggers it, and what the pre-reqs are.
What I mean is, if I have the following files:

app.coffee
app.js
app.map

Where app.js ends with:
/*
//@ sourceMappingURL=app.map
*/
If I run the source CoffeeScript file (which just compiles it to JS on the fly via a require() hook):
coffee --nodejs --debug app.coffee

Then I'm successfully able to debug the original CoffeeScript source — amazing!
But if run the JS file directly:
node --debug app.js

Then I see only the compiled JS — even though it clearly has the source map declaration at the bottom.
Is that expected? If so, how come? If not, is there something I might be doing wrong? Or is there anything I can do to help you guys debug?
$ node -p 'process.versions'
{ http_parser: '1.0',
  node: '0.10.13',
  v8: '3.14.5.9',
  ares: '1.9.0-DEV',
  uv: '0.10.12',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1e' }

$ npm ls -g
...
coffee-script@1.6.3
node-inspector@0.5.0
...

Thanks much!

Duplicate issue #363: Problems debugging CoffeeScript program run with 'coffee' command
Created: 2014-05-01T16:49:13Z
I can debug CoffeeScript when compiled with -c-m and run in node.
When I use the 'coffee' command the debugger recognizes the coffeescript file, but I can't do anything with it because the coffeescript is compiled on-the-fly and running in a node sandbox.
I have found a work-around: if I put a callback i containing a debugger statement in the file, I can force the debugger to recognize the file. From then on everything works fine and the rest of the file is debuggable:
    global.stopInDebugger = true;
    ping = () ->
      console.log "ping"
      console.log "step"
      if global.stopInDebugger
        console.log "Stopping in debugger"
        debugger
        console.log "Stepping in debugger"
        j = 0
        for i in [1..10]
          j = j + i

      setTimeout(ping, 1000)
    ping()
The global.stopInDebugger switch is needed to force it to stop the first time. After that I can reset the switch.
Is there some other way to get the compiled code to become visible?

Closing comment (2014-05-09T18:17:31Z): This is a duplicate of #224.
Repository: node-inspector/node-inspector

Issue #318: node-inspector v0.7.0 blank
Created: 2014-03-10T16:54:21Z
hi,
I apologize if this may overlap with past issues, but I have tried to played around with proposed solutions for a similar issue without any luck. I just installed node-inspector in a AWS Ubuntu 12.04.2 instance and node v0.10.12. After running:
$node-debug index.js
debugger listening on port 5858
Node Inspector is now available from http://localhost:8080/debug?port=5858
Debugging index.js
and check chrome (v33.0.1750.146) for http://myinstance-amazonaws-url:8080/debug?port=5858
the result is an empty page with the following source code:
 ...
The result is exactly the same if I run node --debug-brk index.js and node-inspector in separate terminals. The problem persists with safari Version 6.0.2 (7536.26.17) and
firefox (v22.0). In chrome, I have also tried to disable any extensions.

Duplicate issue #319: node-inspector v0.7.0 blank
Created: 2014-03-10T16:55:36Z
hi,
I apologize if this may overlap with past issues, but I have tried to played around with proposed solutions for a similar issue without any luck. I just installed node-inspector in a AWS Ubuntu 12.04.2 instance and node v0.10.12. After running:
$node-debug index.js
debugger listening on port 5858
Node Inspector is now available from http://localhost:8080/debug?port=5858
Debugging index.js
and check chrome (v33.0.1750.146) for http://myinstance-amazonaws-url:8080/debug?port=5858
the result is an empty page with the following source code including
body class="detached" id="-webkit-web-inspector"
The result is exactly the same if I run node --debug-brk index.js and node-inspector in separate terminals. The problem persists with safari Version 6.0.2 (7536.26.17) and
firefox (v22.0). In chrome, I have also tried to disable any extensions.

Closing comment (2014-03-10T17:06:56Z): This is a duplicate of #318
Repository: node-inspector/node-inspector

Issue #534: Script is resumed as soon as node-inspector is loaded
Created: 2015-01-23T09:47:26Z
I'm launching my program with --debug-brk. Execution is immediately paused. However, as soon as I load up node-inspector's page in Chrome, the script resumes, and immediately crashes (with the error I'm trying to debug). This gives me no time to set, say, a breakpoint. (Incidentally, debugger; statements don't help.)

Affects node v0.11.14 and higher. Use an earlier version of node to unblock yourself

v0.11.13 (Last compatible Unstable) - http://nodejs.org/dist/v0.11.13/
v0.10.38 (Last compatible Stable) - http://nodejs.org/dist/v0.10.38/

Node v0.10.38 will give you the profiler 'partial support' warning which you can ignore if you do not use the profiler. Use v0.11.13 as the warning suggests if you need the profiler.

I'm not sure what other information I can share, here. My own code is fairly complex; if you'd like to try and reproduce this on your end, the following should approximately duplicate the environment where I'm seeing this:
brew install nvm
nvm install 0.11
nvm use 0.11
npm install -g node-inspector
node-inspector &
git clone git@github.com:Paws/Rulebook.git --branch letter-01
git clone git@github.com:ELLIOTTCABLE/Paws.js.git --branch support-rulebook
cd Paws.js
npm install
npm install # yes, run it twice. bugs in my codebase. unrelated.
node --debug-brk ./Executables/paws.js check "../Rulebook/The Letters/01. On rules, meaning, and consistency.rules.yaml"
# At this point, it should be paused ...
# ... but as soon as you load up http://127.0.0.1:8080/debug?port=5858, for me, it resumes and crashes.

Duplicate issue #570: node 0.12.0, node-inspector 0.9.1: does not work with --debug-brk
Created: 2015-02-26T22:55:05Z
If I start a script using node --debug-brk I see that it is paused with the message debugger listening on port 5858. As soon as I load the node-inspector page at http://127.0.0.1:8080/debug?port=5858 the script continues immediately.
This makes it impossible to debug script startup, tests, etc.
When I switch back to node 0.10.33, loading the node-inspector page does not cause the script to continue and I can debug correctly.
Any ideas on how to get node-inspector working with node 0.12.0?
Version details:
node: 0.12.0
v8: 3.28.73
node-inspector: 0.9.1
OS: OSX Yosemite (10.10.2)

Closing comment (2015-03-04T09:03:04Z): Closing as a duplicate of #534.
Repository: node-opcua/node-opcua

Issue #623: how to read a node form OPC UA server
Created: 2019-05-02T15:58:15Z
I have an problem with this OPC UA from PLCSIM_Advanced

I need to read the "Tag_1". So I use readVariableValue and Read.

But this is my result. StatusCode: BadNodeIdUnknown.

Although I can read Variable from Object/Server (ns=1), I can't read Variable from Object/PLC_1(ns=3).
May I write wrong NodeId's syntax or I forgot write something??? Can you help me solve this problem. I'm a beginner. Thank you

Duplicate issue #652: unable to get node node values from opcua server using node js
Created: 2019-08-02T09:12:38Z
i am connected to opcua server using node js code.
i get node ids perfectly using UA Expert tool but when i am trying to get node values from node js code it throws invalid node id error.
ua expert

code

error

Closing comment (2019-08-02T17:23:24Z): duplicates #623
Repository: node-opcua/node-opcua

Issue #41: Can an OPC DA client connect to a node-opcua server?
Created: 2015-01-20T17:01:33Z
We tried using the OPC NET API to connect to a running node-opcua server and were unable to.  Is this action supported?

Duplicate issue #199: Issue with connecting OPC DA server
Created: 2016-04-22T09:06:06Z
Hi is their any way to connect OPC DA server using node js . Please suggest me how we can connect.

Closing comment (2016-04-25T20:32:03Z): duplicates #41
Repository: node-opcua/node-opcua

Issue #194: JS OPC UA Client in Webbrowser
Created: 2016-04-18T06:50:02Z
Hi,
I'd like to build a webpage that directly communicates OPC UA servers using client side java script. Is this possible based on your solution? If so, do you have any hints how to start?
Any help is appreciated.
Thanks and best regards,
Daniel

Duplicate issue #712: Error using node-opcua 
Created: 2019-12-30T19:11:29Z
Hello,
I have following issue:
I want to implement my a Server Client to my vue.js-application using node-opcua. For this purpose, I could succesfully install node-opcua (Version: 2.4.1) to my project. However, as soon as I try to import or use the OPCUAClient in order to connect to a server, I get following errors:
ERROR in ./node_modules/node-opcua-pki/dist/lib/misc/install_prerequisite.js
Module not found: Error: Can't resolve 'child_process' in 'C:\Users\Ilya\Desktop\ATP Aufgabe\node_modules\node-opcua-pki\dist\lib\misc'
 @ ./node_modules/node-opcua-pki/dist/lib/misc/install_prerequisite.js 29:22-46
 @ ./node_modules/node-opcua-pki/dist/lib/pki/toolbox.js
 @ ./node_modules/node-opcua-pki/dist/lib/index.js
 @ ./node_modules/node-opcua-certificate-manager/dist/certificate_manager.js
 @ ./node_modules/node-opcua-certificate-manager/dist/index.js
 @ ./node_modules/node-opcua/dist/server-stuff.js
 @ ./node_modules/node-opcua/dist/index.js
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib??vue-loader-options!./src/views/Home.vue?vue&type=script&lang=js&
 @ ./src/views/Home.vue?vue&type=script&lang=js&
 @ ./src/views/Home.vue
 @ ./src/router/index.js
 @ ./src/main.js

Does anyone know, how I can solve it?

Closing comment (2020-01-02T15:18:44Z): duplicate #194
Repository: node-opcua/node-opcua

Issue #218: finding the nodeId of a node by Browse name
Created: 2016-06-20T23:53:15Z
Does this functionality has been added?
As it says here:
https://github.com/node-opcua/node-opcua/blob/master/documentation/creating_a_client.md

Duplicate issue #482: find nodeId by variable browseName
Created: 2018-05-12T06:41:29Z
I'm submitting a ...  (check one with "x")

( ) bug report => search github for a similar issue or PR before submitting
(X) feature request
() support request => Please do not submit support request here, instead see use

use gitter or stackoverflow for community support, or
contact Sterfive for commercial support



Current behavior

Expected behavior

Minimal reproduction of the problem with instructions












...
What is the motivation / use case for changing the behavior?

Please tell us about your environment:



() I have installed node-opcua from source ( using git clone)


(x ) I have installed node-opcua as a package ( using npm install )


( ) I am using an application that uses node-opcua

( ) node-red
( ) other : please specify



Device: Server


OS version: Linux Ubuntu

( ) Windows : version : _________
(x ) Linux   : version : Ubuntu Server 16.04
( ) MacOs   : version : _________
( ) Raspbian: version : _________
( ) Other   : specify :



Description of the other OPCUA system I am trying to connect to:

Name:_________
Version:_________
Manufacturer/Software vendor:_________
link : https://



node-opcua version: ``




Node:
node --version =

HI, i've a simple question, is it possible to determine a nodeId  by variable browseName?
For examples my variable browsename is 4:Temperature1 and it's unique name.
The nodeid is not costant and depend on PLC version, something like this
nodeId: "ns=4;s=|var|PLC3 VXXXX (3259) .Application.PersistentVars.Temperature1",
the part VXXXX is not costant depend on machine version.
How i can find nodeID of Temperature1 whithout know "PLC3 VXXXX (3259)"
Thanks a lot

Closing comment (2018-05-20T20:50:05Z): duplicates #218
Repository: node-opcua/node-opcua

Issue #1009: Is openssl a runtime requirement?
Created: 2021-05-28T17:46:19Z
Is your feature request related to a problem? Please describe.
node-opcua client is configured to use an existing client certificate (meaning it shouldn't need to generate one):
const client = OPCUAClient.create({
    ...
    certificateFile: '/path/to/cert',
    privateKeyFile: '/path/to/key'
})
Connection to a server fails if there's no openssl installed on the system.
Error:
Command failed: "openssl" rand -out "/root/.config/node-opcua-default-nodejs/random.rnd" -hex 256
/bin/sh: openssl: not found

Describe the solution you'd like
I'm not sure if openssl is a runtime dependency. If it is, please consider adding a note in the readme.
Thanks!

Duplicate issue #1041: /bin/sh: openssl: not found
Created: 2021-08-18T01:34:48Z
Current behavior
Here's my sample code
const BPromise = require('bluebird')
const opcua = BPromise.promisifyAll(require('node-opcua'))
const OPCUAClient = opcua.OPCUAClient
const OPCUAManager = opcua.OPCUACertificateManager
const clientCertificateManager = new OPCUAManager()
const privateKeyPath = clientCertificateManager.privateKey
const certificatePath = path.join( // I don't think I can get it computed, so preparing manually
clientCertificateManager.rootDir,
'own/certs/client_certificate.pem'
)
const connectionStrategy = {
initialDelay: 1000,
maxRetry: 1
}
const options = {
connectionStrategy: connectionStrategy,
keepSessionAlive: true,
endpointMustExist: false,
clientCertificateManager
}
let client = OPCUAClient.create(options)
client.connect('opc.tcp://20.98.172.75:4840')
.then(() => {
console.log('connected')
})

########################################### OPENSSL ERROR ###########################################
CWD = .
Command failed: "openssl" version
/bin/sh: openssl: not found
Command failed: "openssl" rand  -out "/root/.config/node-opcua-default-nodejs/random.rnd" -hex 256
/bin/sh: openssl: not found

Step by step instruction to reproduce
Steps to reproduce the behavior:

....
....
....

Expected behavior
It should be connected to the Server.
Gist
 
gist:

Context


(x ) my request is related to node-opcua acting as an OPCUA CLIENT


( ) my request is related to node-opcua acting as an OPCUA SERVER


( ) I have installed node-opcua from source ( using git clone)


(x ) I have installed node-opcua as a package ( using npm install )


( ) I am using an application that uses node-opcua

( ) node-red
( ) other : please specify



Device: ______


OS version: ______

( ) Windows : version : ______
(x ) Linux : version : ______
( ) MacOs : version : ______
( ) Raspbian: version : ______
( ) Other : specify : ______



Description of the other OPCUA system I am trying to connect to:

Name: ______
Version: ______
Manufacturer/Software vendor: ______
link to the manufacturer or product site: https://



node-opcua version: :




Node:
node --version =

Closing comment (2021-08-24T15:37:26Z): duplicates #1009
Repository: node-opcua/node-opcua

Issue #616: BadTooManyMonitoredItems
Created: 2019-04-25T11:19:37Z
Hi,
I wan't to limit the number of monitored items per subscription in the server and return a BadTooManyMonitoredItems if too many monitored items are added. Is this possible using node-opcua?

Duplicate issue #1235: BadTooManyMonitoredItems
Created: 2023-01-28T09:18:16Z
Hi,
I wan't to limit the number of monitored items per subscription in the server and return a BadTooManyMonitoredItems if too many monitored items are added. Is this possible using node-opcua?

Closing comment (2023-01-30T07:22:02Z): duplicates #616
Repository: node-opcua/node-opcua

Issue #171: User Authorization
Created: 2016-03-10T17:13:34Z
Hey,
is there already a possibility to grant different users, different permissions on the server?
For example user1 cannot access node1, but user2 can access node1.
Cheers

Duplicate issue #326: Authorization of a specific action of specific resource by specific user.
Created: 2017-03-25T04:00:01Z
Here's a question.
From the OPC UA spec v1.03 - Part 3:

4.2.3 Authorization
The access to read, write, or execute resources should be authorized for only those entities that have a need for that access within the requirements of the system. Authorization can be as coarse-grained as allowing or disallowing a Client to access a Server or it could be much finer grained such as allowing specific actions on specific information items by specific users.

Say, a server has two variables; one is allowed to be accessed by User_A and User_B, but the other variable only allowed to be accessed by User_A.
Would this be possible with the current implementation of node-opcua? If so, could you please refer me to API doc or code (hopefully a sample code, if any) where I can find hints to do this?

Closing comment (2017-04-02T15:44:27Z): duplicates #171