You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Constantly have to pull character skills for every fit and on each startup. #2806
Since the last update, pyfa is not loading stored character skills.
Here I have a cruor and a magus open. You can see that I apparently cannot fly either, even though I can. I've had no issues with this before. These fits were fine as of just moments ago.
Here I hit to refresh skills on the cruor fit, and it's back to having properly loaded skills:
Here is the magus fit after having done this - still doesn't fit:
And here it is after I refresh skills on the magus tab:
After loading skills, I open a new unopened fit that presumably hasn't loaded the local old skill profile, and everything is fine:
So either the local skill profiles are not loading correctly, or they are not being saved.
Additionally - doing a character skills refresh should update all open fits that are using that profile.
Same issue. There's a successful pull from EVE sso to permanently load skills, and pyfa gives me an error.
I constantly have to scroll to bottom of character selection and select "open character editor" or whatever it is, select the character - "get skills" from tranquility.
I analyzed the saveddata.db file in %USERPROFILE%\.pyfa\ and completely reset the database to rule out any corruption or legacy data.
After starting Pyfa with a fresh database, I added a character and successfully pulled its skills from ESI.
However, after quitting Pyfa and checking the database again, I found the following:
In the characters table, the newly added character is present, with ID 3.
In the characterSkills table, there are only entries for character IDs 1 and 2, which are the default All5 and All0 characters.
There are no characterSkills entries at all for character ID 3.
So it appears that Pyfa successfully retrieves the character's skills from ESI, but never writes those skills to the characterSkills table.
This also explains why the skills have to be pulled again after changing characters or restarting Pyfa: the character itself is persisted, but its skill profile is not.
I will try to make another release with this bug fixed shortly. But, as part of that release, I also want to move pyfa CI from appveyor to github actions, to support Apple Silicon, so it will take a few days at least. If you need an early version, it will be available here once commit with the fix is built: https://ci.appveyor.com/project/pyfa-org/pyfa/builds/54852636 (artifacts tab, but there is 1GB daily download limit there).
Additionally - doing a character skills refresh should update all open fits that are using that profile.
What do you have to do to update them?
As far as I understand, it might need you to open appropriate tab of every fit involved in graph window. This applies to any indirect change. However, it sounds like this case is different.
5. > Additionally - doing a character skills refresh should update all open fits that are using that profile.
What do you have to do to update them?
As far as I understand, it might need you to open appropriate tab of every fit involved in graph window. This applies to any indirect change. However, it sounds like this case is different.
Yes the main issue is fixed, thank you.
To clarify what I meant - re-pulling skills in one tab updated that tab, however clicking in to another tab with the same character showed the old skills. This indicated that when a skill pull was done, only that tab was aware. The act of clicking in to a tab should run a skill check to see if it's using out of date skills and update them, presuming a skill in question is not currently being tested at some other custom level.
Activity
2Bad4Ux2 commentedon Oct 3, 2026
Same issue. There's a successful pull from EVE sso to permanently load skills, and pyfa gives me an error.
I constantly have to scroll to bottom of character selection and select "open character editor" or whatever it is, select the character - "get skills" from tranquility.
Marzhin971 commentedon Oct 7, 2026
Same problem here.
I analyzed the
saveddata.dbfile in%USERPROFILE%\.pyfa\and completely reset the database to rule out any corruption or legacy data.After starting Pyfa with a fresh database, I added a character and successfully pulled its skills from ESI.
However, after quitting Pyfa and checking the database again, I found the following:
characterstable, the newly added character is present, with ID3.characterSkillstable, there are only entries for character IDs1and2, which are the defaultAll5andAll0characters.characterSkillsentries at all for character ID3.So it appears that Pyfa successfully retrieves the character's skills from ESI, but never writes those skills to the
characterSkillstable.This also explains why the skills have to be pulled again after changing characters or restarting Pyfa: the character itself is persisted, but its skill profile is not.
DarkFenX commentedon Oct 7, 2026
I will look into it before making next release. It's either new dependencies, or ESI endpoint changes I completely overlooked.
edit: just reproduced it. Seems like it is caused by SQLAlchemy migration
DarkFenX commentedon Oct 7, 2026
Fixed in 16313f2.
I will try to make another release with this bug fixed shortly. But, as part of that release, I also want to move pyfa CI from appveyor to github actions, to support Apple Silicon, so it will take a few days at least. If you need an early version, it will be available here once commit with the fix is built: https://ci.appveyor.com/project/pyfa-org/pyfa/builds/54852636 (artifacts tab, but there is 1GB daily download limit there).
DarkFenX commentedon Oct 7, 2026
What do you have to do to update them?
As far as I understand, it might need you to open appropriate tab of every fit involved in graph window. This applies to any indirect change. However, it sounds like this case is different.
DarkFenX commentedon Oct 8, 2026
Should be fixed in the release I will publish today
theelous3 commentedon Oct 10, 2026