Whenever I try to deploy my firebase cloud functions, it considers poor formatting as a real error and doesn't let me proceed. For example:
error Expected linebreaks to be 'LF' but found 'CRLF' linebreak-style
Could someone tell me how to prevent this and let me deploy my code regardless of its formatting? Thanks
As I saw you mention in the comments, there is a previous iteration of this issue.
You can see there that you have to configure your linebreak-style in your .eslintrc or in your source code. You can also follow the approach of the second answer and ignore the linebreak-rules to avoid this warnings/errors from happening.
For further information, refer to the documentation.
Related
I am able to parse the markdwon with the help of remark and remark-html. How can I add syntax highlighting features for the code element?
I've been searched for TWO whole days trying to use remark/rehype ecosystem on syntax highlighting which is way more complex to use. I'm still working on searching, it's better to avoid remark/rehype ecosystem and try another method.
Here I share list of my search, just give you some subjective perspective so that you won't waste you too much time on things that not working. None of them will work as you expected, and their sample code are obscure or just broken codes.
https://github.com/remarkjs/remark-highlight.js
They move to support rehype. Are you a big fan of them wanna move as well?
https://github.com/sergioramos/remark-prism
You will get this error: Module parse failed: Unexpected character '�'
https://github.com/torchlight-api/remark-torchlight
They states on their website: 🚨 This client is still very much a work in progress. Please open issues! 🚨View it on github at github.com/torchlight-api/remark and this link is invalid.
https://github.com/rehypejs/rehype-highlight
It force you to use rehpye althought you can you remark-rehype for you to transfer easily. However, debug your code once you encounter some error will be helpless.
sample code use third-pary v-file to read file showing their code is working but not. and it reads html file not markdown file.
It's hard for you to grasp their concept to use their plugins to easily. It waste most of you valuable time to think what they think.
I give up remark/rehype ecosystem and stay away from them. Good luck! :)
I have a UBE that is failing after making a call to a jdeObjectCall. The API returns a 1, indicating a warning, which indicates to the report to stop processing.
The image below shows the jdeObjectCall in question that is returning a 1.
I'd like to determine why jdeObjectCall is returning a warning, so that I can investigate a fix.
Any help on this is greatly appreciated!
Cheers, Cam.
I was able to determine the answer to this question with some help from the forum jdelist.com. The topic in which I discovered my answer can be found here: https://www.jdelist.com/vb4/showthread.php/53758-E1920-Debugging-jdeObjectCall
The way I found my solution is as follows. Apologies for the high-level steps. There is some assumed knowledge here. If you are interested in a more in-depth explanation of one of these items please comment and I will provide it.
Enable logging in the jde.ini file.
Debug the locally.
Examine the output of the log file using a tool like JDETrace.
You can do a search for your business function within JDETrace. In my case, I searched for EditDate.
The line in the log will let you know the name of the busines function object.
Checkout the object in object management workbench.
Find the line where the EditDate function exists.
Place a breakpoint on this line and continue debugging.
I am getting the error here in this Travis build, and I cannot reproduce it locally. Yes, I realize that I do not have a minimal reproducible example, but I do know that it happens within tidyselect::vars_select(). Has anyone else encountered this before? I cannot find any mention of lang_unnamespace() in a Google search.
See if modifying your travis yaml to include the dev versions of the tidyverse packages help.
It looks like you're not calling rlang::lang_unnamespace() directly, correct? That function appears to have been removed, but tidyselect::vars_select() is still trying to call it.
I arbitrarily went back to the beginning of the year to see this old version.
The file doesn't even exist in today's version.
I'm getting message like this in an application:
Referencing the "form" extension by its name (defined by getName()) is deprecated since 1.26 and will be removed in Twig 2.0. Use the Fully Qualified Extension Class Name instead
The code causing this is:
$this->get('twig')->getExtension('form');
There seem to be some related threads, but I've been unable to find a solution for this. I've also taken a deep look at deprecation notes, but I've been unable to find anything that, with my knowledge, helps me to solve the problem. I'd ask for a clear solution for what I have to do to get rid of this message, that doesn't allow me to even try to upgrade.
Thanks in advance.
Well, I think I've found the solution. I just needed to find out the FQCN for the specific call, and it's
Symfony\Bridge\Twig\Extension\FormExtension
So, adding
use Symfony\Bridge\Twig\Extension\FormExtension;
and replacing
$this->get('twig')->getextension('form')
with
$this->get('twig')->getextension(FormExtension::class)
solved the problem.
I think there should be a more specific guide about what to replace and the replacement for each case.
Regards.
PD: I'm trying to find out how to mark this as solved, but maybe I'm not allowed to do this kind of things yet.
Can I know how an experienced OCaml developer debugs his code?
What I am doing is just using Printf.printf. It is too troublesome as I have to comment them all out when I need a clean output.
How should I better control this debugging process? special annotation to switch those logging on or off?
thanks
You can use bolt for this purpose. It's a syntax extension.
Btw. Ocaml has a real debugger.
There is a feature of the OCaml debugger that you may not be aware of which is not commonly found with stateful programming and is called time travel. See section 16.4.4. Basically since all of the information from step to step is kept on the stack, by keeping the changes associated with each step saved during processing, one can move through the changes in time to see the values during that step. Think of it as running the program once logging all of the values at each step into a data store then indexing into that data store based on a step number to see the values at that step.
You can also use ocp-ppx-debug which will add a printf with the good location instead of adding them manually.
https://github.com/OCamlPro-Couderc/ocp-ppx-debug