Re: [Django] #32915: ./manage runserver --nostatic still doesn't return a traceback

[Django]

#32915: ./manage runserver --nostatic still doesn't return a traceback
-+-
 Reporter:  Michael  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  3.2
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Rohith P R):

 * owner:  Rohith P R => (none)
 * status:  assigned => new


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017f849b4c09-06635ffd-64fd-4fb7-823c-68ec773db9c1-00%40eu-central-1.amazonses.com.

Re: [Django] #33256: Some schema tests don't clean up their tables

[Django]

#33256: Some schema tests don't clean up their tables
-+-
 Reporter:  Tim Graham   |Owner:  banani720
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Have you run the command a second time so that you're reusing an existing
 database?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017f8491cef6-841a72ad-b4bf-4daa-94aa-8d549345ed93-00%40eu-central-1.amazonses.com.

Re: [Django] #33256: Some schema tests don't clean up their tables

[Django]

#33256: Some schema tests don't clean up their tables
-+-
 Reporter:  Tim Graham   |Owner:  banani720
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mohammad Ali Mehdizadeh):

 Replying to [ticket:33256 Tim Graham]:
 > Some test errors on a second consecutive run of `./tests/runtests.py
 --settings=test_postgres  --parallel=1 --keepdb schema` shows that some
 tests leave behind their tables. Attached is an initial patch for a couple
 of the cases.
 > {{{
 > ==
 > ERROR: test_add_foreign_key_quoted_db_table (schema.tests.SchemaTests)
 > --
 > Traceback (most recent call last):
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 82, in
 _execute
 > return self.cursor.execute(sql)
 > psycopg2.errors.DuplicateTable: relation "table_author_double_quoted"
 already exists
 >
 >
 > The above exception was the direct cause of the following exception:
 >
 > Traceback (most recent call last):
 >   File "/home/tim/code/django/django/test/utils.py", line 437, in inner
 > return func(*args, **kwargs)
 >   File "/home/tim/code/django/django/test/testcases.py", line 1305, in
 skip_wrapper
 > return test_func(*args, **kwargs)
 >   File "/home/tim/code/django/tests/schema/tests.py", line 3229, in
 test_add_foreign_key_quoted_db_table
 > editor.create_model(Author)
 >   File "/home/tim/code/django/django/db/backends/base/schema.py", line
 355, in create_model
 > self.execute(sql, params or None)
 >   File "/home/tim/code/django/django/db/backends/base/schema.py", line
 151, in execute
 > cursor.execute(sql, params)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 66, in
 execute
 > return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 75, in
 _execute_with_wrappers
 > return executor(sql, params, many, context)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 84, in
 _execute
 > return self.cursor.execute(sql, params)
 >   File "/home/tim/code/django/django/db/utils.py", line 90, in __exit__
 > raise dj_exc_value.with_traceback(traceback) from exc_value
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 82, in
 _execute
 > return self.cursor.execute(sql)
 > django.db.utils.ProgrammingError: relation "table_author_double_quoted"
 already exists
 >
 >
 > ==
 > ERROR: test_add_foreign_object (schema.tests.SchemaTests)
 > --
 > Traceback (most recent call last):
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 82, in
 _execute
 > return self.cursor.execute(sql)
 > psycopg2.errors.DuplicateTable: relation "schema_bookforeignobj" already
 exists
 >
 >
 > The above exception was the direct cause of the following exception:
 >
 > Traceback (most recent call last):
 >   File "/home/tim/code/django/tests/schema/tests.py", line 3238, in
 test_add_foreign_object
 > editor.create_model(BookForeignObj)
 >   File "/home/tim/code/django/django/db/backends/base/schema.py", line
 355, in create_model
 > self.execute(sql, params or None)
 >   File "/home/tim/code/django/django/db/backends/base/schema.py", line
 151, in execute
 > cursor.execute(sql, params)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 66, in
 execute
 > return self._execute_with_wrappers(sql, params, many=False,
 executor=self._execute)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 75, in
 _execute_with_wrappers
 > return executor(sql, params, many, context)
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 84, in
 _execute
 > return self.cursor.execute(sql, params)
 >   File "/home/tim/code/django/django/db/utils.py", line 90, in __exit__
 > raise dj_exc_value.with_traceback(traceback) from exc_value
 >   File "/home/tim/code/django/django/db/backends/utils.py", line 82, in
 _execute
 > return self.cursor.execute(sql)
 > django.db.utils.ProgrammingError: relation 

Re: [Django] #16406: Allow separate access to matches from urlpatterns and extra_context args

[Django]

#16406: Allow separate access to matches from urlpatterns and extra_context args
-+-
 Reporter:  Florian Apolloner|Owner:  Alokik
 Type:   |  Roy
  Cleanup/optimization   |   Status:  assigned
Component:  Core (URLs)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  resolvers, reverse   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Alokik Roy):

 * needs_tests:  1 => 0


Comment:

 Requested Tests added.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017f83465e0f-c877a9a4-f45f-4639-b880-7e62f5d4da4b-00%40eu-central-1.amazonses.com.