News for hackers. Stuff that matters.

axw

Re:Grafana Tempo, a scalable distributed tracing system on Friday October 30, 2020 @03:28AM (#24939932)
Yes, you can do this using Filebeat or in Elasticsearch itself using an Ingest node script processor.

Filebeat: https://www.elastic.co/guide/en/beats/filebeat/current/elast... (You can incorporate variables in the destination index; variables may refer to labels and other fields.)

Ingest node: https://www.elastic.co/guide/en/elasticsearch/reference/curr... (search for "_index")

Re:Ask HN: How do you review code? on Sunday April 03, 2016 @08:59PM (#11418737)
FYI, Eric Snow has implemented an OAuth extension for Review Board: https://bitbucket.org/ericsnowcurrently/rb_oauth_extension

We use this in the development of Juju. We also have a bot that creates Review Board reviews from GitHub PRs, and updates the diffs when the PR is updated.

Re:Portable Native Client on Tuesday November 12, 2013 @08:11PM (#6722676)
Indeed, something I have been thinking about for over a year ;)

http://blog.awilkins.id.au/2012/12/go-in-browser-llgo-does-p...

Sadly I don't have a lot of time, so progress is quite slow. The PNaCl support isn't working at all at the moment, as I'm going through a fairly major refactoring to make things a bit more solid.

Re:Llgo on Go 1.1 on Sunday May 19, 2013 @08:02AM (#5732636)
Author here.

Fair enough. I wrote that post for a much smaller audience (namely, people already following the llgo project), and certainly didn't expect it to be posted to HN. You're right of course, I should always consider people unfamiliar with the project stumbling across my posts.

Re:Llgo on Go 1.1 on Sunday May 19, 2013 @07:59AM (#5732631)
I haven't even thought about that to be honest, but there's not currently anything that would preclude embedding code generated by llgo in a C program. This might change in the future, with the introduction of goroutine scheduler and segmented stacks.

I don't know the first thing about iOS development, so can't comment there.

Re:Llgo on Go 1.1 on Sunday May 19, 2013 @07:30AM (#5732581)
There's a wiki page on the GitHub repo: https://github.com/axw/llgo/wiki/Unimplemented-and-incomplet...

If you'd like to work on a feature, please let us know on the llgo-dev group: https://groups.google.com/forum/?fromgroups#!forum/llgo-dev

Please be aware that this is still fairly rough around the edges, and I'm new to this game (compilers/language implementation, beyond toys).

Thanks!

Re:Go 1.1 RC1 is out on Friday May 03, 2013 @12:02AM (#5648747)
The gory details are here: https://docs.google.com/document/d/1bMwCey-gmqZVTpRax-ESeVuZ...

TL;DR: functions are now represented as (function pointer, pointer to a context structure), whereas before they were represented as a single function pointer.

Re:Show HN: Perl-based server-management tool on Tuesday March 05, 2013 @07:42PM (#5328546)
I haven't seen that before. Thanks, it brought a smile to my face. I made this a few years ago: https://github.com/axw/pushy

Pushy is Python-based, not PERL-based, but otherwise it's similar what you/Matt describe. It never really made much ground, though I recently became aware that Ceph is using it in their ceph-deploy deployment program.