Copy/cut and pasting not working while fired another event like shift+delete

Issue Type: Bug

Copy/cut text.
Fire shortcut key like ( shift + delete ).
Now try to paste the copied text ( not going to paste any single character).

You can use "editor.emptySelectionClipboard": true to disable writing to the clipboard when nothing is selected.
Read more in #45965


Oh, my god. The decoder seems strange.

what has happened???

my face always seems like ghost....
I think the decoder is broken.

The decoder is not broken. The output is probably too stylized given your style image, so that the content is not well preserved.
Below are some things you may want to try to get better results:

turn down -alpha a little bit
increase the resolution of the content image
I just uploaded a decoder with smaller style weight during training, you might like that one a bit more:
wget -c https://s3.amazonaws.com/xunhuang-public/adain/decoder-content-similar.t7
If none of the above works, try to change the style image.


[rdc] Config knob for waveform dump

WAVES env configures RDC tool to dump waveforms of violation paths.
USAGE
$ WAVES=vcd dvsim {cfg.hjson}

I think so. But I never run this option with 4k errors database. :)

On Nov 10, 2022, at 11:29 AM, tjaychen @.***> wrote:
just curious, does this explode the run time if we have a lot of failures?
—
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/pull/16216#issuecomment-1310796226, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3UUWKQFWCKUKLKXLWDWHVEKXANCNFSM6AAAAAAR43RTK4.
You are receiving this because you authored the thread.


Update prefixIds.js

Makes escapeIdentifierName delete invalid ID characters

Tests are missing. Feel free to open new PR.


Fixed Contact Page Styling/Alignment

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

This is not a fix. This is a request to add login and signup pages to the site.
Summarize what this PR fixes:-
styled h1 heading
fixed border on textarea
changed padding and margins in form
fixed submit button styling
Fixes #602
Checklist
(Add an x between the brackets to check the items)

[x] I have summarize what this PR fixes above
[x] I have provided the issue ID/URL above
[x] I have not added Bootstrap or jQuery and used correct styling guide.
[x] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[x] I was the first one to claim the issue or I created the issue - I created the issue

This at least uses rem, which is more aligned with mockup. However, it still looks too spaced out and not centered on the page. I'll merge this in, but still work to be done.


Language: German language added

Besides a small spelling mistake in the English language I've also added German language.
Some things to note:

