I am having trouble when using aggregators with avg because it keeps dividing the last result by the quantity every time pagination goes back or export occurs.
So the 1st time on the page/export the avg is right and every subsequent export/page back the last result gets divided again by the number of rows.
That only happens with more than one xDimension.
Also in the export at each export each summary header is repeated X times exported.
Anyone experienced that? jqgrid 5.3.0.
Edit: (image removed, example removed)
The example help to resolve the problem. Thank you. This was a bug and it is fixed. You can get the fix from GitHub the code is rebuild ed
Related
I have a list of 96 times in 15 minute intervals that I'm trying to use for data validation. It turns out that it works only up to a certain point. When selecting times from 00:00 to 18:30 it works fine. When selecting times from 18:45 to 23:45 it throws an error.
The data that you entered in cell B1 violates the data validation
rules set on this cell.
I made a test file to see if the same thing would happen if I used a different type of data, but when using a lists of numbers or text with the same amount of items it seems to work without issues.
https://docs.google.com/spreadsheets/d/1ClBhZk6fysOq0wqIrE5IxJgPMs_A05gJsN_kEiXoFGI/edit?usp=sharing
Does anyone know the reason why it doesn't work with the list of times? More importantly, does anyone know a way I could get it to work?
Edit:
The steps provided by player0 worked to fix it in my test file linked above, but didn't make a difference in the real file I'm working on. Here's a copy of the real file which exhibits the same problem.
https://docs.google.com/spreadsheets/d/1cOMB0BpzSBR7ZM7fJQQfhA56fniKTBJb-3TePUky6gM/edit?usp=sharing
Please try setting a time of greater than 18:30 in a couple of cells. I keep getting the same errors.
I suppose a workaround could be to not reject input on invalid data, but I feel this should just work with rejecting it and would like to know where I went wrong.
formatting. select columns A & B and force Time (or Plain text):
When I search for something in the Project navigator, some results are missing from the list. If I delete my query and write it again, it starts to work again - but only in come cases.
What is this issue and how can I get around it?
UPDATE: This issue has been fixed in Xcode 12.0.1.
Original answer:
This is a bug in Xcode 12 caused by typing too fast. (Yeah, I know...)
Essentially, what happens is that Xcode starts fetching the list, but if you type the second character before the first query finishes (or the third before the second finishes, you get the idea), you'll get a list with missing items. What likely happens is that Xcode tries to filter the previous list to save time instead of querying all files, and in this case, it filters the incomplete list instead of waiting for the query to finish.
There are 2 easy ways to get around this issue for now:
Use the Open Quickly menu instead (⌘⇧O, Cmd+Shift+O)
Type slower. (no joke, this is what I usually do)
Hopefully this will get fixed soon.
I'm using <TransitionGroup/> and <CSSTransition timeout={2000}>... and all transitions are set to take 2000ms in CSS.
If I add and then remove a small number of entries, it takes roughly 2000ms for onExited() to be called as expected.
But with 500 entires, it takes TransitionGroup 48 seconds (chrome) or 486 (!!!!) seconds (firefox) before onExited() is called on the last element after removing 500 elements.
Why is that? This makes it useless for my use-case.
I've created a sandbox example which is just a modification of the TransitionGroup example from the doc. There is a button to add 100 items at a time and a a "Remove All" button that prints to the console how long it took from beginning the removal until both onExiting and onExited() are called on the last element.
This sounds to me like a bug, but if there is something I can do differently, that would be great.
If it really is a bug I guess I could do it with pure CSS, but right now, I don't know how...
There was nothing wrong in the way TransitionGroup was used. I've created:
TransitionGroup takes 486 seconds to remove 500 components · Issue #599 · reactjs/react-transition-group
where I've also outlined why in the code I think this happens, and a half-assed, incomplete attempt at fixing it.
How can we resolve this issue?.
Macro length exceeds 2500 lines, this might take too long to load. Would you like to proceed? Note: You can disable this warning message
by increasing the "extensions.imacros.maxMacroLength" parameter.
extensions.imacros.maxMacroLength problem, type in address about:config,
then press i promise i be careful
in search type or copy and paste extensions.imacros.maxMacroLength
if it does not show add a new one by right clicking the main window
click new, then integer then paste the words "extensions.imacros.maxMacroLength" .
then type a value higher than the lines in your script
and problem solved
best regards letsdancemusic
You can disable the message with "extensions.imacros.maxMacroLength" in your about:config adress in Mozilla. If this doesnt exist, simply create it.
If you script has repeated instructions shorten the script down and use the "play loop" and increase "max" setting how many times you want the script to repeat, i find anything over 10,000 lines begans to stall the script to start longer the script the longer it takes to load into memory
I'm trying to find a way to limit the time of execution of MSK_optimize routine. However, browsing through MOSEK docs gives me nothing. I have tried with:
MSK_putnaintparam( task, "MSK_DPAR_OPTIMIZER_MAX_TIME", 1 );
and playing with the value on the right, but this does not seem to solve the problem and looks like it does not even affect MOSEK. Setting MSK_DPAR_MIO_MAX_TIME manually is not possible. Other than that, I have found nothing that can influence maximum time MOSEK will run. Any help appreciated.
The function MSK_putnaintparam( task, "MSK_DPAR_OPTIMIZER_MAX_TIME", 1 ); would have returned a proper error code. So if you did not ignore those you would have discovered your mistake.
For anyone that could find this helpful:
The problem is that MSK_DPAR_OPTIMIZER_MAX_TIME is a double and not an integer parameter. After losing a whole day on this, I finally found that putting:
MSK_putnadouparam( task, "MSK_DPAR_OPTIMIZER_MAX_TIME", 1 );
does the trick.