This change amends invalid references to the first onboarding step.
Previously, the route for the first onboarding step was computed in a
router module using our old way of specifying frontend config values.
When we upgraded to our new config style, the module could no longer be
responsible for computing the route due to the module being independent
of the store holding the config. The route was removed, but some
references to it remained.
Change-Id: I8817174bb4acab44c5ff2624d6edb1bd3e675de2
References to the Team page have been modified to refer to its new
name. Previously, it was called Project Members or Users.
Resolves#5761
Change-Id: I71ababe48847d7573f6abbbdb6b24c621b0abd4f
Start using object browser pinia module instead of old files vuex module.
Also removed vuex related code.
Note: dependency will be removed in a follow-up change
Change-Id: I78cfb62a1ecc32bd86381bd3bfd3be4bd0f38e14
This field is deprecated in favor of UserAgent; Removing these
references is the final step necessary before dropping the columns from
the database.
https: //github.com/storj/storj/issues/5432
Change-Id: I3a6619170dcf382f82dc8eddb73b6547eaf636f0
This change ensures that we only trigger a redirect to the onboarding
tour if we're not already there. Previously, we didn't take the current
route into consideration when redirecting. This exposed the risk of an
error occurring that prevented the page from loading.
Change-Id: I70323b21f58229abf463a7c737c262e4253f579a
Add default uploading large file notification when in buckets page.
When dismissed, store in local storage. When user uploads a file that
exceeds 1 GB, show warning notification.
Issue https://github.com/storj/storj/issues/5148
Change-Id: I895a230c017e8439ab2c19ea494930b7e9900a47
Currently when error.html is not available, we should still start the
server and fallback to some simpler implementation. This template does
not require any external assets.
Change-Id: I76b660db988987e1e9ebadd966f60e149f26ff24
lrucache is now using time2 package and we can make expiration
test without using time.Sleep.
https://github.com/storj/storj/issues/5788
Change-Id: I48f2693c3db78fcf4e30e618bb3304be3625100c
go vet was disabled while gateway-mt was not yet
updated to build with some breaking changes in
common. now it's updated, so enable.
Change-Id: Idbb0ab0e56b5bd6545273dd3d41b47e7c79eb4b6
Remove the extra prepended '0x' from the wallet address.
Remove prepended '0x' from the transaction ID.
Change-Id: Id215536915fba62cc348aa2c3356ecc7898d68a2
Fix for an issue:
uploading folder triggers object preview modal to show up if there is already and only 1 uploaded object in this bucket.
By this fix we check if uploading object has prefix (basically folder) so we don't trigger object preview automatically.
Change-Id: I32943ef81c19d4ba1960ecb2f15126dfb381d845
This change separates hubspot form submission for personal and business
accounts, with new company name and storage needs fields.
Issue: https://github.com/storj/storj-private/issues/220
Change-Id: Ieb0fb64f87614c7327dc5f894140fb8a54ededa0
This change modifies the password strength component to reference the
frontend config when displaying the minimum and maximum password
lengths. Previously, these values were written directly in the Vue
file.
Resolvesstorj/customer-issues#691
Change-Id: I75fd3b7acd4536d2adae25525c61df3127d9c0a1
New SQL queries for GetProjectObjectsSegments turns out to introduce
full table scan. This is fix for this problem.
Change-Id: Ieac22aafeb780168523a97e27c9283c9ac6a24c8
This change reverses behavior added by 45d5a93 that made the server
return a 500 status code when the index.html file for the satellite
frontend couldn't be loaded. The presence of this file was previously
intentionally optional.
Change-Id: I875a171a37b735c3523eb5b13d83f084f1781053
Previously, we evaluated index.html as a template in order to insert
frontend config values into meta tags. Now that the frontend fetches
its config through the satellite API, this is no longer necessary.
Resolves#5494
Change-Id: Ic98507c5e16cd80317bd9c31d4b55abda0dd7e34
All values derived from meta tag config values have been removed.
They were unused because references to them were modified to instead
refer to the frontend config fetched through the satellite API.
References #5494
Change-Id: Iab6c5e18eac85e2f757e9e731e23239fa267ee0a
References to the meta tag config values in Vuex store modules and
Pinia stores have been modified to instead refer to the frontend config
fetched through the satellite API.
References #5494
Change-Id: I2d16d8fa8f3159c45f00f506825b0c2119e475ff
The test for the admin API's OAuth authorization behaviour has been
modified to use a random available port given by the system rather than
a hardcoded one. This prevents the test from accidentally using a port
that is already in use.
Change-Id: Iae017b2f397ae53f1a006bae1d0578d2ddfd0875
References to the meta tag config values in Vue components have been
modified to instead refer to the frontend config fetched through the
satellite API.
References #5494
Change-Id: I00ecf81d4a0ba6bd07c827cecb2c689d923d67c0
A common error page component that reflects our new designs has been
added, replacing our old 404 and 50X Vue pages.
Change-Id: Ifc9071674eeda03c5d961c26dce9ff0c80b95c6e
As part of fixing the IO priority of filewalker related
processes such as the garbage collection and used-space
calculation, this change allows the initial used-space
calculation to run as a separate subprocess with lower
IO priority.
This can be enabled with the `--storage2.enable-lazy-filewalker`
config item. It falls back to the old behaviour when the
subprocess fails.
Updates https://github.com/storj/storj/issues/5349
Change-Id: Ia6ee98ce912de3e89fc5ca670cf4a30be73b36a6
the parallelism and parallelism-chunk-size flags
which used to control how many parts to split a
segment into and many to perform in parallel
are now deprecated and replaced by
maximum-concurrent-pieces and long-tail-margin.
now, for an individual transfer, the total number
of piece uploads that transfer will perform is
controlled by maximum-concurrent-pieces, and
segments within that transfer will automatically
be performed in parallel. so if you used to set
your parallelism to n, a good value for the pieces
might be something approximately like 130*n, and
the parallelism-chunk-size is unnecessary.
Change-Id: Ibe724ca70b07eba89dad551eb612a1db988b18b9
