Is your feature request related to a problem? Please describe.
The {{< highlight none >}} :~q:foo:bar {{< / highlight >}} blocks don't work on GitHub. It's confusing and makes the code examples almost useless on GitHub itself. And also in your code editor if you have Markdown syntax highlighting with embedded highlighting for nested code.

Describe the solution you'd like

It'd be ne

Issue Description

I updated echo in one of my projects. After that my static configuration didn't work without changes. Before it automatically resolved to an existing index.html. After that I had to point to that file.

My code was something like that:

docsGroup := e.Group("")
docsGroup.Static("/", "docs")

In docs is an index.html which was delivered when no path was given

The core documentation on how to make requests says to use xxxNow to make request from a client, but those methods are deprecated, e.g., getNow.

CDNJS requires a certain amount of manual review and moderation. This review is required both to allow new projects to be added to the project, and to handle certain types of project changes which can't be automatically imported.

This issue is a place to discuss how we might eliminate this requirement in the future.

I believe the goal of this project should be to take everything which requir

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

See http://blog.erlang.org/ssl-logging-in-otp-22/ for a full description.

One could enable debug logging in Cowboy to see all the packets transmitted and what Cowboy thinks of them, something like that. Could make some client issues obvious in particular.

there was an issue discussed in the #ponzu slack channel where knowing the order in which content type's item.Hookable methods are executed may have helped a lot. this helps users determine the state of the database and what is available at what time.

documentation would be great to mention this order (note the hook invocations):
https://github.com/ponzu-cms/ponzu/blob/ec7b5b2bab2cad13db

I‘v noticed that there is no Etag returned in static files response , any plans to add support for it?
Or, add a config item for it.

Do you want to request a feature or report a bug?
I guess is more feature request

What is the current behavior?
When the <> ... </> short form of fragments used with typescript, tsc gives the error:

`TS17016: JSX fragment is not s

Hi. First of all, thanks for this work!

While working with this code is noticed some unexpected behavior, which is caused by a difference between documentation and code. Not sure which of the two are wrong.

According to https://nghttp2.org/documentation/types.html#c.nghttp2_on_data_chunk_recv_callback

The implementation of this function must return 0 if it succeeds. **If nonzero is return

非常感谢大家对 SOFAStack 开源的关注和支持，这是我们前进最大的动力。

收集目的

• 了解 SOFAStack 的使用场景以便更好的规划技术路线
• 聆听社区的不同声音，让 SOFAStack 变得更好
• 吸引更多的开源爱好者参与贡献，共同打造 SOFAStack

收集方式

请按如下参考格式回复本 Issue 进行登记：

* 公司/组织名称：蚂蚁金服
* 地点：中国杭州
* 网址：http://www.antfin.com
* 使用组件及场景：全套金融级分布式中间件
* 联系方式：[email protected]

展示

我们会定期同步信息至「Awesome SOFA」的用户列表中。

服务

A Spring Boot user has reported a problem with Spring Boot's reference documentation linking to Jetty's documentation. Spring Boot's reference documentation links to the Jetty documentation for the specific version of Jetty that it built against. For example, the documentation for Spring Boot 2.2.4 links to https://www.eclipse.org/jet

I am struggling to test a verticle isolated and all documentation and examples found only show how to test rest endpoints.

Something as simple as this, always fails with timeout

    @Rule
    public RunTestOnContext rule = new RunTestOnContext();

    @Rule
    public Timeout timeout = Timeout.seconds(5L);

    @Test
    public void should_run_verticle(TestContext context) {

• The server SHOULD limit the maximum number of resources to push.
• The depth of the selector SHOULD also be limited by the server.

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

1. The example configuration of tunnel.yml: indent charaters uses both tab and spaces, which makes it not parsable.
   2 After fixed 1, client throws the following error:

configuration error: tls invalid protocol "sni"

Client version: 2.1

https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns/

The date at which the notification is no longer valid. This value is a UNIX epoch expressed in seconds (UTC). If the value is nonzero, APNs stores the notification and tries to deliver it at least once, repeating the attempt as needed until the specified d

See #226