GithubHelp home page GithubHelp logo

Comments (13)

mjrider avatar mjrider commented on July 19, 2024 1

screenshot at 2017-03-16 14-38-48
see the broken </info> tag in the output and the tput cols output

from recipes.

jsamouh avatar jsamouh commented on July 19, 2024 1

@mjrider it's effectly a symfony bug. I'll check

from recipes.

antonmedv avatar antonmedv commented on July 19, 2024

Can you send PR with fix?

from recipes.

mjrider avatar mjrider commented on July 19, 2024

oke, some more debugging, i think it is maybe not related to deployer
it only breaks when your terminal is between 72 and 134 columns
( test script )
https://gist.github.com/mjrider/9bd6bc981b11f1ab37fc4d059293fa4e

from recipes.

antonmedv avatar antonmedv commented on July 19, 2024

Maybe delete => at all?

<info>set('newrelic', ['api_key', 'application_id']);</info>

from recipes.

mjrider avatar mjrider commented on July 19, 2024

yes that would work around the problem.

i think that we just found a bug in symfony, but my symfony knowledge is to small to create a small reproduction script so i could file a bug with symfony

from recipes.

antonmedv avatar antonmedv commented on July 19, 2024

I think, lets fix this recipe first. Maybe someone get this too.

from recipes.

mjrider avatar mjrider commented on July 19, 2024

oke, made a reproduction and a bugreport
symfony/symfony#22021
https://github.com/mjrider/break-symfony-console

from recipes.

jsamouh avatar jsamouh commented on July 19, 2024

@mjrider , I have this in local

capture d ecran 2017-03-16 a 14 18 26

from recipes.

mjrider avatar mjrider commented on July 19, 2024

@jordscream did you try it on different terminal sizes ? because if the terminal is small or big enough, it will not fail

from recipes.

jsamouh avatar jsamouh commented on July 19, 2024

@mjrider , Indeed I reproduce the problem after 74 columns :-/

from recipes.

mjrider avatar mjrider commented on July 19, 2024

Looks like symfony is going for the option of removing formatting from exceptions.
symfony/symfony#22142

from recipes.

chalasr avatar chalasr commented on July 19, 2024

In fact, the exception message will stay raw, for instance <info>Exception!</info> will stay as is in the output. I suggest you to don't throw the exception, but use the SymfonyStyle API instead (see SymfonyStyle::block(), SymfonyStyle::error()), returning an appropriated error code. The patch has been merged in Symfony from 2.7 up to master and will be part of the next maintenance releases.

from recipes.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.