Justin Crown
Justin Crown
> Hi, right now ther eis no way to deactivate it, there is a function called `upperfy` which is called on the `.set` method for every first level variable. >...
:+1: to the suggestion. As you mentioned, this would save A LOT of copy/paste.
It would be awesome to support this same functionality for service creation as well.
Made a PR for this feature: https://github.com/jpignata/fargate/pull/60
I seem to have the same problem as well. Any updates on this? I'm happy to look into it if nobody else is.
Actually @jkemp101 , I think I see what the problem is based on the comments in the test: https://github.com/closeio/tasktiger/blob/6973a28e7a0c2912a5fb651376a0fd819b9ed713/tests/test_periodic.py#L61 My issue was that I was creating a fresh `TaskTiger` instance...
After spelunking a bit, I see that if a task is scheduled it is considered as `unique`, where `unique` indicates that no more than one task of the given method...
That is sound advice for sure @harrywhite4, but I am running into an issue where the signal is not received upon initial creation. This is due to the fact that...
Thanks for the quick response @harrywhite4. Yes, I have confirmed that in these situations the object is indeed created, despite the signal not being received. As a workaround, I will...
I just merged master into this branch locally and tested it out. Things seem to work as promised: 