Same for me, I haven't received digest for a long time, from quick search
of inbox dates that amr reported are similar in my case as well.
I have checked spam and there is nothing there.
On Thursday, July 11, 2019 at 1:48:46 AM UTC+2, Ian Lance Taylor wrote:
>
> On Wed, Jul 10, 2019 at 4:33 PM
On Sunday, 23 June 2019 20:09:48 UTC+2, Aliaksandr Valialkin wrote:
>
>
>
> On Sun, Jun 23, 2019 at 8:34 PM Jason E. Aten > wrote:
>
>> very nice.
>>
>> https://github.com/klauspost/compress just added zstd all in Go, might
>> be a lovely way to remove the CGO dependency.
>>
>
> I'm keeping eye
Same here. It's been a few days now that I did not receive the email
digests.
Don't know the exact date. Checked spam folder: also not there.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving email
Hi,
I have the following function 'LoadPatternDB' where I am allocating memory
for a C struct.My C struct contains the callback function.
1)I cannot deference the struct in the same func 'LoadPatternDB' because I
get the following error when my callback function is called from C code:
*signal
I also have checked my spam, nothing there related.
However - last night I changed my account to receive each posted message
individually rather than as a daily digest - I am now receiving everything.
Maybe there is an issue with the digest process?
On Thursday, 11 July 2019 00:33:46 UTC+1, amr
I'm in the same boat of not receiving digests for a similar timeframe: both
for golang-nuts and golang-dev.
-Mike
On Wednesday, July 10, 2019 at 4:33:46 PM UTC-7, amr wrote:
>
> I appear to be no longer receiving the email digests daily. I last
> received a daily on 26th June, and then a single
On Thu, Jul 11, 2019 at 1:39 PM Klaus Post wrote:
> On Sunday, 23 June 2019 20:09:48 UTC+2, Aliaksandr Valialkin wrote:
>>
>>
>>
>> On Sun, Jun 23, 2019 at 8:34 PM Jason E. Aten wrote:
>>
>>> very nice.
>>>
>>> https://github.com/klauspost/compress just added zstd all in Go, might
>>> be a love
On Thu, Jul 11, 2019 at 7:16 AM Nitish Saboo wrote:
>
> I have the following function 'LoadPatternDB' where I am allocating memory
> for a C struct.My C struct contains the callback function.
>
> 1)I cannot deference the struct in the same func 'LoadPatternDB' because I
> get the following error
On Thursday, 11 July 2019 17:37:09 UTC+2, Aliaksandr Valialkin wrote:
>
>
>
> This is really great idea! Will try implementing it.
>
> Does github.com/klauspost/compress support all the levels for data
> decompression? VictoriaMetrics varies compression level depending on the
> data type. It woul
On Thu, Jul 11, 2019 at 8:28 AM Michael Rutter wrote:
>
> I'm in the same boat of not receiving digests for a similar timeframe: both
> for golang-nuts and golang-dev.
>
> -Mike
>
> On Wednesday, July 10, 2019 at 4:33:46 PM UTC-7, amr wrote:
>>
>> I appear to be no longer receiving the email dige
Hi Ian,
Following is my C Code:
PatternDB *patterndb[WORKERIDS];
int load_pattern_db(const gchar* filename, key_value_cb cb, int workerId)
{
if(patterndb[workerId] != NULL){
pattern_db_free(patterndb[workerId]);
}
patterndb[workerId] = pattern_db_new();
pattern_db_reload_ruleset(patterndb[worker
I use Klaus' library to decompress ~GiB files that have been compressed by
zstd command line (c/c++ code) at level 19. Works great.
On Thu, Jul 11, 2019 at 9:10 AM Klaus Post wrote:
> On Thursday, 11 July 2019 17:37:09 UTC+2, Aliaksandr Valialkin wrote:
>>
>>
>>
>> This is really great idea! Wil
On Thu, Jul 11, 2019 at 7:29 PM Michael Jones
wrote:
> I use Klaus' library to decompress ~GiB files that have been compressed by
> zstd command line (c/c++ code) at level 19. Works great.
>
Thanks for sharing this information!
> On Thu, Jul 11, 2019 at 9:10 AM Klaus Post wrote:
>
>> On Thurs
details...
celeste:gg mtj$ ls -l ~/corpora/go/corpusZ.tar
-rw-r--r-- 1 mtj staff 92386304 Jul 4 02:27
/Users/mtj/corpora/go/corpusZ.tar
this is the Go corpus compressed in chunks and then gathered as a tar file.
92MB at zstd #19, original size is 752 311 514 bytes. (Zstd compresses some
large
On Thu, Jul 11, 2019 at 9:27 AM Nitish Saboo wrote:
>
> Following is my C Code:
>
> PatternDB *patterndb[WORKERIDS];
>
> int load_pattern_db(const gchar* filename, key_value_cb cb, int workerId)
> {
> if(patterndb[workerId] != NULL){
> pattern_db_free(patterndb[workerId]);
> }
> patterndb[workerId
pattern_db_set_emit_func(patterndb[workerId], pdbtool_pdb_emit_accumulate,
cb);
suggests that cb is being saved away for future use.
yes cb is being saved away and is being used for future use for
callbacks to Go code.
Yes, it's fine to store the address of the C struct on the Go side, if
tha
On Thu, Jul 11, 2019 at 10:58 AM Nitish Saboo wrote:
>
> pattern_db_set_emit_func(patterndb[workerId], pdbtool_pdb_emit_accumulate,
> cb);
> suggests that cb is being saved away for future use.
>
> yes cb is being saved away and is being used for future use for callbacks
> to Go code.
T
This is the code snippet I was talking about:
store := make([]*C.struct_Accumulatedparams, 2)
func (obj Syslogparser) LoadPatternDB(opts Syslog) {
>
> patterndb_path := C.CString(opts.patterndb)
> store[0] = (*C.Accumulatedparams)(C.calloc(1,
C.sizeof_struct_Accumulatedparams))
> store[0].callba
Hi,
I have the following function 'LoadPatternDB' where I am allocating memory
for a C struct.My C struct contains the callback function.
I have the function 'LoadPatternDB' that is running in multiple go
routines.I have written a C wrapper that internally uses syslog-ng methods.
While running th
Thank you very much for pointing to that paper! Somehow I think it will be
referenced in the future with a prefix "seminal" :)
What these guys are proposing in that paper would be closer to (Go-style)
func f() (v value | e error) { ... }
(where "|" could be read as "or" or "union")
with that in
On Thu, Jul 11, 2019 at 8:45 PM Nitish Saboo wrote:
>
> I have the following function 'LoadPatternDB' where I am allocating memory
> for a C struct.My C struct contains the callback function.
> I have the function 'LoadPatternDB' that is running in multiple go
> routines.I have written a C wrap
Michael,
Wonderful reasoning! Your post did reach the goal of "encourage to offer
insights", because now I have "now what?" stuck in my head.
My first reaction was "holy ..., it is an assert after all!" Well, "assert"
+ gentle return instead of panic as you pointed out.
thing is ... how would
On July 12, 2019 4:35:54 AM UTC, Andrey Tcherepanov
wrote:
>What these guys are proposing in that paper would be closer to
>(Go-style)
>func f() (v value | e error) { ... }
>
>(where "|" could be read as "or" or "union")
>
I've thought a tiny bit about how union or sum types would work in Go
I didn't quite get that. Sum-types is an independent issue (and can be made to
work with try!).
They seem to be using a slightly different definition of an error. They are
saying an error is when a function fails even when all its preconditions are
met. If the preconditions are not met, and the
Thanks Sam,
I haven't seen your proposal before, but it looks interesting - you seem to
have put quite a thought into it already.
Funny how these seems to be far-sided things - error handling, generics,
sum types - are coming all related to each other at the end of the day...
Andrey
On Frid
Hi Ian,
syslogparser.go
=
func (obj SyslogParser) LoadPatternDB(opts Syslog, workerId int) {
patterndbpath := C.CString(opts.Patterndb) . <<< . STEP 1
defer C.free(unsafe.Pointer(patterndbpath)) . STEP 2
InitStruct := (*C.Accumulatedparams)(C.calloc(1,
C
26 matches
Mail list logo
