AeroNotix
Repos
226
Followers
98
Following
6

A lisp web browser using WebKit

242
17

A Cassandra native protocol client in Common Lisp

Helper application for discovering Erlang nodes

7
1

Z80 processor emulator

Events

started
Created at 4 days ago
Created at 1 week ago
started
Created at 1 week ago
Created at 1 week ago

quiet down the gpgconf check

Created at 2 weeks ago

update emacs dependencies

remove deprecated import-environment usage

add disable-screen-blanking

Merge branch 'master' of github.com:AeroNotix/dotfiles

Created at 2 weeks ago
issue comment
Twilio advertises incorrect stun urls

That's very forward-thinking @seancoleman2. Interesting how a different billion-dollar company couldn't come up with the same thing 🤷🏻.

Will reach out via email!

Created at 2 weeks ago
issue comment
Twilio advertises incorrect stun urls

For the record, none of my systems were affected by this in a negative way. I just think the poor planning and rollout is just so indicative of Googlers it needed more attention than it seemed to be getting.

Created at 2 weeks ago
issue comment
Twilio advertises incorrect stun urls

The change was intended as a low-priority fix for a set of failing spec compliance tests. Nobody knew upfront that https://xkcd.com/1172/ would apply.

Are you joking?

talking with Googlers instead of about them gives amazing results.

Beg to differ. This isn't my first rodeo.

Created at 2 weeks ago
issue comment
Twilio advertises incorrect stun urls

@seancoleman2 oh please do not take the fact I am commenting here to mean that I lay any blame or ownership on yourself, or twilio in general.

I am commenting here because I know how absolutely futile it would be to try to discuss with Googlers on their own forum. Hence starting a conversation here.

Created at 2 weeks ago
issue comment
Twilio advertises incorrect stun urls

No-one else feel like this is too short a timeframe to be rolling this out in? I got an email today and the rollout is at the end of the month.

What is the harm in Chrome silently allowing completely benign parameters to exist in the URLs? The review ( https://chromium-review.googlesource.com/c/chromium/src/+/4037887 ) looks to have barely any discussion, besides someone mentioning it could break twilio and ending up here.

Not sure I fully understand why this change needs to happen, ... at all really.

Created at 2 weeks ago
started
Created at 3 weeks ago
pull request opened
feat: adds a new_from_file to create CredentialsFile
  • Adds a CredentialsFile::new_from_file/1 function which
    • Takes a filepath and reads it

Note: If there is actually a way to do this, it eluded me

Created at 1 month ago
AeroNotix create branch feat/allow-read-credentials-from-any-file
Created at 1 month ago

fix: don't export SSH_AUTH_SOCK if gpg not installed

Created at 1 month ago
wlan0 wifi interface not detected on boot

Just upgraded, wifi card not visible after reboot. I have both the files listed above. What can I do?

Created at 1 month ago

rename function?

Created at 1 month ago

update emacs dependencies

kooobctl completoin

Created at 1 month ago
create branch
AeroNotix create branch main
Created at 1 month ago
create repository
AeroNotix create repository
Created at 1 month ago

update slime

update emacs packages

Created at 1 month ago
issue comment
Modular types

Can you grant maintainership to someone you trust, or has more time? The library is an oasis in the desert of janky ORMs in the JS/TS land. Would be good to keep on truckin'.

Created at 1 month ago
issue comment
feat: allow for repl history

Another thing to consider is that since the repl function returns the NodeJS REPL instance, clients can do this themselves (this should be documented).

That said, I still think the Nest library should do more by default, maybe to mimic the default behaviour of the NodeJS REPL itself.

Example:

async function bootstrap() {
	const replServer = await repl(AppModule);
	if (process.env.NODE_REPL_HISTORY) {
		replServer.setupHistory(process.env.NODE_REPL_HISTORY, () => {});
	} else {
		replServer.setupHistory(path.join(os.homedir(), '.node_repl_history'), () => {});
	}
}
bootstrap();

I think the Nest repl library should do something like the above, by default, with the ability to disable history. Having history enabled by default is less surprising than history disabled by default.

Thoughts?

Created at 2 months ago

feat: allow for repl history

Ref: https://github.com/nestjs/nest/pull/10618

Created at 2 months ago

feat: allow for repl history

Ref: https://github.com/nestjs/nest/pull/10618

Created at 2 months ago

feat: allow for repl history

Ref: https://github.com/nestjs/nest/pull/10618

Created at 2 months ago
pull request opened
feat: allow for repl history

Ref: https://github.com/nestjs/nest/pull/10618

PR Checklist

Please check if your PR fulfills the following requirements:

  • [ ] The commit message follows our guidelines: https://github.com/nestjs/docs.nestjs.com/blob/master/CONTRIBUTING.md

PR Type

What kind of change does this PR introduce?

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update (formatting, local variables)
  • [ ] Refactoring (no functional changes, no api changes)
  • [ ] Build related changes
  • [ ] Docs
  • [ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • [ ] Yes
  • [ ] No

Other information

Created at 2 months ago
AeroNotix create branch feat/allow-for-repl-history
Created at 2 months ago
Created at 2 months ago