just running through Levente’s example scripts. having followed through the video, and double checked the scripts he posted to github, I keep getting this error message when I try to compile my dar file.
%daml build
2022-01-01 02:26:10.93 [INFO] [build]
Compiling nft to a DAR.
File: daml/UserAdmin.daml
Hidden: no
Range: 88:28-88:28
Source: parser
Severity: DsError
Message: daml/UserAdmin.daml:88:28: error:You cannot use `…’ in a record update
File: daml/Token.daml
Hidden: no
Range: 39:2-39:10
Source: parser
Severity: DsError
Message: daml/Token.daml:39:2: error: parse error on input ‘template’
ERROR: Creation of DAR file failed.
I know where the problem is, but after an hour of fiddling, I can’t seem to figure out a way around it. any ideas what I am bumping into? I am assuming his compiled (at least it looked like they did in his vid.).
Hi @rps, I’m unable to reproduce this issue after cloning the repository both with SDK 1.13.1 as specified in the repo as well as after upgrading to SDK 1.18.0.
Could it be that you introduced some changes either after cloning or you manually copied the files and introduced some changes during that?
I am running the latest .sdk but it was not from a starting point of a 1.13.1 upgrade.
Pretty sure the issue is in here somewhere: Message: daml/UserAdmin.daml:100:28: error:You cannot use `…’ in a record update and it may just be a matter of the apostrophe type used. Will try digging around in that.
ok that was not the problem. there were some spelling mistakes (I followed along as he presented and it was late).
got that taken care of, then a gRPC error.
Saved all the .daml files and restarted daml studio
and I could build!!!
Yippee! being able to compile a .DAR file is the BEST way to start 2022!
Thanks for your help cocreature and happy 2022 to you!
HNY! I too had some issues when following along with those examples, it was not due to any error on @Levente_Barczy behalf but I suspect as you have discovered, user transcription errors.
There were a few times when a code block was referenced but only briefly, then the work flow would jump to something a little different or further up the code.
I think that I contacted @Levente_Barczy or @nemanja over this, I’ll check my records to confirm/deny.
Looking forward to an amazing year for Digital Asset and Daml \o/
OMG. I was following so closely, as you probably were, and then a section would be corrected or updated and I would think, “Wait a minute, that was not there.” From my side, it took updating just a couple of upper case letters in the wrong place to sort myself out.
What I will say is that I have never, ever worked with materials where I felt such an investment from anyone into helping me learn. That is from the heart. I am so indebted to the guys at DA training because even when my code would not compile or run, I could try it on Katacoda, or read about it, or try an example on Daml.Hub.
I love to learn and although I spent a great deal of time doing that with this material, I have thoroughly enjoyed the whole experience.
Thanks to each and every contributor on the Daml side. Thanks to a wonderful community (quidagis, you can’t imagine how great it is to find a positive comment from you after a long, brutal day). Thanks to DA management for being smart enough to get a bunch of phenomenally brilliant people together and allowing them to create this whole ecosystem.