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

package compatibility fallout from recent changes #121

Open
samth opened this issue Nov 11, 2020 · 10 comments
Open

package compatibility fallout from recent changes #121

samth opened this issue Nov 11, 2020 · 10 comments
Assignees

Comments

@samth
Copy link
Member

samth commented Nov 11, 2020

The following packages fail to build due to test-engine changes:

  • csc104 (needs builder from test-engine/racket-tests)
  • profj (needs test-engine/test-display.scm)
  • java-lexer (depends on profj)
@samth
Copy link
Member Author

samth commented Nov 25, 2020

ping @mikesperber

@mikesperber
Copy link
Member

@samth ProfJ was broken before, for other reasons, and we decided to leave it.

I've sent fixes to CSC104.

@samth
Copy link
Member Author

samth commented Nov 26, 2020

Are these files/functions hard to support in the new regime? All of these packages compiled successfully before, and I'd prefer not to break things if we can just keep them alive.

@mfelleisen
Copy link
Contributor

@samth Mike sent a patch to our friends in Toronto.

@mikesperber Did you ever hear back whether the patch was okay?

@gfbee
Copy link
Contributor

gfbee commented Nov 26, 2020

I haven't had a chance to try it but am fine with csc104 breaking on snapshots until I get a chance over the holidays to update it (there's also a rewrite of the package in progress anyway).

@samth
Copy link
Member Author

samth commented Nov 27, 2020

I appreciate making an effort to move people to new APIs, but unless these old APIs are very hard to support, the fact that they were used somewhere suggests that they might be used elsewhere too, and we should avoid breaking them.

@mfelleisen
Copy link
Contributor

@samth Mike, Robby, Matthew and I discussed this change extensively and we brought it up during a Tuesday meeting. We all thought it meant progress.

@samth
Copy link
Member Author

samth commented Nov 27, 2020

Obviously the change overall is good. But we should figure out if we can address the particular compatibility issues that we've discovered here without doing too much extra work.

@mikesperber
Copy link
Member

I appreciate making an effort to move people to new APIs, but unless these old APIs are very hard to support, the fact that they were used somewhere suggests that they might be used elsewhere too, and we should avoid breaking them.

The APIs that affected ProfessorJ and CSC104 would have been impossible to support while still making the improvements the test-engine rewrite made. I did check.

Note that there are many other packages that also use test-engine, which should not be affected. (And I did check all of that at @mfelleisen's behest before the patch landed.)

@samth
Copy link
Member Author

samth commented Dec 1, 2020

I've made a PR for profj that makes it compile again.

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

4 participants