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
If you believe you have found a new security vulnerability in this repository, please report it to us as follows.
4
+
5
+
## Reporting Security Issues
6
+
7
+
* Please do **not** report security vulnerabilities through public GitHub issues.
8
+
9
+
* Please create a draft security advisory on the Github page: the reporting form is under `> Security > Advisories`. The URL is https://github.com/exasol/metabase-driver/security/advisories/new.
10
+
11
+
* If you prefer to email, please send your report to `infosec@exasol.com`.
12
+
13
+
## Guidelines
14
+
15
+
* When reporting a vulnerability, please include as much information as possible, including the complete steps to reproduce the issue.
16
+
17
+
* Avoid sending us executables.
18
+
19
+
* Feel free to include any script you wrote and used but avoid sending us scripts that download and run binaries.
20
+
21
+
* We will prioritise reports that show how the exploits work in realistic environments.
22
+
23
+
* We prefer all communications to be in English.
24
+
25
+
* We do not offer financial rewards. We are happy to acknowledge your research publicly when possible.
2. Download the Exasol JDBC driver from the [Download Portal](https://downloads.exasol.com/clients-and-drivers) and install it:
67
+
2. Download the Exasol JDBC driver from the [Download Portal](https://downloads.exasol.com/clients-and-drivers) or get it from `~/.m2/repository/com/exasol/exasol-jdbc/$v/exasol-jdbc-$v.jar`and install it:
When tests fail locally or in CI, search the log output for`ERROR in` or `FAIL in` to find test errors/failures.
183
+
157
184
### Using the REPL
158
185
159
186
```sh
@@ -208,34 +235,49 @@ Script `run-integration-tests.sh` automatically applies this patch when file `$M
208
235
When the patch file has changed or you updated to a new Metabase release, do the following and re-run the integration tests with `run-integration-tests.sh`.
## `FileNotFoundException: Could not locate metabase/test/data/exasol__init.class, metabase/test/data/exasol.clj or metabase/test/data/exasol.cljc on classpath.`
261
+
Releases are built using [release-droid](https://github.com/exasol/release-droid).
234
262
235
-
Verify that `$METABASE_DIR/modules/drivers/exasol` is a symlink to the `metabase-driver` directory.
263
+
# Troubleshooting
236
264
237
265
## Failing Integration Tests
238
266
267
+
### Error `Javascript resource not found`
268
+
269
+
Tests fail with the following error
270
+
271
+
```
272
+
Javascript resource not found: frontend_client/app/dist/lib-static-viz.bundle.js
273
+
```
274
+
275
+
then run
276
+
277
+
```sh
278
+
cd $METABASE_DIR && yarn build-static-viz
279
+
```
280
+
239
281
### Different Decimal Point
240
282
241
283
Tests fail on macOS because they expect numbers with a `.` as decimal point (e.g. `1000.0 µs`) but get a `,` (e.g. `1000,0 µs`), e.g.:
@@ -253,3 +295,33 @@ Solution: run tests under Linux with English locale or pass arguments `-J-Duser.
253
295
### Time Dependent Tests
254
296
255
297
Some Metabase integration tests depend on the current timestamp and will fail when the year changes. See [issue #14](https://github.com/exasol/metabase-driver/issues/14) for details.
298
+
299
+
### Inconsistent Test Results in CI and Locally
300
+
301
+
If a tests fails in CI and succeeds locally or vice versa, ensure you have a clean working copy of `$METABASE_DIR`:
0 commit comments