Several tests are failing

Describe the bug
When building with make check several tests fail
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build; cmake -DENABLE_CHECK=On ..; make check
See the errors

Obs: I've added two print on check_spec.y:
            if 'grammar' in spec:
                cmd.extend(['--grammar-str', spec['grammar']])
            elif 'grammar_file' in spec:
                if spec['grammar_file'].startswith('/'):
                    cmd.extend(['--grammar-file', spec['grammar_file']])
                else:
                    cmd.extend(['--grammar-file', os.path.dirname(os.path.abspath(specs_file)) + '/' + spec['grammar_file']])
            else:
                raise ValueError('Missing grammar/grammar_file')
            print(cmd) #<<<< here
            print(test['I'].encode('utf-8')) #<<<< here
            proc = subprocess.run(
                cmd,
                capture_output=True,
                input=test['I'].encode('utf-8'),
            )

make check
[  3%] Built target unity
[  6%] Built target peppa
[ 11%] Built target test_flags
[ 15%] Built target cli
[ 20%] Built target test_example_dot
[ 25%] Built target test_example_calc
[ 30%] Built target test_example_json
[ 35%] Built target test_peg
[ 40%] Built target test_positive
[ 45%] Built target test_literal
[ 50%] Built target test_range
[ 55%] Built target test_misc
[ 60%] Built target test_cut
[ 65%] Built target test_sequence
[ 70%] Built target test_choice
[ 75%] Built target test_reference
[ 80%] Built target test_negative
[ 85%] Built target test_example_mustache
[ 90%] Built target test_repeat
[ 95%] Built target test_left_recursion
[100%] Built target test_back_reference
Test project PeppaPEG/build/tests
      Start  1: test_literal
 1/48 Test  #1: test_literal .....................   Passed    0.00 sec
      Start  2: test_range
 2/48 Test  #2: test_range .......................   Passed    0.00 sec
      Start  3: test_sequence
 3/48 Test  #3: test_sequence ....................   Passed    0.00 sec
      Start  4: test_choice
 4/48 Test  #4: test_choice ......................   Passed    0.00 sec
      Start  5: test_reference
 5/48 Test  #5: test_reference ...................   Passed    0.00 sec
      Start  6: test_positive
 6/48 Test  #6: test_positive ....................   Passed    0.00 sec
      Start  7: test_negative
 7/48 Test  #7: test_negative ....................   Passed    0.00 sec
      Start  8: test_repeat
 8/48 Test  #8: test_repeat ......................   Passed    0.00 sec
      Start  9: test_flags
 9/48 Test  #9: test_flags .......................   Passed    0.00 sec
      Start 10: test_cut
10/48 Test #10: test_cut .........................   Passed    0.00 sec
      Start 11: test_back_reference
11/48 Test #11: test_back_reference ..............   Passed    0.00 sec
      Start 12: test_left_recursion
12/48 Test #12: test_left_recursion ..............   Passed    0.00 sec
      Start 13: test_misc
13/48 Test #13: test_misc ........................   Passed    0.00 sec
      Start 14: test_peg
14/48 Test #14: test_peg .........................   Passed    0.01 sec
      Start 15: test_example_mustache
15/48 Test #15: test_example_mustache ............   Passed    0.00 sec
      Start 16: test_example_json
16/48 Test #16: test_example_json ................   Passed    0.02 sec
      Start 17: test_example_calc
17/48 Test #17: test_example_calc ................   Passed    0.01 sec
      Start 18: test_example_dot
18/48 Test #18: test_example_dot .................   Passed    0.08 sec
      Start 19: test_literal_spec.json
19/48 Test #19: test_literal_spec.json ...........***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = "1";']
b'1'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 20: test_range_spec.json
20/48 Test #20: test_range_spec.json .............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'Num', '--grammar-str', 'Num = [1-9];']
b'1'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 21: test_insensitive_spec.json
21/48 Test #21: test_insensitive_spec.json .......***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = i"1";']
b'1'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 22: test_sequence_spec.json
22/48 Test #22: test_sequence_spec.json ..........***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = "a" "b" "c";']
b'abc'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 23: test_choice_spec.json
23/48 Test #23: test_choice_spec.json ............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = "a" / "b" / "c";']
b'a'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 24: test_left_recursion_spec.json
24/48 Test #24: test_left_recursion_spec.json ....***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'A', '--grammar-str', 'A = "a" | B "a"; B = "b";']
b'a'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 25: test_lookahead_spec.json
25/48 Test #25: test_lookahead_spec.json .........***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = !"a" [a-f];']
b'b'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 26: test_cut_spec.json
26/48 Test #26: test_cut_spec.json ...............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = R2*;R2 = "1" ~ "2";']
b'121'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 27: test_repeat_spec.json
27/48 Test #27: test_repeat_spec.json ............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = ([0-9] / [a-f] / [A-F])+;']
b'1A9F'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 28: test_reference_spec.json
28/48 Test #28: test_reference_spec.json .........***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = R2; R2 = "1";']
b'1'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 29: test_back_reference_spec.yaml
29/48 Test #29: test_back_reference_spec.yaml ....***Failed    0.12 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = R23 \\0;\nR23 = "2" / "3";\n']
b'22'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 30: test_dot_spec.json
30/48 Test #30: test_dot_spec.json ...............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = .;']
b'\xe5\xa5\xbd'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 31: test_comment_spec.json
31/48 Test #31: test_comment_spec.json ...........***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', 'R1 = "1"# R1 = "3";\n;']
b'1'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 32: test_flags_spec.json
32/48 Test #32: test_flags_spec.json .............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'R1', '--grammar-str', '@squashed\nR1 = R2 R2;R2 = "X";']
b'XX'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 33: test_peppa_spec.json
33/48 Test #33: test_peppa_spec.json .............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'number', '--grammar-file', 'PeppaPEG/tests/./peppa.peg']
b'0'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 34: test_golang_v1_17_spec.json
34/48 Test #34: test_golang_v1_17_spec.json ......***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'Literal', '--grammar-file', 'PeppaPEG/tests/../configs/golang-v1.17.peg']
b'42'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 35: toml/test_array.yaml
35/48 Test #35: toml/test_array.yaml .............***Failed    0.22 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'ints = [1, 2, 3, ]\nfloats = [1.1, 2.1, 3.1]\nstrings = ["a", "b", "c"]\ndates = [\n  1987-07-05T17:45:00Z,\n  1979-05-27T07:32:00Z,\n  2006-06-01T11:00:00Z,\n]\ncomments = [\n         1,\n         2, #this is ok\n]\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 36: toml/test_bool.yaml
36/48 Test #36: toml/test_bool.yaml ..............***Failed    0.11 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b't = true\nf = false\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 37: toml/test_comment.yaml
37/48 Test #37: toml/test_comment.yaml ...........***Failed    0.16 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'# This is a full-line comment\nkey = "value" # This is a comment at the end of a line\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 38: toml/test_control.yaml
38/48 Test #38: toml/test_control.yaml ...........***Failed    0.12 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'comment-lf = "ctrl-P" # \x10\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 39: toml/test_datetime.yaml
39/48 Test #39: toml/test_datetime.yaml ..........***Failed    0.21 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'space = 1987-07-05 17:45:00Z\nlower = 1987-07-05t17:45:00z\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 40: toml/test_float.yaml
40/48 Test #40: toml/test_float.yaml .............***Failed    0.17 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'double-point-1 = 0..1\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 41: toml/test_inline_table.yaml
41/48 Test #41: toml/test_inline_table.yaml ......***Failed    0.33 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'people = [{first_name = "Bruce", last_name = "Springsteen"},\n          {first_name = "Eric", last_name = "Clapton"},\n          {first_name = "Bob", last_name = "Seger"}]\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 42: toml/test_integer.yaml
42/48 Test #42: toml/test_integer.yaml ...........***Failed    0.17 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'capital-bin = 0B0\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 43: toml/test_key.yaml
43/48 Test #43: toml/test_key.yaml ...............***Failed    0.27 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'[[agencies]] owner = "S Cjelli"\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 44: toml/test_string.yaml
44/48 Test #44: toml/test_string.yaml ............***Failed    0.24 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'naughty = "\\xAg"\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 45: toml/test_table.yaml
45/48 Test #45: toml/test_table.yaml .............***Failed    0.24 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'toml', '--grammar-file', 'PeppaPEG/tests/toml/../../configs/toml-v1.0.peg']
b'[[]]\nname = "Born to Run"\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 46: abnf/test_rfc5234.yaml
46/48 Test #46: abnf/test_rfc5234.yaml ...........***Failed    0.24 sec
['PeppaPEG/build/cli', 'parse', '--grammar-entry', 'RuleList', '--grammar-file', 'PeppaPEG/tests/abnf/../../configs/abnf.peg']
b'rulelist       =  1*( rule / (*c-wsp c-nl) )\n\nrule           =  rulename defined-as elements c-nl\n                ; continues if next line starts\n                ;  with white space\n\nrulename       =  ALPHA *(ALPHA / DIGIT / "-")\n\ndefined-as     =  *c-wsp ("=" / "=/") *c-wsp\n                                ; basic rules definition and\n                                ;  incremental alternatives\n\nelements       =  alternation *c-wsp\n\nc-wsp          =  WSP / (c-nl WSP)\n\nc-nl           =  comment / CRLF\n                    ; comment or newline\n\ncomment        =  ";" *(WSP / VCHAR) CRLF\n\nalternation    =  concatenation\n                *(*c-wsp "/" *c-wsp concatenation)\n\nconcatenation  =  repetition *(1*c-wsp repetition)\n\nrepetition     =  [repeat] element\n\nrepeat         =  1*DIGIT / (*DIGIT "*" *DIGIT)\n\nelement        =  rulename / group / option /\n                char-val / num-val / prose-val\n\ngroup          =  "(" *c-wsp alternation *c-wsp ")"\n\noption         =  "[" *c-wsp alternation *c-wsp "]"\n\nchar-val       =  DQUOTE *(%x20-21 / %x23-7E) DQUOTE\n                    ; quoted string of SP and VCHAR\n                    ;  without DQUOTE\n\nnum-val        =  "%" (bin-val / dec-val / hex-val)\n\nbin-val        =  "b" 1*BIT\n                [ 1*("." 1*BIT) / ("-" 1*BIT) ]\n                    ; series of concatenated bit values\n                    ;  or single ONEOF range\n\ndec-val        =  "d" 1*DIGIT\n                [ 1*("." 1*DIGIT) / ("-" 1*DIGIT) ]\n\nhex-val        =  "x" 1*HEXDIG\n                [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]\n\nprose-val      =  "<" *(%x20-3D / %x3F-7E) ">"\n                    ; bracketed string of SP and VCHAR\n                    ;  without angles\n                    ; prose description, to be used as\n                    ;  last resort\n'
Traceback (most recent call last):
  File "PeppaPEG/scripts/check_spec.py", line 87, in <module>
    test_spec()
  File "PeppaPEG/scripts/check_spec.py", line 48, in test_spec
    input=test['I'].encode('utf-8'),
  File "/usr/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'

      Start 47: lua-5.4.3/*.lua
47/48 Test #47: lua-5.4.3/*.lua ..................   Passed    2.31 sec
      Start 48: abnf/*.abnf
48/48 Test #48: abnf/*.abnf ......................   Passed    0.05 sec

42% tests passed, 28 tests failed out of 48

Total Test time (real) =   6.75 sec

The following tests FAILED:
	 19 - test_literal_spec.json (Failed)
	 20 - test_range_spec.json (Failed)
	 21 - test_insensitive_spec.json (Failed)
	 22 - test_sequence_spec.json (Failed)
	 23 - test_choice_spec.json (Failed)
	 24 - test_left_recursion_spec.json (Failed)
	 25 - test_lookahead_spec.json (Failed)
	 26 - test_cut_spec.json (Failed)
	 27 - test_repeat_spec.json (Failed)
	 28 - test_reference_spec.json (Failed)
	 29 - test_back_reference_spec.yaml (Failed)
	 30 - test_dot_spec.json (Failed)
	 31 - test_comment_spec.json (Failed)
	 32 - test_flags_spec.json (Failed)
	 33 - test_peppa_spec.json (Failed)
	 34 - test_golang_v1_17_spec.json (Failed)
	 35 - toml/test_array.yaml (Failed)
	 36 - toml/test_bool.yaml (Failed)
	 37 - toml/test_comment.yaml (Failed)
	 38 - toml/test_control.yaml (Failed)
	 39 - toml/test_datetime.yaml (Failed)
	 40 - toml/test_float.yaml (Failed)
	 41 - toml/test_inline_table.yaml (Failed)
	 42 - toml/test_integer.yaml (Failed)
	 43 - toml/test_key.yaml (Failed)
	 44 - toml/test_string.yaml (Failed)
	 45 - toml/test_table.yaml (Failed)
	 46 - abnf/test_rfc5234.yaml (Failed)
Errors while running CTest
tests/CMakeFiles/check.dir/build.make:94: recipe for target 'tests/CMakeFiles/check' failed
make[3]: *** [tests/CMakeFiles/check] Error 8
CMakeFiles/Makefile2:309: recipe for target 'tests/CMakeFiles/check.dir/all' failed
make[2]: *** [tests/CMakeFiles/check.dir/all] Error 2
CMakeFiles/Makefile2:316: recipe for target 'tests/CMakeFiles/check.dir/rule' failed
make[1]: *** [tests/CMakeFiles/check.dir/rule] Error 2
Makefile:248: recipe for target 'check' failed
make: *** [check] Error 2

capture_output is only available since Python 3.7+. https://docs.python.org/3/library/subprocess.html
Which Python version are you running?

Thank you !
All tests pass now on my machine.


Added XElement support to the serializer

Serializing and deserializing XElement did not work properly before. This PR adds a XElementSurrogate which allows all serializers in duality to properly handle XElement.
Additionally XmlSerializer has a small extra modification to make the serialized xml more readable, without this change the serialized xml would end up as a base64 string.
TODO

[ ]  unittests

Test comment to check webhook


Fixed build module url

Fixes #6225
With the introduction of the Resource class we accidentally required a trailing slash to CESIUM_BASE_URL.

@tfili, thanks for the pull request! Maintainers, we have a signed CLA from @tfili, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Looks good, update CHANGES and I'll merge.

@mramato Updated CHANGES.


Update copy_from portion of DumpFile to work with topology

This should copy topology information if it is contained in the snapshot.
https://github.com/mphowardlab/lammpsio/blob/91aa9797afeb5a0e24feac66c27b9eabc81c22f0/src/lammpsio/dump.py#L383C21-L409C70

This seems like a relatively simple feature to add that someone might expect to work with topology added in. Could you take a pass at implementing it? I think you basically only need to copy the reference to the relevant topology data if it is present in copy_from, as a dump file will never have topology info.


[BEAM-14347] Allow users to optimize DoFn execution with a single generic registration function

This is the first step towards allowing users to fully replace the code generator with a DoFn registration function (design doc https://docs.google.com/document/d/1MLZLUhb-Sn7AJ666yn3TnYgMKE6wiXIBs7cjB_20hMA/edit?usp=sharing).  At the moment, these register struct wrappers, types, and funcs for the passed in DoFn.
Update specialize/main.go to provide some functions used by registration.tmpl

Because the tmpl file is hard to review in isolation, I would do so with the generated file side by side so that you can see how the template translates into the final code. Reviewing the full generated file is impossible because of how many functions are generated.
Next steps
After this is in, I will follow up with prs to:

Handle emitter/iter registration
Handle combiner registration
Perf testing
Updates to the docs/our examples

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Run SQL_Java17 PreCommit

R: @lostluck

I don't yet have time to look at this just yet, but how do you feel about merging this after the 2.39 cut, so the first release that requires Go 1.18 is 2.40?
Whenever we merge it though, this PR must also include a note in CHANGES.md for whichever version it affects, since the Go SDK would then require a minimum Go version of 1.18. The minimum doesn't just apply to the generic using packages, but to the entire SDK.

but how do you feel about merging this after the 2.39 cut, so the first release that requires Go 1.18 is 2.40?

That's fine by me - is your goal just to get some additional validation with all of us building stuff on Go 1.18 for a while?

Whenever we merge it though, this PR must also include a note in CHANGES.md for whichever version it affects

Yeah, I was planning on adding something in CHANGES.md in a follow up pr (along with doc changes) once all the generics work is in - I can also add a placeholder in this PR once 2.39 is cut (and the 2.40 release notes are ready) though

but how do you feel about merging this after the 2.39 cut, so the first release that requires Go 1.18 is 2.40?

Another option (which I might like even more) is to review this PR as is, and then undo all the changes except for the template file and specialize/main.go. That would allow me to keep putting up my remaining generics changes for review, so that when we reach 2.40 all that needs to happen is running go generate, go.mod and CI changes, and adding back registration_tests.go.
That would save me some hard context shifts, but it may be more trouble than its worth - regardless, I'd prefer we prioritize finishing the watermark reviews, and by the time those are all through 2.39 may have been cut (or be close to being cut)

but how do you feel about merging this after the 2.39 cut, so the first release that requires Go 1.18 is 2.40?

Another option (which I might like even more) is to review this PR as is, and then undo all the changes except for the template file and specialize/main.go. That would allow me to keep putting up my remaining generics changes for review, so that when we reach 2.40 all that needs to happen is running go generate, go.mod and CI changes, and adding back registration_tests.go.
That would save me some hard context shifts, but it may be more trouble than its worth - regardless, I'd prefer we prioritize finishing the watermark reviews, and by the time those are all through 2.39 may have been cut (or be close to being cut)

I like this idea. It's a happy medium, and will make later improvements easier to review. My goal is to prioritize the Watermark and checkpoint reviews once my oncall is handed off.

LOL: "-45%" test coverage.
+293,588 lines.
Hmmm. When I look at this properly, I'll see if we can't figure out other helper functions to bring that down. I think that's larger than the rest of the SDK...

LOL: "-45%" test coverage.
+293,588 lines. Hmmm. When I look at this properly, I'll see if we can't figure out other helper functions to bring that down. I think that's larger than the rest of the SDK...

I think the right approach is to exclude it from coverage. I tried to do that in this PR, but I'm guessing it doesn't factor in the current changeset when calculating it.
With that said, shrinking this is a good goal by itself

Hmmm. When I look at this properly, I'll see if we can't figure out other helper functions to bring that down. I think that's larger than the rest of the SDK...

Actually, rethinking this I think I have an idea of how I can shrink this that I'd originally missed - I'll take another pass at doing that in the morning. In general, its a little messy because I still need to hold on to types, but it should help significantly. Feel free to hold off on reviewing until then

Its down to 60,000 lines which is still a lot, but its better at least

@lostluck this should be ready for another look at this point!

Run Python_PVR_Flink PreCommit

Run Portable_Python PreCommit

Run Python PreCommit

Run Java_PVR_Flink_Batch PreCommit

This is great! One last thing that needs to be in here:
CHANGES.md regarding moving the minimum Go version to 1.18

Yep, thanks for the reminder - I'd been waiting until the 2.39 cut for this. Updated!


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 485

Questions ?
Please refer to the Backport tool documentation


pull request for e2e test at 01/14/2017 22:56:16

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


merge from arlac77/template-github-action,arlac77/template-kronos-module

package.json

chore(package): add ^17.0.8 remove ^17.0.7 (devDependencies.semantic-release)

Codecov Report

Merging #1339 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1339   +/-   ##
=======================================
  Coverage   78.94%   78.94%
=======================================
  Files           1        1
  Lines          38       38
  Branches        1        1
=======================================
  Hits           30       30
  Misses          8        8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 818abee...358d29a. Read the comment docs.


Head Slime Antag Code & Details

About the PR

Adds a Head Slime Antag, with rules for rounds and an Admin power to turn entities into the new antag (The secret weights have not been adjusted for now). Basic Antag details are included in the guidebook, but here is an addtional overview:

Head Slime Queens appear as normal crew members, however they can see a faction icon to recognise one anouther.
Head Slime Queens have two moves, Infect and Inject. Infect is a DoAfter event that removes a targets hat (If it has one) and places a Head Slime (real) hat on their head, turning them into a normal Head Slime. Inject is a short DoAfter event that knocks the target out.
Head Slime's cannot be removed.
Head Slimes can only be placed on Humanoids.
Normal Head Slimes gain a debuff to their movement, but do not need to eat or drink. They do not gain any actions.
Table Salt is Lethal to any Head Slime type if ingested.
If a normal Head Slime is gibbed, they will drop their Head Slime hat. If someone else puts it on they will turn into a Head Slime antag. Queens drop nothing.

Antag and GameType Reasoning
The Head Slime is aimed at being a varient on the zombie mode, but with the twist that infected targets are still able to act 'as normal'. The flow of the gamemode is meant to go along the lines of, Queens hatch a plan, start Infecting as secretly as possible but when discovered the station and the head slimes escalate to an all out conflict. The aim of the crew is to find and get rid of the Queens so no more Head Slimes can spawn in. Biomassing and burning the bodies become a good way to get rid of the Head Slimes once taken down.
The Salt weakness exists to give the crew a way to 'test' each other if they are a head slime, in case a Queen is still trying to lie low, or if the crew is just suspicious of someone. In addtion since Head Slimes cannot wear hats they cannot space walk, so in a twist it's the crew who can actually gain an advantage if they decide to space an area.
Media

Currently the antag re-uses the sprite's of the Head Slime Hat, and a Syringe image for the Inject Action. The headslime_start.ogg is currently just a copy of zombie_start.ogg.

I have added screenshots/videos to this PR showcasing its changes ingame.

Changelog

:cl:

add: A new Antag has been added, the Head Slime.

Isn't this just slightly different revs?

Isn't this just slightly different revs?

They couldn't be more different. Revenants don't have any way to assimilate, for one. Plus they can go through walls.
Anyways, I think "head slime" is kind of a weird name, it sounds like they're the bosses of the slime department. Maybe Headslime?

Isn't this just slightly different revs?

They couldn't be more different. Revenants don't have any way to assimilate, for one. Plus they can go through walls.
Anyways, I think "head slime" is kind of a weird name, it sounds like they're the bosses of the slime department. Maybe Headslime?

#18477

Isn't this just slightly different revs?

They couldn't be more different. Revenants don't have any way to assimilate, for one. Plus they can go through walls.
Anyways, I think "head slime" is kind of a weird name, it sounds like they're the bosses of the slime department. Maybe Headslime?

I think they mean revolutionaries.

Isn't this just slightly different revs?

They couldn't be more different. Revenants don't have any way to assimilate, for one. Plus they can go through walls.
Anyways, I think "head slime" is kind of a weird name, it sounds like they're the bosses of the slime department. Maybe Headslime?

I originally intended to name them Brain Slugs, but since I wanted to use the Head Slime hat sprite I chose to use that naming convention instead. As for being like Rev's, kinda of, but that's partly cause this is already like Zombies (Which is also about spreading an antag throughout the station).
The main diff's are the environmental restrictions (Can't space walk), the speed of the infection makes the antag a kidnapping challenge (It's not instant, and the fact that people can scream whilst asleep after the injection is kind of used in this instance to make it harder to do it anywhere near a public space), the take over is very obvious so lines of engagement should be fairly clear (If it's wearing something green on it's head, blam blam), and a funny salt mechanic where a cook could technically banana slip one and feed them some before they got up (Salt is a near instant kill).
It's not designed to be a complex antag, I even smoothed out a few features to make the infection a little easier, it's mainly just a slightly varation on a couple of concepts that already exist within the game.

Re-open if you get a chance to work on this.


Base58 operations

For #48
This adds two operations

To Base58
From Base58

And includes 2 commonly used Base58 alphabets:

Bitcoin
Ripple

Images

Awesome work once again. Thanks for your contributions.


Hugo Academic: Mobile View - header issue (little space)

Hello guys,
i love Hugo and all the themes. It only took me some hours to build a great homepage. But unfortunately i noticed that the mobile view is not correct. Somehow there is little space between the header line and the headline in the banner (Ingenieurbüro für Kunstofftechnik and Ingenieurbüro Hanswurst)
Do you see the issue? Can i add some space here? (not sure how)
https://discourse.gohugo.io/uploads/gohugo/original/2X/e/ec5a4e8b9e475c3482007929c49dd6b7d56f9f58.png
Thanks a lot!

You could try:

Use an image editor to save the text as an image, upload your image to static/img/ folder, and reference it in the logo option in config.toml (see documentation website). Using a logo image may take up less space in the header.
Reduce the font size in the navbar - create a custom CSS (see documentation) and then paste in something like .navbar-brand {font-size: 0.6em !important;}
Use a shorter, mobile friendly title


Fix the train.py RuntimeError:a view of a leaf Variable that requires grad is being used in an in-place operation when running... issue

If you meet the same issue as I am, you can try as follow to fix it:

Works for me, good luck :-)

#17, I believe this is a better fix, and this was the final fix that was merged on YOLOv5

Thx for your advice, and thx for your great job, I'll check out for myself. Sorry for posing a weird issue here, since I do not know much manner here in Github (｡･ω･)~


Slight cleanups to buf.yaml

Just a couple small cleanups:

Deletes FILE_LOWER_SNAKE_CASE from lint.use, as this is already in the DEFAULT category, so this is duplicative.
Deletes a few options that were set to the default value.
Updates lint.ignore to lint.ignore_only via the output of buf lint --error-format=config-ignore-yaml. This will mean that future lint violations within proto/tm/replay.proto will still be caught for other violation types.

Feel free to commandeer this and/or just copy paste into your internal core repo, no need to merge!

I don't believe the build failure is related to this change: https://github.com/vegaprotocol/api-clients/pull/133/checks?check_run_id=1943645581

@bufdev Thanks for the PR.
You're correct that the CI failure is not related to your change. Occasionally, a Github Action will get run without (some/all) of the environment variables correctly populated.


Allow users to upload multiple attachments in one go

Users can now upload multiple attachments in one go, instead of having to pick them one by one.
Closes AB#1171
User changes

A user can now upload multiple attachments in one go.

Superuser changes

None.

Admin changes

None.

System admin changes

[ ] anet.yml or anet-dictionary.yml needs change
[ ] db needs migration
[ ] documentation has changed
[ ] graphql schema has changed

Checklist

[x] Described the user behavior in PR body
[x] Referenced/updated all related issues
[x] commits follow a repo#issue: Title title format and these 7 rules
[x] commits have a clean history, otherwise PR may be squash-merged
[ ] Added and/or updated unit tests
[ ] Added and/or updated e2e tests
[ ] Added and/or updated data migrations
[ ] Updated documentation
[ ] Resolved all build errors and warnings
[ ] Opened debt issues for anything not resolved here

To be discussed on Monday, I have noticed a strange behaviour on the drag & drop functionality. After you have done it once, future drag & drops do not work regardless of the file selected. Probably an issue with the upload component we cant do anything about.

To be discussed on Monday, I have noticed a strange behaviour on the drag & drop functionality. After you have done it once, future drag & drops do not work regardless of the file selected. Probably an issue with the upload component we cant do anything about.

It is a Chrome "feature" that prevents you from doing the exact same thing twice (add another file to your [multi-]selection, or remove a file from it, and drag&drop will accept your selection). Note that Firefox just allows it.


Slimming tests

Description
Having a lot of tests can be good, but having a lot will create maintenance harder, more timely, and overall more costly. This PR addresses that issue by removing tests that are unneeded, already being captured somewhere else, and overall duplicates. I think these tests can be removed without much disadvantage.
Changed Test Files

Computation
Computation Process
Data
Experiment
Material
Process
Reference

Tests
Known Issues
Notes
Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.

I don't know we don't need to close it yet.
Maybe we think about it a bit more?

I don't know we don't need to close it yet. Maybe we think about it a bit more?

okie dokes, I am okay with that!

@InnocentBug I'm thinking of removing this PR  because I think we both like to keep both minimal and maximal tests

ok, let's close it.
The merge hopefully takes some of this pain away.


1.1 and 1.2 no peer connection on windows

since update 1.1 but windows test config no longer synchronizes and finds no peer and remains blocked

my pc is behind a router and it is nat as you can see in the screen where there are only private ips
but the sync works in 1.0

launch a synchro on a windows pc in a nat

Steps to Reproduce

Screenshots

Desktop (please complete the following information):

OS: windows
Version: 10
Branch: 1.1 and 1.2

Can you explain a little bit more about your setup? Is this being run on docker images on windows? The more information to help try to replicate, the better. Thanks!

as I am testing I just use npm to install lodestar

Closing issues for specific incidents on old versions of Lodestar, please re-open if it happens with latest stable


Simplify session state watcher

Split out some stuff from https://github.com/vespa-engine/vespa/pull/14335, no functional changes

👍


Add pre-defined table styles

Could some nice pre-defined table styles be generated like "stripped" or "lined" that would allow a dev using tailwinds to just put the utility classes on a table and have a pre-set table?

I think this sort of things are great for the plugin's the team is going to support, but not for the core. 🙂

Yeah no plans to add these sorts of component-style classes to core right now, but like @MichaelDeBoey said they will be a good fit for the extension system we hope to ship in the coming weeks.
It's possible we revisit this down the road as a core thing one day, but going to close this for now as it's not on the roadmap.


Superset defaulting to local DB

I upgraded my superset environment with the master branch. The superset container is not starting because of:
2023-03-15 11:00:43,041:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected results
I expected it to use the managed PSQL in AWS. The DB_HOST is pointing to the AWS URL but the container is defaulting to local psql.
Actual results
what actually happens.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version:
superset version: superset version
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Seems like this could be an issue with Superset latest on master, or a matter of your config.  Either way probably hard to debug here in a way that would be useful to anyone else.  If this issue persists, it might be a good candidate for joining the Slack and asking there?

Why is it defaulting to local? What is the value of SQLALCHEMY_DATABASE_URI in config?

It turned out that my password had some special characters which conflicted with the SQLALCHEMY_DATABASE_URI. The host was hence invalid. Though the error message was misleading as you'd think it was trying to connect to local DB. To this, I remove those special characters from the DB string. The characters were @ and ). I'm thus closing this issue.


Can we have some kind of indication that the program has started receiving a hopefully usable response?

Several times I've sent a prompt to ChatGPT only for it to just sit there until I Ctrl+C to kill it. It would be nice to either have some kind of indication that a response is being received, or have the program give up after not receiving anything for a while.

+1
Also, it seems the CLI interface with stream turned on waits with displaying the message until the chat.openai.com response is fully generated. Long responses take >20seconds.

I made two fixes that solve the problem:

Now the cli per default streams the output of chatgpt live. So you can see whether it is responding or whether the program is waiting
I added a 60s timeout. If no response is returned within 60s the program breaks and outputs an error message. It is then your responsability to either try again, or try reauthentificating


[Suggestion-1.16.1] Add a blacklist config to allow disabling slabs to be placed Vertically.

Title^
Add a blacklist config to allow disabling slabs to be placed Vertically. Instead of an all On / Off config option. Would be helpful!
Using MC 1.16.1
Kind of like this that already exist but for Vertical Slabs
#The list of slab types and variants to ignore when creating double slabs
#Example: minecraft:purpur_slab

Saw you just released an update that includes this, just wanted to say thanks! :) 👍

No problem!


Does DSPY require cohere? Never saw this in the main documentation.....

AttributeError: module 'cohere' has no attribute 'CohereAPIError'
I know what the error is, but I'm wondering why its forcing cohere?

Are you using the latest version of DSPy? I think this should be solved from 2.4.10 onwards.
Reference - https://github.com/stanfordnlp/dspy/blob/main/dsp/modules/cohere.py.

I just loaded it from pip install so perhaps not if that isn't updated

@clearsitedesigns let us know if the problem persists if you do
pip install -U dspy-ai


example project build failed

this is output after enter terminal to react-native run-android command maybe relevant
JS server already running.
Building and installing the app on the device (cd android && ./gradlew installDebug)...
FAILURE: Build failed with an exception.

What went wrong:
Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory().

Could not create service of type PluginResolutionStrategyInternal using BuildScopeServices.createPluginResolutionStrategy().

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 0s
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
Command failed: ./gradlew installDebug
Error: Command failed: ./gradlew installDebug
at checkExecSyncError (child_process.js:629:11)
at Object.execFileSync (child_process.js:647:13)
at runOnAllDevices (/home/rn/Desktop/react-native-masonry-list-master/example/node_modules/react-native/local-cli/runAndroid/runAndroid.js:299:19)
at buildAndRun (/home/rn/Desktop/react-native-masonry-list-master/example/node_modules/react-native/local-cli/runAndroid/runAndroid.js:135:12)
at isPackagerRunning.then.result (/home/rn/Desktop/react-native-masonry-list-master/example/node_modules/react-native/local-cli/runAndroid/runAndroid.js:65:12)
at process._tickCallback (internal/process/next_tick.js:68:7)

@Luehang this libs have performance issue too. I managed to run. After scroll few times the screen darkens and the application crashes.

Hi @Frekansapp,
react-native-masonry-list is constantly being updated and the example project just hasn't been updating with it constantly.  To temporarily fix this problem, use the following codes in your project.
:tada: Usage Example

If you like react-native-masonry-list, please be sure to give it a star. Thanks and have a good day!

import MasonryList from "react-native-masonry-list";

//...
render() {
    return (
        <MasonryList
            images={[
                // Can be used with different image object fieldnames.
                // Ex. source, source.uri, uri, URI, url, URL
                { uri: "https://luehangs.site/pic-chat-app-images/beautiful-blond-blonde-hair-478544.jpg" },
                { source: { uri: "https://luehangs.site/pic-chat-app-images/beautiful-beautiful-women-beauty-40901.jpg" } },
                { uri: "https://luehangs.site/pic-chat-app-images/animals-avian-beach-760984.jpg",
                    // Optional: Adding a dimensions field with
                    // the actual width and height for REMOTE IMAGES
                    // will help improve performance.
                    dimensions: { width: 1080, height: 1920 } },
                { URI: "https://luehangs.site/pic-chat-app-images/beautiful-blond-fishnet-stockings-48134.jpg",
                    // Optional: Does not require an id for each
                    // image object, but is for best practices.
                    id: "blpccx4cn" },
                { url: "https://luehangs.site/pic-chat-app-images/beautiful-beautiful-woman-beauty-9763.jpg" },
                { URL: "https://luehangs.site/pic-chat-app-images/attractive-balance-beautiful-186263.jpg" },
            ]}
        />
    );
}
//...

The example project will be looked at soon and will be fix and updated.

If you're looking for a high quality app that shows you how to use Redux, Redux Saga, Select and React Navigation plus a whole lot more helpful things, go to https://luehangs.site/marketplace/product/RN Posting Demo App Kit.

Delete other codes and render just MasonryList solved the performance issue. Thank you

:+1: If you like react-native-masonry-list, please be sure to give it a star. Thanks.


2957 notes on collection properties

Purpose of this pull request
This pull request (PR) adds notes for certain source properties.
Note that I employed reuse snippets wherever I could. In many instances I couldn't do reuse snippets, such as in tables or within another reuse snippet.
Issue number: GitHub issue #2957

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks for the review, @kimsauce!


A bug in 'Adjust Width' component

Your paper has the following description of the adjust weight component:

The model takes as input the 𝑥 and 𝑦 coordinates (horizontal and vertical components respectively) for the viewports of the previous chunk of frames to predict the viewports for the next chunk of frames. Let (𝑥𝑓 , 𝑦𝑓 ) be the viewport at frame 𝑓 . However, if the viewport wraps around the equirectangular frame to another side of the frame, it would create a discontinuous time series of viewports. To model it as a continuous time series, 𝑥𝑓 needs to be width-adjusted, which is performed by the ‘Adjust Width’ component in Figure 3 using the following transformation:

However, the above equation does not seem to handle an extreme case: for example, if the user keeps rotating clockwise, crosses the right edge of the ERP frame once, and then crosses the right edge once or more, equation (1) will calculate the wrong result.
I wrote a python script to further illustrate the problem and suggest a solution:
def origin_adjust_width(lst, width):
    x = lst.copy()
    for f in range(1, len(x)):
        if abs(x[f]-x[f-1] + width) < abs(x[f]-x[f-1]):
            x[f] = x[f] + width
        elif abs(x[f]-x[f-1] - width) < abs(x[f]-x[f-1]):
            x[f] = x[f] - width
        else:
            x[f] = x[f]
    return x

def my_adjust_width(lst, width):
    x = lst.copy()
    for f in range(1, len(x)):
        remainder = (x[f] - x[f-1]) % width
        if abs(remainder - width) < abs(remainder):
            remainder = remainder - width
        x[f] = x[f-1] + remainder
    return x

x = [0, 1, 2, 0, 1, 2, 0, 1, 2]
your_res = origin_adjust_width(lst=x, width=3)
my_res = my_adjust_width(lst=x, width=3)
print(your_res)  # [0, 1, 2, 3, 4, 5, 3, 4, 5]
print(my_res)  # [0, 1, 2, 3, 4, 5, 6, 7, 8]

Hi, I think you might be right. Let me just re-check it and confirm. Thank you.

You’re welcome! It was a pleasure to assist you with this issue! Thank you for your amazing work on this project!


Need to write the name of parameter file in ''.

When I tried to pass the parameter file for ARM template using "az deployment group create .." command, I need to pass the parameter file argument in ''. e.g. --parameters<EMAIL_ADDRESS>This page does not provide the '' syntax.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f0aca150-4747-7670-f465-7439aecc40e5
Version Independent ID: f836844c-0089-1477-57af-43a76181e5d6
Content: Deploy resources with Azure CLI and template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/deploy-cli.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@kulkarnisachin07 Thanks for your comment! We will review and provide an update as appropriate.

I have verified and updated the document as required. The update would reflect soon i.e., in less than 24 hours.

Thanks for quick action!


Ah, thanks! For others, comments can be put in mark down like this:
<!-- HERE IS A COMMENT AND AS A HTML COMMENT, IT WILL NOT SHOW UP IN THE PDF -->


Webserver tasks for Helidon 3.0

[x] Routing abstraction for web server #1865
[ ] Request re-routing support #1866
[ ] Support for dynamic matching of resources #81 (deferred to after 3.0)
[ ] Add support for HTTP Strict Transport Security (HSTS) #932 (deferred to after 3.0)
[x] Support for HTTP/2 Server Push #1286
[ ] Webserver fluent path params processing #1867
[ ] Add a robust way to get the service base URL as java.net.URL that takes care of IPv6 specialities #1891

I am closing this epic as we are not going to implement the referenced issues in Helidon 3.
Some of the issues were fixed in 4.0
The remaining issues will be kept as enhancements


Refactor DB model to remove layers of inheritance

This refactors the DB model to remove inheritance and have a more clean separation between data structures (generated by OpenAPI) and functions that operate on these data structures.
Major changes:

DBUtils, SystemDBUtils, DatasetDBUtils no longer inherit from anything and only contain static functions
There is now a "DBCollection" variable introduced to indicate which DB collections functions should be working on

I'm still testing to make sure all elements of the UI work, but I think this is almost done.

Thanks @lyuyangh ! They should all be fixed and I tested the new code


Can we add support for .or?

e.g.
expect(block).subtypeOf("text").or.subtypeOf("media")

It seems that .or can't be supported because an AssertionError is (potentially) thrown before we ever reach .or and any following assertions.

Flowerflip 0.2.3 recognizes quotes as both media and textual

0.2.3 used in https://github.com/the-grid/taylor/commit/8c7cb3d6875f02aa1a4e43a8d1614f18b436ecdd


Add migration steps for yii2-swiftmailer

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
✔

Fixed issues
https://github.com/yiisoft/yii2-symfonymailer/issues/33

Thanks!


Term Management Page

We do not have a way to set the current term in CELTS.  We would like to have an "Admin Management" or "Admin Roles" tab in the sidebar that will lead to this page.  This page populate with all the terms for the year listed out, and admins will be able to choose to set one as the current term

 CELTS #129: Term Management Page


New package: RDKafka v0.1.0

Registering package: RDKafka
Repository: https://github.com/dfdx/RDKafka.jl
Created by: @dfdx
Version: v0.1.0
Commit: 27eb30e1006cab7a1f740f640b2cd0331994f7b5
Git reference: master

Should probably include https://github.com/dfdx/RDKafka.jl/pull/8

[noblock]
I guess this PR is now blocked for automatic merge, so for manual reviewers: as suggested above, I've incorporated dfdx/RDKafka.jl#8 into the master and this PR is now ready to be merged manually.


Paths to CSS and JS for /classic/config path result in 404s

What did you do?
Deployed Prometheus behind a proxy. Opened up the Networking tab on DevTools. Went to /classic/config.
What did you expect to see?
No errors / 404s.
What did you see instead? Under which circumstances?
Observed that the network calls to get the CSS and JS for that page result in 404s.

I omitted the remaining information about the environment since the fix seems to be relatively straightforward.
I believe the fix for this is just a quick followup to @juliusv's PR in https://github.com/prometheus/prometheus/pull/8142 to update the paths below to add /classic:
https://github.com/prometheus/prometheus/blob/39d79c3cfb86c47d6bc06a9e9317af582f1833bb/web/ui/templates/config.html#L2-L3

/help

/assign

@aiyengar2 Thanks for reporting this, you're totally right, and it's broken also without a proxy! Fix PR: https://github.com/prometheus/prometheus/pull/9202


issue 550 add monitoring to iplan

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @yaelal , please pull from master and push, fixed the tests that failed


guide: clarify auth for add --external

per https://discuss.dvc.org/t/dvc-add-external-s3-mybucket-data-csv-is-failing-with-access-error-even-after-giving-correct-remote-cache-configurations/726/4?u=jorgeorpinel

@jorgeorpinel it looks like deployment failed? does it run locally for you?

does it run locally for you?

It does 🤔

build seems to fail at
       [4/4] Building fresh packages...
       error /tmp/build_0e1ac83a/node_modules/sharp: Command failed.
       Exit code: 1
       Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

Cc @rogermparent

Should I merge and see what happens when deploying master? Or wait for @rogermparent

@jorgeorpinel I think master also fails (there is a Slack channel that you can follow). Master has been failing for a while I think. So, let's merge it.

OK, merged. This builds fine in my local machine BTW (Ubuntu 18 on WSL).


Avoid Conda wherever possible

With the recent shenanigans with Conda's license model, we should avoid using conda images wherever possible. SciComp mentioned that it's still okay to use Miniconda as long as you switch your distribution channel or something, but not sure if that's worth the trouble.

#315861a26040adc465c652d21a51807cd96a6c59 added for GATK


Use EMPTY and LOADED state properly on ol.VectorImageTile

Currently, vector image tiles with ERROR source tiles are set to EMPTY state. But the EMPTY state means that the renderer has nothing to do for the extent of that tile. Instead, we want the loadInterimTilesOnError logic to kick in when there are error tiles, so tiles from lower resolutions can fill the spots with error tiles. For this to work, we have to set the state to ERROR instead.
With #7206 fixed, we also no longer need to set a vector image tile to LOADED when only some of its source tiles are loaded, because source tiles will only be created if they are available on the source. By setting an ERROR state when just one source tile has an ERROR state, we ensure that the loadInterimTilesOnError logic works here too.

To see the issue that this pull request fixes, open the https://openlayers.org/en/master/examples/mapbox-vector-tiles.html example, and enter
map.getLayers().item(0).getSource().setUrl(
    'https://{a-e}.tiles.mapbox.com/v4/mapbox.mapbox-streets-v6/{z}/{x}/{y}.vector.pbf?' +
    'access_token=' + key);

in the console. This adds a non-existent server (e.tiles.mapbox.com) to cause loading errors. Then zoom in to a region that you're interested in, and you will see blank tiles.


[Identity] Improving DefaultAzureCredential diagnosability

This PR aims to improve the diagnosability of the DefaultAzureCredential (and the ChainedTokenCredential) by aggregating all the errors that might have occurred on the credential chain during GetToken calls into a single message provided via logs and errors if the chain is finally unable to retrieve a token.
Note: On #15923 it was mentioned to link to the troubleshooting guide on these aggregated errors, but it really makes the most sense on the underlying errors. I have made a separate issue to track that effort https://github.com/Azure/azure-sdk-for-go/issues/16843
If it gets approved:
Fixes #15923

@chlowell
Regarding your comment: https://github.com/Azure/azure-sdk-for-go/pull/16844#pullrequestreview-855777247
I think I can fix this by adding the following to DefaultAzureCredential: https://github.com/Azure/azure-sdk-for-go/pull/16844/commits/d7ad65f4f9b907859a4280dccffeb5dc3135824b
What do you think?

(just leaving some minor comments, looks like you and Charles are hashing it out) :)


Include README in Python Package

setup.py is automatically generated. Should this be done in cooperation with pulumi-terraform?

It is being done in cooperation with pulumi-terraform.  This change updates the dependency (note the pending change in the Gopkg.lock file).
This pulls in https://github.com/pulumi/pulumi-terraform/pull/197.
Or are you saying that pulumi-terraform should also generate the README.rst file in some fashion?  While that would be nice, a quick search did not indicate that there was an existing markdown to restructured text library for golang, so it would end up shelling out to pandoc at the end of the day regardless.

Oh, frig, I missed that. Sorry. LGTM.

In your defense, we had conditioned you that changes to expect changes to Gopkg.toml as well, and now that we are doing the "right" thing, that invariant no longer holds.  Doesn't help that GitHub suppresses the diff for the lock file.


chore: Upgrade golang.org/x/crypto  (#36)

chore:	address the following CVE:

CVE-2023-48795: golang.org/x/crypto Authentication Bypass by Capture-replay

Description

How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/lgtm


OpenAi

Uses OpenAi to select the best template based on the users prompt. The selected template text is then display in the "input text" textbox that can then be used to generate the corresponding GIF.

When I tried typing something into the input box, I got this error in the console


Warning: no rule to process file YTPlayer.html for architecture arm64

Warning: no rule to process file '/Path/To/Pods/YouTubePlayer/YouTubePlayer/YouTubePlayer/YTPlayer.html' of type text.html for architecture arm64

I think it is something related to this.

Thanks @Gerst20051. I'm closing this since I merged a PR #52 that should fix this and silence the warning. Thanks for using the library! :)


How do specify the directory I want to show?

I can't seem to find how to list a specific directory, is there no setting for that?

Unfortunately configuring a different "base" directory is not currently possible. At the moment the Directory Lister code and files to be listed must be in the same folder.
This is due to the way Directory Lister handles (or rather doesn't handle) file access. Directory Lister only lists the files. When it comes to accessing (i.e. downloading) those files it defers to the web server to handle. While Directory Lister could list files outside of the web server's root folder the web server would not be able to access those files for download.
To list a specific directory, upload the Directory Lister code to the directory you want to list.


Any way to protect usage of dashboard?

I know you can implement Google Auth, Github Auth or any custom Auth you'd like to implement to prevent who is accessing your dashboard.
What i'd like is to deploy a dashing instance on a site and be sure that no one will just copy my dashing directory and set up a new instance next to it without using my custom Auth. Is that possible?

I'm not sure I'm fulling understanding your request, but I think that this is more of System Administration issue than a Dashing issue...
I would achieve this by enforcing system permissions on the folder.

I'll try to explain. I want to make a commercial user of a specific dashboard that i would create and deploy with the rest of our solution. This needs to be installed "on site", that basically means that i need to be sure nobody can duplicate the dashboard (and so the work i've put in) to avoid paying for it.
I think this is not against MIT right?
I could develop a specific Auth system in my solution but the client could always reset the config.ru and just avoid it.

Oh, I got you. I don't know if it violates the license...
There are two approaches I would take to this:

Obfuscation - Make the auth code hard to remove / alter
Container / Appliance - Put the code into a VM or Container that has locked down permissions and 'just works' in their environment

Dashing certainly doesn't provide any functionality for licensing or restricting the number of running copies. You'll have to come up with some magic.

Thank you for your answers, i'll try to find something.


Change the default calendar

I want to change the default calendar. Because if someone uses Japanese calendar,  Date().year  returns the year in Japanese but I don't expect the behavior.
I suggest the changes below.
Date.defaultCalendar = .gregorian // Fix the default calendar to gregorian calendar.
Date().year // It'll always returns the year in gregorian calendar.

What do you think? If you agree to my suggestion, I'll make a pull request.

Thank you for suggestion! 😄
I disagree with Date.defaultCalendar. It is confusing because Date object is a just value and independent of the calendar setting in iOS.
Instead, below method will fill your need.
Date().changed(on: .japanese)

Currently, changed() calculates date components with Calendar.current, and so on calendar: Calendar argument will be useful for you.

Thank you for quick response! 😀
I think your idea is good way to change the calendar. I'll try it.

Sorry for less description. This method is not implemented yet. So, if you want it, please send a pull request!

Thank you for description!
I decided to use Calendar directly to get year in Gregorian calendar.  Because I noticed that Timepiece’s conveniences is based on Extension and I can’t add calendar as a stored property(I don’t want use Associated Object).


aio command description has extra newlines

Description
Note the DESCRIPTION section below, it has extra newlines per line. Not sure if it's an oclif@v2 thing. Filed https://github.com/oclif/core/issues/518
Source: https://github.com/adobe/aio-cli-plugin-auth/blob/b54b40c8f2c75a3c57c0f20849013b5402c8698b/src/commands/auth/login.js#L62-L84
Example:
❯ aio login --help
Log in with a certain Adobe IMS context and returns the access token.

USAGE
  $ aio login [--debug <value>] [-v] [-l | -g] [-c <value>] [-f] [-d] [-b] [-o]

FLAGS
  -b, --bare         print access token only
  -c, --ctx=<value>  Name of the Adobe IMS context to use. Default is the current Adobe IMS context
  -d, --decode       Decode and display access token data
  -f, --force        Force logging in. This causes a forced logout on the context first and makes sure to not use any cached data when
                     calling the plugin.
  -g, --global       global config
  -l, --local        local config
  -o, --[no-]open    Open the default browser to complete the login
  -v, --verbose      Verbose output
  --debug=<value>    Debug level output

DESCRIPTION
  Log in with a certain Adobe IMS context and returns the access token.

  If the Adobe IMS context already has a valid access token set (valid meaning

  at least 10 minutes before expiry), that token is returned.

  Otherwise, if the Adobe IMS context has a valid refresh token set (valid

  meaning at least 10 minutes before expiry) that refresh token is

  exchanged for an access token before returning the access token.

  Lastly, if the Adobe IMS context properties are supported by one of the

  Adobe IMS login plugins, that login plugin is called to guide through

  the IMS login process.

  The currently supported Adobe IMS login plugins are:

  * aio-lib-ims-jwt for JWT token based login supporting

  Adobe I/O Console service integrations.

  * aio-lib-ims-oauth for browser based OAuth2 login. This

  plugin will launch the default browser to guide the user through the

  login process. The plugin itself will *never* see the user's

  password but only receive the authorization token after the

  user has authenticated with Adobe IMS.

ALIASES
  $ aio login

Fixed with https://github.com/oclif/core/releases/tag/1.16.6 🎉


Could not find gem 'hellosign' in rubygems repository https://rubygems.org/ or installed locally

Hi I am getting issues while adding the gem and doing a bundle install
Could not find gem 'hellosign' in rubygems repository https://rubygems.org/ or installed locally

ruby version used: 3.0.0

Looks like the gem name should be
gem 'hellosign-api'

instead of
gem 'hellosign

🤦🏻 you're right, thanks!


Implement runcon

@bardiharborow, is there any progress with your implementation that you can share with us?


Clarify using unity input manager

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/gestures-and-motion-controllers-in-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unity-input-manager.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove scss extension from button scss index

Hi, I would like to help with material-components-web-react.
The sass imports are handy, but I was having trouble importing SCSS from Button. I needed to directly import the css from the non-react package, basically duplicating the intent of the index.scss of react-button:

When I looked at the icon component sass import I noticed that it didn't have an extension. Going into node_modules and removing it from the button index.scss file fixed the issue and allowed me to just import the button styles with @import "@material/button/mdc-button";, so perhaps this was just an oversight.
I've never used learn before, so I may need help figuring out how to contribute to this codebase :/

I signed it!

@johnelliott Thanks for opening the PR. You're right it's not necessary and we can remove the extension from the filename. Can you also remove it from card, floating-label, line-ripple, and text-field Sass files for consistency?
Also something I realize is that you do not have the creds for the screenshot tests. I pushed a commit to see if it works for me.

@moog16 thanks Matt. I like this lib; want to show my support :)

Is it OK to add line-ripple, floating-label to the allowed scopes for commit messages?

Codecov Report

Merging #62 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   99.17%   99.17%
=======================================
  Files          18       18
  Lines         606      606
  Branches       49       49
=======================================
  Hits          601      601
  Misses          5        5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a45c75a...f7a52d8. Read the comment docs.

Perhaps this test failure is also permission related for the screenshot job.

RE allowed scopes: YES definitely
RE Testing: Looking into Docker. Might be able to help us here.

Ok, I use Docker and maybe that'd be the easiest way to get many people up and running those tests. I  would be OK helping to set that up but I'd need initial direction.

Opened this PR: https://github.com/material-components/material-components-web-react/issues/71. I'm just gonna run the tests locally and merge this for you. Thanks!

Thanks @moog16


System.Reflection.TargetParameterCountException: 'Parameter count mismatch.'

I am getting the following error:
System.Reflection.TargetParameterCountException: 'Parameter count mismatch.'
I am using HotReload in Windows working with UWP Xamarin Forms

Hi,
What is the version of nuget?
Did it work before ?

BTW you didn't disable xmlc

Hi,
What is the version of nuget?
Did it work before ?

<PackageReference Include="Xamarin.Forms" Version="<IP_ADDRESS>8975" />
<PackageReference Include="Xamarin.HotReload" Version="1.4.14" />

i remove xaml compile , just same error

@Saccomani have it ever been working for you?

@Saccomani could you please click "view details" and show me the stacktrace ?

CI is creating 1.4.15


fix: spelling of 'declared' in README.md

In the readme, 'declared' is written as 'declaered'.

Indeed; thank you!


Update the uds path for GKE

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
3749a8412f1e01537e5647ab5c2ebd92016a1a5d
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-smoke

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
92d13a5708d74210b1a8d32ff6a51539cc215c9d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Sentinel Symantec Endpoint Protection data connector - Paser not working.

Describe the bug
Reference: https://github.com/Azure/Azure-Sentinel/issues/8769
To Reproduce
After updating the parser, the customer reported that results are not parsing any column of the Syslog.
https://github.com/Azure/Azure-Sentinel/commit/e38b6d16bd96c0f023a0369974ead0f6ec2e176e

Hi @v-miketang, thanks for flagging this issue. We will get back to you by 31 Oct 2023.

Hi @v-miketang, sorry for the delay, we will get back to you by 03 Nov 2023.

Hi @v-miketang, we have a mail communication on going for this issue. Analysis have been shared there. Waiting for your confirmation with customer.

We had a call with the customer on this issue. Although the provided issue has been fixed we need to rewrite the entire syslog message.

We are waiting for a call with customer for troubleshooting the issue

We are still waiting for a call with customer for troubleshooting the issue

Hi @v-miketang, since we have provided you the updated parser and since it working now. I am closing this issue.
We will push the changes to master soon.


Correct secret creation command

Private Registry FQDN also needs to be included in secret creation, otherwise Kubernetes will not be able to pull images.

This change is

@k8s-bot I have signed the CLA.


Add string equivalent methods

Add methods for family and order of syllables to eld.EthiopicUCDString class.

[x] get_order() - return list of orders for each character in string, non-syllables return None.
[x] get_family() - return list of families for each character in string, non-syllables return None.
[ ] convert_order(order, index?) - either convert each syllable in string to specific order, or only convert character at specified index in string. Return either as a list or a string.
[ ] convert_family(family, index?)

Is convert_family needed, and if so, expected usage and behaviour?
Should get_order and get_family be able to specify a string index and only report the order or family of syllable at that index in string?

I can't think of a use case for convert_family().
Yes. I think this is the more frequent use case.


added backend in feedback form

i added backend  functionality so that user feedback can be saved in the database issue #1713

database:

please add gssoc-ext and level3 before merge @PriyaGhosal

@AyushSharma72 Please see the conflicts .

@AyushSharma72 Please see the conflicts .

I have tested it it is working fine
It is deployed on netlify so it could be cors error
On your back-end only the localhost is allowed to send request you have to add the netlify url there then it will work

@AyushSharma72 Please see the conflicts .

the error is that on the frontend you have to add the url where your backend is hosted
then it will work

i have tested it :

on this fetch function you have to add the url of the backend
you can merge this pr @PriyaGhosal

hey @PriyaGhosal do you understand if not tell me and give me url of your hosted backend
otherwise please merge this PR

@AyushSharma72
Great contribution ! 🎉 Your pull request has been successfully merged! Also Take a moment to ⭐ Star the repository if you haven't already.


I can't change the default grey background on the line chart

Guys can somebody point me how to change the colour mentioned in the title.
And something else to mention here is that i think the method "setHighLightColor(UIColor)" is not present in the API or at least I couldn't find it.
"Line-, Bar-, Scatter-, Bubble- & CandleDataSet (below mentioned methods can be used for any of the mentioned DataSet classes)
setHighLightColor(int color): Sets the color that is used for drawing the highlight indicators. Don't forget to resolve the color using getResources().getColor(...) or Color.rgb(...) (or simply Color.BLACK)."

use gridBackgroundColor or UIView.backgroundColor
use set.highlightColor. Have no idea why you are saying setHighLightColor if it does not exist

all cool, thank you very much


can't edit on mobile as hard to close and reopen settings

Problems.
Currently editing on mobile is not really possible partly due to how settings sidebar works
While editing on mobile might not be a goal for 6.0 release it seems a shame to let something small like this to get in the way doing basic edits.
Blocks settings

block settings open by default on mobile taking up most of the screen
Blocks setting hide is not obvious. very hard to discover (mobile and desktop)
settings reopen is also hard to find (mobile and desktop)
settings reopen is close to the edge of the screen so hard to click on some mobiles

Describe the solution you'd like
toggle settings button
Implement the quanta solution of toggle in the toolbar now.
Note: this is from quanta design. Quanta toolbar is not needed for this, and we'd still keep the tabs in the settings

cog in bottom of toobar which toggles the open and close state of the settings sidebar

con: bit weird to have toggle on left to open something on the right but should be fine
should be at the bottom of toolbar since settings is not changing the page state.

also close button top left in settings
don't change how choice of block vs page settings shown for now
keep the current "hardly visible" open close toggle for now
make an experimental feature - https://github.com/plone/volto/issues/3896

turned on my default?

What to do about undo, cut and paste?

for the moment put them above the settings button since least amount of change
con: they don't below together and undo buttons should probably move

Alternatives considered

if there is a quanta block menu then there could also be a "settings" item there that specifically opens block settings

why:

fixes: not obvious how to close settings
fixes: not obvious how reopen settings
fixes: hard to reopen settings on mobile

settings in toolbar always opens page settings

Placement of button and undo

put settings next to save and cancel

con: its confusing. it's not a page level action

propose putting undo into a context menu in the toolbar

it doesn't make sense to put settings with undo since they are different kind of actions
context menu would be above save so it's in the right place on horizontal mobile view
pro: can put other functions later like find and replace

propose removing cut and paste from toolbar and using the material design select pattern instead

gestures only for undo/redo

undo should not be visible says apple. we should use a gesture,
android doesn't have a standard gesture for undo

perhaps have snackbar to allow for UI to undo

have an edit mode

if an edit is made then replace save cancel bar with undo bar with settings          undo redo accept
tick/accept returns you to save and cancel bar
this is what google docs mobile does (but then they don't have a "save")

Additional context
full quanta design which combines block menu and slate into one. It switched between block settings and page settings based on if a block was selected or not?

can you please assign the issue to me i will the issue

@gurramkarthiknetha please read and follow First-time contributors, especially Things not to do, Contributing to Plone, and Contributing to Volto.


Add _n operator to the name type

@johndebord is this really still a work in progress, or has it been abandoned?  If I don't hear back from you I'm going to assume it has been abandoned.

Closing due to lack of response/activity. Can be reopened if this is still needed.


wrap python script in discord bot

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
douglasstarnes, @archaengel, @Mrcryptowealth, @tipepo, @jydmyk, @VTenoris, @youssefojeil, @nat5687, @AmanGotchuParadigm, @xavierroma, @jmgrd98, @eurobas, @VijaySamrath, @impolska742, @amateur-dev, @CoryHenson17, @x-qing, @Github33xx, @AetherArt, @zilongliang

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
rswanson, @andrejrakic, @DaneWiid1, @vuhctreh, @0xqibing, @adradr, @zzau13, @jordaniza, @matagus, @victor-57Blocks, @aresbit, @PaleHazy, @rhacker, @Tcorner2x, @m4k2, @Mark1Jay2, @TheFanatr, @lht102, @intldds, @Nickqiaoo


docs: fix jsdoc lint issues

Description:
Fix all jsdoc lint issues. In most cases, full documentation of all methods has added. In some cases invalid / partially complete jsdoc blocks for methods were removed if they added nothing to the readability of the code or converted to non jsdoc single line comments.
Generally speaking full documentation was added to all reducers. Components mostly  just had doc cleanup as per the above.
Reducer code was reorganised so hat all reducers follow the same basic structure and code order.
Some unused legacy was removed.
Motivation and Context:
Fix lint issues.
Improve DX
How Has This Been Tested?
Manually
Types of changes:
Docs updates
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage increased (+0.1%) to 20.192% when pulling db05702d13ad710405de6b763bc9205102ca3b14 on mrfelton:docs/jsdoc into c0c52f8bd3a61410374efb3738e6be6d7f9ee731 on LN-Zap:master.

Updated!


Register New Package MetaArrays: 0.2.4

Registering: MetaArrays
Repository: https://github.com/haberdashPI/MetaArrays.jl
Version: v0.2.4
Commit: 182081c094061f4795eb5d28ad84654a21dbc310
Proposed by: @haberdashPI
Reviewed by: @haberdashPI
Reference: https://github.com/haberdashPI/MetaArrays.jl/commit/182081c094061f4795eb5d28ad84654a21dbc310#commitcomment-33232834

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084


Simplify the binary checking logic

Signed-off-by: Abhijeet Kasurde<EMAIL_ADDRESS>

@sfowl Thanks for the review and merge.


Jinja2 usage

Jinja2 usage is not declared in packaging (setup.py or requirements.txt).  Jinja2 modules are imported anywhere either, but we have some render_template() functions that call jinja2:
https://github.com/fabric-testbed/fabrictestbed-extensions/blob/dfecd98cfd02d1b789a3129367f7fc61fa47009d/fabrictestbed_extensions/fablib/component.py#L118-L123
https://github.com/fabric-testbed/fabrictestbed-extensions/blob/dfecd98cfd02d1b789a3129367f7fc61fa47009d/fabrictestbed_extensions/fablib/facility_port.py#L81-L86
https://github.com/fabric-testbed/fabrictestbed-extensions/blob/dfecd98cfd02d1b789a3129367f7fc61fa47009d/fabrictestbed_extensions/fablib/interface.py#L155-L160
https://github.com/fabric-testbed/fabrictestbed-extensions/blob/dfecd98cfd02d1b789a3129367f7fc61fa47009d/fabrictestbed_extensions/fablib/network_service.py#L533-L538
Looking at flake8's output (while working on PR #105) helped me find these.  I am not sure if these functions are actually useful, or if they could be removed.

I was too quick to conclude that jinja2 is not in requirements.txt (it very much is) and it being used without imported (it is imported in fablib.node).  It is just used without being imported in some modules fablib.component, fablib.facility_port, fablib.interface, and fablib.network_service.  I am still unsure about its usage and testing.


Infra Request - junixsocket (Christian Kohlschütter)

Project Name
junixsocket
Code Repository URL
https://github.com/kohlschutter/junixsocket
Project License
Apache 2.0
Names of primary maintainers/project leads
Christian Kohlschütter
Architectures/operating systems currently supported
Most operating systems and platforms, including macOS, Linux (also s390x), Android, Windows, Solaris, FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, AIX, IBM i.
Why are you interested in supporting the mainframe?
junixsocket is a Java/JNI library. Without support on the Mainframe (z/OS), Java applications that require junixsocket cannot be used.
For what it's worth, I'm already able to build and run junixsocket on z/OS, but I'm currently relying on someone else's resources, which make it hard to plan ahead.
I've also tried cross-compiling with ambitus gcc, but that doesn't seem to work as expected.
I'm trying to make my Open Source library "junixsocket" as useful as possible, and I found that we can use all sorts of BSD-style sockets with Java, not just the ones that are supported out of the box.
For example, with junixsocket you can use AF_UNIX (UNIX domain) sockets since Java 8. You can also use junixsocket in combination with Jetty to serve websites over TIPC (on Linux) or VSOCK (on Linux and mac). You can also use it to connect to databases like MySQL or PostgreSQL. Or use Java RMI over AF_UNIX, for example, among many other applications.
With a little extra work, junixsocket could support AF_IUCV / HiperSockets on z/OS as well...
Which operating system(s) will you need access to?
z/OS
Resources requested outside of the standard resources provided.
All I really need is remote access (ssh/scp/sftp) to a z/OS machine that has xlc and Java 8, 11 or newer.
If you have access to other z/* OSes (z/VM, z/TPF?, z/VSE?, ...), these would be very helpful as well.
For example, I can already build for z/TPF, but I have no way to test the results.
How long will the infrastructure be needed?
Ongoing
Any other comments or questions
Thanks in advance for your help!

Thank you @kohlschuetter for this! We are still in the process of getting the infrastructure up and going, but will reach out once it is. Let us know if you have an immediate need.

@jmertic Thanks for looking into this! Yes, the sooner the better.
I would like to include z/OS binaries to junixsocket by default.
I don't want to rely on binary builds from the test server I'm currently using, which is not maintained by a trust third party like you.


SCALE-104: Make container name configurable

Fixes https://jira.atlassian.com/browse/SCALE-104
From ops perspective it is sometimes difficult to tell which containers belong to which helm releases (for example jira vs jira-jsm). This PR makes it possible to use a unique (in namespace scope) helm release name as the main container name. To keep current names unchanged a new boolean variable is introduced - <product>.useChartNameAsContainerName with false default value, i.e. this is a non breaking change.
Crowd and confluence had hardcoded values.
Checklist

[x] I have added unit tests
[x] I have applied the change to all applicable products

Just one observation, the default value would mean not to use the containername name as chart name, which would be the opposite of the current default.
Downside of this that all the users who currently depend on this value, will see a change request when updating to the new chart, instead of leaving the default as is, being true.
Suggestion, keep the value true by default, and false could override to use the fullname instead.

Will this option be implemented to Confluence as well?


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2022-04-01T17:46:10+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
2f01c68fc59bebac57ae4c14e26ca7bcb91c0ee1
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
2f01c68fc59bebac57ae4c14e26ca7bcb91c0ee1
link
unknown
/test integ-telemetry-mc_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
2f01c68fc59bebac57ae4c14e26ca7bcb91c0ee1
link
unknown
/test integ-telemetry-mc_istio

integ-security-multicluster_istio
2f01c68fc59bebac57ae4c14e26ca7bcb91c0ee1
link
unknown
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest