![]() |
![]() |
#386 |
Jun 2009
12458 Posts |
![]()
I have submitted zipped and unzipped without problems, but sometimes a certificate does not provoke any reaction from the db. They simply disappear immediately after uploading.
|
![]() |
![]() |
![]() |
#387 |
Sep 2008
Kansas
7·463 Posts |
![]()
I submitted zipped files recently - even this past week. They have to be .zip and not .gz or any other derivative. (I use the Compress menu item on my Mac.)
|
![]() |
![]() |
![]() |
#388 |
"Ed Hall"
Dec 2009
Adirondack Mtns
1101110110102 Posts |
![]()
All the zipped files I've sent were from the linux archiver with .zip extension. Prior to the last big downtime of the db, all was well. Since then zipped do not work for me. There could be upgrade changes coincident with my archiver.
|
![]() |
![]() |
![]() |
#389 |
Jun 2009
677 Posts |
![]()
After emailing with Markus the problem has been solved. The upload limit was set to 16MB which was not enough for my certificate. He raised the limit and now it is working again.
I was even able to upload the certificate for the still record ECPP number. It will take a while to process though ![]() |
![]() |
![]() |
![]() |
#390 | |
"Ed Hall"
Dec 2009
Adirondack Mtns
2×32×197 Posts |
![]() Quote:
And Great Job! on that "barely under" 35k certificate! You've been busy... |
|
![]() |
![]() |
![]() |
#391 |
Jun 2009
67710 Posts |
![]()
There must have been an update to factordb‘s hardware. The certificate was verified within a few hours where I expected several days.
Last fiddled with by Puzzle-Peter on 2019-05-02 at 15:24 |
![]() |
![]() |
![]() |
#392 | |
"Ed Hall"
Dec 2009
Adirondack Mtns
2·32·197 Posts |
![]() Quote:
I've been playing elsewhere lately, so I haven't generated any larger certificates in a while. |
|
![]() |
![]() |
![]() |
#393 |
Jun 2009
10101001012 Posts |
![]()
The really big one came through upload.
|
![]() |
![]() |
![]() |
#394 |
"Ed Hall"
Dec 2009
Adirondack Mtns
354610 Posts |
![]() |
![]() |
![]() |
![]() |
#395 | ||
Apr 2019
5×41 Posts |
![]()
It looks like this has been brought up before, but on the help page, the definition(and spelling) of "primordial" is incorrect.
Quote:
Quote:
So for example: 3### == (3##)# (instead of (3#)## ) Just a suggestion that it could be helpful to at least specify the operator precedence somewhere. |
||
![]() |
![]() |
![]() |
#396 |
Sep 2009
198610 Posts |
![]()
The display of probably primes, http://factordb.com/listtype.php?t=1 is broken if you ask for PRPs below 100 digits. The distribution of probable primes, &ls;= 3000 digits, http://factordb.com/stat_1.php?prp shows 2 such which I can't display.
Also the status page, http://factordb.com/status.php usually doesn't show the smallest PRP, probably due to the same problem. Chris |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
A suggestion for factordb. | enzocreti | FactorDB | 10 | 2021-01-05 19:49 |
Extending Factordb | carpetpool | FactorDB | 6 | 2017-01-23 11:04 |
FactorDB PRP's | smh | FactorDB | 231 | 2015-07-28 02:30 |
bugged sequence in factordb | firejuggler | Aliquot Sequences | 2 | 2010-06-15 14:03 |
FactorDB question | Raman | Factoring | 15 | 2010-01-28 10:24 |