Skip to content
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

read more log entries #585

Open
koem opened this issue Oct 1, 2011 · 10 comments
Open

read more log entries #585

koem opened this issue Oct 1, 2011 · 10 comments
Labels
Feature Request A request for a new feature/function Prio - Low A minor issue not having significant influence to a feature/function.

Comments

@koem
Copy link
Contributor

koem commented Oct 1, 2011

Currently only the last 35 log entries are shown in cache detail view. How about a button at the end of the page to read 30 logs more?

As a workaround I always open the cache in the browser, but I don't really like to switch apps.

@SammysHP
Copy link
Member

SammysHP commented Oct 1, 2011

I don't know, why we have this limit. Traffic, database size/loading, displaying... What, if we load 100 logs at once (maximum), displaying 30 as default with a button for the other 70 ones?

@Bananeweizen
Copy link
Member

I think dynamically loading more logs as requested originally is a good idea. And I also think loading as many logs as possible during the initial download is a bad idea.
I personally am happy with the 35 logs most of the time. It's only very seldom that I'd like to read more logs (to see something about the history of the cache or to get a clue where it is located). As long as we are in a "tolerated", but not "agreed" relationship with GC, we shouldn't stress that relationship by creating higher loads on the servers. So if we can implement this dynamic loading, I might even consider voting for a smaller initial count of logs to be downloaded.

@SammysHP
Copy link
Member

SammysHP commented Oct 1, 2011

And what's with stored caches? Maybe we can add an option in the settings how many logs should be loaded and stored as default and the rest is loaded dynamically.

@SammysHP
Copy link
Member

We have still the limit of 35 caches, but only 25 are included in the html page. The only solution would be to revert the "new" log-parsing-code and use the second request for the JSON version (there it's possible to load up to 100 logs at once).

@Lineflyer
Copy link
Member

+3 from support mail...just to document the user opinion on this.
Most are in favor of having a load more entries button like in search results

@dl1ely
Copy link

dl1ely commented Sep 16, 2013

+1 on this one, when i may warm up this "cold" issue. Even when limited to online-Caches, dynamic, user-initiated loading of more logs would be great, for the exact use case @Bananeweizen mentioned.

@aiomaster
Copy link

+1 for the "load more"-button. I really miss that, too!

@yellowduck
Copy link

I'm happy to be able to load more logs if needed, so add my +1 to the list.

What I do miss, is the ability to view my own log if I have found the cache already. Is there a way to include yourself as a 'friend', because friend's logs get loaded no matter how far back in the history they are.

@Lineflyer
Copy link
Member

@yellowduck
The own log is covered in #1793, we also receive quite a lot +1 from support mail for it.

But for all these feature requests there is always one thing to keep in mind:
We need to find a developer who is interested and able to implement it.

@snippet78
Copy link

adding my +1 for a 'load more' button. reading TFTC logs is nice but not much help when looking for a cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request A request for a new feature/function Prio - Low A minor issue not having significant influence to a feature/function.
Projects
None yet
Development

No branches or pull requests

8 participants