arch:tcbinfo: update tcbinfo as xcpcontext update

Summary
arch:tcbinfo: update tcbinfo as xcpcontext update
jlink-nuttx: update regs as nuttx regs save path change
Impact
Testing

BTW, are you guys getting this error when enabling TCBINFO?

armv7-m/arm_tcbinfo.c:38:3: error: cannot apply 'offsetof' to a non constant address
38 |   TCB_REG_OFF(REG_R0)

I only get this with ARM, I can build RISC-V and Xtensa with no issues.  My version is: arm-none-eabi-gcc (GNU Toolchain for the Arm Architecture 11.2-2022.02 (arm-11.14)) 11.2.1 20220111

@Ouss4 last time I tried GCC 11 I got next results: https://github.com/apache/incubator-nuttx/pull/5659#issuecomment-1056999840
IMO ARM GCC 11 is not usable for now. Probably some faulty release was done

@Ouss4 last time I tried GCC 11 I got next results: #5659 (comment) IMO ARM GCC 11 is not usable for now. Probably some faulty release was done

I had version 9 before, so I thought it was because of my outdated version, but updated to the 11th and still the same issue.  I have another computer with GCC 10 and I am getting the same thing.
Sorry for this somewhat unrelated comment, I just want to know what ARM GCC version this is working with.

The NuttX CI is using GCC 10. I use it as well.

@Ouss4 I think this PR should solve your issue

The NuttX CI is using GCC 10. I use it as well.

Yes, but AFAIK, no defconfig enables TCBINFO.

@Ouss4 I think this PR should solve your issue

I just looked again and I see that offsetoff was replaced for registers.  I can try later.

BTW, are you guys getting this error when enabling TCBINFO?

armv7-m/arm_tcbinfo.c:38:3: error: cannot apply 'offsetof' to a non constant address
38 |   TCB_REG_OFF(REG_R0)

I only get this with ARM, I can build RISC-V and Xtensa with no issues. My version is: arm-none-eabi-gcc (GNU Toolchain for the Arm Architecture 11.2-2022.02 (arm-11.14)) 11.2.1 20220111

The tcbinfo is broken by:
https://github.com/apache/incubator-nuttx/pull/5645
https://github.com/apache/incubator-nuttx/pull/5731
That's why @zhuyanlinzyl create this new PR.

The tcbinfo is broken by:
https://github.com/apache/incubator-nuttx/pull/5645
https://github.com/apache/incubator-nuttx/pull/5731
That's why @zhuyanlinzyl create this new PR.

Thanks!  I can still build RISC-V but always had that issue for ARM.  Anyway, let's try to get this one in.

The tcbinfo is broken by:
#5645
#5731
That's why @zhuyanlinzyl create this new PR.

Thanks! I can still build RISC-V but always had that issue for ARM. Anyway, let's try to get this one in.

Hmm, it's strange that RISC-V can pass the build.

The tcbinfo is broken by:
#5645
#5731
That's why @zhuyanlinzyl create this new PR.

Thanks! I can still build RISC-V but always had that issue for ARM. Anyway, let's try to get this one in.

Hmm, it's strange that RISC-V can pass the build.

I just tried again with ESP32-C3 and indeed it's failing.  I guess I didn't had #5731 when I tried last time.

We haven't tried RISCV before, there may some bug in the code. @zhuyanlinzyl and @no1wudi will try and fix the issue in the next week.

@Ouss4 do you have the workable nuttx-jlink.so?

@xiaoxiang781216 I'm not using jlink sorry for the confusion.  I'm doing kind of the same thing for OpenOCD.

Ok, I remember @masayuki2009 upstream nuttx addon before. Do you improve that addon to support more arch with tcbinfo?
BTW, could you add xtensa register list here:
https://github.com/apache/incubator-nuttx/blob/master/tools/minidumpserver.py#L113-L167
This tool can give more useful information than panic when you can't attach JTAG to the device.

Ok, I remember @masayuki2009 upstream nuttx addon before. Do you improve that addon to support more arch with tcbinfo?

Yes, sometime ago I added Xtensa stacking info to support ESP32 and did some general cleanup.  Now I'm updating that to use tcbinfo and add ESP32-S2, S3 and RISC-V.

BTW, could you add xtensa register list here:
https://github.com/apache/incubator-nuttx/blob/master/tools/minidumpserver.py#L113-L167
This tool can give more useful information than panic when you can't attach JTAG to the device.

I'll give that a look.  Xtensa probably requires more than just adding the registers.

BTW, could you share your new version after finishing? @zhuyanlinzyl could help verify xtensa with our device.

Could you share your new version after finishing? @zhuyanlinzyl could help verify xtensa with our device.

Sure, it will be here: https://github.com/espressif/openocd-esp32.  I will let you know it's merged.  We also plan to submitting it to the upstream project.  Since the NuttX changes are self-contained that would be simpler compared to the rest of the fork.

