DRAFT: primary spec and extension profiles

Hi all,
As per the strategy I've enumerated in https://lists.w3.org/Archives/Public/public-webid/2023Nov/0121.html , I'm opening this PR as the "root" PR for my chair / editor work in trying to get to WebID 1.0 following the superspec / subspecs approach proposed, amongst others, in https://lists.w3.org/Archives/Public/public-webid/2023Jul/0056.html .
Though there is still lots of work, I do feel it's time to condense and materialize the growing centers of consensus into a tangible starting point for further work. To that end, a copy of the primary spec that is always up to date with this PR is available at https://jacoscaz.com/WebID/primary-spec/webid.html . I invite you to have a look and provide as much feedback as you can.
This PR brings a completely new approach that profoundly diverges from that upon which the spec has been built so far while aiming to maintain backward compatibility with current implementations. As such, the first commit is much more foundational in nature than your average commit and, in a different world, would have made for the scaffolding-oriented "first commit" in a completely new repository. Looking at it purely in terms of code changes doesn't make much sense.
This PR is obviously a draft and cannot be merged as-is. On top of being incomplete and requiring significant more work and even more discussion, I've also added Tufte-style sidenotes to host my own editing notes for maximum transparency. These are only temporary and not meant to end up in the final document, should this PR ever get merged.
In terms of issues, this PR touches upon basically all of our open issues and, if and when merged, would resolve many of them.
Should this PR gather the support of enough active participants as a good starting point for further work I would build upon it through much smaller and narrowly scoped commits, easily understood by merely looking at their respective deltas.
I'm very aware that this PR is a very unorthodox one. However, as I've argued in the past, I do not believe that the extent of the changes in consensus and in the concept of WebID that have occurred in the past few months / years can be efficiently and effectively captured by a long list of micro-commits. I kindly ask you to keep an open mind and, if you can, indulge this effort for a few weeks. It only takes a few minutes to go through the primary spec as it is right now.
That said, as the group chair I ultimately serve the group. If the group believes this to be an inappropriate course of action, I'll close this PR and evaluate my options.
@namedgraph @melvincarvalho @acoburn @jonassmedegaard @kidehen @TallTed @woutermont

This looks great, well done!

either the document's foaf:primaryTopic or the document's schema:mainEntity

I think this is too specific.  I would prefer a more general statement here, if possible.
Then have an examples section which should be in JSON.  I would prefer a simple example using schema:mainEntityOfPage included, which I think is the simplest possible example, with a broadly adopted vocab.  Other examples could be added too.
Otherwise looks great.  I can live with any version of this spec, whatever the group decides (including wrt to IRIs, if it doesnt take too long).  I'll sign off here as, from my POV WebID, is mission complete.  Congrats and thanks for all the hard work!

I believe it would be best to keep the existing structure / documents in place, and carry out this approach in its own document or branch until things are actually settled. I don't find it appropriate to wipe stuff for a number of reasons.
The Group should consider progressing 1.0 ED and the exploration on new specifications / splitting of the specification. The core of WebID has been instrumental, and its continuity is important. There's considerable reliance on the current work; dependency by other specifications (e.g., Solid), research, and implementations. Personally, I'm inclined to support the ongoing work on 1.0 ED and am willing to contribute as an editor.
That aside, there are a number of outstanding issues / comments that  justifies a halt on 1.0 ED, let alone a shuffling and splitting of the work. What I see is cherry picking, and consensus is being waved without on good grounds or process.
I say this because I'm genuinely concerned about a major fragmentation ahead, and quite possibly the WebID (as we know it) falling apart.
Happy to join a audio/video meeting where we can air a bunch of intertwined concerns, and communicate better.

WebID defines a standard means by which user agents and servers interact to establish a user's identity, ensuring a structured, decentralized approach for identity discovery on the web.

If find that confusing, bearing in mind that a WebID is an HTTP based identifier for unambiguously naming an agent.
Since this is about the Web 1.0 Specification, how about.
This specification presents a standardized approach for naming agents unambiguously, establishing a foundation for loosely-coupled identity authenticity protocols that utilize the existing Web infrastructure.

This specification presents a standardized approach for naming agents unambiguously, establishing a foundation for loosely-coupled identity authenticity protocols that utilize existing Web infrastructure.

Looks good!  Not opposed to the term unambiguous, but FYI: I opened an issue here to try and understand its significance, or why it was important to you.

I do not feel comfortable with this "clean slate"-ish approach. I fear that by rewriting from scratch there is a real risk that we miss out on wisdom of earlier progress. I cannot point at anything in specific, and that is exactly the point making me nervous about the approach: It may make it easier for us right now to make a decision, that we cannot really see what we are looking away from, only what is put on the table in front of us, but I am not convinced that ease of making a decision should be the highest priority.
I hope that we will agree to move forward with roughly what you have put forward now, but I think we would do so as well if it was redone as a series of commits each with a semantically more narrow aim.
I am hereby offering my help to try construct such reenactment-in-git of your thought+editing process.  If you will allow me to pick your brain in doing that.
To clarify, my intent here is not to try steer you into any other direction, but to end at the exact same point as you have presented here - I just wish for this git repository to contain a more elaborate and granular commit history, both for our more educated decision making process, and also for those coming later and curious how we ended where we did.
You have my email - please get in touch if you find it relevant.
Otherwise, I will do as you requested and simply give it a few weeks to let it sink in - but I can say ahead that I doubt that I will change my mind on the powers of revision control in document editing within 14 days.

consensus is being waved without on good grounds or process

IMHO this is uncharitable to @jacoscaz who has gone out of his way first to establish lazy consensus, and they to carefully facilitate the will of the group.  I know of no W3C chair that has done this more carefully or fairly.

I appreciate @jacoscaz work but I'm also wondering why the existing WebID specification documents are not reused?

Lots of feedback already - thanks all! I'll address technical feedback separately and at a later date. For the time being, just a few words on process.
The reason behind the "clean slate" approach is that I believe the extent of the changes presented here, if addressed through micro-commits, would have lead to a virtually infinite amount of re-hashing of topics that we've already discussed in depth, a "distraction" that would have effectively stalled the effort. The history and interpersonal dynamics of this group are ample proof that such a thing would be very likely to happen.
Note that I'm not saying that discussion is bad! Not at all! It can become a blocker, though, if we fail to direct it and progress beyond it. Discussion alone does not get to WebID 1.0.
Additionally, and I acknowledge that this is very subjective, I'm not sure my brain would have been able to produce this PR without the clean slate approach. Tracking the conversation and adjusting the document to new consensus is, in itself, challenging. Doing so across multiple commits while trying to maintain a sane history would have been well beyond my abilities.
That said, if enough participant find this PR palatable I might be able to rework it into a sequence of much smaller commits that would get to the same exact place, as suggested by @jonassmedegaard (I think?). I would not be willing to open a PR for each of those commits but, if we all agree about the end result, I could go back to the beginning and get there in a few more steps.
As for the files, @namedgraph , given the extent of the changes and my own sensibilities towards preserving the history of this repository, I thought it best to "freeze" the current spec and its history for historical purposes and work on new files alone. I'd happy to make more invasive changes to the current documents if that's what the group wants, though.

That said, if enough participant find this PR palatable I might be able to rework it into a sequence of much smaller commits that would get to the same exact place, as suggested by @jonassmedegaard (I think?). I would not be willing to open a PR for each of those commits but, if we all agree about the end result, I could go back to the beginning and get there in a few more steps.

If you could spare the energy in doing that, I indeed think it would be very helpful.
Not helpful as in giving an opportunity to micromanage your work by taking it apart and discussing each commit as if it would be sensible to pick selectively - I do trust your judgement when deciding that it is an all-or-nothing proposal you want to make.
Instead, helpful as in allowing us and future interested parties to better understand what this change consists of.
And in case you missed that bit, I am also offering to aid you in doing the tedious work of reding your change as multiple commits. I would be delighted for this opportunity to collaborate closely with you, if you see a possibility for that to ease the added burden.

if we all agree about the end result, I could go back to the beginning and get there in a few more steps.

Oh, and to clarify: It would be helpful to me to have a more granular changeset before deciding on whether your wholesale proposal is reasonable to me, not only for posterity.
If you think that is not doable (e.g. because you want the next weeks with your family, or perhaps because you fear that providing granularity will invite for unwanted nitpicking discussions despite my optimistic view on that) then it would be helpful that you clarify that intent of yours.  Because then I will spend time reverse engineering your all-at-once commit on my own, privately, to aid in my own understanding (but then wasting the potential benefit in others having access to my insights).

Lots of feedback already - thanks all! I'll address technical feedback separately and at a later date. For the time being, just a few words on process.
The reason behind the "clean slate" approach is that I believe the extent of the changes presented here, if addressed through micro-commits, would have lead to a virtually infinite amount of re-hashing of topics that we've already discussed in depth, a "distraction" that would have effectively stalled the effort. The history and interpersonal dynamics of this group are ample proof that such a thing would be very likely to happen.

As far as I can recall, the current spec only a few niggling issues to be rectified:

MUST for Turtle Notation
Tight-coupling with a specific authentication protocol i.e., WebID-TLS

Those issues don't warrant a re-write that will inevitably lose important insights from the past.
-1 to a wholesale re-write.

To be more explicit than my +1 on @kidehen's comment —
-1 for any kind of wholesale re-write; the existing ED needs only relatively minor revision to become acceptable to me.

Hi all! Apologies for the absence, I had to tend to some unexpected personal matters during the holidays.

For the record, the existing spec only needs minor changes. It never required a wholesale re-write.

@kidehen @TallTed obviously I disagree, otherwise I would not have asked for feedback on a PR like this. If minor changes were all that is needed to finalize the existing spec, shouldn't that have happened years ago? To me, threads like https://github.com/w3c/WebID/issues/3, and that's just an example out of many, read as if the changes required to achieve substantial consensus across active participants are not that minor.
That said, this PR clearly doesn't stand a chance at gathering enough consensus, at least as it is right now. Let's see if I can do anything to make it more palatable.

If we all agree about the end result, I could go back to the beginning and get there in a few more steps.

Oh, and to clarify: It would be helpful to me to have a more granular changeset before deciding on whether your wholesale proposal is reasonable to me, not only for posterity.

@jonassmedegaard I understand, thank you for clarifying. I don't necessarily share your perspective, given that both the existing spec and what I am proposing in this PR can be fully read through in limited amounts of time, but I see the logic behind it. I also deeply appreciate your offer to help out.
So, what if I were to refactor this PR so as to split the current commit into a sequence of much smaller and more focused commits, building upon the existing spec rather than starting off of a new document? I think this would address the feedback from @namedgraph , @jonassmedegaard  and maybe @melvincarvalho (I can't tell from the +1s), at least insofar as getting the PR to a point in which they would be willing to review it.
However, I would still end up rewriting most if not all of the existing spec and I am afraid this would still not be enough for @kidehen , @TallTed and @csarven to contemplate reviewing it. I am not sure as to how to address this, though, as I am honestly and whole heartedly convinced that group consensus lies well beyond any minor change we could make to the existing spec.
As for your offer to help, @jonassmedegaard, I think I'd be more efficient in doing an initial refactor on my own but perhaps I might ask you for your feedback to iterate on it before soliciting the feedback of others? Iterating as a pair would be faster than doing so with the entire group and I suspect your sensibility is shared by a few others.

@kidehen @TallTed obviously I disagree, otherwise I would not have asked for feedback on a PR like this. If minor changes were all that is needed to finalize the existing spec, shouldn't that have happened years ago?

These minor changes never happened because of the process required to enact them. Once again, this spec doesn't need a wholesale rewrite.

@kidehen @TallTed obviously I disagree, otherwise I would not have asked for feedback on a PR like this. If minor changes were all that is needed to finalize the existing spec, shouldn't that have happened years ago? To me, threads like https://github.com/w3c/WebID/issues/3, and that's just an example out of many, read as if the changes required to achieve substantial consensus across active participants are not that minor.

Today's "active participants" are not yesterday's nor yesteryear's.
Substantial consensus existed for the bulk of the existing draft document, but we were unable to overcome the sticking points before the previous WebID WG's charter expired. (I know this because I was an active participant in that WG.)
Regrettably, the existing draft document appeared (and to a somewhat lesser degree, still does appear) as if it were more mature than it is/was. This caused a number of people to act as if it was in full TR status, even though a bit of web digging would have revealed that it was not even CR (Candidate Recommendation), never mind PR (Proposed Recommendation) nor TR (Technical Recommendation). This has led to an indeterminate (but definitely greater than zero) number of implementations now in the wild, based on the existing draft. These include derivative works, such as WebID-TLS and WebID-OIDC.
I am typically pitiless for implementers of draft specifications, and argue that breaking changes are fine when trying to bring such drafts to full TR status. I do not feel that way about this spec because such implementers may well have relied on the existing draft in full good faith, believing its apparent visual status without researching whether that appearance was accurate.
This is why I feel that the fewer changes we make to the existing draft, the better. Some changes are necessary; these are the "minor changes" discussed above by @kidehen, @csarven, and myself, and maybe a few other "minor changes".
Again, wholesale revision is not necessary.

I'm sorry, @jacoscaz, but I must agree with the majority here: this approach is not doable. Believe me, I know the appeal, I often have the urge to do the same, but there are a number of very good reasons not to.
First of all, there is no consensus about the amount of changes that need to happen. Even most recently active issues together can be incorporated with small changes to a few lines. Moreover, while a handful of very active people have reacted positively to most, in the larger scale of this spec we are outnumbered by all the clever people who came before us in reaching consensus on the current draft.
Secondly, even though I'd say you have some editorial freedom in the way you bundle changes, doing it this way no one really knows what you have changed exactly in the content. Moreover, even if we manually diff everything, so much has changed that we can not react on a granular level (or, if we did so, this PR could take another few years to work through).
Thirdly, there's the point of tracking history, which @csarven already raised. We have an obligation to present and future collaborators to keep track of what we do, based on which decisions, based on which reasoning etc. Moreover, I would say we have the obligation to do so in an accessible way. This is why I would urge you not just to split this in multiple commits, but also to treat those in separate PRs (if you ever tried to track changes through a long straight line of commits, you know why).

I think the above points reflect the opinions of most of the currently active members. However, I also want to address the reasons you raise for using this approach, since I believe they contain valid concerns.

[@jacoscaz:] I do not believe that the extent of the changes in consensus and in the concept of WebID that have occurred in the past few months / years can be efficiently and effectively captured by a long list of micro-commits.

Here I believe you are wrong. Other CGs clearly show that it is possible to capture and manage a lot of small changes on a one-per-PR basis. However, I think your real concern is not the management of such PRs, but rather what you say a bit later:

[@jacoscaz:] I believe the extent of the changes presented here, if addressed through micro-commits, would have lead to a virtually infinite amount of re-hashing of topics that we've already discussed in depth, a "distraction" that would have effectively stalled the effort.

This is a valid concern. PRs often become yet another place to discuss the topic their change is about, another hurdle in going from a good idea to an accepted and enacted change. However, rather than throwing away all benefits that come with PRs (see above), we could clearly communicate that the PRs are really meant to already contain the concensus (almost) reached in their corresponding issue, and will only allow for minor finetuning. Moreover, given the tremendous job you already did in manouvering towards consensus in the issues, I don't think this will turn out to be such a problem.

Concretely, I would propose to do the following:

Leave the folder structure as is. There is really no need to stuff all the work up till now in a "legacy" folder. Working with regular draft snapshots is a well known mechanism used by many CGs, so why not simply work on the existing files?

Open one PR to add the top-level README, where it can evolve organically to a great introductory text.

Open another PR to update the License dates. I know, it's super minor, but that also means that it will be done in no time.

Open a PR to get rid of redundant files (spec/.default-acl, spec/diff-20111123.html, spec/style.css, spec/W3C-ED.css, and possibly w3c.json).

Open one PR for each of the recently active issues where you feel consensus has been reached. If you feel you need help formulating that consensus in a concrete change to an existing file, a lot of us would be very willing to extend a hand.

Today's "active participants" are not yesterday's nor yesteryear's.

May I ask you to expand on this, @TallTed ? I'm not sure I understand the underlying message. If we are to bring WebID forward, I believe it would be fair to do so with those that are active today while keeping an eye towards backward compatibility.

Again, wholesale revision is not necessary.

Once again, this spec doesn't need a wholesale rewrite.

I'm sorry, @jacoscaz, but I must agree with the majority here: this approach is not doable.

The group has spoken and the chair serves the group. Obviously, I bring my own set of experiences to the table which strongly discourage me from doing what the group is asking, given its very history, so I tried something different first. Doesn't mean I have any right to do things my way.

Here I believe you are wrong. Other CGs clearly show that it is possible to capture and manage a lot of small changes on a one-per-PR basis.

Indeed they do, although I am not aware of a CG with a history comparable to this one.

Moreover, given the tremendous job you already did in manouvering towards consensus in the issues, I don't think this will turn out to be such a problem.

This sounds exceedingly optimistic to me but, you know what? It's the end of the year, beginning of a new year - let's start with some optimism. Btw @woutermont, nothing to be sorry about. Once again, excellent feedback.

Leave the folder structure as is. There is really no need to stuff all the work up till now in a "legacy" folder. Working with regular draft snapshots is a well known mechanism used by many CGs, so why not simply work on the existing files?
Open one PR to add the top-level README, where it can evolve organically to a great introductory text.
Open another PR to update the License dates. I know, it's super minor, but that also means that it will be done in no time.
Open a PR to get rid of redundant files (spec/.default-acl, spec/diff-20111123.html, spec/style.css, spec/W3C-ED.css, and possibly w3c.json).
Open one PR for each of the recently active issues where you feel consensus has been reached. If you feel you need help formulating that consensus in a concrete change to an existing file, a lot of us would be very willing to extend a hand.

Feels like a good plan! I'll give it a try. If the discussion within each individual PR were to degenerate into endless debate as I fear it might, I will relinquish the chair as per my application as unable to achieve the goal I set out for my chairmanship.

Well, I think I speak for everyone here when I say we would be extremely sad to see you go so soon, so let's all do our best to keep working towards consensus 😉

Not to discourage anyone but I think it is worthwhile to put some emphasis on a general understanding in the group (even if it is not unanimous). This is not particularly unique to the WebID CG but a general practise in open standards development. Incremental changes and demonstrating open discussion and decision making - essentially a clear record of decisions/understands/intents.
If I may say as an example, what happened in this PR is a very similar to the concerns that were raised in https://github.com/w3c/WebID/pull/27 . If we can isolate or distinguish between clarifications that are needed from new proposals, that'd helps us apply a process that's meaningful or most adequate.

There is consensus to create a superset and subset spec, and that should be completed by the group, either as a Note, or preferably as a REC.
A reason is that it allows WebID to have the much needed JSON-LD upgrade.  JSON is not mentioned anywhere in the 2014 spec, and it needs to be in 2024.
The current WebID spec will not change much, and becomes the Turtle mandated spec, which gets handed over to the Solid WG, and they can have full control of it.  The superset should be light and not impose too much on them, or anyone else.  In essence it's just a spec that says that a WebID is a URI that denotes an agent, with some examples.
This CG becomes unblocked and can move forward with future subset specs in the future, and the main superset spec need not change for a very long time.
Everyone gets what they want.

@jacoscaz thank you very much for this effort.  If you dont mind, we've forked this early draft, to the solid-lite project.  This has completley unblocked our work and will enable us to move forward with new innovation.  We will still track the work going on in the CG and aim to align with ongoing group consensus.  But for now we can work without blockers, and we owe you a huge thank you for that!

@melvincarvalho that's absolutely fine! Do try to preserve the history, though, or at least some sense of all of those who participated over the years.


1.20.1 compatibility

update some files to allow the bot to connect via 1.20.1

That shouldn't be hard to implement, although I am not really maintaining this project at the moment. If you want i can do it anyway.


favico reload fix

This should take care of the constant reload of favico. If they're included in the manifest it will stop trying to reload them, always.
Possible related issue can be found here.
Let me know if this is alright - worked fine for me on Chrome Safari and Firefox.

Thanks for this @elodszopos
My one concern with this though is that the manifest is not supported across all/older browsers. Do you know much about this? That being said, these icons are primarily used in a PWA context right? So perhaps the answer is to have a "standard" icon fallback that is included the react-helmet instance.
Sorry if this feels like drunken waffling by myself... 😀

Did some more digging and found this.
A fallback would be advised. Not entirely certain where to put it though, or how to solve it.

Agree with @codepunkt on this.
It's great that you have highlighted the issue again, and perhaps we can all move forward together to try and resolve it.

Fixed in next 🎉


added user repo to the badge relases and add push and pull on main test

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


OSError: [Errno 22] failed to open netns using veth interfaces (Fedora 18 host)

I'm using the topo-extra-files/examples/v2/3-node.ymlsample file.  The host is Fedora 18 with a 4.9.76 kernel.  I can use the bridge driver to get around this issue for now, it seems.
Here's the last part of docker-topo --debug --create topo-extra-files/examples/v2/3-node.yml
DEBUG:__main__: Attaching container 3-node_cEOS-1 interface eth1 to its link
DEBUG:__main__: Connecting veth-type link to 3-node_cEOS-1
DEBUG:__main__:Connecting 3-node_net-1-a to 3-node_cEOS-1
DEBUG:__main__:Create an interface for container 3-node_cEOS-1: {'ifname': 'eth1', 'stats': None, 'protinfo': None, 'map': None, 'linkinfo': None, 'stats64': None, 'af_spec': None, 'net_ns_fd': 30, 'event': None, 'flags': 4099, '-ports': set(), '+ports': set(), '-ipaddr': set(), '+ipaddr': set(), '-vlans': set(), '+vlans': set()}
Traceback (most recent call last):
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 840, in <module>
    main()
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 775, in main
    started = [device.start() == 0 for (name, device) in devices.items()]
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 775, in <listcomp>
    started = [device.start() == 0 for (name, device) in devices.items()]
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 354, in start
    self._attach()
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 371, in _attach
    link.connect(self, interface)
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 659, in connect
    self.network.connect(device, interface)
  File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 601, in connect
    with IPDB(nl=NetNS(ns_name)) as ns:
  File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/netns/nslink.py", line 170, in __init__
    super(NetNS, self).__init__(trnsp_in, trnsp_out)
  File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/iproute/linux.py", line 127, in __init__
    super(RTNL_API, self).__init__(*argv, **kwarg)
  File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/remote/__init__.py", line 200, in __init__
    raise init['error']
OSError: [Errno 22] failed to open netns: 'e5df19bfe142'

Full log: debug.txt
I also confirmed that e5df19bfe142 existed as /var/run/docker/netns/e5df19bfe142

docker-topo use pyroute2 underneath to talk to netlink api. this seems like an issue with pyroute2. Just to confirm, is this 32-bit x86 Fedora 18? and have you tried running the same as sudo ? there seems to be an opened issue which looks a bit similar.

Hmm, I'd also looked at that thread earlier, and so tried running it with/without sudo.  This is 64-bit Fedora 18.
I just tried the repro steps they provided and that test was OK:
(testdir) [wade@us116 config]$ sudo ip netns add test
(testdir) [wade@us116 config]$ sudo python3 rep.py
<pyroute2.ipdb.main.IPDB object at 0x7fd2d9fc36d8>

Perhaps it's something specific to the docker installation / version, then.


Empty command in git.py does not show help message

According to the following line in examples/git/git.py
elif args['<command>'] in ['help', None]:

running ./git.py should give the same message as running ./git.py help. But it gives only the usage message instead.
Also, the line
See 'git help <command>' for more information on a specific command.

in the description does not work as expected.

I've been puzzled by this as well.
$ ./git.py help      2>&1 | wc -l
      36
$ ./git.py           2>&1 | wc -l
       5
$ ./git.py --help    2>&1 | wc -l
      21

The first two (['help', None]) should map to the last one (--help), but all three give widely different outputs.
@gtarabat The last line (See 'git help ... for more information on a specific command.) is printed when you set help=True and run ./git.py --help:
args = docopt(__doc__,
    version='git version <IP_ADDRESS>',
    help=True,
    options_first=True)

@beierman help=True is the default value. The list line is printed as expected when I run ./git.py --help.
What I mean with the last line is that running git help <command> does not give the help message for the <command>.


Question About vtab Implementations

Hello,
I'm implementing a vtab extension and am reviewing other implementations for examples. I have a question about the cursor initialization in csvtab.
In csvtab, the cursor is initialized as follows:
CsvTabCursor {
    base: ffi::sqlite3_vtab_cursor::default(),
    ...
}

It looks like CsvTabCursor.base is initialized with zeros (Default is implemented using unsafe { mem::zeroes() }). However, the SQLite documentation indicates that the first field of the struct, base.pVtab, should be a pointer to the vtable for the cursor. There is also a Rust method that accesses this pointer:
/// Accessor to the associated virtual table.
fn vtab(&self) -> &CsvTab {
    unsafe { &*(self.base.pVtab as *const CsvTab) }
}

My question is: Should CsvTabCursor::new() be setting self.base.pVtab? If not, where is it being set? I also don't see it being set in rust_open().
Thank you for your help!

Not related to rusqlite...
See official CSV extension:
https://github.com/sqlite/sqlite/blob/1ffd7ed54ff340039fbc0e809a784789048bdf8c/ext/misc/csv.c#L322
https://github.com/sqlite/sqlite/blob/1ffd7ed54ff340039fbc0e809a784789048bdf8c/ext/misc/csv.c#L708 (base is not set)
And SQLite core:
https://github.com/sqlite/sqlite/blob/1ffd7ed54ff340039fbc0e809a784789048bdf8c/src/vdbe.c#L8192-L8197

Thank you!


Stutter in fullscreen EDGE

Stutterring in fullscreen.
No issue when not on fullscreen.
Im going to try in Firefox & Chrome.
Keep you tune.

Hi, can you retry with version 0.6 please


BUG: something wrong with spatial_colors legend

Something wrong with the legend in files that should be fairly regular - no bad channels, all EEG ... but the legend colors seem completely random. (The line colors are fine!)
The tests look fine and another experiment of mine looks fine, it's only for some layouts.

I'll see if I can find what it's about, but I'm also attaching an evoked file that has the issue: bad_example-ave.fif.gz
@jaeilepp

Jakko, the problem is  that names = np.intersect1d(layout.names, used_nm) returns a sorted list, but we don't want them to be sorted, but in original order (10/20 EEG chans have nonalphabetic order, it only works for MEG and some EEG layouts due to alphabetic channel layouts) . I'm not sure I understand the exact purpose of the line, and what could happen for specific channel types (the ones we need _clean_names for). Can we do names = [name for name in layout.names if name in used_nm] instead, or does that break something? It fixes my problems.

sounds like the good fix !
A


Android OS 5 Crash

The audio_session library version 0.1.3 is causing a crash whenever its being defined in android os 5, downgrading fixed the issue

Do you have any error message that could help pinpoint the issue?

I've done a sweep of the code and found a couple of APIs that were not guarded to the SDK level. The latest commit should fix that.

I've done a sweep of the code and found a couple of APIs that were not guarded to the SDK level. The latest commit should fix that.

oh good then, the crash happened in the definition of the AudioSessionPlugin library in the android side anyway
flutterEngine.getPlugins().add(new com.ryanheise.audio_session.AudioSessionPlugin());
i think it might be because of what you mentioned. thanks

I've just published release 0.1.4 with the above commit. Let me know how it goes, and if you still run into issues.

I've just published release 0.1.4 with the above commit. Let me know how it goes, and if you still run into issues.

unfortunately it didn't work the AudioSessionPlugin can't be instantiated the error being shown in the log is this:
I/art: Rejecting re-init on previously-failed class java.lang.Class<com.ryanheise.audio_session.AndroidAudioManager$Singleton$1> I/art: Rejecting re-init on previously-failed class java.lang.Class<com.ryanheise.audio_session.AndroidAudioManager$Singleton$1> I/art: Rejecting re-init on previously-failed class java.lang.Class<com.ryanheise.audio_session.AndroidAudioManager$Singleton$1> W/GeneratedPluginsRegister: Tried to automatically register plugins with FlutterEngine (io.flutter.embedding.engine.FlutterEngine@2efb4784) but could not find and invoke the GeneratedPluginRegistrant. V/FA: Activity resumed, time: 1812723

Thanks, that gives me a good lead to go on.

I've just made another fix attempt, although I haven't published it yet since it might be good to hear whether it works for you.
To try it out from Git master you can use this dependency in your pubspec.yaml:
  audio_session:
    git:
      url: https://github.com/ryanheise/audio_session.git

Note that if you use any other plugins that internally use audio_session, you'll also need to add a dependency override to force them to use this version of audio_session:
dependency_overrides:
  audio_session:
    git:
      url: https://github.com/ryanheise/audio_session.git

Let me know how it goes and if all is good I'll publish another release.

I'm using just_audio library that is dependant on audio_session library. I added the dependency override from the git master and everything is working fine now. thanks

FYI this has now been released in 0.1.5, thanks very much for reporting the issue.


Hot patches

You can receive hot patches as follows:

download
replace Control-Freak/Code/client/src/xcf/dojo/xcf.js with that file
press F5 to reload the IDE

I am adding a menu entry doing this for you sometime.
g

did it

ok, i added a mini update action:

this will work for small updates and i can respond within minutes to bugs/change requests. For now, you will have to make a full update.
There is also a problem with data/drivers/system/DriverBase.js :
this file changes very rarely but if it changes, you will have to use the new version instead the one of your data directory (which you usually copy over the new one).

how do I know when update is complete? Can you display status bar/message?

Do I need to restart server after update?

yes, you better restart all, but most of the time F5 in the IDE for reload is enough.
you can restart as soon the message "Restart all now" appears, or when all items are marked as "Finish"


Is there a way to get the error type in the errors list

right now validate gives me something like :
{'password': ['Field must be at least 8 characters long',
                     'This is a custom validator'],
 'email': ['Field is required']}

but I would like to be able to get something more like :
{'password': { 'minlength': 'Field must be at least 8 characters long',
                      'custom1': 'This is a custom validator'},
 'email': {'required': 'Field is required'}}

I tried to customize the message for the validators in order to return ['key': 'value'] with DataRequired(['required': ' something something'], but :

the validators returning message % dict(....) won't accept to '%' between a list and a dict.
it doesn't permit me to keep the original message wtform returns.

I ended up doing this:
from wtforms.validators import DataRequired, Length, Email
from wtforms.validators import ValidationError, StopValidation

class MetaValidator(object):
    def __call__(self, *args, **kwargs):
        try:
            print(super(MetaValidator, self).__call__(*args, **kwargs))
        except (StopValidation, ValidationError) as e:
            print(("we are ", self.error_type, e))
            raise type(e)([self.error_type, e.message])

class DataRequired2(MetaValidator, DataRequired):
    """ So we can set an error type to use answers in ngMessage """
    error_type = 'required'

class Length2(Length, MetaValidator):
    """ So we can set an error type to use answers in ngMessage """
    error_type = 'length'

class Email2(Email, MetaValidator):
    """ So we can set an error type to use answers in ngMessage """
    error_type = 'email'

class BaseForm(Form):
    @property
    def errors_obj(self):
        _errors = {}
        for field_name, error_messages in self.errors.iteritems():
            _errors[field_name] = {}
            _errors[field_name].update(error_messages)
        return _errors

not sure if it is a wanted feature or not. If it is, I don't mind doing a PR

please things which are not bug reports at http://stackoverflow.com/ or other support forums!


RDFStoreTest.testMultiThreadedAccess may be silently failing

(Migrated from https://openrdf.atlassian.net/browse/SES-2289 )
The testMultiThreadedAccess test in RDFStoreTest may be silently failing (with a stacktrace to the console), and most of the test doesn't seem to be executed.
A full multi-threaded test would need to use CountDownLatch or similar to make the test consistent. The current use of a busy-wait loop and Thread.sleep testing con.isActive doesn't seem to work to make sure that only one thread gets a transaction open at one time.
The exception printed to the console is an AssertionError with the following trace:
org.openrdf.sail.SailException: a transaction is already active on this connection.
at org.openrdf.sail.helpers.AbstractSailConnection.begin(AbstractSailConnection.java:196)
at org.openrdf.sail.helpers.AbstractSailConnection.begin(AbstractSailConnection.java:170)
at org.openrdf.sail.RDFStoreTest$1.run(RDFStoreTest.java:741)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "B (parallel)" java.lang.AssertionError: a transaction is already active on this connection.
at org.junit.Assert.fail(Assert.java:88)
at org.openrdf.sail.RDFStoreTest$1.run(RDFStoreTest.java:764)
at java.lang.Thread.run(Thread.java:745)
I have only tested it on master right now (just after 4.0.0-M1), but it may also apply to earlier versions.

This test has been disabled for a while now as it is fundamentally flawed anyway.


[vscode-graphql] fix Svelte support

Fixes #2857
The LSP server wasn't registered for svelte files.
Note: the PR does not have tests

Sorry, I committed using the wrong account, I'll create a new PR.


AXI Lite Demo 32-bit Address

Small change to the AXI Lite Demo.
I found out when creating an IP core for Xilinx's Vivado Block Diagram that the core worked well until I tried to access an address > 0.
I mistakenly thought that the addresses presented to the core would by 32-bit aligned
0x01 would equal 32-bit address 1
but instead should have been
0x01 << 2 or 0x04 equals 32-bit address 1
I've changed the 'axi_lite_demo.v' and the test bench 'test_axi_lite_slave.py' to reflect this.
With these changes I've created multiple IP cores that work with Xilinx Vivado block diagram.

Thanks @cospan for this change. I know, it has been a while. Could you rebase this PR to the current master of the cocotb repository?
Content-wise, what you're calling "32 bit address" is in fact a word address (vs. a byte address). Could you update the code to reflect this naming?

Closing this in favor of moving bus drivers/monitors into extensions. See #863 for details.


Influx unnecessarily shows mentions within the note itself

If a note XYZ.md [[mentions]] itself or its [[^^block]], influx shows such mentions just like mentions from external notes.

Maybe this behaviour could be disabled or made a toggleable option?
I'm looking at the file "journey of sorrow.md" and see this:

Fixed


Add description to readme, improve throwing exceptions

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
#2

👍


PYIC-5599 Update ticfHandler to not persist vc to vcstore. Also update BuildUserIdentity to include ticfVc to bundle when enabled.

Proposed changes
Update ticfHandler to not persist vc to vcstore and also not add to the vcReceivedThisSession in session.
Also update BuildUserIdentity to include the riskAssessmentCredential in the bundle when ticf is enabled.
What changed

Why did it change

Issue tracking

PYIC-5599

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

Happy journey path tested in dev env.


[RE-44] Notify users about Terraform 0.11 dependency

First it looks like the test failed, but it looks like a transient failure.
Diving into this, it looks like we recommend to use 0.11, but we use 0.9.9 in our test.  Should we fix this?
Other then that LGTM

I borked this branch.  Making a new one :-)


（cookbook）o1datagen_sft_qwen_with_unsolth_upload_to_hf with CAMEL

…ing Qwen models with Unsloth
Description
Describe your changes in detail.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[ ] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Since the pr for o1 data synthesis is still in the review stage, this cook is also in the draft stage

colab link：https://colab.research.google.com/drive/1R3o7FcQQx77mskNf9czrJkAnzKruQhqb?usp=sharing

@zjrwtx Thank you for the cookbook! I think the code overall looks great! Maybe we can clean up the comments and explanation a little bit (@Wendong-Fan I'm not sure if that's what we want) ?
Just a reminder, we might need to replace the git clone command to install camel package once the relevant PR is merged.

thanks @zjrwtx, added some comments into colab notebook
thanks @Wendong-Fan  , i already resolve all comment ，But I still need you to double check

Thanks @zjrwtx added some comments into colab notebook


X.A.UpdateFocus: Add focusUnderPointer

Description
Some people like their mouse pointer to move when changing focus with the keyboard, other people like their pointer to stay and focus to follow. xmonad(-contrib) supports both preferences, but imperfectly: The former requires using the XMonad.Actions.UpdatePointer contrib module, the latter (focusFollowsMouse) only reacts to CrossingEvent; the focus isn't updated after changing workspaces or layouts.
This adds an inverse of XMonad.Actions.UpdatePointer.updatePointer that immediately updates the focus instead.
Fixes: https://github.com/xmonad/xmonad/issues/108
Checklist

[X] I've read CONTRIBUTING.md

[X] I've considered how to best test these changes (property, unit,
manually, ...) and concluded:
I tested this a bit with a minimal config file and I hope the reporter and commenters of https://github.com/xmonad/xmonad/issues/108 will test it some more. I do not intend to use this myself.

[X] I updated the CHANGES.md file

n/a I updated the XMonad.Doc.Extending file (if appropriate)

Should be harmless to merge it, please do report bugs should anyone run into any.


-k doesn't watch for changes, as far as I can tell

I have to regen with hyde in another term for it to update

Closing as stale.


Hello, when can the code be released? I really want to learn about it

Hello, when can the code be released? I really want to learn about it

Thanks for your attention！Code and model parameters of PointGPT-S have been released


Develop final

Pull de la develop-final vers la master

Rebase should add all the commits on top of the empty master branch, fingers crossed


Create setup script for Azure Key Vault

Description
Create a setup script and functions to set up and store generated secrets in Azure Key vault. This will be used by the setup script in the civiform/civiform-deploy repo.
Checklist

[ ] Created tests which fail without the change (if possible)
[x] Extended the README / documentation, if necessary

Responded to the comments! I think I'd like to keep this PR focused and update the file structure in a separate PR.


build: increase number of runs for Solidity optimizer

What does this PR introduce?
Increase number of runs to 10,000 in the Solidity optimizer, so to optimize for contract interactions rather than deployment.
gas costs LYX transfer:

everything allowed: -147 gas
one allowed address: -240 gas
one allowed address + one allowed standard: -348 gas

Verified if increasing the number of runs in the optimizer increases the computation (and time) required to verify a contract on Blockscout:

No, it actually reduces the verification time by 13 seconds.

Close as need more research on the implications of increasing the number of runs.


Restore determination draft feature

This bug was introduces when we implemented the multiple proposal form feature, see links below.
If I revert the class "ConceptDeterminationForm" to just "pass" the draft feature works again.
https://github.com/OpenTechFund/opentech.fund/commit/7f239ccbf3b081e3ac1f3d6976b3f71ea91c9cd5
https://github.com/OpenTechFund/opentech.fund/blob/1a7645bb449c3b67a17005db48efda5f3da5a6cb/opentech/apply/determinations/forms.py#L362-L384

@Parbhat Could you take a look at this? I have tracked down the reason but I do not see how to fix it.

This could be unrelated, but the batch action does not function as well.

@fourthletter Bug in batch action is related to this issue. @frjo has tested the batch fix on PR #1531.


RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

Runtime Error while inferencing with trained models.
Command in Windows cmd:
python tools/test.py ^
configs/restorers/basicvsr_plusplus/basicvsr_plusplus_360.py ^
work_dirs/formal_basicvsr_plusplus_360new_cb/iter_90000.pth ^
--save-path result/basicvsr_plusplus_cb

Error message:
load checkpoint from local path: work_dirs/formal_basicvsr_plusplus_360new_cb/iter_90000.pth
Traceback (most recent call last):
  File "tools/test.py", line 142, in <module>
    main()
  File "tools/test.py", line 99, in main
    _ = load_checkpoint(model, args.checkpoint, map_location='cpu')
  File "D:\Anaconda3\envs\pytorch\lib\site-packages\mmcv\runner\checkpoint.py", line 581, in load_checkpoint
  File "D:\Anaconda3\envs\pytorch\lib\site-packages\mmcv\runner\checkpoint.py", line 302, in load_from_local
    checkpoint = torch.load(filename, map_location=map_location)
  File "D:\Anaconda3\envs\pytorch\lib\site-packages\torch\serialization.py", line 600, in load
    with _open_zipfile_reader(opened_file) as opened_zipfile:
  File "D:\Anaconda3\envs\pytorch\lib\site-packages\torch\serialization.py", line 242, in __init__
    super(_open_zipfile_reader, self).__init__(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

tried on Google Colab and still meet the same problem

Seems some defects with your pth file. Would you please try replacing iter_90000.pth with other checkpoints?

Seems some defects with your pth file. Would you please try replacing iter_90000.pth with other checkpoints?

tried but still have the same problem

For example, replacing the checkpoint with the one downloaded from our readme page, cause the same error?

For example, replacing the checkpoint with the one downloaded from our readme page, cause the same error?

the checkpoint downloaded from readme page has no problem, but the checkpoints from my training all have the same problem

@cjj490168650 did you manage to fix the issue?

Please check this issue. @LeoXing1996

Hey @cjj490168650, seems that your model is not saved correctly.
Can you provide a minimum script demonstrating the error?

Closing due to inactivity, please reopen if there are any further problems.


Speed up install on Python 3.10

Currently install in Python 3.10 is slow because scikit-allel doesn't have wheels for this Python version. This now affects colab which has upgraded to Python 3.10.

I've made a new release of scikit-allel (v1.3.6) which has wheels for Python 3.10, so we should be back up to speed. Poetry environment is upgraded within #393 which should resolve this issue.


Create a GitHub release for every tag

What problem or use case are you trying to solve?
Create a GitHub release for every tag"
Describe the UX of the solution you'd like
Do you have thoughts on the technical implementation?
Use the Github in-build function
Describe alternatives you've considered
Additional context

See discussion on #1768, but we already have a release for every tag, the release notes are just not very complete right now. We will fix the incomplete release notes in #1623


No more crash if workspace is undefined

Fix for #7

Thanks for your work 💪
I added these changes manually.


Fix zulip unstable formatting with end-of-line comments

Bug
Given
x = () - (#
)

the comment is a dangling comment of the empty tuple. This is an end-of-line comment so it may move after the expression. It still expands the parent, so the operator breaks:
x = (
    ()
    - ()  #
)

In the next formatting pass, the comment is not a trailing tuple but a trailing bin op comment, so the bin op doesn't break anymore. The comment again expands the parent, so we still add the superfluous parentheses
x = (
    () - ()  #
)

Fix
The new formatting is to keep the comment on the empty tuple. This is a log uglier and again has additional outer parentheses, but it's stable:
x = (
    ()
    - (  #
    )
)

Alternatives
Black formats all the examples above as
x = () - ()  #

which i find better.
I would be happy about any suggestions for better solutions than the current one. I'd mainly need a workaround for expand parent having an effect on the bin op instead of first moving the comment to the end and then applying expand parent to the assign statement.

Current dependencies on/for this PR:

main

PR #6386   👈

This comment was auto-generated by Graphite.

I would be happy about any suggestions for better solutions than the current one. I'd mainly need a workaround for expand parent having an effect on the bin op instead of first moving the comment to the end and then applying expand parent to the assign statement.

This isn't possible without moving the comment inside of placement.rs. I personally prefer if the formatter doesn't move my comments out of the parenthesis, because it does change the semantics of the comment:
a = call([ 	# empty because of x
], b) + []

I prefer:
a = call(
	[
		# empty because of x
	],
	b
) 	+ []

Over
a = call([], b) + [] # empty because of x

Because it is now unclear what the comment refers to

I haven’t reviewed yet but just want to confirm - is this still necessary after my two PRs that get the stability checks passing?

I think so, this is a slightly different case (empty tuple vs. empty function) that the minimizer stumbled into because you can get to it by removing the function. I'll rebase and check again once the other PRs are merged

Okay, should be all-clear to rebase.


Add Farmland to Blacklist

Pretty straightforward, kinda important

If possible, could you use the vanilla tags for the blacklisted items? So the modded woods, leaves, etc can be blacklisted without manually changing the blacklist.json and recompiling?

Basically you can add a data pack yourself to change these things so you don't need to recompile, also the reason why #minecraft:logs isn't on the blacklist is because I felt they where fairly important in boat building so I excluding everything bar stripped logs. I can look into it but I went with the idea that it should be easy enough to find a biome without modded material to build ships in, then you can uses modded material

I will however definitely put farmland on that blacklist

logs are now fully excluded in the blacklist so mod logs should also be, farmland has also been added


Wrong type passed to getRouterCollection?

I'm getting the following error when trying to use this component:

Type error: Argument 1 passed to NilPortugues\Laravel5\JsonApiDingo\DingoProvider::getRouterCollection() must be an instance of Illuminate\Routing\UrlGenerator, instance of Dingo\Api\Routing\Router given

It looks like what should really be passed to this function is an instance of Dingo\Api\Routing\UrlGenerator and the function should accept Illuminate\Contracts\Routing\UrlGenerator.
Have I misconfigured something or is this a bug?

Mind sharing laravel and dingo versions? Might be related in some unnanounced break from the dependencies.

"minimum-stability": "dev",
"require": {
"php": ">=5.5.9",
"laravel/framework": "5.2.",
"tymon/jwt-auth": "0.5.",
"dingo/api": "1.0.x@dev",
...
dingo/api                             dev-master 242411e
laravel/framework                 5.2.x-dev 557b9f6

I'm also seeing this bug:
Type error: Argument 1 passed to NilPortugues\\Laravel5\\JsonApiDingo\\DingoProvider::getRouterCollection() must be an instance of Illuminate\\Routing\\UrlGenerator, instance of Dingo\\Api\\Routing\\Router given, called in \/vagrant\/vendor\/nilportugues\/laravel5-json-api-dingo\/src\/NilPortugues\/Laravel5\/JsonApiDingo\/DingoProvider.php on line 30

"require": {
    "php": ">=5.6.4",
    "laravel/framework": "5.3.*",
    "dingo/api": "1.0.x@dev",
    "tymon/jwt-auth": "0.5.*",
    "nilportugues/laravel5-json-api-dingo": "^1.0"
},

Did you ever find a solution to this error?

The same error!
"require": {
        "php": ">=5.6.4",
        "laravel/framework": "5.4.*",
        "tymon/jwt-auth": "^0.5.9",
        "dingo/api": "1.0.x@dev",
        "barryvdh/laravel-cors": "^0.8.2",
        "nilportugues/laravel5-json-api-dingo": "^1.0"
},


az provider show -n  doesn't work for most RPs

This is autogenerated. Please review and update as needed.
Describe the bug
az provider show -n  should pull info from the providers api for the specified provider.  It looks as though we use an arbitrary apiVersion which isn't likely to match the supported apiVersion for the specified provider.  So this cmd will almost never work
Command Name
``az provider show
Errors:
Error returned will indicate the provider doesn't support the apiVersion sent in the request.  The use has no option to change the apiVersion
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az provider show -n Microsoft.Storage/storageAccounts (or any resource that doesn't have a 2020-06-01 apiVersion

Put any pre-requisite steps here...
``

Expected Behavior
return the results of the GET
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.14.0 *

Extensions:
storage-preview 0.2.5

Additional Context

hi @fengzhou-msft could you pls have a look? thanks

@yungezz were you successful in resolving this?


What does the no-trimming flag do?

Hi,
Firstly, many thanks for this excellent piece of software. My question concerns the no-trimming feature. What exactly does this do? Does it  not trim the end of reads to fit the assembly? Or does it not trim the extreme ends of contigs if there is very low coverage there?
Many thanks in advance
Best
Zack

Hello Zack,
the --no-trimming option disables consensus trimming in each window. Racon creates partial order graphs within non-overlapping windows of each contig, and the consensus calling algorithm can have low coverage ends. Therefore we trim away bases from each consensus sequence until the base coverage reaches half the coverage of the corresponding window.
Best regards,
Robert

Dear Robert,
Many thanks for this information.
Best Zack


SOC and Amps from Lynx Shunt

Would it be possible to read the SOC and Amps from a Lynx Shunt?
Currently it seems to reed the Amps from the multiplus and SOC calculation is own. But the SOC does not reset to 100%.

Hello, there is no reason to use additional hardware as battery monitor. Either the BMS current and SOC are good (not my case), or by setting OWN_SOC = True and CURRENT_FROM_VICTRON = True. The SOC in this case is reset to 100% if overall battery voltage or the first cell reach the allowed maximum. And is reset to 0 in case of reaching minimum. It works perfectly in my case. SmartShunt can be activated for measuring of DC consumption. I cannot consider all possible hardware combinations, this would make the maintenance very difficult and I would not be able to to it in my limited time. But feel free to reverse engineer the program and modify your copy to fit your requirements.


ESE algorithm has a comparison that is always true

https://github.com/SMTorg/smt/blob/411fdd8a66ba1aa9d6bbd9cdff8d5d3b6a6cc126/smt/sampling_methods/lhs.py#L214C1-L221C32
             if PhiP_best - PhiP_oldbest < tol:
                # flag_imp = 1
                if p_accpt >= 0.1 and p_imp < p_accpt:
                    T = 0.8 * T
                elif p_accpt >= 0.1 and p_imp == p_accpt:
                    pass
                else:
                    T = T / 0.8

This comparison on line 214 looks a bit off. It compares the original best PhiP score at the start of the outer loop iteration to the best score found in the inner loop. The PhiP score is initally based on X_oldbest and is only updated when the score decreases.

                    # Best plan retained
                    if PhiP_ < PhiP_best:
                        X_best = X_
                        PhiP_best = PhiP_
                        n_imp = n_imp + 1

Therefore PhiP_best - PhiP_oldbest should always be <= 0, but the tolerance is hard-coded positive so the condition for the if statement is always true.
I checked in the original paper (https://openturns.github.io/openturns/papers/jin2005.pdf) and I think the comparison should be like this.
if PhiP_oldbest - PhiP_best > tol:
You should be able to reproduce this behavior using this example
from smt.sampling_methods import LHS
import numpy as np

if __name__ == '__main__':
    xlims = np.array([np.zeros(10), np.ones(10)]).T
    sampling = LHS(xlimits=xlims, criterion='ese', random_state=0)
    samples = sampling(50)

Very good catch! Thanks for pointing it out! Indeed the condition is wrong, it should have been with a < -tol or as you stated and stated in the paper: PhiP_oldbest - PhiP_best > tol.
This bug is pretty old, as old as SMT, I would say! I am not sure of the impact, the fix may break other tests in SMT as optimized LHS is largely used.
Do you want to submit a PR?

I'm happy to put in a PR.


New Crash Beta 15

Ok so I download beta 15, load world, every thing is fine, night rolls around so i go to scan the sky, get the moon scaned, pan over  to the next target and my Scanner lands on my Astral Sorcery Altar which I have not scanned aparently and it instantly crashes. Reloaded 3 times, crashed right away. I downgrade the version to 14 to find out that i had not scanned the altar before and did so.... May be a partical issue but i cant read error codes very well (Downgrading stopped the crash by the way)

11:04:18
net.minecraft.client.Minecraft
Unreported exception thrown! java.lang.UnsupportedOperationException 	at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1176) 	at thaumcraft.client.fx.ParticleEngine.updateParticles(ParticleEngine.java:296) 	at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_149_ParticleEngine_updateParticles_ClientTickEvent.invoke(.dynamic) 	at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90) 	at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:182) 	at net.minecraftforge.fml.common.FMLCommonHandler.onPreClientTick(FMLCommonHandler.java:343) 	at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:1706) 	at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1096) 	at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:397) 	at net.minecraft.client.main.Main.main(SourceFile:123) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 	at java.lang.reflect.Method.invoke(Method.java:483) 	at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) 	at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

Please use search, there are multiple reports for the same issue you're seeing.
Going back to Beta 14 may help unless you're running a server.

New to github. Also dont know how to search for this exact problem so... hey it might be unique. I dont know. I dont know code but as far as i can tell its... Particles. I dont understand how that would or could crash a game

Enter "crash" in the searchbar above the issues list, you won't know if it's unique unless you search first. It's a known issue affecting a lot of people.

Duplicate of #858

Cool I'll keep that in mind
On Fri, May 25, 2018, 12:32 PM Gee<EMAIL_ADDRESS>wrote:

Enter "crash" in the searchbar above the issues list, you won't know if
it's unique unless you search first. It's a known issue affecting a lot of
people.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azanor/thaumcraft-beta/issues/879#issuecomment-392128061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlyycOxCWERT_kMhpRf95ulUxP-A7rizks5t2EAggaJpZM4UOPmw
.


5238 set up basic docs structure

This pull request adds two docs sections - "Getting Started" and "User Guide".
The "Getting Started" part is just a copy of parts of the main README for now, while the "User Guide" just links to the user guide found on GitHub.
And with this - we can actually start the project locally!
Adresses #5238

Can we figure out a way to avoid a super visible docs directory until we're actually comfortable with these being final docs? Our users will try to go there and be confused by drafts.
Something like website-docs-wip would work better in the meantime.

Okay that sounds good.

Shall we cut a docusaurus branch off master now and move this PR and https://github.com/facebook/create-react-app/pull/5251 there? A good chunk of selbekk's work got merged, nice! Up for whatever you all prefer. @selbekk sent you a DM on Twitter

I merged this into master but I also pushed a docusaurus branch.
I agree it probably makes more sense to start working in it directly than create noise on master. How about this arrangement:

You can both work against docusaurus
You can review each other's PRs
Tell me or @timer (here or on Twitter DM) when you're happy with PRs and we'll press Merge

Also thanks again for working on this, I'm super excited we'll get a real website!

sounds good, thanks!

Good by me as well :) go team!


Make storage upload/download have no chunk size by default.

Fixes #546.
See #606 for old discussion. This was made possible by #811.

/cc @thobrla

Coverage remained the same at 100.0% when pulling 31dc5aefc3d9ffffe49edd67672737b1e28c0aff on dhermes:fix-546 into f08e71b5fdcf0bbdaf1257bab5e64a3c8621f414 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling 31dc5aefc3d9ffffe49edd67672737b1e28c0aff on dhermes:fix-546 into f08e71b5fdcf0bbdaf1257bab5e64a3c8621f414 on GoogleCloudPlatform:master.

@tseaver I moved the default _chunk_size to class.

Coverage remained the same at 100.0% when pulling e442cd214ff5d09e002ea17d2b5a54085871f829 on dhermes:fix-546 into f08e71b5fdcf0bbdaf1257bab5e64a3c8621f414 on GoogleCloudPlatform:master.

LGTM


Add admin endpoint for Pinot Minon.

Description
The Pinot Minion component, unlike other components, was missing an admin endpoint.
In this PR, we added an admin endpoint for Pinot Minion.

The endpoint uses Jersey http server (same as other components).
Setup swagger for Minion.
Also, added the endpoint /appconfigs similiar to other components.
(See: https://github.com/apache/incubator-pinot/pull/6817).

Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[x] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes

Documentation

Clean and easy from a first look. TLS/SSL will kick in automatically when configured.
Need for auth depends on whether this will be a publicly accessible API. If this is only used internally to the cluster, TLS client auth can handle it for us similar to pinot-server. If this is intended to be accessible publicly, I'd suggest to have a short chat about the design.

The purpose here was just to add /appconfigs api as in other Pinot components. Given that minion did not even have an admin server running, I had to set it up. There are no api's other than that currently. @Jackie-Jiang Do you think minion will need public api's that would need acls/tls support? Or would those be via the controller?

The purpose here was just to add /appconfigs api as in other Pinot components. Given that minion did not even have an admin server running, I had to set it up. There are no api's other than that currently. @Jackie-Jiang Do you think minion will need public api's that would need acls/tls support? Or would those be via the controller?

Public APIs on backend services ask for trouble. If possible, every request here should come from controllers.

The purpose here was just to add /appconfigs api as in other Pinot components. Given that minion did not even have an admin server running, I had to set it up. There are no api's other than that currently. @Jackie-Jiang Do you think minion will need public api's that would need acls/tls support? Or would those be via the controller?

Public APIs on backend services ask for trouble. If possible, every request here should come from controllers.

Yes, agree.


IG,Dm

When I use the IG:dm, I saw that the person i was talking to sent some texts to me by looking on my phone, but later on, checking on the IG:Dm, I didnt see the texts the person sent, only mine.

Woah, fast responce, I like it. Well no, I tried just deleting the tab and
then starting it up again, but no. It seems that when Its not open and the
other person sends texts, it shows, but when the program is off, It
doesnt show the texts sent beforehand.
On Mon, May 14, 2018 at 7:24 PM, Ifedapo .A. Olarewaju <
<EMAIL_ADDRESS>wrote:

@chesmix4 https://github.com/chesmix4 does the message appear when you
restart IGdm? could it be that the message was deleted?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ifedapoolarewaju/igdm/issues/205#issuecomment-388993862,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aldr1RBpYLRzv9zH7g0lZrvu6eMwBRfoks5tyhI-gaJpZM4T-qYk
.

It seems that when Its not open and the
other person sends texts, it shows, but when the program is off, It
doesnt show the texts sent beforehand.

I'm a bit confused by this. Could you please rephrase?

Lets see, so when I received a text from this person, my computer was off
(therefore the program obviously wasn't running). I replied to this person
on my phone with the real Instagram App. When i came back home, I ran the
program and saw that the texts that the person sent was not there, but my
responce that I gave was there. After a while, this person had sent another
text and this time, while the program was running, i received the text.
On Mon, May 14, 2018 at 7:29 PM, Ifedapo .A. Olarewaju <
<EMAIL_ADDRESS>wrote:

It seems that when Its not open and the
other person sends texts, it shows, but when the program is off, It
doesnt show the texts sent beforehand.
I'm a bit confused by this. Could you please rephrase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ifedapoolarewaju/igdm/issues/205#issuecomment-388994681,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aldr1QM9CtlO3p8ZwrsVl9AwG0pDt9SEks5tyhNhgaJpZM4T-qYk
.

Hey, can you sign this petition? http://chng.it/NtfGjKbxjt
Thanks! - Joseph


Add shader linking capability to GLSLToSPIRVConverter

This is a PR for this issue. Simple change to make it so that you can use the linking feature in glslang
Thanks

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Colin Hughes seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Tournaments: add /tour setname

Client-side: https://github.com/Zarel/Pokemon-Showdown-Client/pull/896

Unrelated, but someone should probably refactor tournaments to use template strings throughout. Maybe I'll do that... if I have time.


remove unused reference to example_interfaces

Hello there,
I noticed that the package example_interfaces was being used by ros2cs_core for no apparent reason, so I removed it.
The change was only tested on ROS2 Humble on Windows.

hello.
Thank you for your advice.
Deleted because it is a remnant of the previous test.
Confirmed with humble/galactic on ubuntu/windows.


register wasm created Utf8SourceInfo with ScriptContext

ScriptContext::close cleans up all FunctionBody/EntryPointInfos
before destroying native code generator. On xplat this order
is required because EntryPointInfo finalizer may need to deregister
debug data which is managed by native code generator.
Register wasm created Utf8SourceInfo with ScriptContext, so that
ScriptContext can guarantee above shutdown order with wasm created
FunctionBody/EntryPointInfos.
Fix #2517
Also fixes a rlexe.xml syntax error, seen from CI output.

LGTM

Looks right to me. Should work.

@agarwal-sandeep Thanks a lot!

Thanks!


This isn't an issue

The wallet generated with wallet acc is it from, id it trust wallet, binance or which one

I didn't get your meaning. I guess you missed the README

I mean what wallet will we use to import the phrase seed, because there is
alot of wallet application
On Thu, Aug 8, 2024, 13:12 penn @.***> wrote:

I didn't get your meaning. I guess you missed the README
—
Reply to this email directly, view it on GitHub
https://github.com/penn201500/tron-wallet-generator-and-transfer/issues/2#issuecomment-2275668759,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFBDFVNXP35HFGOQRL6PPGTZQNOBVAVCNFSM6AAAAABMGEF772VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZVGY3DQNZVHE
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Tron, you can check it here: https://tronscan.org/#/

Thanks, I'll check it out!
On Fri, Aug 9, 2024, 02:02 penn @.***> wrote:

Tron, you can check it here: https://tronscan.org/#/
—
Reply to this email directly, view it on GitHub
https://github.com/penn201500/tron-wallet-generator-and-transfer/issues/2#issuecomment-2276965444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFBDFVLHJ6YHWRH4EMOPGBDZQQIK3AVCNFSM6AAAAABMGEF772VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZWHE3DKNBUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


How can I generate the .npz file to evaluate other datasets?

Hello，Do you have any questions Npz file?
Can you share it with me?


Update stable version in repo from 3.4.2 to 3.4.3

Think about update stable version to 3.4.3
Version: stable=3.4.2 (491 days old) => latest=3.4.3 (15 days old)
Installs: stable=5605 (79.64%), latest=510 (7.25%), total=7038
Click to edit

wait for 3.5.x


fix: add missing actions to enable loading behavior

add missing setIsSubmitting(false) to AddPostPage, SigninPage and SignupPage
Note: I couldn't setup the express service to test the actual behaviour of the fix but having read the code and the logic I'm confident this should reset the state of the buttons.

@MaximeKoitsalu I tested the code but found that the 'is-loading' class gets added and immediately removed as soon as the button is pressed due to which the loading state is not visible.
Demo:

PS: Can you let me know  what issues you're facing in setting up the express server ?

Ah yeah my bad, what is needed to make it work is to lift the state key "isSubmitting" to the nearest ancestor. We want to reduce the value of isSubmitting to false when the "LOGIN_FAIL" action is dispatched. I'll give it another go in couple hours!

Yup, that seems correct. @MaximeKoitsalu take your time, no hurry.

@itsnitinr Alright, should be working now!

Hi @MaximeKoitsalu. Fabulous work, there's just one tiny bug which I have mentioned as a comment above. Please check it out, won't take more than a minute. Everything else works great. Thanks for contributing.

Honestly, thank you haha! I've been wanting to dive into react and this was my first experience with react, I come from vue and angular so I quickly understood the similarities and the usage of the redux pattern. If you ever need help with anything else feel free to send me a message!

@MaximeKoitsalu Woah, this is seriously very impressive. You should be very proud of yourself, what a great contribution as a first experience with React! I'm jealous xD. Great job, was a pleasure to have you contribute to the project. Thank you for the fixes! Merging the pull request and I hope to stay in touch.


hasSubscriptionsForEvent

Hi,
Is there any way to determine if there is a subscription for a topic?
I used ko.postbox.hasSubscriptionsForEvent for this, but that does not seem to work anymore.
I get error 'Object doesn't support property or method 'hasSubsbscriptionsForEvent' '
Thanks

You realize that you spelled it wrong right?


[recast] Export unofficial target

Export the target that the user can use recast simply:
The package recast:x86-windows provides CMake targets:

    find_package(unofficial-recast CONFIG REQUIRED)
    target_link_libraries(main PRIVATE recast)

Fixes #18649.

@Maxomann  Can you please test my changes?
Thanks.

@JackBoosY Thanks for your changes!
I have tried to set up the RecastDemo project from the recastnavigation/recastnavigation repository. So far I have noticed two things:
First:
#include directives (for example to: #include <recast/Recast/Recast.h>) only work if there is at least one other vcpkg library linked to the RecastDemo target.
So this:
target_link_libraries(RecastDemo PRIVATE recast [...]) would result in fatal error C1083: Cannot open include file: 'recast/Recast/Recast.h': No such file or directory
While this (linking completely unrelated vcpkg library nlohmann_json::nlohmann_json ):
target_link_libraries(RecastDemo PRIVATE recast nlohmann_json::nlohmann_json  [...]) does not produce said error.

Second:
Upon further investigation it seem that certain #include directives in the library itself don't work correctly.
This leads to build errors like: [...]\vcpkg\installed\x64-windows\include\recast\DetourCrowd\DetourPathCorridor.h(22): fatal error C1083: Cannot open include file: 'DetourNavMeshQuery.h': No such file or directory
#include "DetourNavMeshQuery.h" is expected to be in the same folder as DetourPathCorridor.h, but they are both in different sub-folders. Namely:

[...]\vcpkg\installed\x64-windows\include\recast\DetourCrowd and
[...]\vcpkg\installed\x64-windows\include\recast\Detour

I hope this was helpful. If there's anything I can help with further, feel free to let me know.

@Maxomann Please try again.
Thanks.

These changes allowed me to build the demo project: https://github.com/Maxomann/vcpkg/commit/450c7afbc21097e6b71ceb3fe0e6c32f5c4ad69d

Cmake doesn't provide findmodule.cmake, so this LGTM.


FEATURE: Add/Enable PWA (Progressive Web App) 🟢🌟

Feature Summary
I want to Add PWA (Progressive Web App)..
🌟Benefits of PWAs:
Improved Performance and Speed
Offline Availability
Enhanced User Engagement
Responsive and Adaptive Design
Low Storage Requirements... & more..
please assign me for this..
Description
.
Proposed Solution
No response
Alternatives Considered
No response
Screenshots/Logs
No response
Additional Information

[X] I have searched for existing feature requests
[X] I am willing to help implement this feature
[X] I can provide more details or clarification if needed

@YadavAkhileshh sir please add Level 3


implement transactions tab

Title: implement transactions tab
Business/User Value:
User objectives:

filter trasactions by coin

Acceptance Criteria
GIVEN [necessary context and preconditions for story]
WHEN [action]
THEN [reaction]
DEV NOTES

https://github.com/KomodoPlatform/KomodoPlatform/wiki/BarterDEX-API-Summary-by-Category

DESIGN Notes
None
---other items that you may add to a story---
NEEDS PM
None
NEEDS DESIGN
None
Related issues
#15
/label ~"story"

This is user objectives that user want to satisfy when they open the transaction tab in wallet page:

The user wants to know when the transaction happen

The user wants to know the amount of transaction

The user wants to know what type of transaction (withdraw, deposit)

Currently, listtransactions api only returns tx_hash and height in SPV mode.
{
    "tx_hash": "afc2fd0991bdef89da2cd1018c86ab56a5989c6f2b1d4e40861e88bc6125cbec",
    "height": 10076
}

Is there any other way for me to get the above information (time, amount, type)?
cc @ca333 @siulynot

@particle4dev Hi, does it return more info in native mode?

@artemii235 yes, but the purpose of the app is used SPV lightweight mod. Is there an API that I can call with tx_hash to receive more detail?

Don't worry if you can not.
We can hold this task until we find out the best solution. No rush

@particle4dev Hi, I've checked the code responsible for tx history and seems like there is no "easy" way to reduce the execution time of listtransactions. The response is got directly from electrum server and it contains only tx hash and height without other tx data. Also electrum get_history takes really long (especially for first time). So here are steps that I need to implement:

Call electrum get_history at background thread.
Collect transactions by hashes.
Transform the collected data and save it at memory/storage.
Respond to listtransactions with previously prepared data.
It'll allow to provide listtransactions response immediately but as you can see it requires some work to prepare the data.

I think it'll take 1-2 days to implement it, I'll have time for it on next week.
A question about response format: do you have specific requirements for it? Or it can be same as listtransactions in native mode?

@particle4dev Hi Nam, excuse me, wasn't able to finish the task on prev week, going to finish on this one.

@artemii235 hi, that's ok :) thank you so much for hard work

@particle4dev Hi Nam, I've finished implementation and published the new release: https://github.com/artemii235/SuperNET/releases/tag/v1.0.928
Please check following example of listtransaction response in ETOMIC mode:
[
  {
    "txid":"5b4f40383d24504c674325585fa5ab6d478c3ebbf60ec83643ddb27ac536e4af",
    "category":"receive",
    "amount":1.12500999,
    "blockhash":"04c29068c00379e6c59e737e4e7f590407b445b7995d25d4f49b824b64ac391b",
    "blockindex":130530,
    "blocktime":1541574432,
    "time":1541574432,
    "confirmations":5
  },
  {
    "txid":"4d83285b73070d9b7bc4f9ba140bb4bd9248375686bab82d4b7d5adff1c9123a",
    "category":"send",
    "amount":-1.00001999,
    "blockhash":"0a9d036274f0953aa6e62fd8935a79f1a96709ade8bffc509192b3511f209ac4",
    "blockindex":130528,
    "blocktime":1541574338,
    "time":1541574338,
    "confirmations":7
  }
]

As I said before the history is getting loaded in background so it might take some time to load full history, it starts loading from recent transactions so the more transactions address has the more time it'll take to load them all - it does not block listtransactions request, you should just keep in mind that you might not get old transactions immediately especially if there are hundreds of them.
Also in comparison with native some fields are omitted (txfee, etc.) because Electrum doesn't provide them.
Please test the release and let me know if I need to fix or add something.

@artemii235 thanks. I will test it today and send you the feedback. I'm working on other task now

@artemii235 the API work great. I like it a lot. Closed this issue for now.
I need to work on searching transaction feature but still don't know what should UI/UX looks like. I have to research more about it to find what user want.


slirp4netns: 1.1.8 -> 1.1.9

https://github.com/rootless-containers/slirp4netns/releases/tag/v1.1.9

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114404 at d114bd5f run on x86_64-linux 1

3 packages built:

buildah
podman
slirp4netns

1 suggestion:

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/networking/slirp4netns/default.nix:34:5:
   |
34 |     license = licenses.gpl2;
   |     ^


⚠ Adacta-fintech.com has degraded performance

In 811568f, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 7414 ms

Resolved: Adacta-fintech.com performance has improved in 0e3ebb1 after 13 minutes.


Use conda-forge-pinnings for readline

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

I don't understand AppVeyor's complaint:
The build phase is set to "MSBuild" mode (default), but no Visual Studio project or solution files were found in the root directory. If you are not building Visual Studio project switch build mode to "Script" and provide your custom build command.

Also, I am not sure what to do about ecl. Is it a build/run dependency?

Hm…I have skip: true  # [win]. Why does appveyor even bother to build this?

@conda-forge-admin please rerender

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I rerendered the feedstock and it seems to be already up-to-date.

@isuruf @embray: Not sure why appveyor tried to build here but other than that this looks good to me.


[QUESTION] Store face attributes/embeddings?

Hi @nonam4 , first, thanks for this great library.
I have a question if this library is capable of storing the face attributes/embeddings into the database and compare it later on for a verification? e.g. I register my face first and then use it for unlocking the app if the scanned face is valid.
I have created a prototype where it detects the face if it is inside the face placeholder but stuck here at the moment.
Thank you

Hello.
Yes, it's possible because you'll have all face's embeddings but I have no idea how you can achieve this using this library.
Maybe you can try looking for euclidean distance as a starting point..
But I don't think it's a good idea use client side to handle authentication, even worse if there's sensitive data in your app...
You should consider to send face data to backend and there you can compare stored face data, etc...
In my project I use vlad's face-api package (I've also tested human but face-api works better in my case) as a backend comparision framework.
If helps, here's a little contributing I've made...
I wish I could help you more but this is everything I can afford without any payment.

Hi @nonam4 , thanks for answering my question. I am still in the planning phase and doing more research on the best way to do it. Thanks for your reference links. I will take a look.
Cheers.


Adding error message when there's no partition for a presto table

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
If someone tries to use {{ presto.latest_partition('schema.table') }} but the table doesn't have a partition, it throws a confusing error to the user Template rendering failed: list index out of range. This catches the error and throws a clear error message.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
Tested query with presto.latest_partition on a table with no partition
Tested query with presto.latest_partition on a table with a partition
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@john-bodley @serenajiang

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5e1a6ea). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #8745   +/-   ##
=========================================
  Coverage          ?   72.06%
