Typo in error message

[data-henrik]

pipeline/pkg/reconciler/taskrun/resources/taskresourceresolution.go

Lines 81 to 94 in 1f5980f

	return nil, errors.New("Both ResourseRef and ResourceSpec are defined. Expected only one")
	}
	if r.ResourceRef != nil && r.ResourceRef.Name != "" {
	return getter(r.ResourceRef.Name)
	}
	if r.ResourceSpec != nil {
	return &resourcev1alpha1.PipelineResource{
	ObjectMeta: metav1.ObjectMeta{
	Name: r.Name,
	},
	Spec: *r.ResourceSpec,
	}, nil
	}
	return nil, errors.New("Neither ResourseRef nor ResourceSpec is defined")

I ran into this error message:

Neither ResourseRef nor ResourceSpec is defined

It should be "ResourceRef"

[codeleongy]

Hi @data-henrik @vdemeester , I am interested in fixing this bug, could you assign to me: )

[vdemeester]

@codeleongy if you comment /assign it should assign it to you automatically 😉

/assign @codeleongy

[Dev-Ashank]

/assign

[Dev-Ashank]

/unassign

[Aathirajan]

/assign

[Aathirajan]

/unassign

[Aathirajan]

/assign

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[data-henrik]

/lifecycle frozen "it should be fixed for quality reasons"

[vdemeester]

/lifecycle frozen

[AlanGreene]

Looks like this was fixed in #6184 which was first released in v0.46.0
/close

[tekton-robot]

@AlanGreene: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

Looks like this was fixed in #6184 which was first release in v0.46.0
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aaron-prindle]

+1 @AlanGreene, this was fixed with #6184
/close

[tekton-robot]

@aaron-prindle: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

+1 @AlanGreene, this was fixed with #6184
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dibyom]

/close

[tekton-robot]

@dibyom: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.