search

microsoft / MLNETExcel

Excel Add-In to make predictions using ML.NET Models - Built on Blazor WASM
MIT License
12 stars 1 forks source link

Error running MLNET Add-on #19

Closed bkrabach closed 2 years ago

bkrabach commented 2 years ago

After uploading the manifest, received the following error. It was not clear how I could fix this.

InvalidQueryParameterValueValue for one of the query parameters specified in the request URI is invalid. RequestId:2e7f2423-f01e-002a-4e0c-646ada000000 Time:2022-05-10T01:22:29.0303870Zcomp

bkrabach commented 2 years ago

Error was due to wrong url posted, but it'd be great if a more user-friendly error was surfaced that may help to troubleshoot the error.

bkrabach commented 2 years ago

Once I got it running, I still received the error "unhandled error occurred" when attempting to execute the predict function.

luisquintanilla commented 2 years ago

@bkrabach thanks for the feedback. Where did you see the original error you posted? If it came from Excel, unfortunately I don't think we (ML.NET / Blazor) have control over those error messages.

bkrabach commented 2 years ago

Both errors were in Excel. The first was the only text in the add-on box/panel on the right of the worksheet. The second error was more like a notification at the bottom of the panel (the panel still displayed the normal instructions for the add-on).

I was wondering if there was error handling that could be added to the add-on that could be used to trigger a better error? I'm assuming since we've only pointed to a manifest so far, and the error was in loading the actual add-on code, that this is probably not possible - that said, I didn't investigate the manifest to see what options do exist.

luisquintanilla commented 2 years ago

Let me look into that. From my understanding the main purpose of the manifest is to point Excel to the website containing the add-on code and related metadata but maybe there is a way to better to get Excel to handle errors for those cases when the add-in can't be loaded.

luisquintanilla commented 2 years ago

I was unable to use the Manifest to throw / handle errors. Closing for now but I'll keep an eye on this. Thanks @bkrabach