Slack channel IDs are now more than 9 letters – adjust the tip

See merge request !171

fix: allow working with adjusted GUC values (#185)

Closes #185

See merge request !168

* Dedicate a user connect to ensure that Joe Bot keeps using the same connection for the same client session
* Send the rest service queries using connections from the pool
* Specify configuration timeouts of the pool connection

fix: build release Docker images for different registries in separate jobs

See merge request !166

fix: restart removed sessions after psql commands call (#183)

Closes #183

See merge request !165

feat: push the Docker release images to the developer's Docker registry

See merge request !164

refactor: redefine configuration structure (database-lab#278)

See merge request !160

- change configs structure
- adjust Docker image
- clean up README

Fix issues of sessions restoration

See merge request !163

Viktor Grigorev authored Sep 02, 2021 and Artyom Kartasov committed Sep 02, 2021

* duplicating session restore messages for multichannel configuration (see #183 for details)
* noisy debug output of slack\* assistants
* logger lib update (DLE 2.4, more informative debug output)

fix: register multiple channels for a single assistant (#182)

Closes #182

See merge request !162

* initialize and register an assistant once (not for each channel)
* create a single project for the Platform client
* remove checks for initialized message processors
* remove debug mode for libraries because it generates too many entries
* clean up the logs

fix missing user sessions for the socket-mode assistant(#179)

Closes #179

See merge request !161

feat: slack socket mode #179

Closes #179

See merge request !159

Viktor Grigorev authored Aug 17, 2021 and Artyom Kartasov committed Aug 17, 2021

New Slack apps may not use any Real Time Messaging API method. For most applications, Socket Mode is a better way to communicate with Slack.

feat: dump user's session data in json file during shutdown to restore active sessions

Closes #107

See merge request !158

Viktor Grigorev authored Aug 17, 2021 and Artyom Kartasov committed Aug 17, 2021

Proposal is to save all sessions in config/sessions.json file and read it during startup, write during shutdown

Limitations:

* current tutor mounts one config file to docker container `--volume ~/.dblab/joe.yml:/home/config/config.yml`. You have to take care of sessions.json to run new Joe image version
* json is readable format, some people could try to modify it. Joe won't start with incorrect sessions.json file
* it updated sessions.json only during normal shutdown. Any bug with panic could wipe active sessions
* currently it does not check clone param changes. e.g. you can change database user / dbname. Does it make sense to connect with old credentials to the new db?
* any errors during user's session restore will wipe it!

feat: auto-register Joe Bot on the Platform (#180)

Closes #180

See merge request !157

* extend Joe configuration
* add methods for Platform client (the Joe Bot repository - `/pkg/services/platform/platform.go`)
  * `registerInstance`
    * send a request `https://postgres.ai/api/general/rpc/joe_instance_create`
    * keep a Joe Bot instance ID given from the Platform (`pkg/connection/webui/assistant.go`)
  * `deregisterInstance` - send a request `https://postgres.ai/api/general/rpc/joe_instance_destroy`
* deregister instance on stopping (graceful shutdown)

fix: remove setting read blocks

# Description
Number of read blocks is not necessary for now since the Database Lab Engine counts read bytes directly.

# Related issue
database-lab#212

See merge request !156

feat: allow changing requests timeout (database-lab#243)

See merge request !154

fix: display "N/A" as I/O timing values when track_io_timing is off and keep showing numeric values when it's on (#166)

# Description
When track_io_timing is off, we need to show "N/A" for IO timing numbers (both reads and writes) in the summary. If it's on, then we need to show numeric values, which may be 0.

This change removes the existing confusion in displaying "N/A" and "0".

# Related issue
#166

See merge request !155

fix: display "N/A" as I/O timing values when track_io_timing is off and keep showing numeric values when it's on (#166)

fix: measure total time if the query estimation fails (#177)

# Description
Without this, if the estimator doesn't work then the duration of any `exec` command is always shown as 0. This change fixes it.

Closes #177

See merge request !153

fix: change format of the configuration file

See merge request !152

refactor: move the query timing estimator package to the DBLab repository (database-lab#212)

# Description
Move the query timing estimator package to the DBLab repository in order to have an opportunity to use it for CI Observer purposes:
- remove the estimator package from the current repository
- import the estimator package from the Database Lab repository
- refactor `exec` and `explain` commands to use the imported library

database-lab#212 (comment 520279684)

# Related issue
database-lab#212

See merge request !150

fix: release the acquired connection in case of failed queries (#176)

Closes #176

See merge request !151

fix: calibrate estimator thresholds

# Description
- set default configs
- evaluate the necessity of estimation
- count a number of samples

See merge request !149