mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
c2e0a27d2c
This commit fixes a bug where uploading the same file a second time in the same browser session would appear to the user to stall with `Uploading [filename]...` in the composebox. This is because `tus-js-client` makes a HEAD request to check for already-uploaded files -- and, if found, that request is used in the `upload-success` callback. That left the callback with no response body to parse, to know what URL to insert. Store the `/user_uploads/...` URL in the file metadata after a successful upload, and if the fingerprint matches a previous upload, pull that URL (and filename, as it may have changed server-side) out of the previous upload's metadata. Co-authored-by: Shubham Padia <shubham@zulip.com>
53 lines
2.1 KiB
Python
53 lines
2.1 KiB
Python
import os
|
|
|
|
ZULIP_VERSION = "11.0-dev+git"
|
|
|
|
# Add information on number of commits and commit hash to version, if available
|
|
zulip_git_version_file = os.path.join(
|
|
os.path.dirname(os.path.abspath(__file__)), "zulip-git-version"
|
|
)
|
|
lines = [ZULIP_VERSION, ""]
|
|
if os.path.exists(zulip_git_version_file):
|
|
with open(zulip_git_version_file) as f:
|
|
lines = [*f, "", ""]
|
|
ZULIP_VERSION = lines.pop(0).strip()
|
|
ZULIP_MERGE_BASE = lines.pop(0).strip()
|
|
|
|
LATEST_MAJOR_VERSION = "10.0"
|
|
LATEST_RELEASE_VERSION = "10.3"
|
|
LATEST_RELEASE_ANNOUNCEMENT = "https://blog.zulip.com/zulip-server-10-0"
|
|
|
|
# Versions of the desktop app below DESKTOP_MINIMUM_VERSION will be
|
|
# prevented from connecting to the Zulip server. Versions above
|
|
# DESKTOP_MINIMUM_VERSION but below DESKTOP_WARNING_VERSION will have
|
|
# a banner at the top of the page asking the user to upgrade.
|
|
DESKTOP_MINIMUM_VERSION = "5.4.3"
|
|
DESKTOP_WARNING_VERSION = "5.9.3"
|
|
|
|
# Bump the API_FEATURE_LEVEL whenever an API change is made
|
|
# that clients might want to condition on. If we forget at
|
|
# the time we make the change, then bump it later as soon
|
|
# as we notice; clients using API_FEATURE_LEVEL will just not
|
|
# use the new feature/API until the bump.
|
|
#
|
|
# Changes should be accompanied by documentation explaining what the
|
|
# new level means in api_docs/changelog.md, as well as "**Changes**"
|
|
# entries in the endpoint's documentation in `zulip.yaml`.
|
|
|
|
API_FEATURE_LEVEL = 390
|
|
|
|
# Bump the minor PROVISION_VERSION to indicate that folks should provision
|
|
# only when going from an old version of the code to a newer version. Bump
|
|
# the major version to indicate that folks should provision in both
|
|
# directions.
|
|
|
|
# Typically,
|
|
# * adding a dependency only requires a minor version bump;
|
|
# * removing a dependency requires a major version bump;
|
|
# * upgrading a dependency requires a major version bump, unless the
|
|
# upgraded dependency is backwards compatible with all of our
|
|
# historical commits sharing the same major version, in which case a
|
|
# minor version bump suffices.
|
|
|
|
PROVISION_VERSION = (326, 8) # bumped 2025-05-27 to add @uppy/utils
|