40s News Express
- WeChat PC will support automatic login
- Sogou announces completion of merger with Tencent
- The European Union may force electronic equipment to use universal chargers
- Huabei will be fully integrated into the central bank's credit information system, and users will not be able to use it if they refuse to access
- Regarding the unofficial domestic deployment of Vue / Vite Chinese documents
- Cook talks about the leak of secrets to the media at the staff meeting: full investigation will be done
- Google takes the Indian antitrust agency to court: Illegal disclosure of 750 pages of investigation report
- Django 4.0 alpha 1 released
- Spring Boot 2.5.5 official version released
- HTTP/3 support in .NET 6
- Forest v1.5.3 official version released
- Swift 5.5 released
Industry Information
WeChat PC will support automatic login
According to Weibo netizens, new functions have been added to the WeChat Windows client. After logging in to WeChat on the PC side, check "Automatically log in to this device" on the mobile phone. Next time you log in to WeChat, you can complete the PC side without confirming the phone. Log in. In the settings of the PC, there is also an option switch for "Auto Login". After it is turned on, you will not need a mobile phone to confirm when you log in to WeChat on this machine.
Sogou announces completion of merger with Tencent
Sogou issued an announcement announcing the completion of the merger with Tencent. After the merger is completed, Sogou will become an indirect wholly-owned subsidiary of Tencent Holdings and complete its delisting. This is also the first time that Sogou has disclosed further details of the merger since the State Administration for Market Regulation unconditionally approved Tencent Holdings Co., Ltd.'s acquisition of Sogou's shares on July 13 this year.
The European Union may force electronic equipment to use universal chargers
According to reports, the European Commission proposed a bill on Thursday that requires manufacturers of electronic products to provide unified chargers for mobile electronic products such as mobile phones and tablets. The bill has been discussed since 2009, but due to opposition from some manufacturers, there has been no progress.
The bill will have a great impact on Apple, and the iPhone still uses the Lightning interface. Apple has said that if the connector is forced to be unified into one specification, it will hinder innovation and create a huge amount of electronic waste.
Huabei will be fully integrated into the central bank's credit information system, and users will not be able to use it if they refuse to access
Huabei announces the latest progress of access to credit investigation work. The announcement shows that, under the guidance of the central bank's credit investigation management department, Huabei is gradually advancing its access to the central bank's credit investigation system. At present, on the basis of obtaining user authorization, some users have been able to inquire about Huabei records in their credit report. In the future, credit reporting services will gradually cover all users. Huabei credit information will be submitted by formal licensed financial institutions such as Chongqing Ant Consumer Finance Co., Ltd. or cooperative banks. The integration of consumer financial products into credit reporting is a conventional measure. Previously, Weiwei, Baitiao and other products have been connected to credit reporting.
Regarding the unofficial domestic deployment of Vue / Vite Chinese documents
You Yuxi, the founder of Vue.js, posted on the 22nd that some domestic users deployed Chinese documents under other domain names without communicating with the Vue team, and named two websites: vitejs.cn and vue3js.cn .
He emphasized that although the Chinese documents of Vue/Vite are open sourced under the MIT agreement, the documents themselves are copyrighted. Without the approval of the official translation team, unauthorized deployment is an act of disrespect for translators’ labor, and called for the deployment of these websites. Of users stopped similar behavior.
Cook talks about the leak of secrets to the media at the staff meeting: full investigation will be done
Apple CEO Tim Cook sent an e-mail within the company on Tuesday to explain how the content of the staff meeting last week was leaked to the media. He said that Apple is "doing everything we can to identify the identity of the leaker," and pointed out that "the person who leaked the information does not belong to Apple."
On September 17, Cook announced at the staff meeting that Apple will require high-frequency nucleic acid testing for employees who have not been vaccinated, but Apple will not mandate vaccinations. He also said that after Epic's case against Apple's monopoly is over, he "looks forward to the company's continued advancement." Shortly after the conference ended, both pieces of news were leaked to the American technology media The Verge. Cook compared this incident to a product information leak, and Apple has spared no effort to track down such incidents in the past.
Google takes the Indian antitrust agency to court: Illegal disclosure of 750 pages of investigation report
According to reports, Google announced on Thursday that it has filed a lawsuit against India’s antitrust regulator "Competition Commission of India" (CCI) because CCI had previously launched an antitrust investigation against Google, but this confidential investigation report was leaked. .
Several media reports on Saturday said that a CCI investigation found that Google abused its dominance of the Android operating system in the Indian market and used its "strong financial strength" to illegally harm competitors. Google responded at the time that it looked forward to working with CCI to show how Android can bring more competition and innovation, rather than stifle competition and innovation.
On Wednesday, Google said in a statement that it has filed a lawsuit against CCI in the Delhi High Court to prevent further illegal disclosure of confidential investigation results. Google said that the company is protesting against this type of confidence-damaging behavior, which undermines Google’s ability to protect itself, and also damages Google and its partners.
Google said in a statement: "Throughout the investigation, we fully cooperate and maintain confidentiality; we hope and expect that the regulatory agencies that we contact will also maintain the same level of confidentiality."
The Indian antitrust regulator launched an investigation into Google in 2019, saying that Google appeared to use its Android dominance to weaken the ability of device manufacturers to choose alternative versions of the operating system and force them to pre-install Google applications.
And last Saturday, a 750-page investigation report from CCI was leaked. According to media reports, the report believes that Google makes it difficult for device vendors to use alternative versions of the Android system, and uses its influence to force vendors to pre-install Google applications on their devices.
According to the report, Google’s mandatory pre-installation of apps “is equivalent to imposing unfair conditions on device manufacturers”, violating India’s competition laws. The report also said that Google used its Play Store application store status to protect Google's dominant position in India. The Google App Store’s policies are also one-sided and vague, and biased.
The latest technology trends
Django 4.0 alpha 1 released
Django 4.0 officially released the first alpha version, marking that it has entered the feature freeze phase. Django is an open source web application framework, written in Python. The main changes in Django 4.0 are as follows:
- Use zoneinfo as the default time zone implementation;
- Create functional unique constraints;
- Add scrypt password hasher, the new scrypt password hasher is more secure than PBKDF2;
- Built-in support for Redis caching backend, this feature requires redis-py 3.0.0 or higher and template-based form rendering
Spring Boot 2.5.5 official version released
release notes
Spring Boot 2.5.5 was officially released on September 23. This version includes 41 bug fixes, documentation improvements, and dependency upgrades.
update content
bug fix
- Fix executor endpoint will not clean up SPRING\_APPLICATION\_JSON by default #28081
- When using Flyway and Spring Integration DataSource to initialize, the startup fails due to non-empty mode #28079
- When the filter throws exceptions other than NestedServletException, Web MVC metrics may have the wrong state #28069
- When the archive file name contains characters reserved in the URL, the embedded Undertow throws MalformedURLException #28032
- Concurrent image build causes an error when deleting the builder image #27993
- War deployment in standalone Tomcat will cause memory leaks (metaspace) #27987
- IndexOutOfBoundsException appears when running a Zip64 jar file larger than 4GB #27900
- Azure App Service is not correctly detected on Windows #27819
- "The field cannot have an existing value" error when @MockBean is combined with @Repeat#27798
- When the destination of the routing data source has a null routing key, a NullPointerException appears in the RoutingDataSourceHealthContributor #27698
Documentation
- Document that devtools restart does not work when using AspectJ weaving #28083
- The default value of spring.data.elasticsearch.client.reactive.endpoints is not documented #28072
- Clarify that Selenium automatic configuration requires HtmlUnit #27943
- spring-boot-starter-parent configure Java compilation and use -parameters document #27885
- Fix inconsistent development tool documentation #27876
- Fix typo in javadoc #27873
- Document how to use WebTestClient to parameterize the output directory of a REST document #27803
- Documentation support for Java 17 #26767
Dependency upgrade
- Upgrade to Ehcache3 3.9.6 #27974
- Upgrade to Glassfish EL 3.0.4 #27975
- Upgrade to Groovy 3.0.9 #27976
- Upgrade to Gson 2.8.8 #27977
- Upgrade to Jackson Bom 2.12.5 #27978
- Upgrade to Jetty EL 9.0.52 #27979
- Upgrade to jOOQ 3.14.15 #28088
- Upgrade to Kotlin 1.5.31 #28089
- Upgrade to Kotlin Coroutines 1.5.2 #27982
- Upgrade to Lettuce 6.1.5.RELEASE #28031
- Upgrade to Logback 1.2.6 #27983
- Upgrade to Maven War Plugin 3.3.2 #27984
- Upgrade to Micrometer 1.7.4 #27916
- Upgrade to Netty 4.1.68.Final #27985
- Upgrade to Netty tcNative 2.0.43.Final #27986
- Upgrade to Reactor 2020.0.11 #27914
- Upgrade to SendGrid 4.7.5 #28109
- Upgrade to Spring Data 2021.0.5 #27917
- Upgrade to Spring Framework 5.3.10 #27915
- Upgrade to Spring HATEOAS 1.3.4 #27970
- Upgrade to Spring Integration 5.5.4 #27949
- Upgrade to Spring Kafka 2.7.7 #27918
- Upgrade to Tomcat 9.0.53 #27963
HTTP/3 support in .NET 6
According to the introduction of the official blog, .NET 6 provides preview support for HTTP/3, mainly including the following scenarios:
- In Kestrel, HTTP.Sys and IIS, used for ASP.NET server
- Send outbound request in HttpClient
- For gRPC
The .NET development team stated that the RFC for HTTP/3 has not yet been finalized, but they still introduced HTTP/3 into .NET 6 to facilitate users to start experimenting, but this is only a preview feature of .NET 6-because it does not Meets the quality standards of the rest of .NET 6. Therefore, more extensive testing with other servers and clients is required to ensure compatibility, especially in border cases.
Forest v1.5.3 official version released
key update content:
1. Added Forest shortcut interface
2. Request success condition/retry condition
new features:
- feat: Forest shortcut interface (#I4893Q)
- feat: Support global variable dynamic binding method (#I478N2)
- feat: Supports string templates referencing properties (#I3P1QK)
- feat: Support to get the response reason phrase, that is, the response status text (#I4BJVF)
- feat: Custom combination annotation (#I4BISF)
- feat: You can customize the conditions for whether the request is successful (#I4AEMT)
- feat: The host address and port number can be dynamically set (#I4AEJ8)
- feat: Custom retry conditions (#I493N3)
- feat: Added OnRetry callback function (#I493N6)
- feat: Add @Headers annotation (#I4BJQ6)
- feat: Forest request interface inheritance rules (#I4B0N7)
- feat: Automatic redirection control (#I4B0FM)
- feat: Global variables support dynamic binding method (#I478N2)
- feat: Display the back-end framework name in the request log (#I4AKTD)
- feat: Create a new forest-mock subproject (#I468JB)
Bug of
- fix: In POST request, empty Map cannot be converted into {} JSON string (#I455O2)
- fix: The filter parameter is always the first parameter (#I43VV0)
- fix: The content-type of the custom request header will be replaced with uppercase (#I46WNW)
- fix: If the converter is not configured in the Spring project, the Converter will not be found (#I46FKV)
- fix: Response cannot be parsed normally without Content-Type and Content-Encoding headers (#I455PO)
- fix: When a 302 request is requested, Forest will automatically access the redirected url, causing the 302 response header to not be available (#I4AF3B)
- fix: SpringSSLKeyStore failed to initialize in Spring Fix: When a converter with ForestConfiguration parameters is configured, the initialization fails in springboot (#I4AKT3)
- fix: When using the upload file interface in a multi-threaded environment, a stack overflow error will be reported after a long running time (#I37UGY)
- fix: BeanPostProcessor interface is not compatible in the lower version of springboot environment
Swift 5.5 released
The stable version of Swift 5.5 is now released. This is a large-scale version that introduces new ways of concurrent programming, including async/await syntax, structured concurrency, and Actors.
Some of the proposals in the Swift Evolution process have also been implemented in Swift 5.5:
- SE-0291 bag collection
- SE-0293 Extend attribute wrappers to function and closure parameters
- SE-0295 Codable composition of enumerations with associated values
- SE-0296 Async/await
- Concurrent interoperability between SE-0297 and Objective-C
- SE-0298 Async/Await: Sequences
- SE-0299 Extend Static Member Lookup in Generic Contexts
- SE-0300 is used to connect asynchronous tasks with continuation of synchronous code
- SE-0304 Structured Concurrency
- SE-0306 Actors
- SE-0307 allows the use of CGFloat and Double types interchangeably
- SE-0308 if for postfix member expressions
- SE-0310 Valid read-only attributes
- SE-0311 Task Local Values
- SE-0313 Improved control of actor isolation
- SE-0314 AsyncStream and AsyncThrowingStream
- SE-0316 Global actors
- SE-0317 async let bindings
- SE-0319 Conform Never to Identifiable
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。