cplusplus

• Source

JsPointerToString(NULL, 0, &str);

• Expected
  str = empty string

• Actual
  failed and returns JsErrorNullArgument

I think this should be possible

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/foo",
  "definitions": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "bar.json#"
        },
      },
      "required": [
        "bar"
      ],
    },
    "title": "foo"
  }
}

Running quicktype CLI with this Schema produces

Error

When I try to 'conan install' version-range-based requirements for a package from a GitLab remote package repository, I get an unhelpful Python message "ERROR: 'NoneType' object is not iterable." I believe it's triggered by some faulty implementation on the GitLab repository side, but it would be helpful if Conan provided a more specific indication of the error cause.
My example conanfile.py:
`

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Issue Description

The instructions provided on failed jobs (example) don't clearly explain where to find the generated patch file. This can be a problem for anyone who is not familiar with how Github Actions pages are organized.

The general idea is:

From the details page, click on "Summary", then scroll down to the "Artifacts" secti

The Editor is lagging slow and thus unusuable.
Sometimes even crashes occur.
The Problem may be here: (taken from the CEF log, Messages repeated all over again):

[0823/024737:ERROR:gles2_cmd_decoder.cc(4643)] Error: 5 for Command kPostSubBufferCHROMIUM
[0823/024737:ERROR:gpu_channel_manager.cc(222)] Exiting GPU process because some drivers cannot recover from problems.
[0823/024737:ER

I have noticed that for some enums I have compilation fail (which is good, as I don't want to check if any code has some issues with wrong min/max specification for enum values one by one), but for others it is not complaining at all.

It seems that this happens only if there is a missing enum of value MAGIC_ENUM_RANGE_MAX+1

This is fairly representative example of the code that should fail

This issue documents the progress on adding CI configurations
for supported C++ compilers.

• Default GCC on Ubuntu
• GCC 7 on Ubuntu
• Clang 5 on Ubuntu
• Default Clang on macOS
• Default MSVC on Windows
• MSVC 14.1+ (VS 2017) on Windows
• MinGW (MSYS2) on Windows
• Cygwin on Windows
• LXSS GCC on Windows