I realized I never updated Polymer since I first installed with Bower, so I ran bower update on my website's project root and it appeared to update fine, with the exception that it was finding two different versions, 0.3.6 and 0.5.1 I believe. I checked the Github releases section for Polymer and saw that 0.5.1 is the latest stable release so when the option occured I hit 0.5.1. Now when I go to my website on my AppEngine dev server I see this:
Uncaught TypeError: object is not a function
On a bunch of Polymer elements, like
core-collapse.html:59
core-selection.html:77
core-selector.html:78
I'm not sure where I went wrong! Is 0.5.1 not the stabls release? I am very new to terminal stuff so am not sure where to go to try to fix this. Any help would be appreciated! Thanks!
edit: I didn't realize I needed to use /webcomponentsjs/webcomponents.js instead of platform.js now. I'll leave this up in case anyone else is confused in the future!
Related
I am new to Foundation. I started working on a project using an older version of Foundation (2018-2019) and I can't seem to install the dependencies I need to run the project locally, such as Gulp and Babel, and several others. For example, here is a screenshot of the errors I've been receiving any time I try to install a dependency.
list of warnings and errors :
This is the first large-scale project I've worked on using many more dependencies than I'm used to. I've seen "Python" listed among the errors but have never used it, so I'm not sure if that should be installed as well.
I tried to install a few different dependencies, some needing Admin privilege and others not. I'm not sure what I'm doing wrong.
I notice that the mosaic package was updated a few days ago (1.8.3). Since then, I keep getting an error message that mosaic can't load.
> library(mosaic)
Error: package or namespace load failed for ‘mosaic’:
object ‘compare’ is not exported by 'namespace:mosaicCore'
The package installed, and it works on a PC. I've tried reinstalling R and R studio to be sure but I keep getting the same error. Anyone who has had the same problem or figured out how to fix it?
It works fine on a Mac (it was developed on a Mac).
I'm not sure how you did your installation, but you also need to have an updated version of mosaicCore. Looks like that didn't happen for some reason.
I'd suggest updating mosaicData and ggformula as well, if your update method didn't trigger those already. All four packages went to CRAN last week. If it has been awhile, you might do update.packages().
My daughter met the same problem today.
As per the suggestion here, we install the newest mosaicData, and the problem remains.
Then quit Rstudio, restart Rstudio, after running library(mosaic) again, it mentions that several packages are missing,
After installing the missing packages, everything is ok.
I had other people in my class that had the same issue. Similar to the above answer, i had to:
Uninstall/delete the package ggformula
Update the package mosaicCore
Reinstall ggformula
Reinstall mosaic
That is how i was able to resolve the issue.
I'm having problems with using fluent in Silverstripe 4. So I tested to install different versions of fluent to see if I was able to get it working. The version of Silverstripe is 4.1.1.
After uninstalling fluent again, I get "server error" and I can't see anything in the php logs and when trying to run in dev mode, I don't see any difference.
One puzzling thing is that a folder named "themes" appeared in the root folder. I think that it was added by composer during the module installation, but I'm not sure. But I do know that git listed the themes folder as an untracked file. Which suggests that it was automatically added. So I removed that folder when uninstalling the module.
Now I'm not sure what to do. I would want to restore the database as it was before installing fluent (I've tried to add language to see if fluent was working). Or at least get back to square one.
How do people usually do when working with Silverstripe and testing modules?
What I've done so far:
Checked the php logs. No errors found.
Added "Director::set_environment_type("dev");" to _config.php, without seeing any difference when loading the page.
Tested to load the page with ?dev=1 without any difference.
I ran composer update and now the site is working. Might be one thing to test for silverstripe noobs (like me).
I am new to cloud functions and was testing this sample code https://github.com/firebase/functions-samples/tree/master/quickstarts/uppercase-firestore
This fails to execute due to an error from nanomatch. Looking at nanomatch repository on GitHub This is a listed issue and reverting back to 1.2.9 takes care of this error.
I am trying to fix this on my end - but how do I do this? Can somebody guide me on this. Thank you for the help.
TypeError: Cannot read property 'addQmark' of undefined
at Object.<anonymous> (/user_code/node_modules/firebase-admin/node_modules/nanomatch/lib/compilers.js:92:15)
at Object.visit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:129:15)
at Object.mapVisit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:143:12)
at Object.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:168:10)
at Snapdragon.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/index.js:156:32)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:786:23
at memoize (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:859:13)
at Function.micromatch.compile (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:783:10)
at create (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:686:25)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:695:16
THIS BUG WAS FIXED
The version that caused the bug was reverted right when this issue was reported on GitHub, which was within minutes of it being released. To get the fix, just reinstall. You might need to delete node_modules and/or lockfiles first, to ensure cached versions aren't used by NPM. This conversation belongs on GitHub, so that we can respond to user feedback. I found this by chance. StackOverflow is not for support).
Edit 2: it appears that firebase-admin itself needs to re-install dependencies as well. I'm looking into how to make that happen.
Please report and check issues on GitHub, where the codebase is and where this discussion belongs.
Visit https://github.com/micromatch/nanomatch/issues/15 for more info.
Faced the same problem "Thumbnail URL not saved to firestore. Cannot read property 'addQmark' of undefined"
Started today morning when I upgraded to the latest firebase-tools#3.19.1
At first thought was issue with my code, but after rollbacking my code the situation persisted.
Rolled back to firebase-tools#3.19.0 and the situation got fixed.
There is a bug in the latest firebase-tools
Use this:
npm install nanomatch#1.2.9 -S
just rollback to older version
npm install -g firebase-tools#3.19.0
Firebase team is probably/hopefully redeploying all functions without the broken nanomatch package, but for me following the advice from #abhi and redeploying immediately solved the issue!
npm install nanomatch#1.2.9 -S
firebase deploy --only functions
(npm install in the functions folder!)
Out of the blue recently, I started receiving notifications that my Jekyll builds were failing on GitHub Pages:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-builds/.
Besides that, there was no info given, and the site built fine on my local machine. I tried everything I could think of: I built the site locally (worked fine on my machine), I deleted the last few files that had been added (no improvement), and I reset the master branch to exactly as it was when I last had a successful build. I figured for sure the last tactic would work, but I kept getting build failures.
I eventually figured out the answer, which I'm going to write in a moment.
It turned out the problem was that GitHub upgraded their version of Jekyll. I had to come to the solution by two steps:
Upgrade the github-pages gem on my own computer:
$ bundle update github-pages
Discover an interesting new error message:
Liquid Exception: undefined method `gsub' for 1000:Fixnum in /_layouts/post.html
After some fiddling around (and using Jekyll's --verbose option to find where the build was choking), I discovered that this gsub error was caused by a post I had, which was titled "1,000". (It was about a sleepless night, where I tried to count my way to sleep, and gave up after 1,000.) Some updated parser was trying to parse this as a number, apparently. To fix it I changed
title: 1,000
to
title: "1,000"
And voilà, GitHub Pages was satisfied.