microservices
Here are 3,544 public repositories matching this topic...
Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.
{ "error_description": "You must use HTTPS", "error": "access_denied" }
I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.
Currently it's at cmd/mesh 43.7%.
-
Updated
Mar 28, 2020 - Java
It would be nice to see a Jaeger tracer interface. If this isn't already in the works (I searched but didn't see anything), I could attempt a PR.
-
Updated
Mar 7, 2020 - Java
-
Updated
Mar 30, 2020 - C#
现象:使用ONS连接阿里云RocketMq,可支持阿里云RocketMQ定时消息(不是延时消息) ,使用rocketmq stream binder则不能支持,只能支持到延时消息 。
Hi there! I wanted to propose adding the following badge to the README to indicate how many TODO
comments are in this codebase:
The badge links to tickgit.com
which is a free service that indexes and displays TODO comments in publi
Issue Description
Type: feature request
Describe what happened (or what feature you want)
On the service details page, click the return page, and the entered search criteria disappear. You need to re-enter the search criteria every time you return to view the service details.
Describe what you expected to happen
Return to previous page to keep query criteria.
How t
Hello,
I found recently that grpc-go was working on an xds implementation for service discovery, which is great.
Using current HEAD, I tried to get both resolver and balancer working. I managed to get something more or less working for resolver by reversing code & tests code on Gist but as for balancer, I didn't.
I unders
-
Updated
Mar 12, 2020
-
Updated
Mar 26, 2020
Reported on the jib-users Google group.
Error while caching an application layer. It was trying to atomically move (rename) the directory .../tmp/3227117988474356011
to .../layers/<some sha256 hash>
. It may be that atomic move is not supported on the filesystem. Interestingly, it is a Unix filesystem.
at sun.nio.fs.UnixC
i find the root cause of this issue
see config/Docker.file
HEALTHCHECK --interval=10s --timeout=3s CMD curl -f http://localhost:8888/actuator/health || exit 1
values of 10s for interval and 3s for connect timeout is both too small, when the docker machine have a bit lo
Hello,
We're using etcdv3 with a self-signed cert. so we can't use the default micro binary although etcdv3 support has been built in since v1.11.0
Is there any approach to access it without rebuilding the micro binary?
If the rebuild is needed, where should I put the "tls.Config initialize" code?
micro version: 1.11.0
Thanks.
refer, #210 #178
update:
It seems mi
What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.
Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.
I tried deleting everything other than Lambda, API Gateway and S3, but then I began
The default value of falcon.RequestOptions.auto_parse_qs_csv
was changed to False
in v2.0 and handled in falconry/falcon#842 and falconry/falcon#1318.
The FAQ item https://falcon.readthedocs.io/en/stable/user/faq.html#how-do-i-consume-a-query-string-that-has-a-json-value assumes the old default value and needs an update.
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
See https://javadoc.io/ it should be connected to releases on Maven Central and it is version aware, we can link from website.
In what area(s)?
/area test-and-release
Describe the feature
This issue is to create separated dapr system processes as a separate docker image.
system process | proposed docker image name |
---|---|
operator/injector | operator |
sentry | sentry |
placement | placement |
Note: operator/injector are used for K8s, so that we can put
-
Updated
Mar 31, 2020 - JavaScript
**Do you want to request a feature or report a bug?
Feature?
What is the current behavior?
Session object ACLs require both the key and the api_id field of the ACL definition to match.
If they mismatch the API does not throw an error.
What is the expected behavior?
The Gateway API should report the discrepancy to stop the token from being generated.
A recent breakage on master for quick-install YAML was not detected until developers manually ran the quick-install YAML. One aspect is that developers can neglect to update the quick-install YAML. #10425 follows up on fixing that.
The second aspect is that we should automate deployment of the quick-install YAML from the repo during CI for basic validation that it works.
I briefly grepped fo
-
Updated
Mar 30, 2020 - Go
-
Updated
Jul 18, 2019
Describe the bug
Please provide details of the problem, including the version of Spring Cloud that you
are using.
On the docs page for spring-cloud-netflix (https://spring.io/projects/spring-cloud-netflix), first line shows as "Unresolved directive in - include::_attributes.adoc[]".
Expected reference can be seen in the source of the docs (intro.adoc, sagan-index.doc).
**Sam
I can find documentation for using contexts in v1
but they are not listed in the topnav of the v3 page, leading me to believe that they are no longer valid or have changed. At least the With
functions seem to have been changed.
From all the documentation available (incl. v1) it isn't clear to me as a reader how to pass the JWT user-id from the `J
Improve this page
Add a description, image, and links to the microservices topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the microservices topic, visit your repo's landing page and select "manage topics."
I think it is worth mentioning that the solution stated Catching unresolved and rejected promises is not always valid. what I mean is that if a promise is caught on a later turn of the Node.js event loop, then probably throwing an error on this global catch is not a good idea. I am wondering how this is counted as best practice while obviously from the node official documentation it should