Please get on Gitter

It would be great if the TypeScript repo could follow the example of the CoreCLR and CoreFx guys and create a Gitter room for general chatter.

I've brought this up with the team previously. I was personally up for it, but there was a concern over moderation.
I think that in practice, moderation wouldn't be a real issue. In my experience, the IRC channel is reasonably well-conducted. Also, we could always turn Gitter off if we weren't pleased.

Ask and ye shall receive https://gitter.im/Microsoft/TypeScript

Awesome, thanks!
On Fri, May 22, 2015 at 19:36, Microsoft/TypeScript
<EMAIL_ADDRESS>wrote:
Ask and ye shall receive https://gitter.im/Microsoft/TypeScript [https://gitter.im/Microsoft/TypeScript]
—
Reply to this email directly or view it on GitHub
[https://github.com/Microsoft/TypeScript/issues/3254#issuecomment-104739421] .[https://github.com/notifications/beacon/AAK4QhwifFE07DUQgBSTQRzi_dD1_h7zks5oL26UgaJpZM4Ek8AM.gif]


[1.9.x] Use cache change pool when DYNAMIC_RESERVE [7020]

Adds a DYNAMIC_REUSABLE memory mode
This memory mode starts with an empty pool (much like DYNAMIC),
but the allocated slots for CacheChange are not freed, they are
added to the pool of free changes for future reuse insted.

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Failing tests are not related.


cargo build fails under Ubuntu 22.02 on WSL2

ace@UNITINU:~/espressif-trainings/intro/hardware-check$ cargo build --release
(...)
error: failed to run custom build command for esp-idf-sys v0.30.4
(...)
/usr/bin/python3: No module named pip

partial solution: sudo apt install python-pip3
however, then this happens (same error occurs when running in Docker with the supplied docker config instead):
  esptool.py v3.3.2-dev                                                                                Creating esp32c3 image...                                                                                Merged 1 ELF section                                                                                Successfully created esp32c3 image.                                                                                Generated /home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/build/libespidf.bin                                    [995/995] cd /home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/build/esp-idf/esptool_py && python /home/ace/.espressif/esp-idf-release/v4.4/components/partition_table/check_sizes.py --offset 0x8000 partition --type app /home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/build/partition_table/partition-table.bin /home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/build/libespidf.bin                                                                                libespidf.bin binary size 0x22130 bytes. Smallest app partition is 0x100000 bytes. 0xdded0 bytes (87%) free.
  cargo:root=/home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out
  cargo:rerun-if-changed=/home/ace/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-sys-0.30.4/src/include/esp-idf/bindings.h
                                                                                --- stderr                                                                                fatal: No names found, cannot describe anything.                                                                                fatal: No names found, cannot describe anything.
    WARNING: The script virtualenv is installed in '/home/ace/.local/bin' which is not on PATH.
    Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  fatal: No names found, cannot describe anything.                                                                                fatal: No names found, cannot describe anything.                                                                                fatal: No names found, cannot describe anything.                                                                                Output: "/home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/bindings.rs"
  Bindgen builder flags: ["/home/ace/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-sys-0.30.4/src/include/esp-idf/bindings.h", "--rust-target", "1.47", "--blocklist-function", "strtold", "--blocklist-function", "_strtold_r", "--blocklist-function", "v.*printf", "--blocklist-function", "v.*scanf", "--blocklist-function", "_v.*printf_r", "--blocklist-function", "_v.*scanf_r", "--blocklist-function", "esp_log_writev", "--no-layout-tests", "--with-derive-default", "--ctypes-prefix", "c_types", "--generate", "functions,types,vars,methods,constructors,destructors",
"--use-core", "--no-rustfmt-bindings", "--", "-D__bindgen", "-DHAVE_CONFIG_H", "-DMBEDTLS_CONFIG_FILE=\"mbedtls/esp_config.h\"", "-DUNITY_INCLUDE_CONFIG_H", "-DWITH_POSIX", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_ringbuf/include", "-I/home/ace/espressif-trainings/intro/hardware-check/target/riscv32imc-esp-espidf/release/build/esp-idf-sys-4ad62538e5233c10/out/build/config", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/newlib/platform_include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/freertos/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/freertos/include/esp_additions/freertos", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/freertos/port/riscv/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/freertos/include/esp_additions", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hw_support/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hw_support/include/soc", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hw_support/include/soc/esp32c3", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hw_support/port/esp32c3/.", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hw_support/port/esp32c3/private_include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/heap/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/log/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/lwip/include/apps", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/lwip/include/apps/sntp", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/lwip/lwip/src/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/lwip/port/esp32/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/lwip/port/esp32/include/arch", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/soc/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/soc/esp32c3/.", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/soc/esp32c3/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/hal/esp32c3/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/hal/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/hal/platform_port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_rom/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_rom/include/esp32c3", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_rom/esp32c3", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_common/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_system/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_system/port/soc", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_system/port/include/riscv", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_system/port/public_compat", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/riscv/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/driver/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/driver/esp32c3/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_pm/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/efuse/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/efuse/esp32c3/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/vfs/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_wifi/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_event/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_netif/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_eth/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/tcpip_adapter/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_phy/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_phy/esp32c3/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_ipc/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/app_trace/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_timer/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/mbedtls/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/mbedtls/mbedtls/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/app_update/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/spi_flash/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/bootloader_support/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/nvs_flash/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/pthread/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_gdbstub/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_gdbstub/riscv", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_gdbstub/esp32c3", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/espcoredump/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/espcoredump/include/port/riscv", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/wpa_supplicant/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/wpa_supplicant/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/wpa_supplicant/esp_supplicant/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/ieee802154/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/console", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/asio/asio/asio/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/asio/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/cbor/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/unity/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/unity/unity/src", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/cmock/CMock/src", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/coap/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/coap/libcoap/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/nghttp/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/nghttp/nghttp2/lib/includes", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp-tls", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp-tls/esp-tls-crypto", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_adc_cal/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_hid/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/tcp_transport/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_http_client/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_http_server/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_https_ota/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_lcd/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_lcd/interface", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/protobuf-c/protobuf-c", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/protocomm/include/common", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/protocomm/include/security", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/protocomm/include/transports", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/mdns/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_local_ctrl/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/sdmmc/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_serial_slave_link/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/esp_websocket_client/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/expat/expat/expat/lib", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/expat/port/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/wear_levelling/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/fatfs/diskio", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/fatfs/vfs", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/fatfs/src", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/freemodbus/common/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/idf_test/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/idf_test/include/esp32c3", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/jsmn/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/json/cJSON", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/libsodium/libsodium/src/libsodium/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/libsodium/port_include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/mqtt/esp-mqtt/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/openssl/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/spiffs/include", "-I/home/ace/.espressif/esp-idf-release/v4.4/components/wifi_provisioning/include", "--sysroot=/home/ace/.espressif/tools/riscv32-esp-elf/esp-2021r2-patch3-8.4.0/riscv32-esp-elf/bin/../riscv32-esp-elf", "-I/home/ace/.espressif/tools/riscv32-esp-elf/esp-2021r2-patch3-8.4.0/riscv32-esp-elf/bin/../riscv32-esp-elf/include", "-x", "c", "-DESP_IDF_COMP_PTHREAD_ENABLED", "-DESP_IDF_COMP_NVS_FLASH_ENABLED", "-DESP_IDF_COMP_ESP_TLS_ENABLED", "-DESP_IDF_COMP_ESP_HTTP_CLIENT_ENABLED", "-DESP_IDF_COMP_ESP_HTTP_SERVER_ENABLED", "-DESP_IDF_COMP_ESPCOREDUMP_ENABLED", "-DESP_IDF_COMP_APP_UPDATE_ENABLED", "-DESP_IDF_COMP_ESP_SERIAL_SLAVE_LINK_ENABLED", "-DESP_IDF_COMP_SPI_FLASH_ENABLED", "-DESP_IDF_COMP_ESP_ADC_CAL_ENABLED", "-DESP_IDF_COMP_MQTT_ENABLED", "-DESP_IDF_COMP_VFS_ENABLED", "-DESP_IDF_COMP_SPIFFS_ENABLED", "-DESP_IDF_COMP_FATFS_ENABLED", "-DESP_IDF_COMP_SOC_ENABLED", "-target", "riscv32"]
  /home/ace/.espressif/esp-idf-release/v4.4/components/freertos/port/riscv/include/freertos/portmacro.h:439:20: warning: section does not match previous declaration [-Wsection]
  /home/ace/.espressif/esp-idf-release/v4.4/components/freertos/port/riscv/include/freertos/portmacro.h:271:20: note: previous attribute is here
  /home/ace/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-sys-0.30.4/src/include/esp-idf/bindings.h:69:10: fatal error: 'esp_crt_bundle.h' file not found
  /home/ace/.espressif/esp-idf-release/v4.4/components/freertos/port/riscv/include/freertos/portmacro.h:439:20: warning: section does not match previous declaration [-Wsection], err: false
  /home/ace/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-sys-0.30.4/src/include/esp-idf/bindings.h:69:10: fatal error: 'esp_crt_bundle.h' file not found, err: true
  Error: Failed to generate bindings

Juraj fixed it:

Try upgrade to newer version of esp-idf-sys. It might solve the problem. 0.31.6 works for me.

I unfortunately don't have the time for a PR fix that includes updating all deps & checking on all supported platforms. Just using latest of everything should work though.


python3Packages.influxdb-client: 1.15.0 -> 1.17.0

Motivation for this change
Update to latest upstream release 1.17.0
Change log: https://github.com/influxdata/influxdb-client-python/releases/tag/v1.17.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125694 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.influxdb-client
python39Packages.influxdb-client

Result of nixpkgs-review pr 125694 at 517e76b5 run on aarch64-linux 1

3 packages built successfully:

home-assistant
python38Packages.influxdb-client
python39Packages.influxdb-client


Preloading date doesn't work

Preloading a date doesn't work.
Event in the examples page.
Here is my app:

HTML
<input class="calendar form-control" name="end_date" aria-describedby="basic-addon1"             data-defaultDate="2016-03-31 23:59:59 -0300" />
JS
flatpickr(".calendar", {dateFormat: "m/d/Y"});
Using the latest version of your lib.
Also, in your own example page it's not working properly, as you can see in the screenshot

This date is parseable, as you can see on the output of Date.parse() below
> Date.parse("2016-03-01 00:00:00 -0300") <-<PHONE_NUMBER>000
I'm using Chrome on a Mac 10.11 El Captain

Thanks for the report!
An unnecessary and extra flatpickr object was getting created on altInput.
All fixed now :zap:
http://chmln.github.io/flatpickr/#defaultdate
Shall any problems arise in the future, please open a new issue.


added yion to template

moved down a pixel and is updated to current main branch of Anticept/httyd-place

Make sure you coordinate with a repo collaborator so we know to look for the pr


Respect initial ordering Pie/Donut

When the values of a Pie/Donut change the pieces jump around.
I've created a video to better explain what I mean:
https://www.dropbox.com/s/s5r0cnlobzuj531/donut.mov?dl=0
The expected behavior is that the positioning of the elements respects the input data.
Am I making sense?
(btw, I love @vx 👌  )

Hey @hshoff thank you so much for the late reply. It seems that pieSort works like a charm 👌
Here I tried to animate that transition but it does very strange things haha
https://www.dropbox.com/s/lky9u45qqfwvyiw/transition.mov?dl=0
Anyway, animation is not need at this point. Thanks again!

Sometimes you'll need custom tween-ers to interpolate between states correctly. Not sure if that's the problem here without seeing a code snippet. react-move should support custom tweening. Here's a donut chart example.

@williaster I was just using .vx-pie-arc{ transition:500ms; } to animate.
That react-move animation is very sexy!


Options cannot be placed as 1st or 2nd argument

This should work:
$ pypy --no-space 5 🌴
But it currently returns an error "Size must be a number".
Right now, options must be placed after the size and emoji. It would be nice if they could be written anywhere in the command, like this:
$ pypy --no-space 3 👻 --no-copy

👻
👻👻
👻👻👻
👻👻
👻

Maybe we have to use a command line parser to handle the arguments in a cleaner way.
This project is going too far :) anyway feel free to send me a PR, I'll be busy for a moment, no time for dev right now ..


Logs and some test changes to help debug test failure in Test_CLI_Delete

Description
Changes to debug test failure issue: https://github.com/radius-project/radius/issues/6872
Used a different app name and namespace for the failing test instead of reusing from a previous one in the file
Added more logs
Type of change

This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: #issue_number
Auto-generated summary

🤖[deprecated] Generated by Copilot at fb725ff
Summary
🗑🐳🧪

This pull request adds a test case and a test data file for deleting an application with unassociated resources using the CLI. It also improves the output message for deleting an application and adds logging to the validation functions.

Sing, O Muse, of the valiant code reviewers who scrutinized the pull request
And of the skillful coder who improved the CLI with his diligent quest
To make the output message clearer when an application is deleted by name
And to test the deletion of unassociated resources, those containers of fame

Walkthrough

Change the output message for deleting an application to include the application name (link)
Add a new bicep template file corerp-kubernetes-cli-with-unassociated-resources.bicep that defines an application with two unassociated resources (link)

Declare new variables for the application name and the template file path of the application with unassociated resources (link, link)
Deploy the application with unassociated resources and validate that the pods are running (link)
Delete one of the unassociated resources using the management client (link)
Delete the application without deleting the remaining resources using the DeleteAppWithoutDeletingResources helper function (link)
Redeploy the application using an empty template file (link)
Delete the other unassociated resource using the management client (link)

Modify the validation functions ValidateObjectsRunning and matchesActualLabels to log the number and labels of the deployed resources for debugging purposes (link, link, link)

/ok-to-test


Pleiotropy

Simulation of multiple traits with pleiotropy.
Input:
Trait model:

Mean vector
Covariance matrix

Phenotype simulation (can set a different function for pleiotropy):

Degree of pleiotropy
Heritability vector
TraitModel vector (one for pleiotropy, another for individual ones)

Steps required:

[ ] Create a new TraitModel to simulate traits from a multivariate normal distribution
[ ] Create a new function to simulate multiple traits
[ ] Statistical tests for pleiotropy

https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-03804-y
This paper would be a good starting point for pleiotropy. However, we will need the following inputs:

Number of common causal sites (pleiotropy)
Number of causal sites that are specific to the traits
Distribution of causal sites indicated in 1 and 2
Number of traits

We will need to implement pleiotropy without influencing the architecture of sim_phenotype function, so we will need to think about how to make the input in the correct structure. The SLiM documentation had an example with 2 traits, so maybe we can start with 2 traits as a starting point.


Improve detecting whether default can be derived

