Right now we have a pretty decent list of environment variables to detect different terminals that support colors. However, it is often not exactly known from what version on these terminals actually support the colors, if that's detectable and how many colors these support.

I would like to start a list of different terminals / CIs and other things including their corresponding environment vari

Problem

I'd like to send many files in the same time but with different files metaData.
The combination of uppy.setMeta uppy.addFile doesn't wok because the upload is asynchronous, and when files finish to upload they will heritate the last uppy.setMeta configuration.

Moreover the uppy.setFileMeta method is quite impossible to use, because on uppy.addFile we can't declared an id

While generating docs for the v5.2, I noticed our doc coverage dropped to 99% due to a forgotten doc here. and was wondering if it is a good idea to add a CI step to make sure any newly introduced code is properly documented

The Table (and TreeTable) documentation says scrollHeight can be:

Height of the scroll viewport in fixe

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

Please read and follow the issue templates:

1. Bug Report or Documentation Issue or Questions and Help?

2. Which react-native-wechat version are you using?

3. What platform does your issue occur on? (Android/iOS/Both)

4. Please provide a clear and concise description of what the bug is as precisely as possible，you can:

1. post a screenshot to explain in which case you get the i

Is your feature request related to a problem? Please describe.
When using a proxy in front of the Daemon, the port defined in the Node setting for daemon has to be exposed on the Daemon´s server as the Panel will try to reach the Daemon on the defined port. When set to the proxied port (eg: 443) then the proxy will able to forward the frontend to the backend but as soon as you auto-deploy the

Feature request

• Feature request

Description of feature (or steps to reproduce if bug)

Currently the sample data in Colmena consists of a lot of Lorem Ipsum text.

It would be great if there were a few dummy stories, events and pages so they can be linked to a website.

This should give the user a more interesting experience

mongo --eval "db.getSiblingDB('admin').shutdownServer()" doesn't actually shut down the server correctly. I've had a better experience just doing

ps -a | grep mongo
kill [PID]

This could obviously use some more elaboration, and I could look at it more. But it's worth noting for now that the instructions aren't doing what they're supposed to.

My Setu

If I want to change the settings (for example to use the Dogecoin Mainnet), I need to manually enter #settings in the URL.

When you rename a protocol, the old one is not selected so we cannot immediately type.

In vanilla, the race descriptions appear like this:

However in OpenTESArena, it appears like this:

You'll notice tha

The tap testing framework has improved a lot since we initially started this project. One new(er) addition is official APIs for fixtures.

I'm not 100% exactly which tests need to be refactored, but this seems like a great place for someone to get started if they wanted to contribute

When clicking to rescan the horizontal progress bar for first step shows up and locks up the screen until the extraction step.

This is bad UX (my fault 😓 ) -- we should make it not lock up 👌

ps - bonus points on getting the 'time remaining' to show up (currently estimates that 'only seconds' left -- because the computation is to look at the time it took to scan the previous files, and si