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

Feature Request

What

为了让 Component 更好, 我设计了这个奖励机制. 凡是满足以下的条件的 bug 都会奖励 25 元的奶茶钱. 钱虽然不多, 重在感谢

Bug 满足条件

• 必须是能复现的
• 必须是 Component 项目中的bug, 不能是其他第三方库的, Idea Plugin 不算在其中. 因为插件属于帮助性的工具, 出问题也不影响你们开发
• 必须是没有其他人反馈过的 Bug
• 必须是我认可的：首先如果真的是 bug, 我不会为了这点钱死皮赖脸不承认. 因为之前看下来, 很多 bug 都是用户自己配置有问题或者代码写的不对引起的, 并不是框架的问题. 所以这个是需要我来判断的. 当然了, 你足够了解 Component 的话, 你自己也会知道到底是不是 Component 的问题

所有发现 bug 受奖励的名单, 会持续更新(

I suggest adding a few example usage of loginsrv as a Standalone microservice on the main page.

I think these should be added:

• Basics (help being available with loginsrv -help)
• HTTPd (Apache)
• NGINX
• Caddy 1
• Caddy 2

Fx applications may provide a fx.Printer with the fx.Logger option. Typical Fx applications include a logging module that provides something more powerful than a fx.Printer, such as a Zap logger. However, if this logging module has a dependency on other modules (eg Zap cores), then these lower level modules have

microbadger.com shows the size, number of layers, and version of a docker image.

It would be nice if badgen could support this service (I am not sure if an API is available).

https://images.microbadger.com/badges/image/node.svg
https://images.microbadger.com/badges/image/elastic

Architecture as well as workflows tend to be very complex within the appserver.io environment.
We need diagrams for better documentation and overview of architecture and request/response flow.

UAC:

• There MUST be workflow diagrams showing the request/response flow
• Diagrams MUST illustrate the difference in between servlet requests and legacy ones
• There MUST be architectural diagrams
• At lea

Currently the user of the tank-cli has no way of knowing what topics actually exist.
Any access to TANK beyond the usage of tank-cli should not be assumed & one should not have to ask for topic names etc.

There is a minor misspelling in the source file qri/api/context.go. The word "collissions" on line 14 should be changed to "collisions".

Currently the only Getting Started documentation is on keratin.tech and describes a short Docker command. The main documentation on keratin.github.io should also have a Getting Started section, optionally with Docker Compose.

Summary

This is the main tracking issue for DNSLink support. If there is a programmable DNS service out there, we should have support for it.

Ideally even doing things like detecting the provider from the domain name and doing the right thing.

Status

Great tool! Thank you. We're using it in a docker container and users really like it.

Two questions related to proxies:

1. Do you have advice on how best to make besticon use a proxy for fetching content? Perhaps I should submit a PR that modifies this: https://github.com/mat/besticon/blob/master/besticon/besticon.go#L417
2. Related question: when my app shows the icon identified