Stream: IG creation
Topic: Using fhir.davinci.template
Saul Kravitz (Mar 27 2020 at 15:13):
I'm trying to use the davinci template ...obviously, without success.... @Lloyd McKenzie
I've tried the following in the ig.ini file:
template = fhir.davinci.template#0.0.1
I get the error: "Error loading template fhir.davinci.template#0.0.1: Unable to resolve package id fhir.davinci.template (00:03.0979)"
template = fhir.davinci.template
I get the error: "Error loading template fhir.davinci.template: The package 'fhir.davinci.template' has not entry on the current build "
Thoughts?
Lloyd McKenzie (Mar 27 2020 at 15:20):
I just forced the template to re-build. It's possible the package repository got wiped with some work Grahame was doing. Try again and let me know if there's still a problem.
Saul Kravitz (Mar 27 2020 at 15:37):
No change. I updated Publisher and reran...
template = fhir.davinci.template#0.0.1
I get the error:Error loading template fhir.davinci.template#0.0.1: Unable to resolve package id fhir.davinci.template (00:05.0626)
template = fhir.davinci.template
I get the error: "Error loading template fhir.davinci.template: The package 'fhir.davinci.template' has not entry on the current build server (00:02.0582)
Lloyd McKenzie (Mar 27 2020 at 16:33):
Try again. (You'll need to use #current)
Saul Kravitz (Mar 28 2020 at 22:38):
Hi Lloyd, still no luck...am I doing something wrong?
skravitz@MM255565-PC build % ./_updatePublisher.sh
Downloading most recent publisher - it's ~100 MB, so this may take a bit
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 85.5M 100 85.5M 0 0 10.8M 0 0:00:07 0:00:07 --:--:-- 11.9M
Done
skravitz@MM255565-PC build % ./_genonce.sh
FHIR IG Publisher Version 1.0.75-SNAPSHOT (Git# 3c0b2e71171e). Built 2020-03-28T07:12:58.718+11:00 (26 hours old)
Detected Java version: 1.8.0_242 from /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre on x86_64 (64bit). 3641MB available
Parameters: -ig ig.ini
dir = /Users/skravitz/git/pdex-plan-net-fsh/build, path = /Users/skravitz/.rvm/gems/ruby-2.6.3/bin:/Users/skravitz/.rvm/gems/ruby-2.6.3@global/bin:/Users/skravitz/.rvm/rubies/ruby-2.6.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/skravitz/.rvm/bin
Run time = Saturday, March 28, 2020 6:37:17 PM EDT (2020-03-28T18:37:17-04:00)
Package Cache: /Users/skravitz/.fhir/packages (00:00.0097)
Load Template from fhir.davinci.template#current (00:01.0721)
Publishing Content Failed: Error loading template fhir.davinci.template#current: The package 'fhir.davinci.template' has not entry on the current build server (00:02.0840)
(00:02.0840)
Use -? to get command line help (00:02.0840)
(00:02.0841)
Stack Dump (for debugging): (00:02.0841)
org.hl7.fhir.exceptions.FHIRException: Error loading template fhir.davinci.template#current: The package 'fhir.davinci.template' has not entry on the current build server
Lloyd McKenzie (Mar 28 2020 at 22:47):
Sorry for not catching this sooner. The string you're using for the template name is wrong. The line that you want in your ig.ini is this:
template = hl7.davinci.template#current
Chris Moesel (Mar 29 2020 at 22:29):
@Lloyd McKenzie - the template name @Saul Kravitz was using is straight from the IG Guidance doc, so it needs to be fixed there.
Lloyd McKenzie (Mar 29 2020 at 23:01):
Fixed
Saul Kravitz (Mar 30 2020 at 13:43):
OK, I get past the previous issue, but have a new template-related issue.
(BTW, everything runs fine with hl7.fhir.template#0.1.0)
IG publication terminates with the following error:
onGenerate.jira.generate:
[xslt] Processing /Users/skravitz/git/pdex-plan-net-fsh/build/template/package-list.tmp.xml to /Users/skravitz/git/pdex-plan-net-fsh/build/template/package-list.xml
[xslt] Loading stylesheet /Users/skravitz/git/pdex-plan-net-fsh/build/template/scripts/onGenerate.package-list.xslt
[xslt] Processing /Users/skravitz/git/pdex-plan-net-fsh/build/template/jira.tmp.xml to /Users/skravitz/git/pdex-plan-net-fsh/build/template/jira.xml
[xslt] Loading stylesheet /Users/skravitz/git/pdex-plan-net-fsh/build/template/scripts/onGenerate.jira.xslt
[xslt] : Warning! The source document is in no namespace, but the template rules all expect elements in a namespace
First "url" contact telecom must start with "http://hl7.org/Special/committees/"
[xslt] /Users/skravitz/git/pdex-plan-net-fsh/build/template/scripts/onGenerate.jira.xslt:17: Fatal Error! Processing terminated by xsl:message at line 17 in onGenerate.jira.xslt
[xslt] Failed to process /Users/skravitz/git/pdex-plan-net-fsh/build/template/jira.tmp.xml
Publishing Content Failed: Fatal error during transformation using /Users/skravitz/git/pdex-plan-net-fsh/build/template/scripts/onGenerate.jira.xslt: Processing terminated by xsl:message at line 17 in onGenerate.jira.xslt; SystemID: file:/Users/skravitz/git/pdex-plan-net-fsh/build/template/scripts/onGenerate.jira.xslt; Line#: 17; Column#: -1 (01:41.0541)
(01:41.0541)
This error was created by the template (01:41.0541)
Lloyd McKenzie (Mar 30 2020 at 13:57):
First "url" contact telecom must start with "http://hl7.org/Special/committees/"
Your IG needs to declare a 'url' contact with the web page for the responsible work group
Saul Kravitz (Mar 30 2020 at 15:01):
OK. I'm in business... I humbly suggest that this is a very obscure error message for a very glaring error (not specifying an appropriate author , or author contact info). Thanks for your help!
Lloyd McKenzie (Mar 30 2020 at 15:16):
If you give me proposed text you think would be clearer, I'll make the change
Saul Kravitz (Mar 30 2020 at 21:54):
1) Wouldn't this be much more visible as an error in the QA report, instead of having the IG publisher quit?
2) If it must be a harsh quit include the filename and line number of the file triggering the problem and a message "Contact info for IG must reference an HL7 committee and start with....".
My 2 cents...
Thx again and stay safe/sane.
Grahame Grieve (Mar 30 2020 at 22:03):
it would be better in the qa report. @Lloyd McKenzie I don't think we have any arrangements that allow that right now?
Lloyd McKenzie (Mar 30 2020 at 22:08):
I can - and do with some things, but it's slightly harder with this one. I'll see if I can refactor to make that happen
Carl Anderson (Jul 14 2020 at 19:26):
I should add here that when I encountered this, I thought the error was suggesting me to add a contact.telecom.url property to my config.yaml for sushi. However, in config.yaml, the place to add the url is in publisher.url (as is done in this example).
Last updated: Apr 12 2022 at 19:14 UTC
