The result of the "statuses()" function doesn't match the output of "git status" command

Hi,
I am trying to use the following code to get a list of modified file in my git repository:
let mut status_opt = StatusOptions::new();
status_opt.show(StatusShow::IndexAndWorkdir);
// status_opt.include_untracked(false).include_unmodified(false).no_refresh(false);
let status_result = repo.statuses(Some(&mut status_opt)).unwrap();
println!("{}", status_result.len());
for status_entry in status_result.iter() {
    println!("{:?}", status_entry.path());
    println!("{:?}", status_entry.status());
}

However, the above code only shows 15 of my total 40 modified files for some reason...
The command git status -uno show a list of 40 modified files.
I am very puzzled.

Seems like in order to get all WT_MODIFIED files correctly,  i need to set include_untracked = true, and then filter on the status.
So something like
status_opt.include_untracked(true).include_unmodified(false);
...
for status_entry in status_result.iter() {
    let istatus = match status_entry.status() {
        s if s.contains(git2::Status::WT_MODIFIED) => "modified: ",
        _ => continue,
    };
}

Thanks for the report! This may be a more appropriate bug report though for libgit2 as we're just binding them!

I'm going to close this since it's likely an issue with libgit2, but if a change is needed here PRs are of course always welcome!


Add explain the difference between the Model deprecation date and the Deprecation inference

[Enter feedback here]
This document does not explain the difference between the Model deprecation date and the Deprecation inference.
In this case, the user will not be able to determine what to do if the Model deprecation date and the Deprecation inference are set to different dates.
Therefore, it is desirable that the difference between the Model deprecation date and the Deprecation inference be described in the document.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0f14f0d2-0170-b126-66fa-6ee39ed5651b
Version Independent ID: 0db5172d-f7ff-cceb-d696-55071bff32d9
Content: Azure OpenAI Service working with models - Azure OpenAI
Content Source: articles/ai-services/openai/how-to/working-with-models.md
Service: azure-ai-openai
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@tkudo-ms
Thanks for your feedback! We will investigate and update as appropriate.

@tkudo-ms
Thanks for your feedback! We will investigate and update as appropriate.

I've created a pull request for this issue.
Please confirm.

The PM team decided they wanted to handle this via a dedicated new article. We really appreciate you taking the time to report the issue and the public PR. Apologies that we couldn't use your PR this time around.
The new doc is located here:
https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/model-retirements

#please-close


How to edit custom fields Wordpress with xmlrpc?

I can't add or edit any information in some custom fields. I speak about blog post, not another content.
Field with atribute name="url_video" I haven't problem. But for example name="data[url_video]" doesn't work to add/edit.
I think only occurs this with custom field that contains [ ]. Is there any known problem? I can't find anything in Internet. Is a bug, not possible to do or an error in code?
My Python code that works:
client = Client('http://example.com/xmlrpc.php', 'user', 'password')

fields = [ ['video_url', 100], ['video_title', 'yes'] ]

widget = WordPressPost()
widget.title = 'Widget'
widget.content = 'This is the widgets description.'
widget.custom_fields = []
for field in fields:
    widget.custom_fields.append(
        {'key' : field[0], 'value' : field[1]}
    )
widget.terms_names = {
    'category': ['MyCategory'],
}
widget.id = client.call(posts.NewPost(widget))

My Python code that doesn't works:
client = Client('http://example.com/xmlrpc.php', 'user', 'password')

fields = [ ['data[video_url]', 100], ['video_title', 'yes'] ]

widget = WordPressPost()
widget.title = 'Widget'
widget.content = 'This is the widgets description.'
widget.custom_fields = []
for field in fields:
    widget.custom_fields.append(
        {'key' : field[0], 'value' : field[1]}
    )
widget.terms_names = {
    'category': ['MyCategory'],
}
widget.id = client.call(posts.NewPost(widget))

You can do something like this:
First save your post, than update it
widget.id = wp.call(posts.NewPost(widget))
widget.custom_fields = []
for k, v in custom_fields_dict.items():
widget.custom_fields.append({'key': k, 'value': v})
out = wp.call(EditPost(widget.id, widget))


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3109

Questions ?
Please refer to the Backport tool documentation


[TASK] Abstract the Runner into the SDK and add injectable config

Overview
Every blueprint main.rs needs to re-implement repetitive run and registration code which oftentimes has only a few minor differences across different blueprints. This should be abstracted and put into the SDK. The custom configuration should be injected through the exposed structs or environment so that there is less code needed to get a blueprint deployed and running.

Just provide the DefaultRunner with a builder pattern where it takes a list of Event Handlers.

A better approach could be a macro similar to #[tokio::main] that we could build to improve the DX:
#[sdk::main]
async fn main(config: StdGadgetConfiguration) -> sdk::Result<()> {
   // ...
}

Here is another proposal that I though about last night
Proposal: Integrating Dependency Injection (DI) in Gadget Framework Similar to Axum
Introduction
This proposal aims to introduce a Dependency Injection (DI) system in the Gadget framework, inspired by the DI implementation in the Axum web framework. The goal is to enhance the modularity and extensibility of the Gadget framework by allowing jobs to automatically register and resolve dependencies.
Design
Job Definition
Jobs in the Gadget framework will be defined the same way we are currently have, with the job attribute macro. Since jobs are very similar to Axum's handlers, we could take that fact and have trait Job similar to the Handler trait in axum.
Example:
#[job(id = 1, params(x, y), result(_))]
fn my_job(Context(ctx): Context<MyContext>, x: u64, y: u64) -> Result<u64, Inflatable>  {
    // Job implementation ..
}

Job trait
The Job trait would be defined as following:
pub trait Job<T, C>: Clone + Send + Sized + 'static {
    type Out: Into<Field>;
    /// The type of future calling this job returns.
    type Future: Future<Output = Self::Out> + Send + 'static;

    /// Call the handler with the given request.
    fn call(self, params: &[Field], ctx: C) -> Self::Future;

    /// Convert the job fn into a [`JobHandler`] by providing the context
    fn with_context(self, ctx: C) -> JobHandler<Self, T, C> {
        JobHandler::new(self, ctx)
    }
}

The we would implement this trait for anything that adheres to the following:

it is an async fn
Take no more than 16 arguments that all implement Send.
Returns something that implements IntoField

Environment Setup
An environment setup function will be introduced to register jobs and their contexts. This function will manage the lifecycle of the jobs and ensure that dependencies are resolved correctly.
Example:
let my_ctx = MyContext {
   // ...
};

env.with_context(my_ctx)
    .job(my_job)
    .job(my_other_job)
    .run().await?;

That's it, the job method in the env accepts anything that implements the Job trait, which is all #[job] implements that by default, then it will pass all of them when we call run() to their events watchers to do job.call(...).
Conclusion
Integrating a DI system similar to Axum's in the Gadget framework will significantly enhance its modularity and ease of use. By automatically registering and resolving job dependencies, we can streamline the development process and improve the overall robustness of the framework.
Feel free to ask me any questions.


Implement https://github.com/digipolisgent/robo-digipolis-package/issues/6

Should be implemented in the helpers package?


[Fix #3719] Unmarshall return ObjectNode that is event sensitive

Fix https://github.com/apache/incubator-kie-kogito-runtimes/issues/3719

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3720 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3720/1/display/redirect
Test results:

PASSED: 3367
FAILED: 3

Those are the test failures:

org.kie.kogito.quarkus.workflows.CallbackStateIT.callbackStateWithError
Expecting map:  {"query"="GENERATE_ERROR_QUERY"}to contain entries:  ["lastExecutedState"="FinalizeWithError"]but could not find the following map entries:  ["lastExecutedState"="FinalizeWithError"]

org.kie.kogito.quarkus.workflows.CallbackStateTimeoutsIT.callbackStateWithError
Expecting map:  {"query"="GENERATE_ERROR_QUERY"}to contain entries:  ["lastExecutedState"="FinalizeWithError"]but could not find the following map entries:  ["lastExecutedState"="FinalizeWithError"]

org.kie.kogito.quarkus.workflows.CallbackStateWithTimeoutsErrorHandlerIT.callbackStateWithError
Expecting map:  {"query"="GENERATE_ERROR_QUERY"}to contain entries:  ["lastExecutedState"="FinalizeWithError"]but could not find the following map entries:  ["lastExecutedState"="FinalizeWithError"]

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3720 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3720/2/display/redirect
Test results:

PASSED: 3368
FAILED: 3

Those are the test failures:

org.jbpm.bpmn2.IntermediateEventTest.testTimerBoundaryEventInterrupting
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testIntermediateCatchEventTimerDuration
expected: 2 but was: 1

org.jbpm.bpmn2.IntermediateEventTest.testEventBasedSplit2
expected: 2 but was: 1


fix: tentative fix ffor semantic release not working for dev and pre-…

…release channels

:tada: This PR is included in version 1.0.0-dev.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


MIME type error sending mail

Hi, I'm having troubles to send mail using a predefined Session instance in a Tomcat server. When mail is to be sent I got this error:

java.lang.RuntimeException: no object DCH for MIME type multipart/mixed; __	boundary="----=_Part_3_1506400929.1529502766000" [Sanitized]
	at org.simplejavamail.converter.EmailConverter.mimeMessageToEML(EmailConverter.java:202)
	at org.simplejavamail.mailer.internal.mailsender.MailSender.sendMailClosure(MailSender.java:262)
	at org.simplejavamail.mailer.internal.mailsender.MailSender.send(MailSender.java:211)
	at org.simplejavamail.mailer.Mailer.sendMail(Mailer.java:239)
	at org.simplejavamail.mailer.Mailer.sendMail(Mailer.java:230)
	at com.cetelem.web.auto.simulator.portlet.service.impl.LiferayMailService.sendMail(LiferayMailService.kt:51)
	at com.cetelem.web.auto.simulator.portlet.service.definition.MailService$DefaultImpls.sendMail$default(MailService.kt:6)
	at com.cetelem.web.auto.simulator.portlet.controller.AutoSimulatorPortletViewController.sendMail(AutoSimulatorPortletViewController.kt:207)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:180)
	at
