Unhandled backend message
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
[error] 🔥 An unhandled backend message was encountered
[error] 🔥 at /home/runner/work/skunk/skunk/modules/core/shared/src/main/scala/net/protocol/Startup.scala:52
[error] 🔥
[error] 🔥 Message: UnknownMessage(Y, ByteVector(6 bytes, 0x352e352e352d))
[error] 🔥
[error] 🔥 This is an implementation error in Skunk.
[error] 🔥 Please report a bug with the full contents of this error message.
[error] skunk.exception.ProtocolError: UnknownMessage(Y, ByteVector(6 bytes, 0x352e352e352d))
ce3 is 3.3.12, skunk is 0.6.3, postgres 15.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at modules/core/shared/src/main/scala/net/protocol/Startup.scala:52 and reproduce the error with Skunk 0.6.3, CE3 3.3.12, and PostgreSQL 15.4. Trace the UnknownMessage(Y, ByteVector(...)) response to determine which backend message is unhandled. Done means the cause is identified and the protocol behavior is covered appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, scala
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100