hcengineering / hcengineering/platform

API client 0.7.18 no longer connects to Huly Cloud - "Data read, but end of buffer not reached"

Open
#10,481 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
27.7k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Description

My integration using `@hcengineering/api-client@0.7.18` (latest on npm) was working ~1 month ago but now fails with:

```
Connected to server: 0.7.353
[Bridge] Uncaught exception: Data read, but end of buffer not reached 112
```

This appears to be a msgpack protocol mismatch between the npm client (0.7.18) and the current Huly Cloud server (0.7.353).

**Questions:**

1. Was there a recent Huly Cloud upgrade that changed the protocol?
2. Are there compatible package versions that work with current Huly Cloud?
3. Could updated packages be published to npm or GitHub Packages?

**Additional context:**

- My `.npmrc` is configured for GitHub Packages but `@hcengineering/core` is not published there, blocking installation of newer `api-client` versions
- The connection establishes successfully and negotiates the session, but fails on the first data response
- Using token-based authentication with workspace parameter

**Environment:**

- `@hcengineering/api-client`: 0.7.18 (latest on npmjs.org)
- Huly Cloud server reports: 0.7.353
- Node.js 20.x

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.