.
.
.
.

Caused by: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; __	boundary="----=_Part_3_1506400929.1529502766000" [Sanitized]
	at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896)
	at javax.activation.DataHandler.writeTo(DataHandler.java:317)
	at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1350)
	at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1683)
	at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1659)
	at org.simplejavamail.converter.EmailConverter.mimeMessageToEML(EmailConverter.java:198)

In my project is mandatory to send emails reusing the predefined session instance. My mailer building is like this:
val emailToSend = EmailBuilder
                .startingBlank()
                .toMultiple(toAddresses)
                .from(replyAddress)
                .withSubject(subject)
                .withHTMLText(textHTML)
                .buildEmail()

        val mailer = MailerBuilder
                .usingSession(emailConfig.session)
                .withDebugLogging(true)
                .buildMailer()

        mailer.sendMail(emailToSend)

I need a little bit more context.

Does it work with a Session configured through Simple Java Mail?
What is the structure of the email?
What types of attachments / embedded images are there?

Thanks for reply.
1- I get a preconfigured Session provided from a portal CMS.
2- What do you mean by structure? I'm building the mail using the HTML generated by any MJML template (see https://mjml.io/try-it-live)
3- Fails even without embedded images.
I attach a simple generated HTML that fails when I try to use simple-java-mail.
Greetings!
dummy_email.zip

So what I mean with structure is how are you building the email. But from your comment I understand it is an email with HTML content, not plain text content, no attachments and no embedded images.
And still you are getting this error. I've seen the error "no object DCH for MIME type multipart/mixed" happening due to class loader issues. Are you using something like Groovy, or OSGi? The problem, as I understand it, is that the relevant internal JavaMail classes (from javax.activation, javax.mail, javax.mail.internet) that set these MIME type handlers should be loaded using the same classloader as was used for the code utilizing the MimeMessage (in your case using it to convert to EML) or else these MIME type handlers will be missing somehow.

Thanks for the reply. I am indeed running my application in an OSGI environment that provide me the Session instance. So I understand I won't be able to use the library for compatibility reasons at this time.

Well.... you can redefine all the handlers manually, like done @castortech did:
MailcapCommandMap mc = (MailcapCommandMap) CommandMap.getDefaultCommandMap();
String[] mimeTypes = mc.getNativeCommands("multipart/*");
if (mimeTypes == null || mimeTypes.length < 1) {
	mc.addMailcap("text/html;; x-java-content-handler=com.sun.mail.handlers.text_html");
	mc.addMailcap("text/xml;; x-java-content-handler=com.sun.mail.handlers.text_xml");
	mc.addMailcap("text/plain;; x-java-content-handler=com.sun.mail.handlers.text_plain");
	mc.addMailcap("multipart/*;; x-java-content-handler=com.sun.mail.handlers.multipart_mixed");
	mc.addMailcap("message/rfc822;; x-java-content-handler=com.sun.mail.handlers.message_rfc822");
}

Closing this as a duplicate of #147. If I can support OSGi without rewriting Simple Java Mail, please let me know. Otherwise, try looking into something like AOP to solve OSGi's classloading problem.

As stated we have this issue and have implemented a work around for now. I am still planning on proposing a more generic solution, but if you look at the referenced issue it shows the change that was needed. You can always contact me should you have any questions.

Now that I think about it, perhaps Simple Java Mail can simply check if these handlers are set and always manually set them if missing.
Would that solve your problem @castortech and @atrujillofalcon? That would be a simple fix and I don't except Java Mail to modify this part of the framework any time soon.


API responding with  INTERNAL_ERROR

What version of fleet are you using (fleet version --full)?
V2.6.0
What operating system are you using?
Centos
What did you do?

What did you see instead?
curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)

after many many attempts, that change took affect but i was still getting that error. which does not give any explanation on what is the issue. hopefully there is some logging we can enable around that.

Are you able to find the corresponding error log from the Fleet server? It's hard to debug this without that.

i have upgraded to fleet 3.1.0 so i will close this ticket. really appreciate taking a look at it.
already started some API testing on the new version will report if any issues found.
the only thing i see missing is a good docs for API but i'm using this which is really fine as well Link


Fix README.md typos

Just corrects typos in the readme.  contributing.md looks fine.

@evansmj Thanks for the PR, didn't notice those typos :)


Encryption and Tunneling

Hello,
The connection between Myrtille and the client it is secure ? Did you use asymmetric encryption to do communicate ?
Thank you

Do you mean the communication between myrtille and the browser? If that is, yes it's encrypted if the page is accessed using https.
If you mean the communication between myrtille and the rdp client, it could be but currently isn't because both are on the same machine (IPC communication).

I mean betwenne myrtille and the browser yes :)
The probelm is that I tried to use nginx server as proxy to IIS: I set the IIS secure port : 8443 and then I redirect nginx from 443 port to the port 8443.
When the redirection work well, but when I try to lunch an RDP Session from Myrtille, I get timeout expired message ...
There is my nginx configuration:
server {
		listen 80;
		return 301 https://$host$request_uri;
}

server {
		server_name localhost;

		listen 443 ssl;
		ssl_certificate ./ssl/public.crt;
		ssl_certificate_key ./ssl/private.rsa;

			location /Myrtille{
                proxy_pass         https://<IP_ADDRESS>:8443/Myrtille;
				proxy_set_header Host $host;
				proxy_set_header X-Ssl on;
			}
		}

Good idea to use a reverse proxy for myrtille with redirect from port 443 to 8443. However, the latter is meant for the websocket server and not IIS.
I'm not sure if nginx is capable of redirecting a given protocol (wss:// and not https://) but, if it is, it should be configured to do that.
The upcoming myrtille release does support native IIS8+ websockets and uses the standard tcp 80 and 443.

Hi,
I succeed to redirect IIS server with nginx, however, I noticed that when I turn off nginx server, the RDP session is still connected.. It's because that I redirect nginx to the IIS server and not the ws ?
I don't know how to proceed to redirect nginx to ws : should I use port 8080 ?
Thank you.

I don't know well nginx either but it seems possible (https://www.nginx.com/blog/websocket-nginx/).
However, i'd suggest you to use myrtille 1.5.0 which uses the same ports for http and ws, as soon as it's stable (currently beta).

1.5.0 is stable now, you should try it out :)


Reformat the data model documentation.

Change the "Data Model" section to "Concepts" and update the layout.
Also describe the concepts starting from "instance" and so on.

I left the "Abstract Types" subsection mostly as is, because anytype is hard to allocate anywhere specific and leaving it as the only dangling bit seems odd.

I left the "Abstract Types" subsection mostly as is, because anytype is hard to allocate anywhere specific and leaving it as the only dangling bit seems odd.

anytype should be listed in Concepts / Functions, perhaps add Generic functions for that with an example. It would be way cooler to introduce it that way, because generic functions are super cool.


Added BrainhubCarouselItem--visible className

It will be applied to every slide currently fully visible on screen
Fixes: https://github.com/brainhubeu/react-carousel/issues/313
Idea for centered carousel:

active item is in the middle
when there is even number of items shown, on right/left there always is one that is cut in half
when there is uneven number of items shown, this situation does not happen.

That's why i'm subtracting one from elements count when there is even number of items per page, and why I don't when there is uneven count.
Idea for not centered carousel:

active element is always the one on the left, making calculations easier.

Possible problems/ways to improve:

I don't have any idea how to support offset prop, neither am I sure if it should be handled.

[ ] package.json:version has been updated with npm version patch (or major/minor as appropriate)

[ ] @brainhubeu/react-carousel version has been updated in docs-www/package.json to the same which is in package.json:version

@PiotrSzlagura
thanks for your PR, I opened https://github.com/brainhubeu/react-carousel/pull/316 instead because the deployment of docs into a testing environment works only for the main repo branches


[SR-10574] Update ICU from 61.1 to 61.2

ICU 61.2 is a maintenance release adding support for the new Japanese
Reiwa Era (令和).
https://github.com/unicode-org/icu/releases/tag/release-61-2
Resolves SR-10574.

@swift-ci test

ICU has been updgraded to 65.1 in #27937 so closing this


New package: ClimateMARGO v0.0.1

Registering package: ClimateMARGO
Repository: https://github.com/hdrake/ClimateMARGO.jl
Created by: @hdrake
Version: v0.0.1
Commit: 3b3fb4c1d7b2840516e11fe3c81f06fdacbdbb93
Git reference: master

Intentionally blocking to rename without the MARGO acronym.


Media not working via TinaCMS

I really like your site design, and the integration of TinaCMS and the image plugin is perfect! 💯
I've got the site setup from your instructions and it's deployed and TinaCMS works - I can edit config and add new projects, but the media part doesn't work and just gives Error fetching media. Something went wrong while requesting the resource.. I've been to tina cloud and done the sync media, but still no luck.
All I can see in the docs is setting the following in tina/config.js.
  media: {
    tina: {
      mediaRoot: "assets/uploads",
      publicFolder: "",
    },

I wondered if publicFolder should be _site or something?

Yeah I searched around and there wasn't anything clear. This is my first time with 11ty and TinaCMS so wasn't quite sure of either.
I also noticed that if I use TinaCMS to change the site metadata, it changes the site_icon_svg from /assets/icons/favicon.svg to site_icon_svg: /assets/uploads/assets/icons/favicon.svg which then causes the build to fail as there's nothing there. Perhaps related to the media issue.
I'll make sure it's the same version and see what else the console tells me.
Thanks.

I think this is a Content Security Policy (CSP) issue where Halide's default policy (configured in netlify.toml) is blocking Tina-hosted media sources.
Due to the Tina app's use of various resource domains, I am going to re-think Halide's default CSP behaviour. In the meantime you can do one of 2 things to get media in the CMS working again:-

Set the CSP to report errors only by setting reportOnly = true in netlify.toml. Any CSP errors will show in the console but won't cause resources to be blocked
Add assets.tina.io  to the imgSrc line in netlify.toml

You might need to add additional allowed resource URLs to your CSP if you are still seeing errors in the console.
Hope that helps for now!

Set the CSP to report errors only by setting reportOnly = true in netlify.toml. Any CSP errors will show in the console but won't cause resources to be blocked
Add assets.tina.io  to the imgSrc line in netlify.toml

Had the same issue, and this worked! Thanks.

Hi @alexjj and @seasonedfish !
The CSP issue has since been fixed by #6 which disables the CSP completely in Tina CMS at /admin/*.
Not ideal but we have no control over where Tina CMS loads external resources from, so for now this is the best solution I can see. 😐
If you want to opt in to this change, you should bump your netlify-plugin-csp-generator version to the latest (currently 1.6.1) and add the following exclude line to your CSP config inside netlify.toml
[plugins.inputs]
    buildDir = "_site"
    exclude = ["admin/**/*"]

The plugin also has a useful new build debug property that will output exactly which paths are included by your CSP:
debug = true


Add Post-Quantum Cryptography (PQC) Algorithms for TLS 1.3 Key Exchange

Description:
Hi, I've made some changes to the key exchange mechanism in TLS 1.3 by incorporating Post-Quantum Cryptography (PQC) algorithms.
Changes:

Add kyber algorithms to the NamedGroup.
Add TlsAgreement for PQC algorithms. (BcTlsKyber, JceTlsKyber)
Add TlsPQCKemMode to distinguish Client / Server, and move receivePeerValue() forward than generateEphemeral().
We do not add PQC namedGroups to CANDIDATES_DEFAULT. So in order to use PQC namedGroups, you must set the "jdk.tls.namedGroups".
(java -Djdk.tls.namedGroups=kyber1024,x25519,x448 ClientExample)

Questions:

NamedGroupInfo.hanAnyECDSA() was temporarily modified to use PQC namedGroups with ECDSA certificate. Where is a better location than here?
We've added TlsPQCKemMode to distinguish Client / Server, is there any good way to distinguish without this?

I'd be happy to address any feedback or questions you may have.
Thank you for your time and consideration!
Best regards,
hunhee

Is the review still in progress?

Hello, Is the review still in progress?
code for ec-kyber-hybrid, edec-kyber-hybrid are also prepared.

ec-kyber-hybrid : https://github.com/samsungsds-research-papers/bc-java/tree/tls-ec-kyber-hybrid
edec-kyber-kybrid : https://github.com/samsungsds-research-papers/bc-java/tree/tls-edec-kyber-hybrid
@roy-basmacier @peterdettman @lee-changhoon

@yuhh0328

NamedGroupInfo.hanAnyECDSA() was temporarily modified to use PQC namedGroups with ECDSA certificate. Where is a better location than here?

Modifiying the NamedGroupInfo changes are wrong and presumably unnecessary. Proir to TLS 1.3, signature schemes based on ECDSA could function without specifying a particular curve. The "hasAnyECDSA" determined whether a NamedGroup supported such schemes. I might be mistakened, is it applicable to the PQC Groups?

We've added TlsPQCKemMode to distinguish Client / Server, is there any good way to distinguish without this?

TlsPQCKemMode isn't needed. The TlsCryptoParameters interface would be a better way of distinguishing between Client/Server. It would be better to pass a TlsCryptoParameters implementation inside of TlsPQCDomain.createPQC()
Can you clean up these two things? Then we can take over the rest.
Another note that things shouldn't be named for their "PQC"-ness, but instead for the type of algorithm/functionality, presumably "KEM" in many cases here.

@roy-basmacier @lee-changhoon

It has been changed to use "TlsCryptoParameters" to distinguish client/server. (TlsPQCKemMode has been deleted)
"PQC" has been changed to "KEM".
"hasAnyECDSA" is back to its original code.
※ To use the KEM namedGroups with ECDSA certificate, the EC namedGroup must be included in the "jdk.tls.namedGroups".
(jdk.tls.namedGroups=kyber512,kyber768,kyber1024,secp384r1)

Currently, BC only look at the priority of NamedGroups in Djdk.tls.namedGroups if X25519 or secp256r1 is not in the list as mentioned in https://github.com/bcgit/bc-java/blob/main/tls/src/main/java/org/bouncycastle/tls/AbstractTlsClient.java#L409.
If I create a BC client with the list of Namedgroups [kyber768,X25519], it will only send X25519 shared keys only while a client with liboqs provider will send the both pairs of keys. IMO it is preferred if we can support sending a standard NameGroup alongside the PQC ones as a fallback option, since most of the other clients and the servers still does not support PQC NamedGroups.


ARROW-12824: [R][CI] Upgrade builds for R 4.1 release

Ok I've sent #10440 to fix the crossbow issue. Once that's merged, we should be able to comment-bot request those builds

I ran the crossbow steps manually last night (it took some juggling, but I was impatient waiting for #10440 to merge). There were a few things I noticed:

the conda-*-r41 builds failed cause they were looking for a file arrow/dev/tasks/conda-recipes/.ci_support/r/linux_64_r_base4.1.yaml I imagine this can copy the 4.0 files that are already there in that folder bumping 4 to 4.1. Sorry I didn't catch this before, I'm not super familiar with the conda release process.

the test-r-rtools-35 task appears to have a yaml syntax error in it so it didn't run which might be that the block after the job name needs one more indent (though my eye for spotting yaml errors is terrible, so it might be something totally different!)?

I believe the other failures (test-r-without-arrow, r-sanitizer, and r-valgrind are all on-going failures unrelated to this).

@gh-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

I ran the crossbow steps manually last night (it took some juggling, but I was impatient waiting for #10440 to merge). There were a few things I noticed:
* the `conda-*-r41` builds failed cause they [were looking for a file `arrow/dev/tasks/conda-recipes/.ci_support/r/linux_64_r_base4.1.yaml`](https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5987&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=4803) I imagine this can copy the 4.0 files that are already there in that folder bumping 4 to 4.1. Sorry I didn't catch this before, I'm not super familiar with the conda release process.

* the `test-r-rtools-35` [task appears to have a yaml syntax error in it so it didn't run](https://github.com/ursacomputing/crossbow/actions/runs/901048826) which might be that the block after the job name needs one more indent (though my eye for spotting yaml errors is terrible, so it might be something totally different!)?

I believe the other failures (test-r-without-arrow, r-sanitizer, and r-valgrind are all on-going failures unrelated to this).

Thanks for taking a look at these @jonkeane!  Have now submitted a PR with some changes and running the CI, so will see how it goes! :)

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit test-r-rtools-35

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit conda-linux-gcc-py37-cpu-r41

@github-actions crossbow submit conda-*

U people at GitHub are invading my life! And have been for two years! Right
this moment y’all are taking everything of my computer out of my phone all
my personal stuff and it’s not the first time either going off one persons
day so and you are being lied to! Get out of my life or I’m going to report
all of github! To the police the FBI anyone that will listen!
Rhonda Cordell
@.***
214-023-1680
On Thu, Jun 3, 2021 at 2:56 PM Jonathan Keane @.***>
wrote:

@github-actions https://github.com/github-actions crossbow submit
test-r-rtools-35
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow/pull/10389#issuecomment-854137493, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANYAKWHPCN2P2F2XEMLO7ITTQ7M63ANCNFSM45NNYGYQ
.

--
Rhonda Cordell


feat: use fs2 for locking and increase request timeout to 60 secs

this replaces the old locking code with fs2::FileExt

also bumps timeout to 60 secs, default is 30 and can be exceeded easily on slow networks

@mattsse thank you! Looks great :)


Add s390x arch docker image

S390x PR https://github.com/traefik/traefik/pull/8729 is merged in Traefik
For Docker library images to publish s390x docker image, this PR is necessary.
Fix #20

https://github.com/docker-library/official-images/#architectures-other-than-amd64

https://github.com/docker-library/official-images/#architectures-other-than-amd64

Hello @ldez , what I understood is that when Traefik releases a new version in Feb last week which will have support for s390x, the https://github.com/docker-library/official-images repo will be updated with new version and will add s390x to this line https://github.com/docker-library/official-images/blob/master/library/traefik#L11, then docker library scripts will run this Dockerfile https://github.com/traefik/traefik-library-image/blob/master/alpine/Dockerfile. So, I made this PR.
Let me know if my understanding is wrong. Thanks :)

Hi @ldez , any reviews on this ? Thanks

@ldez , docker still outputs s390x images in Jenkins - https://doi-janky.infosiftr.net/job/multiarch/job/s390x/

We will manage the Docker part.


AllowErrors option for UnmarshalOptions

Is your feature request related to a problem? Please describe.
I have a message  like
message Request {
      repeated Event = 1;
}
message Event {
     optional int64 someField = 1;
     int64 otherField = 2;
}

If there're several events in the request and if one of them have an error, for instance in someField, the request will be failed.
But it would be better, to have an option to ignore fields with errors, like AllowPartial and DiscurdUnknown options in UnmarshallOptions.
Describe the solution you'd like
Check this pull request https://github.com/protocolbuffers/protobuf-go/pull/29

This is kind of a complicated process. Let’s presume that the stream loses a byte from the data. At this point all data following that lost bit is going to be garbage. This is part of the trouble with a non-self-correcting encoding.

This is the issue board for the protobuf-go project as well. In fact that repo doesn’t even have an Issues tab, because issues are handled here.


DateField: fix locales in MM/DD/YYYY format

Summary
What changed?
DateField: fix locales in MM/DD/YYYY format
Assessment: https://coda.io/d/_d2LeXkQ1kVX/DateField_sukKr#_luoyc
BEFORE

AFTER

Works, some comments on possible re-ordering.
Can you also add a test for a MUI JS locale and non MUI-JS, and incorrect locale code

speaking of tests ha


pip3 install dlib   error

[root@LAX10-dynCe-001 ~]# pip3 install dlib
Collecting dlib
Using cached dlib-19.24.0.tar.gz (3.2 MB)
Preparing metadata (setup.py) ... done
Using legacy 'setup.py install' for dlib, since package 'wheel' is not installed.
Installing collected packages: dlib
Running setup.py install for dlib ... error
error: subprocess-exited-with-error
× Running setup.py install for dlib did not run successfully.
│ exit code: 1
╰─> [71 lines of output]
running install
running build
running build_py
package init file 'tools/python/dlib/init.py' not found (or not a regular file)
running build_ext
Building extension for Python 3.7.0 (default, Aug 20 2022, 23:46:01)
Invoking CMake setup: 'cmake /tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/tools/python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/build/lib.linux-x86_64-3.7 -DPYTHON_EXECUTABLE=/usr/local/python3/bin/python3.7 -DCMAKE_BUILD_TYPE=Release'
-- The C compiler identification is GNU 4.8.5
-- The CXX compiler identification is GNU 4.8.5
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PythonInterp: /usr/local/python3/bin/python3.7 (found version "3.7")
-- Found PythonLibs: /usr/local/python3/lib/libpython3.7m.a
-- Performing Test HAS_CPP14_FLAG
-- Performing Test HAS_CPP14_FLAG - Failed
-- Performing Test HAS_CPP11_FLAG
-- Performing Test HAS_CPP11_FLAG - Success
-- pybind11 v2.2.4
-- Using CMake version: <IP_ADDRESS>
-- Compiling dlib version: 19.24.0
CMake Error at /tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/dlib/cmake_utils/set_compiler_specific_options.cmake:50 (message):
C++11 is required to use dlib, but the version of GCC you are using is too
old and doesn't support C++11.  You need GCC 4.9 or newer.
Call Stack (most recent call first):
CMakeLists.txt:8 (include)
  CMake Error: Internal CMake error, TryCompile configure of cmake failed      -- Configuring incomplete, errors occurred!
  See also "/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/build/temp.linux-x86_64-3.7/CMakeFiles/CMakeOutput.log".
  See also "/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/build/temp.linux-x86_64-3.7/CMakeFiles/CMakeError.log".
  Traceback (most recent call last):
    File "<string>", line 36, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/setup.py", line 261, in <module>
      'Topic :: Software Development',
    File "/usr/local/python3/lib/python3.7/site-packages/setuptools/__init__.py", line 129, in setup
      return distutils.core.setup(**attrs)
    File "/usr/local/python3/lib/python3.7/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/usr/local/python3/lib/python3.7/distutils/dist.py", line 966, in run_commands
      self.run_command(cmd)
    File "/usr/local/python3/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/usr/local/python3/lib/python3.7/site-packages/setuptools/command/install.py", line 61, in run
      return orig.install.run(self)
    File "/usr/local/python3/lib/python3.7/distutils/command/install.py", line 545, in run
      self.run_command('build')
    File "/usr/local/python3/lib/python3.7/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/usr/local/python3/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/usr/local/python3/lib/python3.7/distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/usr/local/python3/lib/python3.7/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/usr/local/python3/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/setup.py", line 134, in run
      self.build_extension(ext)
    File "/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/setup.py", line 171, in build_extension
      subprocess.check_call(cmake_setup, cwd=build_folder)
    File "/usr/local/python3/lib/python3.7/subprocess.py", line 328, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/tools/python', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-install-1cm_vc8f/dlib_2adfd23dc77a4d09a7dbfdca13b1f274/build/lib.linux-x86_64-3.7', '-DPYTHON_EXECUTABLE=/usr/local/python3/bin/python3.7', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> dlib
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

请问问题是否解决

请问问题是否解决

还没呢


store both hotel name formats

Preserve both name formats - our "short" name and the hotel "real" name (or a close approximation thereof).

Only short name should be displayed to users

Admins can see both

Include "real" name in the export

Hmm yea we had hoped to avoid that having one set of names for t3 and one set of names for hotel. kinda seems we are falling back to that. unless we can derive the hotel names from existing fields?

I think we can kinda derive but the closest we can get to the "hotel name" is by using what we get from them.
Short term solution - store both in room record
Long term solution - move the ROOM_TYPES constant and it's friends into a separate table and then just link


python311Packages.nibe: 2.7.0 -> 2.8.0

Diff: https://github.com/yozik04/nibe/compare/refs/tags/2.7.0...2.8.0
Changelog: https://github.com/yozik04/nibe/releases/tag/2.8.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

3 packages built:

home-assistant-component-tests.nibe_heatpump
python311Packages.nibe
python311Packages.nibe.dist


Implement stream() for FakeService

TestService: Minor refactor of imports
Add support in FakeService for stream()

Updated accordingly


Initial implementation of ByteCountFormatter

Implemented ByteCountFormatter and created tests.
All tests run and pass on MacOS.

@swift-ci please test

@parkera  Hi Tony, I've added most of the suggested tests. I've also updated the ByteCountFormatter so the tests now pass on both Mac and Linux.
I couldn't work out what the 'maximum' property is that is being set in some of the tests so I've omitted them for now but if you can provide more information about the maximum property I will add those as well.
Thanks.

Sorry about the maximum arg, that is an artifact of the way our tests are constructed internally. Omitting it makes sense.

@swift-ci please test and merge

Thanks for the great contribution!


timetz test fails in EDT

https://github.com/lolopinto/ent/blob/main/ts/src/schema/postgres_schema_live.test.ts#L366-L406

src/graphql/tests/hours_of_operation_type.test.ts in examples/simple also fails


Setting up Email triggers

Since we are making a project that has to manipulate one's cluster, we should have email triggers set up. Emai, triggers can act as AWS SNS. I am even not sure if it can be implemented in what manner, but surely can be handy feature.
You might want to use this package Email

I will add this part when

#21
is done. Since Emil triggers should be fast and done as the event is done.
SharedIformers are great approach to achieve this


No subscription found.

After runnnig project I have error- No subscription found.
Thank`s for help.

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

ID: 23ae77b5-542a-b032-20ec-bf81d041fde0
Version Independent ID: 70356207-120a-09a8-f8ab-bfdd9b02ad1f
Content: Power BI Embedded Migration Tool - Power BI
Content Source: powerbi-docs/developer/migrate-tool.md
Service: powerbi
GitHub Login: @markingmyname
Microsoft Alias: maghan

@vladpach Thanks for your comment. This looks like a support request rather than documentation feedback – you can get support by going to https://support.powerbi.com. You might find a solution in the Power BI Community, found at https://community.powerbi.com.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Is this useful?

I would like to discuss and get your opinions about whether this workshop is useful at all and should be submitted to the deRSE20 conference. I think, it is, but please tell me if I am wrong :wink:

Hi Philipp, i think your workshop idea is very useful! maybe it's good to focus on packaging (python) software in general and how to write (python) code more abstract in package style. then in the end, show how to distribute it via conda. i think most people struggle more with designing a package in general rather than how to distribute it.

maybe test-driven development would also be interesting if the workshop should focus in ci.

Hey @larsbuntemeyer! I apologize for not replying to your comments! It came during a very busy time and then I forgot to answer. There hasn't been a lot of traffic in this repository, so the question is, whether this is actually desired by the community (or are people just waiting until the very last minute?). Anyway, although we are already behind the time line that I had in mind (which is my fault, sorry), we still have 16 days until the abstract should be submitted.
I totally agree with you, most scientists rather struggle with formulating their ideas in form of a package, and therefore it would be more useful to teach them how to do so. But there exists already a lot of online tutorials and examples how to setup such a python package (simply google python packaging and you will find at least three pretty extensive ones). These do, of course, not necessarily have RSEs in mind but a more general scope. But what is special about research software in terms of packaging, that makes it worth to create another packaging guide for python?


ReferenceConfigCache doesn't work well when no provider

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.2 and lower
Operating System version: all version
Java version: all version

Step to reproduce this issue

shutdown provider
consumer side use ReferenceConfigCache.get() to invoke provider
invoke provider one time
startup provider
invoker provider again

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
when provider startup, the second time invoke should success.
Actual Result
second time invoke failed
What cause it
When no provider, config.get() return null, at this time we shouldn't store this reference into cache.
public <T> T get(ReferenceConfig<T> referenceConfig) {
        String key = generator.generateKey(referenceConfig);

        ReferenceConfig<?> config = cache.get(key);
        if (config != null) {
            return (T) config.get();
        }

        cache.putIfAbsent(key, referenceConfig);
        config = cache.get(key);
        return (T) config.get();
    }

@YoungHu Could u please send a PR to solve this problem ?

PR already done

The same issue: #1765 . But it's not ReferenceConfigCache's problem.
I think we need to fix it like #1999

@YoungHu Could u refer to #1999 and fix it on dubbo-2.6.x ?

will check it tomorrow by using the master branch code

confirmed this issue fix at master branch with #1999 ,close this one


Squash server error on minikube

After following the k8s installation guide here, looking at squash-server logs I see an edless series of
ERROR: logging before flag.Parse: E0802 13:05:06.865750       1 reflector.go:205] github.com/solo-io/squash/pkg/platforms/kubernetes/crd/client/informers/externalversions/factory.go:60: Failed to list *v1.DebugAttachment: debugattachments.squash.solo.io is forbidden: User "system:serviceaccount:squash:squash-server" cannot list debugattachments.squash.solo.io at the cluster scope

I can see this just after the squash-server has been deployed in minikube.
At the same time squash --url=http://SQUASH-SERVER-ADDRESS/api/v2 list attachments seems to respond correctly despite the errors in the logs, but attaching the debugger to a pod doesn't work.
Versions:

minikube: v0.28.0
k8s:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.5", GitCommit:"f01a2bf98249a4db383560443a59bed0c13575df", GitTreeState:"clean", BuildDate:"2018-03-19T15:59:24Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

I would like to know how to setup squash server. I don't find it in the setup instructions which only mentions cli. Can you point me towards the setup guide or instructions? Thanks.


Create generic initializer for middlewares

At the moment .NET Core uses number of middlewares which are too small to have own initializer. It's suggested to create generic initializer which accepts lambda expressions to be used to Configure() and ConfigureServices()

Fixed


MINOR: improve test coverage for dynamic LogConfig(s)

Adding a dynamically updatable log config is currently error prone, as it is easy to set them up as a val not a def and this would result in a dynamically updated broker default not applying to a LogConfig after broker restart.
This PR adds a guard against introducing these issues by ensuring that all log configs are exhaustively checked via a test.
For example, if the following line was a val and not a def, there would be a problem with dynamically updating broker defaults for the config.
https://github.com/apache/kafka/blob/4bde9bb3ccaf5571be76cb96ea051dadaeeaf5c7/core/src/main/scala/kafka/server/KafkaConfig.scala#L1216

Scala 2.11 compile issues are present.

@dhruvilshah3 thanks, your suggestion was great and picked up a couple of minor issues. PR is ready to merge when ready.

This needs a rebuild by a committer.

ok to test

retest this please

One flake in JDK 11 and scala 2.13: kafka.api.ConsumerBounceTest.testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup.
No failures in scala 2.12.
Looks like we're good to merge @ijuma or @mumrah


ImportError: cannot import name 'BeanieBaseUser' from 'fastapi_users.db'

Describe the bug
I am trying to update fastapi-users from version 5 to 10, but it fails at the beginning when I am trying to import BeanieBaseUser
ImportError: cannot import name 'BeanieBaseUser' from 'fastapi_users.db'
my user file looks like this:

from beanie import PydanticObjectId
from fastapi_users.db import BeanieBaseUser, BeanieUserDatabase
from fastapi_users import schemas

class User(BeanieBaseUser[PydanticObjectId]):
    nick_name: str

A clear and concise description of what you expected to happen.
Configuration

Python version : 3.8
FastAPI version : 0.71.0
FastAPI Users version[beanie] : =5.1.0 ->10.0.0

There is indeed a circular import issue 😞 I'll fix this right away! Thank you for reporting!

It should be fixed with fastapi-users[beanie] >= 10.0.1 (check that fastapi-users-db-beanie == 1.0.1 is installed after that).

Thank you
but now I have a new one
api_1          |   File "/usr/local/lib/python3.8/inspect.py", line 2854, in from_callable
api_1          |     return _signature_from_callable(obj, sigcls=cls,
api_1          |   File "/usr/local/lib/python3.8/inspect.py", line 2228, in _signature_from_callable
api_1          |     raise TypeError('{!r} is not a callable object'.format(obj))
api_1          | TypeError: <fastapi_users_db_beanie.BeanieUserDatabase object at 0x7f16042ad040> is not a callable object

@galvakojis I received an e-mail notification with a new comment you posted, but I can't see it. Did you delete it?

Hi, @frankie567 I'm using the 10.0.5  fastapi_users version, and I have the same problem. I verified the fastapi_users_db_beanie  version and it's 1.0.1.

Some idea?


[WIP] Changes to how retirement benefits are computed

This PR aims to do 3 things:

Replace hardcoded values for parameters used to compute replacement rates with flexible parameters.
Allow users to specify a retirement age in calendar years (as opposed to model periods) by making this a parameter.
Fix the bug described in Issue #400, where the period of retirement is not handled correctly for some cohorts along the time path.

Removing point #3 since I was mistaken in thinking this was a bug as noted in Issue #400.


Update website (currently 1.1.0)

The website (https://reach.tech/router) is at an outdated version (1.1.0).
It should be updated to match the last release, so it includes the new hooks.

Website has been updated!


Force cURL to use ipv4 for Dns resolving

I had an issue today trying rollbar for the first time. After a few debugs i realised that curl_exec returned false.
curl_error returned it "cannot resolve host". After a few searches i managed to make it works by adding that curl option that forces it to resolve hostname into an IPV4 address.
I tested it on a vagrant VM using virtualBox on Windows 8.1
My VM : Ubuntu server 14.04, PHP 5.5.14, cUrl 7.35.0

This definitely should not have been accepted 😂


Allow traffic to istio-sidecar-injector on port 9443.

Problem
NetworkPolicy blocks traffic from API server to istio-sidecar-injector.
Solution

Allow everyone to access istio-sidecar-injector on its https port.
Remove other ports from NetworkPolicy.
Remove NamespaceSelector since API server has no namespace.

Fixes https://github.com/cloudfoundry/cf-for-k8s/issues/69

Thanks @jkbschmid!
I commented on this in the original issue (https://github.com/cloudfoundry/cf-for-k8s/issues/69#issuecomment-601265320), but want to mention it here as well that this is a big indicator that the GKE clusters we're testing with in CI are not providing enough coverage.
Created a placeholder story for us to address this: https://www.pivotaltracker.com/story/show/171883349


Replacing reconcile-based EDSR clean-up with owner reference

This PR reverts #252 and replaces reconcile-based EDSR clean-up on EdgeDevice removal.

This approach is not feasible in our case - cross-namespace owner references are not allowed and EdgeDevice and EDSR may (and probably often will) end up in different namespaces.


Dashboard: Hide scheduled items

I always write todos in my daily note, and I generally schedule them for some day in the future.
Once an item is scheduled and it's not scheduled for today, I don't think it should clutter my dashboard.
For instance, here's a task I wrote today and immediately scheduled it. I don't want to see it in today's dashboard anymore, because for now at least, it's taken care of.

Good idea, and already implemented. At least if you're using the existing 'scheduled' paragraph type. Any reason you're not using this?

@dwertheimer by the look of it, I added this in v0.6.2, but forgot to note it.
Please could you check it's doing what you wanted?

Thank you @jgclark


Feature/db and azure

@macegrace Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


update arrow to 5.0

 Update Arrow to 5.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 20 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 79.663%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
18516

Relevant Lines:
23243

💛  - Coveralls


Missing mochi demos in google drive

Dear authors,
Many thanks to your work on such a comprehensive VideoGen evaluation project. It's great to see so many video samples from a wide range of models which are really easy to compare with. I found that the videos from mochi, the recently released open-source model, existing on the project page, but missing in google drive. Would you please do us a favor and upload them on google drive?
Thanks,
Xiangyu

Hi, the results of Mochi1 have been uploaded to Google Drive

Thanks!


Minimal improvement of loadMoreOnPan

Hi,
I think it's very useful add range of right side of element to load to load more data on both side.
Thanks
Load_more_on_both_side.patch.txt

where do you see the usecase to download data on right?

Hi,
in my case I have a filter for date ranges over historical data and after load they continue browsing the data left and right.

Mmmm... It's work, and it's clean, but in my specified case I have some problem with performance, so my backend colleagues create for me a REST call to get data from left and right in one call.
This is  needed, only for zoom, with 2 call for left and right when zoom are called all 2 function.
Even if my change is not breaking, I add 2 parameter at the end so you can use
onLoadMore(start, end)
the same way as before, at beginning of code you have this condition
if (Math.ceil(start) === end) return;
if the change is only right start and end is 0 (i think).
At the same way I can recreate a single call whit this code
onLoadMoreLeft={this.handleLoadMore}
onLoadMoreRight={(start, end)=>this.handleLoadMore(0,0,start,end))}
the only problem is that I have 2 call when zoom.


nomination-pools: Defer first reward claim for 2 eras

When a delegator first joins a nomination pool, we record the reward_pools_total_earnings at the exact point in time. However, at best the reward pool has the rewards up through the previous era. If the delegator joins prior to the snapshot they will benefit from the rewards of the active era despite not contributing to the pool's vote weight. If they join after the snapshot is taken they will benefit from the rewards of the next 2 eras because their vote weight will not be counted until the snapshot in active era + 1.
In order to be fair to current pool members, all new joiners should wait for 1-2 eras to have their reward_pools_total_earnings set. Prior to having it set they should not be able to claim rewards because they have not contributed to the pools vote weight.
One way to achieve this would be to make delegator's reward_pools_total_earnings an enum:
DelegatorRewardPoolState {
 /// The delegator joined in `era` and must wait until `era + 2` to record the reward pool's total earnings
 JoinEra { era: EraIndex }
 RewardPoolsTotalEarnings { earnings: BalanceOf<T> }
}

Then we could expose an extrinsic that allows anyone to flip a delegator from JoinEra to RewardPoolsTotalEarnings if the current era is >= JoinEra::era + 2.
This approach would maintain the nomination pools design goal of being constant complexity relative to delegators. However it would make the UX for new joiners less friendly because they would have to call this second extrinsic with some time delay after initially joining in order to start earning rewards.
Should wait until #10694 is merged to start working on this.

@emostov I would like to work on this

cc @kianenigma

we're feature freezing pools for now for the initial release, so preferably let's wait out a bit. I will mark it as mentor again once it is ready.

This not relevant anymore as of #11669


[fix][install script] Java8 manual installation desc.

Without this the manual process fails.

CI fails same as https://github.com/130s/hut_10sqft/pull/166#issuecomment-320080612. Merging.


Single select dropdown does not close on 'select' when searchable

Hi,
I have a multiselect instance with following config/props:
:options="list"
id="single-select"
track-by="id"
:custom-label="option =>${option.id '} ${option.name'}"
:allow-empty="false"
:close-on-select="true" (which is also default, I know)
v-model="selected"
I want the single-select to be searchable (which is default) and to close on selection. Unfortunately, on 'select' the dropdown stays opened and in dev-tools I can see, that on selection 4 different events are emitted in the following order:

select
input
close
open

They are all fired by vue-multiselect and i don't know why the last 'open' event is there when I expect the dropdown to close. When I set 'searchable' to false the dropdown acts as expected. I tried adding preserve-search="false", but did not work.
The select stays open only when I select the option with mouseclick, when I press 'enter' to select the option everything works fine.
Thanks in advance for any hints on how to solve the problem!
Reproduction Link
Steps to reproduce
singleselect with seearchable = true and closeOnSelect = true
Expected behaviour
dropdown should close on select
Actual behaviour
dropdown stays opened after selection with mouseclick

Is your multiselect element wrapped in a LABEL element? If so, remove that nesting.

Please provide a JSFiddle or CodeSandbox with a repro.

failing version (2.1.2+) https://jsfiddle.net/6Lsgzhw0/3/
previous behavior (2.1.0) https://jsfiddle.net/xo8n1g2p/5/
My guess would be that the parent is selected and this forwards the focus back to the multiselect.
Maybe you should not give the focus to the parent but instead keep the focus but have the multiselect in the closed state (like the regular select in the 2.1.2 example). This would ensure that (shift+)tab still focuses the correct element before or after.
The open state should be triggered if:

the multiselect gets focused initially
the multiselect is focused and is closed and receives a mouse click or keyboard input (characters or enter)

selecting an element with the keyboard closes the dropdown but looses the tab focus position

The <label> wrapper was the culprit for me. Thanks a bunch @elDub!

Thats was hard to find, and very unexpected change in minor version...

Maybe you should not give the focus to the parent but instead keep the focus but have the multiselect in the closed state (like the regular select in the 2.1.2 example). This would ensure that (shift+)tab still focuses the correct element before or after.

@qwesda this is how it behaves in v3. Just need to release it...
@ReDev1L Sorry to hear that.


Composer install error

[RuntimeException]
Could not load package seretalabs/monolog-fluentd-bundle in http://packagist.org: [UnexpectedValueException] Could not parse version constraint v0.3.*: Invalid version string "v0.3.*"
Guess is here: https://github.com/Elexy/SeretalabsMonologFluentdBundle/blob/v0.4.0/composer.json

I'll have a look when I'm back in the office on Monday

News ? I've the same problem.

seems to be something with composer, just tried here with:
"seretalabs/monolog-fluentd-bundle": "^0.4.0"
in composer.json and just works.
Can you give me more info?


Compilation error on QT example

When building on my local system (which apparently has QT installed), the QT example is configured to build but the example fails to compile. The error message is:
Scanning dependencies of target qt_exe
[ 85%] Building CXX object examples/qt/CMakeFiles/qt_exe.dir/qt.cpp.o
/var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp: In function ‘void qt_main(int, char**)’:
/var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:47:38: error: reference to ‘_1’ is ambiguous
     widget main(hpx::util::bind(run, _1, _2));
                                      ^
In file included from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/lcos/detail/future_data.hpp:19:0,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/lcos/future.hpp:22,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/actions/action_support.hpp:14,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/actions/transfer_action.hpp:15,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/parcelset/parcel.hpp:14,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/applier/applier.hpp:18,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/server/create_component.hpp:13,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_factory.hpp:46,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/components.hpp:13,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/runtime.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/hpx.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:6:
/var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/bind.hpp:47:53: note: candidates are: constexpr const hpx::util::detail::placeholder<1ul> hpx::util::placeholders::_1
         HPX_STATIC_CONSTEXPR detail::placeholder<1> _1 = {};
                                                     ^
In file included from /usr/include/boost/bind/bind.hpp:2030:0,
                 from /usr/include/boost/bind.hpp:22,
                 from /usr/include/boost/thread/pthread/once_atomic.hpp:19,
                 from /usr/include/boost/thread/once.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/detail/dll_dlopen.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/dll.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/plugin_factory.hpp:15,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_registry_base.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_registry.hpp:12,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/components.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/runtime.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/hpx.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:6:
/usr/include/boost/bind/placeholders.hpp:55:15: note:                 boost::arg<1> {anonymous}::_1
 boost::arg<1> _1;
               ^
/var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:47:42: error: reference to ‘_2’ is ambiguous
     widget main(hpx::util::bind(run, _1, _2));
                                          ^
In file included from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/lcos/detail/future_data.hpp:19:0,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/lcos/future.hpp:22,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/actions/action_support.hpp:14,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/actions/transfer_action.hpp:15,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/parcelset/parcel.hpp:14,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/applier/applier.hpp:18,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/server/create_component.hpp:13,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_factory.hpp:46,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/components.hpp:13,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/runtime.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/hpx.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:6:
/var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/bind.hpp:48:53: note: candidates are: constexpr const hpx::util::detail::placeholder<2ul> hpx::util::placeholders::_2
         HPX_STATIC_CONSTEXPR detail::placeholder<2> _2 = {};
                                                     ^
In file included from /usr/include/boost/bind/bind.hpp:2030:0,
                 from /usr/include/boost/bind.hpp:22,
                 from /usr/include/boost/thread/pthread/once_atomic.hpp:19,
                 from /usr/include/boost/thread/once.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/detail/dll_dlopen.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/dll.hpp:20,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin/plugin_factory.hpp:15,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/util/plugin.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_registry_base.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/runtime/components/component_registry.hpp:12,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/components.hpp:11,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/include/runtime.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/hpx/hpx.hpp:10,
                 from /var/lib/buildbot/slaves/apex/master-hpx3/build/examples/qt/qt.cpp:6:
/usr/include/boost/bind/placeholders.hpp:56:15: note:                 boost::arg<2> {anonymous}::_2
 boost::arg<2> _2;
               ^
examples/qt/CMakeFiles/qt_exe.dir/build.make:60: recipe for target 'examples/qt/CMakeFiles/qt_exe.dir/qt.cpp.o' failed
make[3]: *** [examples/qt/CMakeFiles/qt_exe.dir/qt.cpp.o] Error 1
CMakeFiles/Makefile2:9183: recipe for target 'examples/qt/CMakeFiles/qt_exe.dir/all' failed
make[2]: *** [examples/qt/CMakeFiles/qt_exe.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
Linking CXX executable ../../bin/vector_counting_dotproduct
[ 85%] Built target vector_counting_dotproduct_exe
CMakeFiles/Makefile2:998: recipe for target 'CMakeFiles/examples.dir/rule' failed
make[1]: *** [CMakeFiles/examples.dir/rule] Error 2
Makefile:537: recipe for target 'examples' failed
make: *** [examples] Error 2

It seems boost::bind is finding its way into the code, indirectly via some other #include. Boost.Bind defines placeholders in the global namespace (bad), which results in this kind of ambiguity. We'll need to avoid using namespace hpx::util::placeholders here and everywhere else.

Should be fixed by 7b957b2f49ffbac36bf72e1f946238ff06b7b9d4. Would you try it out and report back?

Fixes it for me, thanks!
On 12:21 Fri 22 Apr     , Agustín Bergé wrote:

Should be fixed by 7b957b2f49ffbac36bf72e1f946238ff06b7b9d4. Would you try it out and report back?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/STEllAR-GROUP/hpx/issues/2111#issuecomment-213560199

--
Andreas Schäfer
HPC and Supercomputing
Institute for Multiscale Simulation
Friedrich-Alexander-Universität Erlangen-Nürnberg, Germany
+49 9131 85-20866
PGP/GPG key via keyserver
http://www.libgeodecomp.org
(___/)
(+'.'+)
(")_(")
This is Bunny. Copy and paste Bunny into your
signature to help him gain world domination!


Avoid decoding nvcc output with UTF-8

Fixes #378 by avoiding decoding nvcc output.
Notes:

The result of this function (preprocess) is only used to generate md5 digest. So there's no need to decode it.
The result (bytes) is used in str formatting (https://github.com/cupy/cupy/blob/accf3ad237f6cf63710852df2d5d7d37f05830ee/cupy/cuda/compiler.py#L126), but the type difference doesn't matter; different values of preprocess(...) will result in  different pp_src, even if it's bytes. It's enough as a key to generate hash digest.

LGTM!


index.php not showing content

Hello,
When I work with index_dev.php everything works fine, but index.php is not showing anything.
I have deleted the cache but the problem persists.
What can I do?
Thank you.

The profiler cache ?

@kabdessamad1 I fixed it deleting the full cache folder and also the browser cache using Onyx, not just the Firefox
Thank you anyway!


Implement read-through caching

On package miss, go to nuget.org to download the package.
See https://github.com/NuGet/NuGetGallery/issues/5430

Added basic RemotePackageService. On package lookups, the remote package service will attempt to index packages from nuget.org if they do not exist in the database "cache".

Done.


Support placeholders on File instances

This lets you pass instances of File as properties.

Nice. Should we release a new version?


Task – New message button appears when edit very long description few times

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

Version Number: 9.0.40-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5006359
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Log in
Open any group chat
Create a task with very long description (1000 characters) and assign to any user
Open task details and click on description
Edit description, save and scroll the page up
Edit description, save and scroll the page up again

Description:
Space is a three-dimensional continuum containing positions and directions.[1] In classical physics, physical space is often conceived in three linear dimensions. Modern physicists usually consider it, with time, to be part of a boundless four-dimensional continuum known as spacetime.[2] The concept of space is considered to be of fundamental importance to an understanding of the physical universe. However, disagreement continues between philosophers over whether it is itself an entity, a relationship between entities, or part of a conceptual framework.
In the 19th and 20th centuries mathematicians began to examine geometries that are non-Euclidean, in which space is conceived as curved, rather than flat, as in the Euclidean space. According to Albert Einstein's theory of general relativity, space around gravitational fields deviates from Euclidean space.[3] Experimental tests of general relativity have confirmed that non-Euclidean geometries provide
Expected Result:
New message button not appears
Actual Result:
New message button appears
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/92a8a4c7-590b-4342-afcd-d5d68931a5ce

View all open jobs on GitHub

I somewhat think this is expected behavior, what do you think @alexpensify ?

@AndrewGable - I agree with you and going to close for now. Heads up, I'm not feeling well today and was already planning to be OOO tomorrow. I'll try to check in if something is urgent here.


⚠ Bofrost.lu has degraded performance

In 0884a61, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2013 ms

Resolved: Bofrost.lu performance has improved in cc0493c after 39 minutes.


Default bck.conf

Just a small attempt at making the conf easier to use and cleaner (still require a lot more rework)

Thanks for PR.
Did you check if in config parser it can parse tilda ~ and expand it to users HOME?
Because as I remember originally it was written for full path.

no I didn't :D
Btw I might try to make it cleaner again, it was just an example, I can't help much anyway

The PR is not valid anymore as there are too much changes since last release.
Closing for now.

?? not really https://www.diffchecker.com/waWY1OTw

@ShahriyarR

Can you look at the diffcheck above please, it's suggestion for more logical names (the only thing you have to ignore is the TESTS part)
@ShahriyarR

There is no need for this patch as I have implemented new thing in release_v1.5.4.
It is going to create several options dynamically inside ~/.autoxtrabackup/autoxtrabackup.cnf  please check it and you will see, now backup_dir for example takes home or ~ dynamically.
@BarbzYHOOL


[SDS-NNN] Changes needed to display correct html again

Changes in conf.py and css file in _static\theme_overrides to:

display correct html output
correct for the wide tables

Coverage remained the same at 100.0% when pulling 438cc04b4b63c440247ed92c47725b50af15c02c on fix/SDS-NNN/read_the_docs_html_fix into 3ef709ecba2d3c8194fc334d537bcd690f9ccbf0 on dev.

Building the documentation on windows fails, because pandoc is not installed by default:
> pip install -e .[rtd]
> cd docs
> make html
Running Sphinx v4.3.2
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 20 source files that are out of date
updating environment: [new config] 20 added, 0 changed, 0 removed
reading sources... [ 25%] examples/example_projectq
Notebook error:
PandocMissing in examples\example_projectq.ipynb:
Pandoc wasn't found.
Please check that pandoc is installed:
https://pandoc.org/installing.html

pip install pandoc only installs the python wrapper functions for the pandoc executable. The actual pandoc executable must have been installed already in the system. This should be mentioned in the README.
After installing pandoc via the website mentioned in the message, the documentation build succeeds.


Update NPM package to include support for wildcard model folder structure.

I really love that new feature with the wildcard support, any chance you could update the NPM package so it includes this new feature? Right now I have to manually download this and replace the code in my node_modules.

Alright, seems that this commit a5c31641cf1d14c19ce9711145f178d4bf53fc61 has fulfilled my request.


use vim.keymap.set

You can leave a separate branch for those who are using version 0.5.0

Sure !

Just merged the PR, you can use compat-0.5 branch for backward compatibility.


Can't use post publish dropdown with a screen reader

Hello,
I'm a screen reader user, and have occasionally tried and failed to use Ghost. My blocker is the button for setting a post's publication status. This control has the following issues:

It is apparently a dropdown, but only reports as a button. You may want to use aria-expanded here.
When clicked/expanded, none of the child elements are focusable, or keyboard-interactable in any way.
I'm using Orca under Linux, and even using its mouse emulation mode, I can't seem to click on any of the publication options.

I looked at the code but am not overly familiar with Ember, so I'm wondering if this would be a quicker fix for someone with that knowledge? In particular, it looks like you may be using a basic-dropdown component, but I'm not clear if that ships with core Ember/a third party dependency, and if it gives you the flexibility you need to fix this.
The quickest fix would likely just be making the dropdown elements <button/> so you'd get accessibility for free. The second quickest would likely be slapping role="button" on whatever elements you do use, setting tabindex="0", and adding key handlers for space/enter. If you use this pattern lots, make that a component for reuse.
If someone were to start a PR, I'm happy to test it. But a PR would also show me what specifically to change, so I can probably iterate on it myself and fix any remaining issues. But, chances are that if you can tab/arrow to the publication states and activate them via the keyboard, then things will just work.
In the meantime, is there any other way to tweak publication state other than spelunking in the database? :)
Thanks.

I fixed this issue with aria-expanded not being set when the dropdown is collapsed, in https://github.com/cibernox/ember-basic-dropdown/pull/556. Once a new version is released and the package updated in the Ghost Admin client, this fix will automatically propagate.
However, the other problem is that the children of the dropdown are being aria-owned into the button element. So they become children of the button on the accessibility tree side. NVDA deals with this okay‘ish, VoiceOver, too. But Orca seems to be less forgiving. The problem is that, if this wasn‘t the case, the new content would be far far away from the actual button DOM-wise. Not sure how to solve that in the basic-dropdown component, which is where this fix must happen.

Ah, so the menu options get added directly inside the ? That is
going to make things a bit more complicated, particularly as I don't
think Firefox even exposes button text to Orca in a way that can be
interacted with (I.e. no reading character by character through button
labels.)
Wondering if it'd be worth transitioning to using <details/> and
<summary/> instead? I'd try, but would almost certainly break the styling.
Is it legal HTML to have interactive elements as children of buttons?
Not that that ever stopped anyone before, but it'd probably be easier to
make a case for fixing Orca if it wasn't handling correctly-formatted
HTML. :)

I don't want to hijack this issue, but are there any alternative ways of
publishing to Ghost? Spent some time seeing how hard it'd be to move
dropdown children out of the button, and I think it'll take me far down
a rabbit hole that I don't have the time to explore right now. I'm
trying to create a membership site, and my options are currently:

Fix this accessibility issue so I can use Ghost under Linux.

Find an alternate means of publishing that doesn't use the
inaccessible-to-me interface.

Pursue my initial plan of using Hugo, and rolling my own auth
integration using Cloudflare Workers and a third-party auth provider.

1 is probably beyond what I have time for now, and involves learning way
too much. 3 is lots of work, but uses technologies I already have lots
of familiarity with. That just leaves 2, but so far I'm not finding
alternative publishing methods, unless the Ghost desktop client uses a
different interface.
Thanks, and apologies for the noise. I'd hate to not use Ghost because
there's some alternate way to publish that I just haven't found yet. :)

@ndarilek I think I fixed it. Can you try this preview? It opens a set of unlabeled buttons from the top navigation bar, but if you call up Docs, then How To Use, there are more there that show some more useful content when expanded.

Nice, the dropdown at that link does expose a series of unlabelled buttons.
Just a couple issues that may not be specific to what I reported but are
still a bit odd:

When I attempt activating the dropdown with Enter, I hear "Collapsed:
collapsed." I realize that isn't exactly what I reported, but if you're
patching this dependency, would it be possible to address that as well?
Space works fine. Not sure whether that specific behavior is part of the
component itself, or if the markup representing the collapsed item is
separate and not directly owned by the component.

The buttons don't appear to receive keyboard focus. Again, not sure
if that is specific to the dropdown component, or if the markup you used
in your example just doesn't add the tabindexes. If the latter, it
should be easy enough to add them in Ghost itself.

Thanks for the fixes!

When I attempt activating the dropdown with Enter, I hear "Collapsed: collapsed." I realize that isn't exactly what I reported, but if you're patching this dependency, would it be possible to address that as well? Space works fine. Not sure whether that specific behavior is part of the component itself, or if the markup representing the collapsed item is separate and not directly owned by the component.

It is, but it is a separate issue. Enter is merely being passed through, and the event for some reason fires twice. Space is handled differently, its propagation is being stopped, so it only fires once. I will file a new issue and correct that so that Enter and Space always behave the same.

The buttons don't appear to receive keyboard focus. Again, not sure if that is specific to the dropdown component, or if the markup you used in your example just doesn't add the tabindexes. If the latter, it should be easy enough to add them in Ghost itself. Thanks for the fixes!

It is not my example actualy. It's provided by the original author, I'm just patching things. The reason is because in the DOM order, these items are appended to the end of the document. So simply tabbing forward doesn't go to these initially, but will land on them eventually. This is the thing with aria-owns, it changes the accessibility tree, but not the DOM order, so keyboard focus sometimes acts a bit odd. Having said that, these examples have a separate bug in that the items are always appended at the end, not the place the component actually specifies where they should be added. But I am not sure why, and am not so keen on fixing that part TBH.

Makes sense, and thanks again for these fixes. Is there a PR I can
watch? Happy to do the work of testing the new dependency in Ghost, and
of submitting a PR to bump it should it work here.

I don't want to hijack this issue, but are there any alternative ways of
publishing to Ghost?

Just to quickly talk about workarounds - there are lots of ways to publish without using Ghost Admin. At its heart, Ghost is just an API, and Ghost Admin is the default client. You can use a 3rd party client or write your own client just to do what you need.
There are many 3rd party clients listed on our integrations page such as Ulysses or iAWriter.
If you want to write your own work around, documentation for our Admin API client lives here: https://ghost.org/docs/api/v3/javascript/admin/ and documentation for how to update a post lives here: https://ghost.org/docs/api/v3/admin/#updating-a-post. With the API client, it shouldn't take more than 10 lines of code to grab a post by ID or slug, and update the status to published.

Thanks, wasn't familiar with the integrations functionality, or indeed
whether or not integrations were what I needed. I'll try working some
curl magic until we can land this dependency change. I'm under Linux,
and am not immediately sure if any of the third-party clients would work
for me.

I've successfully slapped together a few lines of JS to publish posts
and pages until this dependency update lands. Now I'm having another
issue, and I don't know if it's related to this one or not. Once I've
published a post, I can't figure out how to save changes I make. They
appear in the editor, but despite my page claiming that it is published,
I never see the updates. Likewise, trying to navigate away from the edit
page prompts me to leave or stay because of unsaved changes.
I'm not sure if there's a Save button somewhere in this dropdown that I
can't find, or if there's another inaccessible control I can't find at
all. Happy to open a new issue--the challenge is that I don't know
enough to determine whether this is related or not. :) I've checked
https://ghost.org/faq/using-the-editor/, please let me know if there are
better docs for my purpose.
Thanks.

I fixed this issue with aria-expanded not being set when the dropdown is collapsed, in cibernox/ember-basic-dropdown#556. Once a new version is released and the package updated in the Ghost Admin client, this fix will automatically propagate.

I've forced an update of Ghost-Admin's sub-dependencies so the ember-basic-dropdown upgrade will go out in today's release 🙂

I'm not sure if there's a Save button somewhere in this dropdown that I
can't find, or if there's another inaccessible control I can't find at
all. Happy to open a new issue--the challenge is that I don't know
enough to determine whether this is related or not. :)

It is definitely the same problem - the same pattern used for publishing is reused for updating. There's an update dropdown, which (same as the publish dropdown) has 2 radio buttons that let you toggle between unpublishing or keeping the post published (keeping it published is the second, but default option) and then there's an "update" button.
To be honest I never use this workflow, I always use cmd / ctrl + s. I don't know if that helps.
It's not helpful immediately, but these workflows and interfaces are due an overhaul later this year as it's not lost on us we've outgrown them.

Ah, so there are keyboard shortcuts. :) Are they documented anywhere?
I've seen them mentioned here and there, but no comprehensive list.
Spent some time yesterday unsuccessfully looking for one.
I did eventually succeed with some combination of ctrl-alt-S, ctrl-S,
etc. under Linux, though I'm not sure which ultimately did it since
there wasn't accessible feedback, and my screen reader may have eaten
some of them. Thanks for letting me know that they're possible. Are
there also keyboard shortcuts to publish posts? I'd like to skip
switching to the command line and running my scripts if at all possible. :)
As an aside, apologies for the forum post. It wasn't my intent to pester
the team with a duplicate--I was genuinely hoping that an end-user might
step in and help me out, thus saving you the effort. Should I post
future accessibility questions to the forum first, then only open up
GitHub issues for anything that is definitely a bug? I opened this
because, as a web developer myself, I was pretty sure it was
accessibility-related. But I could easily see a Ghost user telling me
about the existence of editor keyboard shortcuts, and was disappointed
that no one had the chance to do so unless they just happened to know
about this specific issue.
In any case, thanks again for the help.

By default we try to make sure the keyboard behaves as you'd expect, so save, undo, redo, select all, backspace/delete should all behave naturally. Ghost aims to not trip you up when you are writing.
All common formatting shortcuts like bold and italic are also in place, plus a few extended ones and these are documented here:
https://ghost.org/faq/using-the-editor/#markdown-reference
We're missing documentation for shortcuts not related to formatting and I had thought that was because we only supported obvious ones, and all our custom shortcuts for things like publishing had been removed because they tend to cause conflicts with various keyboard layouts for other languages.
However, I have just done a test and cmd-shift-p does in fact publish the post. It also updates an already published post. cmd-s will save a draft post, and also update an already published post. You should be able to swap cmd for ctrl on linux and this should be a viable workaround for this issue for now 🎉
We need to review our shortcuts and document the remaining handful of custom ones we have that are genuinely useful and making them easy to find.
As for GitHub vs forum, with these issues it's a tricky line. If there are genuine usability problems that we aren't aware of, GitHub is fine for these especially if as in these cases there are people willing and able to contribute solutions. In this case it was also extra fun because I'm not sure anyone even realised we still had a publish shortcut - I wouldn't have suggested the API if I had realised 🙈

Nice, thanks for figuring these out for me! In this case I didn't even
think to try ctrl-s because that's a browser shortcut, albeit one not
likely to get used here, so I expected that to save the current page to
my local drive and not to actually save my post.
Anyhow, still hoping to see a PR fixing the actual DOM positioning of
the controls in the dropdown, and I think this should remain open until
that lands upstream. But for now I'm good. My site is up, and I'm
successfully adding/updating content. Thanks again.

Did the ember-basic-dropdown upgrade help with this?

Partially. There were two issues:

The button reported as only a button, not as a collapsed item. The
ember-basic-dropdown PR addressed this, and I can now tell when the item
is collapsed or expanded.

Apparently, and please correct me if I'm wrong, the component creates
markup like this:

   Text of button

   <div>

     <button>Child button</button>

   </div>

</button>

And screen readers don't know how to handle that, because it doesn't
really make sense for a button to have children.
I think Marco submitted another upstream PR to fix this, and it did seem
to work in the demo I tried. If it hasn't been merged yet, maybe a group
effort to push it forward would be in order? :) Happy to lend my voice
to that effort.

This issue is still present in current Ghost and requires a PR to an upstream component that I submitted in May, be merged.