text:
[SPARK-46611][CORE] Remove ThreadLocal by replace SimpleDateFormat with DateTimeFormatter

What changes were proposed in this pull request?
This PR propose to remove ThreadLocal by replace SimpleDateFormat with DateTimeFormatter.
Why are the changes needed?
SimpleDateFormat is not thread safe, so we wrap it with ThreadLocal.
DateTimeFormatter is thread safe, we can use it instead.
According to the javadoc of SimpleDateFormat, it recommended to use DateTimeFormatter too.

In addition, DateTimeFormatter have better performance than SimpleDateFormat too.
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
GA tests.
Was this patch authored or co-authored using generative AI tooling?
'No'.

There are other usages of SimpleDateFormat which are candidates for this pattern.

I will check.

ping @dongjoon-hyun @srowen

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195431809。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195431809.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195432886。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195432886.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195434035。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195434035.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195434855。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195434855.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195436316。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195436316.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195437543。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195437543.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195438601。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195438601.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195439902。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195439902.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195441010。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195441010.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195442305。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195442305.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195443373。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195443373.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195444707。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195444707.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195445869。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195445869.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195447327。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195447327.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195448316。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195448316.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195449442。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195449442.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195451089。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195451089.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195452405。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195452405.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195453736。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195453736.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195454870。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195454870.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195455952。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195455952.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195456973。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195456973.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195458623。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195458623.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195459708。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195459708.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195460870。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195460870.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195462227。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195462227.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195463590。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195463590.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195464943。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195464943.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195465744。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195465744.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195466919。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195466919.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195468388。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195468388.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

I sent info about the spam from @llkj1 to GitHub support.

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195528798。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195528798.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是 102195530026。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is 102195530026.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

I tried to block the user and have been deleting the spam

is this one ready to go?

Merged into master. Thanks @beliefer@srowen @mridulm

@LuciferYang @srowen @mridulm Thank you!

authors: LuciferYang MaxGekk beliefer llkj1 srowen


text:
[SPARK-7646][SQL] Create table from dataframe support for JDBCDataSource

Supported  CreatableRelationProvider support for JDBCDataSource.
df.saveAsTable to JDBC data source, should create a table and write dataframe content to table.

Can one of the admins verify this patch?

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #32731 has started for   PR 6155 at commit 6696c0b.

Test build #32731 has finished for   PR 6155 at commit 6696c0b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class Pipeline(override val uid: String) extends Estimator[PipelineModel]
final class DecisionTreeClassifier(override val uid: String)
final class GBTClassifier(override val uid: String)
class LogisticRegression(override val uid: String)
final class OneVsRest(override val uid: String)
final class RandomForestClassifier(override val uid: String)
class BinaryClassificationEvaluator(override val uid: String)
final class Binarizer(override val uid: String)
final class Bucketizer(override val uid: String)
class ElementwiseProduct(override val uid: String)
class HashingTF(override val uid: String) extends UnaryTransformer[Iterable[_], Vector, HashingTF]
final class IDF(override val uid: String) extends Estimator[IDFModel] with IDFBase
class Normalizer(override val uid: String) extends UnaryTransformer[Vector, Vector, Normalizer]
class OneHotEncoder(override val uid: String)
class PolynomialExpansion(override val uid: String)
class StandardScaler(override val uid: String) extends Estimator[StandardScalerModel]
class StringIndexer(override val uid: String) extends Estimator[StringIndexerModel]
class Tokenizer(override val uid: String) extends UnaryTransformer[String, Seq[String], Tokenizer]
class RegexTokenizer(override val uid: String)
class VectorAssembler(override val uid: String)
class VectorIndexer(override val uid: String) extends Estimator[VectorIndexerModel]
final class Word2Vec(override val uid: String) extends Estimator[Word2VecModel] with Word2VecBase
class Param[T](val parent: String, val name: String, val doc: String, val isValid: T => Boolean)
class DoubleParam(parent: String, name: String, doc: String, isValid: Double => Boolean)
class IntParam(parent: String, name: String, doc: String, isValid: Int => Boolean)
class FloatParam(parent: String, name: String, doc: String, isValid: Float => Boolean)
class LongParam(parent: String, name: String, doc: String, isValid: Long => Boolean)
class BooleanParam(parent: String, name: String, doc: String) // No need for isValid
class ALS(override val uid: String) extends Estimator[ALSModel] with ALSParams
final class DecisionTreeRegressor(override val uid: String)
final class GBTRegressor(override val uid: String)
class LinearRegression(override val uid: String)
final class RandomForestRegressor(override val uid: String)
class CrossValidator(override val uid: String) extends Estimator[CrossValidatorModel]
trait Identifiable

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32731/
Test PASSed.

Merged build finished. Test PASSed.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

source: gharchive/pull-request

authors: AmplabJenkins SparkQA gvramana rxin

repo: apache/spark

license_type: permissive

license_source: github-api


text:
Revert SPARK-6910 and SPARK-9027

Revert #7216 and #7386.  These patch seems to be causing quite a few test failures:
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.GeneratedMethodAccessor322.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.spark.sql.hive.client.Shim_v0_13.getPartitionsByFilter(HiveShim.scala:351)
	at org.apache.spark.sql.hive.client.ClientWrapper$$anonfun$getPartitionsByFilter$1.apply(ClientWrapper.scala:320)
	at org.apache.spark.sql.hive.client.ClientWrapper$$anonfun$getPartitionsByFilter$1.apply(ClientWrapper.scala:318)
	at org.apache.spark.sql.hive.client.ClientWrapper$$anonfun$withHiveState$1.apply(ClientWrapper.scala:180)
	at org.apache.spark.sql.hive.client.ClientWrapper.retryLocked(ClientWrapper.scala:135)
	at org.apache.spark.sql.hive.client.ClientWrapper.withHiveState(ClientWrapper.scala:172)
	at org.apache.spark.sql.hive.client.ClientWrapper.getPartitionsByFilter(ClientWrapper.scala:318)
	at org.apache.spark.sql.hive.client.HiveTable.getPartitions(ClientInterface.scala:78)
	at org.apache.spark.sql.hive.MetastoreRelation.getHiveQlPartitions(HiveMetastoreCatalog.scala:670)
	at org.apache.spark.sql.hive.execution.HiveTableScan.doExecute(HiveTableScan.scala:137)
	at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:90)
	at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:90)
	at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:147)
	at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:89)
	at org.apache.spark.sql.execution.Exchange$$anonfun$doExecute$1.apply(Exchange.scala:164)
	at org.apache.spark.sql.execution.Exchange$$anonfun$doExecute$1.apply(Exchange.scala:151)
	at org.apache.spark.sql.catalyst.errors.package$.attachTree(package.scala:48)
	... 85 more
Caused by: MetaException(message:Filtering is supported only on partition keys of type string)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree$FilterBuilder.setError(ExpressionTree.java:185)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree$LeafNode.getJdoFilterPushdownParam(ExpressionTree.java:452)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree$LeafNode.generateJDOFilterOverPartitions(ExpressionTree.java:357)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree$LeafNode.generateJDOFilter(ExpressionTree.java:279)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree$TreeNode.generateJDOFilter(ExpressionTree.java:243)
	at org.apache.hadoop.hive.metastore.parser.ExpressionTree.generateJDOFilterFragment(ExpressionTree.java:590)
	at org.apache.hadoop.hive.metastore.ObjectStore.makeQueryFilterString(ObjectStore.java:2417)
	at org.apache.hadoop.hive.metastore.ObjectStore.getPartitionsViaOrmFilter(ObjectStore.java:2029)
	at org.apache.hadoop.hive.metastore.ObjectStore.access$500(ObjectStore.java:146)
	at org.apache.hadoop.hive.metastore.ObjectStore$4.getJdoResult(ObjectStore.java:2332)

https://amplab.cs.berkeley.edu/jenkins/view/Spark-QA-Test/job/Spark-Master-Maven-with-YARN/2945/HADOOP_PROFILE=hadoop-2.4,label=centos/testReport/junit/org.apache.spark.sql.hive.execution/SortMergeCompatibilitySuite/auto_sortmerge_join_16/

Merged build triggered.

Merged build started.

@piaozhexiu could you possibly reopen your PR + mine once this revert is merged.  @liancheng and I can then help to reproduce the issues so we can try merging again.

Test build #37299 has started for   PR 7409 at commit 92fabd3.

@marmbrus sure, I can do that.

Test build #37299 has finished for   PR 7409 at commit 92fabd3.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SparkListenerBlockUpdated(blockUpdatedInfo: BlockUpdatedInfo) extends SparkListenerEvent
case class BlockUpdatedInfo(
class StorageListener(storageStatusListener: StorageStatusListener) extends BlockStatusListener
case class Exchange(newPartitioning: Partitioning, child: SparkPlan) extends UnaryNode

Merged build finished. Test PASSed.

I'm going to merge this.

Thanks!
On Jul 14, 2015 10:57 PM, "Reynold Xin" notifications@github.com wrote:

I'm going to merge this.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/7409#issuecomment-121499037.

authors: AmplabJenkins SparkQA marmbrus piaozhexiu rxin


text:
Check partitionId's range in ExternalSorter#spill()

See this thread for background:
http://search-hadoop.com/m/q3RTt0rWvIkHAE81
We should check the range of partition Id and provide meaningful message through exception.
Alternatively, we can use abs() and modulo to force the partition Id into legitimate range. However, expectation is that user should correct the logic error in his / her code.

Merged build triggered.

Merged build started.

Test build #42280 has started for   PR 8703 at commit 63dfe11.

Test build #42280 has finished for   PR 8703 at commit 63dfe11.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42280/
Test FAILed.

please file JIRA

Merged build triggered.

Merged build started.

Test build #42287 has started for   PR 8703 at commit 04aa45e.

Test build #42287 has finished for   PR 8703 at commit 04aa45e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42287/
Test PASSed.

Can you just use one require statement to make this more compact? and string interpolation

Merged build triggered.

Merged build started.

Test build #42333 has started for   PR 8703 at commit 0e86ae8.

Test build #42333 has finished for   PR 8703 at commit 0e86ae8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42333/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #42338 has started for   PR 8703 at commit a293906.

LGTM

Test build #42338 has finished for   PR 8703 at commit a293906.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42338/
Test PASSed.

authors: AmplabJenkins SparkQA andrewor14 srowen tedyu


text:
STORM-1673 log4j2/worker.xml refers old package of LoggerMetricsConsumer

fix missing package changes

+1

authors: HeartSaVioR knusbaum

repo: apache/storm


text:
SUBMARINE-577. Add pypi badge in README

What is this PR for?
add pypi badge in README
What type of PR is it?
[ Documentation]
Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-577
How should this be tested?

First time? Setup Travis CI as described on https://submarine.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

LGTM

authors: aeioulisa pingsutw

repo: apache/submarine


text:
SUBMARINE-807. Create a tensorboard for a single user

What is this PR for?
Create a submarine tensorboard for a single user via the submarine operator.
Reference: https://github.com/apache/submarine/blob/master/helm-charts/submarine/templates/submarine-tensorboard.yaml
What type of PR is it?
[Feature]
Todos
What is the Jira issue?
https://issues.apache.org/jira/projects/SUBMARINE/issues/SUBMARINE-807
How should this be tested?
# initialization
# Step1: Register Custom Resource Definition
kubectl apply -f artifacts/examples/crd.yaml

# Step2: Create a Custom Resource
kubectl apply -f artifacts/examples/example-submarine.yaml

# in-cluster
cd submarine/submarine-cloud-v2
eval $(minikube docker-env)
make image
kubectl apply -f artifacts/examples/submarine-operator-service-account.yaml
kubectl apply -f artifacts/examples/submarine-operator.yaml

# out-of-cluster
go build -o submarine-operator
./submarine-operator

# helm
cd submarine
helm install submarine ./helm-charts/submarine

Screenshots (if appropriate)

PersistentVolume (helm)

PersistentVolume (operator)

Note: PersistentVolumes are not namespaced resources, so we add the namespace as a suffix to distinguish them

PersistentVolumeClaim (helm)

PersistentVolumeClaim (operator)

Deployment (helm)

Deployment (operator)

Service (helm)

Service (opertator)

IngressRoute (helm)

IngressRoute (operator)

Workbench

Video
Questions:

Do the license files need updating? No
Are there breaking changes for older versions? No
Does this need new documentation? No

@MortalHappiness Can you help Ken review this PR?

LGTM


text:
Change Country map chart base on filter on dashboard

I am using superset ver 0.36.0
i am having a request about changing map of Country map chart on dashboard.Anyone can give a optimal solution for this problem.

I searched for a solution, last year, but there isn't. I had to write a web service that edits JSON of slices.

I searched for a solution, last year, but there isn't. I had to write a web service that edits JSON of slices.

So sad @@. thanks for your reply

@CaptainHoangLe this bug is a bit of an antique. I'm closing it in hopes that you found some sort of workaround/solution. If anyone can validate that this is still an issue in Superset 2.0.x with Dashboard Native Filters (rather than the deprecated Filter Box component), we can revisit/reopen this with updated context. Thanks!

For my company, I partly solved my using handlebar chart, with an iframe inside that opens a country map chart using a variable with map name.

source: gharchive/issue

authors: CaptainHoangLe rusackas zufolo441

repo: apache/superset


text:
Fatal error when export dashboards

I want to export a dashboard with the api and I have the result "Fatal error"
I try to export the default dashboard: World Bank's Data
With the url:
http://localhost:8089/api/v1/dashboard/export/?q=[1]
It returns the message: "Fatal error"
I have the same result with docker installation or installation from scratch

Environment

browser type and version: chrome/firefox
superset version: 1.3.1
python version: 3.8.19
node.js version: v.17.0.1

what feature flags did you enable. can you provide detailed repo steps? thanks!

These are the configurations and the commands that I execute:
Ubuntu 20.04.3 LTS
Python 3.8.10
pip freeze
aiohttp==3.7.4.post0
alembic==1.7.4
amqp==2.6.1
apache-superset==1.3.1
apispec==3.3.2
async-generator==1.10
async-timeout==3.0.1
attrs==21.2.0
Babel==2.9.1
backoff==1.11.1
billiard==3.6.4.0
bleach==3.3.1
Brotli==1.0.9
cachelib==0.1.1
celery==4.4.7
certifi==2021.10.8
cffi==1.15.0
chardet==4.0.0
click==7.1.2
colorama==0.4.4
convertdate==2.3.2
cron-descriptor==1.2.24
croniter==1.0.15
cryptography==35.0.0
defusedxml==0.7.1
deprecation==2.1.0
dnspython==2.1.0
email-validator==1.1.3
Flask==1.1.4
Flask-AppBuilder==3.3.3
Flask-Babel==1.0.0
Flask-Caching==1.10.1
Flask-Compress==1.10.1
Flask-JWT-Extended==3.25.1
Flask-Login==0.4.1
Flask-Migrate==3.1.0
Flask-OpenID==1.3.0
Flask-SQLAlchemy==2.5.1
flask-talisman==0.8.1
Flask-WTF==0.14.3
geographiclib==1.52
geopy==2.2.0
graphlib-backport==1.0.3
gunicorn==20.0.4
h11==0.12.0
holidays==0.10.3
humanize==3.12.0
idna==3.3
importlib-metadata==4.8.1
importlib-resources==5.2.2
isodate==0.6.0
itsdangerous==1.1.0
Jinja2==2.11.3
jsonschema==3.2.0
kombu==4.6.11
korean-lunar-calendar==0.2.1
Mako==1.1.5
Markdown==3.3.4
MarkupSafe==2.0.1
marshmallow==3.13.0
marshmallow-enum==1.5.1
marshmallow-sqlalchemy==0.23.1
msgpack==1.0.2
multidict==5.2.0
numpy==1.21.2
outcome==1.1.0
packaging==21.0
pandas==1.2.5
parsedatetime==2.6
pgsanity==0.2.9
pkg_resources==0.0.0
polyline==1.4.0
prison==0.2.1
psycopg2==2.9.1
psycopg2-binary==2.8.5
pyarrow==4.0.1
pycparser==2.20
PyJWT==1.7.1
PyMeeus==0.5.11
pyOpenSSL==21.0.0
pyparsing==2.4.7
pyrsistent==0.18.0
python-dateutil==2.8.2
python-dotenv==0.19.1
python-geohash==0.8.5
python3-openid==3.2.0
pytz==2021.3
PyYAML==6.0
redis==3.5.3
selenium==4.0.0
simplejson==3.17.5
six==1.16.0
slackclient==2.5.0
sniffio==1.2.0
sortedcontainers==2.4.0
SQLAlchemy==1.3.24
SQLAlchemy-Utils==0.36.8
sqlparse==0.3.0
tabulate==0.8.9
trio==0.19.0
trio-websocket==0.9.2
typing-extensions==3.10.0.2
urllib3==1.26.7
vine==1.3.0
webencodings==0.5.1
Werkzeug==1.0.1
wsproto==1.0.0
WTForms==2.3.3
WTForms-JSON==0.3.3
yarl==1.7.0
zipp==3.6.0
I execute:
superset run -p 8089 --with-threads --reload --debugger
Login in:
http://localhost:8089/superset/welcome/
I execute:
http://localhost:8089/api/v1/dashboard/export/?q=[5]
It works.
I execute:
http://localhost:8089/api/v1/dashboard/export/?q=[1]
I have the message: {"message":"Fatal error"}

Seems to be working just fine in Superset 2.0.1 as far as I can currently tell. Worth noting, perhaps, that I have the VERSIONED_EXPORT flag turned on. If you're still encountering this behavior in newer versions, let us know here or on Slack, and we can re-open this issue with additional/updated details. Thanks!

authors: jordiisidro junlincc rusackas


text:
unable to emit filter from country map

Hi all,
is it possible to implement filter emitting from country map charts?
many thanks!

I think crossfilters are emitted this way now :)


text:
feat: clear search on dataset change

SUMMARY
resets metrics search input to empty state on dataset change.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/17326228/106697785-5759cc00-6594-11eb-8c09-343a7b074755.mov
TEST PLAN
In datasource panel change datasource and check if input field is clear from prev state.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12909 (e22748b) into master (fab6238) will decrease coverage by 3.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12909      +/-   ##
==========================================
- Coverage   66.97%   63.70%   -3.28%
==========================================
  Files        1026      490     -536
  Lines       50330    30243   -20087
  Branches     5242        0    -5242
==========================================
- Hits        33711    19267   -14444
+ Misses      16485    10976    -5509
+ Partials      134        0     -134

Flag
Coverage Δ

cypress
?

javascript
?

python
63.70% <ø> (-0.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/db_engine_specs/hive.py
73.84% <0.00%> (-17.31%)
:arrow_down:

superset/db_engine_specs/presto.py
81.38% <0.00%> (-6.71%)
:arrow_down:

superset/db_engine_specs/sqlite.py
90.62% <0.00%> (-6.25%)
:arrow_down:

superset/utils/celery.py
86.20% <0.00%> (-3.45%)
:arrow_down:

superset/db_engine_specs/mysql.py
89.79% <0.00%> (-2.05%)
:arrow_down:

superset/views/database/mixins.py
80.70% <0.00%> (-1.76%)
:arrow_down:

superset/result_set.py
96.69% <0.00%> (-1.66%)
:arrow_down:

superset/models/core.py
87.22% <0.00%> (-1.64%)
:arrow_down:

superset/db_engine_specs/base.py
84.76% <0.00%> (-1.48%)
:arrow_down:

... and 547 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fab6238...e22748b. Read the comment docs.

authors: codecov-io pkdotson


text:
fix: consistent left margin for dashboard layout.

SUMMARY

Oops! Erroneously merged this to a feature branch instead of master. Ugh.
See https://github.com/apache/superset/pull/13884 for a history/comments, and prior approvals.
A recent PR, #13723, made some changes around how the sidebar works for the native filter features. This looks great when the feature flag is on, but when the feature flag is off, we lose the left margin, as reported in #13863.
This PR makes sure the styling is consistent, by considering feature flag setting, and only toggling off dashboardFiltersOpen (which sets the margin) when the feature is indeed enabled.
@simcha90 if you have a more elegant way to tackle this, or ideas for sufficient testing to cover this possible regression, please let me know your thoughts.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

BEFORE (DASHBOARD_NATIVE_FILTERS set to False):

AFTER (DASHBOARD_NATIVE_FILTERS set to False):

AFTER (DASHBOARD_NATIVE_FILTERS set to True):

TEST PLAN

Verified that the margin is restored, in view and edit mode, with the DASHBOARD_NATIVE_FILTERS flag on and off.
ADDITIONAL INFORMATION

[x] Has associated issue:  Fixes #13863
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

🏷 2021.13

authors: rusackas yousoph


text:
Reduce the number of DB requests made in ValidateServerCapabilities()

I'm submitting a ...

improvement request (usability, performance, tech debt, etc.)

Traffic Control components affected ...

Traffic Ops

Current behavior:
TO currently makes a DB request per server in the ValidateServerCapabilities() function: https://github.com/apache/trafficcontrol/blob/b99eda51b03505f48d67aadf481d16470455a7f4/traffic_ops/traffic_ops_golang/deliveryservice/servers/servers.go#L541. When a delivery service is being assigned to a large number of servers, this slows down the total execution time unnecessarily.
New behavior:
Instead of making a DB request per server, the function should make a single DB request to get data for all the servers at once, then perform the validation. This will make it much faster to assign a delivery service to large numbers of servers at a time.
Minimal reproduction of the problem with instructions:
Assign a delivery service with required capabilities to a large number of servers with those capabilities at a time.

@rawlinp I would like to take this up. Could you please assign this to me?

@rawlinp Just want to check I am going in the right direction before I start on this.

I am thinking of adding a modifying GetServerCapabilitiesFromName method to take a list of server names and then modify the query in way that I can fetch the data/capabilities for all the servers and return them for validation.
Also, I would like to know where I can get more information on how to construct the query. Thanks.

@RaviTezu that sounds like a reasonable idea. This query should be a good example for you to modify for GetServerCapabilitiesFromName: https://github.com/apache/trafficcontrol/blob/b99eda51b03505f48d67aadf481d16470455a7f4/traffic_ops/traffic_ops_golang/deliveryservice/deliveryservices_required_capabilities.go#L348-L360

authors: RaviTezu rawlinp

repo: apache/trafficcontrol


text:
many strange ERR_CLIENT_ABORTand cache behavior

hi,all
when enable read_while_writer,
i found many ERR_CLIENT_ABORT log records indicated 'ttms' all around 900000,
and this is the timeout_in i set for transaction activity...
CONFIG proxy.config.cache.enable_read_while_writer INT 1 CONFIG proxy.config.http.transaction_active_timeout_in INT 900

following are the log samples
1498091553.134 900278 124.135.108.186 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091553.148 900235 114.217.181.44 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091553.286 900089 42.232.247.107 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091553.527 900254 112.248.66.153 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091553.978 900840 112.239.66.236 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091554.133 900684 112.248.185.147 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091554.808 900425 115.51.237.29 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091555.162 900327 119.185.240.112 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.184 900329 60.24.95.104 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.290 900926 115.60.83.249 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.316 900085 27.215.180.100 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.477 900281 218.107.55.254 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.610 900761 112.245.230.166 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-" 1498091556.648 900648 1.25.18.1 ERR_CLIENT_ABORT/200 2999 GET http://update.xyz.abc.com/server5_2.txt - NONE/- text/plain "-"

If this is still an issue please reopen.

repo: apache/trafficserver


text:
ConectionTracker: remove include dep in proxy/http

I moved ConnectionTracker to iocore/net, but I missed that I accidentally brought in a dependency upon proxh/http to iocore through the extern Enable_Config_Var. This patch removes the explicit include dependency and updates the unit tests that had a link time undefined symbol error for Enable_Config_Var.

[approve ci]

[approve ci autest rocky debian]

[approve ci autest rocky]

[approve ci rocky autest]


text:
Docs: Fix few things related to the docs.

Fix missing link for TxnBox inside the plugins main doc page.
Fix doctree for Stale response plugin. They were all displayed at the doctree level, it now just show the title.

[approve ci autest]

Cherry-picked to v10.0.x


text:
Proper support for the %{URL:} conditions

This was never properly, or completely, implemented. This makes sure that
the URL conditions works as both conditions and values. Supported qualifiers
are e.g.
cond %{SEND_RESPONSE_HDR_HOOK} [AND]
cond %{CLIENT-URL:SCHEME} =http
     set-header X-Url %{CLIENT-URL}
     set-header X-Url-Scheme %{CLIENT-URL:SCHEME}
     set-header X-Url-Host %{CLIENT-URL:HOST}
     set-header X-Url-Port %{CLIENT-URL:PORT}
     set-header X-Url-Path %{CLIENT-URL:PATH}
     set-header X-Url-Query %{CLIENT-URL:QUERY}
     set-header X-Url-Matrix %{CLIENT-URL:MATRIX}

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/264/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/278/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1959/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/260/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/389/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1851/

clang-analyzer build failed! https://ci.trafficserver.apache.org/job/clang-analyzer-github/522/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/279/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/265/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/261/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1960/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1852/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/390/

clang-analyzer build failed! https://ci.trafficserver.apache.org/job/clang-analyzer-github/523/

Ship it.

authors: SolidWallOfCode atsci zwoop


text:
[ci] Use r5.large nodes for builds and lint

This uses r5.large for linting and build steps and splits lint into 2 to keep runtime down. This is a subset split off of #11120. Once task_cpp_unittest.sh is fixed so it picks up sccache we can enable these smaller nodes there as well.
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
cc @Mousius @areusch

Thanks @driazati!

authors: Mousius driazati

repo: apache/tvm


text:
[CI] Add ml_dypes dependency for all docker images

The PR #15183 adds ml_dtypes as a dependency of TVM, however, some of the CI docker images do not have ml_dtypes installed, the PR fixes the issue.
cc @yongwww , would you mind also helping upload the new images with ml_dtypes installed to docker hub?

@tvm-bot rerun

@leandron thank you for your review!
The ci_i386 DockerFile depends on ubuntu2004_install_python_package, and the docker image needs to be updated and uploaded.
Besides ci_i386, other docker images that have to be updated include ci_arm, ci_wasm, ci_riscv, ci_minimal, ci_ hexagon, ci_cpu, ci_gpu, ci_arm (they rely on ubuntu_install_python_package.sh which already has ml_dtypes as the dependency but the docker image was still out-dated).

Hi @leandron do you have any further feedback?

The temporary images might have been cleaned up. I’d suggest re running CI and throwing the test job as soon as the image rebuild finishes.
Sorry, I have no access to the temp. images configuration.

@tvm-bot rerun

My recommendation is we merge it in. I don't see any point blocking on this given it is just a dependency and unlikely break anything. The set of binary images are also still stable, aka until we change Jenkinsfile the main CI won't break

Hi @leandron , I'll upload my locally built CI image to my docker hub account, and use this docker image in #15329 , do you think it is acceptable?

Considering the minor nature of this dependency update, there seems to be no reason for us to hold back. The risk of it causing any significant disruptions is quite low. From a technical perspective, the current set of binary images remains stable and is still directed towards the previous build. This is precisely why we initially opted for the binary tag. Until we make the necessary changes to the Jenkinsfile, pointing it to the new binary, our main CI process will remain unaffected. The existing code does not currently rely on the new package, so it is highly unlikely to cause any complications. Even in the rare event that it does result in issues (though I cannot think of any at the moment), we can promptly revert the change if the binary breaks. As a result, there won't be any blockers in the CI pipeline since all builds will continue using the old binary image. Furthermore, it is probable that integrating the new dependency into the main CI process immediately will not lead to any problems. Though I may be overlooking certain aspects, my technical assessment indicates that there is minimal risk associated with incorporating the update.

authors: junrushao leandron tqchen yzh119


text:
[AutoScheduler] Add Dynamic Gradient Descent Search Algorithm for Auto-Tuning

This PR introduces the Dynamic Gradient Descent (DGD) Search algorithm for accelerating the auto-tuning process of GPU kernels within the Ansor/AutoScheduler framework. The DGD algorithm is designed to explore the search space more efficiently than the existing Genetic Algorithm-based approach. The following changes are included:

Dynamic Gradient Descent Search:

Implements a new search strategy that uses gradient descent in a multi-dimensional tile-space.
Utilizes online measurements and proxy model to guide the search process.

Record Processor:

A new class to handle the processing and modification of measure records.
Includes methods to extract and modify SP node coordinates.

This implementation is based on the algorithm described in the paper "Accelerated Auto-Tuning of GPU Kernels for Tensor Computations" presented at ICS'24.
Experimental evaluation on a number of matrix-matrix multiplication and convolution kernels shows that the DGD algorithm achieves an order-of-magnitude improvement in auto-tuning time while maintaining comparable code performance.
Usage:
To use the DGD Search algorithm, instantiate the DynamicGradientSearchTuner class with the desired parameters and call the dynamic_gradient_search method.
Example:
tuner = auto_scheduler.dynamic_gradient_search.DynamicGradientSearchTuner(task, log_file, tune_option)
tuner.dynamic_gradient_search()

Experiments setup:
The experiments used the DGD Search algorithm with a time budget of 1 hour and full duration used by Ansor, comparing the performance achieved by Ansor after suggested trials. The models used for the evaluation were Bert, ResNet-50, and MobileNetV2, with the following configurations based on the Apache blog Introducing TVM Auto-scheduler (a.k.a. Ansor):

Bert: 12000 trials, running on an Nvidia RTX 4090 for 6 hours.
ResNet-50: 20000 trials, running on an Nvidia RTX 4090 for 10 hours.
MobileNetV2: 16000 trials, running on an Nvidia RTX 4090 for 7 hours.

Relative Performance of the DGD Search algorithm achieved in 1 hour and full duration used by Ansor

Networks
Ratio (1 hour)
Ratio (full)

Bert
93.71%
100.15%

ResNet-50
90.46%
96.73%

MobileNetV2
95.08%
101.75%

This table presents the relative performance of the DGD Search algorithm with a 1-hour time budget compared to the full duration used by Ansor. The performance ratios indicate the effectiveness of the Dynamic Gradient Descent Search algorithm in achieving comparable performance within a significantly reduced time frame.

Thank you @Lurkrazy for this contribution !
I add Cc to relevant folks here: @comaniac @jcf94 @merrymercy @FrozenGene  @minminsun @jinhongyii

Given that we are migrating toward meta-schedule and may phase out auto-scheduler, i would suggest we bring new xhanges to that path.

authors: Lurkrazy cbalint13 tqchen


text:
[Frontend][TensorFlow] Support CombinedNonMaxSuppression

Support CombinedNonMaxSuppression in TF frontend. This op supports batched and multi class NMS.
https://www.tensorflow.org/api_docs/python/tf/image/combined_non_max_suppression

@anijain2305 @kevinthesun @yongwww @siju-samuel Please take a look

Thanks @trevor-m @anijain2305

authors: siju-samuel trevor-m


text:
Add thread_warp_size for Metal device in default target attributes

Recently new transpose op strategy was added for cuda which use thread_warp_size from default target attr parameters.
Since Metal fallback to cuda, it needs this parameter to be defined.
The exact value of this param is still open question, 16 should be safe enough but probably it will be changed later after experiments and more clarifications to 32.

LGTM, thanks @elvin-n

authors: elvin-n jwfromm


text:
Fix website policy violation

Use the consent script suggested in the website policy via the consensual_youtube pelican plugin.
/cc @Paul-TT FYI
Fixes #373

Got bitten by CSP headers, following up with https://github.com/apache/infrastructure-p6/pull/1837

repo: apache/www-site


text:
[YUNIKORN-1917] enforce ugm maxapplications rule

What is this PR for?
In increaseTrackedResource, we check maxRunningApps before we increase the resource. However, we don't check it before we create a new allocation. In this case, the real applications will be more than the limit.
https://github.com/apache/yunikorn-core/blob/5f812c1d34e212ebc3126143592233587f12cf51/pkg/scheduler/ugm/queue_tracker.go#L92
What type of PR is it?

[X] - Bug Fix

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1917
How should this be tested?
Add unit test cases for it.

Can you add a case to cover this behaviour? when both user & group limits are present? may be user max app is lower and group max app is higher ? and vice-versa

Yeah, added it. Thanks for the review!

Resolved conflicts. Thanks.

repo: apache/yunikorn-core


text:
[ZEPPELIN-2147] zeppelin should redirect to login page after browser session expires

What is this PR for?
Zeppelin should redirect to login page after browser session expires
What type of PR is it?
[Bug Fix]
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-2147

How should this be tested?

Open any Zeppelin's notebook on a browser
Restart zeppelin server
now as soon as next web-socket message or API request is sent to server that returns either "ticket is invalid" or 405. This should get redirected to login page.
On successful login it should take user back to the page from where he was coming from.

Screenshots (if appropriate)

Questions:

Does the licenses files need update? N/A
Is there breaking changes for older versions? N/A
Does this needs documentation? N/A

changes look good, may need to check the CI though

Thank you @khalidhuseynov  for taking a look at this. CI is green now.

Thank you @r-kamath  for reviewing this. Have handled your review comments.

https://travis-ci.org/prabhjyotsingh/zeppelin/builds/204880085 (229.2)  failed but https://travis-ci.org/prabhjyotsingh/zeppelin/builds/204547180 passed.
Merging this to master and branch-0.7 if no more discussion.

On retrying the same build, CI is green. https://travis-ci.org/prabhjyotsingh/zeppelin/builds/204880085

On retrying CI is green now. https://travis-ci.org/prabhjyotsingh/zeppelin/builds/204880085

authors: khalidhuseynov prabhjyotsingh

repo: apache/zeppelin

license_source: bigquery


text:
ZEPPELIN-2687: Show code in description section of Spark UI

What is this PR for?
Show code in description section of Spark UI
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?
ZEPPELIN-2687
How should this be tested?
Run scala, pyspark and sql snippet(should result in a spark job), and check Spark Web UI
Screenshots (if appropriate)
Before:

After:
Collapsed(short desc):

Expanded(Long desc):

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@karuppayya Thanks for this PR. It is really helpful. Besides this, with more and more features added we have more and more duplicated code in PySparkInterpreter, SparkInterpreter, SparkSQLInterpreter and SparkRInterpreter.  It is better to have a base class to handle all these common things. Anyway, we could do this in another PR. But I just feel we need to to asap. Because zeppelin code base become too large than it could be.

@zjffdu +1 on the refactoring.

On restrating the failed job(selenium tests), it succeeded
https://travis-ci.org/karuppayya/zeppelin/builds/246794338
Ready for reviewing

@felixcheung

Regarding the security exploitation
Spark does escapes any HTML, except for a anchor element with relative links
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/ui/UIUtils.scala#L439
There can be multiple jobs per notebook paragraph
When a sceond paragrph with different code is executed, the corresponding paragraph code shows up in the description section

@felixcheung any suggestion on the length of text(for the short description).
Also in case of scala, python code, when the first code line is a import , should we skip it and show the first line of actual code as short description, instead of the import statement?.
Currently, we show the entire code in the long description. This can potentially bloat the evnt logs. Should we prune it, to say last n lines?.
@felixcheung @Leemoonsoo @jongyoul

what is the goal of this? if the goal is identification, then either the last line (or last few lines) and/or with paragraph id should be sufficient.
I believe the pig interpreter has a similar approach, right @zjffdu ?

Yes, we need to truncate that. @karuppayya Could you add some comment to explain what is the jobShortText and jobLongText.

authors: felixcheung karuppayya zjffdu


text:
ZEPPELIN-3202. Added missing test dependencies in the scio module

What is this PR for?
Added missing test dependencies for the scio module to prevent test failures when running mvn clean install.
What type of PR is it?
Bug Fix
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3202

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

I kicked off another Travis build and it seems that these failing tests are flakey.

I just reran the failing builds, as suggested by @zjffdu in ZEPPELIN-3182, and all are green now.

merging if no more comment

authors: HorizonNet felixcheung


text:
test github action

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?

First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

We are on Github action. Closed

authors: Reamer zjffdu


text:
Add Vuetify

Add Vuetify so we can more easily use standard components like v-cards
Notes:

https://github.com/mooeypoo/rtl.wtf/blob/main/src/.vuepress/enhanceApp.js
vuetify must be under  to work, so I had to add  to the main layout: https://github.com/mooeypoo/rtl.wtf/blob/main/src/.vuepress/theme/layouts/Layout.vue#L2

<template>
  <v-app>
    <ParentLayout>
  </v-app>
</template>

Declining as out of scope

repo: apaskulin/wmf-dev-portal-draft

license: MIT


text:
fix: redis-cluster default config

adjust redis cluster default setting:

mode: replication
sentinel: enabled (need replication mode)
node port service: disabled

/cherry-pick release-0.8

repo: apecloud/kubeblocks-addons


text:
Add support for adaptive risk-based authN

Enable CAS to detect suspicious authentication attempts, and then route the authentication flow to require MFA, or potentially even block authentication attempts if MFA is not configured/available. The adaptive feature should take into account historical data associated with the requesting user id, and needs to calculate some sort of risk score based on the criteria defined by the CAS adopter. The result of the risk assessment can then be used to make decisions about the future of the flow.
The data that is used for criteria queries must be available through CAS event storage mechanisms. The following criteria may be used:

browser agent
authentication time
ip address geolocation

The criteria that needs to be defined by the CAS adopter may take the following form:
select total count of authentication attempts from history where [browser-agent is a fuzzy match]
and [authentication time is a fuzzy match] and [ip address geo location is a fuzzy match] for user=xyz

...where the query parameters in the query are defined by the adopter. The result will be an integer indicating "User xyz has in the past attempted X successful authentications. "
The adopter would then decide what to do with the result if X is less than the required score.
In order to complete this, CAS would need to first be able to match an ip address to a geolocation object.

+1

+1

Notes from call on Oct 7th:

MFA provider not found: create MisconfigurationException ?
Limit the number of processed events - let the operator set limit
Ensure if there are no previous events - produce highest risk score
Never use lowest score
Switch from double to BigDecimal (Math.ceil/round issues)
Pre-fabricate data for risk-based authn testing. JSON dataset for mongodb?
Let the app know generically that risk based authn happened via an attribute
Record risky authn attempts into the event store; take those into account when calculating attempts
Allow for overriding of individual calculators vs the whole eval engine

Pushed the branch risk-authn. The above checklist should be accurate for the current commit.
cc: @leleuj @dima767

This is done now as a first pass. Updated docs to note the experimental nature of the feature.

authors: leleuj mmoayyed rsoletob

repo: apereo/cas


text:
服务器端运行正常，但是openwrt的openclash和passwall2都无法使用

2024-04-10 19:54:13 level=info msg="[UDP] 192.168.5.207:60324 --> 5.5.5.5:55555 doesn't match any rule using DIRECT"
2024-04-10 19:54:13 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57313 --> google.ru:443 error: dial tcp 142.251.37.3:443: i/o timeout"
2024-04-10 19:54:12 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57304 --> google.com:443 error: dial tcp 142.251.36.238:443: i/o timeout"
2024-04-10 19:54:12 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57303 --> 91.108.56.176:80 error: dial tcp 91.108.56.176:80: i/o timeout"
2024-04-10 19:54:11 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57302 --> www.google.com:443 error: dial tcp 172.217.16.164:443: i/o timeout"
2024-04-10 19:54:11 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57294 --> www.google.ru:443 error: dial tcp 216.58.212.195:443: i/o timeout"
2024-04-10 19:54:11 level=info msg="[TCP] 192.168.5.207:57319 --> mozilla.cloudflare-dns.com:443 doesn't match any rule using DIRECT"
2024-04-10 19:54:10 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57291 --> 149.154.175.55:443 error: dial tcp 149.154.175.55:443: i/o timeout"
2024-04-10 19:54:10 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57292 --> 149.154.175.55:80 error: dial tcp 149.154.175.55:80: i/o timeout"
2024-04-10 19:54:10 level=info msg="[UDP] 192.168.1.2:7695 --> 113.24.226.67:8829 doesn't match any rule using DIRECT"
2024-04-10 19:54:10 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57290 --> firestore.googleapis.com:443 error: dial tcp 172.217.16.234:443: i/o timeout"
2024-04-10 19:54:10 level=info msg="[TCP] 192.168.5.207:57317 --> q.i.gdt.qq.com:443 doesn't match any rule using DIRECT"
2024-04-10 19:54:09 level=info msg="[UDP] 192.168.5.207:59981 --> 5.5.5.5:55555 doesn't match any rule using DIRECT"
2024-04-10 19:54:09 level=info msg="[UDP] 192.168.5.207:55038 --> 198.18.1.95:9001 match IPCIDR(198.18.0.1/16) using REJECT"
2024-04-10 19:54:09 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57289 --> firebaseremoteconfig.googleapis.com:443 error: dial tcp 142.251.37.10:443: i/o timeout\ndial tcp 142.251.36.170:443: i/o timeout\ndial tcp 172.217.16.170:443: i/o timeout\ndial tcp 142.251.36.234:443: i/o timeout\ndial tcp 142.251.36.202:443: i/o timeout"
2024-04-10 19:54:08 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57288 --> dns.google.com:443 error: dial tcp 8.8.8.8:443: i/o timeout\ndial tcp 8.8.4.4:443: i/o timeout"
2024-04-10 19:54:08 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57287 --> 149.154.175.55:80 error: dial tcp 149.154.175.55:80: i/o timeout"
2024-04-10 19:54:08 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57286 --> 149.154.175.55:443 error: dial tcp 149.154.175.55:443: i/o timeout"
2024-04-10 19:54:07 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57284 --> 91.108.56.176:80 error: dial tcp 91.108.56.176:80: i/o timeout"
2024-04-10 19:54:07 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57283 --> 149.154.175.55:80 error: dial tcp 149.154.175.55:80: i/o timeout"
2024-04-10 19:54:07 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57281 --> 149.154.175.55:443 error: dial tcp 149.154.175.55:443: i/o timeout"
2024-04-10 19:54:07 level=warning msg="[TCP] dial DIRECT 192.168.5.207:57282 --> 91.108.56.176:443 error: dial tcp 91.108.56.176:443: i/o timeout"
2024-04-10 19:54:07 level=info msg="[TCP] 192.168.5.220:62687 --> 143.92.42.98:10757 doesn't match any rule using DIRECT"
2024-04-10 19:54:05 level=info msg="[UDP] 192.168.5.207:58445 --> 5.5.5.5:55555 doesn't match any rule using DIRECT"
2024-04-10 19:54:05 level=info msg="[TCP] 192.168.5.213:3434 --> tracker.ai.xiaomi.com:443 doesn't match any rule using DIRECT"
2024-04-10 19:54:04 level=info msg="[UDP] 192.168.5.207:55038 --> 198.18.1.95:9001 match IPCIDR(198.18.0.1/16) using REJECT"
2024-04-10 19:54:04 level=info msg="[TCP] 192.168.5.220:62684 --> 143.92.42.98:10757 doesn't match any rule using DIRECT"
2024-04-10 19:54:03 level=info msg="[TCP] 192.168.5.207:57285 --> mozilla.cloudflare-dns.com:443 doesn't match any rule using DIRECT"
2024-04-10 19:54:02 level=info msg="Load MMDB file: /etc/openclash/Country.mmdb"
2024-04-10 19:54:02 level=info msg="[UDP] 192.168.1.2:31744 --> 180.163.30.22:11060 doesn't match any rule using DIRECT"
2024-04-10 19:54:01 level=info msg="[UDP] 192.168.5.207:53012 --> 5.5.5.5:55555 doesn't match any rule using DIRECT"
2024-04-10 19:54:01 level=info msg="[UDP] 192.168.1.2:5082 --> 110.43.98.104:6666 doesn't match any rule using DIRECT"
2024-04-10 19:54:00 level=info msg="[UDP] 192.168.1.2:42357 --> 219.139.198.161:37304 doesn't match any rule using DIRECT"
=====================================================================================
● hysteria-server.service - Hysteria Server Service (config.yaml)
     Loaded: loaded (/etc/systemd/system/hysteria-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-04-10 20:44:59 JST; 12min ago
   Main PID: 21440 (hysteria)
      Tasks: 6 (limit: 288)
     Memory: 4.9M
     CGroup: /system.slice/hysteria-server.service
             └─21440 /usr/local/bin/hysteria server --config /etc/hysteria/config.yaml

Apr 10 20:44:59 jppass01 systemd[1]: Started Hysteria Server Service (config.yaml).
Apr 10 20:44:59 jppass01 hysteria[21440]: 2024-04-10T20:44:59+09:00        INFO        server mode
Apr 10 20:44:59 jppass01 hysteria[21440]: 2024-04-10T20:44:59+09:00        INFO        server up and running        {"listen": ":443"}

是的 现在是无法使用了，。好像被封杀了。

repo: apernet/hysteria


text:
Example stylesheet adjustments to fix some common issues

Hey 😃
I have been putting fixes in my custom stylesheet to help with some common problems I have been experiencing.  It helps with #10 and #11
I thought it worth sharing here.  I will keep updating it as I find more issues/fixes.  Perhaps after a while we could consider patching your plugin with some of these.
/**
 * FIXES FOR APEX-UI-SLIM AND APEX-SYNTAX PLUGINS
 * Last Updated: 2017/01/23 12:57 UTC+00:00
 */

// Drops the tree-view on left so that the OS X controls aren't overlayed.
atom-panel.tool-panel.panel-left .tree-view-scroller {
  margin-top: 30px;
}

// We dont't want to see the title bar.
atom-panel.panel-header .title-bar {
  visibility: hidden;
}

// Fixes Modals as their widths vary drastically and tend to shift as you
// type input, so preferring a fixed width.
.tree-view-dialog,
.modal.overlay > .select-list {
  width: 80vw;
}

// The highlighted/selected text is too invisible to see.
.command-palette .list-group .character-match {
  color: #000;
}

// Fix the highlighting of items in the tree-view, as the colors change,
// especially with git status it's easier to use an underline to indicate
// the currently selected item.
.tree-view .directory.selected > .header,
.tree-view .list-item.selected {
  color: #212529;
  text-decoration: underline;
}

// Show currently selected item in select lists.
.select-list .list-group li.selected {
  border-left: solid 1px #212529;
}

// We want our wrap guides still. :)
atom-text-editor .wrap-guide, atom-text-editor .wrap-guide {
  background-color: #edecec;
}

// Fixes text highlight on modal popups
.modal atom-text-editor .highlight > .region {
  background: #edecec !important;
}

The above works well with the apex-ui-slim and apex-syntax plugins, along with the atom setting to allow custom titlebars enabled:

awesome thanks I'll try and check those out when I have time :D

Sure thing, no problem.  Still more to be added so no rush.

Woot. The main thing that has bugging me is the highlighting in menus needs some more contrast for sure haha.. some day

Thanks, i added some of these manually :)

authors: ctrlplusb jbreuer95 tj

repo: apex/apex-ui-slim


text:
Error: unknown flag: --env-file

If you have a bug report please let us know the following:

osx 10.11.4 (15E65)
0.10.0

Seems that --env-file didn't make the cut into 0.10.0 😢

crap I forgot to add it to build

thanks man haha, even had it on my list, yikes. v0.10.1 will be up in a min

authors: reggi tj

repo: apex/apex


text:
Consider switching CLI library to cobra

Many of the most widely used Go projects are built using Cobra including Kubernetes, etcd, Docker, and CockroachDB.
Though it is not necessarily the best CLI library of all, switching to cobra helps apex removing quite a bit of boilerplate code it currently has with docopt. It can arguably scale better too when the number of sub-commands and options grows over time.

Nice yea sounds good to me. Part of me prefers docopt since you get the arguments for each command right there, but you don't get the command description which does kinda suck. We'd have to rename apex help to apex wiki but that's totally cool with me, more appropriate name anyway

@tj Just submitted PR #89.
Not sure what to do with autocompletion. I know Cobra has autocompletion feature built in but I haven't explored it yet.

no worries about autocomplete for now, we need to support dynamic generation there for function names anyway, we can remove the current stuff in the PR or a separate request

@tj Alrighty, let's keep it together with this PR.

authors: pilwon tj


text:
docs: fix the instructions for executing the simple nodejs server

These are the instructions i had to follow to get the first example to run

gotcha...i'll follow up on why i initially had issues

cool definitely let me know!

authors: jalateras tj

repo: apex/up


text:
toggleSeries always return False for stackedBar chart

Report Issue
While using a line bar chart with custom legends works fine by toggleSeries but using with stacked bar chart the toggle series always returns false. Cannot able to figure out the issue
Here's the link to demo on sandbox : https://codesandbox.io/s/jovial-resonance-fc8jb
@junedchhipa

Hope find the issue, it's from collapsedSeries which an empty array is getting appended after hideSeries is executed in toggleSeries. @junedchhipa


text:
Tooltips and cursors disappear when chart data is updated.

Description
I have a line chart that is updated every second. When I move the mouse over the chart, tooltips and cursors quickly show up, but disappear as soon as new data is loaded. Accessing the diagram menu is also not possible since it looses focus when ever the chart updates.
Steps to Reproduce

Create chart and update data every second or so
Move mouser over chart
Tooltips and cursors only show up quickly and then disappear, menu is not accessible

Expected Behavior
Tooltips, cursors and menu are not hiding or redrawn when chart data is updating

Reproduction Link
https://codesandbox.io/embed/vue-basic-example-forked-n4z9y?fontsize=14&hidenavigation=1&theme=dark

I have also reported this same problem, which is very bad for realtime context, but no answer until now

authors: raesche vandercijr


text:
Internationalization API is not injected with locale

Describe the bug
The ECMAScript Internationalization API is not affected by the injected fingerprint's locale.
To Reproduce
See @mnmkng 's gist.
Expected behavior
The Intl methods should return values consistent with the injected locale.
System information:

OS: [Linux Mint 20.2 Cinnamon]
Node.js version [16.15.1]

Additional context
Originally brought up by @mnmkng in Slack.

We need to use the locale context option in playwright:
// Emulate locale and time
const context = await browser.newContext({
  locale: 'de-DE',
  timezoneId: 'Europe/Berlin',
});

from what I have found there are two ways to set the accept-language header.

By extra headers API

await page.setExtraHTTPHeaders({
    'Accept-Language': 'bn'
});

By a launch argument

const browser = await puppeteer.launch({
    headless: false,
    args: ['--lang=bn-BD,bn']
});

According to the current implementation, we can only manipulate the fingerprint on a page basis to limit the number of browsers that need to be launched to use a unique "identity", so I would go with the header override method.

I think the header was being set correctly yesterday when I tried it, but I might've been wrong.

The Accept-language header is indeed getting set correctly (here, basically the first option from @petrpatek 's message).
The linked PR (#5) fixes the Internationalization API problem from @mnmkng 's gist, but for some reason(???) doesn't work in Firefox. Help, support and ideas greatly appreciated!

Closed via #5

authors: B4nan barjin mnmkng petrpatek

repo: apify/fingerprint-suite


text:
Feature/middlewares

Summary:

2 new functions Apify.utils.puppeteer.addInterceptRequestHandler() and Apify.utils.puppeteer.removeInterceptRequestHandler() allowing to have multiple page.on('request', ...) handlers
Functions for resource (css, image, ...) blocking and content caching migrated to this so that they can be used together
Added Apify.utils.puppeteer.gotoExtended() that supports Apify.Request (all methods, headers, POST payload)
Added some tests for resource blocking that were missing

Fixes:
https://github.com/apifytech/apify-js/issues/204
https://github.com/apifytech/apify-js/issues/192

repo: apifytech/apify-js


text:
iocp and twapi::tls_socket cause hanging system for me

Moved from https://sourceforge.net/p/twapi/bugs/191/
Dear Ashok,
thank you for great twapi and iocp.
With the following lines, I get a block wish window (not responding any more) :
package require iocp_inet
rename ::socket ::socket_ori
rename ::iocp::inet::socket ::socket
package require twapi
package require http
proc ::http::Log {args} {
puts "[http]:$args"
}
http::register https 443 {::twapi::tls_socket}
http::geturl https://www.elmicron.de/labelers.csv
This is TWAPI (developper Version) 4.4.0, http 2.9.1 and wish 8.6.10 (VC6 self compiled), iocp 1.0.0.
I get the following console output (it is tricked, as the console stalls and copy&paste is not possible) (screenshot attached):
(bin) 6 % package require iocp_inet
1.0.0
(bin) 7 % rename ::socket ::socket_ori
(bin) 8 % rename ::iocp::inet::socket ::socket(bin) 1 % package require twapi
4.4.0
(bin) 2 % package require http
2.9.1
(bin) 3 % proc ::http::Log {args} {

puts "[http]:$args"
}
(bin) 4 % http::register https 443 {::twapi::tls_socket}
443 ::twapi::tls_socket
(bin) 5 % http::geturl https://www.elmicron.de/labelers.csv
[http]:^A1 URL https://www.elmicron.de/labelers.csv - token ::http::1
[http]:{Using rc0 for www.elmicron.de:443 - token ::http::1} {}
[http]:^B1 begin sending request - token ::http::1
[http]:^C1 end sending request - token ::http::1
[http]:^D1 begin receiving response - token ::http::1

When I remove the first 3 lines (iocp initialization), it works correctly:
(bin) 1 % package require twapi
4.4.0
(bin) 2 % package require http
2.9.1
(bin) 3 % proc ::http::Log {args} {

puts "[http]:$args"
}
(bin) 4 % http::register https 443 {::twapi::tls_socket}
443 ::twapi::tls_socket
(bin) 5 % http::geturl https://www.elmicron.de/labelers.csv
[http]:^A1 URL https://www.elmicron.de/labelers.csv - token ::http::1
[http]:{Using rc0 for www.elmicron.de:443 - token ::http::1} {}
[http]:^B1 begin sending request - token ::http::1
[http]:^C1 end sending request - token ::http::1
[http]:^D1 begin receiving response - token ::http::1
[http]:^E1 end of response headers - token ::http::1
[http]:^F1 end of response body (unchunked) - token ::http::1
[http]:{Closing socket rc0 (no connection info)}
::http::1

I am sorry for this report. Come to me if I may be of any help.
Thank you,
Harald

Fixed in 1.0.9.

Hi Ashok,
thank you for looking into this, I appreciate.
I can confirm, that it works correctly in the exact setup now for me.
Thank you,
Harald
P.S.
The test recipe should be
`puts "[http]:$args"
instead
puts "[http]:$args"

authors: apnadkarni oehhar

repo: apnadkarni/iocp