Release with missing packages shows null reference exception(s)

Integration
1

Our CI system created a release that was missing some packages. When clicking on the release, the packages section shows "Object reference not set to an instance of an object.

Octopus Version: v2018.3.7

Unhandled error on request: https://DOMAIN/api/packages/notes?packageIds=feeds-builtin%3APACKAGE%3AVERSION%2Cfeeds-builtin%3APACKAGE%3AVERSION e5e6ca1663f94377b3361029a0ecbbb4 by USERNAME : One or more errors occurred. System.AggregateException: One or more errors occurred. —> System.NullReferenceException: Object reference not set to an instance of an object.
at Octopus.Core.BuiltInFeed.BuiltInPackageRepository.GetNotes(String packageId, IVersion version, CancellationToken cancellationToken)
at Octopus.Server.Web.Api.Services.PackageNotesRetriever.<>c__DisplayClass5_0.b__0()
at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue()
at Octopus.Server.Caching.OctopusCache.GetOrAdd[TItem](String key, Func1 valueFactory, DateTimeOffset absoluteExpiry) at Octopus.Server.Web.Api.Services.PackageNotesRetriever.GetReleaseNotes(String feedId, String packageId, String version) at Octopus.Server.Web.Api.Actions.PackageListNotesAction.<ExecuteRegistered>b__3_2(String[] idSplit) at System.Linq.Parallel.SelectQueryOperator2.SelectQueryOperatorEnumerator1.MoveNext(TOutput& currentElement, TKey& currentKey) at System.Linq.Parallel.StopAndGoSpoolingTask2.SpoolingWork()
at System.Linq.Parallel.SpoolingTaskBase.Work()
at System.Linq.Parallel.QueryTask.BaseWork(Object unused)
at System.Threading.Tasks.Task.Execute()
— End of inner exception stack trace —
—> (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.
at Octopus.Core.BuiltInFeed.BuiltInPackageRepository.GetNotes(String packageId, IVersion version, CancellationToken cancellationToken)
at Octopus.Server.Web.Api.Services.PackageNotesRetriever.<>c__DisplayClass5_0.b__0()
at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue()
at Octopus.Server.Caching.OctopusCache.GetOrAdd[TItem](String key, Func1 valueFactory, DateTimeOffset absoluteExpiry) at Octopus.Server.Web.Api.Services.PackageNotesRetriever.GetReleaseNotes(String feedId, String packageId, String version) at Octopus.Server.Web.Api.Actions.PackageListNotesAction.<ExecuteRegistered>b__3_2(String[] idSplit) at System.Linq.Parallel.SelectQueryOperator2.SelectQueryOperatorEnumerator1.MoveNext(TOutput& currentElement, TKey& currentKey) at System.Linq.Parallel.StopAndGoSpoolingTask2.SpoolingWork()
at System.Linq.Parallel.SpoolingTaskBase.Work()
at System.Linq.Parallel.QueryTask.BaseWork(Object unused)
at System.Threading.Tasks.Task.Execute()<—

—> (Inner Exception #1) System.NullReferenceException: Object reference not set to an instance of an object.
at Octopus.Core.BuiltInFeed.BuiltInPackageRepository.GetNotes(String packageId, IVersion version, CancellationToken cancellationToken)
at Octopus.Server.Web.Api.Services.PackageNotesRetriever.<>c__DisplayClass5_0.b__0()
at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue()
at Octopus.Server.Caching.OctopusCache.GetOrAdd[TItem](String key, Func1 valueFactory, DateTimeOffset absoluteExpiry) at Octopus.Server.Web.Api.Services.PackageNotesRetriever.GetReleaseNotes(String feedId, String packageId, String version) at Octopus.Server.Web.Api.Actions.PackageListNotesAction.<ExecuteRegistered>b__3_2(String[] idSplit) at System.Linq.Parallel.SelectQueryOperator2.SelectQueryOperatorEnumerator1.MoveNext(TOutput& currentElement, TKey& currentKey) at System.Linq.Parallel.StopAndGoSpoolingTask2.SpoolingWork()
at System.Linq.Parallel.SpoolingTaskBase.Work()
at System.Linq.Parallel.QueryTask.BaseWork(Object unused)
at System.Threading.Tasks.Task.Execute()<—

2

Hi Michael, thanks for reaching out.

We have an open issue for this bug at https://github.com/OctopusDeploy/Issues/issues/4354.

The previous reports of this error didn’t block the release, but only displayed the errors on the page. Is it the same for you, or is this a blocking issue?

Regards
Matthew Casperson

3

That is correct. We are not blocked. We just had to dig around to figure out our package was missing.

Thanks,

Michael McDaniel

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.