- Berlin, Deutschland
- https://sneak.berlin
- Joined on
2020-02-05
user@heraklion:~/tmp/quak$ time timeout 15 $Q collections
real 0m15.026s
user 0m2.412s
sys 0m0.325s
user@heraklion:~/tmp/quak$ time timeout 60 $Q collections
real …
user@heraklion:~/tmp/quak$ time timeout 15 $Q collections
real 0m15.026s
user 0m2.412s
sys 0m0.325s
user@heraklion:~/tmp/quak$ time timeout 60 $Q collections
real …
there should be a -v or --verbose option that increases the verbosity/log level. specifying it multiple times (i.e. -vv or --verbose --verbose, or -vvv etc) should increase it by that…
mandatory arguments (e.g. 'collection' to 'files') should be positional - e.g. 'quak files ' not flags. this only holds if there are only 1-2 mandatory args. also 'files' should…
b23cf43abf
resolver: a reply marked recursion available from a root server's address stops the lookup (closes #300)
rather than tagging release candidates, just release a 0.0.2 and an 0.0.3 and so on until a 1.0 is ready.
seems to be correct.
your todo:
-
make
go install ...@latestinstall the latest green commit, i.e. main's tip. -
make
sfdupes infoshow the database information: size, rows,…
root@las1stor1:# export SFDUPES_DATABASE="/srv/tmp/sfdupes/db.db"
root@las1stor1:# ./go/bin/sfdupes scan --workers 150 /srv/
⠼ walk (1250586/-, 11448 files/s) [1m10s]
meanwhile, nothing…
root@las1stor1:~# go/bin/sfdupes trees
^C
root@las1stor1:~#
Took far too long, strace on the pid was hanging too. No idea why it was hanging, I don't even know where the database…
root@las1stor1:~# go/bin/sfdupes trees
<hangs>
The tool should always give the user some feedback to show it is doing something and isn't hung. It should show what phase it's on,…
fsn1app1# dig +norec @198.41.0.4 desec.io NS
; <<>> DiG 9.18.39-0ubuntu0.24.04.8-Ubuntu <<>> +norec @198.41.0.4 desec.io NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;;…
user@heraklion:~$ dig +norec @198.41.0.4 desec.io NS
dig +norec +tcp @198.41.0.4 desec.io NS
; <<>> DiG 9.10.6 <<>> +norec @198.41.0.4 desec.io NS
; (1 server found)
;; global…
no. on a network that is filtering/altering DNS packets, the tests should fail!
yes, option 2. upaas is up now and i'm ready to set up the autodeployment. what settings do i need to set in env?
no, just turn off cgo and keep gorm for now. figure out a way to turn off cgo in tests as well.
Do not assume this means the others are a no; just not approved for the time being.