I'm using TLS on etcd 3.3.12 and have a mix of etcd proxies and masters. The proxies don't seem to honour the --cipher-suites setting, as it ends up with ECDHE-RSA-AES256-GCM-SHA384 despite --cipher-suites=TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 being set.

$ pgrep -laf /usr/bin/etcd
21968 /usr/bin/etcd --listen-client-urls https://0.0.0.0:4000 --adv

Development Task

create a table:

CREATE TABLE `t` (
  `a` bigint(20) DEFAULT NULL,
  `b` bigint(20) DEFAULT NULL,
  KEY `idx` (`a`)
);

querying that table with an index hint which uses an undefined index aaa:

TiDB(root@127.0.0.1:test) > select /*+ force_index(aaa) */ * from t;
Empty set, 1 warning (0.00 sec)

TiDB(root@127.0.0.1:test) > show warnings;
+---

const XLSX = require('xlsx');

const wb = XLSX.utils.book_new();

const ws = XLSX.utils.json_to_sheet([]);

XLSX.utils.book_append_sheet(wb, ws, 'Bug sheet');

ws.A1 = { t: 's', f: 'square' };

XLSX.writeFile(wb, 'formula.ods');

The resulting .ODS file contains:

<table:table-cell table:formula="of:=square" office:value-type="string"><text:p>undefined</text:p></table

When adding a new data store database in Metabase it tries to connect first with SSL (if the driver supports SSL), and then without, in that order. If either connection succeeds, the database details are accepted as valid. Yes, you can add driver specific JDBC options to use SSL, but there is no good feed

Right now we have the following, which doesn't validatie the needs of a given view. This allows for any colors to be provided, not necessarily the ones that are required. I'd recommend making these color validations accurate, where for Gauge it would require the min and max for instance. I'm assuming these are required for gauge, that may be in error. Would be nice to provide swagger that p

Issue type:

[ ] question
[ ] bug report
[ ] feature request
[x] documentation issue

Steps to reproduce or a small repository showing the problem:

1. Open Getting started (https://typeorm.io/#/) in documentation
2. Hover the anchors and it will be marked as the examples below with undefined
   https://typeorm.io/#undefined/quick-start `https://typeorm.io/#/undefined/ins

PG 12 supports AS MATERIALIZED and AS NOT MATERIALIZED syntax for user controller of CTE materialization. For example:

WITH x AS MATERIALIZED (SELECT * FROM very_large_table) SELECT * FROM x;

With this syntax, the user can override the optimizer's default decision to not materialize that table (since it's only referenced once).

WITH x AS NOT MATERIALIZED (SELECT * FROM very_s

The documentation for Importing NDF format data does not mention that the method will not be supported in future as per the message in the 'prisma import' command...

"Warning: The prisma import command will not be further developed in the future. Please use the native import features of your database for these workflows. "

https://www.prisma.io/docs/prisma-cli-and-configuration/data-import

Environment

• PostgreSQL version: All
• PostgREST+ version: 6.0.2 (713b214)

Current state

Currently, Comment on Table

COMMENT ON SCHEMA todos IS
  'Todos object description';

generate a summary for all operations on this resource

 /todos:
    get:
      tags:
        - todos
      summary: Todos object description
      parameters:

But sum

The Installation Instructions in the examples README has a dud link to install the macOS version of the Realm mobile platform: https://realm.io/docs/realm-mobile-platform/get-started/

This link results in a 0 byte download for me (tried in Chrome 77, Safari 12.1.2, and curl).

I'm not sure what the canonical

https://github.com/pouchdb/pouchdb/blob/5bb2edebb47034cc74939882cb690070456e6f2e/docs/_includes/api/debug_mode.html#L9

Found this one while skimming the docs: currently at 7.1.1: what would be the up-to-date version of this warning?

Details for the issue

What did you do?

Select Table from the list, click "Modify Table" button, Add field "TestField", move field up or down.

What did you expect to see?

OK button enabled

What did you see instead?

OK button disabled: it remains enabled while modifying the table, but gets disabled when buttons "Move field up/down" are pressed just af

The grafana board seems to be outdated, a lot of the panels have no data, it seems to be missing in /debug/prometheus_metrics...

What version of Dgraph are you using?

v1.2.1

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, OS)?

Kubernetes 3 x 16gb 4cores, prometheus and grafana running locally.

Steps to reproduce the iss

Following the README for inserting new items on an array, gives error; insert is not existent; should be corrected to push

How to change color of menu bar and scrollings to dark color in darkest dark theme?
and light borders around the fields?
it looks strange in dark theme

There's no published benchmark for IOPS on S3 storage

Would it be possible to post this alongside the other benchmarks?

S3 storage would be super cheap way to get started because it's serverless (thus more folks would potentially use gun.js)

Thank you for the useful service. I would like to see more Auth/ABAC for startup usage, right now I'm using a centralized database because it's uncle

必须先将通过STable创建的表先删除，然后才能删除超级表。当级联表很多时就麻烦了，除非写代码来删除。

The encryption section in Java docs https://realm.io/docs/java/latest/#encryption leads to an example that doesn't properly provide a best practice solution for how to store keys used for encryption.

Throw NullPointException when INSERT column and values mismatch.
It is better to throw suitable SQLException for JDBC-driver and proxy.

The tasks are:

• Throw suitable SQLException for JDBC-driver.
• Report suitable error packet with MySQL proxy.
• Report suitable error packet with PostgreSQL proxy.

I wish to suggest that you expand benchmark results for ArangoDB to cover graph queries, for a multi-node clustered configuration, perhaps guided by:

• Linked DataBase Council (LDBC), the graph & RDF benchmark reference
• Graph Benchmark: Comparing and Understanding Graph Databases

You do provide [NoSQL Performance Benchmark 2018 – Mongo

Issue description

GitHub changed how issue templates work. We should update ours:

You are using an old version of issue templates. Please update to the new issue template workflow. Learn more

See: https://help.github.com/en/article

Asynchronously returns the only element of a sequence, and throws an InvalidOperationException exception if there is not exactly one element in the sequence.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d3b7deb0-a592-b6dc-1564-fba73a4dcb4c
• Version Independent ID: 1836b7d9-419e-d8a4-51ff-09f504a56462
• Content: [E

pgcli depends on humanize which is https://github.com/jmoiron/humanize.

The current version has a slightly odd behavior of rounding down unexpectedly:

In [11]: humanize.naturaltime(datetime.timedelta(seconds=120))                                                                         
Out[11]: '2 minutes ago'

In [12]: humanize.naturaltime(datetime.timedelta(seconds=119.9))