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
Hi, i am trying CPM and i have an issue where the second time i run generate step CPM tries to patch already patched packages again. I tracked the issue down to CPM_PACKAGES being unconditionally reset here. This clearly seems wrong, as i understand we clearly want to maintain value of CPM_PACKAGES between generate runs. However, since you have it there this way for four years it must work somehow... Can someone explain how this but is supposed to not reset cached CPM_PACKAGES value every time? Maybe i am missing something in my project configuration?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, i am trying CPM and i have an issue where the second time i run generate step CPM tries to patch already patched packages again. I tracked the issue down to
CPM_PACKAGES
being unconditionally reset here. This clearly seems wrong, as i understand we clearly want to maintain value ofCPM_PACKAGES
between generate runs. However, since you have it there this way for four years it must work somehow... Can someone explain how this but is supposed to not reset cachedCPM_PACKAGES
value every time? Maybe i am missing something in my project configuration?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions