dev  

Messages by Thread

• • Re: [I] Improve upload parameter guidance in Admin Settings [texera] via GitHub
• [PR] feat: enable dataset creation in export results window [texera] via GitHub
  • Re: [PR] feat: enable dataset creation in export results window [texera] via GitHub
  • Re: [PR] feat: enable dataset creation in export results window [texera] via GitHub
  • Re: [PR] feat: enable dataset creation in export results window [texera] via GitHub
  • Re: [PR] feat: enable dataset creation in export results window [texera] via GitHub
  • Re: [PR] feat: enable dataset creation in export results window [texera] via GitHub
• [I] Inconsistent vertical divider height across interface panels [texera] via GitHub
• [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
  • Re: [I] Our Understanding about AWS Lambda Function [texera] via GitHub
• Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
  • Re: [I] log users out periodically for security reasons [texera] via GitHub
• [I] Understanding Config on AWS Fargate [texera] via GitHub
  • Re: [I] Understanding Config on AWS Fargate [texera] via GitHub
  • Re: [I] Understanding Config on AWS Fargate [texera] via GitHub
  • Re: [I] Understanding Config on AWS Fargate [texera] via GitHub
  • Re: [I] Understanding Config on AWS Fargate [texera] via GitHub
  • Re: [I] Understanding Config on AWS Fargate [texera] via GitHub
• [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
  • Re: [PR] feat: cap number of concurrent file uploads [texera] via GitHub
• [I] feat: switch workflow result downloads to use browser native downloads [texera] via GitHub
  • Re: [I] Switch workflow result download to use browser native downloads [texera] via GitHub
• Re: [I] Incorrect output tuple number of R-UDF & Performance Bottleneck [texera] via GitHub
• [I] Cap concurrent file uploads to prevent page freezes with large batches [texera] via GitHub
  • Re: [I] Cap number of concurrent file uploads to prevent page freezes when uploading large batches [texera] via GitHub
  • Re: [I] Cap number of concurrent file uploads to prevent page freezes when uploading large batches [texera] via GitHub
• [I] refactor: expose `validateRepositoryName` in `LakeFSStorageClient` [texera] via GitHub
  • Re: [I] Fix repository name validation message and refactor `LakeFSStorageClient` [texera] via GitHub
  • Re: [I] fix: correct repo name validation message and refactor `LakeFSStorageClient` [texera] via GitHub
• [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
  • Re: [PR] fix: separate user activity window from jwt expiration [texera] via GitHub
• [I] Separate the jwt token expiration time and active threshold [texera] via GitHub
  • Re: [I] Separate the jwt token expiration time and active threshold [texera] via GitHub
• [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
  • Re: [PR] fix: improve email notification subject [texera] via GitHub
• [PR] refactor: expose validate repository name in LakeFSStorageClient [texera] via GitHub
  • Re: [PR] refactor: expose validate repository name in LakeFSStorageClient [texera] via GitHub
  • Re: [PR] refactor: expose validate repository name in LakeFSStorageClient [texera] via GitHub
  • Re: [PR] refactor: expose validate repository name in LakeFSStorageClient [texera] via GitHub
  • Re: [PR] refactor: expose `validateRepositoryName` in `LakeFSStorageClient` [texera] via GitHub
  • Re: [PR] refactor: expose `validateRepositoryName` in `LakeFSStorageClient` [texera] via GitHub
  • Re: [PR] refactor: expose `validateRepositoryName` in `LakeFSStorageClient` [texera] via GitHub
  • Re: [PR] refactor: expose `validateRepositoryName` in `LakeFSStorageClient` [texera] via GitHub
  • Re: [PR] fix: correct repo name validation message and refactor `LakeFSStorageClient` [texera] via GitHub
  • Re: [PR] fix: correct repo name validation message and refactor `LakeFSStorageClient` [texera] via GitHub
• [PR] wip: for loop [texera] via GitHub
• [PR] fix: dataset related dashboard query [texera] via GitHub
  • Re: [PR] fix: dataset related dashboard query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: dataset related dashboard query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
  • Re: [PR] fix: add isDatasetDownloadable and align field order & docstring in dataset query [texera] via GitHub
• Re: [I] Computing Unit Buttons are taking too much space [texera] via GitHub
  • Re: [I] Computing Unit Buttons are taking too much space [texera] via GitHub
• [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
  • Re: [I] Improving subject in email notifications [texera] via GitHub
• [PR] fix: allow navigation menu to adapt to screen width [texera] via GitHub
  • Re: [PR] fix: allow navigation menu to adapt to screen width [texera] via GitHub
  • Re: [PR] fix: allow navigation menu to adapt to screen width [texera] via GitHub
• [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
  • Re: [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
  • Re: [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
  • Re: [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
  • Re: [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
  • Re: [PR] fix: display error notifications for incorrect login credentials [texera] via GitHub
• [PR] chore: Add yarn package manager file [texera] via GitHub
  • Re: [PR] chore: Add yarn package manager file [texera] via GitHub
  • Re: [PR] chore: Add yarn package manager file [texera] via GitHub
  • Re: [PR] chore: Add yarn package manager file [texera] via GitHub
  • Re: [PR] chore: Add yarn package manager file [texera] via GitHub
  • Re: [PR] chore: Add yarn package manager file [texera] via GitHub
• [I] Yarn Package Manager doesn't work on Windows [texera] via GitHub
• [PR] feat(gui) [texera] via GitHub
  • Re: [PR] feat(gui): Add Markdown Support for Descriptions [texera] via GitHub
  • Re: [PR] feat(gui): Add Markdown Support for Descriptions [texera] via GitHub
  • Re: [PR] feat(gui): Add Markdown Support for Descriptions [texera] via GitHub
• [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat: allow datasets with the same name across different users [texera] via GitHub
  • Re: [PR] feat(dataset): allow datasets to have the same name across different users [texera] via GitHub
• Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
  • Re: [PR] fix(ui): Prevent link delete buttons from overlapping [texera] via GitHub
• [PR] chore: enable user system in configuration [texera] via GitHub
  • Re: [PR] chore: enable user system in configuration [texera] via GitHub
  • Re: [PR] chore: enable user system in configuration [texera] via GitHub
  • Re: [PR] chore: enable user system in configuration [texera] via GitHub
  • Re: [PR] chore: enable user system in configuration [texera] via GitHub
• [PR] fix: resolve runtime statistics display issue [texera] via GitHub
  • Re: [PR] fix: resolve runtime statistics display issue [texera] via GitHub
• [PR] docs: update source code license header template in `CONTRIBUTING.md` [texera] via GitHub
  • Re: [PR] docs: update source code license header template in `CONTRIBUTING.md` [texera] via GitHub
• [PR] chore: update Iceberg catalog type to 'postgres' [texera] via GitHub
  • Re: [PR] chore: update default Iceberg catalog type to 'postgres' [texera] via GitHub
  • Re: [PR] chore: update default Iceberg catalog type to 'postgres' [texera] via GitHub
  • Re: [PR] chore: update default Iceberg catalog type to 'postgres' [texera] via GitHub
  • Re: [PR] chore: update default Iceberg catalog type to 'postgres' [texera] via GitHub
• [PR] chore: refactor schema of user_activity table [texera] via GitHub
  • Re: [PR] chore: refactor schema of user_activity table [texera] via GitHub
  • Re: [PR] chore: refactor schema of user_activity table [texera] via GitHub
  • Re: [PR] chore: refactor schema of user_activity table [texera] via GitHub
  • Re: [PR] chore: refactor schema of user_activity table [texera] via GitHub
  • Re: [PR] chore: refactor schema of user_activity table [texera] via GitHub

• Earlier messages
• Later messages