Ophir LOJKINE

Split the async fs interface, indexedDB, and sqlite-specific code

8

Hello ! This is very useful work you have been doing here. If I understand well, this repository contains both the `Atomic` and Shared Array Buffer logic required to provide...

error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

1

Since latest update, cargo outdated returns : ``` ~/.cargo/bin/cargo-outdated: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory ``` ## System info -...

Improve error handling

4

Currently, when parse fails, the user only gets a very uninformative error string as a result. It would be nice to have a custom error type with useful functionality ,...

Add support for comments

2

It would be nice to be able to parse SQL statements with comments in them. #### Example ```sql create--blah blah table--blah blah tt--blah blah (--blah blah x--blah blah )--blah blah...

support MySQL special character escape sequences

5

Hi! Thank you for this great library. I am trying to use it to parse [wikipedia dumps](https://dumps.wikimedia.org/) in my project [wikipedia-externallinks-fast-extraction](https://github.com/lovasoa/wikipedia-externallinks-fast-extraction). Unfortunately, they contain [mysql escape characters](https://dev.mysql.com/doc/refman/8.0/en/string-literals.html) that are currently...

panic on macos

3

When running in debug mode, I get ``` thread 'main' panicked at 'assertion failed: backend.is_current()', /Users/olojkine/.cargo/registry/src/github.com-1ecc6299db9ec823/glium-0.23.0/src/context/mod.rs:647:17 stack backtrace: 0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39 1: std::sys_common::backtrace::_print at src/libstd/sys_common/backtrace.rs:70 2: std::panicking::default_hook::{{closure}} at src/libstd/sys_common/backtrace.rs:58...

new optional input: asset_label

2

Fixes https://github.com/actions/upload-release-asset/issues/18

[feature request] default content-type value

3

It would be nice if the content-type were not mandatory, using [`application/octet-stream`](https://www.iana.org/assignments/media-types/application/octet-stream) as a default value. This is the content-type to use for data of an unknown/unspecified type.

Oftentimes, all assets are not of the same importance, and one would like to make one asset more prominent than the others. It would be great if it were possible...

Currently, when running npm install, one gets the following message : > found **38014** vulnerabilities (37995 low, 16 moderate, **3 high**)