I've forwarded the original message (the big .png attachments), and the headers 
show:
:attachments:
- :name: ICLA-YuriGor-2.png
  :length: 478565
  :mime: image/png
  Content-Type: image/png; name=ICLA-YuriGor-2.png
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-2.png
  Content-ID: "<f_jn5ogdb41>"
- :name: ICLA-YuriGor-1.png
  :length: 464289
  :mime: image/png
  Content-Type: image/png; name=ICLA-YuriGor-1.png
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-1.png
  Content-ID: "<f_jn5ogdau0>"
:source: '201810'
This fails to drag/drop, not sure exactly where since there is no trace:
Exception: #<RuntimeError: Failed to concatenate ICLA-YuriGor-2.png and 
ICLA-YuriGor-1.png>

The headers are now the same.

When I select the second .png and pdf-ize it:
:attachments:
- :name: ICLA-YuriGor-2.pdf
  :length: 478565
  :mime: application/pdf
  Content-Type: image/png; name=ICLA-YuriGor-2.png
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-2.png
  Content-ID: "<f_jn5ogdb41>"
  :content: ''
- :name: ICLA-YuriGor-1.png
  :length: 464289
  :mime: image/png
  Content-Type: image/png; name=ICLA-YuriGor-1.png
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-1.png
  Content-ID: "<f_jn5ogdau0>"
:source: '201810'
So it appears that the content is being corrupted during the pdf-izing of the 
png.

Now, I try the smaller .gif version:
:attachments:
- :name: ICLA-YuriGor-1.gif
  :length: 48572
  :mime: image/gif
  Content-Type: image/gif; name=ICLA-YuriGor-1.gif
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-1.gif
  Content-ID: "<f_jnlykun50>"
- :name: ICLA-YuriGor-2.gif
  :length: 53557
  :mime: image/gif
  Content-Type: image/gif; name=ICLA-YuriGor-2.gif
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-2.gif
  Content-ID: "<f_jnlykun91>"
:source: '201810'
drag/drop: Exception: #<RuntimeError: Failed to concatenate ICLA-YuriGor-1.gif 
and ICLA-YuriGor-2.gif>
headers now are still the same.
try to pdf-ize the first gif works, with headers now:
:attachments:
- :name: ICLA-YuriGor-1.pdf
  :length: 48572
  :mime: application/pdf
  Content-Type: image/gif; name=ICLA-YuriGor-1.gif
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-1.gif
  Content-ID: "<f_jnlykun50>"
  :content: ''
- :name: ICLA-YuriGor-2.gif
  :length: 53557
  :mime: image/gif
  Content-Type: image/gif; name=ICLA-YuriGor-2.gif
  Content-Transfer-Encoding: base64
  Content-Disposition: inline; filename=ICLA-YuriGor-2.gif
  Content-ID: "<f_jnlykun91>"
:source: '201810'
Does this make any sense?

Craig

> On Oct 23, 2018, at 3:33 PM, sebb <[email protected]> wrote:
> 
> I think the problem is that the YAML summary was previously corrupted
> by a failed conversion.
> I just checked and the :content: value is the empty string - use the
> headers link to see the current YAML contents for the message.
> 
> Someone with sufficient karma needs to reparse the original message to
> reset the YAML entry; can then try again.
> 
> Note: I have fixed some of the conversions (e.g. burst, rotate) so
> that a failed operation does not update the YAML summary, so this is
> less likely to happen again.
> On Tue, 23 Oct 2018 at 23:14, Craig Russell <[email protected]> wrote:
>> 
>> At least the new error message works now.
>> 
>> I'm trying to drag/drop a .jpg to another .jpg. Failed with Exception: 
>> #<RuntimeError: Failed to concatenate ICLA-YuriGor-1.jpg and 
>> ICLA-YuriGor-2.jpg>
>> 
>> So I tried to pdf-size the two and that worked, but drag/drop of the .pdf 
>> files also failed: Exception: #<RuntimeError: Failed to concatenate 
>> ICLA-YuriGor-1.pdf and ICLA-YuriGor-2.pdf>
>> 
>> So I think drag/drop is completely broken.
>> 
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> [email protected] http://db.apache.org/jdo
>> 

Craig L Russell
Secretary, Apache Software Foundation
[email protected] <mailto:[email protected]> http://db.apache.org/jdo 
<http://db.apache.org/jdo>

Reply via email to