• I want to propose a feature

What is the current behavior?
Does not specify which browsers are fully/partially supported.

If this is a feature request, what is motivation or use case for changing the behavior?
Before integrating users would like to know if their desired browser support is available. Would also help to build support if we know which browsers need it.

From: https://boltons.readthedocs.io/en/latest/setutils.html#boltons.setutils.IndexedSet

As you can see, the IndexedSet is almost like a UniqueList, retaining only one copy of a given value, in the order it was first added.

This appears incorrect. Perhaps it is a remnant from an earlier version of the library?

Write a Windows .BAT equivalent of travis_ci_helpers.sh

We need this .BAT file for running integration tests under Appveyor, which is unable to run our existing bash script.

Alternatively, rewrite that script in Python so we can use it under both Travis and Appveyor.

Originally posted by @mpenkov in RaRe-Technologies/smart_open#479 (comment)

Steps to reproduce: Try to use fences for code blocks.
Expected behaviour: code blocks.
Actual behaviour: normal text.
Turbo Editor version:1.19, from F-Droid.

![screenshot_20170112-211504](https://cloud.githubusercontent.com/assets/16250597/21908604/41bbceac-

I'm sure many potential plugin users would like to know which browsers we can count on with this plugin before getting hours into implementation. The suggestion of "modern browsers" could mean many things. From reading the source, I can see that you are ruling out old versions of Android, Zune, Kindle and Windows Phone. How does IE fair?

In the code sample below, taken from the Integration page on the wiki,

  #define LOG_PAGE_SIZE       256
  
  static u8_t spiffs_work_buf[LOG_PAGE_SIZE*2];
  static u8_t spiffs_fds[32*4];
  static u8_t spiffs_cache_buf[(LOG_PAGE_SIZE+32)*4];

could the magic numbers be clarified?

For spiffs_work_buf, this is because SPIFFS needs at least 2 pages for doing it's magic, cor

First, big thanks for a really impressive set of image / upload tools. We're really excited to implement it on our site.

Summary

We're making use of functional components, and I'm looking for documentation on how to implement the equivalent of

imageEditEditor: Doka.create()

when passing FilePond properties as attributes in React. It doesn't seem to work by transferring the basic i

Failed to load resource: the server responded with a status of 403 (Forbidden)
{ "message": "API rate limit exceeded for N.N.N.N. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", "documentation_url": "https://developer.github.com/v3/#rate-limiting" }
And maybe allow authentication

When i start lolisafe .js i got warnings
`Knex:warning - Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now,