gen_server call流程分析

最新推荐文章于 2025-08-08 15:51:22 发布
原创 最新推荐文章于 2025-08-08 15:51:22 发布 · 1k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#gen_server #call handler_call

本文深入解析了gen_servercall的工作流程，重点分析了your_modulehandler_call的四种返回情况及其对gen进程的影响，包括正常回复、超时处理及进程终止等关键细节。

gen_server call 流程分析

  • 关注your_module handler_call的返回值：
    • {reply, Reply, NState} 表示正常，给gen进程发通知，并继续循环接收数据，无超时时间
    • {reply, Reply, NState, Timeout} 表示正常，给gen进程发通知，并继续循环接收数据，超时时间为Timeout
    • {noreply, Reply, NState} 表示正常，不会给gen进程发通知，gen进程只能等待超时，并继续循环接收数据，无超时时间
    • {noreply, Reply, NState, Timeout}表示正常，不会给gen进程发通知，gen进程只能等待超时，并继续循环接收数据，超时时间为Timeout
    • {stop, Reason, Reply, NState}表示异常，终止进程
      gen_server模块call流程分析
gen_server实现
erlang
06-09 2496
阅读erlang gen_server源码，分析
提高gen_server call 一个小技巧
taitoubiyan1的专栏
12-25 1368
刚刚突然收到一条建议 一般我们写 gen_server handle call会这么写 handle_call(call, _From, State) -> Result = compute(State), %%compute 获取为一个耗时操作  {reply, Result State}. 简单的通过计算返回state中的某个数据 如果compute为
gen:call和gen_server:call的区别
brook0344的专栏
11-26 3718
调用catch gen:call可以获得更多的异常信息 gen_server:call内部调用了catch丢失了很多信息 ，外部无法catch到   此外好像没啥区别了     gen:call 同步调用其他服务器进程的方法（内部通过收发消息实现） 如果服务器返回{reply,xx,Status} 那么gen:call返回{ok,xx} 如果服务器没有对应的方法Handler
Erlang OTP之gen_server入门
fbher的博客
06-19 553
1.概念 gen_server是对一种服务器开发模式的抽象，在我们日常开发中，其实有很多行为都是重复的，例如我们会用一个loop()来不断使服务器进入一种处于等待，处理信息，返回结果，等待的状态。其实这些工作都是重复的，而一个行为就是把我们这些重复的工作都抽象出来，简化工作。 2.函数介绍 我们常用的函数有以下几个： 1.start() -> gen_server:sta...
gen_server
rwxxtt的博客
07-11 754
文章目录gen_server1、gen_server起步1.1、第一步:确定回调模块的名称1.2、第二步:写接口函数1.3、第三步:编写回调函数2、gen_server回调的结构2.1、启动服务器时发生了什么2.2、调用服务器程序时发生了什么2.3、调用和通知2.4、发送给服务器的原生消息2.5、HastalaVista,Baby(服务器的终止)2.6、热代码替换3、gen_server详解3.1、启动服务器3.2、调用服务3.3、停止服务器3.4、代码更新 gen_server 1、gen_server起
Erlang 源码分析之 Gen_Server
GitChat
11-06 1083
众所周知 Erlang/OTP 是一个具有高并发、低延时、高容错等特性的平台。 其三大 Behaviour : Gen_ Server（客户端服务器）； Gen_ Fsm（有限状态机）； Gen_ Event（事件通知），是其坚如磐石的系统的基石。 本场 Chat 将透过源码分析其中 Gen_Server 的实现原理并管中一窥 Erlang 的设计思想。 本场 Chat 主...
gen_server启动,关闭,消息收发分析
lewiskyo的专栏
04-21 1423
https://www.cnblogs.com/hzy1987/p/5441807.html http://www.cnblogs.com/me-sa/archive/2011/12/20/erlang0023.html 介绍: gen_server是OTP的一个behavior, 在behavior基础上快速构建出可用且可靠的功能. behavior是进程模式的规范化,把代码分成两部分,一部分是...
Erlang OTP四大行为模式之一gen_server解析和案例
qq_35218302的博客
09-10 1489
在刚接触otp gen_server时很多人可能只是对着Erlang程序设计中的案例敲一遍，但对为什么要使用gen_server以及里面各个方法是如何联系和影响进程的估计都不太清楚。 首先讲下行为模式，你可以理解为面向对象中的设计模式（更像是模版方法模式），本质都是为了代码复用，当然你也可以把这些行为理解成为某种应用程序框架。我们往往在创建一个进程执行任务时都会有一下步骤, 1.spawn创建...
22、Erlang的gen_server与Mnesia数据库入门指南
vodka的博客
08-08 74
本文介绍了Erlang中两个核心组件gen_server和Mnesia的基础知识与使用方法。gen_server提供了一种创建服务器进程的标准化方式，能够处理各种请求和消息，适用于构建稳定、高效的并发系统。Mnesia是一个高性能、可配置的数据库管理系统，支持内存表、磁盘表、数据复制和事务处理，非常适合用于多用户游戏、在线支付系统等场景。文章通过具体代码示例详细讲解了gen_server的回调机制以及Mnesia的查询、事务和复制功能，并展示了如何将两者结合使用以实现复杂的应用功能。
22、深入探索 Erlang：gen_server 与 Mnesia 数据库
alice7model的博客
07-11 90
本文深入介绍了 Erlang 中的 gen_server 和 Mnesia 数据库的使用。首先讲解了 gen_server 的基本结构和回调函数的编写方法，并通过一个支付系统的示例详细展示了如何实现服务器的启动、调用和终止等操作。随后，文章探讨了 Mnesia 数据库的查询方法，包括数据选择、投影、条件查询等，并提供了性能优化、错误处理及调试技巧。最后，总结了 gen_server 与 Mnesia 结合使用的潜力，适用于构建高效稳定的分布式系统。
gen_server笔记
cnDenis的专栏
04-25 326
gen_server笔记 by cnDenis http://cndenis.iteye.com 2013年4月24日 gen_server是erlang的OTP框架中最常用的“行为模式”了吧，至少几本erlang教材都是首 先介绍这个。 这东西用来做什么的呢？或者说，为什么要用这东西呢？由于我接触这东西不过几天， 理解尚非常粗浅，就我看来，用gen_server有以下几个好处： ...
erlang 消息发送 gen_server:call cast info
keep it simple，stupid
09-13 2784
gen_server发送 如何用!发送gen_server:call消息
gen_server瓶颈
langxianwu的专栏
07-28 185
如果只维护了一个gen_server进程来处理大多数请求将造成。进程忙不过来，消息队列不大断增大，需要消耗更多的堆内存。最后会导致VIM崩溃。 方法1： 此方法有个缺点 spawn 创建+销毁成本非常高. 我采用gen_server作为第三方服务放入到系统中，为了解决瓶颈问题我在handle_call里面采用noreply，且只创建一个进程Pid，然后给此进程Pid发消息，剩下的业务逻辑...
用超时来实现gen_server的定时
Sunface撩技术
05-23 2069
-module(otp_test). -behaviour(gen_server). -export([start_link/0]). %% gen_server callbacks -export([init/1, handle_call/3, handle_cast/2, handle_info/2, terminate/2, code_change/3]). st
erlang学习笔记之gen_server的回调结构
keyzx的博客
09-13 346
举个例子，如果服务器连接到另一个进程并捕捉退出信号，就可能会突然收到一个预料之外的{'EXIT', Pid, What}消息。gen_server:start_link(Name, Mod, InitArgs, Opts)这个调用是所有事物的起点。自发性消息是一切未经显式调用gen_server:call或gen_server:cast而到达服务器的消息。它会创建一个名为Name的通用服务器，回调模块是Mod，Opts则控制通用服务器的行为。它最终调用的是回调模块里的handle_call/3。
gcc源代码分析之gen_call_value()函数
linux-0.11调试教程
01-12 1662
(call_insn 7 6 9 (set (reg:SI 0)        (call (mem:QI (symbol_ref/v:SI ("printf")))            (const_int 4))) -1 (nil)    (nil)) rtx gen_call_value (operand0, operand1, operand2)      r
gen_server的回调结构下
weixin_48092769的博客
08-31 116
举个例子，如 果服务器连接到另一个进程并捕捉退出信号，就可能会突然收到一个预料之外的{'EXIT', Pid, What}消息。服务器会因为许多原因而终止。某个以handle_开头的函数也许会返回一个{stop, Reason, NewState}，服务器也可能崩溃并生成{'EXIT', reason}。在所有这些情况下，无论它们是怎样发生的，都会调用terminate(Reason, NewState)。如果想让服务器过后重启，就必须编写一个“我胡汉三又回来了”的函数，由terminate/2 触发。
介绍gen_server的示例代码
Abel's Blog
11-18 2853
OTP（open telecomplatform），它的设计目标是用于做一套容错系统。最核心的概念就是behavior。类似类继承，在类里编写函数实现；而外层非应用逻辑相关的东西（热更新，监控机制等等）交OTP体系来控制。 先介绍gen_server模块。使用这个编写服务器只需要确认这3件事情： 1.      确定一个回调模块的名称； 2.      写接口函数； 3.      在回调
erlang面试经（2）
小老鼠啊的博客
12-29 3035
面试经（2）一、OTP相关二、定时器三、运算符四、算法五、Erlang有哪些运算符六、请写出Erlang条件表达式、循环七、如何匹配binary（二进制位也就是字节，默认的话是比特位）从第三字节开始的八、请举例替换二进制字符串中的指定字符串九、怎么使用Erlang语言实现Key和Value的存储十、跨进程通信、跨节点（服务器）通信方式有哪些十一、请简述一下服务器上线出问题处理的流程十二、有哪些调试...
Exception Group Traceback (most recent call last): | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\_utils.py", line 76, in collapse_excgroups | yield | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 186, in __call__ | async with anyio.create_task_group() as task_group: | │ │ └ <anyio._backends._asyncio.TaskGroup object at 0x00000168B3F1F4F0> | │ └ <function create_task_group at 0x00000168A54857E0> | └ <module 'anyio' from 'D:\\dev\\EquipmentRegistryDataPlatform\\venv\\lib\\site-packages\\anyio\\__init__.py'> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 815, in __aexit__ | raise BaseExceptionGroup( | └ <class 'exceptiongroup.BaseExceptionGroup'> | | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception) +-+---------------- 1 ---------------- | Traceback (most recent call last): | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 403, in run_asgi | result = await app( # type: ignore[func-returns-value] | └ <uvicorn.middleware.proxy_headers.ProxyHeadersMiddleware object at 0x00000168A4F34760> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 60, in __call__ | return await self.app(scope, receive, send) | │ │ │ │ └ <bound method RequestResponseCycle.send of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E860>> | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <fastapi.applications.FastAPI object at 0x00000168B3AF1D50> | └ <uvicorn.middleware.proxy_headers.ProxyHeadersMiddleware object at 0x00000168A4F34760> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\fastapi\applications.py", line 1054, in __call__ | await super().__call__(scope, receive, send) | │ │ └ <bound method RequestResponseCycle.send of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E860>> | │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\applications.py", line 113, in __call__ | await self.middleware_stack(scope, receive, send) | │ │ │ │ └ <bound method RequestResponseCycle.send of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E860>> | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <starlette.middleware.errors.ServerErrorMiddleware object at 0x00000168B3D038E0> | └ <fastapi.applications.FastAPI object at 0x00000168B3AF1D50> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\errors.py", line 187, in __call__ | raise exc | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\errors.py", line 165, in __call__ | await self.app(scope, receive, _send) | │ │ │ │ └ <function ServerErrorMiddleware.__call__.<locals>._send at 0x00000168A65497E0> | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <starlette.middleware.cors.CORSMiddleware object at 0x00000168B3D038B0> | └ <starlette.middleware.errors.ServerErrorMiddleware object at 0x00000168B3D038E0> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\cors.py", line 93, in __call__ | await self.simple_response(scope, receive, send, request_headers=headers) | │ │ │ │ │ └ Headers({'host': '172.23.49.43:9999', 'connection': 'keep-alive', 'content-length': '117', 'pragma': 'no-cache', 'cache-contr... | │ │ │ │ └ <function ServerErrorMiddleware.__call__.<locals>._send at 0x00000168A65497E0> | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <function CORSMiddleware.simple_response at 0x00000168B3AF7490> | └ <starlette.middleware.cors.CORSMiddleware object at 0x00000168B3D038B0> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\cors.py", line 144, in simple_response | await self.app(scope, receive, send) | │ │ │ │ └ functools.partial(<bound method CORSMiddleware.send of <starlette.middleware.cors.CORSMiddleware object at 0x00000168B3D038B0... | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <app.core.middlewares.BackGroundTaskMiddleware object at 0x00000168B3D03850> | └ <starlette.middleware.cors.CORSMiddleware object at 0x00000168B3D038B0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 28, in __call__ | await self.handle_http(scope, receive, send) | │ │ │ │ └ functools.partial(<bound method CORSMiddleware.send of <starlette.middleware.cors.CORSMiddleware object at 0x00000168B3D038B0... | │ │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <function SimpleBaseMiddleware.handle_http at 0x00000168B3B141F0> | └ <app.core.middlewares.BackGroundTaskMiddleware object at 0x00000168B3D03850> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 38, in handle_http | await response(scope, receive, send_wrapper) | │ │ │ └ <function SimpleBaseMiddleware.handle_http.<locals>.send_wrapper at 0x00000168A6549A20> | │ │ └ <bound method RequestResponseCycle.receive of <uvicorn.protocols.http.h11_impl.RequestResponseCycle object at 0x00000168B3F1E... | │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 185, in __call__ | with collapse_excgroups(): | └ <function collapse_excgroups at 0x00000168A56A4940> | | File "C:\Program Files\Python310\lib\contextlib.py", line 153, in __exit__ | self.gen.throw(typ, value, traceback) | │ │ │ │ │ └ <traceback object at 0x00000168B523ABC0> | │ │ │ │ └ ExceptionGroup('unhandled errors in a TaskGroup', [TypeError("Unable to apply constraint 'max_length' to supplied value 2025-... | │ │ │ └ <class 'exceptiongroup.ExceptionGroup'> | │ │ └ <method 'throw' of 'generator' objects> | │ └ <generator object collapse_excgroups at 0x00000168B507E1F0> | └ <contextlib._GeneratorContextManager object at 0x00000168B3F1E830> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\_utils.py", line 82, in collapse_excgroups | raise exc | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 187, in __call__ | response = await self.dispatch_func(request, call_next) | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | │ │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | │ └ <bound method APILoggerMiddleware.dispatch of <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0>> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\_utils.py", line 82, in collapse_excgroups | raise exc | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 187, in __call__ | response = await self.dispatch_func(request, call_next) | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | │ │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | │ └ <bound method APILoggerMiddleware.dispatch of <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0>> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | raise exc | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 187, in __call__ | response = await self.dispatch_func(request, call_next) | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | │ │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | │ └ <bound method APILoggerMiddleware.dispatch of <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0>> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 187, in __call__ | response = await self.dispatch_func(request, call_next) | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | │ │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | │ └ <bound method APILoggerMiddleware.dispatch of <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0>> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | │ │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | │ └ <bound method APILoggerMiddleware.dispatch of <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0>> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 103, in dispatch | response = await call_next(request) | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | │ └ <starlette.middleware.base._CachedRequest object at 0x00000168B3F1E950> | └ <function BaseHTTPMiddleware.__call__.<locals>.call_next at 0x00000168A6549990> | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 163, in call_next | raise app_exc | └ TypeError("Unable to apply constraint 'max_length' to supplied value 2025-08-24 16:00:00+00:00") | | raise app_exc | └ TypeError("Unable to apply constraint 'max_length' to supplied value 2025-08-24 16:00:00+00:00") | | └ TypeError("Unable to apply constraint 'max_length' to supplied value 2025-08-24 16:00:00+00:00") | | File "D:\dev\EquipmentRegistryDataPlatform\venv\lib\site-packages\starlette\middleware\base.py", line 149, in coro | await self.app(scope, receive_or_disconnect, send_no_error) | │ │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.send_no_error at 0x00000168A654AA70> | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.receive_or_disconnect at 0x00000168A6549900> | │ │ └ {'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.3'}, 'http_version': '1.1', 'server': ('172.23.49.43', 9999), ... | │ └ <app.core.middlewares.APILoggerAddResponseMiddleware object at 0x00000168B3D03730> | └ <app.core.middlewares.APILoggerMiddleware object at 0x00000168B3D037F0> | | File "D:\dev\EquipmentRegistryDataPlatform\app\core\middlewares.py", line 28, in __call__ | await self.handle_http(scope, receive, send) | │ │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.send_no_error at 0x00000168A654AA70> | │ │ │ └ <function BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.receive_or_disconnect at 0x00000168A654WARNING: StatReload detected changes in 'app\api\v1\zentao\zt_materiallib.py'. Reloading...
最新发布
08-26
检查请求处理流程 在 `zt_materiallib.py` 中确认： - 是否对日期时间字段错误使用了 `str` 类型注解 - 是否在依赖项中错误添加了字符串约束 --- ### 预防措施 1. **启用 Pydantic 严格模式**： ```python from...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值