hi @Ouss4 :
I have use a esp32c3 devkit board as this https://docs.espressif.com/projects/esp-idf/zh_CN/latest/esp32c3/hw-reference/esp32c3/user-guide-devkitm-1.html
but It can not run with nuttx esp32c3-devkit:nsh config.
ESP-ROM:esp32c3-20200918
Build:Sep 18 2020
rst:0x3 (RTC_SW_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d153a
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x1a98
load:0x403ce000,len:0xb4c
load:0x403d0000,len:0x2a7c
entry 0x403ce000
I (34) boot: ESP-IDF v4.3.1-296-gd474c76556 2nd stage bootloader
I (35) boot: compile time 16:00:43
I (35) boot: chip revision: 1
E (38) boot_comm: This chip is revision 1 but the application is configured for minimum revision 3. Can't run.

It reboot always with same log.
Could you give me some advice?

@zhuyanlinzyl it looks like your second stage bootloader was configured for rev3 only.
If you have IDF setup can you build one with rev1? The option to set this should be in the Bootloader option.
I am on my phone now, I should have a binary ready, also I think we can build that from the esp-nutt-bootloader repos. I will check in a moment.

The option to set this should be in the Bootloader option.

Sorry, the option is in "Component Config -> ESP32C3 Specific -> Minimum Supported ESP32-C3 Version"
I built one for rev1. Please give it a try (I called .txt because Github didn't like uploading binary files).
It should also be possible to customize and build the bootloader from here: https://github.com/espressif/esp-nuttx-bootloader#building-locally instead of IDF.
bootloader.txt

hi, @Ouss4 :
Thanks for you advice. I have solve this problem.
Now nuttx can run in esp32c3 devkit board.
But then i find openocd-esp32(build from https://github.com/espressif/openocd-esp32)
connect the esp32c3 devkit board was not correct:
the log as follow:
zyl@zyl:~/code/esp/openocd-esp32/tcl$ ./openocd -f board/esp32c3-ftdi.cfg
Open On-Chip Debugger  v0.11.0-esp32-20211220-1282-g5734ab36 (2022-04-06-11:42)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 5000 kHz

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V11 compiled Mar  3 2022 10:16:14
Info : Hardware version: 11.00
Info : VTarget = 3.199 V
Info : clock speed 5000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40101104
Info : starting gdb server for esp32c3 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
**Warn : No symbols for FreeRTOS!**
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Warn : No symbols for FreeRTOS!
Error: Algorithm timed out after 40001 ms.
Error: ra = 0x40380bfe
Error: sp = 0x3fc84850
Error: gp = 0x3fc83436
Error: tp = 0x0
Error: t0 = 0x4005890e
Error: t1 = 0x0
Error: t2 = 0x30
Error: s0 = 0x60008000
Error: s1 = 0xa0
Error: a0 = 0x2e
Error: a1 = 0x65
Error: a2 = 0x2e
Error: a3 = 0x6000001c
Error: a4 = 0x0
Error: a5 = 0x0
Error: a6 = 0x2
Error: a7 = 0x403816e4
Error: s2 = 0x3fc81a08
Error: s3 = 0x1
Error: s4 = 0x3fc81ab4
Error: s5 = 0x3fc81a84
Error: s6 = 0x0
Error: s7 = 0xa0
Error: s8 = 0x0
Error: s9 = 0xa0

@zhuyanlinzyl
Since you have revision-1 of ESP32-C3, can you check if the correct efuse is burnt:
(this is required for revision-1 since the internal USB-JTAG is non-functional).
$ espefuse.py --port /dev/ttyXXX summary | grep JTAG

JTAG_SEL_ENABLE (BLOCK0)                           Set this bit to enable selection between usb_to_jt = False R/W (0b0)
SOFT_DIS_JTAG (BLOCK0)                             Software disables JTAG. When software disabled, JT = 0 R/W (0b000)
DIS_PAD_JTAG (BLOCK0)                              Permanently disable JTAG access via pads. USB JTAG = False R/W (0b0)
DIS_USB_JTAG (BLOCK0)                              Disables USB JTAG. JTAG access via pads is control = True R/W (0b1)

If DIS_USB_JTAG is false, then you can burn it with: espefuse.py -p /dev/ttyXXX burn_efuse DIS_USB_JTAG
To be honest the issue you are having doesn't seem to be related to the efuse, as I see that JTAG was initialized and the chip was detected correctly.  However, I see those stacking errors, did you add those logs or are they already there?
If the issue is from FreeRTOS, you can disable that by running OpenOCD like: openocd -c 'set ESP_RTOS none' -f board/esp32c3-ftdi.cfg
Note however if you want to try debug awareness, it's still not in the repo.  Actually, there isn't even RISC-V stacking info.  I have it in my local copy along changes to use g_tcbinfo and g_pidhash, coincidently I'm seeing some issues with ESP32-C3 as well (not sure if it's related to ESP32-C3 or I got the RISC-V stacking incorrect somehow):
$ riscv64-unknown-elf-gdb nuttx
(gdb) target extended-remote :3333
(gdb) c
(gdb) info threads
  Id   Target Id                                                       Frame
* 1    Thread<PHONE_NUMBER> "Idle Task" (Name: Idle Task, pid:0, RUNNING) up_idle () at chip/esp32c3_idle.c:265
  2    Thread<PHONE_NUMBER> "lpwork" (Name: lpwork, pid:1, WAIT_SEM)      0x3fc92108 in ?? ()
  3    Thread<PHONE_NUMBER> "nsh_main" (Name: nsh_main, pid:2, WAIT_SEM)  0x3fc92cb8 in ?? ()
  4    Thread<PHONE_NUMBER> "rt_timer" (Name: rt_timer, pid:3, WAIT_SEM)  0x3fc93958 in ?? ()
  5    Thread<PHONE_NUMBER> "wifi" (Name: wifi, pid:4, WAIT_MQNOTEMPTY)   0x3fc94ad8 in ?? ()

Trying to figure out issues with the backtrace of tasks other than the Idle.

hi @Ouss4  I have success setup the openocd-esp32
zyl@zyl:~/code/esp/openocd-esp32/tcl$ openocd -c 'set ESP_RTOS none' -f board/esp32c3-ftdi.cfg
Open On-Chip Debugger  v0.11.0-esp32-20211220-1282-g5734ab36 (2022-04-06-11:42)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
none
adapter speed: 5000 kHz

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V11 compiled Mar  3 2022 10:16:14
Info : Hardware version: 11.00
Info : VTarget = 3.315 V
Info : clock speed 5000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40101104
Info : starting gdb server for esp32c3 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : [esp32c3] Found 8 triggers
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 12 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 65 KB
Info : Auto-detected flash bank 'esp32c3.flash' size 4096 KB
Info : Using flash bank 'esp32c3.flash' size 4096 KB
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 12 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 65 KB
Info : Using flash bank 'esp32c3.irom' size 68 KB
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 12 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 65 KB
Info : Using flash bank 'esp32c3.drom' size 16 KB
Warn : negative reply, retrying
Warn : negative reply, retrying
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"

and riscv64-unknown-elf-gdb show this

zyl@zyl:~/nuttx$ riscv64-unknown-elf-gdb ./nuttx -ex "target remote localhost:3333"
(gdb) info threads
  Id   Target Id         Frame
* 1    Remote target     0x4200471e in up_idle ()
(gdb) ps
Undefined command: "ps".  Try "help".
(gdb) c
Continuing.
(gdb) bt
^C
Program received signal SIGINT, Interrupt.
0x4200471e in up_idle ()
(gdb) info stack
#0  0x4200471e in up_idle ()
#1  0x42000ffc in nx_start ()
#2  0x4200008a in __esp32c3_start ()
#3  0x42000044 in _stext ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) info threads
  Id   Target Id         Frame
* 1    Remote target     0x4200471e in up_idle ()
(gdb)

So I'd like to known why this PR does't work, as I think the info threads and info stack can work

@Ouss4

@zhuyanlinzyl

So I'd like to known why this PR does't work, as I think the info threads and info stack can work

info threads does not work because OpenOCD was started without thread awareness: ESP_RTOS none.  To add that it should be started as openocd -c 'set ESP_RTOS nuttx' -f board/esp32c3-ftdi.cfg.  But as I comented above, the version in master is 1. out dated and 2. does not have RISC-V stacking info.  So that will not work either.  I have updated that and added RISC-V stacking info in my local branch.
Regarding JLink, I don't think they have support for ESP32-C3 as it says Unknown device.

But can we pass the required argument to JLINK manually?

@xiaoxiang781216 I don't know what are the required arguments for Jlink.  I can ask if anyone has used that with ESP32-C3.

@zhuyanlinzyl

So I'd like to known why this PR does't work, as I think the info threads and info stack can work

info threads does not work because OpenOCD was started without thread awareness: ESP_RTOS none. To add that it should be started as openocd -c 'set ESP_RTOS nuttx' -f board/esp32c3-ftdi.cfg. But as I comented above, the version in master is 1. out dated and 2. does not have RISC-V stacking info. So that will not work either. I have updated that and added RISC-V stacking info in my local branch.
Regarding JLink, I don't think they have support for ESP32-C3 as it says Unknown device.

Where can I find your local branch? We want to try your update with ESP32 device.

@xiaoxiang781216 sorry I missed this comment.
I still haven't pushed it.  I updated it with what we have right now and it works on ESP32.  However that won't work for any ARM or RISC-V chip because of the updates we have in https://github.com/apache/incubator-nuttx/pull/5645 and https://github.com/apache/incubator-nuttx/pull/5731.  So I did the same for Xtensa and I am updating OpenOCD again.

Sure, thanks.

@xiaoxiang781216 please take a look at: https://github.com/Ouss4/openocd-esp32/tree/nuttx
You can build it using:
cd openocd-esp32
./bootstrap
./configure --disable-doxygen-html --disable-doxygen-pdf\
            --enable-ftdi --enable-jlink --enable-ulink\
            --disable-werror --disable-presto --disable-openjtag\
            --disable-usbprog --disable-rlink --disable-kitprog\
            --disable-cmsis-dap
make

Then run with ./src/openocd -s tcl -c 'set ESP_RTOS NuttX' -c 'set ESP32_ONLYCPU 1' -f board/esp32-wrover-kit-3.3v.cfg.
And from GDB side:
(gdb) target extended-remote :3333
Remote debugging using :3333
up_idle () at chip/esp32_idle.c:293
293	  esp32_idlepm();
(gdb) mon reset halt
...
(gdb) flushregs
Register cache flushed.
(gdb) c
Continuing.
^Cesp32.cpu0: Target halted, PC=0x400E4782, debug_reason=00000000
Set GDB target to 'esp32.cpu0'
[New Thread<PHONE_NUMBER>]
[New Thread<PHONE_NUMBER>]

Thread 1 "Idle Task" received signal SIGINT, Interrupt.
up_idle () at chip/esp32_idle.c:293
293	  esp32_idlepm();
(gdb) info threads
  Id   Target Id         Frame
* 1    Thread<PHONE_NUMBER> "Idle Task" (Name: Idle Task, pid:0, RUNNING) up_idle () at chip/esp32_idle.c:293
  2    Thread<PHONE_NUMBER> "nsh_main" (Name: nsh_main, pid:1, WAIT_SEM) 0x400d4e59 in sys_call2 (nbr=2, parm2=1073412252, parm1=<optimized out>)
    at /Users/ouss4/NuttX/nuttx/include/arch/syscall.h:258
  3    Thread<PHONE_NUMBER> "ostest" (Name: ostest, pid:2, WAIT_SEM) 0x400d4e59 in sys_call2 (nbr=2, parm2=1073413484, parm1=<optimized out>)
    at /Users/ouss4/NuttX/nuttx/include/arch/syscall.h:258
  4    Thread<PHONE_NUMBER> "ostest" (Name: ostest, pid:3, WAIT_SIG) 0x400d4e59 in sys_call2 (nbr=2, parm2=1073414276, parm1=<optimized out>)
    at /Users/ouss4/NuttX/nuttx/include/arch/syscall.h:258

Thanks, @Ouss4


Integrate with graphql api

Describe the bug
tried to integrate with my backend graphql api but i got the following error

Can you put a reproduction sample in a gist?

@surma here please https://gist.github.com/shohinrahmonov/5f25629ee4ac10dde5f692078fa8f564

That’s not a reproduction sample. That’s a code snippet. I need something I can run to reproduce the error locally. What Node version are you running?

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.

But why the source code was removed? https://github.com/GoogleChromeLabs/squoosh/tree/dev/libsquoosh

See the previous message


Gcp.iam.org folder policy changes

Background
Add a detection for changes to a GCP IAM organization or folder policy.
The detection checks if the user-agent has the word "terraform" in it.
Although this could be spoofed, it will reduce noise from a lot of valid IaC changes.
Changes
gcp_audit_rules/gcp_iam_org_folder_changes.py
gcp_audit_rules/gcp_iam_org_folder_changes.yml
Testing
This has been deployed for over a month in our Panther instance
and with panther_analysis_tool

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: kbroughton:x: GIT SYNC ACTIONGIT SYNC ACTION seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update uuid-creator to 4.6.0

Updates com.github.f4b6a3:uuid-creator from 4.5.0 to 4.6.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.f4b6a3", artifactId = "uuid-creator" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #293 (34d7bb8) into main (231e2d1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #293   +/-   ##
=======================================
  Coverage   88.76%   88.76%
=======================================
  Files          91       91
  Lines        2776     2776
  Branches       68       68
=======================================
  Hits         2464     2464
  Misses        312      312

Continue to review full report at Codecov.

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


Add translated_message field to ChatMessage model

This pull request adds functionality to the Ayushma application by adding a new field, translated_message to the ChatMessage model. The ChatMessageSerializer class has also been updated to include this new field to its output. The converse() function has also undergone changes to support translation of chat messages, recording the original message and the translated message.
Additionally, the utils/openaiapi.py module has been modified to update the converse() function and to add an import of typing.Dict and typing.List.
These changes will enhance the functionality of the Ayushma application by adding the capability to retrieve the original message and its respective translation, making it easier to check the accuracy of the translation, if necessary.

No longer required, resolved by https://github.com/coronasafe/ayushma/pull/131


Code workflow

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


Series question for the MSF module

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04):Linux Ubuntu 18.04
Apollo installed from (source or binary):source
Apollo version (3.5, 5.0, 5.5, 6.0):5.5
Output of apollo.sh config if on master branch:5.5

Steps to reproduce the issue:

configure the gnss 、lidar 、localization 、tf module
run it;
then,  found all the topic we expect are ok(msf_gnss、msf_status...) except for the topic: msf_lidar.

So there are some question for the msf module:
1:  according to the msf_simple_map_creator.sh described. if you want to generate the localization map . you should take the topic of msf_lidar as a input. but msf module should first get a map for the topic of msf_lidar. then how can we handle it by ourselves with the apollo scripts?
2: what's the difference between lossy_map，lossless_map , ndt_map, pyramid_map.  What's the usage for them？ and what's the relationship for them ?
3: Why the description of the msf README.md that you should use the msf_local_map_creator.sh for the map generate.
but in the file how_to_generate_local_map_for_MSF_localization_module_cn.md that you should use msf_sample_map_creator.sh what's the difference?
Supporting materials (screenshots, command lines, code/script snippets):

Best Regard!

Q1

according to the msf_simple_map_creator.sh described. if you want to generate the localization map . you should take the topic of msf_lidar as a input

msf_simple_map_creator.sh doesn't metioned about need msf_lidar as a input. It need pcds but not msf_lidar, msf_lidar is an intermediate results: Gnss localization result, LiDAR localization result. (ROS topic /apollo/localization/msf_gnss, /apollo/localization/msf_lidar)
Q2

what's the difference between lossy_map，lossless_map , ndt_map, pyramid_map

lossless_map -> lossy_map and used for msf localization  module
ndt_map -> used for ndt localization moudle
pyramid_map -> an code module named pyramid_map
Q3

Why the description of the msf README.md that you should use the msf_local_map_creator.sh for the map generate.
but in the file how_to_generate_local_map_for_MSF_localization_module_cn.md that you should use msf_sample_map_creator.sh what's the difference?

I can't found any info about msf_sample_map_creator.sh in git history. could you pls provide the link?

For Q3,
msf_local_map_creator.sh will take the datasets as input to generate LiDAR map,
while
msf_sample_map_creator.sh (I think you mean msf_simple_map_creator.sh). It takes a record file as input to generate the LiDAR map.
It will extract the data from the record file and then create the map as how msf_local_map_creator.sh works.
Just a difference of the input data format.


When it will going have full support for React 16? Because for now, css is getting disturbed when intergrating with react 16?

+1 here, having CSS issues with react 16

https://github.com/xDae/react-plyr/releases/tag/v2.0.1


Could not resolve project :core

FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
Could not resolve project :core.
Required by:
project :app
No matching configuration of project :core was found. The consumer was configured to find an API of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- None of the consumable configurations have attributes

Closed on 86c15d0


Listen and react to spacy.domain/session-scheduled event in the UI

The components to the following:

bulletin-board (our session schedule) uses transclusion with the h-include
component to reload the whole contents of the schedule whenever the
session-scheduled event occurs: this is the simplest implementation, and I
did it this way because every cell needs to be updated to show the new
"Choose Slot" buttons for the new session which needs to be scheduled
waiting-queue deletes the scheduled session from its list and thereby moves
the next session up in the queue
user-notifications adds a notification to let screenreader users know which
session has been scheduled.

Additionally:

I also switched the order of times and rooms in the table because for the
responsive behavior that I dream of in the future I would prefer to group
the data by time as opposed to room. This could be subject to change though,
because I could change my mind... 😬

Works like a charm!


Make creation of secret configurable

This way users can supply their own secrets so it doesn't have to be stored in a values.yaml
What this PR does / why we need it:
It makes creation of the secret object as part of the chart installation optional.
In our deployment workflows secrets aren't created by helm, they're created separately. I imagine that this is quite a common pattern, as it is not very idiomatic to put secrets into your values file (which is likely checked into source control).

Added usage example in README

Can I get an ok-to-test please?

/ok-to-test

/ok-to-test

/lgtm


Support for nested querydsl path such as embeddables

Won't fix this one for querydsl v3.x.x, unless other devs will handle this one. Will focus now on supporting querydsl 4.x.x, hence rql-querydsl v2.x.x.


Concepts not resolved when a spec is executed

Expected behavior
If a spec and concept are in specs dir, executing specification from specs dir should resolve concept.
Actual behavior
Concept is not resolved
Steps to reproduce

Create a spec hello.spec and a concept in specs dir. This concept should be used in spec.
cd specs
gauge hello.spec

Gauge version
Gauge version: 0.4.1

Plugins
-------
html-report (2.1.0)
java (0.4.0)

In this fix, Gauge always looks for concepts in the whole project, folders starting with dot(.) are excluded and a user can add folders to the excluded folders list by adding a new property i.e gauge_exclude_dirs and pass paths to folders separated by comma(,).
For Example: gauge_exclude_dirs = src/test, bin

The fix will be available in nightly > 13-05-2016


Fix flakes in EnqueueAfter tests

Fixes flakes such as https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative_pkg/1709/pull-knative-pkg-unit-tests/1305911274105737216.
the docs for the Len() function in queue package say:
// Len returns the current queue length, for informational purposes only.

Testing locally, when we see the flake we'll then see the correct length immediately after, so it appears to be caused by inconsistent reads. Directly sending the len to the channel when the poll finishes rather than effectively re-polling an extra time in the test seems to fix up the flakes. Since no-one should be using len() other than for information purposes, this solution seems fine. Ran with -count 100 locally cleanly.

/lgtm
/approve


Request: Option for a 'performance mode' with only formations

Currently this seems to be the only Rimworld mod that has a simple way to drag drafted pawns into formations. Unfortunately some of the other functions related to tasking and forced work are a constant drain on TPS even outisde of combat and thus not always desired.
Could we get an option to disable all the extra functionality, leaving just the drafted positioning/formations?

Please explain the pretty generic “ some of the other functions related to tasking and forced work are a constant drain on TPS ”.

Also, I recommend taking this discussion on my discord as a better way to communicate.

I won't pretend to know what exactly it is, since I don't do C#, but I noticed in Dub's performance analyzer that Achtung is making thousands of calls and takes around 2-5 ms per update (in my particular mod load this places it in the top three of heaviest mods) even when no pawns are drafted and I'm using none of the forced work functions.
Not trying to barge in and make demands or pretend I know things better or anything. I'm just wondering if you could separate the mod's two main functions with either an option in the mod's configuration menu or maybe a "light" version of sorts, because I really like the draft formations but probably will have to remove it from my mod loadout for my optimized late-game bases. I know a lot of other players seek your mod's draft functions above the other stuff. So is it something you could maybe add? Or is it not going to happen?

I prefer to to split up my mods. Makes it more time consuming. I have already put like 20-40 hours in optimization into Achtung and if you mod your game so much that you cannot run Achtung you probably have other problems anyway.
Sorry, I am not going to split up Achtung into several mods. If you don't force stuff it basically does nothing.

Okay, well thanks for considering it!


Purchase Module

Is your feature request related to a problem? Please describe.
Adding new module named 'Purchase'.
Describe the solution you'd like
Create purchase invoices with header, detail, and footer. Header should contains invoice number, date, supplier details. Details section should contains Purchase line items. Footer should contains discount, tax and net amount.

Purchase module added


[ESP32-S3] GPIO High when configured as input regardless of PullUp/Down Setting

let mut int_pin = io.pins.gpio15.into_push_pull_output();
int_pin.set_low().unwrap(); // Low

let mut int_pin = int_pin.into_pull_down_input(); // Immediately goes high

On main branch of esp32s3-hal.
Also see #142

I guess it's just the internal pull-down is not strong enough in input mode?


In-line documentation

I would love to see more in-line documentation, particularly with function docstrings. I think this would accelerate adoption.
Personally, I prefer sphinx docstrings: https://pythonhosted.org/an_example_pypi_project/sphinx.html#function-definitions
This allows the added benefit of adding automatic readthedocs

I agree with this. I think the most important ones are the init params for sampler and runner (and their subclasses). For example; what does world_size in SerialSampler do?
And as a second priority maybe the init params for algos.

Thanks for the feedback, and I agree.  And I've used sphinx for readthedocs in the past and really liked it.  Now that this project is picking up some steam, this is at the top of the to-do list....sorry for the wait!

I am told that @astooke  is hard at work on this! :)

