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

[LW-10649] Fix installing & running with strict AppArmor #3207

Merged
merged 9 commits into from
Aug 5, 2024

Conversation

michalrus
Copy link
Member

@michalrus michalrus commented Jun 27, 2024

LW-10649

… by removing the nix-chroot.

The issue manifested on Ubuntu 24.04 LTS

Todos

n/a

Screenshots

n/a

Testing Checklist


Review Checklist

Basics

  • PR assigned to the PR author(s)
  • input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
  • If there are UI changes, Alexander Rukin assigned as an additional reviewer
  • PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
  • PR link is added to a Jira ticket, ticket moved to In Review
  • PR is updated to the most recent version of the target branch (and there are no conflicts)
  • PR has a good description that summarizes all changes
  • PR contains screenshots (in case of UI changes)
  • CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
  • There are no missing translations (running yarn manage:translations produces no changes)
  • Text changes are proofread and approved (Jane Wild / Amy Reeve)
  • Japanese text changes are proofread and approved (Junko Oda)
  • Storybook works and no stories are broken (yarn storybook)
  • In case of dependency changes yarn.lock file is updated

Code Quality

  • Important parts of the code are properly commented and documented
  • Code is properly typed with typescript types
  • React components are split-up enough to avoid unnecessary re-renderings
  • Any code that only works in main process is neatly separated from components

Testing

  • New feature/change is covered by acceptance tests
  • New feature/change is manually tested and approved by QA team
  • All existing acceptance tests are still up-to-date
  • New feature/change is covered by Daedalus Testing scenario
  • All existing Daedalus Testing scenarios are still up-to-date

After Review

  • Update Slack QA thread by marking it with a green checkmark

@michalrus michalrus force-pushed the chore/LW-10649-no-nix-chroot branch from eb373c4 to 4b5094d Compare July 5, 2024 10:15
@michalrus michalrus force-pushed the chore/LW-10649-no-nix-chroot branch from ab11aef to fa13182 Compare July 10, 2024 09:17
@michalrus michalrus requested review from a team July 10, 2024 13:26
Copy link
Contributor

@danielmain danielmain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do not need to comment out the old safeExitWithCode, I see you handle exits correctly.

source/main/utils/buildAppMenus.ts Outdated Show resolved Hide resolved
@michalrus michalrus merged commit 912bfe5 into develop Aug 5, 2024
3 of 4 checks passed
@michalrus michalrus deleted the chore/LW-10649-no-nix-chroot branch August 5, 2024 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants