- Feb 07, 2024
-
-
Georgy Moshkin authored
-
Egor Ivkov authored
-
Egor Ivkov authored
-
- Feb 06, 2024
-
-
Denis Smirnov authored
-
Denis Smirnov authored
Current commit introduces - _pico_routine replicated table - procedure creation with SQL API
-
- Feb 05, 2024
-
-
Dmitry Rodionov authored
This patch combines patches from these two picodata/tarantool fork branches: https://git.picodata.io/picodata/tarantool/-/tree/dynamic-linking-from-system?ref_type=heads https://git.picodata.io/picodata/picodata/picodata/-/tree/svace-fixes?ref_type=heads Previously patches for tarantool were made for 2.11.0 so for 2.11.2 (version we currently use) some of them had to be updated. Patches from b124e8f01fafb98bc3005f77b8852d1f699f8666 initially were committed to fork repo but for manageability it was decided that its easier to support those via patch files. So these changes are added to existing patches in certification_patches dir. Then follow changes from 6b851b86 and 2be2aab5. Patch application is currently concentrated in gitlab-ci.yml. 6b851b moved svace patches application to tarantool's makefile. For now its easier to keep it in one place. Svace patches from previous commit are moved into subdirectory. Patches that touch supplementary files or simply remove them are removed and the list of the files is kept for later to form a dedicated list of files for deletion. Conflicting were picked from f98334ea. Redundant patch for curl libssh was removed because the same change appeared upstream https://github.com/curl/curl/pull/11088/files Luagdb patch was updated. OSCP response patch as well as icu_common_exec patch were removed, since original files are not needed in the build process and thus are deleted from the repo. Lastly patch application is moved to dedicated python script for ease of sharing with vm builder repo. Co-authored-by:
Feodor Alexandrov <feodor.alex.alexandrov@gmail.com>
-
-
-
-
Panic happened in `on_access_denied` trigger. There was a switch to admin and back to user with `su`. Switch back to user panicked in SuGuard drop as user did not have session privilege.
-
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
- Feb 02, 2024
-
-
Alexander Kurdakov authored
Also print new greeting and help
-
Dmitry Rodionov authored
When using git describe fetch depth for shallow clones needs to be deep enough to reach exiting tag. We used to only deepen our submodules for tarantool build but now we reached the same problem for picodata. So fetch tags for it as well. allow_failure in test-helm-docker-image makes CI properly fail and prevent merges when there are failures. Without it it didnt go past "manual action required" icon and allowed to merge CI without fixing other test jobs
-
- Feb 01, 2024
-
-
Feodor Alexandrov authored
-
- Jan 31, 2024
-
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
- Jan 30, 2024
-
-
Dmitry Rodionov authored
Having dynamic build as a default was dictated by certification and now when we merged certification patches back to master it started to cause friction. So this patch makes static build the default and introduces dynamic_build cargo feature instead of static_build one.
-
-
Denis Smirnov authored
-
- Jan 26, 2024
-
-
Feodor Alexandrov authored
1. Add a new option picodata run --shredding to enable shredding upon xlog_remove_file_impl. 2. For test purposes additionally use the inject_errors feature to keep files after shred operation and allow the test code to look inside and make sure that content was really shredded.
-