These are chat archives for arenanet/api-cdi

14th
Sep 2016
darthmaim
@darthmaim
Sep 14 2016 07:03
whoops, i am awake now
no idea what happened
everything looks normal
can you tell me which endpoint it was?
windwarrior
@windwarrior
Sep 14 2016 12:07
soo glad I make javascript only applications
you guys can never trace it back to me >:D
Archomeda
@Archomeda
Sep 14 2016 12:17
unless they start tracking the Referer header :P
or Origin iirc
windwarrior
@windwarrior
Sep 14 2016 16:26
haha yeah x)
but not by simple ip lookups
your flow analysis tools are not gonna blame me :>
Pat Cavit
@tivac
Sep 14 2016 16:37
@darthmaim just lots and lots of connections in TIME_WAIT
Archomeda
@Archomeda
Sep 14 2016 16:42
oh, github changed their emotes? D:
FWIW, TIME_WAIT means our side has closed the TCP connection, but is waiting for a FIN/RST from your side. Since you're using guzzle (which is using cURL internally) it's probably not going to be something easily fixable
The map tiles should be updated in a couple of hours -- uploaded the new ones overnight and now there's a Cloudfront cache invalidation running
Sometimes the invalidation takes awhile to reach all the edges
windwarrior
@windwarrior
Sep 14 2016 17:17
sounds like a socket not being closed
pretty much; sounds like cURL is trying to re-use them but not actually re-using them
I only had a cursory glance at it, but it may have to do with the use of Guzzle\Pool -- IIRC each pool is backed by a curl_multi_t which does its own connection pooling. I think the current code creates Guzzle\Pools on the fly rather than re-using the existing one; it's kind of a shot in the dark but that might be a culprit
windwarrior
@windwarrior
Sep 14 2016 17:19
a 'curlprit' you mean ;)
I'll show myself out
:shipit:
Jonathan Andrist
@rwfrk_twitter
Sep 14 2016 18:33
Yay tiles!! =)
Edgar Doiron
@Coffee4cr
Sep 14 2016 19:11
Tempting, but conversion to CAD sucks
$40+
For anyone using /v2/backstory/* there's an unfortunate breaking change coming in the next month or so: arenanet/api-cdi#360
The backstory answer ids are becoming strings rather than numbers :(
Archomeda
@Archomeda
Sep 14 2016 21:13

the mesmer and revenant backstory question has the same answer ids

wat

the answer ids aren't generated like other ids -- they're just typed in by-hand
they're also persisted in the character blobs
so they can't be changed
Archomeda
@Archomeda
Sep 14 2016 21:17

Pull Request Review is now available. Learn more.

huh, i should keep myself more up-to-date with github changes

specifically -- the revenant/mesmer answer ids are 187,188,189, with this change they'll become 188-187,188-188,188-189 and 189-187,189-188,189-189
Archomeda
@Archomeda
Sep 14 2016 21:17
interesting
huh this is news to me too
Archomeda
@Archomeda
Sep 14 2016 21:19
i suppose it's nice to have reviews separated in categories
or comments, w/e
it's more than that really -- you can mark a branch as protected and it requires at least one approval to merge
Archomeda
@Archomeda
Sep 14 2016 21:20
don't know how it looks like in the PR though

If required reviews are enabled and a collaborator with write, admin, or owner access to the repository submits a review requesting changes, the pull request cannot be merged until the same collaborator submits another review approving the changes in the pull request.

not sure if i would like this though

oh wait
read it incorrectly
i thought it was about a collaborator submitting a PR and that he should approve his own PR, but it's about submitting a review instead
yeah
basically it allows a user with write access to block a PR from being merged until they approve it
Archomeda
@Archomeda
Sep 14 2016 21:28
can a collaborator merge a PR too? in that case i can understand how this can work

otherwise

Repository owners and administrators can merge a pull request even if it hasn't received an approved review, or if a reviewer who requested changes has left the organization or is unavailable.

makes it a little bit redundant

My understanding is that a collaborator can merge a PR without reviews, as long as it isn't to a protected branch
PRs merging into a protected branch need at least one approval review
(from an owner/administrator)
Archomeda
@Archomeda
Sep 14 2016 22:24
hmm alright
Archomeda
@Archomeda
Sep 14 2016 22:41
psst @lye, now that i see that gw2e has been updated, what's the status on #274?
hmm lemme check on that
actually the backend fix might have been deployed
hmm I thought I was in 5 guilds. Wonder where that extra slot came from >_>
Archomeda
@Archomeda
Sep 14 2016 22:45
but yeah, just mentioned that since i saw that my gems count was still at 1028 according to the api, while it hasn't been that for a while now ^^
iirc the 6 guilds count had something to do with the wvw beta or something
oh that makes total sense actually
Archomeda
@Archomeda
Sep 14 2016 22:46
i don't know how that happened, but i remember some people talking about it back then
I should filter out all of the non-live guilds from the API
it's kind of complicated to explain :\
Archomeda
@Archomeda
Sep 14 2016 22:47
does it have something to do with the live <-> beta account linking?
yeah
Archomeda
@Archomeda
Sep 14 2016 22:47
urgh
basically there's some components (including guilds) that work cross-branches
and the wvw beta was a separate branch (normally live only has one branch)
so you could be in 5x live guilds and 5x wvw guilds
and maybe the API doesn't correctly filter out the non-live guilds or something; not entirely sure
Archomeda
@Archomeda
Sep 14 2016 22:48
@queicherius may have an example
the guilds are flagged with which branch they belong to so it should be pretty straightforward to fix
Archomeda
@Archomeda
Sep 14 2016 22:49
but yeah, that beta was pretty interesting tbh :D
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:49
gotta love the new build message. 3 hr. 1 hr 45, 2 hr 15, 1 hr 15, 1 hr 15, 2hr 15, 2 hr, 1 hr, 1hr 45, 50 mins
Archomeda
@Archomeda
Sep 14 2016 22:49
i remember i could log in on both live and wvw beta at the same time, and confuse people with my character names in guild chat xD
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:49
*in sequence in my chat log
Archomeda
@Archomeda
Sep 14 2016 22:50
you probably moved from instance -> open world -> instance -> open world
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:50
the times are not going down.
Archomeda
@Archomeda
Sep 14 2016 22:51
hmm, maybe it repeats once you enter an instance from open world and vice versa?
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:51
I didn't even type out the repeats lol
it should be 3 hr, 2 hr 45, 2 hr 30, 2hr 15..
Archomeda
@Archomeda
Sep 14 2016 22:52
but do we have a new build?
maybe someone clicked the "start countdown" button too many times and there's multiple timers running in parallel :/
i've no idea how that stuff works
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:52
not on your server.
oh, rip
@Archomeda the wallet fix stuff still hasn't been deployed
Archomeda
@Archomeda
Sep 14 2016 22:52
oh :(
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:53
lol the timer is manually activated?
if I'd afked long enough for two builds?
windwarrior
@windwarrior
Sep 14 2016 22:53
yep, there is someone at anet that types these messages flawlessly every 15 minutes
I think there might be a button to start it? It might just be tied to the "okay players can log into this new build" function.
windwarrior
@windwarrior
Sep 14 2016 22:53
(s)he got specially selected for it
only people allowed that have zero type errors and a swiss made watch
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:54
ahaha
I wondered if it was a UTC/local time/server time error
but the half hour skips don't make sense even then
windwarrior
@windwarrior
Sep 14 2016 22:55
which - interestingly - only means that the final assembly was done in switzerland
so basically your entire watch is made in china, except final assembly
Archomeda
@Archomeda
Sep 14 2016 22:55
sometimes the messages are also weird, as in: 3h, 2h45, 2h45, 2h15 (skipped 2h30)
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:55
might be a rounding issue
Archomeda
@Archomeda
Sep 14 2016 22:56
odd rounding issue then
ChieftainAlex
@ChieftainAlex
Sep 14 2016 22:56
I guess this bug won't ever be fixed because most players log out +reboot after 2 mins of yellow messages
Archomeda
@Archomeda
Sep 14 2016 22:56
looks more like an if-statement in a function firing too early or something
windwarrior
@windwarrior
Sep 14 2016 22:56
the person that got hired was not too good in writing FizzBuz
okay, </endtrollmodes>
Archomeda
@Archomeda
Sep 14 2016 22:58
if (minutes < 60) { 1h; }
else if (minutes < 75) { 1h15m; }
else { etc... }
and then it might have been exactly 75 minutes or something
also, screw calculating seconds, you get my example :P
also @queicherius, thanks for that new graph for my death count + per hour... sighs
windwarrior
@windwarrior
Sep 14 2016 23:00
oh damn
ChieftainAlex
@ChieftainAlex
Sep 14 2016 23:39
looking at https://gw2efficiency.com/account/statistics/statistics.deathCountPerHour - median deaths per hour increases with age through to 1000 hrs, so players get more reckless? sounds about right