-
Updated
Jun 12, 2021 - Swift
Here's what's popular on GitHub today...
We’ve seen some amazing community projects this last month. This was a huge month for the community with hundreds of new releases. There’s everything from world-changing tech to weekend hobbies.
Phaser
-
Updated
Jun 13, 2021 - C
-
Updated
Jun 10, 2021 - PowerShell
Game Off
November 01, 2021 - December 01, 2021 • Online
-
Updated
Jun 12, 2021 - Python
Text editors
The text editor is a sacred tool for developers. Here's a showcase of some amazingly awesome open source editors.
CloudBees CodeShip
Fast, Easy and customizable
With faster feedback cycles, local debugging, build caching and customized environments, CodeShip helps you build the products your users love.
-
Updated
Jun 5, 2021 - Java
-
Updated
Jun 12, 2021 - C++
-
Updated
Jun 12, 2021
-
Updated
Jun 13, 2021
-
Updated
Jun 12, 2021
-
Updated
Jun 12, 2021
Issue Type: Bug
After updating my VS Code, my debugging experience became unpredictable and would pause unexpectedly. I've traced down the root cause in my code to an instantiation of a node Worker (from the worker_threads module).
I have created a simple reproducible scenario with instructions here.
The problem manifests when a
-
Updated
Jun 11, 2021
-
Updated
May 15, 2021
-
Updated
Jun 13, 2021 - Python
-
Updated
Jun 9, 2021
-
Updated
Jun 6, 2021 - C++
-
Updated
Jun 13, 2021 - Jupyter Notebook
-
Updated
Jun 12, 2021 - JavaScript
Current implementation of Go binding can not specify options.
GPUOptions struct is in internal package. And go generate doesn't work for protobuf directory. So we can't specify GPUOptions for NewSession.
Steps to reproduce
In Full Kubeflow mode, select a pipeline and click Create Run. During selecting experiment, open a dialog to select existing experiment.
By default, there is no available experiment, but there is no w
Stale
Automatically close stale Issues and Pull Requests that tend to accumulate during a project.
How it works
After a period of inactivity, a label will be applied to mark an issue as stale, and optionally post a comment to notify contributors that the Issue or Pull Request will be closed.
If the Issue or Pull Request is updated, or anyone comments, then the stale label is removed.
If no more activity occurs, the Issue or Pull Request will be automatically closed with an optional comment.
With PaperMC getting access to the new GitHub templates that are slowly rolling out, it would be cool to consider some kind of command to help pre-fill information for reporting bug
As seen here (https://github.com/PaperMC/Paper/blob/0d92e6b53f1889fadc6a6c6aaf72b7e83a37aa31/.github/ISSUE_TEMPLATE/behavior-bug-or-plugin-incompatibility.yml) PaperMC is already in the works on the new template st