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

Warning and Error layer ordering on nodes went wrong #6874

Closed
2 tasks
xvcgreg opened this issue May 29, 2023 · 6 comments · Fixed by #6882
Closed
2 tasks

Warning and Error layer ordering on nodes went wrong #6874

xvcgreg opened this issue May 29, 2023 · 6 comments · Fixed by #6882
Assignees
Labels
--bug Type: bug --regression Important: regression

Comments

@xvcgreg
Copy link

xvcgreg commented May 29, 2023

Discord username

No response

What type of issue is this?

Permanent – Occurring repeatably

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

Layers got messed up:
image

Expected behaviour

node marked properly, like so:
image

How we can reproduce it?

No response

Screenshots or screencasts

No response

Logs

No response

Enso Version

2023.5.29 nightly

Browser or standalone distribution

Standalone distribution (local project)

Browser Version or standalone distribution

standalone

Operating System

Windows

Operating System Version

Win11pro 22H2 22621.1555

Hardware you are using

12th Gen Intel(R) Core(TM) i9-12900HK / RTX3060 Laptop / Nvidia Drivers 531.68

@hubertp
Copy link
Collaborator

hubertp commented May 29, 2023

Screenshot from 2023-05-29 18-37-01

This appears to be a rather serious regression

@hubertp
Copy link
Collaborator

hubertp commented May 29, 2023

Regression introduced in #6595 @wdanilo

@wdanilo
Copy link
Member

wdanilo commented May 29, 2023

Oh wow, why I haven't seen it and why this code breaks it... it should not touch it. Anyway, I'm taking a look right now

@wdanilo
Copy link
Member

wdanilo commented May 29, 2023

Ok, I carefully reviewed all the code in my PR and it's not even close any shapes drawing or ordering, so why it is causing such problems is a big surprise to me. Investigation in progress ...

@wdanilo wdanilo mentioned this issue May 30, 2023
5 tasks
@wdanilo
Copy link
Member

wdanilo commented May 30, 2023

@hubertp @xvcgreg I can't repro it. It just works fine on my end. However, I noticed that we are not defining the ordering of layers there explicitly, which makes the order undefined. It means, that there is a possibility that on some build configurations this order will be different. This is bad and we need to fix such places. Anyway, I created a PR with the fix, @hubertp could you please confirm it works on your end? #6882

@hubertp
Copy link
Collaborator

hubertp commented May 30, 2023

That worked, yes. I got this on the nightly as well, not only on my local build.

@hubertp hubertp moved this from ❓New to 👁️ Code review in Issues Board May 30, 2023
@hubertp hubertp removed the triage label May 30, 2023
@mergify mergify bot closed this as completed in #6882 May 30, 2023
mergify bot pushed a commit that referenced this issue May 30, 2023
This might fix #6874 . I can't reproduce the issue, but I understand why it might happen, as the ordering was not defined explicitly.
@github-project-automation github-project-automation bot moved this from 👁️ Code review to 🟢 Accepted in Issues Board May 30, 2023
@farmaazon farmaazon moved this from 🟢 Accepted to 🗄️ Archived in Issues Board Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug --regression Important: regression
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants