Comments (14)
Just to confirm we'd want to remove stuff like travis.py, .travis.yaml, those contain the GCP code (also check if anything calls them).
I suppose the relevant Dockerfile code too? (https://github.com/Farama-Foundation/stable-retro/blob/master/docker/linux/Dockerfile)
Any other obvious things I am missing?
I'll dig more but at least can point at the above items as necessary to remove.
from stable-retro.
Dockerfile sounds useful to keep IMO, as long as it’s not too hard to maintain I don’t see a problem having it
from stable-retro.
Yea I think that should be good
from stable-retro.
Yes, sorry, I was meaning there is GCP stuff in the dockerfile, I wasn't meaning to outright remove it.
from stable-retro.
Do we have a place we are putting the original travis related code? It seems like just flat out tossing it would maybe be a bad idea, we should make sure if we are pulling travis code out, it's going into dockerfiles (if docker is the path, or whatever CI ).
I.E. I was about to delete:
And realized if people didn't know that existed in the future we might have other issues and folks will have to do deep diving to find these things
from stable-retro.
Good point, we can always revert the code to the old version to find these changes so I won't worry about it
from stable-retro.
Is this done now?
from stable-retro.
Do we want to remove Travis files in the cores subdirectory? I haven't done that yet, but can pull them out and make a PR. (I dont know how many there are it may just be GBA but I can do a quick search)
from stable-retro.
There seemed to be a bit of overlap, I think someone else removed some Travis stuff, but inside the dockerfile there are still references to Google cloud stuff.
from stable-retro.
Do we want to remove Travis files in the cores subdirectory? I haven't done that yet, but can pull them out and make a PR. (I dont know how many there are it may just be GBA but I can do a quick search)
It seems to me that the original project, copy and pasted the emulators from projects which includes travis for testing.
As this was part of the original emulators, I'm in favor of not modifying any of the emulators (except for updating the whole project to a new version if possible)
There seemed to be a bit of overlap, I think someone else removed some Travis stuff, but inside the dockerfile there are still references to Google cloud stuff.
Which file are you referencing?
from stable-retro.
Yea I was actually wondering about whether we really wanted to modify the original projects code, I assume not tweaking it "should" allow an update easier if we decide we need to. I'm ok with that.
Example files:
https://github.com/Farama-Foundation/stable-retro/blob/master/docker/linux/Dockerfile#L20
This has
pip install google-auth google-cloud-storage pytest requests && \
Which we aren't using google cloud storage, nor google auth anymore.
I assume the same holds true more or less from the other dockerfiles in the docker folder.
Just to add a final note on the docker files, I know the one I added for windows works fine, but I'm actually not sure if the others work well/correctly/at all.
from stable-retro.
@onaclov2000 Could you try removing as much of those install as possible then we can close this issue
from stable-retro.
Pull Request submitted.
from stable-retro.
This can be closed.
from stable-retro.
Related Issues (19)
- Python 3.10 Support HOT 11
- Filtered Actions Documentation HOT 3
- support double dragon Neo-Geo(MAME Emulator) ? HOT 17
- OpenAI References
- CI not working HOT 2
- Documentation Cleanup HOT 1
- Checklist for maturity HOT 6
- UI Releases HOT 2
- Error when installing with git via pip HOT 2
- Build on windows HOT 3
- Segmentation fault when compiling integration tool HOT 3
- New version issue with latest git commit HOT 3
- error: metadata-generation-failed HOT 8
- update docker windows builder.
- Error: Could not build wheel for stable-retro HOT 2
- Integration UI Error HOT 4
- Apple silicon build fails
- Cannot build from source to use integration UI HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stable-retro.