[Cuis-dev] Something strange going on with package dependency version numbers

[Phil B]

Ken,

On Fri, Oct 11, 2019 at 10:58 AM <ken.dickey at whidbey.com> wrote:

> On 2019-10-10 18:36, Phil B via Cuis-dev wrote:
>
> > Ugh/yay! It's not a new bug...  it's a fix exposing issues from the old
> > one.
>
> Hi Phil,
>
> I am currently out with a bad cold, so a proper fix will take me a bit
> longer.
>

No rush needed on my account... rest up.  I have everything working again
and only posted it rather urgently because others might experience similar
issues due to recent changes.


> FYI, there are a couple of things on my list to take care of.
>    [1] Caching FeatureSpec's of a Package when scanned
>    [2] Making checks more strict.
>
> I did a short-cut for the current code by just checking feature names
> when adding FeatureSpec's to the SortedCollection of Packages to load.
> When comparing, I need to use the most strict FeatureSpec rather than
> just checking the names.
>
> Simple to fix, but I have been busy of late.  Ya, always.
>
> One feature we could add.  Right now one can use the FileList to re-load
> an already loaded Package.  This re-checks dependencies but always loads
> the indicated Package.
>
> Would it be helpful/useful/not-too-confusing to have an option to
> re-load all dependencies?
>

That might be nice as a feature not exposed via the UI.  It seems
problematic to expose something like this depending on what changes one has
already made to the loaded package graph.  (i.e. reloading might make
things far worse in some scenarios)

>
> My take is that this would break more things than it would help, as an
> updated dependent from one Package might break something in another,
> already loaded, Package which also requires that dependency.
>

Exactly.


>
> One hopes in the typical case to only be updating a package at a time
> and if making a cluster of edits (e.g. with StyledTextEditor components)
> one could re-load a Package at a time from the FileList.
>

Just FYI, that's not my typical use case at all.  It's pretty common that I
have uncommitted edits across a dozen or more packages.  And then I may
only selectively save them (i.e. I might have 10 modified packages but only
save 8 of them)  It can be any combination of adding new features, fixing
bugs, moving things between packages etc.


>
> Starting from a fresh image and re-loading all Packages from their
> Features seems to me to be the simplest solution.
>

That's generally my preference.  The question is what tools can we provide
to help out when the re-load fails which is what I was running into.  In my
case it was >100 packages and about a dozen of them suddenly had dependency
failures and all I was seeing was a series of back to back dialogs telling
me that a dependency failed but not what package the dependency was in
(hence the request to log this information to the Transcript so that I
could sort through it after the fact.)


>
> Well, as you can perhaps tell, my head is stuffed and my thinking
> muddled.
>
> I'll let you "pre-flight" my fix(es) as I get there.
>
> Thanks again for you patience and resiliency..
> -KenD
>

No worries. Rest up, the code will wait.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20191011/406a4fd0/attachment.htm>