protocol

Creating a new issue based on lbryio/lbry-sdk#877

• Update ensure_directory_exists() to check that the directory is writable by the current process.
• If it's not, return a useful error
• Add tests to cover the case when
  • download directory does not exist
  • download dir exists but is not writable
  • dir exists an

Background

Working with the RPC interface, I was unclear on whether the raw_key_bytes response for WalletKit calls like DeriveKey and DeriveNextKey returned public or private keys. It would be helpful to make it explicit in the doc that the response is the public key for the particular key pair.

https://github.com/lightningnetwork/lnd/blob/5681c0eecfac1277834ee54bf4d5e08a9fc46551/l

• OS: Linux
• Version of IPFS Desktop: 0.16.2

Describe the bug
npm warns about a deprecated module called requests

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

Describe the feature you'd like supported

We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update

This crate was a workaround for unwrap panic messages having a crappy source location, but this was fixed upstream in rust-lang/rust#47809. It's now a superfluous dependency, which could be easily dropped.

Is your feature request related to a problem? Please describe.
On the Import page, clicking "import options" shows the desired import path that can be changed by the user. Unfortunately any changes to this setting will not be used the next time you go to the Import page.

Describe the solution you'd like
When focus of the text field is lost, it should save to the extension's storage so

Take this class, for example:

`
import Foundation

// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`

The generated mock ends up having:

... import SOMEBADTHING ...

Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.

When there are too many data-sources, the RPC call fails with "payload too large"

Affected subgraph

Error:

Payload is too big to load: Unexpected RPC error, error: Transport("Unexpected response status code: 413 Payload Too Large"), component: BlockStream

• [Source](https://github.com/pancakeswap/