Application is stuck into an infinite loop

I am using bevy 0.9.1 and when I realized I was using the Intel Integrated GPU instead of my NVIDIA GPU, I updated the NVIDIA driver to "nvidia-driver-525" and now when I run my game it is stuck into an infinite loop just after opening the window (but not drawing anything yet).
When using the lshw command, it seems to consider that both GPUs are used:
$ lshw -C display
WARNING: you should run this program as super-user.
  *-display
       description: VGA compatible controller
       product: TU117GLM [Quadro T1000 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:16 memory:ad000000-adffffff memory:80000000-8fffffff memory:90000000-91ffffff ioport:3000(size=128) memory:ae080000-ae0fffff
  *-display
       description: VGA compatible controller
       product: CometLake-H GT2 [UHD Graphics]
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 05
       width: 64 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
       resources: iomemory:600-5ff iomemory:400-3ff irq:167 memory:6040000000-6040ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

Maybe this is where the bug is coming from? I precise: the game was working perfectly well before updating the driver.

What happens if you manually specify the wgpu backend by using the WpuSettings resource?

Seems like it's a wgpu bug since with this, it doesn't even open a window:
let mut app = App::new();

let options = app
    .world
    .get_resource::<bevy::render::settings::WgpuSettings>()
    .cloned()
    .unwrap_or_default();

let instance = wgpu::Instance::new(options.backends.unwrap());
let request_adapter_options = wgpu::RequestAdapterOptions {
    power_preference: options.power_preference,
    ..Default::default()
};
futures_lite::future::block_on(bevy::render::renderer::initialize_renderer(&instance, &options, &request_adapter_options));

// all the calls to `app` then `app.run()`.

Updated the Instance::new call to:
let instance = wgpu::Instance::new(bevy::render::settings::Backends::VULKAN);

Still stuck.

Could you try running wgpu examples? https://github.com/gfx-rs/wgpu/wiki/Running-the-examples

$ cargo run --example cube

Black window and stuck.

If it can help, here is the backtrace when stuck I got from gdb:
0x00007ffff7c6e6eb in __libc_open64 (file=0x7fffffff58a0 "/dev/nvidia0", oflag=2) at ../sysdeps/unix/sysv/linux/open64.c:41
41	../sysdeps/unix/sysv/linux/open64.c: No such file or directory.
(gdb) bt
#0  0x00007ffff7c6e6eb in __libc_open64 (file=0x7fffffff58a0 "/dev/nvidia0", oflag=2) at ../sysdeps/unix/sysv/linux/open64.c:41
#1  0x00007fffed440b2c in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#2  0x00007fffed441c53 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#3  0x00007fffed44ad33 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#4  0x00007fffed44bc3a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#5  0x00007fffed44a7d0 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#6  0x00007fffed44a830 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glsi.so.525.60.11
#7  0x00007fffed8ec47d in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#8  0x00007fffed90cd93 in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#9  0x00007fffed90dda2 in vk_icdNegotiateLoaderICDInterfaceVersion () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#10 0x00007ffff72d1eda in ?? () from /lib/x86_64-linux-gnu/libvulkan.so.1
#11 0x00007ffff72d9360 in ?? () from /lib/x86_64-linux-gnu/libvulkan.so.1
#12 0x00007ffff72e0561 in vkEnumerateInstanceExtensionProperties () from /lib/x86_64-linux-gnu/libvulkan.so.1
#13 0x0000555555d8a308 in ash::entry::{impl#0}::enumerate_instance_extension_properties::{closure#0} (count=0x7fffffff7274, data=0x0)
    at /home/imperio/.cargo/registry/src/github.com-1ecc6299db9ec823/ash-0.37.1+1.3.235/src/entry.rs:257
#14 0x0000555555d95911 in ash::prelude::read_into_uninitialized_vector<u32, ash::vk::definitions::ExtensionProperties, ash::entry::{impl#0}::enumerate_instance_extension_properties::{closure_env#0}> (f=...)
    at /home/imperio/.cargo/registry/src/github.com-1ecc6299db9ec823/ash-0.37.1+1.3.235/src/prelude.rs:46
#15 0x0000555555ccb50f in ash::entry::Entry::enumerate_instance_extension_properties (self=0x7fffffff7700, layer_name=...)
    at /home/imperio/.cargo/registry/src/github.com-1ecc6299db9ec823/ash-0.37.1+1.3.235/src/entry.rs:256
#16 0x0000555555c8218c in wgpu_hal::vulkan::Instance::required_extensions (entry=0x7fffffff7700, flags=...) at wgpu-hal/src/vulkan/instance.rs:158
#17 0x0000555555c8454d in wgpu_hal::vulkan::instance::{impl#4}::init (desc=0x7fffffff8348) at wgpu-hal/src/vulkan/instance.rs:522
#18 0x0000555555b7a594 in wgpu_core::instance::{impl#0}::new::init<wgpu_hal::vulkan::Api> (mask=...) at wgpu-core/src/instance.rs:82
#19 0x0000555555bae7cf in wgpu_core::instance::Instance::new (name=..., backends=...) at wgpu-core/src/instance.rs:91
#20 0x0000555555a01825 in wgpu_core::hub::Global<wgpu_core::hub::IdentityManagerFactory>::new<wgpu_core::hub::IdentityManagerFactory> (name=..., factory=..., backends=...) at wgpu-core/src/hub.rs:1114
#21 0x00005555559801c1 in wgpu::backend::direct::{impl#11}::init (backends=...) at wgpu/src/backend/direct.rs:941
#22 0x000055555592505b in wgpu::Instance::new (backends=...) at wgpu/src/lib.rs:1739
#23 0x00005555556f35c4 in cube::framework::setup::{async_fn#0}<cube::Example> () at wgpu/examples/cube/../framework.rs:162
#24 0x00005555556fb625 in pollster::block_on<cube::framework::setup::{async_fn_env#0}<cube::Example>> (fut=...) at /home/imperio/.cargo/registry/src/github.com-1ecc6299db9ec823/pollster-0.2.5/src/lib.rs:125
#25 0x00005555556f5ada in cube::framework::run<cube::Example> (title=...) at wgpu/examples/cube/../framework.rs:436
#26 0x0000555555728262 in cube::main () at wgpu/examples/cube/main.rs:406

If it's also stuck with just wgpu, you should open the issue in their repo, not sure we can do much on Bevy side

I opened https://github.com/gfx-rs/wgpu/issues/3297. If you don't mind, let's keep this one open so I'll send a PR to update the minimum wgpu version in the Cargo.toml files so this issue won't appear anymore.

Problem was coming from my driver and not from bevy or wgpu. Closing then.


Fix some more warnings

Remove more uses of unsafeBitCast()

NSXMLParser.swift: Remove all calls to strlen() except for a
single use in UTF8String().

Replace _colonSeparatedStringFromPrefixAndSuffix() with direct
string construction.

Replace a call to strncpy() with String._fromCodeUnitSequence()
to simplify extracting a non-null terminated string from a
buffer.

swift4: DispatchData(bytes:) is deprecated

Use init(bytes: UnsafeRawBufferPointer) instead.

Tested on Linux and macOS

In general I'm somewhat concerned about the performance impact of these changes. I haven't profiled the Swift implementation much, but the ObjC NSXMLParser's performance is heavily dependent on avoiding C string -> NSString conversions (e.g. UTF8STRING calls) whenever possible.
It's possible Swift String operations are sufficiently different that that's not a concern here, but it would be good to check.

@Catfish-Man This is a cleanup and shouldnt introduce any extra calls. UTF8STRING() and the removed _colonSeparatedStringFromPrefixAndSuffix() are both usingString._fromCodeUnitSequence() so the underlying method of string creation hasnt changed however this change does eliminate an unnecessary extra call to UTF8STRING(ns) and also String._fromCodeUnitSequence() being called on a fixed string ("xmlns").
String._fromCodeUnitSequence() does appear to copy the string but Im not sure how that copy can be eliminated if the strings are required to exist after the initial XML buffer data has been freed.

@swift-ci please test

@parkera Do these changes look ok?

LGTM thanks


Error writing to file

Can you try using the test branch?
And can you check if this is the same issue: https://stackoverflow.com/questions/70148547/wsl2-pytorch-runtimeerror-no-cuda-gpus-are-available-with-rtx3080


[ENTVTX-110] Don't hardcode the route name in test

Please review
@Ladicek
@spisiakm

Thanks @akoniar .


Allow the GCS file trigger to not download the file to internal storage

Feature description
Problem
GCS is an interesting edge case because the task LoadFromGcs doesn't require the trigger object to be downloaded to internal storage but only the file URL on GCS is needed
As @Ben8t mentioned, this would be useful for use cases where data is loaded from GCS to BigQuery based on GCS file detection event
Possible solutions

action: NONE (or sth like "do nothing") and if set to that value, not downloading the file to internal storage
expose the moved file to blobs property (atm we only get the original file information)

Beware that this option on a Pull strategy will need to store the previous state of the file in order to avoid an infinite loop.
I workaround by doing a Python script comparing timestamp and storing the last state of file in a BigQuery table

To process 1 object per 1 event, you can also set maxKeys: 1 on the trigger :) super helpful property!
Then you can simply move the file somewhere else when you are done, as here:
id: ingestToDataLakeEventDriven
namespace: blueprint

variables:
  sourcePrefix: inbox
  destinationPrefix: archive
  database: default
  bucket: kestraio

tasks:
  - id: wdir
    type: io.kestra.core.tasks.flows.WorkingDirectory
    tasks:
      - id: git
        type: io.kestra.plugin.git.Clone
        url: https://github.com/kestra-io/scripts

      - id: etl
        type: io.kestra.plugin.scripts.python.Commands
        warningOnStdErr: false
        docker:
          image: ghcr.io/kestra-io/aws:latest
        env:
          AWS_ACCESS_KEY_ID: "{{ secret('AWS_ACCESS_KEY_ID') }}"
          AWS_SECRET_ACCESS_KEY: "{{ secret('AWS_SECRET_ACCESS_KEY') }}"
          AWS_DEFAULT_REGION: "{{ secret('AWS_DEFAULT_REGION') }}"
        commands:
          - python etl/aws_iceberg_fruit.py {{vars.destinationPrefix}}/{{ trigger.objects | jq('.[].key') | first }}

  - id: mergeQuery
    type: io.kestra.plugin.aws.athena.Query
    accessKeyId: "{{ secret('AWS_ACCESS_KEY_ID') }}"
    secretKeyId: "{{ secret('AWS_SECRET_ACCESS_KEY') }}"
    region: "{{ secret('AWS_DEFAULT_REGION') }}"
    database: "{{vars.database}}"
    outputLocation: "s3://{{vars.bucket}}/query_results/"
    query: |
      MERGE INTO fruits f USING raw_fruits r
          ON f.fruit = r.fruit
          WHEN MATCHED
              THEN UPDATE
                  SET id = r.id, berry = r.berry, update_timestamp = current_timestamp
          WHEN NOT MATCHED
              THEN INSERT (id, fruit, berry, update_timestamp)
                    VALUES(r.id, r.fruit, r.berry, current_timestamp);

  - id: optimize
    type: io.kestra.plugin.aws.athena.Query
    accessKeyId: "{{ secret('AWS_ACCESS_KEY_ID') }}"
    secretKeyId: "{{ secret('AWS_SECRET_ACCESS_KEY') }}"
    region: "{{ secret('AWS_DEFAULT_REGION') }}"
    database: "{{vars.database}}"
    outputLocation: "s3://{{vars.bucket}}/query_results/"
    query: |
      OPTIMIZE fruits REWRITE DATA USING BIN_PACK;

triggers:
  - id: waitForNewS3objects
    type: io.kestra.plugin.aws.s3.Trigger
    bucket: kestraio
    interval: PT1S
    maxKeys: 1
    filter: FILES
    action: MOVE
    prefix: "{{vars.sourcePrefix}}"  # e.g. s3://kestraio/inbox/fruit_1.csv
    moveTo:
      key: "{{vars.destinationPrefix}}/{{vars.sourcePrefix}}" # e.g. s3://kestraio/archive/inbox/fruit_1.csv
    region: "{{ secret('AWS_DEFAULT_REGION') }}"
    accessKeyId: "{{ secret('AWS_ACCESS_KEY_ID') }}"
    secretKeyId: "{{ secret('AWS_SECRET_ACCESS_KEY') }}"

done https://github.com/kestra-io/plugin-gcp/pull/313


Assert that the file isnt open is lfs_file_opencfg

Closes #429
Also fixed a magic number in opencfg

I think I'd prefer the operation failed by returning an error, rather than doing an assert

I think I'd prefer the operation failed by returning an error, rather than doing an assert

I think that checking every time for something that is really a user error is not needed, but I will accept this if more people prefer checks. If your program hangs in littlefs I expect that you will compile littlefs in debug and then you will see the problem.
In a different matter, I really need to find a way to check if the struct was initialized, because right now I access uninitialized memory :(

I definitely prefer the return code. I think asserts are heavily overused in lfs. there are many cases where my application would benefit from handling return codes rather than the asserting.

Guys, I am not sure why you should return error on such cases. Iterating over all open files in each open call seems costly, so I think we can stick to an assert. You can open the same file twice, just not with the same struct...

You can open the same file twice, just not with the same struct...

Oh in our testing, we were unable to open a file twice with different structures.
we

opened a file with hdl1
wrote data using hdl1
synced hdl1 (but not close)
opened same file with hdl2
read hd2 (this always reported zero bytes)

Do you expect, in this scenario, the hdl2 read to return the bytes written by hdl1 ? Maybe our test case was buggy, but we concluded that we could not read a file that was already open. If this is not the case, then thats great.

Also, isnt it still checking every open file in the assert? How is asserting any different than returning in terms on complexity ?

I will check the test case you mentioned, thanks!
I currently only check that the struct is not reused, in order to test that the file is not already opened, I will need to add a new assert.
And assert is better because it is not complied in, unless on debug

Hi @NoahGorny, thanks for creating a PR! Sorry to leave this hanging for so long. This is a good addition.
I wonder if it would also be good to replace LFS_F_OPENED (https://github.com/littlefs-project/littlefs/pull/237) so we have the same check for open/close files that doesn't get tripped up by uninitialized memory. Thoughts?

My opinion is this check should assert. For a code size reason, not a usability reason. Asserts can be removed during compilation, return codes can not. And for microcontroller-scale programs, you really don't want to pay for code that should never run.
Also the current behavior for these types of user checks is to assert, if we want to change this behavior it should be done via a different issue or PR.

I wonder if it would also be good to replace LFS_F_OPENED (#237) so we have the same check for open/close files that doesn't get tripped up by uninitialized memory. Thoughts?

If LFS_F_OPENED (#237) is replaced, it might also be a good addition to add the isOpened API mentioned in #442. But then based on lfs_is_node_not_in_list instead of LFS_F_OPENED

Hi @NoahGorny, thanks for creating a PR! Sorry to leave this hanging for so long. This is a good addition.
I wonder if it would also be good to replace LFS_F_OPENED (#237) so we have the same check for open/close files that doesn't get tripped up by uninitialized memory. Thoughts?

I agree, and added commits that deprecate LFS_F_OPENED. It required me to sometimes add files to the mlist when we did not do so before, so you might wanna take a look at 0250015 and 0ca3012 to tell me whether my solution is okay or not.
In any case, I did not add support for asserting of file that was opened twice using a different file struct, so we might want to take a look at it. Reusing an existing struct will now raise assert errors :smile:
By the way, are there any ways to "catch' asserts in the tests? I want to deliberately see the asserts trigger in the tests.
Thanks alot for your feedback btw @geky

I wonder if it would also be good to replace LFS_F_OPENED (#237) so we have the same check for open/close files that doesn't get tripped up by uninitialized memory. Thoughts?

If LFS_F_OPENED (#237) is replaced, it might also be a good addition to add the isOpened API mentioned in #442. But then based on lfs_is_node_not_in_list instead of LFS_F_OPENED

I think @geky should voice his opinion here. I think that currently with the assert not fully catching all cases (opened with different struct) it should not be public API yet... maybe after we catch/handle all such cases

You can open the same file twice, just not with the same struct...

Oh in our testing, we were unable to open and read a file twice with different structures.
we
1. opened a file with hdl1

2. wrote data using hdl1

3. synced hdl1 (but not close)

4. opened same file with hdl2

5. read hd2 (this always reported zero bytes)

Do you expect, in this scenario, the hdl2 read to return the bytes written by hdl1 ? Maybe our test case was buggy, but we concluded that we could not read a file that was already open. If this is not the case, then thats great.

@judgeh It indeed fails with my tests, I created a test (on a separate PR) that fails on this (ad995ceb9bf72f5c87690e2c63f70ed585fabb29)
I am not sure what is the correct approach to this, but I think @geky can have some insights :smile:

Oh in our testing, we were unable to open and read a file twice with different structures.

@judgeh It indeed fails with my tests, I created a test (on a separate PR) that fails on this (ad995ce)

Ah, this looks like the same issue being discussed in https://github.com/littlefs-project/littlefs/issues/483. Thumbing up https://github.com/littlefs-project/littlefs/issues/483 would help know who's ran into this. Also thanks for the test case!
TLDR: Currently, littlefs is transactional in the sense that each open file handle gets its own snapshot. Each file handle can be read/written independently (and independently from disk). Something that came up in https://github.com/littlefs-project/littlefs/issues/483, we could go through all open files and throw out other changes on sync/close, it would just take more code size. More info in https://github.com/littlefs-project/littlefs/issues/483.

it might also be a good addition to add the isOpened API mentioned in #442

I'm still not convinced on https://github.com/littlefs-project/littlefs/issues/442. The behavior of an lfs_file_isopened could be accomplished with an external flag without requiring an additional API into the filesystem. It could also be added later if there is interest.

By the way, are there any ways to "catch' asserts in the tests?

Almost missed this, unfortunately no, the test script currently only treats asserts as failures. The test script should also be documented better...

I didn't notice until after merging that this reverted the LFS_F_OPENED flag, so I went ahead and re-added that change to #495. But can re-revert if needed.
I think I ran into some of the issues you did with the change, but one thing that helped was the new separate API-layer, I could move the check there and it solved some of complex internal situations, as well as reduced the calls to lfs_mlist_isopen to the API layer.


Listview demo project fails to show properly on ios

When I ran the listview project as it is, I encountered issues regarding rendering positions of the listview elements on the ios simulator.

What can be a solution to this?
Thanks!

This is a .NET MAUI product issue and not so much a sample issue. Also I think this has been resolved in recent versions so please try that!


Gurobipy question

Is a license to Gurobi required? Or will ConDoR be able to run within the restrictions of the free "limited license"?
If a license is required, is it feasible to make ConDoR work without the Gurobi dependency?
Thanks!

Unfortunately, at the moment the gurobi license is required to use ConDoR. The limited license will only allow you to solve small instances.
I am working on an extension that will not require such licenses which will be out in the next few months.


GSE161621 - Blum2021MouseSpinal

Project short name:
Blum2021MouseSpinal
Primary Wrangler:
Ida
Secondary Wrangler:
Ami

Associated files

Google Drive: folder

Published study links

Paper: Single-cell transcriptomic analysis of the adult mouse spinal cord reveals molecular diversity of autonomic and skeletal motor neurons

Accessioned data: GSE161621

Ingest

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[x] Upload sheet to validate metadata
[x] Check linking using ingest graph validator
[x] Transfer raw files to ingest to validate data files
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

Donors/specimens
The cell suspension are multiplexed and there is no information on how many donors were used for each replicate.

Four to eight mice in five independent experiments were euthanized with CO2 and decapitated caudal to the brain stem.

Based on this I modelled the experiment with 4 donors for each replicate.
Library preparation
The paper says 10x 3' v3 was used, but the R1 length for replicate 4 matches v2. I've added a 10x 3' v2 library for replicate 4

there isn't a good term to represent the non-cholinergic neurons. I'll use neurons instead
I agree the cell count looks very weird but I think the total cell count published is after QC, while the cell count for the cell matrices are raw, pre QC counts. A lot of cells must have been discarded!

checked in the browser


Depreciated function name 'binom_test' of scipy.

Describe the bug
Depreciated function name 'binom_test' of scipy being called while running predict method of TensorFlowV2RandomizedSmoothing object. The function scipy.stats.binom_test() was removed from SciPy 1.12.0.
To Reproduce

Create a TensorFlowV2Classifier classifier

classifier = TensorFlowV2Classifier(
    model=model,
    nb_classes=NUM_LABELS,
    input_shape=INPUT_SHAPE,
    loss_object=tf.keras.losses.CategoricalCrossentropy(from_logits=False),
    optimizer=tf.keras.optimizers.Adam(learning_rate=LR),
    clip_values=(0, 1)
)

Create a TensorFlowV2RandomizedSmoothing object using the classifier object

classifier_rs_025 = TensorFlowV2RandomizedSmoothing(model = classifier.model,
    nb_classes=NUM_LABELS,
    input_shape=INPUT_SHAPE,
    loss_object=tf.keras.losses.CategoricalCrossentropy(from_logits=False),
    optimizer=tf.keras.optimizers.Adam(learning_rate=LR),
    clip_values=(0, 1),
    sample_size=100,
    scale=0.25
)

Call the predict method on a subset of images
classifier_rs_025.predict(imgs_sub_test)

See error

Expected behavior
Return predictions for the input images
Screenshots

System information (please complete the following information):

Used Kaggle notebook

Note:
Proposed Solution:
Change The function name from binom_test to binomtest and handle the way the inputs and ouputs are returned
This solution worked out for me and i would like to contribute

Hi @Ashuradhipathi Thank you very much for raising this issue and working on a solution!


[Question] Is it possible to use McLightning in Hotspot mode?

Is it possible to use McLightning in Hotspot mode without Wifi connection to a router or smartphone hotspot?

Currently wont work, as it downloads a few things from the internet to show you the web-interface.

No workaround or planed as a future feature?


Training crashes after 50 epochs

My training runs always crash after exactly 50 epochs.  Looking at the log, there are many repetitions of this error:
Exception in thread Thread-104 (_pin_memory_loop):
Traceback (most recent call last):
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/threading.py", line 1045, in _bootstrap_inner
    self.run()
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/threading.py", line 982, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/utils/data/_utils/pin_memory.py", line 54, in _pin_memory_loop
    do_one_step()
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/utils/data/_utils/pin_memory.py", line 31, in do_one_step
    r = in_queue.get(timeout=MP_STATUS_CHECK_INTERVAL)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/multiprocessing/queues.py", line 122, in get
    return _ForkingPickler.loads(res)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/multiprocessing/reductions.py", line 355, in rebuild_storage_fd
    fd = df.detach()
         ^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/multiprocessing/resource_sharer.py", line 58, in detach
    return reduction.recv_handle(conn)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/multiprocessing/reduction.py", line 189, in recv_handle
    return recvfds(s, 1)[0]
           ^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/multiprocessing/reduction.py", line 164, in recvfds
    raise RuntimeError('received %d items of ancdata' %
RuntimeError: received 0 items of ancdata

and then it finally exits with this error:
  File "/home/peastman/miniconda3/envs/torchmd-net2/bin/torchmd-train", line 33, in <module>
    sys.exit(load_entry_point('torchmd-net', 'console_scripts', 'torchmd-train')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/workspace/torchmd-net/torchmdnet/scripts/train.py", line 220, in main
    trainer.fit(model, data, ckpt_path=None if args.reset_trainer else args.load_model)
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/trainer/trainer.py", line 544, in fit
    call._call_and_handle_interrupt(
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/trainer/call.py", line 43, in _call_and_handle_interrupt
    return trainer.strategy.launcher.launch(trainer_fn, *args, trainer=trainer, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/strategies/launchers/subprocess_script.py", line 102, in launch
    return function(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/trainer/trainer.py", line 580, in _fit_impl
    self._run(model, ckpt_path=ckpt_path)
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/trainer/trainer.py", line 989, in _run
    results = self._run_stage()
              ^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/trainer/trainer.py", line 1035, in _run_stage
    self.fit_loop.run()
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/fit_loop.py", line 202, in run
    self.advance()
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/fit_loop.py", line 359, in advance
    self.epoch_loop.run(self._data_fetcher)
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/training_epoch_loop.py", line 136, in run
    self.advance(data_fetcher)
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/training_epoch_loop.py", line 202, in advance
    batch, _, __ = next(data_fetcher)
                   ^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/fetchers.py", line 127, in __next__
    batch = super().__next__()
            ^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/loops/fetchers.py", line 56, in __next__
    batch = next(self.iterator)
            ^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/utilities/combined_loader.py", line 326, in __next__
    out = next(self._iterator)
          ^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/lightning/pytorch/utilities/combined_loader.py", line 74, in __next__
    out[i] = next(self.iterators[i])
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/utils/data/dataloader.py", line 630, in __next__
    data = self._next_data()
           ^^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/utils/data/dataloader.py", line 1328, in _next_data
    idx, data = self._get_data()
                ^^^^^^^^^^^^^^^^
  File "/home/peastman/miniconda3/envs/torchmd-net2/lib/python3.11/site-packages/torch/utils/data/dataloader.py", line 1289, in _get_data
    raise RuntimeError('Pin memory thread exited unexpectedly')
RuntimeError: Pin memory thread exited unexpectedly
[E ProcessGroupNCCL.cpp:475] [Rank 0] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=1127667, OpType=ALLREDUCE, NumelIn=288321, NumelOut=288321, Timeout(ms)=1800000) ran for 1800800 milliseconds before timing out.

Any idea what could be causing it?

Some users started seeing similar behavior to this, so I added this workaround to the README:

Some CUDA systems might hang during a multi-GPU parallel training. Try export NCCL_P2P_DISABLE=1, which disables direct peer to peer GPU communication.

Could it be the root of your issue too? I am assuming this i a multigpu training.
I do not remember the error being as consistent as you say (always 50 steps), so it might be unrelated.
OTOH the error suggests a relation to pinned memory, which makes me think of this:
https://github.com/torchmd/torchmd-net/blob/166b7db8661696f01c4adeb0cb02313c236061a2/torchmdnet/data.py#L132-L139
It would be great if you could try persistent_workers=False and pin_memory=False (separately) and report back.

Thanks!  Yes, this is with multiple GPUs.  I just started a run with persistent_workers=False.  I'll let you know what happens.

Crossing my fingers, but I think persistent_workers=False fixed it.  My latest training run is up to 70 epochs without crashing.


Nullable<T> built-in type alias

Search Terms

nullable type alias
optional type alias
nullable built-in type
optional built-in type
Suggestion

I'd like this added to the list of global built-in types, as an inverse of NonNullable<T>:
type Nullable<T> = T | null | undefined;

Use Cases

Sometimes, when I'm coding at the application level, I want a type that can be either null, undefined, or a value, and I don't want to have to pick one.
In library definitions, it's quite common for an API to accept both null and undefined as equivalent.
It would also make for more easily understood errors and autocomplete, as Nullable<{some: "really", complex: "object", type: true} | number> would be a lot faster and easier to read than {some: "really", complex: "object", type: true} | number | null | undefined.

Examples

Just to name a couple right off:

This part in React's type definitions could be simplified to Validator<null | undefined extends T[K] ? Nullable<T[K]> : T[K]>
Lodash's _.chunk definitions could just use chunk<T>(array: Nullable<List<T>>, size: number): T[][]. (That file is full of similar types of the form `T | null | undefined.)
There are over 400 results in searching the DTS repo alone for "null | undefined" and "undefined | null". (Some of the results are of unrelated things, but at least 80% of them are of a type like this.)

Chances are, if you've done significant TS development in general applications or if you've done significant type definitions work, you've probably run into something where this could've helped.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code Probably, but not 100% sure.
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Duplicate of #39522. Search terms: Nullable (remember to check closed issues)

@MartinJohns I did, it just failed me this time around. 😕


vscode terminal rendering wrongly !


[HUDI-7576] Improve efficiency of getRelativePartitionPath, reduce computation of partitionPath in AbstractTableFileSystemView

Change Logs

Improve the efficiency of getRelativePartitionPath by reducing the number of operations on the path object that are required to get the final result
Reduce the number of times a partitionPath is computed by supplying a partition path argument where possible in the AbstractFileSystemView

Impact
Reduces overhead of building FSViews with large numbers of files
Risk level (write none, low medium or high below)
None
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@the-other-tim-brown Can you fix the Azure CI failure?

@danny0405 error is:
TestUpsertPartitioner.testUpsertPartitionerWithSmallFileHandlingPickingMultipleCandidates:470 expected: <[BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-1, partitionPath=2016/03/15}, BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-2, partitionPath=2016/03/15}, BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-3, partitionPath=2016/03/15}]> but was: <[BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-3, partitionPath=2016/03/15}, BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-2, partitionPath=2016/03/15}, BucketInfo {bucketType=UPDATE, fileIdPrefix=fg-1, partitionPath=2016/03/15}]>

I'll put up a separate minor pr to make the ordering deterministic for small file handling

@danny0405 https://github.com/apache/hudi/pull/11008

@danny0405 can you take another look when you get a chance? I have updated a few spots in the code


[ci] Roll pinned stable toolchain

I'm going to avoid merging this for now to give https://github.com/google/zerocopy/pull/469 a chance to put up its own roll PR.

Here's the PR generated by #469: https://github.com/google/zerocopy/pull/471

Closing in favor of https://github.com/google/zerocopy/pull/471.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3089

Questions ?
Please refer to the Backport tool documentation


"isUserInteraction" always is "false"

Environment

Mapbox (GL) implementation: v10
Mapbox (GL) version: 10.7.0
@rnmapbox/maps Version #main
Platform: iOS
React Native Version 0.69.4
Platform OS: iOS 15
Device: iPhone X
Emulator/ Simulator: yes
Dev OS: OSX 12.5

Standalone component to reproduce
import React from 'react';
import {
  MapView,
  Camera,
} from '@rnmapbox/maps';

const coordinate = [30.319378097536216, 59.879647222152855];

const BugReport = () => {
  return (
    <MapView
      style={{ flex: 1 }}
      onRegionDidChange={region => {
        console.log(region.properties.isUserInteraction);
      }}
    >
      <Camera
        defaultSettings={{
          centerCoordinate: coordinate,
          zoomLevel: 16,
        }}
      />
    </MapView>
  );
};

Observed behavior and steps to reproduce
Move camera by any kind of gesture and property isUserInteraction is false.
Expected behavior
isUserIneraction should be true

Should be fixed by #2225


Produce warnings when branches cross page boundaries

Preferably preserving the location in the source as well.

done f028270bd8e8f0c15bdcc92c071b0b0afdbd6836


Multiple paginators

Can you use multiple paginators in the filter.
Cloning the paginator with jQuery did not work how hoped it would be working. When you change the current page with the first original paginator, the second one dit not update itself. But the data-page event changer is working correctly on the second paginator.

On Tue, Mar 17, 2020 at 11:56 Sebastiaan Kloos<EMAIL_ADDRESS>wrote:

Closed #153 https://github.com/EloquentStudio/filter.js/issues/153.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EloquentStudio/filter.js/issues/153#event-3138648115,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK2LSQGVSDYFDSUMFNNWSLRH7BUHANCNFSM4DG3FY4Q
.

--
Les Schmidt
Simplicity, Clarity, Focus
Founder & Executive Director
BRIIA https://briia.io/
WE ACCELERATE INNOVATION
Why the Tri-Valley? See this
http://www.bayareaeconomy.org/report/tri-valley-rising-2018/!
LinkedIn BRIIA https://www.linkedin.com/company/briia.io/ | Twitter BRIIA
https://twitter.com/briia_io | Medium https://medium.com/@BRIIA_IO
| LinkedIn
Les https://www.linkedin.com/in/lesschmidt | +1<PHONE_NUMBER>


Occurrence signal is updating LinkedEvent Event languages.

A pull request https://github.com/City-of-Helsinki/palvelutarjotin-admin/pull/156 has changes related to this pull request. With these PRs the goal is to remove language selection from provider UI's event form. The event form mutates an event in LinkedEvent. The state would now be maintained and automatically synced to LE by a signal receiver that listens changes on occurrences' languages.
PT-854  Added a signal  receiver for Occurrence which is called post_save and post_delete. It should sync an event occurrences languages to an event in LinkedEvents API.
PT-857 A migration script that adds Arabic, Russia and Chinese to Languages. Occurrence schema is changed to fetch languages from Language table instead LanguageEnum used by other implementations. Languages can now be queried also.
Fixed tests after language changes.

During my tests, the languages were always synced properly to LE, but there is a minor downside in this approach. Removing and adding languages to occurrences have a different signal, so if some languages are removed and changed to new ones, 2 REST requests will be made to LE. If an language that is linked to a multiple occurrences is removed from one of them, no call to LE is made, since the state should not change. However, a call is made if a language that already exists in some occurrences is added to another. Signals just didn't give enough information so I could have avoided these.

With this solution the event selection from event form can be removed, but there is a downside in using those signals in API. Another approach would be to keep the language selection in event form, but to filter languages in occurrences language selection by a selection made to an event. This is easier for API, but worse in UX sense.

Thanks! Let's wait for UI pull request to be approved.

Because of changes in language query, we actually need to change teachers UI queries also!


WriteCharacteristics doesn't work through ESP but is working through noble.

Hi All,
I am trying to work on a BLE lock which is currently being operated through a mobile app using the  react-native ble plx.
I was trying to make it work through the ESP32 so that it can be controlled remotely. I have prepared the data and is being sent to esp32 through aws iot. data is received but when trying to write to the lock it doesn't respond.
In order to see whether it is something wrong with command or not I installed the noble in my mac and passed the same command through the noble write method and it works and lock responds.
Command is created from a buffer in javascript for noble  and this makes lock work
let buffer = encData.slice(0, 20);
      console.log(i + ": " + buffer.toString("hex"));
      //The buffer value in hex is aa5510f0988fbef125a97eee5e7ae2beeaff79
      foundCharacteristic.write(buffer, true, function(error) {
        console.log("set characteristic value ");
      });

I checked a BLE server using the BLE Scanner app in ios and cloned the same characteristics of the lock and could see the value 0xaa5510f0988fbef125a97eee5e7ae2beeaff79 in the app.
When doing for the ESP, I pass this hex value aa5510f0988fbef125a97eee5e7ae2beeaff79 to aws iot and is received in the ESP32 and then the ble scanning is done and the required service and characteristics are found and are written through the following method using the Ble_Client example.

String input = "aa5510f0988fbef125a97eee5e7ae2beeaff79"
if (connected) {
    Serial.println("Setting new characteristic value to \"" + input + "\"");

    // Set the characteristic's value to be the array of bytes that is actually a string.
    Serial.println(input.c_str());
    pRemoteCharacteristic->writeValue((uint8_t*)input.c_str(), input.length());
    connected = false;

  }

This never works for me .Am I passing the correct way the value or something missing? I am able to scan and get the services and characteristcs but the write is a failure. Not sure whether some conversion issues or what is going wrong. Please do help me if there is something to be done. I have been trying for so long.
Thanks in advance

Try with uint8_t input[] = {...};, unless you need to get length from String. But for testing purpose you can test it that way.
Maybe you write to wrong characteristic?

@chegewara  Thanks for the reply. I debugged and tested again with the BLE connect to check what comes from the ESP32 and from the noble.
In noble project ```
let buffer = encryptedData();// -> which returns a buffer
console.log(i + ": " + buffer.toString("hex")); //aa5510f0988fbef125a97eee5e7ae2beeaff79
The above aa5510f0988fbef125a97eee5e7ae2beeaff79 string value I pass and send it to aws iot to receive in the ESP and this is what is written to the ble device.

In the ble scanner app I could see the

- HexValue-"6161353531306630393838666265663132356139376565653565376165326265656166663739"
- String value - "aa5510f0988fbef125a97eee5e7ae2beeaff79"

But noble takes the write() a buffer as input so characteristics.write(buffer) is received as the following in the ble scanner

- Hex Value- "aa5510f0988fbef125a97eee5e7ae2beeaff79"

- String Value- "No Value".

I find the aa5510f0988fbef125a97eee5e7ae2beeaff79 to reach as hex in the ble device when the esp32 characteristics.write(input) is called .The input is also string "aa5510f0988fbef125a97eee5e7ae2beeaff79"


Error in terminal when refreshing PDP page

Issue
When reloading the PDP page (cmd + r) I get the following error in terminal
web_1  | Warning: Failed prop type: The prop `serverState` is marked as required in `WithData(WithCatalogItem)`, but its value is `undefined`.
web_1  |     in WithData(WithCatalogItem) (at withShop.js:34)
web_1  | apollo client error { TypeError: Cannot read property 'apollo' of undefined
web_1  |     at new WithData (/usr/local/src/reaction-app/src/.next/dist/bundles/pages/product.js:5755:42)
web_1  |     at walkTree (/usr/local/src/reaction-app/node_modules/react-apollo/react-apollo.umd.js:34:38)
web_1  |     at walkTree (/usr/local/src/reaction-app/node_modules/react-apollo/react-apollo.umd.js:66:25)
web_1  |     at getPromisesFromTree (/usr/local/src/reaction-app/node_modules/react-apollo/react-apollo.umd.js:96:9)
web_1  |     at getDataFromTree (/usr/local/src/reaction-app/node_modules/react-apollo/react-apollo.umd.js:109:24)
web_1  |     at /usr/local/src/reaction-app/node_modules/react-apollo/react-apollo.umd.js:117:45
web_1  |     at <anonymous>
web_1  |     at process._tickDomainCallback (internal/process/next_tick.js:228:7) queryErrors: [ [Circular] ] }

Haven't seen this in awhile, so I'm closing.


Vector 1

Changed tick marks to match NCL plot and changed colorbar to match NCL plot.
Closes issue #440
Previous version:

New version:

Original NCL plot:

A couple points:
On my side, the background for the label is not showing up. Also, if you look at the screenshot below, it seems like we might be missing a level above 28.8, which would also make sense because it seems like the original plot has a section of darker purple that the recreation does not.
Also, we might want to consider switching colormaps to reflect best practices as in the other examples

I could not get the color bar edges to extend to the end of the colorbar, but the levels on the actual plot are correct now.


fix(setup): remove sudo for pip

Description

We've been using sudo for pip because, as written in ~/.profile, $HOME/.local/bin isn't in the $PATH right after OS installation.
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

However, using sudo for pip isn't recommended.
$ sudo pip install clang-format
[sudo] password for kenji:
Requirement already satisfied: clang-format in /usr/local/lib/python3.10/dist-packages (14.0.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

As I thought sudo can be removed if I add export PATH="$HOME/.local/bin:$PATH" in the setup script, I changed so.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Since I haven't tested this well, I'll mark this as a draft.

@kenji-miyake alternatively, what do you think of virtualenv? virtualenvwrapper lets you have multiple versions of Python workspaces and are stored in a central place (https://virtualenvwrapper.readthedocs.io/en/latest/)

@esteve I think it's good! But there are some problems:

I'm not familiar with it.
I'm not sure if it works well with ROS 2.

Do you know about it?

@esteve Thank you for the link. :pray:
Seeing this, after the user run source ./venv/bin/activate, it seems the same as the normal user mode of pip.
If so, I guess this PR also works with virtualenv. Am I right? :thinking:

@kenji-miyake yes, it should work the same. But this was just to ask you if you think it's a good idea, perhaps we don't need to add this to the development process. One nice thing is that any dependencies we install are in the virtualenv, so if we want to remove all the dependencies with installed, it's as easy as removing the virualenv

@esteve I see. :+1:
Do you think it's good to merge this now (even though it may break something) and will observe it for a while? (And will fix bugs if issues are reported.)
If it's okay, I'll make this ready for review.
Currently, it's not good because it obviously won't work with virtualenv.

@kenji-miyake I think it should be ok to merge this :+1:

Okay, then I'll set reviewers from TIER IV who might be familiar with this issue!


[Feature Request]: New Linter warning decompiler-cleanup should be addressed

Description
A nice Bicep Linter warning decompiler-cleanup was introduced and should be addressed by us (e.g., by renaming all variables the rule complains about).
Example
WARNING: C:\ResourceModules\modules\Microsoft.Network\azureFirewalls\deploy.bicep(120,5) : Warning decompiler-cleanup: The name of variable 'additionalPublicIpConfigurations_var' appears to have originated from a naming conflict during a decompilation from JSON. Consider renaming it and removing the suffix (using the editor's rename functionality). [https://aka.ms/bicep/linter/decompiler-cleanup]

As a general rule we could rename

objects to *Object
array to *List
or something smarter


Use custom types for DiddiScript types

Toward #38. The types follow DSGP 1, and won't be treated like Python built-in types anymore.

Well, let's merge this!


Add scheduled task to publish homeworks

Write to console log as prototype
Restrict activity on unpublished homework

Use quarz

auto howework_ids = SelectPublishableHomeworks().Shuffled()
for (auto howework_id : howework_ids) {
  transactionally {
    auto homework = AcquireById(howework_id)
    if (homework.isPublishable) {
      publish(homework)
    }
  }
}

Need to add a message broker

This will be done at #72


Not able to find `GLIBCXX_3.4.32'

After quantizing the model i am loading model to cuda  then this error has come oftenly.
[/home/ubuntu/miniconda3/envs/dev-2/lib/python3.12/site-packages/optimum/quanto/library/ops.py:66](http://<IP_ADDRESS>:8001/lab/workspaces/auto-H/tree/LogoMaker/App/miniconda3/envs/dev-2/lib/python3.12/site-packages/optimum/quanto/library/ops.py#line=65): UserWarning: An exception was raised while calling the optimized kernel for quanto::unpack: /home/ubuntu/miniconda3/envs/dev-2/lib/python3.12/site-packages/zmq/backend/cython/../../../../.././libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by [/home/ubuntu/miniconda3/envs/dev-2/lib/python3.12/site-packages/optimum/quanto/library/extensions/cuda/build/quanto_cuda.so](http://<IP_ADDRESS>:8001/lab/workspaces/auto-H/tree/LogoMaker/App/miniconda3/envs/dev-2/lib/python3.12/site-packages/optimum/quanto/library/extensions/cuda/build/quanto_cuda.so)) Falling back to default implementation.
  warnings.warn(message + " Falling back to default implementation.")

for libname in ["quanto", "quanto_py", "quanto_ext"]:
torch.library.define(f"{libname}::{name}", schema)
# Provide the inplementation for all dispatch keys in the main library
@torch.library.impl(f"quanto::{name}", "default")
def impl(*args, **kwargs):
    if _ext_enabled:
        try:
            return getattr(torch.ops.quanto_ext, name)(*args, **kwargs)
        except Exception as e:
            if isinstance(e, NotImplementedError):
                message = f"No optimized kernel found for quanto::{name}."
            else:
                message = f"An exception was raised while calling the optimized kernel for quanto::{name}: {e}"
            warnings.warn(message + " Falling back to default implementation.")
    return getattr(torch.ops.quanto_py, name)(*args, **kwargs)


✨ Add ability for user to split / group layers from UI

Overview of design need

Is there an existing GitHub issue this design work pertains to?
Add split layer/ group layers shortcuts/ button #1543
Functions to split/combine multiple layers along an axis #1322

In a sentence or two, describe the problem to be solved for users
Now that napari has the functionality for users to group layers, and then to split apart grouped layers, we should make it easier for them to do this from the UI.

What level of design is needed? (Choose all that apply)

[ ] User experience research:  high-level recommendation/exploration of user needs, design heuristics, and / or best practices to inform a design experience
(Use this option when you feel there’s a challenge to be solved, but you’re curious about what the experience should be — may involve research studies to understand challenges/opportunities for design)
[X] Information flow / conceptual: organizing and structuring of information flow and content, including layout on screen or across multiple steps
[X] Visual: creating mockups, icons, etc
(If choosing this level alone, it means that the content to be mocked up and its organization is already known and specified)

Is design a blocker?

[ ] Yes: engineering cannot proceed without a design first
[X] No: engineering can create a first version, and design can come in later to iterate and refine

If selecting Yes, how much design input is needed to unblock engineering? For example, is a full, final visual design needed, or just a recommendation of which conceptual direction to go?
T-shirt size

[ ] ●○○○○ XS: able to be done in a typical workday or two
[X] ●●○○○ S: able to do within one sprint, if also working on other things in the sprint
[ ] ●●●○○ M: able to do within one sprint, if it is the sole focus
[ ] ●●●●○ L: will likely take more than one sprint to complete, but less than two
[ ] ●●●●● XL: a very large experience to be determined or overhauled, will need to be broken down further

This was also added in the layer co text menu

I think this is solved by the layer list contextual menu split/merge.

Those layer list contextual menu actions for split/merge are now documented:
https://napari.org/stable/tutorials/fundamentals/viewer.html#right-click-menu
So going to close this.


Fix tooling and dependencies update

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


你好，出现deepcopy错误

y = _reconstruct(x, memo, *rv)

File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 270, in _reconstruct
state = deepcopy(state, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 146, in deepcopy
y = copier(x, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 230, in _deepcopy_dict
y[deepcopy(key, memo)] = deepcopy(value, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 172, in deepcopy
y = _reconstruct(x, memo, *rv)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 296, in _reconstruct
value = deepcopy(value, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 172, in deepcopy
y = _reconstruct(x, memo, *rv)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 270, in _reconstruct
state = deepcopy(state, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 146, in deepcopy
y = copier(x, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 230, in _deepcopy_dict
y[deepcopy(key, memo)] = deepcopy(value, memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\copy.py", line 153, in deepcopy
y = copier(memo)
File "C:\D_installation_packet\Anaconda\installion_package\envs\yolov6\lib\site-packages\torch\tensor.py", line 55, in deepcopy
raise RuntimeError("Only Tensors created explicitly by the user "
RuntimeError: Only Tensors created explicitly by the user (graph leaves) support the deepcopy protocol at the moment

看起来您在尝试将ODConv应用在其他任务上，但这个问题与ODConv并不相关，已经超出我们项目的范围了。请考虑到更合适的地方询问这些问题，也请善用搜索引擎，直接搜索“Only Tensors created explicitly by the user (graph leaves) support the deepcopy protocol at the moment”应该已经可以得到许多解决方案了。


Support Python 2.6

This string formatting nicety was introduced in Python 2.7 and breaks
Python 2.6 users like myself. This change is forwards and backwards
compatible between all Pythons.

Thanks for the catch!  Was unaware that this formatting quirk failed in 2.6.
This points out the need for better integration/coverage testing of the pex tool itself since 2.6 is supported and definitely covered by the rest of the tests.

Awesome tool, btw, we're playing with pex now to see if we can use it to manage a somewhat large codebase. So far it is looking great.

Cool.  If you have any questions or need any help, don't hesitate to reach out.  We don't have a pex-specific mailing list but the pants mailing list can be pretty helpful, and there's usually at least one of us in #pypa or #pypa-dev.

Hi @wickman, I know the change was trivial, but do you have any idea when a new version of pex might be available on pypi? We're largely a Python 2.6 shop and I'm trying to work pex into our artifact generating machinery... I can't do that until we get this fix released.

unless i'm missing something, '{}'.format(foo) is not a syntax error in Python 2.6 so the toolchain should work just fine (just that the 'pex --version' command is broken.)  we should still roll a patch release but i just wanted to be clear that you shouldn't be blocked.

You're right, it's not a syntax error, but every command I try to run on Python 2.6 yields an error like this.
Traceback (most recent call last):
  File "/home/sholsapp/.virtualenvs/py509/bin/pex", line 11, in <module>
    sys.exit(main())
  File "/home/sholsapp/.virtualenvs/py509/lib/python2.6/site-packages/pex/bin/pex.py", line 320, in main
    parser = configure_clp()
  File "/home/sholsapp/.virtualenvs/py509/lib/python2.6/site-packages/pex/bin/pex.py", line 57, in configure_clp
    parser = OptionParser(usage=usage, version='%prog {}'.format(__version__))
ValueError: zero length field name in format

Ah, ok.  I see.  Thanks for the context.  I'll get this published asap.

Published.  Thanks for the prod.

Right on. Thank you for the quick response!


Issue with Alarm Trigger for Fish

How does the alarm for GatherBuddy work? It says the alarm will trigger in real minutes earlier instead of Eorzean minutes for fish but even though I set it to 5 (minutes), the alarm always only go off when the fish has spawned.
https://media.discordapp.net/attachments/684745859497590843/948061805245243423/unknown.png

The offset does not work for fish in 2.x
It's fixed and completely changed in 3.0, which is currently in alpha testing and will soon go to dalamud testing.


skip apply "ngx_http_upstream_process_accel_expires" when a request responeded by cache

"ngx_http_upstream_process_accel_expires" is calculate and set valid_date value when a request will responded by a cache, even though it will never use in response.
So, this patch can skip unnecessary process.
On the other hands, this has good side effect to can get TRUE valid_date value of the cache in "header filter" and "log" hook handler.

This pull request will be closed automatically because we don't accept pull requests due to this repository uses mirror.

Thank you for contributing to Nginx!
Nginx does not use GitHub for code submissions.
Please visit http://nginx.org/en/docs/contributing_changes.html
and follow the instructions there to submit changes.


test-all-exercises: Handle practice exercises

TODO: Doesn't handle concept exercises
(a v3 change)

As there don't seem to be any active maintainers, I'll assume that role and merge this. Thanks @petertseng!


version: leave "undefined" if it cannot detect

Let's avoid defaults if we cannot safely detect the version
from the git tag: otherwise we can't distinguish a legit versioned
build from a build which used the fallback.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/lgtm


On Android, flutter run throws "error: package androidx.multidex does not exist"

Steps to reproduce

Take an existing Flutter project from Flutter 3.16.
flutter upgrade to Flutter 3.22.
flutter run on Android

Actual results
The app should launch in the Android emulator.
Logs

Logs

$ flutter run
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
C:\Users\songy\Documents\Projects\Music with Anna\quick_ear\android\app\src\main\java\io\flutter\app\FlutterMultiDexApplication.java:13: error: package androidx.multidex does not exist
import androidx.multidex.MultiDex;
                        ^
C:\Users\songy\Documents\Projects\Music with Anna\quick_ear\android\app\src\main\java\io\flutter\app\FlutterMultiDexApplication.java:23: error: cannot find symbol
    MultiDex.install(this);
    ^
  symbol:   variable MultiDex
  location: class FlutterMultiDexApplication
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s
Running Gradle task 'assembleDebug'...                              6.3s
Error: Gradle task assembleDebug failed with exit code 1

Error output and standard output:
error.log
run.log
Flutter Doctor output

Doctor output

$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.22.0, on Microsoft Windows [Version
    10.0.22631.3447], locale en-CA)
[√] Windows Version (Installed version of Windows is version 10 or
    higher)
[√] Android toolchain - develop for Android devices (Android SDK
    version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community
    2022 17.9.4)
[√] Android Studio (version 2023.3)
[√] VS Code (version 1.89.1)
[√] Connected device (4 available)
[√] Network resources

• No issues found!

This is related to #98136

Possible workaround: https://stackoverflow.com/questions/49886597/multidex-issue-with-flutter/60158352
But I suggest Flutter handles multidex by itself when an existing project is migrated to a newer version.

Deleting the FlutterMultiDexApplication  file works for now

Thanks for the report @songyang-dev
I tried to do the same by going back to 3.16.0 to 3.22.0, but was unable to replicate the reported error.
I tried with flutter run and flutter run --multidex both.
Can you provide exact steps to replicate or a pattern or a config that is needed to replicate this in latest stable ?
Also, if you switch back to 3.19, can you check if the same error occurs or not ?
You can also provide relevant file details that are required to properly replicate the issue.

Deleting the FlutterMultiDexApplication file works for now

Manually deleting worked for me too, but in my opinion this has to work out of the box after upgrading to Flutter 3.22.

I forgot to specify that the existing project needs to be using multidex support. When you run it on the older version of Flutter, it should say in the console that multidex support is being used.

Thanks for the update. I will try to setup and replicate this by going back to previous stable versions and have multidex support. I tried with an existing project by running it in 3.19 and upon upgrading it worked fine, but need to see the multidex support for that project, but it'll take a bit time to properly replicate this.
Meantime, I'll keep the issue open and label based on the reported behavior, for team's attention.

In my side, flutter build appbundle was working fine, then upgrade to 3.22 and same error.
I had to update my android/app/build.gradle
android {
    defaultConfig {
        multiDexEnabled true
    }
}

dependencies {
    implementation "androidx.multidex:multidex:2.0.1"
}

Now everything went back to normal. I'm surprised it worked before without this.

Maybe it works for project that hardcode minSdkVersion, however I'm using minSdkVersion flutter.minSdkVersion

In my project "minSdkVersion 23" is hardcoded in android/app/build.gradle but I still had the problem.


Setting node arguments on azure application settings dont work

Investigative information
Please provide the following:

Function name(s) (as appropriate):
Invocation ID: d5d9c46b-6775-41b3-bc6a-ad38491372c3
Region: East US

Repro steps

Setup an application setting "languageWorkers__node__arguments=--experimental-loader @node-loader/core"
Hit the function

Expected behavior
The invoked function should run with the experimental loader args on the node invocation
Actual behavior
The application setting is ignored, thus causing a crash on the application
Here is a link  for function url
Related information
I've tried setting this node arguments in several ways, none did work.

"languageWorkers:node:arguments".This one works locally on the "local.settings.json" but the colon is not allowed on the applcation settings on azure.

I've found this instructions on this repo and on the azure docs, but none of them seem to work on the deployed version

Hi @zeyuri - this settings is currently only meant for local development, but we are working on addressing your issue in this work item: https://github.com/Azure/azure-functions-host/issues/7139
Please note too that setting languageWorkers:node:arguments in production will have a small negative performance impact on cold start, which is something that we should be sure to document (cc: @anthonychu and @alrod)

Thanks for the answer!

I think I'm gonna try using containers


Fix #4291: xfreerdp segfault when connecting freerdp-shadow-cli

https://github.com/FreeRDP/FreeRDP/issues/4291

This looks like a legitimate fix, anyway I'm really wondering how we lead to that situation (I don't wanna hide a more high level bug)

@freerdp-bot can you test that please ?

@hardening @daixj-shterm Fixed the culprit in #4294
The shadow server allowed being started with an invalid monitor index, leading to 0x0 resolutions on client side which exposed this parameter check error.


Cannot building triton from source since it costs extremely large memory

Hi the following is the building steps

Clone and build LLVM:git clone git@github.com:llvm/llvm-project.git ./llvm-project
cd llvm-project
git checkout 657ec7320d8a28171755ba0dd5afc570a5a16791
cmake -G Ninja -S llvm -B build -DCMAKE_INSTALL_PREFIX=../bin -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_PROJECTS="mlir;llvm" -DLLVM_TARGETS_TO_BUILD="host;NVPTX;AMDGPU" -DLLVM_PARALLEL_COMPILE_JOBS=32 -DLLVM_PARALLEL_LINK_JOBS=4
ninja

Clone tritongit clone git@github.com:triton-lang/triton.git ./triton

Setup and activate python virtualenv:python -m venv .venv --prompt triton
source .venv/bin/activate

Install relative dependenciespip install ninja cmake wheel

Install tritonLLVM_INCLUDE_DIRS=../llvm-project/build/include \
LLVM_LIBRARY_DIR=../llvm-project/build/lib \
LLVM_SYSPATH=../llvm-project/build \
CMAKE_BUILD_TYPE=Debug  \
pip install -e python

After I did that, the terminal shows:
Obtaining file:///home/shore/%E6%96%87%E6%A1%A3/projects/triton_learn/triton/python
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Preparing editable metadata (pyproject.toml) ... done
Collecting filelock (from triton==3.0.0)
  Using cached filelock-3.15.4-py3-none-any.whl.metadata (2.9 kB)
Using cached filelock-3.15.4-py3-none-any.whl (16 kB)
Building wheels for collected packages: triton
  Building editable for triton (pyproject.toml) ...

And then it cost extremely large memory, as I have 48G RAM and 50+G swap, it still not enough for building triton

Try set MAX_JOBS=


Installation: dependency 'volto-object-widget'

Hi! First of all: Slate is cool. And this, your Slate integration rocks.

pasting text by creating multiple blocks is magnificent
the play of Slate with ElasticSearch is a lot easier than that of DraftJS (thanks for the plaintext value!)
the widget for setting links is really comfortable
well, the response on selecting text is a bit sluggish

I switch to Slate.
This is what I think is also necessary to install eea/volto-slate:
"addons": [
  "@eeacms/volto-object-widget"
],

"dependencies": {
  "@eeacms/volto-object-widget": "^1.0.0"
}

It's not enough to follow this instruction of README.txt:
If you already have a volto project, just update package.json:
"addons": [
    "volto-slate:asDefault"
],

"dependencies": {
    "volto-slate": "^1.0.0"
}

Thank you for taking time for this!

@ksuess Thank you! I will update docs.
I found that it also needs @eeacms/volto-blocks-form

@ksuess Fixed. See (README](https://github.com/eea/volto-slate#getting-started)


Vibration is unavailable in Legacy of Kain: Defiance

Even with Xidi v4.0.0 the vibration menu option is grayed out in Legacy of Kain: Defiance. In order to investigate this further I will need some assistance. The Xidi log shows that the game successfully invokes many parts of the DirectInput API for vibration, even to the point of creating a force feedback effect option, and then suddenly gives up for no apparent reason.
I tried this game on Windows 7 and XP using a real Logitech RumblePad 2 with the official Logitech drivers installed. The force feedback driver is installed and works properly via DirectInput, yet for some reason with this game the vibration option is still grayed out.
What I need is some additional information on a working combination of controller hardware and Windows version in order to investigate further. Either that or some additional technical insight into what this game needs internally to allow vibration to be available.

maybe xinputplus make some help? https://community.pcgamingwiki.com/files/file/2265-xinput-plus-v415290/
but I couldn't inject his dll into the game even using hookshot and xinputplus loader

What I need is some additional information on a working combination of controller hardware and Windows version in order to investigate further. Either that or some additional technical insight into what this game needs internally to allow vibration to be available.

@samuelgr Out of curiosity, have you tried using your Rumblepad, and its drivers, in Windows 10/11? (Hope you've been well, otherwise).

@samuelgr Out of curiosity, have you tried using your Rumblepad, and its drivers, in Windows 10/11? (Hope you've been well, otherwise).

Yes, I tried that first before trying with Windows 7 and XP.

I've sourced a Logitech F510 pad to try and help out. Once I've received it, I'll test it and report back here.

Vibration isn't working on Metal Gear Solid 2: Substance either.

Some new feedback from @r2rX in #6 indicates that vibration actually works in Defiance despite the menu option being grayed out. Maybe the UI is a bug in the game but it does not seem like this is an issue anymore.

I also tested this game myself using the GOG version on Windows 11. While the menu option is grayed out, vibration indeed does work during normal gameplay with Xidi v4.0.2.

Thank you very much, @samuelgr for all your time and effort on this project. As bonus feedback, Xidi 4.0.2 also works great with Blood Omen 2.


Update to version 2.10.20

Please update the snap to version 2.10.20.

2.10.20 is in candidate now


Send/Receive Headers via Http2 Frames

getting ready for #4267

[INFO] --- maven-checkstyle-plugin:2.17:checkstyle (default) @ okhttp ---
[INFO] Starting audit...
[ERROR] /home/travis/build/square/okhttp/okhttp/src/main/java/okhttp3/internal/http2/Http2Stream.java:391: Line is longer than 100 characters (found 103). [LineLength]
Audit done.


Update to OpenCL 2.0

Summary
This updates the OpenCL headers that allow for up to version 2.2 support. We use the flags -DCL_HPP_TARGET_OPENCL_VERSION=200 so that our code base uses OpenCL 2.0 by default.
There are a few code changes to update us from some deprecated functions.

to_size_t was removed and instead we use cl::array<size_t, 3>
We no longer need to pass a pair to the OpenCL program to compile kernels (ex here)
cl::make_kernel was deprecated so we now use KernelFunctor when constructing kernels.
The OpenCL header is now just a single file and so I removed the CL folder in the dependency library folder. Now we just do #include <cl.hpp>

Tests
All basic opencl tests pass
Side Effects
We are not using any of the OpenCL 2.0 kernel features and so this should have no side effects for the kernels.
Checklist

[x] Math issue #1276

[x] Copyright holder: (fill in copyright holder information)

Steve Bronder
The Khronos Group Inc.

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Can we somehow check what OpenCL version is supported on the test Mac machine?

Ughhh I totally forgot about metal and Mojave. When I get home I think I can set CL_HPP_MINIMUM_OPENCL_VERSION=120 to let this compile with 1.2 and 2.0

I tried to google this awhile a go, but had not luck finding an anwser. On pre-Mojave OSx with an AMD/NVIDIA GPU, do the GPU OpenCL runtimes that come with the drivers support OpenCL 1.2.x or 2.0?

I'm pretty sure it's only 1.2 (mby even 1.1) that are supported on the pre-installed drivers before Mojave

Gonna close this until I write the dependency wiki


[FLINK-29444][Connectors/AWS] Syncing parent pom to elasticsearch in prep for release

What is the purpose of the change
Prep for connector release
Brief change log

Syncing parent pom to elasticsearch in prep for release
Adding git submodule for connector release scripts

Verifying this change
Build locally
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? n/a

Superseded by https://github.com/apache/flink-connector-aws/pull/21


How to control Equalizer

I have an issue equalizer about Vlc.DotNet.
Generic information

Vlc.DotNet version : (3.1.0)
Vlc.DotNet project used : (WinForms)
libvlc version <IP_ADDRESS>
.net version : (4.5)
Project language : (C#)
Project build architecture : (x64)
Operating system : (Windows 10) (x64)

Summary
How to adjust 10band graphic equalizer and amplifier. please provide code.
is it possible

You can do that with the same options as the VLC command line, but as far as I know, you can't adjust the equalizer dynamically at runtime.

what is the command line?
I have found this equalizer code on codeproject.com it was nVLC.LibVlcWrapper something

Do your own researches and share your findings here. I don't know every aspect of VLC.
https://wiki.videolan.org/VLC_command-line_help

there is a libvlc equalizer api but its not surfaced by vlc.dotnet.
https://www.videolan.org/developers/vlc/doc/doxygen/html/group__libvlc__audio.html#gad252fff10bf02bc8436b3beab4badef9

Does that mean it is exposed by LibVLCSharp ?

Yes.

I agree with Mr. mfkl
there is a libvlc equalizer api but its not surfaced by vlc.dotnet.
pls. update it is very important every users and programmers
Image adjustment is available such as (hue, brightness, contrast, saturation, gamma) working perfectly but not audio equalizer available right now.
Hi all users please share your projects, next time i share my project.

pls. update it is very important every users and programmers

I've been maintaining this project for 3-4 years and as far as I know, this has never been asked. Since Vlc.DotNet is going into maintenance mode, I'm not sure it is worth the effort to add new features here. I encourage you to switch to LibVLCSharp.
However, if you create the PR for that, I might merge it. Otherwise, I'll let this open for someone interested to implement that.

Hi
jeremyVignelles, thanks your quick response. I your project followed 3 years ago, but never share my experience because it's a very good platform for every one learn and quickly coding and make own project quickly, no doubt  Vlc.DotNet is a good.
but it is very important for me make a basic media player, this features
audio equalizer, Image adjustment (it's already make it), run time change visualization
regards,
subh

hi
all don't judge me for my coding, it's messy i'm not a good programmer
Vlc.netbysubh.zip

Can you upload that on a github repository instead? it's easier to review, especially on mobile.

okay sir, give me few days I upload my github account.

Vlc.DotNet is in maintenance mode and will not get any new features. LibVLCSharp has the feature implemented.

Vlc.DotNet is in maintenance mode and will not get any new features. LibVLCSharp has the feature implemented.


I want to use storageMode memory and localStorage both

Can this be done ?

is there a valid use case to store the same data in both localStorage and memory?

Use it as different services... Or in single service but with 2 cache objects... Hard to imagine your use case,,,

Use it as different services... Or in single service but with 2 cache objects... Hard to imagine your use case,,,

The current implementation does not support this.


[Bug]: TypeError: this.Session.aggregate(...).toArray is not a function     at MongodbAdapter.getSessionAndUser

Package
@lucia-auth/adapter-mongodb
Describe the bug
The default integration with Lucia v3 is broken when you try to connect using MongoDB and Mongoose
Migrated fully as explained on the documentation, this doesn't work at the moment
It breaks at getSessionAndUser when you try to validate sessions

How are you initializing the adapter? The MongoDB adapter has been tested against both mongodb and mongoose so I doubt it's a bug

@pilcrowOnPaper then I use the database connection anywhere it's needed

Like what are you passing to the adapter?

Passing the mongoose collection like this

What version of mongoose are you using?

Here's the version I'm using
"mongodb": "^6.3.0",
"mongoose": "^8.1.0",

Might be a v8 issue, will test it out

I can't see to recreate the issue. Tested with MongoDB v6 and Mongoose v8. I'd need a basic reproduction.

i am getting same error here in this project https://github.com/erayakgunn/product-management

I can't see to recreate the issue. Tested with MongoDB v6 and Mongoose v8. I'd need a basic reproduction.

@pilcrowOnPaper This happens when you call validateSession with the SessionID

We have tests for all adapter methods, including getSessionAndUser(), and I'm not getting any error in both Mongoose v6 and v8.

I can't see to recreate the issue. Tested with MongoDB v6 and Mongoose v8. I'd need a basic reproduction.

I'm able to reproduce this with the same package versions and with an example. It seems to happen on first load (with a session cookie set) after restarting the app and clears after reloading the page. I haven't come across this error in any other scenarios.

Blank project and this works fine:
import mongoose from "mongoose";

await mongoose.connect(url);

const result =  await mongoose.connection.collection("users").aggregate().toArray();
console.log(result);

I can't see to recreate the issue. Tested with MongoDB v6 and Mongoose v8. I'd need a basic reproduction.

I'm able to reproduce this with the same package versions and with an example. It seems to happen on first load (with a session cookie set) after restarting the app and clears after reloading the page. I haven't come across this error in any other scenarios.

Yes. It happens with a session cookie set
I'm trying to create an isolated scenario to find the root cause

Can't reproduce it:
import { Lucia, generateId } from "lucia";
import { MongodbAdapter } from "@lucia-auth/adapter-mongodb";
import mongoose from "mongoose";

const adapter = new MongodbAdapter(
  mongoose.connection.collection("sessions"),
  mongoose.connection.collection("users")
);

const lucia = new Lucia(adapter);

await mongoose.connect(process.env.MONGODB_URL);

const userId = generateId(15)
await mongoose.connection.collection("users").insertOne({
    _id: userId as any,
    username: "pilcrow"
})

const session = await lucia.createSession(userId, {});
const validatedSession = await lucia.validateSession(session.id);

What framework are you using?

I am using nuxt and like @cdy-peters said it happens on first load

I can't see to recreate the issue. Tested with MongoDB v6 and Mongoose v8. I'd need a basic reproduction.

I'm able to reproduce this with the same package versions and with an example. It seems to happen on first load (with a session cookie set) after restarting the app and clears after reloading the page. I haven't come across this error in any other scenarios.

I found my issue... I wasn't awaiting the connection. I think I removed it as it was throwing an ES target error that I couldn't resolve. Didn't realise with Nuxt you have to define the ES target for the Nitro server separately, solution.

@pilcrowOnPaper  I did a sample here: https://github.com/donsn/lucia-auth-test

Yeah probably an issue with Mongoose. That said, I can't seem to recreate the issue in a simple project. I can't even use createConnection() for some reason

Yeah probably an issue with Mongoose. That said, I can't seem to recreate the issue in a simple project. I can't even use createConnection() for some reason

Thank you for the update
I'll install the new version, retry the upgrade and send pull request containing a full nextjs sample for others who might have issues (highlighting important points to note when using next.js)
I'll also test to be sure  doesn't cause issues for plain mongodb users
Thanks @pilcrowOnPaper for the awesome library, Lucia & Oslo


add another method to ping yourself from huginn

I have tested this from my sk-huginn.herokuapp.com instance and it seems to work

Nice, thanks!

Please let us know if you see it stop working so we can remove this advice.


bram_int/dsp_int fuzzers: Topmost clock region is not available for Kintex 420T due to bug in Vivado 2017

As soon as I add bram/dsps from the topmost clock region, the design fails,
complaining that more bram/dsps are instantiated than available on the device.
(Although they clearly exist).

Hi, I had a similar issue when experimenting on artix 35T.
The issue is that the device, here XC7K420T, is same fabric than XC7K480T which is larger.
So Vivado applies the artificial limit on design size for 420T.
My recommendation is to create settings for 480T, and mark the 420T as being same fabric.

Just like #1871

@marzoul Thank you for the tipp. That really makes sense. I added a new PR here: https://github.com/f4pga/prjxray/pull/1908
And let's hope it works.

@marzoul OK, that seemed to work! But now, when I run the fuzzer 005-tilegrid/generate_full.py for kintex 480t, I get an error with different offsets in the tilegrid for the following sites:
INT_R_X25Y226; orig offset 53, new 51
INT_L_X24Y226; orig offset 51, new 53
INT_L_X24Y226; orig offset 51, new 53
INT_L_X24Y227; orig offset 55, new 53
What do I need to do about those?

@hansfbaier Sorry this is not an issue that I already faced.
But it might originate from unhandled or partially-handled things in columns that could result in wrong propagation of addresses...

@marzoul Anyway, I was able to make it run using a hack. Now I have the first successful build!
Thanks to your help!
https://github.com/f4pga/prjxray/pull/1908
That means, if I want to build something for 420T, I just use the 480T chip database instead with nextpnr-xilinx?

@hansfbaier To use the 420T, you will just indicate to nextpnr-xilinx that you target a 420T chip. Internally in nextpnr, this will be handled strictly like the 480T, except at the end the generated bistream will have the chip ID for 420T instead of 480T.


Take tab-width into account in shfmt

The indentation size of 4 was hard-coded in the formatter parameters. This PR fixes this by using the tab-width value.

This seems reasonable, however I think the test framework needs some updates to handle using this buffer-local variable in a reasonable way.

#167 should address this in a more accurate way. I think this can be closed.

Yep, looks to be.


Cocoapods Implementation

Good time of day. Please add the implementation of Cocoapods.
"Failed to resolve dependencies Dependencies could not be resolved because root depends on 'shadowswift' 4.0.0..<5.0.0.
'shadowswift' >= 4.0.0 cannot be used because no versions of 'shadowswift' match the requirement 4.0.1..<5.0.0 and package 'shadowswift' is required using a stable-version but 'shadowswift' depends on an unstable-version package 'chord'.
"

Solution to the problem:
You need to install a dependency from the main branch in Xcode. Many thanks to the author for the response via email!


docs: Remove bare URLs from Flow gRPC API Reference

The Flow gRPC API Reference contains bare URLs to Cilium's source code on GitHub and the W3C Trace Context specification. This changes the non-tabled bare URLs to Markdown links for an improved reading experience. Following this change, users can click on the links and directly access a page instead of having to copy and paste URLs. This also adds punctuation in several places for consistency.
I tested these changes locally.

/test


[beta] Search Challenges in Map

[ ] Add Search box on the map similar to previous version.
[ ] Search should be fuzzy.
[ ] Search should be available from all pages.

We removed this feature. We will adding in @Bouncey 's search feature as a replacement.
Happy Coding

Hi @BerkeleyTrue
We might anticipate Navigation UX issues a lot after we ship the new batch of challenges.
Sure, I don't know the motivation behind removing the search, currently its annoying to reach any challenge while browsing. Even more is the case for ability to fuzzy search like we can in the production.
I am not sure, if you are talking about the Elastic Search Feature which I remember @QuincyLarson mentioning? If yes, then it maybe a while before we have that.
Isn't that supposed to be able to search everything on freeCodeCamp (guides, forum, etc.)?

The scope of this issue is to have, a light weight UI component similar to that we have on production, for quick navigation.

@raisedadead I'll check with @Bouncey and see whether he can incorporate his search box into the nav bar in advance of shipping beta.

Sure, @QuincyLarson in that case, lets leave this open and blocked.

@raisedadead Sounds good. @Bouncey is making rapid progress on this: https://www.npmjs.com/package/react-freecodecamp-search

@QuincyLarson thanks for the updates.


Allow net-ldap v0.7.0

it contains a fix for authenticating against Microsoft Active Directory with StartTLS
details:
https://github.com/ruby-ldap/ruby-net-ldap/pull/95

Is there someone working on this, because all Versions < 0.6.0 have the following vulnerability:

Net::LDAP for Ruby lib/net/ldap/password.rb SSHA Password Generation Weak Salt
CVE 2014-0083
Patched Versions >= 0.6.0

:+1:


fixed PMOD 1 (JB) connections 7-10

fixed those values after checking the official schematics for the arty z7 board
https://reference.digilentinc.com/learn/documentation/schematics/arty-z7-schematic
please check to confirm. the new version works for me, however there might be an oversight I did not notice. this PMOD port is called JB in the schematics.

I noticed a few more wrong connections. closing while not fixed.

fixed all the pmod connections (I think!), should be safe to merge now.


Should there be an "Add a VM" button on hosts page ?

Should there be an "Add a VM" button on hosts page ?
 ?

Useful
Info

Versions
Rancher v0.59.0 Cattle: v0.148.0 UI: v0.90.0

Access
github admin

Route
null

by the way:

The VM is a container though. I'm not sure there should be different instrumentation around it for the sake of it? I do agree however it should be visually represented that a container contains a VM process. Perhaps a new icon. For now though it could be covered in the service naming?

Closing due to inactivity, please reopen if you think this is still relevant to current releases & important.  We are revisiting our RancherVM solution + UI.


Next/Prev links not generated for some content

As reported here: https://github.com/symfony/symfony-docs/issues/19075
The create_framework/* pages don't display a next/prev pager because when building docs with this project, the next and prev items in the generated JSON file are null.
Note that pagination is generated successfully for other contents of Symfony Docs. So, this feature is fully working, except for some particular contents.
This is the RST source of the failing content: https://github.com/symfony/symfony-docs/tree/6.4/create_framework
Thanks!

I've debugged the issue.
In this line:
https://github.com/symfony-tools/docs-builder/blob/218bfe8bef908cea3934851fd294ffa0d48db059/src/Generator/JsonGenerator.php#L73
For create_framework docs, the arguments are like this:
$parserFileName = "create_framework/http_kernel_httpkernelinterface"
$flattenedTocTree = array:186 [
  0 => "index"
  1 => "getting_started/index"
  2 => "setup"
  3 => "setup/docker"
  4 => "setup/homestead"
  5 => "setup/web_server_configuration"
  6 => "setup/bundles"
  7 => "setup/file_permissions"
  8 => "setup/flex"
  9 => "setup/flex_private_recipes"
  10 => "setup/symfony_server"
  11 => "setup/unstable_versions"
  12 => "setup/upgrade_major"
  13 => "setup/upgrade_minor"
  14 => "setup/upgrade_patch"
  15 => "page_creation"
  16 => "introduction/from_flat_php_to_symfony"
  17 => "introduction/http_fundamentals"
  18 => "routing"
  19 => "routing/custom_route_loader"
  // ...
  177 => "validation/raw_values"
  178 => "validation/sequence_provider"
  179 => "validation/severity"
  180 => "validation/translations"
  181 => "web_link"
  182 => "webhook"
  183 => "workflow"
  184 => "workflow/workflow-and-state-machine"
  185 => "workflow/dumping-workflows"
];

So, the problem is that we only pass the general TOC tree of the entire Symfony Docs and not the specific TOC tree of the carete_framework/ "book".
Sadly, I have no idea how to solve this. Hopefully someone can help us here. Thanks!

🧙
The answer is finally simple, but like you, i lost a lot of time there digging 😅
In the end, it's "just" a problem of missing links / relative URLs.
What i understand is that the TocTree is fully computed.. from the root.
On the root index.rst file, i believe there is a glitch that make the included links not "root relative" and then ignored in the TocTree.
If you replace the include with a toctree, it works! (in the fjson generated files, the prev & next values are now set)
Want to create your own framework based on Symfony?

- .. include:: /create_framework/map.rst.inc
+ .. toctree::
+    :maxdepth: 2
+
+    create_framework/index

Other exemple: the page "security/access_token" as no prev/next too because it's not linked from the security.rst file (bottom of the page).
:)

@javiereguiluz ? :)

I think you should try (if not already done) and it will then be easier to isolate what is related to configuration, bugs, tree structure, etc.
Feel free to poke me if you need/want on this :)

I'm closing this as "fixed" because the change that Simon proposed is working and the docs now display the Next/Prev links. See https://symfony.com/doc/current/create_framework/introduction.html


Specify in docs that vcf file needs accompanying index file

Include in docs explicit instructions to have both a .vcf.gz and .vcf.gz.tbi file

just attaching a note to this that it's kinda already in the config file here but not in the docs here


Direct2d exploration

Hey @mattgonzalez
This is what I did:

Copied some code in from the module branch of your project
Added a Direct2D implementation
Enabled running tests on the implementation
Try to get single channel to work

Feel free to jump in and run the tests target. You can open this project in CLion (or whatever will build cmake projects) or run cmake from the command line to build and run the tests.
These are the problems/thoughts so far:

[ ] As far as I can tell, there's nothing too "expensive" with getting the adapter and device context, it's basically asking around for pointers, is this correct? — can we do this for every call to the blur, or is it expensive and should be cached (I've made it static here, but i think that will cause problems in reality)
[ ] It doesn't compile. The juce::DxgiAdapter::Ptr adapter; line is unhappy for some reason, when compiling I get an error (cannot convert argument 1 from const int to juce::DxgiAdapter::Ptr).
[ ] Source and Destination — for single channel images, they are usually rendered paths for drop shadow usage. That means that the image being fed to us could be the source and destination — does Direct2D allow this?
[ ] Single Channel images — maybe Direct2D needs the image to be converted to ARGB to run the effect, not sure?
[ ] For now we can proceed with assuming all incoming images are direct2d backed — I think. IMO if we want to check for that, it's before the direct2d algorithm is chosen, so we don't need a bunch of conditional logic for that in the implementation.

Note there's some oddities about running CMake from the root of a JUCE module so you'll need to NOT use Ninja (if you do, you'll run into an infinite loop).
 That's how I've been doing manual inspection. I uhh.... should modify to put them in a subfolder.

These are the problems/thoughts so far:
* [ ]  As far as I can tell, there's nothing too "expensive" with getting the adapter and device context, it's basically asking around for pointers, is this correct? — can we do this for every call to the blur, or is it expensive and should be cached (I've made it static here, but i think that will cause problems in reality)

The adapters are already stored by JUCE. We'll probably want to cache the device context.

* [ ]  It doesn't compile. The `juce::DxgiAdapter::Ptr adapter;` line is unhappy for some reason, when compiling I get an error (`cannot convert argument 1 from const int to juce::DxgiAdapter::Ptr`).

I'll take a look.

* [ ]  Source and Destination — for single channel images, they are usually rendered paths for drop shadow usage. That means that the image being fed to us _could_ be the source and destination — does Direct2D allow this?

Fairly certain that for D2D effects the source & destination need to be different. Could just copy the source back to the destination when we're done and keep a temporary scratchpad image for the output.

* [ ]  Single Channel images — maybe Direct2D needs the image to be converted to ARGB to run the effect, not sure?

I need to figure out how to convert image formats in the GPU instead of on the CPU.

* [ ]  For now we can proceed with assuming all incoming images are direct2d backed — I _think_. IMO if we want to check for that, it's _before_ the direct2d algorithm is chosen, so we don't need a bunch of conditional logic for that in the implementation.

OK

Note there's some oddities about running CMake from the root of a JUCE module so you'll need to NOT use Ninja (if you do, you'll run into an infinite loop).
 That's how I've been doing manual inspection. I uhh.... should modify to put them in a subfolder.

It doesn't compile. The juce::DxgiAdapter::Ptr adapter; line is unhappy for some reason, when compiling I get an error (cannot convert argument 1 from const int to juce::DxgiAdapter::Ptr).

This may be due to mixing the JUCE headers with the system headers. You may have better success if you can include the Windows headers first before any JUCE headers.

Thanks for the comments!
No matter the order of the includes, I can't get references to DxgiAdapter and friends to compile.
For now, I've simplified and just trying to do everything in 1 function.
My suspicion is part of the problem comes from trying to "reach into" the juce_graphics module internals. When one includes a juce module, one is supposed to just include the top level header like "juce_graphics/juce_graphics.h" which then goes and includes everything it needs to be happy — it usually causes problems to root around and try and include random files from modules. It also feels a bit wrong to be including windows.h and so on...
BUT (big BUT!) I'm out of my depth here in Windows-land, so I have no idea what half of this stuff is :D

Got single channel working, with a temporary image as the destination which then copies back to the source.


expected release date

@impiga Hi, thanks for your great work. May I know the time that the code would be released?

Also interested in this, given that I'd like to have this model available in HF Transformers, where currently the following models are supported:

DETR
Deformable DETR
Conditional DETR
YOLOS

Next, it can be compared on the open object detection leaderboard: https://huggingface.co/spaces/rafaelpadilla/object_detection_leaderboard

Thanks for your interest in our work!
@impiga Yutong will help to release the code ASAP.

Object Detection Leaderboard is now under the hf-vision organization:
https://huggingface.co/spaces/hf-vision/object_detection_leaderboard

Hey @PkuRainBow, @impiga, thanks again for the great work!👏🏻
Really looking forward to seeing the code;
any updates on progress towards release here?

The code has now been released. Please check it out and let us know if you have any questions or feedback!


Hyperlink of breadcrump is incorrect

Hi,
when the Single page app is deployed in a path like http://spa.abc.com/app/#states
then the breadcrumps referring http://spa.abc.com/#states .

Thi can be fixed by adding the base  like
<base  href="/app/" />