fix: cover logs error for ws message

[barbarosh]

Some message from websocket contain error

{
  "id": 59,
  "jsonrpc": "2.0",
  "error": {
    "code": -32601,
    "message": "Subscriptions unsupported for this network"
  }
}

Which not present any where, just add console log for represent error for developer

[changeset-bot]

⚠️ No Changeset found

Latest commit: b8ff4f7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[steveluscher]

This is a good change. This does not of course solve the problem of the subscription system endlessly looping when it encounters an error like this. Consider this:

import { Connection } from '@solana/web3.js';
const connection = new Connection('https://api.devnet.solana.com');
connection.onAccountChange({ toBase58() { return '1'.repeat(31); }}, console.log);

This invalid pubkey will generate a JSON-RPC error:

Received JSON-RPC error calling `accountSubscribe` {
  args: [
    '1111111111111111111111111111111',
    { encoding: 'base64', commitment: 'finalized' }
  ],
  error: { code: -32602, message: 'Invalid Request: Invalid pubkey provided' }
}

But then the thing will loop forever, retrying the subscription endlessly.

The problem is that this API has no practical way to communicate subscription failure to the client. This has been fixed in @solana/web3.js@2.0.0 and will not be addressed in the 1.x line.

[github-actions]

🎉 This PR is included in version 1.95.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[barbarosh]

This is a good change. This does not of course solve the problem of the subscription system endlessly looping when it encounters an error like this. Consider this:

import { Connection } from '@solana/web3.js';
const connection = new Connection('https://api.devnet.solana.com');
connection.onAccountChange({ toBase58() { return '1'.repeat(31); }}, console.log);

This invalid pubkey will generate a JSON-RPC error:

Received JSON-RPC error calling `accountSubscribe` {
  args: [
    '1111111111111111111111111111111',
    { encoding: 'base64', commitment: 'finalized' }
  ],
  error: { code: -32602, message: 'Invalid Request: Invalid pubkey provided' }
}

But then the thing will loop forever, retrying the subscription endlessly.

The problem is that this API has no practical way to communicate subscription failure to the client. This has been fixed in @solana/web3.js@2.0.0 and will not be addressed in the 1.x line.

Thanks, for explanation, of course this changes just for notify developer what something wrong with subscribe, and I like about 2 version which fixes this behavior, will wait for stable release

[github-actions]

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.