import sys deffunc(a,b): return (a+b) if __name__ == '__main__': a = [] for i inrange(1, len(sys.argv)): a.append((int(sys.argv[i]))) print(func(a[0],a[1]))
lambda
lambda表达式中不允许使用非final的变量
或者引用非final变量之后不允许对其值做修改
Variable used in lambda expression should be final or effectively final
2023-06-15T13:25:16.093814Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation. 2023-06-15T13:25:16.094655Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made. 2023-06-15T13:25:16.196155Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation. 2023-06-15T13:25:16.196181Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 3300 2023-06-15T13:25:16.196690Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made. InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 13:25:16 UTC - mysqld got exception 0x16 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 2023-06-15T13:25:16.298720Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 3312 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 7ff7811cfd48 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z() 7ff78040004b mysqld.exe!?print_fatal_signal@@YAXH@Z() 7ff7803ffe13 mysqld.exe!?my_server_abort@@YAXXZ() 7ff7811b643a mysqld.exe!?my_abort@@YAXXZ() 7ff7813ec579 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff78133bd51 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78133d5da mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78133c7da mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78135e3f4 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff7813ae091 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff7813ab7b4 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7fff9f85fb80 ucrtbase.dll!_o__realloc_base() 7fffa22784d4 KERNEL32.DLL!BaseThreadInitThunk() 7fffa26a1791 ntdll.dll!RtlUserThreadStart() The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 13:25:16 UTC - mysqld got exception 0x16 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 7ff7811cfd48 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z() 7ff78040004b mysqld.exe!?print_fatal_signal@@YAXH@Z() 7ff7803ffe13 mysqld.exe!?my_server_abort@@YAXXZ() 7ff7811b643a mysqld.exe!?my_abort@@YAXXZ() 7ff7813ec579 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff78133bd51 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78133d5da mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78133c7da mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z() 7ff78135e3f4 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff7813ae091 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7ff7813ab7b4 mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z() 7fff9f85fb80 ucrtbase.dll!_o__realloc_base() 7fffa22784d4 KERNEL32.DLL!BaseThreadInitThunk() 7fffa26a1791 ntdll.dll!RtlUserThreadStart() The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.
感觉其中**Operating system error number 995 in a file operation.**的部分应该是主要原因。
13-Oct-2023 14:22:31.449 INFO [http-nio-80-exec-4] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986 at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:483) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:682) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:810)
Exception in thread "main" com.alibaba.fastjson2.JSONException: illegal input, offset 647, char [ at com.alibaba.fastjson2.JSONReader.read(JSONReader.java:2043) at com.alibaba.fastjson2.reader.ObjectReaderImplMap.readObject(ObjectReaderImplMap.java:434) at com.alibaba.fastjson2.reader.ORG_2_12_TicketsDto.readObject(Unknown Source) at com.alibaba.fastjson2.reader.ORG_1_4_TicketsQueryRespDto.readObject(Unknown Source) at com.alibaba.fastjson2.JSON.parseObject(JSON.java:726) at com.alibaba.fastjson2.JSONObject.parseObject(JSONObject.java:1987) at FastJsonTest.main(FastJsonTest.java:145)
原因:实体类中List使用了泛型接收
1 2
/**容联返回工单数据*/ private List<TicketsDto> data;
解决:去掉泛型声明
1
private List data;
根本原因是该List属性的set方法上不能加泛型
服务停止脚本
1 2 3 4 5 6 7 8
@echo off set port=9001 for /f "tokens=1-5" %%i in ('netstat -ano^|findstr ":%port%"') do ( echo kill the process %%m who use the port taskkill /pid %%m -t -f goto q ) :q
这是一个批处理(Batch)脚本,主要用来查找并终止使用特定端口的进程。我们可以逐行解释这个脚本:
@echo off: 关闭命令的回显,这样在执行脚本时不会显示命令本身。
set port=9001: 设置变量port的值为9001,这是你要查找和终止进程使用的端口号。
for /f "tokens=1-5" %%i in ('netstat -ano^|findstr ":%port%"') do (: 这是一个for循环,它使用netstat -ano命令来获取当前系统所有打开的网络连接和监听的端口,然后通过findstr ":%port%"筛选出使用特定端口的行。
I just ran into this issue and I found a fix (at least for my case). Eventually, while trying to find the issue, I got the log message that Spring Cloud 2022.0.XX is not compatible with Spring Boot 3.2.XX.