I'm trying to make my first contribution to DefinitelyType repo
but vscode shows me this eslint error in every .ts files in this repo:
Parsing error: Cannot read file: [folderPathInMyLocalMachine]/definitelytyped/tsconfig.json
There are a few stackoverflow posts advising to change "project" path in "parserOptions", eslintrc.json in root repo, but I feel like no setups should be changed in this repository because it has been structured and used by many developers.
Surely, I've tried to restart vscode a few times, please let me know if you have any advices!
Solved by turning off VScode eslint plugin 😅 by glancing this post:
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/61764
Related
Before we start, I do know custom hooks are not executed by Github pages, I'm suffering this issue locally(bundle exec jekyll serve).
I manage my own Github pages, and I found a great post about Jekyll hook that I wanted to try it out by myself.
I followed the instruction, first created _plugins folder at the root of my repo,
and created my own *.rb file.
But my hook is not executed at all!
I even downloaded the source file of the example blog, but I couldn't notice any difference that might cause this issue.
FYI, local serve of the example blog worked well with all the hooks executed.
If you can help me on this issue, it would be very much appreciated. Here is the WiP commit of my blog.
Thank you.
I am working on a React app with a MySQLdb and am trying to deploy with Heroku. I have followed a guide closely and am using JAWS DB hook to connect my db to Heroku. I am running into this error when I run the "heroku open" command after pushing to heroku:
"Error: Cannot find module '/app/node_modules/mime/mime.js'. Please verify that the package.json has a valid "main" entry"
My package.json has mime.js installed as a devDependency. I have set the "main" line in my package.json to "index.js" as well.
Repo: https://github.com/AndrewCodesDontYaKnow/ReactCalc
Anyone have any experience with this type of issue? Thanks much.
I just had the same problem with a different module ("telebot" in my case)
I didn't figure out how to fix the issue (if anyone else finds this, I'd also like to know how to fix it), but I got it to work with a work around...
I copied the module source, and put it into my repo, and just used it as a local module...
(in my case I had by my .gitignore file ignore any "lib" folder, it gave me a hard time until i realized the lib folder from the telebot folder is just not getting uploaded to GitHub, and as such not getting to heroku, but after commenting it out, and getting it to upload, the local module worked as intended)
also, I don't think this is an actual answer, but I don't have the rep to comment, so I hope this helps
On my hosting with my MW (1.28.2) and SMW (2.5.3) a have:
/home/www/mediawiki-1.28.2
/home/www/w -> mediawiki-1.28.2 (link to mediawiki-1.28.2)
/home/www/.htaccess
Following https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line I do:
Downloading mediawiki-1.29.0.tar.gz to /home/www/mediawiki-1.29.0.tar.gz
Unpack mediawiki-1.29.0.tar.gz to /home/www/mediawiki-1.29.0
Copy from /home/www/w to /home/www/mediawiki-1.29.0 files and folders: LocalSettings.php, images, some extensions
Then from command-line I do:
Change link /home/www/w from /home/www/mediawiki-1.28.2 to /home/www/mediawiki-1.29.0
cd /home/www/w
/opt/php/7.1/bin/php ~/bin/composer.phar require mediawiki/semantic-media-wiki "~2.5" --update-no-dev
/opt/php/7.1/bin/php ~/bin/composer.phar update
/opt/php/7.1/bin/php maintenance/update.php
And maintenance/update.php does nothing! At all!
And my site down to HTTP 500.
What is wrong and how can I debug maintenance/update.php ?
Okay, there is how I try to solve it:
I removed (temporary) .htaccess
I switched on error reporting in LocalSettings.php
When I went to my website/w/index.php I found that there were two(!) missing extensions: PdfHandler and SpamBlacklist. After removing them from LocalSettings.php all works fine.
That is the question: where were PdfHandler and SpamBlacklist gone???
https://www.mediawiki.org/wiki/Manual:How_to_debug
My guess (just a guess) is that there might be a problem with PHP7 as your default, since some MediaWiki extensions don't support it yet.
I think there was some problem with your dependencies try running "composer update" in the terminal and According to me it actually runs Localsettings.php file and aborts if it identifies any errors in the file so you have to check if there is any mistake in it and finally run php maintanence/update.php in mediawiki directory
I'm having difficulty cloning a repository in Mercurial.
The repository is stored at Kiln on demand, though I'm not sure that makes much difference.
I have a new install of Tortoise HG, which has of course installed the hg command line onto my machine.
When I attempt to clone the repository, I immediately receive the error:
abort: The system cannot find the path specified: 'F:\backups\_hgcookies'
Code: 255
I don't know where it's getting this path from - there is an 'F' drive on my machine that is completely empty aside from hidden system volume files.
The Kiln Tortoise install contains a couple of plugins bundled with it, including kilnauth, which I assume is using a cookie to store authentication information.
I've looked in the mercurial.ini file, however it contains no mention of this folder or hgcookies - that I can see.
I'm wondering if there's a permissions issue somewhere - I'm in the administrators group on the machine, but am on a company network with quite a bit of lockdown which has caused problems before.
I've not found any similar problems through googling, though it's been difficult to get relevent results with the word 'backup' and 'hgcookies' in my terms!
Any help, greatly appreciated.
Seems this was an issue with the KilnAuth extension. I'm not sure why it decided to store the cookies on the F: drive, but I manually created a 'backups' folder on that drive and that allowed it to store the cookie there with no problems.
I had some help from the FogCreek guys diagnosing this - I have to say I've never experienced such awesome customer service, really. Hats off to those guys!
I had just barely gotten the Mercurial-Reviewboard plugin working with TortoiseHG 2.4.2 when I upgraded to TortoiseHG 2.4.3 and it stopped working.
It's now throwing the following error when I click the "Post Review" button.
"postreview plugin version 4.1.0"
"'module' object has no attribute 'findoutgoing'"
I've tried many different branches of the plugin and have had zero luck. The one I have right now is Fredrik Haard's and can be found here:https://bitbucket.org/haard/mercurial-reviewboard
Unfortunately he hasn't updated it in some time.
I've tried looking through the source for the plugin but know next to nothing about Python in general and Mercurial plugins in specific.
If anyone can help in any way I'd greatly appreciate it.
I had this same error "'module' object has no attribute 'findoutgoing'", using the following:
TortoiseHG: 2.4.3 (with Mercurial-2.3.2, Python-2.7.3, PyQt-4.9.3, Qt-4.8.2)
Reviewboard: 1.6.13
Mercurial-reviewboard plugin: windix-mercurial-reviewboard (4.1.0) from 2012-08-30 and with the following change in reviewboard.py at line 400:
self._api_post('/account/login/', {
instead of
self._api_post('/api/json/accounts/login/', {
I only have a local repository, towards which Reviewboard points using the path on the disk.
The problem was fixed as soon as I added in the .hg/hgrc file of that repository, the following:
[paths]
default = http://localhost:8003
where 8003 is the port I configured for the same repo, in the same file inside that repo.
I have two more local repos, in the same situation - no remote base - configured for 8000 and 8005 respectively, I am now able to post review requests from the TortoiseHG user interface for all of them (after having added for each of these repos, the [paths] section and the default url like above).
I hope this helps!
While still having some problems, 'my' fork works for me right now although there are encoding errors for source files that are non-ascii. If it does not work for you (commit from 2012-24-10), and the problems you have are not related to encoding (working on those), could you please describe what is happening/provide log messages?