Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'System.NullReferenceException' occurred in CodeOwls.PowerShell.Provider.dll #1

Open
cdhunt opened this issue May 12, 2014 · 2 comments

Comments

@cdhunt
Copy link

cdhunt commented May 12, 2014

I encounter the NullRef exception when attempting tab-completion. Ultimately, the tab-completion works after Continuing through an exception for each possible node name.

   at NewRelicAPIPoshProvider.Paths.ApplicationsPathNode.GetNodeChildren(IProviderContext providerContext) in c:\Users\chunt\Documents\GitHub\NewRelicApiPoshProvider\NewRelicAPIPoshProvider\Paths\Application.cs:line 42
   at CodeOwls.PowerShell.Provider.PathNodes.PathNodeBase.<Resolve>d__0.MoveNext() in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Paths\PathNodeBase.cs:line 38
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source)
   at CodeOwls.PowerShell.Paths.Processors.PathResolverBase.ResolvePath(IProviderContext providerContext, String path) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Paths\Processors\PathResolverBase.cs:line 53
   at CodeOwls.PowerShell.Provider.Provider.ResolvePath(String path) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 83
   at CodeOwls.PowerShell.Provider.Provider.GetNodeFactoryFromPath(String path, Boolean resolveFinalFilter) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 1163
   at CodeOwls.PowerShell.Provider.Provider.GetNodeFactoryFromPath(String path) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 1157
   at CodeOwls.PowerShell.Provider.Provider.DoItemExists(String path) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 776
   at CodeOwls.PowerShell.Provider.Provider.<>c__DisplayClass67.<ItemExists>b__66() in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 765
   at CodeOwls.PowerShell.Provider.Provider.ExecuteAndLog[T](Func`1 action, String methodName, String[] args) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 1440
   at CodeOwls.PowerShell.Provider.Provider.ItemExists(String path) in c:\Users\beefarino\Documents\Project\p2f\src\CodeOwls.PowerShell\CodeOwls.PowerShell.Provider\Provider.cs:line 766
   at System.Management.Automation.Provider.ItemCmdletProvider.ItemExists(String path, CmdletProviderContext context)
@beefarino
Copy link
Owner

now that your provider is complete, is this still an issue?

@cdhunt
Copy link
Author

cdhunt commented May 16, 2014

Yes. It sill occurs and I'm pretty sure it has something to do with objects being returned. It doesn't happen with the first level of containers which is just a string, but when I start returning deserialized JSON, it occurs consistently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants