Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Why this ERROR message with a builtin function



  • Hi,

    I have this message :

    Deleting temporary script file (/tmp/buildmaster/scripts/469c381be3da4dfea2f6af351188c512)...
    Temporary file deleted.
    Could not resolve function @Split.
    Cleaning up...

    I don't understand because @Split is a builtin function .

    Any clue what's happening ?

    Kind Regards.

    Product: BuildMaster
    Version: 6.0.10


  • inedo-engineer

    Can you give us a little more context? Like, what is your OtterScript overall?

    One possibility is that the INedoCore extension had a load error, though I suspect you'd have another problem if that were the case.


  • inedo-engineer

    Hi,

    the script who is stored in a global module

    ##AH:UseTextMode
    module ParseURL<out $JsonFile>

    {

    set $URL = $DEPLOYABLE_URL;
    
    set $PATH = $DEPLOYABLE_PATH;
    
    set @MYLIST = @();
    
    Log-Debug Split URL /;
    
    foreach $DATA in @Split($URL,"/")
    {
        # Log-Debug $Data;
        set $DATA = $Trim($DATA);
    
        if $DATA != ""
        {
            set @MYLIST = @ListInsert(@MYLIST, $DATA);
        }
    }
    

    ......

    Sometimes, it works, but the major part of the time I have the error resumed above.
    I found nothing in the diagnostic center et nothing in the event viewer of the widows server.

    Does exist other logs somewhere ?

    Kind Regards


  • inedo-engineer

    At this time, the only thing we're aware of that can cause "Could not resolve function" is that the function has not been loaded by the service. Functions are stored in extensions, and Split is stored in Inedo Core extension, so this would actually cause all sorts of errors.

    I created an issue (BM-3255) to give a warning if this extension is not loaded. But please restart the service, check for extension load errors in the message center, and try again.

    Restarting the service would be the only way to resolve this, since extensions are loaded at service start.



  • Hi,

    I got the InedoCore extension from an other installation on an other machine.
    And I copied it into the extension folder, restart the service and it works now.

    Thanks for the answers.

    KR.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation