"default_smd" clearance type is not a valid value.
Could have used "wire_smd" but it doesn't seem to matter nowadays.
(cherry picked from commit 86bcf840c1)
Assert message:
Assertion failed at C:\jenkins\workspace\build-windows-kicad-msvc-8.0-stable\.build\kicad\common\widgets\widget_hotkey_list.cpp:309 in WIDGET_HOTKEY_LIST::getExpectedHkClientData: hkdata != nullptr - No hotkey data found for list item
Fixes KICAD-7NV
(cherry picked from commit 9b40e6b2e3)
In old kicad_pcb files, the timestamp can have less than 8 symbols
if leading zeros are stripped.
For example: 0939A342 -> 939A342
(cherry picked from commit 472192f4b8)
Also adds a cancel confirmation dialog.
Also fixes an issue where a thread termination error message is shown
when calling Delete(), because the thread has already exited after
Wait().
Fixes https://gitlab.com/kicad/code/kicad/-/issues/19279
(cherry picked from commit add58faa30)
Items that are part of net ties (pads and copper shapes that connect to
them) should allow connections from any net in the tie. This prevents
clearance errors from being generated for matched nets
Fixes https://gitlab.com/kicad/code/kicad/-/issues/14008
(cherry picked from commit 41d4a8caab)
This does 3 things:
1) Removes unused zone layers on load
2) Does not save unused zone layers
3) Removes unused zone layers from connectivity calculation
(1) Prevents existing boards from using unused zone layers for any
connectivity or rendering. (2) Updates the contents of boards with
removed zone layers to prevent them from propagating. (3) updates the
connectivity while running pcbnew and removing a zone layer
Fixes https://gitlab.com/kicad/code/kicad/-/issues/17288
(cherry picked from commit 6e591f5f91)
We don't need to parse hidden files/directories for backup targets.
This can be very large (in the case of .git directories) and thus
slow when working over NAS.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18341
(cherry picked from commit 2eea14ea58)
Currently, the system allows custom color selection for the Fill Color
property in the Properties toolbar even when Fill Mode is set to Body
Background Color via the Properties window. However, this does not update
the color to match the Body Background color. To fix this, custom color
selection for Fill Color will be disabled when Body Background Color is
chosen.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18919
(cherry picked from commit cb41f39045)
Currently, new global or local net labels are auto-filled with the
net name if the wire is driven by a global or local label. This
currently happens recursively within SCH_LINE. This fix moves this
to determining the driver from the connectivity graph, and removes
the determination from the SCH_LINE code where it does not belong.
(cherry picked from commit b01796cb84)
Make sure the hierarchy navigation history iterator is valid before
attempting to remove an entry from the history list.
Fix an undetected crash where two undo entries were created when drawing
a new sheet. The first entry was sheet properties entry and the second
was for the drawing the new sheet. The second undo would cause a crash
because the sheet no longer existed for the sheet properties commit.
Remove consecutive duplicate hierarchy navigator history history entries.
Navigating to the same path multiple times doesn't really make a lot of
sense.
Don't rebuild the hierarchy twice when drawing new sheets. This is handled
when pushing a commit.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/19358
The benefit of incremental connectivity is only for larger
schematics. For smaller schematics, the downside of larger bug surface
outweighs the current benefits
(cherry picked from commit 74998790e8)
- Remove bespoke collide routine. We should never rewrite these instead
of using the geometry library
- Optimize check by creating unified geometry before colliding
- Make extra variable that we don't need but makes cherry-picks easier
(min/maxAnnularWidth)
Fixes https://gitlab.com/kicad/code/kicad/-/issues/19325
Remove the PROFILE definitions from the incremental connectivity
profiling so a special build isn't required. If the starting and
stopping the profile timer is excessive, we can add this back.
Check early if a symbol is not unique - before calling SchGetLibSymbol
and in SchGetLibSymbol checks the cache before calling LoadSymbol.
This speeds up opening the symbol browser significantly when having lots
of symbols in the design that needs to be polled from a database
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18826
The various wxCHECKs in the SCH_PIN object where being raised inside
the SCH_SYMBOL object which would also raise it's own wxCHECK that
would cause a recursion guard failure and segfault. The offending
wxCHECKs were replaced with null pointer checks. Missing library
symbol links will be shown with the missing library symbol.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/17146
Fixing this required disabling the footprint/3D viewer canvas drawing
before destroying the canvas in the dialog dtor. This in turn required
adding a virtual method to DIALOG_SHIM that can be overridden by the
derived object to allow performing actions during dialog shutdown that
can be problematic when performed in the dialog dtor. Please note that
this only works for quasi-modal dialogs. Modal and modeless dialogs
should use close window events.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18107
(cherry picked from commit 2e7d819b5d)
Using wxASSERT would allow segfaults when rebuilding the connection graph
under certain conditions. Using appropriate wxCHECK fixes the segfault
issues. This will most likely result in broken connection graphs.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18136
Bus aliases are per schematic not per sheet path. They only need to be
added to the connection graph once per schematic. Loading bus aliases
multiple times when there are multiple instances of a schematic just
replaces the existing bus alias map entry.
This brings the connection graph more in line with the development branch
changes made in commit edc7603d2a.
If two nets are joined by a global power pin but both have global labels
that override the net name, we still want them to be merged. This
checks for all net names in the drivers when looking for subgraph
merging candidates
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18092
(cherry picked from commit ad985aff9d)
The display in the properties manager for arc tracks
was wrong. Implement a set of Get/SetStartX/Y functions
for the traces, to match the End functions.
This is needed because PCB_ARC overrides GetPosition
to return the arc center, not the start position (whereas
PCB_TRACK does return the start for GetPosition)
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19215
(cherry picked from commit 37469b00b2)
When a net happens to have only coincident items on different
layers, the triangulator was not considering the item layers
when optimizing them away. Add a special case to ensure that
the ratsnest edges will exist in this situation.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18982
This normally should never happen, but could do in limited cases such
as from bad imports or CI/testing inputs. It's probably still a bug
in any real design usage, but assert and continue instead of crash.
In some situations then parent window couldn't be available. Eg, when
eeschema is executed as standalone on macOS and trying to show
the global design block table dialog before the main frame exists.
So replace the assert with return and check the windows pointers bellow.
(cherry picked from commit 20ee4effdc)
A "old" data was not deleted at the right time, and because it was managed
by a std::unique_ptr, a Dtor was called at the wrong time, destroying a
static variable.
C++ RTTI cannot be used reliably to cast between types
across a linker boundary (for example, between EDA_ITEM and
BOARD_ITEM). Doing so will cause failures that only happen
on some platforms, some of the time.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18685
- Add a test to be sure a SCHEMATIC exists before trying to use it
- Delete items in Repeat list and undo/redo list before deleting the schematic
- Delete also these items when loading a new schematic (the repeat list was
not cleaned previously)
Before these fixes I see a use after delete issue due to dangling pointers
stored in Repeat list.
(cherry picked from commit d778cb6647)
This is a little tricky, but this seems to be the simplest
way to approximate the right text placement.
There are still some minor offsets and text size adjustments,
which might be possible to compensate for by experimentation.
(cherry picked from commit fee1d115a6)
I'm not exactly sure where the flip comes in, but it seems to be
universal at least across various files:
* RK3588
* BeagleBone Black
* Some local boards as well
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19224
(cherry picked from commit 54b223a5be)
All the footprints have a ref-des field by default in KiCad, but if the
silkscreen text isn't present in the imported file, we should hide it.
If we see a silkscreen refdes, _then_ show it.
(cherry picked from commit 1d0ba992da)
These seem like footprint fields, but there is no obvious way
to associate them. Dumping them on the the silk/fab layers creates
huge overlapping spam on the board, so for now, just leave them
out.
Allegro has a more "2D" layer system with classes (e.g. DEVICE TYPE)
and subclasses (SILKSCREEN_TOP), which make things difficult to
make map cleanly to KiCad layers.
(cherry picked from commit 29a66714cd)
Some texts were left out of the GRAPHIC_ITEM -> BOARD_ITEM
dispatch in some paths. Unify this item creation to avoid
this possibility (and reduce duplication).
(cherry picked from commit 8152ec06d1)
This seems to be a lossy export conversion - it's not possible
to tell apart a closed zone and a line that happens to end where
it started.
Look for features that indicate that a sequence of graphics are
"open" and should be rendered as a set of discrete graphics,
or "closed" and should be a single polygon.
At least for objects in the BeagleBone Black export, this seems
to work well.
(cherry picked from commit 9a68a9c310)
This is a bit of a hack as it will still only allow
9 more layers and drop the rest, but it's a start and
allows testing using the Beaglebone Black board and the
board in issue 19174.
(cherry picked from commit faae009dba)
Some circles are represented as ARC with start == end, but there
are also CIRCLE elements.
For consistency with the existing code, actually use 360-degree
arcs for circles (which also allows them to be used in polygon
holes if needed)
(cherry picked from commit 6cfcba9b37)
These appear to be 'unplaced' components, which we don't really
have a good way to represent at the moment. For the time being,
skip them.
Relates-To: https://gitlab.com/kicad/code/kicad/-/issues/19174
(cherry picked from commit bac027881a)
By adding points to holes as we go, we leave ourselves open
to adding invalid (<3 point) holes to the polygons. This causes
crashes if it happens, so we should never allow it to happen.
Instead of building holes in-place, construct them externally
and only add them if they are valid.
This probably wouldn't actually happen for a valid Fabmaster
file, but if it did, it would be bad new, and we shouldn't leave
crashable pathways facing user input.
(cherry picked from commit 926ef7677b)
When excluding/re-including DRC violations, update the
BDS list immediately rather than waiting for the
BOARD::RecordDRCExclusions() to be called.
This was implemented in 8.99 in 0598ca0f90
(along with DRC exclusion comments).
Follow that commit's updates of the m_DrcExclusions
structures in an analogous way.
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19113
Currently, unselecting the bold option resets the thickness to the
standard size instead of reverting to the original thickness.
To address this, the original thickness should be preserved so it
can be restored when bold is turned off.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18975
(cherry picked from commit 43b1bc52db)
If a schematic item was selected, when activating the probe tool from the
simulator, and deactivating from the Select Item sch editor tool, a crash
happened.
From master branch
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18547
Parsing an empty string as double/int produces uninitialised data.
That is likely to cause an undefined amout of chaos later on,
so catch it explicitly with a wxCHECK.
It's still something that shouldn't happen, and could still cause
chaos, but it's at least deterministic. It also avoids putting
gigantic numbers into things that don't expect them. For example
normalising an angle of 1e303 is functionally an infinite loop.
This happens at least in files with missing fields in rows,
like in #19174's file, line 4:
S!U2306!IC!!!!!!SOT_23_5!!!!!SGM2576/TT9107!!!
The file is still broken, but now it loads.
Relates-To: https://gitlab.com/kicad/code/kicad/-/issues/19174
(cherry picked from commit 4d2d70ce22)
When the italic or bold nature is changed, text using outline fonts may
need to change its font. Add this to the SetItalic/SetBold functions.
Also add a counterpart SetItalicFlag function (following SetBoldFlag)
when you only need to set the flag (e.g. when importing or changing
everything in the text properties dialog).
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/18592
(cherry picked from commit b043f334de)
Because it's confusing when the dialog shows last target value, but it
doesn't apply when you start tuning.
Also the last values are remembered in DRAWING_TOOL::PlaceTuningPattern
now, instead of global variables.
Related: https://gitlab.com/kicad/code/kicad/-/issues/18979
-Allow changing length tuning settings before tuning has been started
-Do not exit out of the length tuning tool after each placement
-Keep specified settings between pattern placements
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18979
(cherry picked from commit 78b2e53777)
A recent change set the parent member of a item put in the repeat list to
nullptr (this is OK) but the code to copy an item from this list did not
update this parent member.
From master branch, commit 8f348820
Handle boolean value parsing during paste operation. The boolean value
was not being handled correctly in grid_tricks, which prevented the
boolean value from being pasted into the target row
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18985
(cherry picked from commit 07f96b83b7)
The white text in dark mode is too washed out on the cell colors to be
visible. Since we already purposely subdue the colors in dark mode, the
easiest fix is to just always use black text.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/17033
(cherry picked from commit c7d280dfa1)
Currently, the used layers passed from parseLayers() do not include
mandatory layers if they are missing in the loaded board file.
To fix this, we can manually add the mandatory layers to ensure they
are always enabled.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18978
(cherry picked from commit 6e2ed5666d)
Previously, when attempting to paste an entire row copied from the global
table into a project table, the value would be pasted from the cell where
the cursor was focused, rather than from the first cell. This issue
occurred because the first cell, a checkbox column, was not selectable.
To resolve this, the checkbox column should be enabled for selection
when the Left Mouse Button event is triggered
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18732
(cherry picked from commit 1fc8e65f7a)
Commit 5ca34147 (a cherry pick from master branch) broke these cross-references.
If was fixed later in master branch, but these changes cannot be cherry picked.
So the old code is reused in 2 functions to fix the issue.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18534
The project was not assigned to the board in the 3D viewer frame,
resulting in a failure to locate the relative path for STEP models.
To fix this, the current project should be assigned to the board in
the 3D viewer frame.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/16242
(cherry picked from commit d2e51fdb5f)
c824484c Fix 3D viewer omission of STEP models with relative path assignment
Co-authored-by: Dhineshkumar S <dhineshkumar@cgvakindia.com>
When loading a schematic that contains fields with trailing/leading white
space, show an infobar message. When editing the template field names,
prompt the user to keep or remove any trailing or leading white space
characters from field names.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18601
(cherry picked from commit d9d984d2c8)
If we are checking a point that is inline with multiple segments, we
were counting both the entry and exit as crossings, leading to points
inside a polygon being registered as outside. Changing the conditional
to only catch one crossing as required.
Adds a QA check to ensure that this remains fixed
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18377
(cherry picked from commit 7916b1ddb8)
We convert arcs/circles to polygons with an allowable error. This means
that the segments might end up being closer than we expect and we should
allow for this deviation when checking courtyards
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18347
(cherry picked from commit 3a8a5bb378)
When calculating the pad bbox, we need to only account for deflation of
zone min width. Additionally, when calculating spokes for roughly
circular elements, we don't need to go to the bbox corners, so special
case it to rotate after the fact
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18329
Sin/Cos are pre-caclulated for all multiples of 45° so we don't need to
short circuit them here. Calculating the bbox intersection point allows
us to pick spoke sizes that are not overly large so as to miss the hit
point testing in the associated fill areas.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18329
In order to find elements, we need to have bbox correctly set. ::min()
for doubles, just gives the smallest positive value. So negative placed
graphics don't trigger the right bbox and they get nopped out of
existence.
Similarly, following the advice from @msteinbeck, we elevate the degree
of the spline before converting it to beziers in order to properly
represent in KiCad
Fixes https://gitlab.com/kicad/code/kicad/-/issues/11153
(cherry picked from commit e0fc7b2b88)
First, ensure that we calculate the bbox of the imported elements.
If the total BBOX is outside our allowed value, refused to import. This
needs to be scaled or addressed in an external editor
If the bbox fits, then make sure that we clamp it such that the largest
element is still within our bounds
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18523
(cherry picked from commit a724b3d8b1)
Previously, creating a new member row by pasting text from the clipboard
did not trigger a cell value change which prevented the correct
association of the member value with the alias. To ensure this, we force
the member to be updated with the current alias before closing the dialog,
as well as with the previous alias when adding a new one
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18558
(cherry picked from commit cd40c6bbbf)
Currently, the system allows custom color selection for the Fill Color
property in the Properties toolbar even when Fill Mode is set to Body
Background Color via the Properties window. However, this does not update
the color to match the Body Background color. To fix this, custom color
selection for Fill Color will be disabled when Body Background Color is
chosen.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18919
(cherry picked from commit cb41f39045)
The "Plot to PDF" function was producing PDF files that lacked text and
graphic items in viewers like Adobe and Foxit. This issue was caused by
the use of the %g format specifier for floating-point numbers defined in
the PDF specification when writing text and drawing shapes in the PDF.
This incorrect format led to a "Too Few Operands" error during rendering.
To resolve this issue, all floating-point numbers must be specified in
fixed-point format according to the PDF specification wherever the issue
was generated.
Fixes#16465
(cherry picked from commit 8851cd77ab)
On Linux, this directory is shared between users, so a multi-user
machine needs to let the other users have access to the directory to
create their own lockfiles.
(cherry picked from commit 921358b096)
From master branch
There is a fallback mechanism here designed to catch cases
where a hotkey is bound to a key that needs Shift to be
input (e.g. ? requires Shift on many non-US keyboards,
but the hotkey for that should be '?', not 'Shift+/'). For any key
where the two options are equally-valid "main" key (e.g. '6' and '^'
or '?' and '/' or ':' amd ';'), this is correct, as it allows
the hotkey to be simply the character in question.
Letters don't require this treatment - using this fallback
in the letter case means that a hotkey bound to 'B' will
also fire when 'Shift+B' is pressed, even when Shift+B is
bound to something else. In fact, it could even preempt the
real Shift+B hotkey.
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19093
After opening a context menu and left clicking on the 3D canvas, the view
was modified because a drag event was generated, probably a wxWidgets bug.
From master branch.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/17422
The change wasn't re-reverted in 1.8.3, it was just not
included. It was than _also_ reverted in 1.8.4, as it was for
1.8.2 (those two tags are on different branches - main and maint/v1.8).
Hopefully, this means that we're done here, and v1.8.5 will also be
const-y, whether it is based on main or maint/v1.8.
The current state of play:
* 1.7.0 and older: const
* 1.8.0, 1.8.1: no const
* 1.8.2: const
* 1.8.3: no const
* 1.8.4: const
Future:
* 1.8.5/1.9.0: presumably/hopefully, const
This is currently breaking at least Arch and Fedora Rawhide
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19062
(cherry picked from commit 9f579f787b)
TTF fonts are supposed to obey a specific winding. But sometimes they
don't, especially with garbage windows font editing programs. If the
outline with hole winding doesn't have an outline, it is probably an
outline itself
Fixes https://gitlab.com/kicad/code/kicad/-/issues/19010
(cherry picked from commit a6b25d1ee1)
For these texts, and when the view was "flip board view" option, these text
positions were incorrectly calculated for texts having a text rotation not 0.
From master branch
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18980
We renumber duplicated pins but the previous order was essentially
random. This keeps the numeric order of the pins on the screen, falling
back to position if they are not numbered
(cherry picked from commit f4bec843d4)
When two arcs only barely overlapped, we cannot predict the actual point
ends as they exist in the error margins. Since arc tracks have
different radii by definition, rounding errors in calculating the
overlap angle led to some mistaken identification of parallel segments.
This adds an advanced config flag to set the preferred cutoff point
(currently 0.001°) for whether two arcs actually overlap in shared angle
space
(cherry picked from commit 6be6680d8c)
Previously, when the search panel was hidden, the focused search control
did not lose focus, causing an inability to focus on any items in the
parent window when using shortcut keys. This forces correct focus back to the edit window
Fixes https://gitlab.com/kicad/code/kicad/-/issues/12613
(cherry picked from commit 2bee6f2549)
Currently, the Gerber file is parsed line by line, This is most of time OK.
But warning: in rare cases some files can have *very long* lines (in fact
have only one line), so the buffer must be very large.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18890
The hierarchy navigator was failing to update properly on undo/redo and
when the referenced schematic file of a sheet was changed.
(cherry picked from commit a871311b6f)
Commit 83de056de9 broke loading legacy schematics that are not shared.
Legacy schematics do not contain instance data "AR Path=" entries when
the schematic file was not shared. The reference and unit information
was only stored in the symbol reference field and unit entries in the
symbol definition.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18779
(cherry picked from commit 21dd41eeb2)
Previously, it was flipped using the shape anchor position. But for this
shape, the anchor (top left corner)) is reinitialized after flipping, so
flipping twice moves the shape.
Now the rectangle center is used as reference position to flip the shape
From master branch
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18797
PCB_SHAPE::Normalize() normalized a graphic segment by (sometimes) swapping
start and end points. But it creates an issue when flipping a segment: the
reference point can be changed.
This normalization was made for DRC purpose when comparing 2 footprints.
Now, PCB_SHAPE::Normalize() does not change end points of a segment, and a
specific PCB_SHAPE::NormalizeForCompare() normalize fct is used for DRC compare.
Previously, start and end points were moved, and therefore the shape itself was
modified. It was probably unexpected.
Now just align the arc start point or the circle center point on grid.
Under certain circumstances, the library symbol links were missing
the library nickname causing the schematic symbols to appear as if
the library symbol was missing.
Added a helper function to create the symbol library name to avoid
code duplication.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/17143
(cherry picked from commit 7acd057c86)
Use the X and Y axis inversion preference settings in the "PCB Editor"
"Origin & Axes" panel to invert the internal coordinates to display to
the user.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18662
(cherry picked from commit 64d4dbb2e8)
If we do not have both a device and type for the sim model, return none
because we cannot parse it. This is handled by the calling routines.
Otherwise, we would return raw spice type erroneously.
There's a change in Boost 1.86 that breaks the SHA1 hashing
in 3D cache.
The master KiCad branch ditches SHA1 entirely here, but it's quite
an invasive change to backport. So apply a sticking plaster for
the remainder of v8.
Relates-To: https://gitlab.archlinux.org/archlinux/packaging/packages/kicad/-/issues/1
Not only is this simpler, but it should be compatible
with all Boost versions (the cast is a problem in 1.86)
and it was also 'improved' in 1.86 for better mixing.
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/18651
(cherry picked from commit 9a3ebfba40)
Boost 1.86 removed the boost::random dependency from boost::uuid, so
we need to include those headers on our own now to use the random
mersenne twister implementation.
(cherry picked from commit a9e115925a)
Adds REPORTER::HasMessageOfSeverity for WX_STRING_REPORTER,
which allows us to show simulation warnings and fail only if there's errors.
Also fixes a crash when SPICE_GENERATOR_KIBIS throws an IO_ERROR.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/18143
(cherry picked from commit 36019314e9)
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.