Ots parsing error incorrect file size in woff header

Font-awesome OTS parsing error: Failed to convert WOFF 2.0 font to SFNT #648

Comments

I’m getting the following in the Chrome console recently. I’m using the latest parent and child code.

When I click on the font in the console, its there so the paths seem correct and file is on the server, so I wonder if its being treated as a text file in the gulp copy, rather than a binary? Maybe needing something like options: < process: processFiles, noProcess: ['ttf,otf,woff,woff2,eot>‘]>?

The text was updated successfully, but these errors were encountered:

Have you tried setting the mime type on server to font/woff2 ?

As far as I understand, pipe literally streams a readable source into a writable destination (may that be a task or file or process) and does not care about whats going in or out. So what ever goes in, comes out.

This demo task is also the preferred method as described in the documentation.

How did you get the files onto the server; is there anything along the path that could have disrupted the encoding or the way the files are read by the server/client?

Thanks guys, really appreciate the help, and sorry if its not actually a bug but a fault with our process.

We use AWS OpsWorks, which basically pulls the latest from the repo, and then runs gulp styles and then gulp dist and copies the dist directory to the web dir, so I’m not sure if it is doing anything else disruptive in the path, its fairly primitive?

Happy to try setting the mime type to font/woff2 , how would I do that?

For apache I think you can add this to .htaccess:

That will set the content-type header.

For nginx I think you can paste this into mime.types file without the surrounding tag and remove AddType from each line.

Obviously this is for all font types, just merge as necessary.

Thanks, I’ve added that to nginx and restarted but still get the errors unfortunately

So I redownloaded the understrap child theme, deleted the fonts and replaced them with the source ones from github, but still get the error.

I’ve also set .gitattributes to force them to binary just in case with:
*.eot binary *.otf binary *.ttf binary *.woff binary *.woff2 binary

At a bit of a loss, as the fonts are there at the url when you click on them in the web page inspector, but just still getting the errors?

Header is set correctly so I guess it’s not that.

How are you uploading the files to server? If you are deploying with git you might need to set filetype as binary in gitattributes so it doesnt modify line endings.

Читайте также:  Error in src address ip address expected

Thanks mate, yes have done that too in .gitattributes

From what I read I´d say that this is most definitely not UnderStrap related. For that reason I´ll close that issue. May the force be with you 😉

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

incorrect file size in WOFF header #566

Comments

Short description of the problem:

With version 0.0.45 I was able to extend ionicons with no problem (just adding few icons to v3 branch)

now with version 0.0.47, im getting this error for the icons:

What behavior are you expecting?

Icons should work normally with this version

Steps to reproduce:

  1. user this as ionicons path in package.json «git@github.com:travessey/ionicons.git#travessey
  2. use one of the new icons and see the result. (big square and not an icon)
  3. Use logo-deals as icon (this is one of the new icons)

Which @ionic/app-scripts version are you using?
0.0.47

The text was updated successfully, but these errors were encountered:

When trying to narrow down on the problem I see that it looks like a problem with the latest version 0.0.47.

I tried to revert to version 0.0.45 and all worked ok.
Also when trying to work with 0.0.46 All worked ok.

It seems that 0.0.47 is causing this.

Anyone have an idea how to solve that?

Sorry, this doesn’t seem like an app-scripts issue. I’m not sure there is anything we can do to help you here.

@danbucholtz Hello,
Thanks for you answer.

If this is the case, How can you explain that it worked fine on 0.0.46?

I found the issue and its behind this commit.

I remove the copy of the ionic-angular fonts and all seems to work fine.
I think its because that ionic-angular/fonts contains some ionicons files which causes the the conflict.

What do you think?

@danbucholtz Hi, Sorry for poping this up again

After some more investigations, I see that both ionic-app-scripts and ionic (here)
are copying items from ionicons .

Because ionic is copying fonts from ionicons, when install ionic you get in the fonts folder woff files. And because the current copy script is copying the fonts from ionic-angular/assets after the fonts from ionicons we get a result that installing ionicons in a project is useless since you always get the files from ionic-angular .
This causes error when trying to create/add custom icons for ionicons .

we need to choose when we want to copy the files from ionicons to avoid this.

@danbucholtz @jgw96 Hi guys,
Can someone open this issue.. I think it is still relevant..

@danbucholtz Ill be happy for a response. Thanks.

Sorry, I don’t know too much about this. It seems outside of the scope of what we intend to support.

Customizing our icon set and then seeing issues with the wrong size is not something we can support at scale.

Читайте также:  Ваше подключение не является приватным как исправить эту ошибку

Источник

Error in Edit a Page #412

Comments

Summary of issue

There are some error when edit Page.
From Browser Console :
VM582 pages:14 The key «viewport-fit» is not recognized and ignored.
app.js:8703 Download the Vue Devtools extension for a better development experience:
https://github.com/vuejs/vue-devtools
app.js:8713 You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html

VM582 pages:1 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
VM582 pages:1 OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
VM582 pages:1 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0
VM582 pages:1 OTS parsing error: incorrect file size in WOFF header
VM582 pages:1 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0
VM582 pages:1 OTS parsing error: FFTM: table overruns end of file
app.js:1188 [Vue warn]: Invalid prop: type check failed for prop «entityId». Expected Number, got Object.

warn @ app.js:1188
app.js:5688 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
removeChild @ app.js:5688
app.js:5688 OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
removeChild @ app.js:5688
app.js:5688 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0
removeChild @ app.js:5688
app.js:5688 OTS parsing error: incorrect file size in WOFF header
removeChild @ app.js:5688
app.js:5688 Failed to decode downloaded font: http://localhost/themes/adminlte/vendor/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0
removeChild @ app.js:5688
app.js:5688 OTS parsing error: FFTM: table overruns end of file
removeChild @ app.js:5688
app.js:1188 [Vue warn]: Invalid prop: type check failed for prop «entityId». Expected Number, got Object.
.

The text was updated successfully, but these errors were encountered:

Источник

AOT Compilation Doesn’t Work With Sub-Package Fonts #20676

Comments

I’m submitting a.

[X] Bug report
(It might be a regression, or it might be a bug uncovered in a browser vendor change.)

Current behavior

When I run my project with npm run ng — serve —aot or when I build npm run build , fonts don’t show up in Chrome or Firefox. They do show up correctly in Safari and they do show up correctly across modern browsers when I run without —aot. See below for the project details.

Expected behavior

Fonts should display correctly when I run under —aot.

Minimal reproduction of the problem with instructions

  1. run npm start
  2. Observe the 3 home icons at http://localhost:4200 in Chrome and Firefox
  3. run npm run ng — serve —aot
  4. Observe the placeholder icons at the url above and the error in the dev tools console

What is the motivation / use case for changing the behavior?

Providing a demo application within a mono-repo that hosts components used across many applications.

Environment

Angular version: 5.0.3

  • Chrome (desktop) version 62.0.3202.94
  • Firefox version 57.0

The text was updated successfully, but these errors were encountered:

I can’t reproduce your problem with `ng serve —aot’ and chrome 62.0.3202.94

I’m also now having trouble reproducing it in my simplified example, although I’m still seeing the problem in our real-life code. I swear the issue came up in the example yesterday. Let me see if I can sort out what’s different now between the two. Thanks for your patience and sorry about the noisiness.

It seems likely that this is the same issue as angular/angular-cli#8735. I’m also having trouble reproducing it there, and difficulty installing @chatham/pattern-library (which might be a private module that reporter is using — similar to what I’m doing). Am continuing to work on reproducing. FWIW, I’d be content to track both issues together.

Читайте также:  Error invalid request error description pc machine id is missing code 102115 origin

I’ve added another commit on my example repo (see above), and am now partly reproducing the issue:

The issue seems to be linked to the build containing two copies of the fonts causing issues when compiling in prod mode.

I can reproduce this duplication on my project 100% of the time, but the fonts only fail to show in the browser some of the time, I assume based on the lexicographical order of the duplicated fonts with hash.

This has only started happening since migration to angular-5.0.5, I’m attempting to put together a public MRE now.

Compiling without aot ( —aot=false ) or without output hashing media ( —output-hashing=bundles or —output-hashing=none ) also stops the duplication of fonts, but neither workaround is particularly appealing for long term production builds.

In my real-life project passing —output-hashing does remove the duplicate fonts, but doesn’t help the Chrome/FF parsing issue for the fonts. (I’m seeing the OTS parsing error: incorrect file size in WOFF header and Failed to decode downloaded font: messages shown in the screenshot above.)

@Andrew-Stubbs I tried to downgrade, but same errors happened for angular =5.0.0 for me

Источник

2.2.0 breaks font awesome #87

Comments

When upgrading from 2.1.1 to 2.2.0 any fonts loaded with webpack and passed through this library get broken with the console error:

I’m guessing it’s caused by this commit, there doesn’t seem to be any check on the filetype so I suppose it’s trying to apply the sourcemap to the font files.

I’ll try and find the time later to put together a sample repo that demonstrates this.

The text was updated successfully, but these errors were encountered:

Duplicated. Downgrading back to 2.1.1 does fix. Thanks for filing @mattlewis92 .

This breaks images as well.

Thanks @brev downgrad solves it for me too

I’m still seeing this issue in 3.0.0.

@jv-PintoBobcat Could you post an example that causes it to happen?

I’m also experiencing this on 3.0.0.

If you want to reproduce on my app:

  • set it up using these istructions but ignore everything related to go-ipfs and ipfs, they are not needed to reproduce this
  • make sure you change the webpack-stream dependency in package.json to version 3.0.0 before launching npm install of course
  • open the page at the webserver of gulp serve . You’ll se the errors and the missing font awesome icons

I’m working around the issue by downgrading to 2.1.1 at the moment

Please use @fazo96’s app to reproduce this. All of my apps that use this are proprietary projects from my company and aren’t set up for public consumption at this time. I’d have to create a mock project just to demonstrate this bug.

@jv-PintoBobcat Fixed by 3.0.1 in my case 👍

Having the same issue with version 3.2.0

Loading font-awesome using:

And my output is

This is the webpack config I’m using successfully with font awesome + webpack stream (latest versions of both):

Источник

Smartadm.ru
Adblock
detector