You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: chriscf [Submitted to the original trac issue database at 2.04pm, Monday, 20th October 2008]
As well as showing the uploaded date/time and the user, the Browse/details page should also show the "client uuid" field (as displayed on the User/show pages). There are a number of rendering issues which seem to be specific to some configurations, and these are often impossible to reproduce without access to client logs. If users are rendering with multiple clients, this makes it impossible to trace the problem.
This information need only be kept for at most a few days, which should be enough time for any problem clients to be identified. It should be possible to add a POST field or otherwise intercept the value that is coming in to be logged in case of errors.
The text was updated successfully, but these errors were encountered:
Author: spaetz [Added to the original trac issue at 11.50am, Tuesday, 29th June 2010]
As much as I would love to add that information, the tileset files don't provide any information about the client UID. In order to add that we would have to modify the .tileset file format in a non-compatible way and that is not something I see myself doing in the short term. But it is sensible and I will keep this in mind for future updates.
Reporter: chriscf
[Submitted to the original trac issue database at 2.04pm, Monday, 20th October 2008]
As well as showing the uploaded date/time and the user, the Browse/details page should also show the "client uuid" field (as displayed on the User/show pages). There are a number of rendering issues which seem to be specific to some configurations, and these are often impossible to reproduce without access to client logs. If users are rendering with multiple clients, this makes it impossible to trace the problem.
This information need only be kept for at most a few days, which should be enough time for any problem clients to be identified. It should be possible to add a POST field or otherwise intercept the value that is coming in to be logged in case of errors.
The text was updated successfully, but these errors were encountered: