Task retry does not take extra command-line args into account?

We've just seen the following pattern for a request:

Task with extra command line args fails
New task is created with message Task launched because of RETRY
New task does not have any extra command line args

Is that expected or a bug?
/cc @ssalinas

Hey @demobox , apologies for the slow response. To make sure I get the situation correct, I'm assuming this is a Scheduled request that you launched with extra command line args using the 'Run Now' option?
If so, that's an interesting one, and brings up the question of whether launching the 'Run Now' with new args should change it for all runs of the scheduled request going forward (essentially creating a new deploy for it). I would argue that in order to change all future tasks' args, you should be posting a new deploy, since 'Run Now' is more of a one-off action.

To clarify that a bit more succinctly, yes that is what I would expect to happen currently. To change all tasks going forward for the scheduled request, I would recommend a new deploy instead.

To change all tasks going forward for the scheduled request, I would recommend a new deploy instead.

Agreed. That is not the intention here, though - sorry if the description wasn't clear. This is only about how retries of a failed task are performed. I.e. if I kick of task A with some extra args, and A fails and I have retries configured for that Request, should the retries of A use the same args?
Obviously, subsequent triggered runs for a scheduled tasks, or direct invocations using "Run now", should probably not inherit these args.
And actually, it wasn't for a scheduled request, but an on-demand one ;-)
Thanks for taking a look, @ssalinas!

Ah, I had misinterpreted, thanks for clarifying. That is likely a bug then, I would expect that those arguments get carried through for a retry. I can look into a fix for that

I can look into a fix for that

Great, thanks!


7 arts and techniques of Papuan Kelulau

7 arts and techniques of Papuan Kelulau created by<EMAIL_ADDRESS>on 2017-05-03 09:00:11

<EMAIL_ADDRESS>replied, Someone submitted this missing proverb:
Tuich el kelulau: Ouerrong (ouuerabek) ra beluu ma rechad. A ta ra tekoi a
kmo: Ng orimel el teletael luldimukl ra ulecheracheb ma ulekdakd. Tuich el
kelulau (English): To force and intimidate people and Beluu. Strategy
deviced by force, false accusation and intimidation. One of the 7 arts and
techniques of Palauan Kelulau ( Whispers).
We have another similar proverb:
Tuich el kelulau e loubuch ra calm.  Which is about compromise.
Are there 5 more of these?  These are awesome.  This is the Palauan 'Art of
War'!  Very cool.  Where can we find them?  Is Sim on here?  Maybe the
museum has these?  Apparently they might have been catalogued by John Useem
in 1949!  Can anyone help find this book?
https://books.google.com/books/about/Report_on_Palau.html?id=1nyqnQAACAAJ

<EMAIL_ADDRESS>replied, Hey John,It looks like UC Berkeley has a copy in their library. I'll add this to the list of things I'll look for on my next trip there. (I try to go a couple of times a year.)If you want it sooner, other libraries have it too and you can order it through inter-library loan from your local library probably: http://www.worldcat.org/title/report-on-palau/oclc/8535563-J

<EMAIL_ADDRESS>replied, Thanks Justin.  I have requested it through my local library interlibrary
loan.  They're normally pretty awesome so I'm guessing they'll come through
once again; they've helped find a ton of our books so far.  (hmmm, I should
probably acknowledge them somewhere...)


'Method not found: RestSharp.IRestRequest RestSharp.RestRequest.AddFile' dependency issue

Integrating our application with the Docusign API and I keep receiving this issue when trying to send a individual document from our application. Here is the trace that I receive the error from:
    string accountId = loginApi(username, password, integratorKey);
Then in the loginAPI method:
        LoginInformation loginInfo = authApi.Login();
calling this method returns the error seen in the title.
We are using these packages:
Docusign.esign.DLL V2.1.8
RestSharp v106.1.0
RestSharpSigned v105.2.3
BouncyCastle v1.8.1
All the dependencies match for the Docusign API package but I'm not sure if having both RestSharp and RestSharpSigned may be confusing the LoginAPI method to call the correct method since Docusign uses RestSharpSigned. Anybody else encounter this issue?

Why is this issue closed?  This is still broken!

re-opened.

@all, @Cloudmersive , @leoseccia    What is the best description of this issue?
"The C# SDK is using RestSharpSigned but it's older than the current RestSharp and doesn't include RestSharp.RestRequest.AddFile" or something different?
Please provide a concise explanation of the issue and suggested fix.
Thanks,
Larry

I believe the problem is that the DocuSign SDK depends on the RestSharpSigned nuget package which has been obsoleted.  According to the RestSharp GitHub page:

The RestSharp package is now signed so there is no need to install RestSharp.Signed, which is obsolete from v106.0.0.

The DocuSign nuget package should be updated to depend upon the RestSharp package instead.  The latest version is currently 106.6.10.  Perhaps DocuSign should require v106.0.0 or higher?  My guess is that there are some breaking changes that will need to be fixed in the DocuSign SDK to work with v106 (which explains the method not found error).

Thank you @mattscully, I have filed internal DS ticket DCM-3465 to have the library updated.

We have upgraded restsharp dependency with https://www.nuget.org/packages/DocuSign.eSign.dll/4.1.0-rc

@all, please try the RC (release candidate) of the SDK: v4.1.0-rc to check that the issue has been solved for you. Thank you.

Resolved with https://www.nuget.org/packages/DocuSign.eSign.dll/4.1.0


Have conflict with CSS framework bulma, sticky invalid

When using both bulma and Metro-UI-CSS, the style of position:sticky becomes invalid.
Sample Code, the button can not stick on.
<head>
    <link rel="stylesheet"<EMAIL_ADDRESS>    <link rel="stylesheet" href="https://cdn.metroui.org.ua/v4.3.2/css/metro-all.min.css">
</head>
<body  style="height: 2000px;">
    <button style="position: sticky; top: 20px;"> test </button>
</body>

Also conflict with a minority framework nicepage

Your question is not clear!

Your question is not clear!

Why sticky becomes invalid?

Create an example on codepen.io with your issue.

https://codepen.io/benben233/pen/bGoEZLW
Only if you delete one stylesheet link, the button becomes sticky

Create an example on codepen.io with your issue.

add style
body {
  overflow-x: none;
}


code refactoring to improve readability and quality

refactor(Db_Controller): rename method/variable
refactor(Db_Controller): Extract method
refactor(DatabaseManager,DatabaseUtils): Introduce explaining variable
refactor(DatabaseUtils,FileUtils): move method
refactor(CommonBottomSheetManager): Extract class
refactor(DatabaseManager,DatabaseUtils): Pull-up Variable/Method

What do you think about this, @theftzoku?

What do you think about this, @theftzoku?

yeah, these things i mentioned already and also need focus on Database structure.

What do you think about this, @theftzoku?

yeah, these things i mentioned already and also need focus on Database structure.

Thanks for checking. 👍

Thanks for your help, @jeeljasani! 😘


Is SF remote debugging still not supported in VS2022?

According to these docs, remote debugging is not supported in Visual Studio 2022.  Is that still correct?

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

ID: e8adfa1c-0bb9-c112-3463-0d655a3e7cd1
Version Independent ID: ef09b17d-cebf-56ca-7f59-71dba2dc3123
Content: Debug your application in Visual Studio - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-debugging-your-application.md
Service: service-fabric
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@jemeese
Thanks for your Question! We are currently investigating and will get back on this.

@jemeese
I'm sorry, but the document you provided does not mention Visual Studio 2022. However, in general, remote debugging is supported in Visual Studio 2022.Here is the link to the official Microsoft documentation on remote debugging in Visual Studio 2022.
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2022
This document provides detailed information on how to set up and use remote debugging in Visual Studio 2022.
If you have any specific questions or issues related to remote debugging in Visual Studio 2022, please let me know and I'll do my best to help you.

It does actually:
Debug your application in Visual Studio - Azure Service Fabric | Microsoft Learnhttps://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-debugging-your-application
[A blue and white sign  Description automatically generated]
Perhaps an old version is still published and you're seeing a newer one?
From: AjayBathini-MSFT @.>
Sent: Monday, August 7, 2023 11:12 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Jeremy Meese @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Is SF remote debugging still not supported in VS2022? (Issue #113294)
@jemeesehttps://github.com/jemeese
I'm sorry, but the document you provided does not mention Visual Studio 2022. However, in general, remote debugging is supported in Visual Studio 2022.Here is the link to the official Microsoft documentation on remote debugging in Visual Studio 2022.
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2022
This document provides detailed information on how to set up and use remote debugging in Visual Studio 2022.
If you have any specific questions or issues related to remote debugging in Visual Studio 2022, please let me know and I'll do my best to help you.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/113294#issuecomment-1668967847, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOA3G2BUCYQQCMLL6GISZ3DXUHKDPANCNFSM6AAAAAA3HTYZZI.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@jemeese
Thanks for bringing this to our attention. I will work with author @tomvcassidy and remove old version the document.
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


feat: add Client class

This reduces the amount of configuration repetition when using this module. As seen in the README changes, this is particularly helpful when setting one's custom cookie settings.
Previously, I was against using classes in this codebase. However, now, this appears to be net positive.

This reduces the amount of configuration repetition when using this module.

I agree that reducing repetition of config is useful.

Previously, I was against using classes in this codebase.

How about considering higher order function type API. For example,
const {
  signIn,
  signOut,
  handleCallback,
  getSessionId,
} = createHandlers(oauthConfig, options) // or maybe useOAuth(config, options)?

By this design, the users can't modify the config or options after once they are created, which prevents unintentional abuse/misuse of the API

This reduces the amount of configuration repetition when using this module.

I agree that reducing repetition of config is useful.

Previously, I was against using classes in this codebase.

How about considering higher order function type API. For example,
const {
  signIn,
  signOut,
  handleCallback,
  getSessionId,
} = createHandlers(oauthConfig, options) // or maybe useOAuth(config, options)?

By this design, the users can't modify the config or options after once they are created, which prevents unintentional abuse/misuse of the API

Great idea! I'll try that in a separate PR to compare the two.

Closing in favour of #255.


c++core: rename read/write to read_csr/write_csr

Rename csr read/write functions in handle class to read_csr and
write_csr to be more explicit in the operation and specify that the
functions are operating on CSRs. This is a template function where the
template argument specifies the register size (uint32_t or uint64_t for
32-bit or 64-bit respectively).
Update samples to use updated API functions.

I'm actually a big fan of generic programming using templates and have had over ten years experience developing software with C++. Now in this case, the use of templates doesn't really accomplish any sort of generic programming (as you can see with the default implementation of the functions).
When @luebbers, @tswhison, and I discussed this, we considered first using function names like you have suggested. In the end, however, we made the decision to use template arguments to encode the type of the variable  (which infers the register size).

I tend to agree with Michael - templates are useful constructs for places where we expect new (and possibly yet unknown types) to be used; I understand that they would be used to work with any type supporting operations that the templated functions perform.
Here, we only care about different sizes of the argument (we don't really care about or interpret their type at all), so it appears that templates don't add any real value, especially if the underlying hardware limits the selection of valid sizes (32 bit and 64 bit for now).


[W6.1d][T10-B1]Xiang Hailin

@Hailinx Some comments added. Please close the PR after reading comments.


Export transforms

Should be a pretty easy change.  When outputting the transform for an object we should export a transform with that name:
ri.CoordinateSystem ( obj.name)

I'll take care of this today.

Ok done.


Now that USDB supports UTF8, the fixing of encodings is obsolete.

Sad to see this code go, it was a fantastic addition to the Syncer. At the same time I am happy about the upgrades in USDB.


Listener container properties for batch receive.

Acknowledgment API cleanup.

Closed via https://github.com/spring-projects-experimental/spring-pulsar/commit/eef1616aecfea9f01b1a7dce096b3ae5a53fc7c7


Docker file needs comments

I read a blog recently that said that all docker files should contain comments. Can you update the docker file with proper comments please.

Haha


replacement-pairs fail at end of word

It seems replacement pairs, at least when of different length, fail at the end of a word. E.g. "Fux" doesn't suggest "Fuchs" even with fsa.dict.speller.replacement-pairs=x chs. Adding two more characters at the end of the word makes it work (i.e. Fuxee suggests Fuchsee, both are fantasy words).
I've added a stand-alone example here in LanguageTool: https://github.com/languagetool-org/languagetool/blob/6d38df7eda58bfc6b796d91e35fc7debda57f7d5/languagetool-language-modules/de/src/test/java/org/languagetool/rules/de/GermanSpellerRuleTest.java#L369
Maybe this is related to this comment. If this is actually a bug and won't be fixed, it should be documented.

It is probably related to the previous bug you mention. I will take a look, but I foresee it will be difficult to fix.

This fixes the problem. There is no reason not to try replacements in short words.

(Released the fix in 2.1.4)


Discussion: New UI and A11y WG facilitator

As @aghassemi leaves the WG, we need to assign a new WG facilitator.
There is no process for changing the WG Facilitator in our Governance documentation but I have filed an issue here: https://github.com/ampproject/meta-tsc/issues/16
Creating this issue to do the change in the public.

Looks like the TSC agrees. ampproject/meta#39
Let's start taking the next steps.

I want to propose myself as the new facilitator of the WG.
My credentials: I work as the PM on the UI Working Group, this means I am often facilitating scoping of components, working with engineers and designers on implementation and tracking the launch of the product.
Happy to field any questions/concerns.
cc @aghassemi who is the outgoing facilitator to facilitate one last issue for the WG.

@nainar would be a great facilitator for this WG. :100: gets my vote.


Reland "Remove references to BindingBase.window (#122119 & #122341)"

Relands https://github.com/flutter/flutter/pull/122119.
Relands https://github.com/flutter/flutter/pull/122341.
Partial revert of https://github.com/flutter/flutter/pull/122369.
~Blocked on reland of https://github.com/flutter/flutter/pull/122233.~

Do not submit until https://github.com/flutter/flutter/pull/122422 trickled through FROB.


containerd switching to HTTPS for HTTP registry after failed HEAD request

Description
(I am seeing this problem with containerd 1.2.5 bundled with microk8s 1.17 snap. I realise this is not latest code, but I'm reporting it here as I can't find a github issue mentioning it before. I'm also not 100% sure if this is containerd or microk8s issue.)
The problem: when k8s+containerd is configured to use HTTP to a repository, and you try to fetch an image where the tag does not exist, it makes an initial HTTP HEAD request then switches to using HTTPS, and barfs when it sees a HTTP response.
However it works correctly (using HTTP) if the tag does exist.
Steps to reproduce the issue:

Create an insecure http docker registry.  I did microk8s.enable registry which gives an registry on <IP_ADDRESS>:32000.
(Aside: don't refer to this as localhost:32000, because connections to [::1]:32000 hang - although k8s opens a multi-protocol socket to reserve the port, it only configures iptables to forward IPv4)

Configure containerd to use http for this registry.  I added the following to /var/snap/microk8s/current/args/containerd-template.toml
[plugins.cri.registry.mirrors."<IP_ADDRESS>:32000"]
  endpoint = ["http://<IP_ADDRESS>:32000"]

and then snap restart microk8s.daemon-containerd

Push an image to this registry with a particular tag: I used kafka:develop
To confirm: the repository exists, here it has tags "develop" and "DEV", but no others.
$ curl <IP_ADDRESS>:32000/v2/_catalog
{"repositories":["kafka"]}
$ curl <IP_ADDRESS>:32000/v2/kafka/tags/list
{"name":"kafka","tags":["develop","DEV"]}

Configure kubernetes to pull an image with a non-existent tag.
...
    spec:
      containers:
      - name: ten
        image: <IP_ADDRESS>:32000/kafka:NONEXISTENT
...

Describe the results you received:
kubectl describe pod says:
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  4m52s                  default-scheduler  Successfully assigned default/dep-test-0-57db5999c6-b8xlh to vagrant
  Normal   BackOff    4m48s (x2 over 4m49s)  kubelet, vagrant   Back-off pulling image "<IP_ADDRESS>:32000/kafka:NONEXISTENT"
  Normal   BackOff    4m48s                  kubelet, vagrant   Back-off pulling image "<IP_ADDRESS>:32000/kafka:NONEXISTENT"
  Warning  Failed     4m48s                  kubelet, vagrant   Error: ImagePullBackOff
  Normal   Pulling    4m34s (x2 over 4m49s)  kubelet, vagrant   Pulling image "<IP_ADDRESS>:32000/kafka:NONEXISTENT"
  Warning  Failed     4m34s (x2 over 4m49s)  kubelet, vagrant   Error: ErrImagePull
  Normal   BackOff    4m34s (x3 over 4m49s)  kubelet, vagrant   Back-off pulling image "<IP_ADDRESS>:32000/kafka:NONEXISTENT"
  Warning  Failed     4m34s (x3 over 4m49s)  kubelet, vagrant   Error: ImagePullBackOff
  Warning  Failed     4m34s (x2 over 4m49s)  kubelet, vagrant   Failed to pull image "<IP_ADDRESS>:32000/kafka:NONEXISTENT": rpc error: code = Unknown desc = failed to resolve image "<IP_ADDRESS>:32000/kafka:NONEXISTENT": no available registry endpoint: failed to do request: Head "https://<IP_ADDRESS>:32000/v2/kafka/manifests/NONEXISTENT": http: server gave HTTP response to HTTPS client
  Warning  Failed     4m34s (x3 over 4m49s)  kubelet, vagrant   Error: ImagePullBackOff
  Normal   BackOff    4m34s (x3 over 4m49s)  kubelet, vagrant   Back-off pulling image "<IP_ADDRESS>:32000/kafka:NONEXISTENT"
  Warning  Failed     4m34s (x3 over 4m49s)  kubelet, vagrant   Error: ImagePullBackOff

Th error "http: server gave HTTP response to HTTPS client"  had me scratching my head as I was 100% sure I'd configured containerd to use http for <IP_ADDRESS>:32000 (and indeed it had worked before, with a valid tag)
The problem became clearer by running strace -s 256 -f -p <pid> on the containerd process:
[pid 25594] 09:26:05.454114 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.454254 write(26, "HEAD /v2/kafka/manifests/NONEXISTENT HTTP/1.1\r\nHost: <IP_ADDRESS>:32000\r\nUser-Agent: Go-http-client/1.1\
r\nAccept: application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.
image.manifes"..., 313) = 313
strace: Process 25605 attached
strace: Process 25604 attached
[pid 25599] 09:26:05.466085 mprotect(0x7f59123bc000, 4096, PROT_READ <unfinished ...>
[pid 25598] 09:26:05.466105 <... read resumed> "900 27 0:205 / /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v1.linux/k8s.io/15
b62f5b42c40474bc0c4e16ee71553cd09d51baa6ba145f44ac1a809a205f90/rootfs rw,relatime shared:262 - overlay overlay rw,lowerdir=/var/snap/microk8s/co
mmon/var/lib/con"..., 1466) = 1466
[pid 25594] 09:26:05.466123 <... nanosleep resumed> NULL) = 0
[pid 25587] 09:26:05.466134 <... nanosleep resumed> NULL) = 0
[pid 10945] 09:26:05.466146 write(13, "\0\0\10\6\1\0\0\0\0\2\4\20\20\t\16\7\7\0\0\4\10\0\0\0\0\0\0\0\2\345\0\0\10\6\0\0\0\0\0\2\4\20\20\t\16\7\7
", 47 <unfinished ...>
[pid  2952] 09:26:05.466172 <... nanosleep resumed> NULL) = 0
[pid 25594] 09:26:05.467864 epoll_pwait(5,  <unfinished ...>
[pid 25587] 09:26:05.467916 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.467950 epoll_pwait(4,  <unfinished ...>
[pid 25605] 09:26:05.468432 set_robust_list(0x7f8c2f7fe9e0, 24 <unfinished ...>
[pid 25604] 09:26:05.468453 gettid( <unfinished ...>
[pid 25599] 09:26:05.468464 <... mprotect resumed> ) = 0
[pid 25598] 09:26:05.468473 read(8,  <unfinished ...>
[pid 25594] 09:26:05.468484 <... epoll_pwait resumed> [], 128, 0, NULL,<PHONE_NUMBER>931) = 0
[pid 25587] 09:26:05.468494 <... nanosleep resumed> NULL) = 0
[pid 10945] 09:26:05.468509 <... write resumed> ) = 47
[pid  2952] 09:26:05.468532 <... epoll_pwait resumed> [{EPOLLIN|EPOLLOUT, {u32=2275430040, u64=140460590911128}}], 128, 0, NULL,<PHONE_NUMBER>580)
= 1
[pid 25598] 09:26:05.469025 <... read resumed> "erlayfs/snapshots/1/fs,upperdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snaps
hotter.v1.overlayfs/snapshots/353/fs,workdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/353/w
ork\n915 27 0:221"..., 16384) = 3826
[pid 25594] 09:26:05.469128 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25587] 09:26:05.469242 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.469263 read(26,  <unfinished ...>
[pid  2952] 09:26:05.469291 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25598] 09:26:05.469830 read(8,  <unfinished ...>
[pid 25594] 09:26:05.469851 <... nanosleep resumed> NULL) = 0
[pid 25587] 09:26:05.469863 <... nanosleep resumed> NULL) = 0
[pid 10945] 09:26:05.469872 <... read resumed> "HTTP/1.1 404 Not Found\r\nContent-Type: application/json; charset=utf-8\r\nDocker-Distribution-Api-Version: registry/2.0\r\nX-Content-Type-Options: nosniff\r\nDate: Fri, 03 Apr 2020 09:26:05 GMT\r\nContent-Length: 101\r\n\r\n", 4096) = 211
[pid  2952] 09:26:05.469892 <... nanosleep resumed> NULL) = 0
[pid 25587] 09:26:05.472207 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25594] 09:26:05.472263 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.472314 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.472394 read(26, 0xc0008fb000, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[pid 10945] 09:26:05.472577 socket(AF_INET, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 16
[pid 10945] 09:26:05.472629 setsockopt(16, SOL_SOCKET, SO_BROADCAST, [1], 4) = 0
[pid 10945] 09:26:05.472667 connect(16, {sa_family=AF_INET, sin_port=htons(32000), sin_addr=inet_addr("<IP_ADDRESS>")}, 16 <unfinished ...>
[pid 25594] 09:26:05.476022 <... nanosleep resumed> NULL) = 0
[pid 25587] 09:26:05.476071 <... nanosleep resumed> NULL) = 0
[pid 25594] 09:26:05.476101 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25587] 09:26:05.476138 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.476177 <... nanosleep resumed> NULL) = 0
[pid  2952] 09:26:05.476204 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.476233 <... connect resumed> ) = -1 EINPROGRESS (Operation now in progress)
[pid 10945] 09:26:05.476262 epoll_ctl(4, EPOLL_CTL_ADD, 16, {EPOLLIN|EPOLLOUT|EPOLLRDHUP|EPOLLET, {u32=1549992776, u64=140459865473864}}) = 0
[pid 10945] 09:26:05.476325 epoll_pwait(4, [{EPOLLIN, {u32=2275428920, u64=140460590910008}}, {EPOLLIN, {u32=2275428024, u64=140460590909112}}, {EPOLLIN|EPOLLOUT, {u32=2275228840, u64=140460590709928}}, {EPOLLOUT, {u32=1549992776, u64=140459865473864}}], 128, 0, NULL,<PHONE_NUMBER>039) = 4
[pid 25587] 09:26:05.476515 <... nanosleep resumed> NULL) = 0
[pid 25594] 09:26:05.476545 <... nanosleep resumed> NULL) = 0
[pid 25594] 09:26:05.476564 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25587] 09:26:05.476591 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.476620 <... nanosleep resumed> NULL) = 0
[pid  2952] 09:26:05.476639 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.476666 getsockopt(16, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
[pid 10945] 09:26:05.476702 getpeername(16, {sa_family=AF_INET, sin_port=htons(32000), sin_addr=inet_addr("<IP_ADDRESS>")}, [112->16]) = 0
[pid 10945] 09:26:05.476746 getsockname(16, {sa_family=AF_INET, sin_port=htons(53630), sin_addr=inet_addr("<IP_ADDRESS>")}, [112->16]) = 0
[pid 10945] 09:26:05.476786 setsockopt(16, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid 10945] 09:26:05.476818 setsockopt(16, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
[pid 10945] 09:26:05.476846 setsockopt(16, SOL_TCP, TCP_KEEPINTVL, [30], 4) = 0
[pid 10945] 09:26:05.476873 setsockopt(16, SOL_TCP, TCP_KEEPIDLE, [30], 4) = 0
[pid 10945] 09:26:05.476943 getrandom( <unfinished ...>
[pid 25594] 09:26:05.477085 <... nanosleep resumed> NULL) = 0
[pid 25587] 09:26:05.477107 <... nanosleep resumed> NULL) = 0
[pid 25594] 09:26:05.477127 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25587] 09:26:05.477155 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.477190 <... nanosleep resumed> NULL) = 0
[pid  2952] 09:26:05.477210 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.477235 <... getrandom resumed> "\xa4\x2b\x3a\x80\x2d\xb2\xcf\x04\xab\xe4\xa8\xc6\x3b\xc5\x8c\xb5\x34\x2a\xa2\xa1\x3d\x66\xef\x9c\xed\xdd\x2e\x64\xfc\x79\x7c\x83", 32, 0) = 32
[pid 10945] 09:26:05.477256 getrandom("\x51\x9c\xe9\x48\x4e\x88\xbd\xc4\xfd\x30\x7c\xd6\xc2\x13\x2f\x49\xfb\x93\x8f\x70\xbf\xfc\xf9\x80\xd3\x60\x8f\xed\x36\xe1\xbf\x9f", 32, 0) = 32
[pid 25598] 09:26:05.477353 <... read resumed> "1098 27 0:273 / /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v1.linux/k8s.io/ec9335221f36a9f6a8b854141634431226a884ff47d1e3777aa8660c478af2b7/rootfs rw,relatime shared:286 - overlay overlay rw,lowerdir=/var/snap/microk8s/common/var/lib/co"..., 12558) = 2113
[pid 10945] 09:26:05.477370 getrandom("\xaa\x7b\x8a\xf1\xa9\xc5\xa7\x09\xf2\xd8\xe3\x57\x4f\xda\x99\xeb\x8a\xef\x3e\x75\xa6\xa8\x52\xf9\xe3\x10\xb2\x60\x14\x7e\x90\xe3", 32, 0) = 32
[pid 10945] 09:26:05.477465 write(16, "\26\3\1\1\0\1\0\0\374\3\3\244+:\200-\262\317\4\253\344\250\306;\305\214\2654*\242\241=f\357\234\355\335.d\374y|\203 Q\234\351HN\210\275\304\3750|\326\302\23/I\373\223\217p\277\374\371\200\323`\217\3556\341\277\237\0&\300/\3000\300+\300,\314\250\314\251\300\23\300\t\300\24\300\n\0\234\0\235\0/\0005\300\22\0\n\23\1\23\3\23\2\1\0\0\215\0\5\0\5\1\0\0\0\0\0\n\0\n\0\10\0\35\0\27\0\30\0\31\0\v\0\2\1\0\0\r\0\32\0\30\10\4\4\3\10\7\10\5\10\6\4\1\5\1\6\1\5\3\6\3\2\1\2\3\377\1\0\1\0\0\20\0\16\0\f\2h2\10http/1.1\0\22\0\0\0+\0\t\10\3\4\3\3\3\2\3\1\0003\0&\0$\0\35\0 \3527\201\231\354B\24\376\2137\317\37[\3229\222n\350\260\0274\36\254\2562\257\313"..., 261 <unfinished ...>
[pid 25598] 09:26:05.477498 read(8, "1058 27 0:307 / /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v1.linux/k8s.io/415433ef1b68bd9cd187f60cf4d70dedc9d8208c7859f5ccee10e363437f5917/rootfs rw,relatime shared:295 - overlay overlay rw,lowerdir=/var/snap/microk8s/common/var/lib/co"..., 10445) = 2053
[pid 25594] 09:26:05.479095 <... nanosleep resumed> NULL) = 0
[pid  2952] 09:26:05.479142 <... nanosleep resumed> NULL) = 0
[pid 25599] 09:26:05.480887 mprotect(0x55b6d9058000, 3067904, PROT_READ <unfinished ...>
[pid 25598] 09:26:05.480936 read(8,  <unfinished ...>
[pid 25594] 09:26:05.480953 epoll_pwait(5,  <unfinished ...>
[pid 25587] 09:26:05.480968 <... nanosleep resumed> NULL) = 0
[pid 10945] 09:26:05.480981 <... write resumed> ) = 261
[pid  2952] 09:26:05.481001 epoll_pwait(4,  <unfinished ...>
[pid 25594] 09:26:05.483059 <... epoll_pwait resumed> [], 128, 0, NULL,<PHONE_NUMBER>824) = 0
[pid  2952] 09:26:05.483101 <... epoll_pwait resumed> [{EPOLLIN|EPOLLOUT|EPOLLRDHUP, {u32=1549992776, u64=140459865473864}}], 128, 0, NULL,<PHONE_NUMBER>632) = 1
[pid 25594] 09:26:05.483133 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid  2952] 09:26:05.483164 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 25587] 09:26:05.483204 nanosleep({tv_sec=0, tv_nsec=20000},  <unfinished ...>
[pid 10945] 09:26:05.483250 read(16, "HTTP/1.1 400 Bad Request\r\nContent-Type: text/plain; charset=utf-8\r\nConnection: close\r\n\r\n400 Bad Request", 517) = 103
[pid 10945] 09:26:05.483308 epoll_ctl(4, EPOLL_CTL_DEL, 16, 0xc000c19614) = 0
[pid 10945] 09:26:05.483339 close(16)   = 0
[pid 25598] 09:26:05.483488 <... read resumed> "1217 27 0:331 / /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v1.linux/k8s.io/c
aa31a564a1df9712704713e8733497977b46e295adfc477a5a8b9d92565922d/rootfs rw,relatime shared:298 - overlay overlay rw,lowerdir=/var/snap/microk8s/common/var/lib/co"..., 8392) = 2053
[pid 10945] 09:26:05.483583 write(2, "time=\"2020-04-03T09:26:05.483561499Z\" level=error msg=\"PullImage \"<IP_ADDRESS>:32000/kafka:NONEXISTENT\" failed\" error=\"failed to resolve image \"<IP_ADDRESS>:32000/kafka:NONEXISTENT\": no available registry endpoint: failed to do request: Head \"https://<IP_ADDRESS>:3"..., 344 <unfinished ...>
[pid 25598] 09:26:05.483615 read(8, "1263 27 0:355 / /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v1.linux/k8s.io/e8d180ca3b205a72e95b4c3ae0b018542e38b4bd4b00680a380dbbe2e2d9c014/rootfs rw,relatime shared:301 - overlay overlay rw,lowerdir=/var/snap/microk8s/common/var/lib/co"..., 6339) = 2053

I can see:

There is an initial plain HTTP request of HEAD /v2/kafka/manifests/NONEXISTENT
This is correctly answered with HTTP/1.1 404 Not Found
Containerd makes a new connection (fd 16)
It sends a splurge of SSL, and the registry responds with HTTP/1.1 400 Bad Request

Note: if I reference a tag which exists, the container comes up correctly.  So clearly it is able to communicate with the registry over http, if the tag exists.
Describe the results you expected:

To get an error saying that the requested tag does not exist
NOT to see any https attempts to a registry configured for http

Output of containerd --version:
$ /snap/microk8s/current/bin/containerd --version
containerd github.com/containerd/containerd v1.2.5 bb71b10fd8f58240ca47fbb579b9d1028eea7c84
$ microk8s.ctr --version
ctr github.com/containerd/containerd v1.2.5

Any other relevant information:
I then tried to reproduce using ctr without kubernetes, but was unable to.
Without --plain-http flag, ctr is making requests over https (ignoring the setting in configuration.toml):
$ microk8s.ctr --address /var/snap/microk8s/common/run/containerd.sock i pull <IP_ADDRESS>:32000/kafka:NONEXISTENT
ctr: failed to resolve reference "<IP_ADDRESS>:32000/kafka:NONEXISTENT": failed to do request: Head "https://<IP_ADDRESS>:32000/v2/kafka/manifests/NONEXISTENT": http: server gave HTTP response to HTTPS client
$ microk8s.ctr --address /var/snap/microk8s/common/run/containerd.sock i pull <IP_ADDRESS>:32000/kafka:develop
ctr: failed to resolve reference "<IP_ADDRESS>:32000/kafka:develop": failed to do request: Head "https://<IP_ADDRESS>:32000/v2/kafka/manifests/develop": http: server gave HTTP response to HTTPS client

And with --plain-http flag, I get the correct response for both non-existent and valid tags:
$ microk8s.ctr --address /var/snap/microk8s/common/run/containerd.sock image pull <IP_ADDRESS>:32000/kafka:NONEXISTENT --plain-http
ctr: failed to resolve reference "<IP_ADDRESS>:32000/kafka:NONEXISTENT": <IP_ADDRESS>:32000/kafka:NONEXISTENT not found
$ microk8s.ctr --address /var/snap/microk8s/common/run/containerd.sock image pull <IP_ADDRESS>:32000/kafka:develop --plain-http
<IP_ADDRESS>:32000/kafka:develop:                                                    resolved       |++++++++++++++++++++++++++++++++++++++|
...

This makes me wonder that it might not be a containerd issue at all, but something to do with kubernetes.  But I can see from strace it's definitely containerd which is attempting to make the HTTPS connection to the registry.

Hey, the cri-containerd will use your mirror settings to retrieve data first. For your case, if the tag is NONEXISTENT, it means that your mirror settings is wrong and cri-containerd will fallback to use default setting which uses https for request.
I don't think it is bug and just please make sure your image is correct. :)

OK, I think I understand: "mirrors" doesn't configure the URL for a repository, but a different URL to try first.
Is there a better way to tell containerd "<IP_ADDRESS>:32000 is the authoritative source, and by the way, it always uses http?"
I note that containerd 1.3.0+ has per-registry tls settings such as
[plugins.cri.registry.configs."foo.example.net:5000".tls]
  ca_file = /etc/foo.crt

But I couldn't find one that says "don't use TLS"

@candlerb https is by default for registry. The mirror setting is to allow user to setting up insecure request (http).
[plugins.cri.registry.mirrors."foo.com"]
  endpoints = ["http://<IP_ADDRESS>:32000"]

For your case, it is just non-found image which makes cri-containerd to file other request to fetch image. It might confuse us when we read the error. But I think it is acceptable :P

I don't think this behaviour is very good.
Containerd treats a 404 as "contact the origin again using HTTPS".  Therefore, instead of simply returning "this image does not exist", it returns an error about a HTTPS server returning a HTTP result, which is confusing, and makes a simple problem hard to debug.
Suppose the registry returned some other 4xx or 5xx error, like a permissions problem.  Would these also cause containerd to fall through and re-contact the server on HTTPS?  That could mask the useful error message.
If I understand correctly, containerd has a hard-coded assumption that a registry named "foo.bar:8080" can always be contacted at  endpoint https://foo.bar:8080/... (after trying mirrors), and I don't think that's necessarily true.  You might not want this to happen for other reasons - e.g. if you've mapped docker.io to a local mirror, but you never want a connection to be made to the real docker.io

Configure kubernetes to pull an image with a non-existent tag.
image: <IP_ADDRESS>:32000/kafka:NONEXISTENT

Perhaps I don't understand, but if you're referring the image as <IP_ADDRESS>:32000/kafka:xxx, should it be configured as a mirror? Wouldn't a mirror only be configured if you (e.g.) want to pull docker.io/library/foo but are mirroring the content on a local registry? So when pulling docker.io/library/foo:latest, instead it should try to pull <IP_ADDRESS>:32000/library/foo:latest ?

Perhaps I don't understand, but if you're referring the image as <IP_ADDRESS>:32000/kafka:xxx, should it be configured as a mirror?

Is there another way?
The Kubernetes deployment contains:
image: <IP_ADDRESS>:32000/kafka:TEST

but if I don't configure a mirror, I can't see a way to tell containerd to use HTTP rather than HTTPS.

Hi all,
Facing the same issue in managed Kubernetes clusters (IBM-IKS), we would not have access to ssh into the worker nodes in IBM Cloud to edit the containerd config.toml file, kindly please look into the issue and provide use a suitable solution for the same.

We are not facing this issue in Kubernetes clusters running with CRI-O as the container runtime(Openshift clusters).
This is impeding our development process and also a few production cluster using containerd such as IBM-IKS, please suggest a fix for the issue ASAP.

Please open an issue with IBM support. this is not the right forum for IBM-IKS @tejasrao97

@dims Yeah I have opened an issue with the IBM support team. We are not facing this issue only in IBM-IKS, all the Kubernetes cluster that's using containerd as it's container runtime are facing this issue.
Most of the kubernetes clusters in production (other than IBM-IKS) are using docker as it's container runtime, but in the upcoming kubernetes Version (v1.20) docker would be deprecated.
The kubernetes documentation says that we can either use containerd or CRI-O as the container runtime. We have tried running CRI-O as the container runtime and we are not facing this issue, because the CRI-O runtime isn't pulling images present on local mirror registry through https by default.
Can you please help us understand why only containerd is configured to pull images through https even for a local mirror registry for which the request isn't going through the internet, but infact it's resolving locally inside kubernetes node network , is there any specific reason for it talk only on https even with a local mirror registry.

@tejasrao97 i believe your team mate started the same conversation in slack? see https://cloud-native.slack.com/archives/CGEQHPYF4/p1607343391141900

Ohh okay, will have a look at the thread, thank you! :)

hello I have the same issue when pull image from harbor use http. Even I configured insecure_skip_verify = true. containerd is 1.4.3.
some one can help?  thanks

hello I have the same issue when pull image from harbor use http. Even I configured insecure_skip_verify = true. containerd is 1.4.3.
I thins the configuration is ineffective in config.yml. when I use ctr --debug image pull -u admin:Harbor12345 --plain-http 10.XXX ,that is ok. some one can help? thanks

the .cri config is only for CRI enabled clients .. CTR is not a CRI enabled client.  You should be able to use kubectl,  crictl, or other CRI enabled clients.  We may address this issue in upcoming releases. Cheers.

please follow Registry Configuration - Examples , https://github.com/containerd/containerd/blob/release/1.5/docs/hosts.md


Failed to create instances and VR

ISSUE TYPE
Bug Report
COMPONENT NAME
VR
CLOUDSTACK VERSION
4.17.10
CONFIGURATION
basic network
OS / ENVIRONMENT
Centos8.5
SUMMARY
VR can't start
STEPS TO REPRODUCE

The following is the management log：

I found out by looking at the system virtual machine：
Command 'nft list tables ip6 | grep ip6_firewall
l' returned non-zero exit status 1
I don't understand what's wrong, hope to get your help, thank you
EXPECTED RESULTS
Instances and VR can be created successfully
ACTUAL RESULTS
Failed to create instances and VR
Looking forward to your reply~~~

@fangyi1008
do you install from official cloudstack packages ?
do you use official systemvm template ?

do you install from official cloudstack packages ?
do you use official systemvm template ?

Yes, I downloaded the package and template from the official, otherwise the system virtual machine would not be able to start successfully. It's that instancing and VR keeps failing.

that's strange. I have created a Basic zone, everything looks good.
can you double check the cloudstack version on management server and centos hosts ? please also check the /etc/cloudstack-release in the system vms.

OK, I'll check it out on Monday. Should be all right. At that time, they were all official download packages. Create an instance using the ubuntu-14.04.6-server-amd64.iso file uploaded by yourself.
thanks.
Get back to you next Monday and have a great weekend.

@fangyi1008
any update on this issue ?

@fangyi1008 any update on this issue ?

Feel sorry. I have been busy with other things recently and have not responded to you. I have checked everything and there is no problem. I really don't know where the problem is

@fangyi1008
does the issue still exist ?

Yes, temporarily give up processing.

this seems to be caused by host error
the host should be Up and Enabled.
@fangyi1008
I am closing this ticket, please feel free to reopen it if you still face the problem


[YUNIKORN-317] cache removal design doc

Adding the design doc for the cache removal implemented in YUNIKORN-317
Small side changes to clean up build and files:
Change to slug to define docs home
Removal of unused files (atom and doap)
Removal of unicode line separator chars (LSEP, U+2028)
Clean up of build script tabs

The core design doc needs a full rewrite. All that is there needs to be done from scratch. That is a good amount of work and will follow as a separate change.
I expect that it will take at least 3 days to rewrite it all. There are a number of things in that doc that are not correct anymore.
When we have that done the existing document will be replaced. For now we just have a tag in it to show that it is not current.
Filed YUNIKORN-495 for this

@wilfred-s feel free to merge this with a proper commit message, thank you.

commit pushed, auto build will publish soon.


3X: need to reboot after activating SIM

LTE connections remains at activating until device restarts
comma@tici:/data/openpilot$ nmcli -f GENERAL.STATE con show lte
GENERAL.STATE:                          activating
comma@tici:/data/openpilot$ nmcli -f GENERAL.STATE con show "openpilot connection unifi"
GENERAL.STATE:                          activated

Sep 29 23:46:11 tici ModemManager[3580]: <debug> [1696049171.985025] [modem0] no 3GPP info given...
Sep 29 23:46:11 tici ModemManager[3580]: <debug> [1696049171.985252] [modem0] not yet registered in a 3GPP network... will recheck soon

One of these AT commands got it to register on the network without rebooting:
AT+CFUN=1  # power on radio
AT+CFUN=1,1  # soft reset

LTE works now, but nmcli device returns nothing (edited)

Won't be the case with the new SIMs


Capi support

Towards https://github.com/giantswarm/giantswarm/issues/29151

Oopsie should we revert @QuantumEnigmaa ?

No it's fine :)
This is the working version I tested on glippy :)


feat(#753): Fix The Problem With The First Digit Naming

In this PR I fixed the name genearation strategy for sequences of values. Now all the randomly generated names will start with a letter.
Closes: #753.
History:

feat(#753): do not generate names with the first digit
feat(#753): fix all the code offences

PR-Codex overview
This PR introduces a new feature to generate random names for DirectivesValues, ensuring they do not start with a digit. It also adds a test case to validate this behavior.
Detailed summary

Added a regex pattern DIGITS in DirectivesValues to identify leading digits.
Implemented a randomName() method in DirectivesValues to generate valid random names.
Created a new test method generatesRandomNameWithoutFirstDigit() in DirectivesValuesTest to validate the random name generation.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here.

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 8min).


fix(module:tabs): fix tabs still shows when no route is matched

close #3873
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
When no route is matched, the tabs component would set nzHideAll to true.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@wendzhue The issue is not totally solved, please check #3873 for more information.


(AzureCXP) Fixes MicrosoftDocs/azure-docs-cli#2273

Corrected typo
--
CC: @dbradish-microsoft

Docs Build status updates of commit 7ec8456:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/release-notes-azure-cli.md

Line 766, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 23, 2020''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 2592, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 2978, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4171, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4179, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4345, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4353, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4369, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4377, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 5062, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 5766, Column 0: [Suggestion-sensitive-language] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'
Line 6475, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 23, 2020''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 80567eb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/release-notes-azure-cli.md

Line 774, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 23, 2020''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 2600, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 2986, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4179, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4187, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4353, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4361, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4377, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 4385, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 5070, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 5774, Column 0: [Suggestion-sensitive-language] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'
Line 6483, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 23, 2020''. Each second level heading (H2) in an article must be unique. NOTE: This Suggestion will become a Warning on 1/29/21.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

#sign-off


Fix typos on README.md

This PR fixes some typos on the README.
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[ x ] I acknowledge that all my contributions will be made under the project's license.

Thank you so much for your contribution!  You can read more about it and apply for it here: https://twil.io/hacktoberfest-swag


Add 5th line-sensor for the line-following task

This PR includes the accommodation of the 5th line sensor array which has been recently introduced in the WallE bot for line following task using the tcrt sensors.

Please update the PR with proper commits, @Krishna-13-cyber; you should not commit modifications that you intend to revert in the next commit.

Since #82 achieves the purpose of updating pin_defs.h for LSA, this PR can be closed.
Thank you.


boa build: added a test that uses a variant file

Am I correct in the understanding that the problem is that the source code is somehow missing when building the second variant?

Am I correct in the understanding that the problem is that the source code is somehow missing when building the second variant?

Indeed, recipe and sources are copied only for the first output.


Windows Container support

Does Armada project also support/facilitate Windows Containers?

Armada supports any pod specification, so it should be possible to use it with Kubernetes cluster with windows nodes, and submit jobs with pod specs containing Windows containers.

Thanks for the update

@beingamarnath Thanks for the interest!  Also curious where you're looking to deploy Armada -- we're interested to hear how other people want to use the project.


Shield vulnerability

Hi Team,
We are using bosh version 270.5.0 , stemcell bosh-aws-xen-hvm-ubuntu-xenial-go_agent/456.27  and shield 8.0.11 on stemcell bosh-aws-xen-hvm-ubuntu-xenial-go_agent/621.5.
We recently discovered a vulnerability in our environment pen-test as "SSH Weak Algorithms Supported" in our bosh and shield deployment for port 5444.
Description: We have detected that the remote SSH server is configured to use the Arcfour stream cipher or no cipher at all. RFC 4253 advises against using Arcfour due to an issue with weak keys.
The following weak server-to-client and client-to-server encryption algorithms are supported: arcfour128 arcfour256
The following weak client-to-server encryption algorithms are supported: arcfour128 arcfour256
Can you please let us know how this vulnerability can be removed?
Please suggest.

SHIELD 8.0.11 is 3 years old. Newer versions of SHIELD have since updated the SSH library to not use arcfour ciphers. You'll need to upgrade to at least 8.5.0 to pick up that fix.

Thank for the response. I will update the shield release to this version 8.5.0 first.


Fix template path for header and footer

template path for header/footer changed in version 2 of components causing this bug

Codecov Report

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

@@          Coverage Diff           @@
##           master    #529   +/-   ##
======================================
  Coverage    80.6%   80.6%
======================================
  Files          29      29
  Lines         887     887
  Branches       85      85
======================================
  Hits          715     715
  Misses        142     142
  Partials       30      30

Continue to review full report at Codecov.

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


crash at login

hello i filled everything in settings api key everything and when i bot 1 is logged it crash
https://ctrlv.cz/4SH7

any help please?

please dont close this topic

Please, for God Sake, ask your questions at reddit.com/r/SteamBot, stop spamming.


Feature/payment provider integration

Features included with this PR:

Customer mappings are no longer required. Only the email address is mandatory and validation will take this into consideration. This is also a required field by the gateway API.
Include the option to specify the number of items. If a value is provided, it will multiply the amount specified in the workflow.
Status and Unique ID fields moved out of the customer details scope - they are relevant to be submitted form record, holding the payment status (new, failed, cancelled, ... ) and the transaction ID.

Looks great, as does the video.
I was a little unclear why the user had to select the status and unique Id fields, but I assume it's because you update those in the callback from the payment provider, and then they can see the result in the entries list. Did I understand that right?
Would be good if and when you do another demo recording if you could show that step too (though appreciate it may be difficult to setup locally).

Depending on the outcome of the payment - successful, failed or cancelled, eMerchantPay API sends a notification to the endpoint we are exposing, the record is identified based on the unique ID, and the status of the record is set. In this stage the reconcile action occurs. Locally this cannot be tested, as ngrok doesn't allow the incoming requests from their side.  I will check for their feedback so far, and then install the package on a cloud instance to expose the endpoint publicly.


error-0x8004de40 Article is outdated

https://docs.microsoft.com/en-us/sharepoint/troubleshoot/administration/error-0x8004de40-in-onedrive?ns-enrollment-type=Collection&ns-enrollment-id=bookmarks
The Easy Fix Tool does not work on windows server 2012 R2.

@robinpoulose1 thank you for reaching out and helping to improve Microsoft Docs. Does this article help at all - https://docs.microsoft.com/troubleshoot/windows-server/identity/apps-forcibly-closed-tls-connection-errors


Replace pixl_dcmd setup.py with pyproject.toml

Definition of Done / Acceptance Criteria
pyproject.toml exists in the module root and defines the module and its dependencies.
Testing
Existing tests for pixl_dcmd pass when module is freshly installed.
Documentation
No response
Dependencies
No response
Details and Comments
Other PIXL modules are already using pyproject.toml and the current setup.py contains a circular dependency.

Possibly done due to orthanc working with a specific version of Python, but don't see why it can't be a pyproject.toml

certainly can, required 3.9 because of orthanc docker image having that version of python


Download button is not accessible using the keyboard: A11y_VS Code extension for API Center_Open API Documentation_Download_Keyboard.

GitHub Tags
#A11yTCS; #A11ySev2; #Win32; #WCAG2.1.1; #GH_VSCodeextensionforAPICenter_Win32_Apr2024; #DesktopApp; #VS Code Extension for API Center; #Keyboard; #A11yMAS;
Environment Details:
Application Name: VS Code Extension for API Center
OS: Windows 11 Enterprise 23H2 (OS build 22631.3296)
Repro Steps:

Create an API center in azure portal.
Open Visual studio Code.
Tab till API center extension in the left side panel and press enter.
Tab till definition under the Api name which you have created, and press enter.
The name which you have provided to the definition will appear for ex-"openapi4", right click on it.
Go to "Open API Documentation" using the down arrow and press enter.
Demo conference API screen will appear.
Tab till download button.
Verify whether the download button is accessible using the keyboard or not.

Actual Result:
Download button is not accessible using the keyboard when we are navigating using the tab key.
Expected Result:
Download button should be accessible using the keyboard keys.
User Impact:
keyboard users will not be able to access the button.
Attachment:

@formulahendry Can you please provide us the standalone sample app or Code pen link to route this bug to external team.

IRT Bug logged: https://dev.azure.com/CSS-IRT/CSS IRT/_workitems/edit/222940

Verified the issue in below environment.
Version: 1.88.1 (user setup)
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:41:02.734Z
Issue is fixed. Hence closing the bug
https://github.com/microsoft/vscode-azureapicenter/assets/124244478/6dc733d8-a789-41e7-8e4d-c90f28565a18


Fix null pointer on provides nothing interaction

Codecov Report

Merging #97 into master will decrease coverage by 7.28%.
The diff coverage is 83.87%.

@@            Coverage Diff             @@
##           master      #97      +/-   ##
==========================================
- Coverage    83.1%   75.82%   -7.29%
==========================================
  Files         115      115
  Lines        2468     2713     +245
  Branches      120      123       +3
==========================================
+ Hits         2051     2057       +6
- Misses        417      656     +239

Impacted Files
Coverage Δ

...aas/interaction/http/RemoteInteractionRoutes.scala
0% <0%> (ø)
:arrow_up:

...ker/baas/interaction/RemoteInteractionClient.scala
0% <0%> (ø)
:arrow_up:

.../interations/MethodInteractionImplementation.scala
82.53% <100%> (+0.28%)
:arrow_up:

.../com/ing/baker/runtime/petrinet/TaskProvider.scala
70.21% <88%> (+3.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Use a consistent style of :

[x] I have signed the Contributor License Agreement.
[ ] This pull request is related to an issue.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

As mentioned by @yao-msft in #3250

Files under Localization folder will be overwritten when we do a localization update, so no changes under Localization folder will take effect.


Add a download button for the generated image

If it is valid and working, I will approve the pull request and merge the PR with hacktoberfest-accepted label.

can you assign this task to me i can add download button .

Sure


Update Breaks Google sheets

Hey, Loved the product and have been using it for a while however this newest update has caused me to many issues and I had to unistall. Seems like it is placing a textbox over other textboxes? Works a little wonky on some pages but a major spot that it causes issues is on google sheets. Breaks the functionality to edit cells.

You can just activate it on choosen website , instead of all web site in the extension setting

Disabled extension for the bing website and all other websites except ChatGPT and Anthropic in https://github.com/braden-w/whispering/pull/124 .
Extension is waiting for approval as we speak! Hope this helps. In the meantime, please feel free to disable the extension 🙏 I apologize again for the breakage


check/add for line required for display labels in pro-mini ontology

check/add for line required for display labels in pro-mini ontology

There are 66 terms that don't have a "property_value: pombase_gene_id" line.  Some of them might not need a pombe gene ID, like:
[Term]
id: PR:000005216
name: cell division cycle 5-like protein
def: "A protein that is a translation product of the human CDC5L gene or a 1:1 ortholog thereof." [PRO:DNx]
comment: Category=gene.
synonym: "cdc5-like protein" EXACT []
synonym: "CDC5L" EXACT PRO-short-label [PRO:DNx]
synonym: "KIAA0432" RELATED []
synonym: "PCDC5RP" RELATED []
synonym: "pombe cdc5-related protein" EXACT []
is_a: PR:000000001 ! protein

A lot of entries with a missing pombase_gene_id have a pombe display name like:
synonym: "Rhb1/GTP+" EXACT PomBase_display_name [PomBase:curators]

So it's obvious in those cases what the pombase_gene_id should be.  I'll add the missing pombase_gene_id in the easy cases and then ask for help for the hard cases.

I've managed to add the pombase_gene_id to a lot of the terms.  There are some cases where it's not possible.
There are some complexes where we can't add the gene ID.  Mostly the term names are quite descriptive.  eg.
id: PR:000037318
name: cdc13:cdk1 complex (Schizosaccharomyces pombe)

Maybe the complexes won't appear in extensions anyway?
That cdc13:cdk1 complex doesn't appear to be used in PomBase so we don't have to worry about it.
This is a tricky case because it's the same PRO term for two genes.   But it's a parent term not a modified protein so maybe it wouldn't be used in an extension?  It's a parent term with no child terms so maybe it can be removed.
[Term]
id: PR:Q9UTS8
name: UPF0695 membrane protein C977.11/PB8B6.06c (Schizosaccharomyces pombe 972h-)
def: "A protein that is a translation product of any of the following genes in Schizosaccharomyces pombe 972h-: fex1/fex2." [PRO:DNx, UniProtKB:Q9UTS8]
comment: Category=organism-gene.
synonym: "Spom972h-fex2" EXACT PRO-short-label [PRO:DNx]
xref: UniProtKB:Q9UTS8
is_a: PR:000029043 ! Schizosaccharomyces pombe 972h- protein

Same with this case.  I'm not sure which gene this is.  Maybe it's rpn501 and rpn502?
[Term]
id: PR:Q9UTM3
name: 26S proteasome regulatory subunit rpn5 (Schizosaccharomyces pombe 972h-)
def: "A 26S proteasome non-ATPase regulatory subunit 12 that is encoded in the genome of Schizosaccharomyces pombe 972h-." [OMA:SCHPO02037, PANTHER:PTHR10855\:SF1, PRO:DNx]
comment: Category=organism-gene.
synonym: "Spom972h-PSMD12" EXACT PRO-short-label [PRO:DNx]
xref: UniProtKB:Q9UTM3
is_a: PR:000029043 ! Schizosaccharomyces pombe 972h- protein

Same again, yip11/yip12:
[Term]
id: PR:Q9P347
name: survival of motor neuron protein-interacting protein yip1 (Schizosaccharomyces pombe 972h-)
def: "A protein that is a translation product of any of the following genes in Schizosaccharomyces pombe 972h-: yip11/yip12." [PRO:DNx, UniProtKB:Q9P347]
comment: Category=organism-gene.
synonym: "SMN-interacting protein yip1 (Schizosaccharomyces pombe 972h-)" EXACT [UniProtKB:Q9P347]
synonym: "Spom972h-yip12" EXACT PRO-short-label [PRO:DNx]
synonym: "yab8-interacting protein 1 (Schizosaccharomyces pombe 972h-)" EXACT [UniProtKB:Q9P347]
xref: UniProtKB:Q9P347
is_a: PR:000029043 ! Schizosaccharomyces pombe 972h- protein

I think we can add these problem ones. We don't appear to use them, and they appear to be grouping terms (possibly required by PRO from before uniprot disambiguate duplicate genes)

I'll close this issue because most of them are fixed.  If we see any others on the gene pages we can open a new issue.


scss: suggestions-bg deep-sky-blue for light & dark themes, fix #158

Hi,
With this simple fix for #158 , here are the results:
dark:

light:

NB: I don't know how to compile scss into dist.css, so I did the change manually.

@nim65s A few more tips for getting this across the finish line:

You can rebuild the client-side files as documented here

I think a good way to accomplish this would be to follow the way wagtail does color themes. You may want to copy this mixin verbatim (I don't think we currently have a good way of importing mixins from wagtail):
https://github.com/wagtail/wagtail/blob/997754fe99d248b0e94539bffeb9ec946f5362fb/client/scss/tools/_mixins.general.scss#L119-L129
and then use the CSS variables provided by Wagtail to make our colors match.

Do you think you have the time and ability to work on this further? Happy to help out as you need.

Thanks a lot for your guidance !
I was able to implement this:
dark:

light:


write_term/2 printing issue?

v2.22.22
?- write_term(+A - +B,[max_depth(2)]),nl.
+... - +...

Not sure but other systems(GNU,SWI,eclipse) print + ... - + ...

At least I get different results:
?- write_term_to_chars(+A - +B,[max_depth(2)],C), T =.. C.
   C = "+... - +...", T = +('.','.','.',' ',-,' ',+,'.','.','.').

?- C = "+ ... - + ...", T =.. C.
   C = "+ ... - + ...", T = +(' ','.','.','.',' ',-,' ',+,' ','.','.','.').

To the point:
?- [user].
+(_,_,_,_,_,_,_,_,_,_).
   true.

?- write_term_to_chars(+A - +B,[max_depth(2)],C), T =.. C, call(T).
   C = "+... - +...", T = +('.','.','.',' ',-,' ',+,'.','.','.').

That is arity/10 vs arity/12

Well gprolog chickens out (no offence intended) by putting spaces around
all operators. A practice I actually have some sympathy with.
On Mon, Jul 17, 2023 at 9:54 AM flexoron @.***> wrote:

v2.22.22
?- write_term(+A - +B,[max_depth(2)]),nl.
+... - +...
Not sure but other systems(GNU,SWI) print + ... - + ...
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/267, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSETG3K4TFYAQKGR6EJDXQR5L5ANCNFSM6AAAAAA2MHW2M4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Brain fog this morning, sorry, You're right here.
On Mon, Jul 17, 2023 at 9:54 AM flexoron @.***> wrote:

v2.22.22
?- write_term(+A - +B,[max_depth(2)]),nl.
+... - +...
Not sure but other systems(GNU,SWI) print + ... - + ...
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/267, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSETG3K4TFYAQKGR6EJDXQR5L5ANCNFSM6AAAAAA2MHW2M4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Splendid! (v2.22.25)
?- write_term(+A - +B,[max_depth(2)]).
+ ... - + ...

?-  write_term(+A - +B,[max_depth(1)]).
 ... -  ...   true. % leading space unwanted or realised?

?- write_term_to_chars(+A - +B,[max_depth(1)],C), T =.. C.
   C = " ... -  ...", T = ' '('.','.','.',' ',-,' ',' ','.','.','.').

v2.22.27
Reverted.

?- write_term(+A - +B,[max_depth(2)]).
+... - +...   true.

or

?- write_term(-_* -_,[max_depth(2)]).
(-...)* -...   true.

Now, I'm not sure if it makes sense to identify such 'errors', too.
Because it lead to arity chaos in the end.
?- write_term([]*[]*[],[max_depth(3)]).
[]* [] * []   true.

GNU,SWI: []*[]*[]
eclipse: [] * [] * []


Runtime checking for associated types conforming to invertible protocols

Emit metadata for runtime checks of conformances of associated types to
invertible protocols, e.g., T.Assoc: Copyable. This allows us to
correctly handle, e.g., dynamic casting involving conditional
conformances that have such constraints.
The model we use here is to emit an invertible-protocol constraint
that leaves only the specific bit clear in the invertible protocol
set.

@swift-ci please smoke test

@swift-ci please smoke test macOS

@swift-ci please smoke test Linux


Migrate from bindata to go:embed

Migrate from bindata to go:embed
go:embed is part of the standard library and does not require an extra
go:generate step.
Migrate all usages of bindata to go:embed.
Make embedded the new default (previously required bindata tag).
Add new tag "servedynamic" which serves from filesystem (old !bindata).
Accept-Encoding compression has been dropped. The assets in go:embed are not
available in a compressed form. The compression could be enabled again by adding
a compress middleware: https://github.com/vearutop/statigz
Fixes #17352.

See also https://github.com/go-gitea/gitea/issues/17352.
Does this PR fix what has been discussed there?

@delvh Everything is embedded properly. It uses go:embed statements and then references those go:embed packages in the modules/ packages.
The only thing not addressed is Accept-Encoding compression. The assets in go:embed are not available in a compressed form. I simply dropped the compression step in this PR.
However as mentioned in the issue it could be added back by adding https://github.com/vearutop/statigz

I haven't looked into details about all changes. But for bindata part, I think it's better to keep the old behavior and the old tag, reasons:

Keeping old tag won't break 3rd build pipelines, I know many teams build Gitea by themselves.
When a developer runs Gitea, they do not need the embedded data, they just want to use local assets and debug quickly, with default tags. For me, I do not want to set a tag to exclude embedded when developing Gitea everytime.

Just my opinion.

This embed uncompressed assets so binary size will go up by a few tens of MBs after this. I'm not against landing uncompressed now and doing compression later. Having go:embed work at all is good first step towards modernizing the asset embeds.

Sorry, I think we need a better resolution to replace the old system. uncompressed assets are unacceptable to me.

Question is thought whether want to still support serving uncompressed assets or if browser brotli support can be made a requirement.
If we want to serve uncompressed with only brotli embedded, it would require a CGO dependency, which I think we should not take. Otherwise we could do gzip like vfsgen, but that is a suboptimal solution in terms of both binary size and web performance.

Actually https://github.com/andybalholm/brotli might work for a pure golang brotli decoder, avoiding CGO.

I think we may not actually need statigz at all, we can just:

Make webpack output .br files, deleting original output files
go:embed the directories as usual
On HTTP request, check Accept-Encoding, if it has "brotli" serve byte stream directly from embed (fast path), if it doesn't decompress at runtime and serve decompressed result (slow path).

Depending on how long these decompressions take, it might be good to keep the results in a memory cache, but I imagine it may be fast enough.

I think we may not actually need statigz at all, we can just:
1. Make webpack output .br files, deleting original output files

2. go:embed the directories as usual

3. On HTTP request, check Accept-Encoding, if it has "brotli" serve byte stream directly from embed (fast path), if it doesn't, decompress at runtime and serve result (slow path).

Depending on how long these decompressions take, it might be good to keep the results in a memory cache, but I imagine it may be fast enough.

Sounds good. The last question is developers don't want to compress when it's in dev mode I think.

Yes, disable the webpack plugin in development. Development should not use go:embed, but instead use the assets from the filesystem that webpack continously outputs, e.g. same behaviour as now with the bindata tag absent.

Sorry for bothering, is this PR active? It seems there is no progress for some review comments.

It's active insofar I'm still interested in merging it, but there were a number of comments around wanting to use compression for the assets and I'm not really in a position to implement that right now, so if someone else wants to edit the PR to do that it'd be excellent.

Thank you very much for your contribution. Since we have a refactoring PR for "custom/static/builtin" assets, there are a lot of conflicts.
So at the moment I can see some possible decisions for this PR:

Keep it open as-is, but it would be stale forever (does it make sense?).
Resolve conflicts and keep it open (I guess resolving conflicts would spend more time than starting a new PR from latest main branch, because the "assets" system has changed a lot).
Start a clear new PR (according to 2), and at least the "bindata" tag should be kept as before.
Or do you have other proposals?

What do you think about it?

I'd merge this even without compression, but some numbers of binary size before and after would be good, so we can judge the impact of missing compression.
It's an important step to get this done as it simplifies the build a lot. I can collaborate adding at least the compressed from webpack side.

I'll have a look at adjusting this PR to use the bindata tag and resolve conflicts

I'd merge this even without compression, but some numbers of binary size before and after would be good, so we can judge the impact of missing compression.
It's an important step to get this done as it simplifies the build a lot. I can collaborate adding at least the compressed from webpack side.

I cannot see it's necessary to merge without compressing. It's a regression for end-user usage. What is the problem of the old embed method for the end user?

Then let's add statigz or similar. I think we can get away with only compressing to brotli because pretty much all browsers support it.

brotli is only good for text based files. Anything binary like png's is better compressed using gzip.

brotli is only good for text based files. Anything binary like png's is better compressed using gzip.

Nope. https://stackoverflow.com/questions/11289369/why-png-size-doesnt-change-after-using-http-gzip-compression

brotli is only good for text based files. Anything binary like png's is better compressed using gzip.

Brotli has non-text modes as well, but we don't really need to dive into it so deeply. I would compress those anyways for simplicity's sake in the first iteration of this as the difference will be neglible and it simplifies the implementation.

FYI, I've added support for generic and font broti modes in precompress.
I think I will also implement a feature to it to take assets from one directory and output compressed ones into another directory with subfolders intact. I guess such an option would be easiest for gitea to implement.

Stale and it seems that nobody is interested in this change?

We need compression before we can merge this, gzip is fine, brotli even better.

If there is no progress ..... there seems no other choice besides close it (also due to the conflicts)

To summarize the situation:

go:embed does not feature compression, so the only way to get it to work is to pre-compress the assets outside of go in a separate tool (webpack or precompress module), which complicates the build
To use brotli (the ideal compression), we need a runtime brotli decoder for better client support and https://github.com/andybalholm/brotli is the only one in existance which is a machine-generated translation from C, which apparently is also very big (5mb+), so not ideal.

https://github.com/thealetheia/broccoli seems to take care of point 1 but seems unmaintained. Point 2 can not be resolved, but I can accept it for the sake of better client performance.

A better solution:  Use go:embed with server-side gzip support #26533

Stale. Free free to reopen if some comments like https://github.com/go-gitea/gitea/pull/22887#issuecomment-1521252597 are addressed.


CAMEL-20361: camel-jbang - Make jolokia pluggable for camel-platform-http-main

Description
camel-jolokia is now a context plugin with @DevConsole annotation.
I was not able to generate file core/camel-jolokia/src/generated/resources/META-INF/services/org/apache/camel/dev-console/jolokia with the camel-package-maven-plugin. This file was added by hands, and it is possible that something is wrong with camel-jolokia maven configuration, or something is wrong with the maven plugin (see https://camel.zulipchat.com/#narrow/stream/364655-camel-core-dev/topic/how.20to.20add.20context.20plugin/near/419592914 ).
Also added jolokia to example repo: https://github.com/apache/camel-examples/pull/133
Tracking
https://issues.apache.org/jira/browse/CAMEL-20361

/component-test camel-platform-http-main

/component-test camel-jolokia

/component-test camel-jolokia

jolokia should be option and not in core at all. Instead there should be a more generic factory for platform-http, that can load jolokia and whatelse we add in the future.
It should be platform-http that when it startup (doInit etc) will check if jolokia is configured to be enabled, and then use the factory to find the JAR (if present) and if present then create the factory and does what it need to do. If the JAR is not present then some exception is thrown. We do this elsewhere in Camel.

@kulagaIA I wonder if you will get more time for this before start of next week, as that is the deadline where we will cut the next 4.4 LTS release.

@kulagaIA I wonder if you will get more time for this before start of next week, as that is the deadline where we will cut the next 4.4 LTS release.
Inteding to finish before 12.07.24, is it ok?

/component-test camel-platform-http-main camel-platform-http camel-platform-http-jolokia

/component-test camel-platform-http-main camel-platform-http camel-platform-http-jolokia

Made PlatformHttpPluginRegistry in camel-platform-http to be a generic factory for platform-http, that can load jolokia and whatelse we add in the future.
Also, apologies for messing up with the commit dates, wanted to finish before 4.4 LTS but got sick

Sorry we have now updated main to 4.5.0-SNAPSHOT so you may need to update this PR a little bit, thanks


fixed race condition in frontend

Which issue this PR addresses:
fixes a race condition introduced by https://github.com/Azure/ARO-RP/pull/2275 . This race condition can lead to adminActions overriding each others' parameters and lead to wrong VMs in wrong subscription to be redeployed for example

Fixes
What this PR does / why we need it:

Test plan for issue:

Is there any documentation that needs to be updated for this PR?

@facchettos could you please detail the race condition scenario that you are fixing in this PR?

@darthhexx imagine you have 2 concurrent calls to one of the functions that I modified (let say _postAdminOpenShiftClusterStopVM). What value of the frontend.adminaction field would we end up using?


Subscription cancellation with options doesn't work.

Steps to reproduce the behavior

Create a subscription.
Pass { cancel_at_cycle_end: 1 } as options to the cancel function.

Expected behavior
The subscription should have been cancelled at the end of the cycle rather than getting cancelled immediately.
Actual behavior
Subscription gets cancelled immediately.
Code snippets
No response
Node version
v16.14.2
Library version
v2.8.4
Additional Information
No response

@rranjan14 Apologise for the issue you are experiencing. I just checked the cancel api and i found that the code snippet is not updated. Could you please check this code snippet and let me know?
instance.subscriptions.cancel("sub_KlLQabJyisz3mu",true)
false (default): Cancel the subscription immediately.
true: Cancel the subscription at the end of the current billing cycle.

@rranjan14 could you please confirm is it worked or not ?

Very strange. The problem started again.

@rranjan14 could you please update the node sdk to the latest version v2.8.6 & let me know is the issue still persist or not ?


Enable doc building for arm64 in the Makefile

The doc building was originally disabled for arm64 since
it does not work on arm64. Now the building is ok for arm64
because the PR: https://github.com/cilium/cilium/pull/12231
was merged.
It would also enable the doc building for arm64 in the Travis CI.
Signed-off-by: trevor tao<EMAIL_ADDRESS>

Coverage decreased (-0.03%) to 36.958% when pulling 726e95ec996b8b6701d7cbe6d0b5e70a0f22be0e on TrevorTaoARM:doc_build4arm into c4b2c1e6c7245bdaf2bb4a904ed80a4087623f4d on cilium:master.


OnBehalfOfCredentials giving error due to missing x5c claim in the JWT header

Getting below error even after setting the OnBehalfOfCredentialOptions.SendCertificateChain  = true
MsalServiceException: A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See aka.ms/msal-net-invalid-client for details. exception: AADSTS700027: Client assertion contains an invalid signature. [Reason - The key was not found., Thumbprint of key used by client: '815C0F457ABD378599BC9310F9713C6DC581C74F',Please visit the Azure Portal, Graph Explorer or directly use MS Graph to see configured keys for app Id '7255edad-9269-44d0-b153-92ceffbf86fa'. Review the documentation at docs.microsoft.com/en-us/graph/deployments to determine the corresponding service endpoint and docs.microsoft.com/en-us/graph/api/… to build a query request URL, such as 'graph.microsoft.com/beta/applications/…. Alternatively, SNI may be configured on the app. Please ensure that client assertion is being sent with the x5c claim in the JWT header using MSAL's WithSendX5C() method so that Azure Active Directory can validate the certificate being used. Trace ID: 7aaf56e0-ca8d-48b6-8103-9de701ba6000 Correlation ID: 796539b1-465c-4552-84f7-b72468ed907d Timestamp: 2022-03-14 16:41:35Z
Same app works successfully with MSAL
var msalResult = await this.application.AcquireTokenOnBehalfOf(scopes, new Identity.Client.UserAssertion(userToken)).WithSendX5C(true).ExecuteAsync();
return msalResult.ToResult();

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Identity:0.45487067,KeyVault:0.23919488,Azure.Core:0.06016083'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @sasohail  - Can you verify that the private key is present in the certificate being used by the OnBehalfOfCredential?

@christothes. The private key is present. this works fine when using  ClientCertificateCredentials.
Also we are able to do onBehalf flow using MSAL with same app id and certificate.

closing as duplicate


Hiding sensitive info

Fix hiding sensitive info for headers, issue https://github.com/camilamaia/scanapi/issues/66.

Codecov Report

Merging #73 into master will increase coverage by 0.98%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           master      #73      +/-   ##
==========================================
+ Coverage   88.98%   89.97%   +0.98%
==========================================
  Files          14       14
  Lines         354      369      +15
==========================================
+ Hits          315      332      +17
+ Misses         39       37       -2

Impacted Files
Coverage Δ

scanapi/reporter.py
61.53% <93.33%> (+32.37%)
:arrow_up:

Continue to review full report at Codecov.

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


Implement NIFS.P & NIFS.V transcript

Hi there
I replaced mocked transcript randomness with PoseidonTranscript.
I would appreciate it if you could confirm.
Thank you.

the current repo folding-schemes is not intended to rewrite microsoft/Nova's in arkworks but to do a independent (different) implementation of Nova scheme (and other folding schemes too).
The transcript will be started previous to the call of this function.

Thank you for polite explanation!
That makes sense.
Sorry this PR is mistake.


[SUGGESTION] Split generated files

Hi, I'm wondering if it would be better to split the generated files in multiple files so that the compiler can handle them without taking 8+ GBs of RAM to compile.

Hi, thank you for the suggestion.
However, I have tried it and it doesn't seem to help. I have tried separate files, separate crates (not entirely possible) and more, whatever I try, it keeps using the same amount.
The reason it takes so much memory is mostly due to serde, typed builder and the big amount of big types, so I don't think it can be solved that easily. It seems to be some kind of indexing in the crate's surface maybe?

Hmm interesting.
I saw that recently serde bundled some of their things in a compiled lib form to speed up compile times. Would it possibly be a good idea to do something similar, where you can build the model lib into a fully compiled form, and then just reference it? So that the model lib build only happens once and can be reused during development+CI/CD.

I don't think that would be possible for a library as it needs to ne source to be accepted by cargo. I also don't think it would help compile time sadly, as the reexporting of all types results in similar issues..
and lastly shipping a binary didn't receive a lot of good attention and probably is not desirable by most users

Oh ok. That is actually why the fhir-sdk crate is separate from fhir-model, so that it only needs to compile once and is faster and supposedly less memory, but well, it is still using memory sadly for some reason. I made an issue on the Rust project, but I have no idea if it is possible to fix.
I you find a way to reduce memory usage and compile time I would be happy to hear it (without reducing functionality of course).
I also can't have CI because of it and I am not happy about it :D

Hi again!
I read up a bit more about Rust and did 1 test that generated very promising result!
Turns out that the typed-builder lib is one of the culprits for the insane build times+RAM usage during compile.
I only tried with fhir-models, as removing it might require modifications to fhir-sdk.
My results ran with DEBUG, RELEASE had similar results:

With/Without
Ram usage
Compile time

With Typed builder
11 500 MB RAM
3m 19s

Without Typed builder
4900 MB RAM
1m 29s

Now I understand that the typed-builder lib is used for creating the resource that are used, but I think that instead declaring them as just a normal struct + impl Default  for every type, should be able to solve the same issue.
BTW thanks for the great work!

Hi, thanks!
That is why you can disable the builders feature :D The problem is, you can not really have Default implementations, as there are required fields.
I used to think about derive_builder instead of typed-builder, as that uses no generics and should reduce compile resources too. But that then needs plenty of annoying error handling, so I prefer this.
If you have no serde and no builders it compiled in 20 seconds on my machine, but both of them are needed imo. Builders can be disabled via feature flag already if you don't want them. But without serde is kind of pointless using FHIR. It would somehow need more a compiler friendly serde implementation.

Closing in favor of https://github.com/FlixCoder/fhir-sdk/issues/17


Show confirmation dialog when there are unsaved changes

Closes https://github.com/mui/mui-toolpad/issues/1571
The code component part of this PR can be seen/reviewed isolated here: https://github.com/mui/mui-toolpad/pull/1628
We can review and merge that part first if it makes things easier.

[x] Confirm when leaving code component editor with unsaved changes (improvements)
[x] Confirm when leaving query editor with unsaved changes, unless "Cancel" is pressed
[x] Confirm when leaving page module dialog unsaved changes, unless "Cancel" is pressed
[x] Confirm when leaving page parameters dialog with unsaved changes, unless "Close" is pressed
[x] Confirm when leaving bindings dialog with unsaved changes, unless "Cancel" is pressed

All except the code component flow use the same useEditorUnsavedChangesConfirm hook.
Preview: https://toolpad-pr-1618.onrender.com/

Works really well. I'm having some doubts about the cancel button behavior, but no idea what would be the best UX.
Maybe the newline in the dialog looks a bit off?

We can always easily change it in the future.

I'm having some doubts about the cancel button behavior, but no idea what would be the best UX.

Playing a bit with the UX, I personally faced no frustration on this, so far. I will report back here if I find something.

@apedroferreira I might have found a bug:

Open https://master--toolpad.mui.com/_toolpad/app/cl9my2gkr0001q89lt82h56ey/pages/q9198sj

https://user-images.githubusercontent.com/3165635/220422687-f27c1f90-28e6-440a-9ed6-0167b6df2c04.mov
It asks me confirm when I exit even if I did no changes.

@apedroferreira I might have found a bug on this PR. It asks me to confirm my exit when I use Escape even if I did no changes.

Open https://master--toolpad.mui.com/_toolpad/app/cl9my2gkr0001q89lt82h56ey/pages/q9198sj
Follow:

Maybe because of auto-formatting there's a difference between the initial value and the value on save... Should be an easy fix, thanks for reporting this, will add a fix in a bit.


Possible resource leak on dead pooled connection

From testing with a SQL Server I could reboot on-demand, I noticed the pool statistics were appearing incorrect. I believe there is a possible resource leak in the ConnPool.addToPool function called by ConnPool.Release
func (p *ConnPool) addToPool(conn *Conn) {
	p.poolMutex.Lock()
	defer p.poolMutex.Unlock()
	if !conn.isDead() {
		conn.expiresFromPool = time.Now().Add(poolExpiresInterval)
		//release to the top of the pool
		newPool := []*Conn{}
		newPool = append(newPool, conn)
		newPool = append(newPool, p.pool...)
		p.pool = newPool
	}
}

If conn.isDead() is true, then I the connection is not being closed and p.connCount is not being decremented. There are some FreeTDS calls in Conn.close() which I suspect if not called, could result in a resource leak.

The following Pull Request (off my fork) proposes a solution to the resource leak:
https://github.com/MarkSonghurst/gofreetds/pull/1

Thanks.
I picked that from your fork.


🐞 - TuiDialogService.open() should be properly typed

Playground Link
No response
Description
Try to supply some data to dialog.open() method.
this.dialogService
    .open<MyOutputType>('Good, Anakin, Good!', {
        label: 'Star wars. Episode III',
        size: 's',
        // "data" here has type "any"
        data: {button: 'Do it!'},
    })
    // "result" here has proper typing
    .subscribe(result => this.myService.process(result));

Notice how dialog data is typed as any and there is no obvious way to set correct type.
The only way to fix the data type is to use the following ugly workaround:
private dialogService: AbstractTuiDialogService<TuiDialogOptions<MyDataType>> = inject(TuiDialogService);

The open() method should accept a second generic to properly type dialog data.
Angular version
17.3.10
Taiga UI version
3.81.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

Link: https://github.com/taiga-family/taiga-ui/pull/6115/files

@waterplea why did you close the PR?

@splincode the mentioned PR doesn't fix the issue. We need second generic on the open() method, not a way to pass any Angular component to open(). I am fine with just passing PolymorpheusComponent.

For now you can type options as a const:
const options: TuiDialogOptions<{ button: string }> = {
  label: 'Star wars. Episode III',
  size: 's',
  data: {button: 'Do it!'},
}

this.dialogService
    .open<MyOutputType>(new PolymorpheusComponent(MyComponent), options)
    .subscribe(result => this.myService.process(result));

In theory we wanted to extract data type from content, because it has typed context, at least in case of templates and functions, but so far I haven't been able to figure that out fast enough and backlogged it.

Context also has output type. Why should input type be treated differently than output. The generic on the abstract class is totally useless from consumer's point of view. Both context and open() should have their own generics.
Right now typing dialog context looks sth like this:
protected context = inject(POLYMORPHEUS_CONTEXT) as TuiDialogContext<MyOutputType, MyInputType>;

I don't see where the generic on the class is useful in this case.

Your workaround doesn't seem to work:

Sorry, my mistake. Partial<TuiDialogOptions<...>>

Partial<TuiDialogOptions<MyDataType>> is almost as long as AbstractTuiDialogService<TuiDialogOptions<MyDataType>> and not that much better workaround.
open() definitely needs a second generic and, honestly, I don't see how that can break anything.

@hakimio do you mean about second generic like that https://github.com/taiga-family/taiga-ui/pull/6175/files ?

Almost, just instead of this.dialogs.open<TuiDayRange, TuiDialogOptions<TuiMobileCalendarData>>, I would like to simply use this.dialogs.open<TuiDayRange, TuiMobileCalendarData>. Basically, I don't think TuiDialogOptions should be mandatory.

Maybe DialogService could override the open() method from the abstract class to set different generics.

@hakimio what do you think?
https://github.com/taiga-family/taiga-ui/pull/7621

Not a fan, to be honest.

You still have to declare dialogs like dialogs = inject(TuiDialogService<TuiDialogOptions<TuiMobileCalendarData>>)
It looks like it would break MobileDialogService.open() typings and it doesn't fix MobileDialogService data property type which is still any.

Ideally, DialogService class generic could look like this:
export class TuiDialogService<T = any> extends TuiPopoverService<TuiDialogOptions<T>> {}

And DialogService should override it's open() method. Sth like this:
// "T" generic here comes from the class definition
public override open<G = void, V extends T = T>(
        content: PolymorpheusContent<T & TuiPopoverContext<K extends void ? G : K>>,
        options: Partial<TuiDialogOptions<V>> = {},
    )

Sth similar could be done for MobileDialogService where open() is already overriden.
I don't think you should change the open() method in the base PopoverService.

@hakimio I think, you can make contribution PR

Only if @waterplea is willing to accept the changes I mentioned.

At the moment I'm focusing on 4.0 and unable to properly assess the suggestion. From the brief look, generic in class definition makes no sense since this generic is relative to open method only and a particular content you pass to it, that expects particular data type. That's why ideally it would be inferred from the content passed. I'll get back to it when we finish first release candidate. In the meantime you can define a type if you dislike long workaround:
export interface WithData<T> extends Partial<TuiDialogOptions<T>> {}

And define options as const like I suggested earlier.

You can now use new tuiDialog factory and a component with public context property to enable strong typing:
https://taiga-ui.dev/components/dialog#data

It only remains an issue if you don't want to define your dialog as a property of the component and instead instantiate it in a method. Or if you don't control the dialog component and can't define the context there or you don't want to make the context public.

You can use runInInjectionContext if you don't want to define it as a property. As for public context – that will remain a limitation for now, I believe this is good enough for this feature at the moment and we can focus on other things. Perhaps in v5 we will rework our dialogs a bit.


LTS Strategy and Upgrading older Images

Goal
We want to implement a system that supports upgrading base images for older product images. This system should be easy to use without much repetitive manual work.
LTS Strategy and Upgrading older Images
Do we want to upgrade base images for all previous release, all the time, indefinitely? This is to be decided. Upgrading older product images is not strictly necessary for the next release, so we decoupled this.

[ ] #237
[ ] #238
[ ] #239

Lastly, manual steps should be automated as best we can.

Maybe some or all of this we already have now by the work @nightkr did last week

Closing this as the technical implementation has been taken care of by @nightkr docker bake implementation. The rest is mostly us agreeing on processes and how long we want to support things, which is handled in the linked ADR PRs.


onUpdate prop can be passed to Playground.

New feature: onUpdate prop which gets called after each code update with the new code and an error object if one was caught during preview eval.
Useful for the ComponentPlayground in Spectacle where you may want to develop a piece of code across multiple slides in a presentation. onUpdate lets you hold onto code that was edited in one slide and insert it into a later slide (and optionally avoid holding onto code that generated an error).

Hm I just realized this isn't even the library used in Spectacle, but whatever, you can still merge this if you want. :slightly_smiling_face: