-
Notifications
You must be signed in to change notification settings - Fork 274
Version common-utils
+ Setup int test environment
#566
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
Conversation
8d9b06c
to
fa38597
Compare
common-utils
+ Setup int test environment
@@ -41,12 +41,15 @@ dev-int-build: | |||
|
|||
.PHONY: dev-int | |||
dev-int: | |||
docker compose -p int -f ./docker-compose.ci.yml run --rm api dev:int $(FILE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The dx should be the same (run make dev-int FILE=blabla
)
# - 6379:6379 | ||
networks: | ||
- internal | ||
api: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this out of docker (since we need to test common-utils
together)
@@ -346,7 +346,7 @@ export class ClickhouseClient { | |||
} else if (isNode) { | |||
const { createClient } = await import('@clickhouse/client'); | |||
const _client = createClient({ | |||
host: this.host, | |||
url: this.host, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just curious about this change...related to the PR or a drive-by fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its a drive-by style change. the flag should work either way. saw the api deprecation warning (https://github.com/ClickHouse/clickhouse-js/blob/1ebdd39203730bb99fad4c88eac35d9a5e96b34a/CHANGELOG.md?plain=1#L258)
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v2, this PR will be updated.
Releases
@hyperdx/[email protected]
Patch Changes