Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix "unexpected end of stream" error. #608

Merged
merged 2 commits into from
Apr 21, 2022
Merged

Conversation

fedinskiy
Copy link
Contributor

We check that MariaDB container started, by looking into log and waiting
for special lines. Before that change, we were looking for a line "ready for connections",
which was duplicated and its first appearance was right before a reload
of the container, so in some cases we were trying to connect to
non-working DBMS. Now we use a unique line.

Summary

(Summarize the problem solved by this PR, and how to verify it manually)

Please select the relevant options.

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

We check that MariaDB container started, by looking into log and waiting
for special lines. Before that change, we were looking for a line "ready for connections",
which was duplicated and its first appearance was right before a reload
of the container, so in some cases we were trying to connect to
non-working DBMS. Now we use a unique line.
@fedinskiy fedinskiy requested a review from pjgg April 20, 2022 15:35
@fedinskiy
Copy link
Contributor Author

This is similar to the change made for sql-app in this MR: #599

@fedinskiy fedinskiy requested a review from rsvoboda April 21, 2022 08:09
@fedinskiy
Copy link
Contributor Author

Second commit is a fix for issue, described here: bitnami-labs/sealed-secrets#822

Copy link
Contributor

@pjgg pjgg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's wait to CI just to double-check that docker-containers expected logs remain the same.

README.md Outdated
- MSSQL: `mcr.microsoft.com/mssql/rhel/server`
- Oracle
- version 18c XE: `gvenzl/oracle-xe:18.4.0-slim`
- version 18c XE: `gvenzl/oracle-xe:21-slim`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does this oracle version need to be changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

README.md Show resolved Hide resolved
@rsvoboda rsvoboda requested review from mjurc and removed request for rsvoboda April 21, 2022 08:28
README.md Outdated Show resolved Hide resolved
pom.xml Show resolved Hide resolved
pom.xml Show resolved Hide resolved
pom.xml Show resolved Hide resolved
pom.xml Show resolved Hide resolved
Until 21.04.2022 we used quay.io/bitnami images to circumvent docker
pull limit. Unforunately, Bitnami deleted all their quay.io images on
the 20th of April, so now we use Docker hub and cashing proxy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants