update

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):

New Feature
Bug Fix
Improvement
Performance Improvement
Backward Incompatible Change
Build/Testing/Packaging Improvement
Other

Short description (up to few sentences):
...
Detailed description (optional):
...

Hello @yutiansut! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file dbms/tests/integration/helpers/cluster.py:

Line 118:80: E501 line too long (450 > 79 characters)
Line 136:80: E501 line too long (132 > 79 characters)
Line 214:80: E501 line too long (93 > 79 characters)
Line 215:80: E501 line too long (108 > 79 characters)
Line 216:40: E127 continuation line over-indented for visual indent
Line 216:80: E501 line too long (116 > 79 characters)
Line 236:80: E501 line too long (85 > 79 characters)
Line 241:80: E501 line too long (85 > 79 characters)
Line 379:80: E501 line too long (89 > 79 characters)
Line 475:80: E501 line too long (155 > 79 characters)

In the file dbms/tests/integration/test_block_structure_mismatch/test.py:

Line 12:1: E265 block comment should start with '# '

In the file dbms/tests/integration/test_dictionaries_all_layouts_and_sources/dictionary.py:

Line 112:1: W293 blank line contains whitespace
Line 296:80: E501 line too long (81 > 79 characters)
Line 352:1: W293 blank line contains whitespace

In the file dbms/tests/integration/test_dictionaries_all_layouts_and_sources/external_sources.py:

Line 391:80: E501 line too long (116 > 79 characters)
Line 394:80: E501 line too long (96 > 79 characters)
Line 413:80: E501 line too long (93 > 79 characters)
Line 433:80: E501 line too long (114 > 79 characters)
Line 434:80: E501 line too long (114 > 79 characters)
Line 444:18: E128 continuation line under-indented for visual indent
Line 462:23: E201 whitespace after '['
Line 462:68: E202 whitespace before ']'
Line 496:80: E501 line too long (104 > 79 characters)

In the file dbms/tests/integration/test_dictionaries_all_layouts_and_sources/http_server.py:

Line 9:80: E501 line too long (96 > 79 characters)
Line 14:80: E501 line too long (104 > 79 characters)

In the file dbms/tests/integration/test_dictionaries_all_layouts_and_sources/test.py:

Line 6:80: E501 line too long (117 > 79 characters)
Line 75:80: E501 line too long (83 > 79 characters)
Line 78:80: E501 line too long (82 > 79 characters)
Line 82:14: E127 continuation line over-indented for visual indent
Line 83:14: E127 continuation line over-indented for visual indent
Line 132:80: E501 line too long (101 > 79 characters)
Line 133:80: E501 line too long (101 > 79 characters)
Line 141:1: E302 expected 2 blank lines, found 1
Line 147:80: E501 line too long (98 > 79 characters)
Line 163:80: E501 line too long (89 > 79 characters)
Line 163:90: W291 trailing whitespace
Line 166:1: W293 blank line contains whitespace
Line 168:80: E501 line too long (81 > 79 characters)
Line 171:80: E501 line too long (84 > 79 characters)
Line 176:80: E501 line too long (102 > 79 characters)
Line 182:80: E501 line too long (117 > 79 characters)
Line 303:80: E501 line too long (93 > 79 characters)
Line 310:80: E501 line too long (117 > 79 characters)
Line 312:1: W293 blank line contains whitespace
Line 325:80: E501 line too long (95 > 79 characters)
Line 330:80: E501 line too long (83 > 79 characters)
Line 331:80: E501 line too long (89 > 79 characters)
Line 358:80: E501 line too long (92 > 79 characters)
Line 369:80: E501 line too long (117 > 79 characters)
Line 371:1: W293 blank line contains whitespace
Line 380:80: E501 line too long (95 > 79 characters)
Line 385:80: E501 line too long (83 > 79 characters)
Line 386:80: E501 line too long (89 > 79 characters)

In the file dbms/tests/integration/test_multiple_disks/test.py:

Line 185:80: E501 line too long (121 > 79 characters)
Line 736:80: E501 line too long (148 > 79 characters)
Line 799:80: E501 line too long (148 > 79 characters)

In the file dbms/tests/integration/test_redirect_url_storage/test.py:

Line 9:1: E302 expected 2 blank lines, found 1
Line 18:1: E302 expected 2 blank lines, found 1
Line 24:80: E501 line too long (202 > 79 characters)
Line 27:1: E302 expected 2 blank lines, found 1
Line 33:80: E501 line too long (217 > 79 characters)
Line 35:80: E501 line too long (95 > 79 characters)
Line 37:1: E302 expected 2 blank lines, found 1
Line 44:80: E501 line too long (214 > 79 characters)
Line 45:80: E501 line too long (118 > 79 characters)

In the file dbms/tests/integration/test_storage_hdfs/test.py:

Line 52:80: E501 line too long (83 > 79 characters)
Line 63:80: E501 line too long (85 > 79 characters)
Line 70:80: E501 line too long (81 > 79 characters)

In the file dbms/tests/integration/test_storage_s3/test.py:

Line 18:80: E501 line too long (116 > 79 characters)
Line 27:80: E501 line too long (116 > 79 characters)
Line 41:80: E501 line too long (116 > 79 characters)
Line 43:80: E501 line too long (126 > 79 characters)
Line 49:80: E501 line too long (83 > 79 characters)
Line 51:80: E501 line too long (95 > 79 characters)
Line 52:80: E501 line too long (99 > 79 characters)
Line 53:13: E722 do not use bare 'except'
Line 79:80: E501 line too long (169 > 79 characters)
Line 82:17: E201 whitespace after '['
Line 82:80: E501 line too long (122 > 79 characters)
Line 82:121: E202 whitespace before ']'
Line 84:1: W293 blank line contains whitespace
Line 93:80: E501 line too long (210 > 79 characters)
Line 102:80: E501 line too long (143 > 79 characters)
Line 105:1: W293 blank line contains whitespace
Line 111:80: E501 line too long (203 > 79 characters)
Line 121:80: E501 line too long (143 > 79 characters)
Line 124:1: W293 blank line contains whitespace
Line 131:80: E501 line too long (224 > 79 characters)
Line 134:80: E501 line too long (200 > 79 characters)
Line 152:28: E201 whitespace after '['
Line 152:50: E231 missing whitespace after ','
Line 152:52: E231 missing whitespace after ','
Line 152:80: E202 whitespace before ']'
Line 152:80: E501 line too long (82 > 79 characters)
Line 153:80: E501 line too long (213 > 79 characters)
Line 154:80: E501 line too long (100 > 79 characters)
Line 158:51: E201 whitespace after '['
Line 158:80: E501 line too long (107 > 79 characters)
Line 158:105: E202 whitespace before ']'

In the file dbms/tests/integration/test_storage_s3/test_server.py:

Line 28:80: E501 line too long (103 > 79 characters)
Line 46:6: E201 whitespace after '['
Line 46:33: E202 whitespace before ']'
Line 49:1: E305 expected 2 blank lines after class or function definition, found 1
Line 70:14: E111 indentation is not a multiple of four
Line 70:14: E117 over-indented
Line 71:14: E111 indentation is not a multiple of four
Line 72:14: E111 indentation is not a multiple of four
Line 73:14: E111 indentation is not a multiple of four
Line 73:80: E501 line too long (80 > 79 characters)
Line 74:14: E111 indentation is not a multiple of four
Line 74:40: E201 whitespace after '['
Line 74:80: E501 line too long (105 > 79 characters)
Line 76:14: E111 indentation is not a multiple of four
Line 76:14: E117 over-indented
Line 77:14: E111 indentation is not a multiple of four
Line 85:80: E501 line too long (109 > 79 characters)
Line 103:51: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 105:80: E501 line too long (129 > 79 characters)
Line 117:80: E501 line too long (85 > 79 characters)
Line 137:80: E501 line too long (80 > 79 characters)
Line 144:1: W293 blank line contains whitespace
Line 167:80: E501 line too long (83 > 79 characters)
Line 182:51: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 184:80: E501 line too long (129 > 79 characters)
Line 196:80: E501 line too long (85 > 79 characters)
Line 218:80: E501 line too long (86 > 79 characters)
Line 219:80: E501 line too long (84 > 79 characters)
Line 237:13: E722 do not use bare 'except'
Line 241:1: W293 blank line contains whitespace
Line 265:80: E501 line too long (83 > 79 characters)
Line 280:51: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 282:80: E501 line too long (129 > 79 characters)
Line 294:80: E501 line too long (85 > 79 characters)
Line 306:80: E501 line too long (163 > 79 characters)
Line 323:80: E501 line too long (163 > 79 characters)
Line 350:80: E501 line too long (87 > 79 characters)
Line 351:80: E501 line too long (91 > 79 characters)
Line 352:80: E501 line too long (84 > 79 characters)
Line 354:80: E501 line too long (103 > 79 characters)
Line 356:80: E501 line too long (84 > 79 characters)
Line 357:80: E501 line too long (107 > 79 characters)
Line 358:9: E201 whitespace after '['
Line 358:77: E202 whitespace before ']'
Line 359:2: E201 whitespace after '['
Line 359:30: E202 whitespace before ']'
Line 361:15: E261 at least two spaces before inline comment
Line 364:2: E201 whitespace after '['
Line 364:42: E202 whitespace before ']'
Line 366:2: E201 whitespace after '['
Line 366:29: E202 whitespace before ']'

In the file dbms/tests/queries/0_stateless/00960_live_view_watch_events_live.py:

Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 15:80: E501 line too long (94 > 79 characters)
Line 28:80: E501 line too long (84 > 79 characters)
Line 40:37: W605 invalid escape sequence '$'

In the file dbms/tests/queries/0_stateless/00962_temporary_live_view_watch_live.py:

Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 15:80: E501 line too long (94 > 79 characters)
Line 28:80: E501 line too long (84 > 79 characters)
Line 30:80: E501 line too long (84 > 79 characters)
Line 40:37: W605 invalid escape sequence '$'

In the file dbms/tests/queries/0_stateless/00964_live_view_watch_events_heartbeat.py:

Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 15:80: E501 line too long (94 > 79 characters)
Line 30:80: E501 line too long (84 > 79 characters)
Line 32:80: E501 line too long (84 > 79 characters)
Line 37:42: W605 invalid escape sequence ')'
Line 39:42: W605 invalid escape sequence ')'
Line 42:37: W605 invalid escape sequence '$'
Line 45:31: W291 trailing whitespace

In the file dbms/tests/queries/0_stateless/00965_live_view_watch_heartbeat.py:

Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 15:80: E501 line too long (94 > 79 characters)
Line 30:80: E501 line too long (84 > 79 characters)
Line 32:80: E501 line too long (84 > 79 characters)
Line 38:42: W605 invalid escape sequence ')'
Line 40:42: W605 invalid escape sequence ')'
Line 43:37: W605 invalid escape sequence '$'
Line 46:31: W291 trailing whitespace

In the file dbms/tests/queries/0_stateless/00966_live_view_watch_events_http.py:

Line 8:1: E402 module level import not at top of file
Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 25:80: E501 line too long (84 > 79 characters)
Line 31:5: E303 too many blank lines (2)
Line 31:31: E231 missing whitespace after ':'
Line 31:80: E501 line too long (150 > 79 characters)

In the file dbms/tests/queries/0_stateless/00967_live_view_watch_http.py:

Line 8:1: E402 module level import not at top of file
Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 25:80: E501 line too long (84 > 79 characters)
Line 31:5: E303 too many blank lines (2)
Line 31:31: E231 missing whitespace after ':'
Line 31:44: E231 missing whitespace after ':'
Line 31:80: E501 line too long (140 > 79 characters)

In the file dbms/tests/queries/0_stateless/00970_live_view_watch_events_http_heartbeat.py:

Line 8:1: E402 module level import not at top of file
Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 25:80: E501 line too long (84 > 79 characters)
Line 30:31: E231 missing whitespace after ':'
Line 30:80: E501 line too long (216 > 79 characters)
Line 31:80: E501 line too long (152 > 79 characters)
Line 33:80: E501 line too long (150 > 79 characters)
Line 35:80: E501 line too long (150 > 79 characters)

In the file dbms/tests/queries/0_stateless/00971_live_view_watch_http_heartbeat.py:

Line 8:1: E402 module level import not at top of file
Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 25:80: E501 line too long (84 > 79 characters)
Line 30:31: E231 missing whitespace after ':'
Line 30:44: E231 missing whitespace after ':'
Line 30:80: E501 line too long (206 > 79 characters)

In the file dbms/tests/queries/0_stateless/00979_live_view_watch_live.py:

Line 9:1: E402 module level import not at top of file
Line 13:1: E265 block comment should start with '# '
Line 15:80: E501 line too long (94 > 79 characters)
Line 28:80: E501 line too long (84 > 79 characters)
Line 40:21: E231 missing whitespace after ','
Line 41:8: E111 indentation is not a multiple of four
Line 42:8: E111 indentation is not a multiple of four
Line 43:8: E111 indentation is not a multiple of four
Line 46:37: W605 invalid escape sequence '$'
Line 49:31: W291 trailing whitespace

In the file dbms/tests/queries/0_stateless/helpers/client.py:

Line 18:80: E501 line too long (83 > 79 characters)

In the file docs/tools/github.py:

Line 15:80: E501 line too long (108 > 79 characters)

In the file utils/github/__main__.py:

Line 32:80: E501 line too long (80 > 79 characters)
Line 45:5: E128 continuation line under-indented for visual indent
Line 53:5: E128 continuation line under-indented for visual indent

In the file utils/github/parser.py:

Line 3:1: E302 expected 2 blank lines, found 1
Line 37:80: E501 line too long (119 > 79 characters)

In the file utils/github/query.py:

Line 283:80: E501 line too long (101 > 79 characters)
Line 322:80: E501 line too long (92 > 79 characters)
Line 326:5: E301 expected 1 blank line, found 0
Line 344:80: E501 line too long (95 > 79 characters)
Line 351:46: E251 unexpected spaces around keyword / parameter equals
Line 351:48: E251 unexpected spaces around keyword / parameter equals
Line 351:77: E251 unexpected spaces around keyword / parameter equals
Line 351:79: E251 unexpected spaces around keyword / parameter equals
Line 351:80: E501 line too long (95 > 79 characters)
Line 357:5: E303 too many blank lines (2)
Line 405:80: E501 line too long (80 > 79 characters)

In the file utils/make_changelog.py:

Line 425:80: E501 line too long (101 > 79 characters)


can we use .c file converted in to .s file in swerv , i got error

Hello SwerV team
Can we use C file in place of assembly file. If yes, what should be cross compiler command for conversion .c to .s file
Actually  i want to put my hello assembly file in place of hello_world2.s.
for this i write hello program in c and converted in .s file . but when i use command
riscv64-unknown-elf-cpp  -I /home/mayank/swerv_eh1/configs/snapshot/default/     hello.s > hello.cpp.s
its working fine. but for next command
riscv64-unknown-elf-as -march=rv32imc hello.cpp.s -o hello.o
i got error
Assembler message:
unrecognized opcode 'sd ra,8(sp)'
unrecognized opcode 'sd s0,0(sp)'
unrecognized opcode 'ld ra,8(sp)
unrecognized opcode 'ld s0,0(sp)''
what should be command to convert .c file to .s file
Please help regarding this.
thanks & regards
Mayank

Mayank, please check your source hello.s file. It should not have any 64 bit mnemonics (ld, sd are 64 bit load/stores, and not supported by -march=rv32imc).
The Makefile (in $RV_ROOT/tools/Makefile) shows the steps to create the required hex files.
program.hex: $(ASM_TEST_DIR)/$(ASM_TEST).s ${RV_ROOT}/configs/snapshots/$(snapshot)/common_defines.vh
    @echo Building $(ASM_TEST)
ifeq ($(shell which $(GCC_PREFIX)-as),)
    @echo " !!! No $(GCC_PREFIX)-as in path, using canned hex files !!"
    cp ${RV_ROOT}/testbench/hex/*.hex .
else
    cp $(ASM_TEST_DIR)/$(ASM_TEST).s .
    $(GCC_PREFIX)-cpp   -I${RV_ROOT}/configs/snapshots/$(snapshot)  $(ASM_TEST).s  > $(ASM_TEST).cpp.s
    $(GCC_PREFIX)-as -march=rv32imc $(ASM_TEST).cpp.s -o $(ASM_TEST).o
    $(GCC_PREFIX)-ld -m elf32lriscv --discard-none -T${RV_ROOT}/testbench/link.ld -o $(ASM_TEST).exe $(ASM_TEST).o
    $(GCC_PREFIX)-objcopy -O verilog --only-section ".data*" --only-section ".rodata*" $(ASM_TEST).exe data.hex
    $(GCC_PREFIX)-objcopy -O verilog --only-section ".text*" --set-start=0x0 $(ASM_TEST).exe program.hex
    $(GCC_PREFIX)-objdump -dS $(ASM_TEST).exe > $(ASM_TEST).dis
    $(GCC_PREFIX)-nm -f posix -C $(ASM_TEST).exe > $(ASM_TEST).tbl
    @echo Completed building $(ASM_TEST)
endif

Thank you sir
Now I have one question
Can I connect any IP with LSU AXI master interface of swerv.
If yes, swerv core can write data in to register of IP like ARM processor
can write data on IP's register through software interface with C API.
Thanks & regards
Mayank
On Tue 28 May, 2019, 9:50 PM aprnath<EMAIL_ADDRESS>wrote:

Mayank, please check your source hello.s file. It should not have any 64
bit mnemonics (ld, sd are 64 bit load/stores, and not supported by
-march=rv32imc).
The Makefile (in $RV_ROOT/tools/Makefile) shows the steps to create the
required hex files.
program.hex: $(ASM_TEST_DIR)/$(ASM_TEST).s ${RV_ROOT}/configs/snapshots/$(snapshot)/common_defines.vh
@echo Building $(ASM_TEST)
ifeq ($(shell which $(GCC_PREFIX)-as),)
@echo " !!! No $(GCC_PREFIX)-as in path, using canned hex files !!"
cp ${RV_ROOT}/testbench/hex/.hex .
else
cp $(ASM_TEST_DIR)/$(ASM_TEST).s .
$(GCC_PREFIX)-cpp   -I${RV_ROOT}/configs/snapshots/$(snapshot)  $(ASM_TEST).s  > $(ASM_TEST).cpp.s
$(GCC_PREFIX)-as -march=rv32imc $(ASM_TEST).cpp.s -o $(ASM_TEST).o
$(GCC_PREFIX)-ld -m elf32lriscv --discard-none -T${RV_ROOT}/testbench/link.ld -o $(ASM_TEST).exe $(ASM_TEST).o
$(GCC_PREFIX)-objcopy -O verilog --only-section ".data" --only-section ".rodata*" $(ASM_TEST).exe data.hex
$(GCC_PREFIX)-objcopy -O verilog --only-section ".text*" --set-start=0x0 $(ASM_TEST).exe program.hex
$(GCC_PREFIX)-objdump -dS $(ASM_TEST).exe > $(ASM_TEST).dis
$(GCC_PREFIX)-nm -f posix -C $(ASM_TEST).exe > $(ASM_TEST).tbl
@echo Completed building $(ASM_TEST)
endif
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westerndigitalcorporation/swerv_eh1/issues/23?email_source=notifications&email_token=AFC6NXYLKCQZMPAE7LWLD53PXVLTXA5CNFSM4HP73LM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWMVD5Y#issuecomment-496587255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFC6NXZTHXHWKOHW6X3P5E3PXVLTXANCNFSM4HP73LMQ
.

Yes, you should be able to connect any memory addressable IP directly, or via an interconnect matrix to the LSU AXI bus.
There is a SweRV FPGA build provided by us which has an example that you may be able to reference.

Sir,
I write C code to read and write in module my_register. C code will execute
inside riscv swerv.
converted C code to assembly from Riscv gcc compiler.
Swerv connected with module my_Register with lsu_AHB interface in a new top
module, add top file in flist.vcs
follow make file and generate program.hex .
Make file vcs-run command in terminal to simulate.
but value is not going to store internal reg q of module with C-api
Reg_write(address,data), i am checking value with $monitor inside
my_register module.
so where can i debug haddrr, hready ,.... signals inside SWERV. actually
where reg_write address value will be store in swerv after assembly
instruction executed? i am stuck.
On Wed, May 29, 2019 at 8:17 AM aprnath<EMAIL_ADDRESS>wrote:

Yes, you should be able to connect any memory addressable IP directly, or
via an interconnect matrix to the LSU AXI bus.
There is a SweRV FPGA build
https://github.com/westerndigitalcorporation/swerv_eh1_fpga provided by
us which has an example that you may be able to reference.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westerndigitalcorporation/swerv_eh1/issues/23?email_source=notifications&email_token=AFC6NX53ITANKPY6YSLAIDLPXXVERA5CNFSM4HP73LM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWN74NA#issuecomment-496762420,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFC6NX7FR52XXDHVDF2FPELPXXVERANCNFSM4HP73LMQ
.


Please update go version to 1.21.9 or 1.22.2

This is for CVE : https://github.com/advisories/GHSA-4v7x-pqxf-cx7m
This is for decK 1.37.

@akoshok1 @mheap
The latest deck version (1.39) already uses 1.22.4.
If we do a patch release for 1.37 with this update, would we need to do the same for 1.38?
Also, prior versions (1.36 and lower) have 1.21 as well. Do we still support these or are these deprecated / EOL? How many simultaneous versions do we support at a time?

@Prashansa-K It looks like the release job uses 1.20 (see https://github.com/Kong/deck/blob/main/.github/workflows/release.yaml#L20)
We should update the jobs to read from go.mod and release a new version. Asking people to upgrade to latest is acceptable for deck

This is fixed in 1.39.3


Memory: Report Characteristic read only memory

Review making the Report Characteristic const (in program space).  It shouldn't change, but initial attempts (via just const) didn't seem to work.

Mitigated with redesign of HID Service.


kuma-cp: 2.3.1 -> 2.4.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kumahq/kuma/releases.
meta.description for kuma-cp is: "Service mesh controller"
meta.homepage for kuma-cp is: "https://kuma.io/"
meta.changelog for kuma-cp is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.0 with grep in /nix/store/l27s62zyvh9jwqj21vq9wnaavdah2gyv-kuma-cp-2.0.0
found 2.0.0 in filename of file in /nix/store/l27s62zyvh9jwqj21vq9wnaavdah2gyv-kuma-cp-2.0.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
kuma
kuma-cp
kuma-dp
kuma-experimental
kuma-prometheus-sd
kumactl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l27s62zyvh9jwqj21vq9wnaavdah2gyv-kuma-cp-2.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kuma-cp https://github.com/r-ryantm/nixpkgs/archive/a77446c93618eabc005f0830341ae288c46ed6c7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l27s62zyvh9jwqj21vq9wnaavdah2gyv-kuma-cp-2.0.0
ls -la /nix/store/l27s62zyvh9jwqj21vq9wnaavdah2gyv-kuma-cp-2.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

kuma
kuma-experimental
kuma-prometheus-sd

3 packages built:

kuma-cp
kuma-dp
kumactl

Maintainer pings
cc @zbioe for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kumahq/kuma/releases.
meta.description for kuma-cp is: "Service mesh controller"
meta.homepage for kuma-cp is: "https://kuma.io/"
meta.changelog for kuma-cp is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.1 with grep in /nix/store/3mgbxi884s2jx2bim0pcmwyakwqkacdr-kuma-cp-2.0.1
found 2.0.1 in filename of file in /nix/store/3mgbxi884s2jx2bim0pcmwyakwqkacdr-kuma-cp-2.0.1

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
kuma
kuma-cp
kuma-dp
kuma-experimental
kuma-prometheus-sd
kumactl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3mgbxi884s2jx2bim0pcmwyakwqkacdr-kuma-cp-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kuma-cp https://github.com/r-ryantm/nixpkgs/archive/4a2a6cabe4c708e0909a5b55f587117369c27def.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3mgbxi884s2jx2bim0pcmwyakwqkacdr-kuma-cp-2.0.1
ls -la /nix/store/3mgbxi884s2jx2bim0pcmwyakwqkacdr-kuma-cp-2.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

kuma
kuma-experimental
kuma-prometheus-sd

3 packages built:

kuma-cp
kuma-dp
kumactl

Maintainer pings
cc @zbioe for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kumahq/kuma/releases.
meta.description for kuma-cp is: Service mesh controller
meta.homepage for kuma-cp is: https://kuma.io/
meta.changelog for kuma-cp is: https://github.com/kumahq/kuma/blob/2.4.0/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.0 with grep in /nix/store/aiw1m85n0gycmi5lgp68hy121d22mmvd-kuma-cp-2.4.0
found 2.4.0 in filename of file in /nix/store/aiw1m85n0gycmi5lgp68hy121d22mmvd-kuma-cp-2.4.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
kuma
kuma-cp
kuma-dp
kuma-experimental
kumactl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aiw1m85n0gycmi5lgp68hy121d22mmvd-kuma-cp-2.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kuma-cp https://github.com/r-ryantm/nixpkgs/archive/da536adb9566d024ed09a3c6d1c7c67ae2c6dd7d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/aiw1m85n0gycmi5lgp68hy121d22mmvd-kuma-cp-2.4.0
ls -la /nix/store/aiw1m85n0gycmi5lgp68hy121d22mmvd-kuma-cp-2.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

kuma
kuma-cp
kuma-dp
kuma-experimental
kumactl

Maintainer pings
cc @zbioe for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kumahq/kuma/releases.
meta.description for kuma-cp is: Service mesh controller
meta.homepage for kuma-cp is: https://kuma.io/
meta.changelog for kuma-cp is: https://github.com/kumahq/kuma/blob/2.4.3/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.3 with grep in /nix/store/wrainw9a7s8amp5dwgmbp2222fzf4xpx-kuma-cp-2.4.3
found 2.4.3 in filename of file in /nix/store/wrainw9a7s8amp5dwgmbp2222fzf4xpx-kuma-cp-2.4.3

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
kuma
kuma-cp
kuma-dp
kuma-experimental
kumactl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wrainw9a7s8amp5dwgmbp2222fzf4xpx-kuma-cp-2.4.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kuma-cp https://github.com/r-ryantm/nixpkgs/archive/2d8854840256b450d93663056e0ab1be5b2908b1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2d8854840256b450d93663056e0ab1be5b2908b1#kuma-cp

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wrainw9a7s8amp5dwgmbp2222fzf4xpx-kuma-cp-2.4.3
ls -la /nix/store/wrainw9a7s8amp5dwgmbp2222fzf4xpx-kuma-cp-2.4.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

kuma
kuma-cp
kuma-dp
kuma-experimental
kumactl

Maintainer pings
cc @zbioe for testing.


Archive failed, error: exit status 65

I wanted to set up two workflows. A release and dev build for our QA.
But I am trying now for half a day to fix the issue and I don't understand what the problem is. The log shows my correct name, but later in the logs it looks like that No certificate for team 'S6XWPU628M' matching 'Apple Development: ázgþr Celebi (359KG8ZNWB)' . My name is Özgür. I created new provisioning profiles and new certificates and still, it doesn't work.
61cfd9bc13a6fc34.log

Hi @oezguercelebi! Sorry to hear about the issue. Can you send us a link to the app and allow us access? That provides us access to the list of certificates and such that would help us debug this.

Hi @oezguercelebi! Sorry to hear about the issue. Can you send us a link to the app and allow us access? That provides us access to the list of certificates and such that would help us debug this.

Hi @bitce, customer support helped me to resolve the issue. I followed a webinar where a "certificate-and-profile-installer" and "ios-auto-provision" was in the workflow. But that seems to be the issue. I removed now the "ios-auto-provision" and manually added the provision profiles from the codesigndoc export. Now I am waiting for customer support to get back to me, because I am struggling to create .ipa version that uses the debug build configuration. But that has nothing to do with the listed issue here. Access is already granted: https://app.bitrise.io/app/69ac985300b7b6f0#/builds.

Hi @bitce, customer support helped me to resolve the issue. I followed a webinar where a "certificate-and-profile-installer" and "ios-auto-provision" was in the workflow. But that seems to be the issue. I removed now the "ios-auto-provision" and manually added the provision profiles from the codesigndoc export. Now I am waiting for customer support to get back to me, because I am struggling to create .ipa version that uses the debug build configuration. But that has nothing to do with the listed issue here. Access is already granted: https://app.bitrise.io/app/69ac985300b7b6f0#/builds.


antora documentation

The docs need to be ported to antora+mrdocs

Addressed in https://github.com/cppalliance/buffers/pull/24.


Hammerhead failed to setAttribute on Element

What is your Scenario?
I am trying to click a button that opens up an Integry modal but during automation I keep receiving this error:

It also doesn't work when unlocking the window and clicking it manually, but it does work fine when clicking it manually outside of automation.
What is the Current behavior?
An error gets thrown at t.setAttributeCore (http://localhost:65062/hammerhead.js:10:28517) when clicking the button.
What is the Expected behavior?
Clicking the button opens the Integry modal without any issues.
What is your public website URL? (or attach your complete example)
DevExpress has access to our repo. Please email me if re-authentication is necessary.
What is your TestCafe test code?
integrations_page_tests.js
test
    .meta({ created_on: '12/27/22', created_by: 'Justin Grabenbauer', updated_on: '', updated_by: '' })
    .meta({ scope: 'sanity', priority: 'low', showstopper: 'no', github_ID: '1585' })
    ('user_can_add_an_integration', async t => {

        // Purpose: To verify that a user can add an integration

        const integration_name = 'ClickFunnels Classic'

        await WorkspaceMainNavPageObjects.navigate_to_workspace_settings()
        await SettingsPageObjects.navigate_to_integrations_page()
        await t.debug()
        await IntegrationsPageObjects.connect_integration(integration_name)
})

integrations_page_repo.js
import { Selector, t } from 'testcafe'

class IntegrationsPageObjects {
    constructor() {
        this.btn_connect_integration = Selector('button').withText('Connect integration')
    }

    async connect_integration(integration_name) {

        // Purpose: To connect an integration

        await t
            .click(this.btn_connect_integration)
            .click(Selector('div').withText(integration_name))
    }
}

export default new IntegrationsPageObjects()

Your complete configuration file
require('dotenv').config()
const data = require('./data/data.json')
const { RequestLogger } = require('testcafe')

// TODO: See if we can make this part local to a function instead of out in the open, globally.
// Set the URL for where we want to start logging
let logger_url = data.api_endpoints.notifications_dropdown

switch(process.env.ENV) {
    case 'staging':
        logger_url = data.authenticated_urls.staging.concat(logger_url)
        break

    case 'production':
        logger_url = data.authenticated_urls.production.concat(logger_url)
        break
    }

const notifications_dropdown_logger = RequestLogger(logger_url)

// Agnostic for all environments
let skipped_tests = [

    // Located in all_contacts_page_tests.js
    'user_can_modify_contacts_table_columns', // 12-19-22

    // Located in all_products_page_tests.js
    'user_can_create_a_subscription_product', // 09-27-22
    'user_can_set_a_price_for_physical_products', // 09-27-22

    // Located in apps_page_tests.js
    'user_cannot_access_sites_when_feature_is_disabled', // 07-28-22
    'user_cannot_access_settings_when_feature_is_disabled', // 07-28-22
    'user_cannot_access_analytics_when_feature_is_disabled', // 09-16-22
    'user_cannot_access_marketing_when_feature_is_disabled', // 09-16-22
    'user_cannot_access_products_when_feature_is_disabled', // 09-16-22
    'user_cannot_access_contacts_when_feature_is_disabled', // 09-16-22
    'user_cannot_access_orders_when_feature_is_disabled', // 09-16-22
    'user_cannot_access_sales_when_feature_is_disabled', // 09-16-22

    // Located in billing_page_tests.js
    'user_can_navigate_to_billing_page', // 08-22-22

    // Located in blog_page_tests.js
    'user_is_able_to_change_blog_template', // 12-06-22
    'user_can_add_a_gif_to_blog', // 11-30-22
    'user_can_change_blog_post_style', // 12-06-22
    'user_can_clone_a_blog_post', // 11-30-22
    'user_can_create_a_blog_post', // 11-30-22
    'user_can_edit_blog_settings', // 07-06-22
    'user_can_edit_existing_blog_post_information', // 11-30-22

    // Located in courses_page_tests.js
    'courses_back_button_navigates_to_previous_page',
    'optin_user_can_navigate_through_course', // 12-06-22
    'user_can_log_into_customer_center_with_magic_link',

    // Located in dashboard_page_tests.js
    'user_can_navigate_to_forms_page_from_dashboard', // 11-22-22
    'user_can_navigate_to_payouts_page_from_dashboard', // 11-22-22

    // Located in funnels_page_tests.js
    'user_can_clone_a_funnel',
    'user_can_navigate_through_funnel',

    // Located in marketing/broadcasts_page_tests.js
    'user_can_create_new_broadcast', // 06-20-22

    // Located in marketing/templates_page_tests.js
    'user_can_create_broadcast_template', // 06-13-22

    // Located in orders/all_orders_page_tests.js
    'user_can_refund_order', // 10/18/22

    // Located in orders/order_page_tests.js
    'user_is_able_to_create_new_order', // 09-27-22
    'user_is_able_to_complete_payment_on_order', // 09-27-22
    'user_is_able_to_partially_pay_order', // 09-27-22
    'user_is_able_to_refund_order', // 09-27-22
    'user_is_able_to_set_delayed_status_on_order', // 09-27-22
    'user_is_able_to_set_processing_status_on_order', // 09-27-22
    'user_is_able_to_set_packed_status_on_order', // 09-27-22
    'user_is_able_to_set_ready_status_on_order', // 09-27-22
    'user_is_able_to_set_delivered_status_on_order', // 09-27-22
    'user_is_able_to_set_shipped_status_on_order', // 09-27-22
    'user_is_able_to_set_backorder_status_on_order', // 09-27-22
    'user_is_able_to_set_pending_status_on_order', // 09-27-22
    'user_is_able_to_set_lost_status_on_order', // 09-27-22
    'user_can_add_multiple_fulfillments_to_order', // 09-27-22
    'user_can_partially_fulfill_order', // 08-11-22

    // Located in pages_page_tests.js
    'user_can_pin_a_page_from_edit_page', //07-29-22

    // Located in pipelines_page_tests.js
    'user_can_navigate_to_pipelines_page', // 09/14/22

    // Located in reporting_page_tests.js
    'opt-ins_by_landing_page_report_displays', // 06/21/22

    // Located in sites_overview_page_tests.js
    'user_can_add_header_to_site', // 07-06-22
    'user_can_change_site_style', // 10-31-22
    'user_can_edit_site_name', // 10-04-22
    'user_can_make_site_password_protected', // 10-03-22

    // Located in themes_page_tests.js
    'user_can_edit_theme_name', // 08-08-22

    // Located in url_redirects_page_tests.js
    'user_can_delete_a_url_redirect', // 11-30-22
    'user_is_able_to_edit_url_redirect' // 11-30-22
]

// Cleanup scripts that need to be skipped, but can't be in the skipped tests
let clean_up_tests = [
    // Located in clean_up_scripts.js
    'clean_up_copies_of_funnels',
    'clean_up_copies_of_funnel_pages',
    'clean_up_copies_of_pages',
    'clean_up_products',
    'clean_up_site_pages',
    'clean_up_workflows',
    'dismiss_notifications',
    'clean_up_collaborators',
]

// Production specific scripts needing to be skipped for various reasons
let production_skipped_tests = [
    'user_can_navigate_to_affiliate_center_page', // Disabling because the link is disabled in production as of 12/07/22
    'user_can_navigate_to_order_tags_page', // Link disabled through Launch Darkly as of 08/29/22
    'user_can_navigate_to_payments_ai_dashboard', // Production PAI account not set up as of 08/29/22
    'user_is_able_to_navigate_to_the_inbox_page', // Inbox link is not activated in production as of 08/31/22
    'customer_can_place_order_through_funnel', // Disabling until we have PAI set up in production as of 10/04/22
    'user_can_navigate_to_sequences_page', // Disabling because it's behind a feature gate in produciton as of 10/17/22
    'user_can_navigate_to_events_and_deadlines_page', // Disabling because the link is disabled in production as of 11/28/22
    'user_can_navigate_to_community_page' // Disabling because the link doesn't display in production as of 12/21/22
]

// Scripts that need to run with a single concurrency
let isolated_tests = [
    // Located in sites_overview_page_tests.js
    'user_can_make_site_public',
    'user_can_edit_site_name',
    'user_can_make_site_password_protected',
    'user_can_make_site_private',
    'user_can_edit_site_domain',
    'changing_site_domain_updates_funnel_urls',
    'changing_site_domain_updates_blog_urls',
    'changing_site_domain_updates_course_urls',
    'user_can_add_header_to_site',

    // Located in account_details_page_tests.js
    'user_can_edit_account_name',
    'user_can_edit_account_password',
    'user_can_change_account_language',

    // Located in general_page_tests.js
    'user_can_edit_workspace_details',

    // Located in blog_page_tests.js
    'user_can_edit_blog_settings',

    // Located in themes_page_tests.js
    'user_can_promote_theme_to_live_from_index_page',
    'user_can_promote_theme_to_live_from_overview_page',

    // Located in the workflow_builder_page_tests.js
    'broadcast_room_category_pulls_back_expected_pages',
    'downsell_category_pulls_back_expected_pages',
    'landers_category_pulls_back_expected_pages',
    'my_funnel_pages_category_pulls_back_expected_pages',
    'opt_in_category_pulls_back_expected_pages',
    'order_category_pulls_back_expected_pages',
    'order_confirmation_category_pulls_back_expected_pages',
    'sales_category_pulls_back_expected_pages',
    'terms_of_service_category_pulls_back_expected_pages',
    'thank_you_category_pulls_back_expected_pages',
    'upsell_category_pulls_back_expected_pages',
    'webinar_confirmation_category_pulls_back_expected_pages',
    'webinar_registration_category_pulls_back_expected_pages'
]

// Filter that joins the skipped scripts with the production skipped tests
let production_filter = skipped_tests.concat(production_skipped_tests).concat(clean_up_tests)

// Filter that joins ALL filtered scripts so that they are not run for a full suite
let full_filter = skipped_tests.concat(isolated_tests).concat(clean_up_tests)

let build_filter = () => {

    // Purpose: To set the suite that we want to run. (isolated, regression, sanity)

    var filter = {}

    switch(process.env.ENV) {
        case 'production':
            if(process.env.SCOPE) {
                filter = {
                    testGrep: `^(?!.*(${production_filter.join('|')})).*$`,
                    testMeta: {
                        scope: process.env.SCOPE
                    }
                }
            }
            break
        case 'staging':
            if(process.env.SCOPE) {
                filter = {
                    testGrep: `^(?!.*(${skipped_tests.join('|')})).*$`,
                    testMeta: {
                        scope: process.env.SCOPE
                    }
                }
            } else {
                filter = {
                    testGrep: `^(?!.*(${full_filter.join('|')})).*$`
                }
            }
            break
    }

    return filter
}

let determine_concurrency = () => {

    // Purpose: To set concurrency dependant on the scope that is passed

    let concurrency = 5
    if (process.env.SCOPE == 'isolated') {
        concurrency = 1
    }
    return concurrency
}

module.exports = {
    assertionTimeout: 5000,
    browsers: [
        "chrome:headless --window-size=1920,1159"
    ],
    concurrency: determine_concurrency(),
    cache: true,
    clientScripts: [
        "scripts/click_expand_all_for_courses_details_page.js"
    ],
    disableMultipleWindows: true,
    filter: build_filter(),
    hooks: {
        fixture: {
            before: async ctx => {
                // Set the notifications dropdown logger globally
                ctx.notifications_dropdown_logger = notifications_dropdown_logger
            }
        },
        // Set the request hook for the notifications dropdown logger
        request: notifications_dropdown_logger
    },
    hostname: "localhost",
    pageLoadTimeout: 30000,
    quarantineMode: {
        successThreshold: 1,
        attemptLimit: 2
    },
    reporter: [
        {
            name: "spec",
            output: "artifacts/reports/spec_results"
        },
        {
            name: "xunit",
            output: "artifacts/reports/xunit_results.xml"
        },
        {
            name: "testrail"
        }
    ],
    runExecutionTimeout: 1800000,
    screenshots: {
        path: "artifacts/screenshots",
        pathPattern: "${TEST}_${DATE}_${TIME}.png",
        takeOnFails: true,
        thumbnails: false
    },
    selectorTimeout: 5000,
    skipJsErrors: true,
    skipUncaughtErrors: true,
    src: "tests/**",
    testExecutionTimeout: 240000
}

Your complete test report
Running tests in:

Chrome <IP_ADDRESS> / Ventura 13

settings - integrations
✖ user_can_add_an_integration (screenshots: /Users/justingrabenbauer/cf2-test-cafe-poc/artifacts/screenshots/user_can_add_an_integration_2022-12-27_10-49-53.png)

The specified selector does not match any element in the DOM tree.
| Selector('div')
 > |   .withText('ClickFunnels Classic')
Browser: Chrome <IP_ADDRESS> / macOS 10.15.7
Screenshot: /Users/justingrabenbauer/cf2-test-cafe-poc/artifacts/screenshots/user_can_add_an_integration_2022-12-27_10-49-53.png
11 |
12 |        // Purpose: To click the Connect integration button
13 |
14 |        await t
15 |            .click(this.btn_connect_integration)

16 |            .click(Selector('div').withText(integration_name))
17 |    }
18 |}
19 |
20 |export default new IntegrationsPageObjects()
21 |

at  (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:16:14)
at asyncGeneratorStep (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:2:258)
at _next (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:2:596)
at  (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:2:761)
at  (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:2:502)
at IntegrationsPageObjects.connect_integration (/Users/justingrabenbauer/cf2-test-cafe-poc/pom/settings/integrations/integrations_page_repo.js:10:49)
at  (/Users/justingrabenbauer/cf2-test-cafe-poc/tests/settings/integrations_page_tests.js:45:39)
at asyncGeneratorStep (/Users/justingrabenbauer/cf2-test-cafe-poc/tests/settings/integrations_page_tests.js:7:315)
at _next (/Users/justingrabenbauer/cf2-test-cafe-poc/tests/settings/integrations_page_tests.js:7:653)

1/1 failed (1m 17s)
Warnings (2):
The "browsers", "concurrency", and "filter" options from the configuration file will be ignored.
The file at "/Users/justingrabenbauer/cf2-test-cafe-poc/artifacts/screenshots/user_can_add_an_integration_2022-12-27_10-49-53.png" already exists. It has just been rewritten with a recent screenshot. This situation can possibly cause issues. To avoid them, make sure that each screenshot has a unique path. If a test runs in multiple browsers, consider including the user agent in the screenshot path or generate a unique identifier in another way.
Screenshots
No response
Steps to Reproduce

Run script
Check console

TestCafe version
2.0.0
Node.js version
18.12.0
Command-line arguments
ENV=staging testcafe "chrome '--window-size=1920,1159'" -t 'user_can_add_an_integration' -c1
Browser name(s) and version(s)
Chrome 108
Platform(s) and version(s)
macOS Ventura 13
Other
No response

Hello @Jgrabenbauer ,
Thank you for the example. I've managed to reproduce the issue.

We will close this issue since it is fixed in the Native Automation mode. Please try the native automation mode in your tests.
Feel free to reopen the issue if you need a fix for the other browsers or you cannot use Native Automation for some reason.


loadPaths needs "path" module to be imported

Description
If you use the loadPaths - Option the plugin throws an error "✘ [ERROR] [plugin sass-plugin] path is not defined".
If you import import path from 'path'; this error is gone.
Expected Behaviour
Path module is included by plugin itself
Actual Behaviour
Path module has to be included by user

Can you give me more context (e.g your build script)? I don't recall any usages of the path identifier within the plugin

Sorry for delay, I already deleted the build file and need to rebuild it.
import path from 'path'; // Without this it breaks with "sassPlugin - path is not defined"
import esbuild from 'esbuild';
import {sassPlugin} from 'esbuild-sass-plugin'
import postcss from 'postcss';
import autoprefixer from 'autoprefixer';

await esbuild.build({
    entryPoints: {
        style: 'assets/admin/styles/main.scss'
    },
    bundle: true,
    //sourcemap: true,
    //minify: true,
    target: ['chrome80'],
    loader: {
        '.png': 'dataurl',
        '.jpg': 'dataurl',
        '.svg': 'text',
        '.woff': 'file',
        '.woff2': 'file',
    },
    outbase: 'public/admin',
    outdir: 'public/admin/css/',
    plugins: [sassPlugin({
        loadPaths: [
            "assets/admin/styles/",
            "node_modules/@fortawesome/fontawesome-free/",
            "node_modules/@fontsource/poppins/scss",
            "node_modules/bootstrap/scss",
        ],
        precompile(source, pathname) {
            const basedir = path.dirname(pathname)
            return source.replace(/(url\(['"]?)(\.\.?\/)([^'")]+['"]?\))/g, `$1${basedir}/$2$3`)
        },
        async transform(source, resolveDir) {
            const {css} = await postcss([autoprefixer]).process(source);
            return css;
        }
    })]
}).catch(() => process.exit(1))

Everything is fine and the error you get has nothing to do with loadPaths.
You are creating a function that uses path from its containing scope
...
precompile(source, pathname) {
            const basedir = path.dirname(pathname)
            return source.replace(/(url\(['"]?)(\.\.?\/)([^'")]+['"]?\))/g, `$1${basedir}/$2$3`)
},
...

so you have to define it in that scope and that import is the way to do it

Thank you.


profile analysis worker is broken

have the renderer or a worker go slow
see the profile analysis worker failing to start

this was caused by https://github.com/microsoft/vscode/commit/828118d55e5b4da1e06536d4cbf933b74eb51291#diff-a8d63e03d2b4ed8a2080e0e9cc22b7a597c207afb25973dfa53fe543ef8555d5
ReferenceError: window is not defined
    at eval (profileAnalysisWorker.js:3:1798)
    at t._safeInvokeFunction (workerMain.js:5:1248)
    at t._invokeFactory (workerMain.js:5:1428)
    at t.complete (workerMain.js:5:1685)
    at L._onModuleComplete (workerMain.js:6:1051)
    at L._resolve (workerMain.js:6:510)
    at L.defineModule (workerMain.js:5:5564)
    at n (workerMain.js:6:1745)
    at eval (profileAnalysisWorker.js:3:1550)
    at anonymous (profileAnalysisWorker.js:8:4534)

The old code was also accessing window and why is this worker the only one failing 🤷 :
const ttPolicy = window.trustedTypes?.createPolicy('defaultWorkerFactory', { createScriptURL: value => value });

have the renderer or a worker go slow

Is there an easy way to do this? What do you mean by 'go slow'?

To verify

enable this setting "application.experimental.rendererProfiling": true
close TypeScript workspace https://github.com/microsoft/TypeScript
open the checker.ts file
open dev tools console
select F1 > Force Retokenize
wait while everything is froozen
when vscode recovers wait for a message like " WARN [perf] Renderer reported VERY LONG TASK (7139ms), starting profiling session '386d1579-8adc-476d-87e4-fb3bcdd13afe'"
immediately run F1 > Force Retokenize again
verify that you don't see the error from mentioned above
verify that you do see "errors" like " ERR PerfSampleError: by <> in ..."


Frontend unit tests

Set up environment to execute frontend unit tests based on karma.

Currently, it is not possible on WIndows Systems to execute karama tests due to too many open files when running the gulp tasks.


Importing FreeCAD in 3.7 segfaults in macOS 10.15

Issue: When installing conda from a fresh Miniconda environment using python 3.7 in macOS 10.15, python segfaults on FreeCAD import. Repro steps:
$ conda create -n fcenv python=3.7
$ conda activate fcenv
$ conda install freecad
$ python
>>> import os, sys
>>> sys.path.append(os.path.join(os.environ["CONDA_PREFIX"], "lib"))
>>> import FreeCAD
[1]    12659 segmentation fault  python

Note that the defaults pull FreeCAD 0.18.3, but I haven't had luck with 0.18.2 or 0.18.1.

Environment (conda list):

$ conda list
# packages in environment at /Users/username/opt/miniconda3/envs/fcenv:
#
# Name                    Version                   Build  Channel
boost-cpp                 1.70.0               h75728bb_2    conda-forge
bzip2                     1.0.8                h01d97ff_1    conda-forge
ca-certificates           2019.9.11            hecc5488_0    conda-forge
certifi                   2019.9.11                py37_0    conda-forge
coin3d                    4.0.0             h26c4a4f_1006    conda-forge
curl                      7.65.3               h22ea746_0    conda-forge
expat                     2.2.5             h4a8c4bd_1004    conda-forge
freecad                   0.18.3           py37h4764a83_2    conda-forge
freetype                  2.10.0               h24853df_1    conda-forge
future                    0.18.1                   py37_0    conda-forge
hdf4                      4.2.13            hf3c6af0_1002    conda-forge
hdf5                      1.10.5          nompi_h3e39495_1104    conda-forge
icu                       64.2                 h6de7cb9_1    conda-forge
jpeg                      9c                h1de35cc_1001    conda-forge
jsoncpp                   1.8.4             ha1b3eb9_1001    conda-forge
krb5                      1.16.3            hcfa6398_1001    conda-forge
libblas                   3.8.0               14_openblas    conda-forge
libcblas                  3.8.0               14_openblas    conda-forge
libclang                  8.0.1                h770b8ee_1    conda-forge
libcurl                   7.65.3               h16faf7d_0    conda-forge
libcxx                    9.0.0                h89e68fa_1    conda-forge
libedit                   3.1.20170329      hcfe32e1_1001    conda-forge
libffi                    3.2.1             h6de7cb9_1006    conda-forge
libgfortran               4.0.0                         2    conda-forge
libiconv                  1.15              h01d97ff_1005    conda-forge
liblapack                 3.8.0               14_openblas    conda-forge
libllvm8                  8.0.1                h770b8ee_0    conda-forge
libnetcdf                 4.6.2             h1a02027_1003    conda-forge
libopenblas               0.3.7                h4bb4525_2    conda-forge
libpng                    1.6.37               h2573ce8_0    conda-forge
libssh2                   1.8.2                hcdc9a53_2    conda-forge
libtiff                   4.0.10            h3527a1b_1004    conda-forge
libxml2                   2.9.9                h12c6b28_5    conda-forge
libxslt                   1.1.33               h320ff13_0    conda-forge
llvm-openmp               9.0.0                h40edb58_0    conda-forge
lz4-c                     1.8.3             h6de7cb9_1001    conda-forge
ncurses                   6.1               h0a44026_1002    conda-forge
netgen                    6.2.1808        py37hd7f4ea3_1006    conda-forge
nspr                      4.20              h0a44026_1000    conda-forge
nss                       3.47                 hcec2283_0    conda-forge
numpy                     1.17.3           py37hde6bac1_0    conda-forge
occt                      7.3.0             hc05df86_1005    conda-forge
openssl                   1.1.1c               h01d97ff_0    conda-forge
pip                       19.3.1                   py37_0    conda-forge
pivy                      0.6.5a3          py37h02c1c16_0    conda-forge
pthread-stubs             0.4               h1de35cc_1001    conda-forge
pyside2                   5.13.1           py37h2815f34_4    conda-forge
python                    3.7.3                h93065d6_1    conda-forge
pyyaml                    5.1.2            py37h01d97ff_0    conda-forge
qt                        5.12.5               h1b46049_0    conda-forge
readline                  8.0                  hcfe32e1_0    conda-forge
setuptools                41.4.0                   py37_0    conda-forge
six                       1.12.0                py37_1000    conda-forge
smesh                     <IP_ADDRESS>              hbe4f68f_6    conda-forge
soqt                      1.6.0a            h93cf301_1003    conda-forge
sqlite                    3.30.1               h93121df_0    conda-forge
tbb                       2019.9               ha1b3eb9_0    conda-forge
tk                        8.6.9             h2573ce8_1003    conda-forge
vtk                       8.2.0           py37hcba847f_203    conda-forge
wheel                     0.33.6                   py37_0    conda-forge
xerces-c                  3.2.2             hbda6038_1004    conda-forge
xz                        5.2.4             h1de35cc_1001    conda-forge
yaml                      0.1.7             h1de35cc_1001    conda-forge
zlib                      1.2.11            h0b31af3_1006    conda-forge
zstd                      1.4.3                he7fca8b_0    conda-forge

Details about  conda and system ( conda info ):

$ conda info
     active environment : fcenv
    active env location : /Users/username/opt/miniconda3/envs/fcenv
            shell level : 2
       user config file : /Users/username/.condarc
 populated config files : /Users/username/.condarc
          conda version : 4.7.12
    conda-build version : not installed
         python version : 3.7.4.final.0
       virtual packages :
       base environment : /Users/username/opt/miniconda3  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /Users/username/opt/miniconda3/pkgs
                          /Users/username/.conda/pkgs
       envs directories : /Users/username/opt/miniconda3/envs
                          /Users/username/.conda/envs
               platform : osx-64
             user-agent : conda/4.7.12 requests/2.22.0 CPython/3.7.4 Darwin/19.0.0 OSX/10.15
                UID:GID : 501:20
             netrc file : None
           offline mode : False

Note that the defaults pull FreeCAD 0.18.3, but I haven't had luck with 0.18.2 or 0.18.1.

Can you try using one of the dev builds:
conda install freecad -c freecad/label/dev

@looooo , that worked. Thanks! Feel free to close or leave open as a hint to others with the same issue.

@johnkgamble Thanks for reporting. With the upcoming 0.18.4 this should be fixed also for the conda-forge packages.

@looooo FYI I'm on 0.18.4 from conda-forge and I'm still getting the seg fault. Installing from freecad/label/dev worked for me as well

@likewei92 Thanks for reporting. It's possible we added some commits targeting this issue, but I can't remember exactly. Anyway, I don't think it's due to recipe differences. So let's focus on the 0.19 release for now.


Update Swagger UI and provide dynamic hostname support

Tidies up the OpenAPI generator code in ffapi
Upgrades Swagger UI to V5
Exposes on the ffapi.APIServer on /api/openapi.yaml as well as /api/openapi.json
Allows an option for dynamically determining the public hostname from the request

For scenarios where there is complex API Gateway infrastructure in front of the FireFly server, that needs to propagate the external protocol/hostname/path via Header on each request

Note there are breaking API changes for any package that is directly using the SwaggerUIHTML function, which to my knowledge is only FireFly Core (where I'm working on a corresponding change).
There shouldn't be any breaking changes for consumers just using ffapi.APIServer to expose their routes as REST.

Codecov Report

Merging #97 (4d3dc80) into main (8401dd6) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #97   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           63        63
  Lines         4993      5039   +46
=========================================
+ Hits          4993      5039   +46

Files Changed
Coverage Δ

pkg/ffapi/apiserver.go
100.00% <100.00%> (ø)

pkg/ffapi/handler.go
100.00% <100.00%> (ø)

pkg/ffapi/openapi3.go
100.00% <100.00%> (ø)

pkg/ffapi/openapihandler.go
100.00% <100.00%> (ø)


[cmake][Issue #341] Revert cuda_gen_all_arch flag and automatic build target selection

WAR fix for Issue #341 while performance drop debug is underway.

@atadkase - let's benchmark cudamapper performance before pushing this change in. could be that we want to keep it for cudamapper and revert only for cudapoa/cudaaligner

It seems that cudamapper perf degrades with this change. I'll rework it so that this affects only cudapoa and cudaaligner

Closing this PR as #409 was opened to address the perf decrease in cudamapper with this change.


What are the possible values for /CertType

Please update the documentation with a list of possible values for /CertType (Page 14,
C:\ops-server-config\Install\OpsDashboardUtility\CreateOneClickInstaller.bat)   If certificate is not a selfsigned, what value I should use for ?

@elinz Is there core documentation for this you can just point them to?

@VytautasGipiskis Upon further investigation, I've found that the /CertType parameter is actually ignored by the OperationsDashboardUtility.exe. If you're using a CA cert or domain cert you would use the /certpath parameter to specify the path to the cert and use the /password parameter to specify the cert password, otherwise your using a self-signed cert and don't need to use the /certpath or /password parameters as self-signed is assumed.
I will be removing the /CertType parameter; see #758.

Thanks, you can close the issue.


SemanticSimilarity descriptor throws pydantic validation error

I am unable to use the SemanticSimilarty descriptor since I already receive a pydantic.error_wrappers.ValidationError: 1 validation error for SemanticSimilarity on initializing the descriptor with SemanticSimilarity().
Full error:
File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for SemanticSimilarity
with_column
  field required (type=value_error.missing)

Since the SemanticSimilarity() call doesn't take any parameters and by itself isn't dependent on my data or environment I'm unable to resolve this error.
I get the same error with multiple different python versions and in different evironments.

Issue resolved itself


Decode reports from a byte buffer

This is speculative: empirically it goes faster but theoretically it could make things worse.
So I would like to try it out by merging into master hence into dev, and if we don't like it we can revert.

So I would like to try it out by merging into master hence into dev, and if we don't like it we can revert.

The cleaner way to do this is to de-automate the relevant services in flux, and then deploy an image from this branch. cc @2opremio who has done this a few times.

Yep, I would rather do that before merging. @bboreham mind giving it a try? I can guide you. It basically entails:

Modifying flux's config in dev to stop deploying scope automatically
Deploying you image manually.


A.04.IR01.IR02.hierarchy

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
In the sentence:
'Checks if a resource type (hierarchyLevel) is provided and is taken from the MD_ScopeCode codelist.'
MD_ScopeCode is a link that points to the INSPIRE Codelist(*) (**)
However, the MD TG maps the INSPIRE values to the already existing original ISO values.
So the codelist values are simply a subset of those defined in B.5.25 MD_ScopeCode <<CodeList>>
(*)The INSPIRE codelist contains the value 'services' that was amended into 'service' in the MD Regulation Corrigendum).
(**) The INSPIRE codelist makes available codes that are absolute HTTP URIs (e.g. http://inspire.ec.europa.eu/metadata-codelist/ResourceType/dataset ) while in ISO 19139 you need just the term 'dataset'. The INSPIRE codelist does not make the term available on its own.
Proposed Change
Remove the link to the INSPIRE Codelist and reference instead table B.5.25 MD_ScopeCode <<CodeList>> of ISO 19115.

Proposed Resolution
"Agreed with proposed change.
Remove the link to the INSPIRE Codelist and reference instead table B.5.25 MD_ScopeCode <> of ISO 19115."


Input data for parametrizable models

Most models/intents will require input data. For example, a simple swap intent will require the amount to swap and the minimum amount to receive as inputs to the model. This is useful because it allows the app developers to reuse such parametrizable intents.
MiniZinc uses a data file that looks like:
n = 5;
y = 6.3;

We can follow the exact same format for Pint. We can also decide to use  toml file instead to simplify parsing and to use something more standard.

No longer relevant


Rejecting issuance initiation navigates back to the issuance screen

Closing this issue as the code in this repository is deprecated (as its name implies). For a more up-to-date web wallet UI, refer to our more recent community edition identity stack that is actively maintained and updated in the waltid-identity repository.


Possible changes to the Compendium Browser

A proposal for a number of changes and the reason, if there are some that are not needed or can be done already in some way they can be marked as done.
General:

[ ] Instead of source, show the Pack, once one is chosen, show the different sources in that pack. This would maintain the functionality while lessening the current bloat.
[ ] Trait Search bar: Add Clear Filter button
[ ] Society: Add filter and icon showing if something is PFS Standard, Limited or Restricted. Would require data entry.

Action Tab:

[ ] Number of actions: Filtering by actionType (Action, Reaction, Free, and Passive) and if the option “Action” is picked, by 1, 2 or 3 actions.

Bestiary Tab:

[ ] Spellcaster: Whether a creature has spells or not.
[ ] (Dev only) Ability to search for individual stats: This could help find errors in data entry.

Equipment Tab:

[ ] Usage: Ability to filter by usage (Held, Worn or Affixed/Etched). If Held also the number of hands, if Worn also where they are worn, if affixed/etched in what kind of equipment.
Weapons

[ ] Specific Magic Weapon: For searching those specifically. Right now it can be done with the trait Magical and picking in Weapon Filters the wanted (or all) of the category, but maybe an easier method is also welcomed.

Armor:

[ ] Specific Magic Armor: Same as Specific Magic Weapon but for armors.

Feats Tab:

[ ] Skill Feats: Indicate somehow (maybe text, like the one for rarity) if you need trained, expert, master or legendary

[ ] Prerequisite: Indicate with some icon if the feat has prerequisites or not
Feat Types:

[ ] Curses: Right now it's empty, should it be deleted?
[ ] Deity Boons: Right now it's empty, either delete or rename and include here the Divine Intercessions
[ ] Society Boons: Right now it's empty, should it be deleted or are we missing the data? What is expected to go here?

Hazard Tab:

[ ] Source Filter is currently broken.

Spell Tab:

[ ] Cast time: Filter by cast time of the spell, for categories maybe something like: reaction, 1 action, 2 actions, 3 actions, variable (for cases like Heal), 1+ minute.
[ ] Saving Throw: For which saving throw they target if any, right now there is no good way to find this.
[ ] Heightenable: If the spell can be heightened or not.

[ ] Add filter for spell range, defense #15561, #11511
[ ] Allow for preset filters #14252
[ ] Allow for quick negated trait search #8446
[ ] Allow for search / negated search in prereqs #12799 (Likely not going to happen)
[ ] Add quick merchant buttons to browser #8447


Fix timout on BlockWriter.Shutdown

Close connection on PERSISTED event to reduce duration of Shutdown().
Connection to KVS endpoint is closed by the server a few seconds after receiving PERSISTED event.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_dataplane_PutMedia.html#API_dataplane_PutMedia_ResponseElements

Persisted: Kinesis Video Streams has persisted the fragment (for example, to Amazon S3). You get this acknowledgement if you configured the stream to persist the data. After you receive this acknowledgement, the producer can stop buffering the fragment.

Avoid creating duplicated connection when there is a prepared one and timecode has over int16 jump
which caused timeout on Shutdown().

@seqsense/cloud_backend please take a look


Enabling aqua ambiguity testing for Turing

We can test ambiguities only for Turing and not its dependencies.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
460 unchanged lines in 13 files lost coverage.
Overall coverage decreased (-28.8%) to 57.205%

Files with Coverage Reduction
New Missed Lines
%

src/mcmc/emcee.jl
2
90.2%

src/variational/VariationalInference.jl
4
14.29%

src/mcmc/gibbs.jl
4
94.05%

src/mcmc/particle_mcmc.jl
10
87.84%

src/mcmc/gibbs_conditional.jl
12
0.0%

src/mcmc/Inference.jl
18
77.3%

ext/TuringDynamicHMCExt.jl
29
0.0%

src/mcmc/mh.jl
32
57.43%

ext/TuringOptimExt.jl
50
0.0%

src/variational/advi.jl
53
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-28.8%

Covered Lines:
917

Relevant Lines:
1603

💛  - Coveralls

Indeed, that's what I suggested in https://github.com/TuringLang/Turing.jl/pull/2257#discussion_r163024095. Maybe put it in a testset and maybe only test ambiguities on Julia >= 1.10 (or some other recent Julia versions) since it might not be worth it fixing ambiguities that only show up in old Julia versions (which sometimes also imply old dependencies)?

(Rebased against master to check if #2294 works)


[BULK UPDATE] DocuTune - Fix build validation issues: docs-link-absolute

Global effort to fix build validation errors
The Microsoft Skilling team is fixing build validation errors and specific brand inconsistencies in Microsoft technical documentation for the rest of FY23 Q1. This will help address various accessibility, security, and usability issues. This PR was generated using DocuTune. It includes only targeted fixes and minor formatting adjustments.
DocuTune PRs improve quality of technical content by finding and automatically correcting a broad set of issues only where the correction is suitable. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!
CorrelationId: 0df9c2d6-63f8-4d1e-8b57-b33611a06514
InitiativeId: docutune-build-validation-issues-2022-05
PointOfContact: Alex Buck

#docutune-draft

Docs Build status updates of commit c0ca245:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Object-Detection-using-Faster-R-CNN.md
:warning:Warning
View
Details

articles/ReleaseNotes/CNTK_2_0_Release_Notes.md
:warning:Warning
View
Details

articles/ReleaseNotes/CNTK_2_1_Release_Notes.md
:warning:Warning
View
Details

articles/ReleaseNotes/CNTK_2_2_Release_Notes.md
:bulb:Suggestion
View
Details

articles/Serialization.md
:bulb:Suggestion
View
Details

README.md
:white_check_mark:Succeeded

articles/Object-Detection-using-Faster-R-CNN.md

Line 2, Column 10: [Warning: duplicate-titles - See documentation] Title 'Object  detection using Fast R-CNN - Cognitive Toolkit - CNTK' is duplicated in: 'Object-Detection-using-Faster-R-CNN.md(2,10), Object-Detection-using-Fast-R-CNN.md(2,10), Object-Detection-using-Fast-R-CNN-BrainScript.md(2,10)'. Titles must be unique within a docset.
Line 33, Column 92: [Warning: duplicate-alt-text - See documentation] Alt text 'image' is duplicated. Within an article, alt text must be unique.
Line 34, Column 68: [Warning: duplicate-alt-text - See documentation] Alt text 'image' is duplicated. Within an article, alt text must be unique.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

articles/ReleaseNotes/CNTK_2_0_Release_Notes.md

Line 0, Column 0: [Warning: h1-missing - See documentation] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

articles/ReleaseNotes/CNTK_2_1_Release_Notes.md

Line 0, Column 0: [Warning: h1-missing - See documentation] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

articles/ReleaseNotes/CNTK_2_2_Release_Notes.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

articles/Serialization.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 4, Column 14: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'minxia' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#docutune-ready

@Wee
Please merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval

@Wee @chrisbasoglu @DhurataJ @pkranen @tfosmark @v-sidlamaPlease merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval

@Wee @chrisbasoglu @DhurataJ @pkranen @tfosmark @v-sidlamaPlease merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval

@Wee @chrisbasoglu @DhurataJ @pkranen @tfosmark @v-sidlama
Please merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval

@Wee @chrisbasoglu @DhurataJ @pkranen @tfosmark @v-sidlama
Please merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval

@Wee @chrisbasoglu @DhurataJ @pkranen @tfosmark @v-sidlama
Please merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval


Enable race detector in unit test

Add -race in unit test to enable race detector
Fix a unit test which has race issue

Thanks for your info @antoninbas , I reverted changes out of client_test.go.
But I prefer to change concurrent detect part in the test, I think the new changes are more straight than before. PTAL.

/test-e2e

/test-e2e

/test-e2e

/skip-e2e


Can't unassign removed collaborators

Gitea version (or commit ref): 30560b0

Description
I just removed a collaborator (chris) from a project, but he's still an assignee on a few pull requests, and he can't be removed because he doesn't appear in the dropdown, and clicking Clear assignees does nothing.
Screenshots
The assignees:

The dropdown:

I think assignees shall be automatically be removed when they are not assignable any longer (changed access)

I'll take care of this now


Question regarding method on Image instances

How is the methods.rb file use in this library. I'm currently working on an image processing library and I find it confusing to understand some of the concepts in this library.
So if I try to get all the method from an Image object image = Vips::Image.new_from_file image.path and after I inspect the methods available I get a long list
[:log10,
 :format,
 :write_to_file,
 :rot270,
 :rot180,
 :rot90,
 :rect,
 :polar,
 :real,
 :!,
 :get_fields,
 :new_from_image,
 :copy_memory,
 :%,
 :&,
 :imag,
 :conj,
 :*,
 :+,
 :-,
 :remove,
 :/,
 :floor,
 :ceil,
 :<,
 :>,
 :parent_get_typeof,
 :offset,
 :bands,
 :interpretation,
 :scale,
 :set_type,
 :^,
 :xres,
 :yres,
 :xoffset,
 :yoffset,
 :write_to_buffer,
 :set,
 :get_value,
 :set_value,
 :write_to_memory,
 :coding,
 :|,
 :~,
 :rint,
 :+@,
 :-@,
 :**,
 :bandand,
 :bandeor,
 :<<,
 :>>,
 :<=,
 :>=,
 :==,
 :bandsplit,
 :!=,
 :bandor,
 :getpoint,
 :[],
 :bandjoin,
 :median,
 :cross_phase,
 :maxpos,
 :minpos,
 :exp10,
 :fliphor,
 :flipver,
 :respond_to?,
 :erode,
 :dilate,
 :ifthenelse,
 :scaleimage,
 :inspect,
 :get,
 :method_missing,
 :size,
 :to_a,
 :height,
 :get_typeof,
 :width,
 :cos,
 :sin,
 :tan,
 :acos,
 :asin,
 :atan,
 :exp,
 :log,
 :filename,
 :get_pspec,
 :get_typeof_error,
 :to_ptr,
 :ffi_struct,
 :ffi_managed_struct,
 :stub,
 :pry,
 :__binding__,
 :pretty_print,
 :pretty_print_cycle,
 :pretty_print_instance_variables,
 :pretty_print_inspect,
 :to_json,
 :describe,
 :must_match,
 :must_be_empty,
 :must_equal,
 :must_be_close_to,
 :must_be_within_delta,
 :must_be_within_epsilon,
 :must_include,
 :must_be_instance_of,
 :must_be_kind_of,
 :must_be_nil,
 :must_be,
 :must_output,
 :must_raise,
 :must_respond_to,
 :must_be_same_as,
 :must_be_silent,
 :must_throw,
 :wont_be_empty,
 :wont_equal,
 :wont_be_close_to,
 :wont_be_within_delta,
 :wont_be_within_epsilon,
 :wont_include,
 :wont_be_instance_of,
 :wont_be_kind_of,
 :wont_match,
 :wont_be_nil,
 :wont_be,
 :wont_respond_to,
 :wont_be_same_as,
 :instance_of?,
 :public_send,
 :instance_variable_get,
 :instance_variable_set,
 :instance_variable_defined?,
 :remove_instance_variable,
 :private_methods,
 :kind_of?,
 :instance_variables,
 :tap,
 :pretty_inspect,
 :is_a?,
 :extend,
 :define_singleton_method,
 :to_enum,
 :enum_for,
 :<=>,
 :===,
 :=~,
 :!~,
 :eql?,
 :freeze,
 :display,
 :gem,
 :send,
 :object_id,
 :to_s,
 :method,
 :public_method,
 :singleton_method,
 :nil?,
 :hash,
 :class,
 :singleton_class,
 :clone,
 :dup,
 :itself,
 :taint,
 :tainted?,
 :untaint,
 :untrust,
 :trust,
 :untrusted?,
 :methods,
 :protected_methods,
 :frozen?,
 :public_methods,
 :singleton_methods,
 :__send__,
 :equal?,
 :instance_eval,
 :instance_exec,
 :__id__]

But no method autorot is on the list but I'm able to call it. I found the description here https://github.com/jcupitt/ruby-vips/blob/master/lib/vips/methods.rb#L440 Is there something dynamic loading this method in the Image instance?
Thank you so much for writing this library.

Hello, yes, ruby-vips is a dynamic binding. There is an introduction here with some background:
http://www.rubydoc.info/gems/ruby-vips/Vips
Read from How it works onwards.

Thank you so much @jcupitt


Plugin Randomly becomes unusable.

I legit have no idea what happened to cause this, but As of yesterday and continuing today players cannot use the Vanilla Additions items. I've attached my latest log files.
2018-11-14-3.log.gz
2018-11-15-1.log.gz
2018-11-15-2.log.gz
2018-11-15-3.log.gz
2018-11-14-1.log.gz
2018-11-14-2.log.gz

Turns out this is an issue with Additions API. I will post this there.


formatPrefix will sometimes not perform rounding

For example: d3.formatPrefix(',.2', 1e3)(1555) produces 1.55, should be 1.56.
This is likely a simple fix, but unfortunately I'm not adept enough to figure out the source code and submit a PR, sorry.

I made a local branch to submit a PR but I don't have write access.
The needed change is to formatTypes.js.
"f": (x, p) => (Math.round(x * Number('1e' + p)) / Number('1e' + p)).toFixed(p);
My earlier comment had i instead of p for some reason, oops.


DRAFT feat(Status): Added status component

Status component draft do not merge.

Preview: https://react-component-groups-pr-component-groups-125.surge.sh
A11y report: https://react-component-groups-pr-component-groups-125-a11y.surge.sh


Extract mode for SCSS file, when processUrls is false.

Detailed description
Extract mode for scss file is working when mix.options({ processCssUrls: true }). But it is not working when setting the processCssUrls is false.
Context
Would like to use relative url on my css.
Your environment
Include as many relevant details about the environment you experienced the bug in and how to reproduce it.

Node 14.4.0
Mac OSX 10.11.6

// assets/styles/main.scss
body {
	background-image: url(../sprites/email.svg);
}

// assets/scripts/main.js
/**
 * Requires all directives from subdirectories.
 * @param requireContext
 * @returns {*}
 */
