primordic/IssueDupesLite huggingface dataset:
Repository: xmartlabs/XLForm

Issue #554: UI breaks on iPad Pro in Landscape
Created: 2015-09-14T09:36:14Z
The width of xlform rows does not stretch to bounds of the screen, instead it centers itself. I would assume using autolayout should have mitigated this issue. Here is the screenshot of how the UI looks.

Duplicate issue #593: Label position for XLFormRowDescriptorTypeSelectorPush is not aligned properly
Created: 2015-09-29T21:37:52Z
The label position for XLFormRowDescriptorTypeSelectorPush is not aligned properly.  It is indented a pixel or two to the right of other row types.

Closing comment (2015-10-02T15:24:21Z): @mtnbarreto It's related to #554
Repository: xmartlabs/XLForm

Issue #235: incorrect behavior when adding a new row in response to pickerview selection on a previous row
Created: 2015-02-20T06:27:23Z
When selecting value from pickerview the new row creation using the following method:
self.form.addFormRow(<#formRow: XLFormRowDescriptor!#>, afterRow: <#XLFormRowDescriptor!#>)
should result in row being created below the in-line pickerview. Instead the row is created before the in-line picker view!
Issue Update: The issue I notices is that that the inline picker shows up as one of the rows in section.formRows with a tag = nil. This messes up the ability to add a new row at the right location in the array.
Workaround: The fix I am using is to filter out the tag = nil from formRows array. Ideally, this should be fixed in the base code logic, so that the same logic for adding a new row can be used whether the selector is "inline" or "push".

Duplicate issue #257: Issue #235 Repost..not sure if it got the attention of Xmartlabs..
Created: 2015-03-11T02:47:06Z
When selecting value from pickerview the new row creation using the following method:
self.form.addFormRow(<#formRow: XLFormRowDescriptor!#>, afterRow: <#XLFormRowDescriptor!#>)
should result in row being created below the in-line pickerview. Instead the row is created before the in-line picker view!
Issue Update: The issue I notices is that that the inline picker shows up as one of the rows in section.formRows with a tag = nil. This messes up the ability to add a new row at the right location in the array.
Workaround: The fix I am using is to filter out the tag = nil from formRows array. Ideally, this should be fixed in the base code logic, so that the same logic for adding a new row can be used whether the selector is "inline" or "push".

Closing comment (2017-05-30T03:31:10Z): Closing this as it duplicates #235
Repository: xmartlabs/XLForm

Issue #554: UI breaks on iPad Pro in Landscape
Created: 2015-09-14T09:36:14Z
The width of xlform rows does not stretch to bounds of the screen, instead it centers itself. I would assume using autolayout should have mitigated this issue. Here is the screenshot of how the UI looks.

Duplicate issue #594: No table view cell separator in iOS 9
Created: 2015-09-30T00:32:28Z
When I have a row in the form of type XLFormRowDescriptorTypeSelectorPush, I see separator lines between each row.  BUT when the form contains only rows of type XLFormRowDescriptorTypeText, there are no separator lines!
iOS 9 bug?  XLForm bug?

Closing comment (2015-09-30T17:43:31Z): imho, this bug is related to #554
Repository: xmartlabs/XLForm

Issue #252: XLFormInlineSelectorCell overrides custom font
Created: 2015-03-09T03:49:20Z
I am setting a custom font for the inline selector textLabel and detailTextLabel but they seem to be getting overridden after the value has been selected:
-(void)update
{
    [super update];
....
    self.textLabel.font = [UIFont preferredFontForTextStyle:UIFontTextStyleBody];
    self.detailTextLabel.font = [UIFont preferredFontForTextStyle:UIFontTextStyleBody];
}

Duplicate issue #259: The method "update" overrides font configurations
Created: 2015-03-11T19:29:07Z
Description
Font configurations set in cellConfig or cellConfigAtConfigure are discarded once the cell is updated. In particular classes, the method update assigns the values to the font property of textLabel and detailTextLabel.
self.textLabel.font = [UIFont preferredFontForTextStyle:UIFontTextStyleBody]; 
self.detailTextLabel.font = [UIFont preferredFontForTextStyle:UIFontTextStyleBody];
Click here to see the full source.
Questions
Why are these values even being set? UIKit initializes these objects with default settings already.
Solution
Delete these lines.

Closing comment (2015-03-12T17:26:28Z): Related to #252
Repository: xmartlabs/XLForm

Issue #494: Constraints warning on running XLFormViewController
Created: 2015-08-07T03:13:00Z
When I am running an XLFormViewController in my app I get the below warning - I also see the same warning in the example application on the start screen.

2015-08-07 04:11:37.102 XLForm[70659:41051330] Warning once only: Detected a case where constraints ambiguously suggest a height of zero for a tableview cell's content view. We're considering the collapse unintentional and using standard height instead.

Duplicate issue #718: ambiguously suggest a height of zero
Created: 2016-01-30T16:18:14Z
In formRowDescriptorValueHasChanged I'm checking row tag and value like this
if formRow.tag == "marketEnabled" {
if let text = formRow.value where text as! String == "enabled" {
//few repeats of creating row and adding via form.addFormRow here
So it looks like the section expands. on this action I'm getting this error:
2016-01-30 19:14:24.044 XLFormTests[18342:11002416] Warning once only: Detected a case where constraints ambiguously suggest a height of zero for a tableview cell's content view. We're considering the collapse unintentional and using standard height instead.

Closing comment (2016-01-31T16:00:25Z): Possible duplicate of #494?
Repository: xmartlabs/XLForm

Issue #483: Form is displayed under navigationBar in ios9
Created: 2015-08-01T17:01:20Z
Running Xcode 7beta4.

Duplicate issue #519: XLForm weird layout issue in iOS 9
Created: 2015-08-23T15:44:53Z

Closing comment (2015-09-09T04:55:53Z): same as #483
Repository: yahoo/CMAK

Issue #238: support for 0.10.0.0?
Created: 2016-05-31T05:36:02Z

Duplicate issue #260: support for kafka 0.10
Created: 2016-07-01T23:19:49Z
will kafka-manager support kafka 0.10?

Closing comment (2016-07-11T05:51:11Z): Closing this as duplicate of #238
Repository: yahoo/CMAK

Issue #18: binary release would be awesome!
Created: 2015-02-09T19:44:34Z
A binary release of this as an executable jar would be awesome! I'd love to try this but I'm not very familiar with the scala toolchain and I'm working through some difficulties with sbt (which I attribute to operator error). Thanks, this kafka-manager looks very cool.

Duplicate issue #294: Releasing the compiled binaries and dependent libraries
Created: 2016-09-08T09:29:50Z
Hi Folks,
We have issues building Kafka Manager in our organisation because of firewall settings , we basically cannot connect externally to download dependent libs while doing sbt build .
Is it possible to also publish/release a compiled version of Kafka Manager along with the source code ?
I am sure this will help many like me .

Closing comment (2017-09-15T09:06:34Z): This is a duplicate of #18 which was closed without really solving the problem as providing a build method is not the same as providing the binaries.
Repository: yahoo/CMAK

Issue #189: Support Kafka 0.9.0.0？
Created: 2016-01-20T03:59:38Z
Kafka's latest version is 0.9.0.0. Is there any plan to support this new version?
I've installed Kafka Manager and choose to control 0.8.2.1(my Kafka is 0.9.0.0). However, when i create topics or delete topics, it will fail.

Duplicate issue #209: Could u support version 0.9.0.0?
Created: 2016-03-07T01:36:30Z

Closing comment (2016-03-24T10:41:20Z): duplicate #189 and #163
Repository: yahoo/CMAK

Issue #488: brocker.rack is not considered for generating assignments
Created: 2018-03-21T11:51:25Z
I've got a 6 nodes cluster in AWS with broker.rack specified, e.g. broker.rack=us-east-1b.
So there are two in us-east-1a, us-east-1b and us-east-1c.
The plan generated by "Generate Partition Assignments" do not take that setting into account and assigns two partitions (out of three) to instances in the same AZ (with the same broker.rack setting).
On the other hand
kafka-reassign-partitions.sh --zookeeper zoo1-zookeeper.production:2181 --topics-to-move-json-file topics-to-move.json --broker-list "0,1,2,3,4,5" --generate
does consider broker.rack.

Duplicate issue #702: Reassign partition doesn't work properly when broker.rack is set
Created: 2019-11-11T17:20:57Z
I have a kafka cluster with 7 nodes(aws ec2) which are distributed over 3 AZ.
I have recently set the option broker.rack and have specified different AZs for each broker.
When I do Generate Partition Assignment & Reassign Partion I don't see the partition being re-assigned as per the AZs (or as per the rack).
Could you please confirm this case ?
Kafka manager version : 1.0.1.

Closing comment (2019-11-11T17:21:23Z): Duplicates #488
Repository: yahoo/CMAK

Issue #238: support for 0.10.0.0?
Created: 2016-05-31T05:36:02Z

Duplicate issue #278: Supports Kafka 0.10.0?
Created: 2016-08-05T08:55:12Z
Hi,when supports  Kafka 0.10.0 ?

Closing comment (2016-08-08T08:19:11Z): This is a duplicate of #238
Repository: yahoo/CMAK

Issue #58: Report data sizes by date
Created: 2015-05-01T01:11:02Z
A bar chart of data size by hour or by day would be helpful for understanding how regular a data flow is and how much data is new vs soon-to-expire. It would require adding an additional JMX metric to Kafka.

Duplicate issue #6: great project!
Created: 2015-02-04T19:19:40Z
Hi - I just deployed Kafka-manager today and it is pretty cool. It abstracts a lot of the day-to-day tasks into a slick webui. What type of effort would be involved if it included near real-time stats like msg/rates disk usage, cluster utilization... I was thinking it would by a nice enhancement.Thanks, Brendan

Closing comment (2015-05-05T05:15:03Z): msg/sec and bytes/sec have been added by @Mogztter through JMX polling.  Topic size information to be added next via JMX (tracked in #58 ).  Closing issue.  Thanks for the feedback!
Repository: yahoo/CMAK

Issue #497: Add 1.0.1 and 1.1.0 as a valid versions
Created: 2018-04-11T19:59:43Z
Add 1.0.1 and 1.1.0 as a valid versions
https://www.apache.org/dist/kafka/1.0.1/RELEASE_NOTES.html
https://www.apache.org/dist/kafka/1.1.0/RELEASE_NOTES.html (http://kafka.apache.org/11/documentation.html#upgrade)

Duplicate issue #505: When to support kafka 1.1.0
Created: 2018-05-17T09:24:39Z
When to support kafka 1.1.0

Closing comment (2018-05-23T18:05:23Z): This duplicates #497
PR is here #498
Repository: yahoo/CMAK

Issue #814: No Docker image for 3.0.0.5
Created: 2020-11-11T09:09:53Z
Latest tag in https://hub.docker.com/r/kafkamanager/kafka-manager/tags is 3.0.0.4
3.0.0.5 release is not pushed to Docker Hub

Duplicate issue #919: Request for Docker Deployment Support in Kafka-Manager: Enhancing Ease of Installation and Configuration
Created: 2023-05-23T09:04:25Z
Dear Kafka-Manager community team,
Firstly, I would like to express my appreciation and gratitude for the excellent work you have been doing in developing the Kafka-Manager tool. As a developer utilizing Kafka, I have greatly benefited from your project.
I would like to take this opportunity to offer a suggestion, hoping to see support for Docker deployment in Kafka-Manager. Docker, being a widely adopted containerization solution, brings numerous advantages such as flexibility, portability, and ease of deployment. By incorporating Docker deployment support, Kafka-Manager would better cater to the needs of developers and operations personnel.
I understand that this may require additional development and testing efforts, but I firmly believe that such an improvement would greatly benefit the entire community. Using Docker for Kafka-Manager deployment would simplify the installation and configuration process, reduce reliance on specific environments, and provide better scalability.
I hope that my suggestion captures your attention and receives serious consideration. I genuinely believe that by supporting Docker deployment, Kafka-Manager would become a preferred tool for many more developers and operations personnel.
Once again, thank you for your contributions to the open-source community. I look forward to your response regarding this suggestion and offer my full support as you continue to enhance Kafka-Manager.

Closing comment (2023-07-25T11:49:44Z): Duplicates #814 #76
Repository: yaqwsx/KiKit

Issue #639: Pannelization fails on Kicad 8
Created: 2024-02-20T14:30:45Z
Prerequisites

 I have read FAQ
 I use KiKit at least version 1.4.0 (older version are not supported)

KiKit version
1.4.0
KiCAD version
8.0.0-rc3
Operating system
Windows
Description
When clicking "Panelize", the following error is displayed:
[Window Title]
Error
[Main Instruction]
Cannot perform:
[Content]
PCB_TEXT.GetShownText() missing 1 required positional argument: 'aAllowExtraText'
[OK]

Steps to Reproduce

Install KiCad 8
Install kikit from the plugins manager
Install kikit cli from pip when instructed
Attempt to panelize a PCB

Duplicate issue #646: PCB_TEXT.GetShownText() missing 1 required positional argument: 'aAllowExtraText'
Created: 2024-02-25T10:18:27Z
Prerequisites

 I have read FAQ
 I use KiKit at least version 1.4.0 (older version are not supported)

KiKit version
python -m kikit.ui, version 1.4.0
KiCAD version
Version: 8.0.0, release build
Operating system
Manjaro
Description
I'm trying KiCad v8.0 flatpack install
Application: KiCad x86_64 on x86_64
Version: 8.0.0, release build
Libraries:
wxWidgets 3.2.4
FreeType 2.13.2
HarfBuzz 8.1.1
FontConfig 2.15.0
libcurl/8.5.0-DEV OpenSSL/3.1.5 zlib/1.3.1 nghttp2/1.58.0
Platform: Freedesktop SDK 23.08 (Flatpak runtime), 64 bit, Little endian, wxGTK, X11, gnome, x11
Build Info:
Date: Feb 23 2024 23:25:22
wxWidgets: 3.2.4 (wchar_t,wx containers) GTK+ 3.24
Boost: 1.84.0
OCC: 7.7.2
Curl: 8.5.0-DEV
ngspice: 42
Compiler: GCC 13.2.0 with C++ ABI 1018
Build settings:
on Manjaro
System Details Report

Report details

Date generated:                              2024-02-25 12:02:49

Hardware Information:

Hardware Model:                              Dell Inc. Precision WorkStation T5500
Memory:                                      12,0 GiB
Processor:                                   Intel® Xeon® X5680  × 12
Graphics:                                    Quadro K420
Disk Capacity:                               4,3 TB

Software Information:

Firmware Version:                            A18
OS Name:                                     Manjaro Linux
OS Build:                                    rolling
OS Type:                                     64 бита
GNOME Version:                               45.4
Windowing System:                            X11
Kernel Version:                              Linux 6.7.6-1-MANJARO

I'v followed your instructions for installing kikad on flatpack
Sorry if I repeat the KiCad and System Data, but it's more info here
Steps to Reproduce
When I try to panelize a board which panelized on KiCad 7 I obtain the following message:
Cannot perform:
PCB_TEXT.GetShownText() missing 1 required positional argument: 'aAllowExtraText'

Closing comment (2024-02-25T12:46:36Z): Duplicate of #639. TLDR: Use the upstream version, or wait a day or two for v1.5 release (it is blocked by https://gitlab.com/kicad/code/kicad/-/issues/17095 not being resolved in repositories).
Repository: yaqwsx/KiKit

Issue #263: Cannot perform: unsupported operand types
Created: 2021-12-30T12:08:15Z
Describe the bug: When I click "Panelize" I get an error message

Expected behavior: Expcted a panel out of my single board
To Reproduce
Screenshots

Version
Specify which version of KiKit do you use:

1.0.0
PCM + pip
Windows 10

Duplicate issue #360: Unsupported operand types for EDA_ANGLE (and EDA_ANGLE)
Created: 2022-05-20T11:28:58Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.4 (older version are not supported)

KiKit version
kikit, version 1.0.5
KiCAD version
6.99.0-1918-g5edc03e85b
Operating system
Windows 11 (22000.675)
Description
Hi guys !
I just installed Kicad and Kikit (via the PCM) as well as the backend with pip.
The problem is that when generating a panel, I have an error.

Here's the Kicad version :

Application: Editeur de PCB KiCad (64-bit)
Version: (6.99.0-1918-g5edc03e85b), release build
Libraries:
wxWidgets 3.1.6
FreeType 2.11.1
HarfBuzz 4.2.0
FontConfig 2.14.0
libcurl/7.83.1-DEV Schannel zlib/1.2.12
Platform: Windows 11 (build 22000), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: May 17 2022 13:49:30
wxWidgets: 3.1.6 (wchar_t,wx containers)
Boost: 1.79.0
OCC: 7.6.0
Curl: 7.83.1-DEV
ngspice: 36
Compiler: Visual C++ 1929 without C++ ABI
Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ON

Steps to Reproduce
kikit panelize \
    --layout 'hspace: 5; vspace: 5; hbackbone: 5; vbackbone: 5; rows: 4; cols: 2' \
    C:\Users\edoua\Dropbox\Electronics\Projects\1Hz-Generator\Kicad\1Hz_Generator.kicad_pcb panel.kicad_pcb

Closing comment (2022-05-20T11:33:28Z): This is duplicate #263. Nighty has a highly unstable API, and thus, it is not supported. It will not be supported until late fall 2022. Any effort to make nightly work is just a waste of effort at the moment.
Repository: yaqwsx/KiKit

Issue #453: Separate fails to copy outline if it contains circles with angles other then multiple of 90 degrees
Created: 2022-12-06T12:39:34Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.1.0 (older version are not supported)

KiKit version
kikit, version 1.1.2
KiCAD version
6.0.7
Operating system
Linux, voidlinux
Description
kikit separate fails to correctly copy the board outline when it contains circles which do not end at 90 degree angles (at least thats what I have narrowed it down to).
Input:

Output:

Project repository with input & output: mwe.zip
Steps to Reproduce

Create a board with outline with circles which do not start & end at 90 degrees intervals
Run kikit separate -s 'annotation; ref: B1' test.kicad_pcb out.kicad_pcb

Duplicate issue #531: "Kikit separate" command creates Edge.cuts that doesn't exist in the source file.
Created: 2023-03-22T04:29:19Z
Prerequisites

 I have read FAQ
 I use KiKit at least version 1.3.0 (older version are not supported)

KiKit version
1.3.0
KiCAD version
7.0.0
Operating system
Windows 10
Description
Thank you for creating a wonderful tool.
I'm completely new to Github and writing an issue, sorry if I'm breaking any community guidelines. (Also, I'm not good at English since it's my learning language.)
So, I used the kikit separate command to separate my kicad_pcb file which contains multiple PCBs.
The output file was created successfully, but it has weird arc line that is not exist in the original file.
I thought it can be a bug so I'm writing this issue just in case.
Here is the screenshot, the left is the original and the right is the file created by Kikit. You can see the center hole shape has changed. The lines are in Edge.cuts layer.

I'm attaching a ZIP file which contains the original kicad_pcb and the output one. (The original file only contains a single PCB, I deleted others so it'd be simple to point the issue)
kicad_pcb_files.zip
Steps to Reproduce
The command I used was this:
kikit separate --source "rectangle; tlx: -40mm; tly: -100mm; brx:40mm; bry:10mm" stepper_board.kicad_pcb output.kicad_pcb

Closing comment (2023-03-22T07:16:08Z): This is a duplicate #453. See the thread for a work-around.
Repository: yaqwsx/KiKit

Issue #647: kikit kicad8 installation error
Created: 2024-02-27T13:23:38Z
Prerequisites

 I have read FAQ
 I use KiKit at least version 1.4.0 (older version are not supported)

KiKit version
current/master
KiCAD version
8.0.0
Operating system
windows
Description
when trying to install, kikit cannot be found from kicad console.
Steps to Reproduce

Install KiCad 8.0.0 using the windows installer
Open kicad terminal
install Kikit using pip install git+https://github.com/yaqwsx/KiKit@master
Try to execute "kikit --version" -> KiKit cannot be found

Duplicate issue #655: kikit install to wrong folder in kicad 8
Created: 2024-03-07T16:29:29Z
Prerequisites

 I have read FAQ
 I use KiKit at least version 1.4.0 (older version are not supported)

KiKit version
1.5.0
KiCAD version
8.0
Operating system
windows 11
Description
when I install kikit backend according to the instructions (open kicad command prompt and type pip install kikit) kikit is installed successfully, but command kikit --help does not work, it return "operable program or batch file not found".
I found, that kikit was installed into c:\ .... \Documents\KiCad\8.0\3rdparty\Python311\Scripts, but this folder is not added to PATH of the kicad command prompt, there is only c:\ .... \Documents\KiCad\8.0\3rdparty\Python39\Scripts. Quickfix is to duplicate the Python311 folder and rename it to Python39. Another, cleaner solution is to add c:\ .... \Documents\KiCad\8.0\3rdparty\Python311\Scripts to the system PATH, it will be reflected also in kicad command prompt after closing it and opening it again.
It would be nice to install kikit into the correct folder or to add note into the documentation, that this problem could occur. It took for me a while to figure out, what is going on.
Steps to Reproduce

install kikit via KiCad8 command prompt
try to run kikit --help
add  c:\ .... \Documents\KiCad\8.0\3rdparty\Python311\Scripts into system PATH and try again

Closing comment (2024-03-07T16:47:50Z): This is a duplicate of #647 and #653.
Repository: yaqwsx/KiKit

Issue #736: kikit 1.6.0 doesn't work with kicad 8.0.4 and 8.0.5, needs numPy 2.0 instaed of 1.26.4
Created: 2024-09-15T21:54:28Z
Prerequisites

 I have read FAQ
 I have searched existing issues (including closed ones)
 I use KiKit at least version 1.6.0 (older version are not supported)

KiKit version
A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.1 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
KiCAD version
8.0.5
Operating system
Windows 11
Description
last functioning kicad version was 8.0.3, with the later versions kikat doesn't work because of older numPy version 1.26.4, needs v2.0
Steps to Reproduce
install of kicad 8.0.4 or 8.0.5. Uninstall kikat and reinstall doesn't fix the issue.

Duplicate issue #765: Cannot install KiKit on v8.06 under win 10
Created: 2024-11-16T23:38:20Z
Prerequisites

 I have read FAQ
 I have searched existing issues (including closed ones)
 I use KiKit at least version 1.6.0 (older version are not supported)

KiKit version
Cannot install KiKit
KiCAD version
Application: KiCad x64 on x64  Version: 8.0.6-82-ge7779d9b91, release build  Libraries: 	wxWidgets 3.2.6 	FreeType 2.13.3 	HarfBuzz 10.0.1 	FontConfig 2.15.0 	libcurl/8.10.1-DEV Schannel zlib/1.3.1  Platform: Windows 10 (build 19045), 64-bit edition, 64 bit, Little endian, wxMSW  Build Info: 	Date: Nov 14 2024 04:22:13 	wxWidgets: 3.2.6 (wchar_t,wx containers) 	Boost: 1.86.0 	OCC: 7.8.1 	Curl: 8.10.1-DEV 	ngspice: 43 	Compiler: Visual C++ 1939 without C++ ABI  Build settings:
Operating system
Windows 10 (uptodate)
Description
I installed KiCAD v8.06 and installed kikit via PCM then when I tried to run the PCB editor I go the prompt to install kikit via the Kicad command prompt as usual.
I entered the command "pip install kikit" which appeared to be succesful and then tried to run "kikit --help" and got the following output
File
"C:\Users\Bob\Documents\KiCad\8.0\3rdparty\Python311\site-packages\kikit\common.py",
line 13, in 
from shapely.geometry import LinearRing
File
"C:\Users\Bob\Documents\KiCad\8.0\3rdparty\Python311\site-packages\shapely_init_.py",
line 13, in 
from shapely.lib import GEOSException  # NOQA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ImportError: numpy.core.multiarray failed to import
C:\Users\Bob\Documents\KiCad\8.0>
Steps to Reproduce
Install KiCAD v8.06
Install KiKit via PCM
Start PCBNEW and get prompt to install "backend"
Install "Backend" per instructions on supplied link
Try to run KiKit --help

Closing comment (2024-11-17T09:20:27Z): This is a duplicate of #736, #720, #761 and #764. KiCAD 8.0.6 update a major dependency without updating transitive dependencies. The fix is to run pip install kikit --force-reinstall. Pip will freshly resolve the dependency tree and KiKit should work again.
Repository: yaqwsx/KiKit

Issue #338: Doesn't work on bare metal Fedora 35, possibly dependency issue
Created: 2022-03-29T00:12:15Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.0 (older version are not supported)

KiKit version
kikit, version 1.0.3+15.g1155a2d
KiCAD version
6.0.4-1.fc35
Operating system
Fedora 35
Description
When I pip install kikit then try to run it, I get this:
Maybe my version of click is too new?
[alex@leftylinux JST-XH breakouts]$ kikit
Traceback (most recent call last):
  File "/home/alex/.local/bin/kikit", line 5, in <module>
    from kikit.ui import cli
  File "/home/alex/.local/lib/python3.10/site-packages/kikit/ui.py", line 2, in <module>
    from kikit import (panelize_ui, export_ui, present_ui, stencil_ui,
  File "/home/alex/.local/lib/python3.10/site-packages/kikit/panelize_ui.py", line 148, in <module>
    def panelize(input, output, preset, layout, source, tabs, cuts, framing,
  File "/home/alex/.local/lib/python3.10/site-packages/click/decorators.py", line 316, in decorator
    _param_memo(f, OptionClass(param_decls, **option_attrs))
  File "/home/alex/.local/lib/python3.10/site-packages/click/core.py", line 2469, in __init__
    super().__init__(param_decls, type=type, multiple=multiple, **attrs)
TypeError: Parameter.__init__() got an unexpected keyword argument 'autocompletion'

Steps to Reproduce

pip install kikit on Fedora 35
kikit

Duplicate issue #339: KiKit installation help on Win10 KiCad 6.0.2
Created: 2022-03-29T11:43:34Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.0 (older version are not supported)

KiKit version
V1.03
KiCAD version
6.0.2
Operating system
Windows10x64bit
Description
Hi,
I have installed Kikit as per the installation instructions successfully, but when checking the command kikit --version after installation getting an error as attached below:

and in Pcbnew, only the Show/hide menu is displayed.
Please help to resolve the installation.
Thanks,
Sujith
Steps to Reproduce
-NA-

Closing comment (2022-03-29T14:10:54Z): Thanks for the reply.

do I need to uninstall the current kikit installation before installing
click 8.0.0? if so what is the commando uninstall?
…
On Tue, Mar 29, 2022 at 5:35 PM Jan Mrázek ***@***.***> wrote:
 This is a duplicate of #338 <#338>.

 Yesterday, a new version of the click library was released that is no
 longer backward compatible with the feature set we use. We didn't restrict
 the library version on purpose in the order to avoid collisions with other
 installed packages. The fix was already committed but wasn't released. As a
 temporary work-around, please downgrade Click to version 8.0.0

 TLDR: before installing KiKit, install Click 8.0.0 (pip install
 click==8.0.0)

 —
 Reply to this email directly, view it on GitHub
 <#339 (comment)>, or
 unsubscribe
 <https://github.com/notifications/unsubscribe-auth/ABONSE7QNYQP36FC7X7ITSDVCLWWVANCNFSM5R6D3IWQ>
 .
 You are receiving this because you authored the thread.Message ID:
 ***@***.***>
Repository: yaqwsx/KiKit

Issue #679: Reference names rotate when creating a panel
Created: 2024-05-01T08:00:42Z
Prerequisites

 I have read FAQ
 I have searched existing issues (including closed ones)
 I use KiKit at least version 1.5.0 (older version are not supported)

KiKit version
1.5.0
KiCAD version
8.0.1
Operating system
Windows 11
Description
I\m trying to create a panel of 3 PCB's using the KiKit plugin. I've done this before successfully (in KiCad V7).
After working with the panelizer for a little while I noticed that some off the reference names have rotated.
At first I suspected that this could have been caused by me rotating the PCB's 90deg using the Layout->rotation option. But after setting this to 0 and trying again, the problem was still there with the same footprints. I have keep upright enabled for all my footprints references.
after panelizing


before panelizing


And these are just a few examples of rotated reference names.
Steps to Reproduce
I will send you the PCB through email.
This is the panelizing preset I've used.
Panelizing preset.json

Duplicate issue #683: Reference designators are wrongly rotated
Created: 2024-05-10T21:14:12Z
Prerequisites

 I have read FAQ
 I have searched existing issues (including closed ones)
 I use KiKit at least version 1.5.0 (older version are not supported)

KiKit version
kikit, version 1.5.0
KiCAD version
8.0.1
Operating system
Windows 11
Description
Sometimes reference designators are rotated differently than in the original pcb. It seems to be a newer issue.
Steps to Reproduce
Make a pcb with several reference designators on it, panalize it (with roatation) and observe wrongl rotated reference designators.

Closing comment (2024-05-12T17:50:01Z): Duplicate of #679 and #656. Already fixed in v1.5.1. Closing.
Repository: yaqwsx/KiKit

Issue #395: Hide references GUI - Apply button cannot be pressed
Created: 2022-08-16T22:36:14Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.4 (older version are not supported)

KiKit version
kikit, version 1.0.5+78.g46fb7ca
KiCAD version
6.0.6
Operating system
Win10
Description
With large boards, the apply button cannot be seen and the dialog cannot be resized.

Steps to Reproduce
Create a board with some components - my design has 3 components;
Create a panel in the GUI - my panel has 9 boards;
Click the Show/Hide Ref toolbar button.
{ "layout": { "hspace": "2mm", "vspace": "5mm", "rows": "3", "cols": "3" }, "source": { "tolerance": "100mm" }, "tabs": { "type": "fixed", "vwidth": "5mm", "hwidth": "5mm", "hcount": "0" }, "cuts": { "type": "mousebites", "spacing": "0.7mm", "offset": "-0.25mm" }, "framing": { "type": "frame", "width": "5mm", "fillet": "2mm" }, "tooling": { "type": "3hole", "hoffset": "2.5mm", "voffset": "2.5mm", "size": "1.152mm", "paste": "True" }, "text": { "type": "simple", "voffset": "2.5mm", "width": "1.2mm", "height": "1.2mm", "thickness": "0.2mm", "text": "JLCJLCJLCJLC" }, "post": { "copperfill": "True", "millradius": "1mm" } }

Duplicate issue #397: Show/hide references - lots of matches occlude buttons
Created: 2022-08-22T22:27:17Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.4 (older version are not supported)

KiKit version
1.0.5+76.gbeeb746
KiCAD version
6.0.7
Operating system
Windows
Description
This is about the Show/hide references dialog.
When there's a certain number of components on the board and their references are all matched to be shown/hidden, then the Cancel and Apply buttons are not visible:

Steps to Reproduce

Try to hide all references on a board with lots of components

Closing comment (2022-08-22T22:29:05Z): Schitt duplicate of #395
Repository: yaqwsx/KiKit

Issue #289: Panelize does not copy title block from original board
Created: 2022-01-15T00:36:04Z
I'm using KiCad v6 with KiKit v1.0.2
When using kikit panelize to create a panel of a board, the panel's kicad_pcb file does not copy over any of the page settings from the original PCB design. Of more specific concern, it does not copy over any of the text in the "title block" section of the page settings.
This is an issue because KiCad v6 now allows you to reference the title block fields in silkscreen text, and that feature is broken if those fields are not carried over.
I've started using that feature to avoid having to manually synchronize a PCB's revision and date between multiple places.

Duplicate issue #299: Text using KiCad Variables not panelized
Created: 2022-01-29T21:21:30Z
Prerequisites

 I have read FAQ
 I use the KiKit at least 1.0.0 (older version are not supported)

KiKit version
kikit, version 1.0.2
KiCAD version
Version: (6.0.1), release build
Operating system
Arch Linux
Description
Silkscreen Text items that use KiCad variables are not being duplicated in the panezilation.
I would recommend to expand those text variables in the panelization step and insert the expanded text variables in the panel *.kicad_pcb.
Steps to Reproduce
Create a Silkscreen text item with the content ${REVISION}. This will insert the Revision field from the "Page Settings"->"Title Block"->"Revision" field on the silkscreen inside of KiCad.
After panelization all those Silkscreen Text items disappear.

Closing comment (2022-01-29T22:03:53Z): This seems like a duplicate of #289. Please, try the upstream version.
Repository: yarnpkg/berry

Issue #3048: [Bug] `yarn workspaces foreach run <script-name>` prints usage error for missing script
Created: 2021-06-27T10:23:24Z
I'd be willing to implement a fix

Describe the bug
I am using yarn workspaces foreach run <script-name> to run scripts that are present in some of my workspaces, but not all of them. The documentation states:

If the command is run and the script being run does not exist the child workspace will be skipped without error.

However, I'm getting a bunch of error logs in the command output:
➤ YN0000: Usage Error: Couldn't find a script named "lint:config".
➤ YN0000:
➤ YN0000: $ yarn run [--inspect] [--inspect-brk] <scriptName> ...

Granted, the command succeeds without error, but this output seems unintended to me.
Edit: it actually fails with code 1.
To Reproduce
Sorry, the codesandbox is crashing, so I can't provide a repro there. Basically you need:

a monorepo with at least 2 packages
yarn 3.0.0-rc.6 with the workspaces plugin
define a package.json script in one of the packages, but not the other
run yarn workspaces foreach run <script-name>

Screenshots
If applicable, add screenshots to help explain your problem.
Environment if relevant (please complete the following information):

OS: Windows
Node version 16.2.0
Yarn version 3.0.0-rc.6

Additional context
Add any other context about the problem here.

Duplicate issue #3292: [Bug?]: `yarn workspaces foreach run` doesn't ignore scripts that contain colons
Created: 2021-08-14T05:12:40Z
Self-service

 I'd be willing to implement a fix

Describe the bug
With the following workspaces:

packages/a contains foo:bar and foo scripts
packages/b has no script

Running yarn workspaces foreach --verbose run foo:bar via a root script fails (it does not ignore b):
[ldiqual@ldiqual-mbp-siteline yarn-foreach]$ yarn foo:bar
➤ YN0000: [a-1a2bd2]: Process started
➤ YN0000: [a-1a2bd2]: foo:bar
➤ YN0000: [a-1a2bd2]: Process exited (exit code 0), completed in 0s 45ms

➤ YN0000: [b-c0f23f]: Process started
➤ YN0000: [b-c0f23f]: Usage Error: Couldn't find a script named "foo:bar".
➤ YN0000: [b-c0f23f]:
➤ YN0000: [b-c0f23f]: $ yarn run [--inspect] [--inspect-brk] <scriptName> ...
➤ YN0000: [b-c0f23f]: Process exited (exit code 1), completed in 0s 14ms
➤ YN0000: Done in 0s 66ms

While running yarn workspaces foreach --verbose run foo via a root script properly ignores the b workspace:
[ldiqual@ldiqual-mbp-siteline yarn-foreach]$ yarn foo
➤ YN0000: [a-1a2bd2]: Process started
➤ YN0000: [a-1a2bd2]: foo
➤ YN0000: [a-1a2bd2]: Process exited (exit code 0), completed in 0s 43ms
➤ YN0000: Done in 0s 47ms

To reproduce
Run yarn foo:bar and yarn foo in this project:
yarn-foreach.zip
Environment
System:
OS: macOS 11.2.3
CPU: (8) x64 Intel(R) Core(TM) i7-8557U CPU @ 1.70GHz
Binaries:
Node: 14.17.5 - /private/var/folders/hr/v4vtphl130zczzkbpdkbs7qm0000gn/T/xfs-9e2b9f09/node
Yarn: 3.0.0 - /private/var/folders/hr/v4vtphl130zczzkbpdkbs7qm0000gn/T/xfs-9e2b9f09/yarn
npm: 6.14.14 - ~/.nvm/versions/node/v14.17.5/bin/npm
Additional context
No response

Closing comment (2021-08-14T08:13:31Z): Duplicate of #3048
Repository: yarnpkg/berry

Issue #650: [Case Study] Exports Support
Created: 2019-12-26T23:47:56Z
I'd be willing to implement a fix

Describe the bug
See:

proposal-pkg-exports
Node 13 Documentation

Node ^12.7.0 with the --experimental-modules flag and Node ^13.0.0 without the flag resolves modules differently than Yarn@2.0.0-rc19 with PNP
To Reproduce
See this project:
https://github.com/sparebytes/yarn2-pnp-exports-example
// packages/package-with-exports/package.json
{
    "name": "package-with-exports",
    "version": "1.0.0",
    "exports": {
        ".": "./main.js",
        "./sub/other": "./other.js"
    }
}

// Example 1
// Expected: packages/package-with-exports/main.js
// Actual: packages/package-with-exports/index.js
require("package-with-exports");

// Example 2
// Expected: packages/package-with-exports/other.js
// Actual: throws error
require("package-with-exports/sub/other");

Environment

OS: Windows
Node version ^12.7.0
Yarn version 2.0.0-rc19

Duplicate issue #1277: [Case Study] support for exports in package.json
Created: 2020-04-30T19:11:06Z
Hi.
Seems, that yarn don't support "exports" in package.json.
Is it true or i am doing something wrong?
Do you have plans to support them?

Closing comment (2020-06-09T12:49:08Z): Tracked in #650.
Repository: yarnpkg/berry

Issue #1177: [Feature] Return "engines" check
Created: 2020-04-09T11:58:55Z
I'd be willing to implement this feature
 This feature can already be implemented through a plugin

Describe the user story
Simple: I want to pin my node version (and, may be, in future - yarn version) via engines entry in package.json or, may be, in .yarnrc.yml
For example, deps builds are broken at node 12, but on node 10 all is OK. I want to ensure what every who try to start my project cannot use node 12.
Describe the solution you'd like
Just restore old behavior from 1.x, maybe as a (optional) plugin.
Describe the drawbacks of your solution
IDK.
Describe alternatives you've considered
IDK
Additional context
IDK

Duplicate issue #4345: [Bug]: Engines section not respected
Created: 2022-04-11T21:30:27Z
Self-service

 I'd be willing to implement a fix

Describe the bug
We have an engine section in our packages. It stopped working when updating to Yarn 3.x (from 1.x)
To reproduce
We have this in our package.json
  "engines": {
    "node": ">=14.0",
    "yarn": ">=1.19"
  },

Environment
Windows 11
Node 16.14.2
Additional context
No response

Closing comment (2022-04-12T10:29:29Z): Duplicate of #1177
Repository: yarnpkg/berry

Issue #638: 🎯 ESM Support for PnP
Created: 2019-12-17T00:06:04Z
Edit 2021-04-14 by @arcanis: In case you reach this thread by Twitter, ESM for PnP is on our roadmap. It's tricky due to some primitives currently missing in Node (they're working on this, but as you can see it's still branded as experimental), in the meantime if you need it then the node-modules linker remain a perfectly fine solution. In any case, help is appreciated, Twitter rants less.


What package is covered by this investigations?```
@softvisio/cli
Describe the goal of the investigation
I am trying to run script, that uses es6 syntax.
yarn add @softvisio/cli
yarn softvisio-cli

But get this error:
(node:4268) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
d:\downloads\yarn\@softvisio-cli-npm-0.1.0-efe3491d08-1.zip\node_modules\@softvisio\cli\bin\cli.js:3
import softvisioCliApi from "../lib/api.js";
^^^^^^

I am using node 13 that can load es6 modules directly.
Is it currently possible to use pure es6 modules with yarn 2 or I need to compile them to commonjs before?

Duplicate issue #1760: [Bug] PnP cannot find ava
Created: 2020-08-24T20:29:35Z
I'd be willing to implement a fix

Describe the bug
Using yarn's PnP feature with AVA test tool results in strange ava not found when I try to import it. But it does say did you mean ava-npm-3.11.1.... I've also tried using yarn pnpify ava but it's the same issue.
$ yarn run test      // "test": "ava"
Uncaught exception in test/database.spec.mjs

  Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'ava' imported from /project/test/database.spec.mjs
  Did you mean to import ava-npm-3.11.1-eda34ac446-282cb94428.zip/node_modules/ava/index.js?

  › Did you mean to import ava-npm-3.11.1-eda34ac446-282cb94428.zip/node_modules/ava/index.js?
  › packageResolve (internal/modules/esm/resolve.js:620:9)
  › moduleResolve (internal/modules/esm/resolve.js:659:14)
  › Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:752:11)
  › Loader.resolve (internal/modules/esm/loader.js:97:40)
  › Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
  › ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:50:40)
  › link (internal/modules/esm/module_job.js:49:36)
To Reproduce

  database.spec.mjs
import test from "ava";
import {resolve, basename} from "path";

import {Database} from "../lib/database.ts";

const db = new Database();

test("create user", async (t) => {
const info = {
  firstName: "foo",
  lastName: "bar"
}
db.newUser(info);
});


  Package.json AVA settings
"ava": {
  "require": [
    "ts-node/register"
  ],
  "babel": true,
  "files": [
    "test/**.spec.js",
    "test/**.spec.mjs"
  ]
}

Environment if relevant (please complete the following information):

OS: Linux 5.8.3-arch1-1 #1 SMP PREEMPT Fri, 21 Aug 2020 16:54:16 +0000 x86_64 GNU/Linu
Node version: v14.4.0
Yarn version: 2.1.1
Typescript version: 4.0.2

Closing comment (2020-08-24T20:36:32Z): Probably a duplicate of #638
Repository: yarnpkg/berry

Issue #2500: [Bug] Some packages aren't hoisted as far as possible (because of peer deps?)
Created: 2021-02-22T11:51:39Z
I'd be willing to implement a fix

Describe the bug
Some packages aren't hoisted completely as high as they could be.
To Reproduce
{
  "devDependencies": {
    "parcel": "2.0.0-nightly.605"
  }
}

After installing, there are two instance of @parcel/fs (both have the same version):
node_modules/@parcel/fs
node_modules/@parcel/core/node_modules/@parcel/fs


  Reproduction
// Sherlock reproduction. For instance:
await packageJsonAndInstall({
  dependencies: {
    [`parcel`]: `2.0.0-nightly.605`,
  },
});

Environment if relevant (please complete the following information):

OS: macOS 10.15.5
Node version v15.9.0
Yarn version 2.4.0

Additional context
(parcel-bundler/parcel#4064)

Duplicate issue #2962: [Bug] nodeLinker node-modules not deduplicating Parcel v2 dependencies
Created: 2021-06-01T02:19:44Z
I'd be willing to implement a fix

Describe the bug
As mentioned in #1049 parcel relies on instantiating modules once only:
import {register} from "@parcel/core";
class X {}
register("X", X);
When installing parcel with nodeLinker: node-modules in yarn v2, the dependencies of parcel are not deduplicated and hoisted such that there are multiple versions of them. A simplified node_modules file tree demonstrating @parcel/fs, @parcel/package-manager not deduplicated is as follows:
node_modules
    | - parcel                           (parcel@2.0.0-beta.2)
    | - @parcel
        | - core                         (@parcel/core@2.0.0-beta.2)
        |   | - node_modules
        |       | - @parcel
        |           | - fs               (@parcel/fs@2.0.0-beta.2)
        |           | - package-manager  (@parcel/package-manager@2.0.0-beta.2)
        | - fs                           (@parcel/fs@2.0.0-beta.2)
        | - package-manager              (@parcel/package-manager@2.0.0-beta.2)

When installing parcel in yarn v1, the deduplicating works, and the @parcel/XXX deps are hoisted to the highest level.
To Reproduce
Here is a sample repo containing parcel v2 that could be bootstrapped when installed with yarn v1 but not yarn v2. More details are available at the repo's readme.

  Reproduction
$ git clone https://github.com/lokshunhung/yarn2-parcel-dedupe-repro.git
$ cd yarn2-parcel-dedupe-repro
$ node ./run-yarn-why.js
$ cd using-yarn2/packages/parcel-app
$ yarn start  # throws error
$ cd ../../../
$ cd using-yarn1/packages/parcel-app
$ yarn start  # works

Screenshots
N/A
Environment if relevant (please complete the following information):

OS: OSX 11.3.1
Node version: 15.12.0
Yarn version: 2.4.1

Additional context
N/A

Closing comment (2021-06-01T05:23:37Z): Duplicate of #2500, already fixed in master
Repository: yarnpkg/berry

Issue #1231: [Feature] generate other editor configs using pnpify --sdk
Created: 2020-04-21T20:22:15Z
I'd be willing to implement this feature
 This feature can already be implemented through a plugin

Describe the user story
Setting up PnP support for coc.nvim as documented on https://yarnpkg.com/advanced/editor-sdks currently requires manually creating a config file after the yarn pnpify --sdk step.
Describe the solution you'd like
The sdk option could take an argument telling it what to generate the sdk for, e.g. --sdk={vscode,coc.nvim,...}.
Describe the drawbacks of your solution
Potential feature creep by supporting every editor in existence.
Describe alternatives you've considered
Plain --sdk could just generate them all. Would unfortunately create lots of unneeded files in the repo. Although current --sdk already generates .vscode even for non VSCode users 🤷
Additional context
From #170 (comment)

Duplicate issue #1441: [Feature] Configure coc.nvim plugins with pnpify --sdk
Created: 2020-06-04T19:34:39Z
I'd be willing to implement this feature
 This feature can already be implemented through a plugin

Describe the user story
For vscode users yarn dlx @yarnpkg/pnpify --sdk will create a .vscode/settings.json extension configuration for eslint,prettier,etc. compatible with pnp. coc.nvim uses .vim/coc-settings.json as it's configuration file and has many plugins which can be configured in a similar manner.
Describe the solution you'd like
Automatically generate .vim/coc-configuration.json for coc.nvim users based on the same rules used to generate it for vscode.
Describe the drawbacks of your solution
Not all developers use coc.nvim and not all developers use vscode. The sdk could be extended with additional configuration parameters to decide whether or not it should generate an IDE configuration. E.g. yarn dlx @yarnpkg/pnpify --sdk --vscode-settings --coc-settings.
Describe alternatives you've considered
Manual configuration of .vim/coc-settings.json following documented instructions, but it's a bit tedious.
Additional context
https://yarnpkg.com/advanced/editor-sdks

Closing comment (2020-06-04T20:41:42Z): Duplicate of #1231 but you ticked the first box so we can leave it open 😄
It's a good idea. The way I could see it work:

On new projects, yarn dlx @yarnpkg/pnpify --sdk will just create the vscode SDK
Additional SDKs can be added with yarn dlx @yarnpkg/pnpify --sdk=vim|atom|...
Running yarn dlx @yarnpkg/pnpify --sdk will update all the existing SDKs if found

This way we keep the current behavior by default (which I think makes sense, VSCode is the most popular editor by far right now), but still provide a way for users to add their own at little maintenance costs. Even infra teams just have a single command to run to update all the SDKs at once.
Repository: yarnpkg/berry

Issue #4157: [Bug?]: Timeouts when using PnP with ESM on Node <=16.14
Created: 2022-02-24T23:33:40Z
Self-service

 I'd be willing to implement a fix

Describe the bug
Running jest tests in CI always timeout (10 minutes) with yarn 3.2.0, running with 3.1.1 and earlier versions it finishes in less than 10 seconds.
To reproduce
yarn jest
Environment
CircleCI 2.1
Additional context
No response

Duplicate issue #4203: [Bug] yarn 3.2.0 - jest suite hangs
Created: 2022-03-09T16:29:21Z
Self-service

 I'd be willing to implement a fix

Describe the bug
After upgrading 3.1.1 to 3.2.2 jest tests started to hang without any output, when tests are run individually they all pass, when I run yarn jest -c ./path/to/my/jest.config.js it hangs.
To reproduce
It's a private repo hard to reproduce, so I'm not able to reproduce easily
Environment
System:
    OS: macOS 12.1
    CPU: (8) x64 Apple M1 Pro
  Binaries:
    Node: 14.15.5 
    Yarn: 3.2.0
    npm: 8.3.2
Additional context
It's a yarn workspaces monorepo

Closing comment (2022-03-09T16:36:20Z): Duplicate of #4157