check & build failed (linux-musl)

[quuc]

Describe the bug
A clear and concise description of what the bug is.

I had some problems with the check & build process.
在 cargo check 的过程中报错了。
报错内容跟 delicate-utils 的依赖 poem 有关。

[root@2cb22c0d29ba delicate]# cargo check
   Compiling delicate-scheduler v0.1.0 (/delicate/delicate-scheduler)
    Checking delicate-utils v0.1.0 (/delicate/delicate-utils)
error[E0599]: the method `as_dyn_error` exists for reference `&ParseCookieError`, but its trait bounds were not sati
sfied
   --> delicate-utils/src/error.rs:28:13
    |
28  |     #[error("Parse Cookie fail.")]
    |             ^^^^^^^^^^^^^^^^^^^^ method cannot be called on `&ParseCookieError` due to unsatisfied trait bound
s
    |
   ::: /root/.cargo/registry/src/github.com-1ecc6299db9ec823/poem-1.0.19/src/error.rs:253:1
    |
253 | pub enum ParseCookieError {
    | -------------------------
    | |
    | doesn't satisfy `ParseCookieError: AsDynError`
    | doesn't satisfy `ParseCookieError: StdError`
    |
    = note: the following trait bounds were not satisfied:
            `ParseCookieError: StdError`
            which is required by `ParseCookieError: AsDynError`
            `&ParseCookieError: StdError`
            which is required by `&ParseCookieError: AsDynError`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `delicate-utils` due to previous error

I tested it in docker environment.
我分别用了 rust:alpine 和 rust:latest 来测试，结果都出现了一样的错误。

To Reproduce
Steps to reproduce the behavior:

1.install docker

apt install docker.io

2.pull & run rust:alpine (x86_64-unknown-linux-musl)

docker run -it --name rs-musl rust:alpine

3.git clone this repo

git clone --depth=1 https://github.com/BinChengZhao/delicate

4.copy env file

cd delicate
cp template.env .env

5.install deps

apk update
apk add mariadb-dev postgresql-dev openssl-dev musl-dev

6.run cargo command

cargo check

7.error (unsatisfied trait bounds)

   --> delicate-utils/src/error.rs:28:13
    |
28  |     #[error("Parse Cookie fail.")]
    |             ^^^^^^^^^^^^^^^^^^^^ method cannot be called on `&ParseCookieError` due to unsatisfied trait bounds

8.exit this container and run rust:latest (x86_64-unknown-linux-gnu)

docker run -it --name rs-stable rust:latest

9.run container & check deps

docker exec -it rs-stable bash

apt list --installed | grep -E "mysql|mariadb|libssl|libpq"

default-libmysqlclient-dev/now 1.0.7 amd64 [installed,local]
libmariadb-dev-compat/now 1:10.5.12-0+deb11u1 amd64 [installed,local]
libmariadb-dev/now 1:10.5.12-0+deb11u1 amd64 [installed,local]
libmariadb3/now 1:10.5.12-0+deb11u1 amd64 [installed,local]
libpq-dev/now 13.4-0+deb11u1 amd64 [installed,local]
libpq5/now 13.4-0+deb11u1 amd64 [installed,local]
libssl-dev/now 1.1.1k-1+deb11u1 amd64 [installed,local]
libssl1.1/now 1.1.1k-1+deb11u1 amd64 [installed,local]
mariadb-common/now 1:10.5.12-0+deb11u1 all [installed,local]
mysql-common/now 5.8+1.0.7 all [installed,local]

10. copy env file & cargo check

I encountered the same error as the alpine (rust musl) container.

Expected behavior
A clear and concise description of what you expected to happen.

1.我想要在 alpine 容器里运行delicate。
I want to run it in a musl environment.

2.我希望开发者能提供预编译的版本。
这样子普通用户就不用操心编译的事情了。

I would like to get the musl binary on the release page.

3.我希望核心配置能在编译后进行修改，而不是重新配置，重新编译。
I would like to be able to change the configuration after compilation rather than recompile it with an .env file.

For example,
template-env.toml

[database]
# pssql or mysql
backend = "postgre"
url = "..."

[redis]
enabled = true

# IP address or hostname
host = "redis-docker"

port = 6379
passwd = "ItIsRedisPassword"

Screenshots

[BinChengZhao]

@cu233

Thank you so much for your use & feedback!

The specific problem has been pinpointed because poem had a breaking change and needed all downstream dependencies to be actively compatible.

I've fixed it.

Your requirements are very reasonable, I will record them in the roadmap one by one, because I am still writing the new feature actuator, and probably the requirements will be finished by early 2022.

If you have time, I hope you can contribute to delicate, for example by creating a docker image, it would be my pleasure if you have the chance.

如果你能参与进来，这将是我的荣幸。

We can use the github-discuss feature to discuss the future of the project asynchronously and contribute to the Rust ecosystem together.

[makorne]

I've fixed it.

Looks the issue is still alive :)

I`ve just tried to build V1.31, #https://github.com/BinChengZhao/delicate/releases/tag/V1.3.1 with poem 1.0.22 (bump 1.05 in utils cargo.toml) :

error[E0599]: the method `as_dyn_error` exists for reference `&ParseCookieError`, but its trait bounds were not satisfied
   --> delicate-utils/src/error.rs:28:13
    |
28  |     #[error("Parse Cookie fail.")]
    |             ^^^^^^^^^^^^^^^^^^^^ method cannot be called on `&ParseCookieError` due to unsatisfied trait bounds
    |
   ::: /home/f/.cargo/registry/src/github.com-1ecc6299db9ec823/poem-1.0.22/src/error.rs:253:1
    |
253 | pub enum ParseCookieError {
    | -------------------------
    | |
    | doesn't satisfy `ParseCookieError: AsDynError`
    | doesn't satisfy `ParseCookieError: StdError`
    |
    = note: the following trait bounds were not satisfied:
            `ParseCookieError: StdError`
            which is required by `ParseCookieError: AsDynError`
            `&ParseCookieError: StdError`
            which is required by `&ParseCookieError: AsDynError`

[BinChengZhao]

I've fixed it.

Looks the issue is still alive :)

I`ve just tried to build V1.31, #https://github.com/BinChengZhao/delicate/releases/tag/V1.3.1 with poem 1.0.22 (bump 1.05 in utils cargo.toml) :

error[E0599]: the method `as_dyn_error` exists for reference `&ParseCookieError`, but its trait bounds were not satisfied
   --> delicate-utils/src/error.rs:28:13
    |
28  |     #[error("Parse Cookie fail.")]
    |             ^^^^^^^^^^^^^^^^^^^^ method cannot be called on `&ParseCookieError` due to unsatisfied trait bounds
    |
   ::: /home/f/.cargo/registry/src/github.com-1ecc6299db9ec823/poem-1.0.22/src/error.rs:253:1
    |
253 | pub enum ParseCookieError {
    | -------------------------
    | |
    | doesn't satisfy `ParseCookieError: AsDynError`
    | doesn't satisfy `ParseCookieError: StdError`
    |
    = note: the following trait bounds were not satisfied:
            `ParseCookieError: StdError`
            which is required by `ParseCookieError: AsDynError`
            `&ParseCookieError: StdError`
            which is required by `&ParseCookieError: AsDynError`

@makorne
Sorry, it's because I didn't hit tag in time before, this fix can be reflected on master,

thanks for your feedback! Can using V1.3.2 now ~
:)

[makorne]

Thank you!

I checked it having set all your .delicate-rs.com domains to localhost.

But still infinite LOADING ( although I turned off cors).
api/user/check responded Unauthorized but no login form loads.

Checked with curl:

curl 'http://api-local.delicate-rs.com:8090/api/user/check' \
  -X 'POST' \
  -H 'Connection: keep-alive' \
  -H 'Content-Length: 0' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36' \
  -H 'Origin: http://delicate-rs.com:8000' \
  -H 'Referer: http://delicate-rs.com:8000/' \
  -H 'Accept-Language: en-US,en;q=0.9' \
  --compressed -v
*   Trying 127.0.0.1:8090...
* Connected to api-local.delicate-rs.com (127.0.0.1) port 8090 (#0)
> POST /api/user/check HTTP/1.1
> Host: api-local.delicate-rs.com:8090
> Accept-Encoding: deflate, gzip, br
> Connection: keep-alive
> Content-Length: 0
> Accept: application/json, text/plain, */*
> User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36
> Origin: http://delicate-rs.com:8000
> Referer: http://delicate-rs.com:8000/
> Accept-Language: en-US,en;q=0.9
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< content-length: 0
< date: Mon, 08 Nov 2021 04:13:37 GMT
< 
* Connection #0 to host api-local.delicate-rs.com left intact

I dont understand how you can develop it on your laptop :)

[BinChengZhao]

Thank you!

I checked it having set all your .delicate-rs.com domains to localhost.

But still infinite LOADING ( although I turned off cors). api/user/check responded Unauthorized but no login form loads.

Checked with curl:

curl 'http://api-local.delicate-rs.com:8090/api/user/check' \
  -X 'POST' \
  -H 'Connection: keep-alive' \
  -H 'Content-Length: 0' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36' \
  -H 'Origin: http://delicate-rs.com:8000' \
  -H 'Referer: http://delicate-rs.com:8000/' \
  -H 'Accept-Language: en-US,en;q=0.9' \
  --compressed -v
*   Trying 127.0.0.1:8090...
* Connected to api-local.delicate-rs.com (127.0.0.1) port 8090 (#0)
> POST /api/user/check HTTP/1.1
> Host: api-local.delicate-rs.com:8090
> Accept-Encoding: deflate, gzip, br
> Connection: keep-alive
> Content-Length: 0
> Accept: application/json, text/plain, */*
> User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36
> Origin: http://delicate-rs.com:8000
> Referer: http://delicate-rs.com:8000/
> Accept-Language: en-US,en;q=0.9
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< content-length: 0
< date: Mon, 08 Nov 2021 04:13:37 GMT
< 
* Connection #0 to host api-local.delicate-rs.com left intact

I dont understand how you can develop it on your laptop :)

I've helped a few community friends build before, and basically there are fewer obstacles, so let me determine what the problem is.

First, let me share my local situation: the

web-local.delicate-rs.com
api-local.delicate-rs.com

Adjust the .env (delicate-schduler) configuration, adjust delicate-web/.env
and delicate-web/src/utils/envConfig.js.

You can try visiting the address

http://{your domain}/api/tasks_state/one_day
In your browser.
(Example: http://api.delicate-rs.com:8090/api/tasks_state/one_day)

If the server side corresponds properly, check delicate-web, check the configuration I mentioned above, you can temporarily change the local (delicate-web/src/utils/envConfig.js.) environment addresses to your own local address first.

[makorne]

I just try using your setting, so my hosts file has
127.0.0.1 www.delicate.com api.delicate.com delicate.com api-local.delicate.com api-local.delicate-rs.com delicate-rs.com web-local.delicate-rs.com

http://api-local.delicate-rs.com:8090/api/tasks_state/one_day gives a good response :
{"code":-1,"msg":"Please log in and operate.","data":null}

.env:

# Customized scheduler domain.
# Required
SCHEDULER_DOMAIN=web-local.delicate-rs.com

# Customized scheduler-front-end domain.
# Required
# Setting this item makes it easier to handle cross-domain issues.
SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

# Customized cookie-domain domain.
# e.g `delicate.com`
# Required
SCHEDULER_COOKIE_DOMAIN=web-local.delicate-rs.com

# Customized scheduler name.
# Required
SCHEDULER_NAME=

# Listening address of the scheduler service.
# Required
SCHEDULER_LISTENING_ADDRESS=0.0.0.0:8090

delicate-web/src/utils/envConfig.js.

const env = process.env.NODE_ENV

const envConfig = {
  development: {
    // Auto set by ci.
    DELICATE_API: 'http://api-local.delicate-rs.com:8090',
    DELICATE_WEB: 'http://web-local.delicate-rs.com:7000'
  },
  test: {
    DELICATE_API: 'http://52.78.161.159:8090',
    DELICATE_WEB: 'http://localhost:3001'
  },
  production: {
    DELICATE_API: 'http://api.delicate-rs.com',
    DELICATE_WEB: 'http://localhost:3001'
  }
}
export default (key) => envConfig[env][key]

http://api-local.delicate-rs.com:8090/api/user/check responded:
,"msg":"Please log in and operate.","data":null}
but there is no login form

[BinChengZhao]

Customized scheduler domain.

Required

SCHEDULER_DOMAIN=web-local.delicate-rs.com

Customized scheduler-front-end domain.

Required

Setting this item makes it easier to handle cross-domain issues.

SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

Customized cookie-domain domain.

e.g delicate.com

Required

SCHEDULER_COOKIE_DOMAIN=web-local.delicate-rs.com

Customized scheduler name.

Required

SCHEDULER_NAME=

Listening address of the scheduler service.

Required

SCHEDULER_LISTENING_ADDRESS=0.0.0.0:8090

Set to the domain name of your local scheduler

SCHEDULER_DOMAIN=http://api-local.delicate-rs.com

Set to the domain name of your local front-end

SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

Set to your local cookie-domain

SCHEDULER_COOKIE_DOMAIN=delicate-rs.com

The delicate-web front-end service should be, accessed via its own domain name e.g. web-local.delicate-rs.com

Because the browser requires it to be at delicate-rs.com with api-**

[BinChengZhao]

I just try using your setting, so my hosts file has 127.0.0.1 www.delicate.com api.delicate.com delicate.com api-local.delicate.com api-local.delicate-rs.com delicate-rs.com web-local.delicate-rs.com

http://api-local.delicate-rs.com:8090/api/tasks_state/one_day gives a good response : {"code":-1,"msg":"Please log in and operate.","data":null}

.env:

# Customized scheduler domain.
# Required
SCHEDULER_DOMAIN=web-local.delicate-rs.com

# Customized scheduler-front-end domain.
# Required
# Setting this item makes it easier to handle cross-domain issues.
SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

# Customized cookie-domain domain.
# e.g `delicate.com`
# Required
SCHEDULER_COOKIE_DOMAIN=web-local.delicate-rs.com

# Customized scheduler name.
# Required
SCHEDULER_NAME=

# Listening address of the scheduler service.
# Required
SCHEDULER_LISTENING_ADDRESS=0.0.0.0:8090

delicate-web/src/utils/envConfig.js.

const env = process.env.NODE_ENV

const envConfig = {
  development: {
    // Auto set by ci.
    DELICATE_API: 'http://api-local.delicate-rs.com:8090',
    DELICATE_WEB: 'http://web-local.delicate-rs.com:7000'
  },
  test: {
    DELICATE_API: 'http://52.78.161.159:8090',
    DELICATE_WEB: 'http://localhost:3001'
  },
  production: {
    DELICATE_API: 'http://api.delicate-rs.com',
    DELICATE_WEB: 'http://localhost:3001'
  }
}
export default (key) => envConfig[env][key]

http://api-local.delicate-rs.com:8090/api/user/check responded: ,"msg":"Please log in and operate.","data":null} but there is no login form

Set to the domain name of your local scheduler

SCHEDULER_DOMAIN=http://api-local.delicate-rs.com

Set to the domain name of your local front-end

SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

Set to your local cookie-domain

SCHEDULER_COOKIE_DOMAIN=delicate-rs.com

The delicate-web front-end service should be, accessed via its own domain name e.g. web-local.delicate-rs.com

Because the browser requires it to be at delicate-rs.com with api-*

[makorne]

Sorry but this changed nothing.

# Customized scheduler domain.
# Required
SCHEDULER_DOMAIN=http://api-local.delicate-rs.com

# Customized scheduler-front-end domain.
# Required
# Setting this item makes it easier to handle cross-domain issues.
SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

# Customized cookie-domain domain.
# e.g `delicate.com`
# Required
SCHEDULER_COOKIE_DOMAIN=delicate-rs.com

[BinChengZhao]

Sorry but this changed nothing.

# Customized scheduler domain.
# Required
SCHEDULER_DOMAIN=http://api-local.delicate-rs.com

# Customized scheduler-front-end domain.
# Required
# Setting this item makes it easier to handle cross-domain issues.
SCHEDULER_FRONT_END_DOMAIN=http://web-local.delicate-rs.com

# Customized cookie-domain domain.
# e.g `delicate.com`
# Required
SCHEDULER_COOKIE_DOMAIN=delicate-rs.com

This is the first time I've encountered your situation.

Did you configure your front-end project with a domain name (the front-end must have its own domain name and be under the same domain as the api, e.g. a.delicate-rs.com b.delicate-rs.com)?

Are you accessing the service through the domain name? (It can't be localhost)

Have you modified the delicate code?

[makorne]

Now frontend is http://web-local.delicate-rs.com:7000/
This url is opened in chrome and firefox on screenshots.

I did not modify the code, only add

    let cors = Cors::new()
        .allow_origin(&scheduler_front_end_domain)
//added:        
        .allow_origin("api-local.delicate-rs.com:8090")
        .allow_origin("delicate-rs.com:8000")
        .allow_origin("web-local.delicate-rs.com:7000")
        .allow_origin("*")
//

[BinChengZhao]

Now frontend is http://web-local.delicate-rs.com:7000/ This url is opened in chrome and firefox on screenshots.

I did not modify the code, only add

    let cors = Cors::new()
        .allow_origin(&scheduler_front_end_domain)
//added:        
        .allow_origin("api-local.delicate-rs.com:8090")
        .allow_origin("delicate-rs.com:8000")
        .allow_origin("web-local.delicate-rs.com:7000")
        .allow_origin("*")
//

You're almost there.

Just configure a proxy for the front end (apache or nginx will do), the domain name of the front end cannot have a port number

You must use . ***.delicate-rs.com

Then, the code in delicate can be restored!

[makorne]

Ok, lets try nginx proxy

But nginx crashed with the example from your readme:

        # Proxy delicate-scheduler server .
		location /api {
            proxy_set_header   X-Forwarded-For $remote_addr;
            proxy_set_header   Host $http_host;
            proxy_pass         http://*.*.*.*:8090;
        }

status nginx.service
× nginx.service - The nginx HTTP and reverse proxy server
     Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-11-08 16:42:42 +07; 4s ago
    Process: 763445 ExecStartPre=/usr/bin/rm -f /run/nginx.pid (code=exited, status=0/SUCCESS)
    Process: 763446 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=1/FAILURE)
        CPU: 21ms

Nov 08 16:42:42 fedora systemd[1]: Starting The nginx HTTP and reverse proxy server...
Nov 08 16:42:42 fedora nginx[763446]: nginx: [emerg] host not found in upstream "*.*.*.*" in /etc/nginx/nginx.conf:69
Nov 08 16:42:42 fedora nginx[763446]: nginx: configuration file /etc/nginx/nginx.conf test failed
Nov 08 16:42:42 fedora systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 08 16:42:42 fedora systemd[1]: nginx.service: Failed with result 'exit-code'.
Nov 08 16:42:42 fedora systemd[1]: Failed to start The nginx HTTP and reverse proxy server.

nginx version: nginx/1.20.1

[BinChengZhao]

Ok, lets try nginx proxy

But nginx crashed with the example from your readme:

        # Proxy delicate-scheduler server .
		location /api {
            proxy_set_header   X-Forwarded-For $remote_addr;
            proxy_set_header   Host $http_host;
            proxy_pass         http://*.*.*.*:8090;
        }

status nginx.service
× nginx.service - The nginx HTTP and reverse proxy server
     Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-11-08 16:42:42 +07; 4s ago
    Process: 763445 ExecStartPre=/usr/bin/rm -f /run/nginx.pid (code=exited, status=0/SUCCESS)
    Process: 763446 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=1/FAILURE)
        CPU: 21ms

Nov 08 16:42:42 fedora systemd[1]: Starting The nginx HTTP and reverse proxy server...
Nov 08 16:42:42 fedora nginx[763446]: nginx: [emerg] host not found in upstream "*.*.*.*" in /etc/nginx/nginx.conf:69
Nov 08 16:42:42 fedora nginx[763446]: nginx: configuration file /etc/nginx/nginx.conf test failed
Nov 08 16:42:42 fedora systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 08 16:42:42 fedora systemd[1]: nginx.service: Failed with result 'exit-code'.
Nov 08 16:42:42 fedora systemd[1]: Failed to start The nginx HTTP and reverse proxy server.

nginx version: nginx/1.20.1

This example does have a bit of a threshold (it assumes the deployer has a lot of experience building front- and back-ends, and I'll try to do a docker version with binary distribution later.)
The readme example uses a static web file + a backend configuration of the same domain.

And *. *. *. * is just a placeholder needed to put your own remote machine ip.

Forget about that！
I'll give you a shortcut.

You just need to set up a proxy for front-end (delicate-web) and that's it.
https://www.tecmint.com/nginx-as-reverse-proxy-for-nodejs-app/