-
Updated
Sep 5, 2020 - Python
Join GitHub (or sign in) to find projects, people, and topics catered to your interests.
Here's what's popular on GitHub today...
-
Updated
Sep 5, 2020 - C++
Monero
-
Updated
Sep 5, 2020 - Dart
-
Updated
Sep 4, 2020 - Go
-
Updated
Sep 5, 2020 - Go
Text editors
The text editor is a sacred tool for developers. Here's a showcase of some amazingly awesome open source editors.
LGTM
Continuous security analysis
LGTM is a code analysis platform for identifying vulnerabilities and preventing them from reaching production.
LGTM automatically runs 1600+ standard analyses contributed by researchers from the Semmle Security Research Team and our customer community, including Microsoft, Google, Uber and Mozilla.
Quickly refine and run custom QL queries to find variants of known issues and prevent them from being re-introduced into your codebase.
-
Updated
Aug 27, 2020 - C++
-
Updated
Sep 4, 2020 - HTML
-
Updated
Sep 3, 2020
-
Updated
Sep 5, 2020 - Python
-
Updated
Sep 4, 2020
-
Updated
Sep 3, 2020
Describe the bug
When I pull the resize button of the code editor, it doesn't the resize the code in the editor.
To Reproduce
Steps to reproduce the behavior:
- Click the resize button on the code editor and drag it down
- The code doesn't resize
Expected behavior
I expected the code to resize as I drag down the button.
Screenshots
If applicable, add screenshots to
-
Updated
May 15, 2020 - Jupyter Notebook
Will break out a separate bug for array_slice.
Originally posted by @cdleary in google/xls#72 (comment)
-
Updated
Sep 5, 2020 - Jupyter Notebook
-
Updated
Aug 23, 2020
-
Updated
Aug 11, 2020 - Java
-
Updated
Sep 5, 2020 - Batchfile
-
Updated
Sep 5, 2020 - HTML
-
Updated
Sep 5, 2020 - PHP
-
Updated
Sep 1, 2020
-
Updated
Sep 5, 2020 - Python
Its not a issue but its a feedback , Include one line code to deal with streaming http response
Check Run Reporter
Now supporting Checkstyle!
Check Run Reporter takes your JUnit, Checkstyle, and other structured reports and presents their results to you right in the GitHub UI. No more need to dig through your pages of CI logs to find out why your build failed.
For the sake of simplicity we are assuming the write-buffer alignment to be 4096kB, and the read-buffer alignment to be 512b. Those are likely good across the majority of systems, but some disks do not support 512b access.
Linux will tell us on sysfs what is the preferred alignment. We should use that.