Hey guys

I am learning and using seata recently, this is a great thing.

Component
spring-cloud-alibaba-seata:0.9.0.RELEASE

Question
I see that the seata source code contains the spring boot web dependency. **Is there a plan to support [sp

Issue Description

引入nacos后，导致服务启动失败
异常信息： Could not resolve placeholder 'project.version' in value "${project.version}"

Describe what happened (or what feature you want)

异常栈：

2020-08-05 15:47:11.844 [ERROR] [main] [org.springframework.boot.SpringApplication] @@@traceId=@@@ Application startup failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Erro

The forward plugin has some rather convoluted config setups. I.e. functions on Proxy that call other functions on the lower bits (Transport and Healthcheck). For some reason I can't remember HealthCheck as an interface; where in reality we only have one impl. here.

This all looks over-engineered and ready to be massively simplified - hopefully with a reduction in LOCs.

[zosy@localhost:~]% rpm -qa zenmap
zenmap-7.60-1.noarch

gnome doesn't use gksu instead of pkexec, so i made a patch.
su-to-zenmap-fix-gnome-root.patch.txt

add com.gnome.pkexec.zenmap.policy to /usr/share/polkit-1/actions should works fine.

[com.gnome.pkexec.zenmap.policy.txt](https://github.com/nmap/n

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

Request: https://twitter.com/Venkatesh_CHN/status/1298826672485961730

Problem Summary:

• There was a change to Steeltoe quite some time ago to comply with the Spring spec for returning HTTP 503 in cases of HealthStatus.DOWN or HealthStatus.OUT_OF_SERVICE.

• For 500 series errors, however, HWC is configured by default to substitute a canned message for the http response content - so, instead of getting back any failed health checks, the monitor just gets a 503 w