Adding OpenAPI Export and Rib to OpenAPI Converter

OpenAPI Export for API Definition Implementation
This PR implements the OpenAPI export functionality for API Definitions as specified in issue #1178 and feedback from @jdegoes  The implementation provides a complete solution for converting User and Golem API Definitions to OpenAPI Specifications and includes comprehensive testing.
Key Features

Full and lossless conversion of API Definitions to OpenAPI 3.0 Specifications
Support for all binding types (Default and File Server)
Preservation of type information from Rib to OpenAPI schemas
Integration with Worker Gateway for serving OpenAPI specs
Swagger UI binding type for API documentation
Comprehensive test suite validating the export functionality

Implementation Details

OpenAPI Export

Added OpenApiExporter for converting API definitions to OpenAPI specs
Implemented type conversion from Rib types to OpenAPI schemas
Added support for security schemes and CORS configurations

Swagger UI Integration

Added new SwaggerUI binding type
Implemented dynamic Swagger UI generation inspired by @jdegoes's comment on my old pull request
Added configuration options for customization

Testing

Added unit tests for type conversion
Added integration tests validating generated clients
Added system tests for Python to check if my schema is correct and Rust clients
Included complex test scenarios with nested types and security configurations

API Changes
Added new endpoint mentioned in the issue
/claim #1178
This time there are only 4 files that need review in honesty. Majority of the files are test files in order for it to be tested. I decided to re-invent the wheel after jdgoes's review, making me think "I can do this in smaller numbers, as he said use more of golem's library and I though, It's better for me to actually blend in the repo instead of trying to get overwhelmed by its" Since Swagger was absolutely a mess in rust, i used a dynamical client generation using Golem's existing file server already, it should serve the jsons and yalms to user in memory.

@zelosleone Before I do a fine-grained review, let me commend you on major improvements, and then point out one area which, at a high-level, is still not right: the integration testing.
The essential task of integration testing is to prove that, if a user builds a component with a complex API (meaning, use of WIT types including variants, flags, records, lists, results, etc.--fully and exhaustively sampling all the different types that WIT supports in the exports of the component), and then stands up an API using the Worker Gateway, by defining a number of different endpoints using Rib; that the resulting OpenAPI Export of this API definition is in fact both correct and precise, and such correctness and precision is evident in client libraries that have been auto-generated from the OpenAPI export.
So, the integration test will first need to start with a component that you write (there are test components already in Golem -- you could simply add one here). This test component will need to have a number of exports, let's call it 10 - 20, each of which accepts and returns a sampling of WIT types. This is to fully exercise your logic and your embedding of the knowledge of how Rib types map to canonical JSON types.
Once you have the test component, then the integration test will:

Construct an API definition with a number of routes. Since API definitions can be imported from JSON/YAML, you could just hard code this in a fixtures directory and load it for testing purposes.
Invoke your export code on the API definition, which should result in an OpenAPI schema that precisely describes the API, including input and output types for all 10 - 20 exports on the test component.
Once you have this OpenAPI schema, dynamically generating client libraries (the choice of Python and TypeScript is fine; I think two client libraries is a good number and certainly one of them should be strongly statically typed; could be TS & Rust too, btw).
Firing up a Worker Gateway (etc.) to serve the API definition (you can look at other integration tests for how this is done--you can spin up whatever portion of the Golem stack is necessary to actually execute workers; see the CLI tests for examples). When this step is done, there will be a server created by the worker gateway that is dynamically serving the API powered by your test component.
Using hand-written test code for each client library, interacting with the API using the generated client libraries, and verifying the results have the structure ascribed to them and are sensible (how you do this depends on how you constructed the test component -- but the goal should be to catch any format or encoding/decoding problems so all your 10 - 20 exports need to return meaningful information, ideally derived from inputs so it can be somewhat dynamic).
Spin everything down.

Such an integration test will reasonably demonstrate that all the pieces fit together, and that when a user exports an OpenAPI Schema from their API (defined in Rib, using the default/worker binding type, but also with file server and swagger UI binding types--which should also be tested in the integration test), this OpenAPI schema is in fact a 100% valid and usable schema for the API being served by the worker gateway. It is so correct and precise that you can generate client libraries from it, and use them in a typed and safe way; or, of course, you can interact with the API using Swagger UI (if you added such a binding type as part of your API definition) directly from the browser of your choice.
Other things important to test include CORS (to ensure that when a deployment is using CORs, that's reflected in the OpenAPI as the preflight options request, etc.), and security (because if an API is secured using Golem auth, then we want the security requirements to be expressed in OpenAPI so that auto-generated clients know they need to provide security).
You might want to use https://console.golem.cloud to play around with adding APIs to see the big picture, which will help you understand how to structure the integration test.
Once all the high-level architecture is correct, I will do a more fine-grained review.
Btw some parts of https://github.com/golemcloud/golem/pull/1208 seem to be copied from your PR (see, for example, test server). Can you confirm or reject?

Thanks for the helpful tips and helpful lessons @jdegoes You are really better than my professors in my university, thank you very much. I updated everything, made an unit test:

defines a non-trivial API, which complex input and output types
generates OAPI schema for the API
generates a client library for the OAPI
interacts with the original API and verifies successful communication

Which you mentioned it is needed in discord, I used github actions for this because building golem in windows was a pain due to wasm version conflict in cargo files. Here is the output file generated:
test-output.json
Also significantly reduced the files changed for this, as i simply used the existing files to place unit tests. As for the copying issue, I did not give any permission to do so, neither I know him.

My sincere apologies @jdegoes , my integration tests were performed by an AI, I now realize that it plagiarized code from @zelosleone , a huge apology to both of you, it was not my intention.

@zelosleone There's still a lot of work that has to be done. Please ping me when you have all the pieces put together and you are ready for a review.

@jdegoes Everything is finished, hopefully. Added docs as well.

@jdegoes Finished manual testing as well after removing WASMI from my build.

Everything is done. Firstly, Yaml and Json files generated:
target.zip
Output Code:
[ 1/75] Running test: golem_worker_service_base::api::register_api_definition_api::tests::test_method_pattern
[ 1/75] Finished test: golem_worker_service_base::api::register_api_definition_api::tests::test_method_pattern                                                                          [PASSED]
[ 2/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_push_and_get
[ 3/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_shape_no_overlap
[ 4/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_large_tree_structure
[ 2/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_push_and_get                                                                              [PASSED]
[ 4/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_large_tree_structure                                                                      [PASSED]
[ 5/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_push_subpath
[ 6/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict
[ 7/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_matches
[ 5/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_push_subpath                                                                              [PASSED]
[ 8/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_matches_two_routes
[ 3/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_shape_no_overlap                                                                          [PASSED]
[ 7/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_matches                                                                                [PASSED]
[ 9/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict_static_variable
[10/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_variables
[11/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_variables_different_order
[ 6/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict
                                                                [PASSED]
[12/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict_variable_static
[13/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_routes_resolution
[14/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all
[15/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all_fallthrough
[16/75] Running test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all_fallthrough_complex
[17/75] Running test: golem_worker_service_base::gateway_execution::router::core::tests::test_router
[12/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict_variable_static                                                                  [PASSED]
[ 8/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_matches_two_routes                                                                        [PASSED]
[18/75] Running test: golem_worker_service_base::gateway_execution::to_response::test::test_evaluation_result_to_response_with_http_specifics
[16/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all_fallthrough_complex                                                             [PASSED]
[19/75] Running test: golem_worker_service_base::gateway_execution::to_response::test::test_evaluation_result_to_response_with_no_http_specifics
[ 9/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_conflict_static_variable                                                                  [PASSED]
[17/75] Finished test: golem_worker_service_base::gateway_execution::router::core::tests::test_router
                                                                [PASSED]
[20/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_with_json
[21/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_without_json
[11/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_variables_different_order                                                        [PASSED]
[10/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_variables                                                                        [PASSED]
[22/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_with_html
[19/75] Finished test: golem_worker_service_base::gateway_execution::to_response::test::test_evaluation_result_to_response_with_no_http_specifics                                       [PASSED]
[23/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_type_text
[24/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_type_json
[13/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_multiple_routes_resolution                                                                [PASSED]
[20/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_with_json                                   [PASSED]
[14/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all
                                                                [PASSED]
[25/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_failed_content_mapping
[26/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_u8_type_with_json
[15/75] Finished test: golem_worker_service_base::gateway_execution::router::tree::test::test_catch_all_fallthrough                                                                     [PASSED]
[27/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_non_u8_type_with_json
[18/75] Finished test: golem_worker_service_base::gateway_execution::to_response::test::test_evaluation_result_to_response_with_http_specifics                                          [PASSED]
[32/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_singleton_u8_type
[24/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_type_json                                  [PASSED]
[28/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_non_u8_type_with_html_fail
[29/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_record_type_json
[30/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_record_type_html
[21/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_without_json                                [PASSED]
[26/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_u8_type_with_json                                  [PASSED]
[31/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_string_type
[27/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_non_u8_type_with_json                              [PASSED]
[23/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_type_text                                  [PASSED]
[37/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_string_type_as_json
[32/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_singleton_u8_type                                    [PASSED]
[33/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_list_u8_type
[28/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_list_non_u8_type_with_html_fail                         [PASSED]
[29/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_record_type_json                                        [PASSED]
[30/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_record_type_html                                        [PASSED]
[34/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_list_non_u8_type
[35/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_record_type
[25/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_singleton_u8_failed_content_mapping                     [PASSED]
[42/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_record_type
[36/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_string_type_as_text
[22/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_accept_headers::test_string_type_with_html                                   [PASSED]
[37/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_string_type_as_json                               [PASSED]
[38/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_json_string_type_as_json
[33/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_list_u8_type                                         [PASSED]
[45/75] Running test: golem_worker_service_base::service::gateway::api_definition::tests::test_repo_error_to_service_error
[40/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_list_u8_type
[41/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_list_non_u8_type
[34/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_list_non_u8_type                                     [PASSED]
[46/75] Running test: golem_worker_service_base::service::worker::connect_proxy::keep_alive::test::test_websocket_keep_alive
[46/75] Finished test: golem_worker_service_base::service::worker::connect_proxy::keep_alive::test::test_websocket_keep_alive                                                           [IGNORED]
[43/75] Running test: golem_worker_service_base::service::gateway::http_api_definition_validator::tests::test_unique_routes
[44/75] Running test: golem_worker_service_base::service::gateway::api_deployment::tests::test_repo_error_to_service_error
[38/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_json_string_type_as_json                          [PASSED]
[39/75] Running test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_singleton_u8_type
[45/75] Finished test: golem_worker_service_base::service::gateway::api_definition::tests::test_repo_error_to_service_error                                                             [PASSED]
[40/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_list_u8_type                                      [PASSED]
[31/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_string_type                                          [PASSED]
[42/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_record_type                                       [PASSED]
[47/75] Running test: golem_worker_service_base::gateway_api_definition::http::path_pattern_parser::tests::test_parse
[35/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::no_content_type_header::test_record_type                                          [PASSED]
[36/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_string_type_as_text                               [PASSED]
[43/75] Finished test: golem_worker_service_base::service::gateway::http_api_definition_validator::tests::test_unique_routes                                                            [PASSED]
[44/75] Finished test: golem_worker_service_base::service::gateway::api_deployment::tests::test_repo_error_to_service_error                                                             [PASSED]
[48/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_single_value
[39/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_singleton_u8_type                                 [PASSED]
[49/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_multiple_values
[50/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_variables
[51/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_variables_and_queries
[52/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::test_path_patterns_to_string
[41/75] Finished test: golem_worker_service_base::gateway_execution::http_content_type_mapper::tests::with_response_type_header::test_list_non_u8_type                                  [PASSED]
[47/75] Finished test: golem_worker_service_base::gateway_api_definition::http::path_pattern_parser::tests::test_parse                                                                  [PASSED]
[53/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_parser_without_vars
[54/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_parser_with_vars
[55/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate0
[56/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate1
[48/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_single_value                                          [PASSED]
[57/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate2
[49/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_multiple_values                                       [PASSED]
[51/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_variables_and_queries                                 [PASSED]
[52/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::test_path_patterns_to_string                                                [PASSED]
[58/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate3
[59/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate4
[53/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_parser_without_vars                                                    [PASSED]
[54/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_parser_with_vars                                                       [PASSED]
[60/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition
[55/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate0                                                  [PASSED]
[56/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate1                                                  [PASSED]
[61/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_left
[50/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::split_path_works_with_variables                                             [PASSED]
[62/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_left_right
[63/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_right
[58/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate3                                                  [PASSED]
[64/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_with_literals
[59/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate4                                                  [PASSED]
[65/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_request
[66/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_worker_response
[67/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::test_api_spec_proto_conversion
[60/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition                                                      [PASSED]
[68/75] Running test: golem_worker_service_base::gateway_api_definition::http::place_holder_parser::tests::test_parse_place_holder
[57/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expression_with_predicate2                                                  [PASSED]
[69/75] Running test: golem_worker_service_base::gateway_api_definition::http::rib_converter::tests::test_convert_type
[61/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_left                                       [PASSED]
[62/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_left_right                                 [PASSED]
[63/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_expr_right                                      [PASSED]
[70/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_cors_preflight_binding
[64/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_with_if_condition_with_with_literals                                   [PASSED]
[65/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_request                                                                [PASSED]
[66/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::expr_worker_response                                                        [PASSED]
[71/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_cors_preflight_binding_default_response
[68/75] Finished test: golem_worker_service_base::gateway_api_definition::http::place_holder_parser::tests::test_parse_place_holder                                                     [PASSED]
[72/75] Running test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_no_binding_with_options_method
[69/75] Finished test: golem_worker_service_base::gateway_api_definition::http::rib_converter::tests::test_convert_type                                                                 [PASSED]
[73/75] Running test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_applies_cors_to_worker_routes
[74/75] Running test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_fails_for_non_options_cors_route
[75/75] Running test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_does_not_duplicate_cors
[70/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_cors_preflight_binding                              [PASSED]
[67/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_api_definition::tests::test_api_spec_proto_conversion                                              [PASSED]
[71/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_cors_preflight_binding_default_response             [PASSED]
[72/75] Finished test: golem_worker_service_base::gateway_api_definition::http::http_oas_api_definition::tests::test_get_route_with_no_binding_with_options_method                      [PASSED]
[73/75] Finished test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_applies_cors_to_worker_routes    [PASSED]
[74/75] Finished test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_fails_for_non_options_cors_route [PASSED]
[75/75] Finished test: golem_worker_service_base::gateway_api_definition_transformer::cors_transformer::tests::test_update_routes_with_cors_middleware_does_not_duplicate_cors          [PASSED]

test result: ok; 74 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.169s

     Running tests\api_integration_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\api_integration_tests-cdcc1ff186194272.exe)

running 1 test
test api_integration_tests::test_api_interaction ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running tests\complex_wit_type_validation_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\complex_wit_type_validation_tests-9ad4fccc2523bf3e.exe)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests\openapi_converter_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\openapi_converter_tests-5a3242faff59836e.exe)

running 8 tests
test openapi_converter_tests::test_merge_openapi_empty_components ... ok
test openapi_converter_tests::test_merge_openapi_components ... ok
test openapi_converter_tests::test_merge_openapi_response_components ... ok
test openapi_converter_tests::test_merge_openapi_security ... ok
test openapi_converter_tests::test_merge_openapi_security_schemes ... ok
test openapi_converter_tests::test_merge_openapi_paths ... ok
test openapi_converter_tests::test_merge_openapi_tags_and_servers ... ok
test openapi_converter_tests::test_merge_openapi_with_overlapping_paths ... ok

test result: ok. 8 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests\openapi_export_integration_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\openapi_export_integration_tests-3cb33677328afcea.exe)

running 2 tests
test openapi_export_integration_tests::test_export_path_generation ... ok
test openapi_export_integration_tests::test_complex_api_export ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests\rib_json_schema_validation_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\rib_json_schema_validation_tests-fa7469e17d4806b9.exe)

running 6 tests
test rib_json_schema_validation_tests::test_list_json_schema_validation ... ok
test rib_json_schema_validation_tests::test_record_json_schema_validation ... ok
test rib_json_schema_validation_tests::test_invalid_json_schema_validation ... ok
test rib_json_schema_validation_tests::test_complex_nested_json_schema_validation ... ok
test rib_json_schema_validation_tests::test_negative_primitive_validation ... ok
test rib_json_schema_validation_tests::test_variant_json_schema_validation ... ok

test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running tests\rib_openapi_conversion_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\rib_openapi_conversion_tests-5b21bcefd3c5d4c0.exe)
Running 9 tests

[1/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_primitive_types
[2/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_list_type
[1/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_primitive_types     [PASSED]
[2/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_list_type           [PASSED]
[3/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_record_type
[4/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_enum_type
[5/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_variant_type
[3/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_record_type         [PASSED]
[4/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_enum_type           [PASSED]
[6/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_option_type
[5/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_variant_type        [PASSED]
[7/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_result_type
[8/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_complex_nested_type
[9/9] Running test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_convert_input_type
[7/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_result_type         [PASSED]
[9/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_convert_input_type  [PASSED]
[6/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_option_type         [PASSED]
[8/9] Finished test: rib_openapi_conversion_tests::rib_openapi_conversion_tests::test_complex_nested_type [PASSED]

test result: ok; 9 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.050s

     Running tests\swagger_ui_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\swagger_ui_tests-5fe79919ce6f057d.exe)

running 5 tests
test swagger_ui_tests::test_swagger_ui_disabled ... ok
test swagger_ui_tests::test_swagger_ui_theme_variants ... ok
test swagger_ui_tests::test_swagger_ui_generation ... ok
test swagger_ui_tests::test_swagger_ui_config_default ... ok
test swagger_ui_tests::test_swagger_ui_default_title ... ok

test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests\utoipa_client_tests.rs (C:\Users\deniz\Documents\GitHub\golem\target\debug\deps\utoipa_client_tests-2addd939665fcd0e.exe)

running 1 test
test utoipa_client_tests::test_workflow_api_with_swagger_ui ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

   Doc-tests golem_worker_service_base

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

Would be better to finish this first as i used this main branch and had to separate the pull requests https://github.com/golemcloud/golem/pull/1214

@zelosleone
I will have more time to review just after the new year, and can do a Zoom meeting since that may be the fastest way of discussion what remains to be done in the PR.
However, until then, I have two major comments:

First off, the revisions necessary for doing end-to-end integration tests are not done. In particular, you have not added a new component with a large, exported API that tests all WIT types, and verified you can talk to the component through a client generated by the OpenAPI schema created by your code for that exportedAPI. See this comment for more details.
Second, I don't think you've implemented the API in such a way that Console or CLI can actually utilize it, so I added a new requirement that will be quite easy when all parts are connected in the right way -- but impossible otherwise. I've reproduced the requirement below:

- [ ] Golem CLI modified to add a new subcommand 'golem-cli api-definition swagger' (launches a browser to a generated swagger UI for the api definition) and another new subcommand 'golem-cli api-definition export', which exports an API definition to OpenAPI schema

This basically says you need to add two new commands to golem-cli that (1) open up the Swagger UI, and (2) do an OpenAPI export. In order to realize those two new commands, the proper REST API with associated plumbing will need to be created, which will motivate part of the functionality that is missing now.
Happy New Year!


[VL] [Bug fix] support min max aggregation with varbinary type

support min max aggregation with varbinary type. #385 https://github.com/oap-project/gluten/issues/2169

Thanks, Could you please create a gluten PR to test your branch and pass all Gluten CI. Then I will merge this PR. because we are fixing Velox UT recently.  Here is my example. https://github.com/oap-project/gluten/pull/2572 @gaoyangxiaozhu

Thanks, Could you please create a gluten PR to test your branch and pass all Gluten CI. Then I will merge this PR. because we are fixing Velox UT recently. Here is my example. oap-project/gluten#2572 @gaoyangxiaozhu

sure, will do

@zhejiangxiaomai gluten unit tests passed, Velox UT failures are not related.


Fixed #21046 -- Made startproject/app write platform-specific line endings.

Closing per ticket.

Even if the original issue is moot, what about keeping the patch (maybe without the test), as there is a small optimization (file copied instead of read/write)?

Sure

@timgraham OK with #7416?


Fix possible race when deleting unready vmsnapshot and the vm remaining frozen

What this PR does / why we need it:
This should fix flakiness in test: [test_id:6837]delete snapshot after freeze, expect vm unfreeze
The issue presented there was:
deleting vmsnapshot-> deleting vmsnapshot content while the update content reconcile loop was during a wait for a call to the freeze source api command. In the CI it seems that sometimes the call can take longer time(~1s) to return. Once return there is the attempt to create the volumesnapshot that test added a fake webhook to make that call fail, hence the call returns error the reconcile loop is exited and when needing to call it again the content is already deleted.
In order to fix this issue we moved the remove of the content finalizer from the vmsnapshot reconcile to the vmsnapshotcontent reconcile which happens only after unfreezing the vm. We are not allowing the vmsnapshot to be deleted incase the process was not completed successfully (possible that the vm will still get frozen) until the content is deleted first (makes sure there will be no other call to freeze).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Fix possible race when deleting unready vmsnapshot and the vm remaining frozen

@mhenriks The fix we talked about

Related to https://github.com/kubevirt/kubevirt/issues/7940 ?

@mhenriks right Im working on UT and the tests failures here. will ping you when ready

@oshoval I believe its not related, and I also believe the issue you sent is probably a test issue, but Ill look at it separately

/retest

@mhenriks added another commit with UT. please review again

/retest-required

/lgtm
/approve

/hold

/retest-required

/test pull-kubevirt-e2e-k8s-1.22-sig-storage

/test pull-kubevirt-e2e-k8s-1.23-sig-storage

/test pull-kubevirt-e2e-k8s-1.23-sig-storage-nonroot

/test pull-kubevirt-e2e-k8s-1.24-sig-storage

/test pull-kubevirt-e2e-k8s-1.22-sig-storage
/test pull-kubevirt-e2e-k8s-1.23-sig-storage
/test pull-kubevirt-e2e-k8s-1.23-sig-storage-nonroot
/test pull-kubevirt-e2e-k8s-1.24-sig-storage

/lgtm

/unhold
Added the last commit to fix the flaky test


Computed fields cannot be excluded from model export

Initial Checks

[X] I confirm that I'm using Pydantic V2 installed directly from the main branch, or equivalent

Description
When using computed fields and properties, it is not possible to exclude them from the model export. the computed_field decorator does not allow to use the exclude argument, and the fields configuration option has been removed.
The example code prints
/tmp/pydantic/pydantic/_internal/_config.py:234: UserWarning: Valid config keys have changed in V2:
* 'fields' has been removed
  warnings.warn(message, UserWarning)
{'whatever': 1, 'foobar': 2}

Example Code
from pydantic import BaseModel, computed_field

class FooModel(BaseModel):
    whatever: int

    @computed_field()
    @property
    def foobar(self) -> int:
        return self.whatever + 1

    model_config = dict(
        fields={"foobar": {"exclude": True}}
    )

model = FooModel(whatever=1)

print(model.model_dump())

Python, Pydantic & OS Version
pydantic version: 2.0a4
        pydantic-core version: 0.33.0 release build profile
                 install path: /tmp/pydantic/pydantic
               python version: 3.10.9 (main, Dec  7 2022, 13:47:07) [GCC 12.2.0]
                     platform: Linux-6.0.0-6-amd64-x86_64-with-glibc2.36
     optional deps. installed: ['typing-extensions']

@alvarolopez the reason we introduced computed_field was so that properties could be included in the serialization. I'm curious — what is the use case you have in mind for using a computed_field where you want to exclude it from serialization as part of its definition?
I would think the right thing to do in that case generally would be to just only use @property instead of @computed_field, but maybe you want it to show up in the JSON schema, or something else? Trying to understand.

@dmontagu 🤯 you are totally right. I am sorry for the noise, the problem is not a but, but lack of coffee.

I think it makes sense in principle; in practice I'd rather not add more code to maintain without a good motivating reason :).
Thanks for closing the issue.

I was wondering if we could re-open this, I need this feature to compare two objects that are off the same class. I want to compare them without the computed fields as they are deterministic values, and I don't want to compute them.
For the general audience, I think it would be helpful to just have the option; you never know when you need it and don't bother to ask if the feature doesn't exist. Not to mention you can potentially save on a lot of compute in the long run if you dump without computed fields when you actually don't need them.

@dmontagu I need this for my project for reasons described above, can we add it if I make a PR? It should be few lines of code to the model_dump method, I don't see this being a problem for Pydantic at large.

Ok.

This feature would be very helpful for my project.
I dump a sample instance of my data model to show users what an input file looks like. However, only some of the fields are inputs, and the others are auxiliary for my code. I can exclude the auxiliary fields with pydantic.Field(exclude=True) but I cannot do the same for computed_fields.

This feature would be very helpful for my project.
I dump a sample instance of my data model to show users what an input file looks like. However, only some of the fields are inputs, and the others are auxiliary, and users shouldn't see them. I can exclude auxiliary fields with pydantic.Field(exclude=True) but I cannot do the same for `computed_field's.

This feature has been on my backlog for a while, sorry. Feel free to implement it if it is urgent; otherwise, I will do it eventually.


Problems with Switch type or with gpio_set_level function (MEGH-5681)

Answers checklist.

[X] I have read the Rainmaker documentation and the issue is not addressed there.
[X] I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
[X] I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

IDF / ESP32-Arduino version.
ESP-IDF v5.1.3
Operating System used.
Windows
How did you build your project?
Command line with idf.py
Development Kit.
ESP32-Wroom-32 with own development board
What is the expected behavior?
I expect that once the button is turned on, the additional board connected to the pin will turn on and work
What is the actual behavior?
Instead, the additional board turns on and after a few minutes reboots
Steps to reproduce.

I use the Multi_device example
I change OUTPUT_GPIO in app_driver.c to 17
When I turn on the switch, the logic level on port 17 is correct, the additional board controlled via pin 17 turns on, but resets after few minutes

Debug Logs.
There are no error messages or reboot messages in the port and logs

More Information.
When I used Arduino IDE and digitalWrite function, the additional board working perfectly, do not reboots. I think that problem may tied up with declarations of pins, but I test with different pull-up_en, not helps. I tried to add gpio_set_level to 16 pin, no changes.
I add images with electrical scheme of the development board, maybe it helps to find solution

Please. help me, its very important

@KalashQK , is this really related to RainMaker though? Do you mean the logic works fine when you are not using RainMaker?


plugin update question

Will it work if I upgrade only one dependency to v0.18.0

hello everyone，Can i add a react-resizable effect to the pivot table v2 to change the column width

The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: https://github.com/apache/superset/issues/13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant.


spacing issues on testimonial

@sssoz There's a misalignment in Peter Bae's testimonial (see bottom box and text overlap)

Originally posted by @jorlowitz in https://github.com/oaworks/internal-planning/issues/109#issuecomment-827175971

Cards were not a good use case for the Partners and Testimonials pages. Using the same layout as the Team page now (full-width lists).
Done: https://oa.works/people/partners/ & https://oa.works/impact/testimonials/


fix: authnContext to string

Fix per #32
Versione di TypeScript: 4.2.2

@Datalux this doesn't look right to me, why are we removing the type? And isn't entityID already a string?

@bfabio we still have those spurious error messages due to #32
This pr fixed It but we Need to keep an Eye on the cause of these undefined values, if we converte them to a string (even if "") It doesn't throw that warning/error


replace unmaintained safemem::copy_over with slice::copy_within

the safemem library is unmaintained
both safemem::copy_over and slice::copy_within use ptr::copy internally, so the performance impact should me minimal.
slice::copy_within was added in rust 1.37.0, but I don't know if lol-html has an official MSRV

CI failures are unrelated clippy warnings.

Could you please rebase on top of your clippy fix?

Could you please rebase on top of your clippy fix?

done

Thank you!


Remember Hot Corners?

Summary of the new feature/enhancement
I realize this would be a whole new feature and not necessarily improvements to the existing toys, but I have long waited for Microsoft to implement the old Mac feature "hot corners" where by simply moving the mouse to any of the 4 corners of the screen would do things like prevent sleep, or launch a screen saver, or any program for that matter. It sounds like a power user function to me, so power toys sounds like a good place for it.  In the event of multiple screens, it would still be just 4 corners two on each extreme end of double wide screen or one on each corner of a quadruple double stacked screen. There were some improvements to the Mac version I hoped one day to see on a Microsoft version, but one thing at a time I guess. First, let's see if the feature makes the proverbial "cut".

Proposed technical implementation details (optional)

@damianlavalle
closing as duplicate of https://github.com/microsoft/PowerToys/issues/1305
Feel free to add your comments there.
Thanks.


[WIP] Update plutus version to 1.30

I made scripts compile but without functionality to compare ScriptInfos.
The Plutus.Eq instances are gone and its not clear why would one compare ScriptInfos.

Thanks a lot Yura! I'll test the new scripts first thing on Monday.


Non existent var

see https://scrutinizer-ci.com/g/elkarte/Elkarte/inspections/8e1de498-8f7a-4a44-a0d6-6c71366e9347/issues/files/sources/subs/Package.class.php?status=new&selectedLabels[0]=9&orderField=path&order=asc#inspectioncomment-155709100
Apparently it has been there since the beginning, but it should not exist at that point in that conditions (unless I'm reading it wrong that may happen).
I'm not sure if it is necessary or not, so I track it for future reference. O:-)

Protip: give more context when reporting an issue from scrutinizer.

Memo: remember that scrutinizer reports do not last very long...

Closing as not understandable.

Probably got lost or maybe even fixed / removed when I did the last batch of package xyz file updates.


Validate that analytics can exclude CDS internal traffic

Desired outcome
All metrics on Google analytics dashboard can be filtered to exclude traffic from CDS employees.
User and event counts can be filtered to exclude CDS employees beyond the LR team
Expected behaviour to be measured
When a CDS employee starts a session on the Learning resources website via their work computer or phone (or from their typical work IP address), there is no change in any of the metrics on the google analytics dashboard with an "exclude internal traffic" filter applied.

This issue is similar to Issue 212 except that:

It's lower priority
It would be good if we can continue to collect data on internal CDS use, but exclude it easily in the analytics dashboard rather than blocking it entirely. It's not currently a metric we're tracking, but if it becomes one it would be good to have historical data.

🧩 I'm not quite sure how to measure this metric quite yet 🤔


cannot find fonts when running from inside a container

I am using the latest container asciidoctor/docker-asciidoctor from hub.docker.com, which contains asciidoctor-pdf 1.6.2.
asciidoctor-pdf fails with: (only latest part of the trace)
No such file or directory - /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/data/fonts/notoserif-regular-subset.ttf not found (Errno::ENOENT)
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:3608:in `each'
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:3608:in `each_with_object'
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:3608:in `block in register_fonts'
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:3607:in `each'
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:3607:in `register_fonts'
        from /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/lib/asciidoctor/pdf/converter.rb:328:in `init_pdf'

But the file is there:
bash-5.1# ls /usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/data/fonts/notoserif-regular-subset.ttf
/usr/lib/ruby/gems/3.0.0/gems/asciidoctor-pdf-1.6.2/data/fonts/notoserif-regular-subset.ttf

Any idea?

It sounds to me like this is a volume mapping issue. You may be mapping the volume in such a way that it cannot access the location of the font file anymore. I've seen cases where the message is misleading because one filesystem is fused into the other, so when you check the path after the fact it is present. You need to inspect the filesystem location while Asciidoctor is running, from within the container.
In the future, please direct questions about using the software to the project chat at https://asciidoctor.zulipchat.com. If you repost your question there, others might be able to chime in to help you debug it.


Security threat. /bin/sh: 1: Syntax error due to improper character handling

When using exec provider with variable with special characters. eg:
prompts:
  - "{{violation}}"

providers:
  - exec:python3 provider.py:

tests:
  - description: exploit
    vars:
      violation: "`('"

Whenever a variable contains special shell characters we might get an error like:
Error: Command failed: python3 provider.py "[{\"role\":\"user\",\"content\":\"`('\"}]" "{\"id\":\"exec:python3 provider.py\",\"config\":{\"basePath\":\"\"}}" "{\"vars\":{\"violation\":\"`('\"}}"
/bin/sh: 1: Syntax error: Unterminated quoted string

Using shell when executing script providers is also a security threat! The provider should be executed directly (via exec call) rather that via system call  through shell. Adding more escaping rules is not the right path as it can quickly get convoluted and either brake the passed values or leave a gap for another escaping trick.
For example if the variable is:
      violation: "`rm -rf /*`"

It will execute the rm -rf /* command rather than passing that to provider. This behavior is not only insecure but also inconsistent with other providers.

I believe in JS it's spawn() that does the proper exec syscall (and JS's exec is actually a system call):
https://stackabuse.com/executing-shell-commands-with-node-js/

Thanks for raising this.  #343 rewrites exec calls to not use a shell via execFile and spawn.  You're right that this solves a lot of headaches and potential side effects with escaping.
There is a backwards compatibility issue for anyone who relied on shell behaviors.  I'm considering retaining support with a useShellUnsafe or similar config param for the exec provider type.

Resolved in version 0.33.0


chore: Change Sort by and Sort descending controls for Time-series Bar Chart

SUMMARY
This PR hides the SERIES LIMIT SORT BY and SERIES LIMIT SORT DESCENDING when no SERIES LIMIT is set and viceversa.
There is an issue for which some controls are not properly cleared when hidden. This issue is already affecting master and will be fixed in a separate PR.
AFTER
https://user-images.githubusercontent.com/60598000/156021827-ca7b40c6-ac7d-436d-8a31-c864e7ec1dbf.mp4
TESTING INSTRUCTIONS

Open a Time-Series Bar Chart
Add a SERIES LIMIT
Make sure the SERIES LIMIT SORT BY and SERIES LIMIT SORT DESCENDING appear
Remove the SERIES LIMIT
Make sure the SERIES LIMIT SORT BY and SERIES LIMIT SORT DESCENDING do not appear

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] 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

Hello @zhaoyongjie this is the problem that I am mentioning in the description as well. This issue is affecting master too and it requires more investigation. @stephenLYZ is working on it in a separate PR. Thanks!

For reference, the problem mentioned above can also be reproduced from this PR https://github.com/apache/superset/pull/17726. The Sort descending will always be applied even when hidden

Hello @zhaoyongjie this is the problem that I am mentioning in the description as well. This issue is affecting master too and it requires more investigation. @stephenLYZ is working on it in a separate PR. Thanks!

Thanks for the explanation. LGTM


Create Codemasters23

My html add

Your pull request needs further work because of the following reason(s):

Your filename must be codemasters23.html
Your file does not have the .html extension.

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

944e1af680e48a7fdb7b175ff5e8978c30c7ebfa

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

This contains potentially hazardous tags that need manual review.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

ebff1b13131bf27402b6b0c9ab0baea5bbef5fb2


convert the time_received_ns  value to second

Hi.
Is there a specific parameter or configuration option available to convert the time_received_ns value from nanoseconds to seconds?
I have carefully reviewed the documentation, but unfortunately, I couldn't locate any relevant information or guidance on the specified topic.

Hi Ali,
Unfortunately no, only V1 of GoFlow2 is in second.
Could you indicate your use-case?


fix: datepicker keyboard navigation fix vue2 only

Datepicker keyboard navigation fix vue2 only
Some background:
We received a bug fix report from DP-86647.
Steps to reproduce it are in the ticket comment section.
Seems like keyboard navigation does not work well in the product.
It works ok in storybook, in both variants, default and with popover.

Doing research seems like refs are not being assigned.
This methodology was failiing in product el => { if (el) setDayRef(el, day) }.
Then it is necessary to rethink how to write this dynamic ref.
This issue is only vue2, since in vue3 template refs works in slightly different way. (Also this report comes from vue2, not vue3, I would not touch vue3).

I did the necessary refactor to make it work and in my local tests it is working as expected in product.

I didnt dig on why it is happening on the product side.
Because storybook is vue2 and its works well.
Would be cool to get and tackle the origin of this issue.
There is a chance were we get this same issue on our emoji picker in the vue2 product side, or may not.

No visual tests are required.


Create ComplexFloat trait to model Floats as a subset of Complex

Resolves #2. Replaces #53. Nearly all the work here was already done by YakoYakoYokuYoku. I have merely updated it to master and  made a few discretionary changes which I think improve the work slightly. More unit tests will be coming.

If you want it you could add a Co-athored-by: Martin Reboredo<EMAIL_ADDRESS>at any one of your commits. LGTM otherwise.

I will certainly do so. Thanks!

Ping, any chance I could get a review before end of year?

Bump

Awesome work, I'm happy this trait comes alive.


Update tests

Codecov Report

Merging #93 (ec3a8d3) into int (dc3010d) will increase coverage by 0.40%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              int      #93      +/-   ##
==========================================
+ Coverage   65.91%   66.32%   +0.40%
==========================================
  Files          12       12
  Lines        1159     1164       +5
==========================================
+ Hits          764      772       +8
+ Misses        306      303       -3
  Partials       89       89

Impacted Files
Coverage Δ

agent.go
76.60% <100.00%> (+0.70%)
:arrow_up:

dnsproxy.go
76.66% <100.00%> (ø)

apiclient.go
90.90% <0.00%> (+4.54%)
:arrow_up:

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 dc3010d...ec3a8d3. Read the comment docs.


Updates lib to be compatible w/ v0.5.11

@codelemur Sorry, I didn't see your PR when I opened mine (duplicate?): #3

The only "extra" thing I'm doing is adding some boilerplate that demonstrates how to get vessel and use github-based CI (not travis).  If you look at my forked version, you can see that my CI passes: https://github.com/matthewhammer/motoko-sha/pull/1

I don't know about the provider stuff, or whether we need it here.  I also added some dfx.json stuff that may or may not be needed.  Since the semantics of that file is always unclear, it's always unclear.

@matthewhammer no problem, #5 looks good to me


digital ocean preset

Usage notes/documentation:

Need to add engines.node version to package.json (docs)
set HOST to <IP_ADDRESS>

also supports docker images: https://github.com/unjs/nitro/issues/54

Let's iterate over later for docker support.


Update CFX to Bootstrap 4.x

In case you are still interested in doing this, there is a pretty straight forward guide: https://getbootstrap.com/docs/4.0/migration/


Collapsible Tree D3js cumulative data with each node

I am trying to use the d3js Collapsible Tree visualisation in my Power BI project, the code of which can be found here - https://bl.ocks.org/mbostock/4339083
Along with the name of the node, I also want the data of that node displayed alongside. For example, if Asia expands into India, China and Japan, then the node Asia should display the cumulative data of all these 3 countries, whereas India, China and Japan will show their own respective datas. Similarly, the node China must display the data of all the cities of China combined, and all the cities of China must show their respective data.
It would be great help if I could get assistance for the same.

Have you find a solution to use d3js collapsible tree in Power BI,
I'm looking for the exact same solution


⚠ Secret Website 3 has degraded performance

In c958d10, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2608 ms

Resolved: Secret Website 3 performance has improved in dbec420.


Deprecate Iterative Algorithm

Delete search_iterative().

@jeremyliweishih we add this to your epic for when you get around to it!

@chukarsten sounds great!

@freddyaboulton brought up that we can define a AutoMLAlgorithParameters class and have users specify them there for either the Default/Iterative algorithm. Will consider implementing that in this issue to make AutoMLSearch API less confusing (as there would be parameters specific for each algorithm [allowed_component_graphs being one of them]). If not I will file another issue for tech debt.


remove github robot

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Replace github robot with prow robot, romve it first.
Does this PR introduce a user-facing change?:

/lgtm


[dv/sim] dvsim no longer works for regression V1 and V2

Dvsim no longer works for regression sets V1 and V2 - but it does still work for the all option.
I have tested with boch Hmac and AES.
both gives

on the lastest Master.

Whoops! I did modify the logic that computes the tests per milestone. I will take a look and fix it soon.

Fixed wit h#6698.


Error adding Icon when running New-DeviceAppManagement_MobileApps command

I am trying to run the New-DeviceAppManagement_MobileApps to add Android Applications.
I have had it working with the following command:
New-DeviceAppManagement_MobileApps -androidStoreApp -displayName $Application.Name -appStoreUrl $application.URL -publisher $application.Publisher `
            -Description $application.Description -minimumSupportedOperatingSystem $androidVersion

But when I try to add an icon, I keep getting a 400 ERROR code back.
I tried to create the same application using the GRAPH API with the icon, and that works
I noticed the icon parameter requires a MimeContent Object
So first I created one.
The Value of the Mimecontent should be a byte, that is why I ran this code:
$encoding = [system.Text.Encoding]::UTF8
 $iconResponse = Invoke-WebRequest $application.Icon
 $iconExt = ([System.IO.Path]::GetExtension("$application.Icon")).replace(".","")
 $iconType = "image/$iconExt"
 $data = $encoding.GetBytes($iconResponse.Content)

If I then run the following, it creates the object
$icon = New-MimeContentObject -type $iconType -value $data
But using that object in the New-DeviceAppManagement_MobileApps function gives a 404 error
400 Bad Request {   "error": {     "code": "BadRequest",     "message": "{\r\n  \"_version\": 3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: bcded7cb-75bc-4658-bc16-f333fd06f6c7 - Url: https://fef.amsub0102.manage.microsoft.com/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=2018-03-22\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{}\"\r\n}",     "innerError": {       "request-id": "bcded7cb-75bc-4658-bc16-f333fd06f6c7",       "date": "2018-10-15T19:08:08"     }   } }
This is the command I use:
New-DeviceAppManagement_MobileApps -androidStoreApp -displayName $Application.Name -appStoreUrl $application.URL -publisher $application.Publisher
-Description $application.Description -minimumSupportedOperatingSystem $androidVersion -largeIcon $icon`
I also tried:
New-DeviceAppManagement_MobileApps -androidStoreApp -displayName $Application.Name -appStoreUrl $application.URL -publisher $application.Publisher
-Description $application.Description -minimumSupportedOperatingSystem $androidVersion -largeIcon (New-MimeContentObject -type $iconType -value $data)`
But that doesn't work aswell.
Running the same code without the largeicon URL fixes the problem

Looking into it, I will get back to you soon.

Out of curiosity, what kind of image file are you using?  What is the file extension?

Hi
I used a lot of different files.
I googled a few, used the one from the Play Store. I was able to upload them through the INtune portal.
The last one I used was this one: https://is2-ssl.mzstatic.com/image/thumb/Purple128/v4/cf/f7/e2/cff7e281-fdc7-3a40-8ff0-ca7966d165cf/source/60x60bb.jpg
This is the one I got through the Application_ios_add (https://github.com/microsoftgraph/powershell-intune-samples/blob/master/Applications/Application_iOS_Add.ps1), this is through the Intune API.
This works through MS Graph, but not through Intune PS

I think the problem is that the $iconResponse.Content already is in the correct format without having to encode it.  Please try this:
# Get the icon and its file type
$iconResponse = Invoke-WebRequest $application.Icon
$iconBytes = $iconResponse.Content
$iconExt = ([System.IO.Path]::GetExtension("$application.Icon")).replace(".","")
$iconType = "image/$iconExt"

New-DeviceAppManagement_MobileApps `
    -androidStoreApp `
    -displayName 'Test' `
    -appStoreUrl 'https://play.google.com/store/apps/details?id=com.whatsapp' `
    -description 'Test app' `
    -minimumSupportedOperatingSystem (New-AndroidMinimumOperatingSystemObject -v4_0 $true) `
    -publisher 'Test' `
    -largeIcon (New-MimeContentObject -type $iconType -value $iconBytes)


Break long table columns

My problem is that I can't see in the generated pdf the whole column. It will be cut at the end on the current page and on the next page it starts with the next row.

Sorry, but I can't post here the whole screenshot.
I didn't find any solution for my problem.
I'm using this versions
        <asciidoctor.maven.plugin.version>1.5.6</asciidoctor.maven.plugin.version>         <asciidoctorj.version>1.5.4</asciidoctorj.version>         <asciidoctorj.pdf.version>1.5.0-alpha.17</asciidoctorj.pdf.version>         <jruby.version><IP_ADDRESS></jruby.version>

A cell cannot be taller than the height of a single page. You will have to split it manually. This is a hard constrain of this converter due to a limitation in the underlying PDF generator (specifically prawn-table). This constraint is documented in the README: https://github.com/asciidoctor/asciidoctor-pdf#known-limitations


Create Export lib to store some smart-dump functions

Resolves https://github.com/opencollective/opencollective/issues/7494

@Betree OK, I'll give another pass at it and split it even further so we can minimize possible conflicts later on.


Added 2.7 release notes.

Issue #, if available:
https://github.com/opensearch-project/alerting/issues/847
Description of changes:
Added 2.7 release notes.
CheckList:
[x] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #864 (baa35c6) into main (e0b7a5a) will decrease coverage by 0.14%.
The diff coverage is 85.71%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #864      +/-   ##
============================================
- Coverage     75.80%   75.66%   -0.14%
  Complexity      110      110
============================================
  Files           125      125
  Lines          6890     6888       -2
  Branches       1037     1035       -2
============================================
- Hits           5223     5212      -11
- Misses         1137     1148      +11
+ Partials        530      528       -2

Impacted Files
Coverage Δ

...opensearch/alerting/util/DocLevelMonitorQueries.kt
72.94% <85.71%> (+0.69%)
:arrow_up:

... and 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Basic examples

@javisantana

@andrewxhill I merged the examples but I could not merge API.md because you did changes on top of an old version.
Please, update the branch with develop, fix the merge and send PR again

crap, sorry. in haste Commits on Aug 9, 2013

the examples were all i needed, no new pull request coming. thanks


Allow logical flows to link to actors

Partition the slope diagram so sources/sinks are grouped by type.

Todo:

update OrphanDao::findOrphanLogicalDataFlows
update slope diagram
update editor

1833 - Support Actors in Logical flows

update slope and target graph to understand actors

$scope.selected.app => $scope.selected.node [fixed]
partition source and target lists by kind [defer]
update popop [done]

decorator

exclude from rating actor dt decorators [fixed]
recaclculate usage for flows [fixed]
not returning decorators assoc. to actor flows [fixed]

stats

exception [fixed]

boingy

different rendering [fixed]
links to appropriate entity [fixed]
rename $ctrl.selectedApplication -> $ctrl.selectedNode [fixed]
detail table [fixed]

editor

add actors [fixed]
decorate actor flows [fixed]

housekeeping

recalc flow ratings: [fixed]
recalc dt usage ignores actor flows [fixed]


Physics system plans

I see that the physics system is not super extensible at the moment. Leaning in to generic functions and CLOS could make it easier to deal with as long as it wouldn't be too slow, though that could be premature optimization talking.
I did some light refactoring purely for my own benefit here (not change reccomendations)
https://github.com/Drainful/sucle/blob/physics-refactor/src/sucle/physics%2B%2B.lisp
I'm curious about your plans/goals for the physics system, and I'm interested in helping out if you're open to it.

As you can probably tell, I have not focused so much on the physics side, and don't really know how to change it. For the longest time I've wanted to have items and things running around, but I couldn't figure out how to structure it. Things like animals, buttons, monsters, rocks, in-game items, particles, etc...
Using CLOS wouldn't be a problem, there would probably only be a few hundred things anyway.
Looking at https://github.com/Drainful/sucle/blob/physics-refactor/src/sucle/physics%2B%2B.lisp and running it I can tell that its a lot more readable and it works [how did you refactor that?] but I'm not sure how the physics package system commented below would be extended to have other objects. Please, it would be great if you could tell me how to do this...

I've tinkered with physics engines and CLOS enough to have a good idea of what to do I think. Here's my initial attempt. It's not functional yet, but it should give you the idea of my plan.
https://github.com/Drainful/sucle/blob/physics-clos/src/sucle/closphys.lisp
By splitting the physics function in to a set of generic functions and methods related by method combinations, any facet of the system could be extended.

Thank you so much for providing insight into this! I never would have thought to use multiple inheritance with method combination this way, now the solution appears very intuitive and Common-Lispy.
How it seems like it would work:

In order to create a new type of game object, one would inherit from entity, living-entity, or has-position/physics/drag/mass/gravity
Then to customize rules for that object, one would use method specializers to override the defaults
Every physical object is wrapped in a before-physics and after-physics
Each game tick, step-physics is called on each of the game objects in the world

This seems like a great way to organize game objects, where there are tons of different types of objects that could exist, all having different properties and rules, so some would not have gravity, others would not have drag, etc... A long time ago I looked at the Minecraft source code in Java, but because Java does not support multiple inheritance, this strategy would not be available. Because CLOS is one of the most advanced object systems, perhaps this could be the first game system to effectively utilize CLOS, and do objects even better than the engines in other languages.
I can't wait to get around to implementing the new system! However I won't be able to work on it for a few days because of life.
Thanks for solving one of the longest-standing issues in sucle!!!!! If there's ever something you need help with, just ask!!

I think this engine has a lot of potential; I should be thanking you. Would you be open to accepting a pull request for this when your time frees up? I’ve kinda gotten invested. I’d make sure to document well, and integrate my code cleanly with the rest of the project. It would just be a re-implementation of what currently exists, but after that it should be easy to implement, say, collision between entities.

Sure a pull request that refactors the existing code and is well documented would be very welcome, but I think it would be better if we:

Stepped through the decisions together
Clarified what you are looking for out of this project
Figure out what the project goals are/should be
Clarify what the expectations are/should be
etc...

The following are statements which are subject to change. I'm open if you want to take the project in a different direction, or have ideas of what it should/should not be. Or, if you are no longer interested, you do not have to stay, it is up to you.
TLDR: There are unique, never-before seen benefits to writing a voxel engine in Common Lisp, however this project does not have deep pockets or a viable business model. I'm doing it for fun.
What advantage would this have over other voxel simulations?

Common Lisp
CLOS, one of the best object systems, for entities and physics, possibly the first major implementation
Simple infinite world full of lisp objects
Programmatically create voxel worlds, with the live-coding ability of Common Lisp

What disadvantages does this have compared to other voxel games?

In terms of fancy graphics, GUI, networking, animation, realism, there is a lot to be desired.
It does not have the ecosystem of other languages, so implementation will be a challenge.
I am not doing this for profit, and I don't have very much time or resources.
It does not have a market monopoly or huge existing userbase or codebase.

Why I started and continued this project:
I started this project out of my own amusement, and at the moment it is mainly a voxel editor and walking simulator.  I have yet to see voxel art or Minecraft maps that mimic the kinds of things you can create map-wise in this. With entities added, all sorts of worlds could be made that could not exist in other voxel games. One of the ideas is that while the majority of voxel editors, including minecraft, are geared towards being relatively static, this game would have procedural generation and interactivity all the way through.

I'm telling you this so you can decide if you are still interested, so you know what you are getting into.

First I want to thank you for writing that up; I am still interested, and I think we share a similar vision for a hackable live-codeable common lisp voxel engine. My goal for contributing to this project is to strengthen the core of the engine by creating well polished mechanics and systems with many extension points so that I can use Sucle as a basis for experiments in game design, and perhaps for a fully fledged game.
I will be approaching the project from the same hobbyist perspective, and I am familiar with the limitations brought on by using a relatively obscure language. I can't promise I won't lose interest in the future, but right now I'm excited to see what can be done. On that note, I wrote up this document explaining my choices with the physics system refactor. https://github.com/Drainful/sucle/blob/physics-clos/closphys.org

Thanks for writing up the document explaining the physics system refactor. closphys.org and closphys.lisp have been move to the development branch. closphys.org has also been moved to doc/closphys.org. Now all that's left is to flesh it out a bit more and add more entities I presume. If there is any feature that you don't understand or would like to have explained, don't hesitate to reach out.
Thanks again!

Sure. After the refactor is done I could make a branch for PR with the new physics.lisp all in 1 commit; might be cleaner. It might be ready tonight; I plan to work on it for a bit.

I have to refactor the main loop a little bit in order to pass dt to the step-physics function; I'll set up a classic game loop with an adaptive time step. The per-frame funciton is a good candidate for a refactor after physics.

Here are some new functions that expose the current physics-rate and dt: https://github.com/gregcman/sucle/commit/c140bebfa06ac62ff2d35fc41f84fde94dbc3b73
(fps:dt) -> The target dt
(fps:ticks-per-second) -> The target physics rate
These functions don't expose the real amount of time passed, but what the expected dt should be for each physics tick. So (fps:dt) gives 0.016666 for 60 ticks per second, because at the moment the physics system tries to run at 60 ticks per second regardless of the graphical framerate, which is set by (fps:set-fps 60) at the beginning in the function sucle-app.
The call to (fps:tick ...) in sucle-per-frame may run the physics code within 0 to any number of times, up to a cap. The physics loop is an implementation of this: https://gafferongames.com/post/fix_your_timestep/

Got it. I have the new physics system working now; I just need to fix a bug with gravity and do a lot of code cleanup and I'm ready to submit a PR. What's your opinion on (clos)physics.lisp being in a separate package rather than #:sucle? It'll take a bit more work to sort out things like which utility functions should be in each one, but perhaps it's cleaner. I'd be happy either way.

Thanks for refactoring the physics system, and breaking it into more manageable chunks. More packages are usually better, if you export symbols well.
However, with regards to the overall direction of the physics system, I have recently come across this thing called the 'Entity Component System' or ECS. Unreal, Unity, and Minecraft Bedrock edition use something like this. There's a simple library for a hybrid CLOS-ECS at https://sjl.bitbucket.io/beast/ which seems like it could map closely to closphys.lisp
So I would advise you to submit the pull request, it doesn't have to be complete. Then, I would port it to use https://sjl.bitbucket.io/beast/ which looks similar enough to what we're doing here. So you don't have to fully flesh out the pull request or tidy everything up, you can just PR what you already have and we'll work from there.

I've used beast in the past! Yes I like the ECS style, and I've used an ECS written in rust (Specs) to do a physics system before. I will say that the traditional primary benefit of ECS is to follow data-oriented design (ECS is good for cache-coherency), while in common lisp we don't have the fine-grained control over memory necessary to fulfill that advantage.
Therefore I see little benefit to using Beast over the already quite flexible CLOS (over which it is a fairly thin abstraction layer), but I don't think its worse either, so if that's the way you want to go I'm on board. The advantage of Beast over CLOS is the ability to write "systems" which can iterate over every object which fulfills an aspect requirement, which can be done through CLOS with a bit of helper code.

Unreal, Unity, and Minecraft Bedrock edition use ECS primarily for the performance benefit, using very specific contiguous memory layouts to maximize cache coherency. We could achieve the same effect by using an ECS written in a lower level language via ffi, though it's probably not worth the trouble.

Buttons, particles, rocks, and items [and eventually animals and monsters] can finally exist in sucle! This is a major update and should be reflected in the [not-yet existing] versioning system.
On ECS:
You say that these big engines use ECS for the performance gains, and that using an ECS written in Common Lisp is nearly pointless, because it is not low-level enough. Yes, I may be cargo-culting somewhat. However, although Common Lisp may not be able to take advantage of some of the low-level strategies afforded by ECS, such as cache coherency, ECS has the ability to add/remove components of individual entities at runtime, although I think Beast doesn't have this capability. Maybe using Beast is not a well-thought out plan... Perhaps for now, the performance gains don't matter, and the big guns should not be pulled out yet, because there is not yet a bottleneck in sucle sufficient to warrant ECS.

That would be my perspective. If it means anything, CLOS is 100% capable of adding and removing "Components" (superclasses/aspects) at runtime simply by redefining a class to have or not have the relevant superclasses. The limitation, if it could be called that, is that every instance of that class (and every instance of its subclasses) are altered at once. I believe it is possible to altar the class heiarchy of a single object at runtime as well. but I haven't looked in to it.

But in reference to bottlenecks, the new phsyics system seems to have some intermittent lag. The slime profiler doesn't reveal much time spent in the new physics functions, but it does reveal that they do a bit of consing, so it might be garbage collection lag. The temp vectors should have mostly removed that problem though. More investigation is required.
Also, I don't really know what to do with the jumping mechanic. Currently if spacebar is pressed, every frame where (on-ground entity) is true entity gets some vertical boost to velocity. The issue is that it seems like on-ground is true for multiple frames in a row before a jump, making the actual velocity gained unpredictable.


TachiyomiSy preview r531 crash

Open a random entry, read it, exit it and press on the "expand tags and more"  button(kinda look like an arrow pointed down)
Crash does not always happen, I hope crash logs will help
Android 12
S10

also experiencing node not yet measured related crashes


Add tvOS Static Library Build Target to Support tvOS

Can you add a new tvOS Static Library build target for this package?
I found an example on how to do this in another library: https://github.com/react-native-community/react-native-video/pull/614/commits/bed60891765c7127eec6740f5e00b552f2cf8b95

@kmagiera I created a PT https://github.com/kmagiera/react-native-screens/pull/65

Thanks a lot @hufkens! Closing this as just merged #65


feat(bing): add image recognition functionality (#452)

@Richard-Weiss Please review this PR as I've forked node-gpt-api to keep this library better maintained
Add groundwork for implementing the image recognition feature.
The only missing component is setting the parameters in the message dynamically.
I would appreciate any assistance.
--Edit--
I've added receiving the necessary values from the body of the /conversation request.
The imageURL or imageBase64 are added dynamically by for example PandoraAI.
Tested with image URL and direct base64 string.

@danny-avila
Why do you need a review to merge a PR in your own fork into the main branch of your own fork?
Or did I get something wrong?
This seems a bit odd.
I can approve it but next time you can just create a new local branch from my pr and merge it locally into your main branch.
No need for any approval as it isn't being merged into the upstream repo.

Why do you need a review to merge a PR in your own fork into the main branch of your own fork?
Or did I get something wrong?
This seems a bit odd.

I'm looking to diverge from upstream since it seems the maintainer has no interest in maintaining it. The goal here is not simply to have my own fork but to ensure the community can keep maintaining the original project

I can approve it but next time you can just create a new local branch from my pr and merge it locally into your main branch.
No need for any approval as it isn't being merged into the upstream repo.

There is "no need", but as this repo is publishing to npm and already at 600 weekly downloads for this week, I would appreciate a second look/test.

Also I see that you are missing the actual important commit.
You can google how to fetch a pr and merge it locally or I can show it to you tomorrow.

Is your PR on the upstream not have https://github.com/waylaidwanderer/node-chatgpt-api/pull/452/commits/187085f1ed96269ed0bd0f273463de5f0270a301 as the latest commit? it's here

@danny-avila I'll create a new PR only containing the relevant commits for the image recognition.
I'll tag you once it's done.
I also have a feature in my fork for using Local LLMs, is this something you or other users might be interested in?


Adding StackView destroys layout.

I have the following code in my ViewController class
// MARK: - Properties

let titleView: UIView = {
    let titleView = UIView(frame: CGRect(x: 0, y: 0, width: screenSize.width, height: 70))
    titleView.translatesAutoresizingMaskIntoConstraints = false
    let backgroundColor = UIColor(red: 0x6D/255, green: 0xBC/255, blue: 0x63/255, alpha: 1.0)
    titleView.backgroundColor = backgroundColor

    return titleView
}()
let welcomeStackView : UIStackView = {
    let stackView = UIStackView(frame: CGRect(x: 0, y: 100, width: 50, height: 40))
    stackView.translatesAutoresizingMaskIntoConstraints = false
    stackView.axis = .vertical

    return stackView
}()

// MARK: Lifecycle

override func viewDidLoad() {
    super.viewDidLoad()
    print("Up and running")
    setupBackgroundView()
}

// MARK: - Setup

private func setupBackgroundView() {
    self.view.backgroundColor = .purple

    //Add subviews to main view
    self.view.addSubview(titleView)
    setupTitleView()

   //        self.view.addSubview(welcomeStackView)
   //        setupWelcomeView()
}

}
When I layout just the titleView, everything is fine and it looks like this.

Once I uncomment the line which adds welcomeStackView to the main view, everything seems to break and it looks like this.

Does anyone have any idea why this is happening?

Hi @hhammoud2,
First, since you control view's from your UIViewController you must override viewDidLayoutSubviews() and layout your titleView in this method. See below
Second, UIStackView is based on auto layout, I've never tried it, but it may be difficult to mix manual layout with UIStackViews. But you may try to layout it in viewDidLayoutSubviews() and see if its content will get layouted automatically.
override viewDidLayoutSubviews() {
   super.videDidLayoutSubviews()

   titleView.pin.top(topLayoutGuide.length).left().right().sizeToFit(.width)
   // UIStackView takes the remaining vertical space.
   welcomeStackView.pin.below(of: titleView)..bottom().left().right()
}

Please also have a look at the PinLayout example app.


scons -c fails if .sconsign.dblite is deleted

This issue was originally created at: 2008-12-03 12:50:06.
This issue was reported by: rhl.
rhl said at 2008-12-03 12:50:06

scons -c doesn't delete .sconsign.dblite and .sconf_temp (is
this a bug in its own right?)
Given the problems with a corrupted .scons_temp if you ^C out of a configure
context (Issue http://scons.tigris.org/issues/show_bug.cgi?id=2157), I added an
"rm -rf .sconsign.dblite .sconf_temp" to the
clean actions.
This results in:

scons -c
scons: Reading SConscript files ...
Checking for C++ header file tr1/unordered_map... yes
find . \( -name .svn -prune -o -name \* \) \( -name \*~ -o -name core -o -name
\*.so -o -name \*.os -o -name \*.o \) -exec rm -f {} \; ; rm -rf .sconf_temp
.sconsign.dblite
scons: done reading SConscript files.
scons: Cleaning targets ...
scons: done cleaning targets.
OSError: [Errno 2] No such file or directory: '.sconsign.dblite':
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/Script/Main.py",
line 1261:
    _exec_main(parser, values)
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/Script/Main.py",
line 1226:
    _main(parser)
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/Script/Main.py",
line 989:
    nodes = _build_targets(fs, options, targets, target_top)
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-.1.0.d20081104/SCons/Script/Main.py",
line 1182:
    jobs.run(postfunc = jobs_postfunc)
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/Job.py",
line 111:
    postfunc()
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/Script/Main.py",
line 1179:
    SCons.SConsign.write()
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/SConsign.py",
line 107:
    syncmethod()
  File
"/u/tst/products/DarwinX86/sconsDistrib/1.1.0.d20081104/lib/scons-1.1.0.d20081104/SCons/dblite.py",
line 104:
    self._os_unlink(self._file_name)
Exception exceptions.OSError: (2, 'No such file or directory',
'.sconsign.dblite') in <bound method dblite.__del__ of <SCons.dblite.dblite
instance at 0x67fc38>> ignored

It is obvously scary to mess with .scon* files, but in this case it
is needed.

gregnoel said at 2008-12-24 07:13:18

Bug party triage.  There are plans afoot so that 'scons -ccc' will delete the
.sconsign file(s) and the like, but that's still a ways out.  In the meantime, a
stack trace is kinda rude, so put this where we'll look at it again.

This bug is now affecting me.  The .sconsign.dblite made with Python 3 is not compatible with Python 2.  So when I build gpsd with scons on python 3, I need to nuke .sconsign.dblite to do a build on Python 2.
scons: Building targets ...
scons: *** [ais_json.os] ValueError : unsupported pickle protocol: 4

This bug is now affecting me. The .sconsign.dblite made with Python 3 is not compatible with Python 2. So when I build gpsd with scons on python 3, I need to nuke .sconsign.dblite to do a build on Python 2.
scons: Building targets ...
scons: *** [ais_json.os] ValueError : unsupported pickle protocol: 4

@garyemiller
I'm pretty sure the issue you're having is not this issue, but rather incompatibility between py2 and py3 pickle protocols being used by SCons as well as py2/py3 incompatibilities.
Also this issue is explicitly listed in Announce.txt.
https://github.com/SCons/scons/blob/master/src/CHANGES.txt#L412
Please bring your issue to the users mailing list, IRC, or our discord channel and we'll see if we can help you.

"The issue you're having is not this issue, but rather incompatibility between py2 and py3 pickle protocols "
This is a cascade of failures.
Yes, of course, we all know what the pickle problem is.
As we all know the solution is simply to delete .sconsign.dblite
But THIS problem is that I can't just fix it ny making "scons -c" delete .sconsign.dblite, since that fails.  Which is THIS bug.
I don't need help, I know how to fix the pickle bug.  scons needs help to fix this 11 year old bug.
Google .sconsing.dblite.   This bug has hit a lot of people and there is no workaround, except for manual "rm  .sconsign.dblite".
I'm willing to pop onto IRC, if someone tells me what channel.

"The issue you're having is not this issue, but rather incompatibility between py2 and py3 pickle protocols "
This is a cascade of failures.
Yes, of course, we all know what the pickle problem is.
As we all know the solution is simply to delete .sconsign.dblite
But THIS problem is that I can't just fix it ny making "scons -c" delete .sconsign.dblite, since that fails. Which is THIS bug.
I don't need help, I know how to fix the pickle bug. scons needs help to fix this 11 year old bug.
Google .sconsing.dblite. This bug has hit a lot of people and there is no workaround, except for manual "rm .sconsign.dblite".

I'm willing to pop onto IRC, if someone tells me what channel.

#scons on freenode.net of course.
As listed on our website: https://scons.org/contact.html

My understanding is there's really no way to make this work from code in the config scripts; scons has carefully constructed exit code which will cause the file to be rewritten at the very end as the signature database is closed, while instructions you give in SConstruct et.al. would be executed much earlier. Greg Noel's comment about a "really clean" option that has scons itself take care of it would work, but I guess that never came about?

My understanding is there's really no way to make this work from code in the config scripts; scons has carefully constructed exit code which will cause the file to be rewritten at the very end as the signature database is closed, while instructions you give in SConstruct et.al. would be executed much earlier. Greg Noel's comment about a "really clean" option that has scons itself take care of it would work, but I guess that never came about?

Nope. But it does sound like a reasonable idea.  Just make sure the sconsign is removed in an atexit() or similar?

I'd like to add a doc note somewhere that says not to try to remove the sconsign file in your sconscript, but there's very little talking about them (user guide mentions them in the context of writing a decider, and that's it except for the sconsignfile argument handling), so I'm not seeing a logical place. Any thoughts?

As to the original bug report, I don't see this happening in a trivial test - manually removing .sconsign.dblite after a successful build does not seem to cause any problems in doing scons -c. Perhaps in the interim that logic has gotten more robust?

the .sconsign*dblite files are now removed atexti() when you "scons -c".  So this issue should no longer exist.  If you concur, I'll close this as fixed.

I'm not seeing the file being removed, nor any code that would do so.

SConstruct: line 2848:
atexit.register(lambda: os.system("rm -rf .sconsign*.dblite"))

I see, in an sconscript. Got it.