mit

Version

v15.8.0

Platform

Darwin Alekseys-iMac.local 20.5.0 Darwin Kernel Version 20.5.0: Sat May 8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64 x86_64

Subsystem

stream

What steps will reproduce the bug?

Run the following code:

'use strict'

const { Transform, pipeline } = require('stream')

function createTransformStream (tf, context) 

We have a server that is for authenticating to AWS to be able to upload.
That server requires JWT for authentication. The XHR plugin supports custom headers.
Would it be possible to implement the same thing on the AWS plugins as well?

🚀
Is your feature request related to a problem? Please describe.
Doc string states:
Date().weekday -> 5 // fifth day in the current week.
Guess what, 5 is not friday. It's thursday. It makes some sense after i dug deeper, but as a programmer, i assumed monday could be 0 or 1, therefore thursday should be 3 or 4. Monday is 2! Because sunday is 1!

**Describe the solution you'd li

System information

• node version: v10.13.0
• npm or yarn version: 6.4.1
• OS/version/architecture: gLinux 64-bit (Google-internal, like Debian Testing)
• Applicable nodegit version: v0.23.0 built from source

https://www.nodegit.org/api/tree/ has an example of how to use tree.walk(), but it doesn't mention a critical detail, which is mentioned in an example:
https://github.com

Background (please complete the following information):

• Panel or Wings: Panel
• Version of Panel/Wings: 1.4.2

Describe the bug
Editing a sub-user and attempting to edit the same sub-user presents you with the loading spinner from the previous action, not allowing you to edit the user a 2nd time without a refresh.

To Reproduce

1. Make new sub-user
2. Edit newly created

How do we retrieve experiment metadata like tags and attrs, after it has been set using set_experiment. I am using the latest python client 0.14.6. Not able to read that info from the object returned by set_experiment.

Describe the problem
We should check all methods that are just the same as a method that exists in the hierarchy already.

• There is a rule that detect it
• A release test is there: testNoEquivalentSuperclassMethods, it, for now, tests for the number of cases we have in the system

What needs to be done
We need to remove the methods. But: this sounds trivial, but in practice, there

as of tap 11 there is a feature for testing with snapshots. It seems to me like there are couple places in our test suite where we could move to this pattern to this technique.

This is a great place for someone to hack on if they wanted to get started in this repo