Mahadevan

There's something wrong with the multiple-select: https://deploy-preview-35857--twbs-bootstrap.netlify.app/docs/5.2/forms/select/#sizing  It's OK in the regular version: 

https://deploy-preview-35857--twbs-bootstrap.netlify.app/docs/5.2/forms/floating-labels/#readonly-plaintext The value in "Input with value" is not readable:  

For tables with `table-hover`, the bg color of the hovered row is not very different from bg of normal row. See: https://deploy-preview-35857--twbs-bootstrap.netlify.app/docs/5.2/content/tables/#hoverable-rows

Something like this, then? ```C int lfs_fs_resize(lfs_t *lfs, lfs_size_t new_block_count) { int err = 0; // read existing superblock from disk lfs_superblock_t superblock; err = lfs_dir_get(lfs, &dir, LFS_MKTAG(0x7ff, 0x3ff, 0),...

What about the service/method subject params? They should probably remain plain strings. Agree that other args/receivers should be pointers.

The user services built using nRPC could use this too. Also a few other such "core" services: * logging - nats.Publish() your logs to a "log" service * application metrics...

Protocol-wise, using a heartbeat message to indicate pause/resume looks good. I assume you're not going to leave it up to the user's client to decide when to call a `StreamCallSubscription.Pause()`...

The server might need control on how long the send() may take? At least as a timeout?

Thanks for your input! Right now, the situation is that you need to refer to `pg_settings` inorder to interpret the "settings" field of the JSON output. Additionally, the `pg_settings` has...

Does it behave properly without SSPI auth (with trust/md5/scram)? Collecting metrics from Postgres servers running on Windows has not been tested much. Bug reports welcome. Neither of the 2 popular...