Resource requested by bevy_panorbit_camera::egui::check_egui_wants_focus does not exist: bevy_egui::EguiUserTextures

Hello,
Thank you for your awesome crate. It is a huge help to the bevy beginners.  I'm fairly new to the bevy scene.
I ran into this error and some errors regarding Context (which I couldn't reproduce) on my machine.
I am not sure if this is me having a corrupt and very old installation of an OS or this is due to some bug in the program or bevy.
Error
Initially, I was working on my own project and ran into this error:
Resource requested by bevy_panorbit_camera::egui::check_egui_wants_focus does not exist: bevy_egui::EguiUserTextures
As it is an egui error, it happens when bevy_egui is featured.
What I did
After some tinkering with values and plugins, I suspected the versions. I used bevy_egui crate in 0.25 and 0.26 with and without feature render also checked bevy with its own render feature. Nothing worked on my project when having full dependencies as the following:
bevy-inspector-egui = "0.23.4"
bevy_utils = "0.13.2"
bevy_window = "0.13.2"

Assuming I am the main criminal here for skipping through the documentations and notes, I used your own examples. Both with a [workspace] empty config and without one on a fresh config (not that it matters just thought I mention). Again, I went forward and edited flags on your own Cargo.toml (the render thing). Also tried to bump to version 0.26.
The demo advanced ALWAYS crashed. 100% of the times. egui worked when the version was 0.25 without any other dependency in my own project.
Searching in the internet, I didn't find anything mostly because I am still not efficient in googling bevy related stuff. This caught my eye and I tried to contact the author of the issue as well so I just link it here for future reference.

I also have this issue and if I just let bevy_editor_pls insert the EguiPlugin it never inserts the bevy_egui::EguiUserTextures Resource and sometimes segfaults the program

Originally posted by @lambdadeltakay in https://github.com/mvlabat/bevy_egui/issues/252#issuecomment-2018554081
All in all, I thought I report this for the sake of being documented. I have no idea how can I contribute to fix the issue as I am still learning bevy. But if I can make a blind guess, it guess the problem lies within this package. Please let me know if I can help in any capacity.
I am using a recent update of Arch (altho old in installation and pretty much it has its own set of problems) and I attached a full trace down below.

RUST_BACKTRACE=full cargo run --features="bevy_egui" --example advanced
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
 Running `target/debug/examples/advanced`

2024-04-13T10:01:46.934734Z  WARN log: error setting XSETTINGS; Xft options won't reload automatically
2024-04-13T10:01:46.945243Z  INFO bevy_winit::system: Creating new window "App" (0v1)
2024-04-13T10:01:46.945400Z  INFO log: Guessed window scale factor: 1
2024-04-13T10:01:46.991157Z  INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce RTX 3070 Ti", vendor: 4318, device: 9346, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "550.67", backend: Vulkan }
2024-04-13T10:01:47.282967Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux rolling Arch Linux", kernel: "6.8.2-arch1-1", cpu: "11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz", core_count: "8", memory: "15.5 GiB" }
thread 'Compute Task Pool (7)' panicked at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/system_param.rs:570:17:
Resource requested by bevy_panorbit_camera::egui::check_egui_wants_focus does not exist: bevy_egui::EguiUserTextures
stack backtrace:
0:     0x56b093bfa616 - std::backtrace_rs::backtrace::libunwind::trace::hd6ffdc229294c06f
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/../../backtrace/src/backtrace/libunwind.rs:104:5
1:     0x56b093bfa616 - std::backtrace_rs::backtrace::trace_unsynchronized::h991f79b6e9960513
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2:     0x56b093bfa616 - std::sys_common::backtrace::_print_fmt::hf4ebe716f7ccda10
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:68:5
3:     0x56b093bfa616 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h410d4c66be4e37f9
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:44:22
4:     0x56b093c26070 - core::fmt::rt::Argument::fmt::he0ff0e0e188c0db5
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/fmt/rt.rs:142:9
5:     0x56b093c26070 - core::fmt::write::he40921d4802ce2ac
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/fmt/mod.rs:1120:17
6:     0x56b093bf6f5f - std::io::Write::write_fmt::h5de5a4e7037c9b20
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/io/mod.rs:1846:15
7:     0x56b093bfa3f4 - std::sys_common::backtrace::print::hd8e2e3f655086663
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:47:5
8:     0x56b093bfa3f4 - std::sys_common::backtrace::print::h11c067a88e3bdb22
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:34:9
9:     0x56b093bfbc77 - std::panicking::default_hook::{{closure}}::h8c832ecb03fde8ea
10:     0x56b093bfb9d9 - std::panicking::default_hook::h1633e272b4150cf3
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:292:9
11:     0x56b093bfc178 - std::panicking::rust_panic_with_hook::hb164d19c0c1e71d4
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:781:13
12:     0x56b093bfc052 - std::panicking::begin_panic_handler::{{closure}}::h0369088c533c20e9
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:659:13
13:     0x56b093bfab16 - std::sys_common::backtrace::__rust_end_short_backtrace::hc11d910daf35ac2e
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:171:18
14:     0x56b093bfbda4 - rust_begin_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:647:5
15:     0x56b093c23465 - core::panicking::panic_fmt::ha6effc2775a0749c
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:72:14
16:     0x56b08ffd3368 - <bevy_ecs::change_detection::ResMut as bevy_ecs::system::system_param::SystemParam>::get_param::{{closure}}::h2e930ec5dc85514d
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/system_param.rs:570:17
17:     0x56b08ffd78ff - core::option::Option::unwrap_or_else::h9ccaa69006e28daa
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/option.rs:976:21
18:     0x56b08ffdb0a3 - <bevy_ecs::change_detection::ResMut as bevy_ecs::system::system_param::SystemParam>::get_param::h1cd923751882e7c0
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/system_param.rs:567:21
19:     0x56b08ffd74ab - <(P0,P1) as bevy_ecs::system::system_param::SystemParam>::get_param::h1171ed556ed8a62f
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/system_param.rs:1363:20
20:     0x56b08ffd5e7c - bevy_egui::::::get_param::h88cb0c59dc3d6247
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_egui-0.25.0/src/lib.rs:347:10
21:     0x56b08ffc6652 - <(P0,P1,P2) as bevy_ecs::system::system_param::SystemParam>::get_param::h6a544d3385754ea2
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/system_param.rs:1363:20
22:     0x56b08ffcc085 - <bevy_ecs::system::function_system::FunctionSystem<Marker,F> as bevy_ecs::system::system::System>::run_unsafe::hb68e7465b8c35f46
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/system/function_system.rs:493:22
23:     0x56b093969fd9 - bevy_ecs::schedule::executor::multi_threaded::MultiThreadedExecutor::spawn_system_task::{{closure}}::{{closure}}::h4819dd6baa2b42d4
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/schedule/executor/multi_threaded.rs:534:26
24:     0x56b0939aa7b9 - core::ops::function::FnOnce::call_once::h52d56c755ecc1146
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:250:5
25:     0x56b093929539 - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::hac576f44f4a8f4b7
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panic/unwind_safe.rs:272:9
26:     0x56b093976bbd - std::panicking::try::do_call::h7658211b416e8e5a
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
27:     0x56b09397df1b - __rust_try
28:     0x56b09397667e - std::panicking::try::he3106bc3f39d09ea
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
29:     0x56b0939cff2a - std::panic::catch_unwind::h1bd227ad3f936291
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
30:     0x56b0939698ca - bevy_ecs::schedule::executor::multi_threaded::MultiThreadedExecutor::spawn_system_task::{{closure}}::h9597e5cfa7c785cb
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.13.2/src/schedule/executor/multi_threaded.rs:529:23
31:     0x56b093927d87 - <core::panic::unwind_safe::AssertUnwindSafe as core::future::future::Future>::poll::h1825a220bd537531
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panic/unwind_safe.rs:297:9
32:     0x56b09395487e - <futures_lite::future::CatchUnwind as core::future::future::Future>::poll::{{closure}}::hd491861c7b3d3a00
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-lite-2.3.0/src/future.rs:588:42
33:     0x56b093929474 - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::h645c7a0b9691250a
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panic/unwind_safe.rs:272:9
34:     0x56b093976da6 - std::panicking::try::do_call::hb2990bd85ad64e37
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
35:     0x56b09397df1b - __rust_try
36:     0x56b093976718 - std::panicking::try::hebb93ec4f1aaad9e
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
37:     0x56b0939cff7b - std::panic::catch_unwind::h46594b9492343a45
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
38:     0x56b0939545b0 - <futures_lite::future::CatchUnwind as core::future::future::Future>::poll::hbe8fd1935f644d9f
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-lite-2.3.0/src/future.rs:588:9
39:     0x56b093970f39 - async_executor::Executor::spawn_inner::{{closure}}::ha791aa456099a3f4
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-executor-1.10.0/src/lib.rs:237:20
40:     0x56b093909c07 - async_task::raw::RawTask<F,T,S,M>::run::{{closure}}::h32788f23108fe0aa
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-task-4.7.0/src/raw.rs:550:21
41:     0x56b0939aa284 - core::ops::function::FnOnce::call_once::h2e3c4522e9abef1e
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:250:5
42:     0x56b09392939c - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::h15ea68178764cabc
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panic/unwind_safe.rs:272:9
43:     0x56b093976a08 - std::panicking::try::do_call::h3e7c2bba5c70cd9d
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
44:     0x56b09397df1b - __rust_try
45:     0x56b093975efa - std::panicking::try::ha12b978c1c4eff62
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
46:     0x56b0939d01fb - std::panic::catch_unwind::hf285d9518ccfff2f
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
47:     0x56b093903c54 - async_task::raw::RawTask<F,T,S,M>::run::h69301f18717db755
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-task-4.7.0/src/raw.rs:549:23
48:     0x56b093a0e51f - async_task::runnable::Runnable::run::h4cd6a868d3d76438
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-task-4.7.0/src/runnable.rs:781:18
49:     0x56b0939eeff2 - async_executor::Executor::run::{{closure}}::{{closure}}::hb9369966ddf25561
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-executor-1.10.0/src/lib.rs:352:21
50:     0x56b0939e8495 - <futures_lite::future::Or<F1,F2> as core::future::future::Future>::poll::h3cae43337f80d69c
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-lite-2.3.0/src/future.rs:449:33
51:     0x56b0939eeba1 - async_executor::Executor::run::{{closure}}::h0ac20053eadaf831
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/async-executor-1.10.0/src/lib.rs:359:32
52:     0x56b0939e3666 - futures_lite::future::block_on::{{closure}}::h2d65b073b7eac8ae
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-lite-2.3.0/src/future.rs:99:19
53:     0x56b0939e5671 - std::thread::local::LocalKey::try_with::h4479394c6d398926
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/local.rs:286:16
54:     0x56b0939e50b4 - std::thread::local::LocalKey::with::h1c45df7b950fcecd
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/local.rs:262:9
55:     0x56b0939e343d - futures_lite::future::block_on::h2f5056a4514e9b9c
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-lite-2.3.0/src/future.rs:78:5
56:     0x56b0939faf82 - bevy_tasks::task_pool::TaskPool::new_internal::{{closure}}::{{closure}}::{{closure}}::{{closure}}::h36cacc40e82fc1ae
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_tasks-0.13.2/src/task_pool.rs:180:37
57:     0x56b0939f6521 - std::panicking::try::do_call::h28d42a01fec84196
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
58:     0x56b0939fb93b - __rust_try
59:     0x56b0939f6358 - std::panicking::try::h9ada44ff19d7fb13
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
60:     0x56b0939f233e - std::panic::catch_unwind::hdc1b4dbfe21a8674
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
61:     0x56b0939fac8c - bevy_tasks::task_pool::TaskPool::new_internal::{{closure}}::{{closure}}::{{closure}}::h9d6f3d8d62567020
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_tasks-0.13.2/src/task_pool.rs:174:43
62:     0x56b0939e57c1 - std::thread::local::LocalKey::try_with::h6c816048fc66774f
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/local.rs:286:16
63:     0x56b0939e512b - std::thread::local::LocalKey::with::h96b61245cff574b1
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/local.rs:262:9
64:     0x56b0939faa95 - bevy_tasks::task_pool::TaskPool::new_internal::{{closure}}::{{closure}}::he809386342cb1058
at /home/yas/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_tasks-0.13.2/src/task_pool.rs:167:25
65:     0x56b0939e8c86 - std::sys_common::backtrace::_rust_begin_short_backtrace::ha014311ad1a9592a
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:155:18
66:     0x56b0939ea5cd - std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}::hde7246d4a9e5e886
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/mod.rs:529:17
67:     0x56b0939ec881 - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::he5f82f7d19faf347
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panic/unwind_safe.rs:272:9
68:     0x56b0939f65b5 - std::panicking::try::do_call::h6b7e52662797902a
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
69:     0x56b0939fb93b - _rust_try
70:     0x56b0939f6482 - std::panicking::try::hdbc58e0535411d34
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
71:     0x56b0939ea3ed - std::panic::catch_unwind::hd4492b24aae18d36
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
72:     0x56b0939ea3ed - std::thread::Builder::spawn_unchecked::{{closure}}::h14e791413a5d6eda
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/thread/mod.rs:528:30
73:     0x56b0939f238f - core::ops::function::FnOnce::call_once{{vtable.shim}}::h9e69d4f788419c6d
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:250:5
74:     0x56b093bff915 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once::h6b630278c760b971
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/alloc/src/boxed.rs:2015:9
75:     0x56b093bff915 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once::h70462b441b6c0e1f
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/alloc/src/boxed.rs:2015:9
76:     0x56b093bff915 - std::sys::pal::unix::thread::Thread::new::thread_start::h3631815ad38387d6
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys/pal/unix/thread.rs:108:17
77:     0x7e35ef21f55a -
78:     0x7e35ef29ca3c -
79:                0x0 -
Encountered a panic in system bevy_panorbit_camera::egui::check_egui_wants_focus!
Encountered a panic in system bevy_app::main_schedule::Main::run_main!

When two libraries pull in bevy_egui and their versions are different, you will encounter lots of instability and breakage. Search your Cargo.lock to see what library is pulling in the duplicates (if this is the issue).

Hi, glad you like the plugin.
As already mentioned, check if any dependencies pull in different versions of bevy_egui. This is most likely what is happening because I am pretty certain this is the exact issue I was getting after a major bevy update while bevy_egui hadn't been updated yet.
If that fails, give me a minimal reproducible example and I will see what I can find out.

I can reproduce the error if I run:
cargo run --example advanced --features bevy_egui

However that is expected because the advanced example doesn't add the EguiPlugin. So make sure EguiPlugin is added to your app.

Thank you for your fast response. I implemented my own version of your crate off (I just want an interactive graph tool so did not invest so much time in it).

However that is expected because the advanced example doesn't add the EguiPlugin. So make sure EguiPlugin is added to your app.

Regardless, I can confirm that EguiPlugin was directly and indirectly early enough in all my attempts.

Sounds like aren't using this plugin any more, so I will close this issue.

Thank you!
I will notify if I used it again and found the bottom of the issue.


Options to set colors for : selected line, selected text, Console View background.

Feature Request
Description of Problem:
User would like to configure colors as per Notepad++ "Nord" theme:

https://github.com/arcticicestudio/nord-notepadplusplus
(Dark theme with light blue text.)

Looking for a way to set the colors for the current line and selected text to match the theme.
Currently, the default yellow for current line and light purple for selected text do not fit the theme.
Related is that light blue text is hard to read against the white background of Console View.
Potential Solutions:
Would be nice if options could be added to Theme dialog:

token.CURRENT_LINE
token.SELECTED_TEXT

And update Theme-related code to act accordingly.
As for the Console View background, it might make sense for it to inherit the color from token.BACKGROUND.
Otherwise, add an option to the Theme dialog.
Thanks!

This has been requested from a user in MS today


[Tracking] Xilinx toolchain

Discussed in https://github.com/cucapra/calyx/discussions/873

Originally posted by sampsyo January 13, 2022
As a recreational project this winter, I poked around at our infrastructure for running programs for real on Xilinx FPGAs (which is all the incredible work of the inimitable @sgpthomas!!). I just wanted to tie together the issues I've been filing to summarize the current state of things, which might be especially relevant to @yn224.
The bottom line is: compilation is working OK, with one significant asterisk; emulation is barely starting to work; and I have not tried real FPGA execution.

Compilation: As of #850, #851, #852, and #855, we are successfully producing xclbin files from Calyx programs. :tada:

[x] The big remaining problem is an issue involving multiple memories and multiple AXI interfaces, described in #853.
[ ] The next step to be done here is to see if the xo generation Tcl needs different declarations of the AXI interfaces, as described in https://github.com/cucapra/calyx/issues/853#issuecomment-1006817950.
[ ] It would also be useful to continue trying to simplify our Tcl script to the absolute bare minimum necessary to produce an xo file (so we understand exactly what we're doing).

Emulation: You can see emulation working in the janky "tests" I made in #866.

[ ] However, the one tiny test I am running is not producing the right answer. (The memory state seems to be unmodified from the initial state.) One next step is to debug this stuff.
[ ] There is also some important refactoring to be done in #872.
[ ] We are also missing docs for the fpga stage, which we should write after the refactoring. (We can delete the docs for the emulation stage.)

Execution: Basically, we need to try out real execution on actual hardware. It only really makes sense to focus on it after emulation works, but we could do some of the experimentation concurrently. This would also benefit from the refactoring in the aforementioned #872.

Of course, the end result of all this should be that we can do fud e something.fuse --to dat --through fpga and everything just works (and the output matches our interpreter and Verilator execution). I also strongly believe we should maintain a focus on documenting things as thoroughly as we can possibly muster in the appropriate chapter—this stuff is so damned confusing and under-documented that we really benefit from writing things down clearly and exhaustively along the way.
Some fun future work after everything's nailed down for an MVP:

[ ] Let's do Intel!! I keep hearing good things about OPAE, which is the Intel equivalent of Xilinx's XRT.
[ ] Maybe we can remove our bespoke statistics-only Vivado synthesis setup and replace it with this toolchain. Who knows.

[01/26] I have verified that allocating the same number of AXI interface with the number of external memory declarations on futil files solve the problem of xclbin files being generated. For instance, if the example file includes 3 external memories, then we need to declare m0_axi, m1_axi, and m2_axi.
Some examples used include memory tutorial, modified memory tutorial (mem_tut_dup.txt) (where I basically duplicated the logic to have 2 different memory), and vectorized-add.
I also tested with the case where there are more AXI declaration than the number of external memory declaration and that also seems to work fine
.

@yn224, I'm moving discussion to #853, which is the issue about this specific problem.

@sampsyo should we close this/re-evaluate once #1153 is merged and @nathanielnrn's work over the summer is complete?

Certainly time to re-evaluate, given all this progress! I checked off a few things—the stuff to be re-categorized (put on a roadmap somewhere, factored out into another issue, etc.) include trying to simplify the relevant Tcl script, future work on Intel, and removing the special statistics-only stages in fud.

https://github.com/Xilinx/embeddedsw/issues/225#issue-1415371661
Can you help me with this, please??


Fix missing Latitude and Longitude meta-data in extract_raw_data()

WHAT DOES THIS PR DO?

This PR ensures that the extract_devices_data method includes latitude and longitude metadata for all device categories (BAM and low-cost sensors). The changes address the issue of missing latitude and longitude in the final output.

JIRA CARDS
OPS-231 OPS-234
CHANGES MADE

Included latitude and longitude metadata for both BAM and low-cost devices.
Simplified device filtering logic.

HOW DO I TEST OUT THIS PR?
from datetime import datetime, timedelta, timezone
from airqo_etl_utils.utils import Utils
from airqo_etl_utils.date import date_to_str_hours
from airqo_etl_utils.airqo_utils import AirQoDataUtils
from airqo_etl_utils.constants import DeviceCategory
import pandas as pd

hour_of_day = datetime.now(timezone.utc) - timedelta(hours=2)
start_date = date_to_str_hours(hour_of_day)
end_date = datetime.strftime(hour_of_day, "%Y-%m-%dT%H:59:59Z")

def extract_raw_data() -> pd.DataFrame:

    return AirQoDataUtils.extract_devices_data(
        start_date_time=start_date,
        end_date_time=end_date,
        device_category=DeviceCategory.LOW_COST,
    )

extract_raw_data()

Summary by CodeRabbit

Improvements

Enhanced sensor data extraction for AirQo devices, including refined parameter descriptions, improved data handling, and optimized logic.

Bug Fixes

Added missing type annotations and adjusted logic for better device filtering and data extraction.

New Features

Introduced a new parameter to the get_devices function to filter for active devices only.

Hi @MartinKalema , thanks again.
In the background through phone calls, Slack private DMs and emails, please mobilise your colleagues to review your recent PRs. Thanks!

@Baalmart This PR is good to go. The active query parameter was added to the get_devices() method as shown below.
params = {"tenant": str(Tenant.AIRQO), "active": "yes"}


Add workflow to deploy to AKS

Add workflow to deploy to AKS

Automated Deployment Warning
Ensure your manifest at ./kubernetes/deployment.yaml, ./kubernetes/ingress.yaml, and ./kubernetes/service.yaml uses the image name "registry1730324216310.azurecr.io/image-workflow-1730324168691:latest" for the application you wish to deploy.
For example, the image line in your deployment would look something like
image: registry1730324216310.azurecr.io/registry1730324216310.azurecr.io/image-workflow-1730324168691:latest


ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data'

there is something wrong with my machine and I reinstall my ubuntu. I re-gitclone the code and just keep the data.but when I follow the readme to do installation,it print:
(monoscene) potato@ubuntu-X299-UD4-Pro:~/workplace/MonoScene$ pip install -e ./
Obtaining file:///home/potato/workplace/MonoScene
Installing collected packages: monoscene
Running setup.py develop for monoscene
Successfully installed monoscene-0.0.0
(monoscene) potato@ubuntu-X299-UD4-Pro:~/workplace/MonoScene$ python monoscene/scripts/train_monoscene.py     dataset=kitti     enable_log=true     kitti_root=$KITTI_ROOT     kitti_preprocess_root=$KITTI_PREPROCESS    kitti_logdir=$KITTI_LOG     n_gpus=1 batch_size=1 sem_scal_loss=False
Traceback (most recent call last):
File "monoscene/scripts/train_monoscene.py", line 1, in
from monoscene.data.semantic_kitti.kitti_dm import KittiDataModule
File "/home/potato/workplace/MonoScene/monoscene/data/semantic_kitti/kitti_dm.py", line 3, in
import pytorch_lightning as pl
File "/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/pytorch_lightning/init.py", line 20, in
from pytorch_lightning import metrics  # noqa: E402
File "/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/pytorch_lightning/metrics/init.py", line 15, in
from pytorch_lightning.metrics.classification import (  # noqa: F401
File "/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/pytorch_lightning/metrics/classification/init.py", line 14, in
from pytorch_lightning.metrics.classification.accuracy import Accuracy  # noqa: F401
File "/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/pytorch_lightning/metrics/classification/accuracy.py", line 18, in
from pytorch_lightning.metrics.utils import deprecated_metrics, void
File "/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/pytorch_lightning/metrics/utils.py", line 22, in
from torchmetrics.utilities.data import get_num_classes as _get_num_classes
ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data' (/home/potato/anaconda3/envs/monoscene/lib/python3.7/site-packages/torchmetrics/utilities/data.py)

I think maybe that "Successfully installed monoscene-0.0.0" ,the building process make wrongs?

This is the error in pytorch-lightning version. Could you verify that your pytorch-lightning version is "pytorch-lightning==1.4.0rc0"?

This is the error in pytorch-lightning version. Could you verify that your pytorch-lightning version is "pytorch-lightning==1.4.0rc0"?

yes，I use the "pip install -r requirements.txt"

Could you try this?
https://github.com/NVIDIA/DeepLearningExamples/issues/1113#issuecomment-1102969461

Could you try this? NVIDIA/DeepLearningExamples#1113 (comment)

I tried to reinstall the pytorch-lightning of another version,but it just printed:
RuntimeError: SpatialClassNLLCriterion_updateOutput does not have a deterministic implementation, but you set 'torch.use_deterministic_algorithms(True)'. You can turn off determinism just for this operation if that's acceptable for your application. You can also file an issue at https://github.com/pytorch/pytorch/issues to help us prioritize adding deterministic support for this operation.

You can set deterministic to False on lines 145 and 159 in the following file
https://github.com/cv-rits/MonoScene/blob/master/monoscene/scripts/train_monoscene.py#L159

You can set deterministic to False on lines 145 and 159 in the following file https://github.com/cv-rits/MonoScene/blob/master/monoscene/scripts/train_monoscene.py#L159

it works，thanks

ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data' (C:\ProgramData\anaconda3\Lib\site-packages\torchmetrics\utilities\data.py)

@Nikithareddy2201  yes！ i'm facing the same problem ,Have You Ever solve it ?

I think the error is because of newer torchmetrics version, could you downgrade it to 0.6.0 with
pip install torchmetrics==0.6.0


Background Tasks stuck other requests when i use a http middleware

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
import time

from fastapi import FastAPI, BackgroundTasks, Request, Response
from loguru import logger

app = FastAPI()

@app.middleware("http")
async def logger_request(request: Request, call_next) -> Response:
    logger.debug(f"http middleware [{request.url}]")
    response = await call_next(request)
    return response

class Worker:
    def __init__(self, arg):
        self.arg = arg
        logger.debug(f"worker[{arg}] init")

    def work(self):
        for i in range(10):
            logger.debug(f"worker[{self.arg}] work[{i}]")
            time.sleep(1)

@app.get("/")
async def root():
    return {"message": "Hello World"}

@app.get("/work/{worker_id}")
async def work(back_task: BackgroundTasks, worker_id: int):
    worker = Worker(worker_id)
    back_task.add_task(worker.work)

    return {"message": f"work[{worker_id}] created"}

@app.get("/hello/{name}")
async def say_hello(name: str):
    return {"message": f"Hello {name}"}

Description

router "/work/{worker_id}" would create a task(a sync task, actually) on backgroud, after calling it, other new requests will stuck  until the task finish
it just happen when i use a http middleware
i knew it is a starlette issue but i could not find a solution yet, anybody tell me how to solve this?

Operating System
Windows
Operating System Details
No response
FastAPI Version
0.74.1
Python Version
Python 3.7.10
Additional Context
No response

You are blocking event loop by calling sleep which is synchronous. This is also true for every sync code. Your code runs in single thread in single process, async works well that when there are a lot IO operations (db calls, server2server requests), for that time event loop "awaits" and can do other job, but remember at the end of the day it is still one process and one thread, CPU bound task will block it.
Of course there are option to scale it, for example see some fresh reddit discussion, https://www.reddit.com/r/Python/comments/sxovwp/async_io_tasks_vs_threads/
If you are using uvicorn, type in uvicorn --help and read about workers
--workers INTEGER               Number of worker processes. Defaults to the
                                  $WEB_CONCURRENCY environment variable if
                                  available, or 1. Not valid with --reload.

Having more workers (processes) would give you power to have multiple CPU bound code running in parallel (max is number of processes).
Some other - maybe better setups are workers in very different host/processes/containers and some queue. You add job to be done to Redis for example and 'worker' instance collect and execute them one after another. This requires some more complex system so if your requirement is to have MAX of few background task at once, more processes should be enough for you

it's on me that i forgot

You are blocking event loop by calling sleep which is synchronous. This is also true for every sync code. Your code runs in single thread in single process, async works well that when there are a lot IO operations (db calls, server2server requests), for that time event loop "awaits" and can do other job, but remember at the end of the day it is still one process and one thread, CPU bound task will block it.
Of course there are option to scale it, for example see some fresh reddit discussion, https://www.reddit.com/r/Python/comments/sxovwp/async_io_tasks_vs_threads/
If you are using uvicorn, type in uvicorn --help and read about workers
--workers INTEGER               Number of worker processes. Defaults to the
                                  $WEB_CONCURRENCY environment variable if
                                  available, or 1. Not valid with --reload.

Having more workers (processes) would give you power to have multiple CPU bound code running in parallel (max is number of processes).
Some other - maybe better setups are workers in very different host/processes/containers and some queue. You add job to be done to Redis for example and 'worker' instance collect and execute them one after another. This requires some more complex system so if your requirement is to have MAX of few background task at once, more processes should be enough for you

it's on me that i forgot to say that i had already use multi workers, even 16 workers, it still stuck.

Hi, I might be stuck with some similar situation, what's wrong with my code:
@app.middleware("http")
async def signature(request: Request, call_next):
    try:
        signature = request.headers.get('X-Coding-Signature')
    except AttributeError:
        return Response(status_code=status.HTTP_403_FORBIDDEN, content='Authentification failed.')
    content = await request.body()
    sha1 = hmac.new(bytes(SECRET_TOKEN, encoding="utf8"), content, 'sha1')
    sha1 = sha1.hexdigest()
    calculate_signature = 'sha1=' + sha1
    if not calculate_signature == signature:
        return Response(status_code=status.HTTP_403_FORBIDDEN, content='Authentification failed.')
    else:
        return await call_next(request)

and the route hook
@app.post('/hook')
def simple_hook(json: dict[str, Any]):

    try:
        id = json['sender']['id']
        name = json['sender']['name']
        # eventName = json['eventName']

        print("[coding.net] %s(%d): %s. " % (name, id, 'eventName'))

    except Error as e:
        print("ERROR: %s" % e)
        return {'code': -1}

    return {'code': 0,'message':'done!'}

Everything was just fine without the signature middleware above. Any hints?
Thank you for your work and your any reply

More about your issue: https://github.com/encode/starlette/pull/1441


lxc: mp: backup/replicate not working properly

Backup:

when trying to activate backup on a mount-point, the plan try to do it... again and again, but does not actually do anything. Need to be done manually.

Replication:

Default Proxmox is to replicate.
the module tries to explicitly activate it if configured to true, and remove it to get default value if set to false

By changing the value of mountpoint.backup in proxmox_lxc. proxmox provider still sending the default value "false"..

I think the mountpoint block is somewhat not behaving as expected, as soon as there is more then one:

Heres the state part for it:

The result is only one mountpoint and both have the backup state "false".
If you look at what terraform is gonna do to the resource:

It recognizes the backup attribute changed to false (wich is obviously not correct). And would like to add another mountpoint, as there is only one stored in the state.
Important note on that: I also checked the "backup" manually.


Convert manage definition to a LWRP

This gives us nice new functionality

I’m adding the Type: Jump In GitHub label to this issue. This is a great issue for someone to get their feet wet with and we’d love a PR to resolves the issue.

Would a manage resource as implemented as the definition file make sense? Right now it is based on individual users. Would a single resource that took the input of users that either were allow or denied make sense? I implemented this using Chef::Util::FileEdit's insert_line_if_no_match function, but after I did it realized that maybe a new resource is needed here.

Converted with full backwards compatibility by using the accumulator pattern


Fix cffi build issue.

Update dependencies.

Signed-off-by: Wade Barnes<EMAIL_ADDRESS>

@nodlesh, Give this a try locally with the test harness first.


boot failed: not a bootable disk

boot failed: not a bootable disk

It's always here，more than two hours

This is normal? Before Windows is installed, the harddrive is empty so as you can see in the screenshot it boots from DVD instead to perform the installation. After the installation is done, it will be able to boot from harddrive.

It's always here，more than two hours

Okay, and you cannot connect to port 8006? Can you try using the latest version (v2.06)?

I can connect to the browser port 8006, and this page is displayed. My operating system is Centos7 64bit, and the mirror version is the latest

Or try version v2.06 because in your screenshot it says v2.04

Thank you, my friend. I'll try 2.0.6


docs/prometheus-operator: clarify alertmanager config indentation

The current sentence is ambiguous: it might be interpreted as the file
needing to use 2 spaces as indentation.
Change it to clarify the whole file needs to be indented two spaces.

I'm still not sure why this works on CI, maybe it's dependant on some of the flags I added. My configuration when I encountered this issue was:
component "prometheus-operator" {
  namespace              = "monitoring"
  grafana_admin_password = "foobar"

  etcd_endpoints = [
    "<IP_ADDRESS>",
  ]

  prometheus_metrics_retention = "90d"
  # We don't plan on exposing Prometheus so this doesn't really matter
  prometheus_external_url      = "https://prometheus.my-cluster.example.net"

  alertmanager_retention    = "360h"
  # We don't plan on exposing alertmanager so this doesn't really matter
  alertmanager_external_url = "https://alertmanager.my-cluster.example.net"
  alertmanager_config       = "${file("alertmanager-config.yaml")}"
}

And my alertmanager-config.yaml:
config:
  global:
    resolve_timeout: 5m
  route:
    group_by:
    - job
    group_wait: 30s
    group_interval: 5m
    repeat_interval: 12h
    receiver: 'null'
    routes:
    - match:
        alertname: Watchdog
      receiver: 'null'
  receivers:
  - name: 'null'

Yes, with this it works fine with the configuration I mention above.

This has never been a problem for me :thinking:. And here is the config I use:
component "prometheus-operator" {
  grafana_admin_password = "admin"
  alertmanager_config    = file("alertmanager.yaml")
}

Lokoctl correctly deploys prometheus-operator for me. Also alert manager is working because I am getting alerts sent to my slack.

I can reproduce it easily with lokoctl 0.1.0:
$ go get github.com/kinvolk/lokomotive/cmd/lokoctl
$ lokoctl version
0.1.0
$ cat test.lokocfg
component "prometheus-operator" {
  namespace              = "monitoring"
  grafana_admin_password = "foobar"
  alertmanager_config    = file("alertmanager-config.yaml")
}
$ cat alertmanager-config.yaml
config:
  global:
    resolve_timeout: 5m
  route:
    group_by:
    - job
    group_wait: 30s
    group_interval: 5m
    repeat_interval: 12h
    receiver: 'null'
    routes:
    - match:
        alertname: Watchdog
      receiver: 'null'
  receivers:
  - name: 'null'
$ lokoctl component render-manifest prometheus-operator
FATA[0000] render chart: installing chart failed: template: prometheus-operator/templates/prometheus/rules-1.14/kubernetes-absent.yaml:29:14: executing "prometheus-operator/templates/prometheus/rules-1.14/kubernetes-absent.yaml" at <.Values.alertmanager.enabled>: nil pointer evaluating interface {}.enabled  args="[prometheus-operator]" command="lokoctl component render-manifest"

My guess is that we miss equivalent of this patch https://github.com/kinvolk/lokomotive/commit/5c03dda5c2579b0910012b34df53d1e63c6d5f6b#diff-e6bf98874488d240d555276efaa6052eL42 for helm 3 implementation of render.

My guess is that we miss equivalent of this patch 5c03dda#diff-e6bf98874488d240d555276efaa6052eL42 for helm 3 implementation of render.

Not sure I get the context, should I merge while we get that patch?

This is what I am using:
  config:
    global:
      resolve_timeout: 5m
      slack_api_url: "<ADD URL>"
    route:
      group_by: ['job']
      group_wait: 30s
      group_interval: 5m
      repeat_interval: 12h
      routes:
      - match:
          alertname: DeadMansSwitch
        receiver: 'null'
      - match:
        receiver: 'slack'
        continue: true
    receivers:
    - name: 'null'
    - name: 'slack'
      slack_configs:
      - channel: '#alertmanager'
        send_resolved: false

Oh this could be problem. The documentation says:

Note: Make sure it is indented to two spaces.

https://github.com/kinvolk/lokomotive/blob/master/docs/configuration-reference/components/prometheus-operator.md#configuration

Ah, the whole configuration! Yes, I tested indenting everything two spaces and it worked. I think we should rephrase to be more clear, I'll modify this PR to do that.

PTAL.

Created https://github.com/kinvolk/lokomotive/issues/211


Terraform secrets redeux

#13

Ran Plan for dir: terraform workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #14. To continue, delete the lock from #14 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

atlantis plan

Ran Plan for dir: terraform workspace: default

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Ran Plan for dir: terraform workspace: default

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: terraform workspace: default


RPH_G7_CE1 misnamed

In the schematic RPH_G7_CE1 is erroneously labelled as GPIO 8: RPH_G8_CE1.

Fixed! Thanks for catching that.


Unable to Build on Android (AGP 8)

Anh @hiennguyen92 ơi, em đang gặp lỗi build này mà không biết xử lý sao, anh giúp em với ạ
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':flutter_callkit_incoming:compileDebugKotlin'.
> Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17).

  Consider using JVM Toolchain: https://kotl.in/gradle/jvm/toolchain
  Learn more about JVM-target validation: https://kotl.in/gradle/jvm/target-validation

* 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.

please using 2.0.0+2


Is it possible Sikuli could work via wire protocol?

Is it possible Sikuli could work via wire protocol?
Just a thought.  http://www.sikulix.com/
OR, is there already something similar that exists somewhere?

Yes it works. I have made it work on grid.
You add sikuli jar to class path on hub using your json file.
"hub_additional_classpath": [
"./extension-proxy-0.6.jar"
]
On the nodes there is no option to add jar in class path. I have opened a defect for the same. As of now workaround is
Nodes can be launched with by adding all-node-extensions-0.6.jar to class path. We are using -cp parameter
"C:\Program Files\Java\jdk1.7.0_79\bin\java.exe" -Dhttp.proxyHost=proxy.ariba.com -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.ariba.com -Dhttps.proxyPort=8080 -cp "C:\selenium_ex/SeleniumGridExtras-jar-with-dependencies.jar;C:\selenium_ex/all-node-extensions-0.6.jar"  -jar "C:\selenium_ex/SeleniumGridExtras-jar-with-dependencies.jar"

@djangofan @shankarkc Can this be closed? I can start work on adding additional items to the node classpath soon (maybe)

Sure. This can be closed. Sikuli works on grid extra. I have it running in
our company Datacenter.
On Jun 26, 2016 9:35 AM, "Shawn McCarthy"<EMAIL_ADDRESS>wrote:

@djangofan https://github.com/djangofan @shankarkc
https://github.com/shankarkc Can this be closed? I can start work on
adding additional items to the node classpath soon (maybe)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/223#issuecomment-228583210,
or mute the thread
https://github.com/notifications/unsubscribe/AEb7V8q3avt4J1Tk-X8r4m-j5zxUUuoQks5qPfpvgaJpZM4IaU7C
.

Ok thanks. Closing this. Djangofan, please use shankarkc's method to run sikuli with selenium-grid-extras.


(PUP-7303) Ensure exemption of global vars from hiera stability check

This commit changes the hiera configuration stability check so that it
no longer checks global variables once they have been set.

CLA signed by all contributors.


Stacked bar visualisation on 2.6.0

After upgrading from chart.js 2.5.0 to 2.6.0 stacked bar visualisations aren't stacking any more - will try to look into chart.js code and make a pull request if successful.
2.5.0

2.6.0

Code
new Chart(chartContainer, {
    "type": "bar",
    "data": {
        "labels": context.contextLabels,
        "datasets": datasets
    },
    "options": {
        "scales": {
            "yAxes": [{
                "stacked": true,
                "ticks": {
                    "min": 1,
                    "max": max > 100 ? max : 100
                }
            }]
        }
    }
});

EDIT(SB): code formatting

@jungleBadger that's actually a bug fix, the 2.6.0 screenshot is the expected result: stacked on y but not on x. I think setting stacked: true on the x axis should produce the result you want?

@simonbrunel well thats embarrassing! Thank you very much for your answer and sorry about the mistake.
(setting X axis to stacked worked as expected)

I actually didn't upgraded to 2.6.0 again before sampling your suggestion. Worked on 2.5.0 with the following code but 2.6.0 the previous behaviour persists.:
new Chart(chartContainer, {
                "type": "bar",
                "data": {
                    "labels": context.contextLabels,
                    "datasets": datasets
                },
                "options": {
                    "scales": {
                        "xAxes": [{
                            "stacked": true
                        }],
                        "yAxes": [{
                            "ticks": {
                                "min": 1,
                                "max": max > 100 ? max : 100
                            }
                        }]
                    }
                }
            });

The sample code (http://www.chartjs.org/samples/latest/charts/bar/stacked.html) has the stacked: true option on both axes - seems odd, but perhaps that's what you're seeing?
window.onload = function() {
    var ctx = document.getElementById("canvas").getContext("2d");
    window.myBar = new Chart(ctx, {
        type: 'bar',
        data: barChartData,
        options: {
            title:{
                display:true,
                text:"Chart.js Bar Chart - Stacked"
            },
            tooltips: {
                mode: 'index',
                intersect: false
            },
            responsive: true,
            scales: {
                xAxes: [{
                    stacked: true,
                }],
                yAxes: [{
                    stacked: true
                }]
            }
        }
    });
};

Hello @tiesont I've tried with both stacked true and behaviour persists

@jungleBadger Don't suppose that you could create a jsFiddle (or similar) that reproduces what you're seeing?

@jungleBadger you need stacked: true on both x and y axes (fiddle 2.6.0)
@tiesont I agree that editable snippets in the example would be nice (that could be a new ticket)

@simonbrunel I'll create an issue for that, then.

Hey Guys I believe you are right about the snippet and I apologize for not doing so.
Besides that I can make this work using 2.5.0 only. Even with stacked true on both axes - I will keep looking into it since the fiddle worked.
Many thanks.

This is how stacked works on both axes in 2.6.0:

@jungleBadger you can still create a fiddle with your code


README example wants formSubmitted on controller

I wasn't able to get the README example to work unless I added formSubmitted: null to the new controller.  Without it, I got Property set failed: object in path "controller" could not be found or was destroyed. — I guess because the Submitting mixin aliases against it?

Seems like a bug to me - thanks for opening the issue! I'll look into it today or tomorrow.

I noticed a few typos in the docs that might have led to this error - they were fixed with #3. The Saving mixin has formSubmitted: false so if that's mixed into the associated controller you shouldn't get the error. I wasn't able to replicate the issue otherwise.
Please let me know if the issue still persists with the latest version and docs.


Added full changelog link to github release description

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report

Merging #183 (3fb3254) into master (ff83236) will increase coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #183      +/-   ##
==========================================
+ Coverage   53.66%   53.88%   +0.22%
==========================================
  Files         142      140       -2
  Lines       15891    15851      -40
==========================================
+ Hits         8528     8542      +14
+ Misses       6902     6857      -45
+ Partials      461      452       -9

Flag
Coverage Δ

1.14.x
27.99% <ø> (+0.13%)
:arrow_up:

1.15.x
27.91% <ø> (+0.04%)
:arrow_up:

1.16.x
27.91% <ø> (+0.04%)
:arrow_up:

1.17.x
53.83% <ø> (+0.16%)
:arrow_up:

connection
14.61% <ø> (ø)

discovery
13.49% <ø> (ø)

e2e
47.00% <ø> (+0.06%)
:arrow_up:

integration
47.00% <ø> (+0.06%)
:arrow_up:

macOS-latest
?

ratelimiter
15.93% <ø> (ø)

scripting
16.32% <ø> (ø)

table
41.02% <ø> (+0.04%)
:arrow_up:

ubuntu-latest
53.88% <ø> (+0.12%)
:arrow_up:

unit
27.99% <ø> (+0.13%)
:arrow_up:

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

log/table.go
78.33% <0.00%> (-1.31%)
:arrow_down:

...d/gtrace/internal/test/test_gtrace_darwin_amd64.go

cmd/gtrace/internal/test/test_gtrace_windows.go

internal/table/session.go
76.65% <0.00%> (+1.17%)
:arrow_up:

internal/db/database.go
67.74% <0.00%> (+3.22%)
:arrow_up:

internal/conn/conn.go
83.48% <0.00%> (+4.58%)
:arrow_up:

Continue to review full report at Codecov.

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


How different will Taskboard re-write will be from Kansha?

Hi,
I am following your great work and I like it :)
I am just wondering how far Taskboard would be different from Kansha?
On my point of view it seems very close.
Just want to get your opinion.
many thanks

I had never heard of Kansha before, interesting.
TaskBoard will definitely have things in common with Kansha, as they are both kanban-style boards.
I just messed around with their demo, and found it very different from TaskBoard in the way it behaves and presents itself to the user. Which one is better is a matter for the user to decide.


update Shaanxi Normal University and hohai university licenses

the domain of Shaanxi Normal University is snnu.edu.cn
the domain of Hohai University is hhu.edu.cn
previous snnu.txt and hhu.txt is wrong

@chwjun I am sorry, the domain hhu.edu.cn is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).

  thanks for your reply very much, the another question is why the domain of snnu.edu.cn can't work , i am a student from shaanxi normal university , the email address can be registered only if you are a student.
The Lion King
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "JetBrains/swot"                                                                                @.>;
发送时间: 2023年8月9日(星期三) 中午11:33
@.>;
抄送: "The Lion<EMAIL_ADDRESS>主题: Re: [JetBrains/swot] update Shaanxi Normal University and hohai university licenses (PR #18262)
@chwjun I am sorry, the domain hhu.edu.cn is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Support transliteration to ASCII to avoid extended characters in Java source code

Hi,
again a german issue. If I define an enum with words that contain umlauts:
"enum" : ["Herr", "Frau", "Fräulein"],
the class is generated, but cannot be compiled because it generates an enum with an invalid name:
FRÃ„ULEIN("Fr\u00e4ulein");
What can I do to avoid that issue?

This hasn't been much of a problem after all. No intention of implementing this at present because it doesn't seem to affect enough people.


Write a Ruby program to find roots of quadratic equation

Description
Write a Ruby program to find roots of quadratic equation
Use the quadratic formula to find the roots of the quadratic equation
x = $(-b &plusmn \sqrt(b^2 - 4ac))/2a$
The input will be the coefficients of $x^2$, $x$, and the constant $c$.
Input  : 1 2 1
Output : -1 -1

Contributed by - @PavanKumarCB

How to contribute

Save the solution in FindRootsOfQuadraticEquation.rb file
Add FindRootsOfQuadraticEquation.rb file in program/find-roots-of-quadratic-equation folder

!assign


That uses a moog filter emulation?

Thanks for posting those files! I've been looking for a nice intro to PCM style programming on an MCU.
That is a moog filter emulation or a diode ladder?

@01GOD currently default is set to tb303 emulation mostly taken from open303 project. But if you are interested, there're config options in synthvoice.h as I remember to use moog and some other variants, but they may require level tuning.


bump version to v0.1.5

since v0.1.4:
Merge pull request #592 from omisego/591_malformed_txs_for_IFEs
Merge pull request #596 from omisego/589-fix-transaction-all
Merge pull request #600 from omisego/add_migration_to_launcher
Merge pull request #612 from omisego/cherry_pick_add_depl_marker
Merge pull request #607 from omisego/601-status-content-type
Merge pull request #604 from omisego/refactor-swagger-doc
Merge pull request #641 from omisego/fix_spend_not_found
Merge pull request #661 from omisego/parallel_builds
Merge pull request #664 from omisego/enable_introspection
Merge pull request #669 from omisego/update_launcher

Coverage remained the same at 73.239% when pulling fd14eb5abfd304c2608b411bd59e0b7f3a1c10d0 on bump_version_to_0.1.5 into d22e9cb43153ca62e1e55c78edbd9d61e05b0c82 on v0.1.

Coverage remained the same at 73.239% when pulling fd14eb5abfd304c2608b411bd59e0b7f3a1c10d0 on bump_version_to_0.1.5 into d22e9cb43153ca62e1e55c78edbd9d61e05b0c82 on v0.1.


