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

DependencyAnalyser raises DNU #17866

Open
Ducasse opened this issue Feb 22, 2025 · 6 comments
Open

DependencyAnalyser raises DNU #17866

Ducasse opened this issue Feb 22, 2025 · 6 comments

Comments

@Ducasse
Copy link
Member

Ducasse commented Feb 22, 2025

The solution is here but I could make the code load in correct order so I reverted it.
#17858

@Ducasse Ducasse added this to the 13.0.0 milestone Feb 22, 2025
@Ducasse
Copy link
Member Author

Ducasse commented Feb 22, 2025

  • Clicking on the refresh
  • Double clicking on a method

raises an error.

@Ducasse
Copy link
Member Author

Ducasse commented Feb 22, 2025

May be we should move the dependency analyzer to new tools
this way we will get it loaded after StPresenter and without problem.

In PR I moved the loading after newTools: so I do not get why this is not working.

@Ducasse
Copy link
Member Author

Ducasse commented Feb 22, 2025

From

	self
			load: 'DependencyAnalyzer'
			group: 'Tool-DependencyAnalyser-UI-Tab'
			spec: spec.
		self specCode: spec.
		self roassal: spec.
		self microdown: spec.
		self newTools: spec.
		self drTests: spec.

and baselineOfQA

	spec
			baseline: 'QualityAssistant'
			with: [ spec repository: repository ].
		spec
			baseline: 'DependencyAnalyzer'
			with: [ spec repository: repository ].

		spec
			package: 'General-Rules'

to

		self specCode: spec.
		self roassal: spec.
		self microdown: spec.
		self newTools: spec.
		
		spec
			baseline: 'DependencyAnalyzer'
			with: [ spec repository: repository ].
		self
			load: 'DependencyAnalyzer'
			group: 'Tool-DependencyAnalyser-UI-Tab'
			spec: spec.
		
		self drTests: spec.

@Ducasse Ducasse closed this as completed Feb 22, 2025
@Ducasse Ducasse reopened this Feb 22, 2025
@Ducasse
Copy link
Member Author

Ducasse commented Feb 22, 2025

Since I reverted the PR I lost all the changes before :(
So the bug are still there. I do not know what to do

@Ducasse
Copy link
Member Author

Ducasse commented Feb 23, 2025

I tried another time and failed again so I reverted the other PR because my changes were not there.
So I stop.

@Ducasse
Copy link
Member Author

Ducasse commented Feb 23, 2025

Too frustrating. 2 hours for integrating something that was done in 3 min. The ratio is not good.
The architectural mess is killing us.
#17869

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

No branches or pull requests

1 participant