24024
af7c11d7f9
- 新增图像生成接口，支持试用、积分和自定义API Key模式 - 实现生成图片结果异步上传至MinIO存储，带重试机制 - 优化积分预扣除和异常退还逻辑，保障用户积分准确 - 添加获取生成历史记录接口，支持时间范围和分页 - 提供本地字典配置接口，支持模型、比例、提示模板和尺寸 - 实现图片批量上传接口，支持S3兼容对象存储 feat(admin): 增加管理员角色管理与权限分配接口 - 实现角色列表查询、角色创建、更新及删除功能 - 增加权限列表查询接口 - 实现用户角色分配接口，便于统一管理用户权限 - 增加系统字典增删查改接口，支持分类过滤和排序 - 权限控制全面覆盖管理接口，保证安全访问 feat(auth): 完善用户登录注册及权限相关接口与页面 - 实现手机号验证码发送及校验功能，保障注册安全 - 支持手机号注册、登录及退出接口，集成日志记录 - 增加修改密码功能，验证原密码后更新 - 提供动态导航菜单接口，基于权限展示不同菜单 - 实现管理界面路由及日志、角色、字典管理页面访问权限控制 - 添加系统日志查询接口，支持关键词和等级筛选 feat(app): 初始化Flask应用并配置蓝图与数据库 - 创建应用程序工厂，加载配置，初始化数据库和Redis客户端 - 注册认证、API及管理员蓝图，整合路由 - 根路由渲染主页模板 - 应用上下文中自动创建数据库表，保证运行环境准备完毕 feat(database): 提供数据库创建与迁移支持脚本 - 新增数据库创建脚本，支持自动检测是否已存在 - 添加数据库表初始化脚本，支持创建和删除所有表 - 实现RBAC权限初始化，包含基础权限和角色创建 - 新增字段手动修复脚本，添加用户API Key和积分字段 - 强制迁移脚本支持清理连接和修复表结构，初始化默认数据及角色分配 feat(config): 新增系统配置参数 - 配置数据库、Redis、Session和MinIO相关参数 - 添加AI接口地址及试用Key配置 - 集成阿里云短信服务配置及开发模式相关参数 feat(extensions): 初始化数据库、Redis和MinIO客户端 - 创建全局SQLAlchemy数据库实例和Redis客户端 - 配置基于boto3的MinIO兼容S3客户端 chore(logs): 添加示例系统日志文件 - 记录用户请求、验证码发送成功与失败的日志信息
103 lines
2.6 KiB
C++
103 lines
2.6 KiB
C++
#ifndef GREENLET_THREAD_STATE_CREATOR_HPP
|
|
#define GREENLET_THREAD_STATE_CREATOR_HPP
|
|
|
|
#include <ctime>
|
|
#include <stdexcept>
|
|
|
|
#include "greenlet_internal.hpp"
|
|
#include "greenlet_refs.hpp"
|
|
#include "greenlet_thread_support.hpp"
|
|
|
|
#include "TThreadState.hpp"
|
|
|
|
namespace greenlet {
|
|
|
|
|
|
typedef void (*ThreadStateDestructor)(ThreadState* const);
|
|
|
|
// Only one of these, auto created per thread as a thread_local.
|
|
// Constructing the state constructs the MainGreenlet.
|
|
template<ThreadStateDestructor Destructor>
|
|
class ThreadStateCreator
|
|
{
|
|
private:
|
|
// Initialized to 1, and, if still 1, created on access.
|
|
// Set to 0 on destruction.
|
|
ThreadState* _state;
|
|
G_NO_COPIES_OF_CLS(ThreadStateCreator);
|
|
|
|
inline bool has_initialized_state() const noexcept
|
|
{
|
|
return this->_state != (ThreadState*)1;
|
|
}
|
|
|
|
inline bool has_state() const noexcept
|
|
{
|
|
return this->has_initialized_state() && this->_state != nullptr;
|
|
}
|
|
|
|
public:
|
|
|
|
ThreadStateCreator() :
|
|
_state((ThreadState*)1)
|
|
{
|
|
}
|
|
|
|
~ThreadStateCreator()
|
|
{
|
|
if (this->has_state()) {
|
|
Destructor(this->_state);
|
|
}
|
|
|
|
this->_state = nullptr;
|
|
}
|
|
|
|
inline ThreadState& state()
|
|
{
|
|
// The main greenlet will own this pointer when it is created,
|
|
// which will be right after this. The plan is to give every
|
|
// greenlet a pointer to the main greenlet for the thread it
|
|
// runs in; if we are doing something cross-thread, we need to
|
|
// access the pointer from the main greenlet. Deleting the
|
|
// thread, and hence the thread-local storage, will delete the
|
|
// state pointer in the main greenlet.
|
|
if (!this->has_initialized_state()) {
|
|
// XXX: Assuming allocation never fails
|
|
this->_state = new ThreadState;
|
|
// For non-standard threading, we need to store an object
|
|
// in the Python thread state dictionary so that it can be
|
|
// DECREF'd when the thread ends (ideally; the dict could
|
|
// last longer) and clean this object up.
|
|
}
|
|
if (!this->_state) {
|
|
throw std::runtime_error("Accessing state after destruction.");
|
|
}
|
|
return *this->_state;
|
|
}
|
|
|
|
operator ThreadState&()
|
|
{
|
|
return this->state();
|
|
}
|
|
|
|
operator ThreadState*()
|
|
{
|
|
return &this->state();
|
|
}
|
|
|
|
inline int tp_traverse(visitproc visit, void* arg)
|
|
{
|
|
if (this->has_state()) {
|
|
return this->_state->tp_traverse(visit, arg);
|
|
}
|
|
return 0;
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
}; // namespace greenlet
|
|
|
|
#endif
|