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

Macaroons are created after wallet creation. However, the documentation in the main installation (https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md) states the following:

Running lnd for the first time will by default generate the admin.macaroon, read_only.macaroon, and macaroons.db files that are used to authenticate into lnd.

As a first-time LND user,

• OS: Linux
• Version of IPFS Desktop: 0.16.2

Describe the bug
npm warns about a deprecated module called i18next-node-fs-backend

npm WARN deprecated i18next-node-fs-backend@2.1.3: replaced by i18next-fs-backend

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

Tokio's automatic cooperative task yielding feature can cause abruptly prevent a task from making further progress. A very busy connection driver might as a result end up failing to fairly serve transmits or timeouts, resulting in bad behavior (e.g. spurious timeouts or congestion window reduction) under heavy load.

Ideally tokio will expose some too

Describe the bug
Any number of peers past 1000 gets cut of in the toolbar
To Reproduce
Steps to reproduce the behaviour:

1. Connect to over 1000 peers (Enabling AcceleratedDHTClient and DHT server mode helps with that)
2. Look at the extension icon

Expected behaviour
The number does not get cut off

Screenshots
<img width="32" alt="Screen Shot 2021-08-05 at 12 37 28"

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/