tickets
16 rows where "created" is on date 2008-08-19 and resolution = "fixed" sorted by resolution
This data as json, CSV (advanced)
Suggested facets: changetime, owner, reporter, has_patch, needs_tests, changetime (date)
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution ▼ | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8403 | 2008-08-19 00:21:53 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.349070 | Accepted | closed | File uploads/storage | dev | fixed | Current file locking does not work on NFS mounts | The code in `django.core.files.locks` assumes that `flock()` is safe to use on every POSIX system to lock files. This isn't the case when the filesystem in question is a relatively recent NFS system. In that case, `flock()` actively raises an error (rather than potentially silently failing to lock things, which was the older behaviour). For those situations `fnctl()` should be used to do file locking. From a bit of a search around and some source reading (plus some comments on the Mailman list, although I've avoided reading the relevant code there for the moment, since it's GPL and I might end up being the person who fixes this ticket), it looks like posixfile.lock() in the Python source is an appropriate way to do this. I realise the `locks.py` file isn't our source, but it is broken in this respect and we do include it. So we have to fix it, since, right now, you can't save files to an NFS-mounted filesystem. This effect in Django was initially noticed in [http://groups.google.com/group/django-users/browse_thread/thread/384c3ec44672cb02 this django-users thread]. | mtredinnick | mtredinnick | file lock | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8404 | 2008-08-19 00:29:36 | 2013-02-14 10:21:24 | 2022-03-06 03:42:10.492942 | Accepted | closed | contrib.auth | Bug | Normal | dev | fixed | Auth password reset tests are too restrictive about template requirements | The tests in `django.contrib.auth.tests.views.PasswordResetTest` check for a correct "failure to submit" with an invalid email address by looking for a particular error message string. The problem is that this string actually reveals that a particular email address isn't on the system. So if somebody writes a password reset template for their own sites that doesn't reveal the presence or absence of a user (an ITS requirement in some organisations, e.g. financial sites), there is no way to have that test pass. So we need to come up with a better way to test for "success" (i.e. failure to submit the form) when the email address doesn't exist in the system. Possibly just easing back and checking for the existence of form.errors in the template rendering will be enough (or the existence of that error message in the context used for rendering), rather than checking the actual string output so carefully is enough. But maybe somebody has another idea. | nobody | mtredinnick | 0 | 0 | 0 | 0 | 0 | 0 | |
| 8406 | 2008-08-19 02:12:13 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.829506 | Accepted | closed | Documentation | dev | fixed | docs: incorrect model repr in interactive sessions | There is a number of instances in the docs where the `repr` for model objects is incorrectly shown as `...` instead of `<SomeModel: ...>`. | nobody | arien | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8407 | 2008-08-19 02:31:43 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.995558 | Accepted | closed | Documentation | dev | fixed | docs: incorrect output shown for Paginator use in interactive session | The docs show an session at the Python prompt where a `Paginator`'s `page` method throws an `InvalidPage` exception for pages that don't have any objects; the actual exception thrown is an `EmptyPage`. While `EmptyPage` descends from `InvalidPage`, the display is incorrect and may well confuse people. | nobody | arien | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8409 | 2008-08-19 07:18:25 | 2008-09-17 05:42:12 | 2022-03-06 03:42:11.293814 | Accepted | closed | HTTP handling | dev | fixed | Django built-in server is very slow with Firefox browser when serving admin media | Firefox (v3.0.1) with default settings is taking a very conservative view on cacheability of admin media files served by the Django built-in server in django.core.servers.basehttp.py. This can be dramatically improved by arranging for AdminMediaHandler class to provide Last-Modified headers in its responses. Without this change, IE outperforms Firefox on admin pages by a big margin (apparently its heuristics for cache expiry in this case are far looser). | nobody | andylowry | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8410 | 2008-08-19 07:47:01 | 2011-09-28 16:12:17 | 2022-03-06 03:42:11.434908 | Ready for checkin | closed | Core (Cache system) | dev | fixed | memcache backend add method is inconsistent with it's other methods | Split of from #7460 [1] The add method of the memcached backend uses a different approach for it's key/value pair then the other methods. Seems to be 'left' over from past changes/fixes ? Patch attached here aims to make 'add' consistent in terms of handling the key/value pair as it's brother the 'set' method. [1] http://code.djangoproject.com/ticket/7460 | nobody | trbs | memcached, consistency, add | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8411 | 2008-08-19 08:58:02 | 2008-08-30 04:04:53 | 2022-03-06 03:42:11.599541 | Unreviewed | closed | Documentation | dev | fixed | Link to custom model fields documentation missing on SVN release documentation page | It might be helpful to have http://www.djangoproject.com/documentation/custom_model_fields/ explicitly listed on http://www.djangoproject.com/documentation/ | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8414 | 2008-08-19 10:46:36 | 2010-11-23 23:32:01 | 2022-03-06 03:42:12.112270 | Unreviewed | closed | Core (Cache system) | 1.2 | fixed | multiple sites on one memcached | For every site which use for example CacheMiddleware we need to run new memcached instance, its not efficient with few small sites. I think that adding a key_prefix to the CACHE_BACKEND params will solve this problem. I've attached patch aganist memcache backend. | nobody | urban | cache prefix session cached_db | 0 | 1 | 0 | 1 | 0 | 0 | ||
| 8415 | 2008-08-19 12:25:17 | 2011-09-28 16:12:17 | 2022-03-06 03:42:12.279443 | Ready for checkin | closed | contrib.localflavor | dev | fixed | Spelling error in Dutch localflavour nl_provinces.py | There is a spelling error in django/contrib/localflavor/nl/nl_provinces.py Allthough this is a minor patch, it *is* a string change so perhaps setting milestone to 1.0 in this point in time is wrong. But because this local name is best left untranslated i think it should go in anyway. Existing translations should be updated to reflect the correct spelling. | nobody | nlsp | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8419 | 2008-08-19 15:43:17 | 2011-09-28 16:12:17 | 2022-03-06 03:42:12.965336 | Design decision needed | closed | Database layer (models, ORM) | dev | fixed | Fix race in get_or_create() which can lead to update | There is a race condition in get_or_create - if the object is not present for the initial get(), but is swiftly created elsewhere, then the save() will update the object created elsewhere and return it with created=True. This patch uses save(force_insert=True) to stop this from happening, and to drop through into the existing code that re-attempts the get(). I also update some of the documentation to make the behavior completely clear. Note: Patch follows discussion with Malcolm at http://groups.google.com/group/django-developers/browse_thread/thread/179ed55b3bf44af0/067be6c02aba2bb3?hl=en#067be6c02aba2bb3 I am only submitting the patch to get_or_create(), which seemed uncontroversial. I personally believe that a similar force_insert=True should be used in create(), or if not then at least that force_insert and force_update flags should be available for create() as well as for save(). | nobody | Richard Davies <richard.davies@elastichosts.com> | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8422 | 2008-08-19 16:18:53 | 2011-09-28 16:12:21 | 2022-03-06 03:42:13.458263 | Accepted | closed | contrib.admin | dev | fixed | FilePathField gives no blank option in admin when blank=True is set | it seems that the issue in ticket #1756 is still occurring. | nobody | tosh | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8424 | 2008-08-19 18:16:55 | 2013-12-10 05:41:37 | 2022-03-06 03:42:13.793614 | Accepted | closed | Database layer (models, ORM) | New feature | Normal | fixed | Implement time filters | As of r8442, it is possible to filter a queryset by year, month or day using the usual syntax, However, filters for hours, minutes and seconds were missing. I have added those into a patch for your consideration along with unit tests and documentation. {{{ Meeting.objects.filter(meeting_time__hour=12) }}} | UloPe | gnuvince | datetime filter hour minute second | 0 | 1 | 1 | 1 | 0 | 0 | |
| 8425 | 2008-08-19 19:20:06 | 2011-09-28 16:12:17 | 2022-03-06 03:42:13.960248 | Design decision needed | closed | Database layer (models, ORM) | dev | fixed | Palau, Federated States of Micronesia and Marshall Islands are soverign nations and should not be included in the USStateField | http://travel.state.gov/travel/cis_pa_tw/cis/cis_993.html https://www.cia.gov/library/publications/the-world-factbook/geos/ps.html http://en.wikipedia.org/wiki/Palau Citizens of Palau are not US citizens. | anonymous | Jake Nelson <jake.nelson@gmail.com> | palau usstatefield | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8426 | 2008-08-19 19:27:19 | 2010-08-07 01:29:24 | 2022-03-06 03:42:14.122349 | Accepted | closed | Forms | dev | fixed | Wrap help_text in "<span class="helptext"></span>", like errors in "<ul class="errorlist"></ul>" in HTML output | form.as_p() and form.as_ul() should both either have a div (with class="help"), span, or br around the help_text. form.as_table() already has a br tag before the helptext. So this should be added to improve consistency. This will really aid in styling the form with CSS! | kmtracey | erikcw | help_text, as_p, as_ul, forms | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8427 | 2008-08-19 21:04:22 | 2011-09-28 16:12:17 | 2022-03-06 03:42:14.290242 | Unreviewed | closed | Translations | dev | fixed | Updated the Norwegian translation | Updated the Norwegian translation. Added the missing localflavour strings (mostly as blank msgstr). Thanks to Christian Mikalsen for helping out =) | nobody | jonklo | norwegian | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8433 | 2008-08-19 23:33:54 | 2011-09-28 16:12:17 | 2022-03-06 03:42:15.512847 | Accepted | closed | contrib.admin | dev | fixed | auth add_view popup | add_view should probably be: {{{ if "_addanother" in request.POST: request.user.message_set.create(message=msg) return HttpResponseRedirect(request.path) + elif '_popup' in request.REQUEST: + return self.response_add(request, new_user) else: request.user.message_set.create(message=msg + ' ' + ugettext("You may edit it again below.")) return HttpResponseRedirect('../%s/' % new_user.id) }}} | nobody | sorl | 0 | 1 | 0 | 0 | 0 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE tickets (
id int primary key,
created datetime,
changetime datetime,
last_pulled_from_trac datetime,
stage text,
status text,
component text,
type text,
severity text,
version text,
resolution text,
summary text,
description text,
owner text,
reporter text,
keywords text,
easy boolean,
has_patch boolean,
needs_better_patch boolean,
needs_tests boolean,
needs_docs boolean,
ui_ux boolean
);