View Issue Details

IDProjectCategoryView StatusLast Update
0005593Talerobsolete componentpublic2019-12-20 18:12
ReporterMarcello Stanisci Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.6Fixed in Version0.6 
Summary0005593: Need 404 page.
DescriptionIf a nonexistent page is tried to be accessed, the bank shows the Django's exception page. Instead, a custom "page not found" page should be displayed.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2019-02-20 17:35

reporter   ~0013910

Last edited: 2019-02-20 17:35

This commit b0f9913, has all the gear in place but it's missing the last step to make the change effective: switching the "debug = True" line to "debug = False" in settings.py. So we should agree about this forthcoming switch before resolving this issue!

Christian Grothoff

2019-02-21 13:37

manager   ~0013921

Can we have debug on on test, and off on demo?

Marcello Stanisci

2019-02-21 16:30

reporter   ~0013924

Yes, but the only viable way that I can think of is putting some condition inside settings.py that sets debug to False if it is running on 'demo', or to True otherwise.

Not sure if there is some way to "pinpoint" a commit for a particular file and make it stick to that commit. This way we could put "debug = False" for commit X at stable branch, and make settings.py stick to that commit for all its life (or until we change policy). In fact, settings.py changes very rarely so this would not impact very much our overall activity; but at the same time, it sounds very dirty.

Christian Grothoff

2019-02-21 16:59

manager   ~0013925

Testing for the hostname in settings.py sounds viable, but crazy Git hacks not so much. I think this is only worth it if we can keep it reasonably simple. Otherwise, just turn it off.

Marcello Stanisci

2019-02-21 18:08

reporter   ~0013926

Resolved with the check in settings.py, b0f9913..652e1f1.

Marcello Stanisci

2019-02-21 18:11

reporter   ~0013927

And by the way: we check for a env variable to be defined instead of parsing hostnames. This variable is defined as soon as one runs 'source activate' which must be done upon SSH'ing into the server.

Issue History

Date ModifiedUsernameFieldChange
2019-02-20 16:55Marcello StanisciNew Issue
2019-02-20 16:55Marcello StanisciStatusnew => assigned
2019-02-20 16:55Marcello StanisciAssigned To => Marcello Stanisci
2019-02-20 17:35Marcello StanisciNote Added: 0013910
2019-02-20 17:35Marcello StanisciNote Edited: 0013910
2019-02-21 13:37Christian GrothoffNote Added: 0013921
2019-02-21 16:30Marcello StanisciNote Added: 0013924
2019-02-21 16:59Christian GrothoffNote Added: 0013925
2019-02-21 17:00Christian GrothoffTarget Versiongit (master) =>
2019-02-21 18:08Marcello StanisciStatusassigned => informing
2019-02-21 18:08Marcello StanisciResolutionopen => fixed
2019-02-21 18:08Marcello StanisciNote Added: 0013926
2019-02-21 18:11Marcello StanisciNote Added: 0013927
2019-02-27 20:11Christian GrothoffFixed in Version => 0.6
2019-02-27 20:11Christian GrothoffTarget Version => 0.6
2019-12-20 18:12Christian GrothoffStatusinforming => closed
2022-08-23 18:26Christian GrothoffCategorybank (demonstrator) => py bank (demonstrator, obsolete)
2023-12-03 00:23Christian GrothoffCategorypy bank (demonstrator, obsolete) => obsolete componet
2023-12-11 19:08Florian DoldCategoryobsolete componet => obsolete component