Search Results

"Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. … After the question has been edited to contain working code, we will consider reopening it." We don't review broken code Broken code is off-topic here I'm confused, It's not broken. Just not perfect. …

Questions: Should such a question be closed since it contains broken code? Can I edit the question if I'm 99.99% sure my edit is correct, since I've tested it and reproduced OP's results? … The question that made me ask this question: https://codereview.stackexchange.com/questions/126336/inpainting-algorithm-using-conjugate-gradient-for-colored-images-using-matlab#comment257440_126336 …

The off-topic list at meta includes: Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. … Should this sort of edit be deemed acceptable? What if OP (a new user) does not return to edit in the missing includes? Should the question be closed then? …

Currently, the close reason reads as such: Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. … If questions seeking explanations fall under this umbrella (or any question which simply isn't actually seeking a review), why is there nothing in the close reason to indicate this? …

Our close reason meta thread for broken code. Where it says we close your question to prevent answers. And that you should edit the code to not be broken. … For an iterative review, is it okay to edit my own question to include revised code? Which says OP shouldn't edit code into the question. …

I asked a question yesterday here. … It has been put on hold for the following reason: "Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. …

All of a sudden the question has 5 close votes due to being buggy. … EDIT: For reference, from the "broken code" link in the "put on hold" message: If your question contains broken code… Does your question contain something like: ... runs ...but it gives …

We recently had a question with un-compilable code. The question was answered and the answerer pointed out the broken code. The user has since edited the question to fix the code. … It's not my intention to cast aspersions on anyone (I've answered broken code before) but the answer was premature. …

itself explaining what I did so that it could then be changed again when my change is peer reviewed (I don't yet possess the tag to edit and then delete my quote box as the first change must be peer reviewed … With so much talk of "broken code" not allowed, why should a person asking a question who forgot two pairs of parenthesis get their question flagged or worse, removed because of a slight oversight. …

If we find that a question contains obviously broken code, our standard procedure is to close the question, sending the author back to the drawing board. … But is it acceptable for another user to edit the question to fix the code and nominate it for reopening? Follow-up question: What if a user just did that? …

A couple of minutes ago I stumbled upon this question. The reasons I'm asking this question are: There has been no activity since Jamal♦ last edited it. … It has been migrated from SO, altough it's a question concerning broken code. …

Roll back the edit that introduced the bug and edit out the off-topic line? I flagged the "comments" that are really answers. But I can't flag the down-votes. I could answer the question. … Or the revised, more broken version? …

For example, we received this (now-deleted) question, which was closed with the following reason: Questions containing broken code or asking for advice about code not yet written are off-topic, as … Should we be using the "Too Broad" close reason for such questions? Is the "Broken Code" close reason being used too broadly? …

The current close reasons are: Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. … After the question has been edited to contain working code, we will consider reopening it. Questions must involve real code that you own or maintain. …

Where I noticed the question, agreed with the closure and voted to close it as broken, which started another review in the close queue. … And so we can see that when the question was posted it was when we had our previous close reasons: Questions containing broken code or asking for advice about code not yet written are off-topic, …