-
Notifications
You must be signed in to change notification settings - Fork 590
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
Requests not shown #463
Comments
Any errors in the browser console? |
I've got the same problem too. No error on console, Got the entries response from XHR request, but request not showing on web |
I can't replicate the issue, entries seem to be working fine for me. Is it only the requests screen or all other screens are empty even though they should have records? |
Can you try running |
Yes, I'm already run telescope:publish artisan command |
I can't think of an explanation of what you're seeing here and can't replicate it. You'll have to investigate it in your apps since you're the only ones who can replicate it. |
I've had this with two fresh installs today. Same outcome as those people reporting above. Edit: It was to do with the filtering condition as described in @ryanmortier comments below. |
@Mezzair fresh installs on a fresh laravel app works fine for me. Still can't replicate. |
Check the Vue component in dev tools, the Root.Index.IndexScreen.entries property should contain some records. |
Same issue here. I just deployed an application to production with Laravel Forge and telescope is enabled for production. The only page working for me is It worked great when it was running in dev on my Mac. The
edit: slightly different issue though as the entries are not in the database like the OP. edit2: nevermind, #409 and #76 (comment) fixed my issue. |
The documentation has been updated to explain filters: laravel/docs#4808. I think the majority of the issues are related to filtering in production. This issue, #470, #434, #409, #288, #134 and #76 are all related to the same issue. @themsaid perhaps we should add a note in the README related to filters for use in production environment? Having said that, I think the OP of this issue mentioned that entries are stored in requests but not displayed in the request tab. I don't think that issue is related to filters though. |
@paras-malhotra I think my problem is not in filtering issue. since I already return true inside telescope filter function. and I get request entries on my database (telescope_entries table). and even in network is showing the entries but in vue Root.Index.IndexScreen.entries is just empty array not binded from the XHR Request |
@Jimmy-JS yes I understand. Can you add breakpoints on line 118 and 96 of IndexScreen.vue and see what's going on with the entries variable and where |
Maybe this will help reproduce the problem. I had the following filter set on production, and this is when the problem started.
1.7 Million entries where saved on the telescope_entries table. Only after importing the production db locally, the problem was reproduced on the local environment. |
@themsaid yup it's empty although it was getting entries from XHR request. Here is the screenshot: |
Got the same problem. Requests totally not shown since one heavy request been recorded. Telescope:clear did help but only until that request been recorded again. Finally I have found out that request's json exceeded the Altering it to LONGTEXT and telescope:clear fixed the issue. |
I think this can only be fixed by someone who can replicate it. I'll keep the issue open but I really can't think of why it's acting like this with some people and not others. |
Everyone. You just insert into telescope_entries with truncated json content (invalid). Then this record gets rejected by DatabaseEntriesRepository::get() line 83. And then 'entries' section of response contains array with keys starting not from 0, but 1 or other number instead. As a result UI completely rejects to display any request from given array. It shows 'just empty space' message. |
fixed that in 364c09f Thanks @nakonechny for the explanation :) |
Hello,
we face an issue on our production server where the requests entries are not shown in the requests tab.
However, it seems in the database the requests are tracked normally.
Also, when viewing the api calls telescope does, we seem to get some results.
Any idea what could I look into to check what is wrong?
Thanks!
The text was updated successfully, but these errors were encountered: