It's not clear from the website's documentation, or the --help output, how to do the following equivalent curl task:

Post a raw JSON query to ElasticSearch:

curl \
    --header "Content-Type: application/json" \
    --request POST \
    --data '{ "_source": [ "restricted_countries.*" ], "query": { "match_all": {} }, "size": 1000 }' \
    'http://localhost:9200/_search'

T

When I set boolean options using let, they accept v:true but not v:false.
Nvim says E521: Number required: &ignorecase = 'false'.

• nvim --version: NVIM v0.5.0-456-gdeb4566ca
• vim -u DEFAULTS (version: ) behaves differently? NO
• Operating system/version: Debian testing, linux-image-5.5.0-1-amd64
• Terminal name/version: alacritty 0.4.2
• $TERM: screen-256color

Steps

I'm trying to achieve something similar to https://docs.bons.ai/examples.html#examples-overview
but what I'm getting is when section is selected in the menu it will go to the content of that section but not the title (beginning of a section) - title will be under the header.

Any tips on that?

Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.

Steps to reproduce the behavior

1. Setup Strapi with MongoDB configuration.
2. Create a collection (resource).
3. Give findOne access to the public.
4. Send a request to /resource-name/any-invalid-id.

Expected behavior
404 response.

**Sys

There is a typo in "Securely transporting stuff: HTTPS explained":

So, https servers two main purpose

must be

So, https serves two main purpose

Problem

Here are the types for a ts test https://github.com/paularmstrong/normalizr/blob/master/typescript-tests/entity.ts#L11

Since in the normalized entities all relationships are all id type this should be string instead of User

{
  ...
  user: string
}

Jumping to a subsection via the sidenav will sometimes cause the page header to overlap the anchor point. When navigation is working correctly, there's a perceptible flicker/jump, so I'm guessing javascript is being used to calculate the offsets. Looking at mkdocs's docs, this isn't an issue. I'm wondering if this is something that will be fixed by upgrading mkdocs (#6623), or if it's a theme issu

版本号

1.8.5

什么问题

node server/install.js
Error: (node:28710) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.

经查询mongoos官网说明,在5.7版本中使用了较高版本的MongoDB driver3.3.x，其中useUnifiedTopology为过期的方法，

It looks like most of the advice from the OWASP REST Cheat Sheet is discussed in this API-Security-Checklist, but OWASP talks about the importance of CORS, which is not mentioned at all in this API-Security-Checklist. Probably good to make mention. Also, the OWASP REST Cheat Sheet provides a bit more guidance regarding validation that might be good to incorporate.

https://github.com/OWASP/Che

Your example of a well structured URL:

https://api.contoso.com/v1.0/people/jdoe@contoso.com/inbox

in URL Structure includes PII in the URL which is prohibited in PII parameters

Is your feature request related to a problem

Coming from this issue: tiangolo/fastapi#817

The docs have some sections with functions using *, in the parameters.

It is explained here: https://fastapi.tiangolo.com/tutorial/path-params-numeric-validations/#order-the-parameters-as-you-need-tricks

But in other sections like: https://fastapi.tiangolo.com/tutor

While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

from wxpy import *
bot = Bot(cache_path=True) # 保持登陆状态
@bot.register()
def reply_friend(msg):
print('接收：' + str(msg)) #打印接收到的消息
msg.reply("hello world") #回复消息
msg.reply_image('12.png') #回复图片
msg.reply_file(‘12.png') #回复文件
msg.reply_file('1.txt') #回复文件
embed()
以上是一个例，期望运行结果是不管谁发送过来的消息都直接回复，但是第六行可以发送消息成功，第七行可以发送图片成功，第八行把图片已文件的形式发送也可以成功，但是第九行文件就是发送不了，发送1.zip也是发送不了

Feature Summary ✨

When a user presses the button to Create a study guide, study guide creation page should be shown to the user.

Why do we need this?

Essential feature as withou

Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

When generating documentation for a class that extends another, and the base class has it's constructor documented, JSDoc generates duplicated documentation pages for the class that is being extended.

Input code

I was able to reproduce the bug on a minimal example project containing 2 files:

classes/Foo/index.js

/**
 * Represents foo.
 */
export class Foo { 
    /**
   

Custom error formatter must have now 5 arguments instead of the old 4. These changes were introduced here on #1652

When migrating from 0.19 to 1.1.0 I had issues on a custom error formatter because the original_exception argument was introduced but that change was not documented on the upgrading guide.

I'm submitting a ...

• bug report
• [ X] feature request
• question

PostGraphile version: 4.4.4

postgraphile should honor variables in query string as defined in https://github.com/graphql/express-graphql#http-usage when the query is provided as post body.

with the following exampl

Expected behavior

The path defined for example in the tsconfig file of the web3-providers-http package is misleading and should get corrected if possible in a non-breaking manner.

Actual behavior

The defined path is web3-providers instead of web3-providers-http.

Steps to reproduce the behavior

1. Open a tsconfig file from one of the provider packag

I'm upgrading a build environment from python 2 to python 3 and noticed that endpoints with seeded random numbers are not returning the same values. It seems to be related to usage of randint:
https://github.com/postmanlabs/httpbin/blob/f8ec666b4d1b654e4ff6aedd356f510dcac09f83/httpbin/core.py#L1448

It seems like randint is not seed safe and it looks like only random() is: https://bugs.python.o

I couldn't load and build the project using the latest qt creator and the wiki guide for building, i think it's out dated, please update and add more details for beginners who want to contribute.

有很多开发者朋友问我有没有类似的前台项目、后台管理项目的种子项目，其实都是类似的，区别在于这些项目需要模版引擎(不建议使用JSP)和静态资源(css、js、img)的支持，稍微调整下即可适用，按照MVC的分层来说的话差异的只是视图层，下面是基于Thymleaf模板引擎的改造步骤，供参考。

1. 加入Thymleaf模板引擎依赖

<dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-thyme

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

Currently, we ask contributors to strive for consistency with existing code, but it would be helpful to clarify the following regarding docstrings:

• Docstrings should begin with a short (~70 characters or less) summary line that ends in a period.
• The summary line should begin immediately after the opening quotes (do not add a line break before the summary line)
• The summary line should de

The Go documentation states the following on http.Request.RemoteAddr:

The HTTP server in this package sets RemoteAddr to an "IP:port" address before invoking a handler.

Therefore, you could expect that a code like this is correct:

package main

import (
	"fmt"
	"net"
	"net/http"

	"github.com/go-chi/chi"
	"github.com/go-chi/chi/middleware"
)

func main() {
	r