Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systeminfo starts with Error "err from getObjectList: TypeError: ..." #214

Open
Sayonara-Rolo opened this issue Feb 17, 2024 · 11 comments · May be fixed by #293
Open

Systeminfo starts with Error "err from getObjectList: TypeError: ..." #214

Sayonara-Rolo opened this issue Feb 17, 2024 · 11 comments · May be fixed by #293
Labels

Comments

@Sayonara-Rolo
Copy link

Hi ioBroker Community,

When I start "systeminfo" I get the following Error
"err from getObjectList: TypeError: Cannot read private member from an object whose class did not declare it"
and the Warning
"Unhandled error in main: TypeError: Cannot read private member from an object whose class did not declare it"
See attached Picture "systeminfo_Protocol240217.jpg"
systeminfo_Protocol240217

An instance of systeminfo is created, which appears to be running (green)
See attached Picture "systeminfo_Instance240217.jpg"
systeminfo_Instance240217

Apart from the Admin Object, no other Objects are created.
See attached Picture "systeminfo_no-Object240217.jpg"
systeminfo_no-Object240217

Systeminfo is up to Date with the Version 1.1.0.

What could be the Reason for this?

Thank,
Sayonara-Rolo

@xbmc-freak
Copy link

I have the same problem!
Can any one Help us?

@mcm1957 mcm1957 added the bug label Mar 11, 2024
@micki88
Copy link

micki88 commented Mar 13, 2024

After I updated to js-controller 5.0.12, this same error apeared...

@lammy000
Copy link

me 2

`

systeminfo.0 | 2024-03-25 09:49:02.916 | error | err from getObjectList: TypeError: Cannot read private member from an object whose class did not declare it -- | -- | -- | -- `

@pierangelof
Copy link

Hi,
I have the same problem. Have you found in the meanwhile a solution?

@Sayonara-Rolo
Copy link
Author

Hi,
the problem still exists.
It seems that a number of users have the same incorrect behavior.
It's a shame that the developer didn't get in touch.
It seems to me that this adapter is no longer being maintained :(

@mcm1957
Copy link
Member

mcm1957 commented May 13, 2024

Hi, the problem still exists. It seems that a number of users have the same incorrect behavior. It's a shame that the developer didn't get in touch. It seems to me that this adapter is no longer being maintained :(

I would suggest that you calm down a little bit.

If you can analyze / fix the code you are very welcome to provide a PR. And you are right, there's no active maintainer for this adapter currently.

If you did not recognize - work at ioBroker is done be volunteers at their free time and without any paiment. Its easy to consume and to request only. Please help by supporteing ioBroker with your know how / coding or whtever you can provide. Or develop your own system. No developer spending its time need to be attacked by "its a shame ...". Such statements will likely reduce the number of active Developers only.

Have a nice day
mcm1957

@Apollon77
Copy link
Member

At Whever find time to look into it ... or maybe @Sayonara-Rolo wanne try it out and report back?

i think the issues is in https://github.com/iobroker-community-adapters/ioBroker.systeminfo/blob/master/myAdapter.js#L63-L68 ... all here ".bind(adapter)" is missing for all these function calls because they get patched . This woukd no longer since ages and there could be other "ex Frank Joke Adapters" where this is already fixed. I think these places could be changed like
https://github.com/iobroker-community-adapters/ioBroker.radar2/blob/master/fjadapter-core.js#L325-L332 ... ideally this could already do the trick ... if there is more we see afterwards ;-)

@Sayonara-Rolo
Copy link
Author

Hi, the problem still exists. It seems that a number of users have the same incorrect behavior. It's a shame that the developer didn't get in touch. It seems to me that this adapter is no longer being maintained :(

I would suggest that you calm down a little bit.

If you can analyze / fix the code you are very welcome to provide a PR. And you are right, there's no active maintainer for this adapter currently.

If you did not recognize - work at ioBroker is done be volunteers at their free time and without any paiment. Its easy to consume and to request only. Please help by supporteing ioBroker with your know how / coding or whtever you can provide. Or develop your own system. No developer spending its time need to be attacked by "its a shame ...". Such statements will likely reduce the number of active Developers only.

Have a nice day mcm1957

I don't want to or didn't mean to attack anyone here. I apologize for that.
I would also like to expressly praise and appreciate the voluntary work of the developers.
And I admire the work that some developers put into the adapters.

On the other hand, I don't think it's good for users if they no longer receive feedback from a developer.
In my opinion, this reduces confidence in the adapters.
In this case, you could leave a note saying that the adapter is no longer being maintained.

Once again, many thanks for the commitment and dedication of the developers.

Unfortunately, I don't have the know-how to program or debug the adapter myself.
Thanks, Roland

@mcm1957
Copy link
Member

mcm1957 commented May 14, 2024

Thanks for the feedback adn explaining things.

Yes I can understand that you are frustracted. But this (nad many other) adapter lacks an active maintainer. So you nobody responded either. I cannot promise to look at it at a short time - my list is sinply tooo long. But I am aware that this adapter needs a maintainance.

@lfischer85
Copy link

lfischer85 commented Jan 12, 2025

At Whever find time to look into it ... or maybe @Sayonara-Rolo wanne try it out and report back?

i think the issues is in https://github.com/iobroker-community-adapters/ioBroker.systeminfo/blob/master/myAdapter.js#L63-L68 ... all here ".bind(adapter)" is missing for all these function calls because they get patched . This woukd no longer since ages and there could be other "ex Frank Joke Adapters" where this is already fixed. I think these places could be changed like https://github.com/iobroker-community-adapters/ioBroker.radar2/blob/master/fjadapter-core.js#L325-L332 ... ideally this could already do the trick ... if there is more we see afterwards ;-)

You are right, I have replaced these lines as you suggested, and my Systeminfo Adapter is working again.
Unfortunately I don't know how to properly create a pull request, but I wanted to let you and others know, that this seems to do the trick.
Thank you for pointing this out.

Edit: Ah I was a bit fast. The getObjectList Error disappeared, but the adapter still has another issue.
Debug Logs say:

MS TypeError: this._extendObject is not a function at MyAdapter.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1796:17) at /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:434:96 at new Promise (<anonymous>) at MyAdapter.extendObject (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:433:20) at MyAdapter.makeState (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:670:21) at setItem (/opt/iobroker/node_modules/iobroker.systeminfo/systeminfo.js:467:14) at /opt/iobroker/node_modules/iobroker.systeminfo/systeminfo.js:544:48 at /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:409:48 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants