$ git grep -n  '<< 24' src/
src/base64.h:88:        unbase64(src[i + 0]) << 24 |
src/cares_wrap.cc:83:  return static_cast<uint32_t>(p[0] << 24U) |
src/node_sockaddr.cc:305:  uint32_t check = ptr[0] << 24 | ptr[1] << 16 | ptr[2] << 8 | ptr[3];
src/util-inl.h:51:  (((x) & 0xFF) << 24) |                                                      \
src/util-inl.h:61:  (((x) & 0x0000000000FF0000ul

It would be helpful in all React plugins to forward HTML properties to plugin container <div> tag.

Example usage:

<ProgressBar className="x" />

I would expect it will generate code:

<div class="x">
   <div class="uppy uppy-ProgressBar" style="position: initial;">
       <div class="uppy-ProgressBar-inner" style="width: 100%;"></div>
       <div class="uppy-ProgressBar-

[ ] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

This is more like a suggestion, not an issue

What did you do?

Tried to use UIImage rotated(by angle: Measurement) on a round image

What did you expect to happen?

The image to be rotated

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

Currently, eggs are exported in json format. Eggs can contain a lot of multiline strings, which makes it very hard to read them in json format.

YAML has much better support for multiline strings (see here) which would make it much easier to modify eggs as code and see changes in Pull Requests.
In addition YAML is easier to read and we've converted wings to use ya

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.

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