when I rosrun kinect2_bridge kinect2_bridge , occurs Segmentation fault (core dumped)

Two issues:

i. "rosrun kinect2_bridge kinect2_bridge", Segmentation fault (core dumped)
ii. "roslaunch kinect2_bridge kinect2_bridge.launch", [FATAL] [1527649735.162269400]: Failed to load nodelet '/kinect2_bridge' of type 'kinect2_bridge/kinect2_bridge_nodelet'  to manager 'kinect2'
iii."gdb kinect2_bridge" results are the last.
=======================================================================

fang@fang-ubuntu:~$ rosrun kinect2_bridge kinect2_bridge
[ INFO] [Kinect2Bridge::initialize] parameter:
base_name: kinect2
sensor: default
fps_limit: -1
calib_path: /home/fang/catkin_ws/iai_kinect2_catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opencl
depth_device: -1
reg_method: opencl
reg_device: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
Segmentation fault (core dumped)

==============================================================================================================================================================

fang@fang-ubuntu:~$ roslaunch kinect2_bridge kinect2_bridge.launch
... logging to /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/roslaunch-fang-ubuntu-2606.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started
roslaunch server http://fang-ubuntu:34707/
SUMMARY
PARAMETERS

/kinect2_bridge/base_name: kinect2
/kinect2_bridge/base_name_tf: kinect2
/kinect2_bridge/bilateral_filter: True
/kinect2_bridge/calib_path: /home/fang/catkin...
/kinect2_bridge/depth_device: -1
/kinect2_bridge/depth_method: default
/kinect2_bridge/edge_aware_filter: True
/kinect2_bridge/fps_limit: -1.0
/kinect2_bridge/jpeg_quality: 90
/kinect2_bridge/max_depth: 12.0
/kinect2_bridge/min_depth: 0.1
/kinect2_bridge/png_level: 1
/kinect2_bridge/publish_tf: False
/kinect2_bridge/queue_size: 5
/kinect2_bridge/reg_device: -1
/kinect2_bridge/reg_method: default
/kinect2_bridge/sensor:
/kinect2_bridge/use_png: False
/kinect2_bridge/worker_threads: 4
/kinect2_points_xyzrgb_hd/queue_size: 5
/kinect2_points_xyzrgb_qhd/queue_size: 5
/kinect2_points_xyzrgb_sd/queue_size: 5
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/
kinect2 (nodelet/nodelet)
kinect2_bridge (nodelet/nodelet)
kinect2_points_xyzrgb_hd (nodelet/nodelet)
kinect2_points_xyzrgb_qhd (nodelet/nodelet)
kinect2_points_xyzrgb_sd (nodelet/nodelet)
auto-starting new master
process[master]: started with pid [2636]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to c7e59464-63b6-11e8-8e01-705a0f426a43
process[rosout-1]: started with pid [2649]
started core service [/rosout]
process[kinect2-2]: started with pid [2652]
process[kinect2_bridge-3]: started with pid [2653]
process[kinect2_points_xyzrgb_sd-4]: started with pid [2654]
process[kinect2_points_xyzrgb_qhd-5]: started with pid [2655]
process[kinect2_points_xyzrgb_hd-6]: started with pid [2656]
[ INFO] [1527649733.188623786]: Loading nodelet /kinect2_bridge of type kinect2_bridge/kinect2_bridge_nodelet to manager kinect2 with the following remappings:
[ INFO] [1527649733.192839128]: waitForService: Service [/kinect2/load_nodelet] has not been advertised, waiting...
[ INFO] [1527649733.279522688]: Initializing nodelet with 8 worker threads.
[ INFO] [1527649733.298373143]: waitForService: Service [/kinect2/load_nodelet] is now available.
[ INFO] [1527649734.244030497]: [Kinect2Bridge::initialize] parameter:
base_name: kinect2
sensor: default
fps_limit: -1
calib_path: /home/fang/catkin_ws/iai_kinect2_catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: default
depth_device: -1
reg_method: default
reg_device: -1
max_depth: 12
min_depth: 0.1
queue_size: 5
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
[FATAL] [1527649735.162269400]: Failed to load nodelet '/kinect2_bridgeof typekinect2_bridge/kinect2_bridge_nodeletto managerkinect2'
[kinect2-2] process has died [pid 2652, exit code -11, cmd /opt/ros/indigo/lib/nodelet/nodelet manager __name:=kinect2 __log:=/home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2-2.log].
log file: /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2-2*.log
[kinect2_bridge-3] process has died [pid 2653, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load kinect2_bridge/kinect2_bridge_nodelet kinect2 __name:=kinect2_bridge __log:=/home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2_bridge-3.log].
log file: /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2_bridge-3*.log
[kinect2_bridge-3] restarting process
process[kinect2_bridge-3]: started with pid [2884]
[ INFO] [1527649735.489066003]: Loading nodelet /kinect2_bridge of type kinect2_bridge/kinect2_bridge_nodelet to manager kinect2 with the following remappings:
[ INFO] [1527649735.491047558]: waitForService: Service [/kinect2/load_nodelet] could not connect to host [fang-ubuntu:47353], waiting...
[kinect2_points_xyzrgb_sd-4] process has finished cleanly
log file: /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2_points_xyzrgb_sd-4*.log
[kinect2_points_xyzrgb_qhd-5] process has finished cleanly
log file: /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2_points_xyzrgb_qhd-5*.log
[kinect2_points_xyzrgb_hd-6] process has finished cleanly
log file: /home/fang/.ros/log/c7e59464-63b6-11e8-8e01-705a0f426a43/kinect2_points_xyzrgb_hd-6*.log
[kinect2_points_xyzrgb_sd-4] restarting process
process[kinect2_points_xyzrgb_sd-4]: started with pid [3373]
[kinect2_points_xyzrgb_qhd-5] restarting process
process[kinect2_points_xyzrgb_qhd-5]: started with pid [3374]
[kinect2_points_xyzrgb_hd-6] restarting process
process[kinect2_points_xyzrgb_hd-6]: started with pid [3375]
^C[kinect2_points_xyzrgb_hd-6] killing on exit
[kinect2_points_xyzrgb_qhd-5] killing on exit
[kinect2_points_xyzrgb_sd-4] killing on exit
[kinect2_bridge-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

==================================================================================================================================================================

fang@fang-ubuntu:/catkin_ws/iai_kinect2_catkin_ws/devel/lib/kinect2_bridge$ gdb kinect2_bridge
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kinect2_bridge...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/fang/catkin_ws/iai_kinect2_catkin_ws/devel/lib/kinect2_bridge/kinect2_bridge
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdfefc700 (LWP 32592)]
[New Thread 0x7fffdee0e700 (LWP 32593)]
[New Thread 0x7fffde60d700 (LWP 32594)]
[New Thread 0x7fffdde0c700 (LWP 32595)]
[ERROR] [registerPublisher] Failed to contact master at [localhost:11311].  Retrying...
[ INFO] Connected to master at [localhost:11311]
[New Thread 0x7fffdd60b700 (LWP 32700)]
[New Thread 0x7fffd7fff700 (LWP 32701)]
[ INFO] [Kinect2Bridge::initialize] parameter:
base_name: kinect2
sensor: default
fps_limit: -1
calib_path: /home/fang/catkin_ws/iai_kinect2_catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opencl
depth_device: -1
reg_method: opencl
reg_device: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
[New Thread 0x7fffc3ba6700 (LWP 32744)]
Program received signal SIGSEGV, Segmentation fault.
0x00007fffd45716f1 in llvm::cl::AddLiteralOption(llvm::cl::Option&, char const*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
(gdb) bt
#0  0x00007fffd45716f1 in llvm::cl::AddLiteralOption(llvm::cl::Option&, char const*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
#1  0x00007fffbfce2f4c in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1
#2  0x00007ffff7dea1da in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffffffd968, env=env@entry=0x6ca4c0) at dl-init.c:78
#3  0x00007ffff7dea2c3 in call_init (env=, argv=, argc=, l=) at dl-init.c:36
#4  _dl_init (main_map=main_map@entry=0x6db670, argc=1, argv=0x7fffffffd968, env=0x6ca4c0) at dl-init.c:126
#5  0x00007ffff7deed00 in dl_open_worker (a=a@entry=0x7fffffffb088) at dl-open.c:577
#6  0x00007ffff7dea094 in _dl_catch_error (objname=objname@entry=0x7fffffffb078, errstring=errstring@entry=0x7fffffffb080,
mallocedp=mallocedp@entry=0x7fffffffb070, operate=operate@entry=0x7ffff7deea30 <dl_open_worker>, args=args@entry=0x7fffffffb088) at dl-error.c:187
#7  0x00007ffff7dee44b in _dl_open (file=0x7fffc2f424d8 "/usr/lib/x86_64-linux-gnu/beignet//libgbe.so", mode=-2147483647,
caller_dlopen=, nsid=-2, argc=1, argv=0x7fffffffd968, env=0x6ca4c0) at dl-open.c:661
#8  0x00007fffeacca02b in dlopen_doit (a=a@entry=0x7fffffffb2a0) at dlopen.c:66
#9  0x00007ffff7dea094 in _dl_catch_error (objname=0x66cae0, errstring=0x66cae8, mallocedp=0x66cad8, operate=0x7fffeacc9fd0 <dlopen_doit>,
args=0x7fffffffb2a0) at dl-error.c:187
#10 0x00007fffeacca62d in _dlerror_run (operate=operate@entry=0x7fffeacc9fd0 <dlopen_doit>, args=args@entry=0x7fffffffb2a0) at dlerror.c:163
#11 0x00007fffeacca0c1 in __dlopen (file=, mode=) at dlopen.c:87
#12 0x00007fffc2f26853 in GbeLoaderInitializer::LoadCompiler() () from /usr/lib/x86_64-linux-gnu/beignet//libcl.so
#13 0x00007fffc2f1add7 in ?? () from /usr/lib/x86_64-linux-gnu/beignet//libcl.so
#14 0x00007ffff7dea1da in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffffffd968, env=env@entry=0x6ca4c0) at dl-init.c:78
#15 0x00007ffff7dea2c3 in call_init (env=, argv=, argc=, l=) at dl-init.c:36
#16 _dl_init (main_map=main_map@entry=0x6da840, argc=1, argv=0x7fffffffd968, env=0x6ca4c0) at dl-init.c:126
#17 0x00007ffff7deed00 in dl_open_worker (a=a@entry=0x7fffffffb588) at dl-open.c:577
#18 0x00007ffff7dea094 in _dl_catch_error (objname=objname@entry=0x7fffffffb578, errstring=errstring@entry=0x7fffffffb580,
mallocedp=mallocedp@entry=0x7fffffffb570, operate=operate@entry=0x7ffff7deea30 <dl_open_worker>, args=args@entry=0x7fffffffb588) at dl-error.c:187
---Type  to continue, or q  to quit---
#19 0x00007ffff7dee44b in _dl_open (file=0x7af560 "/usr/lib/x86_64-linux-gnu/beignet//libcl.so", mode=-2147483647, caller_dlopen=,
nsid=-2, argc=1, argv=0x7fffffffd968, env=0x6ca4c0) at dl-open.c:661
#20 0x00007fffeacca02b in dlopen_doit (a=a@entry=0x7fffffffb7a0) at dlopen.c:66
#21 0x00007ffff7dea094 in _dl_catch_error (objname=0x66cae0, errstring=0x66cae8, mallocedp=0x66cad8, operate=0x7fffeacc9fd0 <dlopen_doit>,
args=0x7fffffffb7a0) at dl-error.c:187
#22 0x00007fffeacca62d in _dlerror_run (operate=operate@entry=0x7fffeacc9fd0 <dlopen_doit>, args=args@entry=0x7fffffffb7a0) at dlerror.c:163
#23 0x00007fffeacca0c1 in __dlopen (file=, mode=) at dlopen.c:87
#24 0x00007fffedfd12fb in ?? () from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
#25 0x00007fffedfd1459 in ?? () from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
#26 0x00007fffedfd19c2 in ?? () from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
#27 0x00007fffedfd2233 in clGetPlatformIDs () from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
#28 0x00007ffff56d77f6 in cl::Platform::get (platforms=platforms@entry=0x7fffffffba00)
at /home/fang/tools/libfreenect2/include/internal/CL/cl.hpp:2338
#29 0x00007ffff56d94e5 in libfreenect2::OpenCLDepthPacketProcessorImpl::initDevice (this=this@entry=0x6a1920, deviceId=deviceId@entry=-1)
at /home/fang/tools/libfreenect2/src/opencl_depth_packet_processor.cpp:431
#30 0x00007ffff56d9e9c in libfreenect2::OpenCLDepthPacketProcessorImpl::OpenCLDepthPacketProcessorImpl (this=0x6a1920, deviceId=-1)
at /home/fang/tools/libfreenect2/src/opencl_depth_packet_processor.cpp:245
#31 0x00007ffff56d3ff1 in libfreenect2::OpenCLDepthPacketProcessor::OpenCLDepthPacketProcessor (this=0x6a01e0, deviceId=-1)
at /home/fang/tools/libfreenect2/src/opencl_depth_packet_processor.cpp:721
#32 0x00007ffff56b6336 in libfreenect2::OpenCLPacketPipeline::OpenCLPacketPipeline (this=0x65b040, deviceId=-1)
at /home/fang/tools/libfreenect2/src/packet_pipeline.cpp:151
#33 0x00000000004138f8 in Kinect2Bridge::initPipeline(std::string const&, int) ()
#34 0x00000000004292f4 in Kinect2Bridge::initialize() ()
---Type  to continue, or q  to quit---q
Quit
(gdb) q
A debugging session is active.
Inferior 1 [process 32578] will be killed.
Quit anyway? (y or n) y

===============================================================================
These troubles me few days, I even try every solutions only if can search on the internet, but they doesn't work. Please help me, thank you very much.

I am running into the same issues. Have you found a solution yet?


Added MTLS support

Adding MTLS support for both the dir and vhost commands.

Adds the -C switch to specify the MTLS certificate file
Adds the -K switch to specify the MTLS certificate key files

Nice! This looks like a super handy addition. Thank you :)

What is this for? Are those client certificates? We should definitely specify this in the module options more clearly

thanks this was added to the dev branch!


Recurrent Kernel Panic with 0.8.3 release

Hi @ayufan , after upgrade to last stable release 0.8.3 I have problem with Rock64. Help me pls
Diagnostic logs: http://ix.io/1OaB
Syslog events: Rock64Server kernel panic.txt

The problem is the 'uart' but was cause by a loose wires connect to pins 6, 8 and 10 but not attached to anything.
I removed those loose wires and the problem disappeared.


Fix debouncer issue

Signed-off-by: Frank Jogeleit<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 93.701%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
2172

Relevant Lines:
2318

💛  - Coveralls


Vulkan features

Add features to allow usage with Vulkan (SDL_Vulkan_GetDrawableSize, SDL_Vulkan_CreateSurface, SDL_Vulkan_GetInstanceExtensions)

Add resharper config or editorconfig if you want to keep your shitty formatting


purescript-0.15 support

This package appears to have fallen out of package-sets for purescript-0.15.  Can it be updated?

would you like to help? here's a starter kit for you to contribute the update: https://github.com/justinwoo/purescript-record-extra/tree/0.15.0-starter-kit

I can pick at it, but it will be at least a few weeks before I can get to it.  Anyway, thanks for the starter kit; that will help a lot!

I just update the FFI file to use ES modules on the 0.15.0-starter-kit branch and the tests are now passing.
I had a skim of the 0.15.0 changelog and the switch from Common JS to ES modules looked like the only breaking change.
It definitely felt too easy, but maybe this was the only change required? 😅

@jonathanlking Did you look through the migration guide? https://github.com/purescript/documentation/blob/master/migration-guides/0.15-Migration-Guide.md

@JordanMartinez Thanks for sharing the guide, I didn't, but now have! ✨
Apart from ES modules, I think the only other applicable section is on migrating to Data.Reflectable, which isn't a requirement until 0.16.0.
As get from purescript-record still uses an IsSymbol constraint (rather than Reflectable), I don't think we can drop IsSymbol from this library yet anyway?

Yeah, continue using IsSymbol for now. Switching to Data.Reflectable will happen in 0.16.0

Just a note: purescript-dissect appears to overlap significantly with this package and is in 0.15 package sets.  I've flipped to that package for my app.  Sorry.

Hello,
Anyone has code that could be merged? If not, please point me to your branch if it has some more work over Justin's https://github.com/justinwoo/purescript-record-extra/tree/0.15.0-starter-kit ? I can pick it up.

I'd also very much like a release of 0.15.0-starter-kit @jonathanlking

https://github.com/justinwoo/purescript-record-extra/releases/tag/v5.0.0


Create sequences_miray_cengil.py

Describe your changes
Checklist

[x] I have read the [CONTRIBUTING]
[x] I have performed a self-review of my own code
[x] I have run the code locally and it works as expected
[x] I have commented my code, particularly in hard-to-understand areas

Screenshots (if appropriate)

Ok, sorry I used unnecessary modules in all my codes, I removed them all. I hope it's correct this time.


Fix translating for playlist panel

The objects in the playlist panel, to the right of the main video, have the ytd-playlist-panel-video-renderer class.

Cool


Mute unused variable warning

This is fixed in #814

Ok cool, didn't see it

Reopened as per in-person discussion. This is the appropriate fix.


Notifications Error.

Notifications stopped working a few days ago.
When I click on notifications tab, the page breaks.
I've tried in other browsers and get the same issue.

Any clues from the Console or Network Tab in devtools?

Any clues from the Console or Network Tab in devtools?

This is a bug on the comment side, will get the data fixed for you.  Shoot me a DM on Discord with which email it's under .
It would be nice to handle this better on the app side, but it should not happen.


Localhost added to 'servers' list unnecessarily

https://github.com/nats-io/node-nats-streaming/issues/106

Added a test to verify we are not somehow adding a localhost entry when only servers is provided. No issue from the nats client.


Use the xyproto/env package

xyproto/env is a package that is used in production in at least company, and that is used in several open source projects and has a few (minor) advantages:

Cache the environment variables when the program is starting, for quick repeated lookups.
Use .Str() for strings, .Bool() for boolean values and .Dir() for directories, for clarity.

Also, changing:
if noprune := os.Getenv("OLLAMA_NOPRUNE"); noprune == "" {

into
if !env.Bool("OLLAMA_NOPRUNE") {

Is a change that highlights that the environment variable is being used like a boolean value, where it's either set or not.

Hi @xyproto. Thank you for the pull request. That looks like a really nifty library (and it seems like you have quite a few 😃)
Ollama strives to stick to the official Go library as much as possible (unless there's a seriously large commitment required to do so). While I could see some small performance improvements here, I don't think it warrants bringing on new dependencies. Sorry about that

@jmorganca That is understandable! Thanks for considering the PR. 🙂


Error while importing SBML in import_sbml

The function import_sbml_reactions does not have sbml_warnings defined. Fix coming soon.

Fix is up on this branch: https://github.com/biocircuits/bioscrape/tree/sbml-dev


main.sh script throw an error after entering the password for the p12 file

The script thows an error pertaining legacy flag used with openssl command in the script, right after the password for p12 file is captured. It seems to get past that error once I remove the flag. I am using RHEL 8.9. Bash is at a version in the range mentioned in the documentation. jq is there. Curl is at version level  below what was mentioned

The legacy flag was added to support P12 files which were generated using older versions of OpenSSL whenever a newer version of OpenSSL is being used.
I'll get the script updated so that it works with either new or old versions of OpenSSL.
In the meantime, you can still use the script by removing the -legacy flag from Line 24: https://github.com/EntrustCorporation/pki-utilities/blob/main/cagw-shell-util/main.sh#L24

@pchithapuram1: The latest working copy of the script has been fixed to work with both old and new versions of OpenSSL.
Download from here: https://raw.githubusercontent.com/EntrustCorporation/pki-utilities/main/cagw-shell-util/main.sh

@pchithapuram1: The latest working copy of the script has been fixed to work with both old and new versions of OpenSSL.
Download from here: https://raw.githubusercontent.com/EntrustCorporation/pki-utilities/main/cagw-shell-util/main.sh


lock timechart behind feature

just a pr for #2 which puts the timechart and timedata behind the timechart feature - more features can always be made for other charts in the future
also made the feature rely on the instant crate which works on wasm and actually doesn't add bloat on native because it falls back to the standard library

might make a PR in future to let the examples compile to wasm so there can be web demos

Will get to it tonight, thanks again!

Great!


[PUI] Auto-build frontend on update

Ref: https://github.com/inventree/InvenTree/pull/5568
Once the react frontend is "good enough" to ship, we will make the "breaking" change to the update procedure which automatically builds the react frontend

@SchrodingersGat should we maybe shift this to 0.15.0 or do you still want to ship this with 0.14.0?

I'm happy to bump it, so that we have some time to build confidence in the process

@SchrodingersGat we are now shipping the frontend ready-to-go on docker and packaged installs - can we close this?

I believe this can be closed out, yet :)


How do I directly read from RockDB data created by ARDB

I'm struggling to catch odd bug when SCAN command misses some records. I decided to read from underlying RocksDB directly to see what keys I get.
I use this library http://mvnrepository.com/artifact/org.rocksdb/rocksdbjni/5.2.1
Here is snippet of my code
    val rocksName = "/home/expert/jdata/ardb/data/data/rocksdb/"

    val options = new Options()
    org.rocksdb.RocksDB.loadLibrary()
    val cmp = new Comparator(new ComparatorOptions) {
      override def compare(a: Slice, b: Slice): Int = {
        0
      }

      override def name(): String =
        "ardb.comparator"
    }
    options.setComparator(cmp)
    val rocksdb = org.rocksdb.RocksDB.openReadOnly(options, rocksName)

    val family = rocksdb.getDefaultColumnFamily
    val seqNo = rocksdb.getLatestSequenceNumber
    val it = rocksdb.newIterator(family)
    it.seekToFirst()
    while (it.isValid) {
      println(it.key())
      it.next()
    }

I can open DB. I see that LatestSequenceNumber is roughly what I'd expect to see as number of items in my DB. But iterator is empty.
Am I doing something incorrectly with RocksDB that you specifically configured in ARDB ?
Here is what I get in RocksDB LOG file
2017/06/08-02:49:42.230154 7f423d155700 RocksDB version: 5.2.1
2017/06/08-02:49:42.230184 7f423d155700 Git sha rocksdb_build_git_sha:
2017/06/08-02:49:42.230187 7f423d155700 Compile date Apr  3 2017
2017/06/08-02:49:42.230196 7f423d155700 DB SUMMARY
2017/06/08-02:49:42.231491 7f423d155700 CURRENT file:  CURRENT
2017/06/08-02:49:42.231494 7f423d155700 IDENTITY file:  IDENTITY
2017/06/08-02:49:42.231503 7f423d155700 MANIFEST file:  MANIFEST-035032 size: 76961 Bytes
2017/06/08-02:49:42.231505 7f423d155700 SST files in /home/expert/jdata/ardb/data/data/rocksdb/ dir, Total Num: 1467, files: 007862.sst 007863.sst 009915.sst 009916.sst 010002.sst 010161.sst 010418.sst 011558.sst 011745.sst
2017/06/08-02:49:42.232450 7f423d155700 Write Ahead Log file in /home/expert/jdata/ardb/data/data/rocksdb: 035034.log size: 0 ;
2017/06/08-02:49:42.232500 7f423d155700                         Options.error_if_exists: 0
2017/06/08-02:49:42.232501 7f423d155700                       Options.create_if_missing: 1
2017/06/08-02:49:42.232502 7f423d155700                         Options.paranoid_checks: 1
2017/06/08-02:49:42.232503 7f423d155700                                     Options.env: 0x7f420fffaba0
2017/06/08-02:49:42.232504 7f423d155700                                Options.info_log: 0x7f4235900ea0
2017/06/08-02:49:42.232505 7f423d155700                          Options.max_open_files: 10000
2017/06/08-02:49:42.232505 7f423d155700                Options.max_file_opening_threads: 16
2017/06/08-02:49:42.232506 7f423d155700                         Options.disableDataSync: 0
2017/06/08-02:49:42.232507 7f423d155700                               Options.use_fsync: 0
2017/06/08-02:49:42.232508 7f423d155700                       Options.max_log_file_size: 0
2017/06/08-02:49:42.232509 7f423d155700                  Options.max_manifest_file_size:<PHONE_NUMBER>3709551615
2017/06/08-02:49:42.232510 7f423d155700                   Options.log_file_time_to_roll: 0
2017/06/08-02:49:42.232510 7f423d155700                       Options.keep_log_file_num: 1000
2017/06/08-02:49:42.232511 7f423d155700                    Options.recycle_log_file_num: 0
2017/06/08-02:49:42.232512 7f423d155700                         Options.allow_fallocate: 1
2017/06/08-02:49:42.232513 7f423d155700                        Options.allow_mmap_reads: 0
2017/06/08-02:49:42.232514 7f423d155700                       Options.allow_mmap_writes: 0
2017/06/08-02:49:42.232514 7f423d155700                        Options.use_direct_reads: 0
2017/06/08-02:49:42.232515 7f423d155700                        Options.use_direct_writes: 0
2017/06/08-02:49:42.232516 7f423d155700          Options.create_missing_column_families: 0
2017/06/08-02:49:42.232517 7f423d155700                              Options.db_log_dir:
2017/06/08-02:49:42.232518 7f423d155700                                 Options.wal_dir: /home/expert/jdata/ardb/data/data/rocksdb
2017/06/08-02:49:42.232525 7f423d155700                Options.table_cache_numshardbits: 6
2017/06/08-02:49:42.232526 7f423d155700                      Options.max_subcompactions: 1
2017/06/08-02:49:42.232527 7f423d155700                  Options.max_background_flushes: 1
2017/06/08-02:49:42.232527 7f423d155700                         Options.WAL_ttl_seconds: 0
2017/06/08-02:49:42.232528 7f423d155700                       Options.WAL_size_limit_MB: 0
2017/06/08-02:49:42.232529 7f423d155700             Options.manifest_preallocation_size: 4194304
2017/06/08-02:49:42.232530 7f423d155700                     Options.is_fd_close_on_exec: 1
2017/06/08-02:49:42.232531 7f423d155700                   Options.stats_dump_period_sec: 600
2017/06/08-02:49:42.232532 7f423d155700                   Options.advise_random_on_open: 1
2017/06/08-02:49:42.232532 7f423d155700                    Options.db_write_buffer_size: 0
2017/06/08-02:49:42.232533 7f423d155700         Options.access_hint_on_compaction_start: 1
2017/06/08-02:49:42.232534 7f423d155700  Options.new_table_reader_for_compaction_inputs: 0
2017/06/08-02:49:42.232535 7f423d155700               Options.compaction_readahead_size: 0
2017/06/08-02:49:42.232535 7f423d155700           Options.random_access_max_buffer_size: 1048576
2017/06/08-02:49:42.232554 7f423d155700           Options.writable_file_max_buffer_size: 1048576
2017/06/08-02:49:42.232555 7f423d155700                      Options.use_adaptive_mutex: 0
2017/06/08-02:49:42.232556 7f423d155700                            Options.rate_limiter: (nil)
2017/06/08-02:49:42.232557 7f423d155700     Options.sst_file_manager.rate_bytes_per_sec: 0
2017/06/08-02:49:42.232558 7f423d155700                          Options.bytes_per_sync: 0
2017/06/08-02:49:42.232558 7f423d155700                      Options.wal_bytes_per_sync: 0
2017/06/08-02:49:42.232559 7f423d155700                       Options.wal_recovery_mode: 2
2017/06/08-02:49:42.232566 7f423d155700                  Options.enable_thread_tracking: 0
2017/06/08-02:49:42.232567 7f423d155700         Options.allow_concurrent_memtable_write: 1
2017/06/08-02:49:42.232568 7f423d155700      Options.enable_write_thread_adaptive_yield: 1
2017/06/08-02:49:42.232569 7f423d155700             Options.write_thread_max_yield_usec: 100
2017/06/08-02:49:42.232569 7f423d155700            Options.write_thread_slow_yield_usec: 3
2017/06/08-02:49:42.232570 7f423d155700                               Options.row_cache: None
2017/06/08-02:49:42.232571 7f423d155700                              Options.wal_filter: None
2017/06/08-02:49:42.232572 7f423d155700             Options.avoid_flush_during_recovery: 0
2017/06/08-02:49:42.232574 7f423d155700             Options.base_background_compactions: 1
2017/06/08-02:49:42.232575 7f423d155700             Options.max_background_compactions: 1
2017/06/08-02:49:42.232575 7f423d155700             Options.avoid_flush_during_shutdown: 0
2017/06/08-02:49:42.232576 7f423d155700             Options.delayed_write_rate : 16777216
2017/06/08-02:49:42.232577 7f423d155700             Options.max_total_wal_size: 0
2017/06/08-02:49:42.232578 7f423d155700             Options.delete_obsolete_files_period_micros:<PHONE_NUMBER>0
2017/06/08-02:49:42.232579 7f423d155700 Compression algorithms supported:
2017/06/08-02:49:42.232580 7f423d155700 	Snappy supported: 1
2017/06/08-02:49:42.232581 7f423d155700 	Zlib supported: 1
2017/06/08-02:49:42.232581 7f423d155700 	Bzip supported: 1
2017/06/08-02:49:42.232582 7f423d155700 	LZ4 supported: 1
2017/06/08-02:49:42.232583 7f423d155700 	ZSTD supported: 0
2017/06/08-02:49:42.232585 7f423d155700 Fast CRC32 supported: 0
2017/06/08-02:49:42.232586 7f423d155700 Opening the db in read only mode
2017/06/08-02:49:42.234461 7f423d155700 Recovering from manifest file: MANIFEST-035032
2017/06/08-02:49:42.234535 7f423d155700 --------------- Options for column family [default]:
2017/06/08-02:49:42.234538 7f423d155700               Options.comparator: ardb.comparator
2017/06/08-02:49:42.234539 7f423d155700           Options.merge_operator: None
2017/06/08-02:49:42.234540 7f423d155700        Options.compaction_filter: None
2017/06/08-02:49:42.234540 7f423d155700        Options.compaction_filter_factory: None
2017/06/08-02:49:42.234541 7f423d155700         Options.memtable_factory: SkipListFactory
2017/06/08-02:49:42.234542 7f423d155700            Options.table_factory: BlockBasedTable
2017/06/08-02:49:42.234562 7f423d155700            table_factory options:   flush_block_policy_factory: FlushBlockBySizePolicyFactory (0x7f42358fd270)
  cache_index_and_filter_blocks: 0
  cache_index_and_filter_blocks_with_high_priority: 0
  pin_l0_filter_and_index_blocks_in_cache: 0
  index_type: 0
  hash_index_allow_collision: 1
  checksum: 1
  no_block_cache: 0
  block_cache: 0x7f42358fd0f8
  block_cache_name: LRUCache
  block_cache_options:
    capacity : 8388608
    num_shard_bits : 4
    strict_capacity_limit : 0
    high_pri_pool_ratio: 0,000
  block_cache_compressed: (nil)
  persistent_cache: (nil)
  block_size: 4096
  block_size_deviation: 10
  block_restart_interval: 16
  index_block_restart_interval: 1
  filter_policy: nullptr
  whole_key_filtering: 1
  skip_table_builder_flush: 0
  format_version: 2
2017/06/08-02:49:42.234563 7f423d155700        Options.write_buffer_size: 536870912
2017/06/08-02:49:42.234564 7f423d155700  Options.max_write_buffer_number: 5
2017/06/08-02:49:42.234566 7f423d155700          Options.compression: Snappy
2017/06/08-02:49:42.234566 7f423d155700                  Options.bottommost_compression: Disabled
2017/06/08-02:49:42.234567 7f423d155700       Options.prefix_extractor: nullptr
2017/06/08-02:49:42.234568 7f423d155700   Options.memtable_insert_with_hint_prefix_extractor: nullptr
2017/06/08-02:49:42.234569 7f423d155700             Options.num_levels: 7
2017/06/08-02:49:42.234570 7f423d155700        Options.min_write_buffer_number_to_merge: 2
2017/06/08-02:49:42.234571 7f423d155700     Options.max_write_buffer_number_to_maintain: 0
2017/06/08-02:49:42.234572 7f423d155700            Options.compression_opts.window_bits: -14
2017/06/08-02:49:42.234572 7f423d155700                  Options.compression_opts.level: -1
2017/06/08-02:49:42.234573 7f423d155700               Options.compression_opts.strategy: 0
2017/06/08-02:49:42.234574 7f423d155700         Options.compression_opts.max_dict_bytes: 0
2017/06/08-02:49:42.234575 7f423d155700      Options.level0_file_num_compaction_trigger: 4
2017/06/08-02:49:42.234576 7f423d155700          Options.level0_slowdown_writes_trigger: 20
2017/06/08-02:49:42.234576 7f423d155700              Options.level0_stop_writes_trigger: 36
2017/06/08-02:49:42.234577 7f423d155700                   Options.target_file_size_base: 67108864
2017/06/08-02:49:42.234578 7f423d155700             Options.target_file_size_multiplier: 1
2017/06/08-02:49:42.234579 7f423d155700                Options.max_bytes_for_level_base: 268435456
2017/06/08-02:49:42.234580 7f423d155700 Options.level_compaction_dynamic_level_bytes: 0
2017/06/08-02:49:42.234580 7f423d155700          Options.max_bytes_for_level_multiplier: 10,000000
2017/06/08-02:49:42.234582 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[0]: 1
2017/06/08-02:49:42.234583 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[1]: 1
2017/06/08-02:49:42.234584 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[2]: 1
2017/06/08-02:49:42.234585 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[3]: 1
2017/06/08-02:49:42.234586 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[4]: 1
2017/06/08-02:49:42.234587 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[5]: 1
2017/06/08-02:49:42.234587 7f423d155700 Options.max_bytes_for_level_multiplier_addtl[6]: 1
2017/06/08-02:49:42.234595 7f423d155700       Options.max_sequential_skip_in_iterations: 8
2017/06/08-02:49:42.234606 7f423d155700                    Options.max_compaction_bytes:<PHONE_NUMBER>
2017/06/08-02:49:42.234607 7f423d155700                        Options.arena_block_size: 67108864
2017/06/08-02:49:42.234608 7f423d155700   Options.soft_pending_compaction_bytes_limit:<PHONE_NUMBER>6
2017/06/08-02:49:42.234609 7f423d155700   Options.hard_pending_compaction_bytes_limit:<PHONE_NUMBER>44
2017/06/08-02:49:42.234610 7f423d155700       Options.rate_limit_delay_max_milliseconds: 100
2017/06/08-02:49:42.234610 7f423d155700                Options.disable_auto_compactions: 0
2017/06/08-02:49:42.234611 7f423d155700           Options.verify_checksums_in_compaction: 1
2017/06/08-02:49:42.234612 7f423d155700                         Options.compaction_style: kCompactionStyleLevel
2017/06/08-02:49:42.234614 7f423d155700                           Options.compaction_pri: kByCompensatedSize
2017/06/08-02:49:42.234614 7f423d155700  Options.compaction_options_universal.size_ratio: 1
2017/06/08-02:49:42.234615 7f423d155700 Options.compaction_options_universal.min_merge_width: 2
2017/06/08-02:49:42.234616 7f423d155700 Options.compaction_options_universal.max_merge_width:<PHONE_NUMBER>
2017/06/08-02:49:42.234617 7f423d155700 Options.compaction_options_universal.max_size_amplification_percent: 200
2017/06/08-02:49:42.234618 7f423d155700 Options.compaction_options_universal.compression_size_percent: -1
2017/06/08-02:49:42.234619 7f423d155700 Options.compaction_options_fifo.max_table_files_size:<PHONE_NUMBER>
2017/06/08-02:49:42.234620 7f423d155700                   Options.table_properties_collectors:
2017/06/08-02:49:42.234620 7f423d155700                   Options.inplace_update_support: 0
2017/06/08-02:49:42.234621 7f423d155700                 Options.inplace_update_num_locks: 10000
2017/06/08-02:49:42.234622 7f423d155700               Options.min_partial_merge_operands: 2
2017/06/08-02:49:42.234623 7f423d155700               Options.memtable_prefix_bloom_size_ratio: 0,100000
2017/06/08-02:49:42.234624 7f423d155700   Options.memtable_huge_page_size: 0
2017/06/08-02:49:42.234625 7f423d155700                           Options.bloom_locality: 1
2017/06/08-02:49:42.234626 7f423d155700                    Options.max_successive_merges: 0
2017/06/08-02:49:42.234627 7f423d155700                Options.optimize_filters_for_hits: 0
2017/06/08-02:49:42.234628 7f423d155700                Options.paranoid_file_checks: 0
2017/06/08-02:49:42.234629 7f423d155700                Options.force_consistency_checks: 0
2017/06/08-02:49:42.234636 7f423d155700                Options.report_bg_io_stats: 0
2017/06/08-02:49:42.236109 7f423d155700 Recovered from manifest file:/home/expert/jdata/ardb/data/data/rocksdb//MANIFEST-035032 succeeded,manifest_file_number is 35032, next_file_number is 35034, last_sequence is 71033660, log_number is 0,prev_log_number is 0,max_column_family is 2
2017/06/08-02:49:42.236119 7f423d155700 Column family [default] (ID 0), log number is 35031
2017/06/08-02:49:42.237051 7f423d155700 EVENT_LOG_v1 {"time_micros":<PHONE_NUMBER>237037, "job": 1, "event": "recovery_started", "log_files": [35034]}
2017/06/08-02:49:42.237067 7f423d155700 Recovering log #35034 mode 2
2017/06/08-02:49:42.237100 7f423d155700 EVENT_LOG_v1 {"time_micros":<PHONE_NUMBER>237092, "job": 1, "event": "recovery_finished"}

Thanks!

the data is stored in the columnfamily with the name by dbid not the default one.

Awesome! It worked! I'll probably have more questions about the way you encode keys and etc. If I don't find all answers in https://github.com/yinqiwen/ardb/wiki/Design-Draft can I contact you again ? If yes should I write another issue or can I find you in some chat ?

@yinqiwen Looks like it's not ARDB's fault that it misses items during SCAN. It happens to me sometimes with direct access to RocksDB.
I have few questions. I also noticed that I can't find some values via RocksDB.get() call. But I get that key-value when I iterate through entire DB. Byte-array of the key is exactly the same.

What could be the reason for such behavior ?
How can I fix it ?
Could it be caused by damaged caused by hanging ARDB I reported in another bug ? If yes how can I repair Rocks DB ?

Thanks!

@unoexperto  do u using rocksdb's default bitwise comparator? ardb use custom comparator which may cause A.Compare(B) == true but  A is not bytewise equal to B.

@yinqiwen After very long and frustrating debugging I found that my problem wasn't missing items during sequential read using RocksDB iterator but failure of RocksDB to write data.
I have custom comparator. I write data sequentially from another database. I write data to RocksDB using BatchWrite in batches of 500 items. I don't see errors. The process reports that 35426957 items were processed but then it's done I see 32322150 returned by rocksdb.getLongProperty(rawFamily, "rocksdb.estimate-num-keys"). And it's confirmed by getting Iteraror.seekToLast(). Last ID is not what I expect.
I tried transfer several times and it stops saving data at different points.
Could you please suggest how to identify the root cause of such behavior ? Should I flush periodically maybe ?

rocksdb.estimate-num-keys is only estimate counter which is not accurate.  u can use a iterator  to iterate from first to last keys to get the accurate counter.


Loader for controller 'XXX' not found.

Hi,
I tried to write a new controller according to the guidance in this link.
https://control.ros.org/foxy/doc/ros2_controllers/doc/writing_new_controller.html
I think my export definition for pluginlib in the CMakeList file and at the bottom of the controller .cpp file are correct. But when I tried to spawn the controller using code as follows.
  effort_position_controller_spawner = Node(
      package="controller_manager",
      executable="spawner.py",
      arguments=["effort_position_controller", "--controller-manager", "/controller_manager"],
  )

I got the error as follows.

Could you help me to think where the problem might occur? Thanks a lot.

I think I fixed it by adding this in the CMakeList file.
target_compile_definitions(${PROJECT_NAME} PUBLIC "PLUGINLIB__DISABLE_BOOST_FUNCTIONS")


Dragon's Dogma 2 Cannot Open with REFramework installed (June 02 2024)

The game will not open with REFramework installed. The window will open (blank), hang around for a bit, then close automatically. Apparently does not count as a crash, since crash dump is not generated.
re2_framework_log.txt
Tested with June 02 Nightly Build 953.
DLSS = None
DLSS_FrameGeneration=OFF
Verified game files repeatedly, no effect.

OS Windows 11
Graphics card NVIDIA GeForce RTX 4090
CPU 13th Gen Intel(R) Core(TM) i9-13900HX

Try the newest nightly build and report back
https://github.com/praydog/REFramework-nightly/releases/

That seems to have done the trick! Awesome, thank you 🙏


flatten social providers' userAttributeMapping props

Environment information
n/a

Description
current experience requires us to nest an object an add an attributeName key with the value from the IdP. Often times this is the only thing specified in the object, where the object then feels unnecessary.
current experience
// amplify/auth/resource.ts
import { defineAuth } from '@aws-amplify/backend';

export const auth = defineAuth({
  loginWith: {
    externalAuthProviders: {
      loginWithAmazon: {
        clientId: secret('LOGINWITHAMAZON_CLIENT_ID'),
        clientSecret: secret('LOGINWITHAMAZON_CLIENT_SECRET'),
        attributeMapping: {
          email: {
            attributeName: "email",
          },
        },
      },
      callbackUrls: [
        'http://localhost:3000/profile',
        'https://mywebsite.com/profile'
      ],
      logoutUrls: ['http://localhost:3000/', 'https://mywebsite.com'],
      domainPrefix: 'subdomain'
    }
  }
});

expected experience
// amplify/auth/resource.ts
import { defineAuth } from '@aws-amplify/backend';

export const auth = defineAuth({
  loginWith: {
    externalAuthProviders: {
      loginWithAmazon: {
        clientId: secret('LOGINWITHAMAZON_CLIENT_ID'),
        clientSecret: secret('LOGINWITHAMAZON_CLIENT_SECRET'),
		// remove need for nesting
        userAttributeMapping: {
          email: 'email'
        }
      },
      callbackUrls: [
        'http://localhost:3000/profile',
        'https://mywebsite.com/profile'
      ],
      logoutUrls: ['http://localhost:3000/', 'https://mywebsite.com'],
      domainPrefix: 'subdomain'
    }
  }
});

the expected experience is documented here https://docs.amplify.aws/gen2/build-a-backend/auth/add-social-provider/#attribute-mapping

Marking as bug to align with the docs.

done in https://github.com/aws-amplify/amplify-backend/pull/1251


Hot Button documentation

I went ahead and put in the offline monitoring (phase 1 instead of phase 4) here: https://github.com/openaps/docs/commit/7b8750c22230bb22ceb8581608382909b31d5233
Thanks @lukas-ondriga!


add(ember): update TailwidnCSS + EmberJS integration

Name
Link

EmberJS
tailwind-ember-example

Linked resource was pretty old.
Was probably not working with TailwindCSS >= 2.0.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

For future travelers: In past few months every time I've been bootstrapping new Ember + Tailwind CSS project, I had to back reference to the easy and well established ways to do this. So far I have not found a better how-to than this one.


Proposal remove npm dependency

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

This proposal is based on the use of:

[x] "wikimedia/composer-merge-plugin".
[x] "https://asset-packagist.org"
[x] "oomphinc/composer-installers-extender": "@dev"

Config composer.json basic:
"require": {
    "php": "^7.4|^8.0",
    "wikimedia/composer-merge-plugin": "*"
},
"extra": {
    "branch-alias": {
        "dev-master": "1.0.x-dev"
    },
    "installer-types": [
        "npm-asset"
    ],
    "installer-paths": {
        "./node_modules/{$name}": [
            "type:npm-asset"
        ]
    },
    "merge-plugin": {
        "include": [
            "composer.assets.json"
        ]
    }
},
"repositories": [
    {
        "type": "composer",
        "url": "https://asset-packagist.org"
    }
]

composer.assets.json:
"require": {
    "npm-asset/vizuaalog--bulmajs": "^0.11.0",
    "npm-asset/bulma": "^0.9.1",
    "npm-asset/bulma-helpers": "^0.3.12",
    "oomphinc/composer-installers-extender": "@dev"
}

As a result we get all the assets in ./node_modules in the same way as if we had used npm.
Note:
We must wait for the compatibility as composerV2 that is already made.
https://github.com/wikimedia/composer-merge-plugin/pull/189

Foxy could be removed from yiisoft/app if this is merged.

👍


CAPC does not resolve service offering with zone as additional filtering parameter

/kind bug
What steps did you take and what happened:
The following error is generated when multiple cloud stack zones with the same offering name exist.
E0104 21:43:15.451029       1 controller.go:317] controller/cloudstackmachine "msg"="Reconciler error" "error"="1 error occurred:\n\t* expected 1 Service Offering with name 4 vCPU 8 GiB RAM, but got 2\n\n" "name"="<>" "namespace"="<>" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="CloudStackMachine"
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Cluster-api-provider-cloudstack version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

PR https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/pull/208 fixed the issue.


Haxelib doesnt works when haxe is installed using scoop

I installed haxe v4.0.5 using scoop.
Haxelib exe was properly placed in the scoop bin directory.
But I cannot use haxelib command from the command line. It does nothing at all.

When I double click on the exe in windows explorer, i get an error message saying that neko.dll isn't found.

The reference to the dlls that haxelib depends on isn't correct.

Fixed by PR #635


Upload Error for file the 11gb, Dr

The error happens when transferring larger files like this, the transfer bar starts fast but slows down until it stops completely, below is my current configuration.
If you can help me please, thank you very much.

Config:

Update: I noticed that whenever an error happens, it's around 4.2~4.6gb transferred to cache folder.


Camera long delay when testing PS eye cameras

I have along delay with the cameras refreshing slowly. Is it just me or anyone else. Using a 3.0 usb hub with multiple extension with 4 cameras. I also have a beefy pc and should be fine about that. Oh btw im also running the newest release.

It doesn't matter if you're using usb 3.0, the cameras are 2.0 only. A single USB root cannot handle 4 cameras. You have to spread them out. There are many many posts about this in the psmoveservice forums, and there's info about this in the wiki.


[Enhancement] Support all new version Statement by new Parser

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #6070 #4049
Problem Summary(Required) ：

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 77 / 83 (92.77%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
75
81
92.59%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
1
1
100.00%


Germany - treemap does not show beneficiary names

For the German Treemap, the tiles do not show the beneficiary names (although they are shown in the ranking below the treemap).

It's not an issue - babbage.ui (library we use in OS Viewer to create visualizations) hides too long labels. And, in case of Germany, all labels are too long :smile:


Independent suspension nodes

Summary
Currently if 2 independent branches of a DAG pause execution because of SuspendTemplate node it is not possible to resume only one branch. Clicking "Resume" leads to resuming both branches. I understand that apparently as for now "suspended" state is global for the whole workflow, and it is expected behavior. But it is highly desired feature to allow independent resuming of suspension nodes.

Use Cases
I use suspension nodes for operator to manually approve some further actions. If a DAG has 2 independent branches with different actions I want to approve them independently.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Yes, we would also prefer to see this feature in action. I also have the same use case where it would be cool to have independent resuming of suspension nodes.


Finish update to Cpp14

We missed an exercise that was added after the initial upgrade.

@patricksjackson Finishes #292

My bad, I even remembered to ping on the new problem but forgot about this one. Thanks!


URI/CURIE disambiguation

Does this project plan to provide some functionality to support on URI/CURIE disambiguation?
Something like a validation/sanitation functionality would be really useful. Let me illustrate it with a couple of examples (assuming a function called curie_validate(curie,prefixes): valid(boolean), issue_level(integer), hints(list of strings)):

curie_validate("[schema]:Thing", ["schema"]) could return True, 0, ["no URI ambiguity"]
curie_validate("@schema@:Thing", ["schema"]) could return True, 0, ["no URI ambiguity"][^1]
curie_validate("schema:Thing", ["schema"]) could return True, 1, ["potential URI ambiguity", "matching prefix"]
curie_validate("schema:Thing") could return True, 2, ["potential URI ambiguity", "no prefix matching check possible"]
<EMAIL_ADDRESS>could return True, 3, ["potential URI ambiguity", "no matching prefix", "unexpected format/characters"][^2]
curie_validate("my_prefix:Thing", ["schema"]) could return False, 0, ["unknown prefix"]
curie_validate("http://example.org") could return False, 1, ["invalid CURIE"]

[^1]: If I read the URI specification right, @ should be fine for URI/CURIE disambiguation.
[^2]: According the CURIE specification<EMAIL_ADDRESS>is a valid CURIE! This is the CURIE grammar: curie := [ [ prefix ] ':' ] irelative-ref, being irelative-ref defined in the IRI specification. Look here for some examples of valid irelative-refs.

I'm not really sure I understand what you are asking for - can you try rewriting your issue to have less visual clutter (e.g., mock the function in a python block)? I'm not familiar with the formalism you're using here to describe this function, but it's very confusing for me
Also it's not clear if this is unique functionality or this would build on top of existing functionality in this package.

Ups, I'm sorry. I took my time to structure it and thought it would be understandable. Obviously not 🙁
I'm adding first the reason for the question on the top of the issue description. If you agree on it, I can then take some time to better elaborate the idea. If you say straight away "out-of-scope", then I'm saving my time 🙂

FYI, I'm leaning towards out of scope.

But, I'm curious where you would want to use such functionality in practice. Do you have a dataset where this would be appropriate to apply to it?

I'm getting here from the LinkML project, which declares the type Uriorcurie.
There the function is_curie has been implemented to decide is an attribute of type Uriorcurie should be handled as a CURIE or as a URI. But it's been implemented in such a way that it's interpreting lot of valid URIs as CURIES (due to the URI/CURIE ambiguity mentioned in the issue description).
I've started discussing in LinkML how to tackle the issue. Although I only need the fix in LinkML, I've a strong OSS-mindset and "sharing is caring" attitude. Therefore I thought that resolving it in a low-level component like curies would be more benefitial for the community.
I'm not asking to implement it, don't get me wrong. I could try to prepare a PR for it, but I don't want to waste my time. That's why I'm trying first to find out, if you could be interested.
BTW, I've updated the top of the description to provide a better context description.

Function interface draft (originally in the description, moved to a separate comment so that description is on problem space and this comment is focused on solution space):
Something like a validation/sanitation functionality would be really useful. Let me illustrate it with a couple of examples (assuming a function called curie_validate(curie,prefixes): valid(boolean), issue_level(integer), hints(list of strings)):

curie_validate("[schema]:Thing", ["schema"]) could return True, 0, ["no URI ambiguity"]
curie_validate("@schema@:Thing", ["schema"]) could return True, 0, ["no URI ambiguity"][^1]
curie_validate("schema:Thing", ["schema"]) could return True, 1, ["potential URI ambiguity", "matching prefix"]
curie_validate("schema:Thing") could return True, 2, ["potential URI ambiguity", "no prefix matching check possible"]
<EMAIL_ADDRESS>could return True, 3, ["potential URI ambiguity", "no matching prefix", "unexpected format/characters"][^2]
curie_validate("my_prefix:Thing", ["schema"]) could return False, 0, ["unknown prefix"]
curie_validate("http://example.org") could return False, 1, ["invalid CURIE"]

[^1]: If I read the URI specification right, @ should be fine for URI/CURIE disambiguation.
[^2]: According the CURIE specification<EMAIL_ADDRESS>is a valid CURIE! This is the CURIE grammar: curie := [ [ prefix ] ':' ] irelative-ref, being irelative-ref defined in the IRI specification. Look here for some examples of valid irelative-refs.

Okay, I have a few opinions:

We shouldn't need something like this, since we should either have fields that are only for URIs, CURIEs, or if they must co-exist, we can use the official solution which is Safe CURIEs
We don't live in a world where people use official solutions, LinkML being one example
There are reasonable concerns about the quality and correctness of code that's hacked into LinkML, so if you are looking for a home for generally reusable code that is easy to understand, high quality, well documented, and fully tested, I would be happy to accept a contribution into this package such that others can reuse it

TL;DR: Since I don't think I would have time to maintain the code and I don't see much interest from your side, I won't try to contribute a solution for a problem that you disagree with. Thanks anyway for the discussion.

We shouldn't need something like this, since we should either have fields that are only for URIs, CURIEs, or if they must co-exist, we can use the official solution which is Safe CURIEs

I agree, but migrating from non-SafeCURIEs to SafeCURIEs is not so easy. So I don't count on convincing them to do so. In any case a migration strategie would be needed not to force all existing LinkML schemas to be migrated.

We don't live in a world where people use official solutions, LinkML being one example

I don't know what you consider an official solution. Sticking to the specs? Using well established components?

There are reasonable concerns about the quality and correctness of code that's hacked into LinkML, so if you are looking for a home for generally reusable code that is easy to understand, high quality, well documented, and fully tested, I would be happy to accept a contribution into this package such that others can reuse it

As said before, that's exactly the intention contacting you. Finding out if getting here a central solution that can be reused is an option for you. Got the message, you're open for PRs, but they must provide "reusable code that is easy to understand, high quality, well documented, and fully tested" 🙂

I don't typically implement solutions in my open source software to problems that I fundamentally disagree with, so I will probably not work on or support this myself (besides code review!)
If you want to make a contribution, you should be somewhat available for maintenance and discussions regarding such code

Your fundamental disagreement with the problem is a major drawback for me. IMO this issue won't only exist in LinkML, otherwise the CURIE spec wouldn't mention it. Since I don't think I would have time to maintain the code and I don't see much interest from your side, I won't even try and therefore close this issue. Thanks anyway for the discussion.


Document orphaned resources, or allow removal?

When a user runs awsmobile delete a number of resources aren't deleted and are left orphaned in the account. Could I suggest that these are documented somewhere so the user knows what to delete manually. It appears to be dynamodb and s3, are there any other resources I should be aware of?
An alternative could be providing an extra parameter on the awsmobile delete command that also deletes these resources. This is handy in development when spinning up multiple environments and you don't care about the data.

Thanks for the feedbacks @SeanBannister.
We are aware of that issue, and we have notified our mobile hub team about it, will notify you when there is any update.
You suggestion about the extra parameter in the cli will also be considered.

agreed. it looks like appsync is the only resources that gets removed and everything else is left orphaned.

Related to this discussion: CloudFormation can be used to build / tear down resources, as long as MobileHub is not used.
https://twitter.com/dabit3/status/1022192837683634176


BT5: are the payloads of each packet are the same?

I think it is better to make it a separate issue.
The payload I mean the payload of the Extended Advertising Secondary Packet.
From what I read in the source code, the transmitter-Linux is sending the same ODID payload repeatedly.
the first 3+25 bytes reference payload (ODID) that is supposed to be transmitted is:
F2 19 09 02 12 31 31 32 36 32 34 31 35 30 41 39 30 45 33 41 45 31 45 43 30 00 00 00

But what I decoded from the recorded over-the-air data (captured with an SDR) is different from packet to packet. Below are the first 3+25 bytes of 4 packets.
F2 19 09 02 0A 31 31 0F 37 32 1C 36 35 30 41 39 30 25 33 41 45 91 36 43 30 00 08 00
01 1A 09 02 12 E1 EB 06 3F 32 DC 31 35 30 41 39 30 C5 32 41 45 31 45 43 30 B0 77 A6
6B 50 0A BA 1E 31 31 32 DE 33 34 31 35 30 41 39 90 44 33 41 45 31 ED 0C 4F 00 40 73
3E B3 0E CA 13 31 31 32 36 32 34 B1 3A 30 41 39 30 45 33 29 45 31 45 43 30 00 00 00

I can see some bytes are the same as the reference, but some are not.
So either they are actually carrying different payloads or I didn't decode them correctly. I'd like to confirm with you before I go into some dead end.
Thanks

I assume you are able to pick up the signals with the Android receiver application? I think you mentioned earlier that you got that working at least. If yes, that should prove that the transmitter is working correctly.
Which mode are you transmitting with? "l", "4" or "5"?
Legacy mode using the non-extended HCI API (i.e. option "l") will use this header.
Legacy mode using the extended HCI API (i.e. option "4") will use this header.
Long range mode using the extended HCI API (i.e. option "5") will use this header.
Each of them have several header bytes that never change. Try to look for those bytes in the packet data that you pick up with the SDR. Please note that the message counter byte will always change from one advertisement to the next.

sudo ./transmit 5 p
The Android receiver is working fine, and I am writing my own SDR receiver.
My question is about the actual ODID payload, which is, I believe, independent of the protocol used.
For example, the first 3 bytes mean: ODID version 2, each message is 25 (0x19) bytes long and there are 9 messages in total. The next 25 bytes are the first message, Basic ID.
I assume these payloads should be delivered as they are and all the same between BT5 packets. That is why it bothers me doing the decoding. I don't know where I got wrong.

What if you dump the raw bytes from the transmitter? Then you know exactly what you should be looking for on the receiver side?
In bluetooth.c, in the hci_le_set_extended_advertising_data_pack() function, modify it to be:
    printf("Bytes being sent %d: ", sizeof(buf));
    for (int i = 0; i < sizeof(buf); i++)
        printf("%2X ", buf[i]);
    printf("\n\n");

    send_cmd(dd, ogf, ocf, buf, sizeof(buf));

BTW: keep in mind that only for the BT4 transmissions ("l" or "4") will the advertisements consist of a single 25 byte message (+ the header stuff). For BT5 Long Range + Extended Advertising (the "5 p" option you are using), all the 25 byte messages will be bundled together in a message pack and sent in a single advertisement.

I don't know what your end goal is, but if you are trying to setup a reliable receiver that can capture all the packets from a transmitter (e.g. for testing compliance with US and EU rules), one possible option is to buy a Texas Instruments Bluetooth development board and use this SW for sniffing the Bluetooth transmissions:
https://github.com/nccgroup/Sniffle
I have not tried this myself but I do know that someone is using it for this purpose. When both the transmitter and receiver are placed in a radio shielded room, this combination should be pretty reliable.

for your piece of code, that is exactly what I did to get the reference payload.
and yes, I expect the same 9 messages with 25 bytes in length from each BT5 packet.
I just ordered a CC2640R2 launchpad, then found that it does not support sniffing.


Disable go back browser button

I have a form at "localhost/form" the user comes in from this route "localhost/intro"
I want to disable the going back button on the browser when the user reach "localhost/form".
Is there a way to do this with the router ? like kill the history or hack the browser behavior ?
Thanks

router.replace() instead of router.go()

Ok but when ? the user uses the browser button

What browser button?
Also:  your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests.
We encourage you to ask it on the forum  or on gitter.


Custom layout for parallax slides

Is there any way of using a custom layout with parallax, for example using multiple images?

You may want to take a look at the parallax implementation:
https://github.com/heinrichreimer/material-intro/tree/master/library/src/main/java/com/heinrichreimersoftware/materialintro/view/parallax
Main part of it is the Parallaxable class.

I managed to achieve what I was looking for by including custom Views into a ParallaxLinearLayout and using it in the slides.


Add a Gitter chat badge to README.md

alanshaw/upmon now has a Chat Room on Gitter
@alanshaw has just created a chat room. You can visit it here: https://gitter.im/alanshaw/upmon.
This pull-request adds this badge to your README.md:

Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same when pulling 0c1429a5379e6ceb88b8fffd3c2b89af51fbe020 on gitter-badger:gitter-badge into fc30ba725533662155c9b5c12e31b64d8685ef66 on alanshaw:master.


(docs) Request for elaboration on usage docs for defineEntries

defineEntries is a fn call to define how to render, build, and configure the ssr for your waku app.
Some initial usage docs live here: https://github.com/dai-shi/waku/blob/main/docs/minimal-api.mdx
It would be really helpful for someone new to look through how the initial usages of defineEntries are used, then summarize some info in a docs entry for this function.
I'd be happy to help answer questions and assist with writing some info up for this, but I think it would be a perfect task for anyone coming into the waku project looking for a starting point :)

I was wondering if you could explain where it is the explanation of defineEntries function in Docs or README! I couldn't find it since waku was released as v0.19.0. Is it deprecated
https://github.com/dai-shi/waku/issues/24#issuecomment-1894091550

Oh I was also wondered definedEntries before releasing managed mode. If it's important to know this API for library athors, it's good to describe this API. Reading the source code of it briefly, It feels like it's working for build process. But it's too hard for newcomers to know about it.
https://github.com/dai-shi/waku/blob/901594c2195de5a7d601ca6ecda674202e9a0915/packages/waku/src/lib/builder/build.ts#L750
How about explain API descriptions like what each parameter work for or the interaction of parameters(renderEntries, getBuildConfig, getSsrConfig)? And then I feel like that it's easier to know and investigate the use cases of this API.

I saw that new_defineEntries() is now available.

https://github.com/dai-shi/waku/blob/main/examples/31_minimal/src/entries.tsx
https://github.com/dai-shi/waku/blob/v0.21.6/packages/waku/src/minimal/server.ts#L64-L113

@tylersayshi I'm not sure if this is a good first issue anymore.


Possible data context corruption with nested viewmodels

In this scenario, if the component has text set on it, it uses a local viewmodel to do a text transformation. This denies the tapped handler access to the original data context in which it was defined.
Expected behavior (I might be mistaken): displayString should be added to the data context, not override it completely.
<App>
	<Rectangle ux:Class="ProblemChild" Color="Gray" Width="80" Height="80">
		<string ux:Property="MaybeString"/>
		<WhileString Value="{Property MaybeString}" Test="IsNotEmpty">
			<JavaScript>
				module.exports = {
					displayString : this.MaybeString.map(value => value+" etc")
				}
			</JavaScript>
			<Text Value="{displayString}" Alignment="Center"/>
		</WhileString>
	</Rectangle>

	<JavaScript>
		module.exports = {
			items : [
				{ id:0, text: "foo"},
				{ id:1 },
				{ id:2, text: "bar"}
			],
			itemClicked : args => console.log(args.data.id)
		}
	</JavaScript>

	<StackPanel Alignment="Center" ItemSpacing="8">
		<Each Items="{items}">
			<ProblemChild MaybeString="{text}">
				<Tapped Handler="{itemClicked}"/>
			</ProblemChild>
		</Each>
	</StackPanel>
</App>

It's not likely actually overwriting it. The problem is that you have two data contexts on the same node, and the itemClicked callback is taking the wrong one. I'm not sure if we have any way to resolve this conflict now.  THat is, I presume itemClicked is being called, just with the wrong context, thus args.data.id is not defined.
Simplfiied the setup looks like this:
<Each>
   <ProblemChild>
        <JavaScript>

Both Each and JavaScript set a context (in different ways) on the ProblemChild. It's not really a scenario we've tested much.
I don't know if we can solve the situation automatically, but I agree there should at least be some way to resolve it, even if the user has to mark something somehow.


[v1]-missing keys: 560

loaded 3D unet's pretrained weights from models/StableDiffusion/stable-diffusion-v1-5/unet ...

### missing keys: 560;
### unexpected keys: 0;
### Motion Module Parameters: 417.1376 M

What could be the reason for the presence of missing keys?

The same situation applies to me here as well

Those are parameters of the motion module, which is not included in the original Unet.

@liutaocode Thank you!

@liutaocode Thank you!

@song-wensong So can I just ignore these missing keys? Or what should I do to fix it?

Ignoring them is fine.

@liutaocode Thank you!

@song-wensong So can I just ignore these missing keys? Or what should I do to fix it?


Add better support for providing environment variables as inputs for exec-like tasks

Expected Behavior
Tracking of environment variables as the input to exec like tasks like Test and Exec is simple. It should be possible to declare that the environment variable is an input to the task and what kind of input (like plain property, file or directory with path sensitivity, optional property). Currently, it is rather cumbersome.
Current Behavior
To add an environment variable as an input, something like this needs to be done:
inputs.property('myProp', System.getenv('SOME_ENV')).optional(true)

If it should be a file, this should suffice:
inputs.file(System.getenv('SOME_ENV'))
  .withPropertyName('myInput')
  .withPathSensitivity(RELATIVE)
  .optional(true)

Both are quite verbose for such a simple task.
Context
We currently pass the Gradle process’ environment to any spawned child process. These environments include variables like:
DISPLAY=/private/tmp/com.apple.launchd.cQ9TyQSdpP/org.macosforge.xquartz:0
TERM_SESSION_ID=w0t0p0:8A5578C2-CBBC-4D4C-8372-00E893D1FC74

These values change from shell to shell, or are even updated after each command execution, and mostly irrelevant to the actual executed process. Their inclusion among inputs would make sharing cached results even between different terminal sessions impossible. Yet there are some environment variables that do influence the results we get (e.g. terminal encoding etc.), which therefore should be included among the task’s inputs.
The reason these weird environment variables are not currently busting up-to-date checks is that because we ignore the environment completely. This is rather problematic for correctness.
The problem is made worse by the fact that some frequently used tasks like the Java Test task are based on spawning child processes, and thus have this problem.
One option is to whitelist some of the environment variables, and pass only those to the child process by default. Another option is to introduce something like this:
@Environment(“SOME_ENV”)
String getSomeEnv() { ... }

Which would pass SOME_ENV to the child process with the value of the property.

See the old issue: https://github.com/gradle/build-cache/issues/50

We want to do a similar thing for system properties: https://github.com/gradle/gradle/issues/9092
The only difference is that all system properties are tracked by default, while the environment variables are not.
We could switch to actually whitelisting environment variables for the test task.

@eskatos Is this something which will be fixed as part of instant execution?

@wolfs what was done wrt. environment variables for instant execution is the introduction of ProviderFactory.environmentVariable(variableName)
https://github.com/gradle/gradle/blob/c28a59f06bae758fa610a35e23793e682b339c2e/subprojects/core-api/src/main/java/org/gradle/api/provider/ProviderFactory.java#L47-L65


[BUG] Alarm delay

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
停掉api，大约20分钟后发出报警
Expected Behavior
停掉api，3分钟后发出报警
Steps To Reproduce
1、启动一个测试服务，http api 返回 200
2、配置hertzbeat，http api监控，填写相关信息，检测正常，设置监控周期60秒
3、确认阈值规则，http api 可用性，触发次数3次
4、所有告警收敛、告警静默规则全部删除
5、运行一个小时，待系统稳定后，停掉测试api服务
6、大于15至20分钟后，报警发出
Environment
HertzBeat version(s):1.4.3 和 1.5.0 都有

Debug logs
无
Anything else?
无

thanks for feedback, we will try to reproduce it.

perhaps related to issue https://github.com/apache/hertzbeat/issues/1714
after doing this, https://github.com/apache/hertzbeat/issues/1714#issuecomment-2049230115 ,alarms are never delayed.


[Question] Is this package no longer maintained?

Thanks for creating this awesome library. I want to ask if this package is still maintained? Thanks

Thank you for your kind words! Yes, we're still maintaining the library, but it might take some time to address all issues because we're not actively working on maintaining this library anymore. Your feedback is important, so please don't hesitate to report any specific problems or suggestions you have. We appreciate your support!

Could you update the darts version to 0.26.0 (this lib's darts is 0.23.0)? Thank you very much!


Documentation

Hi
For those noobs / newcomers, it would be great to have some nice documentation please. A tutorial, if you like. We could go through each class and understand it, but the 'table' on the main screen does not help. There's far too much going on and it would be great to learn how to 'add new features' on top of this recycler view, as it seems quite generic at the moment. Like for example, if we were to add 'multi-select' capabilities, would that be simple to add to this?

hi, I already tried and more or less succeeded in adding (multi)selection to the project look at my fork for it. once it's cleanedu and reviewed i'll create a pull request...
https://github.com/gandulf/android-advancedrecyclerview

Thanks gandulf - I saw that and actually been looking at the code (seems to work!). I did however find that I could in theory get the sections to collapse as well, but there's just so little comments / documentation that it's difficult to navigate around. Would be great if someone familiar with the code writes some sort of a document explaining how it all works.

+1
Really need wiki support for newcomers.

Does anyone know how to include this is in a project because I'm completely lost.

@fadelakin Carefully check the samples, you may get some clue.

@daimajia I did but for the expandable list which is what I want, he uses a host of different classes to piece everything together but I'll keep looking.

Looking through the examples is tough. It's a puzzle in there and really what's needed is some good tutorial / documentation. This is a fantastic piece of code but very difficult to grasp.

Alright, I'm done with the sample. Pushing now.

Seriously, this project needs documentation. The sample code is 90% irrelevant, picking out what's necessary and what not is just frustrating.

I really just want to be able to use the Swipeable stuff on my RecyclerView with backgrounds depending on left/right swipe and I see the library does that but looking at the samples I can't do anything. I see lots of questions and that's due to the poor documentation I believe. Please make at least 1-2 step by step tutorials. I have no idea what those get(position).getId(); method should do in my 'data provider' and what the provider could be.


Intermittent memory access error

Every few executions I get the following error:
Memory access fault by GPU node-1 (Agent handle: 0x37b9900) on address 0x7f18ada2e000. Reason: Unknown

What I find surprising is that my code works at all yet sometimes fails.
My memory structure is perhaps some what complex, but I don't see why this should be causing problems.
I have no async memory calls.

I cannot reproduce this under gdb so I would guess there's a race condition somewhere.
I use no async calls and have no threads so I don't know how it could be my code.
Please advise.

Are you using rocm-3.5 branch?

Yes indeed, this was occuring both on 3.3 and now on 3.5

I absolutely understand that his may be due to my own buggy code.
So I appreciate any assistance especially if this turns out to be the case!

You could try by SERIALIZING kernels and memcpys. With ROCm3.5, you can use AMD_SERIALIZE_KERNEL and AMD_SERIALIZE_COPY env vars as described @ https://github.com/ROCm-Developer-Tools/ROCclr/blob/roc-3.5.x/utils/flags.hpp#L220-#L225

will give it a shot thanks

I'm not really sure what these env vars are doing, but it doesn't make much of a difference
LOG_LEVEL=14 HIP_DB=api+copy+mem AMD_SERIALIZE_KERNEL=3 AMD_SERIALIZE_COPY=3 ./bin

results in both of these
A) working - https://gist.github.com/Dekken/f527c1499ea362075a03807f31c18031
B) not working - https://gist.github.com/Dekken/9d5f831f3ce6a7ae860cf9035adbed17
I think there's binary characters being logged somewhere in there too which isn't ideal!

Got it to happen with dbg
Memory access fault by GPU node-1 (Agent handle: 0x1276a70) on address 0x7fffa1ec4000. Reason: Unknown.

Thread 33 "binary" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffa1dbf700 (LWP 58336)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff6763535 in __GI_abort () at abort.c:79
#2  0x00007ffff5a3cf43 in core::Runtime::VMFaultHandler(long, void*) () from /opt/rocm/lib/libhsa-runtime64.so.1
#3  0x00007ffff5a3b505 in core::Runtime::AsyncEventsLoop(void*) () from /opt/rocm/lib/libhsa-runtime64.so.1
#4  0x00007ffff59fa1c7 in os::ThreadTrampoline(void*) () from /opt/rocm/lib/libhsa-runtime64.so.1
#5  0x00007ffff7f7afa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#6  0x00007ffff683a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

After building https://github.com/RadeonOpenCompute/ROCR-Runtime with debug symbols.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff6763535 in __GI_abort () at abort.c:79
#2  0x00007ffff6bf2ffd in roc::callbackQueue(hsa_status_t, hsa_queue_s*, void*) () from /opt/rocm/lib/libamdhip64.so.3
#3  0x00007ffff5b8b0b4 in AMD::callback_t<void (*)(hsa_status_t, hsa_queue_s*, void*)>::operator() (this=0x7ffe90001930, args#0=41, args#1=0x7fffa1710000, args#2=0x12b4f80) at /path/to/rocm/hsa-rocr/src/core/inc/exceptions.h:87
#4  0x00007ffff5b88b53 in amd::AqlQueue::DynamicScratchHandler (error_code=536870912, arg=0x7ffe90001860) at /path/to/rocm/hsa-rocr/src/core/runtime/amd_aql_queue.cpp:866
#5  0x00007ffff5bcf8e8 in core::Runtime::AsyncEventsLoop () at /path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp:1035
#6  0x00007ffff5b5c362 in os::ThreadTrampoline (arg=0x12b3c20) at /path/to/rocm/hsa-rocr/src/core/util/lnx/os_linux.cpp:75
#7  0x00007ffff7f7afa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007ffff683a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

and

Memory access fault by GPU node-1 (Agent handle: 0x1276c00) on address 0x7fffa0e51000. Reason: Unknown.
Nearby memory map:
0x7fffa0db4000, 0x1000, VRAM
0x7fffa0db5000, 0x3000, VRAM
0x7fffa0e80000, 0x60000, System

PtrInfo:
  Address: 0x7fffa0db4000-0x7fffa0db5000/0x7fffa0db4000-0x7fffa0db5000
  Size: 0x1000
  Type: 1
  Owner: 0x1276c00
  CanAccess: 1
    0x1276c00
  In block: 0x7fffa0c00000, 0x200000
PtrInfo:
  Address: 0x7fffa0db5000-0x7fffa0db8000/0x7fffa0db5000-0x7fffa0db8000
  Size: 0x3000
  Type: 1
  Owner: 0x1276c00
  CanAccess: 1
    0x1276c00
  In block: 0x7fffa0c00000, 0x200000
PtrInfo:
  Address: 0x7fffa0e80000-0x7fffa0ee0000/0x7fffa0e80000-0x7fffa0ee0000
  Size: 0x60000
  Type: 1
  Owner: 0x1275880
  CanAccess: 1
    0x1276c00
  In block: 0x7fffa0e80000, 0x60000
phare: /path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp:1264: static bool core::Runtime::VMFaultHandler(hsa_signal_value_t, void*): Assertion `false && "GPU memory access fault."' failed.

Thread 33 "phare" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffa1f1f700 (LWP 62364)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff6763535 in __GI_abort () at abort.c:79
#2  0x00007ffff676340f in __assert_fail_base (fmt=0x7ffff68c5ee0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7ffff5c3c710 "false && \"GPU memory access fault.\"",
    file=0x7ffff5c3c168 "/path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp", line=1264, function=<optimized out>) at assert.c:92
#3  0x00007ffff6771102 in __GI___assert_fail (assertion=0x7ffff5c3c710 "false && \"GPU memory access fault.\"", file=0x7ffff5c3c168 "/path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp", line=1264,
    function=0x7ffff5c3c080 <core::Runtime::VMFaultHandler(long, void*)::__PRETTY_FUNCTION__> "static bool core::Runtime::VMFaultHandler(hsa_signal_value_t, void*)") at assert.c:101
#4  0x00007ffff5bd0ab8 in core::Runtime::VMFaultHandler (val=1, arg=0x12b38c0) at /path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp:1264
#5  0x00007ffff5bcf8e8 in core::Runtime::AsyncEventsLoop () at /path/to/rocm/hsa-rocr/src/core/runtime/runtime.cpp:1035
#6  0x00007ffff5b5c362 in os::ThreadTrampoline (arg=0x12b3c20) at /path/to/rocm/hsa-rocr/src/core/util/lnx/os_linux.cpp:75
#7  0x00007ffff7f7afa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007ffff683a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

This seems to have been resolved by setting a non-zero sized "dynamicShared"
If possible, is there some documentation of this parameter somewhere I could peruse?
Thanks

It would appear I may have commented too soon.
While setting a non-zero value for dynamicShared, the program no longer functions as expected.

I have my code running on Nvidia hardware with no issues.

Any chance I can get a comment on this?
If I can get access to a machine with an "official setup", and if I can't reproduce this, I'll close the ticket (and reconsider my life choices)

I don't know if it's relevant, but the error appears to happen less often when executed just after compiling/linking

fault.Failure.ErrorType is 0

ok, I'm an idiot.
My code shouldn't ever work, yet it does.


considering :: for methods describe

only # and . can are considered methods inside a describe here: https://github.com/rubocop-hq/rubocop-rspec/blob/master/lib/rubocop/cop/rspec/describe_method.rb#L26
But according to BetterSpecs :: can also be used... :thinking:
Also, why is . used? Ruby always uses :: in its documentation. Maybe there should be cop to enforce this... :thinking:

I have always used . (e.g. Foo.bar) to describe class methods and # (e.g. Foo#bar) to describe instance methods. But I don’t know if I can find documentation for claiming it is a “standard” :-)

It seems . is more widely used and it would be nice to have a convention. Maybe it is enough with documented it in this cop and in BetterSpecs, then it will become standard :rofl:

Just in https://github.com/rubocop-hq/ruby-style-guide I see something over 20 examples of using # between class name and instance method name (search for Object#to_s, String#+, Hash#key?) while :: is only used in code examples. So my recommendation still stands, use . for class methods and # for instance methods.

@bquorning

Just in https://github.com/rubocop-hq/ruby-style-guide I see something over 20 examples of using # between class name and instance method name (search for Object#to_s, String#+, Hash#key?) while :: is only used in code examples. So my recommendation still stands, use . for class methods and # for instance methods.

Is # used for class methods? :confused:
I think it is find to encourage the use of ., as long as it is documented to avoid future confusions/discussions. :wink:

Actually, RSpec Style Guide defines this in a pretty non-ambiguous way:

Use the Ruby documentation convention of . when referring to a class method’s name and # when referring to an instance method’s name.

Not sure if RSpec/DescribeMethod covers all the cases.
However, I don't see a good reason to relax the cop and allow ::.
WDYT?

There are no updates on this for quite a while. @Ana06 do you mind if we close this?


Create dictionary explaining what the fields are in the release files (HT, VCF)

This is dependent on finalizing the readme for the HGDP + 1KG subset which can be reused for this ticket. #204

#204 has been closed and that was specific to HGDP + 1KG. For HGDP + 1KG we have this in the globals and will also have a link on the downloads page to the descriptions specific to that subset. There is a lot of overlap for this and those defined for the HGDP + 1KG subset, but what is the plan for the full dataset release? Should we add a README to the release folder (would need one for the VCF and one for the HT) or also a link on the downloads page, or both?

Duplicate with ticket #368


Custom Data Generation

API | Common
Only magic in this PR!
Implementation of the Custom Data Generation API. Still WIP. What's in the test plugin is currently working, other things are missing or untested.
Also includes extended nbt tag type support, all the data types which are supported in LanternNBT are now also supported in Sponge. This includes:

boolean[]
boolean (Was already supported)
String[]
short[]
float[]
double[]
char
char[]
DataView[]
List support for any of the default and above data types
No more losing your double[] (, etc.) once it got serialized into a nbt tag.

~wip

I'd like to see the produced class file and byte code if possible.

Having redone the API 8 Data stuffs, this can likely be valid for candidacy with API 7.3 if someone decides to pick it up.


Add loading state to hook

The hook now supports checking if files are currently loading.

Thank you man!

Thank you man!