Can't install most recent version web3.js - solidity

I am getting 20 errors every time I install web3.js. I tried using earlier versions of the library but am still getting errors. I found this thread and was able to download version 0.19.0 but there is no documentation for 0.19.0 on the web so it's not really usable. Does anyone have any ideas?

Related

Typo3 6.2 Upgrade Version Matrix Issue

I am trying to upgrade from Typo3 6.2 to a later version (to be determined). When I run the Core Update in the install tool the 'Fetched list of released versions' works, however, it is then followed by a 'General error'. In the log, this is the error:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1380898792: No version matrix found in registry, call updateVersionMatrix() first. | TYPO3\CMS\Install\Service\Exception\CoreVersionServiceException thrown in file /home/usr/public_html/typo3/sysext/install/Classes/Service/CoreVersionService.php in line 271. Requested URL: https://domain.dev/typo3/sysext/install/Start/Install.php?install[action]=importantActions&install[context]=backend&install[controller]=tool&install%5Bcontroller%5D=ajax&install%5Baction%5D=coreUpdateIsUpdateAvailable&_=1608549770287
I have looked around for ages and can't find a fix that works. I will be very grateful for any help, please.
I don't think that you can update such an old Version by the install-tool update mechanism any more. since that version a lot has changed.
newer versions of 6.2 are only available as paid service (ELTS) from the TYPO3 GmbH.
And I think the server structure also changed meanwhile so that old ULRs might fail.
your way of update should be a manual update to (any outdated version of) 7 LTS, then the same for 8 LTS until you come to 9 LTS and 10 LTS
on each version do the upgrade wizards and fresh up the extensions if possible (including the upgrade wizards of the extensions).
individual extensions need their own updates.
use the deprecation log on each version to identify possible failures for the next TYPO3 version.
somewhere between you might change the installation to composer installation, which will result in a cleaner update way (if you are familiar with composer). for the future it will be very helpful to understand composer.

Running Big Commerce's Stencil CLI on Windows 10

I can not get Stencil to run for the life of me. I am using NVM to mange my version of node - I tried both 10.16 and 10.19.
I have reinstalled Stencil 2 or 3 times now and ever time I get the same error:
WTF? Has anyone got this to successfully run on a Windows 10 machine? We originally had node 13.9 installed but I was getting the same errors so I figured it was because it was outside their "approved" versions. I spoke to their customer support and they told me that it should work with newer version but that they can't give it proper approval until it's goes through some process.
So I can't get this to work on any version......
Any help would be very much appreciated!
Before installing nvm was a previous version of node installed? You'll need to uninstall nvm and node before installing nvm which can cause this. You can confirm which version of node is installed using node --version

Key Error: Session ID with latest version of GeckoDriver, FF, and Selenium

I recently upgraded the various pieces of our selenium suite, and when I updated the GeckoDriver to the latest version (0.16.1) I started encountering the following error during set up:
KeyError: 'sessionId'
I know this issue has been brought up here before, but I've checked the other threads and made sure I've followed the correct process. It seems the universal suggestion is to make sure everything is updated correctly.
I'm using robot framework with a modified version of their Selenium2Library to write and run the tests.
robot version is 3.0.2
selenium version is 3.4.3
FF version is 53.0.3
I have also tried altering my proxy settings following the guidance in the thread here(I am on a mac OS X El Capitan):
Why doesn't Selenium's response have a sessionId?
All of this is to no avail. The only thing I can do to get my tests back to a semi-functional state on firefox is to downgrade the geckodriver. I'd like to avoid that if possible, since this newest version has some bug fixes helpful to me.
Any guidance on what I should try next?
Upgrade version of selenium2Library. Current version is 1.8.0
Selenium2Library
Run Command
pip install robotframework-selenium2library --upgrade in cmd
Problem will be solved.
I've resolved this using the nuclear option -- I did a full uninstall of the three main dependencies in the original question and reinstalled through pip.
Latest versions seem to be in good shape. For some reason this resolved the underlying keyError. It does not appear that upgrading the Selenium2Library had any effect.

Newslist stopped working after upgrade to 4.2 version

After upgrade to 4.2 version ImpressPages - NewsList Module has stopped working:
Fatal error: Call to undefined method Ip\Internal\Text\Html2Text::get_text() in /mysite.com/Plugin/NewsList/HelperPageContents.php on line 127.
I know, NewsList plugin has upgrade to 1.05v but
after upgraded to this version, there is still the same problem.
Should look like the upgrade procedure?
It is not possible. There is no such code in recent version. But I've found other bugs that may occur if you have invalid HTML or other content related issues. They all have been fixed and released under 1.06 version. Please update and let me know how it goes.
Cheers.

ppl011 fails to install on 10.9.2

I'm trying to install ppl011 using brew and it fails.
The story began when I did rvm requirements. It failed during the gcc46 step. When I tried to install gcc46 itself, it failed while installing ppl011. Eventually, I was able to generate these: https://gist.github.com/ege02/9490126
I have been googling this for the past 24 hours. I'm also new to OSX/Linux so I pretty much have no idea what I'm doing. I'd appreciate some guidance!
I'll add this in case it helps someone. It turned out that the issue was caused by an incompatibility with the (as of this writing) recently released Command Line Tools 5.1. Downgrading to CLT 5.0.1 allowed me to work around the issue. More details here.