Sending packet from android to esp32 with same MAC is received once!!

Hello,
I made an app on android that sends BLE beacons to the esp32, that is scanner later in esp32.
The problem is when the App starts sending multiple beacons with the same MAC address, they are filtered as 1 packet only by esp32.
I searched in filter and tried to change a lot of parameters but no improvement.
Anyone have an idea regardging this issue.

I believe the scan method ignores repeated devices and it's the intended behaviour.
You could try using ```
BLEScan::clearResults()


Automatically lower case rancher catalog template names

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
add jenkins-x catalog url: https://github.com/jenkins-x/jenkins-x-platform
exception in rancher logs:
[ERROR] CatalogController jenkinsx [catalog] failed with : failed to update templates. Multiple error occurred: [TemplateVersion.management.cattle.io "jenkinsx-jenkins-x-platform-0.0.1-SNAPSHOT" is invalid: metadata.name: Invalid value: "jenkinsx-jenkins-x-platform-0.0.1-SNAPSHOT": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')] 2019/04/15 09:07:59 [INFO] Catalog sync done. 0 templates created, 4 templates updated, 0 templates deleted
Result: catalog doesn't sync when chart version in chart.yaml is in uppercase characters the issue reproduced.
expected behavior :
manipulate chart.yaml version to lower case to avoid the issue.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.1.8 stable
Installation option (single install/HA): HA

Cluster information

Cluster type: Hosted
Machine type: Metal
Kubernetes version: 1.13.5

@deniseschannon ,
is there any estimation to fix this issue?
sill happen in version 2.2.8

This Pull Request should fix the problem:
https://github.com/rancher/rancher/pull/26703

New PR https://github.com/rancher/rancher/pull/26943

Reopening due to unable to deploy app
The catalog is now able to be added, but when navigating to Apps > Launch and trying to deploy the app from this catalog, it fails with the same error:

This happens in both master-2939-head and v2.4-2941-head

Validated in both v2.4-head and master-head

The original error does not appear when adding the catalog
Apps do not have the error mentioned in the reopening of this issue: https://github.com/rancher/rancher/issues/19615#issuecomment-626007957

I'd like to note that this specific Jenkins-X chart is trying to do a helm install, when jenkins x should use jx to install. Therefore, there are other errors that happen when installing this chart. However, the catalog is present in etcd.


Fixed UI For Dark-Mode : Closes #1154-->The Link "Prepare For the Github Foundation exam" gets disappeared when we switch to dark-mode

Fix #1154
Bug
The Link "Prepare For the Github Foundation exam" gets disappeared when we switch to dark-mode
Image 1

Image 2

After Fix
Image 1

Image 2

@sanjay-kv Please Check The Above Pull Request


Need Spacebar definition to dismiss dialog

tap(" ") doesn't do it.  Are there other constants that I just don't know?

Fixed on latest master.


Numaresource Operator Serial Test Improvements

This patch is to make the test suite more robust.
Rather than using hardcoded scheduler name, we obtain it from
the numaresourcesscheduler CR.
In addition to that, we perform a check to make sure that in case
pod event checks return no events, we print a warning as that could
indicate misconfiguration in the cluster.
Signed-off-by: Swati Sehgal<EMAIL_ADDRESS>

/cc @fromanirh

Thanks for the review @fromanirh and @shajmakh. Moving the PR to WIP as I am working on addressing the review comments.

@fromanirh @shajmakh This PR is ready for another round of review.

thanks for the changes, looks good to me but let's wait for Francesco's review


Some non-extractable strings on the Majiro script

script file :  start.mjo.zip
Game : サナララR (Sanarara R)
I found the "現在は選択できません" string encoded in shift-jis as a hex editor.
And when I replaced it with a Korean string(현재는 선택불가) encoded through euc-kr, I found that it changed.
However, the VNTextPatch tool cannot extract a string.
Attach additional scripts for the same issue. ↓

script file :  1_02.mjo.zip
神の使い（但し自己脳内で）

Fixed.


Update assets and add some design tweaks

[x] Update refresh icon to support retina display
[x] Add some spaces and edit font-face:

@shahruz

unistall isn't a word .-.

LoL

LoL of the rings

But this is not the original repo! If you scroll top, it shows @sharuz forked it from @buzzfeed...
I think we're filing bugs on the wrong repo!

@revelt check the PR on the original repo and the latest commit..

@equinusocio I'm very grateful for your and everybody's contributions on this fork. I do see that it's more alive then original. Anyway, I'm concerned because ideally there should be only one master repo where issues are tracked. It's especially important for this library because it's like Sublime Text's Package Manager - an essential thing. My existing plugins didn't sync with Toolbox and I'm still perplexed what to do about it.

@equinusocio wew

I'm switched to sketchpacks


Waterfall chart throws Zipped file not found: ppt/charts/chartNaN.xml

Hi, very cool library! Unfortunately, I encountered an issue that prevents me from using waterfall charts.
Stack trace
(node:4420) UnhandledPromiseRejectionWarning: Error: Zipped file not found: ppt/charts/chartNaN.xml
    at Function.<anonymous> (/node_modules/pptx-automizer/src/helper/file-helper.ts:56:13)
    at Generator.next (<anonymous>)
    at /node_modules/pptx-automizer/dist/helper/file-helper.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/node_modules/pptx-automizer/dist/helper/file-helper.js:4:12)
    at Function.zipCopy (/node_modules/pptx-automizer/dist/helper/file-helper.js:52:16)
    at Chart.<anonymous> (/node_modules/pptx-automizer/dist/shapes/chart.js:149:44)
    at Generator.next (<anonymous>)
    at /node_modules/pptx-automizer/dist/shapes/chart.js:8:71
    at new Promise (<anonymous>)

Steps to reproduce:

create a new presentation called "root.xlsx" with one slide
create a new presentation called "waterfall.xlsx", add a waterfall chart to it and call it "WATERFALL"
try adding the slide from "waterfall" to "root"
Error: Zipped file not found: ppt/charts/chartNaN.xml

Minimal code
const ppt = Automizer.loadRoot('root.pptx').load('waterfall.pptx', 'waterfall');

ppt.addSlide('waterfall', 1, (slide) => {
    slide.modifyElement('WATERFALL', [
        modify.setChartData({
            series: [{ label: 'Value' }],
            categories: [
                { label: 'Revenue', values: [500] },
                { label: 'Cost', values: [-100] },
                { label: 'Profit', values: [400] },
            ],
        }),
    ]);
}

const summary = await ppt.write('test.pptx');
console.log(summary);

System
macOS Monterey v12.6
PowerPoint for Mac v16.66 (22100900)

Hi! I'm glad you like pptx-automizer! :)
I did not test the library against waterfall charts, i need to dig deeper into this. My first impression: automizer usually manipulates ppt/charts/chart1.xml, but waterfall uses ppt/charts/chartEx1.xml. I did not expect to have different filenames, but take a look at modifyChartData() in src/shapes/chart.ts. I guess it needs to fork the filename depending on the type of chart.

I'm still working on this in a seperate branch, but it requires some refactoring. This problem also affects e.g. map charts, needs to be solved.

Hi, any update on this issue?

Hi, I'm very busy at the moment, but I'll try to solve this by the end of the week.

Hi @AlexanderKulia, I could make some steps towards chartEx implementation, but it's not finished yet. You can run dev.ts: The first series and all categories are added properly, but ppt will give you a "repair"-message. It might be related to cx:subtotals in \ppt\charts\chartEx1.xml, but I'm not sure on this.

This should work now! Please test it with your custom waterfall chart.
Use a modifier like this:
slide.addElement('ChartWaterfall', 1, 'Waterfall 1', [
    modify.setExtendedChartData(<ChartData>{
          series: [{ label: 'series 1' }],
          categories: [
            { label: 'cat 2-1', values: [100] },
            { label: 'cat 2-2', values: [20] },
            { label: 'cat 2-3', values: [50] },
            { label: 'cat 2-4', values: [-40] },
            { label: 'cat 2-5', values: [130] },
            { label: 'cat 2-6', values: [-60] },
            { label: 'cat 2-7', values: [70] },
            { label: 'cat 2-8', values: [140] },
        ],
    }),
]);

Please notice:

You need to use setExtendedChartData instead of setChartData
At the moment, it is required to place (at least) a blank space into cell A1 of your template's datasheet to avoid a problem with editing data.
There is currently no modifier available for cx:subtotals. Please give me a hint how to implement this properly.

I have only tested ppt's default waterfall chart. Please let me know if this works for your stuff, too :smiley:
PS: Please excuse the confusing merges an PRs, I'm still practising on how to keep branches in sync. :sweat_smile:

hey, thank you for the update. will check the changes on the weekend and let you know

hi @singerla I was able to add a waterfall chart and it looks good to me. however I noticed that I cannot view Excel data by right clicking on the newly added waterfall chart. Excel just opens its default page, not the data sheet
Can you reproduce the issue at you end?
import Automizer, { ChartData, modify } from './index';

const automizer = new Automizer({
  templateDir: '.',
  outputDir: '.',
});

const main = async () => {
  const ppt = automizer.loadRoot('root.pptx').load('charts.pptx', 'charts');

  ppt.addSlide('charts', 1, (slide) => {
    slide.addElement('charts', 1, 'WATERFALL', [
      modify.setExtendedChartData(<ChartData>{
        series: [{ label: 'VALUE' }],
        categories: [
          { label: 'CAT1', values: [856] },
          { label: 'CAT2', values: [-760] },
          { label: 'CAT3', values: [96] },
        ],
      }),
    ]);
  });

  const res = await ppt.write('out.pptx');
  console.log(res);
};

main();

I'm sorry, can't reproduce with __tests__/pptx-templates/ChartWaterfall.pptx. Must be something inside your customized template. Did you notice:

At the moment, it is required to place (at least) a blank space into cell A1 of your template's datasheet to avoid a problem with editing data.

Excel tells you more about errors inside a file: You can unzip your output-pptx an go to embeddings-directory. Open the the files with a -created-flag and take a look at the message excel throws.

My bad, I thought A1 wasn't empty but it was. Editing works now 👍

Allright, I'm glad to hear :)
We need to handle empty cells properly, please take a look at #39.
Thanks a lot again for mentioning this issue!


support node version >= 1.0.0

npm will check package.json 'engines' property, need to add node version 1.0.0 support for iojs.
npm install --build-from-source --registry=http://registry.npm.taobao.org --disturl=http://npm.taobao.org/mirrors/iojs sqlite3@3
npm ERR! Darwin 14.0.0
npm ERR! argv "/Users/mk2/git/nvm/versions/io.js/v1.0.4/bin/iojs" "/Users/mk2/git/nvm/versions/io.js/v1.0.4/bin/npm" "install" "--build-from-source" "--registry=http://registry.npm.taobao.org" "--disturl=http://npm.taobao.org/mirrors/iojs" "sqlite3@3"
npm ERR! node v1.0.4
npm ERR! npm  v2.3.0
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS><4.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["2.2.4","2.2.1","2.1.16","2.1.14","2.1.1","2.2.3","2.2.2","2.2.0","2.1.19","2.1.18","2.1.17","2.1.15","2.1.13","2.1.12","2.1.9","2.1.7","2.1.11","2.0.18","2.1.10","2.1.4","2.1.8","2.1.5","2.1.3","2.1.2","2.1.0","2.0.17","2.0.16","2.0.15","2.0.14","2.0.13","2.0.12","2.0.11","2.0.10","2.0.9","2.0.8","2.0.7","2.0.6","2.0.5","2.0.4","2.0.3","2.0.2","2.0.1","2.0.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

I need to fix the ci tests

All builld pass finally

thanks, as you saw I've integrated your comments and they are now in master.

Changes Unknown when pulling 1c0331c6486636f5ac3a49efaf5ebe1b501dc32a on fengmk2:support-iojs-version into ** on mapbox:master**.


Trying to get it working

Hi! I'm trying to use your package to finally get H5P content integrated on a laravel project.
I tried some approaches and I can't get it working properly :(
If I try to require it on a laravel 5.7 or 5.8 instance, I always get a composer error:

Your requirements could not be resolved to an installable set of packages.
Problem 1
- djoudi/laravel-h5p 1.0 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- Conclusion: don't install laravel/framework 5.5.x-dev
- Can only install one of: laravel/framework[v5.8.30, 5.7.x-dev].
- Can only install one of: laravel/framework[5.7.x-dev, v5.8.30].
- Can only install one of: laravel/framework[5.7.x-dev, v5.8.30].
- djoudi/laravel-h5p 1.0.x-dev requires laravel/framework 5.7.* -> satisfiable by laravel/framework[5.7.x-dev].
- Installation request for djoudi/laravel-h5p ^1.0 -> satisfiable by djoudi/laravel-h5p[1.0, 1.0.x-dev].
- Installation request for laravel/framework (locked at v5.8.30, required as 5.8.*) -> satisfiable by laravel/framework[v5.8.30].

Even i a new laravel instance.
Then I tried to do it on a laravel 5.5 instance. I got this installed but I simply can't get the proper layout working (as I saw in some screenshots here), neither i can access the create page where I get the H5PFrameworkInterface compatibility error reported here: https://github.com/djoudi/Laravel-H5P/issues/12
I'm on this subject for quite a while now. Any help please. Thanks.

I'm still getting the same error about H5PFrameworkInterface. I had a little more success using version 2.0 of this package with Laravel 5.8, but didn't manage to upload a library or create a content yet.
Moving the css and js folders inside the assets folder should fix the layout problem.


Added Icons to Navbar

Related Issue
Icons absent in Navbar section
Fixes: Added icons to navbar
Description
Added attractive icons to the NavLinks present on the navbar section.
#3019
Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[X] I have made this change from my own.
[X] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

Please review the PR and let me know if any additional changes are required

not looking good @Devaki01


Core Github Actions for Test, Publish and Docs

Status
READY
Description
This PR adds the following GitHub Actions:

Documentation building and deploying on github pages
Linting & Testing of Core library and Extensions
Publishing to pypi

Currently the publish is pointing at the test pypi instance. Once we've merged this over, we can configure within the main ibm-generative-ai repository.
Impacted Areas in Library

Build

Which issue(s) does this pull-request fix?
Closes: IBM/ibm-generative-ai#4
Any special notes for your reviewer?

Checklist

[x] Automated tests exist
[x] Updated Package Requirements (if required, and with maintainers' approval)
[x] Local unit tests performed
[x] Documentation exists link
[x] Local pre-commit hooks performed
[x] Desired commit message set as PR title and description set above
[x] Link to relevant GitHub issue provided

A few questions regarding the documentation build + gh pages:

Currently the github pages is being rendered from the branch docs is this still going to be the case are we going to change branch?
We are also rendering the github pages from root, will the gh action take care of arranging file hierarchy as expected?

A few questions regarding the documentation build + gh pages:
* Currently the github pages is being rendered from the branch `docs` is this still going to be the case are we going to change branch?

With GitHub actions, the branch / directory method is no longer required, it effectively pushes the artifacts straight to their hosting.

* We are also rendering the github pages from root, will the gh action take care of arranging file hierarchy as expected?

Yes, we just tell it where the html is located (https://github.com/IBM/ibm-generative-ai/pull/5/files#diff-d7ecc9db1d2f1f75440ba2c3e433aec8c252e9c86a6260732400737857c71d3b)

You can see it running here: https://jpwsutton.github.io/ibm-generative-ai/#id1


Package import specifier "#internal/nitro" is not defined in package

Environment

Operating System: Darwin
Node Version:     v18.13.0
Nuxt Version:     3.4.1
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, ionic
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
When running npm run generate using the Ionic VScode plugin to build and serving the files.
Describe the bug
500
Package import specifier "#internal/nitro" is not defined in package removed/package.json imported from removed/.nuxt/dist/server/server.mjs
at new NodeError (node:internal/errors:400:5)
at importNotDefined (node:internal/modules/esm/resolve:350:10)
at packageImportsResolve (node:internal/modules/esm/resolve:777:9)
at moduleResolve (node:internal/modules/esm/resolve:932:16)
at defaultResolve (node:internal/modules/esm/resolve:1153:11)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:842:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ModuleWrap. (node:internal/modules/esm/module_job:77:40)
at link (node:internal/modules/esm/module_job:76:36)
Additional context
When I run npm run dev everything works fine, also if I use Ionic to run without building first.
As mentioned, Ionic uses npm run generate as specified in package.json: "ionic:build": "npm run generate".
Logs
From Ionic Output
[npm] [nuxt] [request error] [unhandled] [500] Package import specifier "#internal/nitro" is not defined in package /Users/anderslutzhoft/Webapps/caloryai/package.json imported from /Users/anderslutzhoft/Webapps/caloryai/.nuxt/dist/server/server.mjs
[npm]   at new NodeError (node:internal/errors:400:5)
[npm]   at importNotDefined (node:internal/modules/esm/resolve:350:10)
[npm]   at packageImportsResolve (node:internal/modules/esm/resolve:777:9)
[npm]   at moduleResolve (node:internal/modules/esm/resolve:932:16)
[npm]   at defaultResolve (node:internal/modules/esm/resolve:1153:11)
[npm]   at nextResolve (node:internal/modules/esm/loader:163:28)
[npm]   at ESMLoader.resolve (node:internal/modules/esm/loader:842:30)
[npm]   at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
[npm]   at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
[npm]   at link (node:internal/modules/esm/module_job:76:36)

I'm very new to development and issue reporting, so I apologize if my report is lacking. Please let me know if any additional information is needed!
I've spent a few hours searching the internet for reports on this; I found only a few, but all of them should have been fixed with earlier updated. Thus I'm experiencing this now with the latest deps, I was hoping to get some help here.

I've also made this repo to reproduce: https://github.com/anderslutzhoft/serverless-test

Thank you! I can't reproduce with your repo when running npm run generate or ionic build: see https://stackblitz.com/edit/github-bj8gbc?file=package.json.

We have the same issue on MacArm without ionic.
When we locally build a project the dev runner crashes:
[nuxt] [request error] [unhandled] [500] Package import specifier "#internal/nitro" is not defined in package ***/package.json imported from ***/.nuxt/dist/server/server.mjs
  at new NodeError (node:internal/errors:399:5)
  at importNotDefined (node:internal/modules/esm/resolve:350:10)
  at packageImportsResolve (node:internal/modules/esm/resolve:777:9)

We have this issue only on Mac (ARM?),
Linux machines don't show this error for us.
Maybe not related, but isn't it weird that nuxt imports dist files? Or is the dist server shared for the dev and build?

Thank you! I can't reproduce with your repo when running npm run generate or ionic build: see https://stackblitz.com/edit/github-bj8gbc?file=package.json.

In this reprocuce, first I exec npm run dev, it works. Then I exec npm run build, I find the development process will be affected and the browser will show 500 Error.

Yes, currently we do not support running a build while running a dev server as they share the same output directory. We plan to allow this, however; let's track in https://github.com/nuxt/nuxt/issues/14607.


Import: create placeholder images for files that can't be loaded (fix #1296)

Fixes #1296.
CesiumMan with its image missing in master:

And in this branch; a placeholder image is created pointing at where the image should be:

The missing texture will be reported through File > External Data > Report Missing Files. You can check what the missing file should be and put the image file there after the import to make it work.
Placeholders are created only for images from a file (ie. not from bufferView/data URIs).

Seems like a good idea.
What does the exporter do when it finds this?

Both the material setups shown in the OP export the same way: with no base color texture.

Seems OK.
Thanks !

Seems OK.
Thanks !


Explore OpenAPI spec based generation of api calls

Projects such as https://github.com/karlvr/react-redux-typescript-swagger-api-pattern allow for generation of react redux sagas for OpenAPI specifications. The product of this task should be a wiki article about potential ways in which tapis-redux can automatically generate OpenAPI interfaces and types in TypeScript either by using the above project or our own generator. Ultimately, the generated redux-saga and reducers need to be able to:

Accept configuration of URL and token headers
Accept API callback
Have selectable reducer states for API produced objects
TypeScript types for generated calls that are developer friendly for middleware and ui component consumers

Wiki: OpenAPI spec based generation

Starting new repository for tapis-typescript npm package