Just a quick note, this issue can be closed. https://github.com/astooke/rlpyt/issues/101


feat: add env package

Closes #87
Adds @acme/env package to have typesafe env's across the monorepo.
Usage

All envs are added in a single root .env. When deploying apps, make sure the deployment has all required envs for the apps and the packages it uses

Define your schema (as well as destruct process.env) like you would in a normal T3 App in packages/env/index.ts.

export const server = z.object({
  NODE_ENV: z.enum(["development", "test", "production"]),
  TEST: z.string().transform((s) => s.length),
});

Then, in every app/pkg which needs to use some env var, pull it in using getEnv

import { getEnv } from "@acme/env";

export const env = getEnv(["NODE_ENV"]);
env.NODE_ENV;
//  ^? development | test | production

// ------------------------------------
import { getEnv } from "@acme/env";

export const env = getEnv(["TEST", "NODE_ENV"]);
//           ^? { TEST: number, NODE_ENV: development | test | production }

Cons

Not sure what the performance hits are - we're mapping over all the keys so for large .env files this might make an impact?

As i set it up now, the Next.js app doesn't use any env explicitely - all that usage is in the auth/api package - so in the current setup we aren't getting validation on build time but the errors come at runtime. This could be solved by just pulling all the AUTH/API envs into the nextjs app too ofc, but it's not the best ergonomics? You could also choose to export the @acme/auth's env and import that in the nextjs app?

Overall this might be the best way to go. A couple thoughts:

It's definitely cleaner DX to have a single getEnv in packages/env like this. My reasoning in having each package/app pass its own schemas (picked from the server and client schemas defined in the env package) to the env package is that way at runtime zod is only parsing the necessary variables for each package, instead of parsing all variables and then sending the ones each package requests. I honestly don't know the performance hit from zod parsing env variables every time they're called - maybe that adds up for larger repos with bigger envs, in which case it might be better to minimize what zod is doing at runtime.

Not sure about best way to do checks at build time. Since the Next.js app is already compiling the auth and api packages at build time, would it be any different to import all the auth and api env variables directly into the app? I can check tomorrow, but I know I've had Next.js builds fail from a missing env variable in API, even though it wasn't directly imported.

