workspace handles

[nikochiko]

• db: add handle to workspaces
• add default handle generator for workspaces
• refactor input box and update logic for handles
• add handles to workspace admin
• show handle-input on workspaces
• create default handle for workspaces on creation

Q/A checklist

• If you add new dependencies, did you update the lock file?

poetry lock --no-update

• Run tests

ulimit -n unlimited && ./scripts/run-tests.sh

• Do a self code review of the changes - Read the diff at least twice.
• Carefully think about the stuff that might break because of this change - this sounds obvious but it's easy to forget to do "Go to references" on each function you're changing and see if it's used in a way you didn't expect.
• The relevant pages still run when you press submit
• The API for those pages still work (API tab)
• The public API interface doesn't change if you didn't want it to (check API tab > docs page)
• Do your UI changes (if applicable) look acceptable on mobile?
• Ensure you have not regressed the import time unless you have a good reason to do so.
  You can visualize this using tuna:

python3 -X importtime -c 'import server' 2> out.log && tuna out.log

To measure import time for a specific library:

$ time python -c 'import pandas'

________________________________________________________
Executed in    1.15 secs    fish           external
   usr time    2.22 secs   86.00 micros    2.22 secs
   sys time    0.72 secs  613.00 micros    0.72 secs

To reduce import times, import libraries that take a long time inside the functions that use them instead of at the top of the file:

def my_function():
    import pandas as pd
    ...

Legal Boilerplate

Look, I get it. The entity doing business as “Gooey.AI” and/or “Dara.network” was incorporated in the State of Delaware in 2020 as Dara Network Inc. and is gonna need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Dara Network Inc can use, modify, copy, and redistribute my contributions, under its choice of terms.

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208891640450156

[nikochiko]

@devxpy do you want to review and merge this part first? - adding workspace->handle to DB and allowing workspace admins to edit it.

Or, to wait and review it along with the UI changes for rendering the workspace page on /{workspace-handle} (that is not in this PR yet)?

[nikochiko]

[devxpy]

this could be a method on Handle?

[devxpy]

I do think the better path would be to move handles from app user to workspace entirely, but I guess this is easier

[nikochiko]

I was thinking the same, but not entirely. On the users' profile page, we do include contributions to other workspaces and I think that's the way we want it.

I also think it's likely that we might want to allow adding saved runs from another workspace to a user's profile a la github

[devxpy]

I meant more like how we transferred billing info from user to workspace so its consistent and we can always refer to current_workspace.handle

[nikochiko]

that makes sense to me 👍

[greptile-apps]

PR Summary

This PR adds handle functionality to workspaces, allowing teams to have unique identifiers similar to user handles, with automatic handle generation and management through the admin interface.

• Added handle OneToOneField to Workspace model with proper validation and uniqueness constraints in /workspaces/models.py
• Implemented automatic handle generation for workspaces based on display name in /handles/models.py with fallback options
• Added handle input field and update logic to workspace edit form in /workspaces/views.py with transaction handling
• Added new index on PublishedRun model for optimizing visibility/workspace queries in bots/migrations/0091_publishedrun_bots_publis_visibil_cf3dd8_idx.py
• Updated PublishedRunVisibility to support public visibility for team workspace handles in /bots/models.py

_{💡 (3/5) Reply to the bot's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

_{10 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: returning None from a generator is incorrect - should use 'return' with no value or just 'return []'

[greptile-apps]

logic: handle added to autocomplete_fields but Handle model needs search_fields defined in its admin for autocomplete to work

[greptile-apps]

logic: Handle creation and save should be wrapped in a transaction to ensure atomicity. If save fails after handle creation, the handle could be orphaned.