bins/dbg/end2end_test --gtest_filter=ProxyEnd2end/ProxyEnd2endTest.RpcDeadlineExpires/2 GRPC_POLL_STRATEGY=epoll1

https://sponge.corp.google.com/target?id=55d577b5-5feb-49aa-bc4a-67d6fa40a994&target=github/grpc/c%2B%2B_linux_dbg_native&searchFor=&show=ALL&sortBy=STATUS
Note: Google Test filter = ProxyEnd2end/ProxyEnd2endTest.RpcDeadlineExpires/2
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from ProxyEnd2end/ProxyEnd2endTest
[ RUN      ] ProxyEnd2end/ProxyEnd2endTest.RpcDeadlineExpires/2
D1009 15:51:03.238311320    5184 end2end_test.cc:215]        TestScenario{use_proxy=false, inproc=false, credentials='INSECURE_CREDENTIALS'}
I1009 15:51:03.238410914    5184 ev_epoll1_linux.cc:93]      grpc epoll fd: 3
D1009 15:51:03.238425638    5184 ev_posix.cc:107]            Using polling engine: epoll1
D1009 15:51:03.238437101    5184 dns_resolver.cc:306]        Using native dns resolver
I1009 15:51:03.240335411    5184 ev_epoll1_linux.cc:93]      grpc epoll fd: 3
D1009 15:51:03.240351947    5184 ev_posix.cc:107]            Using polling engine: epoll1
D1009 15:51:03.240360853    5184 dns_resolver.cc:306]        Using native dns resolver
I1009 15:51:03.240402425    5184 server_builder.cc:269]      Synchronous server. Num CQs: 4, Min pollers: 1, Max Pollers: 2, CQ timeout (msec): 10
test/cpp/end2end/end2end_test.cc:1289: Failure
      Expected: StatusCode::DEADLINE_EXCEEDED
      Which is: 4
To be equal to: s.error_code()
      Which is: 0
[  FAILED  ] ProxyEnd2end/ProxyEnd2endTest.RpcDeadlineExpires/2, where GetParam() = TestScenario{use_proxy=false, inproc=false, credentials='INSECURE_CREDENTIALS'} (19 ms)
[----------] 1 test from ProxyEnd2end/ProxyEnd2endTest (19 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (19 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] ProxyEnd2end/ProxyEnd2endTest.RpcDeadlineExpires/2, where GetParam() = TestScenario{use_proxy=false, inproc=false, credentials='INSECURE_CREDENTIALS'}

This is a dup of #12917 and should have been fixed by #12939, which was merged last night.
@vjpai


Running API locally

Is it possible for us to run this project (self-assessment-api) locally?
I've tried following instructions, but it seems to require saervicemenager, which in turn seems to require NEXUS credentials, which I assume is an internal tool?
If there's a way for us to run something locally that would be great, as it would remove the need for us to create a stubbed version of your APIs to permit load and performance testing.

Hi @dharma66
Apologies for the delay in getting back to you. Unfortunately it will not be possible for you to run this project locally as it depends on some internal libraries that are not public.
Thanks,
Jacob


Support for partial expressions

While working on a new workflow using the concurrency key, I added the following block to one of my Jobs:
    concurrency:
      group: staging_${{ needs.validate-dispatch.outputs.headRef || github.head_ref }}
      cancel-in-progress: true

Unfortunately, the parser (via actions-linter) is marking that line as an issue: 😭
Error: Could not parse /home/runner/work/docs-internal/docs-internal/.github/workflows/staging-deploy-pr.yml:  Expecting: one of these possible Token sequences:
  1. [LParens]
  2. [fromJSON]
  3. [contains]
  4. [startsWith]
  5. [endsWith]
  6. [join]
  7. [toJSON]
  8. [hashFiles]
  9. [success]
  10. [always]
  11. [failure]
  12. [format]
  13. [cancelled]
  14. [Contextgithub]
  15. [Contextenv]
  16. [Contextjob]
  17. [Contextsteps]
  18. [Contextrunner]
  19. [Contextsecrets]
  20. [Contextstrategy]
  21. [Contextmatrix]
  22. [Contextneeds]
  23. [StringLiteral]
  24. [NumberLiteral]
  25. [True]
  26. [False]
  27. [Null]
  28. [LSquare]
but found: 'staging_'

I would assume the parser is getting tripped up by the partial string and partial expression nature of the value.  That said, I also believe that GitHub Actions does support a line of this nature, so ideally this parser would consider it valid as well.
For the short term, I've worked around this by using the format method within my expression instead:
    concurrency:
      group: ${{ format('staging_{0}', needs.validate-dispatch.outputs.headRef || github.head_ref) }}
      cancel-in-progress: true

ℹ  Also important: the actions-linter does NOT fail on these errors, just marks them as failure annotations but still passes. 👌🏻


Bug 1909793: Rook bp

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
[ ] Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.
[ ] Pending release notes updated with breaking and/or notable changes, if necessary.
[ ] Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
[ ] Code generation (make codegen) has been run to update object specifications, if necessary.

@travisn @leseb

/retitle Bug 1925004: [release-4.6] Rook changes for tuneFastDeviceClass


0.7.7 version has a simultaneous input issue

Hello.
I love to play FF THEATRHYTHM FINAL BAR LINE using haute42.
Here is 0.7.7 playing situation.
https://drive.google.com/file/d/1xakqKHuUCKsIADoDgochZJwVZsAgr6Pi/view?usp=sharing
and 0.7.6
https://drive.google.com/file/d/1sNzjOgGsKFUBsPpu4-emQqC_D7MxAkAC/view?usp=sharing
I think this problem is a gp2040-ce code issue.

Hi @Arastoa ,
I am going to guess you are running in a mode that has SOCD on.
Our SOCD filters will cause opposing inputs to be cleaned based on the currently selected SOCD rule.
If you are playing something like THEATRHYTHM FINAL BAR LINE I would recommend that you put it into an input mode that supports no SOCD cleaning.  This can be changed in the web-config.
That should resolve your issue.
There is no issue with the GP2040-CE code, it is functioning as intended.

I pushed triangle, square button.
I tested socd neutral and last win in 0.7.7. Nothing changed.
I think socd is not involved this situation.

@Arastoa we will need some more info from you if the buttons pressed are not directional inputs.
If you are on Discord can you please submit a support ticket there so we can have a more in-depth conversation?
If not, can you please tell us more about which controller you are using, which system this is occurring on, any special setups you have, etc.
The videos you provided do not give us enough info.

@Arastoa are you able to provide any more info on this?

Closing due to lack of response


New TOPMed reference data uses a list for AF instead of a float

This is breaking seqr's search. The TOPMed table needs to be updated and then the combined reference script needs to run again. Airflow is currently pointing at 2.0.4 for GRCh38 which has the bug. We can revert to 2.0.3 if the fix is more challenging than anticipated.

We need to determine if the list contains both ref and alt frequencies or is just a single entry list. Reviewing the previous TOPMed version VCF and HT should help clear this up. We can update the single annotation instead of running the entire combine script again.

Lists were a single entry for all topmed annotations. I updated this by transmuting the field by grabbing the first and only entry in the list. I verified all data types match the 2.0.3 and rewrote gs://seqr-reference-data/GRCh38/all_reference_data/v2/combined_reference_data_grch38-2.0.4.ht

Hi @mike-w-wilson.  We recently downloaded the TopMed Hail Table (updates/2022.4/data/combined/write_combined_ht_gnomad3.sh) and used it to build the combined reference hail table.  However, we are now having issues with the variant search in our instance of seqr.  Was this a manual fix of the combined reference table or is there a fix in the scripting somewhere?

This happens for other fields as well:
# Freeze 5
In [8]: comb_old.topmed.show(2)
+---------------+------------+-----------+-----------+-----------+------------+------------+
| locus         | alleles    | topmed.AC | topmed.AF | topmed.AN | topmed.Hom | topmed.Het |
+---------------+------------+-----------+-----------+-----------+------------+------------+
| locus<GRCh38> | array<str> |     int32 |   float64 |     int32 |      int32 |      int32 |
+---------------+------------+-----------+-----------+-----------+------------+------------+
| chr1:10001    | ["T","A"]  |        NA |        NA |        NA |         NA |         NA |
| chr1:10001    | ["T","C"]  |        NA |        NA |        NA |         NA |         NA |
+---------------+------------+-----------+-----------+-----------+------------+------------+
showing top 2 rows

# Freeze 8
In [9]: comb_new.topmed.show(2)
+---------------+------------+--------------+----------------+-----------+--------------+--------------+
| locus         | alleles    | topmed.AC    | topmed.AF      | topmed.AN | topmed.Hom   | topmed.Het   |
+---------------+------------+--------------+----------------+-----------+--------------+--------------+
| locus<GRCh38> | array<str> | array<int32> | array<float64> |     int32 | array<int32> | array<int32> |
+---------------+------------+--------------+----------------+-----------+--------------+--------------+
| chr1:10001    | ["T","A"]  | NA           | NA             |        NA | NA           | NA           |
| chr1:10001    | ["T","C"]  | NA           | NA             |        NA | NA           | NA           |
+---------------+------------+--------------+----------------+-----------+--------------+--------------+


V10

upgraded project to the latest stable release.

Thanks! Looks good, I'll merge it and will do a 10.0.0-beta.0 release with it!


refactor: replace deprecated gulp-util

gulp-util has been deprecated recently. Continuing to use this dependency may prevent the use of your library with the recently released version 4 of Gulp.
The README.md lists alternatives for all the components so a simple replacement should be enough.
See:

https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
https://github.com/gulpjs/gulp-util/issues/143

@bhargavrpatel
Did you get a chance to look at this and contemplate the transfer of maintainership?


defaults are ignored on upsert

As of 2.3.13, default values and type options that are specified in the schema are ignored during an upsert operation when the record is being inserted. Updates to existing records work as expected.
//schema declaration

var Schema = require('mongoose').Schema;

var ip_address = "<IP_ADDRESS>";

exports.beta_email = new Schema({
	email : { type: String, index: true, uppercase: true },
	ip_address : { type: String, match: /[\d]{1,3}\.[\d]{1,3}\.[\d]{1,3}\.[\d]{1,3}/, 'default': ip_address },
	first_submit : { type: Date, 'default': Date.now },
	total_submits : { type: Number, 'default': 1 },
}, { collection: 'beta_email' });

//upsert ( does not write fields with default values ( first_submit, ip_address ) and leaves the email in lowercase )

db.model('beta_email')
	.update(
		{ email: req.body.email },
		{ $inc: { total_submits: 1 } },
		{ upsert: true, multi: false },
		function(err) {}
	);

//produces

{
   "_id": ObjectId("4ecf18651b77a21f69254acf"),
   "email"<EMAIL_ADDRESS>   "total_submits": 1
}

// save

var Beta_Email = db.model('beta_email');
var be = new Beta_Email();
be.email = req.body.email;
be.save( function(err) {} );

//produces this:

{
   "email"<EMAIL_ADDRESS>   "_id": ObjectId("4ecf1883f04792b1a5000002"),
   "ip_address": "<IP_ADDRESS>",
   "total_submits": 1,
   "first_submit": ISODate("2011-11-25T04: 24: 35.707Z")
}

I probably should have mentioned... It's very likely I'm doing or understanding something wrong.
I suppose I could simply query first, and insert or update as necessary. It just seems like a schema supported upsert would be something people would use frequently.

But if you are knowingly telling it to do an upsert, and the field that you are querying by doesn't exsist, shouldn't it insert a new record? In what case would you be overwriting existing data? The update operation shouldn't have anything to do with default values.

the upsert operation actually takes place on the db itself, it isn't a mongoose thing.
re overwriting data:

re overwriting data:
var schema = new Schema({ name: String, number: { type: Number, default: 77 }})
var Thing = db.model('Thing', schema);

var t = new Thing({ name: "mongodb", number: 1 });
t.save(function () {
  // t has been saved with number set to 1.
  Thing.update({ name: "mongodb" }, { name: "MongoDB" }, { upsert: true }, function () {
    // Mongoose will default this update to: { $set: { name: "MongoDB" }}
    // Now the overriding part; if Mongoose passed defaults then we'd inadvertently be
    // setting number to 77 which isn't the intention.
  })
})

Got it, that makes sense. So the only way for mongoose to have an upsert method that included defaults, it would have to query the db prior to the update, which probably wouldn't make sense from a performance aspect.
Thanks for the clarification.

yeah depending on how much perf you need it might be ok. someone else just mentioned today that they might be putting a patch together for that so we'll see.


Timeout Reason

General Troubleshooting

[X] I have checked for similar issues on the Issue-tracker.
[X] I have updated to the latest JDA version
[X] I have checked the branches or the maintainers' PRs for upcoming features.

Feature Request
JDA should add the ability of adding a reason to timeouts.
Example Use-Case
member.timeoutFor("Bad Word", duration)

This could be used for better Audit-Logging, and keeping track of why a Bot would have timeout a Guild Memeber.

You can use reason(...):
member.timeoutFor(duration).reason("bad word").queue();


deck.gl: Support the max/minRadiusPixels properties

fixes #974
The maxRadiusPixels and minRadiusPixels can be set in the layer
description to prevent the points from getting too big/small when
zooming in/out. If the property is a number, the lineWidth min/max
pixels are also set to 1/3 of the corresponding radius.
Here's how it looks now (@kaligrafy 10 review points if you find where this image shows :p ):

Boulevard Roberval, à Longueuil


Incorporate contributed commit

@cjgronlund : Thanks for your contribution! The author, @hning86, has been notified to review your proposed change.

@cjgronlund : Thanks for your contribution! The author, @sgilley, has been notified to review your proposed change.

@cjgronlund : Thanks for your contribution! The author, @sgilley, has been notified to review your proposed change.

@cjgronlund : Thanks for your contribution! The author, @sdgilley, has been notified to review your proposed change.

#sign-off from documentation manager @cjgronlund
Change verified by @Blackmist
@sdgilley

@cjgronlund: I'm sorry - only the author of this article, @sdgilley, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@Jak-MS - Manager sign-off above. Thank you!


Enabling spotless, disabling checkstyle check on plugins

Signed-off-by: Himanshu Setia<EMAIL_ADDRESS>Description
This change enables spotless check and reformats above plugins as per spotlessApply style.
:plugins:mapper-annotated-text
:plugins:mapper-murmur3
:plugins:mapper-size
:plugins:repository-azure
:plugins:repository-gcs
:plugins:repository-hdfs
:plugins:repository-s3
:plugins:store-smb
:plugins:transport-nio
:qa:die-with-dignity
Issues Resolved
#974
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check


Ad. Owl FTSO

Merged in https://github.com/TowoLabs/ftso-signal-providers/commit/37eab711fdfa3dd2791004538341054f9c0edcff


Improve support for AAD Auth proxying w/ group authz support

This PR improves support for backing oauth2_proxy with Azure Active Directory, along with a few other changes. We've been using this internally for lightly-loaded services for a couple of weeks, and are ready to open contribute it back upstream. Thanks for the great base upon which to build!
BREAKING CHANGES:

In order to generalize group support, the Google google-groups field was renamed to permit-groups.
Raw cookie value construction was changed to delineate fields using the : character instead of the | character in order to adopt conventional construction of the X-Forwarded-Groups header (usually foo|bar|baz).
The provider option is now mandatory.

Added functionality:

Azure support now includes group support, including passing an X-Forwarded-Groups header, filtering groups (in order to limit cookie size), and restricting access based on group string matches.
Added a Vagrantfile and simple HTTP request reflector for testing

ETA?

Sorry, I don't follow. We've been using this internally for a bit now. Does it need something to be ready for merge?

FYI, I went live with this and it turns out that having prompt=consent as a query param for initial authorization does not work for non-admin users.  I had to revert back to the mainline version here without the prompt query param.

@bdwyertech, thanks for the report. I'm unfortunately no longer in a position to test this, but did you have any success with different values for prompt? Thinking about it, it is probably advisable to remove it altogether, since I don't believe it's necessary to require the consent prompt every time.
I'm surprised to hear you had that result. I don't believe that everyone was an admin in my former team. Hopefully it's a simple fix. Do let @pasoroki know if you're able to do any testing, as he may be interested in updating this PR. :)

I will definitely update the PR.
We have a ticket for one person who didn't get 2FA request when he tried to authorize. That might be related. I'll try first to remove prompt at all from the request

This PR is updated:

merged latest changes from the origin
added empty prompt option by default
fixed issue with HTTP 500 error if state option were not set

The test.sh throw lots of errors, they are unrelated to our changes.

The test panic is:
--- FAIL: TestAuthOnlyEndpointSetXAuthRequestHeaders (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
...
github.com/bitly/oauth2_proxy.NewOAuthProxy(0xc4201f9800, 0xc42021e070, 0xc42021e060)
	/home/travis/gopath/src/github.com/bitly/oauth2_proxy/oauthproxy.go:163 +0x590
github.com/bitly/oauth2_proxy.TestAuthOnlyEndpointSetXAuthRequestHeaders(0xc4201f66c0)
	/home/travis/gopath/src/github.com/bitly/oauth2_proxy/oauthproxy_test.go:628 +0x1fe

I think I that's on this line:
log.Printf("OAuthProxy configured for %s Client ID: %s", opts.provider.Data().ProviderName, opts.ClientID)

so opts.provider.Data().ProviderName is probably de-referencing a nil somewhere.
You are making a significant change to how providers work in this PR: making the provider no longer default to "google" but instead return nil (and an error) if no recognized provider is specified. So it is quite plausible that this provider-option-handling change is related to this test failure.
Command-line common-use-case compatibility-breaking changes should not be bundled with other changes like group handling enhancements, and is probably enough to prevent this from being merged. On the other hand, while this project/repo is not "dead", it is not clear what might be merged next, or in how many weeks or months. It looks like any of the changes you want to get in might be a bit too big to get into the next round, not really because they're "bad", but just because review capacity of the maintainers is low. (I'm not a maintainer.)
If this PR is just useful as a common resource for multiple users of this variant/functionality, that's quite fine, you can ignore me :)

@ploxiln you were right.
We removed default provider and were defining provider for each option set in every test.
New tests didn't have that. I removed back Google as a default provider

fwiw, I don't think the more strict provider option is a bad idea, just unrelated :)
(I would still have it default to google, but right now it accepts any unrecognized string as google, so that could be cleaned up - in a separate PR)

@talem @jediah   This is really useful, any issues blocking merge?

"In order to generalize group support, the Google google-groups field was renamed to permit-groups."
consider leaving the google-groups param along with permit-groups,for backwards compatibility, and set
permit-groups = google-groups   if permit-groups is none, and google-groups is not none.

Agreed with @johnarnold, having this merged would be great.

I'll update PR next week, but don't think anyone would merge it =(

why is that ? @jehiah tagged the associated issue (#335) as enhancement, so I don't think authors would be against this.

Well, I hope you are right @iksaif

The -pass-groups=true parameter will only work if -pass-access-token is set. The reason is that groups are saved in the session cookie which is created inside EncryptedString method that requires c *cookie.Cipher. This is only set when: https://github.com/bitly/oauth2_proxy/blob/731fa9f8e00b294ff1bf4a687e63d2ecdd9a4a50/oauthproxy.go#L166
I think this needs some explanation in docs or change of the condition so if pass-groups is set than the pass-access-token is a required flag.

@combor PassAccessToken is setup by default
https://github.com/bitly/oauth2_proxy/blob/master/options.go#L111
I marked in README that its default value is false

Thank you @jan-schulz-k24  that is very helpful
Now I need to figure why golang 1.9 is timing out

Hejj all, what us the current status of this? Can't wait to use it. 👍

We've been using it for couple of months now from our fork and it works ok

@combor When I clown the fork, the build fails on my opensuse server...

Clone*

@nduijvelshoff could you give us the errors you're getting/build output and we'll see if we can debug the problem

@nduijvelshoff You can also use this container: quay.io/uswitch/oauth2_proxy

@combor This won't suite for me since I'm reusing the Kibana docker image.
@pingles Hereby my error:
./oauthproxy.go:569: session.IDToken undefined (type *providers.SessionState has no field or method IDToken)
./oauthproxy.go:570: session.IDToken undefined (type *providers.SessionState has no field or method IDToken)
./oauthproxy.go:571: p.provider.GetGroups undefined (type providers.Provider has no field or method GetGroups)
./oauthproxy.go:576: session.Groups undefined (type *providers.SessionState has no field or method Groups)
./oauthproxy.go:585: cannot use session (type *providers.SessionState) as type string in argument to p.provider.ValidateGroup
./oauthproxy.go:702: session.Groups undefined (type *providers.SessionState has no field or method Groups)
./oauthproxy.go:703: session.Groups undefined (type *providers.SessionState has no field or method Groups)
./options.go:282: assignment count mismatch: 2 = 1
./options.go:291: p.SetGroupRestriction undefined (type *providers.AzureProvider has no field or method SetGroupRestriction)

Wow, super strange. I've take a clean clone on a new laptop and can build with:
$ go get -v -t ./...
$ CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o bin/proxy

I'd say maybe its a dependency versioning issue but then the options go assignment error suggests something else is wrong.

@pingles going to check it out tonight.... can you share the complied bin with me? 👼

You can find it in our container.

@pingles are you sure we are talking about the same repo? https://github.com/outlook/oauth2_proxy.git
Tested it on Suse and Ubuntu (Go 1.10).

@nduijvelshoff ah, yeah @combor and i were talking about our changes in our fork. code is at https://github.com/uswitch/oauth2_proxy

@pingles @combor I get it, I see it also supports the AAD groups... Going with that one. Thanks!

@pingles is it possible to add -basic-auth-username to overwrite the "x-user" to combine it with:  "-basic-auth-password string: the password to set when passing the HTTP Basic Auth header"

Any plans to support groups in /auth request as well (for Nginx auth_request)? It took me some hours to figure out why I don't see any groups there 🤦♂

Sorry @kerma I don't work on that

@pasoroki would you accept a PR with that functionality ?

@kerma sure, just don't forget to cover code with tests

@kerma sure, just don't forget to cover code with tests

When might this be merged? Groups support is really the only path forward when it comes to Azure provider support for companies larger than ~10 individuals.

Merge? We really need this feature. Thanks

This looks like exactly what we need - any idea when it can get merged (and released)?

I've played with this PR and haven't been able to get Azure Roles or Groups passed through. Does anyone have docs on the Azure set-up side of things?

@dekimsey you will have to use v2.0 api endpoint and scope: profile I guess

@lukasmrtvy Thanks, that made me look into this deeper. I haven't been able to see/get roles but I did get groups working. It was a number of things some PEBKAC others permissions issues with the Graph API (user_list_memberof)[https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/user_list_memberof].
WRT to the PR itself, I did find that a large group list will cause it to go into loop hitting the azure cookie /oauth2/callback repeatedly as the Cookie maximum size is exceeded and unable to save in the browser. To whom whoever decides to merge this or take this over, might be worth catching that situation rather than infinite looping. Also, the FilterGroups parameter cannot be specified multiple times which makes filtering tricky.

This looks like exactly what we need - any idea when it can get merged?

@mariusfylling this is dead project. Keycloak and Keycloak Gatekeeper can do the magic for You.
Keycloak Gatekeeper itself can replace this oauth2 proxy, but there is a small problem: https://issues.jboss.org/browse/KEYCLOAK-8728

@mariusfylling this is dead project. Keycloak and Keycloak Gatekeeper can do the magic for You.
Keycloak Gatekeeper itself can replace this oauth2 proxy, but there is a small problem: https://issues.jboss.org/browse/KEYCLOAK-8728

Thank you, will look into this.

Fyi: there is an active discussion about forking this project here: https://github.com/bitly/oauth2_proxy/issues/628


Create "maintenance" page

Follow this tutorial to create a "maintenance" page redirection in NGINX.
https://www.calazan.com/how-to-configure-nginx-so-you-can-quickly-put-your-website-into-maintenance-mode/
Then create a node script to switch (rename) from that mode, and add it to the npm scripts.

I read the docs, and I can accomplish this but I need a designed html page. @Poliuk , could you do it?

I think this is not needed before launch. It's not that important.
On Mon, 2 Jan 2017, 18:11 Abel Serrano Juste<EMAIL_ADDRESS>wrote:

I read the docs, and I can accomplish this but I need a designed html
page. @Poliuk https://github.com/Poliuk , could you do it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/worona/worona-dashboard/issues/72#issuecomment-269997869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADJvuu5KxsMHMoUOnLAPdr2OMziFjY7Eks5rOS-8gaJpZM4K1Mai
.

Not really needed ATM.


Weekly Activities [08Apr-21Apr]

This is a 2 weeks of activities planned at once. Since Spring & React is new stack and especially Java is a requirement on this app, we'll focus on how to build RESTful web apps using these technologies

Followed several courses and forums to learn how to build RESTful apps with React & Java Spring.
It took 20 hours to get React up-and-running
It took however, 32 hours to get something working on Java Spring boot.
Next week, the main plan is to start building W-Learn using these technologies


Add focus/portrait mode

Added focus in commit https://github.com/rampadc/NDISenderExample/commit/0fc3c9657dcaf4afc84865f31ef2c33f1213dc60 and corresponding GUI code in https://github.com/rampadc/ndi-control-gui/commit/9ef83fa9e9d5bccc20e4b1bfb317262451166f6f

Pushing portrait mode using depth data to v0.2 milestone due to significant rework needs to be done for the processing callback.


The creation of the agent's SDS server is non-deterministic if SPIRE and Istio are started by helm

Bug Description
The istio-agent/agent.go code checks whether the security.WorkloadIdentitySocketPath exists before starting the Istio SDS server to create that socket.
When using helm to install Istio and SPIRE, the order in which SPIRE and Istio are started is non-deterministic, so this may cause the Istio agent to incorrectly create the socket if SPIRE is started after Istio.
There should be some sort of optional explicit configuration that inhibits the startup of the SDS server by agent.go even when that socket doesn’t yet exist because SPIRE hasn't gotten around to it.
Version
istioctl version: 1.14.3
kubectl Server Version: v1.22.13-eks-15b7512

Additional Information
No response

This is coding change for the solution which adds an optional flag to disable Istio's creation of the socket

seems reasonable, can you raise a PR?

seems reasonable, can you raise a PR?

https://github.com/istio/istio/pull/41440

The PR has been closed without merging. I have a better solution that does not require Istio modifications. We had success adding an initContainer with an k8s.overlay in the IstioOperator. The mountPath and CHECK_FILE should match where the workload-socket is being mounted by the existing patch for SPIRE.
ingressGateways:
  k8s:
    overlays:
      - apiVersion: apps/v1
        kind: Deployment
        name: istio-ingressgateway
        patches:
          - path: spec.template.spec.initContainers
            value:
              - name: wait-for-spire-socket
                image: busybox:1.28
                volumeMounts:
                  - name: workload-socket
                    mountPath: /run/secrets/workload-spiffe-uds
                    readOnly: true
                env:
                  - name: CHECK_FILE
                    value: /run/secrets/workload-spiffe-uds/socket
                command:
                  - sh
                  - "-c"
                  - |-
                    echo `date -Iseconds` Waiting for: ${CHECK_FILE}
                    while [[ ! -e ${CHECK_FILE} ]] ; do
                      echo `date -Iseconds` File does not exist: ${CHECK_FILE}
                      sleep 15
                    done
                    ls -l ${CHECK_FILE}


Abstract task group children serialization

This introduces a new function serialize_for_task_group to DAGNode, which should implement serialization logic when a DAGNode is put into a task group. Since all nodes belonging to a DAG are either the root group, or always in a parent task group, this guarantees a DAG's all nodes can be correctly serialized.

Merged directly to apache#20795


TUF client workflow - Do we need to update roots first?

Description

https://theupdateframework.github.io/specification/latest/#update-root notes that the root should be updated before fetching the timestamp. Should we do the same? Currently, we initialize from the local cache rather than make any network calls.
@asraa

Should this be in a client repository?
If you're speaking of the timestmap.json check for cache validity: note that this isn't part of the TUF client workflow start, this is a decider on starting the TUF update or not.

I think though, Sigstore deployments and clients are in a lot of different environments, and some may prefer to configure WHEN to perform the TUF client workflow. See this doc for the proposed cache-ability and configurability and the justification for that choice: https://docs.google.com/document/d/1QWBvpwYxOy9njAmd8vpizNQpPti9rd5ugVhji0r3T4c/edit#

Yes, we should update root before we fetch and verify timestamp. We need to better define how often Sigstore clients should run the TUF client workflow, would be good to get your feedback on the doc Asra linked to.

There is a risk, yes. If we update the TUF metadata, whether due to a scheduled root update or a proactive rotation of a compromised key, then a cosign client which already has a cached copy of timestamp will not know about the rotation until the locally cached timestamp has expired.
We should do something different. The doc Asra linked to suggests that by default a client will at least check for updates every 3 days (aiming to reduce that to every day) and that a client should be able to both 1) require a metadata update on every invocation and 2) using the cached data until the timestamp has expired – this is how cosign works today but the design suggests this should be configurable and default to not using this behaviour.

default to not using this behaviour.

+1 This might address your concern @haydentherapper : I think the issue context is likely around the SCT rotation and how long-lived clients aren't updating proactively.

Is there any risk with the current client not checking for updated roots first?

Santiago put it aptly that this default 7 days is effectively a "freeze attack" for 7 days.

Is this still relevant?
Can we move to sigstore/sigstore if yes?

This has been fixed by the new sigstore-go TUF client that uses go-tuf.


[Suggestion] Resin purchase/wait time calculation

I have another suggestion regarding resin for the Experience calculator.
Resins are refillable by 3 methods -

By Waiting
By using Fragile resin
By using Primo gems

Total limit - 120 resins.
By Waiting
1 Resin every 8 minutes. Regenerating all 120 Resin would take around 16 hours (960 minutes) to complete.
For 20 Resins 160 minutes.
By using Fragile resin
1 Fragile resin gives 60 Original resin
By using Primo gems
1 Refill gives 60 Original resin
Maximum 6 refills can be done

Refill
Cost

First refill
50 Primogems

Second refill
100 Primogems

Third refill
100 Primogems

Fourth refill
150 Primogems

Fifth refill
200 Primogems

Sixth refill
200 Primogems

Approach 1 - Simple but accuracy differs.
Example 1
Suppose I require 380 resins to level up a character.
And I have 20 resins in hand.
So, I need 360 more.
The output would be -

You require net total 360 resins.
By waiting for 48 hours you get additional 360 resin.
By using 6 Fractured Resins you get additional 360 resin.
By spending 800 primogems you get additional 360 resin.

Example 2
Suppose I now require 450 resins to level up a character.
And I have 30 resin in hand.
So, I need 420 more.
The Output would be -

You require net total 420 resins.
By waiting for 56 hours you get additional 360 resin.
By using 7 Fractured Resins you get additional 420 resin.
By spending 800 primogems today (to get 360 resins) & 50 primogems next day (to get 420-360 resins), you get 420 resins.

