Trac query page not working on Chrome, patch submitted upstream

[Adam Johnson]

Just an FYI: I think I found a bug in Trac that silently prevents the
ticket query page from submitting in Chrome, after adding filters. I've
reported it upstream and provided a patch:
https://trac.edgewall.org/ticket/13141

If this becomes a major problem before Trac (or Chrome!) is fixed I can
look at adding a shim to fix it on code.djangoproject.com.

Workaround is to use a search engine to search Trac, which I often do
anyway, for example:
https://duckduckgo.com/?q=site%3Acode.djangoproject.com+%22ROOT_URLCONF%22&ia=web

-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3RzEgiVd3PayHt9L01ckFBjuF3%3Dp9ZZmQHbhniQuNHog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trac query page not working on Chrome, patch submitted upstream

[Adam Johnson]

Update, a kind anonymous soul posting on the Trac ticket found out it's an
experimental web feature in Chrome that does this, and disabling it (
chrome://flags/#enable-experimental-web-platform-features ) fixes the issue.

On Sun, 31 Mar 2019 at 11:16, Adam Johnson  wrote:

> Just an FYI: I think I found a bug in Trac that silently prevents the
> ticket query page from submitting in Chrome, after adding filters. I've
> reported it upstream and provided a patch:
> https://trac.edgewall.org/ticket/13141
>
> If this becomes a major problem before Trac (or Chrome!) is fixed I can
> look at adding a shim to fix it on code.djangoproject.com.
>
> Workaround is to use a search engine to search Trac, which I often do
> anyway, for example:
> https://duckduckgo.com/?q=site%3Acode.djangoproject.com+%22ROOT_URLCONF%22&ia=web
>
> --
> Adam
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2Z%2BD8kpZCb0TnHm%3D4R_3jRFTwKaZV6KQ8nR5VJ7%2BPJqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC

[Altayeb omer]

Hi

On Sun, Mar 31, 2019, 07:55 Nourhan Hekal  Hi , I am Nourhan a student at Cairo university faculty of engineering and
> I would like to join django "Test framework cleanup" , But I would be more
> happy if you please simply the requirements.
> Thanks in advanced
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/e30e7751-c03d-4742-9c3b-00ad4227902f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CA%2BL9vAE%3D4AhpVGw4y7dBjAxCEdFshfFWQp6kAxAad9JnWveZCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use CDN for djangoproject.com

[Tobias McNulty]

On Sat, Mar 30, 2019 at 7:32 PM Tom Forbes  wrote:

> I’m a stats nerd, and I think I’m not alone on this list in that respect,
> would it be possible to share some more numbers after a week of usage? I
> would be interested in the total bandwidth used/saved, the global
> distribution of requests and the average requests per second. If I remember
> correctly fastly has a fantastic live dashboard with all of this info.
>

For static, I think we'll end up using just under 300 GB a month, or about
a quarter of the total bandwidth served by this particular server (which
also handles most other djangoproject.com subdomains). I'll see if I can
collect some slightly more interesting numbers after a week or two.

I’m not entirely clear on the HTTP/2 issue, does Fastly not terminate these
> and forward on http 1.1 requests? Could you elaborate a bit?
>

HTTP/2 supports connection coalescing
,
where the browser (with varying degrees of aggressiveness, depending on the
manufacturer) may reuse existing connections for different subdomains. In
our case, Fastly originally provisioned a wildcard SSL cert ('*.
djangoproject.com'), so *we think* that some versions of Firefox were
reusing HTTP/2 connections originally established for
static.djangoproject.com for requests to www.djangoproject.com, *even
though* there was no overlap in IPs for the two domains. In the browser
(courtesy of Mariusz) it looked like this:

[image: Screenshot_20190320_113825.png]
Clicking on the cert icon showed the wildcard cert from Fastly, not our
Let's Encrypt cert, as well. In other words, it appeared Firefox was
ignoring DNS for www.djangoproject.com and assumed that it could send those
requests to static.djangoproject.com instead, simply because the server
responded with an SSL certificate that matched www.djangoproject.com. I.e.,
it appeared to be *even more aggressive* than described under "The Firefox
way" in the link above.

I find this explanation entirely dissatisfying (if not altogether
frightening), so part of me hopes I've got it wrong. :-\

In any case, after requesting that Fastly de-provision the wildcard cert
and include only the specific domains we needed, the issue went away. There
is an HTTP status code (421) that can be used to tell the browser it's made
such an error, so I believe we also could have solved this by setting up a
catchall service in Fastly to return HTTP 421 for any requests received on
subdomains we weren't expecting. But avoiding the spurious requests to
begin with seemed like a better solution, and provisioning certs only for
the domains we need is cleaner to begin with and seems to have fixed the
problem.

I was never able to reproduce this in Firefox myself, but I did see
evidence of it occurring insofar as we *also* started getting a very small
number of requests to the '*docs*.djangoproject.com' service in Fastly
after changing the DNS for '*static*.djangoproject.com.' Of course, no one
would have noticed these because the requests returned successfully, but
they should not have been going through Fastly (until the DNS was changed
for 'docs', of course). Mariusz may be able to add something about the
when/how he saw this; I do think it was fairly intermittent. Anyways, I'm
pretty sure this would have gone undiagnosed for weeks if not months if he
had not noticed and alerted us to the issue (causing all sorts of
frustration and confusion in the meantime), so thank you again, Mariusz!

Cheers,
Tobias

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMGFDKREk0NZx93DMxOJdACO%2BHgSjGdoTLVuOLUHY3nFBgHTjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: gsoc proposal

[Carlton Gibson]

Hi Kartik. 

GSoC, for us at least, isn't for beginners. In the past students have 
already been contributors.
Maybe that's not 100% necessary but a good amount of experience with Django 
at the very least would be. 
If you get into Django maybe it's something you could consider for the 
future. 

I wish you all the best, 

Kind Regards,

Carlton

On Friday, 29 March 2019 12:38:24 UTC+1, kartik garg wrote:
>
> I am a beginner in django and wanted to apply for GSOC but I don't know 
> how to apply for that. can anybody please help me. I haven't applied for 
> gsoc before. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/214acf68-b28d-4dab-b1eb-36af55535e00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Reports -- March 2019

[Carlton Gibson]

Hi all. 



Calendar Week 12 -- ending 24 March.


Released Django v2.2rc1


Triaged:

https://code.djangoproject.com/ticket/30267 -- get_language_from_path not 
respecting i18n_patterns prefix_default_language=False (wontfix)
https://code.djangoproject.com/ticket/30275 -- Autofocus the first field in 
contrib.admin add form (worksforme)
https://code.djangoproject.com/ticket/30268 -- Django admin list_editable 
overrides changes done elsewhere (invalid)
https://code.djangoproject.com/ticket/30256 -- ManyToManyField with a 
non-list default value has different behavior in an inlined Admin vs a 
standalone Admin (invalid)
https://code.djangoproject.com/ticket/30256 -- autocomplete_fields cause 
one or two extra queries for each field wth foreign key or many to many 
relation (Accepted)
https://code.djangoproject.com/ticket/30263 -- Mention the Media.merge 
change in the release notes (Accepted)



Reviewed:

https://code.djangoproject.com/ticket/30196 -- Make FileResponse always set 
Content-Disposition header.
https://code.djangoproject.com/ticket/29956 -- Allowed overriding an order 
field widget in formsets.
https://code.djangoproject.com/ticket/30258 -- Failed to add 
CheckConstraint on IntegerRangeField



Authored:

https://github.com/django/django/pull/11093 -- Fixed #30263 -- Doc'd 
changes to form Media sorting (refs #30179).





Calendar Week 13 -- ending 31 March.


Triaged:

https://code.djangoproject.com/ticket/30289 -- ManyToManyField Admin 
Inlines do not respect user permissions (Accepted
)
https://code.djangoproject.com/ticket/30300 -- Allow migrations directories 
without __init__.py files. (Accepted)
https://code.djangoproject.com/ticket/30298 -- Search results in Google for 
Django documentation mixes up languages (Invalid)
https://code.djangoproject.com/ticket/30272 -- 
get_language_from_request(..., check_path=True) not respecting 
i18n_patterns prefix_default_language=False (Accepted)
https://code.djangoproject.com/ticket/30285 -- The domain in broken link 
emails can be spoofed (wontfix)
https://code.djangoproject.com/ticket/30296 -- Add how-to guide for 
JavaScript frameworks integration (Accepted)



Reviewed:

https://github.com/django/django/pull/11149 -- Fixed #30289 -- Prevented 
admin inlines for auto-created ManyToManyFields from being editable if the 
user only has the view permission.
https://github.com/django/django/pull/11060 -- Fixed #30241 -- Added system 
checks for translation settings.
https://code.djangoproject.com/ticket/30064 -- Admin search with a null 
character crashes with "A string literal cannot contain NUL (0x00) 
characters." on PostgreSQL
https://github.com/django/django/pull/11134 -- Doc'd that HttpResponse 
accepts bytestrings.
https://code.djangoproject.com/ticket/29692 -- ncorrect removal of order_by 
clause created as multiline RawSQL
https://code.djangoproject.com/ticket/30294 -- HttpResponse doesn't 
handle memoryview objects
https://code.djangoproject.com/ticket/30196 -- Make FileResponse always set 
Content-Disposition header.



Kind Regards,

Carlton



-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/9c7d03bd-dd68-46ec-b027-773f80e4c39b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extend FAQ with "How do I get Django and my JS framework to work together?"

[Nathan Gaberel]

Hi everyone,

I've been working on this for a while too (for React & Webpack
specifically) and will be sharing my current setup at DjangoCon Europe
next week.
For those of you attending, please come and talk to me, I'd love to
get your feedback and maybe we can exchange ideas. :)

Best,
Nathan

On Thu, 28 Mar 2019 at 01:11, Maciek Olko  wrote:
>
> Thank you all for all your responses!
>
> It's been a long time (sorry!), but:
> * I've added a Django ticket considering topic discussed here. [1]
> (* I updated a bit AJAX Django wiki page. [2])
>
> Aymeric, in terms of copyright ownership, would you agree on rephrasing 
> fragments of your articles to put it into Django docs?
>
> Regards,
> Maciej
>
> [1] https://code.djangoproject.com/ticket/30296
> [2] https://code.djangoproject.com/wiki/AJAX
>
> śr., 27 lut 2019 o 15:37 użytkownik Jamesie Pic  napisał:
>>
>> FTR I published my own writeup here:
>> https://blog.yourlabs.org/post/183077442308/django-js-research-report
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers  (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/CAC6Op184WMaf09CD1NqznfCQv%2BqhcMePB8nUdTKpTns1Fejc0A%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/django-developers/KVAZkRCq9KU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/CALYYG80eYMHMqis10UpxsehTdQRObxKP5c7c%2Bfr9TF6fLdxTwA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAO052S3JR3u5-_fW1t0yvycgv%3DSnH9ydp0XhR%3D5906zjng_aXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Reports - March 2019

[Mariusz Felisiak]

Week ending March 31, 2019.

*Triaged:*
https://code.djangoproject.com/ticket/30291 - pt-br translation for 
humanize has no spaces (messes with naturaltime filter) (invalid)
https://code.djangoproject.com/ticket/30292 - The unique_together meta 
option does not get migrated (invalid)
https://code.djangoproject.com/ticket/18726 - Combination of F() expression 
with query seems to confuse sql compiler's table aliases (fixed)
https://code.djangoproject.com/ticket/29697 - Complex query crashes with 
"missing FROM-clause entry for table" (fixed)

*Reviewed/committed:*
https://github.com/django/django/pull/11088 - Fixed #28431 -- Added check 
for BinaryField to prevent strings defaults.
https://github.com/django/django/pull/11137 - Fixed #30295 -- Fixed 
max_lengths.tests.MaxLengthORMTests when run in isolation.
https://github.com/django/django/pull/11060 - Fixed #30241 -- Added system 
checks for translation settings.
https://github.com/django/django/pull/7 - Made UsernameField render 
with autocapitalize="none" HTML attribute.

*Reviewed:*
https://github.com/django/django/pull/11128 - Doc'd django-docs-translation 
and Read the Docs release steps.
https://github.com/django/django/pull/11138 - Fixed #28373 -- Allowed 
connection time zone value is used for date tz convert for supported db.
https://github.com/django/django/pull/11149 - Fixed #30289 -- Prevented 
admin inlines for auto-created ManyToManyFields from being editable if the 
user only has the view permission.

*Authored:*
https://github.com/django/django/pull/11130 - Fixed #28621 -- Fixed crash 
of annotations with OuterRef.
https://github.com/django/django/pull/11134 - Doc'd that HttpResponse 
accepts bytestrings.
https://github.com/django/django/pull/11148 - Unified 
DatabaseOperations.last_executed_query() on Oracle with other db backends.

Best regards,
Mariusz

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/71d21e8e-3472-49a0-979e-b98339daf0d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.