Comments (1)
joshwlewis
commented on June 15, 2024
The way I understand it the current approach to tracking GOOGLE_CHROME_CHANNEL fails to guarantee repeatability in deployments and violates the 12 Factor App approach.
Yes, I tend to agree here. Unfortunately, Google only provides packages for their 3 release channels. They don't provide a way to download pre-built binaries of specific versions, which would be ideal to solve this problem. It is possible to download and build binaries for specific versions, but it's very resource intensive. So, at least for right now, we can't support version pinning.
Chromium does provide some version pinned packages which might make more sense to target repeatability. However, this buildpack targets Chrome, so maybe that's an idea for another buildpack.
On a whim I decided to upgrade our dated stack
Cedar-14toHeroku-16and everything seemed to work again. I'm assuming a new version of chrome stopped working onCedar-14.
I'm glad to hear it's working for you again. It's a good call to upgrade your stack anyway, Cedar-14 won't be around too much longer.
from heroku-buildpack-google-chrome.
Related Issues (20)
- --host-resolver-rules command line flag working locally but fails on heroku HOT 1
- google-chrome-beta_current_amd64.deb' is not a Debian format archive HOT 23
- --host-resolver-rules crashing application now
- Please update HOT 4
- javascript error
- Chrome crashes when jemalloc build pack is used on Heroku HOT 1
- Not Optimized for Some Websites
- Help my google chrome is old version HOT 1
- How to specify static version ? HOT 11
- Example Ruby in README code is out of date
- Not able to run angular unit test case with chrome browser
- As Heroku being dead for testing purposes. What is the closest alternative for this buildpack on Render?
- ValueError: There is no such driver by url https://chromedriver.storage.googleapis.com/115.0.5790/chromedriver_linux64.zip HOT 3
- Chrome version 116; Chrome Driver expecting version 114 HOT 14
- Security risks of running with `--no-sandbox`
- The chromedriver version (117.0.5938.62) detected in PATH at /app/.chromedriver/bin/chromedriver might not be compatible with the detected chrome version (116.0.5845.187); currently, chromedriver 116.0.5845.96 is recommended for chrome 116.*, so it is advised to delete the driver in PATH HOT 1
- Register Selinium Webdriver HOT 1
- DevToolsActivePort file doesn't exist ( Issue coming in Heroku)
- This version of ChromeDriver only supports Chrome version 121
- executable shim stopped working
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 heroku-buildpack-google-chrome.