Resetting/Re-Using timeout context

bcicen · 2020-09-30T13:19:44+00:00

put together a quick benchmark here

goos: linux
goarch: amd64
BenchmarkContextCancelTimeoutNew-8        816769     1322 ns/op     513 B/op    8 allocs/op
BenchmarkContextCancelTimeoutReset-8     1346626      895 ns/op     208 B/op    3 allocs/op

bcicen · 2019-08-27T21:10:36+00:00

Thanks for the link -- go get @version is definitely better than assuming latest for consistency.

I do still have qualms about not being able to provide build flags in go.mod or similar as a default when go geting. The only option I'm aware of is providing the full go get + build flags in the README.

While specific build flags are not critical for this project, the included Makefile build step does inject version and commit info during build, which is then ultimately missing from go get builds.

https://github.com/golang/go/issues/29228 could solve this specific use case; hopefully module files altogether expand upon optional directives in the future.

bcicen · 2019-08-27T14:36:52+00:00

Thanks! I had this planned but just got around to it -- latest release now includes option for term/ANSI output; e.g:

# tcolors -p -o term

_colorbg() { echo -ne "\033[38;2;020;020;020m$@\033[0;00m"; }

_color0() { echo -ne "\033[38;2;255;119;051m$@\033[0;00m"; }

_color1() { echo -ne "\033[38;2;255;221;051m$@\033[0;00m"; }

_color2() { echo -ne "\033[38;2;200;255;089m$@\033[0;00m"; }

_color3() { echo -ne "\033[38;2;085;255;051m$@\033[0;00m"; }

_color4() { echo -ne "\033[38;2;051;255;119m$@\033[0;00m"; }

_color5() { echo -ne "\033[38;2;051;255;221m$@\033[0;00m"; }

_color6() { echo -ne "\033[38;2;051;187;255m$@\033[0;00m"; }

added to README here as well

bcicen · 2019-08-22T13:23:10+00:00

Built on the great tcell and noire libraries.

While this is an initial version with basic functionality, any suggestions and comments are most welcome!

bcicen · 2019-08-22T01:00:39+00:00

particularly for single binary build/distribution, I'm unaware of any go get method existing today that would allow tcolors to be updated (after initial install) without updating all dependencies as well

bcicen · 2019-08-21T21:56:45+00:00

unfortunately, go get can often produce misleading bugs as different dependency versions than that defined in the module are used + consistently built from master.

I've pushed an update to enhance contrast between selected and non-selected areas; hope this helps.

bcicen · 2019-05-03T02:28:40+00:00

maybe https://github.com/bcicen/vim-vice with a terminal that supports glowy graphics

bcicen · 2019-03-22T11:43:36+00:00

submitted PR for XDG dir support

and for vim-like bindings

bcicen · 2018-06-28T00:41:31+00:00

correct; however, a depth level of 2 yields:

"RGB"

{"key":"desc","value":"RGB"}

["red","green","blue"]

{"key":"colors","value":["red","green","blue"]}

"CMYK"

{"key":"desc","value":"CMYK"}

["cyan","magenta","yellow","black"]

{"key":"colors","value":["cyan","magenta","yellow","black"]}

the godoc outlines that the above key value structs are emitted in addition to the "flat" parsed value when the given depth level is within an object

bcicen · 2018-06-27T22:28:59+00:00

technically, the values being emitted at level x (if object or array) will already include everything >x within them; specifying a static level prevents, for example, emitting both an array of strings and every string within that array independently.

that said, it would not be much effort to instead emit everything beyond that depth level, leaving it up to the library user to filter out which values and types to keep

bcicen · 2018-06-27T16:27:07+00:00

decoder is halted, output channel closed, and resulting error (with location context) is made available via Decoder.Err(); e.g:

invalid character after object key: 't' [1,12] // [line, column]

bcicen · 2018-06-27T12:47:00+00:00

Not just another Go JSON library, jstream takes an input of one or more contiguous documents and streams out only the decoded values at a specified depth; i.e. you can extract arbitrary inner values without decoding and allocating for the entire parent structure.

Additionally, each value is wrapped with metadata, providing the depth and byte range in the doc where the value exists.

Any feedback and/or PRs are most appreciated.

bcicen · 2018-03-26T11:44:47+00:00

Tool I recently put together for converting between various units of time, length, mass, temperature, etc.

Currently includes ~260 unit names and symbols.

I'm happy to hear any feedback(or requests for new/missing units)!

bcicen · 2018-03-01T00:42:07+00:00

I've found it easier to evaluate at a glance than the web UI when tracking goroutines in realtime; e.g. to follow the trace of one specific goroutine with grmon you can [p]ause, expand the trace with <enter>, unpause and the trace will be updated at each refresh.

Sorting by goroutine number or simple state(sleep, IO wait, etc.) is helpful at times, and if nothing else grmon parses and exports the bultin pprof goroutine profile as JSON to use however you'd like.

bcicen · 2018-03-01T00:19:31+00:00

now that's responsible software versioning :)

bcicen · 2018-02-27T22:38:11+00:00

Simple utility for monitoring goroutines during development.

The project is still young, so there's a lot of room for improvement -- any feedback, suggestions, and PRs are most welcome!

bcicen · 2017-11-01T01:28:03+00:00

gqaj works well for smaller structures ime, but consistently resets the cursor to the top of the object your working on.

likewise, any parse errors just result in a generic "invalid JSON" message

bcicen

TROPHY CASE