profile
viewpoint

davidcallanan/py-myopl-code 43

Interpreter for the BASIC language written in Python 3

davidcallanan/py-simple-math-interpreter 3

An interpreter that can evaluate simple calculations to understand how computers process human-readable text

davidcallanan/mc-loot-table-shuffler 1

Minecraft loot table shuffler

davidcallanan/js-palette 0

A simple JavaScript color palette management library

issue closedjangxx/node-ViGEmClient

Left trigger and right trigger for xBox controller?

Hello again, as you suggested I switched to using ViGEm :)

This is working perfectly, except I can't figure out how to enable/disable the left an right triggers on an xbox controller? How can I do this?

I've tried using LEFT/RIGHT_SHOULDER and LEFT/RIGHT_THUMB to no avail.

closed time in 7 days

davidcallanan

issue commentjangxx/node-ViGEmClient

Left trigger and right trigger for xBox controller?

Nevermind, I figured it out, leftTrigger and rightTrigger are axes, not buttons.

davidcallanan

comment created time in 7 days

issue openedjangxx/node-ViGEmClient

Left trigger and right trigger for xBox controller?

As you suggested I switched to using ViGEm :)

This is working perfectly, except I can't figure out how to enable/disable the left an right triggers on an xbox controller? How can I do this?

I've tried using LEFT/RIGHT_SHOULDER and LEFT/RIGHT_THUMB to no avail.

created time in 7 days

startedjangxx/node-ViGEmClient

started time in 7 days

issue commentjangxx/node-vjoy

Feeding not working

😀😀😀 This is amazing! Thanks for getting back so quickly, it's working perfectly.

davidcallanan

comment created time in 8 days

issue openedjangxx/node-vjoy

Feeding not working

Hi, firstly thanks for creating this package.

I have completed code that a) checks if vJoy is enabled, b) creates a device, and c) updates the axes and buttons.

All the code is running without any errors.

However, only part (a) and (b) seem to be working. None of the input (part c) is appearing when I run the "Monitor vJoy" application provided by vJoy.

Any ideas why this might be the case?

If I use the "vJoy Feeder (Demo)" application provided by vJoy, the inputs are working, so it is either an issue with my code or this package.

Here is a few snippets of my code:

if (vJoy.isEnabled()) {
	console.log("INFO: vJoy is enabled.");
} else {
	console.log("ERROR: vJoy is either not installed or not enabled.");
	process.exit();
}
for (var i = 1; i <= 8; i++) {
	if (vJoyDevice.status(i) != "free") {
		continue;
	} else {
		break;
	}
}

player.device = vJoyDevice.create(i);

if (player.device) {
    // ...
} else {
    // ...
}
// this code does not give errors as long as I map float from range -1 to 1, to the range 1 to 32768
device.axes.X.set(Math.floor((x + 1) / 2 * 32768) + 1);
device.axes.Y.set(Math.floor((y + 1) / 2 * 32768) + 1);
device.buttons[4].set(true);

created time in 8 days

issue commentracismbreaker/racismbreaker

Main is still offensive

@blacklistisnotracist Every word can be offensive. Stick with master.

blacklistisnotracist

comment created time in 22 days

issue commentgit-for-windows/git

Change non-inclusive naming

And now I can't even upvote the apparently "disruptive" comments. I think whoever is doing this is the one who's disruptive. Look at all the havoc you're after causing, just because you didn't agree with the majority's opinion.

dscho

comment created time in 22 days

issue commentgit-for-windows/git

Change non-inclusive naming

HEADS UP! A bunch of content is being marked as "disruptive content" and "off-topic". Please give your opinion some ground instead of censoring the other opinion. Thank you.

dscho

comment created time in 22 days

issue commentgit-for-windows/git

Change non-inclusive naming

I think master in this context is similar to the word mastercopy. I think we can all agree it has nothing to do with slavery, and if people get offended by it, well, they can deal with it.

It is clear that I and most people who have read this issue do not support this change.

dscho

comment created time in 22 days

push eventdavidcallanan/node-deno-integration-example

unknown

commit sha f9baccd4d22dc5e92a2d438db2e4469c2548d055

update readme

view details

push time in a month

issue commentdenoland/deno_lint

fallthrough in switch/case statements

I think it should be part of both fmt and lint

davidcallanan

comment created time in a month

issue openeddenoland/deno_lint

Deno fmt feature request

Not essential but I think it would be cool and catch bugs.

I propose that the deno fmt command would do the following to each case block in a switch statement:

  • Add a // fallthrough comment to the end of the case if there is no unconditional break statement.
  • Remove any // fallthrough comment otherwise.

Examples

