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

Request detail page never loads #175

Closed
unformatt opened this issue May 5, 2017 · 3 comments
Closed

Request detail page never loads #175

unformatt opened this issue May 5, 2017 · 3 comments

Comments

@unformatt
Copy link

unformatt commented May 5, 2017

Having this problem with both silk 0.7.2 and 1.0.0.

I've run silk_clear_request_log and I have one request logged in silk.

Request detail pages (e.g. http://localhost:8000/silk/request/b141a25e-3944-471a-8787-06fb316913f4/) don't load, they just hang and peg my CPU while the console slowly logs messages related to RefactoringTool:

2017-05-05 20:08:53,006 DEBUG RefactoringTool:log_debug Adding transformation: raise
2017-05-05 20:09:43,961 DEBUG RefactoringTool:log_debug Refactoring
2017-05-05 20:09:49,364 DEBUG RefactoringTool:log_debug Adding transformation: standarderror
2017-05-05 20:09:49,364 DEBUG RefactoringTool:log_debug Adding transformation: numliterals
2017-05-05 20:09:49,368 DEBUG RefactoringTool:log_debug Adding transformation: reduce
2017-05-05 20:09:49,371 DEBUG RefactoringTool:log_debug Adding transformation: repr
2017-05-05 20:09:49,374 DEBUG RefactoringTool:log_debug Adding transformation: except
2017-05-05 20:09:49,379 DEBUG RefactoringTool:log_debug Adding transformation: has_key
2017-05-05 20:09:49,382 DEBUG RefactoringTool:log_debug Adding transformation: xreadlines
2017-05-05 20:09:49,386 DEBUG RefactoringTool:log_debug Adding transformation: operator
2017-05-05 20:09:49,389 DEBUG RefactoringTool:log_debug Adding transformation: apply
2017-05-05 20:09:49,392 DEBUG RefactoringTool:log_debug Adding transformation: throw
2017-05-05 20:09:49,395 DEBUG RefactoringTool:log_debug Adding transformation: renames
2017-05-05 20:09:49,402 DEBUG RefactoringTool:log_debug Adding transformation: idioms
2017-05-05 20:09:49,405 DEBUG RefactoringTool:log_debug Adding transformation: exitfunc
2017-05-05 20:09:49,405 DEBUG RefactoringTool:log_debug Adding transformation: ne
2017-05-05 20:09:49,408 DEBUG RefactoringTool:log_debug Adding transformation: sys_exc
2017-05-05 20:09:49,416 DEBUG RefactoringTool:log_debug Adding transformation: tuple_params
2017-05-05 20:09:49,420 DEBUG RefactoringTool:log_debug Adding transformation: paren
2017-05-05 20:09:49,423 DEBUG RefactoringTool:log_debug Adding transformation: ws_comma
2017-05-05 20:10:40,070 DEBUG RefactoringTool:log_debug Refactoring

I thought my use of SQL Server could be the problem. I changed to MySQL and have the same issue.

pip freeze:

autopep8==1.2.4
autotask==0.5.4
awsebcli==3.7.6
blessed==1.9.5
botocore==1.4.16
bunch==1.0.1
cement==2.8.2
colorama==0.3.7
contextlib2==0.5.4
coverage==4.3.4
django-anymail==0.6.1
django-cors-headers==1.1.0
django-jsonfield==1.0.1
django-memoize==2.1.0
django-object-actions==0.8.2
django-pyodbc-azure==1.9.3.0
django-rest-swagger==0.3.5
django-silk==0.7.2
django-sql-server-bcp==0.1.6
django-test-without-migrations==0.6
Django==1.9.5
djangorestframework-bulk==0.2.1
djangorestframework==3.3.3
docker-py==1.7.2
dockerpty==0.4.1
docopt==0.6.2
docutils==0.12
drf-extensions==0.3.1
et-xmlfile==1.0.1
jdcal==1.3
Jinja2==2.8
jira==1.0.7
jmespath==0.9.0
MarkupSafe==0.23
MySQL-python==1.2.5
oauthlib==2.0.1
openpyxl==2.4.7
pathspec==0.3.4
pep8==1.7.0
psycopg2==2.6.1
Pygments==2.1.3
pyodbc==3.0.10
python-dateutil==2.6.0
pytz==2016.10
PyYAML==3.11
raven==5.26.0
requests-oauthlib==0.7.0
requests-toolbelt==0.7.0
requests==2.13.0
semantic-version==2.5.0
six==1.10.0
sqlparse==0.2.2
termcolor==1.1.0
texttable==0.8.4
tlslite==0.4.9
Unidecode==0.4.20
wcwidth==0.1.6
websocket-client==0.37.0
xlrd==0.9.4
@unformatt
Copy link
Author

Could this be due to a large request body?

@unformatt
Copy link
Author

Seems like the rendering of the Curl and Django Test Client with syntax highlighting on a large request body might be what's hanging it up (Request is only 93k). I'll ignore request bodies for now. Silk would probably benefit from not defaulting to SILKY_MAX_REQUEST_BODY_SIZE = -1 since it effectively can't handle request bodies over a certain size. Or if request body is over a certain size, disable syntax highlighting.

@szuliq
Copy link

szuliq commented Mar 1, 2021

@unformatt big thanks for this answer. It has helped me a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants