RPM Build Missing howlerjs

[dcrdev 255]

FYI - looks like bower hasn't pulled down the howlerjs package when the .60 rpm was built, the logs are littered with this:

2017-12-20 22:10:30.890 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 3.2.60.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -updatepackage emby-server-rpm_{version}_x86_64.deb
	Operating system: Unix 3.10.0.693
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 8
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	System.IO.DirectoryNotFoundException: Could not find a part of the path '/opt/emby-server/system/dashboard-ui/bower_components/howlerjs/dist/howler.min.js'.
	   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
	   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
	   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileStream(String path, FileOpenMode mode, FileAccessMode access, FileShareMode share, FileOpenOptions fileOpenOptions)
	   at SocketHttpListener.Net.HttpResponseStream.<TransmitFileManaged>d__51.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.FileWriter.<WriteToAsync>d__57.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ResponseHelper.<WriteToResponse>d__0.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__72.MoveNext()
	System.IO.DirectoryNotFoundException
	   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
	   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
	   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
	   at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileStream(String path, FileOpenMode mode, FileAccessMode access, FileShareMode share, FileOpenOptions fileOpenOptions)
	   at SocketHttpListener.Net.HttpResponseStream.<TransmitFileManaged>d__51.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.FileWriter.<WriteToAsync>d__57.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ResponseHelper.<WriteToResponse>d__0.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__72.MoveNext()

^ When I say littered, there are 103 occurrences of the above.

 

I've checked the the howlerjs directory doesn't exist within the rpm.

[Luke 42078]

Thanks, yes indeed the file is missing from the source repository. What device are you browsing from? i am surprised that file is even being requested at all. thanks.

[dcrdev 255]

It's just Chrome on Linux

[Luke 42078]

do you have the halloween theme enabled?

[dcrdev 255]

I do not no - just the default Dark theme.

[Luke 42078]

Do you have another user who might be using it? looking at the code, howler should only be getting requested when we try to play a sound, and the only place that is currently happening is in the Halloween theme. if you're convinced the answer is no, then can you attach a complete log file? thanks !

[dcrdev 255]

Well it's possible that other people might be using the halloween theme I guess, although I can't say for certain. However these errors seem to correspond to my user account - the requests being made directly before are url's that contain my username...

 

You say this is related to automatic audio playback - could this possibly be because I have theme music enabled?

 

If you really want my full log, I'll do upload it later - it's just a bit of a pain scrubbing personal information from it each time.

[Luke 42078]

Nevermind, thanks, i found it. You'll see this over https in browsers that support service worker such as Chrome or Firefox. The log messages are unfortunate, but it will be harmless, so I'm not going to issue an emergency release over this. Thanks.

[dcrdev 255]

Yeah no I wasn't suggesting it caused any issues, just that it's massively inflating the size of the log file.

 

More of a heads up really -would be good if it was fixed in the future.