Project

General

Profile

Bug #8905

Take into account that Django development server is not powerful

Added by Evgeny Novikov over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Scheduling
Target version:
Start date:
05/30/2018
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

It seems that a development server of Django 2 sometimes does not handle requests well like a production server. Instead it rejects them, breaks pipes, uploaded files, etc. Before we did not suffer from this issue so much, but now it happens often and we lose quite many verification results. Anyway we should not rely on any server and spend as much time as could be necessary to perform reliable and predictable communication.


Related issues

Related to Klever - Feature #8729: Bridge does not work with Django 2.*Closed02/19/2018

Actions
Related to Klever - Bug #8668: Connection error warnings can lead to task decision results misinterpretationClosed01/15/2018

Actions

History

#1

Updated by Evgeny Novikov over 1 year ago

  • Related to Feature #8729: Bridge does not work with Django 2.* added
#2

Updated by Ilja Zakharov over 1 year ago

  • Status changed from New to Resolved

Implemented directly in core-new-formats.

#3

Updated by Evgeny Novikov over 1 year ago

  • Related to Bug #8668: Connection error warnings can lead to task decision results misinterpretation added
#4

Updated by Evgeny Novikov over 1 year ago

  • Status changed from Resolved to Closed

I cherry picked 68f9876 to master c9a14a01 since I think that this is a proper solution in any case not only for a Django 2+ development server.

Also available in: Atom PDF