TGINSIGHT SIMILAR POSTS
Source channel @githubtrending · Post #14713 · May 16
#go#bugtracker#decentralized_application#distributed_systems#git#gitdb git-bug is a powerful, decentralized issue tracker that stores issues, comments, and users directly inside a Git repository as versioned objects, not just files. This means you can manage your issues offline, sync them later, and keep everything clean and organized within your existing Git workflow. It’s very fast, supports syncing with platforms like GitHub and GitLab, and offers multiple ways to interact, including command line, text user interface, or web browser. This tool helps you track and manage project issues efficiently without needing a separate server or database, making collaboration and version control seamless. https://github.com/git-bug/git-bug
Search: #scheduled
@luckydonaldsbots · Post #290 · 12/11/2021, 10:33 PM
Also there will be a scheduled downtime for two remaining bots tomorrow, in about 16h 20h from now : - @BanWarnBot - @RulesRulesBot Those have a database, and therefore they need to be take down to not loose any changes happining while the data is moved over. #scheduled#downtime
Hashtags
@djangoproject · Post #92 · 07/11/2016, 11:59 AM
https://docs.python.org/3/library/asyncio-dev.html#asyncio-coroutine-not-scheduled 18.5.9.6. Detect #coroutine objects never #scheduled When a coroutine function is called and its result is not passed to ensure_future() or to the BaseEventLoop.create_task() method, the execution of the coroutine object will never be scheduled which is probably a bug. Enable the debug mode of asyncio to log a warning to detect it. Example with the bug: import asyncio @asyncio.coroutine def test(): print("never scheduled") test() Output in debug mode: Coroutine test() at test.py:3 was never yielded from Coroutine object created at (most recent call last): File "test.py", line 7, in <module> test() The fix is to call the ensure_future() function or the BaseEventLoop.create_task() method with the coroutine object.
Hashtags