I'm using Polymer 1.0 and recently in dev tools a large number of [DOM] Found 2 elements with non-unique id #someCustomComponent: (More info: shortUrlWithNoUsefulInfo) errors popped up. The duplicate ids are coming from Polymer built components like iron-input which should be in shadow-dom and thus not visible as a duplicate id. Anyone else running into this?
I believe this issue came with the latest Chrome update but I can't say for sure if this is the actual cause. There is already an open issue on Github regarding that problem.
After looking further into the problem it came to my attention that the duplicate Id's are only a problem with paper-input that have a type of password. In my own case it doesn't matter if I use one of the Polymer components (iron/paper-input) or a standard HTML input with type password.
What helped me to work around this:
//script must run before Polymer is imported
window.Polymer = {
dom: 'shadow'
};
But there are some other solutions mentioned on Github and further explanations to what causes the issue:
Github paper-input dublicate id's
Related
I am using Reactjs in an ElectronJS project. There seems to be an intermittent problem where when i type some text in a textbox it types in reverse order (screenshot: https://share.getcloudapp.com/DOuxq0b2).
This happens sometimes (on both windows and macos) when I select a pre-existing entry and start typing over it (without hitting delete first). But doesn’t always happen consistently. I am not sure why this happens and most of the times i am unable to reproduce this. My program simply saves the data that is being entered in a state on the onChange event. I am not even sure if this is bug in Reactjs or html.
I was wondering if any of you have faced this when building projects with react or electronjs, if so how did you fix this?
I followed the guide to upgrade to Ionic 5 (after solving all deprecated warnings) and also to Angular v9.
On the first build, I got a bunch of errors NG8001 is not a known element (for header, title, buttons, menu-button etc).
I searched the web and there was just one occurence of this error by a guy who placed a question on the same issue today!
Any idea how to solve?
Many thanks!
I found the issue, a file called "zone-flags.ts" should have been present (it's there on a new v5 project), but was not in the upgraded one. I copied it over a brand new v5 project, and all is well now... Dont know why it wasnt created by the upgrade.
Thanks!
I'm trying Azure Functions for the first time and have been able to build and publish "Release" versions without any issue.
I want to step through the code and so need to create and publish a "Debug" version but when I try and build I get the following errors with the same code:
CS0579 Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyProductAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyVersionAttribute' attribute
From researching this error the main suggestion has been to remove them from the AssemblyInfo.cs file but rebuilds just put them back in again and the "Release" version is happy with these settings being there.
What am I missing so I can create a "Debug" version of the code?
Thanks
According to your description about CS0579 Duplicate error ,I suppose some temporary *.cs files generated during compilation got accidentally added to the project. The files were from the obj\Debug directory, you could try to delete these files to solve problem. For more details, you could refer to this SO thread.
In my case, some temporary *.cs files generated during compilation got accidentally added to the project.
The files were from the obj\Debug directory, so they definitely shouldn't have been added to the solution. A *.cs wildcard went a little crazy and added them incorrectly.
If it doesn't work, there are also other solutions you could have a try. Such as right click project name>choose Edit FunctionName.csproj. Edit the csproj and turn the generation of the attributes causing the issues off. More solutions you could refer to this article.
Resolution
I found this issue on GitHub where there were a couple of options to resolve this issue which I am going to cover here plus a third option I tried not mention in the issue.
I have managed to now get the Debug to build by following one of Janley's link and adding 4 extra lines into the .csproj file:
<GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>
<GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute>
<GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>
<GenerateAssemblyFileVersionAttribute>false</GenerateAssemblyFileVersionAttribute>
<GenerateAssemblyInformationalVersionAttribute>false</GenerateAssemblyInformationalVersionAttribute>
<GenerateAssemblyTitleAttribute>false</GenerateAssemblyTitleAttribute>
<GenerateAssemblyVersionAttribute>false</GenerateAssemblyVersionAttribute>
I am trying to update my app in the windows store with a new version. I am getting the error message in the UI:
This package is superseded by one or more higher-ranked packages.
The version number of the new binary is higher than the existing one. Here is what the version numbers look like in the store UI:
How can I raise the rank of the new version so that the store accepts it? What are the elements to package rank? I searched online for this but could not find the answer.
Thanks.
A day after first having the problem, I submitted a package numbered 2.0.6, which I had tried yesterday, and it went right in.
I tried to delete the original submission as suggested above, before trying submitting 2.0.6, but couldn't find a delete button. Maybe by opening the older one up in the UI I made the UI realize it was older. dunno.
I'm having a heck of a time trying to publish any HTML report with htmlpublisher.
My input looks like this:
And the 404 looks like this:
The report is definitely generated in build/. I've visually compared my config.xml file to a known working example and it's apparently the same. The entry in jobs/ is there, with the correct name and documentation.
I can't figure out what I'm doing wrong. I've checked the "keep past HTML reports" box, unchecked it, played with the paths, read the (poor) documentation but I can't seem to get it working. Can anyone help?
What version of Jenkins are you running? I'm seeing this issue on all of my projects since updating to 1.529. The files are being copied to jobs/ correctly as you mentioned.
The answer you accepted is incorrect and contradicts the documentation at https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin
EDIT: The issue has been resolved in 1.530: https://jenkins-ci.org/changelog
I've updated and I'm not seeing 404s anymore.
The developers of Jenkins has confirmed that this issue is related to the version 1.529 and it is solved in 1.530.