Remove alt text from Github Images

The alt text from the github fork/star/etc. images is showing up with the NPM package search description, so the alt text needs to be removed.

@nebrelbug Could I call dips on this one!

Sure! Thanks for helping! I'm sorry I didn't respond sooner.

Closed by PR #8. Thanks @psycho5 !


Inline the #finishRendering helper in TextLayerBuilder.prototype.render

This helper method is simpler/shorter than it originally was[1] and with recent refactoring so is the render-method, hence we can just inline this code now.

[1] It used to e.g. dispatch the "textlayerrendered" event.

/botio integrationtest

Thanks!


Data interpretation logged by tensorboard_log

Thank you for interesting simulator!
I checked run_vision_ppo.py by following command.
python3 -m python.run_vision_ppo --render 0 --train 1
And, I found data when they train in the envtest/python/saved directory (e.g. PPO_1, PPO_2). I found some policies when they're training(/policy), and Test Trajectory(/TestTraj).
The questions I would like to ask is as follows.

where is the logging of reward transition when they train?
what does each axis means in the graph of  TestTraj/Plots?
which code define the parameter of plotting or logging?

hi,

the training reward is logged in tensorboard. you can to to saved and run

tensorboard --logdir=./

the plots in the first row are position [x, y, z] and the plots in the second row are velocity [x, y, z]

the plotting is done here

Which directory should I run this command tensorboard --logdir=./, or should I run this command b/f I run python3 -m python.run_vision_ppo --render 0 --train 1`?

I move to a directory of saved/PPO_(num) and I run tensorboard --logdir=./ then I can seer transition of each reward.
Thank you!

@yun-long
I have one question about interpretation of TensorBoard.
I can see rewards transition when I learns in the simulation, but I do not know how what does it means.

I think the reward is a sum of reward of each episode, Is it correct?
Is this rewards a rewards when agent trains? or rewards when agent evaluate?

Hi,
the reward you see on Tensorboard is from here.
In summary, contains the sum reward and each individual reward component. The reward is a training reward, not an evaluation reward.

Which code does write these rewards to TensorBoard?

hi
the code is here

Thank you!


Added Lithuanian dictionary extension

Followed this CONTRIBUTING.md
Added seattle.md sample in Lithuanian
Built and tested it. Spell checking works on Lithuanian seattle.md sample.

Just a few questions:

Should I change version numbers and if yes which ones:

Do I need to edit files like: README.md, release-please-config.json, manual-publish.yml and etc. to add that new extension is available or is it done by maintainer or bots automatically? If not CONTRIBUTING.md could be updated to include what other files should be updated or if that's it, it could added at the end that default config if enough for a pull request.

Here in image I search for "polish" to find where "lithuanian" might go.

@Combinacijus,
Thank you.
To reduce the need to edit a bunch of files, the README and other files get updated automatically after the PR is landed.
Kind regards,
Jason

@Combinacijus,
Please feel free to add your name here: Contributors

@Jason3S That was very fast, thanks!


After level up, AS application can't close

Error: Error thrown in hooked function '' for hook 'gas.close'. Cannot read properties of undefined (reading 'render')
    at Hooks.onError (foundry.js:630:24)
    at #call (foundry.js:612:36)
    at Hooks.call (foundry.js:590:38)
    at Object.fn (index.js:143:11)Caused by: TypeError: Cannot read properties of undefined (reading 'render')
    at Object.fn (PCAppShell.svelte:57:24)
    at #call (foundry.js:608:20)
    at Hooks.call (foundry.js:590:38)
    at Object.fn (index.js:143:11)

fixed in 1.1.1


z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

Description of the issue
I have SMLIGHT CC2652P Zigbee USB Adapter SLZB-02 Zigbee dongle
connected to intel NUC at dev/ttyUSB0
I tried
ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Dec 10 15:14 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0

test -w /dev/ttyUSB0 && echo success || echo failure
success

it seems zigbee-herdsman fail to start. I don't have idea how to fix this, please help.

Starting Zigbee2MQTT without watchdog.
[2024-12-11 10:11:09] info: 	z2m: Logging to console, file (filename: log.log)
[2024-12-11 10:11:09] debug: 	z2m: Loaded state from file /config/zigbee2mqtt/state.json
[2024-12-11 10:11:09] info: 	z2m: Starting Zigbee2MQTT version 1.42.0 (commit #unknown)
[2024-12-11 10:11:09] debug: 	z2m: sd-notify loaded
[2024-12-11 10:11:09] info: 	z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-11 10:11:09] debug: 	z2m: Using zigbee-herdsman with settings: '"{\"network\":{\"panID\":6754,\"extendedPanID\":[221,221,221,221,221,221,221,221],\"channelList\":[25],\"networkKey\":\"HIDDEN\"},\"databasePath\":\"/config/zigbee2mqtt/database.db\",\"databaseBackupPath\":\"/config/zigbee2mqtt/database.db.backup\",\"backupPath\":\"/config/zigbee2mqtt/coordinator_backup.json\",\"serialPort\":{\"path\":\"/dev/ttyUSB0\"},\"adapter\":{\"disableLED\":false}}"'
[2024-12-11 10:11:10] debug: 	zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[25]},"serialPort":{"path":"/dev/ttyUSB0"},"adapter":{"disableLED":false},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json"}'
[2024-12-11 10:11:10] info: 	zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-12-11 10:11:10] info: 	zh:zstack:znp: Serialport opened
[2024-12-11 10:11:10] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-11 10:11:10] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-11 10:11:10] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-12-11 10:11:10] debug: 	zh:zstack:unpi:writer: --> buffer [239]
[2024-12-11 10:11:11] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-11 10:11:11] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-11 10:11:12] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-12-11 10:11:12] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-11 10:11:12] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-11 10:11:18] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-11 10:11:18] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-11 10:11:24] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-11 10:11:24] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-11 10:11:30] error: 	z2m: Error while starting zigbee-herdsman
[2024-12-11 10:11:30] error: 	z2m: Failed to start zigbee
[2024-12-11 10:11:30] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-12-11 10:11:30] error: 	z2m: Exiting...
[2024-12-11 10:11:30] error: 	z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:113:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:161:27)
    at start (/app/index.js:154:5)

Hello I got the same problem with the same configuration.
Can somobody check the code of the last update ?
Many Thanks
Patou

hello, i had the same problem.
By hard rebooting (disconnecting power) the raspberry pi4 I got a working add-on again.
I also changed the "serial" field to
port: /dev/ttyUSB0
in the past I had the full reference including the name of the stick, but not anymore.

Hello,
I have the same problem, see the log file zigbee2mqtt_2024-12-17T07-07-00.298Z.log for details. Everything runs normally until 00:37:59, after which no more data is received. At 03:00:06 the following error occurs
[2024-12-17 03:00:06] debug: 	zh:controller:endpoint: Error: ZCL command 0x003c84fffe21fdd6/1 manuSpecificTuya.dataRequest({"seq":1,"dpValues":[{"dp":2,"datatype":4,"data":[1]}]}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)
    at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)
    at /app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:285:45
    at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
    at Znp.request (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:278:27)
    at ZStackAdapter.dataRequest (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1034:24)
    at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:488:46)
    at /app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:422:31
    at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
    at ZStackAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:420:33)
    at Request.func (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:299:36)

But actually nothing is running from 00:38:00 onwards, the "last seen" device is 'Heizung Schlafzimmer' at 00:37:59.
System:
Home Assistant Core 2024.11.3 as virtual machine on QNAP-NAS
ttyUSB0
/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0

I have similar issues. These seem to be random.
My setup was working perfect for a few years.
Any help or ideas are appreciated
Zigbee2MQTT version 			       1.42.0 commit: unknown
Coordinator type 			                zStack3x0
Coordinator revision 			        20210120
zigbee-herdsman-converters version 	20.58.0
zigbee-herdsman version 		        2.1.9
Config:
serial:
port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
adapter: zstack
LOG
[10:16:37] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-12-21 10:16:47] info: 	z2m: Logging to console, file (filename: log.log)
[2024-12-21 10:16:47] debug: 	z2m: Loaded state from file /config/zigbee2mqtt/state.json
[2024-12-21 10:16:47] info: 	z2m: Starting Zigbee2MQTT version 1.42.0 (commit #unknown)
[2024-12-21 10:16:47] debug: 	z2m: sd-notify loaded
[2024-12-21 10:16:47] info: 	z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-21 10:16:47] debug: 	z2m: Using zigbee-herdsman with settings: '"{"network":{"panID":6755,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","serialPort":{"path":"/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0","adapter":"zstack"},"adapter":{"disableLED":false}}"'
[2024-12-21 10:16:48] debug: 	zh:controller: Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":"HIDDEN","panID":6755,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0","adapter":"zstack"},"adapter":{"disableLED":false},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json"}'
[2024-12-21 10:16:48] info: 	zh:zstack:znp: Opening SerialPort with {"path":"/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-12-21 10:16:48] info: 	zh:zstack:znp: Serialport opened
[2024-12-21 10:16:48] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-21 10:16:48] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-21 10:16:48] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-12-21 10:16:48] debug: 	zh:zstack:unpi:writer: --> buffer [239]
[2024-12-21 10:16:49] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-21 10:16:49] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-21 10:16:50] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-12-21 10:16:50] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-21 10:16:50] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-21 10:16:56] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-21 10:16:56] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-21 10:17:02] debug: 	zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2024-12-21 10:17:02] debug: 	zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2024-12-21 10:17:08] error: 	z2m: Error while starting zigbee-herdsman
[2024-12-21 10:17:08] error: 	z2m: Failed to start zigbee
[2024-12-21 10:17:08] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-12-21 10:17:08] error: 	z2m: Exiting...
[2024-12-21 10:17:08] error: 	z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:113:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:161:27)
at start (/app/index.js:154:5)
[10:17:10] INFO: Preparing to start...
[10:17:10] INFO: Socat not enabled
[10:17:10] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.

I don't know exactly where the problems came from, but I did a few downgrades and since then Zigbee2mqtt has been running stable for me again.
Home Assistant Operating System 13.2 -> Is fine
Home Assistant Core 2024.11.3 -> downgrade to 2024.11.1
Zigbee2MQTT 1.42.0-2 -> downgrade to 1.40.2-1


Remove old metrics

This commit removes the following metrics:

pie_io_write_latency_seconds
- use pie_io_write_latency_on_mount_probe_seconds instead
pie_io_read_latency_seconds
- use pie_io_read_latency_on_mount_probe_seconds instead
pie_create_probe_total
- use pie_mount_probe_total or pie_provision_probe_total instead
pie_performance_probe_total
- use pie_performance_on_mount_probe_total instead

@llamerada-jp @cupnes I updated my code, so could you review this PR again? The changes I made since you reviewed are as follows: https://github.com/topolvm/pie/compare/db39a5b5ab5592f4719d10b8a8843abd93567a7c..36f60e1#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5


Added .de Zerocopter Program

JSON Formatting and Validation done along with Adding Bug Bounty Program.

Thank you for adding more programs @theinfosecguy


Build failure: zed-editor

Steps To Reproduce
Zed-editor fails to build for MaxOS Intel using NIXPKGS_ALLOW_BROKEN=1 nix-shell -p zed-editor -I nixpkgs=channel:nixos-unstable
Build log
  ...
  cargo:rerun-if-changed=/nix/store/xz8j1amvgwas4nbfqgpmcz147pkd391s-apple-framework-VideoToolbox/Library/Frameworks/VideoToolbox.framework/Headers/VTBase.h
  cargo:rerun-if-changed=/nix/store/wahwaqbn6f57ybai7akc5920vrln9s2j-apple-framework-CoreFoundation/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h
  cargo:rerun-if-changed=/nix/store/xz8j1amvgwas4nbfqgpmcz147pkd391s-apple-framework-VideoToolbox/Library/Frameworks/VideoToolbox.framework/Headers/VTErrors.h

  --- stderr
  thread 'main' panicked at /private/tmp/nix-build-zed-0.137.6.drv-0/cargo-vendor-dir/bindgen-0.65.1/ir/ty.rs:1074:22:
  Not able to resolve array element?: Continue
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: builder for '/nix/store/dv6kd8ljw54aw4j728cy97mqg0jxlv6y-zed-0.137.6.drv' failed with exit code 101;
       last 10 log lines:
       >   cargo:rerun-if-changed=/nix/store/a5swqw43q2yahpawgwbrsgildzqni5n1-apple-framework-CoreMedia/Library/Frameworks/CoreMedia.framework/Headers/CMBase.h
       >   cargo:rerun-if-changed=/nix/store/xz8j1amvgwas4nbfqgpmcz147pkd391s-apple-framework-VideoToolbox/Library/Frameworks/VideoToolbox.framework/Headers/VTBase.h
       >   cargo:rerun-if-changed=/nix/store/wahwaqbn6f57ybai7akc5920vrln9s2j-apple-framework-CoreFoundation/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h
       >   cargo:rerun-if-changed=/nix/store/xz8j1amvgwas4nbfqgpmcz147pkd391s-apple-framework-VideoToolbox/Library/Frameworks/VideoToolbox.framework/Headers/VTErrors.h
       >
       >   --- stderr
       >   thread 'main' panicked at /private/tmp/nix-build-zed-0.137.6.drv-0/cargo-vendor-dir/bindgen-0.65.1/ir/ty.rs:1074:22:
       >   Not able to resolve array element?: Continue
       >   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
       > warning: build failed, waiting for other jobs to finish...
       For full logs, run 'nix log /nix/store/dv6kd8ljw54aw4j728cy97mqg0jxlv6y-zed-0.137.6.drv'.

Additional context
Add any other context about the problem here.
Notify maintainers
@GaetanLepage
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-darwin"`
 - host os: `Darwin 23.5.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.2`
 - channels(ari): `"darwin"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Add a :+1: reaction to issues you find important.

More about the build error here: https://github.com/NixOS/nixpkgs/pull/303233#issuecomment-2048650618
The Swift package is in crates/live_kit_client/LiveKitBridge - perhaps removing xcrun and adding swift swiftpm to the build inputs may fix this.
Another possibility is to integrate swiftpm2nix.

Building the Swift package will soon become unnecessary, as mentioned in my comment referenced by Gaétan. Unfortunately we'll have to wait for https://github.com/NixOS/nixpkgs/pull/229210 as Livekit depends on ScreenCaptureKit on macOS.

Looks like https://github.com/NixOS/nixpkgs/pull/326406 merged early support for apple_sdks 12.3 -- would that resolve the blocker you mentioned @niklaskorz?

Looks like #326406 merged early support for apple_sdks 12.3 -- would that resolve the blocker you mentioned @niklaskorz?

Draft PR is available at #329653 but is blocked until https://github.com/zed-industries/zed/pull/13343 is merged and released. As the draft is based on that PR branch, it however already builds and runs:
$ nix build "github:nixos/nixpkgs?ref=pull/329653/head#zed-editor"
$ result/libexec/zed-editor

#329653 is now ready for review, fixing the latest Zed release on macOS. Livekit (and thus collaboration features) remains disabled on both macOS and Linux until https://github.com/zed-industries/zed/pull/13343 is released.


Menus are too large in 0.3.0

Lapce Version
v0.3.0
System information
Fedora 39
Describe the bug
I'm not using display scaling, but the menus seem a little too large:
Additional information

Different app, for comparison:

I would like to add that in this version I noticed that the terminal fonts are not rendering properly.

I don't really know the Lapce source code, but with a little bit of guidance I might be able to help with this.
Best regards.

@Mforcen that's #2736.

@lnicola I did not notice that issue, thanks for pointing it out to me.
Best regards.

Same issue on Linux Mint 21 Cinnamon with Lapce 0.3.1 (Flatpak version).

Also I did not manage to the the font sizes in the settings (both for UI & Editor, values were not saved, simply clicking on any other settings' section would reset the default value, and UI was never taking those new font size settings into account).
Installing Lapce nightly release (cb968ab, jammy-ubuntu version) I managed to reduce the font sizes to 8 from the default size of 13, making Lapce usage comfortable enough on my setup. Only the drop-down menus remain oversized.
However, a few minutes after, with the same nighly version (only restarting Lapce in between), I can't manage to save new font size values anymore. It is a bit different though: values appear to be saved when clicking to another settings section. But they are not taken into account by the UI, and closing the settings panel and opening it again shows they are back to the previous default I was able to change in still mysterious circumstances (font-size = 8).

The same issue with v0.4.0 for Ubuntu 22.04.04 and display resolution 3456x2160.

It wasn't fixed

The context menu under Linux is "manually" drawn in Floem which has a fixed font size right now.
The fix would be passing the UI font size in Lapce to Floem and Floem draw the context menu with that font size.

related to https://github.com/lapce/lapce/issues/3212
i think making them slightly transparent will also help

Same problem on Arch + Plasma. I was able to circumvent it by Ctrl+- 3 times, but that setting is reset after a restart, so I have to redo it every time.
Minor inconvenience for an editor that gets pretty much everything else right (I'm coming from PyCharm, so the low RAM usage and blazing speed is definitely not lost on me :wink: )


Null-safety support

Any plans to introduce null-safety support?

It already supports null safety.


monero_wallet_light implementation

This PR includes monero_wallet_light implementation

Should https://github.com/woodser/monero-cpp/pull/55 be closed?

FYI my Element Matrix appears to be having a problem where my messages aren't being received.

Matrix dot org and monero dot social homeservers have issues sending/receiving  to/from eachother. Its being looked in to.

@plowsof Any update on the issue sending messages to each other?

FYI my Element Matrix appears to be having a problem where my messages aren't being received.

May we can talk on IRC #monero-bounties channel?

I made the changes, I still have to test though

I'm successfully running monero_light_tests on my monero-project fork, branch light_wallet_maintenance

Closed by #70


Refactor to be able to write tailwind component in plain CSS?

Context
As the title states. Having styles in css rather than css-in-js is more idiomatic and portable.
A couple of issues:

can we access the theme function from tailwind in css?

can we do complex calculation (mixin & function in postcss maybe)? For example, look at the implementation of the current dark variant:
addVariant('dark', [
  ':merge(html[data-color-scheme="dark"]) &',
  ({ container }) => {
    const originalRule = container.nodes[0];
    const mediaRule = postcss.atRule({
      name: 'media',
      params: '(prefers-color-scheme: dark)',
      nodes: [
        postcss.rule({
          selector: `html:not([data-color-scheme="light"]) ${originalRule.selector}`,
          nodes: originalRule.nodes,
        }),
      ],
    });
    container.removeAll();
    container.append(mediaRule);
  },
]);

This requires postcss and would require an alternative in other preprocessors / systems.

does it impact dev experience? Will it still trigger hot reload in vite?

Considerations
unocss is a very potential alternative to tailwind & windi that binds closely to a vite implementation and its philosophy. But it seems documentation is not very comprehensive. Plus, is it worth trading off familiarity with tailwind, especially in ways to customize theme & adding components & utilities to each predefined layer?
In tailwind land, we can try using postcss-js to 'objectify' a pure css / postcss string then pass it as a tailwind plugin, as described here: this method. However, this requires the use of the deprecated require.extensions (not a huge deal, but considerable). Does it also impact performance when we have another CSS-to-JSS conversion layer on top on tailwind?
Maybe we can combine both worlds and try using unocss with a postcss-js (or something alike) to accomplish what we set out to do, while also preserving hot reload?
Attempt to migrate to UnoCSS
After attempt to migrate to unocss (https://github.com/sveltevietnam/sveltevietnam.dev/tree/experimental-unocss), the dev server becomes too heavy to be acceptable.
=> Let's keep tailwind and apply the CSS-to-JSS conversion layer as discussed above.

For completion and later reference, I've made 2 postcss plugins during the process of this issue:

postcss-color-scheme
postcss-space-between


updated the voting section.

the text in this section was saying that the voting was successful which isn't accurate.
We only voted on the "concept" of the community fund previously. The soft forks are what really matter. So i've updated this to talk about the accumulation soft fork.

Approved and merged.


Feature request: from_fn adapter

It would be helpful to have an InternalIterator version of std::iter::from_fn

Currently this can be achieved by wrapping an std iterator with the adapter: std::iter::from_fn(...).into_internal(). And it's as good as a direct implementation would be (which would only give an ergonomics improvement).
I will add this once I find some time.

I meant a function which returns ControlFlow<R>, so you can write an internal iterator without needing to create a new struct. Something like:
internal_iterator::from_fn(|f| {
    f(item)?;
    ControlFlow::Continue(())
})

I'm not sure if that is possible with Rust's type system

That would require provided closure to be generic (as its argument f is supposed to be impl FnMut(Item)), which is currently not possible. There might be a way to do this by making from_fn a macro, or by making the closure take a &mut dyn FnMut(Item) instead, I'll see what I can do.

You could do a macro that generates a struct and an impl of InternalIterator given a body of try_for_each

Provided body would not be able to capture any of its environment, so I doubt the usefulness of such macro (unless you can show me specific examples where you'd like to use it).
I managed to implement a from_fn function that takes a plain closure: playground. It requires dynamic dispatch and the type signature becomes a bit convoluted which I am not a fan of, but does this look like something that would be useful to you?


Error when generating gallery

When I try to generate a gallery, I get the following error:
$ wraith generate_gallery configs/btmash_dev.yaml
/Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/folder.rb:72:in `block (2 levels) in threshold_rate': undefined method `>' for nil:NilClass (NoMethodError)
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/folder.rb:71:in `each'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/folder.rb:71:in `block in threshold_rate'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/folder.rb:70:in `each'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/folder.rb:70:in `threshold_rate'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/gallery.rb:50:in `match'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/gallery.rb:35:in `parse_directories'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/gallery.rb:125:in `generate_gallery'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/lib/wraith/cli.rb:88:in `generate_gallery'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/wraith-2.4.1/bin/wraith:5:in `<top (required)>'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/bin/wraith:23:in `load'
	from /Users/ashokmodi/.rbenv/versions/2.1.3/bin/wraith:23:in `<main>'

Looking through the issue queue, alphanumeric labels seemed to be an issue. However, in my case, it is in lowercase (but I also only have one label since I'm using the historical shots approach). If I run wraith latest configs/btmash_dev.yaml, it works just fine. Below is my config file.
#Headless browser option
browser:
  phantomjs: "casperjs"
  # slimerjs: "slimerjs"

#If you want to have multiple snapping files, set the file name here
snap_file: "javascript/casper.js"

# Type the name of the directory that shots will be stored in
directory: 'shots/btmash_dev'
history_dir: 'shots_history/btmash_dev'

# Add only 2 domains, key will act as a label
domains:
  dev<EMAIL_ADDRESS>
#Type screen widths below, here are a couple of examples
screen_widths:
  - 320
  - 768
  - 1024
  - 1500

#Type page URL paths below, here are a couple of examples
paths:
  menu:
    path: /
    selector: '.header'
  brand:
    path: /
    selector: '.node-page'
  services:
    path: /
    selector: '#block-views-services-block-home'
  footer:
    path: /
    selector: '#footer'
  about:
    path: /work

#Amount of fuzz ImageMagick will use
fuzz: '20%'

#Set the filename of the spider file to use, if not specified it will fallback to spider.txt
# spider_file: bbc_co_uk_spider.txt

#Set the number of days to keep the site spider file
spider_days:
  - 10

#Choose how results are displayed, by default alphanumeric. Different screen widths are always grouped.
#alphanumeric - all paths (with, and without, a difference) are shown, sorted by path
#diffs_first - all paths (with, and without, a difference) are shown, sorted by difference size (largest first)
#diffs_only - only paths with a difference are shown, sorted by difference size (largest first)
mode: diffs_first

threshold: 5

This should be fixed with #265


Support audio resampling

Either use the SDL2 facility, or wrap/corrode avresample or speexdsp.

https://github.com/rust-av/speexdsp-rs is wrapped and corroded, it just needs to be wired in.


Text box is disabled

Whenever I click on the textbox, placeholder changes to oops! Something went wrong.
And even I don't have to click on that textbox after the page is reloaded, within 5-6 seconds it get's disabled

Hi @KaranPato ,
Please check developer console for more details.
The problem is in google library itself, probably you are using the wrong api key.
Thanks,
Stas

Actually, I was using the right API but from 16th July they have started a new rule to add the Billing details and all. That's why it isn't working.
Anyways, Thanks
Karan


Added a note to help with manual capture

This guidance is useful for two paged sign in forms that require additional input for the user to continue to capture fields on the page.

@jaszperez : Thanks for your contribution to the Azure documentation! The author, @ajamess, has been notified to review your proposed change.


Not working in KiCad 7 on Mac

Hello, version 7 of KiCad seems to have broken the plugin. I am receiving this error message on a mac:
Traceback (most recent call last):

File "/Users/username/Documents/KiCad/7.0/3rdparty/plugins/com_github_mitxela_kicad-round-tracks/round_tracks_action.py", line 378, in Run
rt = RoundTracks(board, self)

File "/Users/username/Documents/KiCad/7.0/3rdparty/plugins/com_github_mitxela_kicad-round-tracks/round_tracks_action.py", line 56, in __init__
for class_id in self.board.GetDesignSettings().GetNetClasses().NetClasses():

AttributeError: 'BOARD_DESIGN_SETTINGS' object has no attribute 'GetNetClasses'

...saw that this was already posten and answered here: https://github.com/mitxela/kicad-round-tracks/issues/22
Closing it - Thanks Mitxela!

closed.


Why can't i simply uninstall or disable debugers etc (anything f**k i want)? Its really annoying.

Why can't i simply uninstall or disable debugers etc (anything f**k i want)? Its really annoying.

You can disable built in debuggars by Extensions viewlet > ... > show built in extensions > find node debug and disable it


Is Kingfisher doing this or something else?

I've got a UITableViewCell subclass with a UIImageView and a label that are dynamically tall via UITableViewAutomaticDimension.  Kingfisher is loading the image into the ImageView from a remote URL.
The first time the cells are rendered it looks perfect.  If I reload the table or unload thew view and return, the cell ends up as tall as the image, rather than as tall as the label.  If I do not use Kingfisher and set the image by some other means or do not load an image into the view at all, it looks fine.
Screenshots

At the first time, your cell height is determined by the original image view height, and setting an image to the image view will not change its layout anymore. When you reloading the table view, since the image view already has an image set, it has an intrinsicContentSize and the cell layout itself with this size.
So basically it is what the UIKit works and I believe it should not be an issue in Kingfisher. (and Kingfisher is not touching anything about view layout or dimension at all. It is just setting the image property)

I have my doubts.  Like I said, when I set the image to a local asset, this doesn't happen.  Also, the height of the image is dynamic to match the resulting height of the cell, which is dynamically tall depending on the height of the label.


Inconsistent version naming scheme in OpenCL-SDK-vJJJJ.MM.DD-Source.tar.gz

In the newest release, the downloadable source file OpenCL-SDK-v2022.09.23-Source.tar.gz has the directory OpenCL-SDK-2022.5.18-Source.
Not only do the dates not match up, but the version string of the directory doesn't contain a 0 in the first space, when the day or the month is less than 10.
This inconsistency makes it quite hard to automate things.

Eek, @MathiasMagnus did I mess something up here?
Looks like this is driven by the project version in the CMake file, which is still the older "2022.05.18", so that's at least part of the problem.  The leading zero gets removed by CMake when it parses this into the PROJECT_VERSION variable.
Should we try to make the directory in the zip and tgz files match the git tag?  Or would it be OK to remove the directory altogether, since the git tag is in the filename anyhow?

I think we didn't bump the version inside CMakeLists.txt. Last time we did this as two separate commits.

I didn't know we'll be tagging right after the submodule bump. Anyhow, I'll update RELEASE.md to make sure we don't go astray next time. Overwriting the version tag should trigger the release scripts again.
As for the 0 being swallowed from 05, that should not happen. I've already seen that issue while working on the CD scripts and I recall solving that. On the CLI the package is renamed to holding the Git tag name verbatim. And I think I did something on the CMake side as well, but I may be wrong. Revisiting...

Reopening until we do a release with the corrected naming.

Hi - can you please confirm that the latest release (v2022.09.30) fixed the naming issue?  Thanks!

Yes, the version number now matches up everywhere. Thank you very much


chaining script cmdlets which use -pipelinevariable do not work as expected

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
create 2 functions:
PS> function cmdletB {[CmdletBinding()]param()BEGIN{"b2"}PROCESS{"! p2 !"}END{"e2"}}
PS> function cmdletA {[CmdletBinding()]param()BEGIN{"b1"}PROCESS{"! p1 !";cmdletB}END{"e1"}}

this will operate as expected:
PS> cmdletA -pv a| % {"> $a <"}
> b1 <
> ! p1 ! <
> b2 <
> ! p2 ! <
> e2 <
> e1 <

however, if you add -pv a to the invocation of cmdletB, you can see the issue.
PS> function cmdletA {[CmdletBinding()]param()BEGIN{"b1"}PROCESS{"! p1 !";cmdletB -pv a}END{"e1"}}
PS> cmdletA -pv a| % {"> $a <"}
> b1 <
> ! p1 ! <
> ! p1 ! <
> ! p1 ! <
> ! p1 ! <
> e1 <

it seems to lose all output from cmdletB.

PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

No pipeline, no pipeline variable. cmdletB -pv a cannot expand $a (just nowhere). This function works (every script block) but has no output.


Make integration test Dockerfile version-agnostic

Currently need to update the tarball file name manually.

Implemented in ec8c48f011f0e1e4305b1c59977848aa00ed8cd9.


feat(FTL): Created Firebolt Transport Layer API

Overview
Created a Transport Layer API for sending/receiving JSON-RPC from a Firebolt Execution Environment
Justification
The Transport Layer API should be agnostic to the actual Firebolt API, to minimize code duplication / chance of typos / etc.
Changes

Added a mock Transport Layer w/ a "defaults.js" in each module
Created a two-way handshake to wire up SDK to FTL regardless of which loads first
Created a Queue FTL, to store API requests until the handshake is done
Created a way to store mock events in each defaults.js, so the mock FTL can dispatch them for testing

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 3 files pending identification.

Protex Server Path: /home/blackduck/github/Lightning-SDK/226/rdkcentral/Lightning-SDK

Commit: 733cb0069695074979915a9a15d910d072ef7b28

Report detail: gist

Hi @jlacivita The headers on this repository had to be switched to Metrological, so the three index.js files that have RDK Management copyrights on line 5 need to switch to Metrological instead.
Thanks,
Martin Hughes, RDK CMF Compliance Team

Thanks again @mhughesacn !


Start the Rosetta initiative for bring hlphp back up to speed

Greetings!  Here's the situation:
Since the release of highlight.js v10, JSON-only language definitions were no longer possible because hljs introduced function support into language definitions. Historically, highlight.php (hlphp) has relied on JSON-only representations of language definitions but there's no way to represent functions in JSON. So does that mean the death of this project? Am I going to be manually maintaining 190+ language definitions?
Here's the crazy idea I came up with one night while being in an impaired state, why not write a translator for language definitions written in JavaScript to now be written in PHP? Are there existing projects out there at attempted this? Yes. The ones I've found are not as active or do not support modern JS syntax.
Enter, Rosetta-PhpScript. Internally, it uses Babel to generate an AST and then I parse that AST and start translating it into a valid PHP AST that nikic's php-parser can handle and then generate valid PHP.
Is there an ETA on this? Nope! My former employer has suddenly gifted me "time off", so I've got some time to kill. I'm hoping to get this project done this summer but no promises!

Hi, just curious about the state of this initiative. Do you consider it viable? Is there something blocking it?
Maybe there is something I can do to help you?


Interest in collaboration with human-panic?

This seems to set out to have a similar goal to human-panic.  I'm curious if there is any collaboration we can foster between these crates or if there are reasons to keep these separate.
See https://crates.io/crates/human-panic

Hi @epage! Thank you for your message.
I knew the human-panic crate before creating bugreport and definitely didn't want to start a competing project. To be honest, I don't see a huge overlap in functionality, but maybe I'm mistaken!
From what I understand, human-panic only comes into play if there is an actual (unexpected) crash of a program through panic!.
On the other hand, bugreport-code is intended to be executed on purpose by a user if they want to report a bug (which might not involve a program crash at all).
What both crates have in common is the need to collect some information about the program in question (and it's environment). If you see a potential collaboration on this front (or any other front), please let me know!

Oh, from the summary, I missed that it was user-driven (since I only did a quick glance at the example).
I'm assuming the use cases and users line up enough that one crate could serve both needs, with a hook-install function and a dump-report function.
If it doesn't, I can see having each crate advertise the other!  We've been doing that with other CLI related crates (e.g. assert_cmd) to try to improve discovery within the ecosystem.  I could also see adding this to the CLI book.

I'm assuming the use cases and users line up enough that one crate could serve both needs, with a hook-install function and a dump-report function.

Speaking in terms of mathematical relations, would you see the current bugreport functionality as a subset of the human-panic functionality? Or the other way around? I think I do see some overlap, but both crates also come with functionality that users of the other crate might not need. But again, I'm happy if that's not the case.

If it doesn't, I can see having each crate advertise the other!

Absolutely. Let's do that right now: 456eb0dc57d1d278f5289f831faf7c2fa361eeb8

We've been doing that with other CLI related crates (e.g. assert_cmd) to try to improve discovery within the ecosystem

By the way: I LOVE assert_cmd! I use it for integration tests in most of my Rust CLI programs. The only reason I haven't contributed to the project is that it already fits my needs perfectly :smile:

Speaking in terms of mathematical relations, would you see the current bugreport functionality as a subset of the human-panic functionality? Or the other way around? I think I do see some overlap, but both crates also come with functionality that users of the other crate might not need. But again, I'm happy if that's not the case.

I assume they would benefit from each others information gathering with the differences beyond that being

human-panic also gathering the call stack
Each having an output format tailored to its use case

My hope in having them together include

Improving human panic with ideas from here, like env gathering
Allow shared initialization of the gathered information, rather than having distinct APIs that developers have to duplicate their initialization with (like env vars)
Encourage devs to include both to improve supportability

I very well could be missing something in this.

Thank you for clarifying. I am very open to the ideas proposed, but I'd like to be honest: I probably won't spend too much time on this myself.


Stanza add/update/remove

Formalize this process and allow upgrades to new database versions.

Make sure that restore and expiration still work - perhaps new unit tests.
Add db-id param to restore and archive-get to specify and database.

This should also make it easy to throw a "stanza does not exist" error.

Moved to xml backlog.


remove rkt reference

Project has ended

Hi @hiramf
Thanks for this PR.
Did you want to remove all the rkt references? If you did, also consider changing / removing:

https://k8s.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/
https://k8s.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/
https://kubernetes.io/docs/reference/glossary/?all=true#term-rkt

/lgtm

RIP rkt 🚀
@hiramf +1 to @sftim's comment. If you remove other rkt references, please bundle them into a single PR. 👍
/approve


feat: add auth translation namespace

This adds a feature namespace translation ("auth") with a new language ("pt"). Please let me know if I am following the right path!
Web frontend checklist

[x] Formatted my code with yarn format && yarn lint --fix
[x] There are no warnings from yarn lint
[x] There are no console warnings when running the app
[-] Added any new components to storybook
[-] Added tests where relevant
[-] All tests pass
[x] Clicked around my changes running locally and it works
[-] Checked Desktop, Mobile and Tablet screen sizes

I'm literally in the process of vetting this area of the codebase and re-structuring/renaming the translation keys where appropriate, but I don't want to lose some of your Portuguese translations! I think it may be best to hold this until I'm done with that (hopefully soon, been having less time myself to contribute too lately 😅  ) otherwise I might have to deal with more manual work of comparing what keys I've changed against these very WIP translation JSONs... (hence the confusion, lack of docs and general awkwardness of contributing tranlations to this as it's really not ready yet, sorry if you had to struggle through!)

Hi, @darrenvong ! I will close this PR. The intention was to clarify the translation logic with the README and also to contribute with extracting a few language tokens. But I see a lot of progress in your latest commits. I will close this PR and contribute back with Portuguese translations in a later time.


High fidelity designs on User Profile pages

done

Done, I worked on a second design option for the user profile page.
https://www.figma.com/file/p6Jhdhhif1KeKAagDL58Fh/Untitled?node-id=0%3A1


Update README.md

Thank you for taking your valuable time to contribute.

That's a lot nicer than what I deserve for a 2 character drive-by PR ;)
Thanks anyway :)


Revise ambiguous dct:type mapping on Data Service

Problem statement
In GeoDCAT-AP 2.0.0 dct:type on Data Service is used in three different contexts.

service category with "Classification of spatial data services" code list
service type with "Spatial data service types" code list
type with "Resource types" code list. (this one also appears in Dataset)

This makes correct assignment of usage notes, labels and the required code lists rather difficult, as well as consequent validation e.g. via SHACL.
The current approach is not in line with the profiling guidelines established in the context of the SEMIC Style Guide property reuse guideline Reuse of a property with terminological adaptations and Reuse of a property with semantic adaptations.
Also, the approach becomes even more problematic in a cross-profile environment where incompatible requirements can be easily made.
Proposal
Introduce subproperties of dct:type

geodcatap:serviceCategory for "Classification of spatial data services" code list
geodcatap:serviceType for "Spatial data service types" code list
geodcatap:resourceType for "Resource types" code list with the domain of dcat:Resource to accomodate both for Datasets and Data Services

This approach is in line with the profiling guidelines established in the context of the SEMIC Style Guide property reuse guideline Reuse of a property with terminological adaptations and Reuse of a property with semantic adaptations.
If interoperability is a concern, a data publisher can always easily materialize the subPropertyOf inference and replace the subproperties with dct:type.

Posponed until the next webinar

For info, in Flanders we are mapping to a subproperty of dct:type (related to #78 ):

Eigenschap
URI
GeoDCAT-AP
GeoDCAT-AP Vlaanderen

servicetype
http://data.vlaanderen.be/ns/metadata-dcat#servicetype
dct:type
subproperty van dct:type

servicecategorie
http://data.vlaanderen.be/ns/metadata-dcat#servicecategorie
dct:type
subproperty van dct:type

We had a discussion about this issue (Czech Office for Surveying, Mapping and Cadastre and Czech Environmental Information Agency) and we support the proposal - to create new subproperties of dct:type.


Log request and response headers

This is a feature request. Give the possibility to log both request and response headers.

@coorasse  i did overwrite RequestLog class to implement request header storing stuff

maybe you want to share your code or open a PR? it would be really appreciated! 🙇

@coorasse  I will create PR

@uzaif313 That would be great!

@abuisman  I will create PR this weekend

@uzaif313 can’t wait! Thanks

Here is the PR @uzaif313 created: https://github.com/renuo/rails_api_logger/pull/3

Any update on this? Is the PR merged?

In case anyone needs this, I merged all forks of this repo in another new fork 🙃 This include adding uuid, request_headers and used_ip to the logs.


Huge produce resprite

About the PR

Me and Prazat (Discord -> prazat911) resprited a huge amount of botany produce! The growth stages were not resprited (Maybe we will resprite them in the future).
Also some of the produce didn't need to be resprited - and may have been centered on their canvas OR they were very hard to resprite, so they were not resprited (Maybe we'll do it in the future).
Why / Balance

Looks cooler
Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl: prazat911
:cl: .kreks.

tweak: Huge botany produce resprite!

Wild sprites, not sure how to feel about it in contrast to our current artstyle

First it was a PR for one Russian server with different sprites, now I need to fix meta for all sprites

Okay, I can understand by the reactions that you didn't like the resprite very much


⚠ 366.ru has degraded performance

In c807970, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 1444 ms

Resolved: 366.ru performance has improved in 02d76de.


alternative repr that does not look like it can be evaluated

the repr() generated by attrs looks something like this by default:
MyClass(a=1, b=2)

this is fine in simple cases. however, when using init=False, and implementing my own __init__(), this repr() is misleading since it looks like code that can be evaluated, while actually it is not (and if it is, it's not an intended usage pattern anyway). what about having something like this instead for those cases:
<MyClass a=1 b=2>

...which is still very useful (e.g. for debugging), and it resembles a bit what python produces for classes that do not implement a custom __repr__():
>>> x = object()
>>> x
<object object at 0x7f6cda0c45e0>

obviously, this custom repr() behaviour would require explicit enabling. a flag to attr.s(), e.g. attr.s(use_eval_repr=False) (please come up with a better name), would make sense to me.
what do you think?

btw, i can take a stab at a pr if you think this feature is worth adding. is seems that passing a flag to _add_repr() and using a slightly different format string depending on that flag is pretty much all that is needed.

I agree but I’m not sure if it’s worth the complexity and confusion.  Just because the __init__ doesn’t come from us, doesn’t mean it’s not evaluable and users might get confused by the changing behavior.

that's why i suggested to have another flag to enable this "custom repr". it would be an independent flag (not dependent on init=False in any way) so that it's just an additional opt-in feature.

I think I have an alternate solution that might satisfy this too. Adding some thoughts to a new issue (will link it in a sec).

Solved by #568!

not sure that's correct, @hynek. i opened this ticket about custom repr for classes,
but #568 (also written by me) is about attribute-level custom repr.
see the examples in the description of this issue; i don't think that can be achieved with #568.
(tentatively reopening the ticket, feel free to close if things turn out to be different from what i wrote.)

IIRC this ticket was about "Make attr.s(repr=, rather than attr.ib(repr= which is #568, also take a callable which collects and assembles the final one (and then secondly possibly implement a concrete callable implementation for bracket-looking-repr or soemthing).

exactly, @Julian. in #568 i added a repr=... with a custom callable for attr.ib().
in this (much older!) issue i didn't suggest a specific API, but i agree using repr=... with a custom callable, but for attr.s() seems the logical choice.


Make CachedHashingSpec more lenient

Fixes https://github.com/sbt/zinc/issues/552
The 20% assersion is failing often.

To validate this pull request against other sbt modules, please visit this link.


feat(a11y): implemented a11y tree snapshot function

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

:exclamation: No coverage uploaded for pull request base (main@f94d612). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2378   +/-   ##
=======================================
  Coverage        ?   93.65%
=======================================
  Files           ?      222
  Lines           ?    23311
  Branches        ?     2049
=======================================
  Hits            ?    21832
  Misses          ?     1441
  Partials        ?       38

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


Cloned, added token, renamed to .env.local, installed and run but map not loading

https://i.imgur.com/WbAO6KD.png any ideas what I do wrong?

Make sure in .env it is written
PUBLIC_MAPBOX_TOKEN="pk.eyJ1 etc etc"
Mine did not work till this was written this way.
Hope this helps


Payment issue for E/App PR#29426

Issue created to compensate the Contributor+ member for their work on https://github.com/Expensify/App/pull/29426
E/E issue linked to the PR - https://github.com/Expensify/App/issues/24952
Contributor+ member who reviewed the PR - @allroundexperts
The amount is $250 because that's what we pay for TS Migration!

https://www.upwork.com/en-gb/jobs/~01d9e57771da0c2fda

@allroundexperts - $250

Posting anyways

$250 payment approved for @allroundexperts based on summary above.


Nuxt: useHead undefined after initiating a regex (since monday)

Environment
Linux (this problem doesnt appear to happen on windows).
tested on different node versions.
Reproduction
https://stackblitz.com/edit/github-819pq2-4sknkq?file=layouts%2Fdefault.vue
Describe the bug
"var emailregexx =
/^[a-zA-Z0-9.!#$%&'+/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]+)$/;
useHead({
meta: [
{
name: 'viewport',
content:
'width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0',
},
],
});"
This code crashes. And my question is why.
I've created an issue on nuxt at: https://github.com/nuxt/nuxt/issues/27392 . There danielroe asked me to created to ticket here.
It happens since monday(maybe friday or thursday) and this code is already years old.
When you remove the regex line, all works normally again.
When you change the regex to the following 2 options it works:
/^[a-zA-Z0-9.!#$%&'+/?{|}~-]+@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]+)$/; (removed the `)
/^[a-zA-Z0-9.!#$%&'+\/?`{|}~-]+@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]+)$/; (escaped the /)
Additional context
Error that gets thrown:
useHead is not defined
at _sfc_main.setup (./layouts/default.js:42:23)
at callWithErrorHandling (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:195:19)
at setupStatefulComponent (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7572:25)
at setupComponent (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7533:36)
at renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:623:15)
at renderVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:755:14)
at renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:710:7)
at eval (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:639:25)
at async unrollBuffer$1 (./node_modules/@vue/s
Logs
No response

@hankdetank please provide an unimport-only reproduction next time 😋
Example (using only unimport here) reproduction in this case

This appears to be an issue with the upstream, and the error will occur at this step:
https://github.com/unjs/unimport/blob/b2db6fec8bb58a405a23d7f72dfd652614bc8017/src/regexp.ts#L31 stripLiteral return an incorrect result, it stripped a part of the regular expression.
And here is a workaround, replace this regex to /^[a-zA-Z0-9.!#$%&'+\/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]+)$/


render area:highway=footway

https://www.openstreetmap.org/way/372975520
https://www.openstreetmap.org/way/4483968
ideally all highway areas would be rendered, and it would use the surface=* tag to determine material. I can't figure out how to do that though .-.

Thank you!


EL-1463 add helm and multi deploys

What does this pull request do?
JIRA ticket https://dsdmoj.atlassian.net/browse/EL-1463
Moved most env_vars to values files
moved Google Maps API Key to kubernetes secret for staging and production (fixes 2 x security warning on repo)
Set up per branch deploys into staging
Set up 2 pipelines, the original one and the helm one so we can dual deploy along both pipelines until we are happy and then we can switch the URL/Host names over and remove the old pipeline
Checklist

[x] Provided JIRA ticket number in the title, e.g. "LGA-152: Sample title"

Playwright tests are failing. Also the ordering and structure of the pipeline has changed. I think it's better to not have the tests on their own branch.


Debugging in Visual Studio Code no longer works

Since a couple of weeks I can no longer debug any script using Visual Studio Code. Downgrading to an older version of dotnet-script does not help. It's a bug in combination with .Net 5, Visual Studio Code or the C# (OmniSharp) extension in Visual Studio Code.
I tested debugging script on two separate machines and a Hyper-V "Windows 10 dev environment" (using "Quick Create..."). It does not work on any of these.
Steps to reproduce

Latest version of .Net 5, latest version of Visual Studio Code, latest version of C# extension in Visual Studio Code, any version of dotnet-script
Create new folder
Run dotnet script init inside that folder
Open the folder in Visual Studio Code
Open main.csx which only contains Console.WriteLine("Hello world!");
Optional: Add breakpoint on Console.WriteLine("Hello world!");
Debug main.csx

Expected behavior

Breakpoint works
"Hello world!" in console ouput

Actual behavior

Breakpoint does not work
No "Hello world!" in console ouput
Debugger getting stuck (never continues/stops)

Technical details
dotnet script --info
Version             : 1.1.0
Install location    : C:\Users\USERNAME\.dotnet\tools\.store\dotnet-script\1.1.0\dotnet-script\1.1.0\tools\net5.0\any
Target framework    : net5.0
.NET Core version   : 5.0.8
Platform identifier : win
Runtime identifier  : win10-x64

Visual Studio Code
Version: 1.58.1 (user setup)
Commit: 2aeda6b18e13c4f4f9edf6667158a6b8d408874b
Date: 2021-07-13T06:58:28.115Z (4 days ago)
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

OmniSharp
Version: v1.23.13

Console Output
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\USERNAME\.dotnet\tools\.store\dotnet-script\1.1.0\dotnet-script\1.1.0\tools\net5.0\any\dotnet-script.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\USERNAME\.dotnet\tools\.store\dotnet-script\1.1.0\dotnet-script\1.1.0\tools\net5.0\any\Microsoft.CodeAnalysis.Scripting.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\System.Collections.Immutable.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\USERNAME\.dotnet\tools\.store\dotnet-script\1.1.0\dotnet-script\1.1.0\tools\net5.0\any\Microsoft.CodeAnalysis.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\USERNAME\.dotnet\tools\.store\dotnet-script\1.1.0\dotnet-script\1.1.0\tools\net5.0\any\Dotnet.Script.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\netstandard.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\System.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.8\System.Console.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.

Debugger gets stuck after "Loaded ... System.Console.dll ..."

I found the problem. The launch.json that dotnet script init creates contains "stopAtEntry": true. By setting it to false, it works like before.
I can not remember that stopAtEntry ever worked. Most of my scripts contain "stopAtEntry": true but they never behaved like this.
Maybe consider changing the default of "stopAtEntry" to false, as at least I will now always set it to false after creating a new script using dotnet script init.
Of course searching for weeks without success and then one day after creating an issue I finally found the cause my self 🙈


Reflect CrateDB 3.1.2 release

Summary of the changes / Why this improves CrateDB
This PR updates the documentation on master to reflect the release notes of the 3.1.2 CrateDB release, published yesterday.
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed

Shouldn't the entries in unreleased.rst be removed?
And could you also add a follow up version bump to 3.1.3-snapshot in the 3.1 branch? See release docs

@mfussenegger You are completely right, I had forgotten that step. I'll bump the snapshot too.


not-for-all-eyes -> not-for-all-audiences

Community requested a term that was less potentially ableist

Additional context:
https://twitter.com/mmitchell_ai/status/1640783971155075074


Set stream flags in input_stream_adapter [WIP]

Set stream flags in input_stream_adapter on various error conditions. Fixes #976.
For performance reasons do not use the istream interface but the underlying streambuf to get/unget characters. The behavior of this implementation differs slightly from the reference implementation (see below) in case a streambuf operation throws an exception (badbit is not turned on in the istream's error state).

For reference, this class was used to generate test cases:
class input_stream_adapter : public input_adapter_protocol {
    std::istream& is;

public:
    explicit input_stream_adapter(std::istream& i) : is(i) {
        // skip byte order mark
        if (is.peek() == 0xEF) {
            is.ignore();
            if (is.peek() == 0xBB) {
                is.ignore();
                if (is.peek() == 0xBF) {
                    is.ignore();
                    return;
                }
                is.unget();
            }
            is.unget();
        }
    }

    traits::int_type get_character() override {
        if (is.good()) {
            const auto ch = is.peek();
            if (ch != traits::eof()) {
                is.ignore();
                return ch;
            }
        }
        return traits::eof();
    }

    void unget_character() override {
        is.unget();
    }
};

Can one of the admins verify this patch?

Coverage decreased (-0.6%) to 99.442% when pulling 4fc0988e026cb64344bcefc1751a442d9ebf4a21 on abolz:istream into 8968adcd53951b652f9f480ad62e66dc2714b061 on nlohmann:develop.

The current state of this PR is a compromise between consistency[*] and performance. And it's the best I could come up with. (Since I won't have the time to look at this closer in the near future, I'll remove the "WIP" state and leave this PR as is.)
AFAIK, there is no way to use the underlying streambuf directly while providing the same semantics as the istream interface (since there is no way to set the stream state without throwing an exception) in case a streambuf operation throws an exception. But most importantly, the stream state is no longer unconditionally set to "good" and no characters are extracted from "bad" streams.
IIRC, using the istream interface degrades the performance by a factor of ~5. So this PR still uses the streambuf directly, but sets the stream state on errors (or if EOF is reached). I think the performance degradation is acceptable for the increased consistency with built-in stream extraction operators...
[*] As I understand it from reading the standard 🙈


az vm update - az: ' vm update --resource-group' is not in the 'az' command group.

Describe the bug
Running az vm update commands fails for my customer in multiple clients including Cloud Shell.
"az vm list" and other commands seem to work, but no az vm update commands are successful.
Two different "az vm update" commands fail with the error below:
To Reproduce
We ran the following command:
az vm update --resource-group RGName --name VMName --set tags.test=tags
az: ' vm update --resource-group' is not in the 'az' command group. See 'az --help'.
Another example with --debug is attached.
az vm update debug Log.txt
Expected behavior
It's expected that the command completes successfully. I do not have an issue in Cloud Shell, and the customer has one On Prem client that does not have an issue, but in his Cloud Shell and multiple other machines in Azure, they all get the errors above.
Environment summary
All machines are using version 2.0.56, aside from one on 2.0.57. I am on 2.0.56 and do not have the issue.
Affected machines are Windows 2012 and various versions of Linux. It spears that all Azure VM's have the issue.
Additional context
Out of the machines we checked, the only one without the issue is the On-Prem Windows 10 machine. Cloud Shell run from that machine fails as well.

From the debug trace, there is clearly an encoding issue on the affected machines. The terminal is sending the unicode character \xa0 instead of a plain space. Does this issue only occur for this one command or do other commands show this problem?

We originally had the issue with the command in the txt document to swap the disk with another VHD.
In testing we also had the issue with the command mentioned to create a tag on the VM.
az vm update --resource-group RGNAme --name VMName --set StorageProfile.OsDisk.Vhd
and
az vm update --resource-group RGName --name Name --set tags.test=tags
It also did not matter if we used "--resource-group and --name" or "-g and -n". Same result.

Are you running these commands from a script?  Or copy-pasting from another document?

These are just written in notepad, then copied in.

And if you type them directly?

I can't say for sure if that was successful as my customer is currently away, however copying the same command into his on-prem Windows 10 client works without issue.
That one machine works, but no azure VM's or Cloud Shell are successful.

@montyleew, I looked at your "debug.txt" file and saw that some of the spaces are actually "\xa0" characters which is the hexadecimal value "A0". This character is a "Non-breaking space" character, which in certain scenarios is treated differently from other whitespace characters, which is probably why the shell does not treat it as whitespace when breaking the command into its individual tokens yielding:
['\xa0 vm \xa0 update \xa0 --resource-group', 'RGNAme \xa0 --name', 'VMName \xa0 --set \xa0 StorageProfile.OsDisk.Vhd.Uri=https://SAName.blob.core.windows.net/vhds/VMName-OS-1.vhd', '--debug']
As you can see, the Non-break-space characters are treated as part of each token instead of whitespace, if they were regular whitespace, the correct tokens would have been parsed.
Is the customer copying and pasting this command from html or some other document?

Yes, this is being copied from Notepad.
I did copy that text from my notes as well, so I'm not sure if those were added afterwards.
I'll have him type this in directly and report back.
I appreciate the help!

That's interesting, out of curiosity, were these commands typed into notepad or copied from elsewhere?

I'll find that out for us. The customer appears to be offline.
I'm trying to find out if the characters were added when I copied the results from the customer out of Outlook. I don't see them here.

You were right. Typing it in manually resolved the issue.
Thanks for the help, the behavior made no sense to me!

Hi @montyleew when copying from any document, I'd recommend you copy first to something like Notepad++ and use something like their "Convert to UTF-8" option.


Step 09 : shield_changed signal not connected

In the UI, the shield is not displayed because the shield_changed signal from Player scene  is not connected to anything.
To make it works, I have to connect the signal in the main scene that will apply the change in the UI :
func _ready():
  spawn_enemies()
  $Player.shield_changed.connect(update_shield)

func update_shield(max_shield, shield):
  $CanvasLayer/UI.update_shield( max_shield, shield )

It's not necessary to do this at all. The update_shield() function is in the UI script already, so adding another function to call it is redundant.
You also don't need to connect the signal in code, you can connect the player's shield_changed signal directly to the update_shield function in the UI using the editor. I am adding some clarifying text to that effect in the tutorial.


Update Perfect hash to build against 4.2

Pull Request Description
Updates the hash to be built against Swift 4.2. Also removes the xfail from the 4.0 configuration, because of SR-8234.
Acceptance Criteria
To be accepted into the Swift source compatibility test suite, a project must:

[x] pass ./project_precommit_check script run

PASS: Perfect, 4.2, cdc17d, Swift Package
========================================
Action Summary:
     Passed: 1
     Failed: 0
    XFailed: 0
    UPassed: 0
      Total: 1
========================================
Repository Summary:
      Total: 1
========================================
Result: PASS
========================================

@swift-ci test


Server error https://bundle.run/<EMAIL_ADDRESS>

Getting errors for several new packages:

https://bundle.run/<EMAIL_ADDRESS>https://bundle.run/<EMAIL_ADDRESS>https://bundle.run/<EMAIL_ADDRESS>

What's the error you're seing?
Only https://bundle.run/<EMAIL_ADDRESS>is working for me.
ENOENT: no such file or directory, open '/var/app/current/.tmp/1df60ebf00ac68e8e6300083463da9241bd411f9/package/lib/index.esm.js.js'

Seems to be a bug in packd.

Yep, I got a similar one with editorjs.
https://bundle.run/<EMAIL_ADDRESS>


SMHE-1602: improve CombinedDeviceModelCode

Fix a problem when there is no device model code for the gateway device when the format of the combined device model code is correct. Added a validation that the device model codes has at least content before parsing the combined device model codes.

https://jenkins.fdp.osgp.cloud/view/SMHE-cucumber/job/gxf-smhe-cucumber-build/166/


xtask: Enable strict provenance checks in Miri

I noticed while testing https://github.com/rust-osdev/uefi-rs/pull/662 that Miri is printing some useful warnings about pointer/integer casts. Enabling the -Zmiri-strict-provenance flag turns these warnings into errors so that they'll fail CI, otherwise it's easy to miss them.
Checklist

[ ] Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
[ ] Update the changelog (if necessary)

Wonderful, nice catch! strict pointer provenance and its analysis is still under development to my knowledge. So we probably can expect that working code might fail in future nightly versions because of additional checks, right?

Wonderful, nice catch! strict pointer provenance and its analysis is still under development to my knowledge. So we probably can expect that working code might fail in future nightly versions because of additional checks, right?

Yep, I think that's correct. Probably also generally true for any Miri thing actually, I don't think there are any stability guarantees on what it checks right now, but pointer provenance is maybe more likely to give the occasional nightly failure.


Project Sharing

The author will still share the code, right?

I'm also interested in the code.

Hi, can you share your code, i want to refer your paper.


[Request] Information about roles

Hello,
I don't know if for other people is the same, but I find pretty confuse all the documentation about the roles and the ACL rules...how really it works.
I am following all the setup with the certificates that are provided.
When restarting elasticsearch it does not let me execute again sgadmin.sh, giving me an error about admin/get does not exist.
If I don't restart ES, I can check the searchguard index with the user kirk, but after restarting ES, I cannot.. Is it normal? How can I check it? Do we need to create an admin user?
I tried to create it, and add it in all possible roles...but it does not work for me...
All this configuration it is only needed in the master node?
There are 2 elasticsearch.yml files? one for ES itself and another for the SG2 configuration(inside sgconfig)??
Would it be possible to have more information about how to do all this configuration?
Thank you!

docs will come, stay tuned.
For know we recommend to look into the Vagrantfile for that https://github.com/floragunncom/search-guard/blob/2.2/Vagrantfile

@carioka88 you need only one elasticsearch.yml. elasticsearch.yml.example in sgconfig just give you lines to add at the end of your /etc/elasticsearch/elasticsearch.yml file.

I see.
Thanks!


error C2039 (VS2019, win10 x64)

1>C:\Users\kokar\source\repos\Xenos\ext\BlackBone\src\BlackBone\Process\ProcessModules.cpp(194,14): error C2039: 'inserter': is not a member of 'std'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\include\array(20): message : see declaration of 'std'
1>C:\Users\kokar\source\repos\Xenos\ext\BlackBone\src\BlackBone\Process\ProcessModules.cpp(194,22): error C3861: 'inserter': identifier not found

Try compile Xenos with BlackBone, but this error occured. I already install WDK, SDK and some other.

I'm getting this as well, but it's easy to fix. I believe all I had to do was add this line somewhere to the beginning of BlackBone/Process/ProcessModules.cpp:
#include <iterator>

Thanks, it's work!


Floating numbers are not being highlighted properly

Hello!
I was playing with Hy and sqlite databases and found that floating are not being highlighted properly.
See this screenshot:

As you can see the 7 is highlighted as a number but the .9 is not.
Using the new :Inspect command from Neovim nightly I can see that the .9 is being highlighted as a symbol and the 7 as a number:

Btw, the commas are not the problem:


<EMAIL_ADDRESS>decompress error

 xxx in ~ λ scoop install gimp

Installing 'gimp' (2.10.38-1) [64bit] from 'extras' bucket
Loading gimp-2.10.38-setup-1.exe from cache
Checking hash of gimp-2.10.38-setup-1.exe ... ok.
Extracting gimp-2.10.38-setup-1.exe ... ERROR Exit code was 1!
Failed to extract files from C:\Users\nsimi\scoop\apps\gimp\2.10.38-1\gimp-2.10.38-setup-1.exe.
Log file:
  ~\scoop\apps\gimp\2.10.38-1\innounp.log

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=gimp%402.10.38-1%3a+decompress+error

https://github.com/ScoopInstaller/Extras/issues/14437#issuecomment-2522568417
May relate to ScoopInstaller/Main#6261.


What's about reworking MaterialDialogs.ShowAlertAsync to make it really awaitable and return Task instead?

Hi!
I've tried also MaterialDialogs.ShowAlertAsync which works fine in general.
However, with current implementation I can't see a way of notifying when the alert (confirmation) box is closed with negative (cancelling) result.
Currently the method is (in general) awaitable, which completes on the confirm popup appearing, however, usually, it doesn't have much sense from the app logic functionality perspective. From my experience, it's rather more important to be able further processing of the app logic after the choice been done.
So, I would suggest to rework it to return Task<bool>, which would complete after the used made his choice.
What do you think? I can also fork and apply that update as well if you have no time for that.

Hi.
You have a point, and I like your suggestion. I still have time until the day after tomorrow to apply this, along with the other feature request. Can you wait until then?
I'll update you also if I was not able to apply it. If so, you can just send me a pull request.

That's fine. I am not in a rush. Just mentioning that. Also, you might know better if there are some other places you can consider having same logic as well.

And speaking of other things... In the confirm dialog, if you have the title too long to fit it into one line, it will be cut as on wrapping it's still going to have height == 40. Is there any reason why you made it fixed?

I can also fix that. I set it to 40 since it was the recommended height, but I forgot to consider long titles.
BTW, thanks for raising these issues/suggestions.

I will also add your suggested implementation for MaterialDialogs.ShowSnackbarAsync().

Version 1.0.6 has been released, adding MaterialDialogs.ShowConfirmAsync() which returns Task<bool>. Also,  the title of the alert dialog now breaks line when it is long.


execution optiomization, redundant validation.

Hello!
I'm noticed a little problem with response_model feature:
Code sample:
@router.patch("/settings/swipes", response_model=schemas.UserSwipes, status_code=200)
def update_users_settings_preferences(
        user_update: schemas.UserSwipes,
        response: Response = Response,
        token: str = Header(...),
        db: Session = Depends(get_db)):
    try:
        ...

class UserSwipes(BaseModel):  # Consider UserProfile attributes as low boundary
    smoking_low: Optional[int] = Field(..., ge=0, le=4, description="Minimal boundary smoking", example=2)
    smoking_high: Optional[int] = Field(..., ge=0, le=4, description="Maximum boundary smoking", example=3)
    alcohol_low: Optional[int] = Field(..., ge=0, le=4, description="Minimal boundary smoking", example=2)
    alcohol_high: Optional[int] = Field(..., ge=0, le=4, description="Maximum boundary smoking", example=3)

    @root_validator
    def ensure_bigger(cls, values: dict[str]) -> dict[str]:
        old_k_v = list(values.items())[0]
        for k, v in values.items():
            if 'low' in k:
                old_k_v = k, v
            else:
                if k.split('_')[0] == old_k_v[0].split('_')[0]:
                    if old_k_v[-1] > v:
                        raise Exception('Minimal value biggest that Maximum item!')
                else:
                    raise Exception("'high' item must follow 'low' item.")
        return values

This @root_validator executes twice because of respomse_model and user_update: schemas.UserSwipes.
But obviously you don't need to execute a  validation a second time.

You validate the input, and then you validate the output... What's the problem here?

You validate the input, and then you validate the output... What's the problem here?

I think there is no need to validate at the response model if you already validating at user_update unless you are modifying UserSwipes data. If you are modifying the data, then may be response validation is also necessary(totally depends upon your usecase).

I think there is no need to validate at the response model if you already validating at user_update unless you are modifying UserSwipes data. If you are modifying the data, then may be response validation is also necessary(totally depends upon your usecase).

I think there is no need to validate at the response model if you already validating at user_update unless you are modifying UserSwipes data. If you are modifying the data, then may be response validation is also necessary(totally depends upon your usecase).

So your suggest just to remove response_model parameter? I will agree with you, but it's a little bit inconvient, cuz by this parameter you can easily figure out what happens at this function (like at standard function annotation) also you can easily fold it and when you will see return some_model without response_model you will think that you just forgot it.

I think there is no need to validate at the response model if you already validating at user_update unless you are modifying UserSwipes data. If you are modifying the data, then may be response validation is also necessary(totally depends upon your usecase).

So your suggest just to remove response_model parameter? I will agree with you, but it's a little bit inconvient, cuz by this parameter you can easily figure out what happens at this function (like at standard function annotation) also you can easily fold it and when you will see return some_model without response_model you will think that you just forgot it.

Thanks for the help here @Kludex and @krishnardt ! 👏  🙇
If you solved your original problem, then you can close this issue ✔
...otherwise, please provide a full, minimal, self-contained example that I (we) can copy paste to understand better your use case. It's not quite obvious to me what you are trying to achieve or the problem you are seeing. 🤓

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Text Formatting Instructions Problem 4

Just a suggestion.  Maybe breakdown the formatting of the instruction a little more so it's easier to break down and read.
ex.
ReactDOM offers a simple method to render React elements to the DOM which looks like this: ReactDOM.render(componentToRender, targetNode). The first argument is the React element or component that you want to render. The second argument is the DOM node that you want to render the component within. As you would expect, ReactDOM.render() must be called after the part in your code where you declared the element you want to render.
to:
ReactDOM.render(componentToRender, targetNode) is ReactDOM's simple method to render React elements to the DOM.

The first argument is the React element or component that you want to render.
The second argument is the DOM node that you want to render the component within.

ReactDOM.render() must be called after your declared variables that you want to render.

Ok! I think this is a generally good suggestion. I applied some edits to make it look more like this. Thanks for the feedback!


Can the libaray load a huge exist image file but not create a new one?

I have to process an huge tiff image, if loaded by image sharp ,it will throw an exception. How to load an exist large tiff file using this library.

Hi,
No this library is not able to load a tiff by it's own. It relies on ImageSharp for loading common file formats like tiff.
What is the error you get with ImageSharp ? which version does you use ?


Inconsistent Homepage Links

The links at different places are inconsistent
NPM 1:   http://ondras.github.com/rot.js (404)
NPM 2:   http://ondras.github.io/rot.js/hp/ (redirects to actual url)
README:  https://ondras.github.io/rot.js (redirects to actual url)
ACTUAL URL: https://ondras.github.io/rot.js/hp/

Unfortunately it is not really possible to fix this only via PR  ^^

Okay, there is a room for improvement here.

I would say that the /hp is an implementation detail; the main page should be https://ondras.github.io/rot.js -- as this is the canonical entry point for all GitHub-hosted pages. Will update all locations to this one.

Should be fixed now.


llamacpp/quantize binary in git repo

currently there is a binary file distributed as part of the git repository.
I understand it simplifies the distribution, so I am opening the issue just to not track it somewhere.
What is the plan for it?  Should it be a git submodule and built from the llama.cpp repository?

@tiran Wondering if you might have cycles to work on this for the May 30 release. Let us know and we can pop it onto the 5/30 milestone, or we can keep it on the backlog for now.

End of May is doable. I'm going to need somebody with a Mac book to test the new package.

we shouldn't put a binary in git.
Ideally if we need it, we'd build it and attach it to releases.  Also dev instructions.
Do we need a fork of llama.cpp to have fixes for quantize and build that in our build?
Also I can test on Mac

The idea is to move the quantize binary into a separate project and Python package. This allows us to have a conditional dependency on the binary. MacOS users will then get the binary automatically. I have created https://github.com/tiran/instructlab-quantize/ .
# requirements.txt
instructlab-quantize; sys_platform == 'darwin' and platform_machine == 'arm64'

# Python code
if sys.platform == "darwin" and  platform.machine() == "arm64":
    from instructlab_quantize import run_quantize

    run_quantize("llama.cpp/models/ggml-vocab-llama.gguf", "Q4_K_M")

@tiran This looks like a nice approach. I can test as well once you are ready.

Go ahead, the package is on PyPI and the PR is ready to test.

I have extended my instructlab-quantize package for @cdoern . It now comes with Linux binaries for x86_64 and aarch64 with RHEL 8 ABI. The binaries work on all Linux distros with glibc ABI 2.27 or newer.


[BUG] Cosmetic bug for rich_repr  repr-error

I'm sorry, I tried to come up with a simple example, but I could not create a simple example that generated a repr-error. I'm using Rich 10.4.0 and (ab)use __rich_repr__ to create some translatable help.
Basically, when a repr-error is generated, it contains an item enclosed in single quotes. This item can contain terms that are also enclosed in single quotes. If so, the result is not highlighted properly.

For info, here's what it looks like when I fix the error in my code, using my own colour scheme  (I love this feature of Rich)

Easy fix, will be in the next version.
I wonder if I should offer alternative themes in Rich...

Regarding additional themes: I found it easy enough to design my own themes - although I did have to dig up in the code to figure out some "repr" attribute names, like repr.bool_true.
If I were you, I would just invite people to design their own themes, and provide links.
One thing that I am not too fond of in the default theme for Rich when using Pygments for highlighting some code blocks is that, by default, Rich uses three different colours for True, False, and None for their "repr"  while Pygments uses a single colour for all three.  So, depending on how True/False/None are processed, they can show up in different colours in the terminal.  For example, in your README, we can see True and False showing up in light blue in a code block on the left-hand side, and respectively green and red on the right-hand side.  I think I understand why you chose to use different colours for these three singletons, but I prefer a single colour myself.

Should be fixed in 10.5.0
I find the different highlighting of True / False / None helps when scanning a data dump. The color alone is enough to know what it is.
I see your point that the styles don't match syntax highlighting. In tracebacks I forced the reprs to use the colors from the Pygments theme, because the difference is more jarring when the two are right next to each other. But for printing data structure I find the utility of the default theme to be worth it.

Sorry for not replying sooner: as far as I can tell from my tests, it is fixed. Thanks!


Eridian Weapons

Hi, It is possible to generate any kind of Eridian Weapons using the save game editor?
Thanks in advance.

GD_Manufacturers.Artifacts.Artifact_TypeA
Put that as your manufacturer.


[WIP] SR-936. Segmentation fault on NSMutableData().hash

Issue: https://bugs.swift.org/browse/SR-936
Currently this code: NSMutableData().hash - produces a Segmentation fault.
The reason i found is that on .hash call, CoreFoundation uses _CFIsSwift to check if used class is Swift class or not.
For NSData the result isfalse and runs normally without an error.
For NSMutableData the result is true which causes it to call .hash again and creates a loop.

This issue is also valid for NSCharacterSet and NSMutableCharacterSet as they return true in _CFIsSwift as they are not contained in __CFRuntimeObjCClassTable array.

@parkera can you point in any direction for this one?

Would this work as a fix? Link

@phausler can you take a look at this one?

changing the class tables would be a rather divergent change from how CF handles this in objc; I would consider that divergence a breaking change that would not be able to be merged back to the internal CF.
There are few issues at hand here:

we need factory pattern initializers to actually return NSCF types from the init methods
we need to have dynamic dispatch callouts to the NS types that cover all of the cases like for example hashing
we need many more unit tests to verify all of this

So what would be the best direction to take with this atm?
Using a same workaround as in workaround commit for NSMutableData but for other classes that possibly used in _CFIsSwift check?
Or is there better approach to this? I can't quite get it.

When using any NS(Mutable)CharacterSet methods that calls to CoreFoundation methods, for example: addCharacters(in: ), removeCharacters(in: ) - the use ofCF_SWIFT_FUNCDISPATCHV leads to crash as there is no methods that are set to __CFSwiftBridge in __CFInitializeSwift for NSMutableCharacterSet.
Implementing this methods leads to infinite loop, as _CFIsSwift returns true.
This also causes the crash of CharacterSet as described in: https://bugs.swift.org/browse/SR-3215.
But CharacterSet crahses can be fixed by using _NSCFCharacterSet in initializer instead of NSCharacterSet

@phausler is it possible that #1035 can be a possible fix for this (segfault) issues?
I've tried using the factory initializer in this commit and it seems to be working, but I'm not exactly sure if I was using it correctly.

NSData should be using factory patterns but there are some edge cases I have not yet worked out - primarily how DI rules get enforced with swift. I need to do some more research to figure out how we can get that to work

Thanks for the answer :)
I think that factory initializer as it is right now is already a big step. Hopefully NSCharacterSet's issues causing segmentation faults could be fixed more easily than NSData's.
Also while I was trying to implement factory initializer for NSData I've faced some issues, like fields not allowing access.
For example _NSSwiftData's _backing did not allow access to setter or getter, that's why I've switch it with NSData. This is probably one of many edge cases that you've mentioned.

yea NSCharacterSet should be dramatically easier to implement as a factory pattern since it funnels a bit cleaner

This pull request seems to have gone stale, and has conflicting files. It's also not clear whether other requests have superseded it. In the case that it's still required, please re-open with a rebased version of the change.


setBackgroundColor with transparent,but it don't work

here is code:
 cropImageView.setBackgroundColor(getResources().getColor(R.color.transparent));
here is my "transparent" :)
 <color name="transparent">#00ffffff</color>
well,i try to change the value,for example,#70ffffff,it work,but,when the transparency too low,for example,#20ffffff,it don't work totally,it may use the default backgroudColor i guess.
or may there is a api :isShowOverlayBackground(),or sth like that that i not found??
i don't know if i explain well,but since you guy speak English,so i guess you know what i talk about;
hope everything fine,thankyou

see Visual Customization

BackgroundColor
Default: #77000000
The color of the crop overlay outside of crop window area, covering parts of the cropping image outside of the crop window.
Make sure the background has some transparency so the cropping image will be visible.

actually,i have read  Visual Customization several times before(just mean i am not that kind of always ask autho whithout reading your introduction)..
i want to let The color of the crop overlay outside of crop window area,to be transparent at all~~~~
that is why i set setBackgroundColor(R.transparent).
but it dosen't work..
but if i set setBackgroundColor(R.black),it work.
so what's happened.. :)
happy weekend

It was a poor choice of naming, didn't think it will be so confusing.
cropImageView.setBackgroundColor is Android method that affects the background color of the widget.
you need to change the overlay using custom attribute on the xml:
<com.theartofdev.edmodo.cropper.CropImageView
  xmlns:custom="http://schemas.android.com/apk/res-auto"
  android:id="@+id/cropImageView"
  android:layout_width="match_parent"
  android:layout_height="0dp"
  android:layout_weight="1"
  custom:cropBackgroundColor="#77000000"/>

wow,it(using custom attribute on the xml:) really work!thank you..


[Not TestBench]Can't start DFRefactor

I accidentally compiled & started DFRefactor (from the studio) and I got the following error (rough translation from Dutch):
The application can not be started because the side-by-side configuration is invalid. Check the application logs or use the command-line program sxstrace.exe for more information.
I can't say I've ever seen this error before. I've tried booting DFRefactor from the TestBench as well, but that does nothing either.
I'm not sure how useful this bug report is, but it is something I came across by accident and it doesn't seem like expected behaviour.

Faulty .manifest files cause this.
To solve this we should get rid of the AppSrcManifestFiles.zip and also all COM CodeJock components from the Program folder (*.ocx).

The AppSrcManifstFles.zip has been removed and all programs has been set to automatically build the manifest file and embedd it. That should together take care of the problem.


Update and correction on main.css

Meyer's CSS reset is already being used for this - see index.html:
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/meyer-reset/2.0/reset.min.css"
        integrity="sha256-gvEnj2axkqIj4wbYhPjbWV7zttgpzBVEgHub9AAZQD4=" crossorigin="anonymous" />


Fix potential panic in anchore client

Backport #2828 to 0.40.x

No need to backport, not relevant to this version.


Image Processing docs

Description
Expanded documentation for Harris and Hessian detectors.
References
https://github.com/boostorg/gil/pull/350, https://github.com/boostorg/gil/pull/364
Tasklist

[ ] Check if the docs are in the final output
[ ] Ensure all CI builds pass
[ ] Review and approve

I agree with @mloskot : markdown documentation such as the toplevel *.md files is intended to be browsed by contributors who review the repo on github (which provides markdown rendering built into their portal) or quickly glance over them in purely textual form on your local machine.
Any end-user documentation (tutorials, API docs, etc.) needs a bit more care, i.e. is actually compiled into html and possibly other formats using sphinx. This is published online in https://boostorg.github.io/gil.
Build the docs locally by running bjam / b2 inside gil/doc and review the generated HTML to make sure your changes are compiled correctly.


fix(Gradle): Fix regression when project uses Gradle < 7.2.0

In a previous commit (1), support for Composite build was added using Gradle Internal API. Unfortunately, this introduced a regression for all projects using Gradle < 7.2.0 which could not be analyzed anymore. This commit fixes the regression by using reflection to call the internal API.
For projects running Gradle < 7.2.0 and using the composite build feature, the behavior is restored to the previous one i.e. it will throw a NullPointerException when accessing the group ID of a subproject from an included build.
Solves https://github.com/oss-review-toolkit/ort/issues/6419.
Signed-off-by: Nicolas Nobelis<EMAIL_ADDRESS>

@mnonnenmacher  can we please merge this ?
The CI test failure is unrelated.

@nnobelis Just noticed that you should have used "Fixes" instead of "Solves" to auto-close the issue. Anyway, I'll close it manually.

The CI test failure is unrelated.

Just fixed it here https://github.com/oss-review-toolkit/ort/pull/6434.