order expenses by date desc

Coverage decreased (-0.02%) to 77.75% when pulling 88af98e8173185181104207c985403faadd2c169 on webpackFixes into f3d8106d556f2cf697d0a8a76c035c36d5e2b567 on master.


Support for Relation Mapping to Model Object / Data Model Object

Thanks for such wonderful library for swift in a short time.
As we have seen mapping between JSON data to Data Model Object in RestKit & JSONModel, I couldn't find such feature in SwiftyJSON. Using SwiftyJSON, it is a time consuming task to parse JSON. It will be better if there is any such mapping feature.
Thanks again.

+1000000000
Will there be any support to mapping ?

It will be better if you add it.

This issue has been inactive for a while so I'm gonna go ahead and consider it fixed. Please let us know if you want to reopen it.


strange behaviours

I updated the app to the latest version available at https://lab.flipper.net/apps/upython excited at the idea of being able to use an interactive shell.
but I have encountered two strange behaviours:
One, non fatal, happens when upython is launched  and Flipper already has a /dev/ttyACM0 connected and used by a terminal client; App and device crashing immediately (reporting "bus fail").
Another, very strange and makes feature unusable is: how to confirm and execute an interactive command? return key won't work inside py shell. I've tried  with "screen" and "putty" terminal client without success

Does it say "bus fail" or "bus fault" ? For me, sounds quite familiar to this issue here: flipperdevices/flipperzero-firmware#3927

"bus fault", sorry
and happens only if also the flipper is connected with flipper android app through bluetooth

* Change screen or PuTTY to send different line endings: `\r\n`

* Try https://github.com/ofabel/fssdk with `fssdk cli`

Also I can get around this by using CTRL+J

I've updated to 1.5 today
Now I'm unable to start flawlessly the app, I get a BusFault every try too start
Also without smartphone not connected, also with BT disabled
I think you can run the app, what is your configuration?
What can I do to debug this crash?

The goal of the app is run script without an external device
However, how do I stop background tasks?
Il mer 16 ott 2024, 14:41 Oliver Fabel @.***> ha
scritto:

@muziofg https://github.com/muziofg yes, it seems that the application
became a bit more unstable 😢
But the core developers are working on this issue, see
flipperdevices/flipper-application-catalog#522
https://github.com/flipperdevices/flipper-application-catalog/pull/522
for details.
I usually start the application over the serial CLI, but same here -
success rate is about 80%. I also shutdown any background tasks (like
Bluetooth or Subghz) to have as much RAM space as possible.
—
Reply to this email directly, view it on GitHub
https://github.com/ofabel/mp-flipper/issues/3#issuecomment-2416733148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFPCHBFDL5BJGT2T6FWVTLZ3ZNGZAVCNFSM6AAAAABPMX5B32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWG4ZTGMJUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

magically, after upgrade to the next stable v1.1.2 this flipper application works, also works with bluetooth enabled

Version 1.6 crashes again when app is connected via BT
Hope the fix (not merged yet) solves the issue
https://github.com/flipperdevices/flipperzero-firmware/pull/3992


Java indexer: make file URL construction more resilient [phab:D2094]

Created by schroederc at 2017-12-11 20:48:43:

ronshapiro accepted this revision at 2017-12-11 20:51:52

ronshapiro wrote at 2017-12-11 20:51:53:
LGTM

schroederc closed via commit 99da13983a049fc57e67426be73545b1d96e682f at 2017-12-11 20:57:09


Api: allow customize access log retention

For example, setting access log retention. Allow passing in log group properties to the accessLog param.
Requests:

https://serverless-stack.slack.com/archives/C01JG3B20RY/p1632604722467800

I'm not sure if this is the right place to suggest this, but it would be nice if you could set a default for all of the functions.  Having to set it for each one when you might want them all the same would make it too easy for mistakes to slip in.  A new property on defaultFunctionProps might work really nicely?

Proposed specs :

[ ] Research : Alex Debrie's reference post about API Gateway logs.
[ ] Research : How to verify log configuration in synthesized stack.
[ ] Research : How SST currently handles API Gateway logs and/or log groups.
[ ] Research : Alternatives and best way to expose access log configuration in SST.
[ ] Implement : Basic (custom format) Api (HTTP API) access logs.
[ ] Implement : [optional] Other Api access log formats (?)
[ ] Test : Api with and without access Logs (custom format)


⚠ Samsung has degraded performance

In fd47426, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2596 ms

Resolved: Samsung performance has improved in 9dc7250.


Exquisite Bug in WiFi LWIP layer being IRRESPONSIVE release/v5.2 ESP32 commit f81b598d1024175db6d5e75e4acdba9131c617d6 (IDFGH-13071)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Description:
We have discovered a critical bug in the LWIP/WIFI layer on the ESP32 in SDK commit f81b598d1024175db6d5e75e4acdba9131c617d6 (HEAD -> release/v5.2, origin/release/v5.2) on ESP32. This issue may be present in other versions as well.
Symptoms:
The WiFi on the ESP32 device is connected to the WiFi router, but the LWIP layer stops responding to any requests or sending data.
WebSocket connections simply time out.
Ping requests from external sources stop receiving responses.
When the WiFi router is turned off and then back on, the device reconnects to WiFi (the handler is called successfully), but remains unresponsive at the IP level on LWIP.
Workaround:
The issue can be temporarily resolved by destroying and rebuilding the network interface for the Wi-Fi station and LWIP layer using the following code:
// Destroy the network interface for the Wi-Fi station and Netif if already created, then rebuild it.
    if (sta_netif != NULL) {
        // Unregister event handlers
        ret = esp_event_handler_unregister(IP_EVENT, IP_EVENT_STA_GOT_IP, &event_handler);
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to unregister IP_EVENT handler: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }
        ret = esp_event_handler_unregister(WIFI_EVENT, ESP_EVENT_ANY_ID, &event_handler);
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to unregister WIFI_EVENT handler: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        // Stop Wi-Fi
        ret = esp_wifi_stop();
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to stop Wi-Fi: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        // Deinitialize the Wi-Fi driver
        ret = esp_wifi_deinit();
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to deinitialize Wi-Fi: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        // Clear Driver and Handlers of the Wi-Fi
        ret = esp_wifi_clear_default_wifi_driver_and_handlers(sta_netif);
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to clear Wi-Fi driver and handlers: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        // Destroy the Wi-Fi station network interface
        esp_netif_destroy(sta_netif);
        sta_netif = NULL;

        // Delete the default event loop
        ret = esp_event_loop_delete_default();
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to delete default event loop: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        // Destroy the event group
        if (s_wifi_event_group != NULL) {
            vEventGroupDelete(s_wifi_event_group);
            s_wifi_event_group = NULL;
        }

        // Deinitialize the network interface layer
        ret = esp_netif_deinit();
        if (ret != ESP_OK) {
            printf("Error in %s at line %d: Failed to deinitialize network interface: %s\n", __FILE__, __LINE__, esp_err_to_name(ret));
        }

        reconnect_wifi = 1;
    }

By destroying and reconstructing the LWIP and WIFI layer, the system returns to normal operation.
Unresolved Issues:
There is still an underlying issue causing this behavior, which has yet to be identified. Further investigation is needed to pinpoint the root cause of the problem.

The WiFi on the ESP32 device is connected to the WiFi router, but the LWIP layer stops responding to any requests or sending data.

Could you please share more details about this state? How can we replicate this condition? Could you please create a simple example that could be used to reproduce this issue? And maybe share more info about your local environment (e.g. type/make of your WiFi router...)

@filzek Any feedback for commit https://github.com/espressif/esp-idf/issues/14016#issuecomment-2219832946 ?
BTW, from your report, you did destroy and reconstruct the LWIP and WIFI layer to make the system returns to normal operation. How do you detect if this issue is happened? (Or you just always destroy the network interface and create it again?)

@AxelLin we cannot create a simple example to reproduce, but the wifi become irresponsive any packet will not flow by the TCP stact, disable and enable the WiFi will not solve the problem, to solve the problem its is really necessary to destroy and recreate it all.
We detect it by doing 4 kind of survey a UDP multicast request, a simple ping to the router that was previously answered, a ping to the cloud ping server, a websocket connectivity action and a http external request, those actions measure if the TCP/IP layer stack are working or not, and by the WiFi side we use the tools avaliable in the SDK, so, if there is no answer in a trivial check it so go to destroy the network after a defined constant check retries.
So far that was the unique way to make devices responsive again.

@filzek
Just wondering if this issue happens on older IDF versions?
If it's a new issue in certain IDF version, maybe you can try git bisect to find the first bad commit.

Completele solved at commit c8c6fd141377b9a48b29c8ebb51fb7efadde0566 (HEAD -> release/v5.2, origin/release/v5.2)


Allow upload of external certificates.

Is your feature request related to a problem? Please describe.
We do get certificates from external sources which need to be used by some of our pods.
Describe the solution you'd like
A way of adding them to the cert-manager so the secrets are created and the certificates are managed in a consistent way along with the once that are created by the cert manager is needed.
Describe alternatives you've considered
"just" using secrets and mimicking the things that the cert manager does. This is not a nice option because then we lose the features that we deal with "just" certs and the in the background the secrets and so on are generated.
Additional context
none
Thanks for considering this in advance. Alternative options are welcome on how we could achieve this.

Hi,
Thanks for asking!
We do have certificates which were generated by our customers. We do have the private key and the certificate. Those we would like bring into our pods.
Mit freundlichen Grüßen / Best Regards
Andreas Fiseni

OSTHUS GmbH
Eisenbahnweg 9 – 11, Eingang TH 6
52068 Aachen, Germany
T    +49 241-94314-414
F    +49 241-94314-19
andreas.fiseni<EMAIL_ADDRESS>www.osthus.comhttp://www.osthus.com/
LinkedInhttps://www.linkedin.com/company/osthus          Twitterhttps://twitter.com/OSTHUS          Youtubehttps://www.youtube.com/user/OsthusCompany          Instagramhttps://www.instagram.com/osthus_careers/
Commercial establishment: 52068 Aachen
Registered at: Amtsgericht Aachen, HRB 6398
Managing Director: Dr. Torsten Osthus, Wolfgang Colsman, Andreas Mohr

The information contained in this email is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately
P Please consider the environment before printing this email.
From: James Munnelly<EMAIL_ADDRESS>Sent: Monday, January 27, 2020 16:00
To: jetstack/cert-manager<EMAIL_ADDRESS>Cc: Andreas Fiseni<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [jetstack/cert-manager] Allow upload of external certificates. (#2507)
"just" using secrets and mimicking the things that the cert manager does. This is not a nice option because then we lose the features that we deal with "just" certs and the in the background the secrets and so on are generated.
Could you elaborate on what parts of cert-manager you want to make use of in this kind of configuration? I can totally see why you might want to have secrets that are 'managed' in a 'read only' manner (i.e. alerting, notifications etc). But it'd be great to hear your own motivation for this.
/kind feature
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jetstack/cert-manager/issues/2507?email_source=notifications&email_token=AD5FLC5H7IIBM75LRHSPLYDQ73ZF3A5CNFSM4KEK5MY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ7Z35Y#issuecomment-578788855, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD5FLC366MDQVRPHZMB2PYDQ73ZF3ANCNFSM4KEK5MYQ.

You can manually create a Secret resource and 'mount' it into your pod if you already have the private key/certificate data - this does not require cert-manager: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
We don't currently have a passive 'monitor a secret but don't attempt to renew it' mode in cert-manager - I'd be keen to understand if/why this feature would be useful to you (in order to gather feedback & use cases!)

Using secrets to manage our external certificates could be an option. Thanks for sharing this.
The idea was, to have a unified way of handling certificates across our pods.
But I guess for this unification bigger changes in cert-manager would need to be done. So the only point I can make, is that it would be interesting to transparently (transparent from the pod's perspective) to exchange certificates. So in our deployment scripts we do not need to distinguish between "did we got this one from the customer, do we need to self sign it or do we use an internal CA".
This way, a deployment just refers to "an alias" and how the cert actually got there is not from interest. If we would use the "Secret resource" option, we would need to distinguish the different sources.
I am not sure, was I able to describe the use case to be understood?

Without some additional runtime component (such as an init container, sidecar container, or potentially cert-manager-csi), the only way to consume this sort of information from within a Pod is using Secret resources and mounting them in as files. It's not possible to simply reference a 'Certificate' and have that mounted in.

This way, a deployment just refers to "an alias" and how the cert actually got there is not from interest. If we would use the "Secret resource" option, we would need to distinguish the different sources.

Using the 'secret' approach is effectively the alias you are looking for. There doesn't need to be any relation between the Secret resource's name and the source of where it is from.
Aside from that though, regarding what cert-manager can do today for certificates that it does not issue - I'd still like to understand what features that you use today with cert-manager that you'd like to also use with certificates that are not issued by cert-manager - I'm not against it, but we should understand and agree upon the goals that we all have 😄

hi, i was specifically searching for this issue, we are also having some pods which uses client certs which we do not issue/generate.
As @munnerz asked, what i would like cert-manager to do is,
1 - take/upload those external certificates via some new CRD with kind 'ExternalCertificate'
(similar to current 'Certificate' Custom resource)
which do not have any IssuerRef pointing from it as we don't know who issued the cert.
2 - create a secret in a namespace we provide
3 - monitor them for expiry and notify
In summary,
basically perform crud ops on those external certs resource
- import  and create secrets from cert and private key
- update the same secrets if user manually updates the previously imported cert
- delete the secrets if user invoked deletion
- cert-manager just monitors for expiry and notify them if they forget to update before expiry of
currently imported certs
i m open for discussion, i'm a java dev having basic understanding of Golang,
i would very much like to help in implementing and contributing back to community even if we can not use it for our needs now.
i think it will be very helpful in future for people like me and @osthus-af  who wants to use in this way.

@daemon-thread  thank you for describing it in this way. @munnerz thats is exactly what I tried to explain, sorry for not making my point clear.

We also have such requirement.
I would be good to let cert manager help monitoring those BYO certificate and notifying when it was going to expire.

@munnerz if you need rationales, please read this. In other words: managing all certs statuses and metrics via Certificate it would be a great value.

@munnerz This feature would be really helpful especially to organizations/users who work in air-gapped environments, use self-signed certs and probably involve a manual approval process that the cert-manager's user doesn't have control over.  Also, it would be nice if we could have managed certificates and BYO certificates conceptually being the same kind of resource to share the same monitoring logic.


pnpm failed to install tsx

ENOENT  ENOENT: no such file or directory, copyfile '/Users/shuiluo/Library/pnpm/store/v3/files/35/760ee16f278b22518ce1ba0b25715f07b3fdfe4bfebc6e2002edd360f74932d6e4b24e9184bcaf3762f621f0accb1cc44c0b3752d6c254b8af213f71276359-exec' -><EMAIL_ADDRESS>Only this dependency is problematic
It is OK to install esbuild separately
pnpm 7.1.8
node 16

Closing as it doesn't sound like a tsx problem... tsx isn't even mentioned in the error
Maybe try it again, or in a separate project, or try clearing the pnpm store (~/Library/pnpm/store). If still problematic, ask in the pnpm repo.


CanCancel payment request (payment link)

We would like to be able to cancel payment link orders.  Some clients phone us and tell us that they do not understand the pay.shtml screen (mostly elderly) so they transfer the money directly ....
the problem is that we cannot manually set the order status to

paid
or cancelled and then reorder

problem: when we select cancel the reply is The order(s) cannot be canceled + the cancel button is missing
https://live.adyen.com/hpp/pay.shtml
shop payment ID for example; 800001435

please add the ability to cancel these orders

also as general feedback, maybe it would be smart to CSS upgrade the HPP / https://live.adyen.com/hpp/pay.shtml payment page. People do get lost here.

Hi Sean,

Yes that should be possible by using the pending status instead of the payment review status.
this page is totally customzible for our clients see our skin manual: https://docs.adyen.com/developers/hpp-manual#gettingstartedwithcustomisations

Regards,
Rik
Adyen
Regards,
Rik
Adyen

On 1) OK thanks. I assume this is in settings you mean?

OK. Maybe an idea to also 'per default' upgrade the CSS a little? (so
the default looks nicer too by default)

On Wed, Jun 22, 2016 at 11:20 AM, Rik ter Beek<EMAIL_ADDRESS>wrote:

Hi Sean,

Yes that should be possible by using the pending status instead of the
payment review status.
this page is totally customzible for our clients see our skin manual:
https://docs.adyen.com/developers/hpp-manual#gettingstartedwithcustomisations

Regards,
Rik
Adyen
Regards,
Rik
Adyen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Adyen/magento/issues/611#issuecomment-227688838, or mute
the thread
https://github.com/notifications/unsubscribe/AAn0a8SqIsLSg5d7u7nQN-xY_g40NkD7ks5qOP5IgaJpZM4I6pHY
.

Hi Sean,
You can now cancel an PayByMail order.
The default look and feel is in my opinion good enough as a default. We want to push our merchants to upgrade this with their own look and feel of their website instead of using our default skin.
Regards,
Rik

The default look and feel is in my opinion good enough as a default. We
want to push our merchants to upgrade this with their own look and feel of
their website instead of using our default skin.

.... do they really need pushing?
Have you seen the Mollie interface?
On Mon, Jun 27, 2016 at 10:49 AM, Rik ter Beek<EMAIL_ADDRESS>wrote:

Hi Sean,
You can now cancel an PayByMail order.
The default look and feel is in my opinion good enough as a default. We
want to push our merchants to upgrade this with their own look and feel of
their website instead of using our default skin.
Regards,
Rik
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Adyen/magento/issues/611#issuecomment-228687909, or mute
the thread
https://github.com/notifications/unsubscribe/AAn0a7lu5UpjFJLMZhGetSctw4kFObSqks5qP46RgaJpZM4I6pHY
.


Fix PID balancer and env rate logging

Checked that the test and coverage errors are due to the posix_ipc dependency, a temporary issue that will be fixed by a Vulp update.

Converting to draft until and waiting for said Vulp update.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.427%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
313

Relevant Lines:
328

💛  - Coveralls


Hessian-free optimization?

Just probing here a little bit to see if there was an interest for a Hessian-free optimizer, as e.g. in theano-hf by boulanni. Don't know the Keras code much yet, but I'd like to get some input if that's doable in a reasonable amount of time...

It would definitely be possible to add it as an Optimizer (see keras/optimizers.py).
It's not a priority, since HF has been shown to underperform RMSprop and Adagrad, while being more computationally intensive.

Oh OK, wasn't aware of that... can you point me to a paper etc. with some benchmarks etc?

Can't find any paper, but what I would recommend you do is simply to implement it in Keras (should be quick to adapt boulanni's code) and benchmark it (time and accuracy) against other optimizers. Then you can answer the question without having to rely on what I remember reading about.
The fact is, nobody uses Hessian-Free optimization. If there was any advantage to it, everybody would be using it.

Just a FYI to everybody seeing this: a paper by Sutskever et al discusses Heassian-free vs. momentum methods here:
http://machinelearning.wustl.edu/mlpapers/paper_files/icml2013_sutskever13.pdf
Quote: "Momentum-accelerated SGD, despite being a firstorder
approach, is capable of accelerating directions
of low-curvature just like an approximate Newton
method such as HF. Our experiments support the idea
that this is important, as we observed that the use of
stronger momentum (as determined by µ) had a dramatic
e↵ect on optimization performance, particularly
for the RNNs. Moreover, we showed that HF can be
viewed as a first-order method, and as a generalization
of NAG in particular, and that it already derives some
of its benefits through a momentum-like mechanism."
So yeah, probably Hessian-free is not very useful...

For what it's worth (responding to an old thread) the above quote by @harpone does not establish the conclusion.  Actually the 2013 ICML paper quoted above demonstrates that careful use of momentum  methods almost closes the gap in performance that existed between HF-based methods and other first-order methods.  That is, as of 2013, the HF-based methods of Martens + Sutskever were still better than the momentum methods employed in the 2013 paper. (at least for a number of important tasks, esp. training SRNs)
Perhaps the conversation subsequently evolved to the point that HF-based methods no longer tops after the advent of Adam and others.  But that requires more reading.  Perhaps I will find the paper Chollet refers to about Adagrad and RMSprop as I read further.

I also have a need for a HF optimizer for estimating RNN parameters.   I have played around with various first order optimizers but I am seeing too much noise,  I was wondering if anyone has build a HF optimizer for Keras yet or whether I need to build one from scratch.   I am currently looking at the Optimizer class to figure out what needs to be done.


Documentation CONTRIBUTION and CODE OF CONDUCT file

Kindly do add the labels used in the issue in PR also

Congratulations on your first merged PR! Good work.

Congratulations on your first merged PR! Good work.

Thank you @Femme-js
You could close my issue since it is resolved now.


Dropdowns/Selects unsupported

Seems that Dropdowns/Selects are unsupported.

If it helps I have a small sample repo showing what I assume is a similar problem:
https://github.com/DesHorsley/blue-harvest-dropdown
One mat-select on the screen, when you try click('Favorite food') or see('Favorite food') you get a similar error to:
      Elements:
      Favorite food
      Favorite food


"Integrate Azure Firewall with Azure Standard Load Balancer" article doesn't include how to use DNAT rule.

The note in this article (https://docs.microsoft.com/en-us/azure/aks/limit-egress-traffic):

When you use Azure Firewall to restrict egress traffic and create a user-defined route (UDR) to force all egress traffic, make sure you create an appropriate DNAT rule in Firewall to correctly allow ingress traffic. Using Azure Firewall with a UDR breaks the ingress setup due to asymmetric routing. (The issue occurs because the AKS subnet has a default route that goes to the firewall's private IP address, but you're using a public load balancer - ingress or Kubernetes service of type: LoadBalancer). In this case, the incoming load balancer traffic is received via its public IP address, but the return path goes through the firewall's private IP address. Because the firewall is stateful, it drops the returning packet because the firewall isn't aware of an established session. To learn how to integrate Azure Firewall with your ingress or service load balancer, see Integrate Azure Firewall with Azure Standard Load Balancer.

Mentioned article Integrate Azure Firewall with Azure Standard Load Balancer but the action given was to configure DNAT, which the article doesn't include. Please explain further about the public loadbalancer scenario and how to configure.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a38439d0-0125-3445-1c0a-a03b940e315d
Version Independent ID: c6436a35-94b9-6396-3b13-9291f0a17b21
Content: Restrict egress traffic in Azure Kubernetes Service (AKS)
Content Source: articles/aks/limit-egress-traffic.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the feedback! We are currently investigating and will update you shortly.

@tdihp Please check this document for Azure Firewall DNAT, replace Private IP with Public IP of the Load balancer.

Thanks for the update @VikasPullagura-MSFT , what I'm not following is the relationship of the two sentences:

make sure you create an appropriate DNAT rule in Firewall to correctly allow ingress traffic
To learn how to integrate Azure Firewall with your ingress or service load balancer, see Integrate Azure Firewall with Azure Standard Load Balancer.

It appears the DNAT isn't related to the 2nd sentence, so what is the relationship between them?

@tdihp I am assigning the issue to the doc author for adding comments.

@mlearned Can you please look into this issue and add your comments.

Adding @MicrosoftDocs/aks-pm

I'm in this same situation.  It is not clear to me what DNAT rules (as eluded to in this article) I would need or if I just need a direct route from my azure firewall external ip to the internet (as is mentioned in the other linked article).

This feedback has been incorporated and example provided on what is for:
https://docs.microsoft.com/en-us/azure/aks/limit-egress-traffic#add-a-dnat-rule-to-azure-firewall

Thank you for updating @palma21
#please-close


Fix - LHN - When you delete a message from a room, the conversation in the members remains bolded

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/36013
PROPOSAL: https://github.com/Expensify/App/issues/36013#issuecomment-1932019454
Tests

Log in with two accounts User A & User B
Under user A, create a WS
Invite user B to the created WS
Under user B, go to a conversation other than #announce room
Under user A, send a message to the #announce room and Delete the sent message
Verify that the #announce room from User B side is not bolded in LHN

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/38649957/09201140-5a1a-45d1-89f7-2a3e45099ebc

Android: mWeb Chrome

https://github.com/Expensify/App/assets/38649957/51027ae9-1dec-47fa-a1ae-73b8c6712e67

iOS: Native

https://github.com/Expensify/App/assets/38649957/89f12307-482c-4a6f-823c-cc5234620cad

iOS: mWeb Safari

https://github.com/Expensify/App/assets/38649957/d2efee59-e985-4340-b458-214fe2377b23

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/38649957/e2d9e6d0-ed68-4288-8dda-f6579b24520a

MacOS: Desktop

https://github.com/Expensify/App/assets/38649957/7eec9f4d-3029-4f58-9f42-ccf5e9125032

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/4160319/6397495c-0fbc-4d38-83f1-58713a6c358e

Android: mWeb Chrome
https://github.com/Expensify/App/assets/4160319/dd06020a-2815-4b9d-b4f1-643da2dca114

iOS: Native
https://github.com/Expensify/App/assets/4160319/b257fec8-5c92-4992-80c7-da61285fcfd1

iOS: mWeb Safari
https://github.com/Expensify/App/assets/4160319/dc2d5c2a-f28a-4de4-bc85-924ec454159c

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/4160319/23d82bfa-229e-4b90-b26f-df2f90264c7f

MacOS: Desktop
https://github.com/Expensify/App/assets/4160319/0a220f3e-ece9-4854-8afa-d7cf473eac5e

@akinwale U're good to go

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.44-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


mWeb Android/Chrome - Compose box is hidden when we delete edited message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app in android chrome
Open any report
Send any text
Write some text in compose box and long press message sent in step 3 and edit the message
Remove all the text and click send, in delete popup, click on delete
Observe that composer is now not visible

Expected Result:
App should display the composer after we delete edited message
Actual Result:
App does not display the composer after we delete edited message in android chrome
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.48-3
Reproducible in staging?: Y
Reproducible in production?: Needs repro
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43995119/077a2e60-4a14-41de-8b26-84a3f97b16e0
https://github.com/Expensify/App/assets/43995119/05da3129-20d3-4b0b-862c-916e1af8a8e0
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690903191529089
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@bfitzexpensify We are near closure of the checklist. Contributor is not able to repro on PROD, i need a bit more time to validate PROD. If you can check on your side as well to confirm if its a blocker or no, would be great

I'm also not able to reproduce it on prod, investigating what caused the issue

Proposal
Please re-state the problem that we are trying to solve in this issue.
Compose box is hidden when we delete message by saving empty draft
What is the root cause of that problem?
When we save the empty draft, delete confirmation modal appears and the input gets blurred. On select delete, deleteDraft is called, but isFocusedRef.current is false and the main composer doesn't show
https://github.com/Expensify/App/blob/5034433c46088208bea475476d2be98f623ac0af/src/pages/home/report/ReportActionItemMessageEdit.js#L203-L206
This is the root cause
What changes do you think we should make in order to solve the problem?
We need to check if deletion is from confirm modal
Change the above code to
        if (isFocusedRef.current || ReportActionContextMenu.isActiveReportAction(props.action.reportActionID)) {
            ComposerActions.setShouldShowComposeInput(true);
            ReportActionComposeFocusManager.focus();
        }

Removes the isFocused state. We can use isFocusedRef instead.
This works fine
What alternative solutions did you explore? (Optional)

We will handle this as a part of https://github.com/Expensify/App/pull/23618 since it's a regression

@s77rt
Do you agree with the solution I proposed?

Hi @s-alves10, I tested the proposed change but the compose input is still not shown after following the reproduction steps:
https://github.com/Expensify/App/assets/6829422/b9826036-d80b-4c4e-8134-1178fc463b78

@s-alves10 Yes.
We should show the Main Composer only if we are deleting the active report action.
A report action is considered active if it's focused, have the context menu open or have the emoji picker open - we need to be sure we are not missing any other cases.

Yes. We've missed the deletion by saving empty draft

We will handle this as a part of https://github.com/Expensify/App/pull/23618 since it's a regression

Ok, I'm going to revert the PR that introduced the regression to unblock the deployment

Follow up PR will be created in an hour
@marcochavezf

Ok sounds good, let me know when it's ready, otherwise we'd need to revert

@s77rt
Can you test with the branch https://github.com/s-alves10/App/tree/fix/issue-24016?

@s-alves10 Please raise a PR, I will test asap. You need to test that as well.

@s-alves10 Let's continue proposal discussion here.

The PR that caused the regression was reverted, so I'm going to close this issue since it's no longer happening on staging

Hi @marcochavezf, @s77rt, it seems like issue was useful to trigger the solution, will it be eligible for reporting bonus?

Oh sorry @dhanashree-sawant, I think yes since it was a deploy blocker and fixed with the revert. Reopening for payment cc @bfitzexpensify

Cool, this has been paid out.

I think this is reproducible again

This actually got reported again https://expensify.slack.com/archives/C049HHMV9SM/p1692747837798019

I think this should be fixed in https://github.com/Expensify/App/issues/23908


Custom messages

Hi Can we add any custom message in the code

Hi @alpha191yash,
Sure, you can add your custom message by changing the function outputStrClock() in the LEDDotMatrixClock.ino file.
Just be aware of the message size due to the reduced memory size of this Arduino Nano board.
Regards,
Leonardo.


Support compiled PlantUML binary path

Similar to the bin_path option from https://github.com/quantorconsulting/mkdocs_build_plantuml

Thanks for raising this issue @MattTheCuber. Binary support wasn’t implemented to maintain simplicity and ensure a unified interface. Perhaps locally deployed puml server using docker would suit you?
Run PlantUML service with Docker

Hi @MattTheCuber, please can you confirm if the ^2.0.0 version of the package and Docker PlantUML server work for you?

Sure. The mkdocs_puml==2.3.0 works well. However we aren't using docker so I didn't test that.

Great, I'm really glad to hear that 😄 I added a note to think about supporting binary directly but I can't say that I'll implement it any time soon. As for now, I'd like to keep server-only support. Anyway, thank you for your commitment!


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/206 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 6260e13:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Incompatibility with Blazor Preview 9

Hi,
in Blazor Preview 9 the signature of the method to call client side javascript has changed, so we get an error when we try to access the local storage.
The paramters to the javascript call over JsRuntimeInvokeAsync have to be an object array now and it returns a ValueTask instead of Task
Carl

I’ll push an update later today

Pushed

3.0.0-preview9.19424.4.2


Request a demo about tensorflow C++ 2.x for inference

I found the offical released tensorflow C++ library with version 2.6 on the website: https://tensorflow.google.cn/install/lang_c, However, there is no a complete demo to show how to load and preprocess data (especially for sequential data, not picture), load model and for inference in the C++ environment. Can you help me find several examples?
Thank you sincerely.

Hi @v3551G !
Instructions for built-in C API from source can be found here. You can find other details on other ops here. Attached a relevant thread to understand  the process.
@sachinprasadhs ! Could you look at this feature request.
Thank you!

We don't have an end to end example on Tensorflow c++ yet, however, you can find the API reference for al the C++ implementation here https://www.tensorflow.org/api_docs/cc and each API will be having details/code example/code snippet which will help you. Thanks!


Malformed LifecyclePolicy block when both transition parameters are used

Found a bug? Maybe our Slack Community can help.

Describe the Bug
If both transition_to_ia and transition_to_primary_storage_class are used in the module, the following error is returned by Terraform:
Error: error updating EFS file system (fs-***) lifecycle configuration: BadRequest: One or more LifecyclePolicy objects specified are malformed.
│ {
│   RespMetadata: {
│     StatusCode: 400,
│     RequestID: "***"
│   },
│   ErrorCode: "BadRequest",
│   Message_: "One or more LifecyclePolicy objects specified are malformed."
│ }
│
│   with aws_efs_file_system.default[0],
│   on main.tf line 18, in resource "aws_efs_file_system" "default":
│   18: resource "aws_efs_file_system" "default" {

This happens because the module inserts both transition_to_ia and transition_to_primary_storage_class in one lifecycle_policy block, and Terraform expects a distinct lifecycle_policy block for each parameter.

Ran into this issue as well today.

This has been fixed in https://github.com/cloudposse/terraform-aws-efs/releases/tag/0.32.6

thank you!


Add Sort (by tags) functionality

Closes #18

Sorts the contacts in NUSCourseMates according to the tags (Close Friend, Friend, Emergency) in that order.
For contacts with >1 tags, the tag with the highest priority will be considered. For example, a contact with both Close Friend and Emergency will appear with other contacts tagged as Close Friend .
Format: sort tags
Test cases are being written now.

Contacts with the same tag will be sorted according to their names in alphabetical order.


from keyword can get highlighted in import ... from ''; statement

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.64.0-insider
OS Version: Kubuntu 21.04

Steps to Reproduce:

Have 2 files (2nd file is just to have something to import)

// index.ts
import { hi } from './other';

// other.ts
export const hi = 'hi'

Ctrl+hover between "./other" and from (may have to try multiple times)

// index.ts
import { hi } from './other';
                     ^^^^^^
              ^^^^

// other.ts
export const hi = 'hi'

Expected behavior:
Because the from keyword is normally not defintion-clickable, it should not be clickable as describe above as well.
Video:

https://user-images.githubusercontent.com/30693990/145874967-eaae0e11-e988-457a-82d7-5dbcb3c90bc7.mp4

/needsMoreInfo
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

/needsMoreInfo
Is it reproducible with all extensions disabled? You can try this with F1 and >Developer: Reload Window With Extensions Disabled

Yes, I filled out the form

Does this issue occur when all extensions are disabled?: Yes


Fix missing lines in about (or other text contents)

On https://news.ycombinator.com/user?id=tokenadult, the bio contains some pictograms in the first line. They're not displayed by the theme.

This now seems to render the same as no theme. @gabrielecirulli Confirm and close?


Websockets fail with HTTPS and http/2 if there is a reverse proxy on the line.

ViteJS fails to upgrade to websockets when using HTTPS and http/2 and there is a reverse proxy between the server and the browser.
Reproduction
Create a new container and install a blank new ViteJS project.
npm init @vitejs/app test --template vue
cd test
npm install
npx vite --https --host my-test.mydomain.com --port 8443

Install a reverse proxy, and tell it to use your container, and a test domain. For example haproxy on rpm based systems:
dnf -y install haproxy

Set /etc/haproxy.cfg to this minimal config:
frontend port8443
    bind *:8443 ssl crt /etc/haproxy/certificate.pem alpn h2,http/1.1
    default_backend default

backend default
    server my-test <IP_ADDRESS>:8443 ssl verify none alpn h2,http/1.1

.. where <IP_ADDRESS> is the IP of your container with the vitejs instance.
certificate.pem should be a certificate valid for a domain. Use this domain in /etc/hosts to map to the ip of the haproxy server.
Once it's all set up, open the domain in the browser. Vite will load, ... but then, it will go into an endelss loop trying to reconnect.
The broswer's inspector will have a message, its a bit hard to catch:
Logs
In chrome, observe:
[vite] connecting...
client:200 WebSocket connection to 'wss://my-test.mydomain.com:8443/'
failed: Error during WebSocket handshake: Unexpected response code: 404
(anonymous) @ client:200

In firefox:
[vite] connecting...
Firefox can’t establish a connection to the server at wss://my-test.mydomain.com:8443/.

Workaround
Use only http/1.1 - in haproxy, remove alpn h2,http/1.1 on both sides.
However, this might be not an option for people using hosting services.
System Info

vite version: vite/2.0.0-beta.36
Operating System: Fedora 32 / 33
Node version: tested with v12.19.0,  v12.20.1 and v14.14.0
Package manager (npm/yarn/pnpm) and version: npm 6.14.8, 6.14.10

Honestly I have no idea how to fix this, so PR welcome.

Honestly I have no idea how to fix this, so PR welcome.

I did some digging, and from what I am reading, I believe to use websockets with http2 in node, you'd have to use http2 instead of http with the allowHTTP1:true option. The http2 module probably adds some overhead, and I didn't test this at all. I'm just adding some information for someone to look at in the future :)
Refs:
https://github.com/websockets/ws/issues/1458
https://github.com/shellscape/webpack-plugin-serve/pull/184
https://github.com/shellscape/webpack-plugin-serve/pull/186

I did some digging, and from what I am reading, I believe to use websockets with http2 in node, you'd have to use http2 instead of http with the allowHTTP1:true option. The http2 module probably adds some overhead, and I didn't test this at all. I'm just adding some information for someone to look at in the future :)
Refs:
https://github.com/websockets/ws/issues/1458
https://github.com/shellscape/webpack-plugin-serve/pull/184
https://github.com/shellscape/webpack-plugin-serve/pull/186

@bompus
The code includes this option.

@bompus
The code includes this option.

i dont know much about protocol but i got issue with same place hmr websocket when try play middlewareMode + http2. i posted other issue maybe your issue and mine is same root.
#1807

i dont know much about protocol but i got issue with same place hmr websocket when try play middlewareMode + http2. i posted other issue maybe your issue and mine is same root.
#1807

@bompus I think your issue would be solved by https://github.com/vitejs/vite/pull/1992, but that's different than this issue. @LaKing does haproxy need any other config to properly proxy websocket connections? The 404 status code is really suspect.

@airhorns, no special settings needed for websockets. The haproxy minimal conf works with websockets, I tested it with node and a browser test

set server.hmr.host to your acture host normally <IP_ADDRESS> , and set server.hmr.protocol to 'ws' may solve this problem , cause vite use location.protocol to judge whether to use wss or ws, but usually reverse proxy wont deligate websocket,
that will cause an error in this line,then socket will trigger an close event making page reload

Adding @xorik's code to vite.config.js worked. If there's some way to automatically detect it, that would be nice.

UPD this config helped with the issue:
  server: {
    hmr: {
      host: 'some.server,
      port: 443,
      protocol: 'wss'
    }
  }

This solved my reload problem behind haproxy in a docker node container.
// "@sveltejs/adapter-node": "^1.0.0-next.51",
// "@sveltejs/kit": "^1.0.0-next.174",
// "svelte": "^3.43.0",

Same problem for gitpod. Thanks a lot to @xorik, server.hmr.host solves the problem.!

I ran into the same problem that using the Whistle tool to reverse proxy an online address locally caused an infinite loop and HMR failure.
If you fill in port:443, Vite will refresh indefinitely, but removing the port:443 will send the requests (https://xxx.net/...whistle-path.5b6af7b9884e1165...///whistle.bifrost/cgi-bin/list?_=1650621054028) every few seconds, then the page will refresh（the timestamp of the request parameter _ will change），and the HMR will be disabled when you save.
here is my config：
server: {
  hmr: {
    port: 443,
    protocol: "wss",
  },
  port: 3001,
  proxy: {
    '/api/conf': {
        target: 'https://xxx.net/api/conf',
        changeOrigin: true,
    },
  },
}

Closing as #8650 fixed this. Please try 3.0.0-beta.1.


Almost no javadoc in source code?

Any plan to add javadoc to source code?
It definitely help user to better understand how siddhi works, and of course would be more contributions.

Hi @gembin ,
Thanks for raising this. As starters I updated the Siddhi Manager class with javadoc. We will try to keep this going and make Siddhi source more understandable.

@tishan89
That's awesome, thanks a lot for your effort!

@tishan89
BTW, where is the best place to ask questions about how to use Siddhi?
I find https://groups.google.com/forum/#!forum/siddhi-dev and https://groups.google.com/forum/#!forum/siddhi-user seems inactive.

@gembin , Please use http://stackoverflow.com/tags/wso2 to raise any issues.. Tag Siddhi as well..

@mohanvive, thanks!

@mohanvive
Please help to answer my questions here http://stackoverflow.com/questions/37281740/siddhi-cep-3-x-newbie-questions ,  thanks!


The Ascent of Arceuus: improvement

On the step "Saving Arceuus" -> "Inspect some rocks near the Arceuss Alter", The wrong rocks were highlighted.
If its random if yea player, maybe highlight all the possible rocks to inspect

I can take a look at this


[BUG] Raise exception when attempting to change DF

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Resolves #1052

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

Hey @reaganjlee , the test failures are unrelated to your PR and are due to a musl release that recently made one of our golang library dependencies unhappy. Could you merge in main and @ me so I can rerun CI?

And thank you for adding this!

@beggers Should be good now!


Cannot create a private collection that includes a link?

Create collection
Add a link in the modal
Press Create. Nothing happens.
Delete the link. Press Create. The collection is created.

https://images.zenhubusercontent.com/228681195/e12ee7b9-5cd3-4b41-88f7-8725374003cb/screen_recording_2021_07_28_at_5_08_53_pm.mov

Post to the backend fails with 400
Body:
{
"name":"asdasd",
"description":"asda",
"contact_name":"dasd",
"contact_email":"asd","
Name":"",
"DOI":"https:/doi.org/12313",
"links":[{"link_name":"","link_type":"DOI","link_url":"https:/doi.org/12313"}],"
data_submission_policy_version":"1.0"
}

Response:
{
  "detail": "Additional properties are not allowed ('Name', 'DOI' were unexpected)",
  "status": 400,
  "title": "Bad Request",
  "type": "about:blank"
}

Somehow, the link type and name fields are being appended to the payload

It's not a frontend regression, I see the same request on prod.

A PR is out to fix this! PTAL thank you 🙌 https://github.com/chanzuckerberg/corpora-data-portal/pull/1312


Chargebee upgrades can cause a second subscription to be created

We need to implement subscription upgrades via the API.
To Do

[ ] Create a new API endpoint that allows organisation administrators to upgrade to Scale Up accounts - effectively to change the Chargebee plan-id to scale-up-v2. The API needs to update the plan within the Subscription object, and also set the number of seats in the Subscription to 5.
[ ] Modify the front end to hit this API when clicking on the upgrade button. This should send the chargebee plan-id to the API above.
[ ] Create a "Youve upgraded" modal with the new information.

OK i think this is just fundamentally not following the same steps described here. We need an endpoint similar in that page to generate_checkout_existing_url which AFAICT we don't have, and the FE is not attempting to call when upgrading the sub.

This PR ads a new endpoint to get the URL to the hosted page for an existing subscription, the FE should call this and direct the user there to upgrade instead of generating a new hosted page and then call the 'update-subscription' endpoint with the id of the hosted page as normal.
The issue we have at the moment (as I understand it) is that the FE is generating a brand new hosted page unassociated with an existing subscription id and hence a new subscription is being created rather than the existing one being amended.
Note that this flow is only applicable for organisations with existing subscriptions of course. Any new organisations / orgs without a subscription id will need to follow the current workflow.

Frontend will be live under the flag "upgrade_subscription", it looks like the hosted URL that comes from the API needs to be slightly different as it always shows the existing plan without the ability to edit. If possible this should preselect a plan that is passed to the API.

Ok, a bit of digging and looking through chargeee's unusually poor documentation, it turns out we just need to add the plan id of the plan the user wants to switch to when getting the hosted page.
To achieve this, I've updated the endpoint slightly so that it better describes what's happening.
The endpoint now looks like:
POST /api/organisations/:id/get-hosted-page-url-for-subscription-upgrade

 + request
{
    "plan_id": "startup"
}

 + response
{
    "url": "https://some.chargebee.url/page/id"
}

@kyle-ssg this is currently in a PR on the API here so once that's merged you can test it out on staging.

The plan IDs are:

startup-v2
scale-up-v2

Looks good against staging, though it doesn't work against production (maybe that's known but raising here just incase)

Frontend's live under https://github.com/Flagsmith/flagsmith/pull/544

I'll look at handling that better but the above just means that the organisation you're trying to request the page for doesn't have a subscription, or their subscription doesn't have an id (maybe it's some manual subscription or something).


wont start

when I start the application, nothing happens and it doesnt appear in task manager
v16, used to work fine
-admin mode
-restarted pc
-reinstalled everything livestreamer related
-installed streamlink
-downgraded t 15.x

I'm guessing you're using Windows (you ignored the issue template and did not provide any useful environment informations)...
Can you please launch the application from the windows cmd shell and then see for any log output? There's either something wrong with your application config/cache or something else on your system is preventing you to launch it.
You could try deleting your config folder in %LOCALAPPDATA%\livestreamer-twitch-gui, but I'd like to see an error log first, in case there's a bug that needs to be fixed.

Any response?


Java Style Guide: Constants example (Joiner vs Logger)

I've seen many discussions about if a static final Logger instance should be considered a constant or not (i.e. uppercase letters), and there are references to this style guide in which is suggested to use the logger as a non-constant value:
static final Logger logger = Logger.getLogger(MyClass.getName());

However, in most of the cases (at least all that I know), the Logger instances are immutables because there are no methods to change the internal status or to retrieve a mutable object, which seems to be the same case of the Joiner:
static final Joiner COMMA_JOINER = Joiner.on(','); // because Joiner is immutable

What is the fundamental difference between a Logger and a Joiner to differentiate them as a constant or non-constant?
What would be the case of a Gson instance if declared as a static final?
Thanks in advance

Probably, but it is still a weak rule to do this determination, e.g. what if the Joiner given as an example has a caching mechanism internally? What if you are specifying an interface but you have implementations with and without side effects? How do you know that a Logger has detectable side effects? Do we need to read and understand all of our dependencies in order to know if they can be used as a constant or not? Due to these questions I asked what would be the case of a Gson static final instance.

@vgonzalo They do have this on their documentation:
"Warning: joiner instances are always immutable; a configuration method such as useForNull has no effect on the instance it is invoked on! You must store and use the new joiner instance returned by the method. This makes joiners thread-safe, and safe to store as static final constants."

@Delfic I think you are enforcing my point: requiring to read the documentation about its implementation or understanding the internal algorithms is a weak styling rule because implementations can change over time (e.g. as I mentioned above, adding an internal caching mechanism can break this definition of immutability even if it's thread safe).
About the Logger, those mutators are present in the java.util.logging.Logger only, however in log4j2 or slf4j, for example, the LogManager gives you a Logger instance without mutators.

@vgonzalo Styling rules serve two main purposes: Better the readability of the code and prevent VCS conflicts coming from different styles.
If you go with one choice for all log implementations you prevent the latter but if you do care about the internal implementations and abide by it you address the former.
That being said it's a rule that seems impossible to enforce by static analysis.


Add eligible / not eligible to submissions

Allow to set a submission to eligible or not eligible, saving who set that and when (it's shown as a tooltip now).

When a new submission is created, neither option is selected.

An admin can use the Clear option if a submission was set as Not eligible or Eligible by mistake.
closes #25

Hey @damianmarti , good stuff!!
Sorry, I merged #62. Could you fix the conflicts? Don't worry too much about the style, @ChangoMan can help out later.

Conflicts resolved!


rustc_private error when compiling crates.io dependencies with Xargo configuration

When an enclave crate is configured to compile with Xargo, instead of manually importing the sgx_tstd standard library, you randomly get the following error from some dependencies:
error[E0658]: use of unstable library feature 'rustc_private': this crate is being loaded from the sysroot, an unstable location; did you mean to load this crate from crates.io via `Cargo.toml` instead?

A lot of crates compile with no issue at all, correctly linking to the tstd, but random expressions used in some crates trigger this error.
This is probably due to some miss-configuration of the tstd.
Which version of rust's std is the tstd based on? Are updates from stable Rust pulled into the tstd?

rust sgx sdk v1.1.2 supports rust nightly-2020-04-07.
rust sgx sdk on longer supported rust-stable after v1.0.8.
Add feature(rustc_private) to your enclave::lib.rs.
#![cfg_attr(all(target_env = "sgx", target_vendor = "mesalock"), feature(rustc_private))]

Me and my team are using the correct compiler version for the sdk versions that we use. The problem is that adding this feature in our crate does not disable this error in crates we depend on. We shouldn't have to fork half our dependency tree because of a misconfiguration, nor should we be adding this workaround to our top-level crate.

When an enclave crate is configured to compile with Xargo, instead of manually importing the sgx_tstd standard library, you randomly get the following error from some dependencies:
error[E0658]: use of unstable library feature 'rustc_private': this crate is being loaded from the sysroot, an unstable location; did you mean to load this crate from crates.io via `Cargo.toml` instead?

A lot of crates compile with no issue at all, correctly linking to the tstd, but random expressions used in some crates trigger this error.
This is probably due to some miss-configuration of the tstd.
Which version of rust's std is the tstd based on? Are updates from stable Rust pulled into the tstd?

Which crate will trigger this error? Can you provide a specific crate name？

Off the top of my head, we've seen it getting triggered by lazy_static in our dependencies.
Looking at conversation logs i found this as well:
error[E0658]: use of unstable library feature 'rustc_private': this crate is being loaded from the sysroot, an unstable location; did you mean to load this crate from crates.io via `Cargo.toml` instead?
   --> /home/username/.cargo/registry/src/github.com-1ecc6299db9ec823/secp256k1-sys-0.1.2/src/lib.rs:301:5
    |
301 |     assert!(mem::align_of::<usize>() >= mem::align_of::<u8>());
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #27812 <https://github.com/rust-lang/rust/issues/27812> for more information
    = help: add `#![feature(rustc_private)]` to the crate attributes to enable
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `secp256k1-sys`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

@reuvenpo You can try to use -Z force-unstable-if-unmarked flag to solve your problem. This flag forces the crate to be unstable, while also allowing them to use other "unstable" crates.
RUSTFLAGS="-Z force-unstable-if-unmarked" xargo build --target x86_64-unknown-linux-sgx --release

Ok, awesome :D
We checked it for a few dependencies that we've been having trouble with, and indeed this workaround solves the issue for the entire dependency tree.
That being said, this is still an issue that needs to be investigated... The Xargo docs don't mention anything like this, which indicates that something is missing from the sgx-sdk. Until a solution is found though, can you please document the need for this flag when using Xargo to compile the stack?
As a side question, why do you show examples of compiling packages without Xargo? It's not very useful to have your crate marked as no_std and then add tstd as a dependency of that crate alone. It forces you to only use no_std dependencies, while you're still linking to a mostly-usual std anyways so you don't get any of the benefits of no_std.

Yes, I also see that there is no mention of any information about this flag(force-unstable-if-unmarked) in the xargo doc, so this issue still needs analysis. If there is any progress, I will record the analysis results in this issue.

The issue is because crates in SGX custom sysroot do not declare # [staged_api] and # [stable] features. If set the -Z force-unstable-if-unmarked flag, rustc will automatically mark rustc_private features, so setting the -Z force-unstable-if-unmarked flag will not compile errors when building crates.
https://github.com/rust-lang/rustc-dev-guide/blob/master/src/stability.md
Xargo uses the -Z force-unstable-if-unmarked flag when building a custom sysroot, but this flag is not set when building the top-level crate, so there will be no compilation errors when building custom sysroot.
There are two ways to solve this problem:
1: Use the -Z force-unstable-if-unmarked flag;
2: Add #[staged_api] and #[stable] / #[unstable] features to each crate in SGX custom sysroot, and each pub attribute Item also needs to be declared # [stable] / # [unstable] features;
Which solution would be better, any idea?

interesting... I imagine it depends on how much effort you want to put into this... If you don't want to go back and mark all the public functions with these annotations, then i suppose it's acceptable for most use cases to point out and explain the usage of this flag when using Xargo. Does the SDK compile with stable compilers? If so, then this might cause issues for that workflow (although we specifically use nightly compilers)


dart:async: Exception Caught by Scheduler Library

We observed the following message in our logs:
The following assertion was thrown during a scheduler callback:
'package:flutter/src/rendering/object.dart': Failed assertion: line 1135 pos 20:
'node.isRepaintBoundary': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      PipelineOwner.flushPaint (package:flutter/src/rendering/object.dart:1135:20)
#3      RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:518:19)
#4      WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:865:13)
#5      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1289:15)
#6      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1218:9)
(elided 5 frames from class _AssertionError and dart:async)

Flutter doctor
$ flutter doctor                                                                                [16:30:24]
Building flutter tool...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.3 22E252 darwin-arm64, locale en-CA)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.71.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!

Based on the logs, it looks similar to https://github.com/flutter/flutter/issues/120874, so please follow-up in it for further updates. You may upvote the original issue for team's attention and priority.
Closing in favor of it.


[Feature Request] Helm chart in production

Hey there,
we are currently looking at temporal to manage workflows for our microservices. While looking at the helm chart I came across the note in the README "We do not recommend using Helm for managing Temporal deployments in production". The link to the discussion does not work anymore. Is this still up-to-date? Does anyone know why they dont recommend this?

See https://web.archive.org/web/20221001133521/https://temporal.io/blog/temporal-and-kubernetes

Duplicate: #371


Optional adapters/Lazy-load adapters (#965 #1090)

Fixes #965
Fixes #1090
I'm just staging this PR, it's based off connection managers (#1064) and is done barring any further changes to that branch. It makes all adapters optional, and installers have to explicitly opt-in with the [feature] syntax. It also makes adapter packages load lazily, when the configuration's credentials object is parsed.
Internal changes
There were some internal structural changes to adapters and connection contracts:

dbt.adapters.factory.ADAPTER_CLASSES now starts off empty, as do the various portions of connection contracts that are adapter-specific.
When the chosen target references an adapter typename, dbt imports dbt.adapters.typename as ``, registers .Adapter for the type, and returns pkg.Credentials for validation. So packages need to expose their adapters/credentials under those names.
Converting dbt internal schema representations into bigquery schema representations now happens in the bigquery adapter itself, purely for dependency reasons.
adapter-specific Connection contracts are now part of the adapter packages themselves, instead of part of dbt.contracts.connection

Test changes
I changed the tox environments (and so also the CI tests) to use the new -e .[...] syntax. Things seem to work.
User impact
To get the existing dbt installation behavior, either continue to use -r requirements.txt or use -e .[postgres,snowflake,redshift,bigquery]. When this is on pypi, users will have to pip install dbt[postgres,snowflake,redshift,bigquery] to get the same behavior, which is unfortunate. Python does not really provide an opt-out mechanism for dependencies, only opt-in, and has no concept of a "default" features set.
If that is scary from a backwards-compatibility perspective, one gross idea I had was to make this something like dbt-core, and make a dbt package that depends upon dbt-core[postgres,snowflake,redshift,bigquery].

Superseded by #1109


Docs: Admonitions consitency

What were you initially searching for in the docs?

While i was browsing the docs, i've noticed something is not right with the format

and when i started to work on a PR, i've noticed a bit of inconsistency on various pages where:

on some pages we have admonitions with title: Info/ Warning/ Note etc
on some we don't

Describe how we could make it clearer
I'd like to suggest we adhere to a convention whereby

every admonition will have the default title

Current

Proposed

for cases where we provide a custom title, we prefix it with the default title in the format <default title>: <custom title> - i.e Tip: DynamoDB

Current

Proposed

use the example admonition instead of question mark or quote

Current

Proposed

nice to have - collapsible blocks ( default open)

Open block

Closed block

If you happy with my suggestion, i'll start working on a PR to address all the pages from A to Z.

I like them!!! Please go ahead and we can make some small tweaks as part of the PR :) Thank you so much @DanyC97 !

Hey @DanyC97 thank you again so much for the help here, docs is so crucial to us and it's hard to get quality contributions like these.
Now available in the latest docs!


MegEngine: fix some bugs

fix some bugs of megengine C++ model (.mge) visualization:

show the shape of the middle tensor;
fix scope matching model identifier (mgv2) due to possible leading information;

please help review, thanks~

Hi @lutzroeder, can this mr be merged?

@Ysllllll can you rebase to TIP. The mgbtest0 and ./tools/megengine changes should be no longer needed. If not, please share a small repro. The data type is still an open discussion. For now, use the specific name if there is no general name to get unblocked. This will result in the uint8 not getting rendered which can be addressed in a later change.

OK. Yes, for ./tools/megengine, its changes is no longer needed. for mgbtest0, need to modify a little bit, that is, remove the if statement of the file size( if (size === (stream.length - position - 4))), Here is an example:
add_with_data.zip


feat(generic): add ForPage

What?
add ForPage
Why?
It's pretty useful
How?
check for where the page items would be and then just return a slice between the bounds

Codecov Report
Base: 97.82% // Head: 97.84% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (af41b35) compared to base (f54bf01).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #62      +/-   ##
==========================================
+ Coverage   97.82%   97.84%   +0.02%
==========================================
  Files           8        8
  Lines         920      929       +9
==========================================
+ Hits          900      909       +9
  Misses         14       14
  Partials        6        6

Impacted Files
Coverage Δ

generic.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.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: bump sc4s/splunk versions

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


CEO-430 Move the widget title below the widget type selection.

Purpose
Moves the widget title below the widget type selection when creating/editing a GeoDash widget. Updates the GeoDash help text to correspond with this change. Note that I didn't update the images on the GeoDash help page until it's decided if we want a GIF or an image. Swaps the position of the "Close" and "Copy" buttons on the "Copy Widget" modal to be consistent with the other GeoDash widget modals.
Related Issues
Closes CEO-430
Submission Checklist

[x] Included Jira issue in the PR title (e.g. CEO-### <title>)
[x] Code passes linter rules (npm run eslint/clj-kondo --lint src)

Screenshots

src/js/geodash/CopyDialog.js
50, fix indent.


Don't take collateral if validation doesn't fail in phase 2

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Formatting, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

@sjoerdvisscher here is a PR with that fix. I think we might need a bit of help debugging the PAB issue. Should we make an issue with this too?

I have looked at this a bit. The problem seems to be that the test was not ok to begin with. The 3rd test does not fail if you comment out the second test. So there's some state transfer between tests. @koslambrou it seems you wrote these tests, does that sound plausible?

Found the error, but I don't know why your fix triggered it.
It's in the test case "PingPong contract state is maintained across PAB instances" in CliSpec.
Change
let newConfig = bumpConfig 50 "db1" pabConfig

to
 let newConfig = bumpConfig 50 "db1" defaultPabConfig

That solved it locally.

@koslambrou if the test failure is unrelated to this fix, maybe it makes more sense to fix the test in a separate PR and hold this PR until that has landed? If you want it here you can always make a PR to this branch.

@MaximilianAlgehed The fix is on main. You can rebase.

@koslambrou Rebased and tests are passing.


Save debugging session complete with breakpoints

It would be super snazzy awesome if there were a way to save all current breakpoints in your devtools window somewhere so you can wipe them to work on something else, then reapply them all later if/when you revisit the first issue. Yes, I can disable them all, but I often use the enable/disable all button already and this would complicate things.
This would be very helpful for my team at work since we're fixing a lot of separate little bugs all over the site.
Thanks!
-ETO

Hey @HeroicOvenmitt thanks for the suggestion!
This repo is for content on web fundamentals site. You can file anfeature request over at https://bugs.chromium.org/p/chromium/issues/list 👍


add detailed logging info for sale_nft_origyn data

After doing all this work I have a better idea of how to do this in a more elegant way but due to limited time this works for the moment.

@skilesare moved the function to utils.mo but you might want to hold on this since I'm working on a better solution.

Closing this. Replaced with canistergeek


Change the Feedback link to take you to github

Fixes #787.
Considering we're just duping all feedback hub issues to github, lets cut out
the middleman and take them straight here.

Maybe a little nitpicky but thoughts on cutting out an extra step and going to "https://github.com/microsoft/Terminal/issues/new"?

Maybe a little nitpicky but thoughts on cutting out an extra step and going to "https://github.com/microsoft/Terminal/issues/new"?

I have no strong feelings one way or the other.

Maybe a little nitpicky but thoughts on cutting out an extra step and going to "https://github.com/microsoft/Terminal/issues/new"?

I have two feelings about it:

Dropping people onto the main page might offer them the opportunity to read the issues before writing a new one.
I think the new issue form will offer them our templates and automatically try to find duplicates these days, so it might be a good call to go there.

I want @DHowett-MSFT to weigh in on this before merge though.

So the way it is today most closely mimics what we had before: dropping people onto the "feedback portal" where they can find everything. It's probably better for discovery than using the New Issues page.
If they can't find what they're about to report, "new issue" is just one click away. If they submit new feedback and github suggests the dupe they couldn't find, that's another chance to get them to +1 an existing report.

OK let's roll with this then.


.gm domains

Problem
There's no whois server registered to the IANA Route Database Zone for all .gm domains.
Conclusion
That makes all .gm domains fails.

Please report to http://www.nic.gm/htmlpages/whois.htm for whois lookup


[fix][broker] Fix failure while creating non-durable cursor with inactive managed-ledger

Motivation
Right now, the broker is failing to create a reader for a topic that is inactive and has deleted the inactive ledger as it has reached the inactive-ledger-timeout threshold. inactive-ledger-deletion task deletes inactive ledger but it doesn't create a new ledger because of that such topic stays with LedgerClosed state and without active ledger, and meanwhile if any reader tries to connect on that topic then reader creation fails with below error
09:55:28.217 [pulsar-io-4-26] WARN  org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:57218][persistent://tenant1/us-east1/ns1/t1][rea
der-8a3095b8c5] Failed to create consumer: consumerId=15, null
java.util.concurrent.CompletionException: java.util.NoSuchElementException
        at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) ~[?:?]
        at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1113) ~[?:?]
        at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235) ~[?:?]
        at org.apache.pulsar.broker.service.persistent.PersistentTopic.internalSubscribe(PersistentTopic.java:717) ~[pulsar-broker.jar]
        at org.apache.pulsar.broker.service.persistent.PersistentTopic.subscribe(PersistentTopic.java:693) ~[pulsar-broker.jar]
        at org.apache.pulsar.broker.service.ServerCnx.lambda$handleSubscribe$12(ServerCnx.java:1095) ~[pulsar-broker.jar]
:
java.util.NoSuchElementException
	at java.base/java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:1859)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.getFirstPosition(ManagedLedgerImpl.java:3715)
	at org.apache.bookkeeper.mledger.impl.NonDurableCursorImpl.<init>(NonDurableCursorImpl.java:59)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.newNonDurableCursor(ManagedLedgerImpl.java:1127)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.newNonDurableCursor(ManagedLedgerImpl.java:1108)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.newNonDurableCursor(ManagedLedgerImpl.java:1100)

Stats-internal
{
  "entriesAddedCounter" : 0,
  "numberOfEntries" : 0,
  "totalSize" : 0,
  "currentLedgerEntries" : 0,
  "currentLedgerSize" : 0,
  "lastLedgerCreatedTimestamp" : "2023-10-26T15:24:57.886Z",
  "waitingCursorsCount" : 26,
  "pendingAddEntriesCount" : 0,
  "lastConfirmedEntry" : "1000:-1",
  "state" : "ClosedLedger",
  "ledgers" : [ ],

Modifications
Make sure, inactive-ledger-timeout task creates a new ledger after deleting inactive ledger to avoid above such failures while creating reader and subscription cursor.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Codecov Report

Merging #21508 (1744b2d) into master (78fc853) will increase coverage by 39.86%.
Report is 1 commits behind head on master.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             master   #21508       +/-   ##
=============================================
+ Coverage     33.39%   73.26%   +39.86%
- Complexity    12194    32625    +20431
=============================================
  Files          1638     1890      +252
  Lines        127949   140442    +12493
  Branches      13952    15436     +1484
=============================================
+ Hits          42733   102897    +60164
+ Misses        79564    29459    -50105
- Partials       5652     8086     +2434

Flag
Coverage Δ

inttests
24.11% <33.33%> (-0.05%)
:arrow_down:

systests
24.76% <33.33%> (?)

unittests
72.56% <100.00%> (+40.74%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...a/org/apache/bookkeeper/mledger/ManagedLedger.java
0.00% <ø> (ø)

...che/bookkeeper/mledger/impl/ManagedLedgerImpl.java
80.90% <100.00%> (+41.65%)
:arrow_up:

... and 1539 files with indirect coverage changes

And it's a break change to the ManagedLedger.java since we already have @InterfaceStability.Stable
  /**
   * Can evolve while retaining compatibility for minor release boundaries.;
   * can break compatibility only at major release (ie. at m.0).
   */
  @Documented
  public @interface Stable {}


Added Support for Vanilla and Quantized ChatGLM3 Models to Model Builder

We have integrated support for both vanilla and quantized versions of the ChatGLM3 models into the Model Builder. Additionally, we have successfully performed parity checks for both model types to ensure consistency and reliability across different configurations.

@kunal-vaishnavi PTAL

@microsoft-github-policy-service agree company="AMD"

Can you add the ChatGLM3 models to the CIs?
https://github.com/microsoft/onnxruntime-genai/blob/0f59a900568cf65d74554cc34027648989f4ab1c/test/python/_test_utils.py#L55-L77
The models in hf_paths are downloaded from Hugging Face, and the models in ci_paths are currently uploaded to /data/ortgenai_pytorch_models in one of the CI VMs.
https://github.com/microsoft/onnxruntime-genai/blob/0f59a900568cf65d74554cc34027648989f4ab1c/.github/workflows/linux-gpu-x64-build.yml#L122

@kunal-vaishnavi I really appreciate your time for this PR review. Please let me know if there are other suggestions going forward.


Option Screens Index Out of Bounds Exceptions

The code here is causing the UI to crash whenever you open a configuration screen.
It's because many grids have a single column and there's no index 1.
Not sure what is for can we remove it? I took it out in my code and everything works great.
https://github.com/IBM/HTTP-BlackOps/blob/50844b3072445194c5443aaf37a760730f906847/CommonControls/OptionsGrid.cs#L309

Thanks Paul, please go ahead with the fix.


replace the anoma process with the sub-command

1st commit, related to #592 - anoma sub-commands replace the current process
2nd commit, closes #583

merged to next, later destinations master, maint-0.2


Chat edgebug stat (Pull request)

Yep. Like in clarity, interium, some other big name pastes 😎
Clarity | edgebugged
Interium | Edgebug [1]
https://youtu.be/m_uhWdSBvSo
I dont really understand how it works. Will be grateful if you will help me!
I will try selfcoding it soon

I can only help you with the chat print part.
https://www.unknowncheats.me/wiki/Counter_Strike_Global_Offensive:Printing_text_to_chat

this would be helpful!

Yep. Like in clarity, interium, some other big name pastes 😎
Clarity | edgebugged
Interium | Edgebug [1]
https://youtu.be/m_uhWdSBvSo
I dont really understand how it works. Will be grateful if you will help me!
I will try selfcoding it soon

this would be helpful!


Sdk volume tests i

Volume Tests for osd-sdk
This PR contains the below tests.
Create,Delete,Inspect,Mount,Unmount,Attach,Detach,
Clone,Enumerate.
Notes for Reviewer :
Commented code is for tracking purposes to implement the cases in fake driver.

Please solve build  failure issue


Returning Cert Manager mention.

Affected URL
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/
Cert Manager mention was removed in kubernetes/website@8781518d as part of
the merge conflict resolving.

Links to cert-manager placed back (so we wouldn't see again
[cert-manager][cert-manager] in article text).
In addition link to cert-manager documentation is updated to official
website (it's still readthedocs website but, its official by the stand of team
behind of the cert-manager)

/assign @bradtopol

/lgtm

/approve


[Feature] Implementing a profile screen for the regular contributors

What is the proposed feature?
Since every open-source organization has regular contributors. I believe, having a page in the organization's mobile app for them to showcase their contributions and milestones with the organization would be handy.
I have designed the following mockup in order to demonstrate what I suggesting. So, please feel free to add your thoughts.

How do I approach the proposed feature implementation?
As I mentioned in issue #17 if we are using GitHub authentication for this application we can track the contributors and their contributions using the GitHub APIs also we can use that Auth ID and maintain a separate profile our regular contributors (One can become a regular contributor when she/he has a certain amount of PRs).
Also, the organization can introduce some badges (Score Badges) to its contributors as well. I believe this kind of page will motivate the contributors to get started with this organization.
What are the features this screen offers?

Sharing their profile as an image.
Track their contributions.
Mange their open-source contributions related badges.

Would you like to work on this feature?
Yes.

We have to use a database for store user details (like badges) right?

@hiranthaR  yeah we can use something like Firebase.

Rather using database we can use github data ,  models and recycleviews if apporved would love to work on this


[💡Feature Request] Screener

Describe the feature
possibility of adding stock screeners.

I feel like a stock screener will be a bit out of scope, since at its core Harvest is an algo trading framework. That being said, it might be interesting to add an interface to get the fundamentals of the stock, like earning reports and the industry of the company.