Hot answers tagged

13

Funny story... When I first joined the team here at Stack Exchange, Jeff just went around on the trilogy sites and made me a moderator... And he used the "elected" route instead of the "appointed" route, for reasons that are no doubt lost to time (or maybe they're preserved in chat, I can't be bothered to search). This problem shows up on ...


7

Confirmed; see bottom section, below. However, please refer to Provide a way to retrieve questions and answers that have been deleted -- which is "status-planned". This is a feature, not a bug. And this kind of feature has been requested many times. So, shush please, don't ruin it for us. ;) Confirmation info: You can see this behavior (for now) with this ...


6

Yes, that bug is annoying, especially since specifying a todate that's before the fromdate returns a valid result set, EG: { "items": [], "has_more": false, "quota_max": 10000, "quota_remaining": 9995 } -- rather than an error. Having the dates be equal is theoretically possible. Having negative time is impossible (in this context). However, ...


5

This is a bug. The timeline path seems to have several problems. More on these below. The earlier date query returns the result you expect, but look at it in the document explorer: Notice that the entry is a comment and that it has an Owning post. Now if we look at the whole timeline (filtering out some user cruft), we see: Just two revision entries for ...


5

This was fixed in the latest deploy.


5

Confirmed the bug on a post that accrues comments much slower than a typical Stack Overflow question does. Currently, the OP's filter returns "comment_count": 1 on that post. There are no comments. I believe this is a side-effect/bug/quirk with how the API appears to be counting the comments. ¿Perhaps it is counting Ids in the comment table and not ...


5

I don't know for sure what the original problem was, but the most recent issue was a result of implementing a new badge without rebuilding the API. Once the API was pushed to production, the bug was resolved. If it happens again (especially if there's a new badge) please let me (or really any employee) know. We can contact a developer directly. From a ...


5

Recently the user name truncation issue has been fixed in the Stack Apps site, now it is looking good. Screenshot for reference:


5

Yes, this is a serious bug. You can replicate it from any browser using the code below. Every time I run it, it fetches 180 pages at an average rate of 5.51 calls per second. On the 181st call I get: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.stackexchange.com/2.2/tags?page=181&...


4

That is the 2.1 documentation, it's just the title (and perhaps the first sentence) that hasn't been updated. All of the routes added in 2.1 are there, so you don't have to worry that it's missing anything important.


4

Tricky. This was a consequence of the API misinterpreting a normalized field used elsewhere in the system to indicate whether or not a post has upvoted answers. Everywhere else, "is answered" is true if either of the following are met: The question has an accepted answer The question has an answer with a score > 0 The API wasn't doing the "or" check. ...


4

I mean, the value's not wrong, just perhaps not useful? The QPM is taken over the entire lifetime of the site, so 10005086 / 3644369.9112 = 2.745354133577943, where 3644369.9112 is ((Date.now() / 1000) - site.launch_date) / 60 I'm not sure if there'd be a better default timespan though—it's probably better to just pull the question count for the period you'...


4

If you have TamperMonkey installed, this simple script should fix the problem: // ==UserScript== // @name SAHPA (Stack Apps Home Page Aligner) // @namespace http://tampermonkey.net/ // @version 0.1 // @description Aligns the user names on the StackApps Home Page // @author anonymous2 // @match http://stackapps.com/ // @grant ...


3

This was fixed in the latest deploy.


3

Update: Evidence now suggests that the API quota rolls over at a unique time for each app. 24 hours after that app-key, plus IP, combination made its first API call. See this chat message. The quota does reset every 24 hours, but the time seems to wander is custom for every app-instance. Some years ago, I seem to remember it resetting around midnight UTC,...


3

We moved from nginx to HAProxy for our SSL provider this weekend as part of a larger rollout. In the move, we shifted our header checks to the now de-facto standard SSL protocol header. While I thought I fixed all the apps relying on the old header and standardized everything internally, stackexchange.com was left out and thought your auth requests weren't ...


3

Update: Per Kevin Montrose's answer and its comments: The bug has now been fixed and the is_answered property will return true if either of these is true: The question has an accepted answer The question has an answer with a score > 0 To detect just whether a question has an accepted answer, merely check that the accepted_answer_id property is present and ...


3

Fun one. Changes behind the scenes to how closed reasons are handled caused the API to stop getting a real reason and start getting a null one. This was just different enough from failing to get a reason that it went unnoticed, oy. This was fixed in the most recent build.


3

This has been fixed with the latest deploy. There was a bug introduced in our move to elastic search where min/max was applied after paging results, instead of before. This meant that in any question that would typically have a lot of out-of-range results, the first page would tend to be culled down to nothing.


3

The documentation was updated sometime in the last 2 years and the API docs (version 2.2) now state that the property may be absent:


3

This design issue has been fixed in the How to Format section. Currently the text is visible correctly: ► backtick escapes `like _so_` Screenshot for reference:


3

The console JS was doing fuzzy matching on ?site; but that's not really correct, as you demonstrated. With the latest deploy it does an exact match if possible.


3

This seems to have been silently/magically fixed in the last 7 months (Date of Nicos Karalis' comment). Descriptions seem correct now. I had verified that they weren't correct when I upvoted this question on Apr 29 '14. Side note: It's not documented, but apparently tag-based badges are not listed unless they have been awarded at least once. Take a look ...


3

I faced the same issue when I was using the stack exchange API to post a message to stack overflow website. I figured I had to post my application on a domain name. I hosted my application on free domain provided by 000webhost.com. You may wish to take a similar approach. After deploying the application on the domain, change the oauth domain and the ...


3

If the code tags are <pre>s, then \n is fine. Pre means "preformatted;" it makes the browser ignore the usual rules and preserve whitespace, etc. Repeat after me: "There is no such thing as a special character." Html is perfectly happy to receive UTF-8.


3

Although it doesn't appear to say so in the doc page, intitle expects an exact phrase, not a list of words. You can currently see this by: /2.2/search?intitle=get column array&site=stackoverflow which currently returns one result with that exact phrase in the title, but doesn't return the many questions that have those 3 words in other arrangements. ...


3

It sounds like you've either got a bug which is in fact making more requests than you think it is, or you're on a network where there's some other source of high-frequency requests. You're not supposed to have to deal with this situation in general, because this isn't an API error - it's an error from the load balancer because your IP is generating incoming ...


3

This is a bug. I've tagged your question accordingly. total, in the wrapper object, should always be the length of the items array, after concatenating all pages of results. When I run /2.2/notifications?pagesize=100&filter=!*L6X1NqVdlFobvlv, I get 4 pages of results, currently totaling 382 items: total remains fixed at 77. This is clearly a bug, ...


3

The Informed badge is removed from the "Next badge" tracking. Previously it was listed in the Available badges section. Now it is not available under the Available or Bronze section. So the bug has been fixed recently. Screenshot for reference: Copied from the MSE answer


Only top voted, non community-wiki answers of a minimum length are eligible