04:44:29 selsta: yes, probably tomorrow though 12:59:02 Who should I prod to get the TXT records updated for update.getmonero.org ? Pony or was that handed around ? 13:54:52 i'm not sure, but binaryfate might have access ^ 14:41:54 only fluffy has access at the moment 15:26:14 the daemon seems to return multiple www-authenticate headers which causes requests from firefox to fail 15:26:51 the daemon is started with: ./monerod --stagenet --rpc-login superuser:abctesting123 --rpc-access-control-origins http://localhost:9100 15:43:02 ideally firefox would handle the issue gracefully like the other browsers, but I'm looking to remove the duplicate from the response 16:00:57 @woodser The daemon do the right thing. It's firefox fetch() api that's broken. 16:04:02 I thought the firefox fetch() api was breaking because it can't parse the daemon's www-authenticate response header, which is either duplicated or separated by newlines instead of commas? 16:05:32 I can see the wallet-rpc return 2 lines: 16:05:41 known firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1491010 16:05:43 WWW-authenticate: Digest qop="auth",algorithm=MD5,realm="monero-rpc",nonce="k7VW9A39o7Dp7OjSnVCA/w==",stale=false 16:05:46 WWW-authenticate: Digest qop="auth",algorithm=MD5-sess,realm="monero-rpc",nonce="k7VW9A39o7Dp7OjSnVCA/w==",stale=false 16:06:02 I see the same from daemon responses 16:09:08 The RFC nnnn says it's correct. But fetch() discard them as duplicates or something. I'll try to find the issue on the tracker... 16:10:44 https://bugzilla.mozilla.org/show_bug.cgi?id=1491010 16:11:58 while it's technically correct, and that issue should be resolved in firefox, we might be able to support firefox in the interim by cleaning up the response headers 16:15:43 How about not using fetch at all? xmlhttprequest do not suffer from same bug. 16:21:17 worth trying 16:22:01 Or https://github.com/request/request-promise can handle digest auth. 16:23:18 When using xmlhttprequest one has to handle the construction of the auth response. Not that it's that hard.. 17:39:50 selsta see PR 6407 17:40:44 thanks, trying it currently 17:42:57 What's the difference between std::string(host) and std::string{host} ? I tried the former and it did not help, and I thought it was the same. 17:43:26 it is, but maybe applied to the wrong line? the compiler was giving funky line numbers for some reason 17:43:58 I think the compiler was saying the line on get_host was the issue, but it was set_host 17:43:58 I did it for both the set and get IIRC. Even though it only moaned about one. 17:44:06 also C++ compiler error messages are useless 17:44:10 :D 17:44:45 Then I guess I messed up something else -_- 17:44:46 no it gives the correct line number 17:45:04 nah, they are extremely helpful, you just have to be a compiler writer to understand them 17:45:17 lol so I guess not very helpful most of the time 17:45:26 right, I guess you need a lot of experience to to appreciate them 17:45:52 the thing is they are often times giving the equivalent of stack traces for templates 17:46:19 do you know why this compiled on Windows? 17:46:21 so its quite noisy and you have to look at the bottom of the stack first 17:46:26 the tests arent built 17:46:29 or is release-static not building tests? 17:46:29 ok 17:46:49 its a cmake command to request it 18:05:03 Oh. I tried again, it does work, but the error comes up for a second similar case, I did not notice the liner number was further out. 18:07:51 luigi1111: can you merge #6407 to fix compilation? ty 18:20:56 Reminder meeting tomorrow 17 UTC https://github.com/monero-project/meta/issues/449 18:21:12 (take into account hour change tonight) 19:10:50 done