#3735 Discussion Forum Posts / 500 Error [24262]

v1.0.0
closed
Jenny Steele
sf-2 (994)
General
Tim Van Steenburgh
2015-08-20
2012-02-13
Chris Tsai
No

https://sourceforge.net/apps/trac/sourceforge/ticket/24262

Hello,

Thanks for the great collaboration environment for open source projects! I'm the primary author of the GWT Highcharts project which we're hosting on SourceForge, and we've been making good use of the built in discussion board feature for answering questions about the project and getting ideas from users of the software. Things seem to be working ok, but I noticed this week that two posts that were added we can't navigate to because they're showing a "500 error" (so I can't seem to find anyway to respond to those posts).

Specifically, these two threads:

https://sourceforge.net/p/gwt-highcharts/discussion/general/thread/99c945d6/
https://sourceforge.net/p/gwt-highcharts/discussion/general/thread/4a0a2095/

Which you can get to by following the two topics titled "Alignment Issue" and "Alignemnt Issue in my chart" posts on the main discussion page at:

https://sourceforge.net/p/gwt-highcharts/discussion/general/

Any idea why those particular threads are causing issues? The rest of the threads seem to be working fine.

Thanks,

-Shawn

Related

Tickets: #4166
Tickets: #4194

Discussion

  • Anonymous - 2012-03-19

    Originally by: moxiesquinn

    Here's another thread that just started exhibiting this problem:

    https://sourceforge.net/p/gwt-highcharts/discussion/general/thread/a8c957ca/

    That thread was working fine (I had several back-and-forth exchanges with the original poster), and now all of a sudden after the most recent post the thread is no longer accessible (same "500 error").

    Is there a specific character, mark up syntax or something else about the contents of the last post to that thread that is tickling things?

     

    Last edit: Anonymous 2016-01-28

  • Dave Brondsema

    Dave Brondsema - 2012-04-19

    Looks like links in the original ticket are working now, but the one in the comment still errors.

    This is the traceback from the error

    Module /var/local/allura/Allura/allura/templates/widgets/post_widget.html:23 in top-level template code
<<                  <b>{{value.subject or '(no subject)'}}<br/></b>
                   {% endif %}
                   {{g.markdown.convert(value.text)|safe}}&nbsp;
                   {{lib.related_artifacts(value)}}
                   {% if value.edit_count %}
>>  {{g.markdown.convert(value.text)|safe}}&nbsp;
Module allura.lib.stats:57 in inner
<<                  return func(*l, **kw)
                   with stats.timing(self.timer):
                       return func(*l, **kw)
               inner.__name__ = func.__name__
               return inner
>>  return func(*l, **kw)
Module markdown:412 in convert
<<                  else:
                           # We have a serious problem
                           message(CRITICAL, 'Failed to strip top level tags.')

               # Run the text post-processors
>>  message(CRITICAL, 'Failed to strip top level tags.')
Module markdown:112 in message
<<              sys.exit(0)
           elif level > WARN:
               raise MarkdownException, text
           else:
               warnings.warn(text, MarkdownWarning)
>>  raise MarkdownException, text
MarkdownException: Failed to strip top level tags.
     

  • Dave Brondsema

    Dave Brondsema - 2012-04-19
    • milestone: limbo --> forge-may-04
     

  • Dave Brondsema

    Dave Brondsema - 2012-04-20
    • size: --> 2
     

  • Jenny Steele - 2012-05-10
    • status: open --> in-progress
    • assigned_to: Jenny Steele
     

  • Jenny Steele - 2012-05-15
    • status: in-progress --> code-review
    • qa: Tim Van Steenburgh
     

  • Jenny Steele - 2012-05-15

    On allura js/3735. For this, I added error handling around markdown to let the user know when they've put something in there it doesn't like so they can fix the code themselves. In the examples I looked at, they were all code snippets that weren't marked as such, but this will prevent other unexpected problems from making a page 500. To test, enter the text in the attachment in a markdown box and click "Preview". You will see a message that an error happened and the text it tried to convert. If you enter the same content in the box with "~~~~" it will display correctly.

     
    error.txt

  • Tim Van Steenburgh - 2012-05-17
    • status: code-review --> in-progress
     

  • Tim Van Steenburgh - 2012-05-17

    Cool, nice solution! I did find one little thing. The rendering of the error message looks great in comments, but funky in Wiki pages. See screenshot: http://screencast.com/t/GCuTKpvDC4V3

    Hopefully that can be fixed easily?

     

  • Jenny Steele - 2012-05-18
    • status: in-progress --> code-review
    • milestone: forge-jun-01 --> forge-may-18
     

  • Dave Brondsema

    Dave Brondsema - 2012-05-18
    • milestone: forge-may-18 --> forge-jun-01
     

  • Tim Van Steenburgh - 2012-05-22
    • status: code-review --> closed
     

Log in to post a comment.