Andrew Hewus Fresh writes:
> On Sat, Jan 30, 2021 at 01:20:25PM -0700, Aaron Bieber wrote:
>>
>> Aaron Bieber writes:
>>
>> > Andrew Hewus Fresh writes:
>> >
>> >> On Tue, Jan 26, 2021 at 05:23:30PM -0700, Aaron Bieber wrote:
>> >>> Hi,
>> >>>
>> >>> Recently a program was found that caused
On Sat, Jan 30, 2021 at 01:20:25PM -0700, Aaron Bieber wrote:
>
> Aaron Bieber writes:
>
> > Andrew Hewus Fresh writes:
> >
> >> On Tue, Jan 26, 2021 at 05:23:30PM -0700, Aaron Bieber wrote:
> >>> Hi,
> >>>
> >>> Recently a program was found that caused breakage in 'portgen go'. The
> >>>
Aaron Bieber writes:
> Andrew Hewus Fresh writes:
>
>> On Tue, Jan 26, 2021 at 05:23:30PM -0700, Aaron Bieber wrote:
>>> Hi,
>>>
>>> Recently a program was found that caused breakage in 'portgen go'. The
>>> breakage was two fold:
>>>
>>> 1) https://proxy.golang.org/qvl.io/promplot/@latest
Andrew Hewus Fresh writes:
> On Tue, Jan 26, 2021 at 05:23:30PM -0700, Aaron Bieber wrote:
>> Hi,
>>
>> Recently a program was found that caused breakage in 'portgen go'. The
>> breakage was two fold:
>>
>> 1) https://proxy.golang.org/qvl.io/promplot/@latest returns unexpected
>>results.
On Tue, Jan 26, 2021 at 05:23:30PM -0700, Aaron Bieber wrote:
> Hi,
>
> Recently a program was found that caused breakage in 'portgen go'. The
> breakage was two fold:
>
> 1) https://proxy.golang.org/qvl.io/promplot/@latest returns unexpected
>results. This caused portgen to bomb out.
> 2)
Hi,
Recently a program was found that caused breakage in 'portgen go'. The
breakage was two fold:
1) https://proxy.golang.org/qvl.io/promplot/@latest returns unexpected
results. This caused portgen to bomb out.
2) Even it 1) had worked, the logic in 'get_ver_info' was broken and it
picked
