profile
viewpoint
Tobias Nießen tniessen Germany https://tniessen.me Doing stuff with computers. Graduate student. Open source contributor and maintainer.

nodejs/node-core-utils 139

CLI tools for Node.js Core collaborators

nodejs/uvwasi 109

WASI syscall API built atop libuv

tniessen/memfs-fuse 11

Simple fuse demo filesystem

tniessen/iperf-windows 5

Visual Studio solution to natively build iperf3 on Windows

tniessen/iperf-vsproj 2

iperf3: A TCP, UDP, and SCTP network bandwidth measurement tool

tniessen/node-args.js 2

Another Node.js argument parser

tniessen/cryptpad 1

Text editor for Windows supporting strong encryption

dthomso1/CubeSatSeniorDesign 0

CubeSatProject

tniessen/admin 0

Facilitating joint collaboration amongst the TSC and CommComm

tniessen/automation 0

Better automation for the Node.js project

issue closednodejs/node-core-utils

Add a verbose option

A few things that come to mind

  1. Show commands spawned by ncu
  2. Show HTTP request response, in particular responses that could not be parsed as JSON (e.g. when Jenkins authorization fails, it returns XML)
  3. Pipe stdout and stderr, also do not use spinners if verbosity is on in case the output is overwritten

closed time in an hour

joyeecheung

pull request commentWebAssembly/WASI

Document how to write and run tests

The wasmtime repo's WASI test suite uses Rust as the source language, which fails by panicking. It will print messages to stdout and eventually hit the unreachable opcode. Our test harness captures guest stdout and stderr, and prints any of them that are non-empty when the instance traps.

This doesn't do you much good if your implementation doesn't have basic stuff like writing to stdio working, but in my experience that is usually the first thing you get working.

caspervonb

comment created time in 2 hours

push eventWebAssembly/spec

Travis CI

commit sha e83e4b66d2c965e293941065547e2ff2837d7e5a

Deploy to GitHub Pages: 397bb5358c8c5ed776d103718a7603922b81374c

view details

push time in 2 hours

Pull request review commentWebAssembly/WASI

Document how to write and run tests

+# Testing+

If we could bundle additional files with the tests and were allowed to use these files in <basename>.arg (or even statically in the test, I guess), that would seem easiest. What do you think?

You could but this also introduces a lot of extra unrelated dependencies in your tests that can be avoided.

Different toolchains have different mechanisms for it but it can be quite trivial to embed the data. In Rust for example one could use the include_bytes macro.

const model_1 = include_bytes!("model_1.tensor")

Other toolchains have their ways too.

caspervonb

comment created time in 3 hours

pull request commentWebAssembly/WASI

Document how to write and run tests

One open ended question is how do we handle printing diagnostics to the test runner.

Assertions which just call unreachable aren't that great but it It would be preferable to NOT depend on output_stream in every single test to print the failure before aborting.

caspervonb

comment created time in 3 hours

push eventWebAssembly/wasi-crypto

Frank Denis

commit sha 34214a5936e924e7b127f64bb9ab20fad3e97840

Rust implementation: add Cargo information

view details

Frank Denis

commit sha 4f85a9c4d780834d73b3d694d1ada63d89fa1140

Rust implementation: make handle managers private

view details

push time in 3 hours

push eventWebAssembly/spec

Zhi An Ng

commit sha c0b7eb03fff96b429f35b62fac192a7ba5af638e

Fix usage of extend in t.load and t.loadN_sx extend\F{\_}\sx isn't an operator, but extend_\sx is.

view details

Ng Zhi An

commit sha 397bb5358c8c5ed776d103718a7603922b81374c

Missed the braces

view details

push time in 4 hours

PR merged WebAssembly/spec

Fix usage of extend in t.load and t.loadN_sx

extend\F{_}\sx isn't an operator, but extend_\sx is.

+2 -2

0 comment

1 changed file

ngzhian

pr closed time in 4 hours

push eventWebAssembly/wasi-crypto

Frank Denis

commit sha 8110e83a1faba35ccebabc5cb31eb222f118e43e

Update .gitignore

view details

push time in 4 hours

push eventWebAssembly/wasi-crypto

Frank Denis

commit sha 78906d04493dc152e65767cd58799663c9dd1bb5

Remove wiggle support for the hostcalls implementation

view details

push time in 4 hours

pull request commentnodejs/next-10

doc: add minutes for meeting 6 Jan 2021

@nodejs/next-10 would be great to get a review so that I can land this.

mhdawson

comment created time in 4 hours

issue closednodejs/next-10

Node.js Next 10 Years team Meeting 2021-01-21

Time

UTC Thu 21-Jan-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 21-Jan-2021 08:00 (08:00 AM)
US / Mountain Thu 21-Jan-2021 09:00 (09:00 AM)
US / Central Thu 21-Jan-2021 10:00 (10:00 AM)
US / Eastern Thu 21-Jan-2021 11:00 (11:00 AM)
EU / Western Thu 21-Jan-2021 16:00 (04:00 PM)
EU / Central Thu 21-Jan-2021 17:00 (05:00 PM)
EU / Eastern Thu 21-Jan-2021 18:00 (06:00 PM)
Moscow Thu 21-Jan-2021 19:00 (07:00 PM)
Chennai Thu 21-Jan-2021 21:30 (09:30 PM)
Hangzhou Fri 22-Jan-2021 00:00 (12:00 AM)
Tokyo Fri 22-Jan-2021 01:00 (01:00 AM)
Sydney Fri 22-Jan-2021 03:00 (03:00 AM)

Or in your local time:

  • https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Next%2010%20Years%20team+Meeting+2021-01-21&iso=20210121T1600
  • or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Jan+21%2C+2021+in+local+time

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Key Technical Areas - Brainstorm to generate list #39
  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

  • link for participants: https://zoom.us/j/99950131676

  • For those who just want to watch: We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.

  • youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

closed time in 4 hours

mhdawson

issue commentnodejs/next-10

Node.js Next 10 Years team Meeting 2021-01-21

PR for minutes: https://github.com/nodejs/next-10/pull/44

mhdawson

comment created time in 4 hours

PR opened nodejs/next-10

doc: add minutes for meeting 21 Jan 2021

Signed-off-by: Michael Dawson mdawson@devrus.com

+72 -0

0 comment

1 changed file

pr created time in 4 hours

issue commentnodejs/next-10

Key Technical Areas - Brainstorm to generate list

One of the next steps in addition to discussing in the next meeting: https://github.com/nodejs/next-10/issues/43

mhdawson

comment created time in 4 hours

issue commentnodejs/next-10

Key Technical Areas - Brainstorm to generate list

@darcyclarke just went to look at adding the picture,very happy to see it already there, thanks!

mhdawson

comment created time in 4 hours

issue openednodejs/next-10

Create fun-retro for broader input on key Technical trends/Node.js features

Possible approach

  • Create copy of the board we created today
  • Tweet/promote asking people to add in their own thoughts.
  • Compare results and incorporate what we've missed.

created time in 4 hours

issue closednodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2021-01-21

Time

UTC Thu 21-Jan-2021 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Thu 21-Jan-2021 13:00 (01:00 PM)
US / Mountain Thu 21-Jan-2021 14:00 (02:00 PM)
US / Central Thu 21-Jan-2021 15:00 (03:00 PM)
US / Eastern Thu 21-Jan-2021 16:00 (04:00 PM)
EU / Western Thu 21-Jan-2021 21:00 (09:00 PM)
EU / Central Thu 21-Jan-2021 22:00 (10:00 PM)
EU / Eastern Thu 21-Jan-2021 23:00 (11:00 PM)
Moscow Fri 22-Jan-2021 00:00 (12:00 AM)
Chennai Fri 22-Jan-2021 02:30 (02:30 AM)
Hangzhou Fri 22-Jan-2021 05:00 (05:00 AM)
Tokyo Fri 22-Jan-2021 06:00 (06:00 AM)
Sydney Fri 22-Jan-2021 08:00 (08:00 AM)

Or in your local time:

  • https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2021-01-21&iso=20210121T2100
  • or https://www.wolframalpha.com/input/?i=09PM+UTC%2C+Jan+21%2C+2021+in+local+time

Links

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • TLS: improve compliance with shutdown standard, remove hacks #36111
  • Rename default branch from "master" to "main" or something similar #33864

nodejs/docker-node

  • Publish packages to GitHub Registry #1410

nodejs/TSC

  • any interest in an RFC process? #962

nodejs/security-wg

  • Potential stagnation of open issues on h1 bounty program #654

Invited

  • Anatoli Papirovski @apapirovski (TSC)
  • Beth Griggs @BethGriggs (TSC)
  • Ruben Bridgewater @BridgeAR (TSC)
  • Сковорода Никита Андреевич @ChALkeR (TSC)
  • Colin Ihrig @cjihrig (TSC)
  • Shelley Vohr @codebytere (TSC)
  • Daniel Bevenius @danbev (TSC)
  • Franziska Hinkelmann @fhinkel (TSC)
  • Gabriel Schulhof @gabrielschulhof (TSC)
  • Gireesh Punathil @gireeshpunathil (TSC)
  • James Snell @jasnell (TSC)
  • Joyee Cheung @joyeecheung (TSC)
  • Mary Marchini @mmarchini (TSC)
  • Matteo Collina @mcollina (TSC)
  • Michael Dawson @mhdawson (TSC)
  • Myles Borins @MylesBorins (TSC)
  • Michaël Zasso @targos (TSC)
  • Tobias Nießen @tniessen (TSC)
  • Rich Trott @Trott (TSC)

Observers/Guests

Notes

The agenda comes from issues labelled with tsc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Zoom link: https://zoom.us/j/611357642 Regular password

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.

Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.


Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • :+1: - Attending
  • :-1: - Not attending
  • :confused: - Not sure yet

closed time in 5 hours

mhdawson

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2021-01-21

We cancelled as we did not have enough attendees this week.

mhdawson

comment created time in 5 hours

push eventMaxBittker/sandspiel

Max Bittker

commit sha ee82f0d6379cc9190ae84caf9843ace40c87b80d

Update sandspiel.postgres

view details

push time in 5 hours

issue commentWebAssembly/design

Proposal: Fp IEEE compliance level flags for Wasm (FP-Fast-Math for Wasm Scalar & SIMD)

Yes, any decisions that affect float precision/behavior should be baked into the Wasm module by the tools. New instructions can be added for behavior that cannot be expressed with the current ones.

arunetm

comment created time in 5 hours

Pull request review commentWebAssembly/WASI

Document how to write and run tests

+# Testing+

Another reason to embed any data the test needs to that it avoid the dependency on the filesystem API, making the test more precise and less fragile. It should be fairly straight forward to embed data in wasm, I think there are a few different ways you can do this if you are using an llvm-based toolchain.

caspervonb

comment created time in 7 hours

issue commentnodejs/next-10

Key Technical Areas - Brainstorm to generate list

Link/reference to the funretro board we put together here: https://easyretro.io/publicboard/cLBIBu3wA2Um7qIziXq1zmC4gdi1/f2334393-fe0f-4202-8ee5-0ef677e0ff9e

Screen Shot 2021-01-21 at 1 12 41 PM

mhdawson

comment created time in 8 hours

issue openednodejs/abi-stable-node

Rename primary branch to main

Github tooling is in place to do this. Unless there are objections I'll go ahead and do it.

Once we do that we should also do for node-addon-api

created time in 9 hours

pull request commentnodejs/TSC

feat(charter): introduce emergency and async votes

Any progress on this?

mmarchini

comment created time in 9 hours

Pull request review commentWebAssembly/WASI

Document how to write and run tests

+# Testing+

Depends on the previous question but probably just define some fuzzy asserters in the source language. Internal logic should be handled internally IMO.

Sounds good.

I'm not sure what wasi-nn needs, not that familiar with the proposal but seems it just loads models from memory?

That's right but, practically speaking, those models/weights/tensors are large and are easier to manage as separate files than static data sections in a compiled Wasm file. It's not an exact corollary, but in an example over in Wasmtime I load this data from files before using them in wasi-nn. If we could bundle additional files with the tests and were allowed to use these files in <basename>.args (or even statically in the test, I guess), that would seem easiest. What do you think?

caspervonb

comment created time in 9 hours

issue openedopenjs-foundation/cross-project-council

CPC Working Session - 2021-01-26

Agenda: TBD based on related issue below

Facilitator: @tobie @SaraJo @joesepi Related issue(s): #699 Doodle link: N/A Date: 2012-01-26 1700 UTC Zoom link: https://zoom.us/j/91398697172?pwd=QVgxRUFXdmtHVUNiODhoSU11ejF0QT09

Please wait for your meeting to be added to the OpenJS Foundation calendar before using the Zoom meeting. If there are two conflicting meetings, please note that the meeting on the calendar takes precedence.

created time in 9 hours

PR opened nodejs/next-10

fix: alignment of needs matrix
+1 -1

0 comment

1 changed file

pr created time in 10 hours

create barnchnodejs/next-10

branch : darcyclarke-fix-needs-alignment-matrix

created branch time in 10 hours

more