This is great! It solves the worst dx on create-t3-turbo at the time. I agree that losing env validation during build time is an issue, but it could be solved by adding a validation that runs on the pnpm run build or pnpm run dev scripts in the package. json and turbo workflow. Would that resolve all of these problems, or am I wrong (I didn't use TurboRepo other than for a few experiments)?

I'll keep this in draft for awhile. This will mess up caching in that one env variable change will most likely bust the entire turbo cache

hello really nice idea, here are some of my thoughts:

env package should bo scopable by different apps
packages shouldn't depend on environment variables

packages shouldn't depend on environment variables

Yea this is the plan to refactor the packages so they are dry

I was thinking also about having a .ts file per application, something like envs.ts
where you can define multiple zod schemas (for client + server environments)
// envs.ts or apps/nextjs/envs.ts

export const clientEnvs = z.object({})
export const serverEnvs = z.object({})

and later:

being able to validate the schemas before you run your app, e.g"dev": "envs check && next dev"

infer the type of the .ts zod schema and continually make it synchronized. i18next has something similar but with JSON filesimport { clientEnvs } from "envs"

clientEnvs.   // <- typesafed list of options

But that sounds more like a new library

Are there any updates on this PR?


DeprecatedFunctions sniff: update minimum WP version

The version number in this property is supposed to be 3 versions before the current WP release and what with WP 4.8 having been released, should now be updated.
I'm not aware of any deprecated functions in WP 4.8, but have to admit that I haven't followed this very closely.
According to the official changelog, there are none: https://codex.wordpress.org/Version_4.8
And I can't seem to get a one-page diff view using trac: https://core.trac.wordpress.org/changeset?old_path=%2Ftrunk&old=40888&new_path=%2Fbranches%2F4.7&new=39524&sfp_email=&sfph_mail= (aside: would be great if there was a way to only get the diff of PHP files at that)
Does anyone know of a clever way to check for newly deprecated functions between releases ?

A search for @deprecated 4.8 reveals wp_dashboard_plugins_output() was deprecated. Appears to be the only one.

@JDGrimes Thanks for that. I've updated the PR with an additional commit adding the newly deprecated function & updating the unit tests. Feel free to squash the commits on merge.

Oh dear... looks like - contrary to the earlier assertion as annotated in the code - there were actually deprecated functions in WP 4.7 as well.
Added these now in - yet another - separate commit.
I'm by no means claiming completeness, just did a quick search on @deprecated 4.7 which would not have caught anything with more spaces between the @deprecated and 4.7. So if anyone feels like doing a more extensive search, please do! and let me know what else you turn up :sunglasses:

I've created a tool to scan a WordPress codebase for all deprecated elements: https://github.com/JDGrimes/wp-deprecated-code-scanner
Currently just detects classes and methods based on the use of _deprecated_function(). Results seem to indicate that we may have missed some other deprecated functions as well.
Currently it just prints the results to the command line in markdown format. I'll see about generating some output with it that is easier to compare with what we have here in this sniff, which will make it easier to compare results and see what the differences are.
It is bleeding edge, so has some bugs still.

@JDGrimes Wow! That sounds really useful - if only for this snifff ;-)
Might be an idea to add the other _deprecated_...() functions at some point as well. _deprecated_argument() will be useful for #826
For easiest compare, I think it would be helpful to have a consistent array order for each of this sniffs and maybe see if your tool can display the lists in the same order ?
I propose:

Deprecated function - Ordered by WP version in which deprecation occurred & order alphabetically on function name within each subset. (I'll fix up this PR and see if anything in the original array needs changing too)
Deprecated function arguments - As noted previously in the ticket, those should be ordered alphabetically to prevent a later deprecated second argument overruling a previous array entry for the same function.

I've created an issue for deprecated arguments: https://github.com/JDGrimes/wp-deprecated-code-scanner/issues/2. I do plan to add checks for hooks as well, etc.

Deprecated function - Ordered by WP version in which deprecation occurred & order alphabetically on function name within each subset.

Exactly what I was thinking.

Exactly what I was thinking.

Re-ordering the array in the sniff as we speak ;-)

It should now be able to generate the output as needed:
bin/wpdcs run --format wpcs /path/to/wp/src

Oh, it will include methods though, not just regular functions.

I've pushed a new commit which sorts out the re-ordering for the functions we already accounted for.
I've also added delimiters between each set within the test case file to make maintenance easier and adjusted the test functions accordingly.
Now we "just" need to do a compare between the output of your tool and the current list in the sniff. @JDGrimes Would you like to have a go at that ? You can add a new commit to this branch with the changes.

Oh, it will include methods though, not just regular functions.

That's for another sniff - see https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/731

Here is an initial diff: https://www.diffchecker.com/BmXjilmq
It revealed several inconsistencies not related to different functions:

For one, there are a few functions that don't have the versions specified correctly in the _deprecated_function() call, see https://core.trac.wordpress.org/ticket/41094.
The versions in WordPress are almost always specified in full, like 4.8.0, but only 4.8 in the sniff. I can change this in the generator, or we can change how we specify the versions in the sniff.
Sometimes the alternative is specified differently than in the sniff now. For example, the sniff is currently inconsistent as to whether parentheses are included; in core they almost always are.
There may be more methods in the sniff's list than we realized, these aren't included in the generated output.

I also noticed some issue with the ordering of the functions - I did the ordering case-insensitively and the functions are declared in the array in lowercase (and compared as such as well).
Is it possible to adjust the ordering in your tool to be in line with that ?

The versions in WordPress are almost always specified in full, like 4.8.0, but only 4.8 in the sniff. I can change this in the generator, or we can change how we specify the versions in the sniff.

I'm in favour of using complete version numbers in the sniff. When I have time, I'll update the sniff if nobody objects.

Sometimes the alternative is specified differently than in the sniff now. For example, the sniff is currently inconsistent as to whether parentheses are included; in core they almost always are.

I'm in favour of using the parentheses in the sniff as well. I checked to see if this could be done generically via the error message, but with some alternatives passing arguments add_theme_support( \'custom-background\', $args ), it can't.
Again, if nobody objects and when I have some time, I'll update the sniff.
@JDGrimes Once I've done the sniff update, could you run a new compare to see how much is left ?

I also noticed an issue with the ordering of the functions - I did the ordering case-insensitively and the functions are declared in the array in lowercase (and compared as such as well).
Is it possible to adjust the ordering in your tool to be in line with that ?

I noticed this as well but forgot to mention it. I'll update the tool to lowercase all of the function names before ordering in this case.

I'm in favour of using complete version numbers in the sniff.

+1

I'm in favour of using the parentheses in the sniff as well.

+1 as well.

@JDGrimes Once I've done the sniff update, could you run a new compare to see how much is left ?

Sure thing.

Okidoki, updates to the version nrs + parentheses/alternatives all sorted.

Great, here is a new diff: https://www.diffchecker.com/E4xhROBg
There are still some differences that aren't just a result of functions appearing in one list and not in the other, particularly in regard to alternative functions:

