Update non-issues GitHub urls #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 21, 2019
vladsud
added a commit
that referenced
this pull request
May 29, 2020
1. @fluidframework/client-common-utils Purpose: to have common place that all client code can rely on, and reved with client mono-repo. I believe most of common-utils should move into client-common-utils, but I'm too lazy to do it in one go. 2. @fluidframework/container-utils. Purpose: for various stand-alone utilities that container provides, likely helper methods for error handling. Better name suggestions are welcome! With this, CustomErrorWithProps moved to #1 & CreateContainerError to # 2.
nmsimons
added a commit
that referenced
this pull request
Aug 28, 2020
TriDucNgo
added a commit
that referenced
this pull request
Mar 29, 2021
merge official into personal fork
karlbom
pushed a commit
to karlbom/FluidFramework
that referenced
this pull request
Apr 14, 2021
Removed prettier from property-dds project.
NicholasCouri
added a commit
that referenced
this pull request
Mar 28, 2023
## Description Currently tinylicious fails to run sample scenarios in the [Share Live Repo](https://github.com/microsoft/live-share-sdk) 2 interesting commits: a) [Update deps (minor) on server release group in tinylicious (#14586) · 12b3f4c (github.com)](12b3f4c#diff-18fce4d66a0b908f502bc635b1c1377557fd7ec4f8d9df8dcaa4d9c261158ca9)) Throws when getTenantGitManager is invoked. 2) [Separate api for getting tenant gitManager. (#14290) · d368f26 (github.com)](d368f26#diff-deeaa88a2f939b81094f7412e1482709a59c4c47850a5c379c92aef0b78d70d5)) Moved the call when creating the document from getTenant to getTenantGitManager and I'm not sure if it applies to tinylicious but it is consumed by it. This PR is trying to revert the current behavior by keeping changes #2 and not throwing on #1 Repro steps: a) Clone https://github.com/microsoft/live-share-sdk b) Follow instructions from the Readme to install (I had to also install vite as it was failing without it) c) Simply try to run one of the samples (I'm using samples\javascript\03.live-canvas-demo\) http://localhost:3000/
NicholasCouri
added a commit
to NicholasCouri/FluidFramework
that referenced
this pull request
Mar 28, 2023
## Description Currently tinylicious fails to run sample scenarios in the [Share Live Repo](https://github.com/microsoft/live-share-sdk) 2 interesting commits: a) [Update deps (minor) on server release group in tinylicious (microsoft#14586) · microsoft/FluidFramework@12b3f4c (github.com)](microsoft@12b3f4c#diff-18fce4d66a0b908f502bc635b1c1377557fd7ec4f8d9df8dcaa4d9c261158ca9)) Throws when getTenantGitManager is invoked. 2) [Separate api for getting tenant gitManager. (microsoft#14290) · microsoft/FluidFramework@d368f26 (github.com)](microsoft@d368f26#diff-deeaa88a2f939b81094f7412e1482709a59c4c47850a5c379c92aef0b78d70d5)) Moved the call when creating the document from getTenant to getTenantGitManager and I'm not sure if it applies to tinylicious but it is consumed by it. This PR is trying to revert the current behavior by keeping changes microsoft#2 and not throwing on microsoft#1 Repro steps: a) Clone https://github.com/microsoft/live-share-sdk b) Follow instructions from the Readme to install (I had to also install vite as it was failing without it) c) Simply try to run one of the samples (I'm using samples\javascript\03.live-canvas-demo\) http://localhost:3000/
This was referenced Mar 28, 2023
NicholasCouri
added a commit
that referenced
this pull request
Mar 29, 2023
## Description Currently tinylicious fails to run sample scenarios in the [Share Live Repo](https://github.com/microsoft/live-share-sdk) 2 interesting commits: a) [Update deps (minor) on server release group in tinylicious (#14586) · 12b3f4c (github.com)](12b3f4c#diff-18fce4d66a0b908f502bc635b1c1377557fd7ec4f8d9df8dcaa4d9c261158ca9)) Throws when getTenantGitManager is invoked. 2) [Separate api for getting tenant gitManager. (#14290) · d368f26 (github.com)](d368f26#diff-deeaa88a2f939b81094f7412e1482709a59c4c47850a5c379c92aef0b78d70d5)) Moved the call when creating the document from getTenant to getTenantGitManager and I'm not sure if it applies to tinylicious but it is consumed by it. This PR is trying to revert the current behavior by keeping changes #2 and not throwing on #1 Repro steps: a) Clone https://github.com/microsoft/live-share-sdk b) Follow instructions from the Readme to install (I had to also install vite as it was failing without it) c) Simply try to run one of the samples (I'm using samples\javascript\03.live-canvas-demo\) http://localhost:3000/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kept specific issues pointed to prior repo