You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
153841: base: clean up TempStorageConfig r=RaduBerinde a=RaduBerinde
#### server: clean up default TempStorageConfig
We currently create an invalid initial `TempStorageConfig` (the `Path`
isn't set). In practice, this config is overridden by
`cli.initTempStorageConfig()`.
We clean this up by leaving the initial `TempStorageConfig` empty.
Epic: none
Release note: None
#### base: clean up TempStorageConfig
`TempStorageConfig` is very confusing. It is very hard to follow the
exact mechanics of when `InMemory` differs from `StoreSpec.InMemory`,
how the paths differ, etc.
In this change:
- we replace the `StoreSpec` field with the `EncryptionOptions` and
the `temp-dirs-record.txt` file path.
- we clean up and clarify the initialization code.
- we improve the documentation for the `--temp-dir` flag.
Epic: none
Release note: None
153846: randgen: fix recent regression in tuple generation r=yuzefovich a=yuzefovich
In 1a751b5 we made a slight change to how we generate random tuples. Namely, we no longer call `ResolvedType` on each tuple element. This can be problematic since we might have generated an element with some Any modifier, which could later lead to "illegal AppendFloat/FormatFloat bitSize" panic when operating with floats.
This commit simply reverts the relevant changes from the commit mentioned above.
This required some minor adjustments to `TestCanonical` since there tuple with NULL elements will have their resolved type differ from the originally requested one.
Fixes: #153805.
Release note: None
Co-authored-by: Radu Berinde <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments