Currently getting the following error whenever changing an ItemRack equipment set (for example replacing chest armor with a new one).
BetterBags then does not register the change in the set.

22x BetterBags/core/events.lua:201: ctx has been cancelled: categories/Changed
[string "=[C]"]: in function `error'
[string "@BetterBags/core/events.lua"]:201: in function `SendMessage'
[string "@BetterBags/data/categories.lua"]:380: in function `DeleteCategory'
[string "@BetterBags_ItemRack/main.lua"]:39: in function <BetterBags_ItemRack/main.lua:36>
[string "@BetterBags_ItemRack/main.lua"]:101: in function `handler'
[string "@ItemRack/ItemRack.lua"]:299: in function `FireItemRackEvent'
[string "@ItemRackOptions/ItemRackOptions.lua"]:440: in function `SaveSet'
[string "@ItemRackOptions/ItemRackOptions.lua"]:288: in function `ButtonOnClick'
[string "*ItemRackOptions.xml:842_OnClick"]:1: in function <[string "*ItemRackOptions.xml:842_OnClick"]:1>

Locals:
(*temporary) = "ctx has been cancelled: categories/Changed"```

I'm on Cataclysm Classic, forgot to mention.

I can't be sure when it started sadly. I didn't play over the holidays and only started leveling my alt again two days ago. Before that I might have just not noticed the bug when raid logging on my main.

I couldn't help but investigate a little and found this lead, by calling error() in the context:Timeout and context:Cancel methods from BetterBags when something calls them on the BetterBags_ItemRack context.
Like this:

  if self.keys["event"] == "BetterBags_ItemRack" then
    error("someone started timeout on ItemRack ctx")
  end

And turns out it does happen:

1x BetterBags/core/context.lua:130: someone started timeout on ItemRack ctx
[string "=[C]"]: in function `error'
[string "@BetterBags/core/context.lua"]:130: in function `Timeout'
[string "@BetterBags/data/refresh.lua"]:150: in function `StartUpdate'
[string "@BetterBags/data/refresh.lua"]:250: in function `cb'
[string "@BetterBags/core/events.lua"]:49: in function <BetterBags/core/events.lua:47>
[string "=[C]"]: ?
[string "@Ace3/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...Ons/Ace3/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
[string "@Ace3/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function `SendMessage'
[string "@BetterBags/core/events.lua"]:206: in function `SendMessage'
[string "@BetterBags/data/categories.lua"]:381: in function `DeleteCategory'
[string "@BetterBags_ItemRack/main.lua"]:39: in function <BetterBags_ItemRack/main.lua:36>
[string "@BetterBags_ItemRack/main.lua"]:101: in function `handler'
[string "@ItemRack/ItemRack.lua"]:299: in function `FireItemRackEvent'
[string "@ItemRackOptions/ItemRackOptions.lua"]:440: in function `SaveSet'
[string "@ItemRackOptions/ItemRackOptions.lua"]:288: in function `ButtonOnClick'
[string "*ItemRackOptions.xml:846_OnClick"]:1: in function <[string "*ItemRackOptions.xml:846_OnClick"]:1>

Locals:
(*temporary) = "someone started timeout on ItemRack ctx"

I'm guessing you're not meant to have a long-lived context. It's not documented tho :D Cidan/BetterBags#662

Maybe creating a new context everytime updateCategories is called will work?
Edit: Works for me (moving context:New to beginning of updateCategories).
But it's still unclear to me what the intended way is. Are we supposed to create a new Context for every API call?

Today there is no error and the set is updated in bag view, so apparently it does not always happen 🤔
Edit: Now it started happening again. I guess something triggers the context cancellation during play

I don't have any chars on cata, so I will try to trigger this in classic and see if i can come up with a solution.

I can reproduce on classic, currently trying to figure out why this is happening. Did this only start recently? Because the last BetterBags release has been about 4 months ago.

Oh, I'm sorry, I did not see your comments!
I did some investigating too and am pretty sure this is caused by a bug in BetterBags that started about 4 months ago, but you are the first to notice it. I have forwarded this to Cidan and he said he will look into it, confirming it is likely a bug there. I think the context is falsely being deleted after some time, however I have now also asked how he inteded contexts to be used, just in case.

It seems like Cidan is a bit busy as of late so I will probably just go with the potential fix by sending a new context each time. I pushed the commit already if you would like to give the latest version a try. Will do some testing tomorrow and probably publish a new version

I am getting this in SoD too. Almost every time I replace an item in an existing set. Then the BB categories are broken until a reload.

Seems stable to me. I will tag a new version and publish to CurseForge. Please tell me if you still have issues with this :)