For example I need to know when this commit, that resolved this issue, was released to be able to support newer and older Chrome versions.
Chromium's current version is specified in this file: chrome/VERSION So you will have to look at that file, to find out in which version that commit is present. For example, the link you have posted points to commit id: 277a0c8 which can be seen in that page and if you click that commit id which points to: https://chromium.googlesource.com/chromium/src/+/277a0c817996a9ea0617a410d356d57e1cf8d548
So in your case if you look at this file: https://chromium.googlesource.com/chromium/src/+/277a0c817996a9ea0617a410d356d57e1cf8d548/chrome/VERSION, that commit was merged in Chromium version 81.0.4035.0
Hope that helps
Another way is to use the Chromium Dash service:
https://chromiumdash.appspot.com/commits?commit=277a0c817996a9ea0617a410d356d57e1cf8d548&platform=Linux
Related
I couldn't figure out a nice way to determine a suitable revision number to use with Puppeteer Sharp.
What I did was use the version lookup feature on the "OmahaProxy - Google Chrome" site. I looked-up the version of Chrome I'm running on my computer. [That seems like a reasonable starting point.] I assumed (guessed) that the "Branch Base Position" shown in the version info was a revision number.
I then opened the Chromium continuous builds archive and looked for a build for the revision around the revision number I found from the "OmahaProxy" site.
Is there a better way to find or pick a suitable revision number?
Puppeteer is always bundled with a specific revision of a specific version. I usually check the release information on Github where the expected Chromium version and revision is specified. For example:
v1.17.0
Big Changes
Chromium 76.0.3803.0 (r662092)
Then to download the right one,
Go to Chromium browser snapshots
Choose the directory of your platform (e.g., Linux_x64)
Copy the revision number into the "Filter:" field without the "r" (e.g., 662092)
Download the .zip file you need.
Additional info
The URL template below can be just plugged in with the right information:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=<platform>/<revision>/
For example:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/662092/
The most common issue on Linux is missing dependencies, and the Puppeteer "Troubleshooting" document specifies all the Linux dependencies. (See apt instructions for Ubuntu.)
curl needs -L when downloading on the console. See Stackoverflow thread.
When one is using puppeteer-core,
you will then need to call puppeteer.connect(\[options\]) or
puppeteer.launch(\[options\]) with an explicit executablePath
option.
(from puppeteer vs puppeteer-core)
Puppeteer requires number which correspond Chromium browser build snapshot number. You can get the latest snapshot number here:
https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Win_x64%2FLAST_CHANGE?generation=1528272852044880&alt=media
or you can view all available snapshots here:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/
Reportportal's logger-java-logback-4.0.0.BETA-1 is referring to client-java-4.0.0.BETA-1 but this jar has been removed from artifactory. Can the owners please put it back.
https://bintray.com/epam/reportportal/client-java
4.0.0 is not working for me for which I have posted another question.
If I can atl;east get the logback BETA jar, I can get by for sometime
As soon as RELEASE versions are pushed to bintray, public BETAs are being removed to avoid reaching Bintray storage size limits. Please, use 4.0.x
When doing "Sync with deployed on ..." in phpstorm, the diff shows as if all local js files were updated recently and thus offers to upload them even they were not changed or most recent changes are on the server. Anyone had this weird issue or knows how to fix it?
The GUI allows you to switch to "Compare by: Content". Note that this will be more bandwidth-intensive than comparing by modification date.
See e.g. this for a screenshot: https://www.jetbrains.com/phpstorm/help/comparing-deployed-files-and-folders-with-their-local-versions.html
I wonder if it is possible in TortoisHG, like in TortoiseSVN, to check if a commit message includes an issue id?
In TortoiseSVN you could set the bugtraq properties on the repo to make a dialog box pop up and warn if an id was not included, and I am looking for a way to do the same thing (still need it to be possible to check in, just show a warning that id is not included and be able to abort the commit if you want to).
Thanks in advance
Jonas H.
As far as I know, nothing like that is possible directly in TortoiseHG.
But TortoiseHG is only a GUI for Mercurial, and in Mercurial, you can do stuff like that with hooks.
See chapter 10 in the HG book for a general desription of what hooks are and how they work:
Handling repository events with hooks
There is even a specific example in this chapter that rolls back a commit if it doesn't contain a bug id.
This dialog in TortoiseHg 2.4's settings looks like what you want:
I only know about the setting issue.linkmandatory = True which forces entry of an issue reference specified in issue.regex and issue.link on every commit.
I've just installed latest 1.4.3 version of Mercurial and see new status messages for unknown/modified files.
Previous versions showed this for modified files:
M README.txt
This new version shows some gibberish like:
←[0;32;1m file.txt←[0m
What is this and how to interpret it?
Also, is it possible to revert to the old style notation?
SOLUTION:
If you happened to enable the 'color' plugin on Windows you'd get above behavior. After I commented the 'color' plugin, everything went back to normal.
Looks like Ansi control codes, ie. codes to change color and other things on terminal.
These codes doesn't work on XP terminal (worked on Dos terminals with ANSI.SYS in config).
Look if there is a setting somewhere to disable colored output.