Sending query hints to Vertica

Hello
Vertica uses query hints that SQL editors generally see as comments.
Example:  insert /*+ direct */ into tablename ....
Some SQL Editors have an option to send the comments to the DB server instead of ignoring them.  Does DBeaver have this option anywhere?

DBeaver doesn't modify SQL queries before execution.
So these comments will be passed to server without any modifications.
This the default behavior and there are no options which affects it.

Thanks Serge, that is great to know!


Increase the max number of vis neighbors you can render

Change it to something like 1000, the check should be 1000 total visible neighbors instead of 25 for each gene.

Huh. Interesting. How would you prioritize which ones to show?
On Apr 20, 2017 10:12 PM, "Rob Schaefer"<EMAIL_ADDRESS>wrote:

Change it to something like 1000, the check should be 1000 total visible
neighbors instead of 25 for each gene.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/schae234/cob/issues/78, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGw_DtE7aoWSrXX2mAG1G8fsmxYzPkpBks5ryB6mgaJpZM4ND0Ga
.


Bump matplotlib version

This fixes a deprecation warning in python 3.7 that shows up everytime you import cirq.

It could be because incremental is on version 3.5.2 while non-contrib is on 3.6.

Good 'ol Travis, catching my mistakes. Modified version to ~=3.0.


invalid stub handshake response received

Hello
i got the following issue:
[2024-03-25T15:55:55Z INFO ] Serial port: 'COM5'
[2024-03-25T15:55:55Z INFO ] Connecting...
[2024-03-25T15:55:57Z INFO ] Using flash stub
Error:   x Error while connecting to device
  `-> Invalid stub handshake response received

i can connect with py -m esptool -p .... to my sparkfun esp32 thing board.
I use this instruction guide to flash the device: https://github.com/beeb/coffee-scale-app/blob/main/rs/README.md
Also i set the baudrate to a lower one (115200) in the espflash.toml without success.
I tried to find with google the issue with the handshake and thats why i set the baudrate to a lower part.
What did i wrong or miss?

Can confirm, same issue here (windows, cargo-espflash 3.0.0)

Hi! Mind trying to use the --no-stub flag?

Note that the board has a 26MHz crystal and CONFIG_XTAL_FREQ_26=y is set in the sdkconfig.

Correct, more information https://docs.esp-rs.org/book/troubleshooting/std.html#wrong-xtal-frequency

yeah after some more try and errors and short reading (stub is a kind of a bootloader?) right?
with this flag --no-stub is successfull but i was very confused.
@beeb yeah  i am struggeling a litte bit but i after some breaks one step after another.    But great project so far. :)

Could you try using this branch https://github.com/SergioGasquez/espflash/tree/feat/esp32-26mhz?
cargo install cargo-espflash --git https://github.com/SergioGasquez/espflash --branchfeat/esp32-26mhz

i got a few timeout notification but it seems to work. No handshake error or need to set the --no-stub flag

Hey @SergioGasquez thanks for looking into it. I can confirm that with the stable release and --no-stub the flashing works.
However this is what I get with your branch every time I try:
[2024-03-26T19:18:38Z INFO ] Serial port: 'COM3'
[2024-03-26T19:18:38Z INFO ] Connecting...
[2024-03-26T19:18:38Z INFO ] Using flash stub
Error: espflash::timeout

  × Error while connecting to device
  ╰─▶ Timeout while running command

@SergioGasquez
I tried to make a log cargo espflash flash --release -L serial --monitor but i don´t find a file or something else. Sorry i´m a beginner in that case.

I tried to make a log cargo espflash flash --release -L serial --monitor

Logs are not enabled with the -L arguments. Logs are enabled by RUST_LOG=debug cargo espflash flash --release --monitor

However this is what I get with your branch every time I try.

Might share debug logs? Although I think I may know what's happening: The stubs are sending the sync message but espflash is not able to read it properly (different baudrate)

Just pushed a commit https://github.com/SergioGasquez/espflash/commit/d86a622250dee85bdf817fb7a86b300889033b78 to the branch, could you guys reinstall it and test it with logs enabled:
cargo install cargo-espflash --git https://github.com/SergioGasquez/espflash --branch feat/esp32-26mhz
RUST_LOG=debug cargo espflash flash --release --monitor

Thanks @SergioGasquez , here are the logs from my side (I shortened the data sequences for brevity):
[2024-04-02T17:13:57Z DEBUG] Flash(
        FlashArgs {
            build_args: BuildArgs {
                bin: None,
                example: None,
                features: None,
                frozen: false,
                locked: false,
                package: None,
                release: true,
                target: None,
                target_dir: None,
                unstable: None,
                flash_config_args: FlashConfigArgs {
                    flash_freq: None,
                    flash_mode: None,
                    flash_size: None,
                },
            },
            connect_args: ConnectArgs {
                after: HardReset,
                baud: None,
                before: DefaultReset,
                chip: None,
                confirm_port: false,
                list_all_ports: false,
                no_stub: false,
                port: None,
            },
            flash_args: FlashArgs {
                bootloader: None,
                erase_parts: None,
                erase_data_parts: None,
                log_format: Serial,
                min_chip_rev: 0,
                monitor: true,
                monitor_baud: None,
                partition_table: None,
                target_app_partition: None,
                partition_table_offset: None,
                ram: false,
                no_verify: false,
                no_skip: false,
            },
        },
    )
[2024-04-02T17:13:57Z DEBUG] connecting to crates.io:443 at <IP_ADDRESS>:443
[2024-04-02T17:13:57Z DEBUG] No cached session for DnsName("crates.io")
[2024-04-02T17:13:57Z DEBUG] Not resuming any session
[2024-04-02T17:13:57Z DEBUG] Using ciphersuite TLS13_AES_128_GCM_SHA256
[2024-04-02T17:13:57Z DEBUG] Not resuming
[2024-04-02T17:13:57Z DEBUG] TLS1.3 encrypted extensions: [ServerNameAck]
[2024-04-02T17:13:57Z DEBUG] ALPN protocol is None
[2024-04-02T17:13:57Z DEBUG] created stream: Stream(RustlsStream)
[2024-04-02T17:13:57Z DEBUG] sending request GET https://crates.io/api/v1/crates/cargo-espflash/versions
[2024-04-02T17:13:57Z DEBUG] writing prelude: GET /api/v1/crates/cargo-espflash/versions HTTP/1.1
    Host: crates.io
    User-Agent: ureq/2.9.6
    Accept: */*
    accept-encoding: gzip
[2024-04-02T17:13:57Z DEBUG] Chunked body in response
[2024-04-02T17:13:57Z DEBUG] response 200 to GET https://crates.io/api/v1/crates/cargo-espflash/versions
[2024-04-02T17:13:57Z DEBUG] dropping stream: Stream(RustlsStream)
[2024-04-02T17:13:57Z DEBUG] Config: Config {
        baudrate: None,
        bootloader: None,
        connection: Connection {
            serial: None,
        },
        partition_table: None,
        usb_device: [
            UsbDevice {
                vid: 1027,
                pid: 24597,
            },
        ],
        save_path: "C:\\Users\\valentin\\AppData\\Roaming\\esp\\espflash\\config\\espflash.toml",
    }
[2024-04-02T17:13:57Z INFO ] Serial port: 'COM3'
[2024-04-02T17:13:57Z INFO ] Connecting...
[2024-04-02T17:13:57Z DEBUG] Using Classic reset strategy with delay of 50ms
[2024-04-02T17:13:57Z DEBUG] Boot Mode: 0x3
[2024-04-02T17:13:57Z DEBUG] Download Mode: false
[2024-04-02T17:13:57Z DEBUG] Writing command: Sync
[2024-04-02T17:13:57Z DEBUG] Writing command: Sync
[2024-04-02T17:13:58Z DEBUG] Writing command: Sync
[2024-04-02T17:13:58Z DEBUG] Writing command: Sync
[2024-04-02T17:13:58Z DEBUG] Writing command: Sync
[2024-04-02T17:13:58Z DEBUG] Failed to reset, error Connection(
        WrongBootMode(
            "0x3",
        ),
    ), retrying
[2024-04-02T17:13:58Z DEBUG] Using Classic reset strategy with delay of 500ms
[2024-04-02T17:13:58Z DEBUG] Boot Mode: 0x3
[2024-04-02T17:13:58Z DEBUG] Download Mode: false
[2024-04-02T17:13:58Z DEBUG] Writing command: Sync
[2024-04-02T17:13:59Z DEBUG] Writing command: Sync
[2024-04-02T17:13:59Z DEBUG] Writing command: Sync
[2024-04-02T17:13:59Z DEBUG] Writing command: ReadReg { address:<PHONE_NUMBER> }
[2024-04-02T17:13:59Z INFO ] Using flash stub
[2024-04-02T17:13:59Z DEBUG] Loading flash stub for chip: Esp32
[2024-04-02T17:13:59Z DEBUG] Write 12356 byte stub text
[2024-04-02T17:13:59Z DEBUG] Writing command: MemBegin { size: 12356, blocks: 3, block_size: 6144, offset:<PHONE_NUMBER>, supports_encryption: false }
[2024-04-02T17:13:59Z DEBUG] Writing command: MemData { data: [0, ... 129], pad_to: 4, pad_byte: 0, sequence: 0 }
[2024-04-02T17:13:59Z DEBUG] Writing command: MemData { data: [162, ... 0], pad_to: 4, pad_byte: 0, sequence: 1 }
[2024-04-02T17:14:00Z DEBUG] Writing command: MemData { data: [230, ... 0], pad_to: 4, pad_byte: 0, sequence: 2 }
[2024-04-02T17:14:00Z DEBUG] Write 744 byte stub data
[2024-04-02T17:14:00Z DEBUG] Writing command: MemBegin { size: 744, blocks: 1, block_size: 6144, offset:<PHONE_NUMBER>, supports_encryption: false }
[2024-04-02T17:14:00Z DEBUG] Writing command: MemData { data: [86, ... 0], pad_to: 4, pad_byte: 0, sequence: 0 }
[2024-04-02T17:14:00Z DEBUG] Finish stub write
[2024-04-02T17:14:00Z DEBUG] Writing command: MemEnd { no_entry: false, entry:<PHONE_NUMBER> }
[2024-04-02T17:14:00Z DEBUG] Stub written!
Error: espflash::timeout

  × Error while connecting to device
  ╰─▶ Timeout while running command

Just to confirm, these logs were using the latest commit of my branch? Looks like it's retrying lots of times the sync command (probably because it's not able to read it due to the different baud rate).
Also, could you try using the --before no-reset argument?

Yes this is on commit d86a622250dee85bdf817fb7a86b300889033b78. Here's the result with the --before no-reset argument:
[2024-04-07T13:55:54Z DEBUG] Flash(
        FlashArgs {
            build_args: BuildArgs {
                bin: None,
                example: None,
                features: None,
                frozen: false,
                locked: false,
                package: None,
                release: true,
                target: None,
                target_dir: None,
                unstable: None,
                flash_config_args: FlashConfigArgs {
                    flash_freq: None,
                    flash_mode: None,
                    flash_size: None,
                },
            },
            connect_args: ConnectArgs {
                after: HardReset,
                baud: None,
                before: NoReset,
                chip: None,
                confirm_port: false,
                list_all_ports: false,
                no_stub: false,
                port: None,
            },
            flash_args: FlashArgs {
                bootloader: None,
                erase_parts: None,
                erase_data_parts: None,
                log_format: Serial,
                min_chip_rev: 0,
                monitor: true,
                monitor_baud: None,
                partition_table: None,
                target_app_partition: None,
                partition_table_offset: None,
                ram: false,
                no_verify: false,
                no_skip: false,
            },
        },
    )
[2024-04-07T13:55:54Z DEBUG] connecting to crates.io:443 at <IP_ADDRESS>:443
[2024-04-07T13:55:54Z DEBUG] No cached session for DnsName("crates.io")
[2024-04-07T13:55:54Z DEBUG] Not resuming any session
[2024-04-07T13:55:54Z DEBUG] Using ciphersuite TLS13_AES_128_GCM_SHA256
[2024-04-07T13:55:54Z DEBUG] Not resuming
[2024-04-07T13:55:54Z DEBUG] TLS1.3 encrypted extensions: [ServerNameAck]
[2024-04-07T13:55:54Z DEBUG] ALPN protocol is None
[2024-04-07T13:55:54Z DEBUG] created stream: Stream(RustlsStream)
[2024-04-07T13:55:54Z DEBUG] sending request GET https://crates.io/api/v1/crates/cargo-espflash/versions
[2024-04-07T13:55:54Z DEBUG] writing prelude: GET /api/v1/crates/cargo-espflash/versions HTTP/1.1
    Host: crates.io
    User-Agent: ureq/2.9.6
    Accept: */*
    accept-encoding: gzip
[2024-04-07T13:55:54Z DEBUG] Chunked body in response
[2024-04-07T13:55:54Z DEBUG] response 200 to GET https://crates.io/api/v1/crates/cargo-espflash/versions
[2024-04-07T13:55:54Z DEBUG] dropping stream: Stream(RustlsStream)
[2024-04-07T13:55:54Z DEBUG] Config: Config {
        baudrate: None,
        bootloader: None,
        connection: Connection {
            serial: None,
        },
        partition_table: None,
        usb_device: [
            UsbDevice {
                vid: 1027,
                pid: 24597,
            },
        ],
        save_path: "C:\\Users\\valentin\\AppData\\Roaming\\esp\\espflash\\config\\espflash.toml",
    }
[2024-04-07T13:55:54Z WARN ] Pre-connection option 'NoReset' was selected.  Could you try with the new espflash version? I guess this is a stub issue, so it probably should be transferred


Update service-updates-how-to.md

Adding ASR Update Rollup 37

@maorteg : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Rajani-Janaki-Ram Please review

@Rajani-Janaki-Ram Disregard this pull request. Since it took 2 weeks until this request was reviewed, during that time the documentation was already updated with latest release info.
I'm closing this one.


Training_cifar10.py breaks when using USR_PROFILER

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System: Ubuntu 14.04
Compiler: g++, nvcc
Package used (Python/R/Scala/Julia):
MXNet version: latest
Or if installed from source:
MXNet commit hash (git rev-parse HEAD):
If you are using python package, please provide
Python version and distribution: 2.7
If you are using R package, please provide
R sessionInfo():
Error Message:
Please paste the full error message, including stack trace.
root@d6dfc4c90761:/mxnet/example/image-classification# python train_cifar10.py --network resnet --num-layers 110 --batch-size 128 --gpus 0,1,2,3
INFO:root:start with arguments Namespace(batch_size=128, benchmark=0, data_nthreads=4, data_train='data/cifar10_train.rec', data_val='data/cifar10_val.rec', disp_batches=20, dtype='float32', gpus='0,1,2,3', image_shape='3,28,28', kv_store='device', load_epoch=None, lr=0.05, lr_factor=0.1, lr_step_epochs='200,250', max_random_aspect_ratio=0, max_random_h=36, max_random_l=50, max_random_rotate_angle=0, max_random_s=50, max_random_scale=1, max_random_shear_ratio=0, min_random_scale=1, model_prefix=None, mom=0.9, monitor=0, network='resnet', num_classes=10, num_epochs=300, num_examples=50000, num_layers=110, optimizer='sgd', pad_size=4, random_crop=1, random_mirror=1, rgb_mean='123.68,116.779,103.939', test_io=0, top_k=0, wd=0.0001)
[23:18:15] src/io/iter_image_recordio.cc:220: ImageRecordIOParser: data/cifar10_train.rec, use 4 threads for decoding..
[23:18:15] src/io/iter_image_recordio.cc:220: ImageRecordIOParser: data/cifar10_val.rec, use 4 threads for decoding..
[23:18:15] /mxnet/dmlc-core/include/dmlc/./logging.h:300: [23:18:15] src/c_api/c_api_ndarray.cc:381: Operator _zeros cannot be run; requires at least one of FCompute, NDArrayFunction, FCreateOperator be registered
Stack trace returned 10 entries:
[bt] (0) /mxnet/python/mxnet/../../lib/libmxnet.so(_ZN4dmlc15LogMessageFatalD1Ev+0x3c) [0x7feadfb2b5cc]
[bt] (1) /mxnet/python/mxnet/../../lib/libmxnet.so(MXImperativeInvoke+0x673) [0x7feae069e9a3]
[bt] (2) /usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call_unix64+0x4c) [0x7feb828bce40]
[bt] (3) /usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call+0x2eb) [0x7feb828bc8ab]
[bt] (4) /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(_ctypes_callproc+0x48f) [0x7feb82acc3df]
[bt] (5) /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(+0x11d82) [0x7feb82ad0d82]
[bt] (6) python(PyObject_Call+0x43) [0x4b0cb3]
[bt] (7) python(PyEval_EvalFrameEx+0x5faf) [0x4c9faf]
[bt] (8) python(PyEval_EvalCodeEx+0x255) [0x4c2765]
[bt] (9) python(PyEval_EvalFrameEx+0x68d1) [0x4ca8d1]
Traceback (most recent call last):
File "train_cifar10.py", line 53, in
fit.fit(args, sym, data.get_rec_iter)
File "/mxnet/example/image-classification/common/fit.py", line 187, in fit
monitor            = monitor)
File "/mxnet/python/mxnet/module/base_module.py", line 444, in fit
for_training=True, force_rebind=force_rebind)
File "/mxnet/python/mxnet/module/module.py", line 388, in bind
state_names=self._state_names)
File "/mxnet/python/mxnet/module/executor_group.py", line 205, in init
self.bind_exec(data_shapes, label_shapes, shared_group)
File "/mxnet/python/mxnet/module/executor_group.py", line 301, in bind_exec
shared_group))
File "/mxnet/python/mxnet/module/executor_group.py", line 605, in _bind_ith_exec
context, self.logger)
File "/mxnet/python/mxnet/module/executor_group.py", line 583, in _get_or_reshape
arg_arr = nd.zeros(arg_shape, context, dtype=arg_type)
File "/mxnet/python/mxnet/ndarray.py", line 900, in zeros
return _internal._zeros(shape=shape, ctx=ctx, dtype=dtype)
File "/mxnet/python/mxnet/_ctypes/ndarray.py", line 133, in generic_ndarray_function
c_array(ctypes.c_char_p, [c_str(str(i)) for i in kwargs.values()])))
File "/mxnet/python/mxnet/base.py", line 78, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [23:18:15] src/c_api/c_api_ndarray.cc:381: Operator _zeros cannot be run; requires at least one of FCompute, NDArrayFunction, FCreateOperator be registered
Stack trace returned 10 entries:
[bt] (0) /mxnet/python/mxnet/../../lib/libmxnet.so(_ZN4dmlc15LogMessageFatalD1Ev+0x3c) [0x7feadfb2b5cc]
[bt] (1) /mxnet/python/mxnet/../../lib/libmxnet.so(MXImperativeInvoke+0x673) [0x7feae069e9a3]
[bt] (2) /usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call_unix64+0x4c) [0x7feb828bce40]
[bt] (3) /usr/lib/x86_64-linux-gnu/libffi.so.6(ffi_call+0x2eb) [0x7feb828bc8ab]
[bt] (4) /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(_ctypes_callproc+0x48f) [0x7feb82acc3df]
[bt] (5) /usr/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so(+0x11d82) [0x7feb82ad0d82]
[bt] (6) python(PyObject_Call+0x43) [0x4b0cb3]
[bt] (7) python(PyEval_EvalFrameEx+0x5faf) [0x4c9faf]
[bt] (8) python(PyEval_EvalCodeEx+0x255) [0x4c2765]
[bt] (9) python(PyEval_EvalFrameEx+0x68d1) [0x4ca8d1]
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

I use mxnet docker for GPU. without re-build mxnet, the system works well with the command python train_cifar10.py --network resnet --num-layers 110 --batch-size 128 --gpus 0,1,2,3

I  modify config.mk in /mxnet/make directory, and set USR_PROFILER = 1

make

after that, I can use profiler and I can run the sample py code in /mxnet/example/profiler/*

However I cannot run python train_cifar10.py --network resnet --num-layers 110 --batch-size 128 --gpus 0,1,2,3. It shows the error message above.

What have you tried to solve it?

No idea

make clean and make again

@piiswrong Yep, I have tried that to make the profiler work (i.e. 1. set USR_PROFILER = 1, 2. make clean, 3 make). It does not work. Any other suggestions?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


[BUG] OSD integTest lack additional_config entrypoint for both OS and OSD clusters

Hi,
This is related to OSD specific integTest.
In OS, the additional config entry can be grab from the opensearch-<>-test.json and added to the opensearch.yml.
In OSD, this functional is half-complete in service_opensearch_dashboards.py and only allow hardcoded entries, without interpreting the entries from opensearch-dashboards-<>-test.json.
Moreover, in OSD integTest you need to start both OS and OSD, means the additional config in OS also need a new param to hold, so it wont get mixed up with OSD additional config. Right now both are under additional-cluster-configs key and will both be pushed to opensearch_dashboards.yml.
Thank.

Only partially resolved this issue in PR:

3590

[Triage] The issue is partially resolved.

We have implemented the OSD side of configs already.
As for OS configs during OSD test there does not seems to have a specific need from plugins.
Will close this issue for now until further notices. Thanks.

Seems like there is a use case here:

https://github.com/opensearch-project/opensearch-build/pull/4402

Low priority: for OpenSearch Dashboards we set cluster.routing.allocation.disk.threshold_enabled=false in our GitHub workflows. It would be a nice-to-have feature to be configure OpenSearch when we needed
Priority is low because we should figure out why that threshold is being hit.

I wouldn't categorize this as a low priority since this is blocking running the tests with the same environment today locally and in the infra pipeline. Having identical test environments is key to reproducibility. Figuring out why we have to increase the memory limits is a different issue and I don't think we should tie the two together since that may be a bigger problem to solve and we shouldn't hold off on this feature on the hopes that that will be resolved.


Can anybody tell me the exact paper name which explains this project

Dear authors,
Do u have any resources explaining loss function working and model training?
Thanks in advance.

Urgent please

@article{wang2021face,
title={Face. evoLVe: A High-Performance Face Recognition Library},
author={Wang, Qingzhong and Zhang, Pengfei and Xiong, Haoyi and Zhao, Jian},
journal={arXiv preprint arXiv:2107.08621},
year={2021}
}


[Feature request] Omit a mandatory parameter if resource can be queried by List

For example:
There is a generated cmdlet, which matches API design, where HsmName and ResourceGroupName are mandatory.
Get-AzKeyVaultManagedHsmRegion -HsmName <String> -ResourceGroupName <String> [-SubscriptionId <String[]>]
 [-DefaultProfile <PSObject>] [<CommonParameters>]

But we can list all HSMs by HsmName and then get its ResourceGroupName so that ResourceGroupName can be omitted in this case. That's one of CLI common design.
See
az keyvault region list --hsm-name
                        [--resource-group]

Proposal:
Autorest.PowerShell supports this as its built-in function.

how to handle conflict

two resources group names contain resource with the same names
resource graph may be a better choice


Unable to detect how many accessories are connected to iPhone device

Hi @Shmoopi , Can you please help in this issue?
I connected to USB from MacBook and headphones to iPhone 6 contains iOS 12.4.7 version.
I also tested this code with iPhone 8 contains iOS 13.5.1 versions.
always getting 0 for number accessories connected.
EAAccessoryManager *accessoryManager = [EAAccessoryManager sharedAccessoryManager];
// Get the number of accessories connected
int numberOfAccessoriesConnected = (int)[accessoryManager.connectedAccessories count];
// Check if there are any connected
if (numberOfAccessoriesConnected > 0) {
// There are accessories connected
return true;
} else {
// There are no accessories connected
return false;
}
in SSAccessoryInfo.m file

Hi @Shmoopi , Can you please help in this issue?
I connected to USB from MacBook and headphones to iPhone 6 contains iOS 12.4.7 version.
I also tested this code with iPhone 8 contains iOS 13.5.1 versions.
always getting 0 for number accessories connected.
EAAccessoryManager *accessoryManager = [EAAccessoryManager sharedAccessoryManager];
    // Get the number of accessories connected

    int numberOfAccessoriesConnected = (int)[accessoryManager.connectedAccessories count];

    // Check if there are any connected

    if (numberOfAccessoriesConnected > 0) {

        // There are accessories connected

        return true;

    } else {

        // There are no accessories connected

        return false;

    }

in SSAccessoryInfo.m file


Universal OTA approach -> real production grade code

I believe to have designed an approach to OTA that is universal, robust and production ready.
Considering it is design only for now (yes I did make proof of concepts to check it is not nonsense), I would like feedback before I start coding all of it (which I will anyway).
One thing I want to say already is that I choose this two step design because I see many repositories that simply cannot combine the SSL based download scheme with their native functionality and fit within RAM and Flash.  So, having said that, read on...
One comment I am looking for, is how you would like it to end up in the main tree of esp-open-rtos? As an extra, in the bootloader tree or ...?
You can also leave comments at https://github.com/HomeACcessoryKid/ota
Thanks in Advance...

for those interested to look at the result so far, it is quite useable but still not well documented yet.
(https://github.com/HomeACcessoryKid/ota)
(https://github.com/HomeACcessoryKid/ota-demo)
you should start with flashing the ota repository, and then observe what happens... it all bootstraps out of that... it can take a few minutes to complete the first time so be patient
feedback appreciated

Couldn't the firmware just be signed, avoiding the need for SSL? Could have a version number that is checked too, to stop an attacker downgrading the firmware.

Of course anyone could do that even today, but it opens a whole lot of questions how to make this accessible to many people that cannot deliver a satisfactory setup for those either because they lack infrastructure to setup a web server, or they are not top-grade-coders or ...
In my approach, the web hosting - world wide - is delivered by GitHub so if the repository becomes popular, it scales.
Also, key management is a hassle, so my approach takes care that the GitHub certificates protect the payload, and the ota program protects those certificates. When setting up a 'release' in GitHub it takes care that only the owners of the repository can set up the files in it.
So, yes, your approach could work (but why didn't anyone do it then?), but it lacks the architecture of a plan that can work for the entire esp-open-rtos population without any investment...
Considering that scope, I would appreciate further review and thanks for your initial one already.
Thanks,
HacK
PS. downgrading is not necessarily a bad thing and I made it possible in my code on purpose.
PPS. The way I am building my suite of production grade HomeKit accessories based on off the shelf hardware means that I need to be concerned about delivering to many devices...

Does github allow download via http, or only https now?
Allowing downgrading might be bad when just using signatures, because an attacker might be able to trick the device into downloading to a old public signed firmware that had a vulnerability that had already been fixed, and then exploit that vulnerability.
It doesn't seem that much harder to sign releases than to manage SSL certificates, and seems worth considering given the significant reduction in code complexity. It might also support a range of distribution methods including upload from a signed file via the wificfg interface etc.
Personally I've avoided OTA updates to avoid the loss of security, but people seem to want it, it seems an essential feature, so I might need to implement it and shall explore the options.
I use signed data for upload. A server can verify the source to ensure the integrity of the system. The key for this can be set via the wificfg interface, stored in the sysparam area. I presume the same could be done for a firmware key, to allow people to switch the firmware sources to one based on a different key, or it could be hard coded in the firmware but that would locked it to the one source.

GitHub is https only nowadays.
It is true that more and more devices require OTA in order to be able to patch security and feature upgrades. My devices are often build in, connected to mains and there are many.
Having to solder for each update would stop one from doing it and would create that many more devices in the world that can be hacked.
I'm happy to think along in your approach of the subject.
The subject of scalability and low complexity is important for me and for that reason alone, I will stick with my approach. My users won't have to keep any keys, only add like 5 lines of code to whatever they have and they are in business.
The way of downgrading is because the author withdraws a version in GitHub. The device cannot influence that so short of hacking that GitHub account, there is no attack surface.
You have me half convinced that approaching such a scenario can also be covered by publishing the old code with a higher version is also OK. I'll sleep a few more nights over that...
Note that in my approach, the author of the code still adds a SHA384 hash and length file that is verified before the code is accepted. I think that extending my OTA program to optionally also accept a public key from the user-program author (uploaded at wifi-cfg time) is a good improvement. It maintains the low complexity option. Consider that one added to the todo-list.


Remove dependence on WEBGL_color_buffer_float for EDL

Fixes #6794.
Fixes #6792.
Closes https://github.com/AnalyticalGraphicsInc/cesium/issues/6543.
When looking at #6792, noticed that EDL was using a lot more gbuffer data than it really needed... we were storing eyespace positions as RGBA float, when that could all be re-derived in the EDL pass from a much more compact packed depth.
I'm not seeing much of a performance change on either my GT750m/Windows or Intel/Linux systems, but it's nice to reduce requirements and memory use anyway.
Also discussed with @lilleyse offline the possibility of removing the MRT requirement by using a double-size gbuffer (so, 1920 x 2160 for a 1920 x 1080 render), but decided the science experiment for performance might not be worth it since frag_depth will always be necessary.
Mentioning it here if anyone thinks otherwise, or thinks it would be fun to try.

Thanks for the pull request @likangning93!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Works in 2D/CV.

Fine in CV, seems to actually work better now in 2D than before, but still not perfectly.

👍


Accept new build flags when upgrading

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

This pull request fixes #1699 by accepting new build flags when upgrading a Formula
Please review, and thanks for your comments!
/cc @MikeMcQuaid

Thanks again for the great PR, @amyspark!


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
d354121 -> b224509

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.24.1 -> v1.25.1

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.25.1
Compare Source
Bug Fixes

deps: update gomod (#704) (b5574c4)

v1.25.0
Compare Source
Features

add ability to unskip upgrade test (#702) (95cbb82)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:


[path_provider] refactor: move Directory if statements to function

Description
There is too much duplicate if statements, I feel it is better to move it in a standalone private function.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the [CLA].
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@googlebot I signed it!

This refactor definitely makes sense; could you update it for null safety so that it applies to the latest master? If so I can review and land it.
We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.

This refactor definitely makes sense; could you update it for null safety so that it applies to the latest master? If so I can review and land it.
We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.

I just did and also fixed the one for directories, removed duplicate logics.

Looks good, thanks! It's failing the format check on the bots; if you can make that minor change that would be great, otherwise we can do it as part of getting it checked in.

I just used the pub global run flutter_plugin_tools format command suggested in the error message to format the code.

Looks like there were infrastructure issues with one of the tests; re-running to see if it will turn green.

Looks like there were infrastructure issues with one of the tests; re-running to see if it will turn green.

Yeah, I noticed!

Ah, it's failing due to an FFI breaking change that caused issues for path_provider_windows; that's since been fixed. Could you merge master into this branch and re-push? That should get everything green.

Ah, it's failing due to an FFI breaking change that caused issues for path_provider_windows; that's since been fixed. Could you merge master into this branch and re-push? That should get everything green.

I wasn't able to merge master into the branch, Git is saying everything is up to date.

Your last merge from master was 12 days ago; there have been a number of commits since then. Make sure you are merging from a freshly synced master (e.g., fetch upstream; merge upstream/master), not a local, stale master.

Your last merge from master was 12 days ago; there have been a number of commits since then. Make sure you are merging from a freshly synced master (e.g., fetch upstream; merge upstream/master), not a local, stale master.

I have merged the master but that same test keeps failing and I don't think it has to be with code:
ERROR: Unable to execute "gcloud auth activate-service-account --key-file=/home/cirrus/gcloud-service-key.json". Stderr:

That's an infra issue; I've restarted the tests. Merging in master was to fix a different error that the previous run had, which was a real error at that version of master.

That's an infra issue; I've restarted the tests. Merging in master was to fix a different error that the previous run had, which was a real error at that version of master.

The previous run error was actually the same as this, kindly look into it.

I'm investigating why this infra failure is now happening persistently. In the meantime, I can manually land, but I'm afraid the last null-safety migrations collided with the changes here; could you merge in the latest master and resolve the conflicts? Once you do, I'll manually land it.
Sorry for the collision; unfortunately getting path_provider migrated was high priority.

Are you still planning on updating this to correctly account for the null safety changes?

Are you still planning on updating this to correctly account for the null safety changes?

I have been busy with work these days, I should be able to look into it by Sunday.

Thank you for your contribution. I'm going to close this PR for now since there are outstanding comments, just to get this off our PR review queue. Please don't hesitate to submit a new PR if you have the time to address the review comments. Thanks!


ROX-18865: removing Cloud Provider and Availability Zone form groups from create instance modal

As it states in the title above. It should look as below:

Codecov Report
Patch coverage has no change and project coverage change: +0.04% :tada:

Comparison is base (d671e2b) 8.90% compared to head (c033126) 8.95%.

Additional details and impacted files
@@           Coverage Diff            @@
##            main    #117      +/-   ##
========================================
+ Coverage   8.90%   8.95%   +0.04%
========================================
  Files         37      37
  Lines        550     547       -3
  Branches     112     112
========================================
  Hits          49      49
+ Misses       465     462       -3
  Partials      36      36

Files Changed
Coverage Δ

src/routes/InstancesPage/CreateInstanceModal.js
0.00% <ø> (ø)

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


event: scaled range bucket timer

Commit Message: Add RangeTimer and scaling implementation
Additional Description:
Add an interface for timers that can be enabled for some timeout within a range. Also add an implementation where timers are created by a manager object which can efficiently scale their timeouts.
Risk Level: low - no functional changes
Testing: wrote and ran unit tests
Docs Changes: none
Release Notes: none
For #11427, and supersedes #12106

/wait


npm ERR! peer dep missing<EMAIL_ADDRESS><=0.59, required by<EMAIL_ADDRESS>

react-native info:
System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 169.62 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.3 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 16, 23, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 25.0.2, 26.0.2, 27.0.0, 27.0.3, 28.0.3, 29.0.2
      System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>00203
    Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    create-react-native-app: 1.0.0
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7
    react-native-rename: 2.2.2

Why did you close this?

^ +1. Is the cap at RN 0.59 intentional or am I going to be okay incorporating this into RN 0.61.2?


Create/Deploy Docker project

I'd love the option to create a docker project (func init --docker) and then publish to ACR or Docker Hub

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.\n\nHappy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


documents pipelines-as-code-info configmap

Closes #907
Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #914 (ccfa57e) into main (5fcc471) will decrease coverage by 0.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #914      +/-   ##
==========================================
- Coverage   64.13%   63.95%   -0.18%
==========================================
  Files          79       79
  Lines        5130     5144      +14
==========================================
  Hits         3290     3290
- Misses       1530     1544      +14
  Partials      310      310

Impacted Files
Coverage Δ

pkg/webhook/reconciler.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Error! DLL amfrt64.dll failed to open (Intel CPU & NVIDIA GPU)

What's your platform?
Python Version: 3.10.6 64-bit
Platform: Windows 10 amd64
FFmpeg Version: N-105325-g7512293cf9
FFmpeg Path: C:\Users\skril\AppData\Local\Programs\Python\Python310\Lib\site-packages\ae_ffmpeg\Windows\ffmpeg.exe
Auto-Editor Version: 23w04a

Bug description
After using auto-editor for months (using mp4) I had mkv files laying around. I tried a few and oddly each gave me an AMD GPU hardware encoder error. I thought it was an incompatibility issue, so then I attempted to force other well-known encoders and it didn't understand. I also converted the files to mp4 if it helped and that didn't work either. I am very confused. Thanks.
What command did you use
(Tried both mkv and mp4)
auto-editor --margin 0.2sec "example.mkv"
Error! DLL amfrt64.dll failed to open

auto-editor --margin 0.2sec "example.mp4"
Error! DLL amfrt64.dll failed to open

(Forcing encoder)
auto-editor -vcodec h264_nvenc --margin 0.2sec "example.mkv"
Error! Unknown encoder 'h264_nvenc'

auto-editor -vcodec libx264 --margin 0.2sec "example.mp4"
Error! Unknown encoder 'libx264'

What properties does your input video have?
No response
Comments

I want to clarify that I am NOT a code expert.

UPDATE: So, up until now I figured out that when looking more closely at files which had 'hevc' aka h.265 transcoding, auto-editor will always produce the aforementioned .dll error; yet still does not recognize common codecs like libx264 etc. Why is this happening?

"libx264", isn't an common codec, it's a specific h264 implementation under GPLv3. If you want to use it, install ffmpeg then run auto-editor with the --my-ffmpeg flag. h.265 should be supported, the codec is called hevc

If you're getting this error, download FFmpeg and then add the --my-ffmpeg flag when using auto-editor.

Note: I'm not sure if it's possible to compile the default ffmpeg that can work on all common hardware. If you know, please make a pull request.


Mistyping in SouthKorea Provider

Hi.
In SouthKorea provider src/Yasumi/Provider/SouthKorea.php, LUNAR_HOLIDAY constant has mapping table for 'seollal' and it has entry for year 2039, but date value is year 2037.
We should change 2039-1-24 instead of 2037-1-24.
Thanks.

@barami Thank you very much for spotting this! I will make a correction.

Fixed in the dev branch (Targeted for the 2.5 release).


Support JS file？

I thought it supports any file, but there is no effect in the js file. Will you support js files?

Thank you for your valuable feedback.
Actually, we didn't plan to support all the languages, we initially planned only for a flutter, but now we have added support for all the languages and all file extension except for CSS, LESS, SCSS. We don't want to break the internal feature of the vscode, that's why we are not supporting these languages
You can now enjoy it in the js file


Capture delay

First of all, thanks for an awesome library. This is so helpful to work with.
I have an issue with capturing delay. It takes about 2-3sec. for it after the respective button is pressed, which is very noticeable in the eye. Please assist me in solving this issue. Thanks in advance

Guys, is there an option to facilitate the capturing process? Please answer, this is really very important.

I have this same issue, any feedback on how to improve this would be great

change the captureQuality to 'low' or 'medium', this will facilitate the capturing process

For some reason there is no real delay when taking a photo in an android emulator.

But when this exact same app is tested on hardware there is a 4-5 sec delay after hearing the shutter sound to when the callback is called.

Hello guys, I wanna ask you if you found a solution for the delay sound. Also when using flash, capture sound is heard before camera takes picture. Is there any solution for this?
Thanks alot.

Replacing the Capture  tag with  from the readme example improved the issue for me. Hope this helps.

+1

Any one found a solution for this please ??

It is also possible to have sync calls to the native thread: https://github.com/react-native-community/discussions-and-proposals/pull/11#discussion_r
I quickly tested it an it works much faster than using the async method.
However this can conflict with the react-native chrome debugger. If we would use this implementation under the hood we should detect if a chrome debugger instance is connected and fallback to the async code. cc @sibelius

we can try that, maybe a flag or something

@DavitVosk @Tzinov15 @jose920405 @Gatreek92 Anyone interested can try https://github.com/n1ru4l/react-native-camera/commit/da3f8ec538ffc96552a08574cac7fec14fa386a6
I added a sync mode toggle to the example app. Keep in mind this is android only. I had no time to do benchmarks, but it seems to me that sync mode is slightly faster than async mode.

We have a delay to on capturing photo and capturing video to (the record starts 1 entire second after the sound) only on android.
Please reopen.


Introductory blog post

Notes for post in here https://docs.google.com/document/d/1ymsSMPZ6zyCZN5vOAin308qqG4joq2hZC6UMQXKRSP4/edit
Get in touch with Alice from Lowr to share what we've written.

I have got the reading age down to 14. Think this post is pretty much ready to go.

READABILITY CONSENSUS
Based on (7) readability formulas, we have scored your text:
Grade Level: 9
Reading Level: standard / average.
Age of Reader: 13-15 yrs. old (Eighth and Ninth graders)


V2 - Add a callback hook for when environments are fetched for local evaluation

This callback should also be triggered for when calls fail too, something along the lines of
 onEnvironmentChange: (error:Error, result: EnvironmentModel) => void

Added this in this commit, feel free to check out if that's what you had in mind.

Hey @noah-troncoso would you be up for contributing to our docs?


New version: GnuWin32.Grep version 3.5.0

Pull request has been created with komac v2.1.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335141
2024-03-22 18:10:34.376 [CLI ] Unable to locate nested installer at: C:\Users\VALIDA~1\AppData\Local\Temp\WinGet\GnuWin32.Grep.3.5.0\extracted\grep.exe

(Automated response - build 872.)

Automatic Validation ended with:

Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\grep.exe returned exit code: 2

(Automated response - build 876.)

@wingetbot waivers Add Validation-Executable-Error


Enhancement : RevitConnector : transfer Revit Builtin categories (OST_xx)

Prerequisites

[x] I read the contribution guidelines
[x] I checked the documentation and found no answer.
[x] I checked existing issues and found no similar issue.
[x] I checked the community forum for related discussions and found no answer.
[x] I'm requesting the feature to the correct repository (see also speckle-server, speckle-sharp, specklepy, speckle-docs, and others)

What package are you referring to?
Revit Connector
Is your feature request related to a problem? Please describe.
Yes, since we're depending with leaDE on classifications and Revit has nothing to offer but builtin categories this is more a bug than a feature
Describe the solution you'd like
Currently, when pushing from Revit to speckle, the display name for the builtin cat is transfered. Since this is related to the language you start Revit with, it is not a relyable classification. Translations may change during Revit versions and we have to provide mappings for all supported languages of Revit for all Revit versions (2023. 22. 21. 20, ...)
Additionally to the translated Revit category I'd like to add a new parameter to the transfered parameters called BuiltInCategory and value is OST_Walls for example.
Describe alternatives you've considered
There is no alternative ;-)
Additional context
nothing to add, so far
Related issues or community discussions
Found nothing

Hey @thoffeller we were just discussing the same issue recently, yes please go ahead!
Note that there are a few different places where we set the element.category property, but a quick search should yield all cases.

Hi @teocomi , shall I replace the current approach and override it or do we add another category? I haven't checked other connectors, is there a similar approach? This would be realy useful, because we do mappings to elements based on their classification.

Please just add a new builtInCategory property, other connectors don't have this problem as far as I know :)


Rate-limiting plugin doesn't work

Summary
I created a rate-limiting plugin which limit by consumer and set policy to "redis", but it doesn't work.
Steps To Reproduce
1.Create a api named "api_test"
2.Create a consumer named "consumer_test".
3.Create a rate-limiting plugin which apply to "consumer_test" and "api_test", set policy to "redis".
some configuration:
config.minute = 1
config.redis_database = 1
config.limit_by = consumer
config.policy = redis

Other configuration is default, and redis_host and redis_password is correct.
4.Run some requests to "api_test" found no work.
5.After that, I try to change policy to "local" and "cluster", but still no work.
Additional Details & Logs

Kong version (0.10.1)
Kong debug-level startup logs (kong start)
Kong error logs (N/A)
Kong configuration (nature)
Operating System (docker/ubuntu)

Whether postgres will affect this?

Sometimes it even dosen't work anymore...let all request be proxied...

There was a recent PR that seems related; can you have a look at https://github.com/Mashape/kong/pull/2481 and see if this solves your problem?

@p0pr0ck5 At last, I found that if I set redis_database to 0, it work fine.


Readability improvement for Cache Description

For GC288FW the cache-description is in blue color. Nevertheless the readability improvement (change of background color) is not working here. For my opinion descriptions with this color should also be improved for readability by c:geo.

Also #010101 is a very dark color, but not handled. The problem is, that the brightness is subjective and there are many ways to change the color.

I know....I raised this issue to ask whether this color should be included or not ??


🚀 Feature: In Mobile view, Sidebar should auto-close on click of any menu-item

🔖 Feature description
Sidebar should auto-close on click of any menu-item.
🎤 Why is this feature needed ?
Better UX.
✌ How do you aim to achieve this?
Will call sidebar close function on click of sidebar Item
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
Yes I am willing to submit a PR!

@akshitarora921 can u assign this issue to me?

@dartpain can u assign this issue to me?

@tenokami  should it auto close? I personally would prefer for the sidebar to be there, unless im short on space

@dartpain I agree wit you here. For sidebar to close whenever the user clicks anything in it: chat, reset key, about, etc would be unexpected behaviour and cause frustration

@dartpain @tenokami Just want to add a reference video https://github.com/arc53/DocsGPT/assets/11087313/ec29ca15-53b3-448f-bb9e-e1b86a862c64


proprietary license identifier

The spdx license list only contains open-source licenses. Other json configs, like composer.json and package.json allow the "proprietary" license identifier for closed-source projects. I hope this can be allowed here as well.
https://getcomposer.org/doc/04-schema.md#license

Interesting. @ryanycoleman reccomended the spdx library because it is what the forge uses for validation. We could add code to try validating against spdx, the try validating against proprietary, then fail.

I guess the Forge isn't ever going to accept 'proprietary' as a licence string, since they wouldn't be able to redistribute the code, but @nibalizer's suggestion sounds like a good idea - allow it as a special string.

I really would like to be able to validate my (or my companies) proprietary puppet-modules metadata.json without the need for "--no-strict-license", not all modules go the the forge ;)

I agree... my company uses "Proprietary" to identify modules which we haven't open sourced (this is a management approval process for us). I'd still like to be able to keep these modules release-ready...

:+1:

:+1:

anyone care to provide a patch here ;)

Sure :)

My pull request is merged (thanks!) and solves the issue so i'll close it.


Cannot find module webpack from next-plugin.mjs

I installed the package:

pnpm install @builder.io/react-hydration-overlay

I updated the root of my app like this:

click to expand

// file: _app.tsx
/*
...
imports
...
*/
import { HydrationOverlay } from<EMAIL_ADDRESS>
const MyApp: AppType = ({ Component, pageProps }) => {
  return (
    <HydrationOverlay>
      <Head>
        <title>{BRAND_NAME}</title>
      </Head>
      <Component {...pageProps} />
    </HydrationOverlay>
  );
};

export default api.withTRPC(MyApp);

I updated my next config like this:

click to expand
// file: next.config.mjs
import { withHydrationOverlay } from<EMAIL_ADDRESS>/**
 * Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially useful
 * for Docker builds.
 */
await import("./src/env.mjs");

/** @type {import("next").NextConfig} */
const config = {
  reactStrictMode: true,

  /**
   * If you have `experimental: { appDir: true }` set, then you must comment the below `i18n` config
   * out.
   *
   * @see https://github.com/vercel/next.js/issues/41980
   */
  i18n: {
    locales: ["fr"],
    defaultLocale: "fr",
  },

  typescript: {
    ignoreBuildErrors: true,
  },
  eslint: {
    ignoreDuringBuilds: true,
  },
  swcMinify: true,
};

export default withHydrationOverlay()(config);

I run

pnpm dev

Current behavior
My terminal throws this error:
> next dev

- ready started server on <IP_ADDRESS>:3000, url: http://localhost:3000
- info Loaded env from /home/benjamin/code/jegwell-t3/.env
- error Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/benjamin/code/jegwell-t3/node_modules/.pnpm/@builder.io+react-hydration-overlay@0.0.5_react-dom@18.2.0_react<EMAIL_ADDRESS>imported from /home/benjamin/code/jegwell-t3/node_modules/.pnpm/@builder.io+react-hydration-overlay@0.0.5_react-dom@18.2.0_react<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:224:11)
    at moduleResolve (node:internal/modules/esm/resolve:837:10)
    at defaultResolve (node:internal/modules/esm/resolve:1035:11)
    at DefaultModuleLoader.resolve (node:internal/modules/esm/loader:269:12)
    at DefaultModuleLoader.getModuleJob (node:internal/modules/esm/loader:153:32)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:33)
    at link (node:internal/modules/esm/module_job:75:36) {
  type: 'Error',
  code: 'ERR_MODULE_NOT_FOUND'
}
 ELIFECYCLE  Command failed with exit code 1.

Expected behavior
My app start without errors
Additionnal info

my package.json:

click to expand
{
  "name": "jegwell-t3",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "build": "next build",
    "dev": "next dev",
    "postinstall": "prisma generate",
    "lint": "next lint",
    "typecheck": "tsc --noEmit",
    "start": "next start",
    "test:e2e": "playwright test",
    "test:e2e:local": "playwright test --headed --project='Mobile Chrome'",
    "test:e2e:local-ui": "playwright test --ui",
    "test:e2e:snapshots": "playwright test --update-snapshots",
    "stripe:listen": "stripe listen --forward-to localhost:3000/api/stripe",
    "stripe:trigger": "stripe trigger payment_intent.succeeded"
  },
  "dependencies": {
<EMAIL_ADDRESS>"^0.0.5",
    "@clerk/nextjs": "^4.17.1",
    "@fontsource/roboto": "^4.5.8",
    "@hookform/resolvers": "^3.1.1",
    "@prisma/client": "^4.11.0",
    "@radix-ui/react-alert-dialog": "^1.0.4",
    "@radix-ui/react-dialog": "^1.0.5",
    "@radix-ui/react-dropdown-menu": "^2.0.5",
    "@radix-ui/react-label": "^2.0.2",
    "@radix-ui/react-popover": "^1.0.7",
    "@radix-ui/react-radio-group": "^1.1.3",
    "@radix-ui/react-select": "^1.2.2",
    "@radix-ui/react-slot": "^1.0.2",
    "@stripe/stripe-js": "^1.54.1",
    "@t3-oss/env-nextjs": "^0.2.1",
    "@tanstack/react-query": "^4.28.0",
    "@tanstack/react-table": "^8.9.3",
    "@trpc/client": "^10.18.0",
    "@trpc/next": "^10.18.0",
    "@trpc/react-query": "^10.18.0",
    "@trpc/server": "^10.18.0",
    "class-variance-authority": "^0.6.0",
    "clsx": "^1.2.1",
    "cmdk": "^0.2.0",
    "lucide-react": "^0.224.0",
    "micro": "^10.0.1",
    "next": "^13.4.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-hook-form": "^7.45.2",
    "react-slick": "^0.29.0",
    "stripe": "^12.16.0",
    "superjson": "1.12.2",
    "tailwind-merge": "^1.12.0",
    "tailwindcss-animate": "^1.0.5",
    "zod": "^3.21.4"
  },
  "devDependencies": {
    "@playwright/test": "^1.36.2",
    "@types/eslint": "^8.21.3",
    "@types/node": "^18.15.5",
    "@types/prettier": "^2.7.2",
    "@types/react": "^18.0.28",
    "@types/react-dom": "^18.0.11",
    "@types/react-slick": "^0.23.10",
    "@typescript-eslint/eslint-plugin": "^5.56.0",
    "@typescript-eslint/parser": "^5.56.0",
    "@vitejs/plugin-react": "^4.0.0",
    "autoprefixer": "^10.4.14",
    "eslint": "^8.36.0",
    "eslint-config-next": "^13.4.1",
    "jsdom": "^22.0.0",
    "postcss": "^8.4.21",
    "prettier": "^2.8.6",
    "prettier-plugin-tailwindcss": "^0.2.6",
    "prisma": "^5.1.1",
    "tailwindcss": "^3.3.0",
    "typescript": "^5.0.2",
    "vitest": "^0.31.1"
  },
  "ct3aMetadata": {
    "initVersion": "7.12.2"
  }
}

I tried using the Webpack helper, it gave me a similar error

click to expand
> next dev

- ready started server on <IP_ADDRESS>:3000, url: http://localhost:3000
- info Loaded env from /home/benjamin/code/jegwell-t3/.env
- error Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'webpack' imported from /home/benjamin/code/jegwell-t3/node_modules/.pnpm/@builder.io+react-hydration-overlay@0.0.5_react-dom@18.2.0_react<EMAIL_ADDRESS>Did you mean to import webpack/webpack-lib.js?
    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:781:9)
    at moduleResolve (node:internal/modules/esm/resolve:830:20)
    at defaultResolve (node:internal/modules/esm/resolve:1035:11)
    at DefaultModuleLoader.resolve (node:internal/modules/esm/loader:269:12)
    at DefaultModuleLoader.getModuleJob (node:internal/modules/esm/loader:153:32)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:33)
    at link (node:internal/modules/esm/module_job:75:36) {
  type: 'Error',
  code: 'ERR_MODULE_NOT_FOUND'
}
 ELIFECYCLE  Command failed with exit code 1.

My IDE could not auto import withHydrationOverlay somehow, ts complains that the module does not exist.

Did I miss something?
PS: As a maintainer, is it better to have those "click to expand" or should I remove them next time?
Video
https://github.com/BuilderIO/hydration-overlay/assets/73464907/a7785582-b931-4231-928a-2fe79670c0b9

This is technically a duplicate of [https://github.com/BuilderIO/hydration-overlay/issues/15](my post) except you did a far better job at documenting your issue. As I mentioned in my post, the issue arises because of an explicit dependency on webpack, whereas the best practice with NextJS now  is to use webpack plugins through the webpack helper instance in the config file, not to install webpack directly.

If the maintainer can update the wrapper function to optionally accept a webpack instance, it will solve our problem.

@JohnRPB it seems like you know what you are doing, could you make a PR fixing this?
If not:
I suppose all we have to do is get rid of the webpack import in next-plugin.mjs and use the webpack given as an argument to the withHydrationOverlayWebpack function?
I never did that before so if you have any material that could help me to do this feel free to share it

I tried to fix this with the last brain cells I had after work.
Here is what I manage to understand:

We need to use the Webpack helper and pass as an optional argument the webpack given by the nextjs config file (see line 4 of the first block of code here) to the withHydrationOverlayWebpack function.

If no argument are given we use the webpack imported at the top of the file I suppose?. (this is the current behavior)

The next-plugin.ts file use the withHydrationOverlayWebpack.
We need to update it to make it use the webpack given as argument instead of the imported webpack at the top of the file.

I did that, build the library, added to my nextjs project. It somehow managed to start the dev server but did not show the overlay showing the Hydration Errors. I might have missed something.

It's getting late I will continue this an other day. :sleeping:

Not sure if this happens to everyone.
I use next.config.mjs and it happened to me so I guess this happens to everyone using mjs

Happening with me. I use .js and a package.json with type: module.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module<EMAIL_ADDRESS>imported from<EMAIL_ADDRESS>@kdx/kdx:dev:     at finalizeResolution (node:internal/modules/esm/resolve:255:11)
@kdx/kdx:dev:     at moduleResolve (node:internal/modules/esm/resolve:908:10)
@kdx/kdx:dev:     at defaultResolve (node:internal/modules/esm/resolve:1121:11)
@kdx/kdx:dev:     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
@kdx/kdx:dev:     at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
@kdx/kdx:dev:     at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
@kdx/kdx:dev:     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
@kdx/kdx:dev:     at link (node:internal/modules/esm/module_job:84:36) {
@kdx/kdx:dev:   code: 'ERR_MODULE_NOT_FOUND',
@kdx/kdx:dev:   url<EMAIL_ADDRESS>@kdx/kdx:dev: }
@kdx/kdx:dev:
@kdx/kdx:dev: Node.js v20.10.0

Should be fixed in https://github.com/BuilderIO/hydration-overlay/releases/tag/%40builder.io%2Freact-hydration-overlay%400.0.6

So I'm still getting the exact same error from before: "Cannot find package 'webpack' imported from<EMAIL_ADDRESS>I look and see that the webpack.mjs file imports 'webpack' as a dependency.

@JohnRPB upgrading to 0.0.6 fixed the webpack error I had. I did not use the webpack helper, I used the withHydrationOverlay function in my config file of my nextjs app (I don't use the App router).
Do you have more info related to your setup? or even steps to reproduce it?


Problem with EasyMotion Plugin

there are some problems with your i3config. If i rename my config in .i3.config for instance then your syntax highlighting works fine but the easymotion plugin dont work anymore. :(
if i dont use your syntax highlighting, so for example i dont change the name, then the easymotion plugin still works fine. I dont have a clue whats the problem. can't be the double !?

Hi Sven1,
Oh sorry for the late reply I need to catch still.
I don't use easymotion so I can't check it.
Just for testing purposes... how about keeping the file name as is and creating a symlink to it with target .i3.config?
Would that make both easymotion and i3config happy?

I was also running into this issue. Not sure the exact cause is, but removing the filetype (i.e. set ft=conf) easymotion would work again.
I've switched over to https://github.com/PotatoesMaster/i3-vim-syntax which works fine with easymotion. Really strange bug.

Hi @BerkeleyTrue,
not sure why you needed set ft=conf.
i3configdoesn't require setting a filetype, you can achieve the same results by changing the file name as one of .i3.config, i3.config, something.i3config, something.i3.config or setting set ft=i3config

@mboughaba my comment was to demonstrate removing the i3config settings by setting filetype to conf(i.e. not i3config), not the otherway around.


Retry 409 conflict response

Describe the bug
Our service sometimes hits a conflict while putting. We'd like to retry, the lib offers an option, but it appears a 409 response is not retried.
First it'd be fair to ask, should 409 generally be retried? For us the error literally says to do so, but perhaps in the general case it makes less sense. If it does make sense, it'd be lovely to have this feature. We're having to retry manually now. Not the worst, but definitely more complex than then simple .with_retry(RetryConfig::default())
Generic S3 error: response error "<?xml version='1.0' encoding='UTF-8'?> <Error>OperationAborted<Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>tx29de9421407d406eb7588-0064f72112</RequestId></Error>", after 0 retries: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz) Caused by: 0: response error "<?xml version='1.0' encoding='UTF-8'?> <Error>OperationAborted<Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>tx29de9421407d406eb7588-0064f72112</RequestId></Error>", after 0 retries: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz) 1: HTTP status client error (409 Conflict) for url (https://s3.gra.perf.cloud.ovh.net//block-submission-archive-prod/2023/09/05/12/29/7257748/0x26c152f988d9b3c47d5cbb0cf5571981b9684501df4713a8e0c18881a7124cdc.json.gz

To Reproduce
Store an item which is already in the process of being stored.
Expected behavior
Retry 409.
Additional context

What is the conditional operation being performed? From the HTTP specification

The 409 (Conflict) status code indicates that the request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request. The server SHOULD generate content that includes enough information for a user to recognize the source of the conflict.

In particular a 409 error code should not be being used for a transient error

s3.gra.perf.cloud.ovh.net

Are you talking to S3 or some S3-compatible API?

Operation is (object_store.put)[https://docs.rs/object_store/latest/object_store/trait.ObjectStore.html#tymethod.put]. Nothing special. API is advertised as an S3 API. The specific error returned also appears in the Amazon S3 reference, so it appears to all be to spec. It also makes sense to me. If a user makes two calls to put at the same path at the same time the server can write both (broken), queue the second, abort either, or abort both. Apparently S3 elects to abort the second and reply 409. I'm guessing that's what the error is saying.

imo a retry is reasonable here, but looking closer at the S3 reference, not on any 409, although OperationAborted looks ok to retry.
Reading the (HTTP 409 semantics)[https://www.rfc-editor.org/rfc/rfc9110#name-409-conflict]:

The 409 (Conflict) status code indicates that the request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request. The server SHOULD generate content that includes enough information for a user to recognize the source of the conflict.

After diving into this more deeply, I personally lean: we shouldn't retry this by default. It is totally reasonable to retry a concurrency conflict, but the user might want to be made aware instead of simply retrying and having one version overwrite the other. At most I'd suggest a feature where a user can specify what they want to be retried, and sets the OperationAborted code to be retried. I'd understand if maintainers feel that large a feature needs a bunch of upvotes first.
Side note: in our case I started ignoring 409s. I'm fairly sure these are duplicates in our case and storing one is enough. I'm having to string match the error now, it'd be neat if this lib could return its (AlreadyExists)[https://docs.rs/object_store/latest/object_store/enum.Error.html#variant.AlreadyExists] if it's correct OperationAborted is only a concurrent write error.

I'm fairly certain S3 only returns OperationAborted for the bucket level APIs, concurrent upserts simply follow last writer wins.

If two PUT	requests are simultaneously made to the same key, the request with the	latest timestamp wins

From https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html#ConsistencyModel
I suspect your S3 compatible API is only vaguely compatible 😅

Interesting. I think we can close the issue here. If more people on other platforms show up with similar errors, especially AWS, it may be worth taking another look.
Thanks for the swift replies and a great lib 💛


feat: Setup arxiv multi-pipeline experiment

Motivation
Configuration for arxiv dataset pipelines using multiple trigger policies and evaluation handlers.

I don't have a problem with merging this, although I run similar but different stuff for SIGMOD right now, which I will also merge at some point :)

Maybe we can merge the shared parts of the configurations at some point to reduce the duplication.


Adds support for being a nested addon

This adds support for ember-metrics to be a nested addon.
Implementation lovingly borrowed from the various references in:
https://github.com/ember-cli/ember-cli/issues/3718

😍  Thanks!


added Dutch translation

Thanks! Merged on devel.

We're switching to LingoHub to help manage translations. If you'd like to be added as a translator to the project, could you join the #i18n channel on Telescope's Slack?


handshake failed: ssh: unexpected message type 1 (expected 52)

I reported this on coreos/coreos-vagrant#106 but it also happens when trying to manage a cluster on EC2.
It happens when you have more than 7 keys in the ssh-agent.
My ~/.ssh/config says what key should be used for that host but the ssh tunneling feature seems to ignore that.

Let's figure something out for this one before 1.0

@jonboulle you wrote "let's figure something out before 1.0", but set the milestone to 0.13 -- is this intentional?...

I was able to reproduce this issue pretty consistently on Ubuntu once my SSH agent had more than 5 keys added to it. Removing keys fixed the issue, though it'd be nice to not have to work around this.
Note that Ubuntu also has a keychain, and you can't remove keys added using it from the agent with ssh-add -d, they will be automatically added back in.

We have to add tests first.

If we modify upstream Godeps/_workspace/src/golang.org/x/crypto/ssh/client_auth.go and add SSH2_MSG_DISCONNECT support we can handle this "unexpected" message correctly. Because it actually means 2016/03/15 16:35:00 Received *ssh.disconnectMsg ssh: disconnect reason 2: Too many authentication failures (<nil>). There is nothing to do in fleet code, only proper error handling. The error relates to SSH daemon configuration.
diff --git a/Godeps/_workspace/src/golang.org/x/crypto/ssh/client_auth.go b/Godeps/_workspace/src/golang.org/x/crypto/ssh/client_auth.go
index e15be3e..fbb6806 100644
--- a/Godeps/_workspace/src/golang.org/x/crypto/ssh/client_auth.go
+++ b/Godeps/_workspace/src/golang.org/x/crypto/ssh/client_auth.go
@@ -8,6 +8,7 @@ import (
        "bytes"
        "errors"
        "fmt"
+       "log"
        "io"
 )

@@ -283,6 +284,8 @@ func confirmKeyAck(key PublicKey, c packetConn) (bool, error) {
                case msgUserAuthFailure:
                        return false, nil
                default:
+                       msg, err := decode(packet)
+                       log.Printf("Received %T %v (%v)", msg, msg, err)
                        return false, unexpectedMessageError(msgUserAuthSuccess, packet[0])
                }
        }
@@ -324,6 +327,8 @@ func handleAuthResponse(c packetConn) (bool, []string, error) {
                case msgDisconnect:
                        return false, nil, io.EOF
                default:
+                       msg, err := decode(packet)
+                       log.Printf("Received %T %v (%v)", msg, msg, err)
                        return false, nil, unexpectedMessageError(msgUserAuthSuccess, packet[0])
                }
        }
@@ -387,6 +392,8 @@ func (cb KeyboardInteractiveChallenge) auth(session []byte, user string, c packe
                case msgUserAuthSuccess:
                        return true, nil, nil
                default:
+                       msg, err := decode(packet)
+                       log.Printf("Received %T %v (%v)", msg, msg, err)
                        return false, nil, unexpectedMessageError(msgUserAuthInfoRequest, packet[0])
                }

@kayrus makes sense (especially after reading the IANA defined parameters).  What's the plan of attack for taking this upstream?

@brianredbeard PR is here: https://go-review.googlesource.com/#/c/20687/

this fix is closed in favor of https://go-review.googlesource.com/#/c/20801/

Fixed: https://github.com/golang/crypto/commit/9e7f5dc375abeb9619ea3c5c58502c428f457aa2, we have to update godeps.


GSA IT should adopt Web AuthN

In order to avoid being a phishing target, education will never suffice. We must adopt Web AuthN
Acceptance Criteria

GSA IT allows us to use Web Authn tokens instead of (or in addition to) TOTP and PIV

Security considerations
Vastly improves our stance.
Implementation sketch

[ ] Ask infra, raise with leadership, talk with Bo and Shive.

Aidan Feldman (Tech Portfolio, NYC, he/him)  40 minutes ago
@William Salamon - ISI is leading GSA's ICAM Working Group, so i'd check with him

Aidan Feldman (Tech Portfolio, NYC, he/him)  < 1 minute ago
https://gsa-tts.slack.com/archives/C01J79YG1UL/p1612547494000300?thread_ts=1612545086.000200&cid=C01J79YG1UL
brian.muolo
@Aidan Feldman (Tech Portfolio, NYC, he/him) I hadn't seen anything specific on Web AuthN yet, but I'll ask our team and IS if there are any efforts ongoing.
From a thread in #gsa-it-tts-shared | Today at 12:51 | View reply


ui: Fix action badge pointers

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Fix #125

Codecov Report

Merging #159 (6aa56bc) into main (ee5ad61) will decrease coverage by 2.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #159      +/-   ##
==========================================
- Coverage   42.88%   40.71%   -2.18%
==========================================
  Files          88       81       -7
  Lines        2404     2316      -88
==========================================
- Hits         1031      943      -88
  Misses       1373     1373

Impacted Files
Coverage Δ

ui/src/shared/actions.js
62.96% <ø> (ø)

tests/py/event.py

tests/py/request.py

tests/py/runner.py

tests/py/run.py

tests/py/command.py

tests/py/validators.py

tests/py/connectors/docker/base.py

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 ee5ad61...6aa56bc. Read the comment docs.


rate-limiting !work/!sleep

[betatester10244] i'll file an issue'
[Sumairu 🦀❄] but the Sleep/Work thingy is still a bit too spammy. It'll either need to be limited to X messages per command invocation, the thread in which it was invoked, only being allowed for self-assigning, or just being cut (though that might be a bit much)
[betatester10244] blegh
[betatester10244] best would be to limit to say 10 messages
[Sumairu 🦀❄] that is arguably still a bit much
[betatester10244] five, whatever
[Sumairu 🦀❄] it's bikesheddable, yes
[betatester10244] same difficulty to implement
[betatester10244] but that requires effort™
[betatester10244] additionally
[betatester10244] my day has been SHIT
[Sumairu 🦀❄] I'm sorry to hear that
[Sumairu 🦀❄] hope it improves from here on out
[betatester10244] thanks
[betatester10244] and i have forgotten to bring home my charger
[betatester10244] so development is suspended in favour of battery health

welp the spammer's gone for now


Upcoming special SQL NULL handling in drift_postgres

Hello!
This is just to open a discussion on how would be the best way to support the upcoming SQL NULL values in the postgres package.
Particularly via the Dart select API and the customSelect method.
Originally the use case for json null was discovered when we were doing some polishing on the ElectricSQL Dart type mapping between Postgres and the drift schema. There were some issues with how the types were being mapped in your PR. Now the tests are run on a real Postgres instance so it's easier to see what's behaving differently.
Context: https://github.com/isoos/postgresql-dart/issues/322

When binding parameters, you can always write a custom type mapping to a TypedValue and drift won't mess with that, it's passed to the postgres package unchanged. That's probably what you would be doing for JSON/JSONB either way, right? So just setting the relevant flag to not turn that into an SQL null is sufficient.
The other direction is more complicated unfortunately, as we don't have access to the ResultRow in higher layers of drift, only the interpreted map. Do you need a way to distinguish the nulls in this direction as well?

Yes, I was able to do the inserts with TypedValue via drift.
For the rows reading we could actually use the CustomType API if that's a possible solution. But right now, nulls don't go through it. This would be the ideal solution as we already have control over how the values are mapped in/out for all the supported types.
I agree it is a niche case. We don't have an use case other than being able to work with Electric supported values transparently via drift on the backend, same as on the client, which supports the JSON null on SQLite by using a custom serialization/deserialization.


Release 6.2.2

Along with an actual publish to npm, will close https://github.com/gmusic-utils/ytmusic.js/issues/20

Published


css: change styling of SignUp button

currently, we haven't styled SignUp button in the  index page. please write necessary styles to make the button look good.

Target File: style.css
✨ Feel free to add your own changes !
💬 drop a comment if you like to take up this issue, so i can assign it to you.

Example:
...

/* Register Button */

.btn-register {
    background: var(--primary);
    border: none;
    padding: 10px 45px;
    border-radius: 2px;
    font-size: 22px;
    color: #fff;
    font-weight: 500;
}

I would like to take this up. Can I style it the way I want?

I would like to take this up. Can I style it the way I want?

sure ! go ahead

Completed. Take a look at PR #36 . Thanks!

fixed in #36


[Feature request] Generate AWS lambda zips using uv build

Generating python lambda zips is a cumbersome process. It would be great if uv build can have the ability to generate AWS Lambda zip files which can be used to create lambda function in AWS.
AWS Documentation Link: https://docs.aws.amazon.com/lambda/latest/dg/python-package.html#python-package-create-dependencies

Could you expand on how are you currently using uv to generate these?

My shell script does the following

Use uv to build wheel file
Extract the wheel file
Copy contents of the wheel into a directory
Copy project runtime dependencies into the same directory
Zip the directory
Upload the zip to AWS

Is there a reason you wouldn't be able to use --target like the AWS lambda guide says? I'm trying to understand if there's a compatibility gap with what pip enables you to do.

The 4th point of copying runtime dependencies is exactly a pip install --target. I guess "installing" would have been a better word than "copying".. will update the above

At the very least it'd be nice to include some documentation for this process.
I'm not sure how we'd expose this if we did. An alternative uv build output format?

What is tricky is including path dependencies https://github.com/sst/sst/pull/5132

@zanieb In my mind it was an alternative uv build output format

Hi @kishaningithub , I'm struggling with this issue as well. Can you share your shell script please?

@williamrjribeiro The script i am using is basically the same as the in the AWS documentation. Can you let know the issue you are facing?

here is something worked out for me @williamrjribeiro  , I didn't try to use pip, because that's what I am running away from.
#!/usr/bin/env bash

# Exit immediately if a command exits with a non-zero status
set -e

# Step 1: Clean up old builds
echo "Cleaning up old builds..."
rm -rf build dist lambda_package lambda_function.zip

# Step 2: Verify the virtual environment exists
if [ ! -d ".venv" ]; then
    echo "Error: Virtual environment '.venv' not found!"
    exit 1
fi

# Step 4: Build the wheel file using `uv`
echo "Building the wheel package..."
uv build --wheel

# Step 3: Use `uv run` to determine the Python version
echo "Detecting Python version..."
PYTHON_VERSION=$(echo "import sys; print(f'{sys.version_info.major}.{sys.version_info.minor}')"|uv run -)
if [ -z "$PYTHON_VERSION" ]; then
    echo "Error: Could not determine Python version!"
    exit 1
fi
echo "Detected Python version: $PYTHON_VERSION"

# Step 4: Locate site-packages directory
VENV_SITE_PACKAGES=".venv/lib/python$PYTHON_VERSION/site-packages"
if [ ! -d "$VENV_SITE_PACKAGES" ]; then
    echo "Error: Could not locate site-packages in the virtual environment at $VENV_SITE_PACKAGES!"
    exit 1
fi

# Step 5: Extract the wheel file
echo "Extracting the wheel file..."
WHEEL_FILE=$(ls dist/*.whl | head -n 1)  # Get the first wheel file
if [ -z "$WHEEL_FILE" ]; then
    echo "Error: No wheel file found in 'dist/' directory!"
    exit 1
fi
mkdir -p lambda_package
unzip -q "$WHEEL_FILE" -d lambda_package

# Step 6: Copy dependencies from the virtual environment
echo "Copying dependencies from virtual environment..."
cp -r "$VENV_SITE_PACKAGES/"* lambda_package/

# Step 7: Package the Lambda deployment
echo "Packaging Lambda deployment..."
cd lambda_package

# here using -u option helped me and it speed up the zip creation too
# Replace (update) an existing entry in the zip archive only if it has been
# modified more recently than the version already in the zip archive

zip -qr ../lambda_function.zip .
cd ..

echo "Lambda deployment package created successfully: lambda_function.zip"

# Step 8: Upload to AWS Lambda
LAMBDA_FUNCTION_NAME="delete_me"  # Replace with your Lambda function name
echo "Uploading to AWS Lambda: $LAMBDA_FUNCTION_NAME"
aws lambda update-function-code --function-name "$LAMBDA_FUNCTION_NAME" --zip-file fileb://lambda_function.zip

echo "Deployment complete!"

@toddlers Thank you for the script! 🙏
I'm using SST+Pulumi to deploy my little Python script to a lambda function. The lambda fails when it runs with error [ERROR] Runtime.ImportModuleError: Unable to import module 'main': No module named 'main' Traceback (most recent call last):
Here's my pyporject.toml:
[project]
name = "poc-events_python-consumer"
version = "0.0.0"

dependencies = [
    "sst",
    "pydantic>=2.10.2",
    "cloudevents[pydantic]",
]

requires-python = "~=3.12"

[tool.uv.pip]
no-strip-extras = true

[tool.uv.sources]
sst = { git = "https://github.com/sst/sst.git", subdirectory = "sdk/python", branch = "dev" }
cloudevents = { git = "https://github.com/cloudevents/sdk-python.git", branch = "main" }

[tool.setuptools]
py-modules = []

[project.scripts]
handler = "lambda:handler"

The script path is python-consumer/src/lambda/__init__.py which has the def handler function.
This is how the lambda function is created with Pulumi:
const pythonConsumer = new aws.lambda.Function("PocEventPythonConsumer", {
      role: lambdaRole.arn,
      runtime: "python3.12",
      handler: "lambda.handler",
      code: $asset("packages/python-consumer/lambda_package/"),
    });

Maybe I should just wait for https://github.com/sst/sst/pull/5132 to be merged and released.


Firewall, category dropdown list not visible via Chrome

No idea if it's a known bug, but with Chrome I can't see the dropdown list for selecting categories in rules tab. With Firefox it's perfectly displayed / useable.

it looks like it, I seem to be missing the selector as well on my in in chrome

@mimugmail my mistake, on my end it seems to be there (forgot to add some categories), which version do you use? I seem to have version 67.0.3396.87 on my end.

67.0.3396.99

@mimugmail does the JS console show an error on a page reload?

No error found, also cleared the cache and restarted Chrome, still not working.

@mimugmail I've just upgraded Chrome to match your version, but don't seem to have your issue. Is your issue consistent with stable and devel? (devel is slightly different, it seems we have the Add button there in the same corner)

it could also be a plugin in chrome altering the page in some way

I installed Chrome on a machine where there was only Firefox, with 18.7 beta it's working, 18.1.10 vanilla it's working, 18.1.10 with HAProxy no category. Really strange ..

really odd, my box has haproxy installed too it seems, but no issue. did you perhaps install os-cache ?

I'll close this now .. have to do some more testing with other machines.


Fixes linting

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
5 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.04%) to 49.463%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/dataconverter/readers/em_nion/concepts/swift_handle_nx_concepts.py
1
11.86%

pynxtools/nyaml2nxdl/nyaml2nxdl_forward_tools.py
1
79.42%

tests/dataconverter/test_writer.py
1
96.77%

pynxtools/nexus/nxdl_utils.py
2
74.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
5387

Relevant Lines:
10891

💛  - Coveralls


Eclipse doesn't start

Please provide a brief summary of the bug

Please provide steps to reproduce where possible
No response
Expected Results

Actual Results
If i open eclipse, i start and shutdown before i can see Dashboard
What Java Version are you using?
java version "1.8.0_341" Java(TM) SE Runtime Environment (build 1.8.0_341-b10) Java HotSpot(TM) 64-Bit Server VM (build 25.341-b10, mixed mode)
What is your operating system and platform?
Windows 10 64bit
How did you install Java?
No response
Did it work before?
it worked for 3 days and now the error comes every times

Did you test with other Java versions?
no

Relevant log output

hs_err_pid6932.log

java version "1.8.0_341" Java(TM) SE Runtime Environment (build 1.8.0_341-b10) Java HotSpot(TM) 64-Bit Server VM (build 25.341-b10, mixed mode)

This isn't a temurin build --^, fwiw.
Going by the hs_err file the actual version in use is JDK 17:
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (<IP_ADDRESS>+1) (build <IP_ADDRESS>+1)

Crash is in c2:
# Problematic frame:
# J 7638 c2 jdk.internal.jimage.ImageLocation.decompress(Ljava/nio/ByteBuffer;I)[J (116 bytes) @ 0x0000028e33d498ff [0x0000028e33d49620+0x00000000000002df]

i have installed jdk:
java version "<IP_ADDRESS>" 2022-08-18 LTS
Java(TM) SE Runtime Environment (build <IP_ADDRESS>+1-LTS-2)
Java HotSpot(TM) 64-Bit Server VM (build <IP_ADDRESS>+1-LTS-2, mixed mode, sharing)
no changes. eclipse crash after startup

It's an amd graphic driver error I had the same problem in intellij
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1.
solved by installing Adrenalin 22.5.1 Recommended (WHQL) (downgrade)


Decompose DepthToSpace operator.

This PR decomposes the ONNX DepthToSpace operator into  reshape+transpose+reshape as documented by https://github.com/onnx/onnx/blob/master/docs/Operators.md#DepthToSpace

Currently we lower DepthToSpace in src/Conversions/ONNXToKernel/Tensor/DepthToSpace.cpp into ONNXReshape -> ONNXTranspose -> ONNXReshape. There are 2 cases to consider, when all dimensions of the shape for ONNX.Reshape are known at compile time or when they aren't. In the former we generate a onnx.Constant to encode the shape, in the later we have to generate code to compute the new shape.
I think the current approach is reasonable, it allows reuse of the code we already have to lower onnx.Reshape and onnx.Transpose so that, should we have a bug ior need to optimize codegen for those operations, we can leverage the effort.  Also, the implementation of SpaceToDepth can leverage the same approach.


example train_object_detector.py throws Boost.Python.ArgumentError

I was playing around with the examples, when I stumpled over this error in train_object_detector.py:
Traceback (most recent call last):
  File "./train_object_detector.py", line 85, in <module>
    dlib.train_simple_object_detector(training_xml_path, "detector.svm", options)
Boost.Python.ArgumentError: Python argument types in
    dlib.dlib.train_simple_object_detector(str, str, simple_object_detector_training_options)
did not match C++ signature:
    train_simple_object_detector(boost::python::list images, boost::python::list boxes, dlib::simple_object_detector_training_options options)
    train_simple_object_detector(std::string dataset_filename, std::string detector_output_filename, dlib::simple_object_detector_training_options options)

It should be working with the second implementation of the function. I don't even know, what to debug here. It looks all right.
I am running boost 1.62.0 on Gentoo Linux.

I now tried to run the example in a ubuntu docker and it runs fine. Looks like the new version of boost is causing some problems.


Add beta with Pydantic 2 compatibility

2 is bigger than 1, numbers go up

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


Add one more limits to AFDx

@jessie-jyy : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Question

Is it possible to print two different route at the same time?
if so how?
Thank you

Not at this time, sorry!
With two routes, it would generally not be possible to find a sequence of rectangles that covers both routes.

for me the second route is always in the same rectangle as the first route, it is a variant

I see. It would certainly be possible to add this functionality, but I think it is outside the domain of this library, which only attempts to print the map along one route well.
Additional details in the map, such as roadside markers and alternative routes, should really be added by whichever larger client application that uses this library.
Anyway, it is not something I will add in the nearest future. Sorry!


Upgrade F* to use Z3 4.13.3

This PR explicitly sets --z3version 4.13.3 for all F* invocations in this repo.
Rather than changing FStarC.Options to flip the default Z3 version, I preferred to set this in all our makefiles, scripts, config files etc., so that we don't break other projects. We can consider flipping the default later.
I also adjusted rlimits and proofs in a couple of places so that they work with 4.13.3
The main difficult one with X64.Vale.Decls, which is fragile: I wrestled with this for a while, but it works now with a large rlimit and a few retries. We have a thread investigating this further with Nikolaj Bjorner, but I don't think that should block us here.
Fixes #3476.  Fixes #2828.  Fixes #2332.  Fixes #2431.
See also #2974 and #2995.

I should add that this is just a small delta on top of a heroic effort by @mtzguido over several months on finding and fixing various proof regressions in both F* and Z3. Thanks @mtzguido!

I can confirm that F* now successfully builds on aarch64!


nixos/venus: drop module since quite old and gets no updates

Closes #111440

Motivation for this change
Venus has no maintainer, uses python 2.7 and as far as I can tell gets no updates from its developers. So I would suggest to just drop it.
Things done

[ ] 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"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/111440 can be closed after

Do we want to add an alias?

Rather than an alias, it would go inside nixos/modules/rename.nix and be a mkRemovedOptionModule.

@cole-h added the mkRemovedOption

@cole-h Done, but in a different order. I figured first removing the module and then removing the package does not break things, since the module depends on the package.
Happy to change the order though if I missed something


Replace SQLite with Postgres

This will close #48

Railway automatically exposes an ENV variable DATABASE_URL into the application container. Having support for that would be useful.


Update ubuntu base + refresh all packages

Signed-off-by: Chris Evich<EMAIL_ADDRESS>

@cevich can we get fresher images? :-)

@cevich can we get fresher images? :-)

Yep, building them now.  Assuming it completes successfully, the new image ID will be automatically posted in a PR comment.

looks like there was a failure :/

Oof, I was afraid I might hit that.  Fix is easy-ish though...

...k, that should fix it.

Just a boring rebase, so I manually canceled the image build.