enctool
sqldb-logger
enctool | sqldb-logger | |
---|---|---|
3 | 3 | |
3 | 339 | |
- | - | |
3.6 | 0.0 | |
8 months ago | 4 months ago | |
Go | Go | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
enctool
-
Ask HN: Anyone have any cool Open Source Projects and looking for contributors?
https://concise-encoding.org/ is looking for help!
I'm planning to release v1 later this year, and there are still a number of things to finish:
- Finish upgrading the portable testing rig (whereby the tests are defined in CTE format so that they can be run against any implementation).
- Bring the Antlr grammar files up to date and make sure they're as easy as possible to build CTE parsers from.
- Add schema validation support to https://github.com/kstenerud/enctool for Concise Encoding documents (using https://cuelang.org/)
- Critiques on the format itself (passages that are unclear or don't make sense, features that shouldn't be there or need more work, etc)
- Implementations in other languages & platforms (CBE is more important to start because one can always use enctool to convert between CBE and CTE).
-
Working in the software industry, circa 1989 – Jim Grey
It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...
There are still a few things to do:
- Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.
- Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.
- Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.
I'm thinking that they should look more like:
c1
-
Ask HN: What are some tools / libraries you built yourself?
Yes, that is exactly the aim of the binary format. It has a few basic concepts like being byte-oriented, 1-byte headers for most things, ULEB128 encoding for large values, same chunking mechanism for all arrays and string-likes, same "open/close" mechanism for all container types, etc.
The binary codec is VERY simple, and can be trivially implemented for an async-safe or otherwise constrained environment. In fact, I expect that many implementations will only build the binary codec, since you could just pass any recorded binary data through enctool [1] or whatever to see or manipulate its contents as a human. An embedded system would have no need to process the text format.
[1]https://github.com/kstenerud/enctool
sqldb-logger
- A logger for Go SQL database driver without modifying existing stdlib usage
-
DB Question: Can I get the final sql query from db.Exec?
You can use this to get instant query logging for sql.DB. https://github.com/simukti/sqldb-logger
-
Ask HN: What are some tools / libraries you built yourself?
sqldb-logger: https://github.com/simukti/sqldb-logger
It's a thin layer that wrap Go (Golang) SQL database driver, it does not change sql.DB usage in any existing Go app.
It is because I prefer to use vanilla Go sql.DB in my web service and I could not find any SQL logger for Go SQL database standard library that can use structured JSON logging.
What are some alternatives?
null - Nullable Go types that can be marshalled/unmarshalled to/from JSON.
logxi - A 12-factor app logger built for performance and happy development
yadm - Yet Another Dotfiles Manager
logutils - Utilities for slightly better logging in Go (Golang).
gutenberg - A fast static site generator in a single binary with everything built-in. https://www.getzola.org
go-logger - Simple logger for Go programs. Allows custom formats for messages.
GoJS, a JavaScript Library for HTML Diagrams - JavaScript diagramming library for interactive flowcharts, org charts, design tools, planning tools, visual languages.
lumberjack - lumberjack is a log rolling package for Go
fselect - Find files with SQL-like queries
phuslu/log - Fastest structured logging
Pion WebRTC - Pure Go implementation of the WebRTC API
glog - Leveled execution logs for Go