home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Media Source
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Brownard" data-source="post: 1298114" data-attributes="member: 48291"><p>I have identified at least part of the issue, there is an issue in 2.5 where if a network request takes longer than expected and reaches the timeout the request is never marked as finished, e.g. in your case the request to get all network shares times out and the busy spinner is displayed indefinitely because the request never appears to complete. I have a fix for this ready, however it still won't address the underlying issue of the NAS not being found, it will just mean you'll be presented with an empty list of shares if the request times out rather than a permanent busy spinner, which is at least a better behaviour than the current.</p><p></p><p>I don't have any experience with handling a NAS but will try and see if I can get something setup and also investigate why it seems to take so long to enumerate network shares that it can lead to a timeout.</p></blockquote><p></p>
[QUOTE="Brownard, post: 1298114, member: 48291"] I have identified at least part of the issue, there is an issue in 2.5 where if a network request takes longer than expected and reaches the timeout the request is never marked as finished, e.g. in your case the request to get all network shares times out and the busy spinner is displayed indefinitely because the request never appears to complete. I have a fix for this ready, however it still won't address the underlying issue of the NAS not being found, it will just mean you'll be presented with an empty list of shares if the request times out rather than a permanent busy spinner, which is at least a better behaviour than the current. I don't have any experience with handling a NAS but will try and see if I can get something setup and also investigate why it seems to take so long to enumerate network shares that it can lead to a timeout. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Media Source
Contact us
RSS
Top
Bottom