Displaying 1 to 10 from 10 results

Ben.Demystifier - High performance understanding for stack traces (Make error logs more productive)

  •    CSharp

.NET stack traces output the compiler transformed methods; rather than the source code methods, which make them slow to mentally parse and match back to the source code. The current output was good for C# 1.0; but has become progressively worse since C# 2.0 (iterators, generics) as new features are added to the .NET languages and at C# 7.1 the stack traces are esoteric (see: Problems with current stack traces).

rebound - Command-line tool that instantly fetches Stack Overflow results when you get a compiler error

  •    Python

Rebound is a command-line tool that instantly fetches Stack Overflow results when you get a compiler error. Just use the rebound command to execute your file. Featured on: 50 Most Popular Python Projects in 2018, the top of r/Python, awesome-cli-apps, awesome-shell, terminals-are-sexy, and awesome-mac.

Pinpointer - Pinpointer is yet another clojure.spec error reporter based on a precise error analysis

  •    Clojure

Pinpointer is yet another clojure.spec error reporter based on a precise error analysis. Notice: Pinpointer is built on top of clojure.spec, which is one of Clojure's new features that have been developed most actively. So, it's still in alpha and its APIs are also subject to change.




grunt-less-imports - A grunt task to create LessCSS import statements from a collection of stylesheet files

  •    Javascript

A grunt task to create LessCSS @import statements from a collection of stylesheet files. Why use this? To get useful error messages from the LessCSS parser, that tell you in what file the error was encountered! LessCSS uses @import statements to aggregate files and will tell you about parsing errors in those files. But maintaining these statements by hand is a pain. In order to automatically aggregate all the style files in a project, a method of first concatenating the files before parsing is widely used. This works but you loose the valuable information about where to fix your mistakes.

php-api-problems - PSR7 Response implementation for the Problem Details for HTTP APIs

  •    PHP

PSR7 Response implementation for the Problem Details for HTTP APIs (RFC7807) specification. To report a single error, all you need to do is pass in the mandatory parameters and you'll be fine.

laravel-appleseed - Prevent the pesky Apple Touch Icon error log entries.

  •    PHP

Eliminate error and server log entries that get thrown by missing favicons, especially the apple-touch-icon.png errors. If you are seeing errors in your server logs, its for a reason: favicons are custom representations of your site, and its probably good to implemented them. This just provides a better user experience for the various devices and browsers that want them.

spectrace - clojure

  •    Clojure

spectrace is a clojure.spec (spec.alpha) library aiming to be a fundamental tool for analyzing spec errors. Although this might be useful enough as it is to make simple error messages, it's not sufficient in some cases due to the difficulty of extracting more useful information from it.


errorlookup - Simple tool for retrieving information about Windows errors codes.

  •    C++

Portable open source tool which can help by translating error codes into a more meaningful text description. The interface is simple - just a box to type your code, and another which displays the details - so there doesn’t seem much to learn. The program also supports a wide range of codes: regular Windows errors, DirectX, NTSTATUS errors, Windows Internet errors, STOP codes, And we think it can probably be configured to read more (Settings > System modules), although there’s no documentation to confirm that and we didn’t test it.

searcher - Query Search Portals from R

  •    R

The goal of searcher is to provide a search interface directly inside of R. For example, within R, there is now the ability to look up rcpp example numeric vector or ggplot2 fix axis labels without having to open a browser, go to a search site, and type the query. By default, the search functions automatically search the last error on call. The search_*() functions can be used to search a query directly from R on major search engines, code repositories, and help websites. The following search platforms are supported: Google, Bing, ixquick, DuckDuckGo, StackOverflow, GitHub, and BitBucket. By default, an appropriate suffix for each platform that ensures relevant results to R is appended to all queries. This behavior can be disabled by using rlang = FALSE.