giseldo/neodataset huggingface dataset:
Partially broken undo in eeschema (lp:#1824403)

[Original report](https://bugs.launchpad.net/bugs/1824403) created by **Ron Burkey (rburkey)**
```
If you perform an operation that (as a side effect) splits an existing wire
into two parts and adds a junction, undoing that operation does not restore
the wire properly.

I've attached an image that's a composite of several screenshots that
illustrates the issue.  The top of the image (labeled "A") is prior to any
operation.

The middle of the image ("B") shows the result of an operation, which is
moving an arrow-shaped object (which happens to be a PWR_FLAG), rotating
it, and attaching it to the wire next to the net label "+3VDC", which
splits the wire into two segments and adds a junction.

The bottom of the image ("C") is the result of an undo with ctrl-Z.  The
PWR_FLAG has moved back to its original position, but the original wire
segment is not correctly restored.  Subsequent undo's have no effect.

I hadn't noticed this problem prior to today's nightly build, so I suppose
it may be a regression.

Application: kicad
Version: 5.1.0-unknown-e90452d~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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
```
Original tags: eeschema

Story points: 10.0
Grid size spontaneously changes (lp:#1824362)

[Original report](https://bugs.launchpad.net/bugs/1824362) created by **Ron Burkey (rburkey)**
```
In eeschema, if you run an ERC, and then use the links in the ERC window to
jump to the location of an error, the grid size can spontaneously change.
(For me, it happens annoyingly often.)

I consistently use a 25-mil grid, and the change (when it occurs) is always
to 50 mils.

This has been an ongoing annoyance for me for a long time (since version 4,
I believe, when I started using KiCad), but I have hesitated to report it
because I cannot fully work out the conditions under which it occurs.  Here
is my best attempt at a procedure to reproduce it using today's nightly
build:

1. Create a hierarchical design, and put some kind of an error on a child
sheet.
2. Set the grid size to 25 mils.
3. Save and exit.
4. Run eeschema again, and verify that the grid size is still 25 mils.
5. Run the ERC.
6. Use the ERC links to jump to the error.
7. Verify that the grid size is now 50 mils.

Application: kicad
Version: 5.1.0-unknown-e90452d~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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
```
Original tags: eeschema

Story points: 6.0
ERC no longer fully functional with no-connects (lp:#1824359)

[Original report](https://bugs.launchpad.net/bugs/1824359) created by **Ron Burkey (rburkey)**
```
I have a number of schematics in which is is not visually feasible for no-
connects to be directly placed at the associated connector pins, and
therefore in those cases there is a short wire between the pin and the no-
connect.

This has always been accepted by ERC before, but with the latest nightly
build it is flagged as an error.  (So I can have dozens of these errors on
any given schematic.)

Perhaps this is related to the recent fix for bug #1821342, which also
involved wires between component pins and no-connects.

Application: kicad
Version: 5.1.0-unknown-e90452d~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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
```
Original tags: eeschema

Story points: 6.0
netlist problem with nested dc sweep (lp:#1824336)

[Original report](https://bugs.launchpad.net/bugs/1824336) created by **Dietmar Warning (m+s)**
```
If I setup a nested dc sweep e.g. for mos output characteristic with vds
sweep at first and vgs sweep as second I got a simulation error because the
dc command is wrong, see below

.dc V2 0 3 10mV1 500m 3 500m

A space is missing before V1.

Working with Version 5.1.0_1 release build under Win 7.
Single DC sweep is working.
```
Original tags: netlist setup simulation

Story points: 6.0
show shortcuts on icons (lp:#1824296)

[Original report](https://bugs.launchpad.net/bugs/1824296) created by **zakhar nasimov (thedocument)**
```
It would be ideal to show shortcut keys besides the tooltips which appear
shortly after cursor hovers over the icon.

Application: kicad
Version: 5.1.0, release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 5.0.2-gentoo x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.0
    OpenCASCADE Community Edition: 6.9.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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=OFF
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
impliment option to prohibit laying track into copper fill zone (lp:#1824288)

[Original report](https://bugs.launchpad.net/bugs/1824288) created by **zakhar nasimov (thedocument)**
```
A few simple options to cause a filled zone to also be a keepout for either
tracks, vias or both  right into the copper fill zone options dialog. This
prevents a few issues especially with external autorouters.

Application: pcbnew
Version: 5.1.0, release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 5.0.2-gentoo x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.0
    OpenCASCADE Community Edition: 6.9.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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=OFF
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
Eeschema: Create / undo self-intersecting wire breaks dlist (lp:#1824251)

[Original report](https://bugs.launchpad.net/bugs/1824251) created by **Seth Hillbrand (sethh)**
```
See the attached video for details.  Create a wire that connects to the
same wire in two places and then undo the connection.  The action is not
undone correctly and the dlist is corrupted.


Application: kicad
Version: (5.1.0-221-ge28c937a5c-dirty), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-4-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 8.3.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0
Wrong PNG import  in bitmap converter (lp:#1824238)

[Original report](https://bugs.launchpad.net/bugs/1824238) created by **Hildo Guillardi Júnior (hildogjr)**
```
I am importing the attached file to "Bitmap to Component COnverter" trying
to create the .kicad_mod file. In the dialog visualization the image is
just fine but, in the library created it is just a rectangle.

Application: kicad
Version: 5.1.0-unknown-89d2e67~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-145-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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
```

Story points: 6.0
Routing issues with 5.1 : routes do not follow pad (lp:#1824182)

[Original report](https://bugs.launchpad.net/bugs/1824182) created by **Félix Piédallu (felix-piedallu)**
```
When routing with Kicad 5.1, routes tend to avoid the pad… See the attached
image when i try to go to the right of the PCB.
I never experienced this with <=5.0.
The workaround is to route TO the pad and not FROM the pad (even though the
issue is the same, it's easier to force the route to follow the pad
correctly).
The expected behaviour is what you can see on PD3.
```
Original tags: pcbnew pns

Story points: 22.0
Reference-designator-number (REFDES number) of symbols all gone or reverted back to "?" on an existing schematic that newly/re-assigned to be linked/specified as a sheet of another schematic of different project. (lp:#1824042)

[Original report](https://bugs.launchpad.net/bugs/1824042) created by **Heru Himawan Tejo Laksono (heru-htl)**
```
This bug is happened to KiCad Version: 5.1.0, compiled from source code
under Slackware 14.2 with wxWidgets 3.0.2 Unicode and Boost 1.59.0.

Bug description:
The reference designator number of symbols in Eeschema-schematics are all
gone or reverted back into "?" on an existing schematic that newly/re-
assigned to be linked/specified as a sheet of another schematic of
different project.

Notice:
This bug also happened to KiCad 5.0.x released as debian package under
Debian Stretch from backports repository with release version numbered:
5.0.2+dfsg1-1~bpo9+1

Step depiction to check/reproduce this bug:
1. Create a project named i.e as XXX.
2. Create a schematic with file name i.e XXX.sch under XXX project, add
some symbols in it, set appropriately and correctly all REFDES of such
symbols i.e as R1, R2, C1, so on.
3. Create another project i.e named i.e as YYY.
4. Create a schematic with file name i.e YYY.sch under YYY project,
place/add a Hierarchical Sheet, configure such Hierarchical Sheet --> on
Schematic Sheet Properties, set "Sheet name" i.e as "YYY_schematic", set
"File name" into the path of YYY.sch, and click OK button of Schematic
Sheet Properties to apply.
5. Double click to the Hierarchical Sheet as set in step 4 above to open
YYY.sch, and, you'll find that all reference designator of all symbol in
YYY.sch just gone, reverted back unexpectedly i.e into R?, C?, U? and so
on.
```
Original tags: eeschema

Story points: 6.0
eeschema: different hierarchical label not connecting (lp:#1824003)

[Original report](https://bugs.launchpad.net/bugs/1824003) created by **Alan Miller (alanmi)**
```
Application: kicad
Version: (5.1.0-173-g27e6f5b9e), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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

I use 2 hierarchical labels on my schematic, call them Ind and IV2, if I
connect them inside the sheet and on the upper level connect them to 2
components, they are seen as 2 separate nets when importing in pcbnew

Used to work but not anymore.
```

Story points: 6.0
Bad description for power symbols (labels) and the special pwr_flag symbol (power out marker) (lp:#1823996)

[Original report](https://bugs.launchpad.net/bugs/1823996) created by **Rick Jenkins (rick-hartmantech)**
```
The "Power Port" menu contains a large number of symbols labelled as "Power
Flag", for example "Power Flag, +3.3V". The DRC does not recognise these
components as power flags; only the general PWR_FLAG symbol seems to be so
recognised. This is confusing to the user.

Either the symbols not recognised as Power Flags should be renamed as
something else, such as "Power Net 3.3V", or (better) the DRC should be
modified to recognise them as Power Flags.

Application: kicad
Version: 5.1.0, release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 5.0.7-gentoo x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.0
    OpenCASCADE Community Edition: 6.9.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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=OFF
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0
Segmentation fault after a failed assertion when "Cleanup Tracks and Vias" in Pcbnew (lp:#1823973)

[Original report](https://bugs.launchpad.net/bugs/1823973) created by **Paul van der hoeven (paulvdh)**
```
KiCad V5.1.0+dfsg1 gets a "failed assertion" when clicking on:
> Pcbnew / Edit / Cleanup Tracks and Via's.

The backtrace shows:
ASSERT INFO:
/build/kicad-PCtFts/kicad-5.1.0+dfsg1/pcbnew/tracks_cleaner.cpp(363):
assert "connectivity->GetConnectivityAlgo()->ItemEntry( aTrack
).GetItems().size() != 0" failed in testTrackEndpointDangling().

BACKTRACE:
[1] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&)
[2] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[3] wxEvtHandler::TryHereOnly(wxEvent&)
[4] wxEvtHandler::DoTryChain(wxEvent&)
[5] wxEvtHandler::ProcessEvent(wxEvent&)
[6] wxWindowBase::TryAfter(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxMenuBase::SendEvent(int, int)
[9] g_closure_invoke
[10] g_signal_emit_valist
[11] g_signal_emit
[12] gtk_widget_activate
[13] gtk_menu_shell_activate_item
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_main_do_event
[17] g_main_context_dispatch
[18] g_main_loop_run
[19] gtk_main
[20] wxGUIEventLoop::DoRun()
[21] wxEventLoopBase::Run()
[22] wxAppConsoleBase::MainLoop()
[23] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[24] wxEntry(int&, wchar_t**)
[25] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[26] __libc_start_main
[27] _start

**** Full version info: ****

Application: kicad
Version: 5.1.0+dfsg1-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-4-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: Clang 7.0.1 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

****

On my system this is triggered every time in the "Highpower-Mechaduino"
project.
I zipped the whole project and uploaded it to the KiCad users forum:
https://forum.kicad.info/t/kicad-5-1-crashes-often/16232/13?u=paulvdh

Direct link to the zipped project:

https://kicad-info.s3.dualstack.us-
west-2.amazonaws.com/original/2X/9/9b29de1e9c5628c4c063f82109693d1a326f5645.zip
```
Original tags: pcbnew

Story points: 6.0
pcbnew copper pours does not close (lp:#1823863)

[Original report](https://bugs.launchpad.net/bugs/1823863) created by **Martin Thomas (mtlaunchpad)**
```
I have a board with an inner copper pour. I marked it with the signal name
(U_Half) but it did not contact with the vias.
I use the the following version:
***
Application: kicad
Version: (5.1.0-201-gd93008030), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 GnuTLS/3.5.8 zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.19.27-mt x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
***

I attached the board, the problem is the copper pour in Layer In1.Cu on
Zone priority Level 1 within the big zone. I want it to be "/U_Half" which
does not work.


With an older Version I didn't have this problem. The version without
problems is:

***
Application: kicad
Version: (5.0.0-rc2-dev-107-g49486b83b), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1
librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
***
```

Story points: 8.0
ERC no longer works with hidden power pins (lp:#1823741)

[Original report](https://bugs.launchpad.net/bugs/1823741) created by **Ron Burkey (rburkey)**
```
After upgrading KiCad today (my previous update had been last week or the
week before, I believe) eeschema's ERC no longer works the way it had been
with hidden power/ground pins on my components.  The same schematics which
passed ERC last week, now show hundreds of errors.

I have many, many schematics affected by this problem, but an example of a
schematic that was error free last Friday but error-ridden today (Monday)
is here:
https://github.com/virtualagc/virtualagc/tree/schematics/Schematics/2005263-

(I don't know if it makes any difference, but the schematic is structured
as follows, in so far as power and ground are concerned.  There are two
sheets, tied together by a parent sheet.  There are 3 power/ground buses,
called FAP, 0VDCA, and +4SW.  Each of these buses has a single PWR_FLAG,
located on the parent sheet.  All of the components with hidden FAP, 0VDCA,
and +4SW pins are on the two child sheets.)

Application: kicad
Version: 5.1.0-unknown-a81512c~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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
```
Original tags: eeschema

Story points: 6.0