-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document GH replacements for various common ticket searches #130
Comments
The link that you provided is page 40, and clicking "Next" takes me to page 41, as expected. Page 53 is the last page, and Next is grayed out
Searching for "author:kcrisman" finds that issue: |
That is weird. In neither Safari nor Firefox did this work for me; instead, I got a page saying "0 results" or something like that. Also for 53 (not the next page, I didn't mean to imply that). Finally, clicking on "41" yields the same result. And now I just tried yet again in Chrome, and got the same result, so it can't be a cache thing, one would think.
Sure, I'm not worried about it per se, but the easiest way to search GH is just typing a string in the issues box, and if it's not finding all instances of (say) However, if nobody else can verify this, then I guess it must be a phantom. Thanks for checking, anyway. |
Better search: |
Basically we want a version of "Following the pulse of development" that uses GitHub searches instead of Trac reports/searches |
For me, page 40 is the last page. It seems that pages 41 to 53 are just placeholders (for empty pages...) |
This is a good topic for the new "Home" page of github wiki. |
For me, page 40 is the last page. It seems that pages 41 to 53 are just
placeholders (for empty pages...)
Okay, so I'm not completely crazy! But 53 seems oddly specific ... and I
think that actually there probably are 53 pages of results, they just
aren't appearing for some reason.
Obviously this is not a show-stopper, but if it happens more regularly we
would definitely want to educate people to only use "official" query means
such as the ones Matthias outlined.
… Message ID: ***@***.***>
|
I added some hints to the wiki https://github.com/sagemath/sage/wiki |
Searching is a bit wonky. This might be just a Github issue, in which case I guess you should close this. Details:
Just to test things out, I performed a search in issues for my handle
kcrisman
(andcrisman
). I got this while I was searching: https://34.105.185.241/sagemath/sage-all-2023-01-12-003/issues?page=40&q=is%3Aissue+kcrisman+is%3AclosedBut clicking "Next" yields nothing. Or clicking on page 53 is the same thing. There are definitely earlier issues that should show up, and some of them do when I search for
crisman
instead. But not all! (For instance, https://34.105.185.241/sagemath/sage-all-2023-01-12-003/issues/2212 doesn't show up on either list, as far as I can tell.)Anyway, my guess is that there are users with significantly more participation for whom this is also true, and certainly various keywords (graph, algebra, number field) would have many more, and having the search through issues not be complete is worrying (I never assume GH search through code is complete, I've been burned too many times by that). So it could be worth looking into, not just for historical reasons. Or if not, close 😄
The text was updated successfully, but these errors were encountered: