This project is mirrored from https://github.com/metabase/metabase.
Pull mirroring updated .
- Jul 12, 2022
-
-
Dalton authored
* Handle field values endpoint has_more_values state * Fix isSearchable fn * make shouldSearch evaluation lazy * Prettier nonsense * Remove default has_more_values value * Introduce concept of valuesMode to handle has_more_values (#23795) * Introduce concept of valuesMode to handle has_more_values * use hasList in render method * Pass explicit args to getValuesMode * Fix override logic
-
Gustavo Saiani authored
-
Anton Kulyk authored
-
Alexander Polyankin authored
-
Jeff Bruemmer authored
-
Howon Lee authored
#22967 and boat#161 also apply to MySQL JSON implementation. This PR ports the fixes for those (in #23278 and #22997 respectively) to MySQL. There are many other JSON implementation fixes which don't need a separate port because we moved the describe-table mechanism to the SQL JDBC driver instead of just the Postgres driver.
-
Gustavo Saiani authored
-
Cal Herries authored
-
- Jul 11, 2022
-
-
Cal Herries authored
* Allow group managers to see members even if they're sandboxed * Remove failing test * Delete test file * Fix (unrelated) failing E2E test Co-authored-by:
Nemanja <31325167+nemanjaglumac@users.noreply.github.com>
-
Braden Shepherdson authored
-
GitStart authored
Co-authored-by:
gitstart <gitstart@users.noreply.github.com>
-
GitStart authored
Co-authored-by:
gitstart <gitstart@users.noreply.github.com>
-
GitStart authored
Co-authored-by:
gitstart <gitstart@users.noreply.github.com>
-
Braden Shepherdson authored
-
Gustavo Saiani authored
-
Nick Fitzpatrick authored
-
Gustavo Saiani authored
-
Nick Fitzpatrick authored
-
Nick Fitzpatrick authored
-
Nemanja Glumac authored
-
Braden Shepherdson authored
-
Jeff Bruemmer authored
-
Dalton authored
* Add StringInputWidget component * Second pass, add tests, storybook * Use StringInputWidget as default widget * use label, not title * Remove disabled widget logic * Prettier nonsense * Fix default widget TextWidget usage in query builder * Update text in e2e test * Update e2e text selector
-
Aleksandr Lesnenko authored
-
Luiz Arakaki authored
* Add Exasol as a partner driver * Add Exasol partner driver on docs * Remove Exasol from Community drivers
-
Mahatthana (Kelvin) Nomsawadi authored
* Add toast message after moving questions or models * Add test * Address feedback: extract component into its own file * Remove undo action on question move because it doesn't work in all cases * Fix failed test nodata user can't turn a question into a model * Remove commented code that could confuses more people
-
- Jul 09, 2022
-
-
Howon Lee authored
Pursuant to reopening of #22732. Proximate cause is occasional Java bigints getting in where the types assume it'll only be Clojure bigints. On the current reproduction I have it fixes the bug but I am still determining ultimate cause and if there are other phenomena. There was also differential behavior of backport vs. on-master implementation which I still don't understand. This one needs some sync to have gone through, or else it will prehistoric empetuses towards decelization
-
- Jul 08, 2022
-
-
Aleksandr Lesnenko authored
* fix missing enter full-screen button * fix dashboard background trimmed in the dark mode * update specs
-
Aleksandr Lesnenko authored
-
Gustavo Saiani authored
-
Braden Shepherdson authored
Serialization of Databases, Tables, Fields This brought a few core changes: - Add `serdes-entity-id` to abstract the field used for the ID - Pass the options to `extract-one` so it can eg. do encryption things. - Handle dates in YAML storage and ingestion - `:serdes/meta` now holds the entire hierarchy, not just the leaf model+ID pair. There's an open problem here about the right way to handle secrets like a database's password. Do we assume both sides have the same `MB_ENCRYPTION_SECRET_KEY`? Provide a serdes-specific password the user just made up, and every secret gets decrypted with the source key, encrypted with the serdes key, stored, decrypted with the serdes key, and encrypted with the destination key?
-
Nick Fitzpatrick authored
-
Luiz Arakaki authored
-
Anton Kulyk authored
* Remove anchor time setting * Remove anchor time setting * Update setting * Allow styling `SettingSelect` component * Add `ModelCachingScheduleWidget` * Remove `PersistedModelRefreshIntervalWidget` * Pass `disabled` prop to expression input * Install `cron-expression-validator` * Wrap cron validator to support i18n * Fix React hooks style * Handle "custom" select value * Clean cron input when selecting built-in schedule * Connect custom cron input * Update API endpoint to change schedule * wip * Handle the "year" CRON component * Extract components, make explainer text live * Add default custom schedule value * Add helpful docs * Don't allow configuring CRON seconds part * Fix error message * Tweak popover spacing * Workaround validation lib issue * Run prettier
-
Jeff Bruemmer authored
-
Aleksandr Lesnenko authored
-
Anton Kulyk authored
* Replace interval-hours and anchor-time with cron Removed the two settings and replaced with a single cron schedule setting Renamed the /set-interval endpoint to /set-refresh-schedule * Ignore "year" part in schedule endpoint * Fix variable * Use a temp scheduler and initialize the refresh job Running into errors when updating the triggers for each database's refresh job because the "job" itself didn't exist. Reminder of what's going on here: There's a single refresh job. It has a trigger for each database. So updating the trigger would fail since it doesn't exist since there was no job to hold the triggers. This error is quite clear in the tests run locally: ``` ERROR in metabase.api.persist-test/set-refresh-schedule-test (util.clj:421) Uncaught exception, not in assertion. clojure.lang.ExceptionInfo: Error in with-temporary-setting-values: Couldn't store trigger 'DEFAULT.metabase.task.PersistenceRefresh.database.trigger.1' for 'DEFAULT.metabase.task.PersistenceRefresh.job' job:The job (DEFAULT.metabase.task.PersistenceRefresh.job) referenced by the trigger does not exist. location: metabase.public-settings/persisted-models-enabled setting: "persisted-models-enabled" value: true ``` But this logging is absent from the logging in Github annoyingly: ``` FAIL in metabase.api.persist-test/set-refresh-schedule-test (persist_test.clj:26) Setting new cron schedule reschedules refresh tasks Setting :persisted-models-enabled = true expected: "0 0 0/12 * * ? *" actual: (nil) ``` Whic doesn't give us the error, just the test result. * update to newer API `set-interval` -> `set-refresh-schedule` ``` ;; old {:hours 4} ;; new {:cron "0 0 0/1 * * ? *"} ``` Co-authored-by:
Case Nelson <case@metabase.com> Co-authored-by:
dan sutton <dan@dpsutton.com>
-
Nick Fitzpatrick authored
-
Nick Fitzpatrick authored
-
Nemanja Glumac authored
* Wait for the connected question to fully load * Set default values for source dashboard filters This step alone cuts the test execution time in half! * Visit dashboards directly instead of hitting the `back` button * Simplify function name * Tidy up comments * Wait for the target dashboard card to load * Make setup function more explicit and more descriptive * Make sure results loaded in a public source dashboard before testing click behavior
-