When a function has an alternative that isn't a function (like "the Loop", for start_wp()), WordPress doesn't specify that as the third parameter of the _deprecated_function() call. So in the sniff it will currently have a value, but the generator will not detect the alternative.
There are some cases where the alternative function in the sniff is incorrect. For example, it should be wp_editor() for tinymce_include(), but is listed as wp_tiny_mce(). I haven't checked other cases to be sure that they are correct.
In some cases the spacing for the alternative functions is different. get_the_author_meta( \'description\' ) in the sniff vs get_the_author_meta(\'description\') from the generator.

It also appears that not all deprecated functions call _deprecated_function(), so the generator currently doesn't pick them up. I'll see about updating it so that it will check for the @deprecated dockblock annotation as well.

When a function has an alternative that isn't a function (like "the Loop", for start_wp()), WordPress doesn't specify that as the third parameter of the _deprecated_function() call. So in the sniff it will currently have a value, but the generator will not detect the alternative.

This should be fine I think, though we might want to verify those instances & annotate in the sniff with a comment that it's ok.

There are some cases where the alternative function in the sniff is incorrect. For example, it should be wp_editor() for tinymce_include(), but is listed as wp_tiny_mce(). I haven't checked other cases to be sure that they are correct.

I'm wondering if some might have a different alternative function mentioned in the @deprecated tag compared to the _deprecated_function() call. Or the alternative may have been deprecated itself ?
Maybe @grappler who originally created this PR can shed some light on this ? There might be a good reason for the difference.

In some cases the spacing for the alternative functions is different. get_the_author_meta( 'description' ) in the sniff vs get_the_author_meta('description') from the generator.

I'll adjust that one - it had a different quote style from what was used in the WP code previously, so I already adjusted it, just hadn't noticed the spaces. Will also check & adjust others for this if there are more.

It also appears that not all deprecated functions call _deprecated_function(), so the generator currently doesn't pick them up. I'll see about updating it so that it will check for the @deprecated dockblock annotation as well.

That would be awesome!
On that note and for future consideration if we want to start sniffing deprecated hooks as well:
I know for a fact that most deprecated hooks do have a @deprecated tag, but hardly any have a _deprecated_hook() call. A patch for this has been untouched for nearly a year, see https://core.trac.wordpress.org/ticket/10441

Ok, so what started out as a simple property value change is quickly becoming quite a large PR with wide-reaching ripples.
I've gone through the complete list of diffs and these are my findings:

One diff in a function name - the_category_ID - is caused by the sniff list being all lowercase (which it doesn't need to be as the sniff accounts for a case-insensitive compare). I will fix that in the sniff.
One function+ it's alternative was missing an _ at the start - _nc not nc. I will fix that in the sniff.
One function is not deprecated at all - wp_dashboard_quick_press, but the alternative for a very similarly named function wp_dashboard_quick_press_output which is deprecated in the version listed. I will fix that in the sniff.
Nine functions were listed as deprecated under the wrong WP version (according to the docs - I haven't checked the commit history). I will fix that in the sniff.
A few diffs in alternatives are due to spacing in the text string. I will fix that in the sniff.
A few diffs in alternatives are due to WP not listing the alternative in the _deprecated_function() call. I will be opening a trac ticket for those.
There are four diffs in alternatives due to the function call in WP missing the braces. I will open an issue in trac for those.
Four alternatives are in actual fact a filter, not a function. The availability of this alternative is not listed in the _deprecated_function() call, nor in the sniff array. I will open an issue in trac to get this fixed up and will apply the same change here in the sniff.
A few diffs in alternatives are due to the sniff array not listing an alternative, while there is one. Or listing an outdated alternative - i.e. the alternative function itself has been deprecated since -. Or just plainly the wrong alternative. I will fix these in the sniff.
There is one class listed in the function array. The class constructor contains a _deprecated_function() call.

I've created a new sniff called WP.DeprecatedClasses to deal with complete classes having been deprecated and will pull that later.
I'll be opening a trac ticket for core to add a new _deprecated_class() function to be used in class constructors for deprecated classes.
None of the methods of the deprecated class currently had _deprecated_function() calls. I will also open a trac ticket to get those added.

There are eight methods listed in the function array - on top of the three which had been previously identified as such. I will add a comment to these referring to #731 which is the related open issue.
There are a number of functions missing from the sniff list. I will add these later.
On top of the three @JDGrimes previously identified in https://core.trac.wordpress.org/ticket/4109 , there are sixteen more deprecated functions (based on the diff) in Core which are missing a _deprecated_function() call. I will be opening trac tickets for these.
Lastly, there are twelve deprecated methods in Core which are missing a _deprecated_function() call. I will be opening trac tickets for these too.

A new diff after I've pushed the changes to the PR would be appreciated, but things should get shiny once the patches for the trac tickets are merged into core.
Once I've opened the trac tickets, I will edit this comment to add links to them.

Just thinking.... maybe we should create a sniff that checks for calls to any of the _deprecated_....() functions and ensures that there is a @deprecated tag and visa versa ?

After discussing this with @pento I've opened just the one ticket containing all the patches: https://core.trac.wordpress.org/ticket/41121

Great investigation @jrfnl - improving Core, from improving the Code Standards. Who says they aren't valuable?! :-)

Secondary ticket opened to propose a new _deprecated_class() function: https://core.trac.wordpress.org/ticket/41125

Okidoki, updates to the sniff have been pushed, so the compare should be a lot cleaner now ;-) @JDGrimes want to do your thing ?
This PR may now conflict with PR #994. As that one is the easier/smaller one, I suggest I rebase this PR after #994 has been merged.

Probably worth waiting on the outcome of https://core.trac.wordpress.org/ticket/41121 before this is approved for merge?

Probably worth waiting on the outcome of https://core.trac.wordpress.org/ticket/41121 before this is approved for merge?

We don't really need to wait, though I would like to see another compare just to be sure I haven't missed anything.
There is some discussion about replacement string styles in core ticket 41121, but - if needed - we can adjust those minor details later. That is, after all, just a minor part of this PR.

New diff: https://www.diffchecker.com/fBGrpxWW

Rebased after the merge of #994 & squashed a number of commits together to tidy up the branch. Also fixed one more alternative function missing braces. @JDGrimes Care to rerun the comparison one more time ?

https://www.diffchecker.com/YiqiNtww

Thanks @JDGrimes. As far as I can see, the remaining differences have to be solved in core and have appropriate tickets & patches, so as far as I'm concerned, this PR is good to go.


explain why the securityContext Privileged is needed

What would you like to be added:
Reading the documentation, I did not find why the:

securityContext: Privileged
runAsUser: 0
are needed.

I do think, that the fluentd tool need to read all the containers logs, and that it need to find a way to catalog the containers to find out in which namespace, pods it runs and what are the label and annotations on these elements.
Could you provide in you documentation a brief summary on why you need such privilege.
Why is this needed:
The security teams often needs to understand the reason/motivation to allow privileged pods to run on the infrastructure.
Informations:
This ticket has a relation with #760

Closing this issue as the discussion has started in issue #760. It will be easier to track only one issue.


Bug: Springboot installation and upgradefail on macOS

Bug report
While trying to either install or update springboot, on macOS it fails with the following message:
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/<user>/.sdkman/archives/springboot-2.5.5.zip or
        /Users/<user>/.sdkman/archives/springboot-2.5.5.zip.zip, and cannot find /Users/<user>/.sdkman/archives/springboot-2.5.5.zip.ZIP, period.

To reproduce

Run either sdk upgrade with springboot already installed or sdk install springboot .

System info

OS: macOS 11.6
Shell and version: zsh 5.8 (x86_64-apple-darwin20.0)
sdk version: SDKMAN 5.12.4

Any help would be appreciated. Thank you.

Hi @npalladium, I've just tried this in a clean environment and can't replicate it. Are you seeing this with anything other than springboot?

Can you try to flush your archives folder and retry installation? Perhaps you have a corrupted cached archive.

I'm seeing the same but with Groovy. Gradle, Java, Kotlin, Micronaut, and VIsualVM all installed fine. But after attempting multiple different versions of Groovy, no luck.
I'm on MacOS 12.0.1 on a new arm-based MacBook Pro. sdk flush archives does nothing.
$ sdk install groovy

Downloading: groovy 3.0.9

In progress...

-#O=#    #      #

  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip or
        /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip.zip, and cannot find /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip.ZIP, period.

Stop! The archive was corrupt and has been removed! Please try installing again.

$ sdk install groovy
Validate groovy 3.0.9 for darwinx64: valid
Validation URL: https://api.sdkman.io/2/candidates/validate/groovy/3.0.9/darwinx64
Get pre-installation hook: https://api.sdkman.io/2/hooks/pre/groovy/3.0.9/darwinx64
Copy remote pre-installation hook: /Users/jamesdh/.sdkman/tmp/hook_pre_groovy_3.0.9.sh
No Mac OSX pre-install hook found for Groovy 3.0.9.
Completed pre-installation hook...

Downloading: groovy 3.0.9

In progress...

*   Trying <IP_ADDRESS>:443...
* Connected to api.sdkman.io (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [227 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [108 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [5651 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=*.sdkman.io
*  start date: May 30 00:00:00 2020 GMT
*  expire date: Apr 28 23:59:59 2022 GMT
*  subjectAltName: host "api.sdkman.io" matched cert's "*.sdkman.io"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
> GET /2/broker/download/groovy/3.0.9/darwinx64 HTTP/1.1
> Host: api.sdkman.io
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Server: nginx/1.19.1
< Date: Fri, 05 Nov 2021 04:35:23 GMT
< Content-Length: 0
< Connection: keep-alive
< location: https://groovy.jfrog.io/artifactory/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip
<
* Connection #0 to host api.sdkman.io left intact
* Issue another request to this URL: 'https://groovy.jfrog.io/artifactory/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip'
*   Trying <IP_ADDRESS>:443...
* Connected to groovy.jfrog.io (<IP_ADDRESS>) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [229 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [108 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3706 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=*.jfrog.io
*  start date: Feb  4 00:00:00 2020 GMT
*  expire date: Feb 18 12:00:00 2022 GMT
*  subjectAltName: host "groovy.jfrog.io" matched cert's "*.jfrog.io"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=GeoTrust RSA CA 2018
*  SSL certificate verify ok.
> GET /artifactory/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip HTTP/1.1
> Host: groovy.jfrog.io
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
> Referer: https://api.sdkman.io/2/broker/download/groovy/3.0.9/darwinx64
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Date: Fri, 05 Nov 2021 04:35:23 GMT
< Content-Length: 0
< Connection: keep-alive
< Location: https://groovy.jfrog.io/ui/native/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip
< Strict-Transport-Security: max-age=15724800; includeSubDomains
< X-Request-ID: fe8f80c444b4b63b67bb182aa9aa043b
<
* Connection #1 to host groovy.jfrog.io left intact
* Issue another request to this URL: 'https://groovy.jfrog.io/ui/native/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip'
* Found bundle for host groovy.jfrog.io: 0x600003234090 [serially]
* Can not multiplex, even if we wanted to!
* Re-using existing connection! (#1) with host groovy.jfrog.io
* Connected to groovy.jfrog.io (<IP_ADDRESS>) port 443 (#1)
> GET /ui/native/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip HTTP/1.1
> Host: groovy.jfrog.io
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
> Referer: https://groovy.jfrog.io/artifactory/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Fri, 05 Nov 2021 04:35:23 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Accept-Ranges: bytes
< Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0
< Etag: W/"3832-17ae92c9920"
< Expires: 0
< Feature-Policy: geolocation 'none';microphone 'none';camera 'none';payment 'none'
< Last-Modified: Tue, 27 Jul 2021 18:14:12 GMT
< Pragma: no-cache
< Referrer-Policy: no-referrer
< Surrogate-Control: no-store
< Vary: Accept-Encoding
< X-Content-Security-Policy: script-src 'self' cdn.heapanalytics.com www.google-analytics.com 'nonce-1yewb4nptf' 'unsafe-eval'; font-src 'self' data: https://heapanalytics.com; base-uri 'self'; style-src 'self' 'unsafe-inline' https://heapanalytics.com; form-action 'self'; frame-ancestors 'self'
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
< X-Xss-Protection: 1; mode=block
< Strict-Transport-Security: max-age=15724800; includeSubDomains
< X-Request-ID: 9ad1de24094f3e715e1592a860999aba
<
{ [377 bytes data]
* Connection #1 to host groovy.jfrog.io left intact

Downloaded binary to: /Users/jamesdh/.sdkman/tmp/groovy-3.0.9.bin (HTTP headers written to: /Users/jamesdh/.sdkman/var/metadata/groovy-3.0.9.headers)
Get post-installation hook: https://api.sdkman.io/2/hooks/post/groovy/3.0.9/darwinx64
Copy remote post-installation hook: /Users/jamesdh/.sdkman/tmp/hook_post_groovy_3.0.9.sh
No Mac OSX post-install hook found for Groovy 3.0.9.
Moving /Users/jamesdh/.sdkman/tmp/groovy-3.0.9.bin to /Users/jamesdh/.sdkman/tmp/groovy-3.0.9.zip
Processed binary as: /Users/jamesdh/.sdkman/tmp/groovy-3.0.9.zip
Completed post-installation hook...
Moved to archive folder: /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip or
        /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip.zip, and cannot find /Users/jamesdh/.sdkman/archives/groovy-3.0.9.zip.ZIP, period.

Stop! The archive was corrupt and has been removed! Please try installing again.

It appears the downloader may be getting JFrog's index page + redirects mixed up with the actual binary somehow?

@marc0der is there a way to prevent sdkman from removing the corrupt archive? I'd like to take a closer look at it.

Also, FWIW, I'm also seeing the same issue with springboot.

Hi @jamesdh,
I suspect that you have some proxy issues. I tried installing both Groovy and Spring Boot on a clean docker container and experienced no problems. I also tried using curl to download the binary directly, which works fine for me.
curl -O https://groovy.jfrog.io/artifactory/dist-release-local/groovy-zips/apache-groovy-sdk-3.0.9.zip

Please feel free to chat with us on Slack if you have any further issues.

I was experiencing this issue because my .curlrc file defined a user-agent. That, in turn, broke curl (v7.77) somehow when making a request against jfrog's servers.

I was experiencing this issue because my .curlrc file defined a user-agent. That, in turn, broke curl (v7.77) somehow when making a request against jfrog's servers.

I set the user agent for curl in the ~/.curlrc file. Curl impersonated as a browser. Now when you send a request to the JFrog server, it delivers an intermediate page before the download starts. This JFrog page needs JavaScript to be executed to start the download. If you disable JavaScript in the browser, you have the same behavior as SDKMAN.
In the curl (v7.81.0) help I found a switch to ignore a .curlrc file. This could be a possibility to avoid this kind of errors.
curl --help all
...
 -q, --disable            Disable .curlrc
...

Getting rid of the user-agent from .curlrc fixed it for me. Thanks a bunch @martinreck!

Glad to hear that this is resolved. Closing this issue for now.

@marc0der I'm not sure I'd consider this resolved. I think @martinreck's suggestion about ignoring the .curlrc from the sdkman scripts is a great idea. Otherwise you're going to see this issue reappear in the future from another user experiencing it, especially given how vague and unrelated the error messages are.

@jamesdh I don't think that ignoring the curlrc is a viable option. Curl is a standalone system binary that is not provided or managed by SDKMAN. Many people rely on this file to configure proxies etc, so it would cause many problems if we ignored it.
One thing we could perhaps consider is to have a copy of the curlrc in our etc folder that takes precedence over the one in the home directory. I'd consider this as a new feature request.
For now, I'd say this bug report is resolved as I don't see it as a bug but rather as a user configuration issue.


Various build fixes, including fixes to minimum version requirements

Tested with:
cargo +nightly update -Zminimal-versions
cargo check --all-features
cargo +nightly check --all-features --all-targets

Addresses #297.  Ideally this would be tested in CI.

Build failure with rust 1.60 is unrelated; the following runs fine:
cargo +nightly update -Zminimal-versions
cargo +1.60 check --all-features

Well, have you run the above comment on workspace?

Yes. The command in the first post is the motivation for this PR, it didn't run in master, with correctly specified dependencies (proc-macro2 and trybuild) it works.


wrong sdo reply result, when sending rpdo at fast rate

I'm having this very strange issue when reading sdo and sending sync pdo at the same time.
Basically what I'm doing is sending rpdo at 2ms interval time to 0x4000 0x00 od. Meanwhile reading 0x4000 0x00 with sdo. 2 out of 10 times, it returns wrong reading. the data part of the sdo reply is exactly the same as the request i sent, with only cob-id difference.
it seems like inside the stack something is not properly lock protected.

Can you share some more information, which version and which target (driver) do you use.

SHA-1: 41e982962e1be83ef13707e28b1221a07f5ffb40

Merge branch 'odesenfans-common-header-for-drivers'
18/12/2019
We are using this commit, I know it's quite old, but it works so we didn't update to latest version.

https://gist.github.com/npk48/69e6a79acf0c0dfdf2741937db463e37
and the driver we are using for stm32f4

There is probably problem in the driver or with the main() function. Unfortunately I cant help with the driver or example for STM. Those drivers wasn't maintained, so they was removed from newer versions. Please check CO_LOCK_OD() macros. You can also look into CANopenPIC, PIC32 for reference.

I have checked the driver
c #define CO_LOCK_OD()            __set_PRIMASK(1); #define CO_UNLOCK_OD()          __set_PRIMASK(0);
the lock is properly defined by masking the global interrupt flag.
Maybe we need to lock this in the main while loop for sdo processing manually?

It is necessary to lock all functions in fast timer thread (CO_TPDO_process, etc) and each OD variable access from mainline. SDO server already have the lock.
I have recently documented better the locking mechanism. Please see here:
https://github.com/CANopenNode/CANopenNode/blob/fc817770974e31656eea89998f4f2c612432528a/301/CO_driver.h#L389


[reflection] cleanup derive_reflect

Objective

The current derive_reflect implementation is a large function with difficult to follow code paths.
When determining the "active fields" (e.g. those that don't use #[reflect(ignore)]) the logic is unnecessarily complex.

Solution

Refactor derive_reflect by breaking into into smaller functions, and simplifying the logic for obtaining the "active fields".

@MrGVSV @jakobhellermann can I get a review on this from one of you? I think this is an easy win.

Because Nathan has been busy lately, I'm going to bias towards doing follow-up in future PRs :)

bors r+

@NathanSWard, any chance you'll have a chance to fix this up in the next week or so? If not, no worries. We'll open another PR off this and credit you.

Is this PR made obsolete by #4712?

Agreed. I'm going to close this out in favor of #4712. @MrGVSV can you credit the work done here in your PR description :)
Nathan did great work here; it's our bad for having let it sit in backlog for so long.

@MrGVSV please credit the work done here in your PR description in whatever form you see fit :)

Yeah that's my bad for not recognizing this prior work already. I'll definitely add a note to the PR description tonight. Thanks for pointing this out!


Update form with PDF mappings

🔗 Pivotal Tracker ticket

✍ Description
Updated form with more field definitions, fixed typo in dayCareAddressStreet
📷 Design reference

✅ Completion tasks

[ ] Added relevant tests
[ ] Meets acceptance criteria

@ShaynaCummings I just set up the review app to sync with this branch


BEST_checkpoint_r101.tar     fine tune

how can I use  BEST_checkpoint_r101.tar  and go on learning?
when I used BEST.tar I got this error
AttributeError: 'DataParallel' object has no attribute 'src_device_obj'

you need to use .module attribute when your model is wrapped in a DataParallel objetc


How to specify resource limits/requests for the etcd-cluster-backup-sidecar?

The pod creation fails with message
Error creating: pods "etcd-cluster-backup-sidecar-4275925802-" is forbidden: failed quota: security-rq: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
I think the cause is

If quota is enabled in a namespace for compute resources like cpu and memory, users must specify requests or limits for those values; otherwise, the quota system may reject pod creation.

backup sidecar pod fails

You can set in:
backup:
  pod:
    resources

https://github.com/coreos/etcd-operator/blob/master/pkg/spec/backup.go#L34

@hongchaodeng thnx


"Need at least one mount" when trying to vendor fontawesome

Hi, and thanks for creating this hugo module :)
I've run into a problem when using github.com/hugomods/icons/vendors/font-awesome as a module. My build system (nix) does not allow downloading anything during a build, so the dependencies need to be vendored. But when I use hugo mod vendor, I get the following error:
Error: cannot vendor module "github.com/hugomods/font-awesome", need at least one mount

This also happens when I manually put this in my hugo.toml
[module]
[[module.imports]]
    path = 'github.com/hugomods/font-awesome'
[[module.imports.mounts]]
    source = "svg/brands"
    target = "assets/icons/font-awesome-brands"
[[module.imports.mounts]]
    source = "svg/solid"
    target = "assets/icons/font-awesome-solid"
[[module.imports]]
    path = 'github.com/hugomods/icons'

I also found that this seems to be a more common problem with Hugo/Go (see https://github.com/gohugoio/hugo/issues/10123)
I'm unsure how to work around this since I am not very familiar with Go module internals. Is there a way to create a mount that makes hugo mod vendor happy?

Yeah, that's a known issue about vendoring modules, perhaps we can make a dummy mounting to skip this limit, but I'm not sure.

Add a dummy mounting folder, should work now.
Please upgrade to latest version and vendor again, you'll need to remove the _vendor folder first.

There maybe other modules without mountable folders, please open an issue on related repo if you need it.

hugo mod vendor works like a charm now, thanks :)
Still can't get it to work with Nix' buildGoModule (probably because I'm configuring it wrong), but the in-source vendoring allows me to use the module to this is fine for now :)


Capture call stacks in allocation samples

Add a lock around usage of the SamplingHelper name cache(s).  Clear the volatile cache when capturing an allocation sample call stack.  Share out the code for parsing call stacks in C# to read this new data.  The FrameCallback (that can only take one parameter) now takes a new type to distinguish that we want to use the global name cache but an AllocationTick-local buffer to write data into, while the original CPU sampler wants something slightly different.  This (separating name cache from buffer management) will be refactored in a followup PR rather than polluting the locking changes further in this one.

@johnbley, code looks good, but there is some compilation issues on Linux.


Rheem water softener

Added my rheem water softener and a device is not showing up

This is the app I am using

Is this only for ecowater brand?

Ecowater have separate API and integration (https://hacs.xyz/docs/repositories/integration/barleybobs_homeassistant_ecowater_softener). I have Viessmann Duo Smart, this is Ecowater OEM and works with iQua app. Can you check HA logs for some errors? Have you double checked entered data?

Ok! I got it figured out. Username is in email format. Didn't have the @
initially! Shows everything now! So excited to have this in home assistant!
Thank you again
On Tue, Aug 16, 2022, 7:30 AM arturzx @.***> wrote:

Ecowater have separate API and integration (
https://hacs.xyz/docs/repositories/integration/barleybobs_homeassistant_ecowater_softener).
I have Viessmann Duo Smart, this is Ecowater OEM and works with iQua app.
Can you check HA logs for some errors? Have you double checked entered data?
—
Reply to this email directly, view it on GitHub
https://github.com/arturzx/homeassistant-iqua-softener/issues/2#issuecomment-1216571785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEENN4DN4GYU4OJBEKZUHRDVZOCX7ANCNFSM56VRDJZA
.
You are receiving this because you authored the thread.Message ID:
@.***>


You might want to try Cypress circleci orb

https://github.com/abhinaba-ghosh/cypress-react-selector/blob/6aed4f9597fab16b6bf48f69aa55158c84855425/.circleci/config.yml#L19
https://github.com/cypress-io/circleci-orb

Hi @bahmutov Thanks for the suggestion.  ORB is integrated here https://github.com/abhinaba-ghosh/cypress-react-selector/pull/7
Appreciate if any feedback for https://github.com/cypress-io/cypress-documentation/pull/2771
Many thanks.


Cannot set custom baudrate on Linux.

I tried to apply this following code into the node-serialport module, but still with no success...
https://jim.sh/ftx/files/linux-custom-baudrate.c
I saw you left a message on the code of serialport_unix.cpp, however it is still not clear to me:
// On linux you can alter the meaning of B38400 to mean a custom baudrate...
Another option could be to change termios.h for asm/termios.h and use a termios2 struct but that would break many other things in chain.

So what custom baud could you not acheive? On which linux distro and architecture, node and serialport versions?
That comment appears to mean you could alter the cpp (not js) source code (and rebuild source) to change B38400 to say B1500000
Yeah large refactors of platform src are unilkely currently as were currently in a node working group to try to solve some of these cross platform hardware issues.

Thank you jacobronsenthal for your answer.
I did a similar workaround, now I call the new version of termios by the re-compiled cpp.


fields for passwords now grouped together

Connects #238

This doesn't appear to fix the issue:

I want the password and password confirmation fields stacked on top of one another; not separated by the time zone field anymore.


feat(server): add req and res to SSR context

PR Details

Description
Add req and res to SSR server context.
Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

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


Consider using a different suffixes for GAPIC generated class name

Currently we use Api suffix for class name. So gRPC service name is Library, the generated class is LibraryApi.
Internally we got feedback to rename this. Probably Client is fine, so LibraryClient?

Assigning @swcloud for triaging.
Cc: @bjwatson
Also cc @blowmage @quartzmo this could potentially mean regenerating files in google-cloud-ruby.

Additionally, we don't like Service suffixes on multiple service definitions (like TraceService service in trace API or LoggingServiceV2 service in logging API). We may want to do what Golang do -- removing such common patterns, so that it would be TraceClient instead of TraceServiceClient.
This is not a part of the internal feedback, but just my personal feeling.

Let's wait for feedback from @anthmgoogle before proceeding.

The revised plan was to standardize on Client for all 7 languages.

I added checkboxes for all the languages. IIUC, this has already been done for Go, correct @pongad and @jba?

Go has been using "Client" since day 1 (well, close enough). I'll mark Go done.

Thanks @pongad!

C# is also done. Java, Python, NodeJS, Ruby and PHP need to be changed.

Thanks @anthmgoogle. I've checked the C# box.

not closed fully :wink:

Java done.

Node.JS done.

PHP done

All languages done - closing


could pushing the spray bar twice give a different message?

"The personnel decontamination system blasts you with a phenolic-smelling spray." could become "You've already done that. You don't need to, again." Or maybe there is an opportunity for a small joke.

This stuff is pretty nasty...
[or]Your skin sizzles and eyes burn from the caustic spray[stopping].".


[RFC]: Add C implementation for @stdlib/stats/base/dists/pareto-type1/mean

Description
This RFC proposes adding a C implementation, including a Node.js native addon, C benchmarks, and C examples, for the @stdlib/stats/base/dists/pareto-type1/mean package.
When adding support, the following tasks should be completed:

A C source implementation should be added to a src folder within the package's directory.
A native add-on interface should be added in order to call the C implementation from JavaScript.
A JavaScript file should be added to the lib folder to allow benchmarking and unit testing the native implementation from JavaScript.
A new test file should be created which includes unit tests testing against expected behavior.
C benchmarks should be added which measure performance for the C source implementation.
A file containing C examples should be added to demonstrate example usage.
JavaScript benchmarks should be added which measure performance for the native add-on.
Build and configuration files should be added to allow compiling and running the C source implementation using project make commands (as documented below).
The README should be updated to include documentation for the added C API.

To provide a concrete example of what a PR adding the desired method should contain, see https://github.com/stdlib-js/stdlib/pull/3354, which is a PR adding a C implementation for the CDF of an arcsine distribution. This should provide an idea of what is expected.
Prerequisites

Review JavaScript implementation in lib/main.js and its required modules to identify all stdlib functions used.
Verify C implementations exist for each required function.

Related Issues
#3355
Questions
No.
Other
Once the implementation is ready including C examples and benchmarks, we should be able to run the following make commands.
Build native add-on
NODE_ADDONS_PATTERN="@stdlib/stats/base/dists/pareto-type1/mean" make install-node-addons

Run C examples
make examples-c-files<EMAIL_ADDRESS>
Run C benchmarks
make benchmark-c-files<EMAIL_ADDRESS>
Run JavaScript benchmarks
make benchmark-javascript-files<EMAIL_ADDRESS>
Run all tests
make<EMAIL_ADDRESS>test

Notes

If you are interested in contributing a PR which addresses this RFC and are a first-time contributor or not yet familiar with our project conventions, please minimize the submission of LLM-generated code. Please consult our contributing guidelines and the associated development guide. Failure to respect project conventions will result in your PR being rejected without review. Thank you for understanding!

Checklist

[x] I have read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] The issue name begins with RFC:.

@Planeshifter , I am first time in this organisation , Can you help me understand the organisation and how can I contribute here


sysfs: clean paths lexically before use

This is intended to close #2321.
W.r.t. security, after consulting the other maintainers, we must say that fully sandboxing our WASI implementation is beyond the current scope of the project. This will be made explicit in the documentation.
We consider Wasm a mature specification, and security issues against our implementation of it will be taken seriously. WASI is not as mature, nor is our implementation of WASI preview 1.
We also provide advanced enough APIs that you can use to implement your own, better locked down, alternative to our WASI implementation.
That said, this PR still sides with breaking POSIX path resolution semantics in WASI vs. allowing trivial root mount escapes, by using path.Clean to lexically clean all paths before use.
This is a judgement call.
Handling paths lexically is easier to reason about, easier to port, and idiomatic Go. Go provides  path.Clean and filepath.Clean; fs.FS is even stricter disallowing .. entirely. It's also unlikely to break well, behaving, useful applications.

Sorry for coming to this so late, was just randomly thinking about this for some reason even before seeing this new PR.
I think to correctly handle symlinks, we would need to recognize them when opening/statting and use the resolved name recursively through the WASI apis rather than directly opening, likely with a recursion limit if not real cycle detector though that's likely too much.
I think cleaning paths still doesn't prevent the case where a symlink outside the sandbox is present in the mounted files. Naturally this is a far smaller issue than being to create the symlink in wasm itself.
I understand that the WASI implementation won't be fully hardened which makes sense, so the above might be going too far. But just wanted to share in case it didn't seem too hard, but probably is.

Sorry I noticed the comment is about 3) in the issue, and is probably too much so no worries

No worries. Yeah, that sounds like doing path resolution ourselves, maybe with some shortcut. But I honestly don't think there's any shortcut possible.
ISTM that to do path resolution, you really need to start at the root (there's no CWD in WASI preview 1), then for each path element do readlinkat to possibly resolve a symlink, then openat(NO_FOLLOW), then fstat to see if it's a directory, and on to the next element. If you don't have NO_FOLLOW, you have a race. I have no idea about Windows.
That's a lot of syscalls, and a lot of stuff to get wrong, especially if you're doing this for sandboxing/security sake.

ISTM that to do path resolution, you really need to start at the root (there's no CWD in WASI preview 1)

I might not understand the syscalls right, but I didn't really expect CWD to be needed. I thought it could be something like this pseudocode similar to checking whether opening a file matches isDir
https://github.com/tetratelabs/wazero/blob/main/imports/wasi_snapshot_preview1/fs.go#L1619
f, ok := fsc.LookupFile(newFD)
if symlinkTarget := f.File.SymlinkTarget(); symlinkTarget != nil { // Calls `os.Lstat` or `os.Readlink`
  _ = fsc.CloseFile(newFD)
  return doPathOpen(symlinkTarget, etc...) // The contents of pathOpen after pathName is computed from wasm arg
}

The biggest problem is that it seems like a fairly large change to have to add symlink lstat to the File interface, and anyways indeed could be missing something here so something simpler seems fine, just wanted to make sure the idea got across.

CWD is not needed because WASI preview 1 has no concept of CWD.
By the time you get to those lines the file is already opened, and path resolution already happened. The file is opened here:
https://github.com/tetratelabs/wazero/blob/111c51a1bd5acfd1e91afe489d28e52136a3e6d5/imports/wasi_snapshot_preview1/fs.go#L1610
The lines you're quoting are really only checking if you opened what you wanted to open (a directory) after the fact. That's good because “ask for forgiveness instead of permission” avoids a race.
But this doesn't work for symlinks for two reasons:

You don't open a symlink; you stat it with lstat, or read it with readlink, but you can't open and then fstat it, because by then you opened the target; on some platforms, you can say you don't want to open the target, with O_NOFOLLOW, on others not even that.
Symlinks in the last path element are the least of your worries; what you should really be worrying about is directory symlinks in the middle; and those can be symlinks that have been moved around to point to different things than when they were created.


📃: Music Player

🔴 Title : Music Player
🔴 Tech stack : HTML , CSS , Javascript
🔴 Objective : A music player with the following functionalities:

Play, pause, next, and previous track controls
Shuffle and repeat modes
Music slider for tracking progress and controlling playback
Ability to play specific songs one by one
A playlist for selecting tracks

🔴 Summary :
📸 Screenshots
N/A

✅ Details to Include When Taking the Issue:
Name :  Saurabh Sahani
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.):

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

@iamrahulmahato, please assign this project to me.

you can assign this task to me..

@iamrahulmahato, please assign this project to me.

the project is already present so i am closing the issue, Do not get demotivated and raise new issue


Migrate to the Azure cloud adoption framework

Fix #167

Note to self: this PR isn't taking the GitOps workflow into account, so automatic deployment will fail

This should be the solution for reading the output of Terraform, and using it in the GitOps workflow: https://blog.nillsf.com/index.php/2020/08/25/how-to-use-terraform-output-in-a-github-action/


How to Configure Reviewers for Esclation

In the Escalate section, it says, "Escalate: ...you can choose who else in your organization should review the message. Choose from a list of configured reviewers..." Can you please add information to this article on how to configure the list of reviewers for this action? Thank you!

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

ID: 685ef016-8eaf-a40d-73af-0fc28e072e41
Version Independent ID: 8fbf5517-d2bc-12eb-79d0-8209130e29ec
Content: Investigate and remediate communication compliance alerts - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/communication-compliance-investigate-remediate.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@EricaToelle - thanks for the feedback. When you use the policy wizard as outlined in the Configure communication compliance in Microsoft 365 (https://docs.microsoft.com/en-us/microsoft-365/compliance/communication-compliance-configure) topic (Step 4), you select reviewers available for selection later in the escalation workflow for each alert. I'll clarify in the topic that this is where these contacts are configured. Thanks!


Fix two duplicated words and...

Fix two duplicated words and improve the phrasing of one sentence to
remove the appearance of a duplicate word.

Done.


Navigation Unusable on Panasonic TV 2019 MT5813 FVP

Describe the bug
Not tested on other devices, but we have observed the menu being far more skippy than the situation in #11, to the point of unusability.
To Reproduce
Steps to reproduce the behavior:

Launch EPT on Panasonic TV 2019 MT5813 FVP.
Attempt to Navigate Menus.
Observe Major Skipping of Elements.

Expected behavior
Menu is navigatable as would be intuitively expected.

@ShiningTrapez what commit closed this issue?

Hey @JohnPaulHarold, this was closed in https://github.com/bbc/lrud-spatial/pull/25. The issue wasn't device specific


Sending Pre-Compressed Buffers?

Would it be possible to send pre-compressed data? i.e. if one caches messages one could cache the compressed version in order to avoid compressing during every send?
e.g.
Instead of:
cache.set(key, buf)
// ...
for (const socket of sockets) (
  socket.send(cache.get(key)) // compressed by uws
}

cache.set(key, zlib.deflateSync(buf))
// ...
for (const socket of sockets) (
  socket.send(cache.get(key))
}

This would enable 2 things:

Re-use compression
Move compression to other thread

If this is possible to implement I would consider funding the work.

Yes it is possible. It was the behaviour in v0.14. But doing more investigation I found that, this was very poor for both compressive performance, and for CPU performance.
My first idea was that sharing a compressor would be best, but the cost of compressing is directly (linearly) correlated with the difference from what you have in your sliding window and what you are compressing.
This means that dedicated (per connection) compression is both faster and obviously compresses better.
If the difference is minimal, compression costs almost nothing. If the difference is total, it's slow as a snail.
Most who use compression prefers the dedicated compression. So the shared pub sub compression was removed (because of complexity and added work of keeping multiple variants of the outgoing data).
Adding something like a shared compressor (only) for pub sub is most likely doable

+1


Knex compatibility

I'm getting the following errors when using with knex.
Im using the database export from the pormise.js file

statement.run is undefined. i noticed this when running knex.raw()
types are not exported of promise.js so in a ts file import Database from 'libsql/promise'

Promise types were added in https://github.com/tursodatabase/libsql-js/commit/f7d550ff8844a7a0d24abe2dde71c23163609116


Remove support for WARN

The only reason to have WARN is that some tests are not fully implemented.
Fix all of them and remove the WARN error message.

Please elaborate on that here. I don't think it's true

The idea behind WARN was to indicate 'optional' configuration which may fail, but not vital for TXT.

@PatrickRudolph Please elaborate on that here. I don't think it's true. Which tests and what isn't fully implemented?

All tests that are marked NonCritical: true.

The idea behind WARN was to indicate 'optional' configuration which may fail, but not vital for TXT.

If it's not vital, why would you test it then?
Reading the comment above WARN:
// ResultWarn indicates that the test failed for the standard configuration but can still be valid in a different configuration of TXT
I wonder what the standard configuration is?
Should we list at least all non standard configurations on WARN until the test is able to detect them and return FAIL or PASS?
Something like
Test A: WARN

This can happend when .... is configured.
This can happend when .... is not present.
...

If it's not vital, why would you test it then?
You may want to check if the PO index is configured correctly, or if a Policy is in PO index. If check passes, everything is ok. If not, it is not vital.

Different story for PS index. If this one is configured wrong, or the policy is not valid you miss the minimum requirements for running TXT

Simplest fix would be to let the user specify what the "standard" configuration is. It must be specified as command line argument. Knowing that there's no optional configuration any more.
A configuration can be one of:

Developer mode
TXT Ready
TXT FIT Boot HASH autopromotion
TXT FIT Boot policy
CbnT
Running in MLE


Use runEffectRec to avoid stack overflows

This is the proper solution to #24 and #25

Tested, works nicely on a test suite I tried. I presume you had issues with Neodoc tests?

Yup it's about 1k worth of tests :)

... so much for "if it compiles it works" ;)

Haha, yeah ;)
Den 11 feb. 2017 8:37 fm skrev "Felix Schlitter"<EMAIL_ADDRESS>
... so much for "if it compiles it works" ;)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/owickstrom/purescript-spec/pull/40#issuecomment-279127845,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZYCKrZ1fu_N_-o10Eun5NhVX-FRvuxks5rbWVPgaJpZM4L-DT8
.


vbnullstring as parameter causes error

First of all thanks very much for this Library! Not sure if this is by design or if my usage is wrong, however if I pass a vbnullstring or "" as a parameter an error occurs.
The line below in AdoParameterProvider results in the size property of the ADO parameter defaulting  to 0 for empty strings. The size property is not allowed to be 0 for string types (at least not in what I am using it for) and causes an error.
If IsCharMapping(Result.Type) And Len(Value) > 0 Then Result.Size = Len(Value)
I have fixed the issue in my project by changing the line to:
If IsCharMapping(Result.Type) Then
     If Len(Value) > 0 Then Result.Size = Len(Value) Else Result.Size = 1
End If

Is there a better way?

Setting a minimum size of 1 seems like a sensible default indeed!


Use of unresolved identifier

Have you installed everything correctly? Have you read through the documentation and contribution guidelines?

Closing this out for now. If you still feel this is a bug, please update this issue and I'll reopen if necessary. If you feel like you need general support, please ask a question on Stack Overflow.


can not make it work with latest angular 2 project built with angular cli

can not make it work with latest angular 2 project built with angular cli

We are using this all the time in project build with angular-cli and we try to keep our project up to date with all the angular-cli changes, but I can try with newly generated project.

At least it works for me in new project created with angular-cli beta18 + angular 2.1.2. Make sure you have a fixed height with the scrollbar area (by using flex or static height etc.) otherwise you don't get scrollable area.

I am closing this for now, if you are sure there is a problem with the library and can provide me an example code then I can re-open this.


Allow stored item data in chat cards to contain active effects

I was working on an project using dnd5e which required me to store temporary item data in chat cards rather than relying on an actual item that exists on an actual actor.
This worked fine because of our chat card framework supporting the possibility of storedData = message.getFlag("dnd5e", "itemData") on the chat message itself, but this broke down if that item contains active effects which should apply to its usage because the case "applyEffect" handler required the effect to be retrieved by uuid rather than using a local id within the item.
This change prefers an effect local to the item of the chat card rather than a UUID lookup.

Technically this fixes a bug since the current implementation prevents applying effects from a consumed scroll.


Offline Caches & Configuration

Addresses #5.

Adds a large change involving game cache file management, configuration management, their associated UIs.
Adds a helper script that can be compiled into an executable that runs in Windows systems, which is used to handle cache operations.
Adds validation to modal screens that disable the save button until all the inputs are properly formatted.
Enables the download, repair, hash checking and removal of all cache files belonging to all game versions.
Enables the addition, deletion, and editing of game versions, with best-effort hash checking and download functionalities.
Enables UI-based config changes.

Apologies for the wait, and thank you for your contribution!
Currently OpenFusionClient is being reworked to use the latest version of Electron. While I do have a mostly working build right now, currently it doesn't include the changes made in this PR.
I would prefer to wait until that updated version is released to merge these changes, as there are a few things that this PR will benefit from such as a settings menu, etc.
Again sorry that this is taking a while, I have been busy with work and moving. Hopefully we can get this addressed soon.

Win 10, as well as Wine/Bottles were tested. I didn't really try on a Win 7/8/8.1 VM yet, but I don't see why it wouldn't work for those.


module 'comfy.sample' has no attribute 'prepare_mask'

The error that occurred this morning.What is the reason for this?

Update your AnimateDiff-Evolved, ComfyUI had an update.

Thank you, the problem has been resolved. I have found that I am using an older version on Gitcode

Same problem!
ComfyUI: 2119 (2024-04-08)
Manager: V2.16
ComfyUI-AnimateDiff-Evolved - updated just now (delete from custom node folder and reinstall)

log.txt

Oops you already included it, my bad

@Aljnk uninstall AnimateLCM, it's not needed for anything and is just a copy of my code but not maintained.

Super - work. Thank a lot :)

Hi, I've had the same problem and I've done an update of all the extensions


Purpose of location value on node

I am working on a project that involves a lot of manipulation and adding to the original tree that comes into the service.
I am a little bit scared to try and handle all edge cases when I am inserting and moving nodes around so I am trying to use as much of the original tree as possible rather than error handling on every single attribute.
Is there any risk with having the “location” value out of order within an array or within a branch of a tree?
Is there any risk of not having location declared on a node at all?
The deparse method does not seem to care, but want to make sure.

You can leave the location field empty (causing it to be 0), or set it to -1 (which is what Postgres uses when the location is unknown).
The location doesn't matter at all for passing things into the deparser, so it shouldn't be needed for your use case.
Its originally intended to provide the user context of where an error in the query occurred (i.e. when parsing an error is hit), has some use in the pg_stat_statements normalization, and in pg_query some users make use of it when trying to figure out where in the source query a particular AST item is. But all of that doesn't matter for passing things into the deparser.


Tests/full improvements

[x] tests/full needs more space (real fedora upgrade test happens) -> go for 40g
[ ] tests/run/permissions requires root for some use case -> fix that test and tests/full to test both cases
[ ] be really explicit about BRANCH= and how test work (it doesn't respect local changes at all)
[x] add make vmtest target to inject local changes into test/full without the need to push to github
[ ] do not submit testcloud images

Might be simplified depending on #1379 outcome

@happz If all goes good make vmtest should be the way to test local modifications in VM.
If you run into more issues with this tests/full please comment here.

Pushed here so I don't loose it. Should pass but we will see.
Added use case for local modifications without git push
cd tests/full
make test

When I ran this as make test when it was based on top of current 'main' branch it finished with total: 1 test passed.

Would be nice to merge to the type-annotations-staging branch so we can run testsuite from there more easily

Fedora 35 issue is expected

Fedora 35 issue is expected

Fixed in TF, rerunning, image got expired ...