最新版chrome136禁用了默认--user-data-dir的调试功能，--user-data-dir的默认路径为C:\Users\dell\AppData\Local\Google\Chrome\User Data\Default以前只需要指定--remote-debugging-port=9222即可调试，现在需要额外指定--user-data-dir"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="C:\Chrome_data"vscode文档已经更新提示:if this flag isn't given, then the command will open a new window of any running browser and not enter debug mode更改了远程调试开关以提高安全性attaching-to-browsers

使用的旧版centos7系统导致使用let's Encrypt证书的网站无法访问，比如docker使用了cf的dns，会连接cf的registry。ab012f07497a: Waiting e0979c892644: Waiting error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/6a/6aedcda31f51881fd13e67674d84cd6661e278547dc7b23602672fb5a1f76ee4/data?expires=1744254640signature=S%2BTo9ZcvNHuuweoW7qCirv%2Fe9Uo%3Dversion=2: x509: certificate signed by unknown authority[root@13 ~]# curl -v https://xxx* About to connect() to xxx port 443 (#0)* Trying xxx...* Connected to xxx (xx) port 443 (#0)* Initializing NSS with certpath: sql:/etc/pki/nssdb* CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none* Server certificate:* subject: CN=xxx* start date: Apr 08 18:01:56 2025 GMT* expire date: Jul 07 18:01:55 2025 GMT* common name: xxx* issuer: CN=R11,O=Let's Encrypt,C=US* NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER)* Peer's Certificate issuer is not recognized.* Closing connection 0curl: (60) Peer's Certificate issuer is not recognized.More details here: http://curl.haxx.se/docs/sslcerts.html研究发现是系统信任的根证书过期导致需要更新ca-certificates程序包,更新ca-certificates程序包后会自动更新系统信任的根证书查看已安装的版本1.debian/ubuntu# 查看已安装版本dpkg -l ca-certificates | grep ^ii# 或直接提取版本号dpkg-query -W -f='${Version}' ca-certificates2.centos/RHEL# 查看已安装版本rpm -q ca-certificates# 或结合 yum 查看信息yum info ca-certificates | grep -E "Name|Version" [root@13 ~]# yum info ca-certificatesLoaded plugins: fastestmirrorRepodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fastDetermining fastest mirrors * elrepo-kernel: mirror.fcix.net * epel: irltoolkit.mm.fcix.netInstalled PackagesName : ca-certificatesArch : noarchVersion : 2015.2.6Release : 73.el7Size : 1.1 MRepo : installedFrom repo : anacondaSummary : The Mozilla CA root certificate bundleURL : http://www.mozilla.org/License : Public DomainDescription : This package contains the set of CA certificates chosen by the : Mozilla Foundation for use with the Internet PKI.Available PackagesName : ca-certificatesArch : noarchVersion : 2022.2.54Release : 74.el7_9Size : 911 kRepo : updates/7/x86_64Summary : The Mozilla CA root certificate bundleURL : http://www.mozilla.org/License : Public DomainDescription : This package contains the set of CA certificates chosen by the : Mozilla Foundation for use with the Internet PKI.发现已安装的是2015年的版本了更新ca-certificates# Debian/Ubuntusudo apt update sudo apt install --reinstall ca-certificates# CentOS/RHELsudo yum update ca-certificates# Fedorasudo dnf update ca-certificates# Alpine Linuxsudo apk update sudo apk add ca-certificates更新完成后应该就可以使用了，若不行可尝试执行手动更新update-ca-trustupdate-ca-trust force-enableupdate-ca-trust extractdocker需要重启才能生效参考：CentOS 7 更新根证书（root certificates）"docker pull" certificate signed by unknown authority

