Andreas Gerstmayr comments

Results 116 comments of


                                            Andreas Gerstmayr

Should timing badges take into account beforeEach/afterEach?

+1 from me @emilecantin: well, that makes the beforeEach function obsolete ;)

Should timing badges take into account beforeEach/afterEach?

> If your setup is relevant to the success / failure / performance of your test, then it belongs IN the test... In what case is the setup not relevant...

Should timing badges take into account beforeEach/afterEach?

Technically it **is** relevant that your object is initialized when you test methods of it. But I get what you mean, it's not what you test in a particular test....

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

rebased on latest main branch

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

ping for review

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

ping for review

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

rebased on latest main branch

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

no-one interested in replacing SHA-1 in favor of HMAC-SHA256 for password reset tokens?

notifications: use HMAC-SHA256 to generate time limit codes (password reset tokens)

Thanks for merging! 🎉

check why there is a hard dependency on bpftrace in debian packaging

The interaction of the bpftrace PMDA with bpftrace is through forking a new bpftrace process, so we don't need it as a build dependency. Ideally the bpftrace subpackage would have...