Report on my last poll topic
-
I can't even load it. Just hangs, and my browser maxes out a CPU core and never gets anywhere.
I'm not sure how many entries I used, but at one point I got an error stating 32000 characters is the maximum post size, so I made each option small so I could have more poll options.
Filed Under: Yay I just DOS'd my own thread!
-
Some people managed to reply... somewhat.
-
Yup, I can't get in it at all.
-
I think I just invented a new JavaScript benchmark.
-
Me, I just kill the script the first chance I get. This seems to have the unexpected consequence of having to reload the main page after I get out.
-
I can load it, somewhat... Stopping JS manages to load 4699 items on last attempt... Hitting continue after that doesn't seem to do too much other than killing FF dead. Also, onclick events don't attach to anything below the first post, like suggested topics.
@mott555 how many items are there really?
-
@mott555 how many items are there really?
- I generated the list with a quick-and-dirty C# console app.
-
Bonus bug! Discourse renders a 1 when I typed in 4699!! @codinghorror
-
I generated the list with a quick-and-dirty C# console app.
Well I figured you didn't do it by hand.
Bonus bug! Discourse renders a 1 when I typed in 4699!!
Who are you, how are you doing this, and do you live in a country/state that allows gay marriage?
-
Replying seems to work, but the list doesn't show up as a poll for me - just as a plain unordered list. (Maybe this is related to stopping that script using Firefox's timeout dialog?)
I'm posting a response here because the other thread is going to literally melt down my PC.
I kept clicking "Continue Script" and it did eventually turn into a poll. However the page isn't really usable at that point, it pegs my CPU and takes a long time to respond to any keyboard/mouse input.
-
I can't even load it. Just hangs, and my browser maxes out a CPU core and never gets anywhere.
There is a whole chapter devoted on concurrency and on how not to render the browser unusable by long-running operations in David Herman's "Effective JavaScript".Filed under: hint
-
I kept clicking "Continue Script" and it did eventually turn into a poll. However the page isn't really usable at that point, it pegs my CPU and takes a long time to respond to any keyboard/mouse input.
Ok, yeah, clicking on "Continue" a couple of times turns it into a poll. I think I even managed to vote. After voting things broke down completely, though.
I'm a bit curious to what's going on. I don't really know anything about Discourse/JavaScript/whatever, but I'm not terribly impressed when something with just a couple of thousand items manages to floor my relatively high-end desktop machine. It seems like somebody, somewhere must be doing something wrong...
-
Bonus bug! Discourse renders a 1 when I typed in 4699!!
WONTFIX. Markdown; works as designed. Starting a line with a number starts an ordered list (at 1), no matter the number is.
-
I'm a bit curious to what's going on.
I'm a bit disappointed it didn't result in "Too much recursion" myself.
-
There is a whole chapter devoted on concurrency and on how not to render the browser unusable by long-running operations in David Herman's "Effective JavaScript".
It's ironic that the massive gains in multithreading and multitasking over the past two decades, both at the hardware and OS levels, is not relevant because HTML/DOM/browser (the most popular app platform ever) uses a single-threaded cooperative multitasking scheme that became obsolete shortly after I was born.
-
- There is a workaround.
- Just do this.
<ol start="1000004698"> <li>There is a workaround.</li> <li>Just do this.</li></ol>
-
How is that a workaround?
-
Ladies and gentlemen, I think we have the makings of a Signature guy here!
Filed under: Let the abuse begin
-
- Item 1 Line 1 line 2 line 3
- Item2
-
How is that a workaround?
It appears intended to be a way to start a list at something other than 1. It is clearly not a workaround for the problem of starting a line with a number without turning it into a list. And it certainly does break Discurse's formatting in an interesting way. I'm not at all sure how it manages to do that.
-
I'm not sure how many entries I used, but at one point I got an error stating 32000 characters is the maximum post size, so I made each option small so I could have more poll options.
You should have used letters, too - that would've let you put more entries.
-
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- .
- "numbers" = 4580309467
- .
- .
- .
Also:
- INT_MAX
- UINT_MAX
- LONG_MAX
- ULONG_MAX
Filed under: Layout tragedy, That would result in badness points in LaTeX
-
I forgot to mention the VERY poor performance of the preview window when I pasted that list in. Now I admit what I did was certainly abusive, but the preview window stole my CPU for several minutes before I was able to click the submit button and I wasn't expecting that.
-
This post is deleted!
-
How many hamsters running in your rig? 2.4GHz means 2,400,000,000 hamster power, right?
-
I guess I need to download more hamsters!
-
It’s important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces.
So
- twenty-five
- one thousand and one
- six
is
25. twenty-five 1001. one thousand and one 6. six
-
That doesn't sound like a good idea to me. Surely it should only be working if the first item is a 1 (and not any other number)? Based on the idea of what the user seems to want to express, at least.
-
I figured it was something to do with Markdown, but it just doesn't feel right that it works that way. Someone asked me a question requiring a numeric answer, I answered with a number, and Discourse swapped my number out for a totally different one.
I guess I just prefer the good-old-fashioned
[list]
[] Item 1
[] Item 2
[/list]because there's no way of accidentally starting a list with a simple reply.
-
Unless you're SMF in which case that will break excitingly (since
[*]
is magic markup for "I want a list here" and it otherwise wants explicit[li]
tags for list items and[*]
implies a list and li combination of magic voodoo)I guess this is one of the things I hate about Markdown in general and specifically about DC's take on it - is that it's practically tag soup and I don't know what I can expect my content to look like without the preview window. Or it encourages me not to write anything other than simple paragraphs of text which probably won't misbehave.
-
That's how Markdown works.
Knew I'd read that somewhere.
That doesn't sound like a good idea to me.
it just doesn't feel right that it works that way.
Strongly agree.
tag soup and I don't know what I can expect
Yep!
-
There are three types of collections.
- 0 items
- 1 item
- sod off, that's what Markdown does
-
You have mad DoS skillz...
-
Correction, this is how sucky markdown original spec works (which we often depart from).
Pandoc and Cheapskate do something sane here:
100. test
Pandoc
<ol start="100" style="list-style-type: decimal"> <li>test</li> </ol>
Overall, I find pandoc is the best spec to emulate and the best markdown parser + extensions by a mile.
-
See, that I like. That makes more sense than ignoring what the user typed in favour of what you think the user meant to say ;)
-
And it certainly does break Discurse's formatting in an interesting way.
I see what you have done there.
-
it just doesn't feel right that it works that way. Someone asked me a question requiring a numeric answer, I answered with a number, and Discourse swapped my number out for a totally different one.
It's just one of the many ways the editor works against the user using it. Like, when you just want to post a line in quotes ("this_is_a_line"), you have to use "this_is_a_line".- Is the answer to the big question. Only not when some parser is auto-detecting lists.
42.
Is what you get if you put the number in backticks. But that, of course, is a workaround.
-
I see what you have done there.
I've done that quite a few times. The first time, I even specifically drew attention to it, noting that it had been a typo that I started to fix but decided to leave as-is for obvious reasons.
-
-
#55. Numbers work correctly when prefixed with a number sign.
-
55. Numbers work correctly when prefixed with a number sign.
For varying interpretations of "work".
Oh, and look what the quote dragged in.
-
##hashtagyoloswag