在实现一个Excel异步导入功能需要异步解析excel，使用@Async注解启用了解析方法的异步功能。但在解析方法内有Feign远程调用，该接口涉及接口权限，而@Async标注的方法与web请求不在同一个线程中，获取不到request。因此需要从上传接口传递request至异步方法。了解到RequestContextHolder.setRequestAttributes(RequestAttributes attributes, boolean inheritable)方法该方法是 Spring 框架提供的一个工具方法，用于在当前线程中手动设置请求上下文（RequestAttributes）。它主要用于跨线程传递和管理请求的上下文。我们需要在开启新线程前通过该方法手动设置当前的请求，以在多线程中访问到当前的request请求对象。但是我在设置后，获取到的request为空。最后发现是excel解析完成时，之前的导入接口已经完成响应，request对象已经被销毁回收了。后又了解到AsyncContext，它用于控制异步请求的生命周期在HttpServletRequest中提供了一个startAsync()方法用于启动异步处理，它会返回 AsyncContext 对象。此时request在标记异步请求完成前不会被回收。在后台任务完成后，调用 asyncContext.complete() 来标记异步请求的完成。示例代码：private AsyncContext asyncContext = null;public void import(MultipartFile file){ ServletRequestAttributes sra = (ServletRequestAttributes) RequestContextHolder.getRequestAttributes(); RequestContextHolder.setRequestAttributes(sra, true); if (sra != null) { asyncContext = sra.getRequest().startAsync(); }// 调用异步解析方法parseFile(file)}@Asyncpublic void parseFile(MultipartFile file){// 一些耗时内容ServletRequestAttributes sra = (ServletRequestAttributes) RequestContextHolder.getRequestAttributes(); RequestContextHolder.setRequestAttributes(sra, true);// 此时能够正常完成Feign调用（已自定义RequestInterceptor拦截器，将所需信息传递）xxFeignClient.xxxxx();// 完成异步处理 asyncContext.complete();}更新：此方式会阻塞主线程执行，多线程失去了意义，我的场景是被调用方读取header获取用户信息，所以我后续改为在子线程里面将用户信息手动设置到header中实现。参考：记一次springboot @Async处理导致后续request请求参数获取为空的坑

之前将ESP8266接入巴法云,使用一段时间后,发现不够稳定,干脆直接在内网搭建一个HomeAssistant实现灯的控制.这里使用docker搭建:homeassistat(Home Assistant 2021.12.8):version: '3'services: homeassistant: privileged: true image: 'homeassistant/home-assistant:stable' container_name: 'homeassistant' environment: - TZ=Asia/Shanghai network_mode: host volumes: - /home/file/docker/homeassistant/config:/config restart: unless-stopped启动完成后访问服务器8123端口完成初始化.还需要安装一个mqtt服务端,这里同样使用docker搭建mosquitto:version: "3.0"services: mosquitto: container_name: 'mosquitto' image: 'eclipse-mosquitto:2.0.18' ports: - 1883:1883 - 9001:9001 volumes: - /home/file/docker/mosquitto/config:/mosquitto/config - /home/file/docker/mosquitto/data:/mosquitto/data - /home/file/docker/mosquitto/log:/mosquitto/logmosquitto.confpersistence true#persistence_location /mosquitto/data#log_dest file /mosquitto/log/mosquitto.loglistener 9001port 1883allow_anonymous true启动mqtt服务器,然后来到HomeAssistant管理页面,左侧配置-设备与服务,右下角添加集成,找到MQTT,输入刚刚搭建的mqtt服务器.烧录开发板,跟前一篇文章的巴法云代码一样,这里再贴一下,设备接线参考ESP8266通过巴法云接入米家我这边使用的WiFiManager版本为0.16.0,发现使用最新版2.0.17有无法连接MQTT服务器的问题#include ESP8266WiFi.h#include ESP8266WebServer.h#include WiFiManager.h#include Ticker.h //#include PubSubClient.h#include "PubSubClient.h" //默认，加载MQTT库文件 WiFiClient espClient; //wifi客户端模式PubSubClient client(espClient);Ticker ticker; //定时器对象#define ID_MQTT "esp8266-01" //客户端id#define D1 5 //D1#define D2 4 //D2const char* topic = "light001"; //主题名字，与巴法云控制台的主题一致const int B_led = D1; //引脚值，此引脚用于连接继电器的信号端const int led_switch = D2; //引脚值，此引脚用于连接继电器的信号端//**************************************************//const char* mqtt_server = "192.168.4.200"; //默认，MQTT服务器const int mqtt_server_port = 1883; //默认，MQTT服务器端口int count; // Ticker计数用的变量int state = 0; //灯的状态// 建立WiFiManager对象WiFiManager wifiManager; //灯光函数及引脚定义void turnOnLed();void turnOffLed();//计数void tickerCount(){ count++;}// 连接MQTT服务器void reconnect() { Serial.print("Attempting MQTT connection..."); // Attempt to connect if (client.connect(ID_MQTT)) { Serial.println("connected"); Serial.print("subscribe:"); Serial.println(topic); //订阅主题，如果需要订阅多个主题，可发送多条订阅指令client.subscribe(topic2);client.subscribe(topic3); client.subscribe(topic); } else { Serial.print("failed, rc="); Serial.println(client.state()); Serial.println(" try again in 1 seconds"); // Wait 5 seconds before retrying delay(1000); }//}}// 收到信息后的回调函数void receiveCallback(char* topic, byte* payload, unsigned int length) { Serial.print("来了Topic:"); Serial.println(topic); String msg = ""; for (int i = 0; i length; i++) { msg += (char)payload[i]; } Serial.print("Msg:"); Serial.println(msg); if (msg == "on") {//如果接收字符on，亮灯 turnOnLed();//开灯函数 } else if (msg == "off") {//如果接收字符off，关灯 turnOffLed();//关灯函数 } msg = ""; }//开灯void turnOnLed() { Serial.println("turn on light"); digitalWrite(B_led, HIGH); state = 1;}//关灯void turnOffLed() { Serial.println("turn off light"); digitalWrite(B_led, LOW); state = 0;}// 发布信息void pubMQTTmsg(){ // 建立发布主题 //巴法云个性设置，推送消息时：主题名后加/set推送消息，表示向所有订阅这个主题的设备们推送消息， //假如推送者自己也订阅了这个主题，消息不会被推送给它自己，以防止自己推送的消息被自己接收。 String topicString = "light001/set" ; char publishTopic[topicString.length() + 1]; //转换成字符数组 strcpy(publishTopic, topicString.c_str()); // 建立发布信息,当前D1引脚状态 String messageString; if(digitalRead(B_led)){ messageString = "on"; } else { messageString = "off"; } char publishMsg[messageString.length() + 1]; //转换成字符数组 strcpy(publishMsg, messageString.c_str()); // 实现ESP8266向主题发布信息,并在串口监视器显示出来 if(client.publish(publishTopic, publishMsg)){ Serial.println("Publish Topic:"); Serial.println(publishTopic); Serial.println("Publish message:"); Serial.println(publishMsg); } else { Serial.println("Message Publish Failed."); }}//程序入口void setup() { pinMode(B_led, OUTPUT); //设置引脚为输出模式 pinMode(led_switch, OUTPUT); // 开关引脚为输入模式 digitalWrite(B_led, LOW);//默认引脚上电低电平 Serial.begin(9600); //设置波特率9600 //********************自动配置网络************************ // wifiManager.setTimeout(20); wifiManager.setConfigPortalTimeout(120); // 自动连接WiFi。以下语句的参数是连接ESP8266时的WiFi名称// wifiManager.autoConnect("AutoConnectAP"); // 如果您希望该WiFi添加密码，可以使用以下语句： wifiManager.autoConnect("8266","xxxxx"); //重置wifi设置 // wifiManager.resetSettings(); // WiFi连接成功后将通过串口监视器输出连接成功信息 Serial.println(""); Serial.print("ESP8266 Connected to "); Serial.println(WiFi.SSID()); // WiFi名称 Serial.print("IP address:\t"); Serial.println(WiFi.localIP()); // IP //******************************************************* client.setServer(mqtt_server, mqtt_server_port);//设置mqtt服务器 client.setCallback(receiveCallback); //mqtt消息处理 ticker.attach(1, tickerCount); // Ticker定时对象 Serial.println("setup结束");}//循环执行 void loop() {// Serial.println("循环"); int val = digitalRead(B_led); int ctl_val = digitalRead(led_switch); if(ctl_val == 1){//按键按下 delay(400); state = !state; digitalWrite(B_led, state);// digitalWrite(led_switch, LOW); digitalWrite(led_switch, LOW); int ctl_val = digitalRead(led_switch); Serial.print("开2关值为 :\t"); Serial.println(ctl_val); } if (client.connected()) { client.loop(); if (count = 10){ // 每隔10秒钟发布一次信息 Serial.println("心跳报"); pubMQTTmsg(); count = 0; } }else{ reconnect(); }}烧录完成后,现在为HomeAssistant添加该设备在homeassistant的configuration.yaml中最后添加一行light: !include light01.yaml随后在configuration.yaml同级目录添加light01.yaml,内容为- platform: mqtt name: "卧室灯" state_topic: "light001/set" command_topic: "light001" payload_on: "on" payload_off: "off" optimistic: false qos: 0 retain: true完成后重启homeassistant即可连接HomeKit配置-设备与服务中添加HomeKit,然后开放端口在通知中可以看到绑定二维码,使用iPhone的家庭APP扫码绑定用户名-高级模式参考文章ESP8266通过MQTT接入Home Assistant实践ESP8266通过MQTT接入Home Assistant