| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| |
| | |
Main intent here is to be more explicit about what form you're
getting the attachment body in - valid UTF-8 or binary, and has it
been cleaned up in order to be UTF-8?
|
| | |
|
| |
| |
| |
| |
| | |
Text type attachments will always have a UTF-8 body (even if it has
to be scrubbed).
|
| |
| |
| |
| |
| | |
As noted in the ruby docs (http://ruby-doc.org/core-1.9.3/String.html#method-i-encode),
any conversion from an encoding to the same encoding is a no-op, covert it first to utf-16.
|
| |
| |
| |
| | |
Also be explicit about using UTF-8 when handling text data.
|
| |
| |
| |
| |
| |
| |
| | |
Unfortunately, the conditional used in 090531bf2d2b763e5bb281658e91b58905912130
results in `Gemfile.lock` being inconsistent with `Gemfile` under ruby 1.8.7 so
we can't use it until after Alaveteli release 0.22, which is the last release
that will support ruby 1.8.7.
|
| |
| |
| |
| |
| | |
Don't call the method unless we need to. Adds #set_api_key! to set a new
API key even if there's an existing one.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
Add spec to demonstrate that admin-added bodies aren't getting derived attributes.
Add a spec to demonstrate the problem setting the first letter for translations.
Demonstrate failure to update derived attributes in translations.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Prior to this, a name with commas in it plus email address
would have been treated as several separate addresses, some
of which would have just consisted of the bits of the
name between the commas, and would have been invalid.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Just check if there's an associated InfoRequest.
user system total real
old 0.010000 0.000000 0.010000 ( 0.012269)
new 0.000000 0.000000 0.000000 ( 0.000101)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously loaded all PublicBodyHeading and associated PublicBodyCategory
records. Now only loads the PublicBodyCategory records that relate to the
PublicBody.
user system total real
old 0.320000 0.000000 0.320000 ( 0.356155)
new 0.010000 0.000000 0.010000 ( 0.010077)
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ruby can natively decode uuencoded text with String#unpack. [1] This
avoids the uuencode program dependency and avoids writing tempfiles.
The actual implementation is taken from mail [2]. The UnixToUnix module
is not available in our bundled version of mail.
This commit includes a spec to illustrate the failure of uuencode(1) to
decode the particular attachment in incoming-request-bad-uuencoding-2.
email. Parsing with uuencode returns the following error:
External Command: Error from command "uudecode -o /dev/stdout
/tmp/foiuu20150530-14811-u6j936":
uudecode: /tmp/foiuu20150530-14811-u6j936: No `end' line
The file _is_ created and appears to be OK, but the exit code is 1. This
causes AlaveteliExternalCommand to fail and return nil.
See #2508 [3] for the bug report.
[1] http://ruby-doc.org/core-1.8.7/String.html#method-i-unpack
[2] https://github.com/mikel/mail/blob/bc4c9bb9321e9d36a678692f2f562d3146b63f78/lib/mail/encodings/unix_to_unix.rb#L7
[3] https://github.com/mysociety/alaveteli/issues/2508
|
| | |
| | |
| | | |
Inspired by https://github.com/mikel/mail/commit/bc4c9bb9321e9d36a678692f2f562d3146b63f78
|
|\| |
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Skipping this seems to have some unexpected interaction with
fixture data.
https://travis-ci.org/mysociety/alaveteli/jobs/64446161
|
| |
| |
| |
| | |
Otherwise UTF-8 encoded strings will be returned as ASCII-8BIT.
|
| |
| |
| |
| | |
Correct indentation to be consistent
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I think I was wrong in a83b379fd2d676172855825d0592937b234371e2 in
assuming that all email gets properly encoded for transfer. Looking
at the mail gem load method
https://github.com/mikel/mail/blob/b159e0a542962fdd5e292a48cfffa560d7cf412e/lib/mail/mail.rb#L175a,
it reads raw email content from a file in binary mode. So this commit
makes both reading and writing the raw_email a binary mode operation
and adds a data_as_text method for displaying the data in the admin
interface that coerces it to valid utf-8.
|
| | |
| | |
| | |
| | | |
Move setup to spec - not in common with other specs.
|
| | |
| | |
| | |
| | |
| | | |
We don't write the data for a raw email to the database anymore.
It's written to a file.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Remove unneeded setup, fixtures are not used in these specs.
|
| |/ |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In a database with encoding SQL-ASCII, an invalid utf-8 filename
can be saved but will cause an "invalid byte sequence in UTF-8"
when the filename is prepared for display. In a database with a
UTF-8 encoding, saving the string will cause an error like
"ActiveRecord::StatementInvalid (PG::Error: ERROR: invalid byte
sequence for encoding "UTF8""
|
| | |
| | |
| | |
| | |
| | | |
Try likely conversions but if that fails, just replace the characters
that are invalid utf-8.
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
'openaustralia_github/286-public-body-show-visible-requests' into rails-3-develop
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #286
|
|\ \ \ \ \
| | |_|_|/
| |/| | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
mb_chars provides a multibyte-aware wrapper for strings. It should
have no effect on ruby 1.9.3 and above. Although ruby 1.8.7 wouldn't
raise errors on a badly sliced multibyte string, on upgrading to ruby
1.9.3 and above, string operations such as gsub, match and join may
produce ArgumentErrors with the message "invalid byte sequence in UTF-8".
Additionally, a database with 'UTF-8' encoding may produce the error
"PG::CharacterNotInRepertoire: ERROR: invalid byte sequence for encoding "UTF8""
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
rails-3-develop
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
|
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Cleaned up by @jpmckinney in 4329ffa27cf83c00e03a0b0600ee54ce06056ee3,
so adding a couple of regression specs.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Don't call load_raw_emails for all specs - only needed for one.
Don't call update_display_size! explicitly - the point of the
test is that body= should set it as a side effect.
|