support of Let's encrypt

It would be great to add support of the Let's encrypt project https://letsencrypt.org/
as option in the load balancer ssl settings if possible
public beta will start soon

Jup. Would be really nice. :+1:
As I remember they moved it from 16.11 to 03.12. (public beta)

It would be a very nice feature.

:+1: wow!! It would be awesome

+1 you read my mind!! :)

http://forums.rancher.com/t/letsencrypt-integration-to-rancher/923/2?u=vincent

This seems like something that would be best as a rancher-catalog template that interacts in a standalone codebase (probably in Go) with the Let's Encrypt + Rancher APIs, rather than baking support for a very specific niche into Rancher itself (actually Cattle, and in Java).

@vincent99 Let's Encrypt requires access to the web server root(or it can run a standalone webserver) to verify your control over the domain
I think it possible only inside the load balancer because it listens the port

If a rancher-catalog template can interact with an existing LB, it would be possible.
But if it's not the case, we need it part of rancher (since the port 80 and 443 could be already used per machine).

maybe this could work also in tandem with the Route53 service that's already in the catalog. You can use that integration to validate the control of the domain.

I'm not sure that a huge pourcentage of folks use Route53 (I'm not)

Letsencypt is made by a non for porfit company, so integrating it tightly would only feel like a "soft vendor lockin" - If that is part of the concern anyway...

+1

It is possible to write a component that would run in the environment that would interact with both letsencrypt tool chain and the Rancher API to create and update the certificate.  Rancher would then propagate the certificate to the LB.  I would love to see this happen.

I've been playing with letsencrypt within rancher...
For now I haven't hooked into the rancher API, but I was trying to figure it out the best way to run the letsecrypt client.
What I did was:

Add the domain I want to get a certificate for to the loadbalancer with hostname routing and add a path to .well-known. The target for this entry in the loadbalancer is the letsencrypt service running the official letsencrypt docker image (port 80)
Run letsencrypt certonly in standalone mode and using the 80 port with the --standalone-supported-challenges http-01 argument.

This way the letsencrypt service is able to verify the ownership of the domain.
What I'm not sure how to do is the automation phase based on rancher events...
I will take a look at the external-dns catalog component.

:+1:

Cross posting from the forum:
I'd like to implement a container that runs letsencrypt (https://letsencrypt.org/) to acquire certificates for my domains and renew them automatically.
I have found the rancher API calls to add a certificate and to set a network endpoint (domain / subdomain) but I can't find a way to list all my configured endpoints.
I'm going to implement a letsencrypt plugin for rancher.
Do you have any suggestions for me?
@blackjid great manual workflow

+1 @ibuildthecloud

+1

I would love a Let's Encrypt integration with ssl termination / offloading into the loadbalancer.
Certificates should be created via Let's Encrypt API or inside a temporary Let's Encrypt client container and then moved to the loadbalancer and offered to download for production use. The Let's Encrypt client shouldn't stay in production environment.
There is also a github project offering a static website to create Let's Encrypt certificates making requests to the Let's Encrypt API.
It's a open source project:
https://github.com/diafygi/gethttpsforfree/blob/gh-pages/README.md

+1

+1
On Dec 15, 2015 2:02 PM, "Petr"<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/rancher/rancher/issues/2734#issuecomment-164757055.

Also found a nice 3MB webserver with integrated lets encryption feature.
Could be used as Webserver and also a proxy / loadbalancer.
Haven't tested it yet...
https://caddyserver.com/

+1

I guess this is an opportunity to earn some karma for capable ones.
@blackjid @zaubererty How is the status? Can you share some code? I'd love to have a look...
I think, as @ibuildthecloud envisioned, if it would be integrated into the environment, something as the following (optional/convenience!) workflow would be possible:
SSL terminate a port on a LB by the simple click on a checkbox, next to entering a domain.

+1 here :)

Almost there... :wink: :tada:

@janeczku that is so great!

@janeczku wow thank you so much!

+1

+1 for this

@janeczku https://github.com/rancher/community-catalog will be available as a first-class option in 0.57 or 0.58 if you want to put a PR in when you're done.

@vincent99 Certainly! In the process i realized that the permissions for "environment" or "external-dns" agent roles are not sufficient to create certificates and upgrade load balancers. I wonder if there is something we can do, so one needn't have to manually create an API user and fill out even more credentials in the on-boarding form for the service?
I am talking about these labels:
io.rancher.container.create_agent: "true"
io.rancher.container.agent.role: "external-dns"

Great! :)
Is a integration to the Rancher Loadbalancer planned / possible?

@janeczku that should be doable; @alena1108?

:heart:

@janeczku AWESOME job!!

@janeczku I'm also creating a container, that's almost ready to be deployed to the Rancher Community Catalog. You can read about my WIP here: https://github.com/adamgoose/rancher-certificates

Using the following labels gives the container an API Key that has access to certificates:
io.rancher.container.create_agent: "true"
io.rancher.container.agent.role: "environment"

@adamgoose Nice, that even gives permissions for updating the load balancers. :yum: :v:

I've also found that the /v1/certificates endpoint is read-only, so you need to use /v1/projects/{projectId}/certificates

Waiting for this too ^^ .

@seb2411 It's just a matter of https://github.com/rancher/rancher/issues/3556 getting fixed.

:+1:

+1

:+1: so nice to see its on it way :)

+1 @janeczku
+1 @adamgoose

+1

@silviupanaite You now have reactions in right top corner of message ;-)

Let's Encrypt is now available in Rancher's community catalog! Have a nice weekend guys!

Thx ;)

Thx ;)

Thanks @janeczku

thanks @janeczku

Hello,
Just a question, How do I add new domain names to the Common Name fields after launch the Let's Encrypt Container?
Best Regards.

@omata-metamax Just do a stack upgrade and change the environment variables.

@rancherdev I'm glad a community member included this. IMHO, let's encrypt should be included in the HA proxy implementation of rancher. I think it's very low overhead and a free service.

@willseward If I configure the instance to generate each cert in it's own directory will be all directories renewed when is needed?
Best regards.

@omata-metamax I'm not sure what you mean by individual directories. Each named certificate/key pair are placed in eponymous directories---one per instance because one service can only generate one certificate with multiple SANs.
However, by updating the SANs on the cert by means of the environment variable, the instance will pick up the difference and update it near expiry.

@willseward When configuring the instance there is an environment variable called CERT_NAME that will create another directory for that cert. Then I want to know if the cert inside it  name/directory will be upgraded when it near expiry.

@omata-metamax Yes. The service can only update one certificate/key pair at a time. I'd clone the stack for each certificate that you need.

Thank you very much @willseward

@omata-metamax No problem. I'm glad this service exists.
And I agree with @keyscores . It would be nice to have this integrated by default.

Let's encrypt support with webroot verification instead of external dns service would be great!

Has anyone configured LetsEncrypt with Rancher Kubernetes?


Bug in plotting unct envelope McLean Regression

see topsoil-js issue:
https://github.com/CIRDLES/topsoil-js/issues/21

Do you happen to know if the sigma multiplier is used anywhere else in the
TypeScript? (Do I have to add that variable to whatever Java-bridge there
is, or is it already being passed through)
On Tue, Jul 14, 2020 at 8:04 AM Jim Bowring<EMAIL_ADDRESS>wrote:

see topsoil-js issue:
CIRDLES/topsoil-js#21 https://github.com/CIRDLES/topsoil-js/issues/21
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CIRDLES/Topsoil/issues/475, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHP4JPRJF72WJBGDVVCG23R3RXYXANCNFSM4OZTOEZQ
.

That variable name does not exist but there is a variable somewhere that encompasses that idea - when your ellipses are plotted at a or 2  or 95% ... SIGMA_MULTIPLIER is a conceptual placeholder for that value.


Bug Report: Responsive Issues with Card Placement and "Read More" Button .

Reproduction Steps:
1.Access the website on a laptop or desktop with a larger screen.
2.Navigate to the blog section.
3.Scroll through the blog posts and locate a card with the "Read More" button.
-Observe the positioning of the "Read More" button within the blog post cards.
-Notice that in certain cards, the button overflows and appears outside the boundaries of the card on larger screens.
By following these steps, you can trigger the bug and observe the actual behavior where the "Read More" button is not properly positioned within the blog post card on larger screens, causing it to overflow and appear outside the card's boundaries in certain cases.
Second issue:

Access the website on a mobile device.
Navigate to the blog section.
On smaller screens, the cards in the blog section are misaligned and not properly positioned, affecting the overall layout.

By following these steps, you can trigger the bug and observe the actual behavior where the layout and placement of the blog post cards are not properly adjusted for smaller screens, resulting in misalignment and visual issues.
Expected Behavior:

The "Read More" button should be properly positioned within the blog post card, ensuring its full visibility and accessibility.
The blog section should be responsive, adapting seamlessly to different screen sizes and devices.

Actual Behavior:

In certain blog post cards, the "Read More" button is not properly positioned within the card.
The blog section lacks responsiveness, causing layout and display issues on different screen sizes and devices.

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Go for it.
For any support join our community: https://codeincommunity.com/

I am interested to work on this issue please assign me this task under gssoc.


Is it possible for an updated Zotero record to update the Notion record, instead of creating a duplicate?

I've managed to figure out how your plugin works, and great job by the way as it is helpful for me to use the 'recommended' Zotero program for gathering my references, but still have access to them all in notion for my actual note taking etc.
But what do I do if I ever need to go back and edit them? Editing them in Zotero doesn't update Notion, so would I have to remove them from the zotero collection, edit them, and then copy them back in?
I just did a quick test on that, and I ended up with two copies on Notion, so they don't seem to overwrite themselves?
Is there a way to make it so that the edited version will overwrite the notion entry for that reference?
Or, even better, would be avoiding the part where you can only sync by adding a new zotero to a collection, and instead have a manual 'sync all' that updates all records. But again not sure if thats possible with the API we have!

Hi @nirurin, thanks for the feedback!
I read your previous issue (#8) which made me realize I haven't done a great job of explaining exactly how the plugin works and what limitations it currently has. I can update the README with more info.
You're correct that, in order to get updated data into Notion, you currently have to remove them from the Zotero collection and then re-add them. This is because the only action the plugin currently listens for is "add item(s) to collection." And you're also correct that doing so will create a duplicate entry in Notion.
So, as you've identified, there's a couple improvements that could be made here:

Come up with an approach for uniquely identifying database pages in Notion so we can update them on sync instead of creating a duplicate page. I believe this can be done using either:

the Zotero URI property that's being saved in Notion
the Notion link that's attached to a Zotero item when synced into Notion

Come up with a better method of triggering the sync to Notion. A couple possible approaches for this:

(as you mentioned) add a manually-triggered "sync all" option, possibly to the collection context menu
add a listener for the "modify item(s)" action to automatically trigger a sync whenever an item is edited in the "monitored collection"

Does this sound like it captures your needs?

Thanks for the reply! Yeh I ended the old comment and started this one because I had resolved my original issue and didn't want to confuse things.

Both of the solutions you write for issue 1 make sense, but I don't know enough about the zotero and notion api in order to know which solution would work out the best.

Again, both of these solutions sound great, but I would suggest that in an ideal works the program would allow for -both- things. Having it automatically detect modified items and update into notion would be perfect, but I think having a manual 'update/sync all' button would also be useful to have.

Great work on this, I just started my masters so I'll definitely be making use of this. If there's anything I can do to help please let me know!

+1! Your plugin saves me so much time. Thanks! It would be awesome if it could sync notes as well.

@nirurin @viv-yeung I've just released version 0.2.0 that adds the option (available in Notero preferences) to sync items when they're modified. It also updates the existing pages in Notion rather than creating duplicates!
I've updated the README a bit with more details of how the plugin works.
Let me know if this works for you!


Fix grammar of ArabicLocale

Codecov Report

Merging #430 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #430   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     14
  Lines        3081   3116   +35
  Branches      226    229    +3
=====================================
+ Hits         3081   3116   +35

Impacted Files
Coverage Δ

tests/locales_tests.py
100% <100%> (ø)
:arrow_up:

arrow/locales.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@crsmithdev @andrewelkins Please let me know if this PR follows the contribution guidelines. We'd really like to see it merged so we can get back to using the pypi version of arrow ASAP.

Hi @satiani, thanks for the contribution!  (Sorry it took so long, but we've recently added new maintainers to the project and are working through the backlog.)
I have just one concern about this PR, and it's that it removes ArabicLocale completely, which will break any downstream code that references this class.  Would it make sense to rename DefaultArabicLocale back to ArabicLocale?

I can definitely rename it. I see you merged the PR, thanks for that!
Should I open a new PR to rename the class?
On Thu, Sep 28, 2017 at 20:55 Sye van der Veen<EMAIL_ADDRESS>wrote:

Hi @satiani https://github.com/satiani, thanks for the contribution!
(Sorry it took so long, but we've recently added new maintainers to the
project and are working through the backlog.)
I have just one concern about this PR, and it's that it removes
ArabicLocale completely, which will break any downstream code that
references this class. Would it make sense to rename DefaultArabicLocale
back to ArabicLocale?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/crsmithdev/arrow/pull/430#issuecomment-333002161, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKohKt3JLCaRWf8coZCii7nQKhL_wywks5snD_0gaJpZM4M_VPs
.

I updated your branch with the latest master, to fix a conflict and retest.  The PR is still open, so let's make the change here.

@Syeberman I renamed the class name.
Let me know if you have any other feedback. If there is no other feedback, do you have any estimate of when this version may be available on PyPi? I'd like to switch to using the PyPi version instead of my custom build.

@satiani Merged!
As for the release to PyPI, I can't give a date just yet, but we are actively working to catch up to PRs and then update readthedocs.io and PyPI.


map pulsating.

hi. I just added it and I see the map pulsating.
https://streamable.com/xh3qc9

Update, after double checking the files, I found the issue.
Not related to the map :)

Update, after double checking the files, I found the issue. Not related to the map :)

can u share what ur error was as mine was also pulsing but idk what is causing the issue

sure, in my case usign qbcore, it was this:
-- qb-hud/client.lua
CreateThread(function()
    while true do
        SetRadarBigmapEnabled(false, false)
        SetRadarZoom(1200) -- this was set to 1000 and changed to 1200 as said in readme
        Wait(500)
    end
end)


fix typo

Deploy preview for js-primer ready!
Built with commit 50c7fec17df66ad0b367c62216d66a70f5e983a2
https://deploy-preview-571--js-primer.netlify.com

Good Catch! Thanks


linear+gelu fused operator is not supported in ACL

Output of 'strings libarm_compute.so | grep arm_compute_version':
arm_compute_version=v23.11 Build options: {'Werror': '0', 'debug': '0', 'neon': '1', 'opencl': '0', 'embed_kernels': '0', 'os': 'linux', 'arch': 'armv8a', 'build': 'native', 'multi_isa': '1', 'fixed_format_kernels': '1', 'openmp': '1', 'cppthreads': '0'} Git hash=b'add70ace1e57f65d1ae4d0cedaec6e4578cf87ff'
Platform:
AWS c7g.16xl
Operating System:
Ubuntu 22.04

Problem description:
PyTorch2.0 introduced torch.compile() for the neural network compilation. One of the important techniques the Graph compilation  employs is the operator fusion. To execute those compiled graphs efficiently, the platform need to support the fused operators. For example, for Bert base model (I think any transformer model) inner_product+relu ,matmul+relu(or gelu or tanh) are commonly fused in the linear layer.
The issue is ACL23.11 doesn't support the above mentioned operators, hence we are not able to take full advantage of the PyTorch Graph compilation optimizations on aarch64.
Steps to reproduce:
When you run the below script, you can see that the fused operators are falling back to onednn 'c' reference kernels because ACL doesn't support them.
pip3 install torch==2.1.1
export DNNL_VERBOSE=1
import torch
from transformers import BertTokenizer, BertModel
import torch._inductor.config as config
config.cpp.weight_prepack=True
config.freezing=True

tokenizer = BertTokenizer.from_pretrained('bert-base-uncased')
model = BertModel.from_pretrained("bert-base-uncased").eval()

text = "Test bert base torch.compile on aarch64 with ACL"
encoded_input = tokenizer(text, return_tensors='pt')

model.eval()
model = torch.compile(model)

with torch.set_grad_enabled(False):
        model(**encoded_input)

Note: On PyTorch main, I have disabled the operator fusion for aarch64 to be able to use at least the other optimizations from the compilation, here is the PR. So, please use PyTorch 2.1.1 to reproduce the issue.

Hi @snadampal
Thanks for raising this. We will discuss the feature request with the team.

oneDNN shouldn't be falling back to the reference kernels (i.e. ref). acl_post_ops_t should try to fuse the operators in ACL and, if it isn't able to, it should fall back to calling ACL activation functions as a separate layer. It's slower than fusion because you have an extra store and load for each element, but it's an order of magnitude faster than the reference kernels. Let me know if there's any cases like this, the fix may be relatively simple.
Also, do we know the relative importance of different activations and data types? I haven't done any in depth analysis but for compute bound activations like gelu or tanh, there may not be much benefit to fusing them over having a separate activation layer. For the simpler memory bound activations, there should be a larger benefit. I think non-leaky relu (α = 1) is already fused into quite a few kernels, although as far as I know, leaky relu is not yet.

Hi @jondea , torch compiled version of bert-base (the script I provided above) has got  attr-post-ops:eltwise_gelu_erf  post op which is not supported in ACL, hence falling back to c++ reference kernel for fp32, and is failing to create primitive for bf16 fast math mode (because there are no reference fastmath kernels)
post-op init is returning unimplemented from this
https://github.com/oneapi-src/oneDNN/blob/main/src/cpu/aarch64/acl_utils.cpp#L108
I'm not sure if the gap in ACL is only the fused kernel or even the individual kernels.
for fp32:
onednn_verbose,primitive,exec,cpu,inner_product,ref:any,forward_training,src_f32::blocked:ab::f0 wei_f32::blocked:Ab8a::f0 bia_f32::blocked:a::f0 dst_f32::blocked:ab::f0,attr-scratchpad:user attr-post-ops:eltwise_gelu_erf ,,mb28ic768oc3072,17.3999
for bf16 fast math mode:
RuntimeError: could not create a primitive descriptor for an inner product forward propagation primitive

Great, thanks for the reproducer. It looks like ACL does in fact have a GELU implementation, at least for NEON FP32 https://github.com/ARM-software/ComputeLibrary/blob/bc89a0b690200750040770bda0981f4a37b389c4/src/cpu/kernels/CpuActivationKernel.cpp#L107
It should be straightforward to hook this up here:
https://github.com/oneapi-src/oneDNN/blob/5bb1a8ee84cea8013be409f3474ad7e0c6b1e654/src/cpu/aarch64/acl_utils.cpp#L50
and it will automatically get picked up by the acl_post_ops_t inside acl_inner_product_t.
I have made an internal issue to take a look at this and get back to you. Things are quite busy at the moment so I'll need to get back to you on timescales.

thanks for the note, @jondea , I will take a look at it.

Hi @jondea , how about the fusion support for the other primitive and post-ops combinations? Could you please add support for matmul + post-ops like gelu/relu/erf/tanh as well?

At the oneDNN level, we should automatically support combining matmul/conv/inner product with any binary or eltwise post op supported by the equivalent standalone ACL primitive. So matmul/conv/inner + gelu/relu/erf/tanh should accelerated by ACL in oneDNN (GELU went into v3.5).


Use SparseMatrixColorings

Codecov Report
Attention: Patch coverage is 0% with 35 lines in your changes are missing coverage. Please review.

Project coverage is 14.97%. Comparing base (cebfca6) to head (5cde92d).

Files
Patch %
Lines

DifferentiationInterface/src/sparse/jacobian.jl
0.00%
28 Missing :warning:

DifferentiationInterface/src/sparse/hessian.jl
0.00%
7 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #270       +/-   ##
===========================================
- Coverage   96.03%   14.97%   -81.06%
===========================================
  Files          75       56       -19
  Lines        3908     1903     -2005
===========================================
- Hits         3753      285     -3468
- Misses        155     1618     +1463

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


FR: callback to catch token exceptions

When the client deems a token to have expired, using its locally stored creation time and expires_in values, it will automatically renew the token. The renewed token can then be stored/persisted by the application using the callback provided in #110 That works great, and takes the renewal burden away from the business logic of the application.
Now, the locally stored expiry time may be out of step from the real expiry time. This is especially the case at the edge of the token lifetime where HTTP delays in the fetching of the original token may put he expiry time out by one second or more, leaving the application thinking the token has a second more of life, but Google insisting the expired a second ago. This results in an exception, right in the middle of the business logic using the API.
This exception can be caught, the message checked, a token renewal attempted etc and that can get things back on track. However, that is not a domain that should impinge on the business side of the application; it really does not care about the OAuth negotiating wranglings, and it really should not have to care.
So, what I would like to propose for discussion, is a callback that can be used in a similar way to the expired token callback, to allow the application to invisibly attempt to fix any token issues in the event of an invalid token being found. I guess this callback would replace the exception once, then the client would reattempt the remote API call. If it works, great, all carries on happily. If it does not work, then fine, the application had a chance to fix its tokens but couldn't.
Issues I see are the recursive nature of this callback: the callback to the client trying to access the API would need to use the same client to renew the tokens. That may or may not have side-effects.
My workaround at the moment, to try to steer away from this edge-case, is to knock five minutes off the expires_in that the client supplies for a new token, so it renews early. But that's not ideal. This is all in the interest of keeping the lights on in offline access to the API when OAuth authenticated by an end user.

Before I start diving into the code and doing PRs and suchlike, I just wanted to check if I am missing something with perhaps other workaround, or if other people also have this [potential] problem.

Thank you for reporting this issue! We would love to see a PR to fix this. Another way we could do this is we could be conservative when checking to see if the access token is expired, and give ourselves a few seconds of wiggleroom, e.g.:
$wiggleroom = 5; // 5 seconds
$isExpired = time() + $wiggleRoom < $expires;

I haven't looked at this for a while, so I'll try the latest version and have a dig around again.
I don't have any qualitative evidence, but I would think the wiggle room would help some cases where the network happens to be a bit slow. It is just renewing a few seconds early, which can't be a bad thing. I'm using a longer wiggle room because I have some longer running scheduled jobs. I'm guessing long running jobs would be discouraged on cloud-based services where each job is there to do something simple and finish quickly.

I think the main issue here is the library cache by default does not actually look at the token expiration. It just calls for a new access token on every request and caches the fetched access token in memory.
One solution is to store the full access token in the cache, and check the expiration when the access token is retrieved (or set the cache's expiration to the token expiration. either way should work as long as the expiration is valid). This would allow users caching across multiple requests to make a minimum number of token requests to the APIs.

Let me take a step back and explain how I think this works, where I think - as an application developer - it can make things difficult. If my understanding is incorrect, please say:

On initial authorisation, this library obtains an access token, a refresh token, and starts a 30-minute clock ticking on the access token. These are all passed back to the application to look after in the context of a user account.
On each execution of the app - perhaps a page load, or a scheduled service run - the access token, refresh token and creation timestamp are passed to the library.
If the access token time has expired, i.e the 30 minute countdown has been passed, then the library will fetch a new access token using the refresh token and restart the timer.
If a callback has been registered. the application will be informed of the new access token so that it can be stored against the user's account.
The API call to whatever Google service is then made using the current access token.
At this point, if it turns out the access token has expired (assuming we just got the timer wrong) then an exception is raised. This is the main problem for me, as that exception now has to be handled by the application. In reality it is no an exception to the application - it is something the library can handle by renewing the access token. The "wiggle room" will help to reduce the chances of this happening, but IMO whatever time you use will ultimately be arbitrary and in all probability will not be long enough at some point when networks are slow.

On point 4, I have seen applications that do not use the callback, and retain the original access token without ever updating it. They end up renewing the token on every page load, once past the first 30 minutes, which can't be desirable. I realise that is a problem in the application development, but I wonder if it just needs to be highlighted more in the documentation?
My use-case for all this is an application that runs on a user's own server or site, that the user authenticates, but then accesses the Google services on its own using scheduled jobs. I would like to be sure expired tokens (that may expire before the 30 minutes, or where the 30 minute timer was started significantly later than Google's own timer for whatever reason) are handled smoothly and preferably invisibly, and that the application is always informed about the new access tokens to help reduce hits on your services.
Hopefully that clarifies my thinking and isn't just me repeating myself :-)

This all sounds accurate, thank you for taking the time to type this out. Although I'm not sure about point 2. When are the previous tokens used to initialize the library? I assume this is happening in the application layer.
We could definitely include in the Middleware (or add a new middleware) the logic to retry the authentication call if the request throws an expired exception. What do you think of the following changes?

Add an Expiration Handling / Retrying Middleware.
Provide the full access token to tokenCallback
Take into account token expiration in the caching layer.

I am seeing another problem with the caching, which is that CacheTrait is implemented in both FetchAuthTokenCache and ScopedAccessTokenMiddleware. This is a little wonky. I am hoping this isn't an actual issue as long as nobody's really using ScopedAccessTokenMiddleware.

On point 2, the initialisations, I meant the authentication client. The "library" was a little too broad.
$client = new Google_Client();
// set scope, redirect URL, access type, approval prompt etc.
// Set the current access token:
$client->setAccessToken($json_token);

The $json_token looks something like this:
1
5
6
2.04s10.25MBGET reports/site/{site_id}web<EMAIL_ADDRESS>{
    "access_token":"ya29.Gl3UBA86bj2DW...yPLmq1vpffV4",
    "token_type":"Bearer",
    "expires_in":3480,
    "refresh_token":"1\/VRdVb3...Ixs",
    "created":1506594548
}

The current access token, its expiry and the refresh token are all in there. These details were stored in the application and are all that is needed to access Google services for an authorised user. These are the "initialisation details" that I referred to.
Then here also the $client->setTokenCallback() is created to save any changes to the access token when the library renews it (when it checks the timestamp and deems it to have expired, but not when it tries to use it and the remote end says, "hey, it's expired"). I do that here:
https://github.com/academe/laravel-google-api-auth/blob/master/src/Helper.php#L56-L80
I've not got a full grasp of how "middleware" is defined in this library, but if it is a layer to invisibly catch certain states and act on that, it is probably what we would be looking for. I think the point is that it would need to be caught right where the required API request is sent to Google, so that once the access token is renewed, it has all the information is needs to re-send the same request. So I guess middleware that handles this http message and its response would be the place? But I'm a little out of my depth at this point on implementation, but your suggestions sound good.
I'll explore the middleware a little deeper to try to understand it more.


Enhancement: Embed resources

The two external resources (BDF font and icon) should be fully embedded in the code to simplify packaging and deployment.
Consider the https://alire.ada.dev/crates/are package.

Implemented for next release.


Multiple visualizations in a single HTML?

I wrote a HTML page using this library, which is now hosted here.
It contains multiple Bayes Network visualizations (in Instructions, task 2 and task 4 sections).
It seems like the visualizations are linked to one another, in a way I do not fully understand.
In particular, it seems that when I interact with the first visualization then it is the nodes in the last one that gets edited, though the arrows are correctly edited in the first visualization.
In terms of solving it, I tried renaming every JS and HTML element to have an unique game; it did not work.
Why does this happen? Is there any example available of multiple visualizations in a single page?

Here is a minimal reproducible example of the mistake, hosted in Plunker
https://plnkr.co/plunk/H0JcOnw6lcgdQ6wJ


MudLoadingButton: removed Title property

removed title property as the MudBaseButton itself provides it now https://github.com/MudBlazor/MudBlazor/pull/8630

Thanks 🥇


Fix performance degradation while host functions call

Issue #, if available:
This is probably one of the option to fix performance issue
Description of changes:
Hosts functions performance tests before fix
/u01/git/wasm/go-plugin/tests/host-functions
go test -run='^$' -bench '^Benchmark' ./... -count=6 -timeout 99999s
name              time/op
HostFunctions-12  1.76ms ±12%

name              alloc/op
HostFunctions-12  5.95kB ± 6%

name              allocs/op
HostFunctions-12    25.0 ± 0%

Hosts functions performance tests after fix
/u01/git/wasm/go-plugin/tests/host-functions
go test -run='^$' -bench '^Benchmark' ./... -count=6
HostFunctions-12  13.5µs ±12%

name              alloc/op
HostFunctions-12  6.27kB ± 1%

name              allocs/op
HostFunctions-12    25.0 ± 0%

Hosts functions performance tests for v0.7.0
/u01/git/wasm/go-plugin/tests/host-functions
go test -run='^$' -bench '^Benchmark' ./... -count=6
HostFunctions-12  10.6µs ±11%

name              alloc/op
HostFunctions-12  5.99kB ± 2%

name              allocs/op
HostFunctions-12    24.0 ± 0%

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
cc: @codefromthecrypt , @lburgazzoli

ps you can use https://pkg.go.dev/golang.org/x/perf/cmd/benchstat to format the before after so it is easier to read.

ps you can use https://pkg.go.dev/golang.org/x/perf/cmd/benchstat to format the before after so it is easier to read.

Yes, sure. Changed to the new format

hmm I think there is a problem somewhere still, I ran offline just to see before/after and I see a lot of errors.
$ go test -run='^$' -bench '^Benchmark.*' ./... -count 6
?   	github.com/knqyf263/go-plugin/cmd/protoc-gen-go-plugin	[no test files]
?   	github.com/knqyf263/go-plugin/encoding/defval	[no test files]
?   	github.com/knqyf263/go-plugin/encoding/tag	[no test files]
PASS
ok  	github.com/knqyf263/go-plugin/examples/helloworld	0.107s
?   	github.com/knqyf263/go-plugin/examples/helloworld/greeting	[no test files]
PASS
ok  	github.com/knqyf263/go-plugin/examples/host-function-library	0.072s
?   	github.com/knqyf263/go-plugin/examples/host-function-library/library/json-parser/export	[no test files]
?   	github.com/knqyf263/go-plugin/examples/host-function-library/library/json-parser/impl	[no test files]
?   	github.com/knqyf263/go-plugin/examples/host-function-library/proto	[no test files]
PASS
ok  	github.com/knqyf263/go-plugin/examples/host-functions	0.083s
?   	github.com/knqyf263/go-plugin/examples/host-functions/greeting	[no test files]
PASS
ok  	github.com/knqyf263/go-plugin/examples/known-types	0.079s
?   	github.com/knqyf263/go-plugin/examples/known-types/known	[no test files]
PASS
ok  	github.com/knqyf263/go-plugin/examples/wasi	0.080s
?   	github.com/knqyf263/go-plugin/examples/wasi/cat	[no test files]
?   	github.com/knqyf263/go-plugin/gen	[no test files]
?   	github.com/knqyf263/go-plugin/genid	[no test files]
?   	github.com/knqyf263/go-plugin/tests	[no test files]
goos: darwin
goarch: arm64
pkg: github.com/knqyf263/go-plugin/tests/fields
BenchmarkFields-12    	--- FAIL: BenchmarkFields-12
    bench_test.go:51: wasm error: out of bounds memory access
        wasm stack trace:
        	.runtime.hashmapSet(i32,i32,i32,i32)
        	.field_test_test(i32,i32) i64
BenchmarkFields-12    	--- FAIL: BenchmarkFields-12
    bench_test.go:51: wasm error: out of bounds memory access
        wasm stack trace:
        	.runtime.hashmapSet(i32,i32,i32,i32)
        	.field_test_test(i32,i32) i64
BenchmarkFields-12    	--- FAIL: BenchmarkFields-12
    bench_test.go:51: wasm error: out of bounds memory access
        wasm stack trace:
        	.runtime.hashmapSet(i32,i32,i32,i32)
        	.field_test_test(i32,i32) i64
BenchmarkFields-12    	^Csignal: interrupt
FAIL	github.com/knqyf263/go-plugin/tests/fields	0.468s
--snip--
panic: free: invalid pointer
--snip--

disregard my comment as I didn't make test first


Updated esbuild to version 0.14.47 in wrangler package

Hi
I wanted to use the relatively new typescript feature "extends constraints on infer type variables".
This is supported since esbuild version v0.14.46.
Current workaround to use locally
package.json:
  "devDependencies": {
    "esbuild": "0.14.47",
    "wrangler": "2.0.15"
  },
  "overrides": {
    "wrangler": {
      "esbuild": "$esbuild"
    }
  },

hmm, odd error, I can reproduce this locally. I'll have a look at this soon.

I couldn't find anything online about this error. And I am out of ideas.
Do you have an idea where to look?

In the newly built version of wrangler (i.e. in wrangler-dist/cli.js) the error is on this line:
_a = _typeModule(_typeModule), _nbind.Type = _a.Type, _nbind.makeType = _a.makeType, _nbind.getComplexType = _a.getComplexType, _nbind.structureList = _a.structureList;

Note that _a has not been defined (or indeed is ever even mentioned) elsewhere in the file.

Setting alwaysStrict to false in the wrangler package tsconfig.json resolves this problem.
Pushed a commit and rebased on main.

Thanks for the fix @petebacondarwin! Looks good to me, let's land this.


refactor ABI formatting

whenever we see an extern "Rust" on a function, we don't strip it from the function (which fixes #5701)

I'd be glad to move ahead with the first aspect of the change (although I'd still like to see whether #2908 is already fixed, or would be fixed by this), but we cannot make the second change.
Rustfmt's default behavior does not remove the "C" ABI and would add one in the event the input code was missing it. That's the required default as per the Style Guide (refs https://doc.rust-lang.org/nightly/style-guide/items.html#extern-items) with the discussion and reasoning being captured in https://github.com/rust-lang/style-team/issues/52.
Setting the force_explicit_abi option to the non-default value false is intentionally doing the opposite, as noted in the config option docs:
https://github.com/rust-lang/rustfmt/blob/master/Configurations.md#force_explicit_abi

Note: Non-"C" ABIs are always printed. If false then "C" is removed.

Since force_explicit_abi is a stable option, we cannot change this behavior, at least not outside a style edition boundary change. We could potentially evolve this option to be an enum instead of a boolean to offer the equivalent of AlwaysAdd/AlwaysRemove/PreserveExistingButDoNotAddNew as part of the 2024 style edition, but we can't change this now and I wouldn't want to change the boolean behavior to the third variant

Oh well. I just think that it is unfortunate that rustfmt has to support this and that the option is already stable. I think stripping the extern "C" isn't something that rustfmt should be able to do (to me i don't think rustfmt should add or remove tokens, but I guess people have their opinions)

to me i don't think rustfmt should add or remove tokens, but I guess people have their opinions

fwiw I understand this thinking, and there are plenty of cases where we decline to add functionality to rustfmt because the ask seems like a better fit as a lint with something like rustfix providing the automated remediation capability.
However, some key decisions were made long, long ago to have a defacto standard Rust Style with rustfmt being provided to take any arbitrary input and being able to manipulate that input to conform with that standard. That inherently establishes scenarios where rustfmt has to add or remove tokens (not to mention there are some cases, including recent ones, where it's necessary to add/remove parens or braces in order to be able to format code without invalidating it or failing to uphold semantics).
There's tradeoffs to the pretty-printing model with potential token adjustments of course, and the more whitespace-adjustment oriented formatters that don't manipulate tokens have their respective pros & cons too

i've restored the force_explicit_abi = false behavior.

@fee1-dead ping me whenever you get a chance to resolve the conflicts and I'll get it merged :+1:

@calebcartwright: rebased

@fee1-dead thanks for your help on this! @calebcartwright I could merge this one, so I went ahead and did so.


WFLY-13193 Move resteasy-client-microprofile to dedicated module

https://issues.redhat.com/browse/WFLY-13193

@asoldano I think you will need to add something to this or Galleon won't provision this module when it creates a slimmed server:
https://github.com/wildfly/wildfly/blob/master/jaxrs/src/main/java/org/jboss/as/jaxrs/JaxrsSubsystemDefinition.java#L72
If needed @jfdenise can provide more details during morning in Europe tomorrow.

Once you have something you're good with please open a 19.0.x PR so we can get Beta 3 done not too late tomorrow.


Change zoom meeting types

Unfortunately, zoom meetings does not have the ability to live stream, and due to this we can't live stream the performance meetings. We need to change the meeting type to a webinar (I'm not quite sure), and update all the meeting scripts to use and post the new URL.
cc @mhdawson Can you help with this?

@anonrig I think we got you access to zoom? From there you can create a webinar. Once you have the new zoom link, then updating for meeting scrips is a PR to https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/meeting_base_performance


Unable to install ionic v1.x

Ionic version:  (check one with "x")
[x ] 1.x
[ ] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I try to download ionic but it hangs

Also i tried with a specific version but it shows me this:

What could it be?
This is my current Env:

Thanks in advance!

BTW: i installed cordova successfully!

This issue was moved to driftyco/ionic-cli#2060


Use the compendium browser to add a feat to the ASI advancement

When you use the ASI advancement, there's an option to allow a feat instead. There's a space at the bottom of the advancement window where you can drag the feat onto. Can we make that clickable so it brings up the Compendium Browser so the player can select a feat from there? Kind of like how clicking on the blank space for the Species on the character sheet brings up the Compendium Browser to select one.

Yeah, integrating the compendium browser into advancements where useful will hopefully come in 4.2 when I redesign the advancement UI using the new styles.


Fixed an issue that prevents 9.7.0 to 9.7.1 upgrades

Closes #4075

Adds missing SqlDataProvider files

Summary

Adjusted order and added 09.07.02 also for upcoming release @david-poindexter if you can approve please :)


Ethereum support via websocket?

Any idea if the websocket will support ethereum prices in near future?

It kinda does, if you change this line at websocket.js ETH-BTC or ETH-USD instead of BTC-USD...

Or, simply pass ETH-BTC when declaring it...
var websocket = new CoinbaseExchange.WebsocketClient('ETH-BTC');

Correct, websocket feed works for any supported product.


fuse is not documented

Is there any plan to add a documentation for fuse? This issue is moved from https://github.com/chainer/chainer/issues/2529.

This issue was resolved in PR #1789.


Other: Removal of Debug Tags from Screens in app

Describe the feature
Problem Description:
The Flutter app currently displays debug tags on screens, which are visible during development and testing phases. These debug tags can detract from the app's professional appearance and may confuse users or distract from the intended user experience.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

I want to work on this issue
can you assign this to me.

Hi sir,
I would like to work on this.
Kindly assign this issue to me.

can you assigne me this cause i am newbi so it's perfect problem to solve me 😅

Hello sir,
I would like to work on this.
Kindly assign this issue to me.

Hello @Yashshukla11 Sir, I think I contribute on this issue , please assign this me !!!

Done


[WIP] Categorical contrast color palette that is consistent across panels

Follow up to #1079, this branch has a demo of another approach:

Color conversion using predefined palette for contrast
Overall approach adapted from: https://stackoverflow.com/a/31037383/17575201
Contrast colors started from: https://stackoverflow.com/a/12224359/17575201

Downside here is the colors have a lot of contrast, but they start to repeat after 38 timeseries
https://user-images.githubusercontent.com/9369625/230654974-641f980e-7233-4e25-84c0-60bc6574d75b.mov

This could be helpful for our Categorical color palette later, but it's not going to work when we have hundreds or thousands of series 😞


Quoted-Printable, Soft Line Breaks problem

Hi,
I'm using a Quoted-Printable encoding type, and if I have a URL in my email body, with for example
www.milanvasic.com/test/test.jpg , surround with HTML, and if 76 character is dot '.' the SWIFT replace it with equal and break the line, that's correct but the problem is in new line SWIFT add one more dot, and on users side we have a wrong URL's with two dots, like www.milanvasic..com/test/test.jpg.
Regards,
Milan
P.S.
some header details
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Original creation date: 2009-11-03T20:04:39Z
Original reporter: Milan Vasic
Original ticket: http://swiftmailer.lighthouseapp.com/projects/21527/tickets/113

Same happens to me with Symfony2 and Swift Mailer v4.1.5
Anyone know a workaround for this issue?


Add ability to remove credential

Summary of Changes

Credentials can be removed from the details screen
Adds new common delete modal (to be re-used with deleting contacts)
Updates Bifold with latest react-hooks

Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[ ] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[ ] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[ ] Updated documentation as needed for changed code and new or modified features;
[ ] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

@PatStLouis Able to supply the accompanying French translation for this feature?

@jleach we will have a look, is it possible to add the fr localization file with placeholders in the PR like last time?

@jleach we will have a look, is it possible to add the fr localization file with placeholders in the PR like last time?

Sure thing, I can commit an update with that

https://github.com/hyperledger/aries-mobile-agent-react-native/issues/385
Added as a reminder


Fix port

Changing '--port', '0' to '--port', '' to avoid the following error message:
docker: Error response from daemon: driver failed programming external connectivity on endpoint upbeat_haslett (9eb48aa55a0c0d79a31616850c8fff6173fb088c6f6deb1213a8e9c0ffc90a04):  (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32807 -j DNAT --to-destination <IP_ADDRESS>:0 ! -i docker0: iptables v1.8.7 (nf_tables): Port `0' not valid\n\nTry `iptables -h' or 'iptables --help' for more information.\n (exit status 2)).

INFO:__main__:Running: docker run --rm --privileged --shm-size=2g --platform linux/amd64 -e FUZZING_ENGINE=libfuzzer -e HELPER=True -e FUZZING_LANGUAGE=c++ -e PROJECT=<project> -e SANITIZER=coverage -e COVERAGE_EXTRA_ARGS= -e ARCHITECTURE=x86_64 -p 0:0 -v <host_dir>:/corpus/xmltest -v <host_dir>:/out -t gcr.io/oss-fuzz-base/base-runner coverage xmltest.
ERROR:__main__:Failed to generate clang code coverage report.

This works for local experiments:
================================================================================
*tinyxml2, XMLNode * const XMLElement::ShallowClone(XMLDocument *)*
build success rate: 1.0, crash rate: 0.0, max coverage: 0.25104166666666666, max line coverage diff: 0.03356956359567326
max coverage sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_znk8tinyxml210xmlelement12shallowcloneepns_11xmldocumente/fixed_targets/01.cpp
max coverage diff sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_znk8tinyxml210xmlelement12shallowcloneepns_11xmldocumente/fixed_targets/01.cpp
max coverage diff report: None

================================================================================
*tinyxml2, XMLError XMLDocument::LoadFile(const char *)*
build success rate: 1.0, crash rate: 0.0, max coverage: 0.020931449502878074, max line coverage diff: 0.00969787392763894
max coverage sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml211xmldocument8loadfileepkc/fixed_targets/01.cpp
max coverage diff sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml211xmldocument8loadfileepkc/fixed_targets/01.cpp
max coverage diff report: None

================================================================================
*tinyxml2, void XMLElement::SetAttribute(const char *, const char *)*
build success rate: 0.0, crash rate: 0.0, max coverage: 0.0, max line coverage diff: 0.0
max coverage sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlelement12setattributeepkcs2_/fixed_targets/01.cpp
max coverage diff sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlelement12setattributeepkcs2_/fixed_targets/01.cpp
max coverage diff report: None

================================================================================
*tinyxml2, bool XMLPrinter::VisitEnter(const XMLElement, const XMLAttribute *)*
build success rate: 1.0, crash rate: 0.5, max coverage: 0.2803543512245961, max line coverage diff: 0.09436777321894815
max coverage sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlprinter10visitentererkns_10xmlelementepkns_12xmlattributee/fixed_targets/01.cpp
max coverage diff sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlprinter10visitentererkns_10xmlelementepkns_12xmlattributee/fixed_targets/01.cpp
max coverage diff report: None

================================================================================
*tinyxml2, XMLAttribute * XMLElement::FindOrCreateAttribute(const char *)*
build success rate: 0.5, crash rate: 0.0, max coverage: 0.23799582463465555, max line coverage diff: 0.011562849682954122
max coverage sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlelement21findorcreateattributeepkc/fixed_targets/01.cpp
max coverage diff sample: /usr/local/google/home/donggeliu/Code/oss-fuzz-gen/results/output-tinyxml2-_zn8tinyxml210xmlelement21findorcreateattributeepkc/fixed_targets/01.cpp
max coverage diff report: None


Create AzureCore.framework iOS

Contains all common infrastructure needed to process the request pipeline.
Azure.Core

[x] Define HTTP Pipeline Architecture (@tjprescott, @bsiegel)
[x] Implement HTTP Pipeline

[x] Implement basic HTTP Pipeline (@tjprescott)
[x] Pipeline configuration #150
[x] Implement request / response (de)serialization #147
[x] Error handling
[x] Cancellation #325

[x] Implement HTTP Pipeline Policies

[x] Request modification

[x] User Agent #143
[x] Request ID #144
[x] Date #163

[x] Credentials

[x] Bearer token #146

[x] Response modification #161

[x]  Response validation
[x]  Scrub eTag

[ ] Retry #356
[x] Logging #149 (@bsiegel)

[x] Logger interface
[x] HTTP logger policy
[x] cURL-formatted logger policy

[x] ~Retry #145~
[x] ~Tracing #148~
[x] ~Proxy #154~

[x] Define async architecture #152 (@tjprescott)
[x] Define paging architecture #151 (@tjprescott)
[x] Implement paging #164 (@tjprescott)
[x] ~Define LRO architecture #153~
[x] ~Implement LRO~

AzureCore has been released in Preview. Closing.


More accurate descriptions of the sensor info (based on android names)

Updated some of the names in the Sensor Info proto to more accurately describe what they relate to.  Based on the names of the sensors in Android.

There was a PR on the old Unknown6 repo with the similar field names that was lost.
Android uses TYPE_MAGNETIC_FIELD so should magnetic_x etc. be magnetic_field_x?

@trisk yes you are correct.  Updated the magnetic fields to magnetic_field to help clarify them

LGTM assuming these have been verified as the SensorManager inputs.

I have verified these with both my phones as the inputs I was getting.  If someone else needs to verify these inputs please let do so.

Confirming:
Sensor Proto:
"SensorInfo": {
"TimestampSnapshot": 59036,
"MagnetometerX": 0.0022337138652801514,
"MagnetometerY": 0.0026361793279647827,
"MagnetometerZ": 0.2616863250732422,
"AngleNormalizedX": 21.540000915527344,
"AngleNormalizedY": 21.899999618530273,
"AngleNormalizedZ": 52.560001373291016,
"AccelRawX": -0.00027099999715574086,
"AccelRawY": 0.012594999745488167,
"AccelRawZ": 0.39435499906539917,
"GyroscopeRawX": 0.008522115647792816,
"GyroscopeRawY": -0.008522115647792816,
"GyroscopeRawZ": 0.008522115647792816,
"AccelNormalizedX": -0.2290843278169632,
"AccelNormalizedY": 0.09253333508968353,
"AccelNormalizedZ": 9.803537368774414,
"AccelerometerAxes": 3
},
Sensor Outputs:
Linear Acceleration Sensor [0.0022337139,0.0026361793,0.26168633]
AK09911C Magnetic field Sensor: [21.54,21.9,52.56]
Rotation: [-2.71E-4,0.012595,0.394355,0.918871,3.0]
Gyroscope: [0.008522116,-0.008522116,0.008522116]
Gravity: [-0.22908433,0.092533335,9.803537]

Oh this makes so much sense. Great work!
key9 is also present in SensorInfo. Perhaps int32 has_magnetic_field = 9? In 0.35.0 I've only seen -1 or 1. When key 6-8 are null I see key9 == -1.. if key 6-8 are set then I see 1. In some of my older dumps I've seen 2, but I haven't reproduced that on the current version.

Probably Rotation Accuracy:
Rotation: [-2.71E-4,0.012595,0.394355,0.918871,3.0]


added checkbox based theme selector

#911
Add a checkbox based theme selector for the Guidances and Questions pages

merging this one in since our contractor has started and will benefit from this simplification of theme selection

submitting an additional PR afterward to remove some old guidance views/partials that are no longer used


KAFKA-12895: Drop support for Scala 2.12 in Kafka 4.0

JIRA: KAFKA-12895

We propose to deprecate Scala 2.12 support n Apache Kafka 3.0 and to drop it in Apache Kafka 4.0.

Implement KIP-751
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hi @jolshan,
You mentioned earlier that you were interested in this ticket. Could you please take a look?
Thank you ! 😺

Please also update the LICENSE-binary, there are some scala 2.12.19 version, and should also update the gradlewAll file

Currently there are some html metiond about Scala 2.12 are located in Streams module. I'm not sure they should be change in this PR or not.

Scanned through some of the files here: https://github.com/search?q=repo%3Aapache%2Fkafka 2.12&type=code
I noticed the vagrant file also has 2.12 references. Is this just for building old versions? https://github.com/apache/kafka/blob/9cb49092f0865ae18487444be52aa1d03b915de3/vagrant/base.sh#L116
What is the concern about the streams changes?

I noticed the vagrant file also has 2.12 references. Is this just for building old versions?

yes, the dockerfile (e2e) also has 2.12 references.
https://github.com/apache/kafka/blob/6ee46ea86530e019798ba0d4183164d7925dde63/tests/docker/Dockerfile#L99

For the classes where we're actually change code (LogCleanerManager and LogCleaner), can you double check that we have unit test code coverage for these methods? I just want to be sure we're not changing the logic.

This PR should primarily focus on removing Scala 2.12. The changes made to LogCleanerManager and LogCleaner seem more like cosmetic modifications. It might be better to revert them to their original state.

This PR should primarily focus on removing Scala 2.12. The changes made to LogCleanerManager and LogCleaner seem more like cosmetic modifications. It might be better to revert them to their original state.

These are not just cosmetic, they're fixing unnecessary perf overhead as well. I don't think we should have any code remaining that has a "Scala 2.12" comment. So, the change was fine, in my opinion. If we want to do it via a separate PR, let's make sure we have a JIRA and we don't consider the work done until this is also completed.

These are not just cosmetic, they're fixing unnecessary perf overhead as well. I don't think we should have any code remaining that has a "Scala 2.12" comment. So, the change was fine, in my opinion. If we want to do it via a separate PR, let's make sure we have a JIRA and we don't consider the work done until this is also completed.

It seems to me that both "cosmetic" changes and "unnecessary performance overhead" should be handled in a follow-up to avoid prolonged discussions. I believe there are several improvements, such as KAFKA-14615, that can be addressed after dropping Scala 2.12.

If we want to do it via a separate PR, let's make sure we have a JIRA and we don't consider the work done until this is also completed.

https://issues.apache.org/jira/browse/KAFKA-17667

My point is a bit different. It's one thing to have optimizations, but it's another to have leftover code like:

// Note: we don't use retain or filterInPlace method in this function because retain is deprecated in
// scala 2.13 while filterInPlace is not available in scala 2.12.

Doing what it takes to clean up such comments should be part of removing 2.12 support.

Doing what it takes to clean up such comments should be part of removing 2.12 support.

I agree with cleaning up the comments and straightforwardly rewriting the code using Scala 2.13 APIs. However, any tasks requiring further discussion or additional testing can be deferred to a follow-up. This approach helps prevent infinite conflicts in this large patch (with 54 files changed)


[QUESTION] will skia work in UWP ARM64 architecture?

will skia work in UWP ARM64 architecture?

Yes and no.
No for right now because the current set of packages are based on fairly old builds.
Yes for in a bit. Right now we have an old build system. We need to update to VS2019 (#1030). That just does the managed part, but I'm working on the PR for the native bits. Shouldn't be too hard, just haven't gotten to it yet.

I think we can do this for v1.68.2

Hi @mattleibow ,
Thank you for your update.
Can you please share me the expected release timeline for this SkiaSharp support in ARM64 architecture?
Regards,
Vijayasurya A

Things are a bit flexible, but we are aiming for the first previews in March/April. At this time, there are bits that are working, but unfortunately in our work, we removed a whole bunch of types and members to get it to compile. I am right now working to make sure that the API is backwards compatible. This is taking a bit of time as certain things will have to be reworked internally.
A rough estimate is that we will have previews sometime in March.

Hi @mattleibow,
Can you please share with me the expected release timeline for this SkiaSharp support in ARM64 architecture?
Regards,
Manikandan R

I forgot to update this issue with the numbers 😢 The alphas are out on the preview feed: https://aka.ms/skiasharp-eap/index.json
Check out the v2.80.x versions, but the most recent is v2.80.0-alpha.8.
This should have ARM64 for UWP.

Thanks for the updates. When will be the package available in NuGet.org? Any timeline?

Merged and on nuget.org.


Song does not get updated

Describe the bug
Looks like the app does not update automatically when I stop and play another song. Even tho on last.fm it shows "scrobbling now", the app output in debug mode shows:
TRAC[0106] No new scrobble detected.                                                                                TRAC[0106] Cycle complete.                                                                                TRAC[0107] Cycle begin.                                                                                TRAC[0107] No new scrobble detected.                                                                                TRAC[0107] Cycle complete.                                                                                TRAC[0108] Cycle begin.                                                                                TRAC[0108] No new scrobble detected.                                                                                TRAC[0108] Cycle complete.                                                                                TRAC[0110] Cycle begin.                                                                                TRAC[0110] No new scrobble detected.                                                                                TRAC[0110] Cycle complete.                                                                                TRAC[0111] Cycle begin.                                                                                TRAC[0111] No new scrobble detected.                                                                                TRAC[0111] Cycle complete.                                                                                TRAC[0112] Cycle begin.                                                                                TRAC[0112] No new scrobble detected.                                                                                TRAC[0112] Cycle complete.                                                                                TRAC[0113] Cycle begin.                                                                                TRAC[0113] No new scrobble detected.                                                                                TRAC[0113] Cycle complete.

OS: Windows 10

Thanks for reporting. I'm looking into this issue but I can't seem to reproduce it on my end (both on Windows/Linux).
If you'd like, I can take a look and try replicating it with your last.fm username.

My lastfm username is "awroby".
This is how I'm executing: lfm-cli-windows-amd64.master.exe -u awroby -r 1.

Quick example:

Thanks for the information.
I've tried running in my my end and it seems to work:

Which version of lfm-cli are you using? The version I'm currently on is v1.20

C:\Users\user\Downloads>lfm-cli-windows-amd64.master.exe -v
lfm-cli version v1.2.2

I'll try the v.1.2.0 version and update you here.

Eh weird, same behaviour.

execute
play something on soundcloud

No idea what could cause this :|

Interesting... I'll investigate the issue when I get back home on my PC. I'm thinking it could be a platform issue for now.
The program scrapes data directly from your last.fm profile page in order to retrieve the "Scrobbling Now" item. It's weird that it shows on the web page but not on the application.
For now though, I would say try sticking to the default refresh rate of 10 seconds just to not get rate-limited by last.fm.
Let me know if anything changes

Just tested on Windows, v1.2.2 and v1.2.0 seems to be working just fine.

I'm not exactly sure what could be causing this problem on your end.

Was this a problem that occurred in the past/resolved itself? Or just now, out of the blue?
Try scrobbling using last.fm's native web scrobbler (pressing play any track with a YouTube/Spotify linked should activate the web scrobbler). I want to rule out the possibility that this is an issue with the scrobbler client.


ROS2 Humble: Failed to build

Hi,
I'm using Ubuntu 22.04 and ROS2 Humble. I'm following the steps below but can't build the humble branch:
git clone https://github.com/Fields2Cover/Fields2Cover.git
git clone https://github.com/open-navigation/opennav_coverage.git -b humble
colcon build --packages-select opennav_coverage opennav_coverage_demo opennav_coverage_msgs fields2cover

ros2 launch opennav_coverage_demo coverage_demo_launch.py

When I build the packages as above, I'm getting lots of error. The last part of the error is something like this:
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:90: CMakeFiles/opennav_coverage_core.dir/src/headland_generator.cpp.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:118: CMakeFiles/opennav_coverage_core.dir/src/route_generator.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:104: CMakeFiles/opennav_coverage_core.dir/src/swath_generator.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:146: CMakeFiles/opennav_coverage_core.dir/src/visualizer.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:132: CMakeFiles/opennav_coverage_core.dir/src/path_generator.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:76: CMakeFiles/opennav_coverage_core.dir/src/coverage_server.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:188: CMakeFiles/opennav_coverage_core.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< opennav_coverage [13.1s, exited with code 2]

Summary: 2 packages finished [1min 8s]
  1 package failed: opennav_coverage
  2 packages had stderr output: fields2cover opennav_coverage
  1 package not processed

Error Message (whole message):

Thanks for your time !

I replaced fields2cover package to v1.2.0 which is in this link: https://github.com/Fields2Cover/Fields2Cover/releases/tag/v1.2.0
but interestingly still getting same error:
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:90: CMakeFiles/opennav_coverage_core.dir/src/headland_generator.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:132: CMakeFiles/opennav_coverage_core.dir/src/path_generator.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:76: CMakeFiles/opennav_coverage_core.dir/src/coverage_server.cpp.o] Error 1
gmake[2]: *** [CMakeFiles/opennav_coverage_core.dir/build.make:146: CMakeFiles/opennav_coverage_core.dir/src/visualizer.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:188: CMakeFiles/opennav_coverage_core.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< opennav_coverage [16.1s, exited with code 2]
Aborted  <<< Fields2Cover [1min 5s]

Summary: 1 package finished [1min 5s]
  1 package failed: opennav_coverage
  1 package aborted: Fields2Cover
  2 packages had stderr output: Fields2Cover opennav_coverage
  1 package not processed

Error Message (whole message):

Hi @grboguz21 ,
I faced the same issue and you need v1.2.1.

I tried your method but unfortunately getting the almost same error message..
In order to help to find stabil installation process at least Humble users, I want to share my whole steps:
First of all, I created folders listed below:
cd ~
mkdir open_navigation_ws
mkdir open_navigation_ws/src
cd open_navigation_ws/src

and after that I downloaded packages using a bunch of commands below:
git clone https://github.com/Fields2Cover/Fields2Cover.git -b v1.2.1
git clone https://github.com/open-navigation/opennav_coverage.git -b humble

Finally, I got back to the main project folder and build the workspace:
cd ~/open_navigation_ws
colcon build --packages-select opennav_coverage opennav_coverage_demo opennav_coverage_msgs fields2cover

After building that, getting errors related to swath_generator.cpp and coverage_server.cpp:

Something interestingly was getting wrong.

Hi @grboguz21 ,
After cloning F2C v1.2.1, shouldn't you build and install that library first? I follow the guideline in F2C repo.

After that, "colcon build" opennav_coverage source

First of all, thank you for your time.
I missed the point that install building and installing library.
As you said, I deleted all files related directories in /usr or /opt.
After that, I got back to the main folder of Fields2Cover package which is ~/open_navigation_ws/src/Fields2Cover.
In this directory, I ran these commands:
mkdir -p build;
cd build;
cmake -DCMAKE_BUILD_TYPE=Release ..;
make -j$(nproc);
sudo make install;

After that, I wanted to test this library in Python first. In order to do that, I ran these commands below:

Everything was fine so far. As you see library is successfully installed:

But when I try to build with colcon it failed:

I would like to thank to everyone for helping me.
I tried your steps @emusman-lab and attached the log message below as .txt file.
output.txt
and also screenshot of the error message:

I finally solved it !
Your kind support save my life @emusman-lab, I would like to special thank to you.

Now, I'm going to create a clear installation process of your awesome package for ROS2 Humble users and share here @SteveMacenski if you are considering using it for people looking for a solution.
I hope this will be helpful for everyone who are interested in this package.

I have the same error on iron,
here are the steps I used
`
source /opt/ros/iron/setup.bash
cd ~
mkdir open_navigation_ws
mkdir open_navigation_ws/src
cd open_navigation_ws/src
git clone https://github.com/Fields2Cover/Fields2Cover.git -b v1.2.1
git clone https://github.com/open-navigation/opennav_coverage.git -b iron
cd ~/open_navigation_ws/src/Fields2Cover
git checkout tags/v1.2.1
mkdir -p build;
cd build; cmake -DCMAKE_BUILD_TYPE=Release ..;
make -j$(nproc);
sudo make install;
source /opt/ros/iron/setup.bash
cd ~/open_navigation_ws/src/Fields2Cover
colcon build --symlink-install
cd ~/open_navigation_ws/src/opennav_coverage/
colcon build --symlink-install
source install/setup.bash
ros2 launch opennav_coverage_demo coverage_demo_launch.py
`

Nevermind, I fixed it by removing anything related to fields2cover from my pc before reinstalling

Closing, since this ticket covers that need to update the instructions since F2C v2.0 is API breaking, but thanks for the thread folks! https://github.com/open-navigation/opennav_coverage/issues/56

I cloned F2C , version 2.0, built it, tried to build opennav_coverage with no luck. I was happy to find this thread, so I deleted F2C, erased all related folders in /usr and cloned V1.2, built it, then while building opennav_coverage, I got the following error
--- stderr: opennav_coverage                                      /usr/bin/ld: CMakeFiles/test_viz.dir/test_viz.cpp.o: undefined reference to symbol '_ZNK11OGRGeometry11exportToWktEPPc13OGRwkbVariant' /usr/bin/ld: /lib/libgdal.so.30: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status


Popout group flow error

          This is half-fixed as of 2.1.1 -

When a panel or group goes from grid -> popout -> floating, Dockview used to crash. Now, dockview creates the floating group as expected. Nice!
But when a panel or group goes from floating -> popout -> floating, Dockview used to make a (bugged) empty floating group. Now Dockview throws an error, and the panel is closed.
Video attached. I can move this to a new issue if you'd prefer!
https://github.com/user-attachments/assets/7799d295-b19f-4ced-ae05-9408c9a6e2fd
Originally posted by @zaxer2 in https://github.com/mathuo/dockview/issues/782#issuecomment-2557720596

@zaxer2 This should be fixed in 2.1.2. Please do let me know if that works for you


Shows same highlights or notes multiple times

When I click on sync from the obsidion sidebar, sometimes same highlights gets fetched multiple times.

you can add it in your template hightlight
{% if is_new_article %}
xxxx
{% endif %}


Update client name in prober

Use "options.clientName" as part of the prober title, so prober statsd of different clients do not collide with each other.

noice. lgtm.

Suggested change: major version

Also make a new major upstream in sirvice as well. And add to the sirvice MIGRATION.md document

I agree with you. This update might break some dashboards.  I am changing the version.


Make hashtags in Twitter link work

Change URL parameter from hastags to  hashtags.

Thanks @yaph
Merging it right away!


fix: esm types

Summary & motivation
This PR addresses https://github.com/stripe/stripe-js/issues/543 and https://github.com/stripe/stripe-js/issues/545.
It fixes the missing types for subpath exports while supporting the legacy pattern.
Testing & documentation
I tested it with the existing npm script yarn test.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

You actually want to switch to an object under each one with types and default fields.
Like this: https://publint.dev/<EMAIL_ADDRESS>


Fixing spurious diff related to healthcheck timeout

Note, this also starts a pattern of tests related to roundtripping
a deployment
into a request/deploy pair
to JSON
back into request/deploy
into a deployment
and comparing to the original.
Failures in this test are cases where we'll get into a redeploy cycle.
New cycles should be put into this pattern, so that we can ward off regressions.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger


remove mouse_exited() and mouse_entered()

it caused an error in debugger and it was too annoying because the sound can easily be spammed.

Really nice fix for the noice spam when hovering over the start game button!


Document CLI

Hi,
thanks for the library – I was looking for this. I can't find any documentation for it though – have I missed something?

Added documentation to readme.


Details drawer

feat: Add DetailsDrawer for showing device position details
Adds a new component, DetailsDrawer, which displays position details for a selected device. This drawer can be opened from the StatusCard component, providing additional contextual information about the device's state. Users can view attributes for the selected device. The addition of the DetailsDrawer enhances the user experience by offering a convenient way to explore and analyze position data.  When enabled in the preferences, show DetailsDrawer, when is disabled redirect to normal route.

feat: Add Quick Details Button in StatusCard component
This commit introduces a new feature to the StatusCard component by adding a Quick Details button. When enabled in the preferences, the button appears below the table in the card. Clicking on the button triggers the onDetailsClick function and displays additional information. This enhancement provides users with a convenient way to quickly access more details about the device.

Were there any feature requests for this? I'm not sure I understand the value over what's already available.

I think there is no request for this.
The value is that by opening it in a drawer it is easier and faster to see the details of the different devices.
https://github.com/traccar/traccar-web/assets/12776890/0036ef6a-792f-48e9-81e7-df93f3d42c7f
The features are option, so you can enable or disables from preferences.
https://github.com/traccar/traccar-web/assets/12776890/4281c26a-e18e-47fc-97f3-fcf5d14330e4

I think we need to wait and see if there's an interest for it. This basically duplicates existing functionality.

I really like this change. It allows to do/see most stuff from the main page without leaving it

I find it a very interesting function, especially to be able to see the map and a status panel at the same time as in the legacy version.
Something that I think would add a lot is that every time the device changes position it is updated in this new panel.

I suggest replacing this version proposed here with the existing one.


System-Access-Tester: Encoding issue from Microsoft NPS server

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Executing the tester with "Synchronize groups" ticked on shows the groups coming from the authenticating server.
Umlauts are displayed incorrectly...
To Reproduce
Steps to reproduce the behavior:

Add Microsoft NPS service as Radius server and tick "Synchronize groups" in System-Access-Servers
Execute System-Access-Tester and log on
Check for Umlauts
See Mojibake

Expected behavior
Umlauts should be displayed properly...
Screenshots

Relevant log files
None.
Additional context
None.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.7.3-amd64
FreeBSD 13.2-RELEASE-p2
OpenSSL 1.1.1v 1 Aug 2023

It would help to paste it here. Likely because MS doesn't return UTF-8... it's difficult to guess the encoding because it's tied to a localization.

Probably related...
https://github.com/dapphp/radius/issues/5

Äääääh, something seems really borked here on my test system...


feat: finish msg inclusion api

finishes the api for message inclusion
blocked by #680
part of #382
closes #381

Codecov Report

Merging #681 (d092cfc) into main (feebea0) will increase coverage by 1.44%.
The diff coverage is 82.14%.

@@            Coverage Diff             @@
##             main     #681      +/-   ##
==========================================
+ Coverage   39.28%   40.73%   +1.44%
==========================================
  Files          27       29       +2
  Lines        2795     2897     +102
==========================================
+ Hits         1098     1180      +82
- Misses       1609     1628      +19
- Partials       88       89       +1

Impacted Files
Coverage Δ

pkg/inclusion/get_commit.go
0.00% <0.00%> (ø)

pkg/shares/non_interactive_defaults.go
94.82% <94.82%> (ø)

pkg/inclusion/nmt_caching.go
80.00% <100.00%> (ø)

pkg/inclusion/paths.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


argmax tests are disabled

SecureNN argmax tests are disabled because they fail to run on circleci because of memory issues. This can be resolved by figuring a way to upgrade circleci or figuring out if there is an underlying problem with the argmax tests causing them to run out of memory.

They now run for int64, maybe that's good enough for now..?

We aren't running int64 tests as of now! https://github.com/mortendahl/tf-encrypted/issues/320

Closing this issue as it'll be fixed with #320


Added spriral matrix problem in DSA

The Spiral Matrix problem is an intriguing exercise in data structure and algorithm design. The goal is to fill an [n x n] matrix in a spiral order, starting from the top-left corner and continuing in a clockwise direction until the entire matrix is filled. This requires careful manipulation of row and column indices, and keen attention to boundary conditions, as the indices must be adjusted after completing each side of the spiral.
The typical approach involves maintaining four boundaries—top, bottom, left, and right. You traverse the matrix in four steps: from left to right, top to bottom, right to left, and bottom to top, progressively tightening these boundaries to avoid re-processing cells. This process continues until all elements are covered.
Implementing the Spiral Matrix problem reinforces concepts of matrix traversal, boundary management, and iterative logic, making it a staple example in algorithm studies. It’s often used in coding interviews to assess a candidate’s problem-solving and implementation skills. Familiarity with this problem equips one with a solid grasp of handling two-dimensional arrays and improving spatial reasoning abilities

Thank you so much [@strivedi4u] for merging my changes in your repo.
Please assign me a label -> gssoc-extd
Kindly Requested...


About Dataset format

Hello, I have successfully reproduced your work. This is a very nice work.
However, I have a question about the format of demoniac image in the released PASCAL_RAW dataset.
Specifically, I use cv2.imread(img_path, -1) to read the images inPASCAL_RAW/original/demosaic, PASCAL_RAW/original/demosaic_low, and PASCAL_RAW/original/demosaic_oe. The shape of demosaic_low images are 600x400x3, and the shape of demosaic and demoniac_oe are all 600x400x4.

The demoniac_oe and demosaic images seem to be stored in RGBA format. I want to know what is the reason for this difference?
Thank you for your help !

Additionally, if you could make the Default ISP data public, it would be greatly helpful for me.

Hello, sincerely thanks for your interests to our work !
Just regarding less of the final channel is OK,(400,600,3) is fine.
For the original PASCAL RAW dataset, please refer to
https://purl.stanford.edu/hq050zr7488
and download from here.


feat(ingest): emit state payloads as soft-deleted

This way, they don't show up in search. It seems to work with stateful ingestion as expected.
Slack ref: https://datahubspace.slack.com/archives/CUMUWQU66/p1680097899146059?thread_ts=1664448878.351199&cid=CUMUWQU66
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@hsheth2 The test need update
FAILED tests/unit/stateful_ingestion/provider/test_datahub_ingestion_checkpointing_provider.py::TestDatahubIngestionCheckpointProvider::test_provider - AssertionError: 'status' != 'datahubIngestionCheckpoint'
- status
+ datahubIngestionCheckpoint
= 1 failed, 824 passed, 4 skipped, 127 deselected, 63 warnings in 248.60s (0:04:08) =


cloudup: fromPort/toPort on securityGroupIngress is ambiguous

It means port range, but it is easy to confuse with source & destination ports.

It is ambiguous, but the EC2 API uses the same name (and therefore Terraform does as well).  We also can in theory change this in future - it is the fi contract, not the cluster contract.
Closing as "won't fix"


React and Preact in same Storybook instance

I need to introduce Storybook for both React and Preact components. Is there a way to have the same Storybook instance for both React and Preact components? If not is it a feature we can expect in future?

It's not possible right now, but there was a discussion to support that in the future, though it requires a major refactoring of the rendering ability.
Anyway, we have it in https://storybook.canny.io/roadmap, so closing it.


Auto extended Voronoi does not work with time x Scale

I tried to use the newly auto extended version of the Voronoi with a time x axis scale, but this does not work and produces the following error:
react-dom.development.js:2912 Error:  attribute d: Expected number, "ML1533807610677.4…".
Is there a good way to fix this?

There isn't really a good way. As a work around you could flip your data into linear coordinates by converting it all the epoch time. I'll take a look soon to see what I can do.

I overcame this by grabbing the width and height onComponentMount and applying these. Would be great to add a flag to enable time axis for it.


Kubelet --cloud-provider tag is not Supported on GCE with the CNI Plugin

When kubelet has the Cloud Provider Tag set on GCE and the CNI Plugin is being used the kube-controller-manager RouteController attempts to create routes, instead of delegating the responsibility to the CNI network plugin, making nodes unavailable for scheduling.
bash-4.3# kubectl describe pods kube-dns-v20-mzrgb --namespace=kube-system
Name:		kube-dns-v20-mzrgb
Namespace:	kube-system
Node:		/
Labels:		k8s-app=kube-dns
		version=v20
Status:		Pending
Tolerations:	CriticalAddonsOnly=:Exists
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath	Type		Reason			Message
  ---------	--------	-----	----			-------------	--------	------			-------
  50s		19s		7	{default-scheduler }			Warning		FailedScheduling	no nodes available to schedule pods

Looks like this is the related issue on Kubernetes https://github.com/kubernetes/kubernetes/issues/44254

Looks like this is a unmerged fix https://github.com/kubernetes/kubernetes/pull/33573/files
@hh might be worth integrating this into our builds, but lets not worry about it yet.

Have switched to using kubenet to provide networking until this is fixed so we can use --cloud-provider=gce
--network-plugin=kubenet \
--pod-cidr=${ pod_cidr } \
--non-masquerade-cidr=${ cidr } \

bash-4.3# kubectl get pods --namespace=kube-system
NAME                                                          READY     STATUS    RESTARTS   AGE
kube-apiserver-test-master1.c.test-163823.internal            1/1       Running   0          12m
kube-apiserver-test-master2.c.test-163823.internal            1/1       Running   0          12m
kube-apiserver-test-master3.c.test-163823.internal            1/1       Running   0          12m
kube-controller-manager-test-master1.c.test-163823.internal   1/1       Running   0          12m
kube-controller-manager-test-master2.c.test-163823.internal   1/1       Running   0          12m
kube-controller-manager-test-master3.c.test-163823.internal   1/1       Running   0          12m
kube-dns-v20-nksj1                                                            3/3       Running   0          11m
kube-proxy-test-master1.c.test-163823.internal                1/1       Running   0          12m
kube-proxy-test-master2.c.test-163823.internal                1/1       Running   0          12m
kube-proxy-test-master3.c.test-163823.internal                1/1       Running   0          11m
kube-scheduler-test-master1.c.test-163823.internal            1/1       Running   1          12m
kube-scheduler-test-master2.c.test-163823.internal            1/1       Running   0          11m
kube-scheduler-test-master3.c.test-163823.internal            1/1       Running   0          11m

Temporary work around for now is not to use the cloud-provider flag
bash-4.3# kubectl get nodes
NAME                                  STATUS                     AGE
test-master1.c.test-163823.internal   Ready,SchedulingDisabled   15s
test-master2.c.test-163823.internal   Ready,SchedulingDisabled   13s
test-worker1.c.test-163823.internal   Ready                      16s
test-worker2.c.test-163823.internal   Ready                      16s
test-worker3.c.test-163823.internal   Ready                      10s
bash-4.3# kubectl create -f ../kube-dns.yml
service "kube-dns" created
replicationcontroller "kube-dns-v20" created
bash-4.3# kubectl get nodes
NAME                                  STATUS                     AGE
test-master1.c.test-163823.internal   Ready,SchedulingDisabled   29s
test-master2.c.test-163823.internal   Ready,SchedulingDisabled   27s
test-master3.c.test-163823.internal   Ready,SchedulingDisabled   12s
test-worker1.c.test-163823.internal   Ready                      30s
test-worker2.c.test-163823.internal   Ready                      30s
test-worker3.c.test-163823.internal   Ready                      24s
bash-4.3# kubectl get pods --namespace=kube-system
NAME                                                          READY     STATUS    RESTARTS   AGE
kube-apiserver-test-master1.c.test-163823.internal            1/1       Running   0          40s
kube-apiserver-test-master2.c.test-163823.internal            1/1       Running   0          39s
kube-apiserver-test-master3.c.test-163823.internal            1/1       Running   0          30s
kube-controller-manager-test-master1.c.test-163823.internal   1/1       Running   0          40s
kube-dns-v20-w1b9j                                            3/3       Running   0          15s
kube-proxy-test-master2.c.test-163823.internal                1/1       Running   0          39s
kube-proxy-test-worker1.c.test-163823.internal                1/1       Running   0          39s
kube-scheduler-test-master3.c.test-163823.internal            1/1       Running   0          30s

Fixed in 127b57fee87b7799bb841f754fd32541dfefc25d


make registration error a steady state

If a host fails registration with the same error message a second
time, that means we have reconciled it twice with the same data and it
still does not work. Rather than keep trying, which toggles the host
between "registering" and "registration error" indefinitely, leave the
host in the "registration error" state.

The test failure was a transient travis issue. This is working now.


Upgrade from PackageLicenseUrl to PackageLicenseExpression

The existing property is now considered legacy and results in a build warning:
##[warning]C:\Program Files\dotnet\sdk\3.0.100\Sdks\NuGet.Build.Tasks.Pack\buildCrossTargeting\NuGet.Build.Tasks.Pack.targets(198,5): Warning NU5125: The 'licenseUrl' element will be deprecated. Consider using the 'license' element instead.

I don't having that warning...


No confirmation pop-up when deleting SAML2 or OAuth2 configuration from the service provider UI

There are no confirmation pop-ups for delete buttons under SAML2 or OAuth2 configurations in SP UI.
Similar validation required for Revoke & Regenerate options under OAuth2 configuration.

Reducing the severity as this is a request for improvement.

Duplicate of https://github.com/wso2/product-is/issues/1975


Revert "Rails 4.1 support"

Reverts e-accent/local_mail#1

Not so trivial. reverting because it will break rails 3.2 support, which is still needed for master branch...


[AutoPR peering/resource-manager] Fix readme.python.md for Peering

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7338

(message created by the CI based on PR content)

no action until Azure/azure-rest-api-specs#7338 is merged


Cannot sign runtime app file generated from 14.X versions

After generating a runtime app file from a 14.X version in a docker container, I am unable to digitally sign the generated runtime app. This has been observed for on prem versions 14.0.29537.0-na and 14.1.32615.0-na. When attempting to sign the runtime app file in either the docker container or locally using SignTool I get the error, "SignTool Error: This file format cannot be signed because it is not recognized."
It should be noted that the non-runtime app file can be signed.
To Reproduce

Create a new docker container running a BC 14.X version.
Publish a .app file to NAV in the container.
Generate the runtime app file in the container.
Attempt to sign the generated runtime app file.

Expected behavior
Runtime app files can be digitally signed.
Versions:
BC on prem
14.0.29537.0-na
14.1.32615.0-na

@thpeder Is there a workaround until this ships? What update will this be fixed in? What was the issue that caused this?

To answer your questions in order.

No there is no workaround. You simply can't sign runtime packages and publish a signed runtime package. The only option is to not sign them.
14.6, I don't know when that will be released.
We changed runtime packages so you can't just open them with an archiving program, in doing that we broke the format the signing library worked with, so we needed to find another fix to still maintain both properties.

The fix is in our docker images from build 36036, so please have a try with that and tell us if you run into some other issue with it, Thanks.

Thank you for the clarification!


Fix wrong duration calculation for asynchronous calls

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
fixes #X, partially #Y, mentioned in #Z

Documentation
if this is a new feature, link to pull request in https://github.com/php-http/documentation that adds relevant documentation

License
MIT

What's in this PR?
When using asnyc request, duration is always 0
This fixes that
Why?
Currenly for async request we don't see any duration.

First query is synchronous, the other 2 are asynchronous, and are slow. This fixes that

Now we can see the duration of asynchronous calls as well
Checklist

[ ] Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix
[ ] Documentation pull request created (if not simply a bugfix)

released as https://github.com/php-http/HttplugBundle/releases/tag/1.13.1


Demo broken?

Demo seems to be broken. In the console I get a  ReferenceError: ole is not defined error.
Error occurs at
// ole.geops.de:73:11
var editor = new ole.Editor(map);

Same here on FF 59.0.2, works on Chrome though.

Forgot to mention it... @dchatry is right: Doesn't work on FF 60 (Beta), but works on Chromium.

@lb1c Linked to this issue: https://github.com/mozilla-neutrino/neutrino-dev/issues/638
Did not fixed it yet though.

Works fine, thanks!


FIX Handle updated serialize methods in silverstripe/mfa

Issue https://github.com/silverstripe/silverstripe-webauthn-authenticator/issues/110
https://github.com/silverstripe/silverstripe-mfa/commit/eb8d813f0dc77682293ba5d99c181b7d3cbf902c added new __serlialize/__unserialize methods for PHP 8.1 compatibility.  They better handle the whole serialization process, though it also means the actually PHP objects are hydrated rather than just json data.

Seems a bit weird that there's no unit test to update here. Aren't those protected method not tested any way ... either directly or indirectly?

They are not tested


@eessex => Minor channel page updates

Fixes a couple padding issues and adds /artsy-partner-updates to the responsive pages

:tada:


Support for Swift Package Manager?

Currently there is no information about PostHog using SPM?
Are there plans updating project for adding this functionality?

We should support this (see the Package.swift file and this PR: https://github.com/PostHog/posthog-ios/pull/10). Unfortunately we don't have anyone with a lot of experience in iOS development, so we might be missing something.
Please feel free to open a pull request or an issue with exact steps that we still need to do to add this support. :)

I'd add that we're about to start hiring for a mobile developer too :)

We should support this (see the Package.swift file and this PR: #10). Unfortunately we don't have anyone with a lot of experience in iOS development, so we might be missing something.
Please feel free to open a pull request or an issue with exact steps that we still need to do to add this support. :)

I will open new issue with detail explanation of the problem I am running into. Thank you!

This is fixed in the 1.4 version and can be closed. @jamesefhawkins @mariusandra