[New chain]: Swell Network Testnet 1.4.1

Summary

https://github.com/safe-global/safe-deployments/pull/876
https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-1924.json
https://rollup-info.altlayer.io/bacon-look-analyst/swell_testnet

Chain ID
1924
Chain detail URL
https://chainlist.org/chain/1924
RPC URL
https://swell-testnet.alt.technology
Blockscout Client URL
https://swell-testnet-explorer.alt.technology/api/v1/graphql
Etherscan Client URL
No response
Etherscan Client API URL
No response
Version
1.4.1
Address (Master copy)
0x41675C099F32341bf84BFc5382aF534df5C7461a
Deployment Tx hash (Master copy)
0x25f63783f99ddb0ca9078d939a045fc5900f12beca518c33db4c90913350539a
Block explorer URL (Master copy)
No response
Address (Master copy L2)
0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Deployment Tx hash (Master copy L2)
0x25add3404a931286398cfcec45aa5280ef1178dc1478ef3b9ed5c28b74b90353
Block explorer URL (Master copy L2)
No response
Address (Proxy factory)
0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67
Deployment Tx hash (Proxy factory)
0xe8f71c6d9961fce8d7f87dd54948a4af7d3b4406c9afdcf32c4f01697d89da57
Block explorer URL (Proxy factory)
No response

/execute


bug: XML Injection (AKA Blind Xpath Injection) in ORG.XMLUNIT:XMLUNIT-CORE [CVE-2024-31573]

Hello! ✋
First, thank you very much for your time. I have opened as a bug a security vulnerability that affects multiple versions of your library, being 8.4.4 the one I currently use and still contains it https://devhub.checkmarx.com/cve-details/CVE-2024-31573/.
I would like to know first, if there is a specific place to report this kind of vulnerabilities.
On the other hand, I would like to know what this library uses this dependency for, only for testing purposes? If not, there will be any 8.4.X version of the library that will fix that one?
Thank you very much and I remain open to start a conversation.
Note: A test case would be highly appreciated, but we understand that's not always possible

It's a transitive dependency from spring-boot-starter-test, and I don't believe it's actually used anywhere in our test suite since we aren't parsing any XML. I don't think a user of DGS would get the dependency at all unless they are also pulling in spring-boot-starter-test; you can exclude that transitive dependency, or use Spring's dependency management to override the version used there.
See: https://github.com/spring-projects/spring-boot/issues/41029, looks like it wouldn't be updated there until Spring Boot 3.4.

Closing as it is not actionable, this is a coming from Spring Boot like @kilink explained.


Starting a new game should actually clear ItemsHolder/StateHolder

ItemsHolder doesn't change localStorage on new game, so when a new key is "rediscovered" (such as state in StateHolder) it still gets the old value.
Perhaps keeping game id as a timestamp and associating it with each state?

Idea: retrieve localStorage, clear it, then set it as an "oldLocalStorage" object in localStorage. When you start up, if everything else is missing but that's there (meaning the user didn't save the new game), restore using it.


Populate the bar chart description from the README.md

This PR adds a short description to the bar chart section of the README file.
It also adds a image to show the bar chart.

@googlebot  I fixed it. I signed the CLA from my account.

@googlebot I fixed it.


Remove number indexer declaration on window object.

This allows string indexing to be preferred which is the typical expectation for the window object.  Fixes TypeScript issue #10457

Hi @ChogyDan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@ChogyDan, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thanks!

Fixes https://github.com/Microsoft/TypeScript/issues/10457


Enhance Error Messaging by Specifying Failure in STT, TTS, or LLM Components

Our current error messages are verbose and lack clarity in pinpointing the exact component failure, whether it's Speech-to-Text (STT), Text-to-Speech (TTS), or Language Learning Models (LLM). We need to improve our error handling to provide more user-friendly and specific error messages.
Problem Statement:

Current Behavior: Error messages are too verbose and do not specify which part of the process (STT, TTS, or LLM) failed.
Impact: This lack of clarity can be confusing for users and makes troubleshooting more difficult for our support and development teams.

Proposed Solution:

Implement Component-Specific Error Messages: Revise our error handling mechanism to include component-specific tags or identifiers (STT, TTS, LLM) in the error messages.
Simplify Error Language: Make the error messages less technical and more understandable to a general audience.

Goals:

Clearly identify which component (STT, TTS, or LLM) the error originated from.
Make error messages concise and easy to understand for users without technical backgrounds.
Assist in faster diagnosis and resolution of issues by our support and development teams.

Additional Notes:

This improvement is part of our ongoing efforts to enhance user experience and streamline support processes.
We should ensure that these changes do not affect the underlying error handling and logging capabilities.

is this issue still open can you assign me this ?

@MAVRICK-1 Hey, yes the issue is still open. The frontend changes are done and its ready to accept the error along with the point of failure, all you have to do is return the error along with the component which failed from the backend side.
Example:
STT: Failed to transcribe voice
LLM: Failed to connect to openai
etc.

@MAVRICK-1 any updates on this issue?

@MAVRICK-1 any updates on this issue?

Sorry, My exams are going on , I wasn't able to look at it . You can assign this to anyone else.

No worries, I'll keep you assigned till someone else wants to take this up. Feel free to unassign yourself if you are no longer interested to work on this.

@Ashesh3 I would like to work if Mavrick is not working on it.


harmonyOS  show abnormality

On HarmonyOS, when the list has 100 pieces of data, swipe to the bottom, then only 5 pieces of data will appear in the flashlist without displaying any data, but clicking on the blank area has an interactive effect

We have no plans to support HarmonyOS in the near future.


Node 14 upgrade

I sort of remember looking at this not too long ago and running into an issue but I can't remember what it was (assuming a real memory).  I went looking but everything checks out and looks good.
Have you build-tested the backend with 14?   Any API changes we have to worry about?  We cool with diverging from the origin repo?
Also, I would like to wait for #621 to settle before rolling this if there's no urgency here.

Yep no urgency.
I haven't build tested it yet, no. Don't think there should be any issues though


Refactor branch: get different menu's

So basically the need to implement filtering for the discord messages will become important now because of the character limit we are facing.
Initial idea for commands:
!menu = gets all the non vegan menu's
!menu vegan = gets vegan menu's
!menu burgers = gets burger menu's (grilli)
!menu special = gets special menu's (erikoislounaat)

Maybe a bit too niche, but lets keep this issue for now if I ever get the feel to complete this one.


How to compile freechat-server

I'm trying to integrate LLaMA into a very low level LLaMA app and was wondering what freechat-server is from. It seems to be the best way to run LLaMA inside of a macOS app. I tried the compiled server executable from the main llama.cpp repo but it's half the file size of free chat-server and when running it, it says
-[MTLComputePipelineDescriptorInternal setComputeFunction:withType:]:722: failed assertion computeFunction must not be nil.

Is the original freechat-server also open source so I can compile it myself?

freechat-server is llama.cpp examples/server. Current release is at this commit https://github.com/ggerganov/llama.cpp/commit/1a159553f921a
It's a universal binary that I create by lipo'ing an x86 and arm build like this lipo -create server server_x86 -output freechat-server
Can't help with that error, sorry, but you could ask over at the llama.cpp repo.
Thanks for checking out FreeChat.


2 Bug Fixes/Feature Addition

Bug #1 state needs to be passed to event handlers. Otherwise they cannot manipulate the state. And since grand magnificent js does monkey business with objects, trying to acces the bloc state from funcs is hard, error prone and hurts readability.
Bug/Feature #2 We need to be able to pass in instantiated events. Earlier this was not possible due to our lord and savior js and its objects, now still its a hacky solution but atleast we can pass payloads with events

My pleasure!, BLoc and BLac to the moon 🚀. Yeah, i use statiscally typed languages like java and dart more, const var let stuff is kind of unorthodox the least for me :d.

@gokturkDev your contribution was released in 0.4.1 🎉

🙌


Rac 5000 5043 5060 os install smoke

Optimized OS installs by not running stack init routine, runs SKU pack installer, then OBM settings instead. This will reduce execution time for OS installs.
@hohene @johren @derrickostertag

BUILD on-build-config #464 : FAILURE

BUILD on-build-config #464  Error Logs  ▼Test Name: test_node_catalogs
Error Details: Node catalog is empty!
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/nodes_tests.py", line 255, in test_node_catalogs
    assert_not_equal(0, len(resp), message='Node catalog is empty!')
  File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 151, in assert_not_equal
    raise ASSERTION_ERROR(message)
AssertionError: Node catalog is empty!
Test Name: setup_ipmi_obm
Error Details: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-pKVH01fU7qBsDXgF/MLvA8Rl3kc"', 'Date': 'Fri, 16 Jun 2017 16:19:07 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (bmc).","status":"404","UUID":"76b39415-8040-4ea0-a512-05cfafbfce4e"}
-------------------- >> begin captured logging << --------------------
tests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c0735f0d460abdc10c)
tests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c6735f0d460abdc10d)
tests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c8735f0d460abdc10e)
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
testMethod()
File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
self._testFunc()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
compatability.capture_type_error(s_func)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
func()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
func(test_case.state.get_state())
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/obm_tests.py", line 27, in setup_ipmi_obm
assert_equal(len(obmSettings().setup_nodes(service_type='ipmi-obm-service')), 0)
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/obm_settings.py", line 65, in setup_nodes
if self._set_ipmi(uid) == False:
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/obm_settings.py", line 23, in _set_ipmi
Api().nodes_get_catalog_source_by_id(uid,'bmc')
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/apis/api_api.py", line 1862, in nodes_get_catalog_source_by_id
callback=params.get('callback'))
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 322, in call_api
response_type, auth_settings, callback)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 149, in __call_api
post_params=post_params, body=body)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 342, in request
headers=headers)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 184, in GET
query_params=query_params)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 177, in request
raise ApiException(http_resp=r)
'(404)\nReason: Not Found\nHTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-pKVH01fU7qBsDXgF/MLvA8Rl3kc"', 'Date': 'Fri, 16 Jun 2017 16:19:07 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})\nHTTP response body: {"message":"No Catalogs Found for Source (bmc).","status":"404","UUID":"76b39415-8040-4ea0-a512-05cfafbfce4e"}\n\n-------------------- >> begin captured logging << --------------------\ntests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c0735f0d460abdc10c)\ntests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c6735f0d460abdc10d)\ntests.api.v2_0.obm_settings: WARNING: No OBM settings for node type compute (id=594404c8735f0d460abdc10e)\n--------------------- >> end captured logging << ---------------------'
Test Name: test_catalogs
Error Details: Catalog dmi not found in node 594404c0735f0d460abdc10c!
Stack Trace: Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 331, in run
testMethod()
File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
self._testFunc()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
compatability.capture_type_error(s_func)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
func()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
func(test_case.state.get_state())
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/catalogs_tests.py", line 48, in test_catalogs
fail('Catalog {0} not found in node {1}!'.format(source,node.get('id')))
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
raise ASSERTION_ERROR(message)
AssertionError: Catalog dmi not found in node 594404c0735f0d460abdc10c!
Test Name: test_tag_create
Error Details: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-SYVBRiNdLaDZZiPOd2s84/6RKj8"', 'Date': 'Fri, 16 Jun 2017 16:20:46 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"9ed85674-f6be-45c7-abf3-a96248a5d280"}
Stack Trace: Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 331, in run
testMethod()
File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
self._testFunc()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
compatability.capture_type_error(s_func)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
func()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
func(test_case.state.get_state())
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/tags_tests.py", line 45, in test_tag_create
tagsWithRules = self.__create_tag_rule(n.get('id'))
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/tags_tests.py", line 26, in __create_tag_rule
Api().nodes_get_catalog_source_by_id(identifier=id,source='dmi')
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/apis/api_api.py", line 1862, in nodes_get_catalog_source_by_id
callback=params.get('callback'))
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 322, in call_api
response_type, auth_settings, callback)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 149, in __call_api
post_params=post_params, body=body)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 342, in request
headers=headers)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 184, in GET
query_params=query_params)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 177, in request
raise ApiException(http_resp=r)
ApiException: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-SYVBRiNdLaDZZiPOd2s84/6RKj8"', 'Date': 'Fri, 16 Jun 2017 16:20:46 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"9ed85674-f6be-45c7-abf3-a96248a5d280"}
Test Name: get_sku_nodes
Error Details: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-oJyzMzG4MzJjIqU+Yu1rsbNDJbo"', 'Date': 'Fri, 16 Jun 2017 16:21:00 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"1e67fced-2cfe-41bf-accb-dccc95761f42"}
Stack Trace: Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 331, in run
testMethod()
File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
self._testFunc()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
compatability.capture_type_error(s_func)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
func()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
func(test_case.state.get_state())
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/skupack_tests.py", line 148, in get_sku_nodes
Api().nodes_get_catalog_source_by_id(identifier=node_id,source='dmi')
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/apis/api_api.py", line 1862, in nodes_get_catalog_source_by_id
callback=params.get('callback'))
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 322, in call_api
response_type, auth_settings, callback)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 149, in __call_api
post_params=post_params, body=body)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 342, in request
headers=headers)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 184, in GET
query_params=query_params)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 177, in request
raise ApiException(http_resp=r)
ApiException: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-oJyzMzG4MzJjIqU+Yu1rsbNDJbo"', 'Date': 'Fri, 16 Jun 2017 16:21:00 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"1e67fced-2cfe-41bf-accb-dccc95761f42"}
Test Name: post_skupacks
Error Details: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-3MPN44E0/uZxHBH5aaPuu+WPglw"', 'Date': 'Fri, 16 Jun 2017 16:21:22 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"862647c4-095c-4260-abda-1e1d0bab5b8c"}
Stack Trace: Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/case.py", line 331, in run
testMethod()
File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
self._testFunc()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
compatability.capture_type_error(s_func)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
func()
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
func(test_case.state.get_state())
File "/home/jenkins/workspace/on-build-config/RackHD/test/tests/api/v2_0/sel_alert_poller_tests.py", line 54, in post_skupacks
Api().nodes_get_catalog_source_by_id(identifier=node_id, source='dmi')
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/apis/api_api.py", line 1862, in nodes_get_catalog_source_by_id
callback=params.get('callback'))
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 322, in call_api
response_type, auth_settings, callback)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 149, in __call_api
post_params=post_params, body=body)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/api_client.py", line 342, in request
headers=headers)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 184, in GET
query_params=query_params)
File "/home/jenkins/workspace/on-build-config/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/on_http_api2_0/rest.py", line 177, in request
raise ApiException(http_resp=r)
ApiException: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Length': '110', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"6e-3MPN44E0/uZxHBH5aaPuu+WPglw"', 'Date': 'Fri, 16 Jun 2017 16:21:22 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"No Catalogs Found for Source (dmi).","status":"404","UUID":"862647c4-095c-4260-abda-1e1d0bab5b8c"}

test this please

Test this please

BUILD on-build-config #489 : FAILURE

resubmitted in #228


Add random SparseArray2D builder

replace this bussines https://github.com/Dekken/statick/blob/master/inc/tick/array/sparse/array2d.hpp#L65

Props to https://github.com/andro2157


Release 0.0.1

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@25c5dab). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #17   +/-   ##
=======================================
  Coverage        ?   86.31%
  Complexity      ?       31
=======================================
  Files           ?        7
  Lines           ?       95
  Branches        ?        3
=======================================
  Hits            ?       82
  Misses          ?        9
  Partials        ?        4

Flag
Coverage Δ

unittests
86.31% <0.00%> (?)

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

Continue to review full report at Codecov.

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


Inconsistency between completeText and closeButtonTitle

While working on the documentation I have seen that some functions use the wording completeText while others use closeButtonTitle. I think that this is inconsistent and should be unified.
I can do the update if needed but I want to know what wording to pick.
In my opinion completeText seems the most appropriate, but if I had to pick I would be explicit that it is a button label and pick closeButtonLabel.
What do you think about it @hackua?

@frantzmiccoli does both do the same thing? Was it only to deprecate one in the future? If yes, we should add comments.

They do as far as I remember, one is just forwarded as the other into convenience functions.

@frantzmiccoli I agreed with @allaire, we should add a deprecation comment first, and once 1.5 is out we should refactor functions naming.

@vikmeup I also noticed that the objective-c version has a bit more feature. Do you think we should start backporting some? If so, which ones?

@vikmeup Yeah go ahead, I'll try to also clean some GH issues. Thanks


cannot remove stacked-git patch name

I'm using Powerlevel9K with oh-my-zsh with the following variables:
POWERLEVEL9K_MODE='awesome-fontconfig'
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(os_icon dir vcs newline time)
POWERLEVEL9K_OS_ICON_BACKGROUND="white"
POWERLEVEL9K_OS_ICON_FOREGROUND="blue"

POWERLEVEL9K_DISABLE_RPROMPT=true
RPROMPT="%{%}"

# Powerlevel9K VCS Settings
POWERLEVEL9K_VCS_HIDE_TAGS=true
POWERLEVEL9K_VCS_SHOW_SUBMODULE_DIRTY=false

In this setting, when I initialize stacked-git with stg init, I start seeing no patch applied appended to the branch name. Moreover, if I add a patch, I can see the last one's name again appended to the branch name. Here's the screenshot, before and after stg init:

and here's the other one after creating a patch:

I'd like to find out which part of the code adds it so that I can either turn it off on my fork and/or introduce a parameter that would control it.
Thanks a lot!

I got it! It's due to how vcs_info handles Quilt-like backends, e.g. mq, stgit. Here's a patch that moves the misc hooks to action hooks. It would be nice to have this and add a flag to display the patch information.
I'll close the issue for the moment, and later (after I fork it) will ask for a PR with patch information flag.

@yugoren - Thanks for the issue, and the recommended fix! I would really like to get a fix merged into mainline, whenever you have something ready =)


New histogram function classes

Implements:

A new histogram class CMSHistFunc, deriving from RooAbsReal.

Supports the existing vertical template morphing algorithms of FastVerticalInterpHistPdf2 and the horizontal morphing implemented in RooMorphingPdf (aka the Alex Read integral morphing). For the latter all templates on the horizontal grid are stored within the class (compared to RooMorphingPdf which would rely on external FastVerticalInterpHistPdf2 instances). The moment morphing algorithm is also supported.
Compared to RooMorphingPdf we cache as many parts of the morphing workflow as we can to achieve a significant speed-up: the intermediate CDFs of the input templates and the set of common CDF points to interpolate are stored as they do not depend on the morphing parameter.
The horizontal morphs of all the vertical morph Up/Down templates are performed first followed by  the vertical morphing. This is contrary to RooMorphingPdf which performed horizontal morphing on the vertical morphing results.
Saves the bin errors of the input TH1 for later Barlow-beeston uncertainty modelling.

A class CMSHistErrorPropagator, deriving from RooAbsReal . Acts as the sum of a set of CMSHistFuncs each multiplied by a RooRealVar coefficient.

Also sums the bin errors of each component in quadrature to give the total error.
Using this can create a set of RooRealVars that scale the summed bin contents according to this error. The user can set a bin error threshold below which each constituent process will receive an independent poisson uncertainty instead.
If provided with a vector of data values can perform Barlow-Beeston analytic minimisation for a significant speed up.
Can also calculate and apply fractions of the total bin shift that should be propagated to each individual CMSHistFunc component.

A class CMSHistFuncWrapper, deriving from RooAbsReal.

A CMSHistFuncWrapper is created from an existing CMSHistFunc and the corresponding CMSHistErrorPropagator. It evaluates to the template of the CMSHistFunc with bin contents scaled by the appropriate fraction of the total bin error as described above.
Thus the sum of all CMSHistFuncWrappers for a given channel would give the same expected events as provided by the CMSHistErrorPropagator directly, and is useful for the case that the user needs to evaluate specific background processes (e.g. post-fit plots). When fitting it is much faster to simply use CMSHistErrorPropagator to evaluate the total background.

All three of these classes have an OptimizedCachingPdfT implementation (CMSHistV) similar to the FastVerticalInterpHistPdf2 implementation.
text2workspace.py can build a RooRealSumPdf instead of a RooAbsPdf using the above classes. Enabled with the --new-hist X mode where X = 1 or 2. 1 implies the vertical morphing shape uncertainties change the process yield directly, whereas 2 is like the current behaviour in which the normalisation is treated separately as an asymmetric log-normal.

Still to-do:

[x] General clean-up of debug and logging code
[x] Clean-up text2workspace.py
[x] Should implement verbose checks using preprocessor statements
[x] Create b-only model by cloning s+b in text2workspace.py, like combine does it
[x] Add combine option to switch to analytic bb for minimize in cascade minimizer only (or all?)
[x] CMSHistFunc: should be able to skip prepareStorage() step if only loading one template
[x] Morphing features

[x] Restore option to not horizontally morph, but rather just pick the closest template
[x] ~Implement vertical,horizontal morph ordering in CMSHistFunc~ skipping for now
[x] Missing the multiplicative vertical template morphing
[x] Implement automatic rebinning after horizontal morphing
[x] Add (star-)moment morphing to CMSHistFunc if we can optimise it over official implementation. Standard MomentMorphing in one variable is implemented, leave star-morphing for later

[x] Check that new vectorisations actually do something (sqrt probably doesn't). Should be ok according to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51890.
[x] See if the analytic barlow-beeston can be faster (vectorized?). Now vectorized, not clear it's a whole lot faster though.
[x] Make a better version of the analytic barlow-beeston hack for the optimisation of the dirty flag propagation
[x] ~Decide how to handle cases where NLL gets a step-function as bin content goes to zero with bbb parameter.~ Not easy to solve, leave for now
[x] Have the option to mix current gaussian constraints for the total bin errors with poisson constraints for bins with small numbers of MC events.
[x] Validate that RooRealSumPdf works with parts of combine and other other scripts that expect RooAddPdfs. E.g. fit/yield/shape information from MaxLikelihoodFit.
[x] Should use the setActiveBins optimisation throughout, but need to check how this interacts with the cachingPdf
[x] Add support for negative bin contents (e.g. for modelling interference effects). Could be controlled by a flag in CMSHistFunc to not do the standard CropUnderflows. Should also check bin error propagation is done correctly. Bit complicated so leave this for the next round.
[x] Currently possible to have discrepancy between sum of CMSHistFuncWrappers and CMSHistErrorPropagator if a negative shift larger than the bin content is propagated to a single process. The wrapper will crop the underflow, whereas in the CMSHistErrorPropagator sum the subtraction is made on the total and no cropping may occur. Solve this for now by not cropping in the wrapper. As long as the user crops the sum of the wrappers, behaviour should be identical to CMSHistErrorPropagator.

@nucleosynthesis this now includes everything in #379, with a few modifications that allow us to completely remove any need for --new-hist-X options when running T2W. Also a couple of bug fixes for the general CMSHistFunc/BarlowBeeston implementation.
So the new commits need to go into the 81X branch, and we can probably merge this into 74X now.

I think you mean #377 right? If so, we can close that PR

Merged into 81x-root606-integration 0338e179889928bd5808a2786cc1e70b2172b52e
@ajgilbert please update instructions outlined here: https://cms-hcomb.gitbooks.io/combine/content/part2/bin-wise-stats.html  to match datacard directives


bug: Weird Scrollbar Appears on UI

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.1
Operating system/version
MacOS 14.6.1
Describe the bug

This weird scrollbar keeps randomly appearing on the UI.
Once it shows up, it doesn't go away.
When I quit NeoVim and reopen, it goes away but it appears again shortly.
This seems like it has something to do with the dialog box of the API doc (Shift + K shows these dialog boxes).
Steps To Reproduce

Open a TypeScript file with Neovim.
Start writing some code.
View the API doc of a certain API by placing the cursor over it and press Shift + K.

Expected Behavior
The weird scrollbar shouldn't appear on the UI.
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "LazyVim/LazyVim", import = "lazyvim.plugins" },
    -- add any other plugins here
  },
})

Disable noice.nvim and if that solves your problem, then create an issue at noice.nvim Github repo with your findings. Never seen this before.

@dpetka2001
I tried disabling noice.nvim and it seems the problem went away. Will create an issue at noice.nvim instead.
Thank you very much.


using scripts/retrain.py how to proceed?

I have a naive question. I followed the Google Collab tutorial for transfer learning on images of 5 categories of flowers. However, how can I do the same for the images of hands from egohands? What are the changes I should perform?
mona@Mona:~/code/handpose/handtracking$ IMAGE_SIZE=224
mona@Mona:~/code/handpose/handtracking$ ARCHITECTURE="mobilenet_0.50_${IMAGE_SIZE}"
mona@Mona:~/code/handpose/handtracking$ python -m scripts.retrain   --bottleneck_dir=tf_files/bottlenecks   --how_many_training_steps=500   --model_dir=tf_files/models/   --summaries_dir=tf_files/training_summaries/"${ARCHITECTURE}"   --output_graph=tf_files/retrained_graph.pb   --output_labels=tf_files/retrained_labels.txt   --architecture="${ARCHITECTURE}"   --image_dir=images/train
/home/mona/anaconda3/lib/python3.6/site-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
>> Downloading mobilenet_v1_0.50_224_frozen.tgz 100.1%
--- Logging error ---
Traceback (most recent call last):
  File "/home/mona/anaconda3/lib/python3.6/logging/__init__.py", line 992, in emit
    msg = self.format(record)
  File "/home/mona/anaconda3/lib/python3.6/logging/__init__.py", line 838, in format
    return fmt.format(record)
  File "/home/mona/anaconda3/lib/python3.6/logging/__init__.py", line 575, in format
    record.message = record.getMessage()
  File "/home/mona/anaconda3/lib/python3.6/logging/__init__.py", line 338, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  File "/home/mona/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/mona/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/mona/code/handpose/handtracking/scripts/retrain.py", line 1326, in <module>
    tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
  File "/home/mona/anaconda3/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 126, in run
    _sys.exit(main(argv))
  File "/home/mona/code/handpose/handtracking/scripts/retrain.py", line 982, in main
    maybe_download_and_extract(model_info['data_url'])
  File "/home/mona/code/handpose/handtracking/scripts/retrain.py", line 339, in maybe_download_and_extract
    'bytes.')
  File "/home/mona/anaconda3/lib/python3.6/site-packages/tensorflow/python/platform/tf_logging.py", line 116, in info
    _get_logger().info(msg, *args, **kwargs)
Message: 'Successfully downloaded'
Arguments: ('mobilenet_v1_0.50_224_frozen.tgz', 6308169, 'bytes.')
ERROR:tensorflow:No valid folders of images found at images/train

It does seem I am not the only one who is needing help with this based on other git issues. Some guidance is really appreciated.

Hi Mona,
Transfer learning for image classification and object detection tasks differ. It seems the flower tutorial you refer to is a classic image classification task, while the hand tracking is an object identification task. I found the stanford cs231n course helpful in building an understanding of these tasks.

Now, regarding training, the work here heavily depends on the Tensorflow Object Detection Api and assumes the reader is familiar with the api. I would suggest running the api code and understanding it.
I also provide provide reference to tutorials I used/followed to do my own "transfer learning". Please see issue #18
Goodluck!
-V.


Common troubleshooting information

Create a common Troubleshooting/Uninstall markdown file.  Include details on how to uninstall our automation, and how to troubleshoot.
Symlink the markdown file into the files directory of all of our boms
Edit the readme for each of the boms/packages to reference the troubleshooting markdown file
publish changes for all impacted boms/solutions

In the automation solutions repo I created a common software Troubleshooting Guide: https://github.com/cloud-native-toolkit/automation-solutions/blob/main/boms/software/_common/TROUBLESHOOTING.md
I’ve symlinked this into the cp4d, datafabric, integration, maximo and turbonomic folders (in the files directory), and added to the readme for each of them, so that this common troubleshooting guide will be included with all of our automation packages when they are generated.
This includes common uninstallation steps, plus details common error cases like Resources stuck in Terminating state,  Variables may not be used here, invalid credentials, among others.  This lets us define the steps/fixes/workarounds in one place, and it will be applied to all solutions.
I did not publish any of the generated output yet.  I’ll let the owners of each of those solutions generate at their own pace


sql migration extension version bump 0.1.14

bump sql-migration version to 0.1.14

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.253%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14802

Relevant Lines:
29124

💛  - Coveralls


Crashes when file system is updated

QS quits several times a day, usually after downloading an item or making some other change to the file system. Looks like some kind of race condition or failure to respond properly to a file system change notification.
I'm running 10.15.7 but this has been happening for a very long time, like more than a year, and since at least one macOS upgrade.

What version of Quicksilver are you running? There was a version that crashed every time it checked for updates (which prevented a lot of people from ever seeing those updates). The current version is 1.6.1.

What version of Quicksilver are you running? There was a version that crashed every time it checked for updates (which prevented a lot of people from ever seeing those updates). The current version is 1.6.1.

1.6.1 (4026)

1.6.1 (4026)

I can find the ones you submitted if you tell me the name of your computer (in System Preferences → Sharing).

I can find the ones you submitted if you tell me the name of your computer (in System Preferences → Sharing).

It's "bebop".

It's "bebop".

I finally got a chance to review those crash reports. They’re all for the same reason:
Thread 5 Crashed:: Dispatch queue: QSCatalogEntry scanQueue: QSPresetDownloads

So any time something changes in your Downloads folder, Quicksilver rescans it and crashes. It’s probably from the same file each time.
If you’re willing, some detective work would help me out.

Move all of the files out of your Downloads folder to a temporary location.
Add them back one at a time until Quicksilver crashes. (It should be picking up the changes as they happen in that folder, so there should be no need to rescan manually, wait 10 minutes, etc.)
Once you’ve identified the file, if it doesn’t contain anything private, could you share it with me so I can try to reproduce and fix the crash?

Thanks.

Thanks for looking into this.
I have over 300 files in Downloads, so I moved them all out and moved them back with a bash loop, printing names, moving files back to ~/Downloads, and sleeping 1 sec between. As soon as QS crashed, I moved the dozen most recently moved files/dirs out of ~/Downloads again and reran the loop with a longer sleep. Unfortunately, it didn't crash again.
I was thinking it might have to do a delay after moving a directory while QS processed the files within, so that the crash isn't immediate. After experimenting with some subdirectories, I was able to get QS to crash twice more, but I've failed to find anything repeatable. Anyway, I spent like an hour on this and haven't found the smoking gun.
I'd be willing to run it with more verbose logging or in a debugger if that's possible.
-Rich

On Feb 11, 2021, at 6:58 PM, Rob McBroom<EMAIL_ADDRESS>wrote:
I finally got a chance to review those crash reports. They’re all for the same reason:
Thread 5 Crashed:: Dispatch queue: QSCatalogEntry scanQueue: QSPresetDownloads
So any time something changes in your Downloads folder, Quicksilver rescans it and crashes. It’s probably from the same file each time.
If you’re willing, some detective work would help me out.
Move all of the files out of your Downloads folder to a temporary location.
Add them back one at a time until Quicksilver crashes. (It should be picking up the changes as they happen in that folder, so there should be no need to rescan manually, wait 10 minutes, etc.)
Once you’ve identified the file, if it doesn’t contain anything private, could you share it with me so I can try to reproduce and fix the crash?
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/quicksilver/Quicksilver/issues/2550#issuecomment-777937254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA25CHVEOIBK4XQ7XXZVVBDS6SKL7ANCNFSM4WTYGAWQ.

We can’t build with Xcode 9 any more and if I gave you a build from Xcode 12, it would probably crash in a dozen other ways so I won’t be able to do that until things are cleaned up.

I've apparently solved the problem by moving most of the files in my Downloads directory elsewhere. The problem has not occurred since. Thanks, though, for following up.
-Rich

On May 4, 2021, at 6:24 PM, Rob McBroom @.***> wrote:
We can’t build with Xcode 9 any more and if I gave you a build from Xcode 12, it would probably crash in a dozen other ways so I won’t be able to do that until things are cleaned up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/quicksilver/Quicksilver/issues/2550#issuecomment-832356614, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA25CHWZTMAUW56WFTWU5ULTMCM6HANCNFSM4WTYGAWQ.


Upgrade cluster will benefit from generic cluster upgrade description

This is a Feature Request
What would you like to be added
Do a high-level description of how to upgrade the cluster.
Such as:

upgrade etcd
upgrade masters
upgrade workers with keeping in mind that workloads can go down

Why is this needed
Lots of people use manual installations and do not use tools/scripts that are described in the doc.
Comments
I plan to send a simple pull request for the documentation.

/triage feature

/priority backlog
/kind feature


[zh-cn] sync persistent-volumes configure-liveness-readiness-startup-probes patch-releases

# Changes to be committed:
#       modified:   content/zh-cn/docs/concepts/storage/persistent-volumes.md
#       modified:   content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
#       modified:   content/zh-cn/releases/patch-releases.md

/lgtm

/approve


http://localhost:1337/kong gives Failed to load resource: the server responded with a status of 400 (Bad Request)

Hi there,
I'm getting up and running using docker, kong, and konga. I'm unable to create a connection (clicking the button does nothing, after providing field data). Nothing logged to the console, but it does show this:

Here is my docker-compose file:
version: '2.1'

services:

  consul:
    image: progrium/consul:latest
    command: -server -bootstrap -ui-dir /ui
    healthcheck:
      test: ["CMD-SHELL", "curl -I -s -L http://<IP_ADDRESS>:8500 || exit 1"]
      interval: 5s
      retries: 10
    networks:
      - kong
    ports:
      - 8500:8500
    expose:
      - 53
      - 8300
      - 8301
      - 8302
      - 8400
      - 8500
    dns:
      - <IP_ADDRESS>

  nginx-lb:
    build: nginx/
    depends_on:
      consul:
        condition: service_healthy
    networks:
      - kong
    ports:
      - 8000:8000
      - 8443:8443
      - 8001:8001
      - 8444:8444
    expose:
      - 8000
      - 8443
      - 8001
      - 8444
    links:
      - consul:consul
    command: >
        /bin/containerpilot
        -config file:///etc/containerpilot/containerpilot.json
        nginx -g "daemon off;"

  kong-database:
    image: postgres:9.5
    environment:
      - POSTGRES_USER=kong
      - POSTGRES_DB=kong
    networks:
      - kong
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "postgres"]
      interval: 10s
      timeout: 5s
      retries: 5
    ports:
      - 5432:5432

  kong-migration:
    image: kong
    depends_on:
      kong-database:
        condition: service_healthy
    networks:
      - kong
    environment:
      - KONG_DATABASE=postgres
      - KONG_PG_HOST=kong-database
    command: kong migrations up

  kong:
    build: kong/
    depends_on:
      kong-database:
        condition: service_healthy
      kong-migration:
        condition: service_started
    environment:
      - KONG_DATABASE=postgres
      - KONG_PG_HOST=kong-database
      - KONG_PG_DATABASE=kong
      - KONG_ADMIN_LISTEN=<IP_ADDRESS>:8001
    networks:
      - kong
    expose:
      - 8000
      - 8001
      - 8443
      - 8444
    healthcheck:
      test: ["CMD-SHELL", "curl -I -s -L http://<IP_ADDRESS>:8000 || exit 1"]
      interval: 5s
      retries: 10

  konga:
    image: pantsel/konga
    depends_on:
      kong-database:
        condition: service_healthy
    environment:
      - DB_ADAPTER=postgres
      - DB_HOST=kong-database
      - DB_PORT=5432
      - DB_USER=kong
      # - DB_PASSWORD=your-db-password" \ // Omit if not relevant
      - DB_DATABASE=kong
      - NODE_ENV=development
    networks:
      - kong
    expose:
      - 1337
    ports:
      - 1337:1337

networks:

  kong:
    # external: true

Any ideas what might be happening?
Thanks for what looks like a very cool project.

@mateodelnorte.
is there a chance you've previously been logged in Konga?
Have you tried loggin out and in again?

Closing this due to innactivity


Missing breakage/states properties - matching, traces and diagram not displayed on map -

Hi,
I'm trying to use the matching inspection tool. The GPX data is matched, but the diagram, traces and matchings aren't displayed on the map -  I always get an "Uncaught TypeError: Cannot read property 'states' of undefined"/"Uncaught TypeError: Cannot read property 'breakage' of undefined" error at matching.js line 22 / osrm.matching.js line 2502.
matching.js/osrm.matching.js

function onMatched(response) {
  var states = response.debug.states,
      breakage = response.debug.breakage,
      matchings = response.matchings,
      trace = response.trace;
...

This is the response:
Object
	matchings: Array[1]
		0: Object
			confidence: 0.951211
			geometry: "ot|}c@bkzx{DxbAdc@ztAdk@hWzJdt@h]rt@`Y~^jQxl@nUzyBt_AhkBxv@rjBjw@LVqN`V}fBmv@glBox@jKaVlCyG{cBqs@kToLwmAcf@khB_w@wmBmx@mgAgd@yEsBoeAqd@udAed@gxAam@agAcf@{cAcd@c~@w_@e|@m`@sqB}z@gAi@"
			indices: Array[4]
			matched_points: Array[4]
			__proto__: Object
		length: 1
		__proto__: Array[0]
	trace: Object
		classify: true
		coordinates: Array[4]
		__proto__: Object
	__proto__: Object
		__defineGetter__: function __defineGetter__() { [native code] }
		__defineSetter__: function __defineSetter__() { [native code] }
		__lookupGetter__: function __lookupGetter__() { [native code] }
		__lookupSetter__: function __lookupSetter__() { [native code] }
		constructor: function Object() { [native code] }
		hasOwnProperty: function hasOwnProperty() { [native code] }
		isPrototypeOf: function isPrototypeOf() { [native code] }
		propertyIsEnumerable: function propertyIsEnumerable() { [native code] }
		toLocaleString: function toLocaleString() { [native code] }
		toString: function toString() { [native code] }
		valueOf: function valueOf() { [native code] }
		get __proto__: function __proto__() { [native code] }
		set __proto__: function __proto__() { [native code] }

greetings, Sabine

These parameters are only exposed in a version of OSRM that is compiled with debug support.
(assuming your are on a Linux based system)
You need to compile https://github.com/Project-OSRM/osrm-backend from source and run cmake with cmake -DENABLE_JSON_LOGGING=1 .. and install make && sudo make install.
After that you can compile node-osrm from source:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
npm install osrm --from-source

Perfect, thanks!


PlaceHolder and 'selection-change' event?

Is there a way to add a placeholder text to the editor, and also is there a way to listen to the 'selection-change' event?

I'll add a callback for the selection-change event pretty soon.
I'll think about providing a placeholder prop for the editor, but in the mean time I can think of a few things that you could do:

Override the editor element in a custom component to provide a placeholder-ed component instead. The core functionality has been split over into ReactQuill.Mixin but you could just as well copy-paste the whole Component implementation into your sources and edit it as you please.

Or maybe use the css :empty selector to display a ::before pseudo-element with your placeholder text as content. I think this could fail though, unless the editor has zero content at all.

Any ETA on the selection-change event?

Latest version introduces onChangeSelection, which should be what you need.
I'm still interested in the placeholder feature though. Could you open another issue for that?


JWS-1462 fix

Edited the script for configuring tls connections with specified certificates. (JWS-1462)

I tested it and It's working. You can merge it.


Add round(Decimal, Integer) Presto function

Modify Round function to handle round(DECIMAL) and round(DECIMAL, INTEGER) (roundN) signatures.
Currently there isn't a way to register a function name with an array of function objects. We can register a function name with a vector of signatures, but only one function object can be mapped to a name.
For this reason, we need to resolve at runtime within class Round::apply() method.
Added unit tests for roundN function.

Hi @karteekmurthys. Is the PR ready to test? I tried applying this patch locally but queries with round still fail with this issue. Do you know if there is anything else required for the fix? Thanks.

Hi @karteekmurthys. Is the PR ready to test? I tried applying this patch locally but queries with round still fail with this issue. Do you know if there is anything else required for the fix? Thanks.

I'm working on a fix. I will update the pr soon.

There is an unresolved comment here https://github.com/facebookincubator/velox/pull/4776#discussion_r1190593579

@Yuhta Can you please help review this? Thanks.

@mbasmanova  @Yuhta would you please review this?


how to install plugins

I cannot find a way to install plugins

https://github.com/rxi/lite/blob/master/doc/usage.md#plugins


Remove (or stub) HACK_NO_XPCALL

There is no longer a reason to stub out xpcall now that it supports yielding. We can leave this method while we migrate consumers, but make it do nothing.

Closed by #88 (updated CHANGELOG in #91)


Support for PHP8

Please make bundle installable on PHP8 runtime.
Most of the time it's good enough to add ||^8.0 to the composer.json. But list of breaking changes should be checked, obviously.

Added in #89 🎉


Fragalysis download issues and tests failing.

TestFragalysisDownload::test_sdfs_pdbs_fragalysis_download - zipfile.BadZipFile: Bad magic number for file header
According to @apayne97 and @kamin the issue appears to be with the smiles.smi file that comes with the download.
if the  "smiles_info" key is set to False everything works fine.

I don't think this needs to be a Milestone issue - currently it seems to be working but we have no idea yet how to track the issue

Perhaps we can use a retry and a timeout. @ijpulidos pointed out that this is an important indicator of whether the data is actually downloadable.

This seems to have settled down, and regardless I think the tests are currently XFAILED.


Why not RequestParams.put() method not support  boolean value but not throw Error？

Why not RequestParams.put() method not support  boolean value but not throw Error？
the loopj version I used is 1.4.4
when I use looj post http request,I need post many params.One time I use requestParams.put(String,boolean)，Eclipse never throw any code error,but when I Log.i(TAG,requestParams.toString()),the boolean values's params never be contains.I want to know why?

please test with 1.4.6, we don't support old versions

OK.


cleanStatement affects the query behavior

Describe the bug
Trying to use the recent version of the plugin that uses better-sqlite3-multiple-ciphers gives me a unexpected behavior on UtilsSQLite.queryAll function.
Before the cleanStatement call, my query is:
SELECT * FROM "sqlite_master" WHERE "type" = 'table' AND "name" = 'migrations'

but the function replaces " with ', resulting on:
SELECT * FROM 'sqlite_master' WHERE 'type' = 'table' AND 'name' = 'migrations'

This results on an unexpect behavior, since the "cleaned" query returns nothing on my db, while the first returns the correct record of the table migrations.
Expected behavior
I expect that the cleanStatement function doesn't affect the result of the query.
Additional context

sqlite_version(): 3.41.0

Duplicated of #451. Sorry for that.

@Guiqft i will come soon with a fix i am in final testing


⚠ Bofrost.com has degraded performance

In 67e31c8, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1169 ms

Resolved: Bofrost.com performance has improved in 27680b6 after 6 minutes.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: pankajkumishra sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


chore fix ubuntu package conflict by skipping apt upgrade in build-thirdparty workflow

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[x] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments

skip unnecessary apt upgrade command in build-thirdparty workflow to avoid package conflicts in Ubuntu
(https://github.com/apache/doris/actions/runs/4171352643/jobs/7221214733#step:4:283)

Unpacking odbcinst1debian2:amd64 (2.3.11) ...
dpkg: error processing archive /tmp/apt-dpkg-install-SY6NPA/43-odbcinst1debian2_2.3.11_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libodbcinst.so.2.0.0', which is also in package libodbcinst2:amd64 2.3.9-5
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

the previous  command apt update has guaranteed that the latested version of packages and their dependencies will be installed in the following apt install

This problem is encountered when I am doing another PR (https://github.com/apache/doris/pull/16736), which brings no dependency change bug failed in Build Third Party Libraries (Linux) job.

cc @adonis0147

Hi, kind ping to @adonis0147 again. I have force pushed to trigger the CI again to pass the P0 Rregression. Nothing new changed.


[azeventhubs] Relinquish ownership of partitions when the Processor is shut down

As an optimization we can relinquish ownership of partitions when the Processor.Run is stoppped, which makes them immediately available.
Fixes #21868

/azp run go - azeventhubs


Settings handling need rework

Settings loading and saving need more error checking, and handling of value not previously present in the settings file.

Actually, it should switch to a fully GameDatabase compliant system.


Doubts about OKVS: Why not deal with the submatrix A D E of matrix T?

In the page-6 of the RR22 paper, here is a statement: "Since all of  T^* is lower triangular, we can compute P^*".  Therefore, we have completed the solution of vector P and the encoding process of OKVS.
But I am very puzzled about this. In T^* we did not explicitly handle submatrix A^*, D,E . Why can we simply say that T^* is a lower triangular matrix? If these submatrixes (A^*, D,E) are not lower triangular matrices, it seems that we cannot solve vector P through back-substitution?

A* doesn't matter. It can be anything. What matters is that B* and F are lower triangular.
The positions corresponding to A* can be set to anything, e.g. 0. What's left is the system
B* 0
E   F
The first row of B* has not dependencies and so you can simple set it to the value you want. The next row might depend on the previous but no others. So set that according. This is just back substitution...

Thank you for your prompt response. I understand your explanation.
If we focus only on the system:
B^* 0
E   F

we can easily solve for the corresponding values in the vector 𝑃 using back substitution.
However, this system only has $\hat m + \delta$ columns.
Since the size of the vector 𝑃 is 𝑚 and obviously $m > \hat m + \delta$  , how should we solve for the remaining values in 𝑃 (specifically, the $m-\hat m - \delta$   values )?

yes, the positions of p that you don't actually use can just be 0. So p might be 20% zeros.

Thanks very much. I totally understand this problem.


kubectl gs template commands should not print .status

The manifests produced by kubectl gs template subcommands are meant to be used with kubectl apply and therefore should not contain any .status content, to avoid confusing users.

team rocket will not work on this. Feel free to reopen if still needed.


generic quantiles sketch

Coverage decreased (-1.6%) to 97.041% when pulling cc66f6ea0b5b24bec1edb44812d4f431737573ac on generic-quantiles-sketch into ee0e6b806ad7d2d52daac5348021c6baadc6320f on master.


Support various number of buttons in modal

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Being able to add more than two buttons into a modus-modals would be great.

I(t would also be helpful to have the option to only have one button in the modal.

Motivation and context
No response
Which npm package?
@trimble-oss/modus-web-components
Priority
Medium
What is the product name the feature is requested for?
Trimble Creator
What is the team name the product belongs to?
Nexus
What is the division name the team belongs to?
Construction

cc @davidtsilcock
For additional information, https://docs.google.com/document/d/1e3ilHfEdIDAm4s4811iLnF-4H2RTyIHKQrRMF8p74RQ/edit#heading=h.lf66jh7nizs8

@davidtsilcock looks like we can have a single button. Can you please check with your dev team on that?

@enowak1031 @egunther39 @coliff @soniakaukonen
we need to decide if we should support more than two modal buttons and the coloring of the buttons as shown in the screenshot above.

@msankaran0712 @enowak1031 - something worth informing the Tiger team?

@msankaran0712 Agreed about the button placement. We'll adjust these when we convert our current modals to web components.
@soniakaukonen I have sent a message to Eric regarding this. He will bring it up, along with https://github.com/trimble-oss/modus-web-components/issues/1305 in the tiger team meeting tomorrow.

@davidtsilcock will your team be able to contribute?

Yep, we should be able to! I've added it to our JIRA board so it'll be discussed in the next grooming session early next week.

This is to reaffirm that the Modus has approved the functionality with a revision https://github.com/trimble-oss/modus-web-components/issues/1304#issuecomment-1573842398.
cc @davidtsilcock

Yup, a fair revision. Have folded that into our spec. Our story outlining the changes can be found here https://jira.trimble.tools/browse/CREATOR-1957. When this story is done, we will contribute it back to Modus.

hey @davidtsilcock just an update, @egunther39 @soniakaukonen confirmed me that the Modal can accept three buttons in the order from left to right -> outline, secondary, primary

It can accept it currently? Or is that how you'd want us to contribute it back.

hey @davidtsilcock That functionality is not available on the component yet, it will be part of the contribution.

hey @davidtsilcock We now support custom footer for Modals, it was added from this PR https://github.com/trimble-oss/modus-web-components/issues/1728. This means you can have three buttons in the Modal as long as it follows the recommended button progressions.


Vulnerability is not detected using Gradle plugin

Describe the bug
There is different behavior of dependency check Gradle plugin and CLI tool.
It is related to this CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-26520
The CVE is reported to configuration cpe:2.3:a:postgresql:pgjdbc:42.3.2:-:*:*:*:*:*:* but Gradle artifact is org.postgresql:postgresql:42.3.2.
When running dependency check from Gradle plugin, there is no vulnerability detected as artifact names differ.
But when running dependency check from CLI, there is detected vulnerability because it knows from some evidence that the product can be called pgjdbc.
Version of dependency-check used
The problem occurs using version 7.0.1 of the CLI and Gradle plugin.
Log file
cli.txt
gradle.txt
To Reproduce
Steps to reproduce the behavior:

Create simple project with vulnerable org.postgresql:postgresql:42.3.2
Run dependency check analysis using Gradle plugin
There is no detected vulnerability

Expected behavior
Vulnerable org.postgresql:postgresql:42.3.2 will be detected even using dependency check Gradle plugin.

As you can read in the description this CVE is  disputed ; are you sure that it is in the vulnerability data that you have? because of this status it is probably ignored

The general problem here is that CLI returns different results than Gradle plugin.
I ran CLI and Gradle plugin checks at the same time with the same project and the CLI detected the vulnerability but the Gradle plugin did not. That cannot be a problem of vulnerability status.

Incomplete fix for #4085 will be fixed with #4270.


missing changelog

Is there a changelog for this module? I coudn't find it.

@dutu not anymore. All changes are made via pull requests and I try to keep them descriptive of what changed, you can see a full history here:
https://github.com/tiagosiebler/binance/pulls?q=is%3Apr+is%3Aclosed
Something more granular would be the commit history but that's likely too granular.

I see, It would be at least good to mark when the package version changes.
Now it's difficult to figure out what changes were introduced and when. (Le't say I upgrade from "2.8.13" - it's not straightforward to figure out what PRs have meen merged since this version).

I see, It would be at least good to mark when the package version changes. Now it's difficult to figure out what changes were introduced and when. (Le't say I upgrade from "2.8.13" - it's not straightforward to figure out what PRs have meen merged since this version).

That's a very good point I seem to have neglected, thank you for that. Take another look at the closed pull requests link. I've done a quick edit to include version numbers in the PR title. If a PR does not have a version number in the title, the change was included in the next release (the next PR with a version number).
I'll make a better habit to ensure PRs include version numbers. Generally speaking, for most minor changes/fixes/improvements, these are made as patch releases (2.8.13 -> 2.8.14). If there are bigger changes, but they're still expected to be backwards compatible, I tend to make a minor release (2.8.13 -> 2.9.0).
For major changes that either could be or definitely are breaking changes to anyone using the SDK (and/or introduce a potentially different behaviour), I always make a major release (2.8.13 -> 3.0.0). That way this sets expectations on how careful any testing should be for anyone upgrading to the latest version and should avoid any surprises. It doesn't happen often, as I try to avoid breaking changes (and eventually bundle them all into one major release), but sometimes it does make sense to introduce bigger changes of this kind. Hopefully this helps.
If you haven't already, I also recommend joining the telegram community I made for like minded dev/traders:
https://t.me/nodetraders

Thanks for the quick response and resolution!
I see you are adhering to Semantic Versioning which is great!

I see you are adhering to Semantic Versioning which is great!

Approximately 😅 patch releases occasionally see improvements (not just fixes), but usually nothing major and definitely nothing breaking


Updated init scripts for AiiDA Lab

Updates needed to comply with new configuration in the AiiDA Lab Docker stack chain of Dockerfiles.

@sirikal Can we merge this? Seems to build fine now.


05/team

Created the Team section and the Team.data.js file.
The images int he Team.data.js file are just for testing purposes, I'm afraid the imageSrc property will be invalid in a few days because it's served with a token from the LinkedIn's CDN (hence the big URL). I'm also going to need help with the special cases of team members that don't have a LinkedIn profile nor a picture.

Ok this looks good, but:

sort people by their role, so leads first and then the other roles
make all the photos much bigger
store photos in an assets folder rather than using the linkedin link
If someone doesn't have a linkedin profile, then don't link to anything. If they don't have a photo, i'll give you one
Do not use the #opentowork photo from linkedin


Gallery, Tabs: Jumping tab body when swiping right

Open gallery, tap Tabs and scrolling, scroll the contents up, then swipe to the right.
Expected: smooth transition into the new tab body.
Actual: tab transitions to the Right, and then jumps the tab contents.

What's going on here is the demo app scrolling the new TabBarView to that it's scroll offset matches the tab you're coming from.  This is because the app bar's height depends on the scroll offset and we don't want the app bar to change size when you switch tabs.
In the short term the simplest fix for this is to change the app bar's behavior to not scroll.
Once #4430 lands we'll revise the appbar logic that causes the problem.


Expose info  kwarg in experiment.run

This fixes #480, by simply adding an info kwarg to  sacred.Experiment.run which is later used to update the run's info dict.
Needs some tests.

I think with some tests that would be fine, though we should think about a more principled way to add tags to experiments anyway.

What did you have in mind? Putting them in run.info['tags'] seems like an appropriate solution for the time-being to me. This is part of a much larger conversation, but imo sacred is currently "too opioniated" and we should try to be agnostic going forward.

I remember some earlier discussions about tagging, but anyway. You would need to resolve the merge conflicts before I can do anything.

Are the failing tests broken? They look unrelated to this to me.

Yes, it seems like the run_example tests sometimes fail to correctly handle the -l WARNING flags. Interestingly this only happens on test-servers and never on my machine, which is always a bad sign.
But in any case this has nothing to do with your PR which looks good to me.
Regarding tags: Is there a specific reason you do not want to put them in meta_info instead?

Regarding tags: Is there a specific reason you do not want to put them in meta_info instead?

Nope, arbitrary decision. I think it would make sense to put tags in meta_info.  IIRC I also had some other things that needed to be passed around and wanted to put them in info.

The -l WARNING seems to now fail consistently and also on my machine. I also cannot see how this PR relates to the test, but we should either fix the issue or silence the tests, as tests that fail by default counteract the purpose of a CI.

@JarnoRFB I found the bug. Tests should be back up and running now.


'[skip ci] [RN][JS] BridgelessUIManager: Finish sendAccessibilityEvent

Summary: Changelog: [Internal]
Reviewed By: dmytrorykun
Differential Revision: D52383282

7effa2527f71b00c7dc211f04aac41509249b266


[Feature]: Print error.cause

🚀 Feature Proposal
The proposal for error.cause is currently stage 3. This proposal is to support jest printing chains of cause properties if they are present on errors.
Motivation
Nested errors can be critical to debugging. JSON.parse might throw a syntax error when reading a file. But if the filename isn't hardcoded in the stack from that called JSON.parse, a developer debugging would have no idea which particular file could not be parsed. The solution is to support chains of causally related errors: as errors bubble up through layers of code they can be caught and rethrown as a cause, allowing additional information to be captured.
Example
Imagine the application contains this code
const readJson = (path) => {
  try {
    const json = JSON.parse(fs.readFileSync(path));
  } catch (e) {
    throw new Error(`Failed to parse JSON from ${path}`, {cause: e});
  }
}

If the application throws during testing complete information is available about the problem. The code throws an error with a cause property defined, per the spec. The cause contains critical information about what the error is, but if jest does not opt in to printing it that information is only present in interactive environments for those who know to look for it. Currently jest would print
Error: Failed to parse JSON from 'path/to/file'.
  at readJson:5

If this feature is implemented jest would print:
Error: Failed to parse JSON from 'path/to/file'.
  at readJson:5
Caused by: SyntaxError: Unexpected token u in JSON at position 0
  at JSON.parse (<anonymous>)
  at readJson:3

Pitch
Jest has the ability to bring the improved debuggability that this proposal creates to a large audience. It is relevant and stable enough for inclusion.

OK I've now got a proper AST for errors and printing based on traversal with a visitor. This lays the groundwork for me to offer  base printing behavior while ensuring it is still possible for the end user to override any part of the printing as they see fit. This is great as it means the project can offer several extensible printers, for example a colored terminal printer with chalk, an html printer, and even (eventually) a React component hierarchy which could support some very rich functionality indeed.
I have 100% test coverage, but my plan is to test the whole thing out by finishing the integration with jest and hopefully getting some review here.

On second though though maybe Babel isn't as much of an analog as I'm imagining. It's plugin system definitely is ast->ast, so their printing code is never mixed with anything else. Essentially they do a complete pass of the AST for plugins to do transformations, then do a single complete pass to print. I'm talking about doing a pass that mixes different kinds of printing visitors. I think I just need to start building and see what happens.

If you're after encouragement I'm super excited about this direction 😃 But I do not have any comment about the implementation up until any integration with Jest starts to materialize. I have faith in this improving errors for our users though, which is essentially one of our strongest value propositions

I'll always take encouragement! I should have the integration ready pretty soon.

Here's what I've got. Don't pay too much attention to the specific formatting, as I was mostly just testing whether I could apply formatting.
Here is the content of test/integration/test.js:
const { relative } = require('path');
const { ChalkPrintVisitorMixin } = require('@stack-tools/chalk-tools');
const {
  parseErrors,
  cleanErrors,
  PrintVisitor: V8PrintVisitor,
} = require('@stack-tools/node-tools');

const PrintVisitor = class extends ChalkPrintVisitorMixin(V8PrintVisitor) {
  PathLocator(locator) {
    if (locator.path.startsWith('/')) {
      locator.path = relative(process.cwd(), locator.path);
    }
    return super.PathLocator(locator);
  }
};

function doStuff() {
  throw new Error('Uh oh');
}

try {
  doStuff();
} catch (e) {
  process.stdout.write(`${PrintVisitor.visit(cleanErrors(parseErrors(e)))}\n\n`);
}

Actually I'm not even sure I really want a chalk package, since it's not clear what formatting I would put in there. Without that package the code for that example looks like this:
const { relative } = require('path');
const { magenta, white } = require('chalk');
const {
  parseErrors,
  cleanErrors,
  PrintVisitor: V8PrintVisitor,
} = require('@stack-tools/node-tools');

const PrintVisitor = class extends V8PrintVisitor {
  ErrorChain(errors) {
    return magenta`${super.ErrorChain(errors)}`;
  }

  Error(error) {
    return magenta`${super.Error(error)}`;
  }

  ErrorName(name) {
    return magenta.bold`${super.ErrorName(name)}`;
  }

  ErrorMessage(emssage) {
    return white.bold`${super.ErrorMessage(emssage)}`;
  }

  Site(site) {
    return white.underline`${super.Site(site)}`;
  }

  Call(call) {
    return white`${super.Call(call)}`;
  }

  Frame(frame) {
    return super.Frame(frame).replace(/^ {2}/, '');
  }

  PathLocator(locator) {
    if (locator.path.startsWith('/')) {
      locator.path = relative(process.cwd(), locator.path);
    }
    return super.PathLocator(locator);
  }
};

function doStuff() {
  throw new Error('Uh oh');
}

try {
  doStuff();
} catch (e) {
  process.stdout.write(`${PrintVisitor.visit(cleanErrors(parseErrors(e)))}\n\n`);
}

OK one more try with everything:

const { relative } = require('path');
const { magenta, white, reset } = require('chalk');
const {
  parseErrors,
  cleanErrors,
  PrintVisitor: V8PrintVisitor,
} = require('@stack-tools/node-tools');

const PrintVisitor = class extends V8PrintVisitor {
  ErrorChain(errors) {
    return magenta.bold`${super.ErrorChain(errors)}`;
  }

  Error(error) {
    return magenta.bold`${super.Error(error)}`;
  }

  ErrorMessage(emssage) {
    return white`${super.ErrorMessage(emssage)}`;
  }

  Site(site) {
    return white.underline`${super.Site(site)}`;
  }

  Call(call) {
    return reset.white`${super.Call(call)}`;
  }

  Frame(frame) {
    return reset.magenta`${super.Frame(frame).replace(/^ {2}/, '')}`;
  }

  PathLocator(locator) {
    if (locator.path.startsWith('/')) {
      locator.path = relative(process.cwd(), locator.path);
    }
    return super.PathLocator(locator);
  }
};

function doLowLevelStuff() {
  throw new Error('fubar');
}

function doStuff() {
  try {
    doLowLevelStuff();
  } catch (cause) {
    throw Object.assign(new Error('Uh oh'), { cause });
  }
}

try {
  doStuff();
} catch (e) {
  process.stdout.write(`${PrintVisitor.visit(cleanErrors(parseErrors(e)))}\n\n`);
}

Sorry I had to make a bunch of edits as I noticed little things that were wrong.

I've got an integration and it type checks now. Moving on to runtime debugging.

Oh no oh no I didn't consider that jest uses itself to test itself so because I broke the package that formats errors in tests I can't see the errors from the tests I broke O_O

Oooh I can actually npm install --global jest and then just test jest with jest (as opposed to yarn jest that is). This is super useful for working on the test runner itself as it ensures that the thing running the tests is working production code while the thing under test is the version with your changes.

I can also rebuild a single package easily by changing this line in scripts/build.js to:
const packages = [path.resolve(__dirname, '../packages/pgk-name')];

I've got at least a couple tests passing on the integration now. Current puzzle: the tests assert that frames from Jasmine are filtered out and not displayed, and yet I can't find the code that would be doing it if indeed those tests are presently passing.
Here's the relevant test stack trace:
  at stack (../jest-jasmine2/build/jasmine-2.4.1.js:1580:17)
  at Object.addResult (../jest-jasmine2/build/jasmine-2.4.1.js:1550:14)
  at jasmine.addResult (../jest-jasmine2/build/index.js:82:44)
  at Spec.Env.factory (../jest-jasmine2/build/jasmine-2.4.1.js:641:18)
  at Spec.addResult (../jest-jasmine2/build/jasmine-2.4.1.js:333:34)
  at Expectation.addResult (../jest-jasmine2/build/jasmine-2.4.1.js:591:21)
  at Expectation.toBe (../jest-jasmine2/build/jasmine-2.4.1.js:1504:12)
  at Object.it (build/__tests__/messages-test.js:45:41)
  at Object.<anonymous> (../jest-jasmine2/build/jasmine-pit.js:35:32)
  at attemptAsync (../jest-jasmine2/build/jasmine-2.4.1.js:1919:24)

And the snapshot indicates that the correct set of frames after filtering is:
  at stack (../jest-jasmine2/build/jasmine-2.4.1.js:1580:17)
  at Object.addResult (../jest-jasmine2/build/jasmine-2.4.1.js:1550:14)
  at Object.it (build/__tests__/messages-test.js:45:41)

...but why? How? I really don't know. I don't see any defining pattern to those three frames at all. All the frames are basically the same format. Some frames from ../jest-jasmine2/build/jasmine-2.4.1.js are included and some are excluded, even though in theory all of those paths match the JEST_INTERNALS_IGNORE regexp -- if we followed that regex only a single frame would be left, the Object.it frame.
OH!
Ok, brainwave. I am remembering that the snapshot for this test was all kinds of a mess, and I know that I must be cognizant that the old code may not have worked the way I assumed it did, and I think this is one of those moments. I couldn't understand why the snapshot had a blank line in the middle of the stack trace, but that's crucial. The "parsing" code was cutting off the first line assuming it to be the message (it is not), and then it was treating the remaining lines as the stack trace. One of them legitimately doesn't match the jest internals ignore patterh, and the other one is saved because the code always saves the top frame, even if it's from Jest. I just couldn't see that this was what was happening, because I thought the other frame was the top one.

All stack filtering is in that file. Feeding new (full) traces through the tests in https://github.com/facebook/jest/blob/2a5e51590ed77f5db2ab0beec8020ce116f06e67/packages/jest-message-util/src/tests/messages.test.ts is probably a good idea, that way you can see that it spits out the correct thing quicker that the integration tests can

I can also rebuild a single package ~easily~ by changing this line in scripts/build.js to:
const packages = [path.resolve(__dirname, '../packages/pgk-name')];

I recommend running yarn watch which will build all packages, then watch for changes and rebuild each file 🙂

Yep those are the tests I've been running since that's the code I've been changing. It's pretty cool how integrating with jest has allowed me to catch many bugs and flaws in my design and API that would have been difficult to see otherwise.
I think I've nearly got them all passing too...

The tests show two contradicatory behaviors likely due to bugs I've resolved in the logic. I need to know which is correct.
Should noStackTrace ever show stack trace frames, specifically should it show the top frame from the stack? The no stack test checks to make sure that no frames are printed, while the does not print codeframe when noStackTrace = true [test] expects a single stack frame to be printed.
There's also a comment that says, if no stack, no codeframe is implied. Hmm.

The documentation for noStackTrace says "Disables stack trace in test results output." Given that this is a documented option that comes with no qualifications and noCodeFrame is an undocumented object that is also predicated on the existence of a stack in order to have any use, I'd say it seems relatively clear to me that noStackTrace should take precedence and the correct result whenever that option is present is no stack frames and no code frames. But it's certainly different behavior than was present before. Perhaps running the broader test suite will shed some light on what that's about.

OK all the jest-message-util tests pass now that I've cleared up that ambiguity. Initial state of the broader test suite at this point is:
Test Suites: 43 failed, 1 skipped, 376 passed, 419 of 420 total
Tests:       109 failed, 36 skipped, 4246 passed, 4391 total
Snapshots:   101 failed, 1626 passed, 1727 total
Time:        164.339 s
Ran all test suites in 16 projects.

I'm not too worried though -- it looks like most of the failures look to be due to easily fixable problems.

The broader test suite seems to indicate that noStackTrace means "no more than one stack frame".

The console e2e contains a respects --noStackTrace case which passes {noCodeFrame: false, noStackTrace: true} to jest-message-util and then expects there to be one printed stack frame with no code frame.
I'm not gonna say that makes sense to me, but if that's the behavior I have to replicate that's what I'll make it do.

Test Suites: 17 failed, 1 skipped, 402 passed, 419 of 420 total
Tests:       57 failed, 36 skipped, 4298 passed, 4391 total
Snapshots:   50 failed, 1679 passed, 1729 total
Time:        165.92 s

I'm in the home stretch! Most of those remaining failures are caused by one of the 3 remaining anomalies that I still need to debug.
Test Suites: 6 failed, 1 skipped, 413 passed, 419 of 420 total
Tests:       10 failed, 36 skipped, 4345 passed, 4391 total
Snapshots:   9 failed, 1720 passed, 1729 total
Time:        166.294 s

Oh and there are a few places left in the implementation where I don't yet support errors with causes, which I absolutely do need to fix because the old code did "support" them at least in that it didn't blow up if there's a message in the middle of your stack trace, which my code will. This will require a little thought as to what the correct formatting and behavior should be.

The PR will go up today though, as most of the work I've done so far has just been to capture the existing logic with better code. The review for that code will be an excellent place to discuss what changes to the existing logic might be desired.

OK looking at the last big issue I'm seeing it's mostly causing failed snapshots that look like this:
    -       at Resolver.resolveModule (../../packages/jest-resolve/build/resolver.js:311:11)
    +       at Resolver.resolveModule (/home/conartist6/dev/repos/jest/packages/jest-resolve/build/resolver.js:311:11)

I believe my implementation is actually what I'd consider to be correct here, though I admit I don't fully understand the way the previous implementation was working. The reason I've chosen the absolute path is because this stack frame is in reference to a module outside jest's rootDir.
I'm going to go ahead and update those snapshots, though obviously that decision will be subject to review.

Ah but of course the snapshots can't contain anything about the environment or they won't work

Oh and I probably broke windows \ compatibility which is untested so I must remember to fix that. My intention was/is to move that functionality wholly into stack-tools.

Draft PR is up! Let the feedback roll in! I'll be doing my own review there as well.

The file handles bug stems from a fundamental ambiguity in node errors. Errors have a message and a stack, but the first line of the stack is (usually) the content of error.message. If you write to error.message of course, then you've caused these two sources of truth to go out of sync.
I've already kind of made a mess of this because I use both as sources of truth in various places, which is to say I assume that they are in sync. stack-tools does its basic parsing by eliminating error.message from the top of error.stack. @stack-tools/node-tools meanwhile always parses error.stack, deducing error.name and error.message from them.
To complicate things, changing an error's message may be just fine -- so long as you've never tried to print the error or in any other way access error.stack (e.g. in a debugging session). This is because the content of error.stack is generated lazily by node the first time it is accessed. If you write to error.message before reading error.stack, then you'll stay in sync.
Finally this problem has already been anticipated to some degree. I added a replaceMessage method to stack-tools which ensures that error.stack is updated, and of course another way to extend errors is using the error.cause property which hopefully in the longer run will alleviate the need to tamper with error messages.
All that said, partly because this issue can be so finnicky (e.g. affected by debugging), I think my current split approach in stack-tools could create some real pain. I would like to at least have consistent modes of failure between stack-tools (which uses properties) and @stack-tools/v8-tools and @stack-tools/node-tools which only parse error.stack.

Looks like this issue has stalled - but it would be super valuable to ensure error chains are being correctly reported

This was closed in https://github.com/jestjs/jest/pull/13606, unless there's some additional request here I'm missing.

Maybe this one has to be merged before? https://github.com/jestjs/jest/pull/13965

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.1


Show face tags in photo modal

Want to see the face tags in the image modal.

 The problem I've been having is with the actual carousel inside react-images, as the callbacks seem inconsistent and the timing is bad enough I cannot grab the current displayed image from the dom reliably.
There is a ticket in react-images to update it's implementation to a different library so I might wait for that to pan out before I waste more time on this.


feat:mysql&ci intro

You can work on your PR branch, and it will automaticlly apply to this PR.
No need to close this

You can work on your PR branch, and it will automaticlly apply to this PR.
No need to close this


Resource Owner Password Credentials Grant support

Add support for OAuth 2.0 Resource Owner Password Credentials Grant.

[master 53bb3b2] Implement Resource Owner Grant (Issue #3)
Still need to do the unit test for this...


Loopback and backward direction support

It would be greate if this library could support such structure of graph.

Can you share some usecase?


Images exported with HTMLExport are blurry

Describe the bug
When exporting a report containing images with HTML Export the images are blurred / low quality. If exporting the same report with SimplePDF Export the images are clear.
To Reproduce
Steps to reproduce the behavior:

Create a report containing an image.
Export the report with HTMLExport
Open the exported HTML
The blurred, low quality image is generated
For comparison export the same report with PDFSimpleExport where the image is clear, high quality

Expected behavior
Images generated with HTMLExport should look the same as images generated with PDFSimpleExport.
Screenshots
HTMLExport:

SimplePDFExport:

Versions:

FastReport.OpenSource version 2024.1.2

Hello!
We have checked the exports and the problem is not reproduced. Could you please attach a test report where we can reproduce the problem?

Hello,
I have created an example project with this issue: https://github.com/Wazrop/FastReportImageExportTest
The project is pretty straightforward. Endpoints are DownloadPdf and DownloadHtml which both generate either a pdf (PDFSimpleExport) or html (HTMLExport) from the same report file and download the file.
The difference is even more noticeable if each file is printed onto paper.
Thank you for your time.

Also, please try enabling the HighQualitySvg property of the export.


scGPT binning component

Changelog
Add scGPT pre-processing binning component.
Checklist before requesting a review

[x] I have performed a self-review of my code

[x] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[ ] Breaking changes
[x] New functionality
[ ] Major changes
[ ] Minor changes
[ ] Documentation
[ ] Bug fixes

[x] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

ALGTM!

awesome, thanks for the review!


OTel ActorContextDecorator should support all ReenterAfter overloads

Description
Currently only 2 of the 5 overloads for ReenterAfter is supported by the OpenTelemetryActorContextDecorator. This causes telemetry to be lost when using the unsupported variants.
We encountered problems with our system where we had to manually re-set the Baggage, because we called one of the unsupported ReenterAfter overloads. With this fix it should mean we don't have to do this anymore.
I have added tests that cover each of the overloads (expectedly 3 out of 5 failed before the fix).
Suggestions for naming and improvements to the tests are welcome, I just made the simplest tests i could think of to test the problem.
However since I am making changes to the ActorContextDecorator base class, it may have implications for all other decorators. It might be necessary to take a look and see if those need updating to make sure they implement the missing overloads too.
Purpose
This pull request is a:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Dataframe .select() API needs some way to error on missing columns

When we select a column from the dataframe view, we previously made the decision that a missing column would provide results but be implicitly null.
The rationale for this decision was that in many situations, Rerun data producers may not even create a column if something is missing. For example: maybe a detector simply never logs anything if nothing is detected. In these cases, a query-writer reasonably wants a null column to exist.
However, the far, far far more common case is someone exploring the data and writing a test script made a typo. If a user doesn't actually know what was in the dataset, they may think this is validly null data, as opposed to realizing they aren't querying the right content.
We should instead default to error on null, and then provide a mechanism for advanced users to inject any missing-but-required columns into the view only in situations where it makes sense to do so.

Related: https://github.com/rerun-io/rerun/issues/7759


Deadlock while resolving dependencies with excludes

Current Behavior
deadlock while resolving dependencies with excludes
Expected Behavior
resolve dependencies successfully
Context (optional)
No response
Steps to Reproduce
issue.zip

unzip issue.zip and copy gradlew files into it
./gradlew :dependencies --configuration compileClasspath

Gradle version
8.7
Build scan URL (optional)
No response
Your Environment (optional)
No response

The issue is in the backlog of the relevant team and is prioritized by them.
Note that the issue occurs for any 8.x version of Gradle.

Thank you for providing a tiny reproducer!


OpenAPI - as HTML

I tried it test and encounter below error
I was checked it again my installed and again checked it but same error occured.

What problem this test?

You should followed all instructions
https://github.com/securedimensions/authzforce-ce-geoxacml3
and
https://github.com/securedimensions/authzforce-ce-geoxacml3-rest-api-model
Do the same application/geoxacml+json select buttons of Request body and Responses .


Edit author page should save changes

Scenario
Given an author named 'Alan Turing'
When a user visits the edit page of the author Alan Turing
Then no error should occour
Hints
Feature: Changes made to the authors in an edit form (similar to the 'new' form) should be written to the database.
New controller actions (edit and update) and a new view are required.
Tests could be placed in spec/features/author/edit_author_spec.rb.
In a test, if an object's values should be reloaded from the database, after an action has modified them, consider the reload method:
@author.reload
Here is the relevant section (5.11) of the Rails Guide.
Error

Got AbstractController::ActionNotFound: The action 'edit' could not be found for AuthorsController

16 exercise tests have passed. There are 44 in total. You will solve multiple at once towards the end.

Sorry, it's not working for me yet:
Scenario
Given an author named 'Alan Turing'
When a user visits the edit page of the author Alan Turing
And changes first name to 'Bob'
And clicks submit
Then no error should occour
Error

Got AbstractController::ActionNotFound: The action 'update' could not be found for AuthorsController

If you have problems solving this task, please don't hesitate to contact the teaching team!


Is there any way to use this with the npm module "puppeteer"?

Is there any way to launch carbonyl instead of chromium with puppeteer? I know I can use executablePath but its not working with carbonyl, only chrome and chromium. Can I use chromium flags when launching carbonyl to set a wsEndpoint to connect to automate carbonyl?

I cannot use executablePath because it cannot launch docker applications, and I see that the only way to launch carbonyl (without building it myself) is with docker

You can extract binaries from the Docker image using the instructions in https://github.com/fathyb/carbonyl/issues/21#issuecomment-1407774622

Im getting an error "exec /bin/bash: exec format error" when I use " sudo docker run --platform linux/arm64 --entrypoint bash fathyb/carbonyl -c "tar -cf - /carbonyl" > carbonyl.tar.gz"