本篇文章给大家谈谈angular版本问题&compiler_cli_1.readConfigurationisnotafunction,以及angular各个版本区别的知识点,同时本文还将给你拓展:N
本篇文章给大家谈谈angular版本问题&compiler_cli_1.readConfiguration is not a function,以及angular各个版本区别的知识点,同时本文还将给你拓展: No JAAS configuration section named ''Client'' was found in specified JAAS configuration file:、c# – ConfigurationSection ConfigurationManager.GetSection()始终返回null、c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException、Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':classpath'.等相关知识,希望对各位有所帮助,不要忘了收藏本站喔。
本文目录一览:- angular版本问题&compiler_cli_1.readConfiguration is not a function(angular各个版本区别)
- : No JAAS configuration section named ''Client'' was found in specified JAAS configuration file:
- c# – ConfigurationSection ConfigurationManager.GetSection()始终返回null
- c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException
- Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':classpath'.
angular版本问题&compiler_cli_1.readConfiguration is not a function(angular各个版本区别)
问题一、angular版本问题
cielo@cielo-ThinkPad-E550:~/cprogrames/test-bna/angular-test$ ng serve
The serve command requires to be run in an Angular project, but a project deFinition Could not be found.
用npm start也是同样的问题。
cielo@cielo-ThinkPad-E550:~/cprogrames/test-bna/angular-test$ npm start
> angular-test@0.0.1 start /home/cielo/cprogrames/test-bna/angular-test
> ng serve --proxy-config proxy.conf.js --host 0.0.0.0
The serve command requires to be run in an Angular project, but a project deFinition Could not be found.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! angular-test@0.0.1 start: `ng serve --proxy-config proxy.conf.js --host 0.0.0.0`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-test@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/cielo/.npm/_logs/2019-04-12T13_09_57_716Z-debug.log
该问题解决方案:
ng update @angular/cli --migrate-only --from=1.7.3
https://stackoverflow.com/questions/53096996/angular-cli-error-the-serve-command-requires-to-be-run-in-an-angular-project-b
作者:低调奋进
来源:CSDN
原文:https://blog.csdn.net/zwbHUST/article/details/89024467
版权声明:本文为博主原创文章,转载请附上博文链接!
其实我也在starkoverflow看到了。
我的版本明明是7.3.8,但是–from=【】这块写7.3.8没有用。
不过运行了之后好了似乎。报了新的错误
问题二
红一片,我的心情不知道该如何描述。
cielo@cielo-ThinkPad-E550:~/cprogrames/test-bna/angular-test$ npm start
> angular-test@0.0.1 start /home/cielo/cprogrames/test-bna/angular-test
> ng serve --proxy-config proxy.conf.js --host 0.0.0.0
>
compiler_cli_1.readConfiguration is not a function
TypeError: compiler_cli_1.readConfiguration is not a function
at AngularCompilerPlugin._setupOptions (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:92:39)
at new AngularCompilerPlugin (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:53:14)
at _createAotPlugin (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/typescript.js:37:12)
at Object.getNonAotConfig (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/typescript.js:43:19)
at browserBuilder.buildWebpackConfig (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/src/browser/index.js:89:37)
at DevServerBuilder.buildWebpackConfig (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/src/dev-server/index.js:108:46)
at MergeMapSubscriber.rxjs_1.from.pipe.operators_1.concatMap [as project] (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/src/dev-server/index.js:36:40)
at MergeMapSubscriber._tryNext (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:69:27)
at MergeMapSubscriber._next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:59:18)
at MergeMapSubscriber.Subscriber.next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Subscriber.js:67:18)
at TapSubscriber._next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/tap.js:65:26)
at TapSubscriber.Subscriber.next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Subscriber.js:67:18)
at MergeMapSubscriber.notifyNext (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/operators/mergeMap.js:92:26)
at InnerSubscriber._next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/InnerSubscriber.js:28:21)
at InnerSubscriber.Subscriber.next (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/build-angular/node_modules/rxjs/internal/Subscriber.js:67:18)
at SafeSubscriber.__tryOrUnsub (/home/cielo/cprogrames/test-bna/angular-test/node_modules/@angular-devkit/architect/node_modules/rxjs/internal/Subscriber.js:209:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! angular-test@0.0.1 start: `ng serve --proxy-config proxy.conf.js --host 0.0.0.0`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-test@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/cielo/.npm/_logs/2019-04-12T13_24_09_534Z-debug.log
解决方法:
据说仍然还是版本更新不彻底。只好强制一点了。
ng update @angular/compiler-cli --force
ok了,我这样算是完整地跑了一个网页的例子了。
想哭。
总结
以上是小编为你收集整理的angular版本问题&compiler_cli_1.readConfiguration is not a function全部内容。
如果觉得小编网站内容还不错,欢迎将小编网站推荐给好友。
原文地址:https://blog.csdn.net/qq_38904077/article/details/89259218
: No JAAS configuration section named ''Client'' was found in specified JAAS configuration file:
zookeeper.ClientCnxn(line:957) : SASL configuration failed: javax.security.auth.login.LoginException: No JAAS configuration section named ''Client'' was found in specified JAAS configuration file: ''C:\Users\ADMINI~1\AppData\Local\Temp\jaas9138331021728969462.conf''. Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it.
java.net.SocketTimeoutException: callTimeout=60000, callDuration=60110: Call to master/192.168.7.202:16020 failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=2, waitTime=60009, rpcTimeout=60000 row
c# – ConfigurationSection ConfigurationManager.GetSection()始终返回null
我有一个控制台应用程序和一个DLL.
class Program { static void Main(string[] args) { StandardConfigSectionHandler section = StandardConfigSectionHandler.GetConfiguration(); string value = section.Value; } }
应用配置:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <sectionGroup name="ConfigSectionGroup"> <section name="ConfigSection" type="Controller.StandardConfigSectionHandler,Controller" /> </sectionGroup> </configSections> <ConfigSectionGroup> <ConfigSection> <test value="1" /> </ConfigSection> </ConfigSectionGroup> </configuration>
DLL中的section handler:
namespace Controller { public class StandardConfigSectionHandler : ConfigurationSection { private const string ConfigPath = "ConfigSectionGroup/ConfigSection/"; public static StandardConfigSectionHandler GetConfiguration() { object section = ConfigurationManager.GetSection(ConfigPath); return section as StandardWcfConfigSectionHandler; } [ConfigurationProperty("value")] public string Value { get { return (string)this["value"]; } set { this["value"] = value; } } } }
有什么值得我尝试的“ConfigPath”它将返回null,或者抛出一个错误,说“test”是一个无法识别的元素.我试过的价值:
> ConfigSectionGroup
> ConfigSectionGroup /
> ConfigSectionGroup / ConfigSection
> ConfigSectionGroup / ConfigSection /
> ConfigSectionGroup / ConfigSection / test
> ConfigSectionGroup / ConfigSection / test /
解决方法
>你总是在你的GetConfiguration方法中返回null,但是我将假设这只是在问题中,而不是在你的实际代码中.
>更重要的是,ConfigPath值的格式不正确.您有一个尾部斜杠ConfigSectionGroup / ConfigSection /,删除最后一个斜杠,它将能够找到该部分.
>最重要的是,您声明部分的配置系统将会将您的“值”存储在ConfigSection元素的属性中.喜欢这个
<ConfigSectionGroup> <ConfigSection value="foo" /> </ConfigSectionGroup>
所以,把它放在一起:
public class StandardConfigSectionHandler : ConfigurationSection { private const string ConfigPath = "ConfigSectionGroup/ConfigSection"; public static StandardConfigSectionHandler GetConfiguration() { return (StandardConfigSectionHandler)ConfigurationManager.GetSection(ConfigPath); } [ConfigurationProperty("value")] public string Value { get { return (string)this["value"]; } set { this["value"] = value; } } }
要了解有关如何配置配置部分的更多信息,请参阅这个出色的MSDN文档:How to: Create Custom Configuration Sections Using ConfigurationSection.它还包含有关如何将配置值存储在(像您的测试元素)的子元素中的信息.
c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException
但是组合根类中的这一行:
container.RegisterWebApiControllers(GlobalConfiguration.Configuration);
导致异常:
System.TypeInitializationException : The type initializer for 'MyProject.Api.Test.Integration.HttpClientFactory' threw an exception. ---- system.invalidOperationException : This method cannot be called during the application's pre-start initialization phase. Result StackTrace: at MyProject.Api.Test.Integration.HttpClientFactory.Create() at MyProject.Api.Test.Integration.Controllers.ProductControllerIntegrationTest.<GetProductBarcode_Should_Return_Status_BadRequest_When_Barcode_Is_Empty>d__0.MoveNext() in d:\Projects\My\MyProject.Api.Test.Integration\Controllers\ProductControllerIntegrationTest.cs:line 26 ----- Inner Stack Trace ----- at System.Web.Compilation.BuildManager.EnsuretopLevelFilesCompiled() at System.Web.Compilation.BuildManager.GetReferencedAssemblies() at System.Web.Http.WebHost.WebHostAssembliesResolver.System.Web.Http.dispatcher.IAssembliesResolver.GetAssemblies() at System.Web.Http.dispatcher.DefaultHttpControllerTypeResolver.GetControllerTypes(IAssembliesResolver assembliesResolver) at System.Web.Http.WebHost.WebHostHttpControllerTypeResolver.GetControllerTypes(IAssembliesResolver assembliesResolver) at SimpleInjector.SimpleInjectorWebApiExtensions.GetControllerTypesFromConfiguration(HttpConfiguration configuration) at SimpleInjector.SimpleInjectorWebApiExtensions.RegisterWebApiControllers(Container container,HttpConfiguration configuration) at MyProject.Api.ContainerConfig.RegisterTypes(Container container) in d:\Projects\My\MyProject.Api\App_Start\ContainerConfig.cs:line 128 at MyProject.Api.ContainerConfig.CreateWebApiContainer() in d:\Projects\My\MyProject.Api\App_Start\ContainerConfig.cs:line 63 at MyProject.Api.Test.Integration.HttpClientFactory..cctor() in d:\Projects\My\MyProject.Api.Test.Integration\HttpClientFactory.cs:line 17
评论后,一切正常,网络应用程序本身和测试.
所以问题是:
>例外的原因是什么?
>(这种方法真的需要吗?)
这是HttpClientFactory的代码(一个辅助类,用于创建具有适当头的HttpClient,例如api密钥或授权):
internal static class HttpClientFactory { private static readonly Container _container = ContainerConfig.CreateWebApiContainer(); public static HttpClient Create() { var client = new HttpClient { BaseAddress = GetUrl() }; //... return client; } }
解决方法
但是,System.Web.Compilation.BuildManager不能在ASP.NET管道的早期调用,也不能在ASP.NET的上下文之外调用.由于您正在进行测试,BuildManage将抛出您遇到的异常.
所以这里的解决方案(或’技巧’)将在单元测试时替换默认的IAssembliesResolver.我认为旋转变压器看起来像这样:
public class TestAssembliesResolver : IAssembliesResolver { public ICollection<Assembly> GetAssemblies() { return AppDomain.CurrentDomain.GetAssemblies(); } } [TestMethod] public void TestMethod1() { // Replace the original IAssembliesResolver. GlobalConfiguration.Configuration.Services.Replace(typeof(IAssembliesResolver),new TestAssembliesResolver()); var container = SimpleInjectorWebApiInitializer.BuildContainer(); container.Verify(); }
你不得不处理这个问题有点不幸,特别是因为Simple Injector的设计是可测试的.我们似乎忽略了这一点,将RegisterWebApiControllers扩展方法与Web API深深地集成在一起.我们必须退后一步,思考如何更轻松地验证单元测试中的Web API配置.
Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':classpath'.
前言
这个错误怎么看呢?
如果你对gradle 不是很了解的话,有一个建议,就是把异常背下来,当然是看这个:ArtifactResolveException哈。
而不是后面的详情。
正文
给我们详情是这个:
Could not resolve all files for configuration '':classpath''.
其实就是说文件缺少。
然后我们看旁边的。
这是一个错误栈,你最好需要点开每一个。
我打开了其中一个详细内容,告诉我们有一个包下载不下来。
接着你不要马上去弄什么代理,你应该尝试是否这个包已经不存在了,因为可能有些包的确失效了,接着你才应该考虑代理。
总结
以上是小编为你收集整理的Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration '':classpath''.全部内容。
如果觉得小编网站内容还不错,欢迎将小编网站推荐给好友。
今天的关于angular版本问题&compiler_cli_1.readConfiguration is not a function和angular各个版本区别的分享已经结束,谢谢您的关注,如果想了解更多关于: No JAAS configuration section named ''Client'' was found in specified JAAS configuration file:、c# – ConfigurationSection ConfigurationManager.GetSection()始终返回null、c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException、Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':classpath'.的相关知识,请在本站进行查询。
本文标签: