profile
viewpoint
ORES ORESoftware ORESoftware SF Yay Area Generalist / asynchronous.

ORESoftware/curtain 4

Node.js rate limiter using Redis

async-java/async.java 1

A Java port of the async library for Node.js. This lib is designed to be used with Vert.x and Akka.io.

ORESoftware/bumpitty-bump-bump 1

Bump a value in your package.json so that Docker (and others) notice changes.

ORESoftware/bunion 1

Bunyan's weird cousin. Has foot issues.

ORESoftware/cambiasso 1

Load paths to node_modules to avoid relative paths, during npm install phase.

ORESoftware/check-git-status 1

Get a report on the "unclean" Git status for every Git repo within a certain directory.

ORESoftware/clean-trace 1

Get clean stack traces free from unnecessary Node.js internals

ORESoftware/cli.parser 1

Progressive and typed command line parsing, with emphasis on JSON, for Node.js and TypeScript.

issue commentORESoftware/live-mutex

EADDRINUSE: address already in use udsPath

ah yes, but i thought this was happening w the ports not just the socket?

OmgImAlexis

comment created time in a day

issue commentnodejs/node

display node.js version (process.version) at the end of stacktraces

the user case here is for stack traces in general, so you dont have to ask "what node version are you on?" sometimes its easy to forget to ask

ORESoftware

comment created time in a day

issue closedORESoftware/live-mutex

EADDRINUSE: address already in use udsPath

I had a server started with /tmp/lmx.sock as the udsPath and it died unexpectedly(I killed it). When the server came back up it wouldn't reconnect.

Maybe add a way to have the server recover from this? You could have an option to enable this. Catch EADDRINUSE, delete socket file, retry connection. If all good then no worries. Otherwise throw error like normal. That way permissions errors, etc. still get propagated but this doesn't have to be solved by the user.

Couldn't connect to broker. Error: listen EADDRINUSE: address already in use /tmp/lmx.sock
    at Server.setupListenHandle [as _listen2] (net.js:1211:19)
    at listenInCluster (net.js:1276:12)
    at Server.listen (net.js:1375:5)
    at /Users/xo/code/_/proxy/node_modules/live-mutex/dist/broker.js:306:31
    at new Promise (<anonymous>)
    at Broker.ensure.start (/Users/xo/code/_/proxy/node_modules/live-mutex/dist/broker.js:300:36)
    at handleServerConnecting (/Users/xo/code/_/proxy/app/index.js:239:31)
    at processTicksAndRejections (internal/process/task_queues.js:82:5) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '/tmp/lmx.sock',
  port: -1
}

closed time in 2 days

OmgImAlexis

issue commentORESoftware/live-mutex

EADDRINUSE: address already in use udsPath

can't replicate this, but will keep an eye out for it

OmgImAlexis

comment created time in 2 days

issue closedORESoftware/live-mutex

timeout not taking into effect?

const broker = new LMXBroker();
const mutex = new LMXClient({
    lockRequestTimeout: 10000
});

const mutexKey = '123';

// Connect to mutex broker
await Promise.all([broker.ensure(), mutex.ensure()]).catch(error => {
    // This is where the error happens
    log.debug(`Couldn't connect to broker.`, error);
});

// Lock mutex
const lock = await mutex.acquireLock(mutexKey, {
    lockRequestTimeout: 10000
}).catch(error => {
    log.debug(`Couldn't acquire lock for "${mutexKey}".`, error);
});

I still get this error though. Did I miss an option somewhere?

Couldn't connect to broker. lmx client err: client connection timeout after 3000ms.

closed time in 2 days

OmgImAlexis

issue commentORESoftware/live-mutex

timeout not taking into effect?

this should work, but lmk if it don't thx

OmgImAlexis

comment created time in 2 days

PR opened ChannelMeter/stripe-go

Reviewers
CM-2687 - Introduce go modules

see related: ChannelMeter/cm-go-api#465

+408 -406

0 comment

185 changed files

pr created time in 2 days

PR closed stripe/stripe-go

CM-2687 - Introduce go modules

see related: https://github.com/ChannelMeter/cm-go-api/pull/465

+413 -411

1 comment

185 changed files

ORESoftware

pr closed time in 2 days

pull request commentstripe/stripe-go

CM-2687 - Introduce go modules

whoops wrong repo

ORESoftware

comment created time in 2 days

PR opened ChannelMeter/sendgrid-go

CM-2687 - Introduce Go Modules

see related: ChannelMeter/cm-go-api#465

+8 -0

0 comment

3 changed files

pr created time in 2 days

push eventChannelMeter/stripe-go

Operations Research Engineering Software+

commit sha 29a41ccd76fe677285eca1df98d6cf1f0ccf6032

squash-me

view details

push time in 2 days

push eventChannelMeter/stripe-go

Operations Research Engineering Software+

commit sha c314916aefd71af40801e034bef06276922000b5

squash-me

view details

push time in 2 days

PR opened stripe/stripe-go

CM-2687 - Introduce go modules

see related: https://github.com/ChannelMeter/cm-go-api/pull/465

+1025 -411

0 comment

196 changed files

pr created time in 2 days

issue openednodejs/help

How to truncate file while writing to it

I put this question on SO https://stackoverflow.com/questions/60875131/how-to-truncate-file-from-node-js

basically, as my node process is writing to the file, every once in a while, I want to read the last 500 lines of the file (tail -n 500) and then truncate the file, and write the remaining 500 lines to it. any idea how to do that safely?

created time in 2 days

issue openedcprev/cprev

max open watch files

Users may wish to set:

fs.inotify.max_user_watches = 524288

https://confluence.jetbrains.com/display/IDEADEV/Inotify+Watches+Limit

edit the /etc/sysctl.conf file and add that property

created time in 2 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 2ec64ef5489fa9af9f579de531324c60e2bfe6a9

squash-me

view details

push time in 2 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha bf82f6b869d90f2f24494f152758d461798cc4b1

squash-me

view details

push time in 2 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha ecff4b5b4cf44472a54cf28b488fa806ee910899

squash-me

view details

push time in 2 days

issue openedcprev/cprev

cprev server - connect to github

use a github webhook to push changes to the cprev server, send all files to cprev agents and they can determine a diff

created time in 2 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 0759a597fecc4eef6205cbb15556fb72bea4df73

squash-me

view details

Operations Research Engineering Software+

commit sha 51f00c1851c07867030b8f274b0ef0f1c17ee611

Merge branch 'master' of github.com:ORESoftware/cprev

view details

push time in 2 days

push eventcprev/cprev

alex

commit sha 6efc5170480df19c3a59e807a2f6f9fae52f3270

squash-me

view details

push time in 3 days

push eventcprev/cprev

alex

commit sha f06ce451ac802c84cd83eed2a731ef552ec2fe5d

squash-me

view details

push time in 3 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 7f28efedfcbf93f893ed81611e2267ac1100e0ca

squash-me

view details

push time in 3 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 0048663b5aa2f8516373215ed800d68c682719cd

squash-me

view details

Operations Research Engineering Software+

commit sha a85614c6d9e1f75d4db7b161ef4ea0f881be8462

Merge branch 'master' of github.com:ORESoftware/cprev

view details

push time in 3 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

how'd it go?

OmgImAlexis

comment created time in 3 days

issue commentnvm-sh/nvm

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

I think what's confusing is this:

Screenshot from 2020-03-24 15-47-30

so does this belong in ~/.bashrc?

# 1
export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm

or does this belong in ~/.bashrc?

# 2
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

I think at some point I threw the first one into the env and that's what is causing the issue idk

ORESoftware

comment created time in 4 days

issue commentnvm-sh/nvm

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

.bashrc and .bash_profile both source a 3rd shared file called ~/.alex.rc.sh and that file is only sourced once by the shell since I flip a boolean

ORESoftware

comment created time in 4 days

issue openedcprev/cprev

launchctl vs launchd

https://apple.stackexchange.com/questions/384877/how-are-brew-services-different-from-launchctl-services

created time in 4 days

issue commentnvm-sh/nvm

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

yep updated the OP

ORESoftware

comment created time in 4 days

issue commentnvm-sh/nvm

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

