What happened:

I tried to use the --make option to pass --jobs=5 to the NodeJS build process.

What you expected to happen:

I expected the NodeJS build to be faster.

What happened:

I was unable to pass the jobs options to the NodeJS make command, here is what happened:

➤  nexe --build --make --jobs=5
ℹ nexe 3.3.2
✔ Node source extracted to: /home/thibault.hi

#1750 shows a way to debloat an object by extracting its encoding / decoding logic into a serializer class.
In this case, the knowledge_plugins.functions.Function moved its serialize and parse_from_cmg methods.

There are several places along the angr codebase where this pattern could be applied:

• angr/knowledge_plugins/cfg/cfg_model.py
• `angr/knowledge_plugins/cfg/cfg

The docs:

For extendEnv

Set to false if you don't want to extend the environment variables when providing the env property.

For env:

Environment key-value pairs. Extends automatically from process.env. Set extendEnv to false if you don't want this.

Having read this, I was under the impression that if you set extendEnv to false, env has no effect at all (which is exactl

I newbie to tf.

I used pip install --ignore-installed --upgrade path/to/my/downloaded/tensorflow-1.14.0-cp37-cp37m-win_amd64.whl --user

it seems to work :-)

An explicit mention on how to install it on Windows machines can help new users.
Anyway, thank for the repo. Starred!

I am trying to detect the MIME type of a .doc file, and the result I get is of type
File type: xls. MIME: application/vnd.ms-excel
or
ile type: ppt. MIME: application/vnd.ms-powerpoint

When a compiled script is run from $PATH it appears to be unable to locate its own file path.

An example with the JRuby bash launcher:

[] ~/projects/jruby $ bin/jruby.bash -e 'puts ENV_JAVA["jruby.home"]'
/Users/headius/projects/jruby

[] ~/projects/jruby $ jruby.bash -e 'puts ENV_JAVA["jruby.home"]'
/Users/headius/projects/jruby

[] ~/projects/jruby $ shc -f bin/jruby.bash -o bin

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'

I would like to contribute to this repo by building certbot for AWS lambda.

Am I correct in assuming that I would have to spin up a AWS linux EC2 instance, and then build certbot in a statically linked manner? How would one do this? I would like to give it a try after being brought into the right direction.

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.

Tests are failing locally on and on Travis.

There is a $40.00 open bounty on this issue. Add more on [Issuehunt](https://issuehunt.io/r/sindresorhus/d

Reproduction steps:

cd /tmp
git clone https://github.com/Microsoft/TypeScript.git
cd TypeScript
npm install nar
./node_modules/nar/bin/nar create --executable
mv *.nar /tmp/typescript.nar
cd /tmp
chmod +x typescript.nar
echo "var x = function() {alert('test');}" > /tmp/test.ts

You now have everything the way I would expect it

# This will fail
cd /tmp
/tmp/typescript.nar exec --out t

As of #304, we progressively import shared references into the content stream, handing them out dense numbers.

We should probably do the same with prelude references, producing a content stream that dynamically assigns consecutive numbers to shared references and prelude references. This may be further improve compression and/or let us better find patterns that work across shared and prelude re

The test files included in binee are built using C++ Redistributable DLLs. To have them run correctly without having to grab DLL piecemeal as they generate errors in binee, the user should install the redistributable package on the system32 machine used to supply DLLs before copying into the mock windows filesystem.

Hello Riki, your serializer looks very promising!

I'm wondering whether its physical format stable enough to be standardized?
Would be great to have a wire-compatible javascript version of the .NET serializer.
Existing formats like Json, Bson or MessagePack are quite limited (don't support circular references, etc).

Regards, Alex