On Thu, Jun 25, 2020 at 10:47 AM Marcus Müller wrote:
> On 25/06/2020 05.34, Kevin Reid wrote:
> > There is unfortunately
> > no standard way to tell a block to free the resources it is using, other
> > than ensuring it is "deleted" by dropping all references to it.
>
> Well, technically, when a
> if the process is still alive I kill it.
>> All in all a bit of a hack, but I've got to start somewhere.
>> Cheers,
>> Steven
>> ----------------
>> *From:* Kevin Reid
>> *Sent:* 25 June 2020 04:34
>> *To:* Steven Gillies
>> *Cc:* Discuss-gnuradio@gnu.org
bject:* Re: GNU Radio web API
On Wed, Jun 24, 2020 at 8:04 AM Steven Gillies
mailto:stevengill...@outlook.com>> wrote:
I am trying to build a web API to start and stop flowgraphs remotely
and autonomously.
I am having trouble gracefully shutting down one flowgraph and
movin
Hi Kevin,
you're kind of right:
On 25/06/2020 05.34, Kevin Reid wrote:
There is unfortunately
no standard way to tell a block to free the resources it is using, other
than ensuring it is "deleted" by dropping all references to it.
Well, technically, when a flow graph is finished running,
From: Kevin Reid
Sent: 25 June 2020 04:34
To: Steven Gillies
Cc: Discuss-gnuradio@gnu.org
Subject: Re: GNU Radio web API
On Wed, Jun 24, 2020 at 8:04 AM Steven Gillies
mailto:stevengill...@outlook.com>> wrote:
I am trying to build a web API to start an
On Wed, Jun 24, 2020 at 8:04 AM Steven Gillies
wrote:
> I am trying to build a web API to start and stop flowgraphs remotely and
> autonomously.
>
> I am having trouble gracefully shutting down one flowgraph and moving on
> to the next.
>
> My preferred way implement the services is by running
Hello everyone,
I am trying to build a web API to start and stop flowgraphs remotely and
autonomously.
I am having trouble gracefully shutting down one flowgraph and moving on to the
next.
My preferred way implement the services is by running top_block.start() from my
main thread and