I guess I have to open a new issues to see the original template

ORESoftware

comment created time in 4 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

@OmgImAlexis any word on this bird?

OmgImAlexis

comment created time in 4 days

issue openednvm-sh/nvm

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

Getting this in my shell when I open a new bash tab:

$(nvm_sanitize_path "${NPM_CONFIG_PREFIX}");: command not found

in my ~/.bashrc I have:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

i remember seeing the NPM_CONFIG_PREFIX stuff somewhere but don't see it now - I am on ubuntu 18.04

created time in 4 days

push eventcprev/cprev

alex

commit sha 48602b340ef8187bd9f9444d746b56d3c9e32d11

squash-me

view details

alex

commit sha de709001fa2495d418aaf74c2e100694ba402adc

squash-me

view details

push time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha a2839baccf33bb94b4ccddf969a4d12802bf696a

squash-me

view details

push time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 4375b0cd2488c8362eb30388cfee1333eb7d2947

squash-me

view details

push time in 4 days

issue openedcprev/cprev

if user2 alters file after user1, user1 should get a notif along with user 2

if user2 alters file after user1, user1 should get a notif along with user 2

created time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 5868de19bd33469069ae923fcb33bb207772fb72

squash-me

view details

push time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 4fe56639bed9b3ac7b28f2248c1eebd850cfb92a

squash-me

view details

push time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 0ac8a8c776bffc333c711e8f8fb89843660a642e

squash-me

view details

push time in 4 days

created repositoryORESoftware/fake-git-remote

created time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 8c76fa6d202d6f92d9aaa05485ae3ce6563b161c

squash-me

view details

Operations Research Engineering Software+

commit sha 5c89f6ed9aa7c4f170e38d310e2b83c0ff3ad388

squash-me

view details

push time in 4 days

push eventcprev/cprev

alex

commit sha 707852bd3588b6844b5c63e8892c0faed87fdeae

squash-me

view details

alex

commit sha 1f12a133b17829888dfaabb2f4f068e94f5e84d1

Merge branch 'master' of github.com:cprev/cprev

view details

push time in 4 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 5acbd4b527e931beb0561480c5e097b9b6ec77e9

squash-me

view details

push time in 5 days

push eventcprev/cprev

alex

commit sha 5f4d6739e48b50b410861d825f7c3e00fa3fdd23

squash-me

view details

push time in 5 days

push eventcprev/cprev

alex

commit sha a2e4320843613df102a542eb55152342cd3719ad

conflicts

view details

alex

commit sha b32ba8514aa07acfb01b626571c02a3aad49a681

Merge branch 'master' of github.com:cprev/cprev

view details

push time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 545c4b989d1c6cf9cc5033325fc3a511636d8a92

squash-me

view details

push time in 5 days

push eventcprev/cprev

alex

commit sha f81658afac48922e73bae3032c5759ea4b75fbd3

cprev

view details

push time in 5 days

push eventcprev/cprev

alex

commit sha b8576e4187d1cb922bbec8f765000ce992aa9bc6

added notifier

view details

alex

commit sha 398eedc2ceb0738ff413afc6ae16c5eb981f80bb

merged

view details

push time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha dcd079a60366b71aba58038f1a33c06c26e9828f

squash-me

view details

push time in 5 days

issue openedcprev/cprev

cprev execstart for systemd

https://unix.stackexchange.com/questions/574184/allow-home-env-var-in-execstart-in-systemctl-service-file/574405#574405

ExecStart=/usr/bin/bash -c 'exec $HOME/.local/bin/cprev-agent'

created time in 5 days

issue openedcprev/cprev

watch the $HOME/.cprev dir and if something changes, restart the watcher

watch the $HOME/.cprev dir and if something changes, restart the watcher

only restart the watcher if relevant changes occur, like changes to "codeRoots" in the

$HOME/.cprev/conf/cprev.conf.js 

file

created time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 40195d27884cb35096601b4a8002d80c6a22d301

squash-me

view details

push time in 5 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

something might be up with your node version, here is the output for for node version 8:

