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

Is your feature request related to a problem? Please describe.
I'm copying text one tab into another to run it with another recipe. But when I change back to the first tab, the text I originally selected is no longer selected. It would be nice if this is remembered because when working with a wall of text, it's near impossible to figure out where I was.

This applies to both to input and th

Documentation saying:

Key with no values (such as an empty object or array) will return nothing

However there are cases when this behavior is not desirable. It brings inconsistencies between stringify and parse methods, meaning same object can't be stringified and then parsed. Example:

qs.stringify({ foo: [], bar: 1 })
// -> "bar=1"

qs.parse("bar=1")
// -> {bar: "1"}

F

When there are several encrypted scripts on the site, each one contains functions rc4(), base64(), md5().
If you added the disable include option for these functions in the CLI, I could add them only to the first script.

Hi, im trying to use Hashids with Typescript and Node.

import Hashids from 'hashids';

I'm not getting any Typescript errors in the editor, but Im getting this error when the code is compiled.

Using ts-node version 8.5.4, typescript version 3.7.5

`Error: No valid exports main found for 'node_modules\hashids'
at resolveExportsTarget (internal/modules/cjs/loader.js:625:9)

A recent PR (#1180) raised awareness that the first page for many new library users is its docs.rs page, generated from the crate root documentation and not the extensive Readme. While moving all of the documentation, as proposed, felt like too broad, nevertheless the following discussion was quite constructive in how the overall structure could be improved. I'll quote relevant portions on what

if I create a new project with

cargo new bincode_test;
cargo install cargo-edit;
cargo add bincode serde_derive;
cd bincode_test;

And then replace the contents of bincode_test/src/main.rs with the Example code from the README.md.

Then when I try to build the code with:

cargo build

It gives error:

error[E0463]: can'

Currently, only Stop character and digits are mapped but not in all languages. It would be nice to unify those

Per [Section 3.2 of RFC4648], the padding on Base64 URL-safe codec is actually optional. [RFC7636] is a concrete example where a padless encoding is required (as explicitly stated in [Section 3]). Any chance for supporting padless Base64Url encoding out-of-the-box in scodec? This way, manual workarounds (e.g., ByteVector(bytes).toBase64(Base64Url).takeWhile(_ != '=')) would be eliminated.

I got this error in go version go1.11beta2 using github.com/go-pg/pg
Run ok back then, but after update this error show up
src/github.com/segmentio/encoding/json/reflect_optimize.go:15:6: missing function body

TL;DR: metaflac should support outputting to a different file, like vorbiscomment(1).

Background: I have created a music compilation system which works kinda like a software build system. When possible, it encodes and tags in different steps so that a mere tag change doesn't result in the reencoding of the entire library.

both @fsouza and @mateusdelbianco had issues installing ffmpeg on MacOS, I think we should write a section on Readme to address how to build using brew before running snickers and the tests.