设置后是否无法关闭Deno.signal?

如何解决设置后是否无法关闭Deno.signal?

let sig = Deno.signal(Deno.Signal.SIGINT)

await sig

console.log('hi')

执行上面的代码并将SIGINT传递给进程时,第一个SIGINT将恢复该进程。

但是,问题是 处理完信号后 SIGINT不再起作用。

所以,我试图使其工作。

let sig = Deno.signal(Deno.Signal.SIGINT)

await sig

sig.dispose()

console.log('hi')

这就是我所拥有的:

sig.dispose会在sig发生await时立即解析sig。(是否传递了SIGINT) 对于asyncIterator,它意味着返回done: true

与将SIGINT返回其原始状态无关。

这是打算吗?

解决方法

通常期望的处理信号流的方式如下:

const sig = Deno.signal(Deno.Signal.SIGINT);

// NOTICE: you might want to have a task running in the meantime to test this.
// Signals belong to the type of optional/unref-ed promises,in that awaiting
// on such promises does not block the runtime from exiting.
// You might want to add the line below for testing purposes.
setTimeout(() => {},100000);

// Async iterator. You can probably wrap it in a function such it does not
// block top level execution
for await (const _ of sig) {
  console.log("SIGINT captured");
}
SignalStream返回的

Deno.signal确实具有.then方法,因此您也可以采用以下样式:

const sig = Deno.signal(Deno.Signal.SIGINT);

setTimeout(() => {},100000);

while (true) {
  await sig;
  console.log("SIGINT captured");
}

应该等待多次。下面的示例在3个SIGINT触发器(在本地验证为可以正常工作)之后正确退出了该过程:

const sig = Deno.signal(Deno.Signal.SIGINT);

const timeout = setTimeout(() => {},100000);

await sig;
console.log("SIGINT captured #1");
await sig;
console.log("SIGINT captured #2");
await sig;
console.log("SIGINT captured #3,exiting");
clearTimeout(timeout);

console.log("DONE");
正如问题所提出的,

sig.dispose()确实确实起到了解除sig信号束缚的作用,并导致立即唤醒等待的应许。这是为了允许异步迭代器立即退出循环(如果有的话)。调用.dispose()之后,原来的sig将不再可用(由于关闭了后备信号资源并将其从内部资源表中删除)。您必须通过再次调用sig来创建新的Deno.signal(Deno.Signal.SIGINT)

const sig1 = Deno.signal(Deno.Signal.SIGINT);

const exitBlocker = setTimeout(() => {},100000);

await sig1;
console.log("SIGINT received by sig1. Disposing sig1");
sig1.dispose();

const sig2 = Deno.signal(Deno.Signal.SIGINT);

await sig1; // This should resolve immediately,even without signal
console.log("sig1 resolves immediately,but no actual signal happened");

await sig2;
console.log("SIGINT received by sig2. This is the real deal.");
await sig2;
console.log("SIGINT received by sig2 again. Preparing for exit.");

clearTimeout(exitBlocker);
console.log("DONE");

如果在本地运行以上命令,则会看到以下内容:

^CSIGINT received by sig1. Disposing sig1
sig1 resolves immediately,but no actual signal happened
^CSIGINT received by sig2. This is the real deal.
^CSIGINT received by sig2 again. Preparing for exit.
DONE

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-