Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.
Related
I started very basic android development and from the very first day it seems that android studio and kotlin are just like a bundle of problems. Like after first installation of androidstudio I build the basic samples on Kotlin and it worked fine. After few hours I got a notification on androidstudio about some update so I did it and then every thing stopped working I looked for solution on Internet and tried for 2-3 hours but didn't get it back working. Then I uninstalled everything related to androidstudio on my PC and re-installed it and then it started to work again.
After few days I started to implement a tutorial and I used the same code and configuration described in tutorial but on the very first step where they just created a basic sample application without any thing and it started to show errors like Unresolved reference: fillMaxSize and Unresolved reference: size and I couldn't find any solid solution on Internet and surprisingly found out that internet is full of these kind of issues on androidstudio.
In the project I am using the function fillMaxSize() in another file where it works 100% fine but in the same project but in different file it gives error. Can anybody give a solution to this?
Apart from this I just want to ask that is android development in general is like this? That every time you go 1 line further and you see new errors and then you have to spend hours on internet and look for solutions and you then found tons of queries about these errors on internet and nothing is clear and particularly working for your case but it is kind of similar error_
Adding new imports, changing plugin versions, adding plugins, changing dependencies and versions.
After few hours I got a notification on androidstudio about some update so I did it and then every thing stopped working
Updates of course are good as they try to fix or enhance something. However, some updates will add, remove or change some previous working functions to achieve the fixing or enhancing purpose. And that's why some programs require certain version of Software instead of always the latest one to run.
In the project I am using the function fillMaxSize() in another file where it works 100% fine but in the same project but in different file it gives error
In this case, you will have to check whether you have really added the corresponding import to that particular file. If there is really configuration problem, it should not have worked in one file but not the other. import is something that you have to do in every file using that function.
I've been searching everywhere and was unable to find any information related to this- most likely because ag-grid update 18.x is new.
Anyhow: It appears that after updating ag-grid from 17.1.1 to 18.0.1, any page with the ag-grid on it ends up crashing EDGE and IE. Chrome works fine. (There have always been performance issues with EDGE and IE but now ag-grid fails to even load).
My current project is using: Angular 5 in VSCode, AG-GRID, etc. An error I was able to view in the console was onGridResize no longer exists; However I am not calling this event what-so-ever.
So this appears to be something that has fallen off internally? Any help would be appreciated. Thanks!
So before the question I wanna point out that the only thing I could find on this issue was on this stackoverflow question. This issue suggest that this was an issue with wappalyzer, and it was fixed in version 4.0.1. however I am using wappalyzer version 5.1.4 and is up to date with this.
I am building a web-app based on the MEAN-stack, everything worked as intended for a long time, until this error kept poping up in my google-chrome console:
Everytime i would click in my app header, and use my front-end routing to load up different components / modules this error appears, however I dont see any issue with what the web-app presents to me (it's not like I am missing data)
More details on the error:
I have no idea whats going on, or where this issue comes from.
This was due to a failing plugin.
Disable all plugins, and enable them one at a time to find failing chrome extensions.
In this case it was the wappalyzer extension.
I have downloaded and trying to check the new added feature of Speaker Diarization. Since it has some limitation that it will work only with language models (en-US_NarrowbandModel, es-ES_NarrowbandModel, ja-JP_NarrowbandModel), I am trying to change the drop down. But it's not changing and remain fixed at "US Broadband Model (16KHz)".
Please let me know in case I am doing any thing wrong.
After downloading the source code, I did "npm install" and run the server "npm start", then from Firefox "http://localhost:3000/" it's working correctly. But, after deployment in Bluemix, the language selector is not working. The screen comes correctly but language model is not changing. I am not able to select language models other than "US Broadband Model (16KHz)".
Please advice if I am doing anything wrong.
[Note: The previous version (without Speaker Diarization feature) downloaded and it work correctly i.e. the screen comes correctly as well as language model is changing.]
Also answered on DeveloperWorks Answers - https://developer.ibm.com/answers/questions/337891/ibm-watson-speech-to-text-with-diarization-languag.html
I think, based on your post that you have downloaded and modified a sample application. When you run the modified application locally your changes take effect, but when you deploy to bluemix they don't. In which case you need to work out what is different. Without seeing your modifications everything else is speculation.
Since your modified code would be browser side I suspect that they are not the same application as you would be running the code in the same browser. As your changes would be browser side, open up a developer view, and check the source on the page, to verify that your modified code is being returned. If isn't then you need to check how, where and what you are trying to deploy.
If you do see your modified code being returned then you will need to step through it to work out why it isn't being invoked correctly, possibly because of the side effect of other bluemix only scripts being invoked on the page.
I was developing a Spotify apps and all of the sudden Spotify restarted and updated.
Yey, great.. I got version 0.8.3.222.g317ab79d... however typing spotify:app:the_app_name doesnt work anymore. I get metadataFailed, sorry I could not find this app.
Anyone knows where I can find a downgrade?
Spotify 0.8.3 changed the app lookup slightly. The URI for getting at apps in development is now spotify:app:application-identifier-in-manifest.
This changes the behaviour in old versions, which used the application's directory name to load applications. It's also worth noting that your application must have a valid identifier and version in its manifest.json file. Remember to restart the client when changing your manifest so it notices the changes!
The keys you need to set are BundleIdentifier (which will be used to find the app) and BundleVersion. Documentation on the keys can be found here.
When you check spotify.com you can see there is a be right back message this indicated either server or application failures just hold for a few minutes/hours and return to developing after message is gone.