-
Updated
Jul 15, 2022 - JavaScript
microservices
Microservices are an architectural and organizational approach to software development where software is composed of small independent services that communicate over well-defined APIs. These services are owned by small, self-contained teams.
Microservices architectures make applications easier to scale and faster to develop, enabling innovation and accelerating time-to-market for new features.
Here are 7,057 public repositories matching this topic...
-
Updated
Aug 1, 2022 - TypeScript
-
Updated
Aug 2, 2022 - Go
-
Updated
Aug 2, 2022 - Java
Is your feature request related to a problem? Please describe.
A clear and concise descripti
Which Component
spring-cloud-starter-stream-rocketmq
Describe the bug
When hot deployment in eclipse throw MQClientException: The producer group[mygroup] has been created before
To Reproduce
Steps to reproduce the behavior:
- Spring boot application with devtools in Eclipse
- Send message using org.springframework.cloud.stream.function.StreamBridge.send
- Modify any cod
-
Updated
Aug 2, 2022 - C#
-
Updated
Aug 2, 2022 - Go
-
Updated
Jul 30, 2022 - Go
In what area(s)?
/area runtime
What version of Dapr?
1.8.0
Expected Behavior
Get metadata through grpc
Actual Behavior
What problem is the feature used to solve?
kratos does not provide client-side request retry logic
References
- [http retry](https://github.com/gojek/heimdall/tree/master/httpclient)
- [gprc retry](https://github.com/grpc-ecosystem/go-grpc-middleware/tree/master/retry)
Bump to Recharts V2
Renovate tried to bump Recharts from v1 to v2 but it looks like there's some breaking changes in the library that need fixing up in #12476
Let's bump to the latest library and fix up some of the Typescript errors that have started occurring part of the breaking changes.
It looks like there's absolutely 0 documentation on migration, recharts/recharts#2333 so could be
-
Updated
Jun 29, 2022
-
Updated
Aug 1, 2022 - Go
-
Updated
Jul 15, 2022 - Java
-
Updated
Aug 2, 2022 - Python
Background
目前使用qiankun2.x的版本,业务提出需求在发布新的版本时候,期望可以不刷新页面(主应用暂时不考虑)进行该系统的热重载。类似于pc端的热更新,期望qiankun可以导出unload方法,完全销毁app的生命周期,业务系统再次将其重载。
Proposal
- 翻看源码发现不能热更新的原因是因为
import-html-entry中缓存了embedHTMLCache qiankun在importEntry时,如果已经获取过html资源,每次获取的都是内存中的html,以至于script & style也是缓存的- 我的解决方案是,在import-html-entry中导出根据app去清除缓存的钩子函数
- 在qiankun中包裹其方法,根据single-spa的appStatus进行卸载应用
-
Updated
Aug 2, 2022 - Java
Today the jib.to.image is configured statically in a Gradle task or via cli arguments. This only works in very simple scenarios where Gradle is really only build/pushing the image or using static versions that are known before Gradle is invoked.
In my case, and especially important for local reproducible workflows, Gradle is building up all the JARs etc that are going into the image and versi
-
Updated
Jul 22, 2022 - Go
-
Updated
Mar 1, 2022 - Java
-
Updated
Jul 20, 2022 - JavaScript
-
Updated
Jul 27, 2022
Current State
We currently hardcore the APISIX version in the blog or doc, which has misled some newcomers when they read an old blog version. This also makes updating the latest APISIX version in the doc harder, because we need to change several places.
Desired State
Let's add a static file containing the version numbers, and provide a simple one-liner command to get the version numbe
Sometimes it might be handy to easily get a header's value as int, where validation errors would automatically result in an HTTP 400, along the lines of req.get_header_as_datetime & [req.get_param_as_int](https://falcon.readthedocs.io/en/stable/api/request_and_response_wsgi.ht
-
Updated
Jul 28, 2022 - Java
-
Updated
Jun 27, 2022 - Go
On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.
For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.
But the upstream APIs teams just want to know the global time spent in Tyk interna
- Wikipedia
- Wikipedia


expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/
actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc