text:
vue-template-compiler double-escaping newlines in _ssrNode text string templates

Version
2.5.9
Reproduction link
https://gist.github.com/2b3c1a683b334022c626917b0abb2adc
(I used a Gist, because ssrCompile is not exposed by the globals build of Vue.)
Steps to reproduce
compiler = require('vue-template-compiler')
template = "
\n<textarea id=\"foo,\nbar\">foo\nbar</textarea>\n
"
result = compiler.ssrCompile(template)
console.log(result.render)
// output: with(this){return _c('div',{attrs:{"id":"foo,\nbar"}},[_ssrNode("<textarea id=\"foo,\\nbar\">foo\nbar</textarea>")])}

What is expected?
vue-template-compiler should not double-escape newlines in attributes for _ssrNode string templates.
What is actually happening?
vue-template-compiler double-escapes newlines in attributes of _ssrNodes.

If you look at the output from the reproduction steps, you will see that the newline character '\n' is only double escaped, if it is part of an attribute in an ssrNode, if is nor optimized to a string template and stored in the attrs property, is it fine and other newlines that are outside attributes are also fine.
The bug was observed with vue-template-compiler v2.5.9 and node.js v8.9.1.
While the above example seems silly, newlines in attribute are very common when using responsive images, with multiple sizes in the srcset attribute, which are usually broken onto one line per size/url for readability and this is how a colleague of mine ran into this bug, where responsive images were working differently between ssr and rehydration due to the problem, because the browser aborted srcset parsing when finding the "\n" literal string.

While the report explicitly mentions newlines, the double escaping also occurs for other escape sequences like \t.

It looks like the attribute is first escaped using JSON.stringify in processAttrs call to addAttr and then finally the whole string template is escaped again using JSON.stringify(textBuffer) inside flattenSegments, which causes the double escaping.

I could fix the problem by applying the following patch to the genAttrSegment function:
diff --git a/src/server/optimizing-compiler/modules.js b/src/server/optimizing-compiler/modules.js
index 41b1af1d..69a7be87 100644
--- a/src/server/optimizing-compiler/modules.js
+++ b/src/server/optimizing-compiler/modules.js
@@ -77,7 +77,7 @@ function genAttrSegment (name: string, value: string): StringSegment {
         ? ` ${name}="${name}"`
         : value === '""'
           ? ` ${name}`
-          : ` ${name}=${value}`
+          : ` ${name}="${JSON.parse(value)}"`
     }
   } else {
     return {


text:
fix(types): fix function prop type inference (fix #9357)

close #9357

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Before this change:
const ComponentWithFunctionProps = Vue.extend({
  props: {
    functionProp: {
      type: Function,
      default: () => true,
    },
    functionPropWithBooleanReturnType: {
      type: Function as PropType<() => boolean>,
      default: () => true,
    },
    booleanProp: {
      type: Boolean,
      default: true,
    },
    booleanPropWithFunctionDefault: {
      type: Boolean,
      default: () => true,
    },
  },
  methods: {
    test(): void {
      // ERROR!
      // (property) functionProp: boolean | Function
      // -------------------------------------------
      // This expression is not callable.
      //   No constituent of type 'boolean | Function' is callable.ts(2349)
      this.functionProp();

      // ERROR!
      // (property) functionPropWithBooleanReturnType: boolean | (() => boolean)
      // -----------------------------------------------------------------------
      // This expression is not callable.
      //   Not all constituents of type 'boolean | (() => boolean)' are callable.
      //     Type 'false' has no call signatures.ts(2349)
      this.functionPropWithBooleanReturnType();

      // const foo: boolean
      const foo = this.booleanProp;

      // const bar: boolean
      const bar = this.booleanPropWithFunctionDefault;
    },
  },
});

After this change:
const ComponentWithFunctionProps = Vue.extend({
  props: {
    functionProp: {
      type: Function,
      default: () => true,
    },
    functionPropWithBooleanReturnType: {
      type: Function as PropType<() => boolean>,
      default: () => true,
    },
    booleanProp: {
      type: Boolean,
      default: true,
    },
    booleanPropWithFunctionDefault: {
      type: Boolean,
      default: () => true,
    },
  },
  methods: {
    test(): void {
      // (property) functionProp: Function
      this.functionProp();

      // (property) functionPropWithBooleanReturnType: () => boolean
      this.functionPropWithBooleanReturnType();

      // const foo: boolean
      const foo = this.booleanProp;

      // const bar: boolean
      const bar = this.booleanPropWithFunctionDefault;
    },
  },
});

@ktsn this might be up your alley!

Also related: https://github.com/microsoft/TypeScript/issues/17574 and https://github.com/vuejs/vue/issues/9873

Note: If it helps with confidence, I've tested that this change works & compiles in a project with 154 different .vue SFC files (consisting of a little over 23,000 lines of code), all using TypeScript.

I've been looking for a solution for some time now, thanks!

Can anyone look at this? I'd really appreciate it!

Hi, is there any update on this?

Can someone look at this? It's been a thorn in our side for a long time.

@ktsn ?

source: gharchive/pull-request

authors: doyaaaaaken kjleitz medinab

repo: vuejs/vue

license: MIT

license_type: permissive

license_source: github-api


text:
change giflossy link

In reference to #15

I will link to generic releases page so that we are not out of date

Thanks

Glad to help :)
Just curious, but have you thought at all about just including the binaries in your project? That's what I did when I used this module

I think I would have to compile the requirements at install time, THought about it but seems error prone.
I cannot put binaries inside the project they would be not compatible between targets (osx, linux). you have to compile them

Ahh ok

authors: vvo zwhitchcox

repo: vvo/gifify

license: ISC


text:
Radial gradient not rendered in button image

Trying to loading a simple svg button ("UIButton.svg") crashes the library.
The SVGViewer exits with the following error:
System.ArgumentException: Invalid ColorBlend object. The positions array must have 1.0 as its last element.
  at System.Drawing.Drawing2D.LinearGradientBrush.set_InterpolationColors (System.Drawing.Drawing2D.ColorBlend value) [0x00077] in /Volumes/build-root-ramdisk/mono-3.4.0/mcs/class/System.Drawing/System.Drawing.Drawing2D/LinearGradientBrush.cs:196

The SVG file is correctly rendered by Chrome. Here is a screenshot:

You can download the UIButton.svg file from this fiddle:
http://jsfiddle.net/EmanueleS/ve3XN/

Wit the currrent version, it looks like this:

So the crash and the text issues are gone, but the radial gradient seems not to be rendered.
Adapting issue title.

Update: after another fix related to feMerge, the button looks like this:

The problem is only the shadow, which is created by a filter. If removing the filter, the button looks good (but without shadow):

As the filters not working are handled in #43, I'm closing this issue.

Turns out the problem have not really been the filters in this case, but the parsing of float numbers in the color matrix on non-English systems. Here is the current rendering for reference:

source: gharchive/issue

authors: Emasoft mrbean-bremen

repo: vvvv/SVG

license: MS-PL


text:
Add missing steps to quick start in README.md

Describe the bug
The quickstart instructions in the README.md are missing a few steps.

Add running ./manage.py createsuperuser
-- Adds first user to database so that user can log in and get the ball rolling.
Add loading the fixtures to the database so the static files are available for first use.
Add step to create WARM database to PostgreSQL server.

To Reproduce
Steps to reproduce the behavior:

Start from scatch using the instructions in  README.md.
Errors are:
a. Error from PostgreSQL when attempting to create tables in database.
b. Unable to login in to application.
c. Error after logging in when application tries to find a profile record for the first user.

Expected behavior
A knowledgeable new user should be able to follow the quick install instructions in the README.md to successfully get the application to run locally.
Desktop (please complete the following information):

OS: All
Browser All
Version 0.91

Issue largely addressed by #260.  Issue can be closed.  If new problems are found, a new issue can be generated with specific information about the defect in documentation.


text:
let g:ale_c_parse_makefile = 1 doesn't work

Information
I want to use let  g:ale_c_parse_makefile =1 to let  ale work with makefile, but it doesn't work as expected
VIM version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Feb  1 2019 09:58:54)
Included patches: 1-865
Operating System: Ubuntu 16.04.4 LTS
What went wrong
I add let g:ale_c_parse_makefile = 1 to my vim configure file, but it does't work
Reproducing the bug

I did this.
I add let g:ale_c_parse_makefile = 1 to my vim configure file, and then  create a file which directory structure like this

├── include
│   ├── mytool1.c
│   └── mytool1.h
├── main.c
└── Makefile

and the content of file like this
----main.c-----
#include<stdio.h>
#include"mytool1.h"

 int main(){
   fn();
return 0;
}

------mytool1.h--------
void fn();

------mytool1.c--------
#include "mytool1.h"
#include<stdio.h>

void fn(){
    printf("hhhhhh\n");
}

------Makefile--------
cc=gcc
include_dir=include
target=main
obj=main.o mytool1.o

$(target):$(obj)
    $(cc) $(obj) -Wall -o $(target)
main.o:main.c
    $(cc) -c main.c -I$(include_dir)
mytool1.o: $(include_dir)/mytool1.c
    $(cc) -c $(include_dir)/mytool1.c
.PHONY:clean
    $(RM) *.o $(target)

we can check the what the makefile will do
root@acnszavl00033:~/temp# make -n
gcc -c main.c -Iinclude
gcc -c include/mytool1.c
gcc main.o mytool1.o  -Wall -o main

the makefile also works right when I use  'make' to generate obj file 'main', and it runs as expecting

Then this happened.
however, when I open main.c, ale still reports errors like this

and this

ale should parse makefile and find the where is 'mytool1,h' and symbol 'fn()'
:ALEInfo
Current Filetype:
Available Linters: []
Enabled Linters: []
Suggested Fixers:
'remove_trailing_lines' - Remove all blank lines at the end of a file.
'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
Linter Variables:
Global Variables:
let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = v:null
let g:ale_command_wrapper = v:null
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = v:null
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = v:null
let g:ale_list_window_size = v:null
let g:ale_loclist_msg_format = v:null
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = v:null
let g:ale_max_signs = v:null
let g:ale_maximum_file_size = v:null
let g:ale_open_list = v:null
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = v:null
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = v:null
let g:ale_sign_style_error = v:null
let g:ale_sign_style_warning = v:null
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = v:null
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1

Hi @sshsu ,
I copied your test project and my linter is properly parsing the include path:
  Command History: (executable check - success) gcc (finished - exit code 0) ['/bin/bash', '-c', 'cd /home/mboros04/Source/test_c && make -n'] (finished - exit code 0) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/home/mboros04/Source/test_c'' -I/home/mboros0 4/Source/test_c/include -std=c11 -Wall - < ''/tmp/nvimOAURvl/2/main.c'''] <<<NO OUTPUT RETURNED>>>
In the ALEInfo you included, it's showing let g:ale_linters = {}, try running ALEInfo with the main.c file open in vim and see what linters are loading. It works for me with let g:ale_linters = {'cpp': ['gcc'], 'rust': ['rls','cargo'],'c': ['gcc']} (only gcc for my c linter), you probably have more linters loading that are throwing erroneous errors because they aren't configured properly for ALE

Hi @sshsu ,
I copied your test project and my linter is properly parsing the include path:
 Command History: (executable check - success) gcc (finished - exit code 0) ['/bin/bash', '-c', 'cd /home/mboros04/Source/test_c && make -n'] (finished - exit code 0) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/home/mboros04/Source/test_c'' -I/home/mboros0 4/Source/test_c/include -std=c11 -Wall - < ''/tmp/nvimOAURvl/2/main.c'''] <<<NO OUTPUT RETURNED>>>
In the ALEInfo you included, it's showing let g:ale_linters = {}, try running ALEInfo with the main.c file open in vim and see what linters are loading. It works for me with let g:ale_linters = {'cpp': ['gcc'], 'rust': ['rls','cargo'],'c': ['gcc']} (only gcc for my c linter), you probably have more linters loading that are throwing erroneous errors because they aren't configured properly for ALE

thank you , I haven't configure any linters and now I add it
let g:ale_linters = {'c': ['gcc'], 'c++': ['g++'] }

gcc linter can be found now , but errors ''mytool1.h 'file not found ' and 'use of undeclared identifier fn' still exist, here is my ale info:
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) gcc
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/temp && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/root/temp'' -std=c11 -Wall - < ''/tmp/vIijnxJ/6/main.c''']

<<<OUTPUT STARTS>>>
<stdin>:3:20: fatal error: mytool1.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

Okay, I have the same ALEInfo on my project but it's working properly, based on the Command History looks like it should work, unfortunately I can't reproduce the error. When I save the file, ALE recognizes the header and drops all errors.

Could you run make -n from the same directory and attach the output? There's probably some difference in the output which ALE isn't parsing properly, perhaps a space in a filesystem path or similar that isn't handled.

I am getting a similar issue.  I am developing a ruby extension in c and want to use ALE as my linter, but it chokes on #include <ruby.h>
The output of make -n:
echo compiling altprintf.c
gcc -I. -I/home/lattis/.local/share/rbenv/versions/2.6.2/include/ruby-2.6.0/i686-linux -I/home/lattis/.local/share/rbenv/versions/2.6.2/include/ruby-2.6.0/ruby/backward -I/home/lattis/.local/share/rbenv/versions/2.6.2/include/ruby-2.6.0 -I. -DRUBY_EXTCONF_H=\"extconf.h\" -I/home/lattis/.local/share/rbenv/versions/2.6.2/include  -D_FILE_OFFSET_BITS=64  -fPIC -O3 -ggdb3 -Wall -Wextra -Wdeclaration-after-statement -Wdeprecated-declarations -Wduplicated-cond -Wimplicit-function-declaration -Wimplicit-int -Wmisleading-indentation -Wpointer-arith -Wrestrict -Wwrite-strings -Wimplicit-fallthrough=0 -Wmissing-noreturn -Wno-cast-function-type -Wno-constant-logical-operand -Wno-long-long -Wno-missing-field-initializers -Wno-overlength-strings -Wno-packed-bitfield-compat -Wno-parentheses-equality -Wno-self-assign -Wno-tautological-compare -Wno-unused-parameter -Wno-unused-value -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wunused-variable  -o altprintf.o -c altprintf.c
echo linking shared-object altprintf.so
rm -f altprintf.so
gcc -shared -o altprintf.so altprintf.o -L. -L/home/lattis/.local/share/rbenv/versions/2.6.2/lib -Wl,-rpath,/home/lattis/.local/share/rbenv/versions/2.6.2/lib -L. -L/home/lattis/.local/share/rbenv/versions/2.6.2/lib  -fstack-protector-strong -rdynamic -Wl,-export-dynamic -L/home/lattis/.local/share/rbenv/versions/2.6.2/lib  -Wl,--compress-debug-sections=zlib    -lm   -lc

ALEInfo:
 Current Filetype: c
Available Linters: ['ccls', 'clang', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder', 'gcc']
  Enabled Linters: ['gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:
let g:ale_c_gcc_executable = 'gcc'
let g:ale_c_gcc_options = '-std=c11 -Wall'
 Global Variables:
let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc'], 'ruby': ['ruby'], 'rust': ['rls']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:
(executable check - success) gcc
(finished - exit code 0) ['/bin/zsh', '-c', 'cd /home/lattis/dev/c/altprintf/gem/ext && make -n']
(finished - exit code 1) ['/bin/zsh', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/home/lattis/dev/c/altprintf/gem/ext'' -std=c11 -Wall - < ''
/tmp/nvimHjEzV8/2/altprintf.c''']
<<<OUTPUT STARTS>>>
<stdin>:1:10: fatal error: ruby.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>
(finished - exit code 0) ['/bin/zsh', '-c', 'cd /home/lattis/dev/c/altprintf/gem/ext && make -n']
(finished - exit code 1) ['/bin/zsh', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/home/lattis/dev/c/altprintf/gem/ext'' -std=c11 -Wall - < ''
/tmp/nvimHjEzV8/3/altprintf.c''']
<<<OUTPUT STARTS>>>
<stdin>:1:10: fatal error: ruby.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>
(finished - exit code 0) ['/bin/zsh', '-c', 'cd /home/lattis/dev/c/altprintf/gem/ext && make -n']
(finished - exit code 1) ['/bin/zsh', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/home/lattis/dev/c/altprintf/gem/ext'' -std=c11 -Wall - < ''
/tmp/nvimHjEzV8/4/altprintf.c''']
<<<OUTPUT STARTS>>>
<stdin>:1:10: fatal error: ruby.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

C file:
#include <ruby.h>

Can you share a link to your project? If I can try to compile the same code, I might be able to repeat a bug.

okay, here is a project that reproduces my issue: https://github.com/annacrombie/effective-octo-rotary-phone.  Note that Makefile and extconf.h were generated by running the extconf.rb script.  You need to re-run that script to regenerate the Makefile with the correct path to your ruby headers.

question
here is also a same question, project is here:  https://github.com/meetecho/janus-gateway, proceure of installation might be a little complicated, when anything confiugre done， ALE reports error like this in file 'pulgin.h' :

however,  glib can be found by Makefile , it should not be wrong, so I check my ALEinfo then find ALE treats  file 'plugin.h' as a c++ project  file instead a c project  file so ale doesn't load a lot of compile options from Makefile.
aleinfo
here is my ALEInfo when I generate it  in file 'plugin.h'
 Current Filetype: cpp
Available Linters: ['ccls', 'clang', 'clangcheck', 'clangd', 'clangtidy', 'clazy', 'cppcheck', 'cpplint', 'cquery', 'flawfinder', 'gcc']
   Linter Aliases:
