Will release soon
926 karma · joined March 2, 2015
https://mrkaran.dev
Will release soon
https://github.com/mr-karan/doggo/pull/128#issuecomment-2202...
However, each lookup happens serially right now, I'll take a look at making it concurrent per resolver atleast.
Edit: I just pushed the concurrent version of lookups in each resolver. Speed up is quite good around 70-80% on most domains. Will test this more before releasing to main!
https://github.com/mr-karan/doggo/pull/128#issuecomment-2202...
I liked the output of: doggo @bbs-over-dns.com txt bbs-over-dns.com | sort | less
Yes, you can run the web server locally: https://github.com/mr-karan/doggo/tree/main/web
cd web
go run . time doggo google.com A AAAA AFSDB APL CAA CDNSKEY CDS CERT CNAME CSYNC DHCID DLV
0.02s user 0.02s system 1% cpu 2.981 totalMeanwhile, the docs link is https://doggo.mrkaran.dev/docs/
go install github.com/mr-karan/doggo/cmd/doggo@v1.0.2 doggo google.com --short
142.250.185.238 alias doggo-all='doggo $1 A AAAA AFSDB APL CAA CDNSKEY CDS CERT CNAME CSYNC DHCID DLV DNAME DNSKEY DS EUI48 EUI64 HINFO HIP HTTPS IPSECKEY KEY KX LOC MX NAPTR NS NSEC NSEC3 NSEC3PARAM OPENPGPKEY RRSIG RP SIG SMIMEA SOA SRV SSHFP SVCB TLSA TSIG TXT URI ZONEMD ${2:+@$2}'
doggo-all example.com @1.1.1.1Was just mentioning on my other comment[1] about your contributions to the tool.
go install github.com/mr-karan/doggo/cmd@latest
go: downloading github.com/mr-karan/doggo v1.0.0I've built this using Go, my daily driver. It doesn't use any CLI frameworks, that was mostly out of choice as I didn't want to add external deps unless really required. My favourite part was to build this small help.go[3] utility which renders colored/formatted help text.
Over the time I got some good quality external contributions, especially the one from @jedisct1 for adding DNSCrypt[2] support to it.
Releasing a v1.0 has been on the back burner forever (like, a whole year+ :'). Life, other projects, and probably a bit of procrastination got in the way. Finally sat down last week and forced myself to come up with a deadline to push this out.
[1]: https://mrkaran.dev/posts/ndots-kubernetes/
[2]: https://github.com/mr-karan/doggo/pull/17
[3]: https://github.com/mr-karan/doggo/blob/main/cmd/help.go
SELECT *
FROM read_parquet([
's3://bucket/file1.parquet',
's3://bucket/file2.parquet'
]);
[1]: https://duckdb.org/docs/extensions/httpfs/s3api#reading> For the contract note generation job, we spawn about 40 instances in total currently, a mix of c6a.8xlarge, c6a.2xlarge, and c6a.4xlarge.
I've also written about it here: https://mrkaran.dev/posts/clickhouse-replication/
Can you elaborate more on this? How do the workers know when they have to process a new job?
Also, am I right in assuming this is typically a single node setup only, as all the files are mounted on a non "share-able" XFS disk?
[1]: https://fedoraproject.org/silverblue/
[2]: https://docs.fedoraproject.org/en-US/fedora-silverblue/toolb...