Description
Serilog Crashed if we set Minimum log level to DEBUG (All Caps)
Reproduction
"Serilog": {
"MinimumLevel": {
"Default": "DEBUG",
Expected behavior
No exception should throw if we provide a log level in Caps
Relevant package, tooling and runtime versions
serilog.aspnetcore v 4.1.0
Additional context
Exception: The value DEBUG is not a valid Serilog level.
Stack:
at Serilog.Settings.Configuration.ConfigurationReader.ParseLogEventLevel(String value)
at Serilog.Settings.Configuration.ConfigurationReader.<ApplyMinimumLevel>g__ApplyMinimumLevel|9_1(IConfigurationSection directive, Action`2 applyConfigAction, <>c__DisplayClass9_0& )
at Serilog.Settings.Configuration.ConfigurationReader.ApplyMinimumLevel(LoggerConfiguration loggerConfiguration)
at Serilog.Settings.Configuration.ConfigurationReader.Configure(LoggerConfiguration loggerConfiguration)
at Serilog.Configuration.LoggerSettingsConfiguration.Settings(ILoggerSettings settings)
at Serilog.ConfigurationLoggerConfigurationExtensions.Configuration(LoggerSettingsConfiguration settingConfiguration, IConfiguration configuration, String sectionName, DependencyContext dependencyContext)
at Serilog.ConfigurationLoggerConfigurationExtensions.Configuration(LoggerSettingsConfiguration settingConfiguration, IConfiguration configuration, DependencyContext dependencyContext)
Link: https://github.com/serilog/serilog/issues/1661
Serilog log levels are Case sensitive?
Related
When I try to run ./bin/webpack-dev-server I get this:
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration has an unknown property 'mode'. These properties are valid:
object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
For typos: please correct them.
For loader options: webpack 2 no longer allows custom properties in configuration.
Loaders should be updated to allow passing options via loader options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
plugins: [
new webpack.LoaderOptionsPlugin({
// test: /\.xxx$/, // may apply this only for some modules
options: {
mode: ...
}
})
]
I'm pretty sure this is yarn messing up with package versions. Is there a "reinstall everything" command I can run?
My versions are
webpack-dev-server#3.4.1
#rails/webpacker#3.5.5
Most likely a problems with webpacker.yml.
In my case source_path was incorrect.
See this: Invalid configuration object when starting webpack-dev-server
My project uses Reactjs, and I use Visual Studio 2017. Recently I did an software update on VS 2017, but no code/config changes.
However, when I start my project locally in debug mode, I encountered below error:
No JavaScript engines were registered, falling back to a default config! It is recommended that you configure JavaScriptEngineSwitcher in your app. See https://github.com/Taritsyn/JavaScriptEngineSwitcher/wiki/Registration-of-JS-engines for more information.
Error initialising JavaScriptEngineSwitcher.V8.V8JsEngineFactory: JavaScriptEngineSwitcher.Core.JsEngineLoadException: During loading of V8JsEngine error has occurred.
See more details:
Cannot load V8 interface assembly. Load failure information for v8-ia32.dll:
C:\Users\user1\AppData\Local\Temp\Temporary ASP.NET Files\vs\77655ce5\ca0bb6d0\assembly\dl3\300b733a\003cadac_c3f4d201\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\bin\v8-ia32.dll: The specified module could not be found ---> System.TypeLoadException: Cannot load V8 interface assembly. Load failure information for v8-ia32.dll:
C:\Users\user1\AppData\Local\Temp\Temporary ASP.NET Files\vs\77655ce5\ca0bb6d0\assembly\dl3\300b733a\003cadac_c3f4d201\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\bin\v8-ia32.dll: The specified module could not be found
at Microsoft.ClearScript.V8.V8Proxy.LoadNativeLibrary()
at Microsoft.ClearScript.V8.V8Proxy.LoadAssembly()
at Microsoft.ClearScript.V8.V8Proxy.GetAssembly()
at Microsoft.ClearScript.V8.V8Proxy.GetImplType(Type type)
at Microsoft.ClearScript.V8.V8Proxy.CreateImpl[T](Object[] args)
at Microsoft.ClearScript.V8.V8IsolateProxy.Create(String name, V8RuntimeConstraints constraints, Boolean enableDebugging, Int32 debugPort)
at Microsoft.ClearScript.V8.V8Runtime..ctor(String name, V8RuntimeConstraints constraints, V8RuntimeFlags flags, Int32 debugPort)
at Microsoft.ClearScript.V8.V8ScriptEngine..ctor(V8Runtime runtime, String name, V8RuntimeConstraints constraints, V8ScriptEngineFlags flags, Int32 debugPort)
at JavaScriptEngineSwitcher.V8.V8JsEngine..ctor(V8Settings settings)
--- End of inner exception stack trace ---
at JavaScriptEngineSwitcher.V8.V8JsEngine..ctor(V8Settings settings)
at JavaScriptEngineSwitcher.V8.V8JsEngineFactory.CreateEngine()
at React.JavaScriptEngineFactory.GetFactory(JsEngineSwitcher jsEngineSwitcher, Boolean allowMsie)
Error initialising React.VroomJsEngine+Factory: JavaScriptEngineSwitcher.Core.JsEngineLoadException: During loading of VroomJs JavaScript engine error has occurred.
See more details:
The type initializer for 'VroomJs.JsEngine' threw an exception. ---> System.TypeInitializationException: The type initializer for 'VroomJs.JsEngine' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'VroomJsNative': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at VroomJs.JsEngine.js_set_object_marshal_type(JsObjectMarshalType objectMarshalType)
at VroomJs.JsEngine..cctor()
--- End of inner exception stack trace ---
at VroomJs.JsEngine..ctor(Int32 maxYoungSpace, Int32 maxOldSpace)
at React.VroomJsEngine.<>c.<.cctor>b__23_0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at System.Lazy`1.get_Value()
at React.VroomJsEngine.get_Engine()
at React.VroomJsEngine..ctor()
--- End of inner exception stack trace ---
at React.VroomJsEngine..ctor()
at React.VroomJsEngine.Factory.CreateEngine()
at React.JavaScriptEngineFactory.GetFactory(JsEngineSwitcher jsEngineSwitcher, Boolean allowMsie)
This error does not block me from running and testing the code.
Like I said, all I did recently was to update the VS 2017 software...I tried to do a wild search in the project for 'v8-ia32' but nothing found.
To fix these errors I did the following:
Make sure you install the JavaScriptEngineSwitcher.V8, JavaScriptEngineSwitcher.V8.Native.win-x86 and JavaScriptEngineSwitcher.V8.Native.win-x64.
(I didn't install JavaScriptEngineSwitcher.V8.Native.win-x86)
According to https://reactjs.net/getting-started/aspnet.html
edit the ReactConfig.cs, basically, I just added this
JsEngineSwitcher.Current.DefaultEngineName = V8JsEngine.EngineName;
JsEngineSwitcher.Current.EngineFactories.AddV8();
Rebuild the project.
I'm receiving the following error within TFS
Exception Message: TF246021: An error occurred while processing your
request. Technical information (for administrator): SQL Server Error:
2601 (type VersionControlException) Exception Stack Trace: Server
stack trace: at
Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation
operation, TfsMessage message, Object[]& outputs) at
Microsoft.TeamFoundation.VersionControl.Client.Repository5.LabelItem(String
workspaceName, String workspaceOwner, VersionControlLabel label,
LabelItemSpec[] labelSpecs, LabelChildOption children, Int32
maxClientPathLength, Failure[]& failures) at
Microsoft.TeamFoundation.VersionControl.Client.WebServiceLayer.LabelItem(String
workspaceName, String workspaceOwner, VersionControlLabel label,
LabelItemSpec[] labelSpecs, LabelChildOption children, Failure[]&
failures) at
Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer.CreateLabel(VersionControlLabel
label, LabelItemSpec[] itemSpecs, LabelChildOption options, Failure[]&
failures) at
Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.RunCommand(VersionControlScope
versionControlScope, String nonFatalError, VersionControlLabel label,
IEnumerable`1 items, LabelChildOption childOption) at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Object[]& outArgs) at
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage
msg, IMessageSink replySink)
Exception rethrown at [0]: at
System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message
reqMsg, Boolean bProxyCase) at
System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed,
MessageData& msgData) at System.Func6.EndInvoke(IAsyncResult
result) at
Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.EndExecute(AsyncCodeActivityContext
context, IAsyncResult result) at
System.Activities.AsyncCodeActivity1.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext
context, IAsyncResult result) at
System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor
executor, BookmarkManager bookmarkManager)
Inner Exception Details:
Exception Message: TF246021: An error occurred while processing your
request. Technical information (for administrator): SQL Server Error:
2601 (type SoapException)SoapException Details: Exception
Stack Trace:
I've read a previous post within StackOverflow which points at recreating workspaces, I tried that and it doesn't work.
Also I've tried to clean the cache, again without any luck. One thing I noticed when I go and disable 'Label Sources' and run the a build it works. I believe its to do with creating a branch and then deleting some files from a main branch which then gets TFS into a mess. I'm not sure whats the best way to fix this, it'll be difficult to upgrade to a newer version of TFS.
Make sure your TFS 2012 has been upgraded to the latest edition Update 4.
Make sure the build server has the same edition with TFS Application Tier.
Make sure both client cache and server cache are cleaned. Client cache: C:\Users\username\AppData\Local\Microsoft\Team Foundation\4.0\Cache. Server cache: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v11.0
Check Event log in Event Viewer to see whether there is something helpful.
I am building an application but getting an error. Can someone help me to understand how to resolve this?
Exception Message: The request was rejected by the server.Technical
information: HTTP code 400: Bad Request (type
TeamFoundationServerInvalidRequestException)Exception Stack Trace:
at
Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.ReadResponse(HttpWebResponse
webResponse, WebException webException) at
Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.IsAuthenticationChallenge(TfsMessage
requestMessage, HttpWebResponse webResponse, WebException
webException, TfsMessage& responseMessage) at
Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.SendRequest()
at
Microsoft.TeamFoundation.Client.Channels.TfsHttpRequestChannel.Request(TfsMessage
message, TimeSpan timeout) at
Microsoft.TeamFoundation.Client.Channels.TfsHttpRetryChannel.Request(TfsMessage
message, TimeSpan timeout) at
Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation
operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at
Microsoft.TeamFoundation.TestImpact.Client.TestImpactServer.Microsoft.TeamFoundation.TestImpact.Client.ITestImpactServer.PublishBuildChanges(Uri
buildUri, CodeChange[] changes) at
Microsoft.TeamFoundation.TestImpact.BuildIntegration.BuildActivities.GetImpactedTests.Execute(CodeActivityContext
context) at
System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at
System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
executor, BookmarkManager bookmarkManager, Location
resultLocation)Inner Exception Details:Exception Message: The remote
server returned an error: (400) Bad Request. (type
WebException)Status: ProtocolErrorResponse Status Code:
BadRequestResponse Status Message: Bad RequestException Stack Trace:
at System.Net.HttpWebRequest.GetResponse()
I've just ran into the same issue with TFS2013 and our CI builds.
It seems that the error happens with the Test Impact analyser fails somehow.
You can alter your build configuration to not analyse the test impact.
It depends on which build template you are using, but for Scrum 2013, you'll find it under
It's under: Process > Test > Advanced > Analyze Test Impact - set this to false.
Jaans' "solution" works for me too, obviously. As for the cause I started seeing this error after enabling obfuscation as part of my TFS build.
Doesn't look like it's possible to disable test impact analysis only for the release configuration - debug is not obfuscated. If I really want the test impact analysis I'll need 2 build definitions and don't build the release configuration for the one where the test impact analysis is enabled.
It's also "interesting" that it breaks the build even if there are no UT.
I didn't find why it occurs, but I resolved the error using a loop and a try-catch until get impacted tests succeeded.
When attempting to run an ASP.NET MVC application which uses Castle Windsor, the following error occurs.
Server Error in '/' Application.
Inheritance security rules violated while overriding member:
'Castle.MicroKernel.DefaultKernel.InitializeLifetimeService()'.
Security accessibility of the overriding method must match the
security accessibility of the method being overriden.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
Exception Details: System.TypeLoadException: Inheritance security
rules violated while overriding member:
'Castle.MicroKernel.DefaultKernel.InitializeLifetimeService()'.
Security accessibility of the overriding method must match the
security accessibility of the method being overriden.
Source Error:
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.
Stack Trace:
[TypeLoadException: Inheritance security rules violated while
overriding member:
'Castle.MicroKernel.DefaultKernel.InitializeLifetimeService()'.
Security accessibility of the overriding method must match the
security accessibility of the method being overriden.]
Castle.Windsor.WindsorContainer..ctor() +0
The assemblies Castle.Core.dll and Castle.Windsor.dll have been built off the source code available on github. The source code for the assemblies includes the file SecurityAssemblyInfo.cs which has the following source code:
// Sets up assembly level security settings
#if ! SILVERLIGHT
[assembly: System.Security.AllowPartiallyTrustedCallers]
#if DOTNET40
[assembly: System.Security.SecurityRules(System.Security.SecurityRuleSet.Level2)]
#endif
#endif
I have verified using ILSpy that the System.Security.AllowPartiallyTrustedCallers attribute is declared at the assembly on both files.
The web application is being run with <trust level="Medium" />.
I have been able to get a successful build + run of my mvc application by making the following changes to Castle.Core:
SecurityAssemblyInfo.cs:
Changed to only the following:
[assembly: System.Security.AllowPartiallyTrustedCallers]
[assembly: System.Security.SecurityRules(System.Security.SecurityRuleSet.Level1)]
ProxyGenerator.cs:
Changed three lines in ProxyGenerator::ProxyGenerator(IProxyBuilder):
if (HasSecurityPermission())
{
Logger = new TraceLogger("Castle.DynamicProxy", LoggerLevel.Warn);
}
becomes:
// if (HasSecurityPermission())
// {
// Logger = new TraceLogger("Castle.DynamicProxy", LoggerLevel.Warn);
// }
I have no idea what sort of consequences these might have. It would be nice if someone familiar with the SecurityRuleSets could chime in on the first part, and #Krzysztof Koźmic could advise me on why I had to comment out the trace logger.