-
Notifications
You must be signed in to change notification settings - Fork 355
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
Master start ff earlier #5181
Master start ff earlier #5181
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you!
/build-image --live |
Images built based on commit 99f06cd:
Download the images from the bottom of the job status page. |
@KKoukiou I have to focus on other things, so if you want and have time please feel free to finish this PR. The backend solution should be ready we just need to found a way to avoid having white screen in FF before Anaconda backend is ready. |
def _run_webui(self): | ||
# FIXME: This part should be start event loop (could use the WatchProcesses class) | ||
# FIXME: We probably want to move this to early execution similar to what we have on live | ||
profile_name = FIREFOX_THEME_DEFAULT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The live vs boot.iso need different firefox theming. This is not a desired change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is just code move. This code should be started only on boot.iso not on live so the theme here is correct. The other theme is specified in liveinst
script because there is a place where the script is started.
/build-image --live |
Images built based on commit 99f06cd:
Download the images from the bottom of the job status page. |
99f06cd
to
76d9f3e
Compare
Hello @jkonecny12! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2024-01-22 14:43:52 UTC |
Here is a screencast on the current behavior: AwesomeScreenshot-10_16_2023.7.10.28PM.mp4 |
76d9f3e
to
e4a1d7b
Compare
Updated with a new solution of a flag file signalizing that backend is ready to be consumed after Anaconda is initialized. Web UI code was removed because it's in different repository now. @KKoukiou could you please help me there and link a PR here? The Web UI needs to wait until |
/kickstart-test --testtype smoke |
/packit build |
1 similar comment
/packit build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
e4a1d7b
to
929bf95
Compare
929bf95
to
6b202f5
Compare
Verified together with rhinstaller/anaconda-webui#132 and on a spin (KDE Live). Everything seems to be working fine with the current code. |
/packit build |
/kickstart-test --testtype smoke |
Screecast Based on my measuring it seems to be faster almost by 50%. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
# Force the X11 backend since sudo and wayland do not mix | ||
export GDK_BACKEND=x11 | ||
|
||
if [ -x /usr/bin/udisks ]; then | ||
/usr/bin/udisks --inhibit -- "$ANACONDA" "$@" | ||
/usr/bin/udisks --inhibit -- start_anaconda "$@" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to do the additional set up while inhibiting some of the udisks operations? I am not sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the testing it should be fine. Also we inhibit the udisks for the whole Anaconda run if I'm reading this correctly which included start of the Firefox even before.
@vojtechtrefny do you have some recommendation for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This must be a very ancient check -- /usr/bin/udisks
doesn't exists in udisks2, the old udisks package is still available in Fedora, but nobody is using it anymore (udisks 2.0 has been released 11 years ago). I think this can be safely removed.
CC @tbzatek
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well the surrounding check evaluates to FALSE anyway and was for some time already. So this can be safely removed.
If you still want to keep the inhibit, you need to to that via D-Bus call to UDisks (2). Unless you want to suspend the system in the middle of installation, I wouldn't worry about that much.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heh, ok. In that case let's remove it in separate PR because it doesn't seem related to this. Thanks for info.
And I don't think we need that inhibit, it seems it works fine now so we probably don't need that...
/packit build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
The execution time between Gnome Initial Setup and Anaconda is quite big we need to reduce it by moving FF execution sooner before Anaconda is executed. Time to show Firefox window based on my measurements on VM with 2GB RAM and 4vCPUs: Original execution time: 13 seconds With this commit: less than 6 seconds If we want to reduce this time even more we need to do that in Firefox or Gnome Shell (Gnome Initial Setup environment) somehow. Resolves: rhbz#2236438
Currently Anaconda doesn't have DBus API to signalize that backend is ready to be consumed (initialized). For this reason Web UI don't know when it can access the Web UI. For this reason let's introduce a new flag file which is a signal for Web UI that loading screen could be closed and Anaconda is ready to be used. Resolves: rhbz#2236438
6b202f5
to
bde33e7
Compare
Rebased. |
/kickstart-test --testtype smoke |
Broken test is caused by COPR repository containing older a newer builds. 40.8 and 40.17 and trying to install both versions. Could be probably resolved by removing old builds. |
I'm not able to resolve it because I don't have permission to remove the old builds. Merging anyway - not related to change. |
The execution time between Gnome Initial Setup and Anaconda is quite big
we need to reduce it by moving FF execution sooner before Anaconda is
executed.
Time to show Firefox window based on my measurements on VM with 2GB RAM
and 4vCPUs:
Original execution time: 13 seconds
With this commit: less than 6 seconds
If we want to reduce this time even more we need to do that in Firefox
or Gnome Shell (Gnome Initial Setup environment) somehow.
TODO:
[ ] Add event loop also to originalwebui-desktop
script execution code?This part is a question because I think we could have an issue without any event loop running but so far there are no complains about that...Resolves: rhbz#2236438