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

Installation Error on GToolkit #267

Open
seandenigris opened this issue Jan 12, 2023 · 5 comments
Open

Installation Error on GToolkit #267

seandenigris opened this issue Jan 12, 2023 · 5 comments
Labels

Comments

@seandenigris
Copy link
Collaborator

The underlying Pharo build is Pharo-10.0.0+build.521.sha.14f541319d443f4261f84f4fa19fbb34460a5edb (64 Bit)

Since I see Pharo 10 passing in the matrix, I wonder if this is something GT-specific...

First I get a weird error from Calypso about ZnBufferedReadStream>>fuelNextWordsInto: being moved to the FuelPlatformExtensions package. I'm not sure where that package even comes from since I don't see it in either the Pharo or Fuel repos.

Next, I get the following error:
Screenshot 2023-01-12 at 6 32 05 AM

At the top of the stack, you can see my implementation, which seems to have corrected the problem.

@theseion
Copy link
Owner

FuelPlatform is obviously broken in this instance. The implementation for Pharo 10 is

fileNamed: aFilename readStreamDo: aBlock
	^ ((Smalltalk at: #File) named: aFilename) readStreamDo: [ :stream |
		stream binary.
		aBlock value: stream ]

How are you loading Fuel? Which version? Which version of Fuel is in the image (if any) before you load Fuel?

@seandenigris
Copy link
Collaborator Author

I’m loading 5.1.0 on top of whatever version comes with GT. I’ll update with the script and GT base version when I get to a computer

@theseion
Copy link
Owner

I just realised that the methods in your stack trace aren't actually from version 5 but from version 4. Clearly, version 5 wasn't properly loaded.

@seandenigris
Copy link
Collaborator Author

As I investigated, I noticed something similar. Trying to figure out why…

@stale
Copy link

stale bot commented Mar 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants