Feature/add GitHub ci

@rcmorano
close... we have the binaries building
draft release is erroring
+ sleep 1
++ ls release-files/lift-wallet-linux-PR-61.AppImage release-files/lift-wallet-macos-PR-61.dmg release-files/lift-wallet-windows-PR-61.exe
++ sed 's| |,|g'
++ xargs echo
+ publish-release --draft --reuseRelease --reuseDraftOnly --tag pull-request-61 --owner CodingOnChain --repo lift-wallet --token *** --name 'Release PR#61-2f1d268' --notes 'Automatic release from GH action on this project.' --assets release-files/lift-wallet-linux-PR-61.AppImage,release-files/lift-wallet-macos-PR-61.dmg,release-files/lift-wallet-windows-PR-61.exe
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: Error status: 403  response body:{"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/reference/repos#create-a-release"}
 request details:{
  "uri": "https://api.github.com/repos/CodingOnChain/lift-wallet/releases",
  "method": "POST",
  "json": true,
  "body": {
    "tag_name": "pull-request-61",
    "name": "Release PR#61-2f1d268",
    "body": "Automatic release from GH action on this project.",
    "draft": true,
    "prerelease": false
  },
  "headers": {
    "Authorization": "token ****",
    "User-Agent": "publish-release 1.6.1 (https://github.com/remixz/publish-release)"
  }
}
    at Request._callback (/usr/local/lib/node_modules/publish-release/index.js:90:21)
    at Request.self.callback (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:185:22)
    at Request.emit (events.js:315:20)
    at Request.<anonymous> (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:315:20)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:421:28)
    at IncomingMessage.emit (events.js:327:22)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on PublishRelease instance at:
    at asyncAutoCallback (/usr/local/lib/node_modules/publish-release/index.js:313:12)
    at taskCallback (/usr/local/lib/node_modules/publish-release/node_modules/async/lib/async.js:468:21)
    at Request._callback (/usr/local/lib/node_modules/publish-release/index.js:91:20)
    at Request.self.callback (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:185:22)
    [... lines matching original stack trace ...]
    at IncomingMessage.emit (events.js:327:22)
+ sleep 1
++ ls release-files/lift-wallet-linux-PR-61.AppImage release-files/lift-wallet-macos-PR-61.dmg release-files/lift-wallet-windows-PR-61.exe
++ xargs echo
++ sed 's| |,|g'
+ publish-release --draft --reuseRelease --reuseDraftOnly --tag pull-request-61 --owner CodingOnChain --repo lift-wallet --token *** --name 'Release PR#61-2f1d268' --notes 'Automatic release from GH action on this project.' --assets release-files/lift-wallet-linux-PR-61.AppImage,release-files/lift-wallet-macos-PR-61.dmg,release-files/lift-wallet-windows-PR-61.exe
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: Error status: 403  response body:{"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/reference/repos#create-a-release"}
 request details:{
  "uri": "https://api.github.com/repos/CodingOnChain/lift-wallet/releases",
  "method": "POST",
  "json": true,
  "body": {
    "tag_name": "pull-request-61",
    "name": "Release PR#61-2f1d268",
    "body": "Automatic release from GH action on this project.",
    "draft": true,
    "prerelease": false
  },
  "headers": {
    "Authorization": "token ****",
    "User-Agent": "publish-release 1.6.1 (https://github.com/remixz/publish-release)"
  }
}
    at Request._callback (/usr/local/lib/node_modules/publish-release/index.js:90:21)
    at Request.self.callback (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:185:22)
    at Request.emit (events.js:315:20)
    at Request.<anonymous> (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:315:20)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:421:28)
    at IncomingMessage.emit (events.js:327:22)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on PublishRelease instance at:
    at asyncAutoCallback (/usr/local/lib/node_modules/publish-release/index.js:313:12)
    at taskCallback (/usr/local/lib/node_modules/publish-release/node_modules/async/lib/async.js:468:21)
    at Request._callback (/usr/local/lib/node_modules/publish-release/index.js:91:20)
    at Request.self.callback (/usr/local/lib/node_modules/publish-release/node_modules/request/request.js:185:22)
    [... lines matching original stack trace ...]
    at IncomingMessage.emit (events.js:327:22)
    ```

Closed in favor of #63


Update deps

/test all

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test release-notes_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test release-notes_istio_release-1.7

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

release-notes_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test release-notes_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test release-notes_istio_release-1.7

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio_release-1.7

/retest

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
10a5182736c2d931f938946537bb2a6e0d649009
link
/test unit-tests_istio_release-1.7

release-test_istio_release-1.7
ed60dbca44abbfa94162fd580b48fa893e923ccb
link
/test release-test_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio_release-1.7
ed60dbca44abbfa94162fd580b48fa893e923ccb
link
/test release-test_istio_release-1.7

unit-tests_istio_release-1.7
af3792f718ea8733a11e2978897780939388b05b
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Sorry didn't realize this the logging bug, added a hold to avoid accidentally merging code that will flake 90% of the time

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
af3792f718ea8733a11e2978897780939388b05b
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
a0df9cd8c44e5538530d3c6411330699c0b769f4
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
a0df9cd8c44e5538530d3c6411330699c0b769f4
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


TypeError: Failed to convert object of type <class ‘plaidml.tile.Value’> to Tensor.

Hi! The plaidml installation succeed, but there are some problems with the tensors:
To avoid tensorflow operations, I installed ngraph_bridge, but I got this error:
Traceback (most recent call last): File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/tensor_util.py”, line 558, in make_tensor_proto str_values = [compat.as_bytes(x) for x in proto_values] File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/tensor_util.py”, line 558, in <listcomp> str_values = [compat.as_bytes(x) for x in proto_values] File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/util/compat.py”, line 65, in as_bytes (bytes_or_text,)) TypeError: Expected binary or unicode string, got <tile.Value Add FLOAT32(<tile.Value SymbolicDim UINT64()>, <tile.Value Add FLOAT64()>, <tile.Value Add FLOAT64()>, 6)> During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/Users/jasmindalferth/Documents/Mask R-CNN/3_validate.py”, line 160, in <module> model = modellib.MaskRCNN(mode=“inference”, config=ValConfig(), model_dir=RESULT_MODEL) File “INPUT_NETWORK/mrcnn/model.py”, line 1817, in __init__ self.keras_model = self.build(mode=mode, config=config) File “INPUT_NETWORK/mrcnn/model.py”, line 1921, in build len(config.RPN_ANCHOR_RATIOS), config.TOP_DOWN_PYRAMID_SIZE) File “INPUT_NETWORK/mrcnn/model.py”, line 885, in build_rpn_model outputs = rpn_graph(input_feature_map, anchors_per_location, anchor_stride) File “INPUT_NETWORK/mrcnn/model.py”, line 852, in rpn_graph lambda t: tf.reshape(t, [tf.shape(t)[0], -1, 2]))(x) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/keras/engine/base_layer.py”, line 457, in __call__ output = self.call(inputs, **kwargs) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/keras/layers/core.py”, line 687, in call return self.function(inputs, **arguments) File “INPUT_NETWORK/mrcnn/model.py”, line 852, in <lambda> lambda t: tf.reshape(t, [tf.shape(t)[0], -1, 2]))(x) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py”, line 330, in shape return shape_internal(input, name, optimize=True, out_type=out_type) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py”, line 354, in shape_internal input_tensor = ops.convert_to_tensor(input) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/ops.py”, line 1087, in convert_to_tensor return convert_to_tensor_v2(value, dtype, preferred_dtype, name) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/ops.py”, line 1145, in convert_to_tensor_v2 as_ref=False) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/ops.py”, line 1224, in internal_convert_to_tensor ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/constant_op.py”, line 305, in _constant_tensor_conversion_function return constant(v, dtype=dtype, name=name) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/constant_op.py”, line 246, in constant allow_broadcast=True) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/constant_op.py”, line 284, in _constant_impl allow_broadcast=allow_broadcast)) File “/Users/jasmindalferth/Documents/Mask R-CNN/env/lib/python3.7/site-packages/tensorflow/python/framework/tensor_util.py”, line 562, in make_tensor_proto “supported type.” % (type(values), values)) TypeError: Failed to convert object of type <class ‘plaidml.tile.Value’> to Tensor. Contents: Add FLOAT32(<tile.Value SymbolicDim UINT64()>, <tile.Value Add FLOAT64()>, <tile.Value Add FLOAT64()>, 6). Consider casting elements to a supported type.

We removed PlaidML support. PlaidML is working in an MLIR setting now.

So do you know a method how to run tensorflow-gpu on a Mac with the GPU AMD Radeon Pro 5300M?

So do you know a method how to run tensorflow-gpu on a Mac with the GPU AMD Radeon Pro 5300M?

I don't think that there's any way to do that now. I'm seriously disappointed that nGraph removed PlaidML support so prematurely. It's irresponsible; they should've at the very least waited until PlaidML's MLIR support was actually functional; right now, it's a long way off.

The PlaidML team implemented it and was maintaining it and were directed to focus on other things. The backend stopped working with the available PlaidML version many months ago.


Header - Coveo search

The main search bar in the header is implemented via Coevo Atomic library which we need to implement as well. All search requests will got to Coevo.
This is blocked by #6 which should be implemented first.
(Currently we don't index Franklin pages to Coevo, this will happen on a later stage)

Did some quick test
  <head>
    <title>MH Test</title>
    <script>
          (async () => {
            await customElements.whenDefined('atomic-search-interface');
            const searchInterface = document.querySelector('#search');

            await searchInterface.initialize({
              accessToken:'...',
              organizationId: '...',
              organizationEndpoints: await searchInterface.getOrganizationEndpoints('...'),
            });
            searchInterface.executeFirstSearch();
          })();
    </script>
  </head>
  <body>
    <div style="height: 100px;">
        <script type="module" src="https://static.cloud.coveo.com/atomic/v2/atomic.esm.js"></script>
        <style rel="stylesheet" href="https://static.cloud.coveo.com/atomic/v2/themes/coveo.css"></style>
        <atomic-search-interface
            class="search-bar hydrated"
            search-hub="DanaherMainSearch"
            pipeline="Danaher Marketplace"
            language="en"
            reflect-state-in-url=""
            scroll-container="atomic-search-interface"
            language-assets-path="./lang"
            icon-assets-path="./assets"
            enable-relevance-inspector=""
            id="search">
            <atomic-search-box
            redirection-url="https://lifesciences.danaher.com/us/en/search.html"
            data-atomic-rendered="true"
            data-atomic-loaded="true"
            class="hydrated"
            number-of-queries="8"
            minimum-query-length="0"
            clear-filters="">
                <atomic-search-box-recent-queries max-with-query="3" class="hydrated"></atomic-search-box-recent-queries>
                <atomic-search-box-query-suggestions class="hydrated"></atomic-search-box-query-suggestions>
            </atomic-search-box>
        </atomic-search-interface>
    </div>
  </body>
</html>

While this is super easy to integrate it loads 237kBytes compressed. A lot for just the search bar. We should consider using the APIs. @davenichols-DHLS @rgravitvl any thoughs?

Here is the information about how we can implement Coveo.

Atomic
Information:
https://docs.coveo.com/en/atomic/latest/
https://docs.coveo.com/en/atomic/latest/usage/
Online Course:
https://levelup.coveo.com/learn/courses/atomic

This is Coveo's Component Library that contains pre-built UI component that can be placed onto a page.
This contains html, css, and js.
It is built on Coveo's Headless Library so when using Atomic, are loading both Atomic and Headless libraries.
As this is built on top of Headless, it has analytics built-in so there is no need to develop analytics unless something custom is needed.
The main benefit of this is the short implementation time as a bulk of the work is already done and all we need to do is slight tweaks and some styling changes.
The main detriment of this is that since we are relying on Coveo's pre-built components, customization of these components would take some time as the component would need to be overwritten. Also, this requires the most kb to download to a user's browser so this could impact pagespeed.

Headless
Information:
https://docs.coveo.com/en/headless/latest/
https://docs.coveo.com/en/headless/latest/usage/
Online Course:
https://levelup.coveo.com/learn/courses/headless-commerce-tutorial

This is Coveo's JavaScript Library specifically to query their API and fetch the results.
There is analytics built in so there should be no need to develop anything alaytics related unless something custom is needed.
The main benefit of this is that since this is only Javascript, we would retain full control and customization of the UI components.
The main detriment is that there would be a longer development period as the UI would need to be built.

Direct API Calls
This would be directly calling Coveo's API to query and return results.
Since this has no libraries, we would need to build out the analytics code. We can use the coveoua library mentioned below but we would still need to incorporate it.
The main benefit of this is that there are no extra libraries required so this would give the biggest benefit to pagespeed.
The main detriment of this is that, as this is completely custom, there would be an even longer development time.

Extra:

coveoua
This is Coveo's Javascript Library specifically for analytics.
https://docs.coveo.com/en/l2bf0354/coveo-for-commerce/initialize-the-coveo-analytics-library
We would need to use this because while Headless can take care of analytics whenever the user interacts with the search aspects of the site, we want to send information to Coveo for pages that have no search interaction.
Examples:

Page Views
Product Views
Ecommerce events (add to cart, remove from cart, checkout, purchase)

Since this does not change the functionality of a page from a user perspective, this library can be loaded in the footer so the DOM does not have to wait for it to finish.

Acceptance checklist:
[] click on the searchbox should show default suggestions
[] empty search term should show 3 recent searches on top
[] clear icon should appear when search term is not empty
[] submit with empty search (enter or click search button) should go to search page without query
[] submit with a search term (enter or click search button) should go to search page with a query
[] click on a search suggestion should go to search page with the selected query
[] search suggestions can be navigated using up / down keys
[] press enter key on a search suggestion should go to search page with the selected query
[] search suggestion should include analytics of the current user session
[] search submission should record the search call
[] upon a search submission with a query, the search term is recorded in recent searches list
[] click outside the search box & suggestions should close the suggestions list


Failed to get a valid response from Home Connect server

Now I'm not suggesting this is an issue with the code but am reaching out to see if anybody has the same issue!
I'm on Core 2024.10.2 with 1.1.9 of Home Connect Alt.  It has worked since the updates so I'm confident it's nor that.
Anyway - I restarted for some other reason today and when it came back the Home Connect Appliances were all busted:

Failed to load data from Home Connect (('Failed to get a valid response from Home Connect server', 902, None, None, None))
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/home_connect_async/homeconnect.py", line 150, in async_load_data
    response = await self._api.async_get('/api/homeappliances')
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/home_connect_async/api.py", line 119, in async_get
    return await self._async_request('GET', endpoint)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/home_connect_async/api.py", line 114, in _async_request
    raise HomeConnectError("Failed to get a valid response from Home Connect server", 902)
home_connect_async.common.HomeConnectError: ('Failed to get a valid response from Home Connect server', 902, None, None, None)

Their status pages all say everything is fine and the app works (as well as it ever has).  Maybe it'll just come back in time.
I just wanted to reach out and see if anybody else had this issue and apologise if there is a better forum for it than here!

The "Home Connect Service Home Connect Status" entity shows LOADING_FAILED by the way after INIT, which is entirely true and seems to be working correctly :)

the same here

yep same here!

+1
Home Connect app is working. HA is not.

I would rate this as a temporary server issue, but an integration error...

Is there a way to communicate directly with my appliance? The dishwasher is in my home, so is my HA. So don’t need the cloud….

Since nothing has changed in the integration it is indeed most likely a server issue. You should check the app while NOT connected to wifi, which forces it to use the cloud. See the README for details. If it works while disconnected from wifi the please upload a full debug log with Log Mode=7 (see the README for details on that as well).

Can confirm there's a message in the app saying:

Appliance connections will be working again shortly. Sorry.

Still nothing in Home Assistant. Restart HA or even reboot HassOS doesn’t work, Home Connect app works fine. How to get my appliance back in HA?

It's working again, services back online.
Just had to reload the integration once

Perfect, it works again indeed
Groet,
John Janken
(sent from mobile)
On 17 Oct 2024, at 06:30, Nerdix @.***> wrote:

It's working again, services back online.
Just had to reload the integration once
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2418474328, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMSPFDWW46CYXJGFB7DZ344PNAVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJYGQ3TIMZSHA.
You are receiving this because you commented.Message ID: @.***>

I still have the problem, reboot, reload stil the message: LOADING_FAILED

Same here. It worked again earlier today (like I mentioned in the thread), but now problem returned.
Online in Home Connect app.
Offline in Home Assistant integration. Reboot / restart doesn’t help.
Groet,
John Janken
(sent from mobile)
On 17 Oct 2024, at 18:10, SBerg1980 @.***> wrote:

I still have the problem, reboot, reload stil the message: LOADING_FAILED
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2419958991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMXUNGE7MHFEBTOFOYDZ37OP5AVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJZHE2TQOJZGE.
You are receiving this because you commented.Message ID: @.***>

But the app as well reports t
That they have issues, so just be patient.
Not an error of the integration as long as the don't change the APIs 😉

Service is back, dishwasher working, oven(s) less so!

Still have problem. Status for me is Loaded but no device is available.

I do have the same problem
LOADING_Failed

I just added my first Home Connect Appliance (Dishwasher) and had lots of problems to add the appliance to my account, it failed for 5 or 6 times with http errors. Just my luck to use Home Connect the first time when they're having problems :-D .. I had already configured this integration and reached this issue because the integration is giving me LOADING_ERROR... thanks guys for the pointer to the problem (yes, I have it on the app also).

This week the remote control has become totally unreliable and unusable and they don’t seem able to resolve. I use the api to control my dishwasher based on cheap electricity hours and a few other things.
Really hope that they solve these issues fast, otherwise the next appliance I buy will certainly not be a Home Connect based device like Siemens or Bosch.
Groet,
John Janken
(sent from mobile)
On 18 Oct 2024, at 19:18, pmrosa-classes @.***> wrote:

I just added my first Home Connect Appliance (Dishwasher) and had lots of problems to add the appliance to my account, it failed for 5 or 6 times with http errors. Just my luck to use Home Connect the first time when they're having problems :-D .. I had already configured this integration and reached this issue because the integration is giving me LOADING_ERROR... thanks guys for the pointer to the problem (yes, I have it on the app also).
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2422914844, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMUNMGFMY27ACLJ2M2LZ4E7F3AVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRSHEYTIOBUGQ.
You are receiving this because you commented.Message ID: @.***>

It was working fine until I restarted Home Assistant today for the 2024.10.3 update.
Now all connections to Home_Connect_Alt is broken.

Still an issue here too, but reassuring others see the same thing.  It would seem some instability on the Siemens side is affecting this.  The mobile app lost the appliance, then it reappears some time later, and Home Assistant also has sporadic lapses at least for the past two days.

A fully off-line control would be truly great for Home Assistant.

I wonder if anyone at home connect has noticed yet. Their status page still
thinks everything is fine.
Adam
Sent on the go!
On Fri, 18 Oct 2024, 21:13 kpoppel, @.***> wrote:

Still an issue here too, but reassuring others see the same thing. It
would seem some instability on the Siemens side is affecting this. The
mobile app lost the appliance, then it reappears some time later, and Home
Assistant also has sporadic lapses at least for the past two days.
image.png (view on web)
https://github.com/user-attachments/assets/5c7ef44b-2a15-4bc4-a5b9-ec272963fe5d
A fully off-line control would be truly great for Home Assistant.
—
Reply to this email directly, view it on GitHub
https://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2423165538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5VP25OAZPRVIQTDVPOIATZ4FTWPAVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTGE3DKNJTHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Siemens clearly has trouble today:

It's so sad that a big company like Siemens isn't able to perform better. Question is; Can we trust them anymore?

Same here.
Basically it happened after the HA 2024.10.3 update .... but don't know if this has something to do with it. Maybe a coincidence.
Official app still works but has the system outage message at the top.
Now I get the 429 error of rate limit but I reinitialised the integration a couple of times. Probably the API servers also did not like that ;-)

I‘m still on 2024.10.2 and have the same issue

Now I get the 429 error of rate limit but I reinitialised the integration a couple of times.

Where did you see the 429 wire code?  And where do you reset the rate limit?

My Home Connect app is configured to only use the cloud connection (not local) due to VLAN config. I can tell you that the app is experiencing all the same connectivity issues that Home Assistant is. The fault certainly appears to be with the Home Connect back-end and not with this integration. It's been on/off (but mainly off) for a few days now. It is not working right now. I sent a support enquiry last night, but have not had any kind of reply. To be honest, these days, I don't expect to ever hear back from them, but I'll post here if I do.

Also the cloud isn’t working: can’t reach my Siemens appliance in the HC app while my phone is on the mobile network. It’s only accessible in the HC app while connected via local wifi (i.e. same wifi as the Siemens). With that, also the HAss integration (Homey users most likely suffer as well) is dead while depending on the HC cloud. And now it’s weekend, so most likely no-one is available to solve the problem. I hate cloud based integrations, so hopefully a one skilled HAss integration developer succeeds in making a good (HACS) integration that works locally: both my HA and Siemens appliance are on the same local wifi network, so cloud is redundant.

in reply to @von-Chaps:
Anyone who is in doubt to buy Siemens, Bosch or Miele: my advice is to go for Miele. I never had these issues with my 3 wifi connected appliances.

My Home Connect app is configured to only use the cloud connection (not local) due to VLAN config. I can tell you that the app is experiencing all the same connectivity issues that Home Assistant is. The fault certainly appears to be with the Home Connect back-end and not with this integration. It's been on/off (but mainly off) for a few days now. It is not working right now. I sent a support enquiry last night, but have not had any kind of reply. To be honest, these days, I don't expect to ever hear back from them, but I'll post here if I do.

Same issue as everyone else (in Canada) - my iphone Home Connect app shows a notification saying "Connection Outages" - Oct 19 at 73-am" - "Appliance connections will be working again shortly, Sorry" - so it looks like their end not ours.

Still Error 502-Bad Gateway.
Android App & Integration still don't work.
Status-Website says. "System is up and running!"
The "Contact"-Web-Page shows variables of the fields like [cso.contact.form.lbl.email] instead of "Email".
and doesn't work too (sending request leads to error..)
Seems to be a bigger problem....wondering if they are working on it ... at weekend.

I’m in Europe (NL), same issue. Seems global.
Groet,
John Janken
(sent from mobile)
On 19 Oct 2024, at 13:33, julian4646 @.***> wrote:

Same issue as everyone else (in Canada) - my iphone Home Connect app shows a notification saying "Connection Outages" - Oct 19 at 73-am" - "Appliance connections will be working again shortly, Sorry" - so it looks like their end not ours.
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2423775450, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMTHLHO3BNFGMVME353Z4I7PDAVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTG43TKNBVGA.
You are receiving this because you commented.Message ID: @.***>

Same in France. App on IS is KO too

Same in Switzrerland, joining this thread for updates in case anyone finds anything. Siemens seems to have messed it up big time.

Mine is working again

Mine is still Not working

Mine is still Not working

I did have to sign in in de app again and reload de home connect integration

HA integration and HC app (outside lan) work again. So apparently the HC cloud server also.
HA integration must be reloaded and HC app must be restarted to connect to the appliances.
Groet,
John Janken
(sent from mobile)
On 19 Oct 2024, at 22:30, canedje @.***> wrote:

Mine is still Not working
I did have to sign in in de app again and reload de home connect integration
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2424197312, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMUAGEDQU7R2TZORK23Z4K6OPAVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGE4TOMZRGI.
You are receiving this because you commented.Message ID: @.***>

Mine is now working also.

It is working but still in my logs I see following error
fetch https://api.home-connect.com/api/homeappliances/events failed: 503

Have you restarted the app or the integration from the system that you use (HA, Homey or whatever system you use)?
Message ID: @.***>

It is working but still in my logs I see following error
fetch https://api.home-connect.com/api/homeappliances/events failed: 503

Same here. Is there anyway possible to understand these "cryptic" error messages coming from HA?

503 is a default Apache "service not available" error code. It's not an error / bug with this integration. The service API from Bosch / Siemens seems to be not 100% healthy yet, although it is working a lot better the last hours.

And the connection is broken again….
Groet,
John Janken
(sent from mobile)
On 20 Oct 2024, at 11:34, C0rish @.***> wrote:

503 is a default Apache "service not available" error code. It's not an error / bug with this integration. The service API from Bosch / Siemens seems to be not 100% healthy yet, although it is working a lot better the last hours.
—
Reply to this email directly, view it on GitHubhttps://github.com/ekutner/home-connect-hass/issues/426#issuecomment-2424772688, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6FKIMUQO2XL7NXKSSXEI3DZ4N2I5AVCNFSM6AAAAABQB5EWS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUG43TENRYHA.
You are receiving this because you commented.Message ID: @.***>

Not sure if it is a coinsidence but from the time i re-logged into my Home Connect App (was logged out for no forseable reason) my Home Connect integration could pull Data again from my devices.

Not sure if it is a coinsidence but from the time i re-logged into my Home Connect App (was logged out for no forseable reason) my Home Connect integration could pull Data again from my devices.

That's just confirming the unreliable state the service is in at the moment. It is incredibly flaky, working from time to time, but mostly it is not. I am not using this plugin, but my own implementation, and also having the same issues with the service.

Hi all,
Today I told my wife NOT to order a Siemens tumble dryer. Until this problem is resolved and the remote API server behaves bravely.  (for a weer or two)
And not like an ape!

Seems like the service is back in the room now. Coincidentally, the Home Connect app prompted me to give feedback in Google Play during the outage, so I left a scathing review. Someone was on it pretty quick to apologize and state that the service was down over the weekend (duh). No explanation as to why.
I said before that I raised a support issue in the app too. I did actually get a response from them;

Thank you for contacting the Home Connect Team.
I'm afraid we have had some issues over the last few days affecting the connection to appliances.
I apologise about any inconvenience caused by this.
The issues have now been resolved.
If you require any further assistance, please do not hesitate to contact us back.
Kind regards
Mark Fortescue
Customer Service Advisor

Again, no explanation of what happened, but I didn't expect that. However, it does seem that plenty of people were aware that the service was badly broken, so there's that I suppose.
As others have said, it'll be a while before I consider another Home Connect appliance (Bosch, Siemens...)

Seems like the service is back in the room now.
As others have said, it'll be a while before I consider another Home Connect appliance (Bosch, Siemens...)

Thank you for posting this info.
Regretfully, SIEMENS is nether worse nor better that anyone else.  The fact that service do run into trouble from time to time, is understandable and acceptable. What is NOT acceptable, is that they fail to post correct info on the opening page of their app (and elsewhere). We should have had a "Service status" page we could visit.
All I had in my app was a note claiming that there had been an outage on my side!  I interpret this as an attempt to blame me for my problems.  This is where SIEMENS fail and becomes inferior.

Additional info:
In my case, when contact with the server was restored, the app requested an update to the dishwasher firmware.
This could only be started via Bluetooth with the cell phone with app was right next to the dishwasher.
The door status is now reported again, but I can't say yet whether the functionality has been completely restored.
What's really sad is that Siemens could inform registered users via email if they have major adjustments or outages. I'm now also considering whether another Siemens product with Homeconnect would be an option for me.

Thank you for posting this info. Regretfully, SIEMENS is nether worse nor better that anyone else. The fact that services do run into trouble from time to time, is understandable and acceptable. What is NOT acceptable, is that they fail to post correct info on the opening page of their app (and elsewhere). We should have had a "Service status" page we could visit. All I had in my app was a note claiming that there had been an outage on my side! I interpret this as an attempt to blame me for my problems. This is where SIEMENS fail and becomes inferior.

Of course, you are absolutely right. Goes without saying really, cloud services are unreliable andd unpredictable
I would use the local connection, but my oven is on a different VLAN to Home Assistant, so I don't think they can communicate.

Of course, you are absolutely right. Goes without saying really, cloud services are unreliable andd unpredictable
I would use the local connection, but my oven is on a different VLAN to Home Assistant, so I don't think they can communicate.

The, or better say an open, local connection would be awesome. The current implementation is lacking this feature for anything other than the original app.
But I think time will tell... Remember my words: One day we will control those additional smart features (which of course almost all of them are also controllable directly on the device itself - without an app). Where Siemens/ Bosch will help us to do so... Or not.
But to your question: You CAN use the local mode in the original app, although your devices are on different VLANs. You simply have to add an per device IP specific route from VLAN A (where your app is in) to VLAN B (where your device is in). I think the app will try to contact the devices locally via IP and uses it, in case the cloud is not available.
Try it out :)

This is what Home Connect support responded on my complaint. So everybody on the globe is wrong, and they are right. Well, well…
Message ID: @.***>
Your dishwasher is connected stably to our server and should therefore also be temporarily available.
There are no green devices connected to our server.
This often occurs because your router blocks this signal.
The Home Connect device cannot establish a correct connection to our Home Connect servers.
This can be a surprising door for your Home Connect devices by activating “independent port sharing” or “UPNP” in your router, opening the correct port forwarding rules in your router to set to your home connect device.
It is also important to enable the Multicast function in your router so that Wi-Fi devices can make separate contact with each other.
The correct port forwarding rules are:
Port: 443TCP
Port: 80 TCP
Port: 8080TCP
Port 123UDP
You can then check the connection status of your device with our Home Connect servers under the device settings in the app and then under the heading network connection. Both lines to the cloud should be green in color here

Problem returned. Anyone else who has issues too?

Yes for 9 hours now

mine is working fine

@deluxestyle also remotely, i.e. when NOT connected to the same home network as the appliance, like via HC app over 3G/4G/5G or when using a home automation system like Home Assistant or Homey?

yes, as I'm controlling it direct via home assistant. also the HC app works outside of my Wifi

I had a strange issue last week. my dishwasher lost the connection to my wifi. I have a fritzbox and I had to change my encryption to only WPA2 and not as before WPA2/WPA3.

It seems that the HC service has been stable for a while now so I'm going to close this issue


Fix problem with USER_AFTER_REGISTER_ENDPOINT.

Per #177, this may or may not be correct nor complete.

Hi @carrete! Thank you for your contribution! I am afraid that we can not accept this changes to v0.6 branch as it is not actively developed or maintained. Could you please recreate your branch and specify master as a target? We have exactly the same code here in user_manager__views.py:498 with the same issues.

Well, it seems I can do it myself :sweat_smile:

Hi @and-semakin , I see in the change history above you regarded this pull-request for master and then switched it back to v0.6. What, if anything, do you need me to do?

Hi @carrete! Just wanted to try if it will work :) Source branch (carrete:gh-issue-177) is started from 0.6 so it can not be merged into master without conflicts (file moved):

Could you please start your branch from master? I'm afraid that you will have to manually re-apply the same changes to the new file. If everything goes right than what I mean can be accomplished with the following git commands:
# go to your Flask-User fork repository
cd Flask-User

# change branch to master
git checkout master

# update your fork
git remote add upstream https://github.com/lingthio/Flask-User.git
git pull upstream master

# delete old branch
git branch -d gh-issue-177

# create new branch with the same name from master
git checkout -b gh-issue-177

# manually apply the same changes to `user_manager__views.py`
...

# commit changes
git add flask_user/user_manager__views.py
git commit -m "Fix #177"

# push branch to the same PR
git push --set-upstream origin --force gh-issue-177

I apologize for the inconvenience and the fact that this PR has been in review for so long. I can do it myself, but I really appreciate your contribution and want your name to be under this commit :)
Thank you!

@and-semakin Thanks for your very detailed instructions. How does it look now?


Task :react-native-community_checkbox:compileDebugJavaWithJavac FAILED

Hello guys, thank you for maintaining this project.
Today after upgrading everything (macOS to Big Sur, Xcode and Android studio to latest), when trying to build a plain react-native app for android I get this gradle incompatibility error.
I had just started the app with npx react-native init MyApp
micaelmota@Micaels-MacBook-Pro ios % yarn android
yarn run v1.22.4
$ react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 972 file(s) to forward-jetify. Using 12 workers...
info JS server already running.
* daemon not running; starting now at tcp:5037
* daemon started successfully
info Launching emulator...
info Successfully launched emulator.
info Installing the app...
Downloading https://services.gradle.org/distributions/gradle-6.2-all.zip
.............10%.............20%.............30%..............40%.............50%.............60%.............70%..............80%.............90%.............100%

Welcome to Gradle 6.2!

Here are the highlights of this release:
 - Dependency checksum and signature verification
 - Documentation links in deprecation messages
 - Shareable read-only dependency cache

For more details see https://docs.gradle.org/6.2/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)
> Task :react-native-community_checkbox:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
21 actionable tasks: 21 executed

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-community_checkbox:compileDebugJavaWithJavac'.
> Could not find tools.jar. Please check that /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home contains a valid JDK installation.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2m 51s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Starting the app directly from Android Studio works.


feat(version): enable master branch name to be configured

Add new option for Version to set the name of the release branch - defaults to master.

Issue #, if available:
#146
Description of changes:
Allow for the name of the release branch to be changed.
Currently this option is limited only to the Version component but I was was a bit on the fence whether it would make sense to have a single options called e.g. release-branch that is shared across components.
I see the workflows have an options to define multiple release branches.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I think the GitHub workflows also reference 'master'. No?

Yes, it takes in an array of release branches that default to [ 'master' ].
If we reuse this, would you, on release, push the code & tags to all branches within this array.

If we reuse this, would you, on release, push the code & tags to all branches within this array.

I think the other way around. I would expect the default value for releaseBranches to be aligned with the newly introduced releaseBranch so it works out of the box if I change the release branch to something that's not master.

Perhaps the option should be called main-branch instead.


Initial docs of GitOps repository structure

These examples include the notion of a "base" against which the various envs provide adaptations. The problem with this model is that any change to base will immediately be applied to all envs. Avoiding this effect is error-prone. There are some cases where this model is an acceptable trade-off, but I don't think we should treat it as default.


BC22 - Users created from Setup-BcContainerTestUsers does not have any permission sets

Describe the issue
We use Setup-BcContainerTestUsers to create test users with different licenses and permissions.
In NextMajor (BC22) containers, there are no User Groups since (I guess) the User Group feature is deprecated.
Setup-BcContainerTestUsers seems to use the User Groups to add permissions to the test users, and since there are no User Groups the users does not get any permissions.
Scripts used to create container and cause the issue
Setup-BcContainerTestUsers -containerName $containerName -credential $credential -Password $TestUsersPassword

Full output of scripts
Downloading C:\Users\nabjohwik\AppData\Local\Temp\267f3091-3a2d-41bd-ba17-333c3c547195
Using WebClient
VERBOSE: Preparing to expand...
VERBOSE: Created 'C:\Users\nabjohwik\AppData\Local\Temp\9aaaf62d-bc70-4c75-89bb-d4144ea61f8f\Microsoft_CreateTestUsers_<IP_ADDRESS>.app'.
Publishing C:\ProgramData\BcContainerHelper\Extensions\nextmajor\e0477fb6-7024-434d-acba-3069485cf78c\Microsoft_CreateTestUsers_<IP_ADDRESS>.app
Synchronizing CreateTestUsers on tenant default
Installing CreateTestUsers on tenant default
App Microsoft_CreateTestUsers_<IP_ADDRESS>.app successfully published
Invoke GET on https://<IP_ADDRESS>:7048/BC/api/v1.0/companies?$filter=name%20eq%20%27CRONUS%20SE%27&tenant=default
Invoke POST on https://<IP_ADDRESS>:7048/BC/api/Microsoft/Setup/beta/companies(74629193-f9c9-ed11-94ca-000d3abcda6d)/testUsers?tenant=default
Uninstalling CreateTestUsers from tenant default
Unpublishing CreateTestUsers
App successfully unpublished

Screenshots
N/A
Additional context

does it happen all the time - Yes, for all NextMajor containers
did it use to work - Yes, for BC21
BCArtifactUrl: https://bcpublicpreview.azureedge.net/sandbox/22.0.54157.54644/se

I thought this was due to the new User Group functionality, which is turned on by default, but even if I add
-featureKeys @{ "HideLegacyUserGroups" = "None" }

to New-BcContainer, then it still seems to be a problem.
I have sent the TestUsers app to somebody in the app team to get it compatible with 22

I think the test data in the database has changed. I believe there are no User Groups there, independent of if you are using User Groups or not.
If that's case, then the app needs to be redesigned and permissions added directly on users (or some security group mockup thing). :)
The app needs to be updated to support that User Groups are completely removed in an upcoming major anyways...

It has been redesigned with the change submitted at the same time as you replied:-)

Haha, nice! :)

Shipped in 5.0.0


https.proxyHost / https.proxyPort are not respected

The lack of support to https.proxyHost / https.proxyPort system properties blocks a lot of our usage behind for services on our corporate datacenter who need to use a proxy to communicate to individual external services.
This is also weird for Google's Dataflow projects, where the proxy must be enabled for things like pushing a dataflow template, but it can't be enabled when the workers on Google Compute Engine are being spunned up to run a Pipeline.
It seems https.proxyHost was originally part of the design: https://github.com/google/google-http-java-client/issues/161

Fixed by https://github.com/google/google-http-java-client/pull/361


Replacing existing nodes due to changes does not work

If a node needs replacement (e.g. if the image changes) a uniqueness error occurs:
module.kube-hetzner.module.control_planes["0-0-control-plane-fsn1"].hcloud_server.server: Creating...
module.kube-hetzner.module.agents["0-0-agent-small"].hcloud_server.server: Creating...
╷
│ Error: server name is already used (uniqueness_error)
│
│   with module.kube-hetzner.module.control_planes["0-0-control-plane-fsn1"].hcloud_server.server,
│   on ../kube-hetzner/modules/host/main.tf line 22, in resource "hcloud_server" "server":
│   22: resource "hcloud_server" "server" {
│
╵
╷
│ Error: server name is already used (uniqueness_error)
│
│   with module.kube-hetzner.module.agents["0-0-agent-small"].hcloud_server.server,
│   on ../kube-hetzner/modules/host/main.tf line 22, in resource "hcloud_server" "server":
│   22: resource "hcloud_server" "server" {
│

This is because of lifecycle create_before_destroy but the calculated server_name is the same as the old one.

@ifeulner Did you take down the node with terraform destroy -target ?
Indeed, create_before_destroy does not seem compatible. Let's just remove it.

@ifeulner Please, let me know how you proceeded, that's an important issue, and if you see a quick fix, don't hesitate to push it, otherwise I will take care of it. Thanks 🙏

@mysticaltech the obvious quick fix is to adjust the server name based on a image change. But if that at the end really results in a still-working cluster? I doubt it...
Anyways, I I will push the quick fix later...

@ifeulner Yes, but what I wanted to know is, what how are you tested, is it with terraform destroy -target ?
It is not the first time we tried this, and in my previous testing, it was working. But it might have been before we create implemented the create_before_destroy. So the quick fix will be to remove that!
It is imperative that we are left with a fully working cluster of course!

@ifeulner Yes, but what I wanted to know is how did you test, is it with terraform destroy -target ?
It is not the first time we tried this, and in my previous testing, it was working. But it might have been before we implemented the create_before_destroy. So the quick fix will be to remove that!
Of course, it is imperative that we are left with a fully working cluster!

@ifeulner PR most welcome, I believe just removing create_before_destroy will work, because it is a more or less recent addition and before it worked like a charm when a node was drained, destroyed with target, and terraform re-applied.


Fix get_json_object producing wrong output with wildcard paths

The output of get_json_object is wrong when the json path has a wildcard following by a name instruction. In such situations, the early return statement in the code path processing name instruction may cause the entire output row to be a null, instead of ignoring the child objects that do not contain the desired field.
This fixes the issue by removing the early return statement mentioned above.
Closes https://github.com/NVIDIA/spark-rapids/issues/11172.

build

build

build

build

build

Good catch!


Use cygwin git and ssh on Windows, update ansible script & build/test machines

From discussion in June 5 infra call, sounded like the ansible script for Windows could use some care and attention.
Currently there are some build and test failures relating to the fact that the Windows machines are not configured with cygwin properly.
Side-effects of this misconfiguration means that some builds fail, and some openjdk regression tests (that call .sh scripts) can not be run (or they fail).
It is important to correct this so we have reliable build and test on the Windows platform.

The playbooks already have cygwin.
https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/cygwin/tasks/main.yml
I think the issues we've been seeing are at least partly because they also have Windows Git (& Git Bash) which is not needed imo (please object if I am wrong) and this can get the PATH out of sorts.
https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/GIT/tasks/main.yml
I believe we should

Remove Windows git completely, and use cygwin git.
Change the connection protocol of the machines from JNLP to ssh (cygwin)

The *main reason for the protocol change is because JNLP requires either a human login to the slave and connect it to the master or some extra setup on the slave to run a service to do it automatically. If you connect over ssh, there is no extra manual effort or setup required on the machine.
We have switched to the above setup at Eclipse/OpenJ9 and things are much more stable now.
Related #376 #373 eclipse/openj9#2063
PS. Sorry @smlambert I may have hijacked your issue slightly

Windows machines are not configured with cygwin properly.
Not to my knowledge - it's always been there and configured on all the machines

The windows ansible issues are not related to cygwin

Windows configuration issue is blocking us to complete Add AdoptOpenJDK test pipelines into nightly build  in Eclipse OpenJ9 Jenkins. From what I have tested, I can run .sh scripts in Eclipse OpenJ9 windows machine, but I cannot run the same script using AdoptOpenJDK windows machine.
Link to OpenJ9 win build: https://ci.eclipse.org/openj9/view/Test/job/Test-sanity.functional-JDK8-win_x86-64_cmprssptrs/29/
Link to AdoptOpenJDK win build: https://ci.adoptopenjdk.net/view/work in progress/job/TestBuild_Sandbox2/246/console

What do we need to do to resolve this issue? It's causing a number of downstream problems and blocking other issues from being resolved. I'm not sure if the lack of movement is because a lack of priority or if it's unclear what the next steps are or who should be taking them.

See the comment on https://github.com/AdoptOpenJDK/openjdk-tests/issues/499 I believe that recently enabled new Windowns machine azure: win2012r2-x64-1: {ip: <IP_ADDRESS>, user: adoptopenjdk} do not have this issue. So again question would be "any difference between azure and packet especially configuration with cygwin or jenkins?" Could we configure them in a same way?

I ran a jdk_math using .sh from my local branch on new windows machine test-azure-win2012r2-x64-1 and it passed: https://ci.adoptopenjdk.net/view/work in progress/job/TestBuild_Sandbox/466/
Currently, I am running sanity functional to verify: https://ci.adoptopenjdk.net/view/work in progress/job/TestBuild_Sandbox/467
If everything is ok, I think we should disable the incorrectly configured machine test-packet-x64-windows-2012r2-1 and deliver the change to use same script.

So, I have disabled test-packet-x64-windows-2012r2-1 as its configuration is 'off-brand' from the expected configuration in ansible scripts and defacto standard for test machines at Adopt.
We should recycle test-packet-x64-windows-2012r2-1, as it is not useful/usable.  It would be good to get another windows test machine set up (and configured in the same way the test-azure-win2012r2-x64-1 is, as that is usable).

Just gone back onto the machine and /usr/bin appears pretty much at the start of the PATH (Just after /usr/local/bin from a new cygwin shell, so we might be ok now. WIll re-enable and see if anything breaks on it ...

Windows playbook has been updated enough to get JDK8 working, at least. Through my testing, it seems Cygwin's git is preferable generally as Windows git will have issues when interacting with Cygwin: https://github.com/git-for-windows/git/issues/568
Just as an FYI :-)

I think we can call this done and raise individual issues as needed.   Thanks @Willsparker


[Bug] macOS client sumbit content directly when pressing Enter in Chinese input method

Describe the bug
A clear and concise description of what the bug is.
When typing English using Chinese input method in macOS client, pressing Enter should send the content from the input method into the input box, but the client also submits all the content in the input box to the chat conversation. Please refer to Screenshots section for more details
I've searched the issues, both the macOS client and web version have been reported to have similar bugs and have been fixed. However i am still able to reproduce it across different client/desktop combinations
To Reproduce
Steps to reproduce the behavior:

Download latest macOS client
Set Send Key to Enter
Open a new chat conversation
Switch input method to Chinese
Input any words and press Enter, you shall see the words submitted into conversation

Expected behavior
A clear and concise description of what you expected to happen.
Pressing Enter when typing using Chinese input method should not submit it into the chat conversation
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/assets/4954114/409b82fb-31d4-426d-8ee4-e1d371edd502
Desktop (please complete the following information):

MBP Intel Mid 2015

OS: [macOS Monterey 12.7.3 (21H1015)]
Version: [NextChat Version 2.10.3 (20240207.064246)]

MBP M1 2021

OS: [macOS Sonoma 14.3]
Version: [ChatGPT Next Web Version 2.9.12 (20231117.041037]

Additional Logs
Add any logs about the problem here.

Same here


fix(storage-viewer): don't show hidden categories in all view

closes #1191
Hidden categories are controlled in the storage settings by the hidden category toggle.

sorry to interrupt but I'm kinda having second thoughts about having both options in same toggle (that's why I didn't include it when I created issue). I mean use hide hidden categories or not their motive is to keep the stuff inside it hidden regardless. what are your thoughts?


Add GDEW0583Z83 648*480 B/R

Add this new display that was sent by GOOD DISPLAY and does not seem to be supported anywhere else.
DEMO Code.
WiKi https://github.com/martinberlin/cale-idf/wiki/color-GDEW0583Z83-648x480-B|R

Completed. Soon in next CalEPD release


Error when loading a vite.config.ts file with the sveltekit plugin.

jiti fails to load a vite.config.ts file, when that file calls the sveltekit plugin. (like the one that comes with the sveltekit demo app)
Error
[jiti] [transpile] [esm] /home/nbe/projects/playground/repro-jiti-sveltekit/ts.js (4.032ms)
/home/nbe/projects/playground/repro-jiti-sveltekit/ts.js:5
  exports.ts = ts = (await Promise.resolve().then(() => require('typescript'))).default;

SyntaxError: Unexpected identifier 'Promise'

Reproduction
Here is a minimal reproduction which includes only the single file from the sveltekit repo that jiti errors on. The steps are in the readme.
Questions

Is my understanding correct in that we ideally want to instruct jiti to avoid transforming this file, as it is "already ESM"?
Is it fair to assume that closing #72 will also fix this issue?
Are there any other alternatives I could try to work around this in the meantime?

Context
I was taking a stab at fixing a knip issue which is currently blocked by this error.
Environment
Environment

  System:
    OS: Linux 6.1 NixOS 24.05 (Uakari) 24.05 (Uakari)
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
    Memory: 20.28 GB / 31.13 GB
    Container: Yes
    Shell: 5.9 - /run/current-system/sw/bin/zsh
  Binaries:
    Node: 20.10.0 - /etc/profiles/per-user/nbe/bin/node
    npm: 10.2.3 - /etc/profiles/per-user/nbe/bin/npm
    pnpm: 8.10.5 - /etc/profiles/per-user/nbe/bin/pnpm

I just realized that I forgot to link to the minimal repro 🤦🏼♂
https://github.com/thenbe/repro-jiti-sveltekit

With jiti v2, we have adopted native-ESM support and top level imports supported out of the box for main jiti CLI.


Using glib_wrapper! with Shared twice in the same module fails

Just noticed this looking at the code for glib_shared_wrapper!. The macro defines a pub enum MemoryManager {}, so if it's called twice in the same module, it will error about that type being defined twice.
A failing test case, for completeness:
glib_wrapper! {
    pub struct Shared1(Shared<()>);
    match fn {
        ref => |x| x,
        unref => |x| (),
    }
}

glib_wrapper! {
    pub struct Shared2(Shared<()>);
    match fn {
        ref => |x| x,
        unref => |x| (),
    }
}

Yeah I worked around that in glib/src/param_specs.rs with separate modules but ideally that should be fixed :)

I wonder if using PhantomData<T> where T is an uninhabited type is actually undefined behaviour, strictly speaking

See https://github.com/gtk-rs/glib/pull/715

I wonder if using PhantomData where T is an uninhabited type is actually undefined behaviour, strictly speaking

I think if it were it would be considered a compiler bug, since there's nothing unsafe about constructing a PhantomData or defining an empty type.


Adds support for local dependencies in Projectfile

This implements the possibility to require dependencies from our file system, in addition to GIthub.
It's useful at least for development purposes, since it allows us to work on multiple packages locally.
example:
deps do
  github 'user/repo' # the usual

  local '../my-custom-lib'
  local '../another-lib', 'custom-name'
end

I tried to follow the same approach from the github dependency code. Here's a summary of the decisions I went with:

the directory name will resolve to the name of the last directory specified. So ../path/to/directory will be linked at ./libs/directory. A second parameter can be used to override this, just like with github
it also removes "crystal" preffixes/suffixes from the name
it links directly to libs, and doesn't go through .deps. I figured this wasn't necessary since we're not cloning anything
if the directory is also a git repo, it uses the ref for the version. Otherwise it fallsback to the string "local". I didn't really know what to do here, but I figured we should allow for non-git directories to be used

Other than that, I also refactored the specs a bit, separating the ones from GithubDependency to it's own file (and testing the class directly instead of using Project). I also added my own tests for the new type
I got a bit ahead of myself here, and ended up doing a bit of refactoring. If I went too far, I'll be happy to roll back some of the changes and just stick to the feature itself

:purple_heart: :heart:  :blue_heart: :yellow_heart: :green_heart:
This is awesome! Thanks!!


Signal Desktop faulty version potentially causing data loss

Describe the bug
Just lost on two different NixOS machine my Signal Desktop history because of this faulty update...
I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss
https://github.com/signalapp/Signal-Desktop/issues/4513
To Reproduce
Steps to reproduce the behavior:

Upgrade Signal Desktop
Restart Signal Desktop
Asks you to delete db, if you interact in a wrong way it will delete your data

Notify maintainers
@primeos (@ixmatus and @equirosa)

Just lost on two different NixOS machine my Signal Desktop history because of this faulty update...

Sorry to hear that. I recently lost my history too... It's really frustrating!

I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss

Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers).
AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in pkgs/applications/networking/instant-messengers/signal-desktop/default.nix).

I hate Signals way of dealing with long term conversations and history archival, it sucks - there are no proper ways of dealing with this. @moxie0

Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough.
(I raged a bit here https://social.primeos.dev/notice/A22N5eEVCDrkxyDmwy but after I realized that one cannot even import old backups I had to take a break.)

Just lost on two different NixOS machine my Signal Desktop history because of this faulty update...

Sorry to hear that. I recently lost my history too... It's really frustrating!

I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss

Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers).
AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in pkgs/applications/networking/instant-messengers/signal-desktop/default.nix).

I hate Signals way of dealing with long term conversations and history archival, it sucks - there are no proper ways of dealing with this. @moxie0

Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough.
(I raged a bit here https://social.primeos.dev/notice/A22N5eEVCDrkxyDmwy but after I realized that one cannot even import old backups I had to take a break.)

I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database).
After many things, the easiest fix to ensure proper functionalities IMHO is installing:
pkgs.signal-desktop.override {
  gtk3 = pkgs.gtk3.override { trackerSupport = false; };
}

This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess.
That might not fix everything though :upside_down_face:

FYI, in case anyone has feedback/suggestions: We might merge #117555 soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).

Heads-up: I've just merged #122926 to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup ~/.config/Signal/ first in case the script fails unexpectedly.

Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended


Cannot stream when retrieving metadata

The following demonstrates that a large file fails to stream when metadata is also retrieved:
	XMLDocumentManager documentManager = client.newXMLDocumentManager();
	Transaction transaction = client.openTransaction();
	InputStreamHandle handle = new InputStreamHandle();
	DocumentMetadataHandle metadataHandle = new DocumentMetadataHandle();
	documentManager.writeAs("all_well.xml", new FileHandle(
		new File("test-complete/src/test/java/com/marklogic/client/functionaltest/data/all_well.xml")));
	documentManager.read("all_well.xml", metadataHandle, handle, transaction);
	InputStream stream = handle.get();
	while ( stream.read() > -1 ) {}

The last line just loops through reading the InputStream.  But this line will fail because the stream is closed.

This is closely related to #725

This was discovered from this SO post: https://stackoverflow.com/questions/45302832/read-and-write-using-documentmetadatahandle-and-inputstreamhandle

As reported on SO, this was on the 3.0.7 release.  The 3.0.8 release (OkHttp replacement) appears to have resolved this issue.

Verified on nightly regression and Jenkins servers. Test testStack20170725 in com.marklogic.client.test.DocumentMetadataHandleTest class runs fine and has passed.

I should note that the error is no longer there, but we're not streaming.  OkHttp doesn't come with multi-part response processing so we had to use javax.mail.internet.MimeMultipart which does not stream.


In about this repo

bruce-wiki.vercel.app
404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND
ID: arn1::ck5mz-1659287065013-d1dde01549e4

I changed my domain a few days ago and forgot to update this link in the repository. Try this: https://wiki.bruceworld.top/


improve parallel builds, fixed SEGFAULT for NULL parameter for nc_inq_format(), added testing, documentation

This PR started with adding some testing for ncfunc.c, which revealed a SEGFAULT when a NULL parameter is passed to nc_inq_format(). This is fixed in this PR.
Also I continued work on autotools build system for smoother parallel builds. Many test dependencies are eliminated by ensuring that all tests use unique file names for test output. Parallel builds now work for builds with dap remote tests, and buildfiles are simplified by removal of unneeded dependencies.
Also took out some dead code and added doxygen documentation for the functions I touched.
Fixes #678.
Fixes #677.
Fixes #682.
Fixes #681.
Fixes #670.
Fixes #616.
Fixes #667.
Fixes #687.
Fixes #685.
Fixes #689.
Fixes #688.
Fixes #684.
Fixes #690.
Fixes #695.
Fixes #693.

Why did you remove tst_filters? That's part of the new code added by Dennis for multiple compression filters, I believe.  @DennisHeimbigner is that correct?

Sorry, didn't remove tst_filters, remove tst_formats. Just mistyped it in git commit comment. ;-)
I added tst_formats.c and am having some trouble getting it to work with travis. I also added a ref_.hdf4 file, and that seems to be part of the trouble. I will keep working it until I figure it out...

The file test_filters is part of the filter_test directory.
There is a specific ./configure flag to control if the tests
in filter_test are attempted: --enable-filter-tests
This defaults to off because this test is a bit tricky to run
automatically and as far as I recall, I was never able to get it to
run under cmake.
It looks like the equivalent option is not defined in CMakeLists.txt.
It should be and it should default to off. The relevant place it hould be used
is in nc_test4/filter_test/CMakeLists.txt.
See  how it is used in nc_test4/filter_test/Makefile.am.

OK, this is now working for both autotools and cmake builds.
As noted above, I did NOT remove tst_filters, just mistyped "tst_formats" in a commit comment. No tests were harmed in the production of this pull request.
The new tst_foramats is added to test nc_inq_foramt() and nc_inq_format_extended().

This PR is also passing my ARM-based testing.

I just merged in two other open PRs and closed them, to combine code for testing.
Re-running all tests now...

Evaluating now, thanks!

CMake configuration breaks using my automated scripts on Windows, but probably something basic.  I'll investigate.

OK, keep me in the loop. I am happy to revert some files to eliminate the problem and get the rest of the changes through, then I can circle back around to the problem area.
Unfortunately windows is the one giant gap in my CI. I don't have a windows machine with visual studio. Not sure if there is a free version I can use or whether I need to buy one...

The issue is only on Windows, so I'm sure it's pretty straightforward; I'll outline what I find and if it's something I can't fix myself. First avenue of investigation is my automated tools to see if they're doing something they shouldn't, now.

Ed, FYI the community edition of Visual Studio is free.

I have found an old windows laptop. I will fire it up and see what I can manage wrt visual studio community edition. ;-)

No prob I had to set this aside suddenly yesterday (son sick at school) but sitting down to it now:)

I found the issue, it's no big deal, when MSVC is true a property is being set that doesn't need to be set.  This is from some older cmake code that could do with cleaning up; cmake has come a long way since we started using it, plus I can refine a lot of what's been done.  I'll take care of it and get this merged, thanks!

Also FWIW I do my debugging/testing for Windows in a Win10 VM using VirtualBox, with no ill effects.

Well the problem with virtual machines is: when you get mad, what do you
kick? ;-)
On Wed, Nov 29, 2017 at 12:17 PM, Ward Fisher<EMAIL_ADDRESS>wrote:

Also FWIW I do my debugging/testing for Windows in a Win10 VM using
VirtualBox, with no ill effects.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/pull/680#issuecomment-347966258, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEUr3Oi3mCWCBMcZvLSqAc3pYQx_uQFRks5s7a3BgaJpZM4QnvDn
.

@WardF hope your son is feeling better. ;-(
Meanwhile I have been working on PIO issues all day so still have not yet set up a test environment...

Running mpich parallel tests and then will merge.  @edhartnett one thing our (docker-based) regression testing does is it tests the Fortran, C++ and Python interfaces, as well as NCO (for non parallel builds) and parallel-netcdf (for parallel builds) against the particular C library being generated.  I don't know if that's something your Jenkins build is set up to do, and to be honestly it only rarely finds an issue, but it is pretty handy when it does.
Thanks!


[BUG] Set-PnPWebPermission: The parameter "Identity" is declared in parameter-set "__AllParameterSets" multiple times.

Hello there heroes!
I have migrated my scripts to the preview of PnP.PowerShelll this week. After running one, I noticed that the Set-PnPWebPermission cmdlet isn't working at all. Also, the documentation is missing. The page exists, but it shows a copy of the Set-PnPWebPartProperty documentation...
Expected behavior
The cmdlet runs :)
Actual behavior

Missing documentation
No auto-complete in the terminal
An error is thrown, even when the proper parameters are given:

 Set-PnPWebPermission : The parameter "Identity" is declared in parameter-set "__AllParameterSets" multiple times.
At line:1 char:1
+ Set-PnPWebPermission -
+ ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : MetadataError: (:) [], MetadataException
    + FullyQualifiedErrorId : ParameterDeclaredInParameterSetMultipleTimes

Steps to reproduce behavior
Connect-PnPOnline -Url https://contoso.sharepoint.com -PnPManagementShell
Set-PnPWebPermission -User me -AddRole Read

or
Connect-PnPOnline -Url https://contoso.sharepoint.com -PnPManagementShell
Set-PnPWebPermission

or
Connect-PnPOnline -Url https://contoso.sharepoint.com -PnPManagementShell
Set-PnPWebPermission -Identity someweb

What is the version of the Cmdlet module you are running?
0.3.7
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

good catch! Working on it as we speak.

Fixed! It will be available in 0.3.13-nightly which will be available tomorrow.

You rock 👍

It would be really nice to have the -url parameter back for working with subsites.  Where can I make that request?

I want to grant a user permission so i used following command
#Parameters
$SiteURL = "https://.sharepoint.com/"
$UserAccount =<EMAIL_ADDRESS>$PermissionLevel = "Edit"
#Connect to PnP Online
Connect-PnPOnline -Url https://****.sharepoint.com/ -Interactive
#grant permission Level to the user
Set-PnPWebPermission -User<EMAIL_ADDRESS>-AddRole Edit
But eveytime Permission level not found error will occur
Any idea why i am getting this error although i tried with different permission level such as Contibute, Owner,Member still getting the same error

I want to grant a user permission so i used following command #Parameters $SiteURL = "https://.sharepoint.com/" $UserAccount =<EMAIL_ADDRESS>$PermissionLevel = "Edit"
#Connect to PnP Online Connect-PnPOnline -Url https://****.sharepoint.com/ -Interactive
#grant permission Level to the user Set-PnPWebPermission -User<EMAIL_ADDRESS>-AddRole Edit
But eveytime Permission level not found error will occur Any idea why i am getting this error although i tried with different permission level such as Contibute, Owner,Member still getting the same error

Check the site language, permission levels are translated for some reason. In my case, my sites are in Dutch so my permissions are also in Dutch.


build: increment API_VERSION after release

With v2.5.0 out, increment API_VERSION, so binaries dynamically linked against
the released raylib aren't accidentally paired with a development or later
released raylib that may be incompatible.

Issues was discussed multiple time in the past (see #613 for an example).
The intention here is not to change raylib's versioning scheme, just the compatibility/API version evaluated by the dynamic loader.

@a3f Thanks for the improvement and excuse me ignorance on this versioning issue...

No worries, it took me quite some time (and one last comment by @jubalh) to wrap my head around the issue ^^'.


Pausing indexing

I recently bumped into a problem. I have to go through a model and update some fields. With every save, it will call the ES server to update, and it will slow things dramatically. Is there a way to pause the indexing for specific block of operations ?
I noticed  something similar in Laravel Scout : https://laravel.com/docs/5.4/scout#pausing-indexing
App\Order::withoutSyncingToSearch(function () {
// Perform model actions...
});
Thanks in advance !

Hi,
you can set public property $syncDocument to false on your model:
public $syncDocument = false;

as @mschreck indicated the only available way at the moment is to toggle the syncDocument key on your model $model->syncDocument = false


Twig_Template::display should be refactored

I just had a nice little debug session to find out why all globals are gone after upgrading to Twig 1.4.
Following Fabien's suggestion regarding issue #302 I have extended the Template class to implement display() without the try/catch. (In out setup we need the original exceptions thrown by objects accessed from within Twig templates.)
Now with Twig 1.4 the original display method contains some extra code to merge the globals into the template's context ,which was of course missing in my overriding implementation.
An obvious solution would be to copy the globals-related code into my implementation. But that is dirty and likely to break with future releases of Twig.
In my view the root cause of this problem is that the new display method does two things. No matter how short it may be, from a 'clean code' perspective it does two things on different levels of abstraction and these things should be factored out into separate methods:
/**
 * {@inheritdoc}
 */
public function display(array $context, array $blocks = array())
{
    $context = $this->mergeContextWithGlobals($context);
    $this->displayWithErrorHandling($context, $blocks);
}

/**
 * @param array $context
 * @return array
 */
protected function mergeContextWithGlobals(array $context)
{
    // we don't use array_merge as the context being generally
    // bigger than globals, this code is faster.
    foreach ($this->env->getGlobals() as $key => $value) {
        if (!array_key_exists($key, $context)) {
            $context[$key] = $value;
        }
    }
}

/**
 * @param array $context
 * @param array $blocks
 */
protected function displayWithErrorHandling(array $context, array $blocks)
{
    try {
        $this->doDisplay($context, $blocks);
    } catch (Twig_Error $e) {
        throw $e;
    } catch (Exception $e) {
        throw new Twig_Error_Runtime(
            sprintf('An exception has been thrown during the rendering of a template ("%s").',
            $e->getMessage()),
            -1,
            null,
            $e
        );
    }
}

Some might argue this is over-explicit. But it's hard to deny that it makes the intent of the code clearer and it does allow to override the error handling without quirky duplication of code.

done: fc85a1688


Example project crashes when unplugging the external screen

Setup
Windows 10 notebook with one GPU
External monitor connected by HDMI or by docking station (set as primary screen)
Observed behavior
The GLWpfControl.Example project crashes with an UCEERR_RENDERTHREADFAILURE exception when I unplug the external monitor or a dockingstation with an external monitor connected.
See also my comment on #30.

Relates to #30 and #22.

Moving to 4.3.1.

Related to #30 which is moved to 4.3.3

Didn't get to the multi-monitor/multi-gpu issues this version. But hopefully next version we can fix this.


multi-line promise toasts change height on hover when using expand

<Toaster expand={true} />

toast.promise(Promise.resolve(), { success: 'This my very very very very very very very very very very very very very very very very very very very very long and descriptive promise toast!!!' })

when hovering over these toasts, they will change height as their top paddings will disappear, causing weird layout shifts, it looks very ugly

this has been fixed

+1 on this for me. Will be awesome to get this one fixed since this is such a beautiful modal implementation.

WIll look into it this week

Hey y'all, can any of you provide a demo of this? I can't replicate / notice the shift

@wobsoriano hey sorry, this error report is inaccurate, the reproduction steps are actually as follows:
<Toaster expand={true} />

toast.promise(Promise.resolve(), { success: 'This my very very very very very very very very very very very very very very very very very very very very long and descriptive promise toast!!!' })

it happens only with promise toasts, not normal toasts

Are you still getting it with the latest version @ThaUnknown?

@wobsoriano seem like I'm still getting this issue on 0.3.6 sadly when there's only one toast item:
https://github.com/wobsoriano/svelte-sonner/assets/7515754/34084531-140d-4442-8cc4-da0e65a22c6e

I'm not able to reproduce with the latest version, is anyone able to reproduce or should this be closed?

I can still reproduce this, I'll make some minimal test case later

repro.zip
this issue happens when the error/success has more lines than the pending text, I've attached a stupidly simple reproduction case, which runs on body click

@ThaUnknown can you use https://stackblitz.com or https://codesandbox.io/ to create a repro?

you can simply paste the files into stack blitz yourself

I can still repro this, too
https://stackblitz.com/edit/vitejs-vite-gtdpxr?file=src%2FApp.svelte

Thanks for the repro @jakob-kruse, will look into this!

This definitely helps!

This is a very beautiful tool and certainly elevates any Svelte app's experience! 10/10 except for this one small issue, is there a temporary fix that we can use?

@jakob-kruse thanks for the repro! It's now fixed in 0.3.19
https://stackblitz.com/edit/vitejs-vite-d7j7sy?file=package.json


feat: switch to dnf5 as default backend

Needs testing

idk why we need this but mado keeps insisting


Font Awesome Icons in Sidebar too large

Here you see a comparison of the default nebular icons and a font awesome icon in the sidebar.

Where do I have to put my CSS to fix this? I could also help with a pull request.

@tylkomat  I just overwrite the styling by adding this to style.scss:
.nb-theme-default nb-menu .menu-item .menu-icon.fa {
  font-size: 2rem;
}

not working

@nain1-look  I tried it on the older version. Are you using the latest version?

@nain1-look I tried it on the older version. Are you using the latest version?
Hey @weijyewang
yes, angular 7 version, latest version

@nain1-look I tried it on the older version. Are you using the latest version?

.nb-theme-corporate nb-menu .menu-item .menu-icon.fa {
  font-size: 1.5rem;
}

I tried this, its still not working

@shadabk92  I was talking about nebula version and ngx-admin version. I'm using Angular 7 as well. My solutions above was tested with nebular 2.0.0-rc.6, pretty old version

If you installed the newer ngx-admin recently you would have to inspect the element and overwrites the styling using your own selector

@shadabk92 I was talking about nebula version and ngx-admin version. I'm using Angular 7 as well. My solutions above was tested with nebular 2.0.0-rc.6, pretty old version

If you installed the newer ngx-admin recently you would have to inspect the element and overwrites the styling using your own selector

So what is the fix for this, I am actually deploying it for some production work

It worked with 3.4.2, I added the style hack fix in
<EMAIL_ADDRESS>

Worked for me.  Thanks.
I am using the cosmic theme and a newer version of font awesome so I used:
.nb-theme-cosmic nb-menu .menu-item .menu-icon.fas {
font-size: 1.5rem;
}


Missing single-edge paths between two junctions

Some paths consisting of only 2 nodes are missing in Skeleton.paths_list(), depending on the order the nodes ares visited.
Here is a simple script that shows the problem, with a simple (10,10) skeleton and its rotated version. The path list for figure 1 is
[[1, 2, 3],
[3, 4, 5, 6, 7, 8, 9],
[3, 10, 11],
[11, 12, 13, 14],
[11, 17],
[15, 16, 17],
[17, 18, 19, 20, 21]]
and the path list for the graph of figure 2 is:
[[1, 3, 5],
[2, 4, 8],
[5, 6, 7],
[5, 13, 15, 17, 19, 20, 21],
[7, 14, 16, 18],
[8, 9, 10, 11, 12]]
In the first figure, path (11,17) is found, but the equivalent path (7,8) was not found in figure 2.

Here is the script that was used to generate this example.
import numpy as np
import skimage
from skan import csr, draw
import networkx as nx
import matplotlib.pyplot as plt

I = np.zeros((10, 10))

rr, cc = skimage.draw.line(4,0,4,2)
I[rr, cc] = 1
rr, cc = skimage.draw.line(3,2,3,5)
I[rr, cc] = 1
rr, cc = skimage.draw.line(1,2,8,2)
I[rr, cc] = 1
rr, cc = skimage.draw.line(1,0,1,8)
I[rr, cc] = 1

skeleton1 = csr.Skeleton(I)
paths1 = skeleton1.paths_list()

# skeleton of the transposed image
skeleton2 = csr.Skeleton(I.T)
paths2 = skeleton2.paths_list()

plt.ion()
draw.overlay_skeleton_networkx(skeleton1.graph, skeleton1.coordinates)
draw.overlay_skeleton_networkx(skeleton2.graph, skeleton2.coordinates)

print(paths1)
print(paths2)

Wow, that is indeed a bug @ssavary, and I just confirmed that it is still on main (I had suspected that #143 would have fixed it, but no!). I'll try to investigate in the coming days. Obviously if you encounter any further hints please let us know!

I think that the condition if not visited[node]: in the _build_paths function is the culprit, because node 8 had already been visited by path [2, 4, 8] when the first loop looks at node 7. If I correctly follow the code, the order of operations is

first node is 1, generate path [1, 3, 5]. Mark 5 as visited (plus intermediary nodes). No more neighbour to visit.
next node is 2, generate path [2, 4, 8]. 8 is marked as visited. No more neighbour to visit.
next node is 5, generate path [5, 6, 7]. 7 is marked as visited.
generate path [5, 13, 15, 17, 19, 20, 21].
next node is 7, its immediate neighbour 8 has already been visited. Skip to next neighbour (14)
generate [7, 14, 16, 18]. No more neighbour to visit for node 7
finally, generate path [8, 9, 10, 11, 12].

I think that by changing the "visited" variable from a node-based cache to an edge-based (bidirectional) cache would fix the problem, since it's not nodes that we don't want to visit twice, but edges.

@ssavary This is now fixed on main! :tada: Thank you very much for the report and for the analysis — it was spot on! I'd gone through so many hoops with off-by-one errors because I was looking at nodes rather than edges! :facepalm: :joy: One of those seemingly small conceptual changes that make everything clearer! :blush:


Seperate extensions libraries into smaller extension libraries

There should be multiple extension libraries.
FluentHttp.Extensions.Json
FluentHttp.Extensions.Multipart
FluentHttp.Extensions.Testing
etc

Seperated Json into another package.
Multipart became a part of the core package.
Testing will be a seperate update


Support ANP with ICMP Rule

With this PR, Nephe will support icmp protocol in Antrea NetworkPolicy. Its enabled for both AWS and Azure Cloud. Both ICMP-ALL and ICMP-Custom are supported. With ICMP-Custom, user can specify ICMP-Type and ICMP-Code for more granular control.

/nephe-test-e2e-kind

/nephe-test-e2e-kind

/nephe-test-e2e-kind

/nephe-test-e2e-agentless

/nephe-test-e2e-agentless-upgrade

/nephe-test-e2e-aws-upgrade

/nephe-test-e2e-aws-upgrade


[createLayout] Cannot read property 'indexOf' of undefined

Trying to run example of layouts package, but it throws following error:
 Cannot read property 'indexOf' of undefined
Here is the codesandbox example

Hey, Can you take a look at the item format that the PG expects? You can use the playground and it's code.
Furthermore, you can now use the blueprints package which wraps all the logic around the formatting of the container, options, items and returns the blueprint: {items, options, dimensions, structure} where the structure is the layout the the layouter created from those arguments.


MsgWithdrawFunds Concerns

MsgWithdrawFunds includes an IsRefund boolean field:

When true, funds are sent from the project's account (in the project) to the message signer
When false, funds are send from the signer's account (in the project) to the message signer

For each project, the project's account is a single general account, so this means that once the project reaches the 'PAIDOUT' stage, there will be a race to get the funds out of this project account. Since this message can be signed by anyone, even signers not involved with the project can participate in this race. This is very concerning.

Closed by #87


[Feature request] LNURL-withdraw

I notice that Alby Go it doesn't support LNURL withdraw feature.
It can be added in the "Receive" button, with a little scan QR icon, for better understanding by the users.
I tried also to use the "Send" QR scanner but it doesn't recognize the LNURL-w.
It's a nice feature and useful in many cases. It should be added to Alby Go.

This was just merged and will be in the next release :rocket: https://github.com/getAlby/go/pull/158


weights/download.sh only downloads content of nextcloud page.

The wget command should probably be wget -O resnet_50-f46c1a4159.pth https://nextcloud.mpi-klsb.mpg.de/index.php/s/3Yk6p86SBBFYSBN/download

Thank you very much for the fix!


[request] a reload command to refresh configs after changes are made

Development of phishlets could be made smoother by providing users a reload command that re-reads main configs and  phishlet yaml.

Agreed! I have this in the back of my head to eventually implement. Thanks!
Will make it official now.

[war] failed to load certificate files for phishlet 'linkedin', domain 'myowndomain2.com': open /root/.evilginx/crt/myowndomain2.com/linkedin.crt: no such file or directory
[01:51:22] [inf] requesting SSL/TLS certificates from LetsEncrypt..

I understand this command is not yet availble but is there any other work around, because i made som changes in yaml file and i cant see any changes whatsoever (no positive or negativ effect). so im wondering ho do i test that it is working or not?
thx in advance


Created address class for address specific styles

Address styles applied to new class.
Related to #89

@fuhton This looks good to merge on my end. If this is good on your end as well, let's merge.


Credentials - parsing error when running gptscript with tools that have credentials.

gptscript version v0.0.0-dev-f4284f43-dirty
Steps to reproduce the problem:

Run the following gptscript that uses a tool with credentials.

Tools: github.com/sangee2004/slack

search messages in slack and list all messages that have mentioned Disney in the past month

I am prompted to enter the slack token as expected and tool executes successfully.
Run the gptscript again.

This fails with the following parsing error:
09:39:34 started  [main]
09:39:35 sent     [main]
2024/04/12 09:39:35 failed to get credentials for tool slack-credential-tool: error parsing tool name and context "". Tool names cannot contain '///'

Note - Once I remove the config.json that stores the credentials , then I am able to execute the script again.

@sangee2004 fix is merged

Tested with gptscript version v0.0.0-dev-5a8a685c-dirty
This issue is not see anymore.
When the scripts that uses  tools that have github credentials are run the second time , we are not prompted for credentials and credentials from cache gets used successfully.


-b flag broken in release 0.8.24

When running embulk with -b flag, the following error occurs:
NameError: undefined local variable or method bundle_path index' for main:Object`
I believe this is a bug (undefined variable), introduced here:
https://github.com/embulk/embulk/commit/09cd22e929c9652bf82854cd23da99fd4aa74c62#diff-b63a1c764c39ff316cef4fd26d70b97aR6

Ah, sorry, I overlooked this issue. Taking a look.
Can you share your environment (OS, etc), and the command-line you ran?

Ah, but bundle_path_index is definitely a bug... Okay, will fix. Thanks for reporting.

Hmm? But that file (commit) is already fixed in #604. The current embulk_bundle.rb is https://github.com/embulk/embulk/blob/6155ec0901be467d2525768a45121549f500b09a/lib/embulk/command/embulk_bundle.rb.
Again, can you share your environment (OS, etc), and the command-line you ran? @bcipolli

Sorry, I's confused. Removed a comment. 09cd22e is fixed, but the line is alive finally. Will fix.

Being fixed in #681, and releasing v0.8.25 with the fix.

@bcipolli Released v0.8.25. This issue should be fixed there -- can you try, and reopen this if the problem is still there?