'gcc' -> ['g++']
  Enabled Linters: ['ccls', 'clang', 'clangcheck', 'clangd', 'clangtidy', 'clazy', 'cppcheck', 'cpplint', 'cquery', 'flawfinder', 'gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_cpp_ccls_executable = 'ccls'
let g:ale_cpp_ccls_init_options = {}
let g:ale_cpp_clang_executable = 'clang++'
let g:ale_cpp_clang_options = '-std=c++14 -Wall'
let g:ale_cpp_clangcheck_executable = 'clang-check'
let g:ale_cpp_clangcheck_options = ''
let g:ale_cpp_clangd_executable = 'clangd'
let g:ale_cpp_clangd_options = ''
let g:ale_cpp_clangtidy_checks = []
let g:ale_cpp_clangtidy_executable = 'clang-tidy'
let g:ale_cpp_clangtidy_options = ''
let g:ale_cpp_clazy_checks = ['level1']
let g:ale_cpp_clazy_executable = 'clazy-standalone'
let g:ale_cpp_clazy_options = ''
let g:ale_cpp_cppcheck_executable = 'cppcheck'
let g:ale_cpp_cppcheck_options = '--enable=style'
let g:ale_cpp_cpplint_executable = 'cpplint'
let g:ale_cpp_cpplint_options = ''
let g:ale_cpp_cquery_cache_directory = '/root/.cache/cquery'
let g:ale_cpp_cquery_executable = 'cquery'
let g:ale_cpp_flawfinder_executable = 'flawfinder'
let g:ale_cpp_flawfinder_minlevel = 1
let g:ale_cpp_flawfinder_options = ''
let g:ale_cpp_gcc_executable = 'gcc'
let g:ale_cpp_gcc_options = '-std=c++14 -Wall'
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc', 'cppcheck'], 'c++': ['g++', 'cppcheck']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) clang++
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(executable check - success) clang-check
(finished - exit code 1) ['/bin/bash', '-c', '''clang-check'' -analyze ''/root/git/janus-gateway/plugins/plugin.h'' -extra-arg -Xclang -extra-arg -analyzer-output=text']

<<<OUTPUT STARTS>>>
Error while trying to load a compilation database:
Could not auto-detect compilation database for file "/root/git/janus-gateway/plugins/plugin.h"
No compilation database found in /root/git/janus-gateway/plugins or any parent directory
json-compilation-database: Error while opening JSON database: No such file or directory
Running without flags.
/root/git/janus-gateway/plugins/plugin.h:158:10: fatal error: 'glib.h' file not found
#include <glib.h>
         ^
1 error generated.
Error while processing /root/git/janus-gateway/plugins/plugin.h.
<<<OUTPUT ENDS>>>

(executable check - failure) clang-tidy
(executable check - failure) clazy-standalone
(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c++ --enable=style ''/tmp/v3Pza6Q/10/plugin.h''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(executable check - failure) cpplint
(executable check - failure) flawfinder
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''clang++'' -S -x c++ -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c++14 -Wall - < ''/tmp/v3Pza6Q/11/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:10: fatal error: 'glib.h' file not found
#include <glib.h>
         ^
1 error generated.
<<<OUTPUT ENDS>>>

(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c++ -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c++14 -Wall - < ''/tmp/v3Pza6Q/12/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:18: fatal error: glib.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

guess and verify
in order to verify my guess, I open another file 'videoroom.c' within this project, then generate aleinfo, it  tell clearly this is a c project file.  so , for this problem , it is because ale treats file 'plugin.h' as a c++ project file  only according to file name suffix  '.h'  but it actually a c project file which leads to ale chosees a wrong linter and doesn't load compile option.
here is my ALEInfo when I generate it  in file 'videoroom.c'
 Current Filetype: c
Available Linters: ['ccls', 'clang', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder', 'gcc']
  Enabled Linters: ['cppcheck', 'gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_c_cppcheck_executable = 'cppcheck'
let g:ale_c_cppcheck_options = '--enable=style'
let g:ale_c_gcc_executable = 'gcc'
let g:ale_c_gcc_options = '-std=c11 -Wall'
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc', 'cppcheck'], 'c++': ['g++', 'cppcheck']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) cppcheck
(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c --enable=style ''/tmp/vP5t40g/6/janus_videoroom.c''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(executable check - success) gcc
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' --silent --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"Janus\ WebRTC\ Server\" -DPACKAGE_TARNAME=\"janus-gateway\" -DPACKAGE_VERSION=\"0.7.0\" -DPACKAGE_STRING=\"Janus\ WebRTC\ Server\ 0.7.0\" -DPACKAGE_BUGREPORT=\"https://github.com/meetecho/janus-gateway\" -DPACKAGE_URL=\"https://janus.conf.meetecho.com\" -DPACKAGE=\"janus-gateway\" -DVERSION=\"0.7.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PORTRANGE=1 -DHAVE_LIBNICE_TCP=1 -DHAVE_SRTP_2=1 -DHAVE_SRTP_AESGCM=1 -DHAVE_LIBCURL=1 -DHAVE_TURNRESTAPI=1 -DHAVE_SAMPLEEVH=1 -DHAVE_WEBSOCKETS=1 -DHAVE_LIBWEBSOCKETS_PEER_SIMPLE=1 -DHAVE_PFUNIX=1 -I/root/git/janus-gateway/. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fPIC -fstack-protector-all -fstrict-aliasing -ggdb3 -pthread -Wall -Warray-bounds -Wextra -Wformat-nonliteral -Wformat-security -Wformat=2 -Winit-self -Winline -Wlarger-than=65537 -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wno-aggregate-return -Wno-missing-field-initializers -Wno-redundant-decls -Wno-undef -Wno-unused-parameter -Wold-style-definition -Wpacked -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wswitch-default -Wunused -Wwrite-strings -Wcast-align -Wno-override-init -Wunsafe-loop-optimizations -Wunused-but-set-variable -MT plugins/plugins_libjanus_videoroom_la-janus_videoroom.lo -MD -MP -MF plugins/.deps/plugins_libjanus_videoroom_la-janus_videoroom.Tpo -f ''plugins/janus_videoroom.c'' || echo ''./''`plugins/janus_videoroom.c -std=c11 -Wall - < ''/tmp/vP5t40g/7/janus_videoroom.c''']

<<<OUTPUT STARTS>>>
/bin/bash: -c: line 0: unexpected EOF while looking for matching ``'
/bin/bash: -c: line 1: syntax error: unexpected end of file
<<<OUTPUT ENDS>>>

need  && help
so Is there any configuration in ale  which make files with suffix  '.h' recongnized to c project files?
thanks~

@sshsu
If you run the command :se ft, you'll see what filetype vim is associating with .h files. Most likely it's cpp.
ALE get's the file type from vim, you can test this by running the command set filetype=c and then running ALEInfo again

@mboros1
follow your advice, I open file 'plugin.h' and use command set filetype=c and test the file type is 'c' then generate aleinfo
 Current Filetype: c
Available Linters: ['ccls', 'clang', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder', 'gcc']
  Enabled Linters: ['cppcheck', 'gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_c_cppcheck_executable = 'cppcheck'
let g:ale_c_cppcheck_options = '--enable=style'
let g:ale_c_gcc_executable = 'gcc'
let g:ale_c_gcc_options = '-std=c11 -Wall'
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc', 'cppcheck'], 'c++': ['g++', 'cppcheck']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) clang++
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(executable check - success) clang-check
(finished - exit code 1) ['/bin/bash', '-c', '''clang-check'' -analyze ''/root/git/janus-gateway/plugins/plugin.h'' -extra-arg -Xclang -extra-arg -analyzer-output=text']

<<<OUTPUT STARTS>>>
Error while trying to load a compilation database:
Could not auto-detect compilation database for file "/root/git/janus-gateway/plugins/plugin.h"
No compilation database found in /root/git/janus-gateway/plugins or any parent directory
json-compilation-database: Error while opening JSON database: No such file or directory
Running without flags.
/root/git/janus-gateway/plugins/plugin.h:158:10: fatal error: 'glib.h' file not found
#include <glib.h>
         ^
1 error generated.
Error while processing /root/git/janus-gateway/plugins/plugin.h.
<<<OUTPUT ENDS>>>

(executable check - failure) clang-tidy
(executable check - failure) clazy-standalone
(executable check - success) cppcheck
(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c++ --enable=style ''/tmp/v2WHNNH/6/plugin.h''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(executable check - failure) cpplint
(executable check - failure) flawfinder
(executable check - success) gcc
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c++ -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c++14 -Wall - < ''/tmp/v2WHNNH/7/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:18: fatal error: glib.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

(finished - exit code 1) ['/bin/bash', '-c', '''clang++'' -S -x c++ -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c++14 -Wall - < ''/tmp/v2WHNNH/8/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:10: fatal error: 'glib.h' file not found
#include <glib.h>
         ^
1 error generated.
<<<OUTPUT ENDS>>>

(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c --enable=style ''/tmp/v2WHNNH/11/plugin.h''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c11 -Wall - < ''/tmp/v2WHNNH/12/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:18: fatal error: glib.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

we can see the error:  "Could not auto-detect compilation database for file "/root/git/janus-gateway/plugins/plugin.h, No compilation database found in /root/git/janus-gateway/plugins or any parent directory".
I wonder  is the command  set filetype=c was executed so late since ale has detected filetype when open file and loaded compilation database; So I add /* vim: ft=c */   at the top of file(or the end ) in order to change filetype from cpp to c, however it doesn't change file type and I don't know why; Then I directly rename plugin.h to plugin.c, and the filetype is 'c' now and there is no error, aleinfo like this:
 Current Filetype: c
Available Linters: ['ccls', 'clang', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder', 'gcc']
  Enabled Linters: ['cppcheck', 'gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_c_cppcheck_executable = 'cppcheck'
let g:ale_c_cppcheck_options = '--enable=style'
let g:ale_c_gcc_executable = 'gcc'
let g:ale_c_gcc_options = '-std=c11 -Wall'
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc', 'cppcheck'], 'c++': ['g++', 'cppcheck']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) cppcheck
(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c --enable=style ''/tmp/vJkXQZk/6/plugin.c''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(executable check - success) gcc
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -DPACKAGE_NAME=\"Janus\ WebRTC\ Server\" -DPACKAGE_TARNAME=\"janus-gateway\" -DPACKAGE_VERSION=\"0.7.0\" -DPACKAGE_STRING=\"Janus\ WebRTC\ Server\ 0.7.0\" -DPACKAGE_BUGREPORT=\"https://github.com/meetecho/janus-gateway\" -DPACKAGE_URL=\"https://janus.conf.meetecho.com\" -DPACKAGE=\"janus-gateway\" -DVERSION=\"0.7.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PORTRANGE=1 -DHAVE_LIBNICE_TCP=1 -DHAVE_SRTP_2=1 -DHAVE_SRTP_AESGCM=1 -DHAVE_LIBCURL=1 -DHAVE_TURNRESTAPI=1 -DHAVE_SAMPLEEVH=1 -DHAVE_WEBSOCKETS=1 -DHAVE_LIBWEBSOCKETS_PEER_SIMPLE=1 -DHAVE_PFUNIX=1 -I/root/git/janus-gateway/. -pthread -I/usr/include/nice -I/usr/include/gupnp-igd-1.0 -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/uuid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DPLUGINDIR=\"/opt/janus/lib/janus/plugins\" -DTRANSPORTDIR=\"/opt/janus/lib/janus/transports\" -DEVENTDIR=\"/opt/janus/lib/janus/events\" -DCONFDIR=\"/opt/janus/etc/janus\" -g -O2 -fPIC -fstack-protector-all -fstrict-aliasing -ggdb3 -pthread -Wall -Warray-bounds -Wextra -Wformat-nonliteral -Wformat-security -Wformat=2 -Winit-self -Winline -Wlarger-than=65537 -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wno-aggregate-return -Wno-missing-field-initializers -Wno-redundant-decls -Wno-undef -Wno-unused-parameter -Wold-style-definition -Wpacked -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wswitch-default -Wunused -Wwrite-strings -Wcast-align -Wno-override-init -Wunsafe-loop-optimizations -Wunused-but-set-variable -MT plugins/janus-plugin.o -MD -MP -MF plugins/.deps/janus-plugin.Tpo -f ''plugins/plugin.c'' || echo ''./''`plugins/plugin.c -std=c11 -Wall - < ''/tmp/vJkXQZk/7/plugin.c''']

how can I make vim file type detectation for all file with suffix .h to 'c' file?

If you add:
au BufRead,BufNewFile *.h set filetype=c
to your .vimrc for vim or init.vim file in neovim it should work. Works in neovim, I don't use vim but I'm guessing it's the same or similar. Not sure if this is the best way to do this but I had a similar problem with *.rs files getting associated to something other then Rust and it fixed it.
Let us know if this fixes the problem, probably should based on your test with changing the file extension to .c

sorry for late, command au BufRead,BufNewFile *.h set filetype=c  makes effect on changing filetype which with suffix *.h from cpp file to c file, however, compile options still not  be loaded, ALEInfo like this:
 Current Filetype: c
Available Linters: ['ccls', 'clang', 'clangd', 'clangtidy', 'cppcheck', 'cquery', 'flawfinder', 'gcc']
  Enabled Linters: ['cppcheck', 'gcc']
 Suggested Fixers:
  'clang-format' - Fix C/C++ and cuda files with clang-format.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'uncrustify' - Fix C, C++, C#, ObjectiveC, ObjectiveC++, D, Java, Pawn, and VALA files with uncrustify.
 Linter Variables:

let g:ale_c_cppcheck_executable = 'cppcheck'
let g:ale_c_cppcheck_options = '--enable=style'
let g:ale_c_gcc_executable = 'gcc'
let g:ale_c_gcc_options = '-std=c11 -Wall'
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%severity%: %linter%: %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'c': ['gcc', 'cppcheck'], 'c++': ['g++', 'cppcheck']}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%severity%: %linter%: %s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '✖'
let g:ale_sign_info = 'ⓘ'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '✖'
let g:ale_sign_style_warning = '⚠'
let g:ale_sign_warning = '⚠'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) cppcheck
(finished - exit code 1) ['/bin/bash', '-c', '''cppcheck'' -q --language=c --enable=style ''/tmp/vWK2wOP/6/plugin.h''']

<<<OUTPUT STARTS>>>
cppcheck: Failed to load library configuration file 'std.cfg'. File not found
(information) Failed to load std.cfg. Your Cppcheck installation is broken, please re-install. The Cppcheck binary was compiled without CFGDIR set. Either the std.cfg should be available in cfg or the CFGDIR should be configured.
<<<OUTPUT ENDS>>>

(executable check - success) gcc
(finished - exit code 0) ['/bin/bash', '-c', 'cd /root/git/janus-gateway && make -n']
(finished - exit code 1) ['/bin/bash', '-c', '''gcc'' -S -x c -fsyntax-only -iquote ''/root/git/janus-gateway/plugins'' -std=c11 -Wall - < ''/tmp/vWK2wOP/7/plugin.h''']

<<<OUTPUT STARTS>>>
<stdin>:158:18: fatal error: glib.h: No such file or directory
compilation terminated.
<<<OUTPUT ENDS>>>

Header files aren't translation units, so there's no command for compiling them. I might patch the code so the options for C files with a similar name are used to get the options. Otherwise the best you could do is grab all of the options in common for all files that will be compiled and hope that it works.

I've had no problem with linting header files in my projects as long as the file is included by a .cpp/.c file that is being compiled in the Makefile. Because my projects are fairly small, everything under 10k lines of code, I've had no issues just using gcc as a linter. Is that not intended to be working right now?
@sshsu
So it looks like your cppcheck is failing because your std.cfg file is not set up? I'm not familiar with cppcheck but most likely it needs some configuration to work properly.
In the output of your gcc, it's saying
<stdin>:158:18: fatal error: glib.h: No such file or directory
Are you able to compile the project successfully? The project has a ton of dependencies so I didn't really have time to test it, but on your end it looks like the error is that ALE cannot find glib.h using the Makefile.
I was able to get mine to work by making sure I had a project that compiled by simply using make, then using gcc as my only linter and checking the errors to see why it wasn't compiling. Also, with clangd as a linter, it worked very well with minimal set up, just needed to install the latest version. But, I'm only really writing C++ code not C.

I've had no problem with linting header files in my projects as long as the file is included by a .cpp/.c file that is being compiled in the Makefile. Because my projects are fairly small, everything under 10k lines of code, I've had no issues just using gcc as a linter. Is that not intended to be working right now?
@sshsu
So it looks like your cppcheck is failing because your std.cfg file is not set up? I'm not familiar with cppcheck but most likely it needs some configuration to work properly.
In the output of your gcc, it's saying
<stdin>:158:18: fatal error: glib.h: No such file or directory
Are you able to compile the project successfully? The project has a ton of dependencies so I didn't really have time to test it, but on your end it looks like the error is that ALE cannot find glib.h using the Makefile.
I was able to get mine to work by making sure I had a project that compiled by simply using make, then using gcc as my only linter and checking the errors to see why it wasn't compiling. Also, with clangd as a linter, it worked very well with minimal set up, just needed to install the latest version. But, I'm only really writing C++ code not C.

I would thanks if  you patch the code

What do you suggest?

@mboros1 yeah, there are some problems with my cppcheck and I I haven't had time to fix it yet,  and I can  compile this project and run it. It might be like w0rp say that 'Header files aren't translation units, so there's no command for compiling them'

What do you suggest?
I trust your conclusion 'Header files aren't translation units, so there's no command for compiling them'. So can you patch the code so the options for C files with a similar name are used to get the options for circumstance like this?

ALE can lint header files as long as they are included by a source code file that is being compiled and there's a makefile that can be properly parsed.
If gcc and ale_c_parse_makefile are not working, it's generally because the way ALE parses makefile's needs a lot of work on anything that isn't simple; there are many makefiles that can compile that ALE parses in a way that does not compile. For my projects, I just tweak the makefile till ALE can figure it out.
It would be a nice project for someone to pick up; taking a fairly complex project makefile from github and working on the ALE makefile parser till it works.

license_source: bigquery


text:
add joker handler for clojure

Adds new linter for clojure using joker
https://github.com/candid82/joker
I haven't tested with clojurescript, edn, or joker (the dialect of clojure implemented by the joker interpreter), but the linter mode appears to support all three in addition to clojure (although it might need a option or something for handling files from stdin)
can I just add that this is the nicest vim plugin that I have ever worked on, really clear and easy to use API's, guidelines, tests, etc!
fixes #975
ref #544 #1040

Cheers! :beers:

Looks like a laugh and a half.

dad?


text:
Diagonal fill in diff editor is displayed incorrectly in Firefox

Possibly related, although not on win: https://github.com/microsoft/vscode/issues/107153


text:
Coinversation Stablecoin

Grant Application
This application is (select one):

[x] Speculative (use this by default)
[ ] an RFP response

This application is (select one):

[x] Public (fully)
[ ] Public with private finances

Abstract
[Provide a brief description of your project here (summarise key points).
If your application is part of a programme, please mention which in the first line of the abstract.
The details should be in the application 'document' that you add to this repo via a pull request.]
Checklist

[x] The grants document has been read and understood.
[x] The Google Form will be completed accurately. Note that the Google Form requires the pull request URL.
[x] Abstract (above) is succinct and complete.
[x] The application is being included into the correct directory: either 'targeted' or 'speculative'.
[x] The application includes a project description.
[x] The application includes all names of team members.
[x] The application includes a description of the team's experience.
[x] The application includes all necessary links (e.g. GitHub and LinkedIn)
[x] The "Development Roadmap" section in the application has a timeline of development ("milestones").
[x] The "Development Roadmap" section in the application has an estimate of funds required.
[x] The "Development Roadmap" section gives an indication of the team's long term plans.
[x] The "Development Roadmap" section includes documentation as a deliverable for at least one milestone.

I’m closing the application, since you also applied via the open grants program. Feel free to reopen the application if you want to focus on the general grants program instead.


text:
🛑 Wayback Archiver Documentation is down

In 7f44c49, Wayback Archiver Documentation (https://initium.eu.org) was down:

HTTP code: 503
Response time: 1117 ms

Resolved: Wayback Archiver Documentation is back up in 02573e5.

repo: wabarc/status


text:
Question: How do you associate layers and filesystem changes?

Hi,
I recently found your tool because I'd like to do some custom image analysis myself and it has already been very useful! There's just one more thing I'd like to confirm with your help.
The Docker archive contains a manifest.json which points to another file which is kind of the config file (also JSON). It contains a rootfs field and a history field. This is what you're using to associate a layer and its filesystem changes, right? Here's an example:
{
  "created": "2020-01-23T23:05:05.035158536Z",
  "architecture": "amd64",
  "os": "linux",
  "config": {
    "Env": [
      "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
      "URL=https://danjou.gitlab.io/goup/builds/goup_0.2.2_amd64.tar.gz"
    ],
    "Cmd": [
      "/bin/sh"
    ]
  },
  "rootfs": {
    "type": "layers",
    "diff_ids": [
      "sha256:5216338b40a7b96416b8b9858974bbe4acc3096ee60acbc4dfb1ee02aecceb10",
      "sha256:84d37ff1ac0ca62587a1639d3e9fb0e78bff2e94389b684b9f622e09f50e3a8a",
      "sha256:bdaa31f83b57d4f34e3f8d8008c0713ada4beb12a594f99509b025e73d96011d"
    ]
  },
  "history": [
    {
      "created": "2020-01-18T01:19:37.02673981Z",
      "created_by": "/bin/sh -c #(nop) ADD file:e69d441d729412d24675dcd33e04580885df99981cec43de8c9b24015313ff8e in / "
    },
    {
      "created": "2020-01-18T01:19:37.187497623Z",
      "created_by": "/bin/sh -c #(nop)  CMD [\"/bin/sh\"]",
      "empty_layer": true
    },
    {
      "created": "2020-01-23T23:04:53.473947968Z",
      "created_by": "/bin/sh -c apk add --quiet --no-progress --no-cache bash curl libarchive-tools"
    },
    {
      "created": "2020-01-23T23:04:57.969478831Z",
      "created_by": "/bin/sh -c #(nop) ENV URL=\"https://danjou.gitlab.io/goup/builds/goup_0.2.2_amd64.tar.gz\"",
      "empty_layer": true
    },
    {
      "created": "2020-01-23T23:05:05.035158536Z",
      "created_by": "/bin/sh -c curl -sL ${URL} | bsdtar -x -f - \u0026\u0026 mv /goup_0.2.2_amd64/goup /usr/local/bin"
    }
  ]
}

As you can see there are 3 layer diff IDs but 5 history elements. Are you simply going through them in order while ignoring the empty layers and it all works out nicely?
Thanks in advance :)

Indeed! As you've found out, there it not a 1:1 relationship between layer contents and the history, and in short, yes what you described is exactly what I'm doing:  Since the Dockerfile format is essentially annotated bash, there are some annotations (like the ENV entry above) that don't create file system changes, thus, no diffid is needed. Also, Docker is doing some investigation before and after running commands to determine if there was a change in the underlying filesystem, again, not assigning a diffid if there are no filesystem changes. In case you're curious, here is where dive is doing this work, which is entirely leveraging the empty_layer field to determine which history entries to "ignore".
Something to note, I've found that history is not a required field in the docker image format... that is, I've run into a few images built by other tools that Docker will run that did not have history entries.
Docker has a write up of what to expect in an image archive documented here, also be sure to checkout this blog post on Docker image IDs and how they have changed overtime.
Shout out if you build something fun!

authors: dAnjou wagoodman

repo: wagoodman/dive


text:
User with all permissions can't see any images in the ImageChooser modal

Issue Summary
A User with staff status, in group Editors and Moderators with all permissions assigned (also the groups have all permissions assigned) can't see any images in the ImageChooser modal. But the user can see all the images on the image page itself. And it is also possible to add a new image in the modal (that is then correctly used in the streamfield).  But even the newly added image is not shown in the modal after going back to it.

Steps to Reproduce

Checkout current bakerydemo projekt
Make bakerydemo projekt run
Add a User account with Statt status, and all Permissions assigned
Log into this account
Edit the Welcome to the Wagtail Bakery! page
Click on the three dots next to an image and select Change Image
Image Chooser shows no images

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: 3.11
Django version: 5.1.3
Wagtail version: 6.3

@gasman thanks for the elaborated help (as always). Indeed setting the permission in the Group directly in Wagtail fixes the issue. In my project the initial data is also loaded via fixtures. maybe that is the same problem as it is in the bakerydemo. I might try and fix this here as well!

Looks like this may be a core Wagtail bug after all...
The migration wagtailadmin.0001_create_admin_access_permissions defines the access_admin permission and assigns it to the Editors and Moderators groups. Migration wagtailimages.0023_add_choose_permissions (and correspondingly wagtaildocs.0011_add_choose_permissions) assigns choose_image permission to all groups that have access_admin. However, there's nothing to guarantee that the wagtailadmin migration runs first - if wagtailimages runs first instead, it will have no effect.
It should be an easy fix (add an explicit dependency to the wagtailimages and wagtaildocs migrations) - but I'd be keen to find out what causes this to happen on bakerydemo but not a wagtail start project. (It's not the ordering in INSTALLED_APPS, which was my first guess...) It's a little surprising that this hasn't been noticed before now - if this only started recently (perhaps something changed in Django 5.1?) then this may be worth addressing in a patch release.

authors: bruecksen gasman

repo: wagtail/bakerydemo


text:
Rename test.yml to ci.yml

File contains more than testing and this aligns with other Wagtail projects naming of the same kind of file
Prep for #189 (best to have this as a separate commit so we do not lose the file history)

conflicts fixed - merging in - thanks @allcaps

repo: wagtail/guide


text:
feat: Allow React Streamfield to work with >=3 Django

As others have noticed, using the Streamfield and django >= 3 no longer supports django.utils.six.
Solves: https://github.com/wagtail/wagtail-react-streamfield/issues/55

Can anybody accept this, please?

Hm, I tried this fix but I don't see any changes to the StreamField. It's the first time I'm trying this package though, so I'm not sure if the documentation about using it is incomplete or if there is some other problem.

@BertrandBordage Please, accept this, we need in our project. Thanks

@mariod3w  Fwiw, I simply added this to my deploy script:
sed -i "s/from django.utils.six import wraps/from six import wraps/" /path/to/venv/site-packages/wagtail_react_streamfield/monkey_patch.py

imho, the import should be from functools import wraps since this package requires Wagtail >= 2.6 which only supports Python 3.5+ and six.wraps does the same for Python >= 3.4
Other than that 👍 for merge and new version release

I’ll merge this tomorrow with @zerolab’s suggestion to use from functools import wraps, unless someone can think of a way why this is bad idea that has escaped us.
Judging by the code it seems pretty clear that there is no reason to use six considering our support targets, https://github.com/benjaminp/six/blob/c0be8815d13df45b6ae471c4c436cce8c192245d/six.py#L836-L837.

FYI I’ve set up a #react-streamfield channel on the Wagtail Slack if anyone wants to discuss maintenance of this project.

Thank you all, this is now released on PyPI as v1.3.6. It’s my first time publishing a release on this project so would appreciate if a few of you @colinappnovation @andsimakov @mariod3w @nkuttler tried it out on your projects and reported back.
I’ve also tried it out on https://github.com/thibaudcolas/wagtail_react_streamfield_demo but this is obviously just a toy project set up in a hurry.

authors: andsimakov colinappnovation mariod3w nkuttler thibaudcolas zerolab

repo: wagtail/wagtail-react-streamfield


text:
Page in workflow can't be locked

Issue Summary

When a page is in a workflow, it can't be 'personally' locked, the page is shown as 'Locked', but when checking the page.locked, it returns False. (It can be locked via shell/command line, by setting page.locked to True and locked_by to whichever user you want it to be locked by)
Steps to Reproduce

Submit a page to workflow
Lock toggle is hidden (page is shown as locked, and can't be locked)

Thanks for the report! I can confirm this is a regression in a743bf962de7d59889ab23d7639eb4550303f9a2.

I tried having a go at this in #9946, but I think I found a reason why we lost this feature.
Before 4.0, the "Locked/Unlocked" information in the status side panel relies only on "manual" locks (aka BasicLock introduced in #8911), i.e. whether someone has explicitly locked a page. If a page gets "locked" by a workflow, it doesn't count -- the info still says "Unlocked". So, both editors and reviewers will see the status as "Unlocked" (but only reviewers can see the "Lock" button). Pic:

In 4.0, we "lock" pages that are scheduled for publishing (#8917). As with the workflow lock, this is different from the "manual" lock. When we added this, we also updated the status panel info to better reflect the state of the page (whether it can be edited or not):

Show the status title as "Locked" if there's either a scheduled publishing lock, a manual lock, or a workflow lock (in that order).

Even if the lock doesn't apply to the user (e.g. it's a workflow lock and the user is a reviewer), it still says "Locked", but the description will say "You can edit this page, but others may not". It only says "Unlocked" if there's no lock at all.

Only show the "Lock" button if the user has permission to manually lock the page and there is no lock at all.

This is what causes the issue, as now it's impossible to manually lock a page that already has a workflow lock.
I tried re-enabling this feature, but it means there's this weird state where the title says "Locked" (because it's in a workflow), but you can still lock it... I tried changing the description to clear it up a bit, but it still looks a bit weird to me:

Maybe we could improve this by making the title clearer, e.g. "Locked for moderation", "Locked by X", etc. Or, we could also make the title say "Locked"/"Unlocked" depending on whether the lock applies to the current user, rather than whether there's a lock or not.
It would be nice if we could fix this for 4.2, but considering that we've lost this ability since 4.0 and it's not a straightforward fix as I initially thought, we might have to fix this in 4.3 instead.

Considering that we'll likely need some design changes and new translatable strings, I'll bump this to 5.0. If other core team members have a different opinion, feel free to discuss.

authors: WilliamHenryTanza laymonage

repo: wagtail/wagtail


text:
Fix russian translation

Thanks for contributing to Wagtail! 🎉
Before submitting, please review the contributor guidelines https://docs.wagtail.io/en/latest/contributing/index.html and check the following:

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing)
Does the code comply with the style guide? (Run make lint from the Wagtail root)
For Python changes: Have you added tests to cover the new/fixed behaviour?
For front-end changes: Did you test on all of Wagtail’s supported environments?

Please list the exact browser and operating system versions you tested.
Please list which assistive technologies you tested.

For new features: Has the documentation been updated accordingly?

Thanks for the fix @andycraft! I've now updated this on Transifex, where our translations are managed - if you have any further fixes in future, you're very welcome to join the Transifex group and submit them directly.

authors: andycraft gasman


text:
🛑 Gitlab is down

In 2311fea, Gitlab (https://$GITLAB_HOST) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gitlab is back up in a90d806 after 40 minutes.

repo: waja/cyconet-upptime


text:
chore: bump all libp2p packages to latest version

Problem

libp2p released new versions of packages, which include react native support
Solution

bump all libp2p packages to latest version
Notes

Resolves #1772

Lots of fails @adklempner
We can move this to draft until it's ready

repo: waku-org/js-waku


text:
added emqx png icon

Signed-off-by: Stas Yakobov 16795594+fire1ce@users.noreply.github.com

wrong PR

repo: walkxcode/Dashboard-Icons


text:
Viewer bug

The viewer , when an unr is placed on it , shows a different model and always the same

Right now, it's a demo.
I can change the model loaded, by setting the facility array value:
https://github.com/wallabyway/powerBI-tandem-viewer/blob/67b1ce79258b426a46ef59c168c8fda9a4aec385/src/visual.ts#L57
in this case, I'm choosing
allFacilities[2]
Note, that I must add the service account and generate my 2-legged token...
https://wallabyway.github.io/dummy-docs/gettingStarted/intro.html#adding-permissions-to-tandem
This walkthrough might help:
https://github.com/wallabyway/tandem-api-hello-world

repo: wallabyway/powerBI-tandem-viewer


text:
Refeactor the config format to have a listener and backend sections

Here's another way to go about organizing the config. Let me know if you like it. If not, no worries. It's mostly personal preference.

Much cleaner. Really like the new config structure.

authors: skyec waltzofpearls

repo: waltzofpearls/relay-api

license: mit


text:
Cannot add user to local wandb

Weights and Biases version: version 0.8.36
Python version: 3.6.9
Operating System: Ubuntu 16.04
Description
After setting up local wandb I go to http://<host>:8080/admin/users and try to add another user via "Add user" button.
I expect it to generate an invitation link for a new user.
What I Did
When I press submit button, I get an error message:
only admins can use createUser()

There are two users in the table. The first one is the default user that has the same name as my ubuntu account. The second one is the user I created after I set up wandb client.

You can open the Chrome developer console and run the following command to get admin access.  We're working on a new release to fix this that should go out in the next couple days:
document.cookie = "use_admin_privileges=true;"

Thanks!
It worked for me.
I guess, I shouldn't close the issue though, so you will be able to link the fix.

Fixed in wandb/local:0.9.16

authors: cvphelps hokmund vanpelt

repo: wandb/client


text:
[Q] Hyperband badly documented. min_iter doesn't do what is expected

I am trying to run a sweep with hyperband but I am facing two issues. First, the documentation on wandb is quite lacking. Nowhere it says what the 4 parameters are supposed to mean (it does direct you to the paper, but it's complex to understand those even from there).
Second, the min_iter parameter for hyperband, should specify the minimum iteration before stopping? If so it's not working, no matter what I put for min_iter (and also for s) it stops as early as 2 iterations into the process. I want it to carry out for at least 7. Here is the code:
early_terminate:
  type: hyperband
  s: 2
  min_iter: 7
  max_iter: 19

Sorry - I will do a pass on the docs at https://docs.wandb.ai/sweeps/configuration#stopping-criteria and add some examples.   You should only define min_iter or max_iter and this will define the bands where a run might stop. So if you set eta to 3 (default), max_iter to 19 and s to 2 you will get brackets at floor(19/3)=6 and floor(19/3^2)=2.
Does this make sense? This is a little hard to explain.

Hi @jbmorgado could you please share a link to the page you were looking at previously that didn't have good examples?

After calculating out these brackets, what is the next step to use them to determine when the run should be stop early ? I tried to put hyperband in my configuration, but i have run 4 times, i haven't seen any run stopped early, they all run to the end of last epoch. I would very appreciate if you could  make a video or any intuitive way that show us how to use hyperband and what is the normal running behaviour should look like.

authors: cvphelps jbmorgado lukas wwdok


text:
chore: local_wandb_server.py --interactive

❯ python tools/local_wandb_server.py start manual -i
Registry [us-central1-docker.pkg.dev]:
Repository [wandb-production/images/local-testcontainer]:
Tag [master]:
--pull [always]:
local_wandb_server.py: Running command: docker run --detach --pull always -e WANDB_ENABLE_TEST_CONTAINER=true --name wandb-local-testcontainer --volume wandb-local-testcontainer-vol:/vol --publish 8080 --publish 9015 --platform linux/amd64 --rm us-central1-docker.pkg.dev/wandb-production/images/local-testcontainer:master
master: Pulling from wandb-production/images/local-testcontainer
2b55860d4c66: Already exists
8e058277d049: Already exists
...

Nice! Mind updating contrib doc?

We don't seem to have a section on system tests or about the previous usage. Plus external contributors won't be able to run the local-testcontainer anyway. Is this the right place to put that?

Nice! Mind updating contrib doc?

We don't seem to have a section on system tests or about the previous usage. Plus external contributors won't be able to run the local-testcontainer anyway. Is this the right place to put that?

fair, so maybe update the unmock doc or just add a new internal doc so we can reference devs?

Nice! Mind updating contrib doc?

We don't seem to have a section on system tests or about the previous usage. Plus external contributors won't be able to run the local-testcontainer anyway. Is this the right place to put that?

fair, so maybe update the unmock doc or just add a new internal doc so we can reference devs?

will do!

authors: kptkin timoffex

repo: wandb/wandb


text:
chore(weave): Help CTA for Product

Links to discord

Tested and updated link, I think it's good to merge.
Note:

It seems it's transparent so it can sometimes be over content and not look great. This is pretty unlikely for most users as they wouldn't be in a lot of teams like me.

authors: scottire tssweeney

repo: wandb/weave


text:
请问codis集群key分散放置到不同的 redis 节点是采用的什么算法？

请问codis集群key分散放置到不同的 redis 节点是采用的什么算法？这个算法是redis自己身实现的还是，codis实现的？能否简单的介绍下该算法，谢谢！

https://github.com/wandoulabs/codis/blob/master/doc/tutorial_zh.md#设置-server-group-服务的-slot-范围

分片的规则为SlotId= crc32(key) % 1024  ok 谢谢

目前我遇到一个问题，key值分布不均匀，codis能支持其他的算法吗？

能有多不均匀？是不是因为某个key的value实在太大了

redis 16台，key值 总共有14个，只分布在7台redis了。
key对应的value值比较大，但是key的分布不是根据key来的吗？

redis 16台，key值 总共有14个，只分布在7台redis了。

key值总共有14个的意思是整个集群只有14个key？这样本太少了很难做到一定平均分配在不同的机器上。。。另外codis是有1024个slot的，如果真的只有14个key，应该大概率是分在14个不同的slot上，只是恰好有几个slot分在一个group上了，而slot->group的映射是可以手动迁移的

另外codis并不太适合这种单个key很大的场景，一个是迁移会很痛苦，一个是读写的时候可能也会很痛苦。。。

我们用的redis队列，整个应用 key相对较少（不只14个），value比较大。我们业务场景所致，我们再想想办法，我们现在ops峰值到15w了，感觉还不够...

repo: wandoulabs/codis


text:
codis目前还不支持notify-keyspace-events这个特性？

用了这个特性会报错，不过连redis是没有问题的，报错的异常如下：
Caused by: redis.clients.jedis.exceptions.JedisConnectionException: Unknown reply: �
at redis.clients.jedis.Protocol.process(Protocol.java:141)
at redis.clients.jedis.Protocol.read(Protocol.java:200)
at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:285)
at redis.clients.jedis.Connection.getBinaryMultiBulkReply(Connection.java:221)
at redis.clients.jedis.Connection.getMultiBulkReply(Connection.java:214)
at redis.clients.jedis.Jedis.configGet(Jedis.java:2758)

不支持，将来应该也不会支持


text:
use ip in --addr/http_addr first rather than ignoring them

fix issue #221

please run gofmt before commit


text:
🛑 在线人数统计_time-counter is down

In 45ebb57, 在线人数统计_time-counter (https://time-counter.wsee.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 在线人数统计_time-counter is back up in cb6a255 after 4 minutes.

repo: wang-task/upptime


text:
Not able to Integrate with FastAPI

As stated in Integration with web framework we can integrate PyWebIO with FastAPI but the current version of PyWebIO has no support to FastAPI. i have downloaded the latest version of PyWebIO==1.2.3 and FastAPI has already been downloaded
https://imgur.com/a/mPbomhj

The doc you visited is the dev version, you need to install the dev version of pywebio to use this feature.
Use this command to install lasest  dev version:
pip3 install -U https://code.aliyun.com/wang0618/pywebio/repository/archive.zip

See also: https://github.com/wang0618/PyWebIO/discussions/42

hey @wang0618 , i will test it out! Thanks for the prompt reply!

I have downloaded the latest dev version but when i tried to run my python file, i get this ValueError. May I know what static files i have to host in order for it to work?
ValueError: Default CDN is not supported in dev version. Please host static files by yourself.

Did you download from this github repo directly? This repo doesn't contaion the built static file, you need use this command to install dev version:
pip3 install -U https://code.aliyun.com/wang0618/pywebio/repository/archive.zip

You can use the following code to let pywebio host  static files:
from fastapi import FastAPI
from pywebio.platform.fastapi import asgi_app

app = FastAPI()

@app.get("/app")
def read_main():
   return {"message": "Hello World from main app"}

# `task_func` is PyWebIO task function
app.mount("/tool", asgi_app(task_func, cdn=False)))

Doc: https://pywebio.readthedocs.io/en/dev/platform.html#pywebio.platform.fastapi.asgi_app

Think i got it working! Thankss! When will version 1.3 be released tho?

When will version 1.3 be released?

Probably within a week or two. I need to write more test case and update the document.

looking forward to it! Thanks for the assistance, i will be closing off this issue!


text:
wangEditor with angular

i use wangEditor in my angular project
but some problem happened  like this
Uncaught SyntaxError: Unexpected token . wangEditor.min.css:1
The given range isn't in document. wangEditor.js:3464

ng 我没有用过，不过你可参考 https://www.kancloud.cn/wangfupeng/wangeditor3/365539


text:
add a forwarding feature

具体是指把符合条件的请求的response转发给指定的服务器接口以作它用

#39
问题应该是这个 手机端有吗，怎么用，没找到😭

手机还没打包，你是安卓还是ios

#39 问题应该是这个 手机端有吗，怎么用，没找到😭

手机还没打包，你是安卓还是ios
抱歉，没说清楚，我是安卓的，我希望这个功能应该是可以全自动进行的。不然我只能使用autoxjs来监听app的ui行为来完成一些自动任务了hh

后面会提供脚本，目前先只有重定向，可以自己起个服务，转发到自己服务

后面会提供脚本，目前先只有重定向，可以自己起个服务，转发到自己服务

这个app互相之间转发的api文档有吗

1.0.4Beta支持脚本功能，可以自定义转发接口
https://github.com/wanghongenpin/network_proxy_flutter/releases

1.0.4Beta支持脚本功能，可以自定义转发接口
https://github.com/wanghongenpin/network_proxy_flutter/releases

测试了一下，功能没有什么问题。
就是安卓端脚本列表点按会有一些动画残留在ui上的小bug
脚本的log是在哪里查看？pc端吗

现在没法查看log，脚本异常了详情会展示原因，后面持续优化吧

脚本的log是在哪里查看？pc端吗


text:
抱歉为什么会有这样报错

node:internal/errors:465
ErrorCaptureStackTrace(err);
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'wechaty' imported from /home/git/wechatbot.git/wechat-bot/src/wechaty.js
at new NodeError (node:internal/errors:372:5)
at packageResolve (node:internal/modules/esm/resolve:954:9)
at moduleResolve (node:internal/modules/esm/resolve:1003:20)
at defaultResolve (node:internal/modules/esm/resolve:1218:11)    at ESMLoader.resolve (node:internal/modules/esm/loader:580:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:294:18)
at ModuleWrap. (node:internal/modules/esm/module_job:80:40)
at link (node:internal/modules/esm/module_job:78:36) {
code: 'ERR_MODULE_NOT_FOUND'
}

看上去好像是导包问题

repo: wangrongding/wechat-bot


text:
横向的跳跃正常，纵向跳跃时会变成最大力量，求解啊

我的安卓设备是2k分辨率，我将时间系数变成了2.5，横跳可以，纵跳总是最大力气跳出

怎么弄啊，手把手教一下啊？

你要安装python 及opencv numpy matplotlib adb等，环境设置好，就可以了

“横跳”和“纵跳”分别是啥意思？

就是当新方块在右侧就算横跳，在上方的就是纵跳

@the378  应该是左跳、右跳吧？

1这样的就是横跳了，这个设置2.5我的机器正好跳到中心，但是2这种就不行了，直接大力飞出屏外了

@the378 可以把程序打印出来的坐标贴一下吗？

或者2k屏还需调整哪些参数？
88757 KB/s (90888 bytes in 0.001s)
(1514566075, 451, 1486, 208, 1626)
adb shell input swipe 320 410 320 410 701
'cp' 不是内部或外部命令，也不是可运行的程序
或批处理文件。
5872 KB/s (93805 bytes in 0.015s)
(1514566088, 504, 1455, 242, 1606)
adb shell input swipe 320 410 320 410 755
'cp' 不是内部或外部命令，也不是可运行的程序
或批处理文件。

也不太对，第二下无论横竖都会跳飞

@the378 你先把代码里的 300 改成 500 吧。。那样应该就暂时行了。
那个代码是基于 1080 的屏幕写的。你的 2K 屏的 300 还在那个分数的数字上。

哪位大神教下呗，什么都不懂的。或者提示下要了解什么，学点什么知识能做到啊？

500还是不太行，需要慢慢调试了……

@the378 下面这些地方可能都要调整。。。
1.393 https://github.com/wangshub/wechat_jump_game/blob/master/wechat_jump_auto.py#L19
500 1600 1601 https://github.com/wangshub/wechat_jump_game/blob/master/wechat_jump_auto.py#L23
20 https://github.com/wangshub/wechat_jump_game/blob/master/wechat_jump_auto.py#L50
300 https://github.com/wangshub/wechat_jump_game/blob/master/wechat_jump_auto.py#L53
70 https://github.com/wangshub/wechat_jump_game/blob/master/wechat_jump_auto.py#L64

好的，感谢，我会慢慢尝试的

adb shell input swipe 500 1600 500 1600 610
时间参数大于610直接变成按住不动了，小于610可以，单独运行adb命令也这样

试试 adb shell input swipe 500 1600 500 1610 610 呢？
毕竟 swipe，起点和终点可能有点区别比较合适。

@binderclip
谢谢回复，有设置起点和终点，命令为adb shell input swipe 500 1600 600 1500 700
图中的红线为wipe的路径

@sztanyi 请问你的是啥手机？

安卓适配的机型和屏幕太多了...不能 hard coded 啊quq

@binderclip 坚果pro，感觉有毒。adb swipe命令时间超过600左右没有释放动作了。。

我的2k屏实验成功了。。。待我回家后上传相应调整的参数

@binderclip 坚果 pro2 怎么配置呢？

authors: Allianzcortex binderclip liuchonggao mjzcyhp sztanyi the378


text:
华为荣耀8 记得关悬浮球，比如360助手。

运行auto 就可以。完美运行。

哈哈  居然还有这玩意 @shinkeika

authors: shinkeika wangshub


text:
为什么没人用dqn的方式来做呢，谁有训练好的模型啊

为什么没人用dqn的方式来做呢，谁有训练好的模型啊

你可以做啊

这个动作是连续的 。dqn动作是离散的

可以回归啊

authors: Lujango learn2Pro saduoduo


text:
Test common issue 1

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az policy assignment list
Errors:
APIVersion 2019-09-01 is not available
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 608, in execute
    raise ex
cli/core/commands/__init__.py, ln 666, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 659, in _run_job
    six.reraise(*sys.exc_info())
lib/python3/dist-packages/six.py, ln 703, in reraise
    raise value
...
azure/cli/core/__init__.py, ln 493, in default_command_handler
    return op(**command_args)
cli/command_modules/resource/custom.py, ln 1393, in list_policy_assignment
    result = policy_client.policy_assignments.list()
mgmt/resource/policy/_policy_client.py, ln 141, in policy_assignments
    raise NotImplementedError("APIVersion {} is not available".format(api_version))
NotImplementedError: APIVersion 2019-09-01 is not available

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az policy assignment list

Expected Behavior
Environment Summary
Linux-5.11.0-41-generic-x86_64-with-glibc2.29
Python 3.8.10
Shell: bash

azure-cli 2.0.81

Extensions:
interactive 0.4.5
azure-devops 0.17.0

Additional Context

Thanks for the report @wangzelin008! We will look into it ASAP!


text:
🛑 Vichnu-Production is down

In 1865bd9, Vichnu-Production (https://vichnu-production.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Vichnu-Production is back up in 3827fc2 after 13 minutes.

repo: warielon/upptime


text:
Feature/backend GitHub requests

Description
Removes octokit dependency fully.
Uses our public backend.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Chore: cleanup/renaming, etc
[ ] RFC

Notes

Acceptance

[ ] I have read the Contributing guidelines
[ ] I have read the Code of Conduct

Not sure if this is the main goal of this PR or not, but doesn't fix the error I get.

No, unrelated.
Your dev environment is broken.

Not sure if this is the main goal of this PR or not, but doesn't fix the error I get.

No, unrelated. Your dev environment is broken.

As you can see in the code, @baristaGeek, this PR removes the dependency on octokit and uses our backend for requests to the GitHub API.

Any updates @baristaGeek ?

repo: watermelontools/watermelon-extension


text:
[New Feature Thread] Feedback page to get user input

This is a documentation thread
Have yet to deeply think about the best route for users to give feedback / their input on the app.
A few solutions I have thought of include:

Have a link to Github. (Have an area where users can fill out a form that can be reviewed and added as a ticket)
Use an outside service (google forms, Qualtrics) where users fill out a form and we get an email.
Have our own form that goes to the waterthetrees email.
Have a button where the map is. So users can immediately give us a bug report etc.

Can i solve this issue?
Please assign this issue to me. so i will contribute in this issue.

#631 is the current ticket with this issue


text:
Allow passing per-message client options/params

Ability to set OpenAI API key for server on the first request to it

@z0lo13 could you explain your use-case for this?

It will open an ability to have multi users for apps/front without node.js support. It would be great if api key is saved on session.
For now I accomplished the same thing with the client library which is ran on my express server. So I am not really sure if that will be useful for that.
Another use scenario is the ability to switch the open ai api key without editing or restarting the server.
Again, both of the above are perfectly achievable with a custom server like express and client library, however if you're to supporting the server portion, I suppose It could be useful.

I want to allow setting model parameters on a per-message basis in the future. A configurable API key could be part of that as well.

@waylaidwanderer that would be great if you consider this in next updates

Now available in https://github.com/waylaidwanderer/node-chatgpt-api/releases/tag/v1.28.0

FYI @z0lo13, I won't support sessions for the API server, so you'll have to store the options some other way, such as in the browser's local storage. Alternatively, you can run your own server that uses the new feature.

repo: waylaidwanderer/node-chatgpt-api


text:
Problems with Parsing the Motion tf record data

Hello, I was trying to load the motion data with the tf record, following the tutorial, https://github.com/waymo-research/waymo-open-dataset/blob/master/tutorial/tutorial_motion.ipynb. But using a single tf example proto, I get the following error :
2023-04-08 11:54:14.536235: E tensorflow/stream_executor/cuda/cuda_driver.cc:271] failed call to cuInit: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE: forward compatibility was attempted on non supported HW 2023-04-08 11:54:14.536262: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:169] retrieving CUDA diagnostic information for host: nsh1609-1 2023-04-08 11:54:14.536266: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:176] hostname: nsh1609-1 2023-04-08 11:54:14.536383: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:200] libcuda reported version is: 515.105.1 2023-04-08 11:54:14.536400: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:204] kernel reported version is: 515.86.1 2023-04-08 11:54:14.536404: E tensorflow/stream_executor/cuda/cuda_diagnostics.cc:313] kernel version 515.86.1 does not match DSO version 515.105.1 -- cannot find working devices in this configuration 2023-04-08 11:54:14.536603: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2023-04-08 11:54:14.550074: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:185] None of the MLIR Optimization Passes are enabled (registered 2) 2023-04-08 11:54:14.560810: W tensorflow/core/framework/op_kernel.cc:1692] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Key: roadgraph_samples/xyz.  Can't parse serialized Example. Traceback (most recent call last):   File "data_viz_tut.py", line 157, in <module>     parsed = tf.io.parse_single_example(data, features_description)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/util/dispatch.py", line 206, in wrapper     return target(*args, **kwargs)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/ops/parsing_ops.py", line 452, in parse_single_example_v2     return parse_example_v2(serialized, features, example_names, name)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/util/dispatch.py", line 206, in wrapper     return target(*args, **kwargs)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/ops/parsing_ops.py", line 314, in parse_example_v2     outputs = _parse_example_raw(serialized, example_names, params, name=name)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/ops/parsing_ops.py", line 350, in _parse_example_raw     outputs = gen_parsing_ops.parse_example_v2(   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/ops/gen_parsing_ops.py", line 718, in parse_example_v2     return parse_example_v2_eager_fallback(   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/ops/gen_parsing_ops.py", line 812, in parse_example_v2_eager_fallback     _result = _execute.execute(b"ParseExampleV2", num_sparse + len(sparse_types)   File "/home/nsh1609/anaconda3/lib/python3.8/site-packages/tensorflow/python/eager/execute.py", line 59, in quick_execute     tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name, tensorflow.python.framework.errors_impl.InvalidArgumentError: Key: roadgraph_samples/xyz.  Can't parse serialized Example. [Op:ParseExampleV2]
From looking around, I found that this happens if the Fixed Length sizes is different or not mentioned in the features descriptor. can someone help me navigate this issue ?

Facing the same issue with all the "roadgraph_samples/*" features. Can someone help us resolve this issue?

Hey guys. I got stuck on this issue too. I just found a solution https://github.com/waymo-research/waymo-open-dataset/issues/343
So, ignore the following lines that are in the tutorial:
dataset = tf.data.TFRecordDataset(FILENAME, compression_type='')
data = next(dataset.as_numpy_iterator())
parsed = tf.io.parse_single_example(data, features_description)
Use this code instead:
import numpy as np
from waymo_open_dataset.protos import scenario_pb2
FILENAME = '../data/scenario/uncompressed_scenario_training_20s_training_20s.tfrecord-00000-of-01000'
dataset = tf.data.TFRecordDataset(FILENAME)
scenario_data = []
for data in dataset:
proto_string = data.numpy()
proto = scenario_pb2.Scenario()
proto.ParseFromString(proto_string)
scenario_data.append(proto)
This code works for the data inside the ./uncompressed folder, but it does not work for the ones in the ./tf_example folder. I do not know why.

Thanks for flagging this. In the latest version of the dataset, the number of roadgraph samples has increased to 30000.  A temporary workaround is to change the shapes from 20000 to 30000.  We will update the tutorial with the new input shapes shortly.

Thanks for flagging this. In the latest version of the dataset, the number of roadgraph samples has increased to 30000. A temporary workaround is to change the shapes from 20000 to 30000. We will update the tutorial with the new input shapes shortly.

@scott-ettinger Thanks for your clarification. This change resolved the issue for me.

Hello, I'm facing the same issue although samples has been updated to 30000.

authors: Raghuram-Veeramallu Sou0602 Zachs-Playground scott-ettinger xDido

repo: waymo-research/waymo-open-dataset


text:
chore(master): release 1.1.7

:robot: I have created a release beep boop
1.1.7 (2023-06-05)
Miscellaneous

deps: update dependency wayofdev/cs-fixer-config to v1.2.8 (6885861)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-cycle-event-sourcing/releases/tag/v1.1.7 :sunflower:

repo: wayofdev/laravel-cycle-event-sourcing


text:
chore(master): release 2.1.20

:robot: I have created a release beep boop
2.1.20 (2024-02-28)
Bug Fixes

deps: update dependency wayofdev/laravel-webhook-client to v1.2.18 (bce03ef)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v2.1.20 :sunflower:

repo: wayofdev/laravel-stripe-webhooks


text:
Change default theme

Description
This issue changes the default theme from Next to v7
Issues Resolved
#173
Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.39%. Comparing base (f066302) to head (b8b3df2).
Report is 84 commits behind head on 4.9.0.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##            4.9.0     #174       +/-   ##
===========================================
- Coverage   66.96%   55.39%   -11.58%
===========================================
  Files        3300     1194     -2106
  Lines       63585    24048    -39537
  Branches    10141     4013     -6128
===========================================
- Hits        42582    13321    -29261
+ Misses      18538    10100     -8438
+ Partials     2465      627     -1838

Flag
Coverage Δ

Linux_1
?

Linux_2
55.39% <ø> (+0.22%)
:arrow_up:

Linux_3
?

Windows_1
?

Windows_2
?

Windows_3
?

Windows_4
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: Tostti codecov-commenter

repo: wazuh/wazuh-dashboard