Cannot distinguish 2 sequential action dispatch calls

Describe the bug
When verifying that 2 actions have been dispatched from a redux store in a redux middleware one after the other, the verify function cannot distinguish the 2 actions, i.e. any of the 2 actions will match 2 calls instead of 1 each.
To Reproduce
lib/middleware.dart:
import 'package:equatable/equatable.dart';
import 'package:meta/meta.dart';
import 'package:redux/redux.dart';

List<Middleware<AppState>> getHomeMiddleware() => [
      HomeMiddleware().getMiddlewareBindings(),
    ].expand((x) => x).toList();

class HomeMiddleware {
  List<Middleware<AppState>> getMiddlewareBindings() => [
        TypedMiddleware<AppState, TriggerAction>(_handleTriggerAction),
      ];

  void _handleTriggerAction(Store<AppState> store, TriggerAction action, next) {
    next(action);

    store.dispatch(DispatchedA());
    store.dispatch(DispatchedB());
  }
}

@immutable
class TriggerAction {
  @override
  String toString() {
    return 'TriggerAction{}';
  }
}

@immutable
class DispatchedA {
  @override
  String toString() {
    return 'DispatchedA{}';
  }
}

@immutable
class DispatchedB {
  @override
  String toString() {
    return 'DispatchedB{}';
  }
}

class AppState extends Equatable {
  @override
  List<Object> get props => [];
}

test/middleware_test.dart:
import 'package:flutter_test/flutter_test.dart';
import 'package:demo/middleware.dart';
import 'package:mocktail/mocktail.dart';
import 'package:redux/redux.dart';

void main() {
  setUpAll(() {
    registerFallbackValue(TriggerAction());
    registerFallbackValue(DispatchedA());
    registerFallbackValue(DispatchedB());
  });

  test('This is the test that fails', () async {
    final store = StoreMock();

    await getHomeMiddleware().call(store, TriggerAction());

    verify(() => store.dispatch(any<DispatchedA>()));
    verify(() => store.dispatch(any<DispatchedB>()));
  });
}

class StoreMock extends Mock implements Store<AppState> {}

extension MiddlewareExtension on List<Middleware<AppState>> {
  Future<void> call(Store<AppState> store, dynamic action) async {
    for (final middleware in this) {
      await middleware.call(store, action, (_) {});
    }
  }
}

Steps to reproduce the behavior:

Run flutter test
See error

Expected behavior
Test passes.
Logs
package:test_api                           fail
package:mocktail/src/mocktail.dart 722:7   _VerifyCall._checkWith
package:mocktail/src/mocktail.dart 515:18  _makeVerify.<fn>
test/middleware_test.dart 19:11            main.<fn>

No matching calls. All calls: [VERIFIED] StoreMock.dispatch(DispatchedA{}), [VERIFIED] StoreMock.dispatch(DispatchedB{})
(If you called `verify(...).called(0);`, please instead use `verifyNever(...);`.)

Additional context
Tested on Mocktail versions 0.2.0 and 0.3.0.
Commenting out any of the 2 verify checks makes the test pass, so the checks both work on their own.
Adding .called(2) to any of the 2 verify checks and commenting out the other check makes the test pass, so it seems there is no distinction between the 2 different actions.

Hi @ch-angelino 👋
Thanks for opening an issue!
Are you able to provide a link to a minimal reproduction sample? It would be much easier to help if I could clone a working reproduction sample and run/debug it locally, thanks! 🙏

Hi @felangel 👋
Here you go: https://github.com/ch-angelino/Flutter-Mocktail-Bug-Demo-122
Just clone the repo then go flutter pub get and flutter test and the error should come up 🤞
Thanks for looking into this 🙏

Hi @felangel 👋
Here you go: https://github.com/ch-angelino/Flutter-Mocktail-Bug-Demo-122
Just clone the repo then go flutter pub get and flutter test and the error should come up 🤞
Thanks for looking into this 🙏

Thanks I’ll take a look tomorrow morning!

Hey @felangel, any update on this? TIA

Hi @ch-angelino is this still an issue? I'm really sorry I didn't have time to look and it fell off my radar :(

@felangel I just tested that repro repo on Mocktail 1.0.3 and Flutter 3.13.9 and the same error is still coming up:
% flutter test
00:05 +0 -1: Fail 1 [E]
  No matching calls. All calls: [VERIFIED] StoreMock.dispatch(DispatchedA{}), [VERIFIED] StoreMock.dispatch(DispatchedB{})
  (If you called `verify(...).called(0);`, please instead use `verifyNever(...);`.)
  package:matcher                            fail
  package:mocktail/src/mocktail.dart 728:7   _VerifyCall._checkWith
  package:mocktail/src/mocktail.dart 519:18  _makeVerify.<fn>
  test/middleware_test.dart 19:11            main.<fn>


firebug.next's ajax view in the console is horrible

In firebug, ajax calls are logged to the console (if you have the setting turned on) and clicking on the call will expand it and let you view the request using the same view as in the Network tab.
Firebug.next is similar to the developer tools and instead of expanding it, it opens it up in a popup that is pretty difficult to read.  It also doesn't format json reponses nicely (it does in the Network panel but not the Inspector panel)
Firebug.next also shows all network traffic in the Inspector panel instead of just ajax calls.  It would be nice to limit to just ajax calls like it is in firebug.

@janodvarko Could be worth to share the xpi so people could share their feedback. What do you think?
Florent

Yes, I'll release alpha 8
Honza

$fixed firebug-3.0.0-alpha.8


IGNITE-19769 Ignite Docs: change ignite-spring-data-2.2-ext to ignite…

…-spring-data-ext
Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[ ] There is a single JIRA ticket related to the pull request.
[ ] The web-link to the pull request is attached to the JIRA ticket.
[ ] The JIRA ticket has the Patch Available state.
[ ] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[ ] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[ ] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

LGTM


Performance: brush/eraser tool gets laggy

Both segment and broad brush lag after drawing for awhile.

Performance issues while drawing a long "blob". As you continue the frame rate / update rate for drawing seems to drop. - Andrew


BREAKING: HA 2023.4 (beta) no longer uses app-drawer-layout

breaking all custom cards that use this functionality
please see #beta in Discord.
app-drawer-layout was replaced by mwc-drawer
link to Discord: https://discord.com/channels/330944238910963714/427516175237382144/1090920193947074642
I did test the fix that is mentioned, to replace
querySelector("app-drawer-layout partial-panel-resolver")
with
querySelector("app-drawer-layout partial-panel-resolver, mwc-drawer partial-panel-resolver")
but can only replace
app-drawer-layout in the .js file with mwc-drawer and that does Not fix the card

Hi @Mariusthvdb,
In HA 2023.4 not only app-drawer-layout has changed. There are multiple changes there so it cannot be fixed by just changing that selector.
I‘ll let this issue open until a version that supports HA 2023.4 is released.
Regards

Please do, Bram also announced new changes are to be expected.
Don't know which, maybe Kiosk mode devs can connect with Bram cs.

amazing, thank you very much, please release!

Hi @Mariusthvdb,
NemesisRE should be back soon and he will take care of the releases, for now you can do this to test it:

Clone the repo: git clone git@github.com:NemesisRE/kiosk-mode.git
Checkout the branch git checkout prepare_for_ha_2023.4
Run yarn yarn install
Build the plugin yarn build
Copy the JavaScript file in dist/kiosk-mode.js
Test it manually

Take into account that branch has all the changes contained in https://github.com/NemesisRE/kiosk-mode/pull/25 https://github.com/NemesisRE/kiosk-mode/pull/26 and https://github.com/NemesisRE/kiosk-mode/pull/28
Regards

@elchininet ,
I compiled the new kiosk-mode.js from the branch, removed the old one and replaced with the new one:
kios_mode not working and I get the following errors in the log:
https://***/hacsfiles/kiosk-mode/kiosk-mode.js:1:5302 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
https://***/hacsfiles/kiosk-mode/kiosk-mode.js:1:5206 Uncaught TypeError: Cannot read properties of null (reading 'shadowRoot')

Thanks

Hi @gateriderz,
In which version of HA are you testing?
Also if there is a longer stack trace it will be helpful.
I will take a look ai it later in the afternoon.
Regards

Hi @elchininet,
Thanks for your quick reply.
I run Home Assistant 2023.4.0b2
This is the only trace I have under my logs:
2023-03-31 08:30:20.393 ERROR (MainThread) [frontend.js.latest.202303300] https://***/hacsfiles/kiosk-mode/kiosk-mode.js?hacstag=497319128178:1:5302 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
2023-03-31 08:30:20.425 ERROR (MainThread) [frontend.js.latest.202303300] https://***/hacsfiles/kiosk-mode/kiosk-mode.js?hacstag=497319128178:1:5302 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')

Thanks @gateriderz,
I thought that the error was in the current version. The branch is prepared for 2023.4.0b1, during the development of the new version I‘ll be modifying it until the final 2023.4 is released. I‘ll check the changes in 2023.4.0b2 and I‘ll apply them to the branch.
Regards

Hi @gateriderz,
I cannot reproduce it in 2023.4.0b2. Please verify that you have the correct version.
Go to the Chrome dev tools, Network tab, filter the resources by kiosk and select kiosk-mode.js. Then search in the code for APP_TOOLBAR, make sure that you get t.APP_TOOLBAR = "app-toolbar, .toolbar".
Let me know if that is the case and I‘ll try to debug further what is happening.
Regards

Can you deploy a beta?

Things to consider:
Menu swipe in from the left is removed from the app.
Hence the hamburger menu is the only way to reach the menu.
It might be a good idea to notify users about that.
Also, it would be awesome if somehow the swipe could be found a way back in Kiosk mode ;/)
Don't know if at all possible ...

n you deploy a beta?

Hi @nelsonamen, the releases will be done when the owner of the repo is back. For now you can try it with the explanation that I gave above.
Regards

Things to consider:
Menu swipe in from the left is removed from the app. Hence the hamburger menu is the only way to reach the menu.
It might be a good idea to notify users about that. Also, it would be awesome if somehow the swipe could be found a way back in Kiosk mode ;/)
Don't know if at all possible ...

Yes, that would require a change on the README with an statement that what occurs if one hides the sidebar.
About enabling the swipe from the plugin, that would require more than simple CSS clases, but depending on the final structure of the elements it could be achievable.

Hi @gateriderz, I cannot reproduce it in 2023.4.0b2. Please verify that you have the correct version. Go to the Chrome dev tools, Network tab, filter the resources by kiosk and select kiosk-mode.js. Then search in the code for APP_TOOLBAR, make sure that you get t.APP_TOOLBAR = "app-toolbar, .toolbar". Let me know if that is the case and I‘ll try to debug further what is happening. Regards

Thanks @elchininet , you are correct, I had to reload the kiosk-mode.js again by adding kiosk-mode.js?v1 at the end.
The code shows the proper information:

Perfect @gateriderz,
Please, let me know if you have any issue testing it with the new version.
Regards

Hi,
Is it possible to have a tutorial to make Kiosk-Mode work?
I don't understand anything explained here.
What should be replaced?
Where to find the files, or to install them?
Thx

Maybe we should have a bit of patience . Why not let the devs here await coming days of Frontend changes until release of HA 2023.4 so we have some certainty things won't break shortly after.

Hi,
Is it possible to have a tutorial to make Kiosk-Mode work?
I don't understand anything explained here.
What should be replaced?
Where to find the files, or to install them?
Thx

Hi @Jeremyhu102,
You would require a bit of knowledge about Git and working with terminal commands to build the bundle with the steps that I left before and then you can follow the Manual installation instructions (after uninstalling the original plugin). But as @Mariusthvdb mentioned, you can wait until Home Assistant 2023.4 is released and the owner of the repo has released a version to support it.
Regards

For those that do not know how to compile the plugin using the code in the working in progress branch, here you are a gist with the compiled version. You can use this code until the new version is released.

And notice this
OK, I know you will all hate me for doing this, but believe me it is better to do it now then later 😬
We will rename mwc-drawer to ha-drawer during the beta (hopefully next beta)
This means all custom cards that where updated to mwc-drawer should now be updated again to ha-drawer

where to find mwc-drawer ?
In kiosk-mode.js I can not find it

where to find mwc-drawer ?
In kiosk-mode.js I can not find it

Why do you want to find mwc-drawer? This is needed only by someone that wants to change the code of the plugin.
But anyway, if you want to find it, it is not in the current kiosk-mode.js because that element its being added in Home Assistant 2023.4, you need to search for it in the new version that its being prepared in the branch or in the guist that I posted before.

And notice this
OK, I know you will all hate me for doing this, but believe me it is better to do it now then later 😬 We will rename mwc-drawer to ha-drawer during the beta (hopefully next beta) This means all custom cards that where updated to mwc-drawer should now be updated again to ha-drawer

@Mariusthvdb,
It is better to do the changes when they are released, if it is just a plan it could be changed, as almost everything during development. When the next version is released, if it has more changes, the library should be changed to support them.

@Mariusthvdb,
In version 2023.4.0b5 the mwc-drawer element has been renamed to ha-drawer as Bram commented on Discord. The changes have been pushed to the development branch and also to the public gist with the compiled version.
Regards.

great!
Ive dl'd the gist, and all seems to be working swell.
Ill add the new options next (hiding the menu items) and will test those, because that will be a major upgrade!

So this all works just fine!

great, and congrats!
there is but 1 gripe.... might be an edge case, as I probably will always want tp have at least 1 menu item there, but hiding all menu items takes away the whole triple dot icon.
and, that is the anchor for my menu item template using card-mod-themes:
      /* Optionally set the three-dots transparency,
         to allow for a replacement template text. */
      ha-button-menu {
        color: {{'transparent' if is_state('input_boolean.menu_options_template','on')}};
      }

      /* Optionally set a replacement template text. */
      ha-button-menu::before {
        content: "{%- if is_state('input_boolean.menu_options_template','on') %}
                  {{- states('sensor.buienradar_symbol')}} |
                  {{- states('sensor.buienradar_temperature')}} °C
                  {%- endif %}";
        color: var(--app-header-text-color);
        visibility: visible;
        position: relative;
        top: 24px;
        white-space: nowrap;
      }

I would like to ask if anything can be done here, to hide the menu-items, but allow this mod to be there anyways.

while we're at it, and this might be a new FR, so if you'd agree, I can write it up separately:
I still have these:
      /* Hide chevrons
      paper-tabs$: |
        .not-visible {
          display: none;
        } */

which before, used to do as stated: hide the chevrons in the menu bar. Saves us 2 icons yet again...
also, there's a Help icon in the edit mode that can be ditched:
      /* This hides the help button when in edit mode*/
      a.menu-link[target="_blank"] {
        {% if is_state('input_boolean.hide_help','on') %}display: none;{% endif %}
      }

and the above does work still. I would love to have all of these Dashboard mods in a single package, so maybe have a look?
Btw, I believe you should next rename the custom card, it has grown beyond Kiosk mode only...
again, thanks!

Hi @Mariusthvdb,
Yes, we can discuss this in a separate issue to keep this one for HA 2023.4 issue. (Maybe NemesisRE could open a discussion section for these topics).
But the easiest solution that I see (because it is not nice an empty menu when all its items are being hidden) is to create another option to hide automatically the overflow menu if all its items are hidden. In that way you can choose if you want that behaviour or not.
Regards

Hi,
Still does not work
Home Assistant 2023.4.0b6
Supervisor 2023.04.0
Operating System 10.0.rcp

yes it does...
you probably need to install it in a different folder from HACS, and set the path to that resource. HACS can be difficult to persuade when using manual edited files

Hi @Jeremyhu102,
I have tested it on 2023.4.0b5, maybe 2023.4.0b6 has more changes. I'll take a look later. Please, follow the discussion and make sure that you are loading the correct version with the instructions that I gave before.
Regards.

Hi @Jeremyhu102,
I have tested it on 2023.4.0b6 and it works on my side. Please, describe exactly what do you mean with "still does not work", if there are certain features that are not working properly for you or if you receive any errors on the console.
Regards.

hello should the kiosk mode  with latest beta work do i understand that right?

I'm running beta7 without any problems.

Which file to edit?
Where to find this file?
What should be modified?
How to modify it?
I tried to modify this:
/config/www/community/kiosk-mode/kiosk-mode.js
it does not work

I stuck mine in /www/ removed the links in resources to the HACS version, and told it to look at /local/kiosk-mode.js instead.  Working fine for me.

I stuck mine in /www/ removed the links in resources to the HACS version, and told it to look at /local/kiosk-mode.js instead. Working fine for me.

paste what in /www/?     The Folder Kiosk-mode
there is no complete tutorial?  step by step

They've given you two resources to fix it yourself, I even offered where I put mine to make it work.
If you need more help than that, it's probably best you wait for them to release the fixed version.

They've given you two resources to fix it yourself, I even offered where I put mine to make it work.
If you need more help than that, it's probably best you wait for them to release the fixed version.

I did not see anything
or without explanation

You were given the instructions four days ago. .
If you can't do either of those things, there's really not much anyone else here can do to help you.

hello should the kiosk mode with latest beta work do i understand that right?

Hi @homeyjoenka, the new version is not released yet, but if you follow the instructions given in this thread you can make it work.

I'm running beta7 without any problems.

@pedolsky good to know it 👌
I‘ll try to do an extensive test in 2023.4.0b7 later on to see if everything is OK because I have been tested it until 2023.4.0b6

Hi,
Which file to edit? Where to find this file? What should be modified? How to modify it?
I tried to modify this:
/config/www/community/kiosk-mode/kiosk-mode.js
it does not work
Thx

Hi @Jeremyhu102,
You need to follow the instructions that I gave you some days ago. How to install the library manually is documented in the README of the repo.
Regards

Tested in 2023.4.0b7 it is working properly.

When have we update?

Hi @Homeassistjoenka,
You should wait until the owner of the repo review the changes, merge the branch and release a new version.
He should be back around these days.
Regards

Hey @elchininet (& @NemesisRE ) ... with this patch version and using ?kiosk , I have a sliver of what probably remains from the sidebar still in view on my devices that I'm using kiosk-mode on.  Is this expected behavior because of the 2023.4 beta breaking changes, or is this something that can be eliminated, as it was before?
No worries either way, more curiosity than anything else.

Hi @chicknlil,
What you are describing is not expected. Please, open an issue with some screenshots so we can debug there what is happening.
Regards

I've tried following the steps here and cannot get it to work either.  I replaced the .js file with the compiled code linked here and still get a header and errors in my logs.

Hi @bkr1969,
You need to force the browser to load the new version, you can use multiple techniques for that (e.g. here or here)

OK. That helped.  So when the fix is implemented will I need to delete the resource and .js file from /www?

@bkr1969,
Good to know it.
Yes, when the fix is implemented and a new version is released, you just need to delete the manual JavaScript file, remove the resource that you created and install the plugin again through HACS.

I got the fix working, and the kiosk bar disappeared again.
I have an issue with swiping to the right (to display the sidebar).
does that also apply to this issue?
otherwise this comment can be removed.

swiping left is idd an companion issue

@niekniek89,
Please, check this comment.

@niekniek89, Please, check this comment.

I just updated the HA IOS app, and swiping for the sidebar works again!

when is the fix planned to be released?

ill wait for his return

I updated to 1.8.0 but that did not work (updating for 5 minutes then i stopped it). I removed 1.7.8, restarted, cleared cache and installed 1.8.0 fresh. Restarted again. Refreshed my dashboard and nope - still sidebar and header bar visible. The same on my mobile screen (old Android tablet). No change whatsoever. What eles should I restart, refresh or whatever? Double checked the yaml and the neccessary entries. Maybe I'm blind and don't see the problem.

I updated to 1.8.0 but that did not work (updating for 5 minutes then i stopped it). I removed 1.7.8, restarted, cleared cache and installed 1.8.0 fresh. Restarted again. Refreshed my dashboard and nope - still sidebar and header bar visible. The same on my mobile screen (old Android tablet). No change whatsoever. What eles should I restart, refresh or whatever? Double checked the yaml and the neccessary entries. Maybe I'm blind and don't see the problem.

It's not a HACS update currently. You need to follow the instructions in this post.

? There was no mentioning of this in the advertised update. Sorry, I'm lost here. I will have to wait for a real update ...

? There was no mentioning of this in the advertised update. Sorry, I'm lost here. I will have to wait for a real update ...

Actually, I didn't realize a new update had been pushed an hour ago.
Had you previously used the "patch" version or the "original" kiosk-mode? Both of those would need to be removed (including from resources) for the update to work properly.

I did not patch anything, I just had 1.7.8 installed. Updating did not work, I stopped it after waiting for 10 minutes. As I wrote - I removed everything and installed 1.8.0 - but .. haha . .there is no kiosk-mode.js in it. Instead - this is the contents after 'installing':

I updated to 1.8.0 but that did not work (updating for 5 minutes then i stopped it). I removed 1.7.8, restarted, cleared cache and installed 1.8.0 fresh. Restarted again. Refreshed my dashboard and nope - still sidebar and header bar visible. The same on my mobile screen (old Android tablet). No change whatsoever. What eles should I restart, refresh or whatever? Double checked the yaml and the neccessary entries. Maybe I'm blind and don't see the problem.

Hi @DerEmder,
That version doesn‘t have the fix, the branch is not merged yet. That version contains just these changes.

I did not patch anything, I just had 1.7.8 installed. Updating did not work, I stopped it after waiting for 10 minutes. As I wrote - I removed everything and installed 1.8.0 - but .. haha . .there is no kiosk-mode.js in it. Instead - this is the contents after 'installing':

This is weird, I‘ll check it.

This is all confusing. So why is this advertised in HACS as the latest release? I don't care about new features or the mouse thingy - I only care about fixing the bugs so kiosk mode is working again. I guess I will have to wait until a new release. My knowledge is not deep enough to try the 'manual fix' explained above.

@chicknlil  do you need to add that in the download url? that
?kiosk

How can this even work if there is no kiosk-mode.js installed?
And no, it does not work here - neither ?kiosk nor any other way. I try this on my tablet and my dekstop computer - both with chrome browsers. It just does not work for me. What do you mean with 'latest HACS version' ? The 1.8.0 ?
The ressource entry gets removed automatically if you remove kiosk-mode.
I just installed the 'update' again out of frustration- this time it did not hang and installed. But still - no kiosk-mode.js inside and no functionality. No luck here. Any idea?

@chicknlil do you need to add that in the download url? that ?kiosk

Into the path in your address bar. So like http://homeassistant.local:8123/lovelace/kiosk would become http://homeassistant.local:8123/lovelace/kiosk?kiosk

Hmm, this is the list of ressources after installing 1.8.0. This can't be right, can it?

@chicknlil do you need to add that in the download url? that ?kiosk

Into the path in your address bar. So like http://homeassistant.local:8123/lovelace/kiosk would become http://homeassistant.local:8123/lovelace/kiosk?kiosk

Yes, I know that. It does not work here. Of course it does not. There is no kiosk-mode.js installed! I posted the contents of 1.8.0 already - no kiosk-mode.js, just rollup....js. Nothing else. I tried it now for the fifth time.

@chicknlilMoet je dat toevoegen aan de download-URL? dat? kiosk

In het pad in je adresbalk. Dus zoals  http://homeassistant.local:8123/lovelace/kioskzou wordenhttp://homeassistant.local:8123/lovelace/kiosk?kiosk

so? http://<IP_ADDRESS>:8123/lovelace/kiosk?kiosk=

Yes, I know that. It does not work here. Of course it does not. There is no kiosk-mode.js installed! I posted the contents of 1.8.0 already - no kiosk-mode.js, just rollup....js. Nothing else. I tried it now for the fifth time.

I wasn't answering you. :) But given your recent image, it looks like your resource for kiosk-mode needs deleting (it appears corrupted). Try that (and also completely uninstall kiosk-mode from HACS), restart HA, then try downloading the most recent version from HACS again.
I had completely eliminated the HACS version while I used the patched version, and installed it fresh, and mine is working with no issues.

so? http://<IP_ADDRESS>:8123/lovelace/kiosk?kiosk=

I don't believe you'd need the = ... but yeah, make sure the /kiosk is the path to the view you're trying to see without header/sidebar.

Sorry, my bad. Need glasses :)
Anyway - I will try after my lunch - I need brain energy first.
By the way - I removed the kiosk-mode line from the ressource file before installing 1.8.0. After installing 1.8.0 the line re-appears again.
Laters ...

This is all confusing. So why is this advertised in HACS as the latest release? I don't care about new features or the mouse thingy - I only care about fixing the bugs so kiosk mode is working again. I guess I will have to wait until a new release. My knowledge is not deep enough to try the 'manual fix' explained above.

Because it is, "latest release" just mean that, the latest one. It doesn‘t mean "it fixes your specific issue" or anything like that. If you "only care about fixing the bugs so kiosk mode is working again" you need to wait for the release that fixes that, and as I mentioned, it was not the one that you mentioned and it will not be the next one, and possible the next one either (there is a list of pull requests waiting for being released).

But that IS the specific issue this whole thread is about, isn't it? If the software does not work at all - what good are other updates for other issues? It does not make sense to me. But anyway - lunch time

@DerEmder this thread is about this issue, latest release (that was released by the owner of the repo is not). I think that you are forgetting that everyone here works in this for free and we just invest our time here to contribute to the community, as myself because I am only a contributor.

i also updated to 1.8.0 , and i see now the rollup files
removed them, and using the one from gist and point the resource correctly

i also updated to 1.8.0 , and i see now the rollup files removed them, and using the one from gist and point the resource correctly

Yes, the issue with the latest release should be fixed when this gets merged and released:
https://github.com/NemesisRE/kiosk-mode/pull/37

It doesn't work for me. Have changed this path: /local/kiosk-mode.js?v=1.8.0 and copied the latest kiosk-mode.js to my HA. Removed the previous version of kiosk-mode v1.7.8 and still not working :(

Hi @besiktas97,
What do you mean with the latest version?
Check the instructions given at the beginning of the thread, you should uninstall the installed version.
Regards

Hi @besiktas97, What do you mean with the latest version? Check the instructions given at the beginning of the thread, you should uninstall the installed version. Regards

Hello elchininet,
I did a uninstall of the previous version and did a manual installation. the path I made /local/kiosk-mode.js?v=1.8.0 and even I tried /local/kiosk-mode.js?v=1.7.8 and the side bar is still vissible.

You need the version from gist,

Did you use the compiled version provided in this thread?
Are you able to see kiosk-mode.js in the network tab of your browser?

cant clone it:

@besiktas97,
Please, take your time and read the thread, there is public gist with the compiled version that you can install. You don‘t need to clone the repo and compile the code.
Regards.

Rollback to a version that it is compatible

Not really an option at this moment.

Try to solve it with the workarounds that the community creates "for free" for you

Yes, I know. It is free. I don't pay money for it. Is that what you mean? I pay for it with my precious time I could spent in doing other things. So i also use my spare time "for free" to help the dev to make it work again. So please don't lecture me about "free" and Open-Source - I am fully aware of that. LetÄs put it this way: it is a taking and giving and hopefulyl we will all find the right balance.

