[00:46] is there a chart for LP load and downtimes? is there a window of time when LP is less busy? [00:47] clivejo: LP is down for a couple of seconds every week or two. Is there a specific problem that you're seeing? [00:48] wgrant: I notice a lot of Launchpad is available errors popping up in KCI logs [00:49] That sounds like the problem, rather than trying to target times when it's up. [00:49] Can you provide more details on those errors? Any specific times, numbers, response codes? [00:49] What were the requests trying to do? [00:50] upload [00:50] Upload? [00:50] dput to PPA [00:50] That hasn't been down in several months. [00:51] What's the specific error that you're seeing? [00:51] hold on a sec, trying to find one [00:51] Ive retried most of them [00:54] maybe its the API is going down? [00:57] clivejo: It's certainly not going down, but it's possible that the occasional request may fail. It's very difficult for us to diagnose your problem without further details. [00:58] The specific requests that fail, the times of those failures, exact error messages, etc. [01:01] finally found one! [01:01] its a HTML page with title Launchpad is temporarily unavailable [01:02] Technically, the load balancer took too long to connect to an application server. [01:02] OK. [01:02] I'd expect that request to work after a couple of seconds. Do you have retry code in place? [01:03] I'll investigate the underlying issues, but web service clients should usually be able to cope with occasional failures. [01:03] What was the timestamp of that failure? [01:03] Im reading more of the log [01:03] ok so it did upload [01:03] so it must be the API connection? [01:04] dput doesn't use HTTP, so it can't really return an error page. If you're making API requests then it's probably an API request, yes. [01:04] checking to see if the builds complete and publish [01:04] Does the traceback say which request it was? [01:04] Launchpad has many hundreds of APIs. [01:05] seems to be around the publishing stage [01:06] the code doesnt hand the error and fails the entire package [01:11] wgrant: it just done it [01:11] dumped the entire queue of 16 packages [01:11] clivejo: Do you know what the request was? Is it consistent? [01:12] It's possible that requests are randomly failing, or it's possible that you are making a specific request that is taking too long. [01:13] Im looking at the code we are using [01:13] Launchpad employs server-side caching, which is nice but for our purposes 90% of the time we need current data, otherwise we wouldn't be polling on a schedule. [01:13] thats the comment on this code block [01:15] response = http.request_get(uri, 'Cache-Control' => 'max-age=0') [01:15] and this is where the code is dropping out [01:16] I need to know what the request is. [01:16] eg. the URL [01:27] wgrant: sorry I cant seem to find out the URI it is using [01:27] it was montoring this build - https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+build/10031625 [01:28] which was successfully built on LP, but triggered the error in the CI code [01:30] all 16 packages in the build queue got failed for the same reason [01:32] the response from LP is here - http://paste.ubuntu.com/17421152/ [03:00] Somebody please deal with https://answers.launchpad.net/launchpad/+question/295098 [03:00] FWIW, https://answers.launchpad.net/launchpad/+question/295098/+addsubscriber oopses === JanC is now known as Guest67075 === gkadam is now known as Guest83066 === Ribesgg is now known as Ribesg === funnel_ is now known as funnel === verterok` is now known as verterok === pavlushka is now known as tareq2 === tareq2 is now known as pavlushka === pavlushka is now known as DJ3 === DJ3 is now known as pavlushka [11:54] cjwatson: hi! is it possible to submit merge proposals for git branches in launchpad? [11:55] cjwatson: e.g. https://code.launchpad.net/~barry/+git/usd-importer -> git+ssh://git.launchpad.net/usd-importer [11:55] cjwatson: the former has no clicky button [11:55] barry: Yes, but you have to have your repository in the same namespace, which that isn't [11:55] cjwatson: ah [11:55] barry: You should push your thing to ~barry/usd-importer, not ~barry/+git/usd-importer (which is the equivalent of a "junk" branch in bzr-land) [11:56] cjwatson: cool, let me try that. thanks! [11:56] np [12:05] That feels sort of artificial to me as a git user. It shouldn't matter - you should be able to propose a merge to anything that has a common ancestor by default. [12:40] rbasak: Perhaps, but may be expensive to compute that on the fly and not very friendly to future picker UIs === elopio_ is now known as elopio === nacc_ is now known as nacc [17:44] I filled a support question as a bug and now I want to delete it... how do I do that? [17:45] lerner: the bug should have a "Convert to a question" link [17:46] cant I just delete it? I found relevant information in the forums cjwatson [17:46] no. just mark it invalid [17:47] You can also mark it private if you really don't want anyone to see it, but that usually isn't necessary [17:47] (as well as invalid) [17:48] well, even as private, the project owners/drivers can still see it, though entire public might not === pavlushka is now known as pavlushka- === pavlushka- is now known as pavlushka === pavlushka is now known as pavlushka_ === pavlushka_ is now known as pavlushka === davmor2 is now known as davmor2_HOLS === cmars` is now known as cmars