Re: Javascript weirdness
By: Digital Man to deon on Tue Apr 19 2022 04:35 pm

Re: Javascript weirdness
By: deon to Digital Man on Wed Apr 20 2022 08:09 am

Re: Javascript weirdness
By: Digital Man to deon on Mon Apr 18 2022 09:37 pm

Thanks - I emailed it to you - please let me know if you didnt get it.

Has not arrived yet. <shrug>

Not get it yet? I sent it to rob at synchro dot net.

Got it. I'll take a look-see.

There is definitely something weird going, but you don't need to call write(). Calling any method (e.g. even yield()) seems to give a correct answer.

I'll continue to debug further, but my first suspect is that get_all_msg_headers() method. Thanks for the report,
--
digital man (rob)

Synchronet/BBS Terminology Definition #45:
IP = Internet Protocol
Norco, CA WX: 57.3øF, 80.0% humidity, 3 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Javascript weirdness
By: Digital Man to deon on Thu Apr 21 2022 06:17 pm

Originally I was iterating through through that result to update the messages, but I was noticing the following behaviour:

* call get_all_msg_headers()
* iterate through each item "for (hdr in hdrs)"
* set hdr.tag to "foo"
* pass hdr to put_msg_header();

But the items were not updating.

Does put_msg_header() return false when you try to use it in that manner?

So I cant reproduce this now. I'll revert my code to use get_all_msg_headers and if I can reproduce it, I'll provide a log and the status returned.


...ëîåï

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Javascript weirdness
By: deon to Digital Man on Fri Apr 22 2022 10:00 pm

Originally I was iterating through through that result to update the messages, but I was noticing the following behaviour:

* call get_all_msg_headers()
* iterate through each item "for (hdr in hdrs)"
* set hdr.tag to "foo"
* pass hdr to put_msg_header();

But the items were not updating.

Does put_msg_header() return false when you try to use it in that manner?

So I cant reproduce this now. I'll revert my code to use get_all_msg_headers and if I can reproduce it, I'll provide a log and the
status returned.

OK, I got it. It seems to depend on whether I work with the object vs the attribute of it.

First run, where I echo the object "after" put_msg_header:

for (var X in msgs)

X:35
ORIG:0353 <-- msgs[x]
CHANGE:0425 <-- msgs[x].tags = '0425'
<put_msg_header>
<JSON.stringify(msgs[x])> object:{"tags":"0425","number":38,"to":"deon","subject":"Test Reply","from":"Clearing ...
STATUS:0 <!-- return from put_msg_header
AFTER:0425 <-- msgs[x]

vs echo the object "before" put_msg_header:

X:35
ORIG:0353 <!-- msgs[x]
CHANGE:0389 <!-- msgs[x] = '0389'
<JSON.stringify(msgs[x])> (Note it has reverted) object:{"tags":"0353","number":38,"offset":0,"to":"deon","from":"Clearing Houz","subject":"Test ...
<put_msg_header>
STATUS:0 <!-- result
AFTER:0353 <!-- no change

So it seems JSON.stringifying the object reverts its value, that doesnt seem right, but as long as I dont do that I guess I'm OK.


...ëîåï

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)