labofsahil/github-event-dataset-2012 huggingface dataset:
This isn't totally clear about what `skipped` is. Is it a list of strings, or something more structured?

In the current code, it's a list of strings, but I don't think it should be. Think about this CaseImporter being used from some other code, not the management code. The calling code might want to take some other action about the skipped items besides just printing a line of text somewhere. You should return as much useful structured information as you can. In this case, I think that would mean the dictionary of data for each case that was skipped, plus perhaps a short string describing the reason for skipping (if you were really making this a good programmatic API, there would be a list of constants comprising the possible reasons for a skip, and you'd include one of those constants, not just an arbitrary string). It should be the management command that takes that structured data and turns it into a user-readable string for printing.
On Aug 19, 2012, at 4:22 AM, Alex Rønne Petersen <notifications@github.com> wrote:

> In src/core/sys/posix/semaphore.d:
> 
> > @@ -64,7 +64,17 @@ else version( OSX )
> >  }
> >  else version( FreeBSD )
> >  {
> > -    alias void* sem_t;
> > +    // FBSD-9.0 definition
> > +    struct sem_t
> > +    {
> > +        uint _magic;
> > +        struct _usem
> I don't follow. What effect would that have?
> 
Sure sem_t isn't a pointer to that struct?
Good one; there's still a small risk, I suppose, that someone might have used Long.MIN_VALUE explicitly but, I agree, it's a better solution to use that as a marker instead of the existing -1.

I will fix and squash (because I need to change the commit comment too), but I'll add the diff in a comment here first.
I saw what you were talking about, then I couldn't repo the issue. Might be a browser rendering issue.
Regardless, I've verified there are not tabs in the code.
out should be named as byteArrayOutputStream
Force selection should be moved upwards.
詳しい解説をありがとうございます。大変勉強になりました。

用語としては"nominal"に対応するもの、という文脈を抜かして"structural"（構造的）という言葉を見ると、意味が広すぎるのが敗因なんでしょうね。どうしても、「構造がない型って何だよ…」という気分になってしまう（笑。

あるいは、"typing"を正確に訳して「構造的部分型付け」とか？ さらに長くなって誰が得をするんだという感じですが。
`adds` -> `add`
`through Event System` -> `through the Event System`
Why are we changing the interface to `test_rules`?
hmm, indeed. The top is stripped.
Better debug traces :D
Instead disconnect all nodes, you should disconnect only the last one if it's connected this UAToken on the same or on another WS

On the other hand, If the connection is with WakeUp, we shouldn't close connection and only upgrade it to websocket or update wakeup data
what about the case where priorities are the same ?
Why _c.TEMP? THere's no preprocessing here
所谓优雅流程，就是只让pdf等文件创建临时文件，而其它文件（比如java，c，txt）等等都不创建临时文件。
也许把copy_content_to()的调用相关代码封装成一个函数就行了？

ps. 这周内一定要搞定这个！
Yes, 2.2.* would be it.
The problem arises with doctrine/doctrine-bundle and doctrine/orm - in the case of doctrine/doctrine-bundle which requires 2.2.*
The requirement would need to be fixed either here or in doctrine-bundle for it to work *now*.
Instead of re-adding activeCard and transitionCard, just change the frame of activeCard. Fix transitionCard position and use it as a background view
I don't think circular groups are a problem. We could forbid them but they should be harmless because:

- only one rule is applied for a given cascade (rules are not applied recursively)
- we stop validating when the same instance / property is validated with the same group in a given path (existing rule)

I am more concerned about group sequence. I need to think it through to see if the sequence is applied before the conversion and if group sequence groups are allowed as conversion rules.
hmm, I see it in the opposite way. I think < > are common notation to indicate a placeholder/variable. Not having them made my reading "trip over". I also think that at other places you used < >. If it just wouldn't be so damn hard to comment/review docbook code on GitHub ;-)
this should probably be const
At this moment we are basically thinking that - if I method call to the API need to listen for events, we can call start event (before we do any native code execution). Once the method call is done returning, we can call stop event.

The stop event is going to be called from the JavaScript side.
First I removed the parameter, then put it back. Put back the docstring, too, now.
needed_update = 0
Comme c'est un before_save, le champ va être sauvé d'office.
I think I added this, but anyway, scratchd needs to get added. As well as VAR.
Is there a reason to reinvent `get_model` from Django here?
Are we returning a number to the user? I thought that was just on the WP to index side to manage the callbacks of the toasts?
Not sure we should get rid of vendor completely - not everything is available from packagist.
Why Changelogs are wiped away with this commit? How does adding validation relate to getting rid of Change logs? If there's a good reason, I'm all for it. Otherwise, perhaps this commit should be associated to corresponding migration and neither commit should be part of this pull req?
Поначалу хотел сделать, чтобы функция, которая выполняется при удачном завершении воркера принималась в конструкторе, но потом переделал так, чтобы она передавалась при каждом вызове. Тут её можно удалить.
Not that it really matters but "rim:permissions" gets parsed as an object not an array.

`data["rim:permissions"] = {};`
#ifndef DElTAROBOTNODE_H
#define DELTAROBOTNODE_H

typo
just `renders the data` as it can be no table and no list, too