=========================================
  Files             ?      123
  Lines             ?    12827
  Branches          ?        0
=========================================
  Hits              ?     9244
  Misses            ?     3583
  Partials          ?        0

Impacted Files
Coverage Δ

superset/db_engine_specs/presto.py
22.48% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e1a6ea...859614d. Read the comment docs.


Add graphiql options and missing flask context

This add support for graphiql options like as:

default_query: An optional GraphQL string to use when no query is provided and no stored query exists from a previous session. If not provided, GraphiQL will use its own default query.
header_editor_enabled: An optional boolean which enables the header editor when true. Defaults to false.
should_persist_headers:  An optional boolean which enables to persist headers to storage when true. Defaults to false.

Also, add the missing context attribute as requested at this old flask-graphql#52 issue.
However, the approach I used for all 4 servers (flask, aiohttp, webob, sanic) was based on this sanic#8 issue which was solved at this pull request.
There are other related issues as well on each server integrations:

https://github.com/graphql-python/sanic-graphql/issues/11
https://github.com/graphql-python/flask-graphql/issues/45
https://github.com/graphql-python/webob-graphql/issues/5

As far as I know, this context will be passed to the execute method on GraphQL, which will be passed to all resolve functions as stated on GraphQL-JS docs. At the end, this will be part of the GraphQLResolveInfo, which is used by resolve_field_value_or_error to resolve the field.
Based on that, I am not 100% sure if it the correct way of handling custom context for all server integrations so any suggestion is welcome!

After reading a bit regarding what context is used for, I submitted another commit with a possible test suite to ensure and help others to understand the proper functionality of context using Flask as example.


Add the tracking function of point cloud annotation

The point cloud annotation tool should have the same box tracking function as the image annotation tool, which can facilitate the taggers to carry out mass annotation, so as to improve the efficiency of annotation

@DeepBlue23 For those expecting 3d lidar annotation features, you may check it out : https://github.com/basicai/xtreme1


2.0 examples/tree/index.html can not add more than one child

vue.js:2113 [Vue warn]: Error during component render (found in component: <item>)warn @ vue.js:2113get @ vue.js:627run @ vue.js:716runSchedulerQueue @ vue.js:531flushSchedulerQueue @ vue.js:500nextTickHandler @ vue.js:336
vue.js:570 Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

This is the error from console
Code from next branch
dist/vue.js built from npm

Current dist file is out of date, please wait util an actual release.


fix(ssl-preread) match upstream patches exactly

@bungle do you know why they don't match exactly already? (there is a single non-whitespace difference in here)
Generated with:
git -C ../nginx show -p --{src-prefix=a,dst-prefix=b}/nginx-1.13.6/ \
	1a5604bedd98b5f58a0b42d4fbb4223759e6c0c9 \
	b84b67bc0f434747f3e13c5faf8ddf71acd11049 \
	> patches/<IP_ADDRESS>/nginx-1.13.6_05-ssl-preread.patch

@james-callahan I suspect it is other patches that already edit the same file, making a patch for 1.13.6 to not apply cleanly on our patched Nginx 1.13.6. I had to do all sorts of these edits when I got initial round of patches.

The Fuzz comes from this:
-             return rc == NGX_OK ? NGX_DECLINED : rc;
+             return rc;

I am not sure why you wanted that. The upstream Nginx has:
             return rc == NGX_OK ? NGX_DECLINED : rc;

Well, there is not need for this PR in my opinion. It just breaks the already fixed patch and doesn't change the patch itself at all.

Your PR just adds this:
Hunk #5 succeeded at 167 with fuzz 2.

I fixed it manually.

The upstream Nginx has:
             return rc == NGX_OK ? NGX_DECLINED : rc;

Oh? link?
I'm seeing just return rc: https://github.com/nginx/nginx/blob/774d69cf4a0ab2526422c77c0210f1f4d75f2900/src/stream/ngx_stream_ssl_preread_module.c#L191

See: https://github.com/openresty/openresty/blob/0263f89bffe3a1fb3114dcad998e7b0d7119139d/patches/nginx-1.13.6-stream_ssl_preread_no_skip.patch#L10

Ah okay. I didn't realise openresty also patched it.


Python codebase for Connect processor template

This is the first codebase checkin for Connect processor template

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: Neha Shelke:x: NehaDC-IMC:x: IMC-CarolinageNeha Shelke seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Prepare for new release of Bitbucket

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/179961324, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/179961324.

Current version of Bitbucket Slack plugin -  3.0.2 - is already marked as compatible with Bitbucket 7.4.0.


ASP.NET Core or just ASP.NET?

Why the MS still calling ASP.NET of ASP.NET Core if the .NET is no longer called .NET Core.
Can we just use the name ASP.NET without commit a mistake?

That's not changing.

So can I assume that ASP.NET will still be called "ASP.NET Core" for years to come?
I'm preparing a lot of content about ASP.NET (I'm an MVP) and I want to use the permanent name so I don't have to change it anymore.

@Rick-Anderson your answer wasn't very clear to me, could you help me understand?


Joint limits

Set the joint limits in URDF back to the values that are reported in the Barrett documentation after we have stopped using OWD.

Resolved by b62f2241535cda3f098f702f8ea93b403a48aed9.


In order to unify with other angular libs, this component lib will be moved to "nb-trans"

In order to unify with other angular libs, this component lib will be moved to "nb-trans", and the component, pipe and service will be added the prefix 'nb-'.
'nb' nb means ng bigbear
But the trans lib also will support to angular 13

The new lib: @bigbear713/nb-trans has been published.
This is the repository: https://github.com/bigBear713/nb-trans
changes:
NgTransService --> NbTransService
<ng-trans></ng-trans> --> <nb-trans></nb-trans>
[ng-trans-subcontent] --> [nb-trans-subcontent]

trans-subcontent-list  --> subcontentList

ngTrans --> 'nbTrans'
NG_TRANS_DEFAULT_LANG --> NB_TRANS_DEFAULT_LANG
NG_TRANS_LOADER --> NB_TRANS_LOADER
INgTransLoader  --> INbTransLoader
INgTransOptions  --> INbTransOptions
INgTransParams  --> INbTransParams
INgTransChangeLang  --> INbTransChangeLang
INgTransSentencePart  --> INbTransSentencePart
INgTransSentenceCompPart  --> INbTransSentenceCompPart
NgTransLangEnum  --> NbTransLangEnum
NgTransSentenceItemEnum  --> NbTransSentenceItemEnum


Update release with 0.13.2 serving.

Proposed Changes
Title has it all. Unfortunately, the diff of the YAML is super big (upstream too...) because of some reformatting. We should avoid that for future releases.

/lgtm

/approve


Adds mechanism to support managed npm install runs from within the app builder

This change adds a new context which can be used from within the app builder experience to programatically run npm install or npm install <packagename>. This builds on top of much of the existing package.json management logic originally built for srcbook notebooks. Also note that logs stream in while the npm install occurs live!
In addition, I've introduced a very barebones interface that can be used to try it out. Note that a more thought through interface is definitely the long term intention - I just wanted to get something out to get folks moving, and plan to follow up with something later here.
Finally, I've made some small tweaks to the statusbar panel to fix some rendering weirdnesses I encountered.
High level walkthrough

https://github.com/user-attachments/assets/853f93ea-7d29-4a20-9e6f-1f2a6eb6d7e6

Also worth calling out: there's nothing right now serverside to prevent two npm installs from happening concurrently. I can probably add some more client side validation to make that case impossible but I don't know how much of a real problem this actually is in practice.