#2166 Fix markdown crash

v1.0.0
closed
John Hoffman
sf-2 (994)
General
nobody
2015-08-20
2011-05-26
Tim Van Steenburgh
No

Something in a discussion post on [#2144] is causing a 500 error.

Related

Tickets: #2144

Discussion

  • Tim Van Steenburgh - 2011-05-26

    Offending post attached.

     
    bad_post_mongo_doc.txt

  • Dave Brondsema

    Dave Brondsema - 2011-05-27
    • milestone: limbo --> jun-03
     

  • Tim Van Steenburgh - 2011-06-01

    forge:tv/2166

    Pygments version has bumped to a custom build that fixes the bug that was causing the error. To test, you can use the contents of the 'text' attr in the attachment in a ticket or post. Under the old pygments build it would cause a 500; with the new build it won't.

    The actual change to pygments can be viewed here: https://bitbucket.org/tvansteenburgh/pygments-main/changeset/69997f523da1

    • status: in-progress --> code-review
    • assigned_to: Tim Van Steenburgh --> John Hoffmann
     

  • John Hoffman - 2011-06-02

    Tested fine, examined the pygments patch. Merged to dev.

    FYI, 

    source /var/local/env-allura/bin/activate
easy_install -H meanshost -N -v 'Pygments==1.4sf1-20110601'
     

  • John Hoffman - 2011-06-02
    • status: code-review --> closed
     

  • John Hoffman - 2011-06-09

    Re-index.

     

Log in to post a comment.