In the support part (:web: --> :incoming: --> :incoming_secret_placeholder:) I added "Please write your support request in English." (of course I added the German translation) as I think you maybe easier able to reply in this case.
The support email you receive (:email: --> :incomingsupport: --> :body1:) I of course didn't translated into German, but I added note to the body text to show that a German user has send this. (it may be interesting to know and if you possibly have German support staff at some time you know you can reply them back in German).
I've translated the word "secret" into German in all sentences. If you want I can of course also use "Secret" as a kind of proper name, so in this case I wouldn't translate it. This may sound more "cool" in German. :wink: Like "Create a Geheimnis. Afterwards you can share the Geheimnis to anybody you want." if I say it otherwise. (don't know if this sounds cool too... :laughing:)
In German you have a quite big difference in language if you say something informal or formal. [There are even two verbs.] (http://blogs.transparent.com/german/the-german-you-duzen-und-siezen/) As a consequence I had to decide whether to "[duzen] (https://en.wiktionary.org/wiki/duzen)" (informally) or "[siezen]" (https://en.wiktionary.org/wiki/siezen) (formally) the user of your website. I chose to to address him informally) them

BTW I've accepted this [contributor agreement] (https://onetimesecret.com/contributor). I have no idea what this changed on my account, but I can let you know my email address if you want to verify that I accepted it.

Fantastic! Thanks @blobgo. I'll add a thank you to the translations page. Let me know what URI you'd prefer it link to (email me: delano@onetimesecret.com).

My GitHub profile.
BTW - do you have any PGP key for<EMAIL_ADDRESS>And I also noticed that some strings are not translatable. So on https://onetimesecret.com/#recent-tab it now e.g. shows the following Denglish (Deutsch+English) sentence:

Go on then. Teile ein Geheimnis!


⚠ ClamAV has degraded performance

In 4588b29, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 196 ms

Resolved: ClamAV performance has improved in 5b47279.


dar: 2.6.2 -> 2.6.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dar/versions.
meta.description for dar is: '"Disk ARchiver, allows backing up files into indexed archives"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.6.3 with grep in /nix/store/qxa2k4548byp4jlcdih3f2hs4b4iysxp-dar-2.6.3
directory tree listing: https://gist.github.com/bc4e689c01da532462a112fe98511423
du listing: https://gist.github.com/b820528f70b174d76344db8dd40bca7f

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
dar

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qxa2k4548byp4jlcdih3f2hs4b4iysxp-dar-2.6.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A dar https://github.com/r-ryantm/nixpkgs/archive/91085a26c9e0fda7a1dc9e7d2a1e62def983bda7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qxa2k4548byp4jlcdih3f2hs4b4iysxp-dar-2.6.3
ls -la /nix/store/qxa2k4548byp4jlcdih3f2hs4b4iysxp-dar-2.6.3/bin

https://github.com/Edrusb/DAR/blob/master/src/build/ChangeLog


[FIX] Remove call to old method and add call to new method for jira integration

This PR is pretty straight forward, part of the code was still using the old method add_comment_task that has been replaced by add_comment. This resulted in errors when adding notes to findings. Therefore, we replace the old method by the new method which solve the problem.
Let me know if there is more to it as I'm not completely familiar with the new integration :).

PR looks good. Not so good we missed this bug....


support jest.config.mjs and jest.config.cjs

🚀 Feature Proposal
jest.config.js is using commonjs. Can we use jest.config.mjs and jest.config.cjs for config file in node 13.2?
Motivation
esm support for config file
Example
// jest.config.mjs
export default {
  // [...]
  // Replace `ts-jest` with the preset you want to use
  // from the above list
  preset: 'ts-jest/presets/js-with-ts',
};

Pitch
Why does this feature belong in the Jest core platform?
Common feature proposals that do not typically make it to core:

New matchers (see jest-extended)
Changes to the default reporter (use custom reporters instead)
Changes to node/jsdom test environments (use custom environments instead)

this is pretty much blocked by #4842.

@SimenB jest.config.cjs is not blocked by experimental-loader API.

Does it make sense to add support for this, which is useless outside of esm support in node (which we don't support)? It's simple enough in isolation, but I'm not sure it provides much value, and might confuse users more? thoughts?

@SimenB Yes, it does. I have type=module packages and use Jest+Babel to run tests. But Node 13 refuses to load .js files inside such packages, which means that Jest fails to open a .js config. Moreover, you can't manually point to a .cjs file because of a check in readConfigs(). I've made a similar request in #9086.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.13 to before v5.15.5",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a7b359fc6a37faaf472125867c8dc5a068c90982",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=512e21c150c1c3ee298852660f3a796e267e62ec"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "a7b359fc6a37faaf472125867c8dc5a068c90982",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "512e21c150c1c3ee298852660f3a796e267e62ec",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "sched/fair: Prevent dead task groups from regaining cfs_rq's\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.5 by commit 512e21c150c1c3ee298852660f3a796e267e62ec, it was introduced in version v5.13 by commit a7b359fc6a37faaf472125867c8dc5a068c90982. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002329


chore(*) update all CHANGELOG files to align in tense and issue/PR referencing

For all extension's CHANGELOG files, we need to do the following:

All leading verb tenses (especially for "fixed" or "changed") are past tense, like so:
"Created this to do that."

When applicable, the Issue and/or PR are referenced at the end of the line, like so:
"Created this to do that. (Issue #XXX)"
or
"Created this to do that. (Issues #XXX and #YYY)"
or
"Created this to do that. (PR #XXX)"

@kevinthecheung do you want to work on this?

Given that these are all auto-generated from PR names, it sounds like a lot of work to manually fix these before each release. @kevinthecheung what do you think?

I've added this to our release process so the release owner can make these changes, and Kevin can do the final review.


Discovering the input(s) that maximizes activation of each CNN filter

This isn't an issue; rather an enquiry.
Any guidance as to how would one would use your library to find the inputs that maximize each layer/filter?
The first thought that comes to mind is to send random inputs through and measure the activations, but that doesn't feel very efficient.

You'd probably want to borrow some code from https://github.com/keras-team/keras/blob/master/examples/conv_filter_visualization.py but to be honest I wouldn't know where to start

I guess you could use the same metholody as done in:
https://christophm.github.io/interpretable-ml-book/adversarial.html.
What do you mean exactly by maximizing each layer/filter?
A Convolution output is going to be something [batch, h, w, out_channels].
What do you want to maximize actually?

I guess you could use the same metholody as done in:
https://christophm.github.io/interpretable-ml-book/adversarial.html.
What do you mean exactly by maximizing each layer/filter?
A Convolution output is going to be something [batch, h, w, out_channels].
What do you want to maximize actually?

The way I see it you can either aim to get to maximise the maximum output of a specific layer(not easy to do with gradient-based methods) or you can aim to get the maximize the mean of the outputs of a specific layer (easier to do with gradient-based methods)

Let us know if you need more help! I'll close this issue for now


Can this package be run in the browser?

Can this package be run in the browser, say as part of a React web application? I've been looking at similar speed tests package and I'm seeing the owners saying that their packages are not meant to be run in the browser. Just wanted to confirm that with this package. I haven't been able to install this package successfully in my React project, so I guess this may be why.
PS: I'm just looking for a way to determine the user's internet speed once they're navigating through my web app, and alert them if they have a slow connection. I know how to estimate this by using the "image approach", but wanted to see if any package already serves this purpose. Thanks.

Hi,
I'm honestly not sure. There may be problems (using perf_hooks) due to the time tracking code used. It will be easiest to test this fact. In case there are any problems due to perf_hooks, I am currently working on version 3.0.0, which should solve this.
Thank you for your understanding

Hello @rivasaugusto,
I just released the release candidate of version 3.0.0.
You can install and test the library using:
npm install --save universal-speedtest@next

The new documentation can be found here: https://karel-kryda.gitbook.io/universal-speedtest/v/3
I hope that if the current version was not compatible with the browser run, the new version will be.
If you would test it and get back to me with the result, I would be happy.
I hope everything will work as expected 😉.
Thank you in advance


Implemented KMP Algorithm in Cpp

Implemented KMP Algorithm in Cpp
Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Very important algorithm for String Search.
Checklist

☑ I've read the contribution guidelines.
☑ I've checked the issue list before deciding what to submit.
☑ I've edited the README.md and link to my code.

Related Issues or Pull Requests
#427

@HarshCasper @Kajol-Kumari @siddharth25pandey Please let me know what is this merge conflicts means ?
what can I do ?

@HarshCasper @Kajol-Kumari @siddharth25pandey Please let me know what is this merge conflicts means ?
what can I do ?

@Nistha-tech When all the changes in the code occur on different lines or in different files, Git will successfully merge commits without your help. However, when there are conflicting changes on the same lines, a merge conflict occurs because Git doesn’t know which code to keep and which to discard.
Better to send a new PR


Crash on long videos

Hi,
Thank you for the great job. The code works great but it crashes when long videos are being saved after filtering. Is there a way to save long videos faster?
Regards

Hi,
Thanks for the kind words. Unfortunately, the terms of my contract with my new employer prohibits me from working on this code at the moment.
Sorry I can't help further at this time.
Simon


Support the display of page group

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Unable to render Page group properly
Describe the solution you'd like
I want to be able to display a page group using SMART Forms
Describe alternatives you've considered
I can contribute to create this feature
Additional context
page-example.json

Page 1
Page 2

Hi @ryuuzake,
Thanks for contributing! Happy to work through a pull request to get feature into the renderer.
A few points to make:

I think this would be a really good opportunity to use https://mui.com/material-ui/react-pagination/, which will greatly enhance UX.

We know how many pages there are in a Questionnaire, therefore we should be able to use a pagination section to inform how many pages the user has to work through.
User can "skip" pages if they want, i.e clicking on "page 3" while currently on the first page

I'm just thinking about the enableWhen/calculationExpression aspect of this. It might be similar to a "tab", where a tab disappears and appears based on form inputs. Maybe disable the pagination button if the page is "off"?

The spec also highlights this (in https://hl7.org/fhir/extensions/CodeSystem-questionnaire-item-control.html):

This designation may also influence pagination when printing questionnaires.

This means that pagination should also appear in the app's "Preview mode".

Overall, this is a really good addition to the form renderer 👍
Can you create a pull request? Happy to collaborate through some of the points mentioned above.

Hi @fongsean, I'd love to also chime in to this discussion.

1. I think this would be a really good opportunity to use https://mui.com/material-ui/react-pagination/, which will greatly enhance UX.

* We know how many pages there are in a Questionnaire, therefore we should be able to use a pagination section to inform how many pages the user has to work through.

* User can "skip" pages if they want, i.e clicking on "page 3" while currently on the first page

You raised an important point here, and I completely agree that showing the current page and total number of pages would improve the UX. However, I'm afraid that the implementation provided by material UI reference won't render well in a mobile display. As an alternative, I'm thinking about the following mockup:

In this mockup, the user can see the page indicator and the total number of pages. When the user clicks the page indicator, the user can select a different page to visit. The prev/next page button is more accessible, and I make the next page button slightly larger. The intention behind this design is to make it easier for the user to proceed when completing the questionnaire.
I'd love to hear your thoughts on this matter.

First of all, thank you for commenting on the issue
I'll try to address all the points you make:

After tinkering with the source code, I already get it working by copying the Tab logic. I guess your suggestions would make sense. By using pagination, users to able to transverse the Questionnaire more freely
That's a great idea. I haven't test that scenario when tinkering with the source code. Actually, I'm kinda new with the FHIR Item Control Spec and SDC. I'll happy if you could give guide or give json examples for that scenario
Actually I didn't think much about this.. Where can I learn more about this "Preview Mode" in the repo?

Since I'm new, I'd like to confirm some stuff. Mostly about the page spec itself. I have 3 json files containing Questionnaire with a page item. I hope you can help me determine if those examples is within page spec or not.
page-example.json
page.json
page-of-everything.json
Actually this feature request also came with requirements. Some of the requirements are like this:

Page Prev & Next Button is customizeable
Option to show or hide the pagination

I'd like to here you inputs on this. From my side, I thought it would be better if we can expose some kind of zustand store to the end user so that they could change those components more freely

Considering mobile usage is a really good point.
I went though Riza's pull request #947 and those changes look really good. See that thread for PR details.
Those three example Questionnaires are on point. They look great to me.

This feature request also came with requirements. Some of the requirements are like this:

1. Page Prev & Next Button is customizable
2. Option to show or hide the pagination

Customising the renderer is usually done via MUI theming - though I understand that the options are quite limited (colors, box shadows, paddings, etc - but not button sizes). What kind of customisation features do you need to support?
As for the second point, I think we can sidestep the problem completely by not having a pagination.

The spec also highlights this (in https://hl7.org/fhir/extensions/CodeSystem-questionnaire-item-control.html):

This designation may also influence pagination when printing questionnaires.

This means that pagination should also appear in the app's "Preview mode".

If you go to this link https://smartforms.csiro.au/launch?iss=https%3A%2F%2Fproxy.smartforms.io%2Fv%2Fr4%2Ffhir&launch=WzAsInBhdC1zZiIsInByaW1hcnktcGV0ZXIiLCIiLDAsMCwwLCJmaGlyVXNlciBvbmxpbmVfYWNjZXNzIG9wZW5pZCBwcm9maWxlIHBhdGllbnQvQ29uZGl0aW9uLnJzIHBhdGllbnQvT2JzZXJ2YXRpb24ucnMgbGF1bmNoIHBhdGllbnQvRW5jb3VudGVyLnJzIHBhdGllbnQvUXVlc3Rpb25uYWlyZVJlc3BvbnNlLmNydWRzIHBhdGllbnQvUGF0aWVudC5ycyIsImh0dHBzOi8vc21hcnRmb3Jtcy5jc2lyby5hdSIsImE1N2Q5MGUzLTVmNjktNGI5Mi1hYTJlLTI5OTIxODA4NjNjMSIsIiIsIiIsIiIsIiIsMCwxLCJ7XCJyb2xlXCI6XCJxdWVzdGlvbm5haXJlLXJlbmRlci1vbi1sYXVuY2hcIixcImNhbm9uaWNhbFwiOlwiaHR0cDovL3d3dy5oZWFsdGguZ292LmF1L2Fzc2Vzc21lbnRzL21icy83MTV8MC4xLjAtYXNzZW1ibGVkXCIsXCJ0eXBlXCI6XCJRdWVzdGlvbm5haXJlXCJ9IiwiaHR0cHM6Ly9wcm94eS5zbWFydGZvcm1zLmlvL3YvcjQvZmhpciIsZmFsc2Vd, there is a "Preview" button on the left sidebar. That shows a preview of the current form.
This Preview isn't a part of the Questionnaire renderer, it's part of the Smart Forms app.
https://github.com/aehrc/smart-forms/blob/main/apps/smart-forms-app/src/features/renderer/components/FormPreviewPage/FormPreview.tsx
I think having pagination in the preview isn't a good idea after all - given how the "page" extension can be used in a way that the form has "partial" and "full" pages. First thought, It might make sense to have paged previews for "full" pages but not for "partial" pages. But that would make it inconsistent and confuse users.
I think we can hold off from implementing this until there's a real use case for paged previews.
Overall, well done - changes look great!


Minor corrections in servicemonitor.yaml

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
NA

License
Apache 2.0

What's in this PR?
This PR is raised to include a new 'service monitoring' feature for vault. A ServiceMonitor is used to define an application you wish to scrape metrics from within Kubernetes, the controller will action the ServiceMonitors we define and automatically build the required Prometheus configuration. Currently we do not have a service monitor for vault due to which we do not receive any metric related to vault
Why?
We can get vault related metrics post implementing a service monitor
Checklist

[x] Code meets the Developer Guide

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.“aravind-bluescape” seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Please review and merge

The CLA check depends on that you use one of your github registered email addresses for the git commit.


Add an option to allow specifying camera static image size

Add an option to allow the user to specify the height of their live camera static snapshots, vs the default of 277. A value of 0 will not specify any value in the request to Frigate, which appears to return the camera default.
Resolves: https://github.com/blakeblackshear/frigate-hass-integration/issues/19

I haven't seen a way to get the lovelace card to render a larger image. For most people, setting a larger value here will result in a worse experience when using frigate with Home Assistant. It will just make everything load slower and the image will still render the same size. I don't want users to assume that they should be setting a full resolution value here or using the camera.snapshot service for notifications.
Can we let people shoot themselves in the foot? Yes, but then they show up in the ER asking for help.

I don't think that makes sense from a Home Assistant perspective, though.
The async_camera_image method, and camera.snapshot service, are used for many (any!) things beyond just Lovelace. It is in essence a public API, the Home Assistant standard way to get a still from a camera -- and it is genuinely surprising to a Home Assistant user that in the case of the Frigate live camera it returns anything other than a normal fullsize still for that camera as most (or even all?) other primary cameras do.
Usage of (e.g.) a downloader (as suggested on #19 ) is a workaround: Home Assistant has a way to do that downloading, and  camera.snapshot is it :-)
... thus my argument is it will generate support load either way. Either Lovelace will be slow and people won't understand and will complain, or people will ask why the snapshot'd image is so tiny and why they need to configure a downloader for their use case.
=> I think an option is a reasonable compromise? I could move the option into 'Advanced', so it will only show up  when the Home Assistant user has elected to see advanced options -- if that would make  a difference to you?

Does the snapshot service grab a fresh image from the camera when it is called or does it depend on the polling interval?

[Rebased to remove merge conflicts]

I was under the impression that camera.snapshot would be grabbing an old image. I'm good with this once you fix conflicts. I wish the camera view in lovelace could use a smaller resolution image.

Thanks. Conflicts resolved via rebase.


Dismiss view controller when selecting table view cell

Hi all,
Congratulations for this amazing library!
I'm trying to integrate it in one of my personal projects but I'm having a small issue. Right now I'm presenting a view controller with a table view using the library (just like in your example project). I want to dismiss this view controller when selecting a table view cell, the view controller dismisses but for some reason this takes too much time (view controller dismisses approximately 5 seconds after selecting the cell and calling -dismissViewControllerAnimated:completion method). I did a quick test, I added a button to dismiss the view controller and it worked flawlessly, the only issue is on the table view. Also I think is important to state that I do not have any complex code running that could cause a slow performance. Am I doing something wrong? Do I need to set a more advance configuration?
Thanks!

I worked!
Thanks a lot

I worked!
Thanks a lot

You are welcome, if you like it, star it
Thanks.


[vault-provider] Ability to specify secret version

While using kvv2, there are some use cases where we want to specify the vault secret version to be synced and do not assume that it's always the latest version.
It would be great if there's the capability to add an annotation with the specific vault version of the secret that will be synced.

You can specify the remoteRef.version, does that work for you?
Examples are here: https://external-secrets.io/v0.8.1/api/externalsecret/

that will do the thing, thanks @moolen


Cannot delete certain frames

Ensure that none of the frames that form mandatory part of a frame can be deleted independently.

Covered in #32


chore: reformat rxEffect example to remove need for horizontal scrolling

At the moment there's some horizontal scrolling going on the documentation page.
This should remove it and make the example easier to read (as you don't need to scroll to the right anymore)

@nartc nx format:check fails and nx format:write reverts my changes.
Looks like this would need config changes to work (probably prettier?).


Changing 'sender' in signal to be object instead of class

Hello,
Thanks for your work on this module!
Would it be possible to pass the actual view object as the sender of the signal handlers, rather than simply the class of the view?
Using DjangoRESTFramework, I've encountered a situation where I need to generate an email containing a link to a password reset form that is in a React app hosted alongside my DRF API. There is no request context for me to determine the domain, since the signal 'sender' is only the class, and not the actual object that generated the signal. There is also a design consideration that prevents me from simply hard-coding the domain value in the application settings.
If the signal sender passed was the actual instance(view) that generated the signal, then I could use the .request attribute of the view.
I think this would be a small/easy/backward compatible change.
Thanks for your consideration,
Joel

Hi,
I wouldn't want to change sender to be an instance, but in the spirit of Djangos post_save/pre_save/... signal I could add instance= here:
https://github.com/anx-ckreuzberger/django-rest-passwordreset/blob/53123f94b42f5ad918f1ec7d339623d3752ce961/django_rest_passwordreset/views.py#L144-L146
                # send a signal that the password token was created
                # let whoever receives this signal handle sending the email for the password reset
                reset_password_token_created.send(sender=self.__class__, instance=self, reset_password_token=token)

Released in 1.0.0alpha3
https://github.com/anx-ckreuzberger/django-rest-passwordreset/releases/tag/1.0.0a3

Great. This should solve my problem.
Thanks for getting to this so quickly!


added windows 11

after reading this article, i confirmed windows 11 is supported

Learn Build status updates of commit 3ca3886:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/network-security-force-logoff-when-logon-hours-expire.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Only allow magic link sign in with the Auth component

Feature request
Is your feature request related to a problem? Please describe.
I would like to only allow the use of magic link (no password sign in)
Describe the solution you'd like
Maybe a flag noPasswordAuth?
Describe alternatives you've considered
Tried this:
magicLink
view="magic_link"

However there's still a link to go to the sign_in view
Additional context
I personally don't want to store passwords, be responsible for passwords,  or allow for passwords

Auth component is being deprecated.
It will be replaced with Auth UI
I have been working on updating the new component to work with child components for exactly this use case.
The current component your using may be able to use <Auth.MagicLink/>, although I haven't tried it myself to be honest.

Ooo very nice, I'll give that a shot. I noticed that it's written in typescript but it seems like types arent exported?
Could not find a declaration file for module '@supabase/auth-ui-react'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/supabase__auth-ui-react` if it exists or add a new declaration (.d.ts) file containing `declare module '@supabase/auth-ui-react';`ts(7016)

Any ideas on what could be going on?

its prerelease currently, i think it's pending to be done

if you fancy adding that in feel free to pull request some changes if you like. I won't have time to work on this until next week

expect breaking changes btw. especially in regards to the theme/customization.
I'll probably change it so you have to explicitly import the theme into the component.
something like...
import Auth, { themes } from '@supabase/auth-ui-react'

<Auth appearance={{theme: themes.supabase }} />

The auth component has been moved to it's own repo and package.
github.com/supabase-community/auth-ui.
You can also read the docs for auth ui here.


5.10.24 is now stable

Hello,
Could you pls update the latest to 5.10.24? :)
https://community.ubnt.com/t5/UniFi-Routing-Switching/UniFi-Network-Controller-5-10-24-Stable-has-been-released/

Update, building now on Docker Cloud. Should be available ~1h after this post.


add license file

It would help the exposure and discoverability if license file would be included, which is recognized by the github system

I am not so good at this github thing. if you create a pull request for what you suggest, I will accept it.


Pm2 Log Errors - How can i solve these errors ? Screen goes black after a while

/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:46.51.216] [WARN]  You're using a full whitelist configuration to allow for all IPs
Tue, 28 Dec 2021 12:46:51 GMT express deprecated res.send(status): Use res.sendStatus(status) instead at modules/MMM-Remote-Control/node_helper.js:138:25
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:48.37.248] [ERROR] WARNING! Could not validate config file. Starting with default configuration. Please correct syntax errors at or above this line: /home/pi/MagicMirror/config/config.js:90
		{
		^
SyntaxError: Unexpected token '{'
    at wrapSafe (internal/modules/cjs/loader.js:986:16)
    at Module._compile (internal/modules/cjs/loader.js:1034:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1108:10)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at loadConfig (/home/pi/MagicMirror/js/app.js:69:14)
    at App.start (/home/pi/MagicMirror/js/app.js:212:3)
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:50.25.169] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:52.34.401] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:54.24.598] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:56.15.696] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 13:57.12.836] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:03.35.703] [WARN]  You're using a full whitelist configuration to allow for all IPs
[28.12.2021 14:12.06.071] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:19.11.743] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:21.01.131] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:22.10.511] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:23.36.657] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:25.07.967] [ERROR] WARNING! Could not validate config file. Starting with default configuration. Please correct syntax errors at or above this line: /home/pi/MagicMirror/config/config.js:143
{
^
SyntaxError: Unexpected token '{'
    at wrapSafe (internal/modules/cjs/loader.js:986:16)
    at Module._compile (internal/modules/cjs/loader.js:1034:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1108:10)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at loadConfig (/home/pi/MagicMirror/js/app.js:69:14)
    at App.start (/home/pi/MagicMirror/js/app.js:212:3)
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:26.33.999] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:28.47.516] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:29.16.076] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[28.12.2021 14:31.13.222] [WARN]  You're using a full whitelist configuration to allow for all IPs
Gdk-Message: 23:00:00.970: electron: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
XIO:  fatal IO error 62 (Der virtuelle Zeitnehmer ist abgelaufen) on X server ":0"
after 11902688 requests (11902688 known processed) with 0 events remaining.
[28.12.2021 23:02.28.676] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:02.36.709] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:02.45.547] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:02.52.936] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:03.11.406] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:03.21.152] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:03.29.015] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:03.38.495] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:03.43.583] [WARN]  You're using a full whitelist configuration to allow for all IPs
Invalid MIT-MAGIC-COOKIE-1 key/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[28.12.2021 23:04.08.158] [WARN]  You're using a full whitelist configuration to allow for all IPs
[29.12.2021 06:27.59.070] [ERROR] Calendar Error. Could not fetch calendar:  http://p12-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79mZRTz4px5MNIbzMHGisQCPVn-bb7-rMKJRQXT-HvKaLs2H8xYBU6yq8si1DE_1Po Error: Internal Server Error
at NodeHelper.checkFetchStatus (/home/pi/MagicMirror/js/node_helper.js:121:9)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
[29.12.2021 11:49.56.931] [ERROR] Calendar Error. Could not fetch calendar:  http://p12-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79mZRTz4px5MNIbzMHGisQCPVn-bb7-rMKJRQXT-HvKaLs2H8xYBU6yq8si1DE_1Po Error: Bad Request
at NodeHelper.checkFetchStatus (/home/pi/MagicMirror/js/node_helper.js:121:9)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[29.12.2021 15:28.38.305] [WARN]  You're using a full whitelist configuration to allow for all IPs
Gdk-Message: 16:22:09.780: electron: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
[29.12.2021 16:23.10.686] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[29.12.2021 16:23.58.486] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[29.12.2021 16:24.22.567] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[29.12.2021 16:32.14.842] [WARN]  You're using a full whitelist configuration to allow for all IPs
[29.12.2021 16:37.41.656] [WARN]  You're using a full whitelist configuration to allow for all IPs
XIO:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server ":0"
after 41529100 requests (41529100 known processed) with 0 events remaining.
Gdk-Message: 22:25:08.953: electron: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[30.12.2021 22:27.46.806] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[30.12.2021 22:28.24.729] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[30.12.2021 22:28.34.006] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[30.12.2021 22:33.18.173] [WARN]  You're using a full whitelist configuration to allow for all IPs
<--- Last few GCs --->
[3787:0x6103000] 101962762 ms: Mark-sweep 876.8 (983.0) -> 870.2 (982.8) MB, 3464.2 / 40.3 ms  (average mu = 0.990, current mu = 0.993) allocation failure scavenge might not succeed
[3787:0x6103000] 101966444 ms: Scavenge 871.4 (982.8) -> 870.5 (982.8) MB, 26.0 / 0.1 ms  (average mu = 0.990, current mu = 0.993) allocation failure
[3787:0x6103000] 101974528 ms: Scavenge 871.4 (982.8) -> 870.5 (983.8) MB, 7.5 / 0.1 ms  (average mu = 0.990, current mu = 0.993) allocation failure
<--- JS stacktrace --->
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
[01.01.2022 11:23.07.634] [WARN]  You're using a full whitelist configuration to allow for all IPs
<--- Last few GCs --->
[3302:0x75aa000] 105228928 ms: Mark-sweep 876.4 (983.5) -> 875.0 (983.5) MB, 3956.5 / 0.6 ms  (average mu = 0.471, current mu = 0.450) allocation failure scavenge might not succeed
[3302:0x75aa000] 105241072 ms: Mark-sweep 876.4 (983.5) -> 875.1 (983.8) MB, 6107.0 / 0.7 ms  (average mu = 0.486, current mu = 0.497) allocation failure scavenge might not succeed
<--- JS stacktrace --->
[02.01.2022 20:10.50.593] [ERROR] (node:3251) UnhandledPromiseRejectionWarning: Error: fatal: Konnte '/home/pi/MagicMirror/modules/MMM-MyGarbage/.git/index.lock' nicht erstellen: Keine Berechtigung
at Object.action (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/plugins/error-detection.plugin.js:30:33)
at PluginStore.exec (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/plugins/plugin-store.js:21:33)
at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:95:45
at new Promise (<anonymous>)
at GitExecutorChain.handleTaskData (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:93:16)
at GitExecutorChain.<anonymous> (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:77:46)
at Generator.next (<anonymous>)
at fulfilled (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:5:58)

(Use electron --trace-warnings ... to show where the warning was created)
[02.01.2022 20:10.50.596] [ERROR] (node:3251) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[02.01.2022 20:10.50.601] [ERROR] (node:3251) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[02.01.2022 20:10.51.843] [ERROR] (node:3251) UnhandledPromiseRejectionWarning: Error: fatal: Konnte '/home/pi/MagicMirror/modules/MMM-MyGarbage/.git/index.lock' nicht erstellen: Keine Berechtigung
at Object.action (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/plugins/error-detection.plugin.js:30:33)
at PluginStore.exec (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/plugins/plugin-store.js:21:33)
at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:95:45
at new Promise (<anonymous>)
at GitExecutorChain.handleTaskData (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:93:16)
at GitExecutorChain.<anonymous> (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:77:46)
at Generator.next (<anonymous>)
at fulfilled (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/lib/runners/git-executor-chain.js:5:58)

[02.01.2022 20:10.51.844] [ERROR] (node:3251) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)

what mm version?
grep version ~/MagicMirror/package.json
what node and npm version
node -v
npm -v
what os?
lsb_release -a
how did u get here? install today, or upgrade
in either case how did u do it? manual or automated?

what mm version?
2.18.0
grep version ~/MagicMirror/package.json
what node and npm version
node -v
v16.13.1
npm -v
8.1.2
what os?
lsb_release -a
how did u get here? install today, or upgrade
i installed it with the script from your site https://github.com/sdetweil/MagicMirror_scripts
in either case how did u do it? manual or automated?

also, could you post ~/install.log
I just redid install on bullseye and it worked fine.. same node/npm/pm2
~/MagicMirror $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

thanks.. can u give results of
lsb_release -a

No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

also, could you post ~/install.log
I just redid install on bullseye and it worked fine.. same node/npm/pm2
~/MagicMirror $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

install starting  - Di Dez 28 12:51:23 CET 2021
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
Installing helper tools ...
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....

Vorgeschlagene Pakete:
doc-base
Die folgenden NEUEN Pakete werden installiert:
pv
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Es müssen 46,4 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 113 kB Plattenplatz zusätzlich benutzt.
Holen:1 https://archive.raspbian.org/raspbian buster/main armhf pv armhf 1.6.6-1 [46,4 kB]
Es wurden 46,4 kB in 0 s geholt (160 kB/s).
Vormals nicht ausgewähltes Paket pv wird gewählt.
(Lese Datenbank ...

Vorbereitung zum Entpacken von .../archives/pv_1.6.6-1_armhf.deb ...
Entpacken von pv (1.6.6-1) ...
pv (1.6.6-1) wird eingerichtet ...
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Updating packages ...
OK:1 http://phoscon.de/apt/deconz buster InRelease OK:2 http://archive.raspberrypi.org/debian buster InRelease OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:4 https://repos.influxdata.com/debian buster InRelease OK:5 https://archive.raspbian.org/raspbian buster InRelease OK:6 https://deb.nodesource.com/node_16.x buster InRelease Paketlisten werden gelesen...
apt-get update  completed ok
apt-get upgrade  started
apt upgrade result =rc=0 Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Paketaktualisierung (Upgrade) wird berechnet...
Die folgenden Pakete sind zurückgehalten worden:
deconz
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v14.0.0
Installed Node version: v16.13.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V8.1.2
No npm upgrade necessary.
It seems like MagicMirror is already installed.
To prevent overwriting, the installer will be aborted.
Please rename the ~/MagicMirror folder and try again.
install starting  - Di Dez 28 13:27:02 CET 2021
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
Installing helper tools ...
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....

Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Paketaktualisierung (Upgrade) wird berechnet...
Die folgenden Pakete sind zurückgehalten worden:
deconz
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v14.0.0
Installed Node version: v16.13.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V8.1.2
No npm upgrade necessary.
It seems like MagicMirror is already installed.
To prevent overwriting, the installer will be aborted.
Please rename the ~/MagicMirror folder and try again.
If you want to upgrade your installation run upgrade-script from the ~/MagicMirror/installers directory.
install starting  - Di Dez 28 13:30:39 CET 2021
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
Installing helper tools ...
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....

Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Paketaktualisierung (Upgrade) wird berechnet...
Die folgenden Pakete sind zurückgehalten worden:
deconz
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v14.0.0
Installed Node version: v16.13.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V8.1.2
No npm upgrade necessary.
Cloning MagicMirror ...
Cloning MagicMirror Done!
Installing dependencies ...

<EMAIL_ADDRESS>install > echo "Installing vendor files ... > " && cd vendor && npm install --loglevel=error Installing vendor files ... added 9 packages, and audited 10 packages in 5s found 0 vulnerabilities ><EMAIL_ADDRESS>postinstall > npm run install-fonts && echo "MagicMirror installation finished successfully! > " ><EMAIL_ADDRESS>install-fonts > echo "Installing fonts ... > " && cd fonts && npm install --loglevel=error Installing fonts ... added 1 package, and audited 2 packages in 2s found 0 vulnerabilities MagicMirror installation finished successfully! ><EMAIL_ADDRESS>prepare > [ -f node_modules/.bin/husky ] && husky install || echo no husky installed. no husky installed. added 292 packages, and audited 293 packages in 3m 21 packages are looking for funding run npm fund for details found 0 vulnerabilities
Dependencies installation Done!
fixing sandbox permissions
setting up initial config.js
Check plymouth installation ...
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.
Splashscreen: Changed theme to MagicMirror successfully.
install and setup pm2
pm2 not installed, installing
pm2 install result npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. added 180 packages, and audited 181 packages in 38s 10 packages are looking for funding run npm fund for details found 0 vulnerabilities
get the pm2 platform specific startup command
startup command = sudo env PATH=$PATH:/usr/bin:/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi
[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target

[Service]
Type=forking
User=pi
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=$PATH:/usr/bin:/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/home/pi/.pm2/pm2.pid
Restart=on-failure
ExecStart=/usr/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/lib/node_modules/pm2/bin/pm2 kill
[Install]
WantedBy=multi-user.target
Target path
/etc/systemd/system/pm2-pi.service
Command list
[ 'systemctl enable pm2-pi' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
[PM2] Making script booting at startup...
[PM2] [-] Executing: systemctl enable pm2-pi...
[PM2] [v] Command successfully executed.
+---------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save
[PM2] Remove init script via:
$ pm2 unstartup systemd
pm2 startup command done
configure the pm2 config file for MagicMirror
start MagicMirror via pm2 now
save MagicMirror pm2 config now
stop MagicMirror via pm2 now
gsettings screen saver already disabled
screensaver via lightdm already disabled
lxsession screen saver already disabled
We're ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.
install completed - Di Dez 28 13:35:45 CET 2021

how did u get node 16 installed?  my script (before Saturday) only installed node 14

also, output of uname -a

how did u get node 16 installed? my script (before Saturday) only installed node 14

i had a previous installation before but i deleted it because there were the same issue with the blackscreen after a while and i want to give it a try with a fresh installation

Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux

Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux

also, output of uname -a

Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux

did u accidentally close?
the answer for how you got node 16 didn't help me..
did u install node manually before starting my install???

did u accidentally close?

yes i reopen it

the answer for how you got node 16 didn't help me..

did u install node manually before starting my install???

could be that i installed it with the previous installation manually

hm.. i can't reproduce it..
reflashed buster (legacy)
manually copied  2.17.1 (clone gets 2.18)
changed local copy of install script to not clone, as I already had it..
install script installed node v16.13.1 and npm 8.1.2
then installed  MM and pm2, and started mm ok, with initial config.js
what pi is this?  free -m might tell me..
i have a 4 gig pi 4
free -m
              total        used        free      shared  buff/cache   available
Mem:           3838         382        1724         297        1731        3018

so, i suggest u reflash the sd card and after boot, use my script to install again.. (it does all the work)
this will get you 2.18, and node 16

so, i suggest u reflash the sd card and after boot, use my script to install again.. (it does all the work)
this will get you 2.18, and node 16

sry but im not willing to reflash the sd card. This will delete all my other changes. Is there a way to do it with reflashing the sd card ?

hm.. i can't reproduce it.. reflashed buster (legacy) manually copied 2.17.1 (clone gets 2.18) changed local copy of install script to not clone, as I already had it.. install script installed node v16.13.1 and npm 8.1.2 then installed MM and pm2, and started mm ok, with initial config.js
what pi is this? free -m might tell me.. i have a 4 gig pi 4
free -m
              total        used        free      shared  buff/cache   available
Mem:           3838         382        1724         297        1731        3018

Yes its a 4gb pi 4
       total        used        free      shared  buff/cache   available

Mem:           3838        2177         419         234        1241        1505
Swap:            99          99           0

i do not know.. something is messed up. I don't know what.

can i delete Magic mirror and the rest ?

sure, just delete the folder..  rm -rf ~/MagicMirror
to remove pm2
pm2 unstartup systemd
(it will give u a command to copy/paste to execute)
then
sudo npm uninstall pm2
after doing this reboot
then u can run the MM installer script again

sure, just delete the folder.. rm -rf ~/MagicMirror
to remove pm2
pm2 unstartup systemd (it will give u a command to copy/paste to execute) then sudo npm uninstall pm2
after doing this reboot
then u can run the MM installer script again

doing it right now. how can i check if it works ?

it will start MM if u say yes to pm2.

it will start MM if u say yes to pm2.
otherwise (if u say no to use pm2) in the MagicMirror folder do
npm start

your recommandation is to use pm2 ?

yes, if u want it to start on boot, and keep running if it crashes, and record the output in case of problems..
all things u have to develop solutions for yourself otherwise..

now everything i alive. i installed the remote controller. but i cant restart it. Got this

the remote module  defaults to the pm2 process name is 'mm'..
my setup script does 'MagicMirror'
so u have to set it in remote module config
pm2ProcessName: 'MagicMirror'

did it but nothing change..

so that is in the module config section, right?
{
   module:
   position:
   config: {
       pm2ProcessName: 'MagicMirror'
    }
}

the module doesn't put out any debug info.. sorry, thats all I know about that module (from looking at the code)

/*************** AUTO GENERATED BY REMOTE CONTROL MODULE ***************/
var config =
{
address: '<IP_ADDRESS>',
electronOptions: {
fullscreen: true,
width: 3840,
x: 1920
},
ipWhitelist: [],
language: 'de',
modules: [
{
module: 'alert',
config: {}
},
{
module: 'updatenotification',
position: 'top_bar',
config: {}
},
{
module: 'clock',
position: 'top_left',
config: {}
},
{
module: 'calendar',
header: 'Termine',
position: 'top_left',
config: {
calendars: [
{
symbol: 'calendar-check',
url: 'webcal://p12-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79mZRTz4px5MNIbzMHGisQCPVn-bb7-rMKJRQXT-HvKaLs2H8xYBU6yq8si1DE_1Po'
}
]
}
},
{
module: 'compliments',
position: 'top_center',
config: {
compliments: {
anytime: [
'Na du!'
],
morning: [
'Guten morgen',
'Genies deinen Tag!'
],
afternoon: [
'Du siehst gut aus!'
],
evening: [
'Bettzeit',
'Schlaf gut',
'Ab ins Bett'
],
'....-01-01': [
'Happy new year!'
]
}
},
header: ''
},
{
module: 'weather',
position: 'top_right',
config: {
location: 'Solingen',
locationID: '2831580',
apiKey: '4044c29102789952012565d2d4e9d58e',
iconTable: {
'01d': 'wi-day-sunny',
'02d': 'wi-day-cloudy',
'03d': 'wi-cloudy',
'04d': 'wi-cloudy-windy',
'09d': 'wi-showers',
'10d': 'wi-rain',
'11d': 'wi-thunderstorm',
'13d': 'wi-snow',
'50d': 'wi-fog',
'01n': 'wi-night-clear',
'02n': 'wi-night-cloudy',
'03n': 'wi-night-cloudy',
'04n': 'wi-night-cloudy',
'09n': 'wi-night-showers',
'10n': 'wi-night-rain',
'11n': 'wi-night-thunderstorm',
'13n': 'wi-night-snow',
'50n': 'wi-night-alt-cloudy-windy'
}
}
},
{
module: 'weather',
position: 'top_right',
header: 'Wettervorhersage',
config: {
type: 'forecast',
location: 'Solingen',
locationID: '2831580',
apiKey: '4044c29102789952012565d2d4e9d58e'
}
},
{
module: 'newsfeed',
position: 'bottom_bar',
config: {
feeds: [
{
title: 'Tagesschau',
url: 'http://www.tagesschau.de/xml/rss2/'
}
]
}
},
{
module: 'MMM-Remote-Control',
header: '',
config: {
apiKey: '8dfc4a766ebd4c05839e37cce0807310',
pm2ProcessName: 'MagicMirror'
}
},
{
module: 'MMM-iHaveBeenThere',
position: 'fullscreen_below',
header: '',
config: {
success: true,
query: {
data: 'defaultConfig',
module: 'MMM-iHaveBeenThere'
},
data: {
title: '',
AnimationEnabled: true,
pauseDuration: 3,
animationDuration: 10,
displayDesc: false,
zoomLevel: 1.5,
zoomLongitude: -20,
zoomLatitude: 60,
home_lat: 51.1597436635867,
home_lon: 7.00222741009367,
home_desc: 'Solingen',
away_lat: [
25.7741728,
21.1617854,
40.8998,
41.3874,
'52.520008',
'48.137154',
'-22.485331392'
],
away_lon: [
-80.19362,
-86.8510468,
9.5161,
2.1686,
'13.404954',
'11.576124',
'17.4631'
],
away_desc: [
'Miami',
'México ',
'Sardinien',
'Barcelona ',
'Berlin',
'München ',
'Namibia '
],
trip: [
false,
false,
false,
false
],
colorCountries: '#BDBDBD',
colorCountryBorders: '#000000',
colorTargetPoints: '#FFFFFF',
colorPlane: '#FF0000',
colorPlaneLine: '#FFFFFF',
colorLegendBorder: '#FFFFFF',
colorLegendFont: '#FFFFFF',
colorTitleFont: '#FFFFFF'
},
title: '',
home_lat: 51.1597436635867,
home_lon: 7.00222741009367,
away_desc: [
'Miami',
'México',
'Sardinien',
'Barcelona ',
'Berlin ',
'München ',
'Namibia'
],
displayDesc: false,
away_lat: [
25.7741728,
21.1617854,
40.8998,
41.3874,
'52.520008',
'48.137154',
'-22.485331392'
],
away_lon: [
-80.19362,
-86.8510468,
9.5161,
2.1686,
'13.404954',
'11.576124',
'17.4631'
],
home_desc: 'Solingen',
trip: [
false,
false,
false,
false
],
zoomLevel: 1.5,
zoomLatitude: 30,
zoomLongitude: -50
}
},
{
module: 'MMM-MyGarbage',
position: 'top_left',
header: '',
config: {
success: true,
query: {
data: 'defaultConfig',
module: 'MMM-MyGarbage'
},
data: {
alert: false,
weeksToDisplay: 3,
limitTo: 99,
dateFormat: 'dddd D MMMM',
fade: true,
fadePoint: 0.25
}
}
}
],
useHttps: false,
httpsPrivateKey: '',
httpsCertificate: '',
locale: 'en-US'
}
/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== 'undefined') {module.exports = config;}

You mean i have to put it into the config.js file. like i post above.

Done.. Where i have to place it ?

but we are past the original error..  system is running now

Done.. Where i have to place it ?

u did it correctly. (many users don't understand config:{} is parms TO the module..)
i don't know what the module problem is.. as I said, there is no debug info produced
I have a module that restarts MM via pm2, but uses my own code, and not the library he uses..
here is about MagicMirror, not any modules.

is there any way to check the hole system in futher ? where i have an eye on it ?

Thats what i found in the error log of pm2
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
what does it mean ?

did u stop and restart magicmirror?  it has to kill electron to restart it  (in linux that is a signal)

in the console with pm2 restart MagicMirror

yes, so it has to kill the prior to start another... so it sends an interrupt signal (SIGINT)

means this isn't an issue, right ?

correct, this is normal

Hi again, after a while working. Screen turns into blackscreen and i have to start the magic mirror via remote control to get back the view.
Here is the log:
PM2        | 2022-01-07T21:57:33: PM2 log: pid=32343 msg=process killed
PM2        | 2022-01-07T21:57:33: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-07T21:57:33: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-07T21:57:42: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=process killed
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-09T21:39:44: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-09T21:39:44: PM2 log: pid=25252 msg=process killed
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] online
/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | [07.01.2022 21:57.40.285] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir | [07.01.2022 21:57.46.055] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir |
0|MagicMir | <--- Last few GCs --->
0|MagicMir |
0|MagicMir | [1:0x2e160000] 104344852 ms: Scavenge 879.9 (981.0) -> 879.0 (981.0) MB, 10.3 / 0.1 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir | [1:0x2e160000] 104349947 ms: Scavenge 879.9 (981.0) -> 879.0 (982.0) MB, 6.8 / 0.0 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir | [1:0x2e160000] 104354859 ms: Scavenge 880.0 (982.0) -> 879.1 (984.0) MB, 11.9 / 0.7 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir |
0|MagicMir |
0|MagicMir | <--- JS stacktrace --->
0|MagicMir |
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | [09.01.2022 21:39.48.751] [WARN]  You're using a full whitelist configuration to allow for all IPs
/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|MagicMir | [10.01.2022 17:46.24.490] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [10.01.2022 17:48.19.392] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [10.01.2022 17:48.20.285] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [10.01.2022 17:51.24.823] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [10.01.2022 17:53.21.458] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [10.01.2022 17:53.22.209] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [10.01.2022 17:56.25.164] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [10.01.2022 17:58.23.263] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [10.01.2022 17:58.24.087] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [10.01.2022 18:01.25.491] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [10.01.2022 18:03.25.085] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [10.01.2022 18:03.25.775] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [10.01.2022 18:06.25.823] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [10.01.2022 18:08.26.970] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [10.01.2022 18:08.27.714] [INFO]  Calendar-Fetcher: Broadcasting 2 events.

you need to clear the logs or print more of them
the issues at the top are from Jan 7, and the stuff from below from Jan 10
do
pm2 stop all
pm2 flush
pm2 start MagicMirror

then when it fails. pm2 stop all
pm2 logs --lines=100 >somefile.txt
ctrl-c
then examine somefile.txt

PM2        | 2022-01-04T23:00:57: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2022-01-04T23:00:57: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2022-01-04T23:00:57: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2022-01-04T23:00:57: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2022-01-04T23:00:57: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2022-01-04T23:00:57: PM2 log: Worker Interval      : 30000
PM2        | 2022-01-04T23:00:57: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2022-01-04T23:00:57: PM2 log: Concurrent actions   : 2
PM2        | 2022-01-04T23:00:57: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-01-04T23:00:57: PM2 log: ===============================================================================
PM2        | 2022-01-04T23:00:57: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-04T23:00:58: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-04T23:20:43: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-04T23:20:43: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:43: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:43: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:43: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:43: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:44: PM2 log: pid=1124 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-04T23:20:45: PM2 log: Process with pid 1124 still alive after 1600ms, sending it SIGKILL now...
PM2        | 2022-01-04T23:20:45: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGKILL]
PM2        | 2022-01-04T23:20:45: PM2 log: pid=1124 msg=process killed
PM2        | 2022-01-04T23:20:45: PM2 log: PM2 successfully stopped
PM2        | 2022-01-04T23:21:40: PM2 log: ===============================================================================
PM2        | 2022-01-04T23:21:40: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2        | 2022-01-04T23:21:40: PM2 log: Time                 : Tue Jan 04 2022 23:21:40 GMT+0100 (Mitteleuropäische Normalzeit)
PM2        | 2022-01-04T23:21:40: PM2 log: PM2 version          : 5.1.2
PM2        | 2022-01-04T23:21:40: PM2 log: Node.js version      : 16.13.1
PM2        | 2022-01-04T23:21:40: PM2 log: Current arch         : arm
PM2        | 2022-01-04T23:21:40: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2022-01-04T23:21:40: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2022-01-04T23:21:40: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2022-01-04T23:21:40: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2022-01-04T23:21:40: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2022-01-04T23:21:40: PM2 log: Worker Interval      : 30000
PM2        | 2022-01-04T23:21:40: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2022-01-04T23:21:40: PM2 log: Concurrent actions   : 2
PM2        | 2022-01-04T23:21:40: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-01-04T23:21:40: PM2 log: ===============================================================================
PM2        | 2022-01-04T23:21:40: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-04T23:21:41: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-06T10:07:48: PM2 log: App [MagicMirror:0] exited with code [1] via signal [SIGINT]
PM2        | 2022-01-06T10:07:48: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-06T10:07:48: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-06T10:07:49: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-06T10:07:49: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-06T10:07:49: PM2 log: pid=18092 msg=process killed
PM2        | 2022-01-06T10:07:49: PM2 log: PM2 successfully stopped
PM2        | 2022-01-06T10:08:37: PM2 log: ===============================================================================
PM2        | 2022-01-06T10:08:37: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2        | 2022-01-06T10:08:37: PM2 log: Time                 : Thu Jan 06 2022 10:08:37 GMT+0100 (Mitteleuropäische Normalzeit)
PM2        | 2022-01-06T10:08:37: PM2 log: PM2 version          : 5.1.2
PM2        | 2022-01-06T10:08:37: PM2 log: Node.js version      : 16.13.1
PM2        | 2022-01-06T10:08:37: PM2 log: Current arch         : arm
PM2        | 2022-01-06T10:08:37: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2022-01-06T10:08:37: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2022-01-06T10:08:37: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2022-01-06T10:08:37: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2022-01-06T10:08:37: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2022-01-06T10:08:37: PM2 log: Worker Interval      : 30000
PM2        | 2022-01-06T10:08:37: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2022-01-06T10:08:37: PM2 log: Concurrent actions   : 2
PM2        | 2022-01-06T10:08:37: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-01-06T10:08:37: PM2 log: ===============================================================================
PM2        | 2022-01-06T10:08:38: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-06T10:08:38: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-06T14:02:58: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-06T14:02:59: PM2 log: pid=1179 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-06T14:02:59: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-06T14:02:59: PM2 log: pid=1179 msg=process killed
PM2        | 2022-01-06T14:02:59: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-06T14:02:59: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-07T21:57:33: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-07T21:57:33: PM2 error: Process with pid 32343 already exists
PM2        | 2022-01-07T21:57:33: PM2 log: pid=32343 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-07T21:57:33: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-07T21:57:33: PM2 log: pid=32343 msg=process killed
PM2        | 2022-01-07T21:57:33: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-07T21:57:33: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-07T21:57:42: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=failed to kill - retrying in 100ms
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-07T21:57:42: PM2 log: pid=25113 msg=process killed
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-07T21:57:42: PM2 log: App [MagicMirror:0] online
PM2        | 2022-01-09T21:39:44: PM2 log: Stopping app:MagicMirror id:0
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
PM2        | 2022-01-09T21:39:44: PM2 log: pid=25252 msg=process killed
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2        | 2022-01-09T21:39:44: PM2 log: App [MagicMirror:0] online
/home/pi/.pm2/logs/MagicMirror-error.log last 100 lines:
0|MagicMir |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|MagicMir |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|MagicMir |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|MagicMir |   type: 'system',
0|MagicMir |   errno: 'EAI_AGAIN',
0|MagicMir |   code: 'EAI_AGAIN'
0|MagicMir | }
0|MagicMir |
0|MagicMir | <--- Last few GCs --->
0|MagicMir |
0|MagicMir | [1:0x29560000] 105082952 ms: Mark-sweep 880.6 (983.3) -> 879.4 (983.3) MB, 5995.8 / 0.7 ms  (average mu = 0.355, current mu = 0.356) allocation failure scavenge might not succeed
0|MagicMir | [1:0x29560000] 105093208 ms: Mark-sweep 880.7 (983.3) -> 879.5 (983.0) MB, 6254.6 / 0.6 ms  (average mu = 0.374, current mu = 0.390) allocation failure scavenge might not succeed
0|MagicMir |
0|MagicMir |
0|MagicMir | <--- JS stacktrace --->
0|MagicMir |
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | [07.01.2022 21:57.40.285] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir | [07.01.2022 21:57.46.055] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir |
0|MagicMir | <--- Last few GCs --->
0|MagicMir |
0|MagicMir | [1:0x2e160000] 104344852 ms: Scavenge 879.9 (981.0) -> 879.0 (981.0) MB, 10.3 / 0.1 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir | [1:0x2e160000] 104349947 ms: Scavenge 879.9 (981.0) -> 879.0 (982.0) MB, 6.8 / 0.0 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir | [1:0x2e160000] 104354859 ms: Scavenge 880.0 (982.0) -> 879.1 (984.0) MB, 11.9 / 0.7 ms  (average mu = 0.928, current mu = 0.480) allocation failure
0|MagicMir |
0|MagicMir |
0|MagicMir | <--- JS stacktrace --->
0|MagicMir |
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|MagicMir | [09.01.2022 21:39.48.751] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir | [11.01.2022 01:15.57.310] [ERROR] Calendar Error. Could not fetch calendar:  http://p56-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79JvdPX6r9UFvNEbDQfZ_Ti7-MNH3DCOSBWr83Zc7ZvwkTvaostuA1ApLkAw8ROCqw FetchError: request to http://p56-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79JvdPX6r9UFvNEbDQfZ_Ti7-MNH3DCOSBWr83Zc7ZvwkTvaostuA1ApLkAw8ROCqw failed, reason: getaddrinfo EAI_AGAIN p56-caldav.icloud.com
0|MagicMir |     at ClientRequest. (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1483:11)
0|MagicMir |     at ClientRequest.emit (node:events:394:28)
0|MagicMir |     at Socket.socketErrorListener (node:_http_client:447:9)
0|MagicMir |     at Socket.emit (node:events:394:28)
0|MagicMir |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|MagicMir |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|MagicMir |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|MagicMir |   type: 'system',
0|MagicMir |   errno: 'EAI_AGAIN',
0|MagicMir |   code: 'EAI_AGAIN'
0|MagicMir | }
0|MagicMir | [11.01.2022 01:17.46.873] [ERROR] Calendar Error. Could not fetch calendar:  http://p12-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79mZRTz4px5MNIbzMHGisQCPVn-bb7-rMKJRQXT-HvKaLs2H8xYBU6yq8si1DE_1Po FetchError: request to http://p12-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79mZRTz4px5MNIbzMHGisQCPVn-bb7-rMKJRQXT-HvKaLs2H8xYBU6yq8si1DE_1Po failed, reason: getaddrinfo EAI_AGAIN p12-caldav.icloud.com
0|MagicMir |     at ClientRequest. (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1483:11)
0|MagicMir |     at ClientRequest.emit (node:events:394:28)
0|MagicMir |     at Socket.socketErrorListener (node:_http_client:447:9)
0|MagicMir |     at Socket.emit (node:events:394:28)
0|MagicMir |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|MagicMir |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|MagicMir |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|MagicMir |   type: 'system',
0|MagicMir |   errno: 'EAI_AGAIN',
0|MagicMir |   code: 'EAI_AGAIN'
0|MagicMir | }
0|MagicMir | [11.01.2022 01:18.15.014] [ERROR] Newsfeed Error. Could not fetch newsfeed:  http://www.tagesschau.de/xml/rss2/ FetchError: request to http://www.tagesschau.de/xml/rss2/ failed, reason: getaddrinfo EAI_AGAIN www.tagesschau.de
0|MagicMir |     at ClientRequest. (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1483:11)
0|MagicMir |     at ClientRequest.emit (node:events:394:28)
0|MagicMir |     at Socket.socketErrorListener (node:_http_client:447:9)
0|MagicMir |     at Socket.emit (node:events:394:28)
0|MagicMir |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|MagicMir |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|MagicMir |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|MagicMir |   type: 'system',
0|MagicMir |   errno: 'EAI_AGAIN',
0|MagicMir |   code: 'EAI_AGAIN'
0|MagicMir | }
0|MagicMir | [11.01.2022 01:21.37.368] [ERROR] Calendar Error. Could not fetch calendar:  http://p56-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79JvdPX6r9UFvNEbDQfZ_Ti7-MNH3DCOSBWr83Zc7ZvwkTvaostuA1ApLkAw8ROCqw FetchError: request to http://p56-caldav.icloud.com/published/2/MTk3NDg4NzIwOTE5NzQ4OJen2vZPDPO6ZjKDI5IIr79JvdPX6r9UFvNEbDQfZ_Ti7-MNH3DCOSBWr83Zc7ZvwkTvaostuA1ApLkAw8ROCqw failed, reason: getaddrinfo EAI_AGAIN p56-caldav.icloud.com
0|MagicMir |     at ClientRequest. (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1483:11)
0|MagicMir |     at ClientRequest.emit (node:events:394:28)
0|MagicMir |     at Socket.socketErrorListener (node:_http_client:447:9)
0|MagicMir |     at Socket.emit (node:events:394:28)
0|MagicMir |     at emitErrorNT (node:internal/streams/destroy:157:8)
0|MagicMir |     at emitErrorCloseNT (node:internal/streams/destroy:122:3)
0|MagicMir |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|MagicMir |   type: 'system',
0|MagicMir |   errno: 'EAI_AGAIN',
0|MagicMir |   code: 'EAI_AGAIN'
0|MagicMir | }
0|MagicMir | [11.01.2022 01:22.04.150] [ERROR] Failed to retrieve repo info for MMM-Remote-Control: Error: Command failed: cd /home/pi/MagicMirror/modules/MMM-Remote-Control && git fetch --dry-run
0|MagicMir | fatal: unable to access 'https://github.com/Jopyth/MMM-Remote-Control.git/': Could not resolve host: github.com
0|MagicMir |
0|MagicMir | [11.01.2022 01:22.04.520] [ERROR] Failed to retrieve repo info for MMM-iHaveBeenThere: Error: Command failed: cd /home/pi/MagicMirror/modules/MMM-iHaveBeenThere && git fetch --dry-run
0|MagicMir | fatal: unable to access 'https://github.com/basti0001/MMM-iHaveBeenThere/': Could not resolve host: github.com
0|MagicMir |
0|MagicMir | [11.01.2022 01:22.04.858] [ERROR] Failed to retrieve repo info for MMM-MyGarbage: Error: Command failed: cd /home/pi/MagicMirror/modules/MMM-MyGarbage && git fetch --dry-run
0|MagicMir | fatal: unable to access 'https://github.com/htilburgs/MMM-MyGarbage.git/': Could not resolve host: github.com
0|MagicMir |
0|MagicMir | [11.01.2022 01:22.05.272] [ERROR] Failed to retrieve repo info for default: Error: Command failed: cd /home/pi/MagicMirror/ && git fetch --dry-run
0|MagicMir | fatal: unable to access 'https://github.com/MichMich/MagicMirror.git/': Could not resolve host: github.com
0|MagicMir |
0|MagicMir |
0|MagicMir | <--- Last few GCs --->
0|MagicMir |
0|MagicMir | [1:0x35d60000] 104723155 ms: Mark-sweep 881.0 (983.5) -> 879.5 (983.5) MB, 3579.1 / 0.8 ms  (average mu = 0.425, current mu = 0.580) allocation failure scavenge might not succeed
0|MagicMir | [1:0x35d60000] 104732206 ms: Mark-sweep 880.9 (983.5) -> 879.6 (983.8) MB, 6434.6 / 0.6 ms  (average mu = 0.356, current mu = 0.289) allocation failure scavenge might not succeed
0|MagicMir |
0|MagicMir |
0|MagicMir | <--- JS stacktrace --->
0|MagicMir |
/home/pi/.pm2/logs/MagicMirror-out.log last 100 lines:
0|MagicMir | [11.01.2022 06:44.30.915] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 06:47.22.494] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 06:48.36.582] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 06:49.32.163] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 06:52.23.095] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 06:53.36.863] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 06:54.33.363] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 06:57.23.711] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 06:58.37.291] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 06:59.34.697] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:02.24.291] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:03.37.589] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:04.35.943] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:07.24.879] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:08.38.027] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:09.37.235] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:12.25.382] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:13.38.358] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:14.38.724] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:17.25.998] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:18.38.629] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:19.39.901] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:22.26.507] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:23.38.932] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:24.41.178] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:27.27.140] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:28.39.227] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:29.42.410] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:32.27.736] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:33.39.519] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:34.43.674] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:37.28.306] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:38.39.836] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:39.44.911] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:42.28.829] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:43.40.156] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:44.46.100] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:47.29.321] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:48.40.457] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:49.47.646] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:52.29.861] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:53.40.865] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:54.48.841] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 07:57.30.506] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 07:58.41.544] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 07:59.50.614] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:02.31.075] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:03.41.919] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:04.52.177] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:07.31.622] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:08.42.249] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:09.53.327] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:12.32.206] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:13.42.561] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:14.54.916] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:17.32.659] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:18.42.904] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:19.56.050] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:22.33.218] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:23.43.192] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:24.57.263] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:27.33.923] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:28.43.454] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:29.58.433] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:32.34.557] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:33.43.728] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:34.59.634] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:37.35.081] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:38.44.039] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:40.00.984] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:42.35.668] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:43.44.336] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:45.02.199] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:47.36.191] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:48.44.660] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:50.03.385] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:52.36.810] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:53.45.006] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 08:55.04.602] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 08:57.37.625] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 08:58.45.349] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:00.06.508] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:02.38.095] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:03.45.669] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:05.07.786] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:07.38.724] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:08.46.062] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:10.08.987] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:12.39.337] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:13.46.371] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:15.10.171] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:17.39.963] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:18.46.646] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:20.11.455] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:22.40.690] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:23.47.000] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:25.12.625] [INFO]  Calendar-Fetcher: Broadcasting 5 events.
0|MagicMir | [11.01.2022 09:27.41.232] [INFO]  Calendar-Fetcher: Broadcasting 2 events.
0|MagicMir | [11.01.2022 09:28.47.255] [INFO]  Newsfeed-Fetcher: Broadcasting 39 items.
0|MagicMir | [11.01.2022 09:30.13.906] [INFO]  Calendar-Fetcher: Broadcasting 5 events.

googling EAI_AGAIN:

EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.

So you have problems with your internet connection, nothing we can do here.

googling EAI_AGAIN:

EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.

So you have problems with your internet connection, nothing we can do here.

Ok can we increase the timeout maybe ? i don't know how i can solve this problem better...

Ok can we increase the timeout maybe ? i don't know how i can solve this problem better..

no, its WAY down in the system layer,   way outside MagicMirror..
the whole system (raspberry pi) DEPENDS on reliable network connectivity, and name lookup is how it works.
I have seen this error a lot when the user is running a system,  like pihole, to block advertisements

Hi,
I am having similar / the same issue.
Error is -
[10.03.2022 03:18.39.287] [INFO]  Calendar-Fetcher: Broadcasting 10 events.
[10.03.2022 03:20.50.355] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/XXXXXXXXXXXgmail.com/private-a5258b008b4d947ac79c51cc483979d6/basic.ics FetchError: request to https://calendar.google.com/calendar/ical/XXXXXXXXXXXXXgmail.com/private-a5258b008b4d947ac79c51cc483979d6/basic.ics failed, reason: getaddrinfo EAI_AGAIN calendar.google.com
at ClientRequest. (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:315:20)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
type: 'system',
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN'
}
[10.03.2022 03:20.50.403] [ERROR] (node:28950) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'status' of undefined
at /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:70:18
at processTicksAndRejections (internal/process/task_queues.js:97:5)
[10.03.2022 03:20.50.405] [ERROR] (node:28950) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[10.03.2022 03:20.50.408] [ERROR] (node:28950) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The pi connects wirelessly to my router.
Is there any merit in changed the DNS lookup information within the router to google's DNS servers?
It occasionally seems to ;-
a. Stop my wallpaper module from changing the background photos and/or
b. Going to a black screen.
A Ctrl_R forces a MM reread and restarts everything but it doesn't address the issue.
Any help / advise would be appreciated

EAI_AGAIN is a networking error, nothing we can do.
I have seen this many times when users are using an advertisement filter like pihole.
others have rebooted their routers.
nothing consistent.
mm assumes a working network.  the error is reported way below any code mm provides

@sdetweil
Thanks

I have seen this many times when users are using an advertisement filter like pihole.

@sdetweil I always wondered what was causing my black screen! I have to keep a keyboard attached to the pi and hit CTRL+W about once every few days. Is there a domain or URL I can add to my pihole's allow list?

@dieseltravis   no idea, you would have to look at the logs to see whats going on

no update since May, can this be closed @Fredi009sg @MichMich ?

yes