benjinne

My current workaround is to add a `post_shutdown_test` to kill the remaining processes ``` @launch_testing.post_shutdown_test() class TestShutdown(unittest.TestCase): def test_kill_sim(self): unity_pid = check_output(["pidof", "-z", "unity_executable.x86_64"]) print('got unity pid') unity_pid = int(unity_pid)...

Anyone have tips on how I can debug a callback to see why this->now() gets stuck and keeps repeating the same value after a few minutes? I'm able to debug...

@fujitatomoya I don't have a reproducible test package, but I was able to get the stacktrace of the node that has an issue with this->now() returning with the same repeated...

Edit, here's a better stacktrace with all of ros2 built with debug flags stack trace ``` (gdb) thread apply all backtrace Thread 27 (Thread 0x7fffd8ff9700 (LWP 1718540)): #0 __lll_lock_wait (futex=futex@entry=0x7ffffffe90d0,...

> @benjinne I think this might have been solved by [eProsima/Fast-DDS#3194](https://github.com/eProsima/Fast-DDS/pull/3194) and its corresponding backports ([eProsima/Fast-DDS#3195](https://github.com/eProsima/Fast-DDS/pull/3195)) for Humble. > > Could you try? I'm having a hard time replicating the...

@MiguelCompany is there an easy way to check which fast-dds version is being used for a binary install of ros2?

I believe those fastdds changes helped. Everything is running more smoothly and no crashes after running for an hour. I'd say it's fixed.

Here's a fully working example from this branch: ``` #include "Arduino.h" #include #include #define MISO PB4 #define MOSI PB5 #define SCK PB3 #define CS PB0 SPIClass spiclass(MOSI, MISO, SCK); SPIFlash...

> Yes it is possible...https://blakadder.com/replace-tuya-esp12/ Awesome! I'll give this a shot.

I noticed this flasher only comes with E or F versions. https://www.amazon.com/DORHEA-Firmware-Downloader-Downloade-Compatible/dp/B08P37JQYX Should I go with that or buy the S version then solder and program it in place after...