Wait for the release that fixes the issue is released

I will.

@besiktas97, Please, take your time and read the thread, there is public gist with the compiled version that you can install. You don‘t need to clone the repo and compile the code. Regards.

I tried that piece of Javascript from gist and installed it manually. It does not work here. It was actually the first thing I did after reading it. Maybe I did it wrong, I don't know. But I did exactly what was posted above. And I was also unable to clone the repo with the same error message as posted above (Permission denied).

@besiktas97, Please, take your time and read the thread, there is public gist with the compiled version that you can install. You don‘t need to clone the repo and compile the code. Regards.

I tried that piece of Javascript from gist and installed it manually. It does not work here. It was actually the first thing I did after reading it. Maybe I did it wrong, I don't know. But I did exactly what was posted above. And I was also unable to clone the repo with the same error message as posted above (Permission denied).

Yes, you did it wrong for sure because it works. You just need to check all the people here that have that version working (including myself).

And I was also unable to clone the repo with the same error message as posted above (Permission denied).

I‘ll change the instructions, you can only clone a fork of it.

You just need to check all the people here that have that version working (including myself).

I only read from people where it does not work. You are the only one who says it works. So I assume it should work. I will try again and report back if I succeed.

For me gist is also working, I have hidden the title bar again , used the gist, removed the 2 files on the kiosk folder, downloaded the gist there...
Restarted , clear cache, that's it

I‘ll change the instructions, you can only clone a fork of it.

I don't even know what that means and how to do it. I never used Github. So, that's a bit too complicated for me at this point. I am just a user, not a programmer

@DerEmder,
Just as a reference so you can check that what you are saying is not accurate:
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1492651263
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1494911564
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1497265590
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1497768027
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1498226442
https://github.com/NemesisRE/kiosk-mode/issues/27#issuecomment-1498928065

For me gist is also working, I have hidden the title bar again , used the gist, removed the 2 files on the kiosk folder, downloaded the gist there...
Restarted , clear cache, that's it

Thanks, so it should work. I will do the same now.
So you have 1.7.8 installed, removed the two files (.js and .gz) from kiosk-mode folder and uploaded the javascript from gist (kiosk-mode.js) into the kiosk-mode folder. Is that correct?
Then clearing cache etc. and it should work?

@DerEmder,
Just as a reference so you can check that what you are saying is not accurate:

I apologize - overlooked them.

Just install 1.8.0,doesnt mather, remove files afterwarda, place the gist file there, point correctly with resource , to make it work for sure, add ?v1 add the end in your resource... Then clear cache, restart

Just install 1.8.0,doesnt mather, remove files afterwarda, place the gist file there, point correctly with resource , to make it work for sure, add ?v1 add the end in your resource... Then clear cache, restart

I have removed the old version, but when I want to download it O cant download verdion 1.8.0. Only 1.7.8, tonight I will digg more into it.

Yeah doesn't mather , you need to remove files anyways, but I suggest you to wait for next version , they are working on it, be patient

@besiktas97,
Forget the version 1.8.0 it was deleted because it was a wrong release. Just follow the instructions:

Uninstall kiosk-mode

Install the gist manually with the instructions given in the README

Clear cache and that should be enough

Anyway, the pull request that solves the issue is ready to merge. When @NemesisRE take a look at it and merge it, a new version could be released.

Thanks then I will wait I guess for the new release. Patient patient :-)

Ha, that did work. I guess I forgot the ?v1 thing in the ressources file. Header bar is gone now, sidebar still there. But one problem at a time.
Thanks @pergolafabio and @elchininet
Now will wait for the release with a fix.

A last note before I go to sleep - now kiosk mode even works where it is not even part of the yaml. Now the header bar (not the sidebar) is removed in all views and dashboards no matter if there is an entry with kiosk_mode in the yaml or not. Doesn't bother me too much because I can disable it with ?disable_km where I need it.

Hi guys. The new version 1.8.1is released, I have already removed my manual fix and installed it again and it is working properly.
Thanks to all of you for the feedback during the testings 👍
Please, if you notice something, feel free to open an issue with it, closing this issue.

A last note before I go to sleep - now kiosk mode even works where it is not even part of the yaml. Now the header bar (not the sidebar) is removed in all views and dashboards no matter if there is an entry with kiosk_mode in the yaml or not. Doesn't bother me too much because I can disable it with ?disable_km where I need it.

Hi @DerEmder,
Feel free to create an issue describing what you are facing.

https://github.com/gzzyyt/find-music/blob/main/1.pnghttps://github.com/gzzyyt/find-music/blob/main/2.jpgAfter upgrading to 1.8.1, there was no problem with the computer browser webpage when the header was hidden, and it displayed normally. However, there was a black box below my iPad, which prevented me from displaying everything

I had to reboot and redownload 1.81 to get old version out of system.   Seams to working ok
Thanks

Morning, Thank you so much for the update, kiosk mode, grate job

I've updated to version 1.8.1, cleared the cache, and rebooted, but I'm still getting the error below.
Logger: frontend.js.latest.202304061
Source: components/system_log/init.py:257
First occurred: 09:22:39 (4 occurrences)
Last logged: 10:38:18
https://ooooo/hacsfiles/kiosk-mode/kiosk-mode.js?hacstag=497319128173:13:44 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
https://ooooo/hacsfiles/kiosk-mode/kiosk-mode.js?hacstag=497319128173:57:96 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
Home Assistant 2023.4.1
Supervisor 2023.04.0
Operating System 9.5
Frontend 버전: 20230406.1 - latest

Hi @Murianwind,
Please, let‘s discuss your issue here.
Could you follow these steps but search for TOOLBAR and let me know if you can find this in your code t.TOOLBAR = ".toolbar",?
Regards

Awesome all fixed with the latest update. Thank you


Large datasets for predictions

In testing the data upload feature, I mocked a dataset with ~20k rows in the header and ~100k rows in the episodes. The upload view took ~50 seconds to complete - I would expect this to timeout in production. This view is calling the prediction function.

Is this a size of data the tool will be expected to handle?
If so, what are the options for mitigation?

Optimise prediction function?
Make all predictions asynchronous
Other?

@MichaelHanksSF if this is the same issue you mentioned yesterday, some further thinking towards 'Other' here:

Django can (natively)handle chunking, this approach i've used in python with success but unsure how that works on the django side. This likely better combined with other failsafes, e.g.
Set a DATA_UPLOAD_MAX_MEMORY_SIZE (would need to look into what is/isnt suitable data volume)
Can a timeout be defined on the host server instead?


Create compiled log file across all samples to create a single summary log file at the end of each run

I believe this has been superseded by #75 , which is in test; now that we have an easy way to learn WHICH step failed at a glance, we actually DON'T want to concat the log files ... it is easier to jump straight to the info for the step that failed with them separate.


Make sure to never catch SystemExit.

If a SystemExit is raised one way or another, it should not be caught.
In some places, there are already some guards against catching SystemExit, but it's good to add some more.

It seems this is related to https://code.djangoproject.com/ticket/25682. An alternate solution like changing the bare except: may be preferred?

Yes, it's definitely related to that one, except I already saw this a while ago. (I've had quite a lot of trouble debugging Django+CherryPy not stopping after a signal handler called sys.exit().
(And yes, I'm at DUTH as well).

The reason for not choosing to use except Exception by the way is that it's really hard to quickly determine whether or not it actually intended to catch non-Exception BaseExceptions.
Of course I could spent some time to determine if we could use the normal except Exception instead, was just looking for a quick fix.

We should definitely just change the bare except clauses to except Exception (including in the cases where we already have a SystemExit guard) instead of adding more SystemExit guards like this. We can check to see if any of those bare excepts are really intended to handle KeyboardInterrupt, but I doubt most of them are. (The only non-Exception built-in exceptions are SystemExit, KeyboardInterrupt, and GeneratorExit -- I think we can safely say that none of these were intended to catch GeneratorExit.)

Agreed, I'll re-work the diff to use except Exception instead. If other bugs pop up because of that change, at least one can now add a more specific catch for the actual cases.

Closing in favor of https://github.com/django/django/pull/5664 which fixes a few more cases.


Only real content should be given line numbers

line 1,2,3 shouldnt be numbered

Not only that, they shouldn't be called "line numbers" at all, since they're not. They do not correspond in any way to the lines in the JSON file.


GCDS: Checkboxes

Focus state has no outline

Not sure if Forms checkbox label supports hint messaging

Checkbox dimensions are off
-Forms: 40px x 40px
-GCDS: 48px x 48px

Typography doesn't match

DESKTOP

Forms label: Font Size = 20px, Line height = 28px (140%)
Forms hint: none?
GCDS label: Font Size = 20px, Line height = 24px (120%)
GCDS hint: Font Size = 20px, Line height = 24px (120%)

MOBILE

Forms label: Font Size = 20px, Line height = 28px (140%)
Forms hint: none?
GCDS label: Font Size = 16px, Line height = 24px (150%)
GCDS hint: Font Size = 16px, Line height = 24px (150%)
Checkbox label does not scale down on mobile

Current state

Desired state

Started a PR here
https://github.com/cds-snc/platform-forms-client/pull/4343

PR is merged.


Allow redirect URL to be passed in the query string.

When using the Kubernetes nginx ingress controller, the sign_in page is reached via a 302 redirect, which means that we cannot use the X-Auth-Request-Redirect header. Instead, we need to be able to include the URL in the query string.

Any update on this?

you could just redirect to .../oauth2/start?rd=... instead
if you really want this here, you should use GetRedirect() here (it does a bit more to prevent "open-redirects")

@ploxiln is possible a redirect to a different host?

see #399

@ploxiln ok, so the recommendation is to not allow "external" redirects or adding the whitelist domain flag is ok?

A domain whitelist feature would be as good as the current status-quo from a security/phishing perspective. It's just arbitrary (completely unrestricted) redirect domain which is problematic.


Support devicePixelRatio>1 with RESIZE scaling

The what
The RESIZE scaling mode works by setting the display size and the game size to fill the available space of the parent. When devicePixelRatio is larger than 1, I would expect the game resolution to be that times larger than the display size. Currently, with a devicePixelRatio of say 3, the resolution will be very  low for a game on a modern device. The other scaling modes seems to work perfectly well with a higher devicePixelRatio.
The why
As the RESIZE scaling mode is very useful for more responsive games, I think this will be a good feature. If we do a Google search for "phaser scale resize devicepixelratio", we find that this seems to be a somewhat common issue. So I do believe it will be useful to more people than just me. :)
Suggestion
I forked the codebase and pushed a suggestion which works in my case. https://github.com/orjandh/phaser/tree/scale_resize_dpr I don't know what would be the best interface for this, but I made an optional dprResize flag in the config which sets the resolution to the correct values.
I don't know if this change breaks other components. I noticed the camera scroll seemed to work a bit different, but might have been something in my code.
Lastly, I was considering just changing the internals of the scaling manager on the resize event that it emits. But this will break other components like the camera, because it also depends on the resize event.

You're more than welcome to implement this in your own fork, but there are no plans to support DPRs above 1 in any v3 release of Phaser, as reported in the Change Log:
Removal of 'resolution' property from across the API
For legacy reasons, Phaser 3 has never properly supported HighDPI devices. It will render happily to them of course, but wouldn't let you set a 'resolution' for the Canvas beyond 1. Earlier versions of 3.x had a resolution property in the Game Config, but it was never fully implemented (for example, it would break zooming cameras). When the Scale Manager was introduced in v3.16 we forced the resolution to be 1 to avoid it breaking anything else internally.
For a long time, the 'resolution' property has been present - taunting developers and confusing new comers. In this release we have finally gone through and removed all references to it. The Game Config option is now gone, it's removed from the Scale Manager, Base Camera and everywhere else where it matters. As much as we would have liked to implement the feature, we've spent too long without it, and things have been built around the assumption it isn't present. The API just wouldn't cope with having it shoe-horned in at this stage. As frustrating as this is, it's even more annoying to just leave the property there confusing people and wasting CPU cycles. Phaser 4 has been built with HighDPI screens in mind from the very start, but it's too late for v3. The following changes are a result of this removal:


SpanToken.Image regex does not allow empty alt text

The Image SpanToken does not allow empty alt text, so ![](some/image.png) will not be parsed. I think the regex here needs to be updated.
P.S. Thanks for writing Mistletoe - it is great so far! :)

Updated in 25cbccb, and will be included in the next release. Thanks a lot!

Awesome - thanks for the speedy reply! Do you know when the next release will be?

No that's great. If it was going to be months I'd probably pull my own copy, but a week or two is fine :). Thanks again!


Error:SteamMatchmaking is null

Describe the bug
When I use SteamMultiplayer Peer to create a lobby, this error is reported.
Only my Mac computer will report this error, while the Windows computer does not report this error.
To Reproduce
Steps to reproduce the behavior:
Code snippet:
var steam_peer = SteamMultiplayerPeer.new()
steam_peer.create_lobby(SteamMultiplayerPeer.LOBBY_TYPE_PUBLIC)
Screenshots

Version of GodotSteam:
Godot 4.2.2 - Steamworks 1.59 - GodotSteam Multiplayer Peer 4.8

func _init(): 	OS.set_environment("SteamAppID", str(480)) 	OS.set_environment("SteamGameID", str(480)) 	Steam.steamInit()
I even found that on a Mac computer, when I call these codes, my Steam does not display entering the game Spacewar

Hey there!  I know basically nothing about MultiplayerPeer so I cannot speak to that.  However, if SteamMatchmaking() is null, then you do not have Steamworks either enabled or present; which is odd because you mention using the pre-compiled version.  What does the Mac show when Steam is initialized?
If it will not let you set environment variables you will either have to pass the app ID to the initialization function used as the second argument or you will have to create a steam_appid.txt with 480 in it then set that where ever your editor is located.

Hey, I was also getting this problem (also on Mac), but it looks to resolve itself when you pass the appID to the initialisation function rather than setting the environment variable as suggested above

Does that reliably crash?  If so, that should probably be mentioned until it can be fixed (if it can be fixed).

Not so much a crash, just an error in the console, but otherwise to the best of my knowledge it happens every time yeh.
Not sure if its a problem with Godot's OS.set_environment on MacOS, though looking around I can't see anyone else mentioning issues with it outside of GodotSteam

The odd thing is that is exactly what GodotSteam is doing internally when you pass the app ID in:
OS::get_singleton()->set_environment("SteamAppId", itos(app_id));

So I would think it would work with either of them or neither.  But maybe I don't understand the difference between how those two things differ; always possible.

Aha, apologies, this was my mistake, I was using SteamAppID where it should be SteamAppId. It's correct in the documentation as well, so purely my error.
I'm not sure if that changed recently, I was following a video tutorial which seemed to use the full caps id, and I guess I just skimmed over that when comparing the documentation


290 import vdccertificate with data field is failing

Fix Import-VdcCertificate -Data failure due to being converted to an array.  #290

reviewed by @Andrew-Boley


Multiprocessing works differently in Linux and Windows

Hi
That's my small example script. Create a subdirectory "metrics" in the folder from you are running the script and set the environment variable.
#!/usr/bin/python
'''
This is just an example of how to use prometheus_client in multiprocessing application
'''
import os
if 'prometheus_multiproc_dir' not in os.environ:
    os.environ['prometheus_multiproc_dir']='metrics'

from prometheus_client import Counter
from prometheus_client import start_http_server
from prometheus_client import CollectorRegistry
from prometheus_client.multiprocess import MultiProcessCollector
from prometheus_client import core
from multiprocessing import Pool

def worker(n):
    counter = Counter('counter', 'counter', registry=None)
    counter.inc()

def main():
    print("Main PID", os.getpid())
    clear_metrics_dir()
    registry = CollectorRegistry()
    MultiProcessCollector(registry)
    core.REGISTRY = registry
    start_http_server(8000)

    p = Pool(processes=10)
    p.map_async(worker, range(300000))

    p.close()
    p.join()
    print(registry.get_sample_value('counter'))

def clear_metrics_dir():
    dir = os.getcwd()
    os.chdir(os.environ['prometheus_multiproc_dir'])
    [os.remove(file) for file in os.listdir()]
    os.chdir(dir)

if __name__ == '__main__':
    main()

If I run this in Windows I got this output:
Main PID 27372
300000.0

and there are 10 files in the metrics subdirectory.
But on Linux the output is different:
Main PID 24671
42961.0

And there is only one file in the directory.
I'm not quite sure but my guess is the following:
In the core.py at lines 441-444 the variable _ValueClass is initialized:
if 'prometheus_multiproc_dir' in os.environ:
    _ValueClass = _MultiProcessValue()
else:
    _ValueClass = _MutexValue

And then that class is instantiated and it creates the files where the metrics data will be stored.
The class itself is created in the function _MultiProcessValue() and it uses os.getpid() as a default value for the argument.
In Windows when you start another processes with multiprocessing your main module is reloaded for each of the processes. And the prometheus_client library is also reloaded and the class is constructed for each of the new process.
In Lunux the module is loaded only once and therefore the class is created also only once.
All that makes the library write all the metrics of all the processes to the same file on Linux! That makes the metrics basically wrong, and in the worst case the file got corrupted and the HTTP server can not read from the file.
Though the stuff seems to work well if the load on the processes is small. E.g. if you put sleep in the worker function and reduce the number of cycles it can (sometimes) work fine.
If i change the core.py in this way, it works fine on both Linux and Windows (lines 395-406):
def _MultiProcessValue(__pid=os.getpid()):
    files = {}
    files_lock = Lock()

    class _MmapedValue(object):
        '''A float protected by a mutex backed by a per-process mmaped file.'''

        _multiprocess = True

        def __init__(self, typ, metric_name, name, labelnames, labelvalues, multiprocess_mode='', **kwargs):
            pid = os.getpid()
            if typ == 'gauge':

but then the unit tests will most probably fail.

It's documented that "Gunicron's preload_app feature is not supported", which is what you're effectively running in to. The new process currently needs to reload all Python modules for it to work.
The difference you're seeing is likely due to Python implementation differences across platforms, as Windows doesn't support fork.


metrics: add bytes written & bytes read metric

This change adds two new counter vector metrics:

bytes_read_total - number of bytes read by a regionserver connection
bytes_written_total - number of bytes written to a regionserver connection

These metrics have one label - regionserver - which indicates the address of the connection used.

I didn't add any tests here right now. Would it preferable to have add value checking in the integration tests - or to tack this on to the region/client_test.go?

I think not having test is okay for this. Should we still count the bytes read/write even if an error is returned?

It was not okay. This broke... everything =). Not consistently and I haven't really tried to pinpoint why but:
16:11:59  time="2022-05-16T23:11:28Z" level=error msg="error occured, closing region client" client="RegionClient{Addr: regionserver-2.hbase.hbase.svc.cluster.local:16020}" err="region.ServerError: got a response with an unexpected call ID: 0"
16:11:59  E0516 23:11:28.459528   40703 hbase.go:288] internal storage error: HBase Java exception java.io.IOException:
16:11:59  java.io.IOException
16:11:59  	at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:463)
16:11:59  	at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
16:11:59  	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338)
16:11:59  	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)
16:11:59  Caused by: java.lang.IllegalArgumentException
16:11:59  	at java.nio.Buffer.position(Buffer.java:244)
16:11:59  	at org.apache.hadoop.hbase.nio.SingleByteBuff.skip(SingleByteBuff.java:88)
16:11:59  	at org.apache.hadoop.hbase.nio.SingleByteBuff.skip(SingleByteBuff.java:40)
16:11:59  	at org.apache.hadoop.hbase.codec.KeyValueCodec$ByteBuffKeyValueDecoder.advance(KeyValueCodec.java:100)
16:11:59  	at org.apache.hadoop.hbase.regionserver.RSRpcServices.skipCellsForMutation(RSRpcServices.java:2927)
16:11:59  	at org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:1096)
16:11:59  	at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:931)
16:11:59  	at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:895)
16:11:59  	at org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2881)
16:11:59  	at org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45265)
16:11:59  	at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:395)
16:11:59  	... 3 more


Cannot read property 'charAt' of undefined

Import of the result is done successfully but while running the query I am getting 'Cannot read property 'charAt' of undefined'...Please advise....

Can you provide more details please? i.e. The query, any additional errors in the browser console, etc.

With every query...for example -
MATCH (a:AADRole)<-[r:MemberOf]-(t) WHERE a.name = 'Company Administrator' RETURN *

There is an ingestion error there that's breaking your requests and is either hanging your neo4j session or just breaking it completely. Also, it looks like this might also happen if you try to query while the file is still ingesting.
I would imagine that after the NeoClientError in the picture you provided, there is a cypher query or Azure/AAD object that was given back to you in the line right after. Can you provide that cypher query output? I would need more information about where that hyphen is that's breaking your queries in order to troubleshoot further.
There may be sensitive data in the cypher query. Please blur anything that shouldn't be exposed.

Ok...
One Example -
stormspotter-backend_1   | "    MERGE (from)-[obj:ddd-Role_ABCNonACT_Storage-Contributor]->(to) SET obj.actions = ['Microsoft.Authorization//read', 'Microsoft.Insights/alertRules/', 'Microsoft.Insights/diagnosticSettings/', 'Microsoft.ResourceHealth/availabilityStatuses/read', 'Microsoft.Resources/deployments/', 'Microsoft.Resources/subscriptions/resourceGroups/read', 'Microsoft.Storage/storageAccounts/', 'Microsoft.Support/', '*/read'], obj.not_actions = '[]', obj.data_actions = '[]', obj.not_data_actions = '[]', obj.roleName = 'ddd-Role_ABCNonACT_Storage-Contributor', obj.roleType = 'CustomRole', obj.roleDescription = 'abc STORAGE CONTRIBUTOR Role'"

It is working fine...May be it was taking time to import the data.


Doge android wallet

Hello,
I am kind of a big noob.
So I installed the doge android wallet and I've send some coins from anycoin to my wallet.
Back then I didn't understand that I have to wait for it to synchronize. I reinstalled the app and of course I didn't do a backup.
Now my old address is not anymore on my address book (those linked to my app)
Is there any way to get my old address back so I can access my coin?
Thank you have a nice day!

Oh sorry for the mistake on your part with regret I inform you that there is no way to get the account and the money back as all backup phrase are not stored on any server because all Cryptocurrency are create to provide privacy and security to all users.thank you

Damn OK thank you. Was not much Atleast


Finalize how web app interacts with detection docker

Hi @rdkelley,
Let me if I can pick this item please. I want to contribute as well.

We discussed this on the Dec 9 town hall. Work should start on this, and we have freedom to define the format (GraphQL/REST/WebSockets). The key things are to define the data needed. We can start with what's provided by the AWS hosted instance of the Grillo cluster.


Ordered constraint accumulation

Currently, CSubst constraints are always sorted when a new CSubst is created. However, when a KCFG is minimized and splits are lifted into other splits, this sorting results in a misordering of constraints and therefore a slightly poorer user experience when trying to debug the control flow. For example, even though the branchings constraints were chronologically C1, C2, C3, when the KCFG is minimized they could appear as C2, C3, C1.
This PR enables constraint order preservation and uses it when lifting split nodes.

https://github.com/runtimeverification/k/pull/4249


chore: add console.log to test datadog logs

Testing to see if a console.log will show up on Datadog.

Sorry merged without approving, it's all good!


Zone keeps changing to match other monitor

Microsoft PowerToys version
0.82.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones Editor
Steps to reproduce

I have 3 monitors as shown in the attached image. I'm attempting to make monitor 1 have two equal zones. Monitors 2 and 3 should have a single zone each. I can edit the zones accordingly. However, monitor 3 always changes from a single zone to two zones when I save the configuration.
Note that I am not using the "default for horizontal monitors" option.
Note that monitor 3 is the laptop's built-in monitor; monitors 1 and 2 are external monitors
✔ Expected Behavior
Monitor 1 have two zones; Monitor 2 have one zone; Monitor 3 have one zone.
❌ Actual Behavior
After saving the configuration, monitor 3 changes to have two zones. When I reopen the editor, monitor 3 shows only one zone even though I originally saved it with two zones.
It seems like monitor 3's configuration is changing to match monitor 1.
Other Software
No response

/dup #26729


Update qrcode-generator extension

Description

Screencast

Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

Hi @Melvynx and @darmiel 👋
I updated the extension, do you mind checking it out 🙂


SMTP returning 'The remote certificate is invalid according to the validation procedure.' because of Sender.UseSsl

I am using a SMTP mock (node fake-smtp-server) to test FluentEmail.Core with SMTP sender.  I am using the config file to define the SMTP configuration.  My intention is to not have any additional SMTP configuration in my code.  My configuration file is as follows:
<system.net>
  <mailSettings>
    <smtp deliveryMethod="Network">
      <network host="localhost" port="25" enableSsl="false" />
    </smtp>
  </mailSettings>
</system.net>

My mock is launched as follows:
 fake-smtp-server --smtp-port 25 --http-port 10080 --max 10

The default value for Sender.UseSsl is true, so I am forced to use the following to configure SMTP:
 var _defaultClient = new SmtpClient();
 var _sender = new SmtpSender(_defaultClient);
 _sender.UseSsl = false;

Additionally, is FluentEmail.Core a replacement of FluentEmail?  Explanations in the docs would be appreciated.

My work-around:
var _client = new SmtpClient();
var _sender = new SmtpSender(_client)
{
    UseSsl = _client.EnableSsl
};


Bug/644 fix timeline wording

fixes wording on timeline
From "PIN" to "Person In Need"
From "CAV" to "Volunteer"
https://github.com/reach4help/reach4help/issues/644

Note that there is a LOGIC ERROR in the screenshot above:  "Volunteer accepted this request" is on PIN side.  Can we make a new issue and maybe @btuerker can look into it?

https://github.com/reach4help/reach4help/pull/651#issuecomment-640240363
This is actually in an issue with the backend. I will look into it and fix it now


chore(examples): update dependencies

Also adds .babelrc to avoid transpiration of dependencies.

Thank you for reviewing @cal-smith! The Angular deploy failure seems of a timeout, but I saw a node.js heap error in local. Will investigate further.

The Angular deploy is fixed in: #321


Feature/extrinsic deserialization

still TODO:

fix bug - information about extrinsic (signer,nounce) is removed before extrincs are being executed (and shuffled)
~improve randomization - currently only groups are randomized (single group per single extrincis signer)~
remove extrinsic information when no longer needed

Do we have any alterations in client/transaction-pool? What are these?

@gleb-urvanov i tried to separate forking & modifications into separate commits
https://github.com/mangata-finance/mangata-node/compare/4101cd9f38dfb6e4a714850988e1126b1b82c936...e734429bfe0b4c4c3daaaf2ab3ae90d538350b75


Port packfile writing

[x] Port packfile repacking to RfgTools. Only unpacking has been ported so far.

This is complete but not yet committed since I want to put it through more testing first.