The Lounge - CodeProject

Re: One commit ago, Dart code worked just fine

Mark_Wallace31-Jan-20 10:12

Mark_Wallace

31-Jan-20 10:12

Just flag it: "Won't fix: works on my machine sometimes".

I wanna be a eunuchs developer! Pass me a bread knife!

Re: One commit ago, Dart code worked just fine

Jon McKee31-Jan-20 11:11

Jon McKee

31-Jan-20 11:11

contacts.forEach((contact) async {
  // This variable is a placeholder to support debugging the response from database.
  var _contact = await database.recipientDao.findRecipientById(contact.identifier);
  if(_contact == null) {
    // Save the contact.
    newContacts.add(Recipient(contact.identifier, contact.displayName));
  }
});

if(newContacts.length > 0) {

Never used Dart before, but everything in my being is telling me that looks dangerous if forEach isn't a blocking function. Some quick googling tells me you may want to try Future.forEach.

Re: One commit ago, Dart code worked just fine

Afzaal Ahmad Zeeshan31-Jan-20 12:20

Afzaal Ahmad Zeeshan

31-Jan-20 12:20

Yep, you're right. What I am thinking about this is something like:

Future<void> processContacts(List<Contact> contacts) async {
   for (var contact in contacts) {
      if(await database.recipientDao.findRecipientById(contact.identifier) == null) {
         // rest of the async code.
      }
   }
}

Future.forEach follows the similar approach to call the function that returns a Future, and await on it internally.

Who knows, if I change the code to this approach, the problem goes away. Confused | :confused:

The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~

Re: One commit ago, Dart code worked just fine

Jon McKee31-Jan-20 13:08

Jon McKee

31-Jan-20 13:08

I don't know enough about Dart to say. It depends on what you're looking to accomplish. If you want sequential but non-blocking processing of the list, yea I think it should work as long as you await on that function.

EDIT: Removed a sentence, been reading up on asynchronous stuff in Dart and it's the same as C# where it doesn't allow await inside of a non-async function.

Re: One commit ago, Dart code worked just fine

honey the codewitch31-Jan-20 11:29

honey the codewitch

31-Jan-20 11:29

Afzaal Ahmad Zeeshan wrote:
Interesting thing is that this is the same code I committed last night!

~~The fact that it didn't work before and did work now would seriously concern me.~~

Whoops I understood your post backward

Anyway, what I would consider is that your environment changed. See if there were any other commits or changes to the server?

Real programmers use butterflies

Re: One commit ago, Dart code worked just fine

Afzaal Ahmad Zeeshan31-Jan-20 12:27

Afzaal Ahmad Zeeshan

31-Jan-20 12:27

Quote:
what I would consider is that your environment changed

Nope, it is all same.

The file is just 50 lines of code and using the tip of Jon, I am considering a rewrite for this service, most probably that would spot any bugs if there are in my code.

A big problem with Flutter is that it too often requires a flutter clean to remove the clutter, most problems were solved that way, but not this.

The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~

Re: One commit ago, Dart code worked just fine

Eddy Vluggen31-Jan-20 11:42

Eddy Vluggen

31-Jan-20 11:42

No, no, that won't do.

The usual complaint in the forum is that it worked yesterday, and nothing changed and it just stopped working.

You can't just admit you broke it like that.

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Re: One commit ago, Dart code worked just fine

Afzaal Ahmad Zeeshan31-Jan-20 12:30

Afzaal Ahmad Zeeshan

31-Jan-20 12:30

Quote:
is that it worked yesterday, and nothing changed and it just stopped working.

Not yesterday, just one commit ago.

Nothing changed, restarted the emulators to try everything with fresh app installation and it stopped working. I did a hard reset on my Git, but still the same. Sigh | :sigh:

The take away is, always test the code from the beginning and then commit. Sadly, I did not have the tests written to verify these services (contacts storage and database) so this is what I need to work on.

The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~

Re: One commit ago, Dart code worked just fine

Eddy Vluggen31-Jan-20 12:55

Eddy Vluggen

31-Jan-20 12:55

Afzaal Ahmad Zeeshan wrote:
Nothing changed

Exactly what I wanted to hear Big Grin | :-D

Yes, cherry picking, and not meant to be taken too seriously.

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Cloning disks - UEFI hell

charlieg31-Jan-20 8:26

charlieg

31-Jan-20 8:26

Any UEFI, TPM, Windows 10 wizards around? Maybe a link to a suggested Microsoft discussion forum...

All I'm trying to do is clone old disk drive to new SSD. I've done it in a disk duplicator, I've used multiple target SSDs, and tried multiple s/w packages - Macrium Reflect, AEOMI (or whatever), Acronis 2020. Nothing yields a bootable UEFI disk.

My working theory is that when you install Windows 10, something is registered in the TPM module on the motherboard. Read about TPM. *try* and find info on how Windows 10 uses it. Anyway, I think the keys mismatch, and Windows 10 refuses to run. Updating some past posts on other sites, I came across this post:

Quote:
It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

What irritates the heck out of me is that there is no "why" explanation. Why do I have to do it this way?
Mad | :mad:

Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...

"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759

Welcome to the Lounge