Git Product home page Git Product logo

seata-go-server's People

Contributors

billlucky avatar tinycedar avatar zhangxu19830126 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

seata-go-server's Issues

Support Service Registry with Etcd

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to etcd so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

Support Service Registry with Consul

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to consul so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

Support Service Registry with Nacos

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to nacos so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

Support Service Registry with Redis

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to redis so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

K8S Operator

Why you need it?

The goal of TaaS is to become a Cloud-Native seata server-side solution implementation..

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Support Service Registry with Sofa

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to sofa so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

Support TiKV as meta Storage

Why you need it?

TiKV is a reliable high performance, widely used KV storage.

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Support S3 as meta Storage

Why you need it?

Use s3 interface-compatible object storage as taas metadata storage

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

x509 certificate invalid when docker compose up -d

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

run docker compose up -d but can't pull image from https://seata.io

➜  seata-go-server git:(master) docker compose up -d
[+] Building 1.3s (13/13) FINISHED
 => [seata-proxy internal] load build definition from Dockerfile                                                                  0.0s
 => => transferring dockerfile: 65B                                                                                               0.0s
 => [seata1 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata2 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata-dashboard internal] load build definition from Dockerfile                                                              0.0s
 => => transferring dockerfile: 69B                                                                                               0.0s
 => [seata3 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata-proxy internal] load .dockerignore                                                                                     0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata1 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata2 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata-dashboard internal] load .dockerignore                                                                                 0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata3 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => CANCELED [seata-proxy internal] load metadata for seata.io/seata-go-proxy:latest                                              0.9s
 => CANCELED [seata2 internal] load metadata for seata.io/seata-go-server:latest                                                  0.9s
 => ERROR [seata-dashboard internal] load metadata for seata.io/seata-go-dashboard:latest                                         0.8s
------
 > [seata-dashboard internal] load metadata for seata.io/seata-go-dashboard:latest:
------
The new 'docker compose' command is currently experimental. To provide feedback or request new features please open issues at https://github.com/docker/compose-cli
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://seata.io/v2/seata-go-dashboard/manifests/latest: x509: certificate is valid for *.coding-pages.com, coding-pages.com, not seata.io

Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

start compose as expected

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. git clone repo
  2. run docker compose up -d

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version :
  • OS :
  • Others:

seata.io/seata-go-server

docker-compose up -d
Pulling seata2 (seata.io/seata-go-server:)...
ERROR: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\n<html lang="en">\n\n\t<meta charset="UTF-8">\n\n\n <script src="//cdn.jsdelivr.net/npm/js-cookie@2/src/js.cookie.min.js"></script>\n\t<script>\n window.rootPath = '';\n window.defaultLanguage = 'en-us';\n var lang = Cookies.get('docsite_language');\n if (!lang) {\n lang = 'en-us';\n }\n window.location = window.rootPath + '/' + lang;\n </script>\n\n"

部署完之后具体如何在golang程序中使用?可以写个client文档吗?

Why you need it?

Is your feature request related to a problem? Please describe in details

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

代码疑问

代码中存在这样的情况:
代码片段一:

if !tc.leader {
		return
	}

	c := acquireCMD()
	c.cmdType = cmdACKB
	c.ack = ack

	tc.cmds.Put(c)

代码片段二:

if !tc.leader {
		cb(false, meta.ErrNotLeader)
		return
	}

	c := acquireCMD()
	c.cmdType = cmdLockable
	c.resource = resource
	c.gid = gid
	c.lockKeys = lockKeys
	c.boolCB = cb

	err := tc.cmds.Put(c)
	if err != nil {
		cb(false, err)
		releaseCMD(c)
	}

代码片段一中没有判断消息入队列失败情况,代码片段二又判断了入队列失败的情况。
为啥会存在处理不一致的情况呢?代码片段一中的情况是不是遗漏了入队列失败情况下对消息的回收?

Support Service Registry with Eureka

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to eureka so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

怎么用这个东西,有client吗

Why you need it?

Is your feature request related to a problem? Please describe in details

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Support Service Registry with Zookeeper

Why you need it?

Integrated with seata

How it could be?

Register the taas proxy address to zookeeper so that the seata client can discover it.

Other related information

Add any other context or screenshots about the feature request here.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.