Trending repository
-
Updated
Aug 15, 2021 - Go
Your favorite open source projects and the developers who make them happen. Listen in!
August 17, 2021 • Online
Open source projects built in or receiving significant contributions from India :india:
Hound reviews your code then comments directly in Pull Requests, helping your team maintain consistent coding style and high code quality.
Here is a list of links that return 404
https://apility.io/apidocs/
http://developer.linkedin.com/docs/rest-api
https://sentim-api.herokuapp.com/ works
https://quarantine.country/coronavirus/api/ works
https://blog.mugenmonkey.com/2017/09/10/ds3-api.html
https://developer.walmartlabs.com/docs
https://taylor.rest
Please feel free to add more broken links when you find t
RPCs that return detailed information about mempool entries (e.g. getmempoolentry and getrawmempool(verbose=True) include the fields fee, modifiedfee, descendantfees, and ancestorfees which were marked as "DEPRECATED" and replaced with a fees object field in #12240 (since v0.17).
We should remove these fields, but first, properly deprecate them using -deprecatedrpc.
Describe the solution you'd like
It'd be nice to actually apply the security framework when building.
Describe alternatives you've considered
Ignoring security problems won't help.
Errors:
126. new Intl.NumberFormat is not supposed to get passed a single object as param. The first param must be a string and the second param can be an object.
135. Spelling error ('tis' should be 'this').
Suggestion:
86. Needs to be more explicit by calling the function in the example. Calling getName() with any falsy value would not set hasName to true with your correct answer.
Sonatype Lift helps you find and fix your most elusive bugs so you can spend time writing great code, not debugging it. Lift looks for a broad range of performance, security, and reliability errors in the code you write and the libraries you depend on, making it an ideal all-in-one bug catcher for your entire company. Running at each pull request, Lift delivers results as code review comments so you can fix bugs in minutes. (Yes really)
Most of the functions from
statedb.goperform a no-operation (no-op) when an error is encountered. The problem is, that these functions don't have any context of whether previous calls failed or not. For example, bothGetCodeHashandGetNoncerequire the account to exist before returning the value.Solution:
Introduce a
stateErr errorfield on theKeeperand return early on every