Approach 2 - The more complicated route but more precise too
Keeps primogems & fragile resin in check
Example 3
Suppose I need 1000 resins.
~I have 40 in hand for Day 1~
Let's remove initial thingy. Stuff becomes complicated 😅

How many hours to wait to naturally replenish resins in 1 day?
120 resin = 16 hours
30 resins = 4 hours
20 resins = 2.67 hours

16

Spend Primogems for resin refills?

✅

How many primogem refills? (Max 6)

6

Spend Fragile Resin?

❌

Days
Initial Resin/Overnight Replinished resin
Natural replishment cost
Primogems cost
Fragile Resin cost
Resins obtained today
Resin left to acquire

Day 1
0
16 hours (120 resins)
800 (360 resins, 6 refills)
N/A
480
520

Day 2
120
16 hours (120 resins)
600 (300 resins, 5 refills)
N/A
540
- 20

Negative "Resins left to acquire" means we got excess resins
Example 4
Suppose I need 360 resins.

How many hours to wait to naturally replenish resins in 1 day?
120 resin = 16 hours
30 resins = 4 hours
20 resins = 2.67 hours

4

Spend Primogems for resin refills?

❌

How many primogem refills? (Max 6)

0

Spend Fragile Resin?

❌

Days
Initial Resin/Overnight Replinished resin
Natural replishment cost
Primogems cost
Fragile Resin cost
Resins obtained today
Resin left to acquire

Day 1
0
4 hours (30 resins)
N/A
N/A
30
330

Day 2
120
4 hours (30 resins)
N/A
N/A
150
180

Day 3
120
4 hours (30 resins)
N/A
N/A
150
30

Day 4
120
N/A
N/A
N/A
N/A
-90

All this stuff might take a day or 2 to implement 😅😅😅
Let's take another example -
Consider you spend 8 hours a day to code this.
And you managed to implement it in total 48 hours.
Which means it took you 6 days.
You play Genshin Impact before starting to code. And after 6 hours of coding, you again play Genshin Impact.
So, in these settings -

How many hours to wait to naturally replenish resins in 1 day?
120 resin = 16 hours
30 resins = 4 hours
20 resins = 2.67 hours

8

Spend Primogems for resin refills?

❌

How many primogem refills? (Max 6)

0

Spend Fragile Resin?

❌

Days
Initial Resin/Overnight Replinished resin
Natural replishment cost
Resins obtained today
Resin obtained cumulative

Day 1
0
8 hours (60 resins)
30
90

Day 2
120
8 hours (60 resins)
150
180

Day 3
120
8 hours (60 resins)
150
330

Day 4
120
8 hours (60 resins)
150
480

Day 5
120
8 hours (60 resins)
150
630

Day 6
120
8 hours (60 resins)
150
780

You get to spend 780 resins !!!!!

the 780 resins are equivalent to me playing Genshin Impact without coding lol xD
But thanks, this seems like an interesting problem to solve, however I don't have much time especially in the weekdays (have some software projects and university work to handle), will check out during weekends haha


Allow audit event with no user

Audit events are allowed to be created with no associated user. This
makes the API create audit event endpoint also allow this. There is a
requirement in the frontend to create an audit event for sending an
invite email on creation of a supplier, before the user has logged in.

:+1:


4.15.0 Release checklist

Checklist
Build

[x] Bump MockBot to Bot Framework SDK release 4.15.0

https://www.npmjs.com/package/botbuilder/v/latest

[x] Bump botframework-directlinejs to 0.15.1

Bumped to 0.15.1 in #4123

[x] Bump to 4.15.0

[x] Update CHANGELOG.md to mark specific changes in 4.15.0

[x] For 4.15.0, add breaking changes:

Web devs should add import 'core-js/features/map' to their polyfill list if they support IE11 with NPM install

[x] Run npm version --no-git-tag-version 4.15.0
[x] Merged into master, the PR number is #4193
Commit is 49cfdc1
Do not merge any other unrelated changes after this PR. Any other PR merged, will need to be re-tested

[x] Run daily pipeline manually, set "generate release version number" to true

(This will not push to NPM or CDN)
Pipeline name is BotFramework-WebChat-daily
The build number is 294404 and commit is 49cfdc12

[x] Wait for WebChat-release-testing pipeline to complete

Pipeline name is Push-Release-Testing-to-GitHub-Pages
The release ID is 321

[x] Check component governance and make sure there are no high/critical related to code under /packages/ folder

There could be some for projects under /samples/ folder, as they are pointing to previous version of Web Chat

[x] Add manual tests to WebChat-release-testing as needed

Test

The test should run against the build artifacts from Azure Pipelines.

[x] Manual testing on major browsers using webchat-release-testing

[x] Before starting testing, update all the browser version to latest
[x] Chrome 98.0.4758.102
[x] Edge 98.0.1108.62
[x] Firefox 97.0.1
[x] IE11 (Windows 11 22H2 22567.1)
[x] macOS Safari 15.0 (166<IP_ADDRESS>.4, 16612)
[x] iOS Safari 15.1
[x] Android Chrome 98.0.4758.101

[x] Test specific fixes related to 4.15.0 and previous releases

New transcript navigation
New keyboard help screen

Release

[x] Verify on WebChat-release-testing
[x] Make sure you are on main ~or qfe~ branch, run git status to check
[x] git pull
[x] Verify /package.json, /package-lock.json, and CHANGELOG.md has a version of 4.15.0
[x] git log

Verify the latest commit is 49cfdc12

[x] git tag v4.15.0
[x] git push -u upstream v4.15.0

You do not need to kick off a build again, use the previous build

[x] Create a new GitHub release, copy entries from CHANGELOG.md

[x] Subresource Integrity can be generated by

From local: cat webchat.js | openssl dgst -sha384 -binary | openssl base64 -A
From CDN: curl -H 'Accept-Encoding: gzip' https://cdn.botframework.com/botframework-webchat/4.15.0/webchat.js | gunzip - | openssl dgst -sha384 -binary | openssl base64 -A

[x] Attach assets including 3 JS files, stats.json and 5 tarballs

You can copy the artifacts from webchat-release-testing/drops
Tarballs download from npmjscurl -LO https://registry.npmjs.org/botframework-directlinespeech-sdk/-/botframework-directlinespeech-sdk-4.15.0.tgz
curl -LO https://registry.npmjs.org/botframework-webchat/-/botframework-webchat-4.15.0.tgz
curl -LO https://registry.npmjs.org/botframework-webchat-core/-/botframework-webchat-core-4.15.0.tgz
curl -LO https://registry.npmjs.org/botframework-webchat-api/-/botframework-webchat-api-4.15.0.tgz
curl -LO https://registry.npmjs.org/botframework-webchat-component/-/botframework-webchat-component-4.15.0.tgz

[x] Kick off release to NPM

Release name is [[PROD]]Push-WebChat-to-npmjs
The build number is 294404 release number is 37 and commit is 49cfdc12
[x] Verify package content then click Resume
[x] Retain the release indefinitely

[x] Kick off release to CDN (cutoff at 2PM PST, Mon-Thu only)

[x] Prepare the email for approval

Release name is [[PROD]]Push-WebChat-to-Prod-CDN-with-approval
The build number is 294404, release number is 41 and commit is 49cfdc12
Script build number is 131156 (this is fixed)

[x] Send reminder email to approvers

Retain the build indefinitely

Post-release verification - complete within 30 minutes after release to NPM

[x] Test using webchat-release-testing

[x] Clone https://github.com/corinagum/WebChat-release-testing/
[x] 01.create-react-app

[x] Nuke 01.create-react-app/node_modules
[x] npm install
[x] npm install<EMAIL_ADDRESS>(just install the bundle package)
[x] npm run build

[x] Others

Using script tags from https://github.com/microsoft/BotFramework-WebChat/releases/tag/v4.15.0, with subresource integrity<script
  crossorigin="anonymous"
  integrity="sha384-XXXXXXX"
  src="../drops/webchat.js"
></script>

<script
  crossorigin="anonymous"
  integrity="sha384-XXXXXXX"
  src="../drops/webchat-es5.js"
></script>

<script
  crossorigin="anonymous"
  integrity="sha384-XXXXXXX"
  src="../drops/webchat-minimal.js"
></script>

[x] npx serve (at repo root)
[x] Go to http://localhost:5000/ to test, including IE11

Notification to interested parties

[x] Update partner page on Adaptive Cards doc

https://docs.microsoft.com/en-us/adaptive-cards/resources/partners
PR at https://github.com/MicrosoftDocs/AdaptiveCards/pull/443

[ ] Notify related parties for the following fixes

[ ] SDK team
[x] Omnichannel
[ ] Pooja/Zhipeng

[ ] Update root README.md with feature notes -- Note: PR will be combined with post-release checklist PR

Post-release checklist
These are chores that we should do before starting the cycle to reduce ripple effects if we do it in mid-cycle.
Tips:

Clean your repo before start
Remove node_modules from all folder

git clean -fdx

Never delete package-lock.json
If you mess it up, tableflip and redo
In component/package.json

Remove reference to botframework-webchat-core by hand-modifying package.json
Then, npm install (symlinks will be broken afterward)
Then, add those references back by hand-modifying package.json
This also applies for other packages with similar dependencies/symlinks
To build afterward, do tableflip to rebuild those symlinks

Applies to all releases

This list should be copied to versions in the future.

[ ] ~If on QFE branch, make sure CHANGELOG.md and version number bump is cherry-picked to master~

[ ] ~git checkout master~
[ ] ~git cherry-pick XXX (the commitish for bumping version number and CHANGELOG.md)~

[ ] ~Correct the date for 4.15.0 in CHANGELOG.md in PR #XXX~

There could be last minute fixes that could push the planned date later than the one in CHANGELOG.md

[ ] Bump package.json to 4.15.1-0 in PR #XXX

Run npm version prepatch --no-git-tag-version

[ ] Update servicingPlan.json in PR #XXX

Add deprecation notes for previous versions
Subresource integrity hash from https://github.com/microsoft/BotFramework-WebChat/releases/tag/v4.15.0

[ ] Update all samples to use 4.15.0 in PR #XXX

Some samples are pointing to GitHub Releases because the sample need new features from daily build
Search "https://github.com/microsoft/BotFramework-WebChat/releases/download/"

And replace with "https://cdn.botframework.com/botframework-webchat/latest/"

[ ] Clean up unnecessary branch on official repo
[ ] Understand production-hitting vulnerabilities

[ ] Create a new folder
[ ] Run npm init with default values
[ ] Run npm install<EMAIL_ADDRESS>[ ] Look at the result and see if there are any production-hitting vulnerabilities, investigate if needed

The PR is https://github.com/microsoft/BotFramework-WebChat/pull/XXX
Applies to major/minor releases
Bump all dependencies to latest version
On each package.json under root and /packages/:

[ ] ~All NPM packages (@babel/*, jest, lerna, typescript, webpack, etc) in PR #XXX~

Don't bump the following packages

react, react-dom, redux, redux-saga, @types/react
rxjs@5 on playground
microsoft-cognitiveservices-speech-sdk

We will bump it in a separate PR

adaptivecards

We will bump it in a separate PR

expect@25 under test/harness

The newer version requires Node.js (graceful-fs)

[ ] ~Run npm audit fix to make sure everything is fixed~
[ ] ~Test under IE11 to make sure all dependencies are working~
[ ] ~List steps to verify bumping microsoft-cognitiveservices-speech-sdk~

Obstacles to bump npm
Check if the followings are still valid. We should bump to npm@latest <EMAIL_ADDRESS>as soon as possible.
As of writing<EMAIL_ADDRESS>(bundled by node@16) has issue on running postinstall script.
<EMAIL_ADDRESS>is peer-depends on @angular/common, which npm@7 will automatically install missing peer dependencies. Track the issue here.
Bump Docker image

The Docker image can be found at root docker-compose.yml and Dockerfile*.

[ ] ~Docker container for headless Chrome (#XXX)~

They recently moved from 3.14.159-xxx tag scheme to a more sensible 87.0 tag scheme
Tags can be found at https://hub.docker.com/r/selenium/node-chrome/tags
Preferably in separate PR because screenshots change can be large occasionally
Run tests locally, as the screenshots can be slightly different
Also consider bumping to Edge-based images

We discovered an issue and started rolling out of 4.15.1.
See #4198.


Callback for toClipboard function

Hey, is there a possibility to add a callback to the toClipboard function? I'm currently
using the "Standalone usage of the toClipboard function" and was wondering if I could have an onSuccess/onError function called somehow.
Cheers!

Never mind, I think I was able to figure it out by looking at the source code.
const copy = (value: string) => {
  toClipboard(value).then(() => {
    console.log('success')
  }).catch(error => {
    console.log(`copy error: ${error}`)
  })
}

I don't know how to mock a failed copy, but I imagine it should work.


Merge pull request #1 from openlayers/master

Update from original

I think this was opened erroneously. Closing.


Bug : Search Method Fails with Multiple Domains

Hi tavily team !
When using the tavily.search method with a single domain name, the search functionality works correctly and returns the expected results. However, when including multiple domain names in the include_domains parameter, the search results are null (no results are returned).
Example Code:
# Single domain search - works correctly
response_1 = tavily.search(
    query="Qu'elle est la dernière nouveauté du 25 Juin 2024 ?",
    search_depth="advanced",
    include_domains=['www.allocine.fr'],
    include_raw_content=True
)
print(response_1)  # Expected: Non-null results
#{'query': "Qu'elle est la dernière nouveauté du 25 Juin 2024 ?",
 #'follow_up_questions': None,
 #'answer': None,
 #'images': None,
#'results': [{'{'title': 'Netflix : 17 nouveaux films à voir en juin 2024, dont le film de ...',
#}

# Multiple domain search - returns null results
response_2 = tavily.search(
    query="Qu'elle est la dernière nouveauté du 25 Juin 2024 ?",
    search_depth="advanced",
    include_domains = ['www.allocine.fr', 'www.programme.tv'],
    include_raw_content=True
)
print(response_2)  # Unexpected: Null results

#{'query': "Qu'elle est la dernière nouveauté du 25 Juin 2024 ?",
# 'follow_up_questions': None,
# 'answer': None,
# 'images': None,
# 'results': [],
# 'response_time': 1.21}

Expected Behavior:
When multiple domain names are included in the include_domains parameter, the search should return relevant results from the specified domains.
Actual Behavior:
The search method returns null results when multiple domain names are included.
Environment:
tavily-python version: [0.3.3]
Python version: [3.10.0]
Operating System: [Windows 11]

Thank you so much for you time :)

Facing the same issue in the API, through it works fine on the UI

Hi I found a solution to that.
Just add a space in before each domain.
include_domains = [
' www.allocine.fr',
' www.programme.tv'
],

Adding a space in front of each domain works for whatever reason. Would be good to get a more official solution.
Also I'd love it if the included domains were more of a "look through these domains first" instead of "only look through these domains".

Hello,
We're looking into this issue and will let you know the status as soon as we have more information. Thanks for your patience!

I have the same issue but with the AsyncTavilyClient. The addition of space before doesn't solve the issue on my side.

Hi there,
We'd like to inform you that the issue with the include_domains parameter has been resolved. The API now functions as expected when using multiple domain names.


bug(mat-select): Option duplication / staying in component

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
In a very rare edge-case I noticed that some options were duplicated / staying without function in the mat-select. It took me pretty much effort to reduce it to a minimal repro. Some code here might seam very unusual, but this all is needed for a custom control with filtering, paging and so on.
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-92ymn4
Steps to reproduce:

Check 7, 8, 9 & Close
Uncheck 7, 8 & Close
Hit "clear"
Now open the select again. You'll notice item 7 & 8 are still present

In the code there are three parts that could (most likely? Not sure since it is pretty hard to reproduce) fix the issue. One weirder than another:

Removing the sort
Removing the div
Removing empty animation (!)

Expected Behavior
No item duplication in select
Actual Behavior
Items can be duplicated in pretty rare scenarios.
Environment

Angular: 16 & 17
CDK/Material: 16 & 17

@wagnermaciel don't know what happened here, just reformed it, please check if it works now.

@angelaki Unfortunately, adding unexpected content (in this case a wrapper div around your options) into the internals of the mat-select is unsupported

Hey @wagnermaciel do you maybe have an idea what could cause this misbehavior? Maybe it is still interessting since this is just one of the three modifications, triggering this issue. Not even said, that it can even be caused without the div. I just  haven't found a reliable way. So maybe at least finding the root of this issue is still interessting? The behavior is just super weird.

I wouldn't be able to tell without digging into things, but it could be any number of things. Could be that a query within the mat-select is failing because of the unexpected html structure. Using ngIf and ngFor inside of ng-content is also a known foot-gun because it can cause the ng-content to not exist at certain lifecycle stages.

Ok, I see. I was hoping the fact that reordering the items / using empty animations would make the issue interessting enough for someone to dig into the component ;)
What do you mean with

Using ngIf and ngFor inside of ng-content

Since the options usually get repeated via ngFor it is almost always used inside ng-content? I just need the inner div for some kind of loading-animation - guess I could change this code. Could putting another child to the role="listbox"-div solve the issue? Sure this would be way more hacky, since I need to somehow manipulate the inner html of the control.

Sorry, I meant only ngIf. ngFor is safe. ngIf can cause weirdness because it can prevent the wrapper component from having access to the element if it is not being rendered. I would recommend following the examples on our docs site

But I guess showing / hiding options via ngIf is totally fine and commonly used? So this can't be an issue, I guess?
Never the less, I'd like to give it a try. I reload options in the openedChange event. But if initially no options exists (because of lazy loading), I somehow need to be able to open the mat-select. And the demos don't provide a similar solution for lazy loading. I even tried it without hiding the "empty option", but still the same behavior.
Btw.: your Select with reset option demo is broken with native select - just noticed.


opt builder

there's a bunch of doc comments and examples I want to update, but its not neccessary right now
big todo :)

bors r+

bors r+


how to remove the close icon (X)  for immediate update

how to remove the close icon (X)  for immediate update

This issue is the same Issue#26


Add language around revoking LDevID

Owners can maintain an allowlist of LDevIDs, or they can revoke IDevID.

@bluegate010 I'm refreshing the WDT and TODO PR, tagging you for review


Add an endpoint to get the packages for projects

In the front-end, we'd like to show the dependencies immediately after an analyzer run, e.g. as a flat list of de-duplicated packages, either per project, or even across all projects.
The UI could be a table that contains the parent project as a column which can be filtered for. As a quick action, I imagine having an "Export SBOM" button here that would only use the currently visible / filtered packages as the input. This would allow to create SBOMs per project, but also to omit packages with certain filtered properties from the SBOM.

I would split that into two issues, one for the list and one for the graph, because I think that the graph feature is a lot more difficult to implement.

Done. I've edited this issue to be for the list, and created https://github.com/eclipse-apoapsis/ort-server/issues/944 for the graph.

@mnonnenmacher would it be ok on your side if I gave this one a try?

@mnonnenmacher would it be ok on your side if I gave this one a try?

@lamppu Yes, we have currently not planned to start working on it and it should also not be less complicated than the vulnerabilities endpoint.

not be less complicated

Hopefully the "not" was wrong here 😆

@sschuberth can this be closed now, as Johanna's PR is merged? Although, for this endpoint to be used as you've described, it also needs the dependency trees of packages, so the two issues, this and #944 are probably coupled.

Yeah, I agree that I mixed too much of #944 into this. So let's close this as https://github.com/eclipse-apoapsis/ort-server/pull/1072 implemented what I was mainly after.


Don't lock the files while open in Visual Code

VSCode Version: 1.16.1
OS Version:

Steps to Reproduce:
Please enable external editing (don't lock the files while open in Visual Code).
Thanks
I realy enjoy the Visual Code

Reproduces without extensions: No

@BatsheveF What is not working when you try to edit a file outside?

I try to run pub build (build of dart) with output to folder open in VisualCode,
then I get an error:
"Failed to delete entry because it was in use by another process",
I expect to override the files and get a message asking to "reload modified files"
(as I get in visual studio when doing the same action).

Still happens?

yes.
I'm Running a build in PowerShel and getting:
Thursday, November 16, 2017 07:44:46 AM
pub build
Failed to delete entry because it was in use by another process.
This may be caused by a virus scanner or having a file
in the directory open in another application.

DART pub build completed <<<
Thursday, November 16, 2017 07:44:57 AM

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

Still happening.
I opened the vs code with --disable-extensions, and opened the files, then I ran the pub build.
and I'm getting the same message:
"Failed to delete entry because it was in use by another process."

@BatsheveF can you use a tool like "handles.exe" (https://docs.microsoft.com/en-us/sysinternals/downloads/handle) to see which process locks the file?

Done.
Preent Screen:

@BatsheveF you seem to have pointed it to a folder, is that also the thing you notice that the folder is locked, or is it the file?
Can you find out the command line of the CodeHelper.exe and Code.exe processes? You can do this with:
To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks. Depending on your OS you can get at the full command line of the process and paste it here. On Mac, the Activity Monitor allows to find the PID of the process and from a terminal ps aux | grep <pid> reveals its arguments.

On Windows a tool like Process Explorer helps:

Once you have the information please update this issue with it. Thanks!

The folder is locked (and all the files inside it).
 Is that the folder you are actually opening with VS Code?

It looks like the file watcher on Windows is locking the folder, I have heard this before. Does it reproduce if you configure "files.useExperimentalFileWatcher": true and restart?


fix(onramp-kit): monerium/sdk now accepts chainId

What it solves
v2.9.0 of monerium/sdk now accepts chainId

Thank you for considering my suggestion so fast!


feat(pkger): add dry run functionality for task resource

adds dry run functionality for tasks

[x] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[ ] Tests pass
[x] http/swagger.yml updated (if modified Go structs or API)

@kelwang curious why that is?


onPageInit for Index page?

Hi, I was looking for a way to know if the user is now in the main Index page after he gets back from other pages, so I tried onPageAfterBack and onPageBack to get the page name, but it seems they return the current page name not the target one.
I need to fire up a function every time the user gets back again to the index page, as onPageInit('index', .. doesn't work for this.
is there a way?

Pretty sure onPageInit is only called when the page isn't in the cache, so you would need to use onPageReinit.
onPageBeforeAnimation and onPageAfterAnimation would also work I think.
Haven't actually tested this though...

onPageBeforeAnimation is probably the best way to go.
@nolimits4web we probably need a better way to handle this

OnPageReinit actually worked, thanks @jdf221.
myApp.onPageReinit('*', function(page) {
	if (page.name == 'index') doIndexFunction();
});


Secure LDAPPasswordIdentityProvider

There is a problem with oauthConfig.erb.
It should be ldaps instead of ldap, when false is specified for insecure, under LDAPPasswordIdentityProvider.
I have tried with insecure: false, but the connection is made as 389, rather than 636.

Fix by #164


Update index.json with Azure-DevOps Extension version 0.10.0

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/vinitsuri-msft/azure-cli-extensions.git@users/visuri/azdevopsclibumpto10#subdirectory=src/$EXT&egg=$EXT"

There are linter errors with your devops commands. Still investigating the "test_source" failures.

The linter errors are fixed.

There are linter errors with your devops commands. Still investigating the "test_source" failures.

The linter errors are fixed.


install zoxide 404 error

~/.local/share/mise/plugins/zoxide/bin/install
[DEBUG] $ ~/.local/share/mise/plugins/zoxide/bin/install
* Downloading zoxide release latest...
curl: (22) The requested URL returned error: 404
asdf-zoxide: Could not download https://github.com/ajeetdsouza/zoxide/releases/download/vlatest/zoxide-latest-x86_64-unknown-linux-musl.tar.gz
asdf-zoxide: An error ocurred while installing zoxide latest.
[ERROR] ~/.local/share/mise/plugins/zoxide/bin/install failed
Error:
   0: ~/.local/share/mise/plugins/zoxide/bin/install exited with non-zero status: exit code 1

Location:
   /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/convert/mod.rs:757

Version:
   2024.1.0 linux-x64 (0d0d930 2024-01-02)

resolved by mise self-update


gh-439 - Add counter to AbstractAddElementsFromHdfsMapper

Currently, there are no unit tests which confirm that the HDFS counters are working as expected - is this tested elsewhere (e.g. in integration testing somewhere) or are these tests missing?
Would we like to add tests to check that the right counters are being incremented at the right time?

Yeah we don't currently have tests for the counters. If possible, it would be good to write some as part of this issue.


gen_esp32part.py and deprecation of Python 2 (IDFGH-4606)

Due to deprecation of Python 2 some Linux distributions have decided to remove the generic "python" executable from the path, forcing all code to explicitly declare which version of Python they require (A wise solution in my opinion, as it serves as "canary" for undefined code and prevents obscure errors, resolving the longstanding ambiguity, and still allows the use of older python 2 code). This change has been annoying when one's mind is in other tasks, but one must adapt to new times and deprecation was announced years ago.
I was proposing to change the shebang to #!/usr/bin/env python3 here https://github.com/espressif/arduino-esp32/issues/4717 but me-no-dev suggested that a global upstream action might be suitable.
Best regards.

Thanks for reporting.

Thanks for reporting.

Hi @Martin-Laclaustra. Thank you for the suggestion.

Due to deprecation of Python 2 some Linux distributions have decided to remove the generic "python" executable from the path,

Which Linux distributions are you talking about? I think all of them provide some possibility to have a "python" defined.
I personally really don't like hardcoding "python3" into all of the scripts. (ESP-IDF have aprox. 160 scripts!). The right way is to setup the desired Python at the distribution level. We have recommendations regarding that in the documentation, for example for Ubuntu: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux-setup.html#setting-up-python-3-as-default-for-ubuntu-and-debian Please take a look at them to see if any of them are suitable for you.
Another argument against is that the upcoming release (v4.3) still supports Python 2. Forcing Python 3 in the scripts would mean a breaking change for developers who stuck with Python 2.
The default Python is used only when you run install.sh. A virtual Python environment is created and . export.sh switches to that environment and "python" will become the interpreter installed in that virtual environment. Hardcoding sheebangs also could mess things up and use another Python for which install.sh didn't install the required packages.

Hi @Martin-Laclaustra. Thank you for the suggestion.

Due to deprecation of Python 2 some Linux distributions have decided to remove the generic "python" executable from the path,

Which Linux distributions are you talking about? I think all of them provide some possibility to have a "python" defined.
I personally really don't like hardcoding "python3" into all of the scripts. (ESP-IDF have aprox. 160 scripts!). The right way is to setup the desired Python at the distribution level. We have recommendations regarding that in the documentation, for example for Ubuntu: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux-setup.html#setting-up-python-3-as-default-for-ubuntu-and-debian Please take a look at them to see if any of them are suitable for you.
Another argument against is that the upcoming release (v4.3) still supports Python 2. Forcing Python 3 in the scripts would mean a breaking change for developers who stuck with Python 2.
The default Python is used only when you run install.sh. A virtual Python environment is created and . export.sh switches to that environment and "python" will become the interpreter installed in that virtual environment. Hardcoding sheebangs also could mess things up and use another Python for which install.sh didn't install the required packages.

I also commented in the linked https://github.com/espressif/arduino-esp32/issues/4717. I'm closing this now because currently a couple of workarounds are documented and we are tracking related future improvements elsewhere.

I also commented in the linked https://github.com/espressif/arduino-esp32/issues/4717. I'm closing this now because currently a couple of workarounds are documented and we are tracking related future improvements elsewhere.

I personally really don't like hardcoding "python3" into all of the scripts. (ESP-IDF have aprox. 160 scripts!). The right way is to set up the desired Python at the distribution level.

All due respect, but this is not a liking / not-liking problem, but the standard way *nix systems are set up. The correct way is actually to add /usr/bin/env python3 to the scripts, and not asking users to hack system-level settings to run the code with a legacy runtime (NB., new systems come without Python 2 anyway, see https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Python3_by_default).
For a further discussion on why hacking /usr/bin/env is bad, see https://askubuntu.com/questions/817255/default-to-python3-for-usr-bin-env-python
Broadly, a lot of esp-idf users are engineers or hobby-engineers, therefore requiring them to modify their correctly set up systems is not the best approach and may break many other applications they rely on.

I personally really don't like hardcoding "python3" into all of the scripts. (ESP-IDF have aprox. 160 scripts!). The right way is to set up the desired Python at the distribution level.

All due respect, but this is not a liking / not-liking problem, but the standard way *nix systems are set up. The correct way is actually to add /usr/bin/env python3 to the scripts, and not asking users to hack system-level settings to run the code with a legacy runtime (NB., new systems come without Python 2 anyway, see https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Python3_by_default).
For a further discussion on why hacking /usr/bin/env is bad, see https://askubuntu.com/questions/817255/default-to-python3-for-usr-bin-env-python
Broadly, a lot of esp-idf users are engineers or hobby-engineers, therefore requiring them to modify their correctly set up systems is not the best approach and may break many other applications they rely on.

Thank you @adam-ah for your interest in this topic. I don't think that the current situation is ideal. We will work on improving it.
I'm aware of the content of the links. We will find a better solution which works for all of our customers.
I'll respond to your PR in a short time.

Thank you @adam-ah for your interest in this topic. I don't think that the current situation is ideal. We will work on improving it.
I'm aware of the content of the links. We will find a better solution which works for all of our customers.
I'll respond to your PR in a short time.


error when calling drino

/node_modules/@remscodes/renault-api-client/src/gigya/gigya-client.ts:18
    this.httpClient = drino.create({
                            ^
TypeError: t.create is not a function

How to reproduce:
npm init -y
setup normal typescript env
npm install @remscodes/renault-api-client
copy past the example then run
npx ts-node src/index.ts

Hi
Can you provide your tsconfig.json and package.json please.
The problem seems to be related to CommonJS/ESM files imports.
I'm continuing to dig into the potential errors caused by its dependencies.

Hi, sure !
here is tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "esModuleInterop": true,
    "target": "es6",
    "moduleResolution": "node",
    "sourceMap": true,
    "outDir": "dist"
  }
}

and here is my package.json(I removed renault-api-client since I can't use it and installed renault-api to just have the url)
{
  "name": "ohmyzoe_service",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node dist/index.js",
    "dev": "nodemon src/index.ts",
    "build": "tsc -p .",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/express": "^4.17.21",
    "typescript": "^5.3.3"
  },
  "dependencies": {
    "@remscodes/renault-api": "^1.2.2",
    "dotenv": "^16.3.1",
    "express": "^4.18.2",
    "nodemon": "^3.0.2",
    "reflect-metadata": "^0.2.1",
    "ts-node": "^10.9.2",
    "typedi": "^0.10.0"
  }
}

@tchereau I've made a release v1.1.1 that fixes the problem (PR: #76).
The issue was indeed related to drino where the default export available in ESM was not available in CommonJS. Now it's fixed. Thank you for highlighting it.
I've tested the new release with your tsconfig.json and package.json and it works fine.
Can you confirm that it also works on your side too ?

Hi sorry for the delay, I was kinda busy and haven't time for this project
anyway, yes it is working now, thanks you :)


Tab Focus moves in the background

Tab Focus moves out of the lightbox after the close icon instead of rotating within the lightbox. I have fixed this code on my local machine but unable to push my branch due to authorization. Please help me

If you fork the repository and push your changes to a branch there, you can submit a pull request. I’m curious to see how you fixed this.

Thanks. I have raised a pull request. Kindly review it

Actually, this seems to be a react-modal issue. They have a WIP pull request here:
https://github.com/reactjs/react-modal/pull/521
I will wait on that for the fix. Thank you for the time you put into submitting your pull request for this library's sake.

Hi @zee0786 @fritz-c, it seems that we need to improve the tabbing mechanism on react-modal. Hopefully I'll try to finish this PR today.

No Problem @diasbruno , I am using forked repo of the same

It's been fixed in react-modal now.


forbid-prop-types catch hacks for array and object types

I would like forbid-prop-types to catch a hack that I've seen used occasionally to get around this rule. If you configure forbid-prop-types as follows:
"react/forbid-prop-types": ['error', { forbid: ['any', 'array', 'object'] }]

I would like the above to catch each of these props as errors:
static propTypes = {
  tags: PropTypes.instanceOf(Array),
  config: PropTypes.instanceOf(Object),
}

Both of these cases are generally just workarounds for forbidden array and object types.
Would this best be suited as part of forbid-prop-types or in another rule?

instanceOf should probably be forbidden entirely, since instanceof doesn’t work cross-realm and isn’t robust.

Hmm, I've not heard this. I've used it with native classes such as Date without much issue that I can recall. What do you mean by cross-realm I guess?

Cross-realm means, effectively, from an iframe or node’s vm module.

Do you have an article or other references I could look at?

http://2ality.com/2014/12/es6-symbols.html section 4 mentions it a bit, for one.


Incorrect values produced when epoching a continuous discrete signal using MNE epoch function

The idea was to epoch the continuous EEG data of 386.936 s long into non overlapping epoch window, of size 20 s. With a sampling frequency 250 Hz, theoretically each epochs should contain 5000 data points per epoch.
To achieve the objective, the following code was utilised,

epochs = mne.Epochs(raw, events=events, event_id=event_id,
baseline=None, verbose=True) MneApproach=epochs.to_data_frame()

To confirm whether the value return from the mne.Epoch  was correct or not, I had created a script that can performed the epoching manually. The output from the script has been validated visually and was working as intended.
However, I noticed there were different between the script output and the value from dataframe MneApproach. Apart from different values, the MneApproach contained only 176 data points per epoch; which in my opinion is incorrect as the number of data points should be 5000 data points
May I know what did I do wrong while inputting the mne.Epoch function.
The above problem can be reproduced from the following ipynb via Google Colab or from the code below
Really appreciate for any feedback and help.
import urllib.request

print('Beginning file download with urllib2...')

url = 'http://bnci-horizon-2020.eu/database/data-sets/001-2014/A01T.mat'
urllib.request.urlretrieve(url, '/content/A01T.mat')

mat = loadmat("/content/A01T.mat")
# eeg = mat["data"][0, 3]["X"][0, 0] * 10e-6
eeg = mat["data"][0, 3]["X"][0, 0]
ch_names = ["Fz", "FC3", "FC1", "FCz", "FC2", "FC4", "C5", "C3", "C1", "Cz",
            "C2", "C4", "C6", "CP3", "CP1", "CPz", "CP2", "CP4", "P1", "Pz",
            "P2", "POz", "EOG1", "EOG2", "EOG3"]
info = mne.create_info(ch_names, 250, ch_types=["eeg"] * 22 + ["eog"] * 3)
raw = mne.io.RawArray(eeg.T, info)

raw.set_montage("standard_1020")

Manual Approach
raw_b = raw.copy()

values = raw_b.get_data()
# values = numpy.zeros(20, dtype=dtype)
index = ['Row'+str(i) for i in range(1, len(values)+1)]

df = pd.DataFrame(values, index=index).transpose()
df.columns = raw_b.ch_names[:]
# df.head()
event_id = 1  # This is used to identify the events.
duration = 20. # Unit in second

# create a fixed size events array
# start=0 and stop=None by default
events = mne.make_fixed_length_events(raw_b, event_id,duration=duration)
print(events)

NoEpochs=len(events)-1
Epoch = range(0, len(events)-1, 1)

NameEpochs = pd.DataFrame(NoEpochs*(np.ones((df.shape[0], 1))), columns=['Epochs'])

for f in Epoch:
 NameEpochs.Epochs.iloc[events[f][0]:events[f+1][0]] = Epoch[f]

df = pd.concat([df,  NameEpochs], axis = 1)
df.reset_index(drop=True, inplace=True)

df.set_index([df.Epochs, df.index], inplace=True)
del df['Epochs'] ## Delete extra column
df.loc[0.0] # Extrach only epoch 0

Values for the first epoch using manual approach
MNE approach
epochs = mne.Epochs(raw, events=events, event_id=event_id,  baseline=None, verbose=True)
MneApproach=epochs.to_data_frame()
MneApproach
MneApproach.xs(0, level='epoch') # Extrach epoch 0

Values for the first epoch using MNE approach
[1]: https://colab.research.google.com/github/balandongiv/Downsample/blob/master/helpMne.ipynb

Please do not use the bug tracker for usage questions. Your question was already answered on the mailing list --- mne.Epochs has arguments tmin and tmax that you need to specify to get the epoch duration that you want. It is not enough just to space the events 20 seconds apart. You also need to specify how much time before and after each event that you want to include in the epoch.

Hi @drammock  ,
Thanks for the response.

I have not receive any response notification from the mne mailing list. Did I miss something?
I have experiment by including both tmin and tmax, but I still get the incorrect values. Really appreciate if you can add extra information on how to solve the problem.

Thanks in advance.

(mnedev) [~/Desktop] $ ipython
In [1]: import os
   ...: import urllib.request
   ...: import mne
   ...: from scipy.io import loadmat
   ...:
   ...: # download data
   ...: url = 'http://bnci-horizon-2020.eu/database/data-sets/001-2014/A01T.mat'
   ...: urllib.request.urlretrieve(url, 'A01T.mat')
   ...:
Out[1]: ('A01T.mat', <http.client.HTTPMessage at 0x7f46a532f358>)
In [2]: # make Raw
   ...: mat = loadmat("A01T.mat")
   ...: eeg = mat["data"][0, 3]["X"][0, 0]
   ...: ch_names = ["Fz", "FC3", "FC1", "FCz", "FC2", "FC4", "C5", "C3", "C1", "Cz",
   ...:             "C2", "C4", "C6", "CP3", "CP1", "CPz", "CP2", "CP4", "P1", "Pz",
   ...:             "P2", "POz", "EOG1", "EOG2", "EOG3"]
   ...: info = mne.create_info(ch_names, 250, ch_types=["eeg"] * 22 + ["eog"] * 3)
   ...: raw = mne.io.RawArray(eeg.T, info)
   ...: raw.set_montage("standard_1020")
   ...:
Creating RawArray with float64 data, n_channels=25, n_times=96735
    Range : 0 ... 96734 =      0.000 ...   386.936 secs
Ready.
DigMontage is a superset of info. 72 in DigMontage will be ignored. The ignored channels are: {'F5', 'TP8', 'PO1', 'A2', 'T7', 'FC5', 'PO2', 'P4', 'F6', 'T8', 'M1', 'T6', 'Fp1', 'F2', 'PO3', 'PO6', 'O1', 'Oz', 'Iz', 'AF10', 'P9', 'P5', 'AF3', 'T3', 'AF6', 'AF7', 'TP10', 'T4', 'PO7', 'F10', 'FT8', 'Fp2', 'A1', 'AFz', 'F7', 'T9', 'O2', 'F3', 'F8', 'P10', 'F1', 'T10', 'CP6', 'T5', 'AF2', 'TP9', 'CP5', 'AF9', 'AF4', 'F4', 'P6', 'PO9', 'FT7', 'O9', 'M2', 'P8', 'PO4', 'FC6', 'Fpz', 'P3', 'AF1', 'PO10', 'FT9', 'AF5', 'O10', 'TP7', 'FT10', 'PO8', 'AF8', 'P7', 'F9', 'PO5'}
Out[2]: <RawArray  |  None, n_channels x n_times : 25 x 96735 (386.9 sec), ~18.5 MB, data loaded>
In [3]: # make events
   ...: event_id = 1
   ...: duration = 20.
   ...: events = mne.make_fixed_length_events(raw, event_id, duration=duration)
   ...:
In [4]: # make Epochs
   ...: epochs = mne.Epochs(raw, events=events, event_id=event_id,  baseline=None,
   ...:                     verbose=True, tmin=0, tmax=20)
   ...: print(epochs.get_data().shape)
   ...:
19 matching events found
No baseline correction applied
Not setting metadata
0 projection items activated
Loading data for 19 events and 5001 original time points ...
0 bad epochs dropped
(19, 25, 5001)

As you can see this yields 5001 time points.  To trim off the extra 1 sample, you can either reduce tmax by about one sampling period, or you could try using epochs.crop() with the same tmin and tmax, and use it's argument include_tmax=False.

Hi @drammock ,
Once again thanks for the detail explanation. It really help my understanding. Maybe MNE team can consider to include the following example code in the mne documentation to ease other potential user in understanding  better the mne.epoch function.
On separate question, may I know how to retrieve specific epoch. Say I only interested to call the third epoch, or two epochs (e.g., epoch no seven and eleven). I am unable to find related documentation for this particular problem. Currently,  I have to as below to retrieve, say, epoch 16.
MneApproach=epochs.to_data_frame()
print(MneApproach.xs(16, level='epoch').iloc[:,0])

Thanks in advance

Again, please do not use the bug tracker for questions about usage. Use the mailing list or Gitter channel (both are linked here: https://mne.tools/dev/overview/get_help.html).
Discussion of how to select specific epochs is here: https://mne.tools/dev/auto_tutorials/epochs/plot_object_epochs.html

Thanks for the reply, really appreciate it @drammock


DNM: Test the test from fix choco upgrade with custom env vars

I want to be double-safe and test the test for this, related PR #5386

Ok, the double-quote issue is making the upgrade test not to finish because the MSI tries to display a dialog box and there is no one to click on it... let me modify the code to test the env vars themselves

Equivalent to the test above but with the correct test code https://github.com/signalfx/splunk-otel-collector/actions/runs/10947292400/job/30396219992#step:5:189

ok, tests are working as intended


Generated Debug impls for structs do not support hex formatting

Currently the generated implementation of the Debug trait for structures uses an approach that means hex formatting (via {:x?} and similar) is not supported.
In particular, this code explicitly generates calls to std::fmt::DebugStruct::field with the value parameter being the result of a format! macro using the default debug formatting.
If using the nested format! call is not intentional, I think it can be removed as any value that can be passed to it with the debug format specifier must implement Debug and so can be passed directly to the field method.

Not intentional, thanks for the suggestion!

Not intentional, thanks for the suggestion!


problem uploading to PyPI

@matthew-brett kindly built the OS X and manylinux wheels for the v0.5.0 release.  I gave him "Maintainer" access on PyPI, but he encountered the following issue (excerpt from a conversation on Scipy-User)
twine upload -s PyWavelets-0.5.0-cp2*

Uploading distributions to https://upload.pypi.org/legacy/

Uploading PyWavelets-0.5.0-cp27-cp27m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl

[================================] 1759042/1759042 - 00:00:02

HTTPError: 400 Client Error: author_email: Invalid email address. for
url: https://upload.pypi.org/legacy/

I guess this is because of:

https://github.com/PyWavelets/pywt/blob/master/setup.py#L213

maintainer_email="http://groups.google.com/group/pywavelets",

That's an odd message. A single maintainer email address in setup.py and multiple PyPI admins will be very common, hard to imagine that's disallowed.

I guess it's checking whether the text in the maintainer_email field is a valid email address, with an @ sign and so on.


OAK-10608 - [Indexing job] Improve regex expression used to download from Mongo to make better used of Mongo indexes

The current regex expression used to filter from Mongo the included/excluded paths has conditions on both the fields _id and _path. In most cases, the _id field contains the path of the node, but when the path is too long, the _id is replaced by an hash of the path and the full path is added to the document as an additional _path field. For these cases, the regex expression must also check the _path field.
When running an ordered traversal, we use a Mongo index on (_modified, _id). So checks on _id can be done with just the data retrieved from the index. But for the check on _path, Mongo needs to read the full document from the column store, which slows down significantly the traversal.
Currently, if _id does not match, the regex expression will always check _path, forcing a retrieval of the document. But we only need to check _path if the _id is of the form of a long path id, that is, of the pattern 4:h<hash>..., otherwise, if the _id is not a long path, then if it does not match the regex, we can be sure that the document is not needed. The check that _id is an hash can be done without retrieving the full document from the column store, so it will be fast. And in the common case, the document is not a long path, so this simple check will avoid retrieving the document from the column store.
This optimization will have a bit impact when the regex expression matches a small fraction of the repository. In the current implementation, Mongo has to traverse both the index and the column store for all possible regex filters. But with the additional check for long paths, Mongo has still to traverse the full index but it will only retrieve from the column store the documents that match the filter or the long path documents. And since the index is much smaller than the column store and can more easily be cached, this will significantly improve performance.
In a test environment, with an index job that downloads 12M out of 230M mongo documents, I got the following results:

regex filtering, without long path optimization: 1h45
regex filtering with long path optimization: 0h45m

Good description and was easy to get an overview of the problem. Looks good to me 👍

We are adding more and more document store logic here. I think it's best of the document store team could review the PR.


Update issue templates

It appears that the template generated from Github using the markdown syntax which is deprecated in favor of the yaml
Cfr. https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository


WASM _jxlDecompress hangs browser

I'm trying to decompress a jxl encoded file in the browser and am following the examples from the tests and client_worker.js Most functions from the module work, but _jxlDecompress results in a browser freeze. I would like to know what could be going wrong here. Any pointers for debugging are appreciated.
I've followed the instructions on https://github.com/libjxl/libjxl/blob/main/doc/building_wasm.md
I'm using the resulting jxl_decoder.js, jxl_decoder.worker.js and wasm bundles from: https://github.com/libjxl/libjxl/tree/43d1a60af7c4892f764bbbecbf50828c6583d3c6/tools/wasm_demo
I've enabled https and the page that I'm trying to use the module on reports self.crossOriginIsolated -> true so i don't think COOP/COEP is the issue.
I'm using chrome on macOS with an M2, and used a gcp cloud instance with debian to build the bundles.

Will check soon.

Thank you, however this is not high priority for us anymore! I was able to use jxlCreateInstance, jxlProcessInput and jxlFlush to decode images after adjusting the wasm example and building from that. I do now have an issue where we're decoding images of various types (uint8, uint16 and float32) they all work in isolation, but when trying to decode various types mixed in one page only one type will work. I will make a new issue for that when I have a more expansive explanation.
Thanks again! libJXL is awesome <3


Prepare for SAP BTP Development: Entitlements couldn't be checked

Tutorials: https://developers.sap.com/tutorials/btp-app-prepare-btp.html
When checking the entitlements (I use a trial account), some plans listed in the tutorial are not shown in the cockpit. The unit column is missing completely and the linked document (SAP Business Technology Platform Service Description Guide) does not contain information for all services (e.g., nothing about the HTML5 Application Repository service).

Hi,
I'm working on the fixes. Sorry for the delay.
Best regards,
Mahati

Hello,
closing as the tutorials are deprecated. please open a new issue if you need further support.
Best regards,
Mahati


docs(ADVANCED.md): Update switch between rg/fzf example with new feature

description
Make use of the transform action and the $FZF_PROMPT environment variable to
toggle between ripgrep and fzf with a single hotkey.

Thanks.
The use of transform action is obviously more "advanced" and may be a little daunting for some readers. So how about keeping the current example, and adding the new one with transform after it as a separate section?

I understand. I will make the necessary adjustments.

Love it, thanks!


code error: Segmentation fault (core dumped)

vvencapp encontered segmentation fault(core dumped) when encoding POC 144 using following parameter:
-c yuv420  -r 30 -rt idr  -g 16  -ip 160  --preset faster -b 0 --qp 22  --threads 1  -o out.266  -v 6

Is the input video available somewhere? Some more information would be very helpful.
Or does that always happen with long intra period IDR encoding?
I'll do some testing in the coming days. Would appreciate some pointers on where to look.

Yes, the input video is available. Here I just list the key parameters. According to my experiments, it definitely happen with long intra period IDR encoding.
But when I modified '--ip 160'  to '--ip 96', it can run normally.

Would you mind sharing the video?

The video is from CTC (common test conditions), for example BQMall_832x480_60.yuv.

We cannot reproduce the problem. I tried with both v1.0.0 and current head and it works fine.
What CPU are you running on? What SIMD settings are being used? Could you maybe paste the log?

CPU: Intel Core i3-9100F
SIMD: AVX2
Another,  I test the newest verison(v1.1.0), it works fine.

Thanks. Closing the issue.


soroban-rpc: Consider storing all ledger entry types

Soroban-rpc currently only stores the ledger entries strictly required to satisfy the simulateTransaction method. When running soroban-rpc this requires 10GB of diskspace (in practice this is 20GB, since, before checkpointing WAL it occupies another 20GB).
However, this also impacts the getLedgerEntry method, which ideally should be able to serve all the ledger entry types.
We should consider storing all ledger entry types, but, before doing that we should measure how much disk-space it would require.

A quick test in pubnet indicates this will add ~5GB to the database, which isn't much since we are already at 27GB (see https://github.com/stellar/soroban-tools/issues/464 )


[SPARK-44326][SQL][CONNECT] Move utils that are used from Scala client to the common modules

What changes were proposed in this pull request?

There are some utils are used in the scala client including ser/derse, datetime and interval utils. These can be moved to the common modules.
Why are the changes needed?

To make sure Scala client does not depend on the Catalyst in the future.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing test

@cloud-fan

Merging.


Disable Ore Dictionary Dimlets

I'm using a version of RFTools built off of the current github (2.53) and I was looking through the ore dimlets, and found that there were quite a few dimlets made from ores that were basically useless for my pack.
I looked into the dimlets.cfg, and found that those dimlets did not appear there. I know that they can be disabled via dimlets.json, but it would be beneficial to be able to disable them via the dimlets.cfg like other dimlets.

You can actually do that. You can still put <...>.id = -1 in the knowndimlets section of the config. You just have to find the name. An easy way for that is to dump all dimlets in game: /rftdim dumprarity

Oh, thanks!


Arrow ligature does not render consistently in Windows Terminal

Environment

Software
Version

OS
Microsoft Windows NT 10.0.18363.0

Windows Terminal
0.10.781.0

VS Code
1.43.2

Fira Code
2.0.0

Cascadia Code
1911.210

Powershell Core
7.1.0-preview

Windows Powershell
5.1.18362.752

Issue occurs using both fonts and both versions of Powershell.
Steps to reproduce
Type the following sequence of characters into Windows Terminal.
-> -> -> ->
Expected behavior

Four arrow ligatures are rendered, separated by spaces, as in VS Code.

Actual behavior

Two arrow ligatures are rendered. Every second -> is rendered as a ligature.

If you look closely, you can see that the color changes between the - and the >. We don’t stand a chance of ligating the two together, because PowerShell has told us they’re two different units.


 If you were to clone it from GitHub, the origin would point there by default.
There's instructions for these two cases right at the repo front page: https://github.com/kpi-web-guild/django-girls-blog-l1storez.

Add a remote called origin, but authentication to origin master failed

Check that you've added your currently used SSH key to GitHub.

I've enabled branch protection for master. You won't be able to push there directly anymore. This part of the task has been completed.
The only mistake is that you've made 9 different commits, some of which modify README. The task was to create just one empty commit, not touching any files.


[FEAT]: Replace localhost:8000/ text with some info

When running the app, accessing the server root path (localhost:8000 by default) from the browser displays Hello world!, It would be great to display some info. This is the line to be modified:
https://github.com/alesbe/mini-message-board/blob/973cc3600b083449723279affe7278977788bafd/server/routes/home.js#L6
Some info ideas (don't copy the same exact text!):

Display server endpoints (for now /: this same page, /messages: endpoint to post and get messages)
Display where the frontend is running (port 3000 by default)
Display link to this repository

If you could do this without creating extra files, like an HTML would be great! This server endpoint it's not intended to be accessed from the browser, so no HTML should be displayed!
Be creative and add any cool ideas! 🙌

im reopening this for hacktoberfest!