function requireAll(requireContext) {
	return requireContext.keys().map(requireContext);
}

// Require all icons in the sprites folder.
requireAll(require.context('../../sprites', true, /\.svg$/))

// webpack.mix.js
mix
	.options({ processCssUrls: false, })
	.sass('assets/styles/main.scss', 'styles')
	.js('assets/scripts/main.js', 'scripts')
	.svgSprite('assets/sprites', 'sprite.svg')
;

Hi @khaiknievel, thanks for reporting this issue. Can you clarify what you mean with 'it is not working'? What would you expect and what happens instead? Do you have some example output?

Hey, alrights.
The expected css result.
body {
	background-image: url(sprite.svg#email);
}

The actual result.
body {
    background-image: url(../sprites/email.svg);
}

Thanks for the quick reply! Unfortunately that is expected behaviour. Setting processCssUrls to false disables processing of all urls in CSS files. These urls will not be processed by Webpack neither the SVG sprite loader.

processCssUrls: Process/optimize relative stylesheet url()'s. By default, Webpack will automatically update these URLs, when relevant. If, however, your folder structure is already organized the way you want it, set this option to false to disable processing.
https://laravel-mix.com/docs/5.0/options

I see... Dang it. Got you. Thanks. :)

Just gonna leave this here. Ended up using postcss-url. The goal was to use relative url and to be able to use the sprite from css.
yarn add postcss-url --dev
// webpack.mix.js
mix
	.sass('assets/styles/main.scss', 'styles')
	.options({
		processCssUrls: false,
		postCss: [
			require('postcss-url')({
				filter: '**/sprites/*.svg',
				url: (asset) => {
					var file = new File(asset.absolutePath)
					return `../sprite.svg?id=${file.version()}#${file.segments.name}-usage`
				}
			})
		]
	})
	.svgSprite('assets/sprites', 'sprite.svg', { extract: true }, { plainSprite: false })
;

From
body {
	background-image: url(../sprites/email.svg);
}

becomes
body {
	background-image: url(../sprite.svg?id=hash#email-usage);
}

That's an interesting approach! What happens to the hash for different icons? If I read this code correctly, every icon will have a different hash and thus URL causing the browser to download the same sprite several times. Is that correct?
E.g.
body {
    background-image: url(../sprites/email.svg);
}
div {
    background-image: url(../sprites/phone.svg);
}

will become
body {
    background-image: url(../sprite.svg?id=l1c845o5t7#email-usage);
}
div {
    background-image: url(../sprite.svg?id=qfuazwrmq9#phone-usage);
}

Thats correct. Hmm... Kinda defeat the purpose of using a sprite in the first place. Hmm, gonna rethink this through. Dont think I'm able to get the sprite hash anyway.

@khaiknievel I'm trying to use your solution to hash my icon font but I'm stumbling upon this error:
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
ReferenceError: File is not defined

Where did you import the File class from?

@abel-sch Hey, i'm using laravel mix. The File class is an import from laravel-mix/laravel-mix.

Ah thanks, I managed to get it to work.


create  element

From<EMAIL_ADDRESS>on March 19, 2012 17:19:09

Create new <namePart> element that allows division of names into parts.
No longer allow name-like elements (name, persName, corpName, etc.) to nest recursively (via schematron?).

Original issue: http://code.google.com/p/music-encoding/issues/detail?id=56

From<EMAIL_ADDRESS>on June 21, 2012 05:38:32
Labels: -Type-Enhancement -Priority-Medium -Milestone-Release2013 Type-Bug Priority-High Milestone-ReleaseNext

From<EMAIL_ADDRESS>on July 19, 2012 11:41:53
Labels: -Priority-High -Milestone-ReleaseNext Priority-Medium Milestone-Release2013

From<EMAIL_ADDRESS>on July 23, 2012 08:51:50
This issue is too big to tackle right now. There doesn't seem to be a way to restrict the recursive nesting as long as namePart contains phrase-level elements.  Simply adding another element to the name mix is not a good idea right now.
Labels: -Type-Bug Type-Enhancement

From<EMAIL_ADDRESS>on October 11, 2012 16:20:57
Labels: -Priority-Medium Priority-Low

From andrew.hankinson on October 17, 2012 07:52:52
Labels: -Milestone-Release2013 Milestone-ReleaseNext

From<EMAIL_ADDRESS>on May 30, 2014 08:47:28
Labels: -Milestone-ReleaseNext Milestone-ReleaseFuture

Follow TEI practice.  See attached ODD.
nameParts.ODD.txt


Add username field to nodemanager

Connecting to redis 6 using ACL requires the username field to be passed to the core redis connection object.
You get the following exception otherwise:
Traceback (most recent call last):
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/rediscluster/nodemanager.py", line 163, in initialize
    cluster_slots = r.execute_command("cluster", "slots")
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/redis/client.py", line 875, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/redis/connection.py", line 1185, in get_connection
    connection.connect()
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/redis/connection.py", line 561, in connect
    self.on_connect()
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/redis/connection.py", line 637, in on_connect
    auth_response = self.read_response()
  File "/home/gnanesh_r/work/redisinsight/.venv/lib/python3.6/site-packages/redis/connection.py", line 752, in read_response
    raise response
redis.exceptions.ResponseError: AUTH <password> called without any password configured for the default user. Are you sure your configuration is correc
t?

@GnaneshKunal I can't accept this without any added tests to prove it works or at least some code snippet that proves that it first fails w/o your fix, then a proof it do works with your fix. I will not merge this w/o these two things at a minimum.


Regenerate SDK

Fix #301

#291

#291

The fact community PRs don't run the full set of tests before merging is, as always, concerning.


change "code.google.com/p/go.net/websocket" to "golang.org/x/net/websocket"

and since "golang.org/x/" also be redirected to "github.com/golang"...
but I don't want to change the code of golang.org/x/net, tools or tour etc
so, I have to make a symbol-link $GOPATH/golang.org/x  to $GOPATH/github,com/golang

This has already been done.


Ruby Group Capstone Project

Hey there! I hope all is well.
Here is the link to our Project: Ruby Group Capstone
In this case, we are a group of three people.

Team member 1 - Alexandre Medina - @alexmedinasf
Team member 2 - Ruth Abreu - @Ruthmy
Team member 3 - Manuel Sanchez - @Luffytaro22

Thank you very much for your review ✨

Hi :raising_hand: :raising_hand: @Ruthmy @alexmedinasf @Luffytaro22 ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉 🎉
:tada: :champagne:  :tada: :champagne:
Highlights :green_circle:

Tasks are equally distributed fairly to each team member :rocket:

Optional suggestions
N/A
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


WIP: STOR-1767: Debug e2e-vsphere test

This PR is only to debug test failures for https://github.com/openshift/vmware-vsphere-csi-driver-operator/pull/233 . Do not merge!

/retest-required

/retest-required

/retest-required

/retest-required