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

In BA plugin, error with type checking of get/release resource behavior actions #2234

Closed
Etienne13 opened this issue Mar 12, 2020 · 0 comments · Fixed by #2235
Closed

In BA plugin, error with type checking of get/release resource behavior actions #2234

Etienne13 opened this issue Mar 12, 2020 · 0 comments · Fixed by #2235
Assignees
Milestone

Comments

@Etienne13
Copy link
Contributor

Etienne13 commented Mar 12, 2020

Summary

When using a get/release resource behavior action (noted <! and >!), the plugin fails and produces the following error message:

type error for 'lock', 'subprogram classifier' expected, found 'requires data access'.

This is a recent regression.

Steps to Reproduce

  1. import the following model
  2. see the error message attached to the behavior actions (no error message should appear since the model is correct)
package issueGetReleaseResource
public
	
data d
end d;

subprogram spg
  features
	lock: requires data access d {Concurrency_Control_Protocol => Protected_Access;};
  annex behavior_specification {**
	STATES
		singleton: initial final state;
	TRANSITIONS
  		t: singleton -[]-> singleton
   		{
   			lock!<;
   			lock!>
  		};
**};
end spg;
	
end issueGetReleaseResource;

Environment

  • OSATE Version: 2.7.0
  • Operating System: Linux
@Etienne13 Etienne13 added this to the 2.8.0 milestone Mar 12, 2020
Etienne13 pushed a commit that referenced this issue Mar 12, 2020
@Etienne13 Etienne13 self-assigned this Mar 12, 2020
@Etienne13 Etienne13 modified the milestones: 2.8.0, 2.7.1 Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant