• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 180 subscribers
  • Views 1819 views
  • Users 0 members are here
Options
Related

InSource bugs

Daniel Hug

Hello,

I just started using InSource, a great add-on!

There are quite a few bugs when using it with 2019 SR1 CU3, and I would like to list them here in the hope that they can be fixed...

1) I have a notification in Studio for each watch folder I define, regardless of whether there are subfolders with project requests in them or not.

2) If I click on "Create Project" in Studio's notification view, I will invariably get this error message (yes, I did assign project templates to each watch folder):

EDIT: There are actually two different error messages in this context. The above one pops up when I click on "Create Project" where there is no project proposal (no subfolder and no files in the watch folder) and this one pops up if there is a project proposal:

3) A similar problem in the InSource view itself: I get the above another error message when clicking on a project proposal and selecting "create project". This can be avoided by re-selecting a project template (somehow refreshing the selection). EDIT: The following error message pops up when trying to create a project from the InSource view:

So my impression is that all three bugs are related and probably stem from one source. Maybe an incompatibility came up with Studio's CU3?

It's a great plug-in, would be wonderful if somebody could look into this.

Daniel
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Okay, my bad: The templates I was testing with at this point did not have project location filled in... But I would hope for better error handling here:

    (This is in ProjectCreator.cs)

    Filling in the project location changes the way Studio's notification view works (or does not work):

    1) Empty folders still show up an projects under Studio's notifications view. Clicking on "Create Project" results in the same error as described above.

    2) Folders with actual project proposals disappear after clicking "Create Project". The wheel spins a bit, and then Studio is available. The notification is gone (until you check for projects again in InSource). Nothing else happens as far as I can tell.

    Another bug found: I can only add watch folders that have no content.

    Daniel
  • 0 in reply to Daniel Hug

    Hi

    Thanks for your feedback, and I'm glad you found the problem.  We should probably make clear a little history behind this plugin since it was created as an example of what's possible for developers so that they can refine it specifically to their needs.  So the UI, and the functionality is indeed a bit rough around the edges.  There's a link in the ribbon to the source for this reason: https://github.com/sdl/Sdl-Community/tree/master/InSource

    But we will take a look at the issues raised and at least make sure that it behaves as expected.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Hi 

    Thanks for the quick reply. I do appreciate the functionality of this app, yes the UI is rough, but I also appreciate that it's a small project so getting into it and trying to understand the code is not quite so intimidating.

    I did find the link and made use of it, as you can see.

    More bugs:

    InSource seems to be set up to handle single file projects:

    private FileBasedProject CreateProject(ProjectRequest request)

    But they don't show up at all in the InSource view and there seems to be no way to create a project from them from here. However, in Studio's notification view they create a proper Studio error and make studio crash. Here's the stacktrace:

    Fullscreen sdlerror-2019529-15h45m23s.sdlerror.xml Download 
    <SDLErrorDetails time="29-May-19 15:45:36">
  <ErrorMessage>Could not find a part of the path 'V:\05 Writing\!GERMANY\03 Translation Projects Watch folders\Categories\Catalogues Booklets Flyers\Catalogues Booklets Flyers'.</ErrorMessage>
  <Exception>
    <Type>System.IO.DirectoryNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.Community.InSource</Source>
    <HResult>-2147024893</HResult>
    <StackTrace><![CDATA[   at Sdl.Community.InSource.InSource.RequestAccepted(ProjectRequest request)
   at Sdl.Community.InSource.InSourceViewController.<>c__DisplayClass48_0.<CreateProjectsFromNotifications>b__1(Object sender, RunWorkerCompletedEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
   at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Sdl.Desktop.Platform.Implementation.Studio.Run()
   at Sdl.TranslationStudio.Application.ApplicationStartup.RunApplication()
   at Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.1.3.55768</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>danielhug</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ABCD</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>12581868 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

    My feeling is that all or almost all the problems in this app are around how paths are handled.

    Again, thanks for the app and for the support!

    Daniel
  • 0 in reply to Paul

    Hi 

    Since installing InSource, I also get this error:

    Clicking "continue" has no effect and clicking "close" closes Studio and it takes a while until I can start it up again (the license is available again).

    This occurs only after Studio has been running quite a long time: I suspect the timer (checking for new project requests) to be responsible, but that's just my gut feeling.

    (I was never actively using Studio when this error occurred.)

    Daniel
Reply Children
No Data