> assert
{ [Function: ok]
  fail: [Function: fail],
  AssertionError: [Function: AssertionError],
  ok: [Circular],
  equal: [Function: equal],
  notEqual: [Function: notEqual],
  deepEqual: [Function: deepEqual],
  deepStrictEqual: [Function: deepStrictEqual],
  notDeepEqual: [Function: notDeepEqual],
  notDeepStrictEqual: [Function: notDeepStrictEqual],
  strictEqual: [Function: strictEqual],
  notStrictEqual: [Function: notStrictEqual],
  throws: [Function: throws],
  rejects: [AsyncFunction: rejects],
  doesNotThrow: [Function: doesNotThrow],
  doesNotReject: [AsyncFunction: doesNotReject],
  ifError: [Function: ifError],
  strict: 
   { [Function: strict]
     fail: [Function: fail],
     AssertionError: [Function: AssertionError],
     ok: [Circular],
     equal: [Function: strictEqual],
     notEqual: [Function: notStrictEqual],
     deepEqual: [Function: deepStrictEqual],
     deepStrictEqual: [Function: deepStrictEqual],
     notDeepEqual: [Function: notDeepStrictEqual],
     notDeepStrictEqual: [Function: notDeepStrictEqual],
     strictEqual: [Function: strictEqual],
     notStrictEqual: [Function: notStrictEqual],
     throws: [Function: throws],
     rejects: [AsyncFunction: rejects],
     doesNotThrow: [Function: doesNotThrow],
     doesNotReject: [AsyncFunction: doesNotReject],
     ifError: [Function: ifError],
     strict: [Circular] } }
> 

OmgImAlexis

comment created time in 5 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

got it, can you copy the contents of this file on your machine

/usr/local/bin/proxy/node_modules/live-mutex/dist/broker.js:65:16

to here?

OmgImAlexis

comment created time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha fdc0fdc196fd655562ed81e0c5176c71603ea121

squash-me

view details

push time in 5 days

push eventORESoftware/live-mutex

Operations Research Engineering Software+

commit sha c1667fbdc80c042a66258a0c76a6ada3c9491a69

squash-me

view details

push time in 5 days

issue commentnodejs/node

display node.js version (process.version) at the end of stacktraces

this is a very useful feature, useful for a thousand github issues, like this one most likely: https://github.com/ORESoftware/live-mutex/issues/92#issuecomment-602428458

ORESoftware

comment created time in 5 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

my guess is that you are on an old node version? node 7 does not have assert.strict, but node 8+ should.

OmgImAlexis

comment created time in 5 days

issue commentORESoftware/live-mutex

{ TypeError: assert.strict is not a function

yeah it was tested and also compiled with TS tol, hmm, weird, which node.js version are you on?

OmgImAlexis

comment created time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha fdb9f0fa2ed951b6624862020b39b806c7b54b5f

squash-me

view details

push time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 1a41b96e435b8dcd2728f084a905ed8b9831c646

squash-me

view details

push time in 5 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 38a5ec4b09a33a45f9b4046bec49b830b9661a26

squash-me

view details

push time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha f55a7c45170541bf7a8b7863b155a5f78f3e4b77

squash-me

view details

push time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha ecffbb10ef078f3bbf1a6f7148293a2dab9f5c1d

squash-me

view details

push time in 6 days

issue commentsindresorhus/run-applescript

Node.js bindings insead of child process

yeah any idea if electron apis can be imported and used in a non-electron app, in some random nodejs code?

ORESoftware

comment created time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 7a85f4f6d0c7cec42b6857c41c7d931ca4e46b11

squash-me

view details

push time in 6 days

issue commentsindresorhus/run-applescript

Node.js bindings insead of child process

thanks, its possible that the electron api is based on bindings instead of applescript

https://www.electronjs.org/docs/api/notification

ORESoftware

comment created time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha a68f6d062e1edfdd5ec25c1772e9ce6fa0f711ca

squash-me

view details

push time in 6 days

issue commentnvm-sh/nvm

Use nvm as lightweight local node install

yeah i probably change the $NVM_DIR, i get it.

however this didn't work on ubuntu:

  (PROFILE=/dev/null curl -o- 'https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh' | bash) &> /dev/null

aka I still get this added to ~/.bashrc

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

can't you just add an env variable flag to prevent the writing to bashrc? should be a simple new flag right?

ORESoftware

comment created time in 6 days

issue commentnvm-sh/nvm

Use nvm as lightweight local node install

thanks, i forgot to ask, is there a way to change the install location of nvm?

ORESoftware

comment created time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 5382b496162a4d6634303918628c7b023f00b2e3

squash-me

view details

push time in 6 days

issue commentnvm-sh/nvm

Use nvm as lightweight local node install

yeah i am looking to install it without writing to bashrc

ORESoftware

comment created time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha bb376837f18e6354f63d3b28d6631904af9720f9

squash-me

view details

push time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha a2893539c316ea08f8e11c9fca54ef25e2b083a1

squash-me

view details

push time in 6 days

issue closednodejs/node

Event loop tick id

Basically looking for an event loop tick id, for this purpose:

const run = (cb) => {

   let isCurrentTick = true;
   process.nextTick(() => {
      isCurrentTick = false;
   });

  doSomeWork(() =>{
      isCurrentTIck ? process.nextTick(cb) : cb();
  });
  
}

this is an optimization that can reduce the memory overhead of servers. It's mostly about convenience, but in some cases very necessary when you don't know for sure if something is being fired asynchronously or not.

so the fix looks like:

const run = (cb) => {

  const currentEventLoopId = process.getEventTickId();

  doSomeWork(() =>{
      currentEventLoopId  === process.getEventTickId() ? process.nextTick(cb) : cb();
  });
  
}

so what I am looking for is an incrementing id for every tick of the event loop. This fix would obviate the need for using process.nexTick calls to store some local boolean variable as in the first code example.

closed time in 6 days

ORESoftware

push eventcprev/cprev

Operations Research Engineering Software+

commit sha fccb8ce63676093070eb468f3406b422bf98446a

squash-me

view details

push time in 6 days

issue commentelectron/electron

Open source lib for Node.js bindings to Apple notification libraries

is that library open-sourced, because I want to use it

ORESoftware

comment created time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 4461169f2767d74662b7640ba0e32dbfcc927eab

squash-me

view details

push time in 6 days

push eventcprev/cprev

Operations Research Engineering Software+

commit sha 59a9f38d97e23edc875efcf0d2a2925d4e195146

squash-me

view details

push time in 6 days

issue openedcprev/cprev

when installing - create a uuid to idenfity the machine

the install location can be:

$HOME/.cprev/conf/cprev.conf.js

and in there, put a unique uuid to identify the machine

created time in 6 days

issue openedcprev/cprev

refuse to run as root user

check the root user name and guid uuid of the user

created time in 6 days

issue openednvm-sh/nvm

Use nvm as lightweight local node install

I want to install nvm for the current user, but avoid exporting the nvm source script to bashrc, is there a way to do this? aka, I don't want to write to ~/.bashrc.

created time in 6 days

issue openedHomebrew/brew

Looking for an example of creating package for use with brew services

I want to create a package which can be listed as a brew service and used like a systemd service. I google for examples and it's hard to find. I also put this question on Quora: https://www.quora.com/unanswered/Where-is-there-an-example-of-creating-a-homebrew-package-which-can-launch-a-systemd-service-or-brew-service-on-MacOS

created time in 7 days

issue commentmikaelbr/node-notifier

"timeout" and "activate" are logged for me - and I can't stop those logs?

ok so I figured it out, those things are being logged in the callback:

  function(err, response) {
    // Response is response from notification
    console.error(err, response);
  }

so if there err is null, it shouldn't be an empty string '', it should be null

ORESoftware

comment created time in 7 days

issue openedmikaelbr/node-notifier

strange timeout on MacOS

I am on:

"node-notifier": "^6.0.0"

I ran this:

const notifier = require('node-notifier');
const path = require('path');

notifier.notify(
  {
    title: 'My awesome title',
    message: 'Hello from node, Mr. User!',
    // icon: path.join(__dirname, 'coulson.jpg'), // Absolute path (doesn't work on balloons)
    // sound: true, // Only Notification Center or Windows Toasters
    // wait: true // Wait with callback, until user action is taken against notification, does not apply to Windows Toasters as they always wait or notify-send as it does not support the wait option
  },
  function(err, response) {
    // Response is response from notification
    console.error(err, response);
  }
);

notifier.on('click', function(notifierObject, options, event) {
  // Triggers if `wait: true` and user clicks notification
});

notifier.on('timeout', function(notifierObject, options) {
  // Triggers if `wait: true` and notification closes
});

it waited for about 5 seconds, and then logged:

  timeout

a couple things:

  1. I have a timeout handler registered, so you don't have to log "timeout" for me
  2. can the logging for "timeout" be more specific, such as:

node-notiifier: User did not click on the notification, so it close after 5 seconds

created time in 7 days

issue openedmikaelbr/node-notifier

document if uses child process or C bindings

I went through some of the code and it looks like this library uses child processes, instead of using C bindings on each platform. is there any use of C bindings here or is it all through child processes?

created time in 7 days

PR opened mikaelbr/node-notifier

Update checkGrowl.js

prevent memory leaks

+2 -2

0 comment

1 changed file

pr created time in 7 days

push eventORESoftware/node-notifier

ORES

commit sha ed6a46f5df72db4e96c893d093aa0c3f168a994f

Update checkGrowl.js prevent memory leaks

view details

push time in 7 days

fork ORESoftware/node-notifier

A Node.js module for sending notifications on native Mac, Windows and Linux (or Growl as fallback)

fork in 7 days

issue openedcprev/cprev

node notifier

https://github.com/mikaelbr/node-notifier

created time in 7 days

issue openedcprev/cprev

apple script

https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/DisplayNotifications.html

created time in 7 days

issue openedcprev/cprev

ubuntu system notifs

https://askubuntu.com/questions/187022/how-can-i-send-a-custom-desktop-notification

created time in 7 days

issue openedsindresorhus/run-applescript

Node.js bindings insead of child process

I see there are JavaScript libraries for displaying notifications, for example: https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/DisplayNotifications.html

anyone know if there is a way to call the libs directly from JavaScript / Node.js, without launching a child process?

created time in 7 days

issue openedelectron/electron

Open source lib for Node.js bindings to Apple notification libraries

I realize that Electron might only do in-app notifications (not system notifications on Mac machines). But I am looking for Node.js bindings to do the C / objective-C libraries that Apple uses to display notifications on a Macbook Pro etc.

https://developer.apple.com/documentation/usernotifications/

the above link shows how to use Objective C or Swift to display notifications, but am looking to either call that from a child process or from Node.js.

created time in 7 days

startedTooTallNate/node-applescript

started time in 7 days

push eventcprev/vscode-extension

Operations Research Engineering Software+

commit sha bd4d15e0a2515a0e2b4c1d51e4065cb7f4216900

squash-me

view details

push time in 7 days

create barnchORESoftware/live-mutex

branch : next13

created branch time in 7 days

issue commentORESoftware/live-mutex

timeout not taking into effect?

I just merged this in, you can use:

const c = new LMXClient({connectTimeout: 50})
OmgImAlexis

comment created time in 7 days

push eventORESoftware/live-mutex

ORES

commit sha cb7b296eca50bcd29da0b6e230b29fa736123fb9

Next12 - Add connectTimeout option (#90) * squash-me * squash-me * squash-me * 0.2.24 * squash-me * squash-me * squash-me

view details

ORES

commit sha 923df0d2dd0801f6cc4ccb333456aca75049c8ef

Merge pull request #91 from ORESoftware/dev Next12 - Add connectTimeout option (#90)

view details

push time in 7 days

PR merged ORESoftware/live-mutex

Next12 - Add connectTimeout option (#90)
  • squash-me

  • squash-me

  • squash-me

  • 0.2.24

  • squash-me

  • squash-me

  • squash-me

Proposed Changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to fsharp? Put an x in the boxes that apply

  • [ ] Bugfix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • [ ] Build and tests pass locally
  • [ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • [ ] I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

+221 -145

0 comment

16 changed files

ORESoftware

pr closed time in 7 days

more