enhance k9 mail identity selection

Identity selection could enhanced to make life a lot easier.
Today, it is really painful as it is in most client email readers.
Identity selection should be :
-free to edit and modify when writing a message (more or less as the recipient field currently is)
-automatically set with the best value guessed from the recipient values, when replying.
This would be a great feature to differentiate K9 mail from other rigid email clients.
Why?
I use the catch-all of my domain to handle a lot of different addresses.
Catch-all is really a great feature as it allows me to give anyone a unique email address in order to send me an email.
Consequently, I can, if I receive spam on this address, deduce that this correspondant may have abused my personal information.
I also use it to differentiate between groups of interest, without having to mess with a lot of mailboxes or aliases on the server side, as it is a painful task that can never be done correctly and is completely useless.
The only problem I see is to correctly select the account to associate with the email to be sent.
It could be deduced from the receiving account, when replying. Just use the same.
When not replying, either you are in an account view, and it is this account, or you are in the unified view, and this where creativity lies. Simplest solution would be to use the default account, but in my case, it is not the catch-all, so it's not that simple. I would make it this way : if the identity is the one associated with an account, use that account. If the identity is not the one associated with one account, use the 'default unassociated identity account', which is, in my case, the catch-all. In the end, the list-based feature can be used to force any configured account to be used.
This way, current behaviour does not change, but is extended and a lot more flexible than a fixed list-based feature.
Just imagine such a list-based feature for the recipient field in order to see what I mean.

I'd love this, it would make it the best!

I also want the second idea "automatically set with the best value guessed from the recipient values, when replying." I think.
However, I think that's almost a separate issue, so I've made it one: issue #1064
Since that's now a separate issue, is this issue closeable?

I am also very interested in this feature. Been using k9 on a daily basis for six years and this is the only feature I'm missing.
For Thunderbird, there is a very well working plugin called Virtual Identity. Perhaps one can find some inspiration from that?

@johey For Thunderbird, this is a default feature from some release ago, without the need for an old and abandoned plugin. ;)
Anyway, this feature would be nice indeed for K-9. :)

@ArchangeGabriel Thunderbird doesn't allow to use a sender's email if it has not been previously added as Identity. Whereas Virtual Identity allow to compose/reply without creating Identities.
For instance emails like<EMAIL_ADDRESS>and<EMAIL_ADDRESS>can be forwarded to<EMAIL_ADDRESS>(for tracking purpose). Now if you hit the "Reply", Virtual Identity can be set to use<EMAIL_ADDRESS>or<EMAIL_ADDRESS>as sender's email without having to create the Identity first.
Therefore I agree with @johey, Virtual Identity could be a good starting point.

@saintger No, Thunderbird does allow you to do so since 45.0 (last “New” item from here), and that was precisely the point of my previous comment. Just take a look at the last entry from the drop down menu for the From (or whatever it is in your locale) field.
However, I agree that it doesn’t provide the “Smart Reply” thing from Virtual Identity, which escaped from my previous reading of this issue.

@ArchangeGabriel Indeed you can compose without adding the identity first, I missed that as well.
However 'Virtual Identity' is not enough.
For instance I have several email<EMAIL_ADDRESS>and<EMAIL_ADDRESS>all going to the same email account<EMAIL_ADDRESS>and I would like to reply only with<EMAIL_ADDRESS>(it often happen when you migrate from one email provider to another)
In this case I have to use the Thunderbird 'Correct Identity' to associate<EMAIL_ADDRESS>with<EMAIL_ADDRESS>Such advanced identity selection is then useful in case of email migration and for fighting spam/tracking (see plus addressing and subdomain addressing)

@saintger In this case, you just have to not configure<EMAIL_ADDRESS>identity at all and it would work, wouldn’t it?

@ArchangeGabriel It works if you have only one identity. With several identities, Thunderbird has no way to guess the mapping.

Ah, yes, didn’t thought of the case of multiple identities for one account + other identities related to this account but not registered in the settings. Doesn’t Thunderbird uses the default identities of the account in this case? This could be enough if you want to answer all non-registered identities with only one other address, but I agree this doesn’t solve all use cases.

@saintger @ArchangeGabriel: Please don't spam this issue by discussing the finer points of another implementation. You've stated your use cases.

Was going to raise this myself, glad to see somebody else has.  It seems fairly common practice to have floating @mydomain for signing up to stuff.
The Thunderbird plugin is fairly heavy on the implementation and could probably be simplified.
It's worth noting that things can get confusing if you're using distribution lists or BCC, as the "to" field is sometimes not your address.
I would suggest in the event that the To: field does not match a pre-configured identity, then you have the option of selecting any To: or Cc: address when you press on the From: header in the compose screen.
I think you would need to include a final option for "Enter custom..." or similar if none are applicable.
In the event you have a frequently used situation where you need the same custom entry on a regular basis you can use the existing identity functionality to provide a pre-configured identity.

Even if the To: does not match your domain, you can still check out another header (was it Delivered-To:? Not sure) which is the reason the list server routed the message to you. Gmail does this effectively with lists.

Indeed.  You can have Envelope-To: and Delivered-To: too.  I find that Delivered-To:
Delivered-To: is generally the final mailbox, so for me it's @localhost
Envelope-To: is sometimes included, I find that this is usually the single mail-box that my catch-all forwards to.
You can also mine the Received: headers, as sometimes you will have "from X by Y for user@domain".
Seeing the original & actual email destination, is not always feasible.  Which is why whatever is done, a free-text entry is a must for this feature to be useful.  Address selection is almost a nice-to-have in comparison :)

Just being able to manually type in the From: address on sending an email would be good enough for me. Finding out the proper From: on reply would be a nice to have addition that could be saved for later.

I was about to file this request as well, glad to see it's already been raised.
One suggestion I'd like to add is to simply enhance the "Email address" field of the Identity editor to accept wildcards, such as<EMAIL_ADDRESS>Then if mail arrives for<EMAIL_ADDRESS>replying to it will match that wildcard identity and populate the sender as<EMAIL_ADDRESS>and likewise for<EMAIL_ADDRESS>or<EMAIL_ADDRESS>Making the From field editable would be nice as well, but I think simply allowing wildcard matching for existing, configured identities would cover 90% of these use-cases without requiring the user to manually type in their preferred From address based on the received To address.

@ottlinger it seems your issue alligns more with https://github.com/k9mail/k-9/issues/1117

Using v5.600 and identity selection does not work - always sending out with default identity and not using the one selected while sending the email - recipient receives email always with default identity.
This makes additional identities useless as they do not work.

I posted a $250 bounty on bountysource for this here: https://www.bountysource.com/issues/815849-arbitrary-from-address
There is a patch linked there against a very old version of k9 mail. Not sure how hard it would be to adapt.
I may need to contact bountysource and have them relink it to this issue or something (haven't used the site before). They seem to be having some issues with their API server right now, so I will check in with them next week after the Thanksgiving holiday.

Okay, bounty has been fixed and now applies the this github issue.
https://www.bountysource.com/issues/28901565-enhance-k9-mail-identity-selection

This is something I'm interested in as well and I'm considering to implement it.
Had a brief look at the code already and noticed that the "from" address is already filled, if an existing identity in k-9 matches one of the "to" fields of the original mail: https://github.com/k9mail/k-9/blob/b9eba6971fa86b95a4855caddbfa7144e5c23884/app/ui/legacy/src/main/java/com/fsck/k9/activity/MessageCompose.java#L1281-L1287
So to summarize what is missing from my point of view:

An option to enable editing the "from" field in the compose screen manually. Regarding UX when this option is enabled I propose to add an option to the "send as" menu to every account that has this option enabled and when this new option is selected, the user can edit the "from" field in the compose screen. This way we know which server to use. If we allowed editing in the compose screen from the beginning, this would be complicated to determine in case a user has multiple accounts.
Advanced matching for the "from" adress. The user can configure an account to be the domain owner in which case any address with that domain in the "to" fields of the original mail can be used as "from" in the reply, regardless of whether it's an identity in k-9 or not.

@cketti is this roughly how it should be implemented?

Mozilla are going through a similar thing at the moment with Thunderbird, might be worth reviewing their change to see the considerations they made:
https://bugzilla.mozilla.org/show_bug.cgi?id=1518025

@simontb: Thanks for volunteering to work on this :+1:
The ability to use a custom "From" address shouldn't be a general setting. Instead, I want users to be able to mark an existing identity as having a catch-all address. Then tie the ability to provide a custom address to the existence of such an identity.
Here's a rough outline of what I think should be done. All of these should probably be separate pull requests:

Add a way to mark an identity as using a catch-all address (checkbox in EditIdentity?)
Add a way to edit the sender address when composing a message (maybe add a pen icon to catch-all identities and only allow users to provide the local part [+ name?])
Add support for catch-all identities when finding the identity to use for replying to a message. Use the address from the message instead of the (default) one from the identity.
Add support for importing/exporting the "catch-all" identity property

Because this feature involves a couple of changes I think we should add a BuildConfig flag to disable it for release builds while it is in development. It's probably enough to hide the additional UI when the feature is disabled. That way we can continue shipping beta versions without exposing a half-finished feature.
The smaller files this feature touches should probably be converted to Kotlin before making any changes to them (EditIdentity, IdentityAdapter, etc).
I haven't had time to read through the Thunderbird issue. From the title it appears they use a similar approach. If not we should consider copying their approach (I'd love for someone to summarize the Thunderbird issue). At the very least we should use similar wording for the UI parts.
For now I've only considered catch-all addresses like<EMAIL_ADDRESS>Eventually, we want to handle "plus addresses" (user+something@domain.example), too. Suggestion on how the user interface for this should look like are welcome.

@cketti my personal use case and need for this feature is a bit different.
I have a big IMAP post box that catches mail from various domains:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Let's say<EMAIL_ADDRESS>is the IMAP post box that catches mail for<EMAIL_ADDRESS>I would like to be able to have different SMPT settings in order to answer as<EMAIL_ADDRESS>although from a technical perspective the K9-identity is<EMAIL_ADDRESS>With Thunderbird I'm able to provide SMTP-details for each identity except from just setting the from-address ... does that make the use case clearer? It's not just plus addresses but different domains.

@ottlinger: That is a completely different feature request. It is tracked under #1117.

I wrote a post in the forum.
Please share your thoughts.
https://forum.k9mail.app/t/suggestion-placeholder-in-sender-use-one-identity-for-many-aliases/283

tyllmoritz's forum post describes the use of an unquoted space character, which is illegal in an email address, to be used as a placeholder in the configured From email address. I happen to think that this is a great idea.
For instance, all my outgoing mail will be<EMAIL_ADDRESS>So if  @dotancohen.com were configured as a default template for the outgoing From address, then not only would I save time for each mail, I would avoid typos.

Tying functionality to a space in an email address very much falls into the "confusing UI" category. I don't like that idea.

Tying functionality to a space in an email address very much falls into the "confusing UI" category. I don't like that idea.
You're right, it would be confusing.

A slightly-less-confusing UI could look like this:
When editing an identity, you can enter an E-Mail address. on the right side next to the input field for the email-address there are three "setting-dots". Here two settings are available:

"arbitrary sender address"
"arbitrary sender address (partially)"

the first option disables the E-Mail address input field.
the second option inserts "" into the input field, which is internally represented as an ascii control character, for example the space character or the substitute character.
As the second option is much more work, I'd be more than happy to just have the first option.

Please tell me how to combine identity and autocrypt!

@seppwarum: Please use the forum for support requests. If you want anyone to be able to answer your question you'll have to provide more context.

Yes, identities make life a lot easier, but only if you don't use OpenKeychain to encrypt messages.
Each identity created represents an address and needs its own key in OpenKeychain
(Thunderbird allows it to give each identity its own key).
Please remember this, when enforcing identities!

Tying functionality to a space in an email address very much falls into the "confusing UI" category. I don't like that idea.

Though I agree with you in general, in this case it doesn't actually have to be confusing.
The space is not a legal character in an email address, so it should fail validation when trying to send an email. So far so good.
Now, just do not forbid the space character in the verification for setting the default email address. If the user enters a valid email address in the default address field, it will work. If the user enters a space, then when he tries to send an email he is prevented from doing so by the failed validation, reminding him to update his FROM address.
This would be a power user feature and completely transparent to those who do not need it.

Absolutely agree that having custom "From" addresses would be super helpful (I am doing this myself with Thunderbird, in part through aliases and in part with partially-catch-all addresses configured on my mail server). I dare to add that nowadays it is a very basic feature that makes email life "tolerable" without having a super-duper AI Borg spam filter. I find the lack of this feature a big, big problem for k-9 on Android.
I'm not sure that the best way is to tie a particular k-9 identity to have custom catch-all addresses. I think it would be much simpler to do it as Thunderbird does, with virtual identities and allowing by default an editable "From" field (but of course prefilled with the default value of that identity).
However, at this point anything that allows to do that is better than nothing. K-9 is close to useless for me on Android, I can basically use it to only read emails but I need to use Thunderbird to reply back, very annoying.
The suggestion of also filling the "From" field according to rules depending on the receiver address would also be a wet dream, I could live without but would be very nice.
One thing that must be clear however is that the solution to create a different k-9 identity for every "From" address/alias is not useful. We are talking of managing 100-1000 different email address, very often not pre-configured but created on the fly at the whim of the sender.
Example: let's say that I have my POP on mydomain.com and my "real" email address is<EMAIL_ADDRESS>. Now, I want to create a rule for registering accounts on different online shops, and my mail server allows me to create aliases with wildcards. Then I create an alias of myuser@ which is eshop*@ . At this point, when I register a new account on stinkyfood.com I can register as<EMAIL_ADDRESS>while if I want to shop on verylongsocks.com I can use on the fly<EMAIL_ADDRESS>etc, all this without touching again the configuration of my mailserver.
As other users mentioned, this has various advantages: check if there is a misuse or leak of your data and where the abuse comes from, easily severing ties with a compromised account, archiving purposes etc.

Does K-9 have any notion of folder properties and properties inherited from parent folders? Mulberry has this, and a folder has a property of identity to use in replies (defaulting to the account's default identity). Moreover, identities are in their own inheritance hierarchy and so able to selectively inherit properties (like which SMTP server to use when sending). Bonus points for automatically constructing an identity from a plussed Recipient address, as I often use plussed addresses for website login names, which then get auto-delivered to different folders on my server via procmail.

I'm managing my email exactly like https://github.com/thundernest/k-9/issues/935#issuecomment-1047686206 is doing. I've read through this issue and a few of the referenced ones - my conclusion so far is, that setting a custom sender/mail from (generally) or based on the recipient of a certain email, is at the moment not possible in k9-mail?
Has there been any work done based on cketti's comment? https://github.com/thundernest/k-9/issues/935#issuecomment-654363050
Thank you for a quick update on this... (Reading the comments at least brought me an alternative email client "fairemail" on android that should support this...

Dear sir,
I use 1 account with 1 mailbox in k9 app. But I have created lots of different identities in this account with according mailaddresses.
All these addresses are forwarding to the same single mailbox.(these addresses are created in the account at my Internet and service provider)
Just like this identity @.***
So mails send to those different mailaddresses all arrive in 1 mailbox, 1 account.
The recipient of your mail had the same mailaddress @.*** .
I click on reply, and automatically k9 takes @.*** as sender.
So for every new identity you have to create a forwarding mailaddress at your service provider account. And also a new identity in K9 with that new mailaddress.
To make this easy, you need to have your own domain. Like i do :  mypost.be
Greetings

I would love to see function that use mail from "TO" that is one of my identity pin up to my email.
I currently noticed that I CAN manualy change email identity from list when replaying, but for replaying it use default one instead the one that someone send me a email on to.

Every identity should have a different email address !!!
It should be identical to the one you received an email to.
If the mailadres of one identity is identical to the one used in 'To' . Then k-9 will use that as 'From' when you click on 'reply'.
The name of the identity is unimportant. The mailadres is used, not the name.
You can test this by sending mails to your own identities.
Kind regards,
Stijn

What is the status of this feature/enhancement? Is this currently being worked on? If not, can this feature please get more attention. Thunderbird and also roundcube already support this. When can we expect for this feature to arrive in k9?
I know its not as easy as that, but in simple terms Cant we "just copy" the exact way thunderbird is handling this?
It works pretty well in thunderbird and also in roundcube, and its always k9 that causes some issues for me when i need to write email from my mobile because of the missing feature Use "to" address as "from" address when replying.
Please give this feature more attention, it`s been requested since 2015.

It works for me since 2 years. I 've lots of different identities. The
'to' should be identical to the mailadresses of the particular identity and it will become 'from' when you click  on 'reply'.
I think you made some mistake in your different identities.
Kind regards
Verstuurd vanaf mijn Smartphone. Excuseer mijn beknoptheid.
thrdroom @.***> schreef op 22 juni 2023 02:43:15 CEST:

What is the status of this feature/enhancement? Is this currently being worked on? If not, can this feature please get more attention. Thunderbird and also roundcube already support this. When can we expect for this feature to arrive in k9?
I know its not as easy as that, but in simple terms Cant we "just copy" the exact way thunderbird is handling this?
It works pretty well in thunderbird and also in roundcube, and its always k9 that causes some issues for me when i need to write email from my mobile because of the missing feature Use "to" address as "from" address when replying.
Please give this feature more attention, it`s been requested since 2015.
--
Reply to this email directly or view it on GitHub:
https://github.com/thundernest/k-9/issues/935#issuecomment-1601862904
You are receiving this because you are subscribed to this thread.
Message ID: @.***>

@thrdroom I've switched to FairEmail a few years ago, which supports the custom/dynamic From: addresses like TB on PC does.
@StijnJLL this is not about pre-setting-up identities but about dynamic (based on which address the mail has been sent to) setting of the sender address. The people (or at least me) that want this, have the ability to receive emails on a catch-all address and use this to generate arbitrary e-mail-adresses on the spot. Setting up an identity everytime totally defeats the convenience of this.

@StijnJLL this is not about pre-setting-up identities but about dynamic (based on which address the mail has been sent to) setting of the sender address. The people (or at least me) that want this, have the ability to receive emails on a catch-all address and use this to generate arbitrary e-mail-adresses on the spot. Setting up an identity everytime totally defeats the convenience of this.

Agreed, and I really find it puzzling that after so long there is still misunderstanding on what we are asking. I assume people who misinterpret the request have never used Thunderbird or Roundcube, but maybe it is us who are not explaining it well? Let me retry:
I would like to be able to manually edit the "from" field every time I send an email. As in: tap on the "from field", text box pops up, use keyboard to write<EMAIL_ADDRESS>Please forget about the "automatic rules to select a reply address according to the received email", I think at this point it's just a distraction, just give us the possibility to manually edit the "from" field every time we send an email, thanks!

I would like to be able to manually edit the "from" field every time I send an email. As in: tap on the "from field", text box pops up, use keyboard to write<EMAIL_ADDRESS>
I'd say this would be the absolute minimum solution to fulfill this requirement. But

Please forget about the "automatic rules to select a reply address according to the received email", I think at this point it's just a distraction, just give us the possibility to manually edit the "from" field every time we send an email, thanks!

as this is being offered by roundcube, thunderbird an fairemail (these implementations prove it's possible and not hard) it won't make me switch back to k9 mail - as manually modifying every email is waaay more unconvenient than having an automatic selection thats 95% correct.

Agreed, and I really find it puzzling that after so long there is still misunderstanding on what we are asking. I assume people who misinterpret the request have never used Thunderbird or Roundcube, but maybe it is us who are not explaining it well?

I guess, this is the real problem: the use case we're looking for hasn't been properly understood by anyone with the knowledge on how to implement it ....

@flcu thanks for the recommendation of FairEmail. The problem for me is that FairEmail has other limitations like no Oauth in fdroid version and the develeoper locks down a lot of features behind a "pro"-version. While K9 is only missing this one feature "dynamic (based on which address the mail has been sent to) setting of the sender address". I really really don't want to leave K9, but if this doesn't get implemented soon, im forced to leave, cause editing identities by hand before answering every email and/or creating hundreds of identities is an absolute no-go. Atm people get private email alias names which they should never know of in the first place!!!
@cketti I want to suggest a first quick solution to this problem which should be "preatty easy to implement" (excuse my ignorance) and which can be build upon later on.
Give us the option to use a wildcard identity.

When i use an asterisk in the first part of the email of the email field in the identity (*@domain.tld), then every time i hit reply in an email, k9 does use the X-Original-To: field from the header of that email.
This way the people who need dynamic identities based upon the X-Original-To: field could get that easily by just putting an asterisk in the first part of the email of the email field in the identity (*@domain.tld).
Is this suggestion above easy enough to be implemented quickly?
Alternative to<EMAIL_ADDRESS>could also be just an asterisk withtout any @domain.tld part.

Yes, I agree FairEmail has other limitations. At this point, whatever works better, really. Please :)

it's great to see this issue come back to some life.

Please forget about the "automatic rules to select a reply address according to the received email"
i've just double check this and it works.

but i agree that

it's just a distraction

becaus what's desperatly missing is

the possibility to manually edit the "from" field every time we send an email


Getting Error 2103 while installing otel agent on windows server.

Getting Error 2103 while installing otel agent on windows server.

This seems to indicate that you attempted to install the collector using a per-user installation from the system account. Only machine installations are permitted from the system account. Read more here.


add support for istio.io/waypoint-for on gatewayClasses

Please provide a description of this PR:
add support for istio.io/waypoint-for on gatewayClasses

@ilrudie: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e242aec85b5b038d65ec23397127bbfadf6a0635
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ilrudie: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e242aec85b5b038d65ec23397127bbfadf6a0635
link
true
/test release-notes

lint_istio
e242aec85b5b038d65ec23397127bbfadf6a0635
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ilrudie: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e242aec85b5b038d65ec23397127bbfadf6a0635
link
true
/test lint

release-notes_istio
8045d3c151142c69c2b3c38596b0c3c02e6160c3
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Finagle 1.10.0, Util 1.12.12

Latest finagle and util, which contain a source-compatible but binary-incompatible change to tracer factory code.  We need to publish this ASAP, as any code using the latest finagle and querulous 2.6.x is broken.

ship it!

Ugh, it turns out this doesn't help because finagle has been changed in master since the publish yesterday.


Remove failing description in copy/paste example in action.yml

The comments there are supposed to contain code that our users (developers) can copy/paste into their file. Right now if they do that their file will fail. This will fix that.

Looks good to me.


Add Neonmarker & set zap platform

I may have been over zealous in setting the ZAP platform tag. I just noticed that CONTRIBUTING.md actually suggests it's just for add-ons 🤷 Let me know, happy to adjust.

@kingthorin
Oh, thank you so much!  I missed while migrating the existing data 😭
Platforms are included in README's Badge, so I think it's better to include as much as possible if it's related!
Before this big change, it was actually a document that only included addons, but now it will also include a zap scripting repo of users. (I can't miss good resources that aren't included in the community-script 🤩)


Updated Twitch

Updated link

I don't understand why you created another commit to update the Twitch links but I don't care. However, thank you @rmlewisuk :)

I meant to comment on this — the sites are updated in the sites.json file and not the html files so I did it manually. Thank you for your contribution.


Deprecate defaultBuilder in GAPIC java surface

Codecov Report

Merging #1551 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1551   +/-   ##
=========================================
  Coverage     87.04%   87.04%
  Complexity     4205     4205
=========================================
  Files           408      408
  Lines         16866    16866
  Branches       1832     1832
=========================================
  Hits          14681    14681
  Misses         1695     1695
  Partials        490      490

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 cff2a1c...9aeb175. Read the comment docs.

The changes LGTM, but is there an issue or something that discusses why we are making the changes in this PR and https://github.com/googleapis/gax-java/pull/370?

@michaelbausor this is a TODO item in the GAX GA blocker list. The motivation behind this is that we should be consistent of using either newBuilder or defaultBuilder.


Auto-create Topics as part of docker-compose

Is there a variable that can be set in docker-compose to auto create topics?  I don't see anything in the documentation.

The Confluent images don't support an environment variable for this, only the wurstmeister containers do.
Otherwise, you could use minikube instead, for example, and run Strimzi or Confluent Operator and create topics with kubernetes resource files rather than just variables


Add a how-to for networking on OS X

It's not exactly trivial, but it is possible to get Nerves under QEMU on OS X to talk to the network:

https://github.com/bendiken/nerves_system_qemu_arm/tree/howto-networking#networking
A remaining deficiency of networking under QEMU (other than the overall complexity of the procedure) is that DNS resolution in the VM doesn't seem to work unless one explicitly specifies the nameservers to be used directly to Erlang's inet_res:
iex(1)> :inet_res.lookup('nerves-project.org', :in, :a)
[]
iex(2)> :inet_res.lookup('nerves-project.org', :in, :a, [nameservers: [{{8,8,8,8}, 53}]])
[{192, 30, 252, 153}, {192, 30, 252, 154}]

That doesn't seem like it would be a QEMU-specific problem, necessarily, but I haven't investigated further in nerves_networking as yet. Other than that caveat, everything seems to work as it should. Remote IEx shell sessions to the QEMU virtual machine work great, for example.
Kudos to @mikegogulski who first figured this out for Linux, based on which I adapted to OS X. (Linux instructions forthcoming in a follow-up pull request once they've been cleaned up and tested from scratch on a new brand new 16.04 install.)

Sweet! I can't wait to try this out. Can't do it today - but should be able to tomorrow!

@fhunleth If you would go ahead and merge this, @mikegogulski would proceed to create another pull for the Linux instructions.


Contributing/project's future

Are you still looking to move forward with this extension? I happened upon it today, and coming from a web developer background I would love to be able to use this in my projects.
Along those lines, if there's anything that needs contributing towards, do let me know and I'll be happy to help where I can.

Hello! I'm happy to know that this extension would be useful for you!
I'm still looking forward with ReactGD, but as the idea grows, it's more difficult to implement functionalities that works smoothly with the Godot's built-in features.
Right now I'm trying to figure out the best way to describe the component node tree into a virtual node tree to make it easier and performant to update the actual node tree at the same time, that way you can add components to the UI without having then interfering with the actual Control nodes hierarchy, for example:

This hierarchy wouldn't allow VBoxContainer to sort the Buttons that are children of components, so I'm thinking of having something like this instead:

That way, I would still have components inside the tree hierarchy, but they will be represented as virtual nodes, and the actual nodes would be inside the actual node tree.
I think this is the same concept used in ReactJS, of having a virtual tree that are rendered into the actual page, so I'm experimenting with some ways of implementing this idea in ReactGD.
If you have any idea or feature for this project, feel free for opening a issue in this same repository.
Thank you!


Lambda Layer Update

Value Statement
Add lambda layers for each lambda. Reuse layers when able (e.g. pscyopg2). Clean up github actions that are creating virtual environments and zipping that up to push to the lambdas.
There is an associated infra ticket to get the environments into AWS.
Checklist

[ ] Layers created that cover all lambdas
[ ] Actions cleaned up

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @ianperera @jakehova @k-macmillan @kalbfled @trevor2718 @ldraney

We do this now.


Typescript labeled as C++

Expected Behavior
Screenshot from Github

Actual behavior
Screenshot from onefetch

Minimal Steps to Reproduce

Good Idea, maybe I can add  a "Duplicates" Section in the new bug_report.yml issue form that will mention #26 - and possibly other recurring issues.


[SourceKit] Add "Inactive Ranges" request

source.request.inactiveranges is a new request that reports all #if, #else and #elseif decls in the response with an is_active flag. This is mainly useful for a client to know which branches are inactive, but for completeness sake, the active decls are also reported.
Note: it only reports the positions of the decls, not the entire ranges. It's up to clients to map this to the syntactic structure of a tree. Reporting the ranges of the decls could be confusing in the case of nested #ifs, where the ranges can overlap.

@swift-ci please test

@swift-ci please test

@swift-ci please test

Thanks for adding this request, Louis.
One naming idea: Since the request is reporting both active and inactive ranges, what do you think about dropping the negation and just talking about active ranges instead of inactive ranges?

@ahoppen To be clear, you mean just changing the name of the request, right? Not changing what it reports?

To be clear, you mean just changing the name of the request, right? Not changing what it reports?

Yes

Renamed request to "Active Regions".

@swift-ci please test

@swift-ci please test


Fixed regression in the maven site rendering

https://github.com/mojohaus/versions-maven-plugin/issues/536
Maven Site Plugin and Doxia switching to HTML 5 broke all the reports that includes images.
Including other report plugins.
The proposed fix allows to return back to the original compact format that was more synthetic.

comments removed.


Add variable suggestions for NamedParameters

function Test()(string <caret>){
    name = "Ballerina";
}

When the caret is positioned at the above location, we should suggest name.

Plugin is being re-written and will be resolved in the new version.


DOC: Add more description of EVP_PKEY_fromdata(), and examples

Fixes #11131

Travis failures look relevant.

make doc-nits failed

make doc-nits failed

/usr/bin/perl ./util/find-doc-nits -n -l -e
doc/man3/EVP_PKEY_fromdata.pod:1: Section missing in OSSL_PARAM_allocate_from_text()
*** ERROR: Apparent command =head1 not preceded by blank line at line 17 in file doc/internal/man3/s2i_ASN1_UTF8STRING.pod
Makefile:1752: recipe for target 'doc-nits' failed
make: *** [doc-nits] Error 1

So, er, how did that get the through?

Travis failures look relevant.

Actually wasn't, but I've added a cleanup commit nonetheless.

So I still do not get the point of EVP_PKEY_param_fromdata_settable(). Whatever that returns should be in the documentation.

So we have a section that says:
EVP_PKEY_fromdata() creates key parameters or a key, given data from I<params> and a context that's been initialized with EVP_PKEY_param_fromdata_init() or EVP_PKEY_key_fromdata_init().  The result is written to I<*ppkey>. The parameters that can be used for various types of key are as described in the "Built-in RSA Import/Export Types" section on the L<provider-keymgmt(7)> page.
This needs a rewrite.
Clearly, the various key types is more than just RSA.
As far as I know, it doesn't "create" parameters or a key. I can at least confuse create with generate.
Since we pass a EVP_PKEY **, I assume an EVP_PKEY might be allocated (if *pkey is NULL?). I also assume that the EVP_PKEY will get associated with the EVP_PKEY_CTX.
I think that first sentence is also trying to put too much into one sentence.

It might be obvious to you what the difference between parameters and the key is. But it would not hurt to repeat that, have an example with parameters. The provider-keymgmt could also clarify what is part of the key and what is a parameters.

Is there a reason why we need a difference between parameters and keys in these functions?

Is there a reason why we need a difference between parameters and keys in these functions?

You're the second person to ask.  These functions are fairly close to key / param generation, the only real difference that the numbers are humanly generated rather than randomly, and key / param generation is separated.
Also, I can easily imagine that someone wants to use hand crafted FFC params and then use key generation to get a DSA key.  It's also not too hard to imagine that a backend might want to check that it got any key numbers at all if it was given a selector that includes OSSL_KEYMGMT_SELECT_KEYPAIR.  In that case, trying to create an EVP_PKEY with just hand crafted FFC params would fail without a function that uses a more limited selector.
And before you ask, I don't think we should make the OSSL_KEYMGMT selectors public (or turn them into EVP selectors).  That's an entirely new concept, and one I'm not keen to let out all the way.  We might somewhere in the future, but let's let it mature in a controlled way, yeah?

So I still do not get the point of EVP_PKEY_param_fromdata_settable(). Whatever that returns should be in the documentation.

I agree that it should be in the documentation, but not in this documentation.  This is comparable to, say, ioctl(2), which doesn't describe any specific parameter in detail, but refers to other pages where they are enumerated.

So we have a section that says:
EVP_PKEY_fromdata() creates key parameters or a key, given data from I<params> and a context that's been initialized with EVP_PKEY_param_fromdata_init() or EVP_PKEY_key_fromdata_init().  The result is written to I<*ppkey>. The parameters that can be used for various types of key are as described in the "Built-in RSA Import/Export Types" section on the L<provider-keymgmt(7)> page.
This needs a rewrite.
Clearly, the various key types is more than just RSA.

Yes.  The way we're currently documenting the diverse key parameters in our implementations is an abomination in my mind.  I have an idea where to move them, though.  At that point, the reference here will have to change.  Can you tolerate that it looks bad for now, or would you prefer that the key parameters documentation gets moved first?

As far as I know, it doesn't "create" parameters or a key. I can at least confuse create with generate.

Yes and no.  The backend creates an internal keydata structure, and a new EVP_PKEY gets created by libcrypto.  In that sense, "create" is quite correct.  Also, it is conceptually close to key generation, the only real difference is where the numbers come from (human vs random number device).  Also, have you noticed the title of this page?  (emphasis mine)

=head1 NAME
EVP_PKEY_param_fromdata_init, EVP_PKEY_key_fromdata_init, EVP_PKEY_fromdata,
EVP_PKEY_param_fromdata_settable, EVP_PKEY_key_fromdata_settable

functions to create key parameters and keys from user data

That being said, would this introduction work better for you?
EVP_PKEY_fromdata() creates the structure to store key parameters or a key, ...

Since we pass a EVP_PKEY **, I assume an EVP_PKEY might be allocated (if *pkey is NULL?). I also assume that the EVP_PKEY will get associated with the EVP_PKEY_CTX.

Correct, the EVP_PKEY might be allocated (if *pkey == NULL).  It might also be overwritten (if *pkey != NULL).  Just like with key generation.
The EVP_PKEY_CTX has the same function as for key generation, i.e. it holds pointers to the backend, which is then used when actually creating the keydata structure.  It may also be used to set other parameters between fromdata_init and fromdata, which might affect aspects of keydata creation.  We currently do not have any such parameters (or well, I'm sure @romen could argue that the cofactor setting could be used here), but...

I think that first sentence is also trying to put too much into one sentence.

I'm open for suggestions.

On Fri, Mar 06, 2020 at 12:41:33AM -0800, Richard Levitte wrote:

So I still do not get the point of EVP_PKEY_param_fromdata_settable(). Whatever that returns should be in the documentation.

I agree that it should be in the documentation, but not in this documentation.  This is comparable to, say, ioctl(2), which doesn't describe any specific parameter in detail, but refers to other pages where they are enumerated.

My point is that this function should not exist. The example
program you wrote for it just writes things that should be in the
documentation. Please provide an other usecase for this function
than printing what's already in the documentation.

Since we pass a EVP_PKEY **, I assume an EVP_PKEY might be allocated (if *pkey is NULL?). I also assume that the EVP_PKEY will get associated with the EVP_PKEY_CTX.

Correct, the EVP_PKEY might be allocated (if *pkey == NULL).  It might also be overwritten (if *pkey != NULL).  Just like with key generation.
The EVP_PKEY_CTX has the same function as for key generation, i.e. it holds pointers to the backend, which is then used when actually creating the keydata structure.  It may also be used to set other parameters between fromdata_init and fromdata, which might affect aspects of keydata creation.  We currently do not have any such parameters (or well, I'm sure @romen could argue that the cofactor setting could be used here), but...

Please document that.

My point is that this function [EVP_PKEY_param_fromdata_settable()] should not exist.

openssl provider and openssl list will use this type of function to display what any chosen provider (not just ours) can handle.  Also, the array it returns can be use with functions like OSSL_PARAM_allocate_from_text(), should anyone want to write a program that can use named parameters (you know, the usual -pkeyopt key:value form) to create keys.
We've pretty much made it a pattern that any set_params() or get_params() function should come with a settable() or gettable() function as well.  Do you disagree with that principle, or is it rather that you see reasons not to follow that pattern in this case?
I agree that there should still be documentation, though.

Please document that.

Okie, will do

Please provide an other usecase for this function than printing what's already in the documentation.

I think I'd like to defer that to a cookbook kind of thing, which would involve a number of other functions described in other man-pages.  In other words, not in this PR

Regarding a cookbook thing, which is something I think we should do, we need to discuss where and how.  That's a subject for the openssl-project list

So I still do not get the point of EVP_PKEY_param_fromdata_settable(). Whatever that returns should be in the documentation.

This is up to each provider or algorithm to do.  It returns the list of settable parameters for an algorithm.  Writing much more than that would be difficult -- perhaps some universal parameters could be listed.  "key" for a cipher, "iv" for a mac.  I'm sceptical as to the benefit.

"key" for a cipher?

openssl provider and openssl list will use this type of function to display what any chosen provider (not just ours) can handle.  Also, the array it returns can be use with functions like OSSL_PARAM_allocate_from_text(), should anyone want to write a program that can use named parameters (you know, the usual -pkeyopt key:value form) to create keys.
We've pretty much made it a pattern that any set_params() or get_params() function should come with a settable() or gettable() function as well.  Do you disagree with that principle, or is it rather that you see reasons not to follow that pattern in this case?

I have a problem with the pattern in all cases. All the providers
should come with documentation.
I have to think about the OSSL_PARAM_allocate_from_text() case,
but at the moment I don't see it.

All the providers should come with documentation.

No one says anything else.  #11270 is an attempt in that direction.
However, I don't see why documentation and the settable/gettable functions would be mutually exclusive.  As a matter of fact, we could use those functions via some commands to see that our implementations and the docs are in sync.

Where are we on this one?

This issue is in a state where it requires action by @openssl/committers but the last update was 30 days ago

PING!

The cost of one person adding an extra four spaces, compared to the global cost of inconsistency and possible confusion.

This pull request is ready to merge

Merged.
476de2e5e598b46289c6087df04d1bc1886d6ef2 DOC: Add more description of EVP_PKEY_fromdata(), and examples
ccb47dbf47b36da849301aae38c32ed019e75a21 DOC: Extend the description of EVP_PKEY_CTX_new_from_name()


--no-wait doesn't work on generic updates [Knack]

I have a fix, but it will be in a future PR.

PR merged.


NameError: name '_get_skill_dirs' is not defined.

https://github.com/OpenVoiceOS/OVOS-workshop/blob/66b02cd374cef92bd33f51a83b7cdc07205d6e10/ovos_workshop/skill_launcher.py#L566
Commit 308ff2d4430442c10cb077003ba51cf305fb1b67 broke the skill launcher, crashing some skills: chatgpt fallback, and mikejgray/neon-homeassistant-skill
2023-12-29 10:14:28.163 - OVOS - ovos_utils.intents.intent_service_interface:<module>:8 - WARNING - Deprecation version=0.1.0. Caller=ovos_utils.intents:1. ovos_utils.intents moved to ovos_workshop.intents
2023-12-29 10:14:28.179 - OVOS - ovos_utils.intents.converse:<module>:7 - WARNING - Deprecation version=0.1.0. Caller=ovos_utils.intents:3. ConverseTracker has been deprecated without replacement
2023-12-29 10:14:28.192 - OVOS - ovos_utils.intents.layers:<module>:3 - WARNING - Deprecation version=0.1.0. Caller=ovos_utils.intents:4. IntentLayers moved to ovos_workshop.decorators.layers
2023-12-29 10:14:28.206 - OVOS - ovos_utils.intents:<module>:7 - WARNING - Deprecation version=0.1.0. Caller=ovos_utils.events:7. ovos_utils.intents moved to ovos_workshop.intents
2023-12-29 10:14:28.342 - OVOS - ovos_utils.enclosure:<module>:8 - WARNING - Deprecation version=0.1.0. Caller=ovos_plugin_manager.templates.tts:41. ovos_utils.enclosure has been deprecated!
2023-12-29 10:14:28.380 - OVOS - ovos_utils.enclosure.api:<module>:3 - WARNING - Deprecation version=0.1.0. Caller=ovos_plugin_manager.templates.tts:41. EnclosureApi has moved to ovos_bus_client.apis.enclosure
2023-12-29 10:14:28.401 - OVOS - ovos_utils.skills.locations:<module>:10 - WARNING - Deprecation version=0.1.0. Caller=ovos_utils.skills:3. ovos_utils.skills.locations moved to ovos_plugin_manager.skills
2023-12-29 10:14:28.474 - OVOS - mycroft:<module>:37 - WARNING - mycroft has been deprecated! please start importing from ovos_core and companion packages
mycroft module remains available for backwards compatibility and will be removed in version 0.2.0
Traceback (most recent call last):
  File "/home/ovos/.venv/bin/ovos-skill-launcher", line 8, in <module>
    sys.exit(_launch_script())
             ^^^^^^^^^^^^^^^^
  File "/home/ovos/.venv/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 657, in _launch_script
    skill = SkillContainer(skill_id)
            ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ovos/.venv/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 566, in __init__
    for p in _get_skill_dirs():
             ^^^^^^^^^^^^^^^
NameError: name '_get_skill_dirs' is not defined. Did you mean: 'get_skill_class'?

Some great, big development sprint is going on currently. I have reported similar issues over at the Matrix channels.
Guess we caught the Python guru's in the middle of their work, so let's be patience and wait and see.
Keep you posted.


fix: change ftp server to file server

Related to Issue #96
The name 'FTP server' is confusing since the KVM host is now capable of hosting and serving necessary files via http only. Update the docs and variables to represent this change.
Also, enable using either ftp or http to serve config files for the bastion. FTP is still the only option for booting the KVM hosts, and HTTP will still be installed and used on the bastion as it is required. But with these changes, someone using a pre-existing KVM host can use only HTTP. And someone using an FTP server for booting of the KVM host can use that same FTP server to boot the bastion.

Received feedback from users that this was confusing to them, decided to tackle it today. Tested a highly-available deployment (3 LPARs, macvtap) with env.file_server.protocol as 'ftp' and entire test run as 'http'.

A guest on a KVM host does not have a network connection to the KVM host via macvtap !
Ah, you are correct, my apologies! I've updated the description. Looks like none of the code has to change, but that was a lapse in my understanding, thanks!

Everything else look ok @smolin-de ?

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Stopped containers are shown as running

Hello !
This is really great app. Thanks for your work.
There is only one issue for me. I have 2 containers one of them is exited (screenshot) but in the app dashboard it shows that 2 are running and also in the menu it has Stop option instead of Start. Tried appimage and flatpak versions on arch linux. Faced same problem in both.

P.S. will there be option in the future to keep app running in system tray ?

In next release those bugs will be solved

Yup, System Tray is planned

good to hear.. thanks )


[stress] separate playbook into 3 parts

Coverage remained the same at 34.607% when pulling 4637c7349bc22e8926926fe0ec87247ac1decd1b on yuye/part-fix into 02c0ed0670d90f7eab481e02733cdb91f74f609b on master.


MinIO integration doesn't work if release name is not kube-image-keeper

What I do:
Install kuik with MinIO integration, using a release name of kuik, like this:
helm upgrade --install --namespace kuik --create-namespace \
--repo https://charts.enix.io/ kuik kube-image-keeper \
--set minio.enabled=true \
--set minio.auth.existingSecret=minio-root-auth

kubectl create secret generic minio-root-auth --namespace kuik \
--from-literal=root-username=root --from-literal=root-password=very.secret.password

What I expect to see:
kuik starts fine
What I see instead:
The minio provisioning pod fails to start:
$ kubectl describe pod kuik-minio-provisioning-vpzlg | tail
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason       Age                   From               Message
  ----     ------       ----                  ----               -------
  Normal   Scheduled    7m17s                 default-scheduler  Successfully assigned kuik/kuik-minio-provisioning-vpzlg to scw-cli-k8s-happy-swirles-default-489a13773af9
  Warning  FailedMount  66s (x11 over 7m18s)  kubelet            MountVolume.SetUp failed for volume "users-secret-0" : secret "kube-image-keeper-minio-registry-users" not found
  Warning  FailedMount  66s (x11 over 7m18s)  kubelet            MountVolume.SetUp failed for volume "registry-keys" : secret "kube-image-keeper-s3-registry-keys" not found

And the secrets seem to have an extra kuik- prefix:
$ kubectl get secrets
NAME                                              TYPE                 DATA   AGE
kuik-kube-image-keeper-minio-registry-passwords   Opaque               1      6m39s
kuik-kube-image-keeper-minio-registry-users       Opaque               1      6m39s
kuik-kube-image-keeper-registry-http-secret       Opaque               1      6m39s
kuik-kube-image-keeper-s3-registry-keys           Opaque               2      6m39s
kuik-kube-image-keeper-webhook-server-cert        kubernetes.io/tls    3      13m
minio-root-auth                                   Opaque               2      6m52s
sh.helm.release.v1.kuik.v1                        helm.sh/release.v1   1      13m
sh.helm.release.v1.kuik.v2                        helm.sh/release.v1   1      6m40s

Theory:
I see that the Secret name (defined in minio-registry-users.yaml) builds on {{ include "kube-image-keeper.fullname" . }}.
I don't know for sure where the MinIO provisioning pod gets the Secret name from. Maybe the subchart values, specifically
minio.provisioning.usersExistingSecrets which defaults to [ kube-image-keeper-minio-registry-users ] in the kuik chart default values.
Further notes:
I don't know if this is easily fixable.

Ideal scenario: find a way to inject that secret name into the minio subchart.
Less ideal but still cool scenario: in the kuik chart, don't use kube-image-keeper.fullname; just use a common value between the kuik chart and the minio subchart.
Less less ideal scenario: just document this as a shortcoming (and/or issue a warning in NOTES.txt when using a different release name).

:tada: This issue has been resolved in version 1.5.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Problems with using multiple GPUs

What is the issue?
When CUDA_VISIBLE_DEVICES=1,2 is used, and Ollama pulls a model, it only uses GPU numbered 1. unless ollama runs another model, GPU numbered 2 will be used. In this way, if Ollama turns on parallelism, parallel reasoning for the same model will only be performed on gpu 1, and the parallel speed is very slow. How can Ollama use multiple GPUs for one model on inference ?
OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.38

Hello, since this was labeled as a BUG less than 12 hours ago, would it be safe to asume that this issue is still present in version <IP_ADDRESS> for Windows ?

I know this may not be what you're looking for but multi-gpu works perfectly fine for me on docker, so if you were to run it on docker it could avoid this issue for you

Duplicate of #4198


ESBuild

Replaces Rollup and Webpack with ESBuild and Vite.

This PR uses ESbuild for building libraries (@medplum/core, @medplum/react, etc).
What is Vite?
Vite is a build tool that aims to provide a faster and leaner development experience for modern web projects.
This PR uses Vite for building apps (@medplum/app, @medplum/graphiql)
Note that we already use Vite in most of our example applications (medplum-hello-world, foomedical).
Why make this change?
There are many reasons to adopt ESBuild and Vite.  The main two:

Performance - these tools are much faster than predecessors because (1) they're written with faster tools such as Go and (2) they don't have as much legacy baggage such as support for outdated versions of JS.
Modern alignment - these tools are more aligned with the future of JS/TS, such as better support for ESM.

We have actually tried to make this change many times in the past.  However, it has always got stuck for some reason or another (bugs, incompatibilities, dependency conflicts, etc).  This time it looks like it's going to work.
Who uses these tools?
Notably, the TypeScript team themselves started using ESBuild for building TypeScript: https://github.com/microsoft/TypeScript/pull/51387
Vite is used by many organizations such as [...]
Benchmarks
Build time
Method:

Run "time npm run build"
Take the best of 3
Calculate speedup as Told / Tnew

2x app speedup to 8x react speedup!
Package size
Method:

Build
Create tar of files shipped to browser

Package size is slightly larger (1-2%)
Dev server start time
This is difficult to measure objectively.
Using app:
Webpack reports start time of 15.513 seconds:

Vite reports start time of 0.562 seconds:

Foo Medical
Before:

Main index.js is 188.21 kB gzipped
After:

Main index.js is 208.70 kB gzipped
So 11% bigger.  Not great.  That might warrant some investigation.

coverage: 94.115% (+0.01%) from 94.105% when pulling fb187007fe3be62e7d39192320472505bdce26df on cody-esbuild2 into 09379acff959468dec3719c0149f18ed564daf9d on main.

Glad to see the window opening for this change!  I recall it getting stuck 6 months ago and am surprised/pleased that the window opened up now.


add Royal Danish Academy

@ALharchi First stage of verification passed, official domain is kglakademi.dk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ALharchi Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[docs]: Add Tokens pages

Implement docs pages for tokens, using the new 11ty plugin
https://xd.adobe.com/view/54aea3e4-4896-4823-9833-e40f1195e7c6-01fd/grid
One approach to implementing search:
https://claytonerrington.com/blog/adding-a-basic-search/
or maybe https://pagefind.app/

The XD for this is still locked, I have to type the text content in manually.


xplayer: 2.4.0 -> 2.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xplayer/versions.
meta.description for xplayer is: "A generic media player from Linux Mint"
meta.homepage for xplayer is: "https://github.com/linuxmint/xplayer"
meta.changelog for xplayer is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/xplayer passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/xplayer-video-thumbnailer passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/xplayer-audio-preview passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/.xplayer-wrapped passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/.xplayer-wrapped_ passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/.xplayer-video-thumbnailer-wrapped passed the binary check.

/nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/.xplayer-audio-preview-wrapped passed the binary check.

Warning: no invocation of /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin/..xplayer-wrapped-wrapped had a zero exit code or showed the expected version

7 of 8 passed binary check by having a zero exit code.

3 of 8 passed binary check by having the new version present in output.

found 2.4.2 with grep in /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2

found 2.4.2 in filename of file in /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2

directory tree listing: https://gist.github.com/c0c5cfed29bdaa9adfe660842574bf9d

du listing: https://gist.github.com/3ac876042eb1647700e43b3da978fd33

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
xplayer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xplayer https://github.com/r-ryantm/nixpkgs/archive/1bf40576bc6aa03bdeecbc86daedcb31177b418c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2
ls -la /nix/store/gmgbvdbbwlhqvf9zsl34zqjj5c1nkn62-xplayer-2.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

xplayer

Maintainer pings
cc @tu-maurice for testing.

Result of nixpkgs-review pr 133886 run on x86_64-linux 1

1 package built:

xplayer


Re-scale rank chart for returning players

I've just got back into using ScoreSaber after the Quest update (yay!), after previously using the older version back on 1.13.
On the web front-end, if you've been inactive for a while and are given a #999999 global rank, then the rank chart is pretty unhelpful until 50 days have passed:

This PR removes #999999 ranks from the beginning of the history, if there are real ranks following it:

(If the entire history is #999999 ranks, then it isn't changed.)
I personally think this is an improvement since it makes the chart more useful to a returning player, but I understand it's a subjective change, so up to you on whether you'd like to merge!

Merged 👍 not sure why it didn't automatically close


Dev/rest

REST based datasource #714
Added 2 new files

RESTDataProvider.ts
RESTDataProviderTest.ts

Can be closed now as we have other PR


Install fails

Using ember 2.10 ember-cli on a newly generated project, ember install ember-cli-mocha hangs.

Other ember-cli functions are having issues.  This does not appear to be just the add on.

this is most likely the same issue as #159


Free 3D models & other content (info)

Here is collection of links for free and/or opensource 3D resources, mostly on aviation thematic, that founded on different open web resources!

Most usefull mesh formats are: *.3ds, *.obj, *.blend, *.ac (AC3D), *.wrl

BES Scene Collection - http://dcgi.felk.cvut.cz/home/havran/BES/scenes/
VRML Object Librarys - http://www.web3d.org/x3d-resources/vrml/objects/oblib.htm
OpenGameArt - http://opengameart.org
FlightGear MEMBERS - https://github.com/fgmembers
FlightGear repositary - http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/
Open 3D Model.com - http://open3dmodel.com/category/aircraft
Lemma Soft Forums • Creative Commons - https://lemmasoft.renai.us/forums/viewforum.php?f=52
3D Society (russian lang) - http://www.3dsociety.ru/3dmodels
3-D Model Supercars by Mick Imrie and Austin Tate - http://www.aiai.ed.ac.uk/~bat/GA/supercar-3d.html
Artist 3D (free for non-commercial)- http://artist-3d.com/free_3d_models/
Simple aircrafts models -  http://www.anuspanda.smallboytrackbikes.co.uk/models-aircraft.html
Savage collection of Helicopters - https://savage.nps.edu/Savage/#AircraftHelicopters
Savage collection of Fixed Wings - https://savage.nps.edu/Savage/#Section1
Google 3D Warehouse - https://3dwarehouse.sketchup.com/
Thingiverse - http://www.thingiverse.com/
Archive 3D - http://archive3d.net/
NASA Catalog - https://catalog.data.gov/dataset?tags=3d-model
--
Free models links - http://www.dmi-3d.net/freemodels.html
Yegi (search free model) http://www.yeggi.com/q/+aircraft/?s=tx
36 sites with freeware 3D content - http://www.freesoftwaremagazine.com/articles/35_free_3d_model_sites_compatible_free_blender_animation_projects
Repositories overview - http://www.blendernation.com/category/art/repositories/
--
YSFScripts for Blender 2.49 - https://forum.ysfhq.com/viewtopic.php?t=1586
Installing YSFScripts in Blender - https://forum.ysfhq.com/viewtopic.php?t=2709


French Guiana is linked to France & listed as France

Please fix.

Wikipedia states that French Guiana is an overseas territory of France, the naming would technically be correct.

Can I work on this issue ?

I'm not sure if this is a still relevant issue given what @mzeinstra said, @peterspdx, could you please confirm what you'd expect the behavior to be?

If this issue is still relevant, I request to be assigned to it.

@TimidRobot to determine next steps.

I don't believe it is contested that French Guiana is part of France and that French law applies, including case law. See https://en.wikipedia.org/wiki/Overseas_France


Sigh failing on MacBook with URL error.

Consulting with @shaper and filing issue to track.
Attempting to run ./tools/sigh produces:
yuin-macbookpro:arcs yuin$ ./tools/sigh
😌
🙋 check
🙆 check
🙋 peg
Skipping step; 'runtime/build/manifest-parser.js' is up-to-date
🙆 peg
🙋 railroad
Skipping step; 'manifest-railroad.html' is up-to-date
🙆 railroad
🙋 test
(node:30258) ExperimentalWarning: The ESM module loader is experimental.
    at startup (bootstrap_node.js:105:15)
    at bootstrap_node.js:666:3
{ TypeError [ERR_INVALID_URL]: Invalid URL: /var/folders/22/1mwk38yn1j9f6kzpq9j4sx1r004bmn/T/sigh-V49xVD/runner.js
    at onParseError (internal/url.js:217:17)
    at parse (internal/url.js:226:3)
    at new URL (internal/url.js:309:5)
    at resolve (file:///Users/yuin/Dev/arcs/tools/custom-loader.mjs:21:20)
    at Loader.resolve (internal/loader/Loader.js:50:18)
    at Loader.getModuleJob (internal/loader/Loader.js:82:40)
    at Loader.import (internal/loader/Loader.js:68:28)
    at internalESModule.loaderPromise.then (module.js:460:27)
    at <anonymous>
  input: '/var/folders/22/1mwk38yn1j9f6kzpq9j4sx1r004bmn/T/sigh-V49xVD/runner.js' }
🙅 test
😱

Node and npm versions:
yuin-macbookpro:arcs yuin$ npm -v
5.8.0
yuin-macbookpro:arcs yuin$ node -v
v9.9.0

This is at ToT with no modifications after running npm install. We started hacking the urls built in custom-loader to prepend 'file://localhost/' and seemed to make it farther but then experienced new errors.

Potentially fixed by https://github.com/PolymerLabs/arcs/pull/1066#pullrequestreview-107507355


Investigate strapi failures in the sandbox

`Using strapi 3.0.6
No project found at /srv/app. Creating a new strapi project
Creating a new Strapi application at /srv/app.
Creating a project from the database CLI arguments.
Creating files.

Installing dependencies:
Error while installing dependencies:
warning strapi ><EMAIL_ADDRESS>This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning strapi > boom ><EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning strapi > chokidar ><EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"
warning strapi > koa-body ><EMAIL_ADDRESS>Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
warning strapi > koa-session ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning strapi > strapi-generate-new ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning strapi-admin ><EMAIL_ADDRESS>🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
warning strapi-admin ><EMAIL_ADDRESS>Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
warning strapi-admin > @buffetjs/core ><EMAIL_ADDRESS>Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
warning strapi-admin > @buffetjs/styles ><EMAIL_ADDRESS>Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
warning strapi-admin ><EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
warning strapi-admin ><EMAIL_ADDRESS>3.x is no longer supported
warning strapi-admin > webpack-dev-server ><EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning strapi-admin > webpack-dev-server > chokidar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning strapi-admin > @babel/polyfill ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
warning strapi-admin > @fortawesome/fontawesome-svg-core ><EMAIL_ADDRESS>Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
warning strapi-admin > react-intl ><EMAIL_ADDRESS>We have renamed the package to @formatjs/intl-numberformat
warning strapi-admin > react-intl ><EMAIL_ADDRESS>the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package
warning strapi-admin > react-intl > @formatjs/intl-unified-numberformat ><EMAIL_ADDRESS>the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package
warning strapi-admin > react-intl > @formatjs/intl-listformat ><EMAIL_ADDRESS>the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package
warning strapi-admin > react-intl > @formatjs/intl-displaynames ><EMAIL_ADDRESS>the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package
warning strapi-admin > react-intl ><EMAIL_ADDRESS>We've written a new parser that's 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser
warning strapi-admin > react-intl > @formatjs/intl-relativetimeformat ><EMAIL_ADDRESS>the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package
warning strapi-admin > react-intl > intl-messageformat ><EMAIL_ADDRESS>We've written a new parser that's 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser
warning strapi-admin > webpack-dev-server > webpack-log ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning strapi-admin > reactstrap > react-popper ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning strapi-admin > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning strapi-admin > webpack-dev-server > url ><EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning strapi-admin > webpack-dev-server > chokidar > braces > snapdragon ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning strapi-admin > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning strapi-admin > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
warning strapi-admin > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning strapi-plugin-users-permissions ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning strapi-plugin-users-permissions ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning strapi-plugin-users-permissions > request ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning strapi-plugin-users-permissions > request ><EMAIL_ADDRESS>this library is no longer supported
warning strapi-plugin-users-permissions > koa2-ratelimit ><EMAIL_ADDRESS>Please update to v6 or higher! A migration guide can be found here: https://sequelize.org/v6/manual/upgrade-to-v6.html
warning strapi-plugin-users-permissions > koa2-ratelimit > mongoose > @types/mongodb ><EMAIL_ADDRESS>This is a stub types definition. bson provides its own type definitions, so you do not need this installed.
warning strapi-plugin-email > strapi-provider-email-sendmail > sendmail ><EMAIL_ADDRESS>This project is unmaintained
warning strapi-plugin-email > strapi-provider-email-sendmail > sendmail > mailcomposer ><EMAIL_ADDRESS>This project is unmaintained
warning strapi-plugin-upload ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning knex ><EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning knex ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning<EMAIL_ADDRESS>Invalid bin field for "url-loader".
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=14". Got "12.18.2"
error Found incompatible module.

Keep trying!
Oh, it seems that you encountered errors while installing dependencies in your project.
Don't give up, your project was created correctly.
Fix the issues mentionned in the installation errors and try to run the following command:
cd /srv/app && yarn install
Generating APIs and Models
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Error loading the local generate command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
Finished generating APIs and Models
Error loading the local develop command. Strapi might not be installed in your "node_modules". You may need to run "npm install"`

There is no Nginx Gateway error

Timing of strapi boost is varying between 7.30 to 15 min.  Recent longs
Using strapi 3.6.8
No project found at /srv/app. Creating a new strapi project
Creating a project from the database CLI arguments.
Creating a new Strapi application at /srv/app.
Creating files.

Installing dependencies:
Dependencies installed successfully.
Your application was created at /srv/app.
Available commands in your project:
yarn develop
Start Strapi in watch mode.
yarn start
Start Strapi without watch mode.
yarn build
Build Strapi admin panel.
yarn strapi
Display all available commands.
You can start by doing:
cd /srv/app
yarn develop
Starting your app...
Usage: strapi [options] [command]
Options:
-v, --version Output the version number
-h, --help Display help for command
Commands:
version Output your version of Strapi
console Open the Strapi framework console
new [options]  Create a new application
start Start your Strapi application
develop|dev [options] Start your Strapi application in development mode
generate:api [options]  [attributes...] Generate a basic API
generate:controller [options]  Generate a controller for an API
generate:model [options]  [attributes...] Generate a model for an API
generate:policy [options]  Generate a policy for an API
generate:service [options]  Generate a service for an API
generate:plugin [options]  Generate a basic plugin
generate:template  Generate template from Strapi project
build [options] Builds the strapi admin app
install [plugins...] Install a Strapi plugin
uninstall [options] [plugins...]
Finished generating APIs and Models
Building your admin UI with development configuration ...
ℹ Compiling Webpack

After making change to curl command : removing admin i made progress http://strapi/auth/local/register

This is the last error 403 which is related to permissions in the strapi components

Root cause of the failures were the following:

Strapi was running on the 3.0.6 which is 2 year old version , there were 5 /6 upgrades between 3.0.6 to 3.6.8
Dependencies on the older version was bursted
The user and permissions structure was changed in 3.1 version where admin and user roles were separated which was different in the versions before.

Solution :

Upgraded strapi to 3.6.8 and lowered the node version to 1.14 and npm to 6 as 3.6.8 is not compatiable with latest node and npm version
Added bootstrap.js script to programmatically update the permissions on the authenticated (default role given) users
Moved user_data commands to process_template.sh ( #1433  have to look into this later )

Please note we could not upgrade to v4 as docker image of v4 is not out and most likely it might not be. It is suggested to use this for time being https://blog.dehlin.dev/docker-with-strapi-v4

This has been fixed


Properly convert NaN/null values to empty value in StatsDWriter2

This is a follow up to #530 that handles the null value side effect of that change.

Thanks again!

@gehel do you mind cutting one more release to pick up this PR's content?

Sure, doing it right now...

You can follow the build at https://travis-ci.org/jmxtrans/jmxtrans/builds/185150915

Thank you so much.


"disposable" not defined

Hello,
I just downloaded and tried to build ConvNetSharp.Core.2015 with VS2015 and I obtain the following error.

Thanks!

Hi!
You need VS2019 to build ConvNetSharp. You get this error because it uses a language feature that doesn't exist yet in VS2015.
Also, is your repository up-to-date? I believe I removed 2015 related stuff long time ago.

Hi,
I pulled down the repo in a zip file today.  There was a project file which had "2015" in the name which I used.  I can install VS2019, if that is what is needed.
Thank you for your response.

2015 projects were removed in this commit  on Jul 14, 2018.
Maybe try to clone this repo or download the zip again ?
The latest version is https://github.com/cbovar/ConvNetSharp/archive/master.zip

I downloaded the latest repo and installed VS2019.  I now have the 2D demo running :)
Thanks again!

Just wanna learn programming and data but have no source.
On Sun, Apr 19, 2020, 08:17 gschmidt958<EMAIL_ADDRESS>wrote:

I downloaded the latest repo and installed VS2019. I now have the 2D demo
running :)
Thanks again!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cbovar/ConvNetSharp/issues/152#issuecomment-616020914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOVRO3L25GARD6BRJLJMHWLRNJX6BANCNFSM4MLOARIA
.


a faster way to use directline

Currently when a use says "hi" I then do 3 posts ( start convo, get token, say hi) and 1 get ( to get bot's response to the hi) before I can talk to the bot.  That takes 10s on average.
Anything I can do to cut time to 1s ?

We rolled out a number of perf improvements recently.
Do you need the added security that the token provides? A token is useful when you have a thin client app (like a webpage or an app) working directly against the Direct Line API. If you don't need that, you can skip the token generation and just use your secret directly on every call.

Do please take a look at perf and let me know if things haven't improved dramatically. We've added more caching and this API should be a lot faster now.


I'm pondering and exploring switching the directory of my https://github.com/enola-dev/enola from a "Maven-style" (e.g. core/impl/src/main/java/dev/enola/core) to a fully "Bazel-style" (e.g. java/dev/enola/model/xsd/Datatypes.java etc.) layout in this PR, starting small here. This will lead to "nested" BUILD files (e.g. java/dev/enola/BUILD and java/dev/enola/model/BUILD).
I suspect that with my existing .bazelproject as-is, this probably won't quite work?
Wondering if I can I "mix & match" and gradually transition, or need to do one single big refactoring moving lots of stuff around?
@guw any input?

Corrct. We don't support mixing.


DocumentSplitter type error

https://github.com/snexus/llm-search/blob/main/src/llmsearch/parsers/splitter.py#L53 and many other places in the file seem to access extension like it's a string, but it's an object. Causing the splitter to find no files. This was causing the examples to not work for me.

Thanks for reporting. Can you elaborate please on the issue and your setup? It seems the conversion happens implicitly on my system, it also works on Google Colab which is a similar setup (Ubuntu 22.04)

I'm on windows 11, When logging logger.info(f"Scanning path for extension: {extension}") for example I would see Scanning path for extension: DocumentExtension.pdf and I assume it also caused list(docs_path.glob(f"**/*.{extension.value}")) to be list(docs_path.glob(f"**/*.DocumentExtension.pdf"))
Considering that DocumentExtension is an Enum, It seems to have a key and value when used as a explicit type.

And for me, Python 3.11's enum.__str__ is:
    def __str__(self):
        return "%s.%s" % (self.__class__.__name__, self._name_, )

Thanks for that! I understand now, looks the problem is in different behaviour of Enum on Python 3.10 (which was used to develop this package) vs 3.11. In 3.10 has an implicit conversion to string, which doesn’t happen in 3.11.
I will work on compatibility with 3.11.
If you have an access to virtualenv with 3.10, it should work hopefully.

Fixed in v0.3.2

Fixed in version 0.3.2


Add the library to vcpkg

Describe the solution you'd like
I would like to see this library added as a package for vcpkg.
Describe alternatives you've considered
Adding a header file is extremely convenient, but adding the package to vcpkg would provide automatic fixes and features for users.
Additional context
Since the library uses CMake already, I think the packaging for vcpkg shouldn't be difficult.
Thanks for the great effort!

@daljit97 Thanks for bringing this up. Will look into this later today. And if you are interested, can you help create a PR for it?

Sure, I think I can give it a go.

@BowenFu Created a draft pull request here https://github.com/microsoft/vcpkg/pull/26499. It doesn't seem to work as vcpkg fails to install the library (ninja: error: unknown target 'install'), but maybe you can figure why this is (I might have a look at this later time permitting).

Thanks. Will look into this later.

Looks like this cmd is failing.
cmake --build . --config Debug --target install -- -v -j12
Will try repro locally.

@BowenFu Are you happy with the package name and description or anything else? If yes, I think I can submit the drafted pull request for review.

@daljit97 Sure. I see no problem with them. Feel free to submit. Thanks for your efforts.

Alright, the pull request has been merged. If you want, you can mention that the library is available on vpckg in the installation section of the readme, so users will be aware of it.

Sure. I've updated the README to reflect that.


Monitor everything for stargazing

If we aren't monitoring it how will we fix it? @astopy thoughts?
Setup monitoring for:

[X] panotpes API
[ ] DB - how?
[ ] Cellect - new relic and manual instrumentation as a rack app?
[ ] Zookeeper - docker stats perhaps?
[ ] Redis - docker stats perhaps?
[ ] Kafka - docker stats perhaps? Should we just turn kafka off?

Don't we get DB monitoring through RDS?

Probably i just added it in for comments.

At the least we can monitor most things with cloudwatch, at least to keep
track of CPU, etc. (it doesn't monitor memory out of the box, but
apparently there are ways to report memory usage to it).
On Mon, Mar 9, 2015 at 4:42 PM, Campbell Allen<EMAIL_ADDRESS>wrote:

Probably i just added it in for comments.
—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Panoptes/issues/627#issuecomment-77891590.

@edpaget @astopy - should we just turn off kafka for stargazing? we're not using it yet.

If it's not a big deal to keep it on I'd like to just to compute some stats
reading from it.
On Mar 13, 2015 12:45 PM, "Campbell Allen"<EMAIL_ADDRESS>wrote:

@edpaget https://github.com/edpaget @astopy https://github.com/astopy

should we just turn off kafka for stargazing? we're not using it yet.

—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Panoptes/issues/627#issuecomment-79178816.

all good, let's just leave it on.

Monitor via cloudwatch and dockerstats if we need more visiblity.


Databricks ips

Resolves #3901
What is being addressed
Databricks ips have been updated to reflect the new additional ones.

/test-force-approve

/test-force-approve


Incorrect permissions on windows during tests

[x] I was not able to find an open or closed issue matching what I'm seeing.
[x] This is not a question. (Questions should be asked on slack (Signup for Slack here) or our forums.)

Provide a narrative description of what you are trying to accomplish.
Code to reproduce the issue
Run composer test on windows
Expected results
Tests pass.
Actual results

ZendTest\Expressive\Authentication\OAuth2\AuthorizationServerFactoryTest::testInvokeWithValidData
Key file "file://~\Projects\zendframwork\zend-expressive-authentication-oauth2\test/TestAsset/private.key" permissions are not correct, should be 600 or 660 instead of 666

I have the same problem some way to fix

This repository has been closed and moved to mezzio/mezzio-authentication-oauth2; a new issue has been opened at https://github.com/mezzio/mezzio-authentication-oauth2/issues/8.


Added gravatar to the social options and sidebar picture.

Integrated http://en.gravatar.com social option which makes your gravatar photo appear instead of the smiley face.

Thanks!