📗 API Reference Docs Problem

• Version: v16.6.2

• Platform: Darwin user.local 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64

• Subsystem: -

Location

Affected URL(s):

• https://nodejs.org/api/errors.html#errors_error_stack

Description

The doc says

The location information will be one of:

I've ran into this issue for a couple hours and I ended up editing the dist library adding two new functions called fetchVideo and bufferToVideo that works pretty much like the fetchImage and bufferToImage functions.

I'll leave it here to help somebody else with the same issue and in case someone wants to include it on future releases.

face-api.js

...
exports.fetchVideo = fetc

This would be a nice little feature to have, Excel users are using this a lot.

Currently, when entering epic mode the README is frozen in the last level of the tower. When you're trying to fine-tune the score for a level other than the last one, it would be helpful if we had the README for that level available. The proposal is that when entering epic mode, the README is updated with all levels, one following the other.

Example:

# Starbolt - beginner

• Source

JsPointerToString(NULL, 0, &str);

• Expected
  str = empty string

• Actual
  failed and returns JsErrorNullArgument

I think this should be possible

For some reason Amazon REST api's require the content-type to be set to "application/x-amz-json-1.1" instead of the standard "application/json"

Currently the content-type header is set automatically for json data overriding any headers passed in to the request.

It would be useful to first check if the header is set before overriding it:

if (!this.request.headers.set('content-type')) {

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

Describe the bug

Opal #to_json adds spaces while Ruby doesn't. That's not a big issue probably, but it is an implementation difference.

Opal version: master and probably all before

To Reproduce

$ opal-repl
>> require 'json'
=> true
>> {a: 5, b: [1,2,3]}.to_json
=> "{\"a\":5, \"b\":[1, 2, 3]}"
>>

$ pry
[1] pry(main)> require 'json'
=> true
[2]