Fatal error: Maximum execution time of 30 seconds exceeded in D:\wamp\www\moneymanager18_8_15\system\database\drivers\mysqli\mysqli_driver.php on line 221
This happens during uploading.file is getting uploaded,but the same time this error shows.
Write this above your controller.
ini_set('max_execution_time', 0);
ini_set('memory_limit','2048M');
There is a something that CodeIgniter not include this in their documentation.
Go to the page in system/core/CodeIgniter.php and search this and change it according to your requirement
if (function_exists("set_time_limit") == TRUE AND #ini_get("safe_mode") == 0)
{
#set_time_limit(300);// change according to your requirement
}
Related
I try to take a screenshot with:
cy.visit('https://www.mypage.com/')
cy.screenshot()
But I get the error:
RangeError: The value of "offset" is out of range. It must be >= 0 and <= 6497276. Received 6497280
Does not found anything about the screenshot offset on SO.
Thanks to user "first last" I found the solution.
You have to set the viewport before, like:
cy.viewport(1280, 720)
cy.screenshot()
I am going to create end to end(e2e) test using protractor with jasmine and angular 6. I have written some test cases almost 10 cases. That's all working fine, but always some cases become fails. And its failed because of jasmine timeout. I have configure timeout value like below. But I am not getting consistant result. sometimes a test cases is success but at next run it will goes to success or fail. I have searched on google but I have not found any useful solution.
I have defined some common properties for wait
waitForElement(element: ElementFinder){
browser.waitForAngularEnabled(false);
browser.wait(() => element.isPresent(), 100000, 'timeout: ');
}
waitForUrl(url: string){
browser.wait(() => protractor.ExpectedConditions.urlContains(url), 100000, 'timeout')
}
And protractor.conf.js file I have defined that
jasmineNodeOpts: {
showColors: true,
includeStackTrace: true,
defaultTimeoutInterval: 20000,
print: function () {
}
}
I am getting below error
- Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
- Failed: stale element reference: element is not attached to the page document
(Session info: chrome=76.0.3809.100)
(Driver info: chromedriver=76.0.3809.12 (220b19a666554bdcac56dff9ffd44c300842c933-refs/branch-heads/3809#{#83}),platform=Windows NT 10.0.17134 x86_64)
I have got the solution:
I have configured waiting timeout 100000 ms for individual element find where whole script timeout was 20000 ms. So I have follow below process:
Keep full spec timeout below than sum of all elements find timeouts. I have configured defaultTimeoutInterval at jasmineNodeOpts greater than sum of value for all test cases timeout. And then add a large value to allScriptsTimeout: 2000000 inside of export.config. Its resolved my problem.
NB: I gave this answer because I think it may help others who will face this kind of problem.
I have a panel for 27 years, but met this warning when I run a regression.
panel data of global suicide rate with temperature
I use the following codes:
library(plm)
install.packages("dummies")
library(dummies)
data2 <- cbind(mydata, dummy(mydata$year, sep ="_"))
suicide_fe <- plm(suiciderate ~ dmt, data2, index = c("country", "year"),
model= "within")
summary(suicide_fe)
But I got this error:
Error in pdim.default(index[[1]], index[[2]]) :
duplicate couples (id-time)
In addition: Warning messages:
1: In pdata.frame(data, index) :
duplicate couples (id-time) in resulting pdata.frame to find out which, use
e.g. table(index(your_pdataframe), useNA = "ifany") 2: In
is.pbalanced.default(index[[1]], index[[2]]) :
duplicate couples (id-time)
I have a really strange problem. Yesterday I was working with magento just fine and today when I opened the pc and tried login on my account after cleaning cache & session it gives me this error on customer login:
Error occurred. Please try again later on the frontend.
I dig into the system.log and I have this:
ERR (3): Notice: Undefined offset: 158 in {...}/phpseclib/Math/BigInteger.php on line 3426 and 3317
ERR (3): Notice: Undefined variable: cmsPageIdentifier in {...}/default/template/page/html/header.phtml on line 29
and this is the code in question
Line 7-10:
if(Mage::app()->getFrontController()->getRequest()->getRouteName() == 'cms')
{
$cmsPageIdentifier = Mage::getSingleton('cms/page')->getIdentifier();
}
Line 29:
<?php elseif ($cmsPageIdentifier && $cmsPageIdentifier == "conferma-invio") : ?>
In sso.log I have this
DEBUG (7): HTTP status: 503 when trying to get user authentication
DEBUG (7): Field Status was empty in webapi response
Thank you.
I manually fixed the BigInteger and I remained only with the sso.log.
Dug into it and I found that there was another module error blocking customer login. Setting that module to false in app/etc/modules/Module_Name.xml fixed it.
I am trying to call cudppSort to sort a set of keys/values. I'm using the following code to set up the sort algorithm:
CUDPPConfiguration config;
config.op = CUDPP_ADD;
config.datatype = CUDPP_UINT;
config.algorithm = CUDPP_SORT_RADIX;
config.options = CUDPP_OPTION_KEY_VALUE_PAIRS | CUDPP_OPTION_FORWARD | CUDPP_OPTION_EXCLUSIVE;
CUDPPHandle planHandle;
CUDPPResult result = cudppPlan(&planHandle, config, number_points, 1, 0);
if (CUDPP_SUCCESS != result) {
printf("ERROR creating CUDPPPlan\n");
exit(-1);
}
The program exits, however on the line:
CUDPPResult result = cudppPlan(&planHandle, config, number_points, 1, 0);
and prints to stdout:
Cuda error: allocScanStorage in file 'c:/the/path/to/release1.1/cudpp/src/app/scan_app.cu' in line 279 : invalid configuration argument.
I looked at the line in scan_app.cu. It is,
CUT_CHECK_ERROR("allocScanStorage");
So apparently my configuration has an error that is causing the allocScanStorage to bomb out. There are only two calls to CUDA_SAFE_CALL in the function and I don't see a reason why either has anything to do with the configuration.
What is wrong with my configuration?
So that this doesn't sit around as an unanswered question (I'm not sure if this is the right SO etiquette but it seems like an answered question shouldn't sit around unanswered...), I'm copying the comment I made above here as an answer since it was the solution:
I figured this out (I'm still learning CUDA at the moment.) Because the error checking is asynchronous errors can show up in strange places if you don't check for them from time to time. My code had caused an error before I called cudppPlan but because I didn't check for errors the cudppPlan reported the error as if it was in cudppPlan.