Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4 URL Mode #2919

Merged
merged 9 commits into from
Aug 14, 2023
Merged

v4 URL Mode #2919

merged 9 commits into from
Aug 14, 2023

Conversation

infinite-persistence
Copy link
Collaborator

@infinite-persistence infinite-persistence commented Aug 3, 2023

Before-merge checklist

  • Prune the dev SDK env commit

PR Details

  • We are using v1 for Previews, Markdown, Replays and Edit-Meta-Only
  • We would like to deprecate the synchronous v1 in favor of the async v4.

Issues

  • Seeing markdown posts with status 204_pending indefinitely.
    • It can't be a size issue since the post is just a few bytes.
    • Seems to happen when "preview" is enabled -- could it be due to LRBY name clash in quick succession?
      (the preview quest should have preview: true in the SDK params).
    • Example: https://api.na-backend.dev.odysee.com/api/v1/asynqueries/05adfe468d0479edcda2000737974781
  • How to do "metadata-update only" via stream_update on v4?
    • I obtained the token as usual, but directly called the SDK since there will be no URL nor file_path.
    • Proceeded to send the SDK payload with stream_update and no file_path, but I got a status_500.

Didn't remove them previously to make the diffs clearer + quick reference
Previously used in `publish-error.js`, but that has been removed.
It used to be a common task between v1 and v2/v3/v4, so it was placed at the top. But since we are moving to a v4-only solution, it's much clearer to move it as a sequential task.
@infinite-persistence

This comment was marked as outdated.

@keikari

This comment was marked as resolved.

@infinite-persistence

This comment was marked as resolved.

## Issue
When publishing with preview=on, the name collision warning briefly appears
https://user-images.githubusercontent.com/34790748/260001187-84c5f604-ee2f-4757-88d6-412a5569279c.webm

## Why
When a publish is pending via tus, we prevent the next upload form from re-using any of the pending claim names. As we are replacing v1 with v4, every upload (including previews), is a tus upload now, so it's trying to warning against itself, lol.

## Fix
Just don't include previews in the pending name list.
@infinite-persistence
Copy link
Collaborator Author

-- Updates --

  • Addressed UI glitch.
  • Unless something comes up, the plan is to deploy on Monday afternoon.

@infinite-persistence infinite-persistence merged commit 3b442bc into master Aug 14, 2023
1 check passed
@infinite-persistence infinite-persistence deleted the v4.url.mode branch August 14, 2023 07:55
infinite-persistence added a commit that referenced this pull request Aug 14, 2023
Reverts 3b442bc

The TUS address returned is incorrect.
infinite-persistence added a commit that referenced this pull request Aug 14, 2023
The backend issue has been resolved.

Also bumped the minimum version for better logging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants