Michael Hale

Huge :+1: to not having to login to read docs.

This issue was discovered because of a support ticket: https://support.heroku.com/tickets/357431

@dmcinnes or @adelcambre any ideas on this one?

I was hitting this issue with puma workers (fork) and was able to resolve it with the following in my puma.rb: ```ruby before_fork do # ensure native libraries are initialized...

``` $ curl 'http://localhost:5000/sign' --data "lu:t" -u 'BecstsYSkJY33Us91kgl6qPubHowWXcqaBxqhu7Nu6_=:' Authentication failed. ``` It looks like this is an encoding error possibly in kr/fernet. If you replace the '_' with some alpha...

I'm not sure. Ruby properly url encodes/decodes strings that l2met/fernet has trouble with. I'm not certain which is out of spec.

This shows that in ruby decoding an encoded string returns the original string: ``` $ dd if=/dev/urandom bs=32 count=1 2>/dev/null | openssl base64|ruby -ruri -e 's=STDIN.read.chomp; puts [s, URI.decode(URI.encode(s))]' sRd/0ehjza+7zMRjmytZG4yNVUJ7+NhyXWZY+dx/Rg4=...

Allowing the time a sample was taken to be specified to l2met would not only help with accuracy for current measurements, but would also allow historical measurements to be piped...

@ryandotsmith hmm I forgot about the timestamp in the syslog header. Does l2met take that timestamp into consideration when determining the time to record the measurement? If so I think...

Not being an expert on how the receiver stuff works... what are the effective limits on wanting to backfill sample data? Are buckets even required for sample data?