You are not logged in.
For SpaceNut re Post Repair initiative ...
Trailbreaker reached 68700 today. It finished with a Green screen.
Completed Sequence for ID: 68700
Total Command Lines found: 53
Total input Lines in script: 159Number of ID's processed: 300
Starting Number: 68401
Last Number of Run: 68700
Summary for Web Automation Report for 07-17-2022 at 12:08:45
Average time of Loop from Main form: 00:00:44
26 Skip Exceptions were recorded.Total time of Processing: 03:40:43
Potholes: Zero
Skip analysis for 26 skips:
Lines containing String One 75 <<== SpaceNut / 3 >> 25 posts
Lines containing String Two 300 <<== 300 posts in run
Lines containing String Three <<== no potholes
Lines containing String Four 26 <<-- one post to edit >> 68691
OK ... that was interesting ... 68691 turned out to be a SpaceNot post that was not handled correctly.
The program attempted a download of that post, but was turned away. The usual message did not appear.
Thus, we have another day with no posts to edit.
The Inspector will now confirm this report.
Completed Sequence for ID: 68700
Total Command Lines found: 31
Total input Lines in script: 160Number of ID's processed: 300
Starting Number: 68401
Last Number of Run: 68700
Summary for Web Automation Report for 07-17-2022 at 15:59:33
Average time of Loop from Main form: 00:00:22Total time of Processing: 01:49:04
Potholes: Zero
Edits: Zero
Good run!
(th)
Offline
For SpaceNut re Post Repair initiative...
Trailbreaker reached 69000 ...just 8000 posts to go >> 27 days should reach the goal of 78,000
There were two potholes.
***
Work is started on the Outreach campaign ... a manual procedure was sketched out for the process.
The script has some similarity to the one used last year to recover ID's from the spammers.
***
Completed Sequence for ID: 69000
Total Command Lines found: 53
Total input Lines in script: 159Number of ID's processed: 300
Starting Number: 68701
Last Number of Run: 69000
Summary for Web Automation Report for 07-18-2022 at 13:01:38
Average time of Loop from Main form: 00:00:44
29 Skip Exceptions were recorded.Total time of Processing: 03:39:25
Potholes: 2 68883 68882
Skip analysis for 27 skips:
Lines containing String One 69 SpaceNut / 3 >> 23
Lines containing String Two 300 << posts
Lines containing String Three 2 << potholes so 23 + 2 >> 25
Lines containing String Four 32 << more skip lines than expectedPer the run report, 29 skips less 25 >> 4 posts to visit
4 posts to edit were found
Our "unquote" guy is back ...
newmars.com/forums/edit.php?id=68798 unquote
newmars.com/forums/edit.php?id=68808 Manual edit
newmars.com/forums/edit.php?id=68853 Manual edit
newmars.com/forums/edit.php?id=68901 unquote
Because we just reached an even thousand, i'll run ReScan instead of Inspector.
*** An update of WBA is pending ...
The Outreach Campaign is an opportunity to improve performance of WBA ... In particular, I've decided to add a capability of verifying that the program is running in the correct account (or logged in at all). The Outreach Campaign is intended to run in the NewMarsMember account, so that the email address given to the recipient is the NewMarsMember email address. It turns out WBA did not have a command able to halt if the run was not in the right account.
While I'm adding that command, I'll add another to skip to the next item if something that should be present is missing, but the issue only affects one ID so a halt is not necessary.
There are already a significant number of check commands in place, but the new commands will be more flexible.
Update at 22:15 .... The ReScan completed with no edits needed.
(th)
Offline
For SpaceNut re Post Repair initiative...
Today's Trailbreaker will try for 69300
Trailbreaker reached 69300 with a Green screen.
Two potholes showed up: 69233 69131
There were 49 skips ... hopefully 47 of those were SpaceNut posts, but our unquote guy appears to be back.
All questions have been addressed ... there was a range of issues. Mr. Unquote was not present.
Inspector will now check the work.
Update at 17:26 local time
Completed Sequence for ID: 69300
Total Command Lines found: 31
Total input Lines in script: 160Number of ID's processed: 300
Starting Number: 69001
Last Number of Run: 69300
Summary for Web Automation Report for 07-19-2022 at 17:24:00
Average time of Loop from Main form: 00:00:22
2 Skip Exceptions were recorded.Total time of Processing: 01:49:15
Potholes: (2) 69233 69131
Edits: Zero
Good run
Tomorrow's Trailbreaker will try for 69600
(th)
Offline
For SpaceNut re Post Repair Initiative ...
Trailbreaker will try for 69600 today
Two new commands for WBA are in development ...They are mirror images of existing commands
The two existing commands look for text in the clipboard and proceed if the text is found
The new commands will look for text in the clipboard and will halt (or skip) if the text is missing
The primary objective of this enhancement is to provide a way to confirm the program is logged in.
The secondary objective is to confirm the program is logged into the correct account.
This has become an issue as we approach launch of the email outreach campaign.
Update at 14:40 Trailbreaker finished with a Green screen no potholes.
However, our authors went to town with creative coding that fluxBB didn't like ...
The total of posts to visit is 33 ... I'm taking a break after finishing 6 ... this is almost like work!
I was ** really ** enjoying the runs with zero edits needed. At least Mr. Unquote is not on the scene (yet)
Update at 17:16 Just completed post #17 of 33 to visit ... working short stretches in between chores.
update the next day ... all 33 posts are now visited ... Mr. Unquote was back. We also had a mixup of bold and italics ... the author (obviously) changed their mind in the middle of composing the text.
That error was then copied in quotes by several others.
A new problem has shown up, and it is worrying. A couple of the posts were short text compared to the original. In other words, the download failed, or did not complete before the text was accepted as complete.
I'll schedule some time to look at the script to see if there is anything to be done. The problem is that if the original text is not downloaded completely, WBA doesn't know any better, so it just edits what it has and posts that.
(th)
Offline
For SpaceNut re latest GW Johnson Conference files...
If you have time (knowing time is hard to come by), please check the latest file links for the GW Johnson conference series.
This set of files (as I understand the plan) is intended to show a landing vessel concept designed to work with the Large Ship as proposed by RobertDyck, in conjunction with the Space Tugs concept proposed by GW Johnson.
(th)
Offline
For SpaceNut re Post Repair initiative...
Because manual editing of 33 posts spilled over into the next day, I'll set up Inspector to cover both days.
Today's Trailbreaker will try for 69900. I hope it has better luck!
Update regarding script operation ... the script has a WaitForEvent after asking for the post.
This means that as far as FluxBB is concerned, it ** thinks ** it delivered the post to the browser.
I'll have to do some research to see if there is a command that might be issued to get the length of the post in the MySql database, before the download is requested.
Update at 16:54 .... Trailbreaker reachedk 69900 with a Green screen...
Completed Sequence for ID: 69900
Total Command Lines found: 53
Total input Lines in script: 159Number of ID's processed: 300
Starting Number: 69601
Last Number of Run: 69900
Summary for Web Automation Report for 07-21-2022 at 16:54:31
Average time of Loop from Main form: 00:00:48
37 Skip Exceptions were recorded.Total time of Processing: 03:59:57
Potholes: Zero
Skip analysis for 37 skips:
Lines containing String One 66 SpaceNut posts / 3 >> 22
Lines containing String Two 300 Posts
Lines containing String Three 0 potholes
Lines containing String Four 42 37 skips less 22 SpaceNut >> 15 edits
15 edits is better than 33, but still ... a ** lot ** compared to none at all.
Our Unquote guy must be back, along with the the funny bold author.
Update at 20:22 local time ... the unquote guy did not show up
Inspector will now check posts for yesterday and today.
Update next day:
Inspector finished a review of 600 posts with a Green screen, no potholes and NO edits! Good run.
Today's Trailbreaker will cross 70000 if all goes well, to 70200.
(th)
Offline
For SpaceNut and kbd512 ...
Just FYI ... I dropped off a request for assistance at FluxBB.org today ...
FluxBB Home
You are logged in as tahanson43206 : profile | logout
HomeAboutDownloadsResourcesForumsCommunityDocumentationDevelopment
Forums
Logged in as tahanson43206 Last visit: 2021-09-22 09:06:25Topics: Posted | New | Active | Unanswered
Index» General discussion» 20220721 Help finding length of post before download
Pages:1Post reply
#1Today 11:50:18
tahanson43206
Member
Registered: 2020-01-07
Posts: 25First, thanks again for assistance provided in the past!
We are continuing to work on cleanup of the FluxBB/MySql database.
Spammer created ID's have been salvaged and converted for use by members.
We've progressed to removing artifacts left over from a previous forum package. We've completed nearly 70K posts of 78K known to contain artifacts.
The process is automated, with manual oversight, when FluxBB objects to bbcode our authors back in 2002 tossed into the post. Apparently the earlier forum let them pass, but FluxBB is not as forgiving.
The purpose of ** this ** post is to ask if there is a query a Mod can run that shows the length of a post. The automated process is packed with fail safe features, but there is a weak point.
If FluxBB is asked to deliver a post, it makes a good faith effort, but every now and then the post that shows up in the edit window is not complete. Is there a query a Mod can run to reveal how long that post was before the download request was issued?
We have the post ID to work with, and are using the query to fetch each post by ID.
Is there (?possibly?) a way to modify that query to show just the length?
Thanks!
To see the history of our little project, you're welcome to visit newmars.com/forums, and look at the Housekeeping topic.
(th)
Last edited by tahanson43206 (Today 11:51:30)
Copyright © FluxBB 2008 - 2022
Hosting provided by gandi.net. Thanks!
(th)
Offline
As requested, I did attempt to view each files interaction and content however, I only could get the abstract to open. After check there was a note as to its cause
Scheduled - Dropbox will be performing routine maintenance on July 21st, 2022 starting at 5PM(PST).
I will try again in a few days....
Offline
For SpaceNut ... thanks for feedback on Dropbox maintenance.
Maintenance has to be done ** some ** time... Dropbox is a 24 hour global operation, so there is no "right" time.
On the ** other ** hand, most major Internet services try to avoid impacting customers if they can avoid it.
The ** free ** service we enjoy means we can't complain if our service is cut off arbitrarily whenever Dropbox feels like doing maintenance.
(th)
Offline
For SpaceNut re Post Repair initiative ...
Trailbreaker will try for 70200 today ...
If the run is successful, ReScan will be scheduled to cover 69001-70200.
Trailbreaker reached 70200 with a Green screen and no potholes.
43 Skips occurred.
For SpaceNut ... Trailbreaker appears to have caught up with you:
http://newmars.com/forums/viewtopic.php … 928#p69928
I am right in the middle of dealing with 20 posts that needed attention today.
We had some Internet congestion today... as a result, the Fail Save features in the script were overly sensitive ... they asked me to check posts they had processed and uploaded correctly.
About half of today's batch needed no additional work.
Here's another unfinished SpaceNut post ...
http://newmars.com/forums/viewtopic.php … 018#p70018
Update at 14:54 local time .... visits to 20 posts are complete... Mr. Unquote was back in fine form.
At least two SpaceNut posts need attention.
I'm planning to install an updated version of WBA before Inspector is run today.
The new feature that is of greatest potential value is a "Halt if Missing" command, which will stop a run if the program is not logged in properly. I've had numerous runs that were a waste of time because I had forgotten to log in. The script didn't care if nothing was coming down from the server. It just reported an error and went on to the next post. This is annoying when the run is for 1000 posts, as will be the case today.
We have crossed the 70000 marker, so today's Inspector will cover 60001-70200.
(th)
Offline
For SpaceNut re Post Repair initiative
Trailbreaker will try for 70500 today. Inspector will need to be rerun.
The update of two new commands had an unexpected and unwanted side effect, so that the ReScan from 69001 was not successful.
The previous version of WBA is restored, and Trailbreaker is working normally.
Discovery of the problem with handling of exceptions is today's priority.
***
On the Interstate 80 front ... I discovered the cause of my error in thinking 300 miles is the distance from the Pacific to Great Salt Lake. The simultaneous work on the Phoenix run overlaid the 700 miles, which I had been correctly posting in the beginning of the Interstate 80 topic.
Unfortunately, my message to the folks at Delta, Utah, contains the 300 error. The ** right ** thing to do would be to send a correction.
Update at 12;22
Completed Sequence for ID: 70500
Total Command Lines found: 53
Total input Lines in script: 159Number of ID's processed: 300
Starting Number: 70201
Last Number of Run: 70500
Summary for Web Automation Report for 07-23-2022 at 12:13:45
Average time of Loop from Main form: 00:00:49
43 Skip Exceptions were recorded.Total time of Processing: 04:07:46
Potholes: Zero
Skip analysis for 43 Skips:Total Input Lines 14,462
Total Output Lines 184
Lines containing String One 123 SpaceNut / 3 >> 41 posts of 43 total
Lines containing String Two 300 posts
Lines containing String Three zero potholes
Lines containing String Four 43 43 skip lines predicted and foundThis is more like it! Only two posts to check.
In the end, only one post needed adjustment ... Mr. Unquote was back ...
Inspector will now check the work. WBA has been updated so that the new feature ** should ** work this time.
The problem turned out to be placement. The new feature needed to be installed ** before ** the old code, and not after as I had done.
Because yesterday's ReScan did not run correctly, I'll set up a run from 69001-70500.
Update next day...
Inspector covered the full range, from 69001 - 70500 over night.
It finished with a Green Screen, which is encouraging.
It found two potholes as expected.
More importantly, it found two posts that need edits: 69901 and 70199
Update to follow >>>
Potholes: 2 expected 2 found >> 69233 69131
Edits: NOT Zero! 7 bandits were found
Post: newmars.com/forums/edit.php?id=69901 <done>
Post: newmars.com/forums/edit.php?id=70199 <done>
The ReScan was worth doing, even though it took 12 hours. The Internet was glassy smooth last night!
(th)
Offline
For SpaceNut re Post Repair initiative ...
We are in the last leg of this marathon .... Just 25 days
Trailbreaker will tackle the stretch from 70501 to 70800 today.
Completed Sequence for ID: 70800
Total Command Lines found: 53
Total input Lines in script: 159Number of ID's processed: 300
Starting Number: 70501
Last Number of Run: 70800
Summary for Web Automation Report for 07-24-2022 at 12:33:16
Average time of Loop from Main form: 00:00:40
13 Skip Exceptions were recorded.Total time of Processing: 03:21:52
Potholes: Zero
Lines containing String One 30 SpaceNut >> 10
Lines containing String Two 300 Posts
Lines containing String Three Potholes
Lines containing String Four 13 Skips = skips so 3 edits
Inspector completed part of today's run to 70800
A halt occurred at the start of 70551, during the newly added check for logged in state...
In the part completed, there were no potholes or edits.
What this incident tells me is that a small wave of Internet turbulence hit the laptop.
In the past, the laptop would have struggled on, but since it would have been in an inclear state, it would probably have generated a skip that would have had to have been checked later.
I'll restart Inspector to cover the last 50 posts.
Update at 21;07 local time ... The Inspector finished the cleanup run with a Green screen.
Completed Sequence for ID: 70800
Total Command Lines found: 38
Total input Lines in script: 177Number of ID's processed: 50
Starting Number: 70751
Last Number of Run: 70800
Summary for Web Automation Report for 07-24-2022 at 21:08:29
Average time of Loop from Main form: 00:00:25Total time of Processing: 01:19:33
Total time Program was Active: 01:19:33
Potholes: zero
Edits: zero
Good run
(th)
Offline
Evolve III Maestro E-Book MEB11WIFI 11.6 Laptop
This is for SpaceNut ...all others welcome
The ebook/laptop above is on sale for $60 at the local MicroCenter.
I expect you can order it online if you are interested.
I am typing this post on the device.
The device has an hdmi output port so I'm hoping it can drive a monitor. I'll find out tomorrow.
This appears to be designed to compete with Chromebook for the education market.
(th)
Offline
Computers are becoming more virtual in nature and less about the hardware that they have these days.
I did a bit more clearing of my posts leaving off at 71451, I think.
Offline
For SpaceNut 2364 ...
This machine is NOT running a virtual operating system. This is bare bones hardware and a cut down Windows 10.
What's interesting (to me at least) is that Microsoft is offering the full suite of the Office package using the cloud to serve the customer. The cut down Windows 10 is acting as a conduit for the cloud software. This is very similar to the cloud software offerings of Google Chromebook. The microsoft product is priced competitively with Chromebook.
This seems to me to be a healthy competition.
One thing I learned in experimenting with an earlier concept (the Winbook) is that the device is unable to support a modern heavy duty operating system (such as Linux Ubuntu) so I won't even try.
The main thing that ** I hope ** Microsoft should have learned is NOT to try to update this little machine. It is using about half of the 60 Gb SSD for the operating system, and I've learned that additional software consumes the remaining 30 Gb quite rapidly, so I won't try ** that ** either. The device ** does ** accept an SD card, so I'll be adding one today for data.
Thanks for staying ahead of Trailbreaker, as best you can.
Trailbreaker is hot on your heels !!! It will try for 71100 today.
I've activated the new "verify login" feature to Trailbreaker, so I'm expecting a Red screen if any Internet waves of any size come along to swamp the laptop.
Update at 13:13 .... Trailbreaker was ** so ** close to the end of today's run, but it got hit by an Internet wave of sufficient size to snuff the spring driven paddle wheel.
There was on pothole, and there were three posts needing edits ... One gent got confused about underscores.
I'll set up a short run to pick up the last of today's batch.
Update at 13:39 ... two more SpaceNut posts were found, zero potholes and zero edits.
The Inspector will now check the entire set of 300 posts.
Update at 17:38 ... Inspector reached 71087, before an Internet wave came along and swamped the laptop, once again.
There were no potholes, and there were no posts that need attention.
I'll start a run over the last 13 posts now.
(th)
Offline
For SpaceNut re Email Outreach campaign planning....
Here is a manual transcription of what would be the basis for a script for email outreach:
1) Login
2) Start Script
3) Set focus on browser1) Show rules: http://newmars.com/forums/misc.php?action=rules
2) Verify rules in address bar
3) Verify login to correct username: Logged in as newmarsmember
4) Go to address bar
5) Request userlist: http://newmars.com/forums/userlist.php
6) Verify userlist in addressbar
7) Tab 15 to username field
8) Pull username from data file
9) Paste username into Username window
10) Tab 4 to Submit
11) Enter
12) Go to address bar
13) Verify part of display: http://newmars.com/forums/userlist.php? … anson43206
14) Tab 20 to Username field in userlist
15) Enter
16) Go to address bar
17) Verify part of display: http://newmars.com/forums/profile.php?id=
18) Tab 25 to get to Send email button
19) Enter
20) Go to address bar
21) Verify part of address bar: http://newmars.com/forums/misc.php?email=
22) Tab 1
23) Text >> date (today)
24) Text: Invitation to Contact NewMars Forum
25) Tab 1
26) Text ... upload body of message
27) Tab 1
28) Enter
29) Go to address bar
30) Verify part of address bar: http://newmars.com/forums/profile.php?id=
31) End of loop
It is more efficient and more accurate to use mouse positioning, but that takes additional planning that is outside the scope of this stage of preparation.
The multitudinous tabs system works. Once that crude procedure is working, the more efficient mouse click procedure can replace it.
Note that in step 13, the full username is to be verified. This is a failsafe procedure to insure the email is going to the intended member.
Also note that in each line where the word "verify" appears, a failure to verify will cause the loop to skip. The skip will be reported for investigation.
The one exception is that a failure to verify logged-in status will cause a halt.
(th)
Offline
For SpaceNut re Post Repair initiative ...
Today's Trailbreaker will try for 71400.
I am thinking about (and working on) an improved Smart Wait command.
The present one only works with the address bar.
The halts that have occurred recently have occurred when the system (FluxBB or the Internet) took too long to bring text down from the server for display on the edit screen.
A second generation Smart Wait would look for the needed text in the main form, instead of just the address bar.
Update at 14:40 .... The need for a new Smart Wait command made itself known again today ...
Starting Sequence for ID: 71331
Query Text Requested Was NOT Found: Logged in as tahanson43206
Step 15 Search Clipboard Zero Halt if MissingTotal Command Lines found: 60
Total input Lines in script: 176Number of ID's processed: 230
Starting Number: 71101
Last Number of Run: 71400
Summary for Web Automation Report for 07-26-2022 at 14:36:57
Average time of Loop from Main form: 00:00:45
16 Skip Exceptions were recorded.Total time of Processing: 01:27:04
Total time Program was Active: 01:27:04
Early end of run requested.
Once again, the address bar passed muster, but the program ran out of time when the FluxBB server and the Internet dawdled in delivery of the needed data to confirm logged in status.
I have a work session to create the new Smart Wait on Page command scheduled.
In addition, GW Johnson has completed a 10th set of presentation files I want to post on NewMars later today.
Mars_B4_Moon has been collecting links (with useful comments) and ** those ** are ** out there ** to be read.
Keeping up with NewMars is (occasionally) almost like work !!!
***
A few days ago, I reported investing in a greatly reduced eBook/laptop from Microsoft.
I found out why the product is reduced from $250 5 years ago, to $60 now ... the hardware remains as good as new, but the software is five years old. I returned one of the units to the store because it refused to connect to the Internet after Microsoft attempted updates. The new (replacement) unit is behaving exactly the same way, but ** this ** time I paid more attention to it's struggles, and finally took the hint from a help desk person to take charge of the updates.
I went to System >> Updates and asked for a list of all the updates it wanted to apply after 5 years.
Then, I let the process run over many hours, and it ** looks ** as though we (the device and I) may be within shouting distance of a fully up to date Windows 10.
If this long, drawn out process works, I'm thinking of going over to pick up a couple more of these devices while the store is closing them out.
I do feel badly for the many families that may be investing in these for their kids. I am an experienced IT professional with decades of experience dealing with Microsoft products. This would surely be incredibly frustrating for a youngster gifted this device.
However, all that said, for ** your ** situation, with a tight budget and needs for an up to date PC to perform your
Admin duties, I am (tentatively) willing to endorse this device, assuming you have the patience of Job and are willing to put up with the many hours needed to deliver a useful machine.
After all that work, this is a lawn mower engine in a Mack Truck environment, so no one should expect Mack Truck performance. But for ** my ** purposes, it appears capable of performing Internet lookups when my Year-2000-era main system is denied access.
Afterthought but it may be useful to someone ...
There is a way to prevent Microsoft from attempting updates.
There is a service (services.msc) that can be reset from Enabled to Disabled. (this from Internet lookups)
I'm thinking seriously of taking that step if (?when) the eVolve Maestro finished updates.
Update at 15:07 ... 71261 << manual edit ... There was just one post that needed attention in this batch
I'll set up Trailbreaker to finish today's set. Then I'll go back to the development machine to work on that improved Smart Wait command.
Update at 16:08 local time .... Trailbreaker finished with no potholes and five SpaceNut posts and no edits.
Inspector will double check the single update that was made.
Update at 20:23 local time ....
the Internet was glass smooth this evening, and the posts were well behaved!
Completed Sequence for ID: 71400
Total Command Lines found: 38
Total input Lines in script: 177Number of ID's processed: 300
Starting Number: 71101
Last Number of Run: 71400
Summary for Web Automation Report for 07-26-2022 at 20:20:16
Average time of Loop from Main form: 00:00:25Total time of Processing: 02:03:13
Potholes: Zero
Edits: Zero
Good run
Tomorrow's Trailbreaker will tryu for 71700
(th)
Offline
Special request for SpaceNut ....
If you have time (knowing time is in short supply) ... please check the links for the 10th presentation by GW Johnson, just added to the collection in GW Johnson Postings.
Dr. Johnson tells me this is it! He's going on to other activities.
Thanks again for the earlier checks you have done, including finding Dropbox in the middle of scheduled maintenance.
I hope they are done for now, and that the links work correctly.
(th)
Offline
Finally finished checking the last posts links and all are functional and to the correct documents.
I need to find time for the mars landing mission numbers and such in that post, but they are all of high quality as we have come to expect from GW.
Offline
For SpaceNut re #2369
Thank you for checking those links! I was hoping I'd set them up correctly, but it is good to know!
Dr. Johnson had prepared a list of those links for the Conference Committee, so your work in checking them is much appreciated.
***
I got in a few minutes to chip away at installing the new Smart Wait to (try to) improve performance. The Red Screens are a signal that the Internet (and perhaps FluxBB) need more time to display the text to be checked then I was providing.
The Smart Wait feature allows up to a minute by default, and that should be plenty of time.
***
I wrote up a report on my experience with the Evolve Maestro computer and took it in to Microcenter.... the sales rep on duty by the computers called a supervisor over, and he accepted my write-up, so I hope something happens.
Because the systems were manufactured in 2018 or thereabouts, the number of updates needed is overwhelming. I've been encouraging the machine to take the updates, and it made some progress, but is still not finished. I decided to give it a break over night.
(th)
Offline
https://www.microcenter.com/product/646 … -dark-grey
https://www.evolveiii.com/products/education/
It appears to target student in class use with wifi connectivity.
Offline
For SpaceNut re Evolve Maestro #2371
After many hours of update attempts and failures, the Maestro installed all updates except the last one "21H2"
I asked it to retry, and after that failed, I turned off Windows 10 updates permanently.
If anyone else wants to take that risk, the procedures is:
run services.msc
Look for Windows Updates service
Right click and select properties
Change from enabled to disabled
The change will take effect at the next boot.
I'm ** hoping ** the machine is now stable, and that I can count upon it for a good 10 years of service as a simple web lookup tool.
***
In the mean time, Trailbreaker reached 71700 with a Green screen.
That is a surprise, because Internet waves have swamped the laptop since the latest fail safe check was added.
A new version is ready to go into service. It is designed to wait for text to be delivered to the page below the address bar. The script was satisfied that the right value was in the address bar, but apparently too much delay was taking place between display of the address bar, and display of the page below it.
Completed Sequence for ID: 71700
Total Command Lines found: 60
Total input Lines in script: 176Number of ID's processed: 300
Starting Number: 71401
Last Number of Run: 71700
Summary for Web Automation Report for 07-27-2022 at 15:34:53
Average time of Loop from Main form: 00:00:47
27 Skip Exceptions were recorded.Total time of Processing: 01:58:13
Total time Program was Active: 01:58:13
Potholes: Zero
Skip analysis for 27 skips:
24 SpaceNut 3 posts to visit
The 3 included 2 with italics issues, and one that came down garbled so required manual attention.
Inspector will now check the work.
Completed Sequence for ID: 71700
Total Command Lines found: 38
Total input Lines in script: 177Number of ID's processed: 300
Starting Number: 71401
Last Number of Run: 71700
Summary for Web Automation Report for 07-27-2022 at 18:21:23
Average time of Loop from Main form: 00:00:25Total time of Processing: 00:04:04
Zero potholes. Zero edits. Good run!
(th)
Offline
cleared out to post 72854
Offline
For SpaceNut re #2373
Congratulations on your progress!
Just FYI ... the schedule I set up for this activity has a built-in break for the next two days. I'm planning to spend those two days working on the email project.
Also just FYI ... our Phoenix contact appears to be leaning toward thinking about the water problem on the community scale.
We started out thinking of a possible regional approach, but the sheer magnitude of the social cooperation that would be required appears out of the question for Arizona, or anywhere else in the United States these days.
However, he informed me that there is a community in Arizona that already imports ** all ** it's water by truck.
Such a community ** might ** be a candidate for conversion to sea water input, because where ever they are getting there water now is going to dry up.
If they can make the mental leap to sea water, then they have an unlimited supply.
(th)
Offline
For SpaceNut re Post Repair initiative and Email Outreach initiative
As reported earlier, the Post Repair schedule called for a two day break.
I used the time to test the new Smart Wait command with both Trailbreaker and Inspector.
Both scripts are working normally, after a bit of back and forth to correct errors. Changes introduced to support the new feature caused downstream issues. Everything is now working correctly.
The new feature is needed for Email Outreach, to guarantee the program is running in the correct account.
71701 was updated during testing.
The normal 300 post cycle will resume tomorrow.
The Email Outreach script will be given sample code from the working scripts.
(th)
Offline