This checks if a struct contains a required member for which Default is not implemented (Enums or other structs which don't have Default). If it does, Default will not be derived for that struct.

Hey thanks for this.
I think the idea here is interesting, but I am a little confused about how practically useful it is. Maybe I am missing something, but if you have an enum embedded deeply within your spec struct, and want to derive Default, then this would basically recursively search all containing structs recursively and disable it on them, right?
If that's the case, isn't it better to not ask to derive Default? Because you'll only be able to practically derive it for a small subset of the structs anyway?
(The thing I do for enums is to derive default anyway, and then add a couple of manual impl Default for ThisEnum to polyfill in the handful of enums to allow Default to work on the whole struct, and I suspect this might make this harder)

The thing I do for enums is to derive default anyway, and then add a couple of manual impl Default for ThisEnum to polyfill in the handful of enums (while https://github.com/kube-rs/kopium/issues/67 is unimplemented) to allow Default to work on the whole struct, and I suspect this new behaviour here might make this harder.

Yes, but this change was useful for me when I did not want to go through the code and manually implement default for enums.
My use case was specifically generating types for cert-manager.
Here's the CRD.
CertificateSpec has a lot of options, most of which I don't care about in most cases. To make it easier to use, I often just write
CertificateSpec {
  some_prop: value,
  ..Default::default(),
}

For that to work, I need default to be derived on CertificateSpec. So I pass --derive=Default to kopium.
Now, the output won't compile, because Default is also derived on CertificateAdditionalOutputFormats.
/// CertificateAdditionalOutputFormat defines an additional output format of a Certificate resource. These contain supplementary data formats of the signed certificate chain and paired private key.
#[derive(Serialize, Deserialize, Clone, TypedBuilder, Debug, PartialEq, JsonSchema)]
pub struct CertificateAdditionalOutputFormats {
    /// Type is the name of the format type that should be written to the Certificate's target Secret.
    #[serde(rename = "type")]
    pub r#type: CertificateAdditionalOutputFormatsType,
}

/// CertificateAdditionalOutputFormat defines an additional output format of a Certificate resource. These contain supplementary data formats of the signed certificate chain and paired private key.
#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, JsonSchema)]
pub enum CertificateAdditionalOutputFormatsType {
    #[serde(rename = "DER")]
    Der,
    #[serde(rename = "CombinedPEM")]
    CombinedPem,
}

CertificateAdditionalOutputFormat is only used inside an Option<Vec<_>>, so I don't need Default on it. This PR prevents default from being derived on it, while the main CertificateSpec can stay Default.
I could of course manually change it, but I want to avoid manual changes in generated code.
Also, this PR contains another small change:
TypedBuilder is no longer derived on enums, which always gave an error for me.  I can move that into a separate PR, because I assume that being derived for enums is a bug.

CertificateAdditionalOutputFormat is only used inside an Option<Vec<_>>, so I don't need Default on it. This PR prevents default from being derived on it, while the main CertificateSpec can stay Default.

Ah, thanks for clarifying.  You're searching the other way from what I was expecting. I thought you wouldn't get a Default derive on CertificateSpec with this change. The PR makes more sense now.
(For clarity I typically would have generated this to crds/certificate.rs and in crds/mod.rs add my polyfills to avoid messing with generation, but I do think your argument here is strong in that you shouldn't need to have a default derive on something that's option wrapped like this).
I like the TypedBuilder fix also. Lemme look in more detail.

I now added a flag --force-derive-default that re-enables the previous behaviour for derive, because some users may still want to implement Default for a few enums externally instead, as you suggested.
Please let me know if that sounds okay to you, or if I should instead extend the syntax for --derive or do something else. In my opinion, this new flag is the simplest and probably most understandable approach to iimplement this.

I've implemented your suggestions. The can_derive_default() does not yet take into account whether for nullable fields, a default:  value is provided in the CRD. However, such defaults are currently ignored by kopium anyway, so I don't think it's an issue.
I'll check if I can add a way to also implement support for that in another PR, but I'm not sure if that is going to work out.

I've implemented your suggestions. The can_derive_default() does not yet take into account whether for nullable fields, a default:  value is provided in the CRD. However, such defaults are currently ignored by kopium anyway, so I don't think it's an issue.
I'll check if I can add a way to also implement support for that in another PR, but I'm not sure if that is going to work out.

Yeah, agreed, that is an orthogonal concern atm. But proper handling of it would also be very welcome!

I'll merge in and probably do a release early next week. If you have other things you want to try like the default handling I can wait for that.
Thanks a lot for this!

FYI, I think this behavior is currently always on (not opt-in like expected) - even without the --smart-derive-elision flag, none of my structs now derive Default after this new release. I'll keep taking a look to see why that is happening, but just thought I'd flag that here.

Thank you both. I'll ship a patch release for this.


Test Maven project building

Description:
Test building projects created using the Integration Project and test separately created projects. (Need to test this for all the child projects)
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Tested maven module and profile restructuring with children modules.


Fix a memset on a non-trivial object.

The irony here is that we're running a memzero on this object after its implicit constructor ran, which already set everything to zeroes.

The failures are unrelated flakes. Merging.


Duplication in Cth Thread Tracing

Projections tracing for Cth threads currently happens in multiple, often redundant locations. Projections automatically starts and stops tracing via thread listeners (see traceAddThreadListeners and co.), while the thread infrastructure itself also directly makes tracing calls (e.g. traceResume, traceSuspend). The listeners are automatically created when using [threaded] entry methods, meaning they won't be created and used automatically when using Cth threads directly (as, for example, NAMD does). Thus, removing the direct tracing calls done by the thread infrastructure would cause regressions in tracing for NAMD.
Currently, this is handled via nested tracing support that uses a stack and inserts extra calls to beginExecute and endExecute to avoid overlapping EPs, but it's polluting the logs with extra blocks that don't really correspond to anything in the execution. For example the first two and last two lines in this log snippet correspond to the direct calls from the thread infrastructure, while the inner lines (from 2 4 150 ... to 3 0 150 ...) correspond to the actual resumption of the [threaded] EP:
2 4 0 197237 221 0 0 0 0 0 0 0 172786
3 0 0 197238 221 0 0 172786
2 4 150 197239 -1 0 0 0 0 13258496 0 0 172786
1 24 153 197273 222 0 288 0
20 24 72 197274 223 0 288 2 2
16 197276 0
17 197276 0
3 0 150 197279 -1 0 0 174396
2 4 0 197279 221 0 0 0 0 0 0 0 174396
3 0 0 197281 221 0 0 174396

This unnecessarily inflates log size, increases tracing overhead, and leads to performance, memory, clarity, and accuracy issues in Projections.

After talking with Sanjay, we decided that the best thing to do here is probably just adding a flag to thread creation to toggle the direct calls to tracing from the thread infrastructure.


Configure Azure Pipelines

This configuration builds the application and produces builds for both Debug and Release configurations.

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


Update downloading test models

Summary of Changes

At a high-level, describe this request adds/changes/improves/fixes
You don't need to describe every change but each request should have an overarching theme
Don't mix a lot of big unrelated modifications in one request

Closes #x (each request should address an open issue. Open an issue first to discuss what you'd like to change.)
Motivation
Describe why this request is needed/good/useful etc.
If this information is already captured in detail in the related issue, just provide a high-level statement and link to the issue.
Implementation
While your code changes can be seen in the diff between branches, it may not capture why certain choices were made, what else had had been tried unsuccessfully etc.
Also, depending on the size of the request, many changes may be difficult to read through.
Consider this section as a way to provide context, commentary and an introduction to the code you've written.
At minimum, you should address the bullet points you listed in the summary above in some capacity to guide the reviewer on where to look.
Notes
Any other comments about or implications of this PR?
For example, certain PRs could require rebuilding containers, deleting cached build files or other changes for whoever pulls in these changes on an existing repository.

Build failed!

Build failed!

Build failed!

Build successful!


add timeout to Ping call

most RPC calls, like Ping, ought to respond quickly. if they don't, perhaps we've hit a mysterious window during kubernetes setup where TCP connections end up in a black hole and timeout forever. this is causing issues in CI.

Seeing more of these in the tests. We can add timeouts at various levels in the application.

Client side request timeouts: Adding timeouts to 'dm' commands is pretty easy with golang context/channels but this will only timeout requests when users/tests are using the specific client that implements timeouts. This covers a multitude of network issues as the timeout starts from the time the request is sent out. However each client would have to implement it's own timeout logic (python, golang, JS libs). Seems to best fit the requirement at the moment.

Server side timeouts: There are two areas in which server side timeouts can be implemented.
a) Method level timeouts: Timeouts are implemented in each method i.e when it does external calls and timeouts are returned as any other error. Seems fairly suitable for our use case, but will mean quite a lot of duplication if ALL RPC methods require sensible timeouts.

a) Middleware timeouts: Adding sensible timeouts within a middleware is common, however less suitable for us as the same blanket timeout does to apply to all RPC calls.


Default naming convention

The naming convetion mentioned in docs is useful in some migration situations, would it be better to set it as default?

It would break all existing databases that were created with the default. Fairly sure that’s why it wasn’t changed in SQLAlchemy either.

I have thought about adding the suggested value as something that can be imported. Perhaps a subclass that uses that value if nothing is passed.

Maybe a new metadata object MetaDataWithNamingConvetion? then the db can be initialized as db = SQLAlchemy(metadata=MetaDataWithNamingConvetion)

Hello @davidism , do you have any thoughts on this?


Add package extension for StaticCompiler.jl

I'm not adding any tests for this because I don't want the instability of StaticCompiler.jl messing with the test suite, but it's useful to provide this anyways.
With this, on julia versions 1.9+ (I didn't bother with Requires.jl), you can do
using Bumper, StaticTools
function times_table(argc::Int, argv::Ptr{Ptr{UInt8}})
    argc == 3 || return printf(c"Incorrect number of command-line arguments\n")
    rows = argparse(Int64, argv, 2)            # First command-line argument
    cols = argparse(Int64, argv, 3)            # Second command-line argument

    buf = AllocBuffer(MallocVector)
	@no_escape buf begin
        M = @alloc(Int, rows, cols)
        for i=1:rows
            for j=1:cols
                M[i,j] = i*j
            end
        end
        printf(M)
    end
    free(buf)
end

using StaticCompiler
filepath = compile_executable(times_table, (Int64, Ptr{Ptr{UInt8}}), "./")

and then
shell> ./times_table 12, 7
1   2   3   4   5   6   7
2   4   6   8   10  12  14
3   6   9   12  15  18  21
4   8   12  16  20  24  28
5   10  15  20  25  30  35
6   12  18  24  30  36  42
7   14  21  28  35  42  49
8   16  24  32  40  48  56
9   18  27  36  45  54  63
10  20  30  40  50  60  70
11  22  33  44  55  66  77
12  24  36  48  60  72  84

cc @brenhinkeller

Coverage decrease is expected.

That's awesome!! Nice work Mason!
We could add integration tests on the StaticCompiler or StaticTools side instead where the instability is expected -- could be useful on that end


Adding NValue global constraint

Impelemented the NValue global constraint as a global function.
Currently we only have MiniZinc supporting as a backend solver, but Choco does support it too.

I copied your tests for minizinc, but it seems minizinc does not support nvalue in a nested context (error message: "free variable in non-positive context").
removed it from the nested supported list, but turns out for global functions we don't check the supported nested, only supported (Did we have a reason for this? Anyway i now think it was wrong, we should decompose it)


Log in - gets you to start page

Login issue: Sometimes people log in, sometimes not, cache clear, clear not, I land on the start screen. After some clicks I get into map mode, but still, i do open second char and I land with an error. (403). Anyone can point me right direction? env/conf are right, socket is working but not mentioned at all at wiki lol :)
Just a lil note or personal vision:
Once I used to spent some time installing this crap on debian9, today i think the man who wrote it has lost not his time but others'. Sometimes I think that few functions getting the job are far better than that framework garbage  :( and that composer garbage... ehhh 👍

login issues 1.4.1 #718 seems to work, still, looks like you need competition, time to make that shit mapper from scratch.


tail rotated log files

Hello!
Does stream_exporter tail mode supports file rotation?
I tried to attach log directory and made tail to one of them.
Then file was rotated, after that tail filter did not reacted on trigger words not in new log file nor in rotated.

Hi!
Yes, this is supported, and has worked in my tests, at least. How did you rotate the file?

log dir was attached to docker with exporter, and on host machine was made:
mv ./sys.log ./sys.log1 && touch ./sys.log && chown user:user ./sys.log
exporter writed to log:
2017/11/14 14:59:18 Re-opening moved/deleted file ./sys.log ...
2017/11/14 14:59:18 Waiting for ./sys.log to appear...

when insert needed lines to new file then counter in localhost:9178/metrics doesn't add up
also I reproduced it without docker on my machine
thanks!

Hm, that is odd. I wonder if it is something to do with the permissions being wrong initially? I've been using logrotate, and that has worked for me, at least.
What OS are you using?

maybe logrotate worked with truncate but not mv?
os is ubuntu 16.04 on all hosts, all files are rw-rw-r-- and owned by one user
maybe cause is somewhere in there:
https://github.com/hpcloud/tail/issues/122

Sorry that this has been hanging open for a while. I've spent a bit of time investigating this now, and the root of the issue appears to be a few layers down, in the fsnotify library: https://github.com/fsnotify/fsnotify/issues/194.
There is a pull request which for some reason has not been merged that fixes this. I've manually merged it and am testing it out. Looks very promising so far.


Shut down cleanly

Currently a clean shutdown isn't even attempted unless you do SIGINT, and the shutdown logic suffers from various issues:  #309, #340, #358.
We need to overhaul the shutdown process.

I updated the shutdown process to close the P2P code.
SIGINT is the only way shutdown is intended to happen.   We could add an RPC call but that would be a potential security issue.
It shuts down cleanly for me.


