Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pcell do not work for 0.27.6 on REDHAT7 CentOS7 #969

Closed
YiLvErZhaoSanDianwei opened this issue Jan 12, 2022 · 9 comments · Fixed by #970
Closed

Pcell do not work for 0.27.6 on REDHAT7 CentOS7 #969

YiLvErZhaoSanDianwei opened this issue Jan 12, 2022 · 9 comments · Fixed by #970
Assignees
Labels
Milestone

Comments

@YiLvErZhaoSanDianwei
Copy link

Dear @klayoutmatthias,

My Pcell code can work for version 0.27.5 on REDHAT7 CentOS7 linux system, however for version 0.27.6, I got following error:
maximumrecursion depth exceeded while calling a Python object in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in
PCellDeclaration_Native.wants_lazy_evaluation in
PCellDeclaretion.wants_lazy_evaluation in

@lukasc-ubc
Copy link

lukasc-ubc commented Jan 12, 2022 via email

@RomainAlbert
Copy link

And I get the same error under windows.

@klayoutmatthias
Copy link
Collaborator

I'm sorry, something is broken here on 0.27.6.

Please use 0.27.5 until I have fixed this issue.

Apologies for this inconvenience.

Best regards,

Matthias

@klayoutmatthias klayoutmatthias self-assigned this Jan 12, 2022
@klayoutmatthias klayoutmatthias added this to the 0.27.7 milestone Jan 12, 2022
@Kazzz-S
Copy link
Contributor

Kazzz-S commented Jan 12, 2022

Dear @klayoutmatthias,

My PCells are all in Ruby and 0.27.6 (Windows, Linux, and Mac) crashed when it just started, opened a new design, or an existing PCell design.

I have (1) reimplemented wants_lazy_evaluation() method. Then, when I have (2) incidentally remade the klayoutrc file,
things went well on the three different platforms.
Now I get the following warnings on Mac:

Warning: QLayout: Attempting to add QLayout "" to QFrame "", which already has a layout
Warning: Populating font family aliases took 210 ms. Replace uses of missing font family "Sans Serif" with one that exists to avoid this cost. 
Warning: QLayout: Attempting to add QLayout "" to QFrame "", which already has a layout

Just for your information.

I'll rebuild DMGs if you release the next maintenance release 0.27.7 :-)

Thank you and best regards,
Kazzz-S

@klayoutmatthias
Copy link
Collaborator

I fixed the two QLayout Qt warnigns as well - thanks for reporting.

But you mean, you cannot load a GDS file with 0.26.7 which you have written with 0.27.6? Or is that a typo and you wanted to write "0.27.6"?

Thanks and best regards,

Matthias

@klayoutmatthias klayoutmatthias linked a pull request Jan 12, 2022 that will close this issue
@Kazzz-S
Copy link
Contributor

Kazzz-S commented Jan 12, 2022

I fixed the two QLayout Qt warnigns as well - thanks for reporting.

But you mean, you cannot load a GDS file with 0.26.7 which you have written with 0.27.6? Or is that a typo and you wanted to write "0.27.6"?

Sorry, just a silly typo ;-(

Kazzz-S

@klayoutmatthias
Copy link
Collaborator

Very good ... I understand better now :)

I'll publish the new release tomorrow with this fix.

Again, sorry for the inconvenience.

Best regards,

Matthias

@klayoutmatthias
Copy link
Collaborator

I have released version 0.27.7 which should fix this bug

@klayoutmatthias
Copy link
Collaborator

I'll close this issue as 0.27.7 should fix this problem now.

Thanks for reporting!

Matthias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants