Trouble reporting bugs on gitlab

I have been struggling at Gitlab to report a couple of similar crash related bugs. My second one was experienced in symbol editor. Both involved forgetting to set the grid back to 50 mils after using a finer grid.

Bobs Misc Analog Malfunctions.lib (2.9 KB)

  1. Change grid from 50 mils to 5 mils and forget to change it back.
  2. Move a pin
  3. Ooops. I did not intend to move the pin off 50 mil grid. Hit escape key.
  4. KiCad crashes.
  5. I have repeated this several times using the IN180 symbol in the attached.

Application: KiCad
Version: (5.99.0-743-g3ab9db6ff), release build
Libraries:
wxWidgets 3.0.4
libcurl/7.66.0 OpenSSL/1.1.1d (Schannel) zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.39.2
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Build date: Jan 13 2020 22:17:18
wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.71.0
OpenCASCADE Community Edition: 6.9.1
Curl: 7.66.0
Compiler: GCC 9.2.0 with C++ ABI 1013

Build settings:
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_PYTHON3=OFF
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON

Do you mean you haven’t succeeded? What’s the specific problem with gitlab?

Complicated. I am not sure whether my bugs are there. I cannot find them. I have difficulty to use the search function on gitlab. I am unaware of a “preformatted issue template.”

e-mails:

Issue was closed by Seth Hillbrand via commit f1fcf3f1dc4ac780db0caaf1a850e5193b944c6e

Please don’t submit duplicates of your own issues. Why do you immediately close your issues after submitting them? Are they no longer valid?

What is the problem with using the preformatted issue template?

This means seth already fixed what you reported :wink: (It is an auto generated message that means there was a git commit referencing your issue)

OK thanks Rene and eelik. So my post was moved, and then I did not see it. Similar for my bug report? Anyway:

  1. It looks like my bug reports are filed under my regular name, not my e-mail address or my username in this forum.

  2. Just now I downloaded and installed kicad-r14864.fe1b8c888-x86_64-lite and then reproduced the bug again.

Bug reports that are fixed no longer appear in the standard view on gitlab. This is because they are closed and the standard view only shows open issues.

1 Like

I found the following reports by you:

The strange thing is i can not find the “closed” message you reported above (But i have very little expirience with gitlab so it could be that it differs in beahavior with github here. Github would show the same message in the webview)

I just figured out a clarification of my reported bug.

I think the grid size does not matter. When I go to move the pin, a mouse click sets the new location of the pin. If I set the pin location before I do anything, I get no crash. I do get a crash if I hit the escape key before clicking the mouse. I should add that if I do not crash, I cannot undo my move of the pin. Undo does not work.

Well, they are both closed (see my first screenshot above).

Yes but I reproduced the bug a moment ago. See my clarification. I am using the latest download
kicad-r14864.fe1b8c888-x86_64-lite

Ah now i see. One of them was closed by @BobZ, one of them was closed via a commit by @Seth_h

The commit was made 5 hours ago. It will take a while till it is in the nightlies.

Does that mean that he has fixed the problem or only committed to fixing it? I did not intentionally close any bugs.

“commit” means that something has been put into the git repository. But nightly builds are compiled, which happens once a day, and the “commit” which fixed your issue hasn’t been taken into the latest nightly build yet.

image

Thanks.

As I read it, the description is in developerglish :smile: and I cannot tell that it is related to my bug.

My partner claims I speak this at home as well. :slight_smile:

3 Likes

You probably pressed “Comment and Close issue” which actually marks the issue closed, rather than the other action of “closing” a window.

People do the same thing in github…

1 Like

Still happens to me from time to time. (But mostly because i think i need to cancel a comment i started. But github does not have a cancel feature)