Skip to main content
clarity and grammar. Duplicate target doesn't *need* to be canonical.
Source Link
wjandrea
  • 31.7k
  • 20
  • 35

Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to theStack Overflow's goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists orthere's an existing question, otherwise consider answering otherwise.

  • If the issue is specific to the author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example, an accidental semicolon in JavaScript:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to Stack Overflow's goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or syntax error? Close as duplicate if there's an existing question, otherwise consider answering.

  • If the issue is specific to the author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example, an accidental semicolon in JavaScript:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

deleted 35 characters in body
Source Link
Robert Harvey
  • 179.9k
  • 54
  • 265
  • 317

A community-specific reason > NotNot reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

A community-specific reason > Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

To avoid "hard-coding" the list of supported technologies, linked to what "runnable" means instead
Source Link

A community-specific reason > Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (only for HTML/CSS/JavaScriptthe snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

A community-specific reason > Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (only for HTML/CSS/JavaScript) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

A community-specific reason > Not reproducible or was caused by a typo

"While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers."

How we define not reproducible or was caused by a typo

Some questions are too localized to be helpful to anyone other than the author of the post, which is contrary to the goal of creating a high-quality repository of knowledge. Solutions to typos, syntax errors, or logic issues tightly coupled to specific code aren't useful in any other context and are thus closed as "caused by a typo".

Sometimes, the issue can't be reproduced either due to changes making it obsolete, or the problem being device, platform, or project-specific. In these cases, the question is closed for being "not reproducible".


How to use this reason to close questions

Before closing the question for this reason, consider the following:

  • Is the issue a common typo or a syntax error? Close as duplicate if a canonical exists or consider answering otherwise.

  • If the issue is specific to author's context only or can't be reproduced by you or other community members, vote (flag) to close for this reason.


My question was closed. What should I do now?

  • Review feedback (if any) by community members. If the issue was just a typo or a syntax error:

    • Consider if the post can be rewritten to help others with a similar problem. For example:

      I am getting an "Unexpected token" error in const a = { a:42; b:24 };

      can be changed into:

      What property separators are allowed in an object initializer?

  • If the issue can't be reproduced by others, edit the question to provide details on the environment / configuration needed to consistently reproduce the problem. If possible, add a Stack snippet (the snippet must be runnable) / playground / code sandbox link where the issue can be reproduced in a controlled environment.


Return to the index

Added caveat about languages available in Stack snippets
Source Link
Heretic Monkey
  • 12.1k
  • 5
  • 48
  • 70
Loading
Post Made Community Wiki by Cesar MStaffMod
Source Link
Loading