Skip to content
This repository was archived by the owner on Dec 5, 2024. It is now read-only.
This repository was archived by the owner on Dec 5, 2024. It is now read-only.

No Periodic Polling for Locks #823

Closed
@Joen-UnLogick

Description

@Joen-UnLogick

Description

Locks doesn't update automatically without user interaction.
This is a clarification of bug #785 which fixed a part of the problem.

Steps to Reproduce

  1. Open the same unity project in from two locations at the same time
  2. Navigate the project view to watch the same file in both instances of unity
  3. Close all GitHub editor windows in both instances of unity
  4. Lock a file in one of the projects
  5. Observe that the second instance of Unity never marks the file as locked without opening the GitHub Editor Window

Expected behavior:
I would expect that the other other project eventually polled the locked status and showed that the file was locked.

Actual behavior:
Nothing, there is no visual cue that the file is locked.

Locks are polled only on assembly reload (recompile, enter/leave playmode) and when you go into the locks tab of the github window. This works for most developers, but it doesn't always work for artists and level designers.

Reproduces how often:
100%

Additional Information

We host our git server in house because our projects are quite large. This also means that we have plenty of bandwidth to let everyone poll once per second for all we care. The important thing is that everyone can see which files are locked and which ones are free for editing.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions