umami api client test ko with docker umami version 2.13.3

未关闭
  • 哪里不对？
#17 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
docker, typescript
领域
api, backend

调研方向

Start by reproducing the getMe and getWebsites calls from the issue against a self-hosted version 2.13.3 server, using the shown getClient and login flow. Inspect the client requests and the server-side UUID error to determine where the incompatible user identifier is introduced. Done means the affected calls no longer return the reported 504 error, with the behavior covered by an appropriate test if the repository provides one.

由索引模型根据 Issue 内容生成。

描述

Hi,
https://github.com/boly38/action-umami-report/issues/59
I'm trying to play basis example (ex. I first would like to list websites)

  • server with umami docker self-hosted
  • self-hosted umami version 2.13.3

env

export UMAMI_API_CLIENT_USER_ID=admin
export UMAMI_API_CLIENT_PASSWORD=xxx-replace-by-admin-password-here
export UMAMI_API_CLIENT_SECRET=xxx-replace-by-app-secret-set-in-docker-compose
export UMAMI_API_CLIENT_ENDPOINT=https://myumami.example.fr/api

node

import {getClient} from '@umami/api-client';

const umamiUsername = process.env.UMAMI_API_CLIENT_USER_ID;
const umamiPassword = process.env.UMAMI_API_CLIENT_PASSWORD;
let client;
const getMeFixed = false;
{
    client = getClient();
    const {ok, data, status, error} = await client.login(umamiUsername, umamiPassword);
    console.log(`login: ${JSON.stringify({ok, data, status, error}, null, 2)}`);
}
if (getMeFixed) {
    const {ok, data, status, error} = await client.getMe();
    console.log(`getMe: ${JSON.stringify({ok, data, status, error}, null, 2)}`);
}
{
    const {ok, data, status, error} = await client.getWebsites();
    console.log(`getWebsites: ${JSON.stringify({ok, data, status, error}, null, 2)}`);
}

result

login: {
  "ok": true,
  "data": {
    "token": "==REDATED==",
    "user": {
      "id": "==REDATED==",
      "username": "admin",
      "role": "admin",
      "createdAt": "2024-07-12T15:52:00.340Z",
      "isAdmin": true
    }
  },
  "status": 200
}
getWebsites: {
  "ok": false,
  "status": 504,
  "error": "<html>\r\n<head><title>504 Gateway Time-out</title></head>\r\n<body>\r\n<center><h1>504 Gateway Time-out</h1></center>\r\n<hr><center>nginx</center
>\r\n</body>\r\n</html>\r\n"
}

but I got 504 error with server side error logs :

PrismaClientKnownRequestError:
Invalid `prisma.user.findUnique()` invocation:


Inconsistent column data: Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-fA-F-], found `m` at 3
    at _n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7749)
    at _n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7057)
    at _n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6741)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9355)
    at async /app/.next/server/chunks/405.js:1:17597 {
  code: 'P2023',
  clientVersion: '5.17.0',
  meta: {
    modelName: 'User',
    message: 'Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-fA-F-], found `m` at 3'
  }
}

NB: it was the same kind of error for getMe use case.

this issue and error logs are close to umami-software/umami/issues/1964

I just try to create a !admin new user and switch env to use this new creds, login is ok but I got same issue for the getWebsites step .. :'(

any help / hint appreciated
regards

主要语言
TypeScript
星标
49
派生
18
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

umami-software/api-client 的其他 Issue

查看 umami-software/api-client 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。