Improving navbar buttons hover

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: windows
Browser chrome
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Kindly raise a PR when you're done.


Monitoring individual PV modules?

This looks like an amazing Python package - thanks loads for sharing!
One quick question:  Can this Python package monitor data for individual PV modules (if the modules are 'smart modules' or the PV modules have power optimizers installed)?  Apparently the Solar Edge monitoring platform captures module-level data, but I don't know if module-level data is available over MODbus.
update: I've looked through the SolarEdge MODbus docs; and the SolarEdge web API specs and, as far as I can tell, neither exposes module-level data :(

One quick question: Can this Python package monitor data for individual PV modules (if the modules are 'smart modules' or the PV modules have power optimizers installed)?

Not as far as I'm aware. While there is more data exposed on higher register addresses not mentioned in the documentation, I have yet to encounter anything that resembles module data.

Cool, thank you for the quick reply!
Whilst it's not documented, apparently it is possible to get module-level data from Solar Edge's API: https://twitter.com/AyrtonBourn/status/1405071870026731523

Whilst it's not documented, apparently it is possible to get module-level data from Solar Edge's API: https://twitter.com/AyrtonBourn/status/1405071870026731523

Luckily there are still ways. You may also want to try polling the SetApp API on the inverter itself. This is accessible via the Wifi hotspot that is enabled when you toggle the switch on newer model inverters. Have a look at solaredge_setapp, or this discussion at solaredge_local.

Cool, thank you for the quick reply!
Whilst it's not documented, apparently it is possible to get module-level data from Solar Edge's API: https://twitter.com/AyrtonBourn/status/1405071870026731523

I wasn't able to find a way to get the module-level data from the inverter itself using modbus.  However, as you have found out, you can get the (15 min resolution) panel data using the solaredge website API.  I have a python script running that queries the API every 15 minutes and puts the data into an InfluxDB....  Full disclosure that I am not the author of the script in question but I did modify it a bit to "customize" the module names so that they made more sense than the "numbers" that are returned by the API....   Take a look at https://gist.github.com/cooldil/0b2c5ee22befbbfcdefd06c9cf2b7a98 to see if that would be helpful to you...

This still hasn't become available trough the actual modbus ,I'm guessing?


Provide a way to configure the Tenant ID for the authentication

I was using the extension in combination with https://github.com/microsoft/codespace-features/tree/main/src/external-repository in order to clone an Azure DevOps repo in Codespaces. Unfortunately, I was not able get authorized to my repo.
The authorization failed because I have used an account present on multiple Entra ID tenants and the Azure DevOps Organization for the repo to be used was on a specific tenant. This extension does not allows to specify the tenant so in absence of it the authentication occurs on the default tenant. When the extension is loaded the authentication challenge start with this URL:
https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize...
The user must be able to configure the tenant id (optional) in order to authenticate against this URL:
https://login.microsoftonline.com/[tenantIdFromConfigurationHere]/oauth2/v2.0/authorize...
The Microsoft Authentication Provider for VS Code used by this extension allows to specify the tenant for the authentication with a "magic scope" that should be something like "VSCODE_TENANT: aaa-bbb-ccc"
Ref: https://github.com/microsoft/vscode/blob/56f9e01216f191f7d6b8e32d32b62c816e5a6f77/extensions/microsoft-authentication/src/AADHelper.ts#L648
I was thinking to an Environment variable named "AZDO_TENANT_ID" that can be used to build the additional scope 'VSCODE_TENANT:xyz' in this place:
https://github.com/microsoft/ado-codespaces-auth/blob/82aba97a7461c70248c734da83d96578604f7039/src/extension.ts#L55
I started to draft some changes here: https://github.com/liguori/ado-codespaces-auth/commit/099efd689ccbb898ea5d17776c82daddb6a83c4a

To me it makes more sense to put this in extension preferences otherwise it ends up being a random environment variable which you will only know about after reading documentation. See example here https://github.com/microsoft/vscode-azure-account/blob/cd4fe355c3b8741b0d8cd530775c562eb641b2aa/package.json#L137C1-L155C19.
You can customize your devcontainer with VSCode settings so you should be still be able to configure this per repo. https://containers.dev/supporting#visual-studio-code

I have completed the changes and tested/debugged the extension by providing a tenantID as setting and seems to work.
I was unable to test the E2E flow with devContainers and the 'external-repository' feature but as pointed by @ronakj it should work with VSCode settings in devContainer.
Here the PR: https://github.com/microsoft/ado-codespaces-auth/pull/15

Resolved by https://github.com/microsoft/ado-codespaces-auth/pull/15 that bumps the extension to 1.2

This is now released in version 1.2.1 including your fix @liguori. Thank you for the contribution!


Update SignConfig.xml to use stronger cert

Per email thread, we should be using a stronger cert in https://github.com/microsoft/AdaptiveCards/blob/master/source/uwp/Build/SignConfig.xml
(more context here)

@paulcam206 / @matthidinger marking approved since this one seems obvious to be picked up and worked on. thanks!

@paulcam206 this can just come in now right ? Not blocked on anything ?

@paulcam206 if we are doing this for 1.2.1 let's try to get started on this next week. Thanks!


Is there a plan to upgrade docker image to use Ubuntu 16? When will it be upgraded?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):
Apollo installed from (source or binary):
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

Supporting materials (screenshots, command lines, code/script snippets):

Hi @ax7476 thank you for your question. We are currently in the process of upgrading to Ubuntu 18 and even have a branch created for it. We will not be releasing a version that is based on Ubuntu 16 unfortunately.

Is there an approximate release date about updating to Ubuntu 18?

We have a version release coming up in July. You should hear more from us closer to the date. Thank you for your interest in Apollo.


Fix generating terrain icon with certain image formats.

Closes https://github.com/godotengine/godot/issues/84506

texture->get_image() does not return a reference to the texture's image, but it's copy. Thus it's redundant to have 2 Image variables.

@KoBeWi Well, I removed the redunant extra format variable, but I'm looking over the code again and I'm confused what you mean in regards to the image variables.

Ok disregard my comment. I missed that src_image is used twice, otherwise you could just reuse the dst_image ref.

Cherry-picked for 4.2.1.


Firefox saying "This add-on couldn't be installed, it might be corrupt"

Describe the bug
问题描述
The extension is not installing in Firefox version.
To Reproduce
如何复现
Steps to reproduce the behavior:

Go to 'Releases V2.4.8'
Drag and drop the .zip file into addons page in firefox
The error shows up.

Expected behavior
期望行为
The extension will fail to install
Screenshots
截图说明

Please complete the following information):
请补全以下内容

OS: Windows 10
Browser: Floorp (built on firefox)
Extension Version: v2.4.8

https://github.com/josStorer/chatGPTBox/wiki/Install#install-to-firefox


How to assign two host-local IPs to a single NIC?

My goal is to have pod with two IP addresses belonging to the same network, kind of like multi-homing. I have NetworkAttachmentDefinition:
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: mynetwork
spec:
  config: |
    {
      "cniVersion": "0.3.1",
      "name": "mybridge",
      "type": "bridge",
      "bridge": "mybridge",
      "ipam": {
        "type": "host-local",
        "ranges": [
          [
            {
              "subnet": "some values here",
              "rangeStart": "some values here",
              "gateway": "some values here"
            }
          ]
        ]
      }
    }

What I considered already
Two NICs
I could use it to create two interfaces:
annotations:
        k8s.v1.cni.cncf.io/networks: mynetwork@if1, mynetwork@if2

but my network will be broken due to rp_filter == 1, which I can't change.
Assign two static IPs
I could assign two static IPs through POD annotation, but need my solution to scale, i.e. I can't duplicate addresses across POD replicas.

I think you can specify multiple IP addresses with the static CNI plugin: https://github.com/containernetworking/plugins/tree/master/plugins/ipam/static
There's also a whereabouts feature request for multiple IPs (for dual stack, but relevant I think): https://github.com/dougbtv/whereabouts/issues/62


Main has precedence over module in package.json

It appears a recent version of this module has changed the resolution priority. From what i can discern main suddenly has precedence over module. Ie, my build fails because rollup has started pulling in the dependencies' commonjs builds instead of the es builds.
Is this intended?
EDIT:
It appears my usage of main combined with browser is causing main to have precedence... since browser has always had precedence over module or jsnext:main i used @bfred-it's suggestion from https://github.com/rollup/rollup-plugin-node-resolve/issues/55#issuecomment-310306129.
Version 3.0.2 seems to have updated the resolution algorithm enough to break this way of using main and browser. Ie. the following no longer works, as rollup will pull in cjs/index instead of es/index
{
  "main": "node/index.js",
  "module": "es/index.js",
  "jsnext:main": "es/index.js",
  "browser": {
    "node/index.js": "cjs/index.js"
  }
}

EDIT 2:
So this re-raises the question... is there any way of supporting both the browser and module properties but letting module have precedence in ESM aware bundlers, including rollup?

@Rich-Harris hey, this is a pretty big problem because it's currently not possible to use browser field properly.
There are already fixes in PR's, can you please look into them?

Im going to close this as many are reporting this is now fixed in 3.0.3. If you're still experiencing issues, please file a new one or you can comment here and I'll re-open!


deprecated<EMAIL_ADDRESS>

npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

This is not an issue with this module but with the one of its dependencies.


ci: use emulator for the spanner integration tests

For CMake builds we use the emulator to run the spanner integration
tests. The main motivation is the coverage test, which needs to
serialize the tests and runs very slowly against production. Other
builds run fine against the emulator or against production, but testing
locally is usually faster.
The drop in code coverage (0.22%) can be fixed with via #4080, but I think
we should leave that to a future PR.
Fixes #4023

This change is

The build times for the coverage build go down from about 35m to about 25m. Of those 5m are spent in the codecov.io upload.

It would be nice, methinks, if this was a feature of the tests themselves rather than a ci script that runs tests in some special (and difficult to otherwise duplicate) way ... for example, with some form of MakeEmulatorConnection() that would start/stop the emulator, and which could be (conditionally) called from a SetUpTestSuite().  bazel test --test_arg=--use_emulator ... would then just work.
Anyways, a thought.

PTAL


Prevent upload modal & flash message from showing stale messages

Fixes #534
This branch includes the following changes:

Reset messages and errors in ImportResourceTemplate component when HTTP response is successful
Reset messages when update handler is finished
Prevent users from dismissing flash message box, else it never comes back
Extract code to parse a response object into a human-friendly location into a new function in ImportResourceTemplate component
Add Babel plugin for optional chaining (as dev dependency) via the safe navigation (or "Elvis") operator

This lets us safely reach into objects such as HTTP responses without having to check at every level for null or undefined

Coverage increased (+0.3%) to 79.024% when pulling 408e8b5b323ea237ceef6a00f1f467d76dfc824f on refresh_rt_flash_messages_534 into e5582807716eb38fdb7e90012ee5465f6a05326a on master.

If you're in a rush to merge, I can change to "approve" but I think the cleanup would help readability of tests and code.


JupyterLab 3 Update

This modernizes ipysheet for JL3 and makes it a prebuilt extension simplifying the install steps. Unknown what it means for older installations ci cd etc, but others may be interested in the work.

Thanks a lot for the update! And sorry for not looking at it earlier.
It seems to work perfectly on my side. Will merge and test further.

@martinRenou I could be wrong (am on mobile), but last time I checked it looked like this pr dropped support for Jupyter Notebook. Is that intentional?

You're not wrong... I realized it too late.
I am currently adding it back.

I just update my jupyterlab to 3.2.1
I get this error
Error displaying widget: model not found
Can somebody help?

Related: https://github.com/QuantStack/ipysheet/issues/202


Duplication of Widgets

Hi,
Really liking this library over react-grid-layout.
However, not sure if it's been picked up before, but it looks like widgets get duplicated if they are dragged and dropped on widgets of the same type.
Will have a look but if it's a know issue, would love to have a fix.
Thanks!
Update: Odd. It seems that:

The duplication is not consistently occuring
The duplication can also occur when not dragged over the same type

I'm also noticing this issue and it can be reproduced with demo site as well (http://raathigesh.com/dazzle/). You have to drag and drop several times before you hit the issue. @Raathigesh do you know why this maybe happening? It would be great if we can get a fix for this.
Thanks in advance.

I can also reproduce the issue. I will get back to you after doing a bit of digging into this.

Thanks @Raathigesh

Hi @Raathigesh sorry to trouble you but I was wondering did you make any progress on the issue? Thanks!

I'm looking into it but it seems to bit tricky to exactly figure out the reason. The last fix I added also seems to be not working. I will investigate further during the weekend. Could you please update to version 1.2.4 and check whether the issue is still reproducible.

@Raathigesh I tried out version 1.2.4 and I can't reproduce the widget duplication issue on my end so the fix that you put in looks good. Thank you for taking the time to look into it.

I'm closing this for now. Feel free to reopen if this issue surfaces again.


CompileError: command 'arm-linux-gnueabihf-gcc' failed with exit status 4

I'm trying to install on Pi b3+ and getting an error. I tried to manually install grpcio but it didn't fix the problem. Here is the full error.
CompileError: command 'arm-linux-gnueabihf-gcc' failed with exit status 4

----------------------------------------
  Rolling back uninstall of grpcio
Cleaning up...
Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-KA5EiS/grpcio/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-Icbf3Z-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip-build-KA5EiS/grpcio

I tried with --no-deps but it returned without error. I ended reinstalling raspbian and found some other JDK instructions where necessary to install the TF deps.

For those that have not worked at all you have to install these packages
sudo apt-get install libzbar-dev libzbar0

For those that have not worked at all you have to install these packages
sudo apt-get install libzbar-dev libzbar0

Thnak you..it solved my problem with instaling:
pip install matpathlib


Refactor hue discovery to make use of device_registry

Hue component is being rewritten to support V2 API.
Powercalc needs to adopt to these changes by retrieving model information from device registry instead of directly from the Hue component.

Resolved with #350.


Configuration State Machine

Hi,
I'm trying to simulate eFPGA configuration.
The ConfigFSM has three states - state 0 looks for data FAB0_FAB1. State 1 loads FrameShiftState with NumberOfRows and State 2 decrements FrameShiftState until '1' when it returns to State 1.
I expected to see the data being sent and loaded into the Frame_Data_Reg in state 2 as FrameShiftState decrements but it is not changing. This seems to be because the data is loaded into the FrameAddressRegister in state 1 but not state 2.
Is my understanding correct? I have created my own test configuration data so it might be wrong...
Best regards,
Rob.

Hi,
Sorry my mistake - I now see that the WriteData send to the Frame_Data_Reg does not go via the FrameAddressRegister but is muxed in eFPGA_Config.
Best regards,
Rob.


Module Federation with library.type (window) is not working

What is the current behavior?
I currently have three applications. Due to the need to integrate with micro-frontends, JavaScript needs to be loaded within a scoped environment, so it's necessary to set 'library.type' to 'window'. When there are two applications (where the first application provides components, and the second application only uses components without providing any), setting the 'library.type' of the provider to 'window' meets the expectations. However, when the second application starts providing components to the outside, setting its 'library.type' to 'window' leads to issues. The second component fails to find the components from the first application when attempting to load them.

What is the expected behavior?
The expectation is that the components provided by multiple applications can be accessed through mounting on the 'window'.
I have provided a simple repository with reproducible code.

The main goal is to mount sub-applications with module federation in a micro-frontend application, where the final effect can be fully demonstrated on this website with each application displayed.

Hello, sorry for delay, because window is not design for such purposes, you can use window when you have mutliple containters on the same page, but here you have different containers on different pages, but anyway you can do it using low level API:

Also don't forget to load:

Feel free to feedback


🚨 Example PR

Playing with the code :)

BTW public function getWPContentSubDirectory() : string { when a function fails it

returns the base value, null in PHP
or throws an exception

any other behavior is highly opinionated.

@leonstafford Hm??


[FEAT/44] Added Facebook OAuth2 To Authenticate Users

Confirmed: The code has been verified as safe.🛩 ✅
Implemented an endpoint for user login via social media accounts. It manages all server-to-server communications required to authenticate the user.

This code implements social authentication safely, ensuring no harm to the database model. It creates a separate entity named OAuthUser, which is associated with the user model through a relationship, leaving the User model unmodified.

Related Issue:

https://github.com/hngprojects/hng_boilerplate_python_fastapi_web/issues/55

Description
The endpoint /api/v1/auth/facebook-login is created for user authentication via their Facebook account. It ensures a secure login by interfacing with the Facebook API, providing a seamless user experience.
Testing
The endpoint has undergone testing via Postman and PyTest, The resulting images are provided below at the end.
To run test cases use the following command
python -m pytest tests/v1/test_facebook_login.py

Steps to test the endpoint

first go to https://developers.facebook.com/tools/explorer
Login with your developer account if asked.
generate a new access token an pass
use your newly created access token to test the endpoint
here is a curl command if prefer to use command line

curl -X POST -H "Content-Type: application/json" -d '{"access_token": "YOUR_ACCESS_TOKEN"}' http://example.com/api/v1/auth/facebook-login

Types of changes

[x] Integrate Facebook OAuth API.
[x] Create backend endpoints to handle OAuth authentication api/v1/auth/facebook-login
[x] Secure storage of OAuth tokens.
[x] Ensure payload/response objects as follow { "message": string, "status_code": number }
[x] Ensure compliance with Facebook’s OAuth policies.
[x] All new and existing test are passed.

Postman testing attachments.
successful login

201 response: the user is login in for the first time

200 response: the is already registered on the database

invalid token

401 response: the token given has been expired or is incorrect.

missing token

422 response: the token is missing from the response but the body is passed correctly

422 response: the body has not been passed correctly

Resolve confflicts

Someone has merged his pull request by himself I destroyed my last commit work what is going on here 😥

This going to be chaos now I am out🎆🧨


require node module in renderer process

What configuration we need to change to be able to use file system for example on ipcRenderer in a component?
I have tried to use
 require('electron').ipcRenderer

but I have an error that say (launch with npm start)
 "XHR error (404 Not Found) loading http://localhost:5555/node_modules/electron.js"

It appears you may be trying to load electron from within the web build?  Given the localhost:5555 error there.
To run the electron app, follow these instructions: https://github.com/NathanWalker/angular2-seed-advanced#electron-app
Then you should be able to load electron, lemme know!

How is it possible to access electron from within main.web.ts?
import * from 'electron' doesn't seem to work. I tried to add the electron path in the system config but it didn't work.

You can access it main.desktop.ts since that is the main file electron uses.


PalEdit.exe contains Trojan

THIS ISSUE HAS BEEN REMOVED DUE TO MISINFORMATION

Can you stop spreading misinformation?

Does not happen with my Windows defender(old build) , If you want to make sure the program is not harmful, pls use PyInstaller to recompile all code and check.Compiling programs with high-level languages often triggers false detections in antivirus software.

Does not happen with my Windows defender(old build) , If you want to make sure the program is not harmful, pls use PyInstaller to recompile all code and check.Compiling programs with high-level languages often triggers false detections in antivirus software.

Yet why isn't there any mentions of such "false positive" on the README? why he is trying to hide the evidence provided calling it misinformation? if there wan't anything to it he wouldn' deleted the evidence, close it and just be like misinformation but he would then instead spent 2 min explains why there is a "false" positive so when others check they can't just see the creator hiding things


arm/v7 or arm/v8 build not available on ghcr.io

I wanted to give this a go on my QNAP NAS, which has an ARM64 processor (linux/arm/v8).
In the workflow files I did see linux/arm/v7 mentioned, but unfortunately I cannot pull that particular architecture from GitHub (e.g. ghcr.io/yoori/flare-bypasser:latest).
The images published there only contain the linux/amd64 builds.
Would it be possible to provide these other builds as well?
It seems like the step to merge the different builds is missing.
I'm not an expert, but I do something similar in one of my projects. (Disclaimer: Copilot and Google helped me on that one 😅)

Hi, I try )
Here some problem with opencv installation to arm7 - I will try to solve at next 2-3 days

Fixed :
arm/v7, arm/v8 is available now.
problem with multi arch manifest fixed.

Pulling now works.. Not sure if it's arm/v7 specific, but I do get an error about the Chrome binary being non-existent when te container starts.
I'm also not getting any response when using cURL to test the server (though that may be an error in my docker compose still).
/opt/flare_bypasser/bin/FlareBypasserRun.sh: line 158: /usr/bin/chrome: No such file or directory
Run server 0.1.43, chrome: , extensions: , add params:
2024-11-25 20:39:31,094 [flare_bypasser.flare_bypass_server] [INFO]: Start flare_bypass server:
  version: 0.1.43
  python version = 3.11.10.final.0
  os = Linux 5.10.60-qnap #1 SMP Fri Oct 25 15:05:58 CST 2024
  docker = true
  arch = aarch64
  processor =
[2024-11-25 20:39:31 +0100] [26] [INFO] Starting gunicorn 23.0.0
[2024-11-25 20:39:31 +0100] [26] [INFO] Listening at: http://<IP_ADDRESS>:8080 (26)
[2024-11-25 20:39:31 +0100] [26] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2024-11-25 20:39:31 +0100] [29] [INFO] Booting worker with pid: 29
[2024-11-25 20:39:31 +0100] [29] [INFO] Started server process [29]
[2024-11-25 20:39:31 +0100] [29] [INFO] Waiting for application startup.
[2024-11-25 20:39:31 +0100] [29] [INFO] ASGI 'lifespan' protocol appears unsupported.
[2024-11-25 20:39:31 +0100] [29] [INFO] Application startup complete.

I don’t think that chrome error is critical - I think it have other path on aarch64, I will check.
About curl : what show curl with -v option ?

The no-response part was probably an error in my configuration.
Just started the container directly from the command line (docker run -it --rm ...) and then it did respond.. although with a timeout:
2024-11-25 20:04:30,785 [flare_bypasser.flare_bypass_server] [INFO]: Start solve_tasks = [<function process_solve_request.<locals>.<lambda> at 0xfffba9f86e80>]
2024-11-25 20:04:30,786 [flare_bypasser.flare_bypass_server] [INFO]: fork #0, Solve start
2024-11-25 20:04:30,786 [flare_bypasser.flare_bypasser] [INFO]: fork #0, Solve request: {'cmd': 'request.get', 'url': 'http://www.google.nl/', 'cookies': [], 'max_timeout': 60.0, 'proxy': None, 'params': None}
2024-11-25 20:04:30,931 [zendriver_flare_bypasser.core.browser] [INFO]: starting
	executable :/bin/chromium

arguments:
--remote-allow-origins=*
	--no-first-run
	--no-service-autorun
	--no-default-browser-check
	--homepage=about:blank
	--no-pings
	--password-store=basic
	--disable-infobars
	--disable-breakpad
	--disable-component-update
	--disable-backgrounding-occluded-windows
	--disable-renderer-backgrounding
	--disable-background-networking
	--disable-dev-shm-usage
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--disable-search-engine-choice-screen
	--user-data-dir=/tmp/uc_gqg6b_cv
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--user-data-dir=/tmp/70c0cdf7-e26a-437b-80a1-a1e299d486ae
	--no-sandbox
	--remote-debugging-host=<IP_ADDRESS>
	--remote-debugging-port=57777
2024-11-25 20:04:32,775 [zendriver_flare_bypasser.core.browser] [INFO]: enabling autodiscover targets
2024-11-25 20:04:32,964 [flare_bypasser.flare_bypasser] [INFO]: fork #0, New instance of webdriver has been created to perform the request (proxy=None), timeout=60.0
2024-11-25 20:05:30,787 [flare_bypasser.flare_bypasser] [INFO]: fork #0, Close webdriver
Processing timeout (max_timeout=60.0)
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/tasks.py", line 500, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 289, in _resolve_challenge
    return await self._resolve_challenge_impl(req, start_time)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 470, in _resolve_challenge_impl
    challenge_found = await self._check_challenge()
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 333, in _check_challenge
    page_title = await self._driver.title()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/browser_wrapper.py", line 122, in title
    res = await self._page.select("title", timeout=0)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/tab.py", line 237, in select
    item = await self.query_selector(selector)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/tab.py", line 424, in query_selector
    doc: cdp.dom.Node = await self.send(cdp.dom.get_document(-1, True))
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/connection.py", line 435, in send
    return await tx
           ^^^^^^^^
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 257, in solve
    res = await asyncio.wait_for(self._resolve_challenge(req), req.max_timeout)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/tasks.py", line 502, in wait_for
    raise exceptions.TimeoutError() from exc
TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 250, in process_solve_request
    solve_response, _skipped_results, _exceptions = await wait_first_non_exception(solve_tasks)
                                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 147, in wait_first_non_exception
    raise e
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 139, in wait_first_non_exception
    res = await f
          ^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 172, in solve
    return await solver.solve(solve_request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 260, in solve
    raise Exception("Processing timeout (max_timeout=" + str(req.max_timeout) + ")")
Exception: Processing timeout (max_timeout=60.0)

Please, try latest version after this fix

@yoori Thanks for the update. I still get an error though it is a different one.
$ docker pull ghcr.io/yoori/flare-bypasser:latest
latest: Pulling from yoori/flare-bypasser
Digest: sha256:95f3e89512a9727da5a4e580ac8ec5c325f65c00c04e3e1b0e975c59ad33f0cd
Status: Image is up to date for ghcr.io/yoori/flare-bypasser:latest
ghcr.io/yoori/flare-bypasser:latest
$ docker run -it --rm -p 8765:8080 ghcr.io/yoori/flare-bypasser:latest
Starting system message bus: dbus.
/opt/flare_bypasser/bin/FlareBypasserRun.sh: line 169: /usr/bin/chrome: No such file or directory
Run server 0.1.53, chrome: , extensions: , add params:
2024-12-16 20:03:23,166 [flare_bypasser.flare_bypass_server] [INFO]: Start flare_bypass server:
  version: 0.1.53
  python version = 3.11.11.final.0
  os = Linux 5.10.60-qnap #1 SMP Thu Nov 14 05:23:23 CST 2024
  docker = true
  arch = aarch64
  processor =
[2024-12-16 20:03:23 +0000] [44] [INFO] Starting gunicorn 23.0.0
[2024-12-16 20:03:23 +0000] [44] [INFO] Listening at: http://<IP_ADDRESS>:8080 (44)
[2024-12-16 20:03:23 +0000] [44] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2024-12-16 20:03:23 +0000] [47] [INFO] Booting worker with pid: 47
[2024-12-16 20:03:23 +0000] [47] [INFO] Started server process [47]
[2024-12-16 20:03:23 +0000] [47] [INFO] Waiting for application startup.
[2024-12-16 20:03:23 +0000] [47] [INFO] ASGI 'lifespan' protocol appears unsupported.
[2024-12-16 20:03:23 +0000] [47] [INFO] Application startup complete.
2024-12-16 20:03:33,359 [flare_bypasser.flare_bypass_server] [INFO]: Start solve_tasks = [<function process_solve_request.<locals>.<lambda> at 0xffff69b5e2a0>]
2024-12-16 20:03:33,361 [flare_bypasser.flare_bypass_server] [INFO]: fork #0, Solve start
2024-12-16 20:03:33,361 [flare_bypasser.flare_bypasser] [INFO]: fork #0, Solve request: {'cmd': 'request.get', 'url': 'http://www.google.nl/', 'cookies': [], 'max_timeout': 60.0, 'proxy': None, 'params': None}
2024-12-16 20:03:33,470 [zendriver_flare_bypasser.core.browser] [INFO]: starting
	executable :/bin/chromium

arguments:
--remote-allow-origins=*
	--no-first-run
	--no-service-autorun
	--no-default-browser-check
	--homepage=about:blank
	--no-pings
	--password-store=basic
	--disable-infobars
	--disable-breakpad
	--disable-component-update
	--disable-backgrounding-occluded-windows
	--disable-renderer-backgrounding
	--disable-background-networking
	--disable-dev-shm-usage
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--disable-search-engine-choice-screen
	--user-data-dir=/tmp/uc_7viy0tk5
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--user-data-dir=/tmp/ea90c7c9-c730-40e5-b41a-06aedea80a99
	--ignore-certificate-errors
	--ignore-urlfetcher-cert-requests
	--no-sandbox
	--remote-debugging-host=<IP_ADDRESS>
	--remote-debugging-port=40451
2024-12-16 20:03:33,475 [zendriver_flare_bypasser.core.browser] [INFO]: starting
	executable :/bin/chromium

arguments:
--remote-allow-origins=*
	--no-first-run
	--no-service-autorun
	--no-default-browser-check
	--homepage=about:blank
	--no-pings
	--password-store=basic
	--disable-infobars
	--disable-breakpad
	--disable-component-update
	--disable-backgrounding-occluded-windows
	--disable-renderer-backgrounding
	--disable-background-networking
	--disable-dev-shm-usage
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--disable-search-engine-choice-screen
	--user-data-dir=/tmp/uc_slox493s
	--disable-features=IsolateOrigins,site-per-process
	--disable-session-crashed-bubble
	--user-data-dir=/tmp/da6e0ed3-dc95-4326-b3e0-2c89179948d8
	--ignore-certificate-errors
	--ignore-urlfetcher-cert-requests
	--no-sandbox
	--remote-debugging-host=<IP_ADDRESS>
	--remote-debugging-port=58205
2024-12-16 20:03:36,278 [flare_bypasser.flare_bypasser] [INFO]: fork #0, Close webdriver
2024-12-16 20:03:36,278 [flare_bypasser.flare_bypasser] [ERROR]: fork #0, Error solving the challenge. On platform linux at step 'browser init':
On user-agent getting:
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 166, in get_user_agent
    return await asyncio.wait_for(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypasser.py", line 560, in get_user_agent
    driver: BrowserWrapper = await BrowserWrapper.create(
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/browser_wrapper.py", line 115, in create
    zendriver_driver = await zendriver.Browser.create(config)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/browser.py", line 92, in create
    await instance.start()
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/browser.py", line 372, in start
    await self._stop_process()
  File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/browser.py", line 590, in _stop_process
    self._process.terminate()
  File "/usr/local/lib/python3.11/asyncio/subprocess.py", line 143, in terminate
    self._transport.terminate()
  File "/usr/local/lib/python3.11/asyncio/base_subprocess.py", line 149, in terminate
    self._check_proc()
  File "/usr/local/lib/python3.11/asyncio/base_subprocess.py", line 142, in _check_proc
    raise ProcessLookupError()
ProcessLookupError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 279, in process_solve_request
    (solve_response, _skipped_results, _exceptions), user_agent = await asyncio.gather(
                                                                  ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/flare_bypasser/flare_bypass_server.py", line 176, in get_user_agent
    raise Exception("On user-agent getting: " + str(e)) from e
Exception: On user-agent getting:


Updated Dependencies

I've also changed the version constraints to strictly specify the minor version because I don't trust people not to break things. I think it would be useful for us to have full control over the minor versions of our dependencies.

:+1:

👍


Normalize Python version

3.9.6 is the highest on Windows ATM

Changed to Python 3.9.6 in dcfcf1b03d281b6c416f3bfdbe97c8019c9bd40f


Use shouldError/shouldWarn by default unless only shouldValidate is passed in.

When providing a custom shouldError prop, it needs to be passed into both shouldError and the deprecated shouldValidate.
const customShouldError = () => { ... };
const myForm = reduxForm({
  shouldError: customShouldError,
  shouldValidate: customShouldError,
});

If only shouldError is passed in the shouldValidate may override the expected behavior.  For example the shouldError prop returns false but the default shouldValidate returns true, the code will still run the validation.
This PR will allow for either shouldError or shouldValidate to be used.

Codecov Report

Merging #3881 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3881   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          70      70
  Lines        1601    1607    +6
======================================
+ Hits         1601    1607    +6

Impacted Files
Coverage Δ

src/createReduxForm.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Published in v7.3.0.


Media files in CDSTAR

Note: The functionality described in the following document should be implemented
as part of pycdstar.

Clean the local filename:

whitespace to underscore
non-ASCII sluggified

Always use the (cleaned) local filename as alias for the original bitstream.
log upload operations including time started!

Video
Handling of video files requires ffmpeg.

optionally: convert to MPEG-4:

    if p.name.endswith('.mov') or p.name.endswith('.qt'):
        opts = '-c:v libx264'
    elif p.name.endswith('.avi'):
        opts = '-c:v libx264 -crf 19 -preset slow -c:a aac -strict experimental -b:a 192k -ac 2'
    check_call('ffmpeg -i {0} {1} {2}'.format(p.as_posix(), opts, out.as_posix()), shell=True)

probe duration

def get_duration(path):
    cmd = 'ffprobe -loglevel quiet -print_format json -show_streams {0}'.format(path.as_posix())
    return float(json.loads(subprocess.check_output(cmd, shell=True))['streams'][0]['duration'])

create thumbnail with ffmpeg

  ffmpeg -itsoffset -30 -i {0} -vcodec mjpeg -vframes 1 -an -f rawvideo {1}

upload

bitstreams:

raw video
thumbnail

metadata:

duration
full local path?

Image

create thumbnail and web resolution with convert

    'thumbnail': 'convert {0} -thumbnail 103x103^ -gravity center -extent 103x103 {1}',
    'web': 'convert {0} -resize 357x357 {1}'

upload

Audio
TODO
Bookkeeping
The upload catalog
To keep track of what has been uploaded to CDSTAR, we catalog each item.
To make the catalog easily accessible programmatically, it is serialized
as JSON. Care must be taken, though, to keep this serialization version-
control-friendly, i.e.:

write indented JSON
make sure all dicts are soorted before writing

    def write(self):
        ordered = OrderedDict()
        for md5 in sorted(self.keys()):
            ordered[md5] = OrderedDict([i for i in sorted(uploaded[md5].items())])
        jsonlib.dump(ordered, self.path, indent=4)

Operations:

add upload
modification

The backlog
Operations:

check upload status (summary)

Integrating media objects in clld

linked image display
video

upload catalog is implemented in cdstarcat.


not showing mentioned format , its taking default format

Expected behaviour
I need datepicker to take mentioned format which is format: 'dd/mm/yyyy'
Actual behaviour
But it is taking default format:'mm/ddyyyy'
Datepicker version used
I'm not sure about the version
Example code
Jsfiddle example to reproduce the problem.

I'm having the same issue. Sadly.

I have a solution，YYYY-MM-DD HH:mm  2016-09-20 13:20

Hi,
Can you profile a jsfiddle or a snippet to understand your issue please ?


Modules is missing in production mode

Bug report
Maybe same problem with #7425

What is the current behavior?
Seems some modules is missing in production mode
If the current behavior is a bug, please provide the steps to reproduce.
It's hard to create a minimum reproducible example (I tried, I can't upload our project). But there has call stack trace:

What is the expected behavior?
Not missing any module

webpack config
vue-cli v3.0.0-beta.15 default config
Other relevant information:
webpack version:  v4.11.1
Node.js version: v10.4.0
Operating System: macOS High Sierra 10.13.5

Is there any library that has sideEffects: false configured?
grep sideEffects node_modules/*/package.json

@sod Yes, I found in rxjs. But I'm not using rxjs, it's a dependency for lint-staged (lint-staged -> listr -> rxjs). And the missing module is our component, not some library.

I try to remove lint-staged, and it has same problem (of course). Seems we are different problem.

Hi @yangmingshan it difficult to see the problem from your screenshots, but here are some hints that may help you to find the problem:

Disable HashModules and enable namedModules. This should make it easier to read the stuff as modules have useful names.
Disable minimizing. This should make it easier to read the source.
function for module 6jJR doesn't seem to be loaded. Check from the stats in which chunk this module is.
There are 3 possible cases: The chunk should be loaded but isn't. The module is not in the right chunk. The module isn't in any chunk at all.

@sokra Seems the module isn't in any chunk at all, I only found two __webpack_require__("6jJR") call in all build files.

And how to disable HashModules and enable namedModules? I tried optimization.namedModules, not work.
I will keep trying create a minimum reproducible example.

I think we are running into same issue. On production build for 2 chunks only we are seeing

it looks a in  manifest is sparse  array for some reason.
@sokra  Anything I can help to debug this issue from my side? This started after we updated form 4.10.2 to 4.11

I might be experiencing the same bug. In my case I think the problem is that there's a __webpack_require__(…) that shouldn't be there.
I have this source file<EMAIL_ADDRESS>import * as rrd from "react-router-dom";

export const Link = React.createContext(rrd.Link);
//# sourceMappingURL=index.js.map

In the production build it's compiled to:
// EXTERNAL MODULE: ./node_modules/react-router-dom/es/Link.js
var es_Link = __webpack_require__(274);
// CONCATENATED MODULE<EMAIL_ADDRESS>/* harmony import */
__webpack_require__(/*! react-router-dom */
76);
const Link_Link = React.createContext(es_Link.a);
//# sourceMappingURL=index.js.map

The error is thrown inside __webpack_require__(/*! react-router-dom */ 76);:
TypeError: Cannot read property 'call' of undefined at __webpack_require__ (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:20:27) at Module.9 (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:6550:21) at __webpack_require__ (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:20:27) at Object.580 (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:6134:182) at __webpack_require__ (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:20:27) at Object.581 (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:6151:115) at __webpack_require__ (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:20:27) at 0 (http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:82:16) at http://localhost:3000/packs/collector-194eaf08eb5776b1dae1.js:85:9

What's interesting is that:

The import is unused (only Link from react-router-dom is actually used, the root module is not, so it's a surprise that react-router-dom is being imported).
react-router-dom has pkg.sideEffects=false
It appears correct that react-router-dom is not available. The problem really seems that it's being imported at all.

My optimization portion of my webpack config:
module.exports.optimization = {
  minimizer: [
    new UglifyJsPlugin({
      sourceMap: false,
      uglifyOptions: {
        compress: {
          dead_code: false,
          inline: false,
          side_effects: false,
          sequences: false,
          keep_fnames: true,
          keep_fargs: true,
          reduce_funcs: false,
          switches: false
        },
        mangle: false,
        output: {
          comments: "all"
        }
      }
    })
  ]
};

I have the same problem and the optimization: { sideEffects: false } solution/workaround works for me, thanks @bradleyayers
Is it a bug that we need to set this setting? 4.9.2 works without the said setting.

I've just hit it in an Angular CLI 6.0.8 + Angular 6.0.4 app. With NamedModulesPlugin enabled I see the following linew on the stack trace:
/* harmony import */ var tslib__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__("./node_modules/tslib/tslib.es6.js");
/* harmony import */ var rxjs__WEBPACK_IMPORTED_MODULE_1__ = __webpack_require__("./node_modules/rxjs/_esm5/index.js");
/* harmony import */ var rxjs__WEBPACK_IMPORTED_MODULE_2__ = __webpack_require__("./node_modules/rxjs/_esm5/internal/Subscription.js");
/* harmony import */ var rxjs__WEBPACK_IMPORTED_MODULE_3__ = __webpack_require__("./node_modules/rxjs/_esm5/internal/Subject.js");
/* harmony import */ var rxjs__WEBPACK_IMPORTED_MODULE_4__ = __webpack_require__("./node_modules/rxjs/_esm5/internal/Observable.js");
/* harmony import */ var rxjs__WEBPACK_IMPORTED_MODULE_5__ = __webpack_require__("./node_modules/rxjs/_esm5/internal/observable/merge.js");
/* harmony import */ var rxjs_operators__WEBPACK_IMPORTED_MODULE_6__ = __webpack_require__("./node_modules/rxjs/_esm5/operators/index.js");
/* harmony import */ var rxjs_operators__WEBPACK_IMPORTED_MODULE_7__ = __webpack_require__("./node_modules/rxjs/_esm5/internal/operators/share.js");

If you look at the file from which it comes, i.e<EMAIL_ADDRESS>you'll see:
import { __assign, __extends, __read, __spread, __values } from 'tslib';
import { Observable, Subject, Subscription, merge } from 'rxjs';
import { share } from 'rxjs/operators';

The failure is in the line importing ./node_modules/rxjs/_esm5/operators/index.js - this file just requires all the operators from its directory so it seems it should be stripped out due to the sideEffects flag. The require to it stays, though, causing missing module errors which break the whole app.
It's not entirely clear what triggers the issue as it started appearing when I migrated my project's RxJS imports to this new format already used by @angular/core - and yet the error comes from @angular/core and not my own code.

FWIW, in my case changing:
import { pairwise, filter, take } from 'rxjs/operators';
import { merge } from 'rxjs';

in one file (app.component.ts) to the following:
import { filter, take } from 'rxjs/operators';
import { pairwise } from 'rxjs/operators/pairwise';
import { merge } from 'rxjs';

made the app work again. I suspect this may be pretty random...

@dlebedynskyi

Update: after some digging - looks like webpack 4.9.2 is fine, but 4.10.0 breaks.

I have tested 4.9.2 where it worked and 4.10.2 where it didn't so it seems probable that this is a 4.10.0 regression.

I hit the same issue when upgrading webpack in our project, where it failed when loading modules from redux-form. It breaks from 4.9.2 to 4.10.0.
@sokra It seems having a package that has sideEffects: false containing wildcard import breaks in combination with dynamic imports:
import * as constants from './constants'
export { constants }

import 'some-package'
import('./lazy')
console.log('this message is never seen')

lazy.js:
import { constants } from 'some-package'
console.log('constants', constants)

I put up a minimal case to reproduce: https://github.com/henrist/webpack-module-missing-bug

We had kind of the same error as here and #7425
We tried:
optimization.sideEffects = false
Different version of webpack: 4.10.0, 4.12.0, 4.9.2
But nothing worked as the error message was kind of generic: TypeError: Cannot read property 'call' of undefined
We then did:
module.exports.optimization = {
  minimize: false
};

And found out the error was:
We then changed the following lines of code:
export const unbind = Mousetrap.unbind;

to
export const unbind = (combination: Array<string>) => Mousetrap.unbind(combination);

So just as @mgol the real error was random, but  the real question here is why webpack did not provide an error in development mode?

@zahlio what was the compiled code in mousetrap.js:934?

@henrist

I hit the same issue when upgrading webpack in our project, where it failed when loading modules from redux-form. It breaks from 4.9.2 to 4.10.0
this seem to be same issue for us. redux-froms is used in chunk that break for us as well.

@sokra  test with 4.12.1  issue is still happening.

ok next try. #7499 should fix the problem in the repro from @henrist. It's a different problem to the problem by @yangmingshan.
@dlebedynskyi @zahlio Not sure if this is the same problem. Please provide a repro repo to get it fixed.

@sokra  #7499 seems to work for us as well. Tested our code against latest master. Thank you for fix.

Things are working properly from master here too. Thanks :)

My problem is fixed in v4.12.1. Thanks

I ran into this exact same issue with Webpack 4.12.0.
I'm importing a library with free side-effects sideEffect: false.
The call in one of the main files is:
import {IconSettings} from '@salesforce/design-system-react';

When translated to webpack it looked like this:

where the first call tries to import the index.js of all modules supported in the library, __webpack_require('306')
However, 306 is missing in modules, for a reason.

That results into this error, which blows up the entire app.

I was able to fix it by upgrading to 4.12.2 (fixed in that version).
Setting optimizations.sideEffects: false as @bradleyayers worked too but it was probably a temporary fix.

For what it's worth, I was running into this as well, and sideEffects: false did not fix it. I was using Vue CLI 3 TypeScript template and the error was caused by splitChunks:
optimization: {
...,
   splitChunks: {
      cacheGroups: {
        vendors: {
          name: 'chunk-vendors',
          test: /[\\\/]node_modules[\\\/]/,
          priority: -10,
          chunks: 'initial'
        },
        common: {
          name: 'chunk-common',
          minChunks: 2,
          priority: -20,
          chunks: 'initial',
          reuseExistingChunk: true
        }
      }
    },
...
}

I fixed by adding the following to vue.config.js to remove the splitChunks config:
	chainWebpack: config => {
		if (process.env.NODE_ENV === 'production') {
			config.optimization.sideEffects(false);
			config.optimization.delete('splitChunks');
		}
	},


Map doesn't display on front page or for specified locations

https://openbenches.org/ is displaying the 404 page instead of the map.
Going to a page for a specific page, then clicking "Benches near this",  E.g. https://openbenches.org/#53.960972/-1.086261/16 also displays 404 instead of the map.
I suspect the addition at line 146 in https://github.com/openbenches/openbenches.org/commit/03f135c6482eff81ab78ff2fbe6ec8843e6f438f#diff-df61020b75a730cc7203a9e2aae58e72R146

You didn't see nuffink, right!


Test with JDK 23

lol, I thought you meant we needed to add the full framework rather than just this bump!

Finally found the root cause for the flaky testVirtualThreadsExcludedByDefault:
That test would sometimes fail because the native profiling correlation TLS would be non-null even though it should be.
The reason for this was an improper cleanup in testVirtualThreadsStoragePropagatedWithMounts:
This test would span lots of virtual thread and populate the carrier thread TLS. After the test the syncinc of virtual thread TLS with the carrier thread TLS would be disabled. The problem now was that we disabled the sync without actually waiting for all virtual threads to be terminated and therefore unmounted. As a result, for some carrier the TLS would not be cleaned up properly, leaking into the testVirtualThreadsExcludedByDefault test.


nex notifications

nex uniques currently not showing in support server notifications channel

Bump. Would be really nice to have this


Change X (formerly Twitter) logo to their new logo

Description
We need to change the old logo of X (formerly Twitter) to their new logo.

Screenshots
No response
Additional information
Make sure to add it to the dark and light theme.

i can fix this, assign me this pls

i can fix this, assign me this pls

Go for it Champ👑

Done in https://github.com/origranot/reduced.to/pull/468


[Monitor] Bug when changing reference

Part of the process we have chosen with a route manager is that we use a GPX reference while creating/fixing a route in OSM, then we switch to an OSM reference so as to monitor changes (generally damage) that occur in the route.
Currently when we perform this switch, strange things happen:

in order to make sure that the OSM reference is taken into account when computing deviations, I must select a reference date posterior to the current day. Usually I choose tomorrow.
ultimately, the route is still displayed with a GPX reference in the table, with results that are computed with an OSM reference

Fixed in next release (not published yet).
The monitor route definition update logic now correctly handles changing the reference type from "gpx" to "osm".
When setting the monitor route reference day in the route definition, the state of the route at that day at midnight (UTC) is used as the reference to perform the analysis against.  This is why you need to set the reference day to "tomorrow" if you want to see deviations that were introduced between midnight and the time of route creation.  This can be confusing.
To avoid confusion, the existing reference type selection has been renamed to "The OSM relation at a given moment in the past" and an extra option "The OSM relation at this moment" has been added.  When selecting the latter, no reference day has to be entered by the user, and the current system time is used instead (changes since midnight are taken into account).

Solution published in release v4.1.0.


added Windows support and few fixes

and fix the issue that the username and password are mandatory to push even if we did a login before
fix the issues :

https://github.com/sonatype-nexus-community/helm-nexus-push/issues/22
https://github.com/sonatype-nexus-community/helm-nexus-push/issues/3

@joedragons I rollback the changes to the readme file.