Max Watermolen

@robotastic That will help debugging 110%. Thanks for adding to the que!

I agree - Bump

I really thing this needs to be added. after that there would be little to no reason to use unitrunker and that would be nice

As for Edacs this should provide most of the needed code and logic ;) https://github.com/cIay/gr-edacs https://github.com/cIay/gr-edacs/blob/master/EDACS.txt

Ok, So how do we get a pull request going to add lime sdr support?

at line 14 in sources.cc does this have to be replaced? > cast_to_osmo_sptr(source_block)->set_antenna(antenna, 0); or can cast_to_osmo_sptr(source_block)->set_antenna("LNAW"); just be added to line 15

I figured I'd Just add the config ``` { "sources": [{ "center": 159780000, "rate": 2048000, "error": -10000, "gain": 39, "debugRecorders": 0, "digitalRecorders": 4, "modulation": "qpsk", "driver": "osmosdr", "device": "rtl=0" },...

@EricTendian You should make a pull request with that code ;)

I am also seeing this on a RPI 4 running 32 bit raspbian ``` #0 0xb61052a8 in boost::asio::detail::scheduler::post_immediate_completion(boost::asio::detail::scheduler_operation*, bool) () from /lib/arm-linux-gnueabihf/libgnuradio-blocks.so.3.8.2 No symbol table info available. #1 0xa98c0c38 in...

Yeah same on the refresh token as this is a security issue. You should actually just send the refresh_token as a http-only token. That way the frontend doesn't have access...