Could someone please explain to me why in Bugzilla (I'm using 4.4.1) duplicate_or_move_bug_status can only be RESOLVED or VERIFIED?
My rather newbe intuition tells me that it should follow the status of the bug it duplicates especially if that other bug is not resolved nor verified.
Check in Administration->Bug Status workflow.This defines what status our bugs may move from current status. You can edit this if you are a administrator.
Related
I get a strange Error Message during the Code-Generation Process in STM CubeIDE for a STM32F4 target:
The Details:
I am using STM CubeIDE for an embedded Project with an STM32F405 Microcontroller and I have added the CMSIS Package 5.7.0 to the project, because i need some of the DSP functions. I have allready done this before and never experienced such an error message.
The message pops up during the Code-Generation process, after changing something in the Hardware-Setup with the (built in) CubeMX. It occurs two times during the Code Generation process. I can click on "OK" and it does NOT interrupt the Code Generation process, which seems to finish successfully. I can also compile the project without errors and it seems to work ok.
The Question:
Even though it seems to work properly, I'd like to know: what is this, where does it come from, and what can I do to solve this? I'm affraid that might lead to some unpleasant sleeping bugs or other nasty stuff ...
Has anyone experienced anything simlilar and has an explanation or even a solution for this?
Hint: I have recently update to CubeIDE 1.6.0 - maybe this is a Bug in CubeIDE and not in CMSIS?
What I've done:
I tried to google that, with the keywords:
"SliDtzliTZ&" and the "LogicalParser:syntax error detected in expression for ARM.CMSIS.5.7.0" but did not get any usefull results. Next step was to post the question here ...
Thank you in advance,
Chris
This problem happens with release version 5.7.0. Using any older version available in the official repository solves the problem.
I'm using 5.6.0 now and all is fine.
Edit: Problem persists on 5.8.0.
I was in a coding bootcamp last year and have not used vsc in a good while since, but am trying to get back into coding and am making a react app. I tried making a new react-app as i would in the past, but it could not make a template due to being outdated? i tried 'npm uninstall -g create-react-app' as suggested by most then just trying to create it again. problem being when i do i get lines of ERR one of which says,
"The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user"
i have tried anything, anything safe, i can find but nothing will give me access. what exactly is this? i am logged in as i just did and even said lat log in at so and so time meaning my user account is logged in. anything helps, but i guess i missunderstand what is happening here as i am not totally well versed in much of this yet. thank you for your time and helping a newbie out!
I'm trying to load queryverse and it fails. Is anyone else facing the same? Any suggestions? Can someone help me fix this?
Please follow the hyperlink (error - output) to view the error message! Thanks.
PFA. error - ouput
I had a similar problem on my laptop and did the following commands and it eventually worked. Basically what I think happened at least for me was I had an older version of Julia installed and think that these packages just didn't get compiled for the current version of Julia.. but I don't really know its all magic but this might be worth a try.
Pkg.add("VegaDatasets")
Pkg.build("PyCall")
Pkg.add("VegaLite")
Pkg.build("NodeJS")
Pkg.build("VegaLite")
I am not a programmer. I have some software at work that keeps crashing on me. I used the Visual Studio debugger last time it crashed and found out it was unhandled exceptions.
The first unhandled exception is at 0x0048ADF0 in Cyclone.exe and is an Access violation writing to location 0x00000003.
My research leads me to understand that this is the program trying to write to memory that the process doesn't have permission to.
When running the debug in Visual Studio, after the access violation exception there is a long list of Unhandled exceptions similar to this "...at 0x776C016E (ntdll.dll) in Cyclone.exe: 0x00000000: The operation completed successfully." with different addresses.
Is there any way I can fix this without being a programmer? Some sort of modification to the app files or settings, or a tutorial or something.
No, there is no way. It's not different from asking if you can drive a car without knowing anything about driving.
Sounds like you need to report the problem to the person or company who provided it. What you need to do, however, is give them enough information to understand the problem and fix it. This includes:
what version of their program are you running
which computer operating system (e.g. Windows) and which version (e.g. 7)
precisely what steps you have to take to make the error occur
whether you have changed anything recently, e.g. by installing Windows Updates or changing your anti-virus protection
precise details of any error messages you see, ideally by copy/paste or by providing a screenshot of the erro
anything else you think might help them to help you
Be prepared for them to ask you additional questions, or try some tests to help figure out the cause and a way to solve it.
Your research sounds about right but I don't think there is much anyone here can do to help (unless they happen to work on the application).
Your best bet would be to look for a "Help" or an "About" screen and contact the people who wrote it with this information
There's a simple way to read the registry and get the UAC status from there. The only problem is that if you are not an administrator user or the UAC is ON then you can't read that particular key.
Is there a way (API, etc) to get the UAC status accurately without having to read the registry?
Sample code is always appreciated.
Thanks!
jess
EDIT:
I'm starting a bounty. PLEASE PLEASE if you are going to answer do not tell me how I shouldn't care about the UAC status and that the code should be independent of the UAC and how microsoft is so goody goody.
From the internets:
HANDLE tokenHandle;
OpenProcessToken(GetCurrentProcess(), TOKEN_QUERY, &tokenHandle);
DWORD tokenInformationBufferLength = 0;
TOKEN_ELEVATION_TYPE tokenElevation;
GetTokenInformation(tokenHandle, TokenElevationType, &tokenElevation, sizeof(tokenElevation), &tokenInformationBufferLength);
Ok, building the answer on what ssg/comments already said:
http://www.softblog.com/2008-02/vista-tools/
This checks both elevation and UAC status.
First as
How can I detect if my process is running UAC-elevated or not?
already mentions, it will test the ElevationStatus. After that, it
tries to start a subprocess with elevated status which will fail
if standard user is logged in, determining the UAC status.
And no, it does not use the registry.
Not quite where you're looking, I suppose... but if the registry read returns an access failure on the key, that is actually the answer you're looking for -- UAC is enabled.
What I did to solve this problem, was if I had admin rights according to the API call I read the registry value (UAC provides false to admin rights check) and if I did not have admin rights I tried to make a new key in HKEY_LOCAL_MACHINE\Software. If that succeeded, UAC was on and I removed the key.
First off, you don't really want to seek out a way to "get around" the security features of the operating system. Even if you do find a solution that works right now, Microsoft can (and does) change these kinds of features with Windows Update and will break your app in the future. Fighting the security features is an uphill battle and it will be a continuous headache for you. While I would love to hear more of your questions on StackOverflow :) it is most likely not the path you want to go down.
That said, I think you are going about the issue wrong. If your manager doesn't want you to fix the problem, then your manager has accepted the problem. Just mark the whole application as "must run in administrator mode" and be done with it. The users will get a single warning at application start and then the app will run for them. Here's a link to show you how to set this option.
Of course, if you're users don't have admin rights to their own machine you are basically out of luck.