Silencing (not placating) Yarn's "no license field" warning - yarnpkg

How can I deliberately silence Yarn's "No license field" and "License should be a valid SPDX license expression" warnings, globally across my OS?
I don't want to add private: true to my package.json, nor add a license field – I just want to silence Yarn's warnings.

Related

Can't run Unity3d, can't create the ALF for the manual license activation

I installed Unity 2021.3.11f1 on Windows 11, but when I run the editor it says "No valid Unity Editor license found. Please activate your license." So I tried to do [these instructions][1] to activate my license.
However, after running "unity.exe -batchmode -createManualActivationFile -logfile", I can't find the Activation License File (ALF) anyhwere, be it C:/Users/Naburu38, C:\ProgramData\Unity, C:\Users\Naburu38\AppData\Local\Unity, or C:\Users\Naburu38\AppData\LocalLow\Unity.
I run the CMD both as regular and admin. I checked my admin account folders too.
Any suggestions?

Xcode warning is referring to a path that doesn't exist

I have warning on xcode that reads, warning: /Users/blair/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/214RBQA6K22QP/Foundation-A3SOD99KJ0S9.pcm: No such file or directory note: while processing /Users/blair/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/214RBQA6K22QP/Foundation-A3SOD99KJ0S9.pcm
I have about 20 warnings like this that are almost identical. The weird thing is that my machine has no user "blair".
Can anyone please help me figure out whats going on here?
I solved this by setting the "debug" key of the "Debug Information Format" in build settings for the Target, to "Dwarf"
Firebase Crashlytic directs you to set both "debug" & "release" to "DWARF with dSYM file", however i think you have to make a decision whether you actually need it in debug

lx-symbols: Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0xff

I'm trying to load the lx-symbols from the kernel. but it keeps showing me the following error:
(gdb) lx-symbols
loading vmlinux
Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0xffffffff824fb470:
Error occurred in Python command: Cannot access memory at address 0xffffffff824fb470
Now I was successfully able to load the lx-symbols before from the same build(not sure if this is the correct terminology) but don't know why I can load it anymore.
Now, When I first connect to the remote machine via gdb it used to shows the build trace like the following:
GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./vmlinux...done.
(gdb) target remote: 1235
Remote debugging using : 1235
native_safe_halt ()
at /build/linux-hwe-22QmxS/linux-hwe-5.3.0/arch/x86/include/asm/irqflags.h:61
61 /build/linux-hwe-22QmxS/linux-hwe-5.3.0/arch/x86/include/asm/irqflags.h: No such file or directory.
Now when I connect to the remote kernel, it is showing me just this :
(gdb) target remote :1235
Remote debugging using :1235
0xffffffff81a98522 in __irqentry_text_end ()
I notice that the build trace /build/linux-hwe-22QmxS/linux-hwe-5.3.0/arch/x86/include/asm/irqflags.h:61
61 disappear (I did not make any changes to the configuration or setting).
This is the second time I'm facing the same problem. At the first time, I thought maybe i accidentally make some changes but as the problem occurs again, this time I'm quite sure I did not make any changes.
I have my .gdbinit file with the correct path.
add-auto-load-safe-path /../../ubuntu-bionic/debian/build/build-generic/vmlinux-gdb.py
I checked if the source is loading correctly by using the this:
(gdb) source /home/../../ubuntu-bionic/debian/build/build-generic/vmlinux-gdb.py
It didn't throw me any error. So, I guess the source is loading correctly. I just don't know what else to do. Please help.
Try to add to the kernel boot parameters "nokaslr" and/or build with CONFIG_RANDOMIZE_BASE=n

New configuration option and OMNET++ ini error checking

I have added the following configuration option into my C++ code in OMNT++:
Register_PerRunConfigOption(CFGID_LOGEVENTS, "logevents", CFG_BOOL, "false", "log scheduler events");
I specify the 'logevents' in my Config <name>, and I can use it without any issues. The problem is with the ini error checking:
Apparently it does not recognize the newly added config option and shows an error. As a temporary workaround, I am using **.logevent = false in order to change error into warning.
Is this a known issue ?
Every time I run my project, the following error window pops up which is annoying!
Error exist in required project(s): Proceed with launch ?
Is there any ways to fix the error or at least suppress it?
Actually, this is not an error. It only means that IDE does not recognize this option. Your option is added correctly. Build your model using Qtenv or Tkenv and run it, then choose from the menu: Inspect | Available Components | Supported configuration options - the option logevents will be visable.

Error while building dll for resource file --error CVT1100: duplicate resource. type:DIALOG, name:4159, language:0x0409

I trying to create dll from resource files.
I have more than 1 .rc file and want to include in dll.
but i am getting following error
error CVT1100: duplicate resource. type:DIALOG, name:4159, language:0x0409
error LNK1123: failure during conversion to COFF: file invalid or corrupt.
I searched a lot but couldn't solved yet.
I may have had the same problem in my project (but I used Visual Studio 2008).
In my case the problem was that in "Project Properties/Linker/Manifest File/Generate Manifest" when in
- "Debug" mode the setting should be "No" (setting to "Yes" generates exactly the same error)
- but when in "Release" mode the setting should be "Yes".

Resources