Closed 0x4007 closed 3 weeks ago
@Keyrxng perhaps you can look into this
@Keyrxng the deadline is at Thu, Sep 19, 1:34 PM UTC
There is a collection of issues within the devpool that currently have an id:
label which should be the node_id of the task which it relates to however the extracted node_id doesn't correlate to an issue at all.
Some repos do not exist anymore, others have been renamed such as bounty-bot
which is now devpool-directory-bounties
. I scrubbed issue timelines for erroneous node_id label changes and a host of others debug ideas but came up short.
I was under the impression that a node_id
was immutable once created but this proves that theory wrong I think.
I noticed that issues that had been transferred have kept their old partner label rather than the new repo that would come with a new node_id
by the looks of things.
I think the issues have been caused by a combination of both the Unavailable
label and this node_id
discrepancy, as well as some slightly off boolean logic causing the body to be modified even when isFork: false
on select tasks.
I hope that this also addresses #39 but I can't be sure of that until merged and tested in prod because of the fork conditions applied but locally it looks promising as I'm seeing issues being created which are currently being missed by the sync-issues
workflow and out-of-sync node_id
labels being updated etc.
My debugging has been against production locally. I started writing a spec a couple hours in and felt I had nothing of value to provide so I've waited until I knew more but here's a gist I was going to share early on.
As I've covered multiple tasks, rather than open one big PR I'll open few targeting different fixes, bit late now and I'm awfully tired. Tests will require factoring too which I haven't ran since the PR I merged this morning which seems like a a day or two ago 🤣
I intended for this comment to be a spec at first, but I don't want to be appear to be task dipping, but should I open multiple PRs to this one issue or open small tasks for the specific fixes and link them back to this?
Yeah break them off into separate tasks and then associate a single pull to each.
I suppose it would have been proper to make a checklist here and turn it into a parent task
@Keyrxng, this task has been idle for a while. Please provide an update.
Looks like this fixed itself. No idea what happened.
the recent merge is why it seems to have resolved, I at first thought the backend had broken but it looks like that was the intention, it was mostly the old labels like Permitted
that threw me off.
I renamed the organization from "Ubiquity-OS" to "ubiquity-os" in the URL. I also renamed the organization "display name" from Ubiquity-OS" to "UbiquityOS"
I noticed now that it no longer 1. displays on https://devpool.directory or 2. syncs to the backend.
Please research and implement a sustainable fix for if this ever happens again.