Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with bug
Search options answers only
not deleted
user 2
Indicates you've found an erroneous or unexpected behavior in the Stack Exchange API, or the Stack Exchange HTML or CSS, that needs to be fixed.
3
votes
Accepted
API documentation pages match some site names incorrectly
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.
- 18.7k
2
votes
Accepted
3
votes
Accepted
2
votes
Accepted
Trying to get the Total results count crashes the /notifications path
This was fixed in the latest deploy.
Sorry about the wait, a fix was actually staged a few days ago but deploying it was delayed by our yearly company get together.
- 18.7k
2
votes
Accepted
API calls that return select post bodies throw JSON errors
This was fixed in the latest deploy.
Root cause: I had let a copy of our JSON serializer (currently ServiceStack.Text) get out of date.
- 18.7k
2
votes
Accepted
/users/{ids}/timeline creation_date missing or incorrect
The bug was basically selecting the wrong date to display (in this case, an associated post), and the right date for filtering and what not. …
- 18.7k
1
vote
Accepted
Most of the url are missing the protocol
There was some monkeying around on the backend with URI generation, it's settled down now and this issue was resolved.
- 18.7k
2
votes
Accepted
Stack Exchange API is returning non-existant/incorrect notices for questions
The bug here is that deleted notices were still being returned.
This was fixed in the last deploy. …
- 18.7k
4
votes
Stack Exchange API is returning boolean(false) For 'is_answered' On Question With Accepted A...
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 tru …
- 18.7k
2
votes
Accepted
Stack Exchange API is not returning the close vote counts for questions
This was fixed in the latest deploy.
- 18.7k
4
votes
Accepted
1
vote
Accepted
CDN redirect for the API's JavaScript SDK is incorrect
Naturally my first vacation in two years, and I break something right before going offline. Sorry about that.
This was fixed in the latest deploy.
- 18.7k
1
vote
Accepted
Off-by-one error in fromdate processing
Tricky, this was complication of date rounding (we store dates with sub-second precision in the DB) and some bad math when converting unix epoch dates for certain routes.
The latest build should fix …
- 18.7k
3
votes
Accepted
Whatever happened to closed_reason?
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 r …
- 18.7k
3
votes
Accepted
Problem with /search tagged and max
There was a bug introduced in our move to elastic search where min/max was applied after paging results, instead of before. …
- 18.7k