Value is not a integer in policy max bytes

Bug #769993 reported by Marc Boivin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AuthPuppy
Fix Released
Undecided
Unassigned

Bug Description

When trying to set a maximum of 7gb of total consumption per user as a global policy I got "7516192768" is not an integer.

7,516,192,768 being: 7*1024*1024*1024 to get the total number of bytes as asked by the instruction: "Total number of bytes (upload and download) this identity is allowed to transfer."

The weird thing is: Maximum value for a 32bits integer: 4,294,967,295
Yet 2,147,483,648 won't work. In fact, when in GB anything above 1 (1,073,741,824) gets the error "is not an integer."

URL:/policies/create
Plugin: apConnectionPoliciesPlugin version: 0.1.3 (dev)

Marc Boivin (marcboivin)
description: updated
description: updated
Revision history for this message
jackson (neojack34-isf) wrote :

it's weird because we have configured like 10 Gb and 20 Gb policies at ISF without problems

and even a 10TB policy to be use with the splash only, and it's works

Jackson

Revision history for this message
gbastien (gbastien02) wrote :

That problem they have come from a 32 bits server, ours is a 64 bits, but if you enter a value higher than this 9223372036854775807, we have the same problem...

This field should be set as number instead of integer I guess, but we need to see what that does in the database, if the db also have this limitation.

Revision history for this message
Marc Boivin (marcboivin) wrote : Re: [Bug 769993] Re: Value is not a integer in policy max bytes

Can't we use a double or a long?

Sent from my iPhone

On 2011-04-28, at 21:42, gbastien <email address hidden> wrote:

> That problem they have come from a 32 bits server, ours is a 64 bits,
> but if you enter a value higher than this 9223372036854775807, we have
> the same problem...
>
> This field should be set as number instead of integer I guess, but we
> need to see what that does in the database, if the db also have this
> limitation.
>
> --
> You received this bug notification because you are a member of
> AllianceCsfDev, which is the registrant for AuthPuppy.
> https://bugs.launchpad.net/bugs/769993
>
> Title:
> Value is not a integer in policy max bytes

Revision history for this message
Michel Fortin (f-admin-zapbsl-org) wrote :

Erreur d'aiguillage Marc ;-)

1-866-285-9575

Le 2011-04-28 à 23:42, Marc Boivin a écrit :

> Can't we use a double or a long?
>
> Sent from my iPhone
>
> On 2011-04-28, at 21:42, gbastien <email address hidden> wrote:
>
>> That problem they have come from a 32 bits server, ours is a 64 bits,
>> but if you enter a value higher than this 9223372036854775807, we have
>> the same problem...
>>
>> This field should be set as number instead of integer I guess, but we
>> need to see what that does in the database, if the db also have this
>> limitation.
>>
>> --
>> You received this bug notification because you are a member of
>> AllianceCsfDev, which is the registrant for AuthPuppy.
>> https://bugs.launchpad.net/bugs/769993
>>
>> Title:
>> Value is not a integer in policy max bytes
>
> --
> You received this bug notification because you are subscribed to
> AuthPuppy.
> https://bugs.launchpad.net/bugs/769993
>
> Title:
> Value is not a integer in policy max bytes
>
> Status in AuthPuppy authentication server for Wifidog networks:
> New
>
> Bug description:
> When trying to set a maximum of 7gb of total consumption per user as a
> global policy I got "7516192768" is not an integer.
>
> 7,516,192,768 being: 7*1024*1024*1024 to get the total number of bytes
> as asked by the instruction: "Total number of bytes (upload and
> download) this identity is allowed to transfer."
>
> The weird thing is: Maximum value for a 32bits integer: 4,294,967,295
> Yet 2,147,483,648 won't work. In fact, when in GB anything above 1 (1,073,741,824) gets the error "is not an integer."
>
> URL:/policies/create
> Plugin: apConnectionPoliciesPlugin version: 0.1.3 (dev)
>

Revision history for this message
gbastien (gbastien02) wrote :

Released in apConnectionPolicies 0.1.3-alpha

Changed in authpuppy:
status: New → Fix Released
Revision history for this message
Alan Robertson (ninewellsdoctorsmess) wrote :

Hmm - I've just come across this problem in my setup.

I was set previously at 2024000000 (can't remember why as it's not a 1024*1024*1024 multiple of 2!), but I wanted to increase it to 2.5GB. I tried 3221225472 (3GB*1024*1024*1024) and tried various other numbers but none apart from the number I already had in seemed to work.

I was running 0.1.5-alpha and tried updating the plugin to 0.1.6-alpha but it made no difference.

I'm still running AuthPuppy 0.1.0 beta as I haven't worked out how to preserve my existing member database on upgrade yet but wasn't sure if this should make a difference or not...

Thanks

Revision history for this message
jackson (neojack34-isf) wrote :

Hello,

one of our policies actually have a 20000000000 value (20 GB), and it works
flawlessly

At Ile Sans Fil we run authpuppy core 0.1.1 stable

and

<https://auth.ilesansfil.org/policies?>apConnectionPoliciesPlugin
version: 0.1.2 (stable)

I suggest you to update this plugin

also, you may take a look on the 0.1.0 -> 0.1.1 changelog to verify if this
bug has not beed adressed on authpuppy core 0.1.1 stable

Regards
Jackson
Ile Sans Fil technical and volunteers coordinator

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.