-
Updated
Jun 15, 2021
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.
Angular
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
Description
We have to continuously push for quality, thus we always need to improve our testing and test coverage. Any improvement of testing is a great contribution to jina.
If you have no idea how to get started on this, here there are some ideas that could be good to have.
- Increase coverage
Checking the reports on `https://codecov.io/gh/jina-ai/jin
Game Off
November 01, 2021 - December 01, 2021 • Online
nvim --version:
NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC
Made in India
Open source projects built in or receiving significant contributions from India :india:
Codecov | Code Coverage
Codecov provides highly integrated tools to group, merge, archive and compare coverage reports.
- Uploads coverage reports from your CI
- Merges all builds and languages into one beautiful, coherent report.
- Displays coverage data in GitHub Files tab
Is your team using GitHub Enterprise? If so, check out Codecov Self-Hosted.
Do you have less than 5 users in your organization? You can sign up for free on codecov.io.
-
Updated
Jun 15, 2021 - JavaScript
-
Updated
Jun 15, 2021 - JavaScript
-
Updated
Jun 15, 2021
What article on docs.github.com is affected?
https://docs.github.com/en/free-pro-team@latest/developers/apps/migrating-oauth-apps-to-github-apps
What part(s) of the article would you like to see updated?
- The migration guide explains how to create a new Github app to replace your old OAuth app
- It's not clear to me if there's a way to move the users to the new app, so they do
-
Updated
Jun 15, 2021 - Python
-
Updated
Jun 12, 2021
-
Updated
Jun 14, 2021 - Python
currently, when making a payment, the fees are being added to the amount sent.
for instance, if someone want to send 10,000 sats, and the fees is 2,000, the total will be 12,000 sats.
the issue to do a send all is that, when the base amount increase, the fee might changes (fee are being calculated dynamically by lnd).
so for instance, if someone has 15000 sats. he would need to have ma
-
Updated
Jun 14, 2021 - JavaScript
add option to trim
If I run trim
echo [[Column1]; [" Value1 a lot of spaces "] [Value3]] | str trim
it trims only "wrong" withe spaced at the beginning and at the end
───┬──────────────────────────
# │ Column1
───┼──────────────────────────
0 │ Value1 a lot of spaces
1 │ Value3
───┴──────────────────────────
It it would be great a complete white spaces cleaning
-
Updated
Jun 14, 2021 - JavaScript
-
Updated
Jun 12, 2021
-
Updated
Jun 14, 2021 - HTML
-
Updated
Jun 15, 2021 - PowerShell
-
Updated
Jun 12, 2021 - JavaScript
-
Updated
Jun 15, 2021 - JavaScript
-
Updated
May 30, 2021 - C
Sentry
Sentry provides real-time crash reporting, giving your team insight into errors affecting your customers in production. Sentry supports dozens of languages and frameworks and is trusted by thousands of companies like Pinterest, Uber, Stripe, Dropbox, and Airbnb.
Sentry doesn't just alert you to errors, but integrates into your GitHub development flow by linking errors to the commit and author likely responsible, creating new GitHub Issues, and resolving errors with commit message.
Python wheels we build in the CI, such as
PyZMQorLIEF, do not get cached, and are rebuilt every CI run. This wastes time/CPU (LIEFcan take some time to build). The versions of these packages rarely change, so we should be caching and reusing build output.It looks like Cirrus even has a
pip_cachekey, that we may be able to ta