switch foo {
  case "bar":
    console.log("bar");
    break;
    // fallthrough
  case "baz":
    console.log("baz");
  case "coconut":
    if (jellybean) {
      break;
    }
}

would be formatted to:

switch foo {
  case "bar":
    console.log("bar");
    break;
  case "baz":
    console.log("baz");
    // fallthrough
  case "coconut":
    if (jellybean) {
      break;
    }
    // fallthrough
}

Why?

  • Makes it clear if the case falls through or not - pretty self-explanatory
  • Catches many bugs where you forget to include the break keyword. This is because it will add a // fallthrough comment, and you should notice this. If falling through was not intended you can then ensure you add in that break statement.

created time in a month

issue openeddenoland/deno

Deno fmt feature request

Not essential but I think it would be cool and catch bugs.

I propose that the deno fmt command would do the following to each case block in a switch statement:

  • Add a // fallthrough comment to the end of the case if there is no unconditional break statement.
  • Remove any // fallthrough comment otherwise.

Examples

switch foo {
  case "bar":
    console.log("bar");
    break;
    // fallthrough
  case "baz":
    console.log("baz");
  case "coconut":
    if (jellybean) {
      break;
    }
}

would be formatted to:

switch foo {
  case "bar":
    console.log("bar");
    break;
  case "baz":
    console.log("baz");
    // fallthrough
  case "coconut":
    if (jellybean) {
      break;
    }
    // fallthrough
}

Why?

  • Makes it clear if the case falls through or not - pretty self-explanatory
  • Catches many bugs where you forget to include the break keyword. This is because it will add a // fallthrough comment, and you should notice this. If falling through was not intended you can then ensure you add in that break statement.

created time in a month

issue commentdenoland/deno

fmt: add config flag

@j127 Interesting opinion.

I think the most important configuration option is to be able to use tabs, as that allows each user to configure the tab width for themselves in their editor.

However, the option to choose between single quotes and double quotes doesn't support your argument when working in a team, since you still need each team member to agree - which is unlikely. I think something like this should be consistent (probably double quotes because that is consistent across languages). This does not interfere with muscle memory as typing in a single quote will be corrected to a double quote when the format command is ran. If, visually, one wants to see a single quote instead, I would love to see an editor extension or similar that displays single quotes but saves them as double quotes.

My statement above applies to semi-colons too.

I totally agree that there should be a simple setting if dprint supports it. One can always use the defaults if they want.

bartlomieju

comment created time in a month

push eventdavidcallanan/node-deno-integration-example

unknown

commit sha c9e50c35fd914fcec1844445bbd2762fe40951d1

update

view details

push time in a month

push eventdavidcallanan/node-deno-integration-example

unknown

commit sha ea4e1d370113742e5bddededdc3b2d2791998ec2

update2

view details

push time in a month

push eventdavidcallanan/node-deno-integration-example

unknown

commit sha 4cd9a5aa2b13502e2b19b00f0bb1351941faaddf

next commit

view details

push time in a month

issue commentdenoland/deno

`deno bundle` produce typescript file

@bartlomieju I thought the idea was that TypeScript was to be the "source of truth" and so if modules are being bundled it only makes sense to me that TypeScript output would be an option (if not a default).

Another thing that might have come up already is outputting source maps.

davidcallanan

comment created time in a month

issue commentdenoland/deno

fmt: add config flag

I agree that we should try to keep the configurations consistent, but at least like @j127 mentioned tabs should be used to allow people to configure their tab size in their editor. I don't see why tab size has anything to do with the code itself, and this is something that people have strong personal preferences for and could be the difference between someone deciding to use deno fmt or not.

bartlomieju

comment created time in a month

issue openeddenoland/deno

`deno bundle` produce typescript file

Are there plans to support typescript output for the deno bundle command?

Are there plans to emit typescript declaration files when creating an esm bundle with deno bundle?

I think these are important features.

created time in a month

push eventdavidcallanan/node-deno-integration

unknown

commit sha 5b97ec2b75a829cfcd6f5d93de3ebab586c92bd9

initial commit

view details

push time in a month

push eventdavidcallanan/node-deno-integration

unknown

commit sha 2ada336e02ff1cce184306031a3b1d2d9e7c0a95

initial commit

view details

push time in a month

push eventdavidcallanan/node-deno-integration

unknown

commit sha 7b062ce01eea0ed83034e9b5500cfe83cbaf1b65

initial commit

view details

push time in a month

push eventdavidcallanan/node-deno-integration

unknown

commit sha fbf18847b8a8a4ee25eb0096bf99f541d8ac7dad

initial commit

view details

push time in a month

create barnchdavidcallanan/react-deno-frontend

branch : master

created branch time in a month

created repositorydavidcallanan/react-deno-frontend

created time in a month

create barnchdavidcallanan/node-deno-integration

branch : master

created branch time in a month

created repositorydavidcallanan/node-deno-integration

created time in a month

issue commentdenoland/deno

deno bundle doesnt include code from pika

This could be related to an issue I was having while attempting to import react from pika.

katywings

comment created time in 2 months

issue commentdenoland/deno

Accept custom tsconfig in deno bundle

Does -c tsconfig.json not work? This could be the cause of a problem I am having...

amatiasq

comment created time in 2 months

issue commentdenoland/deno

Typescript compile error during bundle gives unhelpful assertion error

I'm getting this same error, but haven't created a reproduction yet

Ragzouken

comment created time in 2 months

issue commentdenoland/deno

WebRTC Integrating

@balupton Is WebRTC not part of the standard browser interface? How would one implement this in userland?

xueqingxiao

comment created time in 2 months

issue commentdenoland/deno

import with absolute path?

I haven't read all the comments above so someone might have already mentioned this.

I think there is no need to be able to import relative to the "project" root, if this is defined as the entrypoint of your application.

What we should be able to do is import relative to the root of the current "module boundary" as I like to call it. In node.js this would have been relative to the root of the package you are in. With Deno, there is no concept of packages, so it would be necessary in code to be able to create a new isolated boundary. I think this is quite fundamental to module resolution in all languages / package managers.

However, I understand that this is likely not possible in Deno in order to achieve compatibility with browsers.

alinnert

comment created time in 2 months

issue commentpnpm/pnpm

feature request: workspace dependencies alias

That's great thanks! It works perfectly :)

davidcallanan

comment created time in 2 months

issue commentpnpm/pnpm

feature request: workspace dependencies alias

Yes that's my problem, I need to create an alias for a workspace, not a package on the npm registry.

davidcallanan

comment created time in 2 months

issue openedpnpm/pnpm

feature request: workspace dependencies alias

<!-- Please only file bugs/feature requests for pnpm here.

If you have a question that is not answered in the FAQ section of the README then it is best to post your question on StackOverflow under the pnpm tag: https://stackoverflow.com/questions/tagged/pnpm or ask it in our Gitter chatroom: https://gitter.im/pnpm/pnpm

If your issue is a bug, please follow the format below: -->

pnpm version: 4.14.2

Code to reproduce the issue:

<!-- If there was a fatal error also include a gist of your pnpm-debug.log file. -->

Hi, within one of my workspaces I am trying to create an alias for a workspace dependency:

"dependencies": {
    "foo": "workspace:@bar/baz"
}

Expected behavior:

The @bar/baz workspace would be added as a dependency, but inside the node_modules the symlink would be named foo.

Actual behavior:

However it seems that aliases for workspace dependencies aren't supported, resulting in the following error:

Scope: all 2 workspace projects
ERROR  Invalid workspace: spec (workspace:@bar/baz)
at Error: Invalid workspace…

Additional information:

  • node -v prints: v12.16.0
  • Windows, OS X, or Linux?: windows 10

created time in 2 months

PublicEvent
CommitCommentEvent
CommitCommentEvent

startedkevlened/isomorphic-webcrypto

started time in 3 months

issue openedfeross/simple-peer

Missing error code in readme.md

Hi, thanks for your amazing package!

I noticed there is an error code missing from the README.md documentation, "ERR_CONNECTION_FAILURE" (as seen below when a connection is closed)

image

created time in 3 months

startedhumanenginuity/assayer

started time in 3 months

issue closedcalvinmetcalf/native-crypto

Potential bug or my code is wrong - key_ops member inconsistent

Hi, thanks for your package, but I am having a problem.

I am running the following code in my browser to generate a key and encrypt a message with it:

let crypto = require("native-crypto");
let keyPair =  await crypto.generate("RS256");
let message = "Hello, World!";
let encrypted = crypto.rsa.encrypt(keyPair.privateKey, message);

This simple example is causing the following exception:

Uncaught (in promise) DOMException: The JWK "key_ops" member was inconsistent with that specified by the Web Crypto call. The JWK usage must be a superset of those requested

It seems as if the generated key is missing the encrypt and decrypt operations. I'm not very familiar with this stuff... how do I fix this, or is this a bug?

closed time in 3 months

davidcallanan

issue commentcalvinmetcalf/native-crypto

Potential bug or my code is wrong - key_ops member inconsistent

@calvinmetcalf Yes, that is what I needed to do in the end, thanks :)

davidcallanan

comment created time in 3 months

issue openedmdn/sprints

/en-US/docs/Web/API/SubtleCrypto/exportKey

Request type

<!-- Select the appropriate option -->

  • [ ] Please close this issue, I accidentally submitted it without adding any details
  • [ ] New documentation
  • [x] Correction or update

Details

<!-- Tell us about the issue you saw. A clear description, links, and screenshots help us fix it faster. -->

The documentation says:

result is a Promise that fulfills with an ArrayBuffer containing the key in the requested export format.

This is incorrect, the return value is not always an ArrayBuffer. As shown in the example later on in the page, when jwk is specified for the format, the return value is a JSON-serializable JavaScript object. It also may be incorrect with some of the other formats but I haven't checked those.

I've waisted a lot of time assuming the return value was an ArrayBuffer, so this should be fixed.

created time in 3 months

issue commentcalvinmetcalf/native-crypto

Potential bug or my code is wrong - key_ops member inconsistent

@calvinmetcalf So is that the issue? I was trying to verify the ownership of a key by requesting a message to be encrypted with their private key and then I could decrypt with their public key to confirm ownership.

davidcallanan

comment created time in 3 months

issue openedcalvinmetcalf/native-crypto

Potential bug or my code is wrong - key_ops member inconsistent

Hi, thanks for your package, but I am having a problem.

I am running the following code in my browser to generate a key and encrypt a message with it:

let crypto = require("native-crypto");
let keyPair =  await crypto.generate("RS256");
let message = "Hello, World!";
let encrypted = crypto.rsa.encrypt(keyPair.privateKey, message);

This simple example is causing the following exception:

Uncaught (in promise) DOMException: The JWK "key_ops" member was inconsistent with that specified by the Web Crypto call. The JWK usage must be a superset of those requested

It seems as if the generated key is missing the encrypt and decrypt operations. I'm not very familiar with this stuff... how do I fix this, or is this a bug?

created time in 3 months

push eventdavidcallanan/sapper-template

dependabot[bot]

commit sha 46259af0d5e5f0367897d3a9ba441c08f4f4c65a

Bump minimist from 1.2.0 to 1.2.5 Bumps [minimist](https://github.com/substack/minimist) from 1.2.0 to 1.2.5. - [Release notes](https://github.com/substack/minimist/releases) - [Commits](https://github.com/substack/minimist/compare/1.2.0...1.2.5) Signed-off-by: dependabot[bot] <support@github.com>

view details

David Callanan

commit sha c63acb773455183404f2fe95d15c8012a92f56a1

Merge pull request #1 from davidcallanan/dependabot/npm_and_yarn/minimist-1.2.5 Bump minimist from 1.2.0 to 1.2.5

view details

push time in 3 months

PR merged davidcallanan/sapper-template

Bump minimist from 1.2.0 to 1.2.5 dependencies

Bumps minimist from 1.2.0 to 1.2.5. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/substack/minimist/commit/aeb3e27dae0412de5c0494e9563a5f10c82cc7a9"><code>aeb3e27</code></a> 1.2.5</li> <li><a href="https://github.com/substack/minimist/commit/278677b171d956b46613a158c6c486c3ef979b20"><code>278677b</code></a> 1.2.4</li> <li><a href="https://github.com/substack/minimist/commit/4cf1354839cb972e38496d35e12f806eea92c11f"><code>4cf1354</code></a> security notice</li> <li><a href="https://github.com/substack/minimist/commit/1043d212c3caaf871966e710f52cfdf02f9eea4b"><code>1043d21</code></a> additional test for constructor prototype pollution</li> <li><a href="https://github.com/substack/minimist/commit/6457d7440a47f329c12c4a5abfbce211c4235b93"><code>6457d74</code></a> 1.2.3</li> <li><a href="https://github.com/substack/minimist/commit/38a4d1caead72ef99e824bb420a2528eec03d9ab"><code>38a4d1c</code></a> even more aggressive checks for protocol pollution</li> <li><a href="https://github.com/substack/minimist/commit/13c01a5327736903704984b7f65616b8476850cc"><code>13c01a5</code></a> more failing proto pollution tests</li> <li><a href="https://github.com/substack/minimist/commit/f34df077a6b2bee1344188849a95e66777109e89"><code>f34df07</code></a> 1.2.2</li> <li><a href="https://github.com/substack/minimist/commit/67d3722413448d00a62963d2d30c34656a92d7e2"><code>67d3722</code></a> cleanup</li> <li><a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94"><code>63e7ed0</code></a> don't assign onto <strong>proto</strong></li> <li>Additional commits viewable in <a href="https://github.com/substack/minimist/compare/1.2.0...1.2.5">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 months

push eventdavidcallanan/py-simple-math-interpreter

David Callanan

commit sha c8ba180c0a3d679ad23c3b163233e652b7032938

parser

view details

push time in 3 months

more