fingerprint mismatch

Hi,
when I ran the resnet50 , and I got fingerprint mismatch error.
W0110 11:13:48.316934  1383 dpu_runner_base_imp.cpp:692] CHECK fingerprint fail ! model_fingerprint 0x1000020f6014407 dpu_fingerprint 0x1000000f6014407
F0110 11:13:48.317059  1383 dpu_runner_base_imp.cpp:664] fingerprint check failure.

I have checked the generated arch json which is "0x1000020f6014407 ", but I don't know why the fingerprint was changed to "0x1000000f6014407" when I ran xmodel on the board.
Is the fingerprint got from dpu.xclbin?

Hi @hill19850213
Yes.
0x1000020f6014407 stands for "DPUCZDX8G_ISA0_B4096_MAX_BG2".  The model's fingerprint should be the same with the target's fingerprint. Otherwise, you can't run the model on the target.
You can use the following command to check the target's information, including fingerprint.
/usr/bin/xlnx/xilinx_show_devices

Hi @hill19850213
Yes.
0x1000020f6014407 stands for "DPUCZDX8G_ISA0_B4096_MAX_BG2".  The model's fingerprint should be the same with the target's fingerprint. Otherwise, you can't run the model on the target.
You can use the following command to check the target's information, including fingerprint.
/usr/bin/xlnx/xilinx_show_devices

Hi @qianglin-xlnx ,
How to view the xilinx_show_devices?
Thanks
Sitting

Hi @qianglin-xlnx ,
How to view the xilinx_show_devices?
Thanks
Sitting

Hi @qianglin-xlnx ,
When I ran the xilinx_show_devices, there is an error as below:
root@xilinx-zu6eg-2020_2:/usr/bin/xlnx# ./xilinx_show_devices
[   74.611394] [drm] Pid 1246 opened device
[   74.615344] [drm] Pid 1246 closed device
[   74.619403] [drm] Pid 1246 opened device
[   74.623326] [drm] Pid 1246 closed device
[   74.627483] [drm] Pid 1246 opened device
[   74.632300] [drm] Pid 1246 closed device
[   74.684687] [drm] Pid 1246 opened device
[   74.688626] [drm] Pid 1246 closed device
[   74.692623] [drm] Pid 1246 opened device
[   74.701829] [drm] sched_reset_exec: stop scheduler
[   74.701889] [drm] get section DEBUG_IP_LAYOUT err: -22
[   74.706682] [drm] get section AIE_METADATA err: -22
[   74.711980] [drm] zocl_xclbin_read_axlf ae58ff81-475e-4c58-adc0-4d1bae03ca45 ret: 0
[   74.721902] [drm] bitstream ae58ff81-475e-4c58-adc0-4d1bae03ca45 locked, ref=1
[   74.729577] [drm] No ERT scheduler on MPSoC, using KDS
[   74.741946] Internal error: synchronous external abort: 96000010 [#1] SMP
[   74.748719] Modules linked in: iptable_nat nf_nat iptable_filter dmaproxy(O) dpu(O) mali(O) zocl(    O)
[   74.757766] CPU: 3 PID: 406 Comm: zocl-scheduler- Tainted: G           O      5.4.0-xilinx-v2020.    2 #1
[   74.766971] Hardware name: ZynqMP ZCU104 RevC (DT)
[   74.771748] pstate: 40000005 (nZcv daif -PAN -UAO)
[   74.776533] pc : zocl_cu_init+0xbc/0x278 [zocl]
[   74.781058] lr : zocl_cu_init+0xb8/0x278 [zocl]
[   74.785572] sp : ffff800012fbbb80
[   74.788871] x29: ffff800012fbbb80 x28: ffff0009735d5080
[   74.794165] x27:<PHONE_NUMBER>000000 x26: 00000000a0020000
[   74.799460] x25:<PHONE_NUMBER>000048 x24:<PHONE_NUMBER>000001
[   74.804755] x23:<PHONE_NUMBER>000000 x22: ffff800011815000
[   74.810050] x21: 00000000a0020000 x20:<PHONE_NUMBER>000001
[   74.815345] x19: ffff800011806000 x18: ffff800011203df8
[   74.820639] x17:<PHONE_NUMBER>000000 x16:<PHONE_NUMBER>000000
[   74.825934] x15: 00000000a0020000 x14: ffff000971c6de00
[   74.831229] x13: ffff800011e75000 x12: ffff000971338e80
[   74.836524] x11: ffff800011e41000 x10: ffff800011424a74
[   74.841819] x9 : ffff8000114023e0 x8 : ffff00096fe2ea80
[   74.847113] x7 :<PHONE_NUMBER>000000 x6 :<PHONE_NUMBER>000001
[   74.852408] x5 : ffff000971c54bd0 x4 :<PHONE_NUMBER>010000
[   74.857703] x3 : ffff800011e30000 x2 : 00000000a0020000
[   74.862998] x1 : ffff800011e30000 x0 :<PHONE_NUMBER>000000
[   74.868293] Call trace:
[   74.870732]  zocl_cu_init+0xbc/0x278 [zocl]
[   74.874906]  configure.isra.0+0x374/0x8f0 [zocl]
[   74.879515]  scheduler+0x87c/0xc88 [zocl]
[   74.883514]  kthread+0x12c/0x130
[   74.886732]  ret_from_fork+0x10/0x1c
[   74.890293] Code: f0000041 9127e021 95e3cfe3 f94006c1 (b9400021)
[   74.896375] ---[ end trace 9c2914902fa9a9d7 ]---

Hi @qianglin-xlnx ,
When I ran the xilinx_show_devices, there is an error as below:
root@xilinx-zu6eg-2020_2:/usr/bin/xlnx# ./xilinx_show_devices
[   74.611394] [drm] Pid 1246 opened device
[   74.615344] [drm] Pid 1246 closed device
[   74.619403] [drm] Pid 1246 opened device
[   74.623326] [drm] Pid 1246 closed device
[   74.627483] [drm] Pid 1246 opened device
[   74.632300] [drm] Pid 1246 closed device
[   74.684687] [drm] Pid 1246 opened device
[   74.688626] [drm] Pid 1246 closed device
[   74.692623] [drm] Pid 1246 opened device
[   74.701829] [drm] sched_reset_exec: stop scheduler
[   74.701889] [drm] get section DEBUG_IP_LAYOUT err: -22
[   74.706682] [drm] get section AIE_METADATA err: -22
[   74.711980] [drm] zocl_xclbin_read_axlf ae58ff81-475e-4c58-adc0-4d1bae03ca45 ret: 0
[   74.721902] [drm] bitstream ae58ff81-475e-4c58-adc0-4d1bae03ca45 locked, ref=1
[   74.729577] [drm] No ERT scheduler on MPSoC, using KDS
[   74.741946] Internal error: synchronous external abort: 96000010 [#1] SMP
[   74.748719] Modules linked in: iptable_nat nf_nat iptable_filter dmaproxy(O) dpu(O) mali(O) zocl(    O)
[   74.757766] CPU: 3 PID: 406 Comm: zocl-scheduler- Tainted: G           O      5.4.0-xilinx-v2020.    2 #1
[   74.766971] Hardware name: ZynqMP ZCU104 RevC (DT)
[   74.771748] pstate: 40000005 (nZcv daif -PAN -UAO)
[   74.776533] pc : zocl_cu_init+0xbc/0x278 [zocl]
[   74.781058] lr : zocl_cu_init+0xb8/0x278 [zocl]
[   74.785572] sp : ffff800012fbbb80
[   74.788871] x29: ffff800012fbbb80 x28: ffff0009735d5080
[   74.794165] x27:<PHONE_NUMBER>000000 x26: 00000000a0020000
[   74.799460] x25:<PHONE_NUMBER>000048 x24:<PHONE_NUMBER>000001
[   74.804755] x23:<PHONE_NUMBER>000000 x22: ffff800011815000
[   74.810050] x21: 00000000a0020000 x20:<PHONE_NUMBER>000001
[   74.815345] x19: ffff800011806000 x18: ffff800011203df8
[   74.820639] x17:<PHONE_NUMBER>000000 x16:<PHONE_NUMBER>000000
[   74.825934] x15: 00000000a0020000 x14: ffff000971c6de00
[   74.831229] x13: ffff800011e75000 x12: ffff000971338e80
[   74.836524] x11: ffff800011e41000 x10: ffff800011424a74
[   74.841819] x9 : ffff8000114023e0 x8 : ffff00096fe2ea80
[   74.847113] x7 :<PHONE_NUMBER>000000 x6 :<PHONE_NUMBER>000001
[   74.852408] x5 : ffff000971c54bd0 x4 :<PHONE_NUMBER>010000
[   74.857703] x3 : ffff800011e30000 x2 : 00000000a0020000
[   74.862998] x1 : ffff800011e30000 x0 :<PHONE_NUMBER>000000
[   74.868293] Call trace:
[   74.870732]  zocl_cu_init+0xbc/0x278 [zocl]
[   74.874906]  configure.isra.0+0x374/0x8f0 [zocl]
[   74.879515]  scheduler+0x87c/0xc88 [zocl]
[   74.883514]  kthread+0x12c/0x130
[   74.886732]  ret_from_fork+0x10/0x1c
[   74.890293] Code: f0000041 9127e021 95e3cfe3 f94006c1 (b9400021)
[   74.896375] ---[ end trace 9c2914902fa9a9d7 ]---

Hi @qianglin-xlnx
I solved this issue. Thanks you

Hi @qianglin-xlnx
I solved this issue. Thanks you

Facing same error..How do you solve it ?I have checked the generated arch json which is "0x1000020f6014407 ", but I don't know why the fingerprint was changed to "0x1000000f6014407" when I ran xmodel on the board.

you can replace xclbin file，than try again！

you can replace xclbin file， later try again！

you can replace xclbin file， later try again！

Faced this:
root@versal-rootfs-common-2021_2:~/demo/VART/resnet50# ./resnet50 resnet50.xmodel                            WARNING: Logging before InitGoogleLogging() is written to STDERR
I0421 07:35:39.625972   746 main.cc:292] create running for subgraph: subgraph_conv1
XAIEFAL: INFO: Resource group Avail is created.
XAIEFAL: INFO: Resource group Static is created.
XAIEFAL: INFO: Resource group Generic is created.
W0421 07:35:48.376049   746 dpu_runner_base_imp.cpp:676] CHECK fingerprint fail ! model_fingerprint 0x602001036088231 dpu_fingerprint 0x602001036088252
F0421 07:35:48.376101   746 dpu_runner_base_imp.cpp:648] fingerprint check failure.
*** Check failure stack trace: ***
Aborted
How to change fingerprint on target
root@versal-rootfs-common-2021_2:/usr/bin/xlnx# ./xilinx_show_devices
-sh: ./xilinx_show_devices: No such file or directory

Hi @AfifaIshtiaq
You need to recompile your model according to your target's bit fingerprint.
If you want to change the target's bit fingerprint, you need to config the dpu design and integrate it. Then, recompile your model according to your new target's bit fingerprint.

Hi @qianglin-xlnx Thanks for quick response I downloaded model from
wget https://www.xilinx.com/bin/public/openDownload?filename=resnet50-vck190-r2.0.0.tar.gz -O resnet50-vck190-r2.0.0.tar.gz but I am having issue in recompiling the xmodel.
How can I change fingerprint in  /opt/vitis_ai/compiler/arch/ folder.

Hi @AfifaIshtiaq
The model you download is the compiled xmodel. You need to download the quantized model in : https://www.xilinx.com/bin/public/openDownload?filename=cf_resnet50_imagenet_224_224_7.7G_2.0.zip
find the quantized model under "cf_resnet50_imagenet_224_224_7.7G_2.0/quantized" folder. Then compile it in Vitis-AI docker.
vai_c_caffe

Vitis-AI /opt/vitis_ai/compiler/arch/DPUCVDX8G/VCK190 > ls
arch_edit.json  arch.json
how to edit the fingerprint in this json file with my DPU finger print as this .json is protected?
root@versal-rootfs-common-2021_2:~#  xdputil query
XAIEFAL: INFO: Resource group Avail is created.
XAIEFAL: INFO: Resource group Static is created.
XAIEFAL: INFO: Resource group Generic is created.
{
"DPU IP Spec":{
"DPU Core Count":1,
"DPU Target Version":"v1.4.1",
"IP version":"v1.1.0",
"generation timestamp":"2022-04-19 15-45-00",
"git commit id":"ae7356b",
"git commit time":2112061226,
"regmap":"1toN version"
},
"VAI Version":{
"libvart-runner.so":"Xilinx vart-runner Version: 2.0.0-c34b0446ca2c0a49345bf041d996eabf612b8614 64 2022-01-13-21:42:10 ",
"libvitis_ai_library-dpu_task.so":"Xilinx vitis_ai_library dpu_task Version: 2.0.0-887576f58e2c191c1abb75c757af12f37fa1571e 64 2022-01-13 13:46:11 [UTC] ",
"libxir.so":"Xilinx xir Version: xir-9120e08ab9769fc285c8a2b8c0856232de0627c2 2022-01-13-21:40:30",
"target_factory":"target-factory.2.0.0 0228accac8740ee81bd172a487c61a04273f5ab1"
},
"kernels":[
{
"DPU Arch":"DPUCVDX8G_ISA2_C64B5_0602001036088252",
"DPU Batch Number":5,
"DPU Frequency (MHz)":333,
"IP Type":"DPU",
"Load Parallel":7,
"Load augmentation":"enable",
"Load minus mean":"disable",
"Save Parallel":2,
"XRT Frequency (MHz)":150,
"cu_addr":"0xa4050000",
"cu_handle":"0xaaab15183080",
"cu_idx":0,
"cu_mask":1,
"cu_name":"DPUCVDX8G:DPUCVDX8G_1",
"device_id":0,
"fingerprint":"0x602001036088252",
"name":"DPU Core 0"
}
]
}

please use: sudo chmod 777 filename.jason
then use: vim filename.json to edit file
At 2022-04-21 16:16:49, "AfifaIshtiaq" @.***> wrote:
Vitis-AI /opt/vitis_ai/compiler/arch/DPUCVDX8G/VCK190 > ls
arch_edit.json arch.json
how to edit the fingerprint in this json file with my DPU finger print as this .json is protected?
@.***_2:~# xdputil query
XAIEFAL: INFO: Resource group Avail is created.
XAIEFAL: INFO: Resource group Static is created.
XAIEFAL: INFO: Resource group Generic is created.
{
"DPU IP Spec":{
"DPU Core Count":1,
"DPU Target Version":"v1.4.1",
"IP version":"v1.1.0",
"generation timestamp":"2022-04-19 15-45-00",
"git commit id":"ae7356b",
"git commit time":2112061226,
"regmap":"1toN version"
},
"VAI Version":{
"libvart-runner.so":"Xilinx vart-runner Version: 2.0.0-c34b0446ca2c0a49345bf041d996eabf612b8614 64 2022-01-13-21:42:10 ",
"libvitis_ai_library-dpu_task.so":"Xilinx vitis_ai_library dpu_task Version: 2.0.0-887576f58e2c191c1abb75c757af12f37fa1571e 64 2022-01-13 13:46:11 [UTC] ",
"libxir.so":"Xilinx xir Version: xir-9120e08ab9769fc285c8a2b8c0856232de0627c2 2022-01-13-21:40:30",
"target_factory":"target-factory.2.0.0 0228accac8740ee81bd172a487c61a04273f5ab1"
},
"kernels":[
{
"DPU Arch":"DPUCVDX8G_ISA2_C64B5_0602001036088252",
"DPU Batch Number":5,
"DPU Frequency (MHz)":333,
"IP Type":"DPU",
"Load Parallel":7,
"Load augmentation":"enable",
"Load minus mean":"disable",
"Save Parallel":2,
"XRT Frequency (MHz)":150,
"cu_addr":"0xa4050000",
"cu_handle":"0xaaab15183080",
"cu_idx":0,
"cu_mask":1,
"cu_name":"DPUCVDX8G:DPUCVDX8G_1",
"device_id":0,
"fingerprint":"0x602001036088252",
"name":"DPU Core 0"
}
]
}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

I have to replace the target in json file of docker with one mentioned on
target as DPu_arch is it right?
In docker i read json file as
{
Target: DPUCVX8G_ISA2_C32B3
}
On versal board
DPU Arch":"DPUCVDX8G_ISA2_C64B5_0602001036088252"
On Thu 21. Apr 2022 at 10:51, aiqiangbrave @.***> wrote:

please use: sudo chmod 777 filename.jason
then use: vim filename.json to edit file
At 2022-04-21 16:16:49, "AfifaIshtiaq" @.***> wrote:
Vitis-AI /opt/vitis_ai/compiler/arch/DPUCVDX8G/VCK190 > ls
arch_edit.json arch.json
how to edit the fingerprint in this json file with my DPU finger print as
this .json is protected?
@.***_2:~# xdputil query
XAIEFAL: INFO: Resource group Avail is created.
XAIEFAL: INFO: Resource group Static is created.
XAIEFAL: INFO: Resource group Generic is created.
{
"DPU IP Spec":{
"DPU Core Count":1,
"DPU Target Version":"v1.4.1",
"IP version":"v1.1.0",
"generation timestamp":"2022-04-19 15-45-00",
"git commit id":"ae7356b",
"git commit time":2112061226,
"regmap":"1toN version"
},
"VAI Version":{
"libvart-runner.so":"Xilinx vart-runner Version:
2.0.0-c34b0446ca2c0a49345bf041d996eabf612b8614 64 2022-01-13-21:42:10 ",
"libvitis_ai_library-dpu_task.so":"Xilinx vitis_ai_library dpu_task
Version: 2.0.0-887576f58e2c191c1abb75c757af12f37fa1571e 64 2022-01-13
13:46:11 [UTC] ",
"libxir.so":"Xilinx xir Version:
xir-9120e08ab9769fc285c8a2b8c0856232de0627c2 2022-01-13-21:40:30",
"target_factory":"target-factory.2.0.0
0228accac8740ee81bd172a487c61a04273f5ab1"
},
"kernels":[
{
"DPU Arch":"DPUCVDX8G_ISA2_C64B5_0602001036088252",
"DPU Batch Number":5,
"DPU Frequency (MHz)":333,
"IP Type":"DPU",
"Load Parallel":7,
"Load augmentation":"enable",
"Load minus mean":"disable",
"Save Parallel":2,
"XRT Frequency (MHz)":150,
"cu_addr":"0xa4050000",
"cu_handle":"0xaaab15183080",
"cu_idx":0,
"cu_mask":1,
"cu_name":"DPUCVDX8G:DPUCVDX8G_1",
"device_id":0,
"fingerprint":"0x602001036088252",
"name":"DPU Core 0"
}
]
}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/Xilinx/Vitis-AI/issues/263#issuecomment-1104896618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIQY4SVDT547ZRM6SXABS3VGEJHBANCNFSM4WIQGVIA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,
I also have problem with model fingerprint.
The DPU fingerprint is: "0x101000016010407".
So, I compile pytorch model facerec_resnet20 (downloaded from model_zoo) with arch.json { "fingerprint":"0x101000016010407"}.
Compile cmd:
vai_c_xir -x quantized/Resnet_int.xmodel -a arch.json -o facerec_pretrained_resnet20 -n facerec_pretrained_resnet20
But, when I ran this .xmodel, I get the error:
dpu_runner_base_imp.cpp:676] CHECK fingerprint fail ! model_fingerprint 0x1000020f6014407 dpu_fingerprint 0x101000016010407
F1130 12:58:53.213528  1400 dpu_runner_base_imp.cpp:648] fingerprint check failure.

So, the question is why model_fingeprint is 0x1000020f6014407 instead 0x101000016010407?
My environment:
Docker Image Version: <IP_ADDRESS>0   (GPU) (tried and CPU version as well)
Vitis AI Git Hash: c80e859e3
Build Date: 2022-09-02
OS: Petalinux 2022.1, ZCU104, custom board image
root@zcu104_custom_plnx:/mnt# xdputil query {     "DPU IP Spec":{         "DPU Core Count":1,         "IP version":"v4.0.0",         "enable softmax":"False"     },     "VAI Version":{         "libvart-runner.so":"Xilinx vart-runner Version: 2.5.0-c26eae36f034d5a2f9b2a7bfe816b8c43311a4f8  2022-11-23-17:44:35 ",         "libvitis_ai_library-dpu_task.so":"Xilinx vitis_ai_library dpu_task Version: 2.5.0-c26eae36f034d5a2f9b2a7bfe816b8c43311a4f8  2022-06-15 07:33:00 [UTC] ",         "libxir.so":"Xilinx xir Version: xir-c26eae36f034d5a2f9b2a7bfe816b8c43311a4f8 2022-11-23-17:08:58",         "target_factory":"target-factory.2.5.0 c26eae36f034d5a2f9b2a7bfe816b8c43311a4f8"     },     "kernels":[         {             "DPU Arch":"DPUCZDX8G_ISA1_B4096",             "DPU Frequency (MHz)":200,             "cu_idx":0,             "fingerprint":"0x101000016010407",             "is_vivado_flow":true,             "name":"DPU Core 0"         }     ] }
Thanks!

you can replace xclbin file， later try again！

The fingerprint of the board does not match that of the DPU model，replace it with the same

Hi,
I solved this issue few days ago with the correct fingerprint.
Thanks!

congratulations~
| |
ln
|
---- Replied Message ----
| From | @.> |
| Date | 12/14/2022 21:09 |
| To | @.> |
| Cc |<EMAIL_ADDRESS>|
| Subject | Re: [Xilinx/Vitis-AI] fingerprint mismatch (#263) |
Hi,
I solved this issue few days ago with the correct fingerprint.
Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Okay, so where to replace the fingerprint seems unclear from the foregoing exchanges. I see this error when running:
WARNING: Logging before InitGoogleLogging() is written to STDERR
W1119 17:22:09.076498   855 dpu_runner_base_imp.cpp:733] CHECK fingerprint fail! model_fingerprint 0x101000016010407 is un-matched with actual dpu_fingerprint 0x101000056010407. Please re-compile xmodel with dpu_fingerprint 0x101000056010407 and try again.
F1119 17:22:09.076589   855 dpu_runner_base_imp.cpp:695] fingerprint check failure.
*** Check failure stack trace: ***

I look in /opt/vitis_ai/compiler/arch/DPUCZDX8G/ZCU102/arch.json and see:
{
    "target": "DPUCZDX8G_ISA1_B4096"
}

There is no hint of a fingerprint there.
Then, on zcu102 board:
root@xilinx-zcu102-20222:/run/media/mmcblk0p1/target_zcu102#  xdputil query
WARNING: Logging before InitGoogleLogging() is written to STDERR
E1119 17:27:11.488224   871 xdputil_query.cpp:196] Unsupported platform fingerprint: 0, cu_idx: 3
{
    "DPU IP Spec":{
        "DPU Core Count":4,
        "IP version":"v4.1.0",
        "generation timestamp":"2022-12-06 16-30-00",
        "git commit id":"8a36f42",
        "git commit time":2022120616,
        "regmap":"1to1 version"
    },
    "VAI Version":{
        "libvaip-core.so":"Xilinx vaip Version: 1.0.0-a176db67b19f94b0a31f9d24ef80322efe4494ad  2022-12-26-14:51:25 ",
        "libvart-runner.so":"Xilinx vart-runner Version: 3.0.0-2efa5fe1e56c2b2c8a7e71e9fc1636242dd50a9f  2022-12-26-14:29:49 ",
        "libvitis_ai_library-dpu_task.so":"Xilinx vitis_ai_library dpu_task Version: 3.0.0-1cccff04dc341c4a6287226828f90aed56005f4f  20 22-12-20 10:29:01 [UTC] ",
        "libxir.so":"Xilinx xir Version: xir-9204ac72103092a7b253a0c23ec7471481656940 2022-12-26-14:21:57",
        "target_factory":"target-factory.3.0.0 860ed0499ab009084e2df3004eeb9ae710c26351"
    },
    "kernels":[
        {
            "DPU Arch":"DPUCZDX8G_ISA1_B4096",
            "DPU Frequency (MHz)":300,
            "IP Type":"DPU",
            "Load Parallel":2,
            "Load augmentation":"enable",
            "Load minus mean":"disable",
            "Save Parallel":2,
            "XRT Frequency (MHz)":300,
            "cu_addr":"0x80000000",
            "cu_handle":"0xaaaad3cd9170",
            "cu_idx":0,
            "cu_mask":2,
            "cu_name":"DPUCZDX8G:DPUCZDX8G_1",
            "device_id":0,
            "fingerprint":"0x101000056010407",
            "name":"DPU Core 0"
        },
...

So I can see "fingerprint":"0x101000056010407" but where in arch.json should this go before recompiling the model?
Thanks.

Your technique is not wrong, however there remains a conflict.
You can see that the model was compiled using Vitis AI 2.5 by comparing the Fingerprint found here:  https://github.com/Xilinx/Vitis-AI/blob/2.5/src/Vitis-AI-Runtime/VART/target_factory/targets/DPUCZDX8G_ISA1_B4096.prototxt
By contrast, it appears that the board image that you are targeting has a newer version of the DPU IP (Vitis AI 3.0):
https://github.com/Xilinx/Vitis-AI/blob/3.0/src/vai_runtime/target_factory/targets/DPUCZDX8G_ISA1_B4096.prototxt
Ideally, you should be compiling your model using Vitis AI 3.0 given the version of the DPU that is running on the target.  The differences are slight, and you might get away with disabling the Fingerprint check, but for the moment I cannot find the documented method to do that.
https://xilinx.github.io/Vitis-AI/3.5/html/docs/reference/version_compatibility.html#all-releases
https://support.xilinx.com/s/article/DPU-fingerprint-ERROR?language=en_US

Thanks @quentonh.
I confirm that my Vitis-AI docker image version is V2.5 (Docker Image Version: <IP_ADDRESS>0) and my zcu102 OS image is v3.0 (xilinx-zcu102-dpu-v2022.2-v3.0.0.img) via https://www.xilinx.com/member/forms/download/design-license-xef.html?filename=xilinx-zcu102-dpu-v2022.2-v3.0.0.img.gz
So, one approach is to use to use a xilinx-zcu102-dpu image that's V2.5. I can't see a full list of such images. Do you have a pointer to a list?
The other approach is to install a different docker (V3.0).
I may try both although flashing a new SD card with a V2.5 image may be faster.


GSLUX-659: Display attributions

JIRA issue
https://jira.camptocamp.com/browse/GSLUX-659
Description

[x] Enable attributions on map

Thanks, @AlitaBernachot! Works as expected, just left a comment regarding CSS organization. An e2e test could also be nice, but not mandatory. I'll let you decide.

Thx for the review! I have added some e2e testing.


Update Docs to Show How to Push to Production

Document how to work off production.

@benschac Thanks for the issue and PR. I'm conflicted on whether to include this mostly because the changes to production are rare and I wouldn't want to cause more confusion for a new contributor. What do others think? cc @freeCodeCamp/moderators

I would suggest it is an edge case and will not be required when staging is merged into master

Could we label it as something along the lines of Legacy work?
On Tue, Aug 29, 2017 at 10:27 AM, Stuart Taylor<EMAIL_ADDRESS>wrote:

I would suggest it is an edge case and will not be required when staging
is merged into master
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-325680066,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYxI-kzdzdOsfsSmlLkeLNCKhoE-c5hks5sdB_TgaJpZM4PD-ig
.

While it's one off there are still requests for this work and we should
have documentation for it while we still need it.  Warning signs could also
work too :D
On Tue, Aug 29, 2017 at 10:28 AM, Benjamin Schachter<EMAIL_ADDRESS>wrote:

Could we label it as something along the lines of Legacy work?
On Tue, Aug 29, 2017 at 10:27 AM, Stuart Taylor<EMAIL_ADDRESS>wrote:

I would suggest it is an edge case and will not be required when staging
is merged into master
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-325680066,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYxI-kzdzdOsfsSmlLkeLNCKhoE-c5hks5sdB_TgaJpZM4PD-ig
.

I am not sure about that one.  when we release the beta to production. backup/master will be "gone". we will not work on that branch after beta released.
more like we have to use example branch. so we don't have to change it again.   for showing them how to use checkout track on another branch. or something.

Thanks for the issue @benschac! More documentation is often good, but I think there are a couple issues with this:

A lot of people reading this guide already are at the edge of their abilities trying to understand what's going on. Adding this without clear instructions not to do this unless it's explicitly mentioned will cause confusion.
Because of the massive differences between dependencies and workflow, a lot more needs to happen than switching the branch. As far as I'm aware, most contributors who need to get an instance of the backup/staging running branch clone it into a new folder and follow the CONTRIBUTING.md of that branch to install and run everything.

I'm not sure if there is a good way to document this.

FWIW, I am inclined to understand what the potential issues especially new contributors and/or occasional contributors should be facing. I have commented on this earlier, faced this while helping potential contributors in chat and even answered on the forum for a question on split versions of the codebase.
But, what @benschac has pointed is correct.
I suggest let's rather have this as a wiki guide on the forum and link to it from the contributing guide at the very top with a warning about the staging vs production (master). just like you would see at times on a Wikipedia article, going through a change frequently
We could then remove the warning when needed.

I'll update my PR after work. Thnx.
On Wed, Aug 30, 2017 at 11:47 AM, mrugesh mohapatra <
<EMAIL_ADDRESS>wrote:

FWIW, I am inclined to understand what the potential issues especially new
contributors and/or occasional contributors should be facing. I have
commented on this earlier, faced this while helping potential contributors
in chat and even answered on the forum for a question on split versions of
the codebase.
But, what @benschac https://github.com/benschac has pointed is correct.
I suggest let's rather have this as a wiki guide on the forum and link to
it from the contributing guide at the very top with a warning about the
staging vs production (master). just like you would see at times on a
Wikipedia article, going through a change frequently
We could then remove the warning when needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-326030922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYxIyyMmNDorBvvDPcLESVDCp5dNe9Lks5sdYP_gaJpZM4PD-ig
.

@benschac Ping! 🔔 No hurry, just making sure you didn't forget about this 🙂

Hey,
Sorry for the late response! I've been moving and I have some work stuff.
I'll totally get to this soon. Thanks for the ping. :D.
On Sat, Sep 2, 2017 at 2:40 PM, Timo<EMAIL_ADDRESS>wrote:

@benschac https://github.com/benschac Ping! 🔔 No hurry, just making
sure you didn't forget about this 🙂
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-326762333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYxI2VjrG9ZRBLufKoQdDPgkcki-qBaks5seaEGgaJpZM4PD-ig
.

I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (111/100 (111%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-04.elitehosts.com ([<IP_ADDRESS>]:39157)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1fPUOk-0006Lf-Tu
for<EMAIL_ADDRESS>Sun, 03 Jun 2018 10:54:22 -0400
Received: from out-10.smtp.github.com ([<IP_ADDRESS>])
by mailin-04.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1fPUOK-0006Hk-6Z
for<EMAIL_ADDRESS>Sun, 03 Jun 2018 10:53:56 -0400
Date: Sun, 03 Jun 2018 07:53:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1528037634;
bh=AG81nfO8ZUUhsX0JVzcoWDzsiofvoxXCHWNKahhhxlo=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=rvTFGh6LEGvDlmPD5uRjtoexxd6amQThZxL6wcVVpcAh9PODvuTsRIhBDZXvtbcrC
O+r8YwHtjHtNXHEIchzbsi1IkON4KxyXxus1MMVUNi/XjZqvGc7xLaRpEzfQpvGIMv
9IaykmaEQxT3yXgFOMiGGLxvy59PbQbwCI/0Hfy4=
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Update Docs to Show How to Push to
Production (#15812)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5b1401026e063_48452b257ccbef5429203c";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCrkP3XYLDae1Pfzzg_s3q0CtDi5Lks5t4_iCgaJpZM4PD-ig
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-MAILIN-04-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-04-MailScanner-ID: 1fPUOK-0006Hk-6Z
X-MAILIN-04-MailScanner: Found to be clean
X-MAILIN-04-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-4.659, required 10, autolearn=not spam, AWL 1.74,
BAYES_00 -1.90, HTML_IMAGE_ONLY_32 0.00, HTML_MESSAGE 0.00,
KHOP_THREADED -1.50, RP_MATCHES_RCVD -3.00, SPF_PASS -0.00,
URIBL_BLOCKED 0.00)
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_5b1401026e063_48452b257ccbef5429203c
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #15812.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#event-1660031592
----==_mimepart_5b1401026e063_48452b257ccbef5429203c
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #15812.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#event-1660031592","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#event-1660031592","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Closed #15812."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#event-1660031592"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "Re: [freeCodeCamp/freeCodeCamp] Update Docs to Show How to Push to Production (#15812)",
"sections": [
{
"text": "",
"activityTitle": "**Quincy Larson**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@QuincyLarson",
"facts": [
]
}
],
"potentialAction": [
{
"targets": [
{
"os": "default",
"uri": "https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#event-1660031592"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 252700832\n}"
}
],
"themeColor": "26292E"
}
----==_mimepart_5b1401026e063_48452b257ccbef5429203c--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (113/100 (112%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-04.elitehosts.com ([<IP_ADDRESS>]:39629)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1fPUPj-000761-Kh
for<EMAIL_ADDRESS>Sun, 03 Jun 2018 10:55:23 -0400
Received: from out-4.smtp.github.com ([<IP_ADDRESS>])
by mailin-04.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1fPUOG-0006Hh-9m
for<EMAIL_ADDRESS>Sun, 03 Jun 2018 10:53:52 -0400
Date: Sun, 03 Jun 2018 07:53:50 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1528037630;
bh=ahkzeu+8haFyGEPrs4XLi+Zcfkej8rngsmBbdkAdb9E=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=Ts1AkUrIJMk7ZBtAC6lSKiEhbPNs5i41xfHKe6rM3kALrV02UaRSsVDAs8PuFoIPW
g8WFEeVfsdvr2hjGJUhkSOl2bN+Ajf50SdDllgFfotfu2xyVbBlNRwWhzY3YsU6heO
n/mXt3npO8mzI9KEIY/Lb3pferiyu68SNFbEke9I=
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Update Docs to Show How to Push to
Production (#15812)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5b1400fe72fac_2a7d2b0d80a7cf5c315724";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCognfEVA2tkpwqlCKTNAaZVcG-kXks5t4_h-gaJpZM4PD-ig
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-MAILIN-04-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-04-MailScanner-ID: 1fPUOG-0006Hh-9m
X-MAILIN-04-MailScanner: Found to be clean
X-MAILIN-04-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-4.66, required 10, autolearn=not spam, AWL 1.74,
BAYES_00 -1.90, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
RP_MATCHES_RCVD -3.00, SPF_PASS -0.00, URIBL_BLOCKED 0.00)
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_5b1400fe72fac_2a7d2b0d80a7cf5c315724
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-394167665
----==_mimepart_5b1400fe72fac_2a7d2b0d80a7cf5c315724
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-394167665","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-394167665","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@QuincyLarson in #15812: I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-394167665"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "Re: [freeCodeCamp/freeCodeCamp] Update Docs to Show How to Push to Production (#15812)",
"sections": [
{
"text": "",
"activityTitle": "**Quincy Larson**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@QuincyLarson",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "freeCodeCamp/freeCodeCamp",\n"issueId": 15812,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/freeCodeCamp/freeCodeCamp/issues/15812#issuecomment-394167665"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 252700832\n}"
}
],
"themeColor": "26292E"
}
----==_mimepart_5b1400fe72fac_2a7d2b0d80a7cf5c315724--


Custom response tag for chaining requests

What is your question?
I would like to use request chaining, but I need to do some preprocessing on the response data before I can use it in the next request. Can I write a custom response tag (I would want it to function just like the built in response tag, except do some custom processing)? Or can a custom tag access data from a previous response like the response tag does? If so can you give me an example of how this is done?
Right now the only apparent way around this is to store intermediate data in env variables. Is this the best way for custom tags to get request data?

I suggest taking a look at the Response Eval plugin. It is a fork of the existing Response tag that adds the ability to execute arbitrary JS on the response. You could possibly make use of that or look at it as a starting point for your own plugin.


Define tableName() in ActiveRecordHistory

Define tableName() in ActiveRecordHistory for possibility to use it as relation.

It's not correct because:

ActiveRecordHistory is extend the class ActiveRecord and it's abstract class for an implementation AR-model.
Usage the ActiveRecordHistory is old method for use this extension and not supported after version 1.1.0.

Thanks for feedback!


Upgrade to Bootstrap 3.3.5

Happy to merge it and to release a new version but I'm not maintaining it anymore. If you want you can release a new package and I can add a notice to redirect to your repo/package.

I don't have much interest in taking over maintenance - I just wanted this particular update.  I'd appreciate it if you would merge and release a new version.

Cool thank you for your answer I'll do a release in a couple of hours

Updated under 1.0.0

$ pip install --ignore-installed django-bootstrap-sass==1.0.0
Collecting django-bootstrap-sass==1.0.0
  Could not find a version that satisfies the requirement django-bootstrap-sass==1.0.0 (from versions: 0.0.1a0, 0.0.3a0, 0.0.4a0, 0.0.5a0, 0.0.6a0)
No matching distribution found for django-bootstrap-sass==1.0.0

I think you may have forgotten to upload the new packaged version.

Sounds like I had a problem with my package data, I will have a look and let you know

error: can't copy 'bootstrap_sass/static/fonts': doesn't exist or not a regular file

Do you know what's causing this?  I suspect package_data in setup.py needs to include 'static/fonts/*'.
Thanks for the patience :)

That's exactly the error I had when I try to run the build again today. I think I might switch to use a MANIFEST.in file and do a recursive-include

I have a fix:
package_data={'bootstrap_sass': [
        'static/*/*.scss',
        'static/*/*.js'
    ]

Oops sorry totally forgot about the project, I think we need to include the fonts as well

Of course, my mistake

No worries we're on the right track


fatal: '...' is outside repository error when using "vcs" element, in a subdirectory

Describe Your Issue
I started to encounter
fatal: ...: '...' is outside repository

error in a very specific directory, with the most recent commit.
I find it really strange, since it happens in a folder called "~/Documents/서울대학교 자료/" and all folders within it.
I wasn't able to reproduce the error—trying non-ASCII characters, folders with spacings—in any other folders outside it.
ANY folders within "~/Documents/서울대학교 자료/" that are version-controlled with git has this issue.
The issue is as follows:
fatal: ~/Documents/서울대학교 자료/test: '~/Documents/서울대학교 자료/test' is outside repository

is shown inside a subdirectory a within test.
It occurs in any subdirectories of a git-controlled directory within 서울대학교 자료.

Have you tried to debug or fix it?
The error only occurs with "vcs" segment enabled.
Also, with .zshrc
zplug "bhilburn/powerlevel9k", \
    use:powerlevel9k.zsh-teme, \
    at:78df520

using the commit 78df520, the error is gone.
However, I couldn't reproduce the error occurs in any other directories.
Environment Information
This information will help us understand your configuration.

zsh version: zsh 5.6.2
zplug 2.4.2
via zplug
6cfe8f8
iTerm2 Build 3.2.20180825

I'm facing the same problem. As far as I could understand, it is happening inside git submodules directories.

Thanks for the report @Zeta611 . This is indeed a problem when you are inside a git submodule. @macserv fixed it on next, our development branch.
@diraol @Zeta611 Could you try out #1071 ?

Tested and approved!

next branch does not fix my issue. Now it doesn't get my unique path and returns:
__p9k_get_unique_path:31: no matches found: /Users/jay/Documents//ᄉ*/. fatal: /Users/jay/Documents/서울대학교 자료/2학기/공학수학 1/LectureNotes: '/Users/jay/Documents/서울대학교 자료/2학기/공학수학 1/LectureNotes' is outside repository is still showing. It won't even show a NERDFont icon with P9K_MULTILINE_LAST_PROMPT_PREFIX_ICON="\uF719  ".
Yes, I updated all POWERLEVEL9K_'s with P9K_'s.
This is what I get with an updated next branch:

Hi @Zeta611 , @diraol 's tip should have helped. Could you restart your Machine and see if that helps? If not, could you go a bit more into detail in what you have tried?

After trying to figure out what's the problem, I found out an odd bug.
If I make a folder with Korean characters in the Finder app (of macOS), the fatal error occurs in any git-controlled folder within it.
The folder with a name in Korean characters is not git-controlled, and the git-controlled folder within it is an empty git repository:

Oddly, if I create a folder with Korean characters within a terminal, the error vanishes:

Maybe this is an macOS w/ Korean characters (I haven't tried other languages, but CJK characters might be a problem) issue...?
Is it possible for a folder named within a GUI finder and the one named in a terminal to behave differently?
This is the minimal .zshrc file:
export ZPLUG_HOME=/usr/local/opt/zplug
source $ZPLUG_HOME/init.zsh

zplug "bhilburn/powerlevel9k", \
    use:powerlevel9k.zsh-theme, \
    at:next

if zplug check bhilburn/powerlevel9k; then
    P9K_LEFT_PROMPT_ELEMENTS=(dir vcs)
fi
zplug load

Please do file -I  (capital i) for both and paste the results here. My guess is that the file names are encoded differently. From what I have read in my research, macOS does decomposed encoding (e.g. ¨ then e) as opposed to precomposed (ë). See here

@onaforeignshore  file -I 한글 한글2 prints:
한글:  inode/directory; charset=binary
한글2: inode/directory; charset=binary

I think your guess is right, since making a folder ä within a terminal works fine, but ä2 in the Finder app spits the same error message: __p9k_get_unique_path:31: no matches found.
Is there a way to resolve this issue?
Thanks for your help!

@onaforeignshore I'm using macOS Mojave 10.14.1, and using APFS filetype.. Does the example with ä works fine on your mac?

I am using High Sierra 10.13.6 with APFS and it works for me.

Although it is odd, this wasn't a problem with 78df520 and prior versions. (I see that there is a huge update going on) Is there a change in code responsible for handling encodings? It seems that both the original issue in the thread regarding the "vcs" element and the unique path problem is related.

While I'm trying to find out how to resolve this encoding issue, I made an ad hoc fix to suppress the issue.
At least I can identify the directory with the faulty decomposed encoding, which is the one not truncated.
From what I learned after some research, zsh uses iconv internally to handle decomposed UTF-8 characters, but how to utilize it is beyond my reach as of now.

Should we close this issue and open another one related to the encoding error?

@diraol You are right. Closing this. Not sure if we should open a new issue, cause this seems to be a bug in git itself. I get the error even with plain bash.

@dritter I think the error of mine is more than a git bug, but I also agree with closing the issue. (It is more about an encoding problem in my case.)

Thanks for chatting through all of this, everyone!


Citing this library

Problem description
I want to cite this repo in a publication.
Proposed solution
Would be nice to have Cite this repository button. https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files

I hope you are interested to be cited, because currently I am struggling how to cite this package in my paper. :D

Maybe @piever has an opinion on this as the original author?

Maybe the citation.cff approach is the most sensible, with @jkrumbiegel 's name (as current maintainer) and mine (as original author)?
I don't think I would ever have the  bandwidth to write a manuscript on AlgebraOfGraphics, but maybe it's easy enough to set up a DOI on Zenodo?

I might be able to set up something on JOSS. It did not take terribly long with Makie and it looks much better than zenodo with its kinda random metadata

At least DOI would be already great


feat(Data/List): match_xYz

Not ready to merge! Please only review.

Should I move lemma match_xYz to a different file, so that I can use linarith to make the proof shorter?

I'm going to golf this.

I don't think that naming lists x₁ etc follows our naming conventions. Also please add a docstring.

I'm going to golf this.

Wow, that was shortened much much much more than I expected!!

@eric-wieser What do you think about variable names here? Otherwise LGTM (I'm not merging because I wrote the current proof).

bors r+


Using INSERT statements is much more slower than using CSV

I wanted to load some data to CH to play with it.
After spending a little time with CH, found that using CSV files over INSERT statements is order of magnitude faster.
Sure I was expecting that insert statements would be slower, but not 412X slower!
2 files, 100K rows, same data, while first is in CSV format the other one contains insert statements.
First file: csv.out
Sample data:
'2010-03-10',<PHONE_NUMBER>2, '8006-6129-3130-5580', 1169
'2015-10-17',<PHONE_NUMBER>4, '4681-5453-2740-1617', 8109
'2013-08-05',<PHONE_NUMBER>0, '6661-8986-3509-6991', 55
...

Second file: insert.out
Sample data:
INSERT INTO mytable VALUES('2010-03-10',<PHONE_NUMBER>2, '8006-6129-3130-5580', 1169);
INSERT INTO mytable VALUES('2015-10-17',<PHONE_NUMBER>4, '4681-5453-2740-1617', 8109);
INSERT INTO mytable VALUES('2013-08-05',<PHONE_NUMBER>0, '6661-8986-3509-6991', 55);
...

This is the table I wanted to load.
CREATE TABLE mytable(
	some_date Date,
	some_int	UInt64,
	some_str String,
	some_float Float32
) ENGINE = MergeTree(some_date, (some_int, some_date), 8192);

Testing CSV load:
$ cat csv.out | time clickhouse-client --query="INSERT INTO mytable FORMAT CSV"
0.04user 0.01system 0:00.38elapsed 15%CPU (0avgtext+0avgdata 35312maxresident)k
416inputs+0outputs (4major+3572minor)pagefaults 0swaps

So it took 0:00.38 seconds.
Testing with insert:
$ cat insert.out | time clickhouse-client -n
15.62user 22.88system 2:36.86elapsed 24%CPU (0avgtext+0avgdata 46324maxresident)k
776inputs+0outputs (5major+106780minor)pagefaults 0swaps

And this took 2:36.86 seconds.
That means using CSV is = 412X faster (2:36.86 seconds / 0:00.38 seconds)
Or using insert statements is 412X slower!
I know that using insert statements involves parsing sql and other stuff and this takes time but isn't 412X a little too much for this?
Is this some kind of bug or it's an expected result?
(dropping and re-creating the the table between loads)

This is expected.
INSERT statements with single rows are slower not only because it need SQL parsing for each statement, but also, because each INSERT into MergeTree goes directly into filesystem without any buffering and forms new "data part" with files per each column. (These data parts will be merged in larger parts in background.)
If you transform
INSERT INTO mytable VALUES('2010-03-10',<PHONE_NUMBER>2, '8006-6129-3130-5580', 1169);
INSERT INTO mytable VALUES('2015-10-17',<PHONE_NUMBER>4, '4681-5453-2740-1617', 8109);
INSERT INTO mytable VALUES('2013-08-05',<PHONE_NUMBER>0, '6661-8986-3509-6991', 55);

into
INSERT INTO mytable VALUES
('2010-03-10',<PHONE_NUMBER>2, '8006-6129-3130-5580', 1169)
('2015-10-17',<PHONE_NUMBER>4, '4681-5453-2740-1617', 8109)
('2013-08-05',<PHONE_NUMBER>0, '6661-8986-3509-6991', 55);

then the query will run almost as fast as when using CSV.
Probably we could detect multiple INSERT statements with similar structure to optimize this automatically.

This goes for just about any database.  Bulk inserts, as Alexey showed, are faster.

@alexey-milovidov thank you for detailed answer.
Typically clients connect to db to insert data to only a handful of tables. Most of the time, it's just one table and so one insert statement with different values. Think it like 1000+ clients sending insert statements for an individual table with only one row but they do it with high throughput. Something like 10K inserts per seconds for each client(in my pseudo benchmarks, I saw 150K inserts per second while using CSV for just one client). In this case, using insert statements will cripple the performance as you know.
So in this case, should I develop an automated way to collect values and generate a CSV file to load or is there any other way to make inserts faster?

@ramazanpolat I guess if you have 1000+ clients doing a lot of single-row inserts, you can re-architecture your app in a way like:

a front-facing API to receive messages from thousands of clients
a queue accumulating these messages (Kafka/RabbitMQ/whatever)
a batch writer which dumps batches of messages every couple of seconds.

I was thinking the same, just wanted to be sure if there is another way.
@alexey-milovidov 's comment "Probably we could detect multiple INSERT statements with similar structure to optimize this automatically" should be considered for client inserts. This will save users lots of time and optimization. Should I open an enhancement issue on this?

Yes, it's better to open issue for enhancement.
I already thinking about it. It is also relevant for bulk INSERTs where VALUES contain expressions.

I'm thinking something like this:
Clients connect to CH with a hint in JDBC URL:
jdbc:clickhouse://<host>:<port>[/<database>][?format=table]

This connection style hints CH server to indicate that client will send a text with a supported format to be directly inserted into a table.
With hinted JDBC connection, client can only send a formatted text (with the specified format in JDBC URL) instead of an SQL.
For example:
Client will connect to CH using the following JDBC URL.
jdbc:clickhouse://localhost:8123/test?CSV=mytable

The CH server will be ready to load data directly to the table named 'mytable'. No SQL parsing or any other stuff needed.
Then client sends CSV (https://clickhouse.yandex/docs/en/formats/csv.html) instead of an SQL statement.
Another idea is to extend java.sql.Statement and java.sql.Connection in a way to hint CH about the format and the table:
class BulkLoad implements Statement{
    ...
    public append(String values) {...}
    public load() {...}
    ...
}

then
BulkLoad bulkLoad = con.createBulkLoad(Format.CSV,"mytable");
bulkLoad.append("value1, value2, value3,...");
bulkLoad.append("value4, value5, value6,...");
bulkLoad.append("(value7, value8, value9,...), (value10, value11, value12,...), ....");
bulkLoad.load();

Regarding insert performance I observed that in case you insert data in a ReplicatedMergeTree where EventDate it's spread on 3-4 years the speed is pretty good with batches of 10k records.. But if the same records I spread them in 20 years.. it's at least 100 times slower..

Yes, this is expected, because each batch of data for INSERT is split to batches by partitions. And partitions are months.
There are two possible workarounds:

use even larger batches (example: 100k instead of 10k);
group data by months before insertion.

This is not an issue in typical use cases when you:

insert realtime data;
insert a dump, almost ordered by time.

@alexey-milovidov thanks for explanation, maybe this can be added in documentation because might be a good hint for others as well

@shuttie , Are you aware of any such existing batch writer for clickhouse?

@zero-master https://github.com/nikepan/clickhouse-bulk , but I've never tried this thing in action.

There is also Buffer table engine, which can be used for solving that
problem (with certain limitations, check documentation:
https://clickhouse.yandex/docs/en/table_engines/buffer.html ).
Also there is an experimental Kafka table engine, and Kafka->Clickhouse
bridge.
12 нояб. 2017 г. 1:22 PM пользователь "Roman Grebennikov" <
<EMAIL_ADDRESS>написал:

@zero-master https://github.com/zero-master https://github.com/nikepan/
clickhouse-bulk , but I've never tried this thing in action.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yandex/ClickHouse/issues/1067#issuecomment-343733404,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABelA3Fb6z0fpV--MWgbtPtZ_qGBCIy7ks5s1uMdgaJpZM4OuTaM
.

@ramazanpolat do you have any further questions?


Consider if we should enable embedsignature

https://cython.readthedocs.io/en/latest/src/userguide/source_files_and_compilation.html#compiler-directives

IPython will just display the signatures in the docstring.
Sphinx's autodoc will try to use them as the signature (Only if no annotations hopefully...), but they also include Cython syntax which Sphinx doesn't understand or strip.


Labels overlapping (z-index problem)

As you can see above, "all labels" seem to be on z-top of "all markers" which leads to a problem where labels are overlapping each others, and are visible when they should be hidden behind z-upper markers...
Am I missing something ?
Or is it an unfixable issue ?
Many thanks

It looks like, by default that the markers all have one z-index and the labels are just above that, hence the overlapping.
I fixed this locally, by just ensuring the markers themselves have specified z-indexes (I used 100 + (2 * number), where number is the marker's index).


Toggle mode to allow for sending input to all panes (focus all panes)

Description of the new feature/enhancement
Hey, I would love to have the ability to focus all panes, or more precisely, to be able to toggle a mode which enables me to send the same keyboard input to all panes in the current tab.
I will greatly benefit from the feature as I regularly connect to multiple servers using SSH and perform the same task on each of them.
Proposed technical implementation details (optional)
I have looked a bit inside the WT code, it seems to me that implementing this feature would require sending the keyboard messages to every non-focused pane, as the current controls implementation using WinRT only allows for 1 control to be in focus.

Thanks! This is a /duplicate of #2634.

Thanks! This is a /duplicate of #2634.


PMD issues for Widget Interfaces

The following issues were found in the widget interfaces when running PMD:
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IButton:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICalendar:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICalendar:39 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICalendar:47 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICalendar:57 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:40 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:49 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:57 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:65 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:76 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ICheckBox:87 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IDropDown:34 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IDropDown:43 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IDropDown:52 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IEditableElement:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:35 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:43 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:52 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:64 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:78 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:87 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:98 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:107 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:119 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:127 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:135 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:146 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:154 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:165 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:173 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:184 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:192 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:203 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:212 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:223 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:234 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:246 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:264 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:278 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:296 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:311 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:324 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:338 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:351 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:359 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:372 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:379 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:389 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:399 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:409 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:420 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:431 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:438 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:448 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:457 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:464 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:474 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:483 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:491 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:501 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:508 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IElement:515 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IHyperLink:31 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IImage:31 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:31 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:39 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:47 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:56 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:66 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:76 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:85 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:94 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:102 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:110 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:121 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:131 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:142 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:150 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:158 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveElement:166 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:35 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:46 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:58 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:68 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:68 Rule:UseVarargs Priority:4 Consider using varargs for methods or constructors which take an array the last parameter..
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:79 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:91 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:101 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:111 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:122 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:134 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:145 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:157 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:168 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:178 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:188 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IInteractiveTable:198 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IRadioGroup:31 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IRadioGroup:39 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IRadioGroup:47 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IReadableElement:31 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.IReadableElement:40 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:42 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:52 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:61 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:71 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ISelectList:79 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:34 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:47 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:56 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:65 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:74 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:83 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:94 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITable:105 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.
[INFO] PMD Failure: org.finra.jtaf.ewd.widget.ITextField:32 Rule:UnusedModifier Priority:3 Avoid modifiers which are implied by the context.

fixed by #99


[Test][IRGen] Add missing EOL.

I thought I'd added this to the previous PR, but it seems I managed to fail to add the change before committing.

@swift-ci Please smoke test


Add disconnect message when joining a server without perms

Currently, the plugin doesn't do anything when a player tries to join a server without perms from the main menu (like with forced hosts) and therefore causes them to time out. It would be nice if there was a disconnect message when trying to join instead.

resolved in #41


precommit: ruff-format

What does this PR do?
follow-up for #19380

Before submitting

Was this discussed/agreed via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
Did you make sure to update the documentation with your changes? (if necessary)
Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
Did you list all the breaking changes introduced by this pull request?
Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--19434.org.readthedocs.build/en/19434/

it was intention of this PR but in the end I quite like the dense formatting :flamingo:


[ISSUE] w.workspace_conf.get_status - AttributeError: type object 'dict' has no attribute 'from_dict'

Description
I received the following exception:
Traceback (most recent call last):
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/interactiveshell.py", line 3378, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<command-1207976897601940>", line 8, in <module>
    conf = w.workspace_conf.get_status(keys="enableWorkspaceFilesystem")
  File "/local_disk0/.ephemeral_nfs/envs/pythonEnv-1b805d4b-f851-4007-9970-aa16ffb0933a/lib/python3.9/site-packages/databricks/sdk/service/settings.py", line 1397, in get_status
    return WorkspaceConf.from_dict(res)
  File "/usr/lib/python3.9/typing.py", line 693, in __getattr__
    return getattr(self.__origin__, attr)
AttributeError: type object 'dict' has no attribute 'from_dict'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/interactiveshell.py", line 1997, in showtraceback
    stb = self.InteractiveTB.structured_traceback(
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/ultratb.py", line 1112, in structured_traceback
    return FormattedTB.structured_traceback(
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/ultratb.py", line 1006, in structured_traceback
    return VerboseTB.structured_traceback(
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/ultratb.py", line 859, in structured_traceback
    formatted_exception = self.format_exception_as_a_whole(etype, evalue, etb, number_of_lines_of_context,
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/ultratb.py", line 812, in format_exception_as_a_whole
    frames.append(self.format_record(r))
  File "/databricks/python/lib/python3.9/site-packages/IPython/core/ultratb.py", line 730, in format_record
    result += ''.join(_format_traceback_lines(frame_info.lines, Colors, self.has_colors, lvals))
  File "/databricks/python/lib/python3.9/site-packages/stack_data/utils.py", line 145, in cached_property_wrapper
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/databricks/python/lib/python3.9/site-packages/stack_data/core.py", line 698, in lines
    pieces = self.included_pieces
  File "/databricks/python/lib/python3.9/site-packages/stack_data/utils.py", line 145, in cached_property_wrapper
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/databricks/python/lib/python3.9/site-packages/stack_data/core.py", line 649, in included_pieces
    pos = scope_pieces.index(self.executing_piece)
  File "/databricks/python/lib/python3.9/site-packages/stack_data/utils.py", line 145, in cached_property_wrapper
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/databricks/python/lib/python3.9/site-packages/stack_data/core.py", line 628, in executing_piece
    return only(
  File "/databricks/python/lib/python3.9/site-packages/executing/executing.py", line 164, in only
    raise NotOneValueFound('Expected one value, found 0')
executing.executing.NotOneValueFound: Expected one value, found 0

Reproduction
from databricks.sdk import WorkspaceClient
import logging

logging.basicConfig(level=logging.DEBUG)

w = WorkspaceClient()

conf = w.workspace_conf.get_status(keys="enableWorkspaceFilesystem")

Expected behavior
conf should be Dict[str,str]
Debug Logs
DEBUG:databricks.sdk:/root/.databrickscfg does not exist
DEBUG:databricks.sdk:Attempting to configure auth: pat
DEBUG:databricks.sdk:Attempting to configure auth: basic
DEBUG:databricks.sdk:Attempting to configure auth: metadata-service
DEBUG:databricks.sdk:Attempting to configure auth: oauth-m2m
DEBUG:databricks.sdk:Attempting to configure auth: azure-client-secret
DEBUG:databricks.sdk:Attempting to configure auth: azure-cli
DEBUG:databricks.sdk:Attempting to configure auth: external-browser
DEBUG:databricks.sdk:Attempting to configure auth: databricks-cli
DEBUG:databricks.sdk:Attempting to configure auth: runtime
DEBUG:py4j.clientserver:Command to send: i
java.util.HashMap
e

DEBUG:py4j.clientserver:Answer received: !yao635
DEBUG:py4j.clientserver:Command to send: c
o635
put
spackageNameRaw
sdbruntime
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o635
put
spackageNameAllowlisted
s22a5145ea2dae9ca02b280a74ea51ee7ffd37e81970529947d8189308ded7814
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o635
put
spackageHash
s22a5145ea2dae9ca02b280a74ea51ee7ffd37e81970529947d8189308ded7814
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o635
put
spackageVersion
sunknown
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o378
logUsage
spythonPackageImported
ro635
n
e

DEBUG:py4j.clientserver:Answer received: !yv
DEBUG:databricks.sdk:[init_runtime_repl_auth] runtime native auth configured
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): adb-4220020519396524.4.azuredatabricks.net:443
DEBUG:py4j.clientserver:Command to send: i
java.util.HashMap
e

DEBUG:py4j.clientserver:Answer received: !yao636
DEBUG:py4j.clientserver:Command to send: c
o636
put
spackageNameRaw
stime
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o636
put
spackageNameAllowlisted
s336074805fc853987abe6f7fe3ad97a6a6f3077a16391fec744f671a015fbd7e
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o636
put
spackageHash
s336074805fc853987abe6f7fe3ad97a6a6f3077a16391fec744f671a015fbd7e
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o636
put
spackageVersion
sunknown
e

DEBUG:py4j.clientserver:Answer received: !yn
DEBUG:py4j.clientserver:Command to send: c
o378
logUsage
spythonPackageImported
ro636
n
e

DEBUG:py4j.clientserver:Answer received: !yv
DEBUG:urllib3.connectionpool:https://adb-4220020519396524.4.azuredatabricks.net:443 "GET /api/2.0/workspace-conf?keys=enableWorkspaceFilesystem HTTP/1.1" 200 None
DEBUG:databricks.sdk:GET /api/2.0/workspace-conf?keys=enableWorkspaceFilesystem
< 200 OK
< {
<   "enableWorkspaceFilesystem": "true"
< }

Other Information

databricks_sdk-0.8.0-py3-none-any.whl
Databricks Runtime Version: [12.2 LTS ML (includes Apache Spark 3.3.2, Scala 2.12)
Node type: Standard_DS3_v2

Facing this as well with databricks-sdk==0.9.0

Hi @nviraj @snowch, thanks for highlighting the issue. We are looking into it, closing this one as it is duplicate of the one you mentioned.


Bring back missing help text.  Fixes #1362.

I also moved the main new_backfill script out of its subdir to make maintenance of the command system easier.

Why was new_backfill moved out, and how are users / developers supposed to know why there is a second backfill command?

Hey, it's been a while and I don't really remember zenbot anymore, but often I try to make incremental changes to things to help visiting developers make a little progress.  The answers are in the source code and change history.
I've always found it a barrier to contribution to have important things distant from each other, could be related.  I imagine if my change is making it harder to use the software, then it could have been the wrong thing.  It looks like my intent was likely mostly to provide help documentation and make important scripts easier to find.

What's the difference between backfill and new_backfill ??
new_backfill seems to do the same as backfill, and only has the option of retreiving last days, and many comments inside the code of thing TODO....
I've always used backfill and didn't have problems.
But why there are 2 commands to do the same?


Added my Javascript BMI calculator

congratulations on your hactoberfest contribution. if you like this repo then give it a star. Happy hacking..


Allow set same value if (set_once) = true

Currently, an enabled (set_once) option forbids the user to set any kind of value to the field. This is inconvenient since sometimes users may want to set the same value to the field. The hasField(...) checks are the only way to make sure that an error would not be produced in such a case.
This PR allows users to set the same value to the field.
Also, the (set_once) checks are being added to setRaw...(...) and clear...() methods.
put...(...) and add...(...) methods now have explicit checks that the collection field is not marked with (set_once).

@armiol, PTAL.


request: publish docker images

It would be helpful if toc was available as a docker image. I think a simple scratch container with a static binary in it would be sufficient.
I'd offer a PR to your goreleaser.yaml but I can't really test it and don't know which docker registry you would prefer.

Hey @joemiller, just added it!
It is available with v0.2.51.
docker run --rm -it yagizcan/toc:latest toc
docker run --rm -it yagizcan/toc:$TAG_NAME toc

Hey @joemiller, just added it!
It is available with v0.2.51.
docker run --rm -it yagizcan/toc:latest toc
docker run --rm -it yagizcan/toc:$TAG_NAME toc

awesome!! thanks

awesome!! thanks


Fs.writefile not writing to github repo on build

Hi! so I wanted to use netlify cms for one of my projects and I am a netlify newbie. so my collections export in JSON format extension: JSON , format: JSON and obviously netlify cms create a file, and each entry to the file is stored as independent JSON files so I wanted to combine all this json files into one json file on the build . Now the problem I am facing is on build in the local server there is no problem the code combines all JSON files into a new JSON file but when building on netlify the file is not created in the git repo ad no error is also thrown.
folder structure:-
-products _( collection output  )_
   --product1.json
   --product2.json
   --product3.json
-public
   --admin
      --config.yml
      --index.html
   --images
   --index.html
   --main.js _( code to combine all products to one product.json file )_
-src
   --shared
      --products.json _( after combining output file . it is produced on build in  local server but not on netlify  )_
-package.json
-etc.

main.js:-
var fs = require("fs");
var path = require("path");
let jsonfile = [];
const dirPath = path.join(__dirname, "../products")
fs.readdir(dirPath, (err, fileNames) => {
fileNames.forEach(filename => {
    const filePath = path.join(dirPath,"/",filename)
    let jsonData = require(filePath);
    jsonfile.push(jsonData);
});
 fs.writeFile("./src/Shared/products/products.json", JSON.stringify(jsonfile), err => {
    // Checking for errors
   if (err) throw err;
   console.log("Done writing"); // Success
 });
});

package.json
"build": "node ./public/main.js && react-scripts build",
Well, this works perfectly in the local server but on build in netlify there are no errors thrown yet the file is not created.
well I am also open any ideas where I can get a combined JSON file directly from the CMS (I have aleady tried list but it looks a bit messsy .)
config.yml
backend:
  name: git-gateway
  branch: master # Branch to update (optional; defaults to master)

# These lines should *not* be indented
media_folder: "public/images/products"
public_folder: "/images/products"

collections:
  - name: "products" # Used in routes, e.g., /admin/collections/blog
    label: "Products" # Used in the UI
    extension: json
    format: json
    folder: "products" # The path to the folder where the documents are stored
    create: true # Allow users to create new documents in this collection
    slug: "{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    fields: # The fields for each document, usually in front matter
      - {label: "Title", name: "title", widget: "string"}
      - {label: "Short Title", name: "stitle", widget: "string"}
      - {label: "ID", name: "id", widget: "hidden", default: '{{year}}_{{month}}_{{day}}_{{hour}}_{{second}}_{{minute}}_{{day}}_{{slug}}'}
      - widget: relation
        name: category
        label: Related category
        required: false
        multiple: false
        hint: >-
          Category of product (The category should already be present in Category Tab )
        collection: category
        valueField: title
        searchFields: ["title"]
        displayFields: ["title"]
      - {label: "Orginal Price", name: "oldprice", widget: "number"}
      - {label: "Discounted Price", name: "newprice", widget: "number"}
      - {label: "Discount ?", name: "discount", widget: "boolean", default: false}
      - {label: "Description", name: "description", widget: "text"}
      - {label: "Cover Image", name: "coverimg", widget: "image"}
      - {label: "Main Image", name: "mainimg", widget: "image"}
      - {label: "Product Image 1", name: "prdctimg1", widget: "image", required: false}
      - {label: "Product Image 2", name: "prdctimg2", widget: "image", required: false}
      - {label: "Product Image 3", name: "prdctimg3", widget: "image", required: false}
      - {label: "Product Image 4", name: "prdctimg4", widget: "image", required: false}
      - {label: "Product Image 5", name: "prdctimg5", widget: "image", required: false}
      - {label: "Slider", name: "slider", widget: "boolean", default: false}
      - {label: "Top Selling", name: "top", widget: "boolean", default: false}
      - {label: "Featured product", name: "featured", widget: "boolean", default: false}
      - {label: "New Products", name: "new", widget: "boolean", default: true}

  - name: "category" # Used in routes, e.g., /admin/collections/blog
    label: "Categories" # Used in the UI
    extension: json
    format: json
    folder: "category" # The path to the folder where the documents are stored
    create: true # Allow users to create new documents in this collection
    slug: "{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    fields: # The fields for each document, usually in front matter
      - {label: "Categories", name: "title", widget: "string" }

Hi @crimzonarc, this seems more related to setting up your build script than the CMS.
I recommend posting in https://community.netlify.com/.

I am having the same issue


Exporting merged declarations doesn't work.

Code
File common.ts
export interface Identifier {
	type: string;
}

File node.ts
import { Identifier } from "./common";

namespace Identifier {
	export function create(type: string): Identifier {
		return { type };
	}
}

export { Identifier };

File use.ts
import { Identifier } from './node';

let id: Identifer = Identifier.create('abc');

Expected behavior:
No error annotation on the Identifier type annotation
Actual behavior:
The type annotation Indentifier has a red underline Can not find name Identifier
Hovering over the Identifer in the import statement shows

It is not clear what merging with an exported symbol really means. does it merge with the source, or does it copy the source properties, merge with that and then export a new type. This never worked really, the fact that we do not flag it as an error is a long standing bug.

I would expect it to merge as if both are declared in the same file (which works without problems). Why is it different if the two Identifier come from different files?
And as you can see the hover knows about both of them.

It currently semi-works. merging in general means that the two declarations are the same. and the declaration name points to the sum of both declaration.
In places where that is not possible, the compiler generates an error, for instance var x; class x {} since the meaning of the merge is not clear.
In this case, due to a bug in the implementation, the compiler does not raise an error for merging with a local alias. Merging with a local alias is rather unclear, did you mean to add a new property to the original declaration? e.g. would all importers of the original interface see a new property? or was it meant to create a local copy of the declaration, add a property to it, and then export that?
For the first option (augmenting the original declaration), the language has some clear merging constructs for augmenting the original declaration (see module augmentation](https://www.typescriptlang.org/docs/handbook/declaration-merging.html#module-augmentation)).
For the second option, the compiler has implementation assumptions about aliases, that makes the it hard to implement this change, in addition it does not follow the same logic like other merges.


SEO documentation

SEO Docs
Task from #57
Follow up from #80

This PR adds documentation for SEO configuration in docs - /docs/seo
Tasks

[x] SEO docs
[x] social preview screenshot

@olayway do you want to review this one?


[ Feature ] Toggle sprint internally should repeat

Buyanov's tarkov always forget to do last action while in animation or looks like.
Example:

lay down
start to reload
emergency standup while reload
try to run holding shift

If you're still being animated - even if you hold shift non-stop - the person will not run until you press shift again.
Is it possible to fix using your mod?

Possibly; I'll look into it


feat: support pdf label creation

The UPS API is very weak, one can't create labels in PDF format. Some clients might want that. This abstracts the logic for the API client user, by detecting the request is for a PDF, requesting a PNG instead and later using a different UPS endpoint to create a copy of the PNG label but in PDF.

At an API level this seems too hacky we should move this to an upper abstraction layer... but let's discuss how can we achieve that

Closing this as we need to move this code to the app layer


Specify implementation requirements for WIRI and WPRI fields

For many register fields defined as WIRI and WPRI, the documents don't (as far as I know) explicitly say what is required of an implementation.  For forward compatibility, it should be made explicit that implementations must hardwire those bits to zeros.

Can you offer your opinion on https://github.com/riscv/riscv-isa-manual/pull/121?

Good enough for me.

Thanks.  Closed by #121.


IVRSystem errors

Trying to import the assets into my scene and I get a flood of errors in console about "The namespace 'Valve.VR' already contains a definition for 'IVRSystem'"
Error starts in "openvr_api" line 16 "public struct IVRSystem".
Has anyone else come across this issue?
Using Unity 5.40f3

I receive the same error. Did you ever resolve the problem?

I figured it out. Don't drag the whole Vive-Teleporter directory into your Unity project. Just put the Vive-Teleporter\Assets\Vive-Teleporter directory into your Unity project's Assets directory .

Hi, sorry for the late response.  I would recommend downloading the unitypackage from the Releases page instead of downloading the repo directly.  However, if you would prefer to download the repo for bleeding-edge changes, you should only import the Vive-Teleporter directory.


[SPARK-49600][PYTHON] Remove Python 3.6 and older-related logic from try_simplify_traceback

What changes were proposed in this pull request?
Apache Spark 4.0.0 supports only Python 3.9+.

#46228

Why are the changes needed?
To simplify and clarify the logic. I manually confirmed that this is the last logic about sys.version_info and (3, 7).
$ git grep 'sys.version_info' | grep '(3, 7)'
python/pyspark/util.py:    if sys.version_info[:2] < (3, 7):
python/pyspark/util.py:    if "pypy" not in platform.python_implementation().lower() and sys.version_info[:2] >= (3, 7):

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you, @LuciferYang .

Merged to master.