13 Matching Annotations
- Sep 2024
-
www.chiark.greenend.org.uk www.chiark.greenend.org.uk
-
If you give the programmer a long list of inputs and actions, and they fire up their own copy of the program and nothing goes wrong, then you haven't given them enough information.
-
- Jan 2022
-
svelte.dev svelte.dev
- Mar 2021
-
github.com github.com
-
In order to move forwards with this issue I'll need an example app that reproduces the behavior (https://www.codetriage.com/example_app).
-
-
github.com github.com
-
But I can describe a simple reproduction case to demonstrate the developer inconvenience (can provide a sample app if it's helpful).
-
-
www.codetriage.com www.codetriage.com
-
An example app is an application that is designed to reproduce a bug or demonstrate an issue.
-
Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?
-
- Jan 2021
-
github.com github.com
-
Also as an aside, your REPL is far, far too complicated. You've got a much better chance of us being able to see your issue and fix it if you boil it down to just the minimum required code in order to reproduce the issue.
-
- Oct 2020
-
stackoverflow.com stackoverflow.com
-
Omitted details change everything here. There won't be circular dependency because unused import is skipped. Consider providing stackoverflow.com/help/mcve .
-
-
github.com github.com
-
Made the repro above more manageable: https://svelte.dev/repl/a55ba18ceca44c898f2b011a0978de85?version=3.6.6
-
- Sep 2020
-
svelte.dev svelte.dev
-
Bug repro for https://github.com/sveltejs/svelte/issues/2086
Fixed by: Bug 1:
- https://github.com/sveltejs/svelte/pull/3172
- https://github.com/sveltejs/svelte/pull/3172/commits/f4ca063c85e491b75d162f429ad243b6f443db13
Bug 2:
- https://github.com/sveltejs/svelte/pull/3209
- https://github.com/sveltejs/svelte/commit/2f08e34b41317619f9bc7bf6bc2418123fb06829
Fixed version here: https://svelte.dev/repl/a55ba18ceca44c898f2b011a0978de85?version=3.6.7
(although https://github.com/sveltejs/svelte/pull/3172/commits/f4ca063c85e491b75d162f429ad243b6f443db13 indicates the fix was included in v3.6.6 tag, so I wonder why it's not fixed here)
supersedes https://codesandbox.io/s/epic-stonebraker-9cxhu?file=/index.js:0-32
Good example of how helpful it is to remove everything irrelevant and create minimal reproducible example.
-
-
github.com github.com
-
If you can't understand where it's coming from in the stack traces, please post screenshots or create reproducing sandboxes and we'll try to help. Most of these are probably coming from a few libraries, so the most productive thing to do is to reduce these cases and then file issues with those libraries.
-
- Feb 2020
-
github.com github.com
-
problem in my app is fixed. It was not related to devise . I removed 'rails-api' gem and it started working.
-