-
Updated
May 3, 2021 - Python
Here's what's popular on GitHub today...
-
Updated
May 2, 2021
View a 3D model of your GitHub contribution graph. Share it, print it, and more!
Crystal
-
Updated
May 4, 2021 - Python
-
Updated
May 4, 2021 - TypeScript
-
Updated
May 3, 2021 - Jupyter Notebook
Text editors
The text editor is a sacred tool for developers. Here's a showcase of some amazingly awesome open source editors.
Testspace.com
Testspace is an integrated GitHub test solution for Automated, Manual, and Exploratory Test Management
- Publish your Workflow test results with a single command
- Implement Manual Tests as Code using your repository
- Facilitate Exploratory testing in all your sessions
-
Updated
May 3, 2021 - C++
-
Updated
Apr 30, 2021 - PHP
-
Updated
May 4, 2021 - Python
-
Updated
Apr 21, 2021 - Python
-
Updated
May 2, 2021 - Go
-
Updated
Apr 19, 2021 - Shell
If you command a lane change under 45mph, nothing will happen. It it should be clear to the user that no lane change can be done because the speed is too low.
Perhaps instead of the message "Steer Left to Start Lane Change" that appears above 45mph something like "Speed too low for lane change"
-
Updated
Apr 29, 2021 - JavaScript
Bug Description
in src/state/governance/hooks.ts
Line 72: const [name, types] = signature.substr(0, signature.length - 1).split('(')
types may be undefined when the proposal has wrong signiture.
Line 75: const decoded = utils.defaultAbiCoder.decode(types.split(','), calldata)
TypeError: Cannot read property 'split' of undefined
Steps to Reproduce
Call propose function on con
-
Updated
May 4, 2021 - Haxe
-
Updated
May 2, 2021 - JavaScript
-
Updated
May 3, 2021 - C++
-
Updated
May 4, 2021 - C#
-
Updated
May 1, 2021 - Shell
-
Updated
May 4, 2021
-
Updated
May 4, 2021 - JavaScript
-
Updated
May 3, 2021 - Jupyter Notebook
-
Updated
May 4, 2021 - Rust
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.
it's not clear from the Client Libary Guide that the default behavior of
signUpwhen used with the hosted platform is to send an email confirmation,we should: