Tags: apache/texera
Tags
chore: drop R support flags from Dockerfiles and CI workflow (#4124) ### What changes were proposed in this PR? This PR removes the `WITH_R_SUPPORT` build argument and all R-related installation logic from the Docker build configuration: 1. **Dockerfiles** (`computing-unit-master.dockerfile` and `computing-unit-worker.dockerfile`): - Removed `ARG WITH_R_SUPPORT` build argument - Removed conditional R runtime dependencies installation - Removed R compilation and installation steps (R 4.3.3) - Removed R packages installation (arrow, coro, dplyr) - Removed `LD_LIBRARY_PATH` environment variable for R libraries - Removed `r-requirements.txt` copy in worker dockerfile - Simplified to Python-only dependencies 2. **GitHub Actions Workflow** (`.github/workflows/build-and-push-images.yml`): - Removed `with_r_support` workflow input parameter - Removed `with_r_support` from job outputs and parameter passing - Removed `WITH_R_SUPPORT` build args from both AMD64 and ARM64 build steps - Removed R Support from build summary ### Any related issues, documentation, discussions? Related to #4090 ### How was this PR tested? Verified Dockerfile & CI yml syntax are valid ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Sonnet 4.5 (claude-sonnet-4-5-20250929) via Claude Code CLI
feat: add account creation time (#3736) ## Context In effort to improve admin dashboard and allow admins to view account creation time, a new column `account_creation_time` is introduced to the `user` table. This attribute is meant to store the timestamp of a user's account creation time and is a required column of the table. Existing user rows have been given a set time for the column. Closes Issue #3673. ## For Developers Please do the following steps to incorporate with new changes: - Apply core/scripts/sql/updates/14.sql to your local postgres instance ## Summary of Feature When a new user is added to the system (created by admin or google login), the user's information will be logged into the database. The `NOT NULL ON DEFAULT SET now()` statement would make sure that every user's account creation time is logged. And admins will be able to view every user's account creation time in the admin dashboard. ## Database Change A new column `account_creation_time` has been added to the `user` table and is set to `NOT NULL`. On default when a new user is inserted into the table, the creation time for the user will be the current timestamp. Attached below are the current & proposed schema of the `user` table. ## Codebase Change To cooperate with the change, we added a new attribute `accountCreation` to `user.ts` to ensure the frontend receives the account creation time from the backend. Multiple files have been changed as adding the not null attribute to `user.ts` required changes to those files. ## Current Schema <img width="276" height="277" alt="image" src="https://github.com/user-attachments/assets/efffa9a0-ea4a-4ef1-8a28-435f59b83d6d" /> ## Proposed Schema <img width="270" height="303" alt="image" src="https://github.com/user-attachments/assets/3271d5f0-b2da-4b6e-9756-15e9289d6a86" /> ## Screenshot of Implementation <img width="1311" height="774" alt="image" src="https://github.com/user-attachments/assets/e20507b7-121e-40c4-bce1-b4cb0d6ac60b" /> --------- Co-authored-by: ali risheh <[email protected]>
feat: add account creation time (#3736) ## Context In effort to improve admin dashboard and allow admins to view account creation time, a new column `account_creation_time` is introduced to the `user` table. This attribute is meant to store the timestamp of a user's account creation time and is a required column of the table. Existing user rows have been given a set time for the column. Closes Issue #3673. ## For Developers Please do the following steps to incorporate with new changes: - Apply core/scripts/sql/updates/14.sql to your local postgres instance ## Summary of Feature When a new user is added to the system (created by admin or google login), the user's information will be logged into the database. The `NOT NULL ON DEFAULT SET now()` statement would make sure that every user's account creation time is logged. And admins will be able to view every user's account creation time in the admin dashboard. ## Database Change A new column `account_creation_time` has been added to the `user` table and is set to `NOT NULL`. On default when a new user is inserted into the table, the creation time for the user will be the current timestamp. Attached below are the current & proposed schema of the `user` table. ## Codebase Change To cooperate with the change, we added a new attribute `accountCreation` to `user.ts` to ensure the frontend receives the account creation time from the backend. Multiple files have been changed as adding the not null attribute to `user.ts` required changes to those files. ## Current Schema <img width="276" height="277" alt="image" src="https://github.com/user-attachments/assets/efffa9a0-ea4a-4ef1-8a28-435f59b83d6d" /> ## Proposed Schema <img width="270" height="303" alt="image" src="https://github.com/user-attachments/assets/3271d5f0-b2da-4b6e-9756-15e9289d6a86" /> ## Screenshot of Implementation <img width="1311" height="774" alt="image" src="https://github.com/user-attachments/assets/e20507b7-121e-40c4-bce1-b4cb0d6ac60b" /> --------- Co-authored-by: ali risheh <[email protected]>
Fix the TypeError in dataset Share Access. (#3309) ### Purpose: Currently, when entering someone else's email in the dataset Share Access, the console displays an error: TypeError: Cannot read properties of undefined. The reason is that the dataset does not have the allOwners property, causing it to remain undefined. ### Changes: Added a new backend API for datasets to retrieve the owners' emails of datasets that the current user can access. The frontend passes the returned values into the Share Access component. ### Demo: before:  after: 