I got an signal SIGABRT error when do in tutorials

IMPORTANT - BEFORE CREATING YOUR ISSUE PLEASE READ THE FOLLOWING:

PLEASE STATE THE VERSION NUMBER you are using.
Are you using the latest version of JTAppleCalendar? Latest version is currently 7.1.5
PROVIDE ENOUGH INPORMATION SO I CAN RECREATE THE PROBLEM.

I use an xcode 9.4.1, swift 4, jtapplecalendar 7.1.0
I just do a https://www.youtube.com/watch?v=zOphH-h-qCs tutorials and #553
this is my code.
`
import UIKit
import JTAppleCalendar
class ViewController: UIViewController {
let formatter = DateFormatter()
override func viewDidLoad(){
    super.viewDidLoad()
}

override func didReceiveMemoryWarning() {
    super.didReceiveMemoryWarning()
}

}
extension ViewController: JTAppleCalendarViewDataSource, JTAppleCalendarViewDelegate {
func calendar(_ calendar: JTAppleCalendarView, willDisplay cell: JTAppleCell, forItemAt date: Date, cellState: CellState, indexPath: IndexPath) {
    let mycell = cell as! CustomCell
    mycell.dateLabel.text = cellState.text
}

func calendar(_ calendar: JTAppleCalendarView, cellForItemAt date: Date, cellState: CellState, indexPath: IndexPath) -> JTAppleCell {
    let mycell = calendar.dequeueReusableJTAppleCell(withReuseIdentifier: "CustomCell", for: indexPath) as! CustomCell
    mycell.dateLabel.text = cellState.text
    self.calendar(calendar, willDisplay: mycell, forItemAt: date, cellState: cellState, indexPath: indexPath)
    return mycell
}

func configureCalendar(_ calendar: JTAppleCalendarView) -> ConfigurationParameters {
    formatter.dateFormat="yyyy MM dd"
    formatter.timeZone=Calendar.current.timeZone
    formatter.locale = Calendar.current.locale

    let startDate = formatter.date(from: "2017 01 01")!
    let endDate = formatter.date(from: "2019 12 31")!

    let parameters = ConfigurationParameters(startDate: startDate, endDate: endDate)
    return parameters
}

}
`
what do i wrong??

I have the same issue. following the same view tutorial and implemented both willDisplay and cellForItemAt but they never get called.
I am using: Xcode: 10.1,  JTAppleCalendar: 7.1.6,  Swift: 4.2,  Deployment target: iOS 12.1
Code:
import UIKit
import JTAppleCalendar

class ViewController: UIViewController {

    let formatter = DateFormatter()

    @IBOutlet weak var calendarView: JTAppleCalendarView!

    override func viewDidLoad() {
        super.viewDidLoad()
        print("ViewController : viewDidLoad")
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        print("ViewController : didReceiveMemoryWarning")
    }

}

extension ViewController : JTAppleCalendarViewDelegate, JTAppleCalendarViewDataSource {

    func calendar(_ calendar: JTAppleCalendarView, willDisplay cell: JTAppleCell, forItemAt date: Date, cellState: CellState, indexPath: IndexPath) {
        print("ViewController : willDisplay")
        let myCustomCell = cell as! CustomCell
        sharedFunctionToConfigureCell(myCustomCell: myCustomCell, cellState: cellState, date: date)
    }

    func calendar(_ calendar: JTAppleCalendarView, cellForItemAt date: Date, cellState: CellState, indexPath: IndexPath) -> JTAppleCell {
        print("ViewController : cellForItemAt")

        let cell = calendar.dequeueReusableJTAppleCell(withReuseIdentifier: "CustomeCell", for: indexPath) as! CustomCell
        sharedFunctionToConfigureCell(myCustomCell: cell, cellState: cellState, date: date)
        return cell
    }

    func sharedFunctionToConfigureCell(myCustomCell: CustomCell, cellState: CellState, date: Date) {
        print("ViewController: sharedFunctionToConfigureCell")
        myCustomCell.dateLabel.text = cellState.text
    }

    func configureCalendar(_ calendar: JTAppleCalendarView) -> ConfigurationParameters {
        print("ViewController : configureCalendar")

        formatter.dateFormat = "yyyy MM dd"
        formatter.timeZone = Calendar.current.timeZone
        formatter.locale = Calendar.current.locale

        let startDate = formatter.date(from: "2017 01 01")!
        let endDate = formatter.date(from: "2017 12 31")!

        let parameters = ConfigurationParameters(startDate: startDate, endDate: endDate)
        return parameters
    }

}

I followed the view tutorial multiple times to make sure I am not missing anything. Not sure what is wrong!

zip your sample prject, and send the zip file to me by dragging it into this chat box.
i'll take a  look

here is the project: CalendarTest.zip

@patchthecode any updates? Sorry I am curious to know what is the issue.

sorry man. my bad.
i totally missed this because this is a closed issue.
usually i dont miss it if the issue is open.
let me check.
In future, lets create a new issue for things like this.

Sure @patchthecode, will create new issue next time.

Sorry, that didn't work. Thank you for your time @patchthecode

I am not sure what the problem is then.
Here, i added 7.1.6 to the podfile.
I then did a pod update
i put the project on 12.0 deployment target and every thing is working fine.
here is the file.
CalendarTest 3.zip

Don't know why it's still the same for me. I had simulator running on iOS 12.1 and I downgrade it to iOS 12.0. Unfortunately still facing the same issue!

did the zip file i sent you work for you?

No, it didn't work. Thank you though


getSnippetHash: Use regexp instead of parsing whole AST

When calculating the env hash to use as cache keys, we don't need an exact list of imports
Therefore, to improve performance, we can replace the current strategy of using the AST by a regexp strategy.
This new strategy can lead to false positives (e.g. a string containing import 'foo') but this is not an issue for the hashing function.
All that matters is that the hash is consistent and accounts for all files (no false negatives)
On actual huge real-life environments, I have seen improvements of up to 95% (from 2s to 100ms)

Left a simple question. Overall LGTM. The performance improvements are amazing! I'm pretty sure the speed up is because of the reduction in the number of allocations, though I could be wrong.

Yeah, the issue with the AST is that you have to parse all of it and traverse all nodes


Cannot display PaymentRequestButton

Summary
I'm trying to follow the tutorial on adding the RequestPaymentButton in React but I am not having luck. I have recreated the code here
It does not appear to be working whatsoever on codesandbox, but, for some reason, in my local environment, I can get it to work only if I try querying paymentRequest.canMakePayment() before trying to call it again with a then()
Furthermore, I can only get the button to display on Chrome using this method but not Safari.
Update:
When trying to use the button when it appears in Chrome, it errors:
Uncaught Error: Payment Request is not available in this browser.
    at new t ((index):1)
    at t.<anonymous> ((index):1)
    at t.show ((index):1)
    at t.Xo._elementShow ((index):1)
    at (index):1
    at (index):1
    at Array.forEach (<anonymous>)
    at t._emit ((index):1)
    at e._handleMessage ((index):1)
    at e._handleMessage ((index):1)
    at (index):1

I can confirm that I have the buttons working here in both Chrome and Safari

Hi @iKrushYou
Yes, HTTPS is required as listed in the documentation as prerequisite.
Also, Payment Request only works inside sandboxed iframes when the allowpaymentrequest attribute is set on the iframe, which is the reason why it does not work inside the codesandbox.io iframe.


Feature/arts 620 link person testbranch

Description
Test automation scripts added for ARTS-620.
Changes

ARTS-620 - Link Person to User With Auth

Checklist:

[ ] Branch name follows convention (feature/arts-#-short-name OR fix/arts-#-short-name)
[ ] I have included a short-meaningful title, description and changes for this PR

the PR is not for merging into main.


Teach tab to focus terminal after rename

Summary of the Pull Request
After rename ends (either by enter or escape) the rename box
gets collapsed and the focus moves to the next tab stop
in the TabView (e.g., new tab button).
To overcome this:

Added RenameEnded event to TabHeaderControl
Forwarded it as RenamerDeactivated from TerminalTab
Registered in the TerminalPage to focus the active control upon
RenamerDeactivated if focus didn't move to tab menu.

This means, no matter how you close the renamer,
the current terminal gains the focus.
PR Checklist

[x] Closes https://github.com/microsoft/terminal/issues/9160
[x] CLA signed.
[ ] Tests added/passed
[ ] Documentation updated.
[ ] Schema updated.
[ ] I've discussed this with core contributors already.

I think the CI is stuck. Can someone kick it? :blush:


I had some problems running the Object Detection - Quick Start sample

when i run these codes:
time_limit = 60*30  # at most 0.5 hour
detector = ObjectDetector()
hyperparameters = {'epochs': 5, 'batch_size': 8}
hyperparameter_tune_kwargs={'num_trials': 2}     detector.fit(dataset_train,time_limit=time_limit,hyperparameters=hyperparameters,hyperparameter_tune_kwargs=hyperparameter_tune_kwargs)
errors:
Exception during a trial: type object 'SSDEstimator' has no attribute '_default_cfg'
Exception during a trial: type object 'YOLOv3Estimator' has no attribute '_default_cfg'
Exception during a trial: type object 'SSDEstimator' has no attribute '_default_cfg'
KeyError: 'map_reward'

sorry,i find the reason,that forget !pip install -U "mxnet<2.0.0"

@Innixma I'm facing this very same issue on Windows 11 while running Object Detection - Quick Start example. I have correct pytorch setup with CUDA and didn't installed mxnet as suggested in documentation (for Windows). Can you please point to me what I'm missing?
Since this seems like mxnet issue, afterwards I tried installing mxnet (CPU) for Windows but there are some dependency version conflicts so it didn't work for me.  If you can point me to some instructions for making pytorch+GPU work on Windows 11 for autogluon.vision it will be very helpful.
Thank you.

@zz-xx currently object detection is not supported on Windows as it only works with MXNet (and MXNet doesn't work on Windows). We are planning to add Torch support in future releases (possibly v0.5), but this is not yet available.

Thank you for confirming this.
I managed to run object detection quick start sample and train my own model using mxnet (CPU) on Windows. Since this is not officially supported, there are lot of dependency version conflicts to navigate. If there's interest, I can document my steps.

@zz-xx if you'd like to provide the steps to assist future windows users who are searching this issue, that could be helpful. It may be best for us to simply add a warning that OD is not supported on Windows though, as training OD models on CPU isn't very helpful beyond toy examples.

Running the Quickstart example on Colab, I faced the same error.:  KeyError: 'map_reward'.
By installing mxnet<2.0.0 the problem is solved.
Thank you for sharing

Running the Quickstart example on Colab, and I faced the same error.: KeyError: 'map_reward'.
Even thought installing mxnet<2.0.0, the problem is still not solved. So what can I do next?
mxnet: 1.9.0
autogluon: 0.5.0

same as @For-Chance  - I've used tabular but this is my first time using objectdetector.
I know my ObjectDetector.Dataset is happy, can show_images() and view bboxes.
yet following along the quickstart doc,  there appears to be an issue
time_limit = 60*30  # at most 0.5 hour
detector = ObjectDetector()
hyperparameters = {'epochs': 5, 'batch_size': 8}
hyperparameter_tune_kwargs={'num_trials': 2}
detector.fit(dataset, time_limit=time_limit, hyperparameters=hyperparameters, hyperparameter_tune_kwargs=hyperparameter_tune_kwargs)

errors out with
ERROR: Exception during a trial: type object 'SSDEstimator' has no attribute '_default_cfg'
ERROR: Exception during a trial: type object 'YOLOv3Estimator' has no attribute '_default_cfg'
ERROR: Exception during a trial: type object 'SSDEstimator' has no attribute '_default_cfg'
...
KeyError: 'map_reward'

if helpful, see full trace
mxnet: 1.9.1
autogluon: 0.5.2
any ideas ?
If i figure it out, will update here.
thanks !!

I was able to get the quickstart working by installing from source per doc
!python3 -m pip install "mxnet<2.0.0, >=1.7.0"
!python3 -m pip install torch==1.12.0+cpu torchvision==0.13.0+cpu torchtext==0.13.0 --extra-index-url https://download.pytorch.org/whl/cpu
! git clone https://github.com/awslabs/autogluon
!cd autogluon && ./full_install.sh

then was able to proceed w/ fit , etc as expected


[OSPP 2024] Enhance operational efficiency of K8s cluster in user's IDC

What would you like to be added:
It is difficult for users to operate, manage and upgrade the K8s cluster in their own IDC (Internet Data Center). We need to enhance the operational efficiency of K8s cluster in user's IDC by adopting KOK (Kubernetes-On-Kubernetes) architecture, where there are host-K8s and tenant-K8s. Host-K8s is located at cloud, provided by cloud service providers and can manage control plane of tenant-K8s in IDC.
Why is this needed:
For K8s clutesrs in user's IDC, it is difficult to operate, manage and upgrade the control plane components. Users typically adopt the following three solutions to manage K8s clusters in their IDC.

Some users only set up a single K8s cluster in IDC for tenant. In this case, when K8s have version upgrades and changes, about three major releases per year, users will suffer from complex operations to upgrade those components. Meanwhile, there is no resource elasticity capability in K8s clutesrs in user's IDC, such as scaling control plane components, which is a costly operation for user.

Some users adopt the KOK architecture in their own IDC to manages tenant-K8s's control plane components. Both host-K8s and tenant-K8s are in user's IDC. In this case, operating and updating control plane components of tenant-K8s will be easy, however, it is still hard to operate and upgrade the control plane components in host-K8s.

More and more users only access their IDC machines to cloud service providers as worker nodes, utilizing the abilities of cloud-edge collaboration provided by OpenYurt. But there are some users needs continuous deployment for offline tasks, depending on strong stability of cloud-edge communication, in this case, they tend to maintain a K8s cluster in their IDC.

We aim to solve the pain points mentioned above, which automates the operation and maintenance of control plane components of tenant-K8s to replace manual user operations, and affords users who needs continuous deployment for offline tasks a efficient operation scheme to manage their IDC K8s cluster.
others
/kind feature

/assign


adding description for the listadmincredentials action

Which issue this PR addresses:
Fixes - WI TBD, RBAC operation not documented in api.
What this PR does / why we need it:
It adds a human readable operation description to be used in Azure RBAC. For the new listAdminCredentials endpoint.
Test plan for issue:
The operations returned by the endpoint include the new one.
Is there any documentation that needs to be updated for this PR?
N/A

/azp rerun e2e


using with https elastic url

Hi,
I am trying to use this image to send data from my jmeter execution to an https url of elastic search, but I am getting the requests rejected due to missing certificates.
Where can I put the needed certificates to enable ssl/tls communication?
Thank you

hi @johnqa ,
can you give me more detail on your need ?

Well but where should the certificate be? The error is "unable to find valid certification path to requested target" but i do not give any certificate anywhere, in the command I am using.

hello,
can you give me the elasticsearch version ?

hi, we have Elastic Search v8.9

hello @johnqa
can you remove the anasoi/jmeter-logstash uimage and pull new version or just use this version (7.17.14) and use the folowing command ?
docker run --rm -e "ELASTICSEARCH_HOSTS=https://elastic_server:9200"
-v results:/input/
-e "FILE_READ_MODE=read"
-e "FILE_COMPLETED_ACTION=delete"
-e "ELASTICSEARCH_INDEX=test-jmeter"
-e "ELASTICSEARCH_USER=user"
-e "ELASTICSEARCH_PASSWORD=password."
-e "ELASTICSEARCH_SSL_VERIFICATION=false"
-e ELASTICSEARCH_VERSION=8
anasoid/jmeter-logstash
only thoes param are add to your initial command
-e "ELASTICSEARCH_SSL_VERIFICATION=false"
-e ELASTICSEARCH_VERSION=8 \

Hi,
Thank you for the effort.
I have did what you wrote and now I have these logs:
[2023-10-17T09:51:03,498][INFO ][logstash.runner          ] Log4j configuration path used is: /usr/share/logstash/config/log4j2.properties
[2023-10-17T09:51:03,508][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"7.17.14", "jruby.version"=>"jruby <IP_ADDRESS> (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server VM 11.0.20+8 on 11.0.20+8 +indy +jit [linux-x86_64]"}
[2023-10-17T09:51:03,509][INFO ][logstash.runner          ] JVM bootstrap flags: [-Xms256m, -Xmx512m, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djdk.io.File.enableADS=true, -Djruby.compile.invokedynamic=true, -Djruby.jit.threshold=0, -Djruby.regexp.interruptible=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true, -Dls.cgroup.cpuacct.path.override=/, -Dls.cgroup.cpu.path.override=/]
[2023-10-17T09:51:03,539][INFO ][logstash.settings        ] Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
[2023-10-17T09:51:03,550][INFO ][logstash.settings        ] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
[2023-10-17T09:51:03,863][INFO ][logstash.agent           ] No persistent UUID file found. Generating new UUID {:uuid=>"53141d19-138a-4dae-9398-afd448087651", :path=>"/usr/share/logstash/data/uuid"}
[2023-10-17T09:51:04,572][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600, :ssl_enabled=>false}
[2023-10-17T09:51:06,425][INFO ][org.reflections.Reflections] Reflections took 87 ms to scan 1 urls, producing 119 keys and 419 values
[2023-10-17T09:51:08,446][WARN ][org.logstash.instrument.metrics.gauge.LazyDelegatingGauge][jtl-csv] A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been created for key: send_to. This may result in invalid serialization.  It is recommended to log an issue to the responsible developer/development team.
[2023-10-17T09:51:08,527][INFO ][logstash.javapipeline    ][jtl-csv] Starting pipeline {:pipeline_id=>"jtl-csv", "pipeline.workers"=>1, "pipeline.batch.size"=>1, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>1, "pipeline.sources"=>["/usr/share/logstash/pipeline-in-csv/filter-wait-logstash.conf", "/usr/share/logstash/pipeline-in-csv/input-csv-logstash.conf", "/usr/share/logstash/pipeline-in-csv/output-next-pipeline-logstash.conf"], :thread=>"#<Thread:0x15e6e0a9 run>"}
[2023-10-17T09:51:09,968][INFO ][logstash.javapipeline    ][jtl-csv] Pipeline Java execution initialization time {"seconds"=>1.44}
[2023-10-17T09:51:10,173][INFO ][logstash.inputs.file     ][jtl-csv] No sincedb_path set, generating one based on the "path" setting {:sincedb_path=>"/usr/share/logstash/data/plugins/inputs/file/.sincedb_2e3001482a97bd583a361a059b521f94", :path=>["/input/**.jtl", "/input/**.jtl"]}
[2023-10-17T09:51:10,195][INFO ][logstash.javapipeline    ][jtl-csv] Pipeline started {"pipeline.id"=>"jtl-csv"}
[2023-10-17T09:51:10,242][INFO ][filewatch.observingread  ][jtl-csv][jtl-input] START, creating Discoverer, Watch with file and sincedb collections
[2023-10-17T09:51:10,620][INFO ][logstash.outputs.elasticsearch][main] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["https://elk-server:9200"]}
[2023-10-17T09:51:10,666][WARN ][logstash.outputs.elasticsearch][main] You have enabled encryption but DISABLED certificate verification, to make sure your data is secure remove `ssl_certificate_verification => false`
[2023-10-17T09:51:10,945][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[https://elk-user:***@elk-server:9200/]}}
[2023-10-17T09:51:11,298][WARN ][logstash.outputs.elasticsearch][main] Restored connection to ES instance {:url=>"https://elk-user:***@elk-server:9200/"}
[2023-10-17T09:51:11,313][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch version determined (7.17.0) {:es_version=>7}
[2023-10-17T09:51:11,315][WARN ][logstash.outputs.elasticsearch][main] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7}
[2023-10-17T09:51:11,408][INFO ][logstash.outputs.elasticsearch][main] Config is not compliant with data streams. `data_stream => auto` resolved to `false`
[2023-10-17T09:51:11,409][INFO ][logstash.outputs.elasticsearch][main] Config is not compliant with data streams. `data_stream => auto` resolved to `false`
[2023-10-17T09:51:11,410][INFO ][logstash.outputs.elasticsearch][main] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["https://elk-server:9200"]}
[2023-10-17T09:51:11,411][WARN ][logstash.outputs.elasticsearch][main] You have enabled encryption but DISABLED certificate verification, to make sure your data is secure remove `ssl_certificate_verification => false`
[2023-10-17T09:51:11,420][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[https://elk-user:***@elk-server:9200/]}}
[2023-10-17T09:51:11,455][WARN ][logstash.outputs.elasticsearch][main] Restored connection to ES instance {:url=>"https://elk-user:***@elk-server:9200/"}
[2023-10-17T09:51:11,456][INFO ][logstash.outputs.elasticsearch][main] Using mapping template from {:path=>"/usr/share/logstash/pipeline/template/jmeter-jtl-8x.json"}
[2023-10-17T09:51:11,463][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch version determined (7.17.0) {:es_version=>7}
[2023-10-17T09:51:11,463][WARN ][logstash.outputs.elasticsearch][main] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7}
[2023-10-17T09:51:11,472][INFO ][logstash.outputs.elasticsearch][main] Config is not compliant with data streams. `data_stream => auto` resolved to `false`
[2023-10-17T09:51:11,472][INFO ][logstash.outputs.elasticsearch][main] Config is not compliant with data streams. `data_stream => auto` resolved to `false`
[2023-10-17T09:51:11,484][INFO ][logstash.outputs.elasticsearch][main] Using mapping template from {:path=>"/usr/share/logstash/pipeline/template/jmeter-jtl-8x.json"}
[2023-10-17T09:51:11,490][INFO ][logstash.outputs.elasticsearch][main] Installing Elasticsearch template {:name=>"jmeter-jtl"}
[2023-10-17T09:51:11,563][ERROR][logstash.outputs.elasticsearch][main] Failed to install template {:message=>"Got response code '403' contacting Elasticsearch at URL 'https://elk-server:9200/_template/jmeter-jtl'", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:84:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:324:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:311:in `block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_cl...
[2023-10-17T09:51:11,567][ERROR][logstash.outputs.elasticsearch][main] Failed to install template {:message=>"Got response code '403' contacting Elasticsearch at URL 'https://elk-server:9200/_template/jmeter-jtl'", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:84:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:324:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:311:in `block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_cl...
[2023-10-17T09:51:11,721][INFO ][logstash.javapipeline    ][main] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>8, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>1000, "pipeline.sources"=>["/usr/share/logstash/pipeline/filter-a-config-fields-logstash.conf", "/usr/share/logstash/pipeline/filter-a-jtl-csv-filter-logstash.conf", "/usr/share/logstash/pipeline/filter-aa-jtl-fields-logstash.conf", "/usr/share/logstash/pipeline/filter-aa-jtl-filter-logstash.conf", "/usr/share/logstash/pipeline/filter-aa-jtl-transaction-logstash.conf", "/usr/share/logstash/pipeline/filter-aa-stats-adapt-json-logstash.conf", "/usr/share/logstash/pipeline/filter-bb-clean-null.conf", "/usr/share/logstash/pipeline/filter-bb-stats-parse-json-logstash.conf", "/usr/share/logstash/pipeline/filter-cc-stats-round-value-logstash.conf", "/usr/share/logstash/pipeline/filter-oo-jtl-thread-logstash.conf", "/usr/share/logstash/pipeline/filter-oo-jtl-time-logstash.conf", "/usr/share/logstash/pipeline/f...
[2023-10-17T09:51:13,746][INFO ][logstash.javapipeline    ][main] Pipeline Java execution initialization time {"seconds"=>2.02}
[2023-10-17T09:51:13,768][INFO ][logstash.inputs.file     ][main] No sincedb_path set, generating one based on the "path" setting {:sincedb_path=>"/usr/share/logstash/data/plugins/inputs/file/.sincedb_3bf673c089affb26c6b714f2f3224e92", :path=>["/input/**.json", "/input/**.json"]}
[2023-10-17T09:51:13,772][INFO ][logstash.javapipeline    ][main] Pipeline started {"pipeline.id"=>"main"}
[2023-10-17T09:51:13,786][INFO ][filewatch.observingread  ][main][statistics-input] START, creating Discoverer, Watch with file and sincedb collections
[2023-10-17T09:51:13,812][INFO ][logstash.agent           ] Pipelines running {:count=>2, :running_pipelines=>[:"jtl-csv", :main], :non_running_pipelines=>[]}

[2023-10-17T09:51:14,108][WARN ][logstash.filters.json    ][main][794d1cb7acae434dfcf3c2d8ddd78a3fda55a594d763229e305a91f5871eac0d] Error parsing json {:source=>"message", :raw=>"  },   \"gui\": {    \"modules\": {     \"jmeter\": {      \"gui\": true     }    }", :exception=>#<LogStash::Json::ParserError: Unexpected close marker '}': expected ']' (for root starting at [Source: (byte[])"  },   "gui": {    "modules": {     "jmeter": {      "gui": true     }    }"; line: 1, column: 0])
 at [Source: (byte[])"  },   "gui": {    "modules": {     "jmeter": {      "gui": true     }    }"; line: 1, column: 4]>}

[2023-10-17T09:51:14,115][WARN ][logstash.filters.json    ][main][794d1cb7acae434dfcf3c2d8ddd78a3fda55a594d763229e305a91f5871eac0d] Error parsing json {:source=>"message", :raw=>" },  \"execution\": [   {    \"scenario\": \"${ScenarioName}\"   }  ],  \"scenarios\": {   \"elkintegration\": {    \"script\": \"/bzt-configs/TestApp4JMeterLoadTests/LoadTests/elkintegration.jmx\"   }", :exception=>#<LogStash::Json::ParserError: Unexpected close marker '}': expected ']' (for root starting at [Source: (byte[])" },  "execution": [   {    "scenario": "${ScenarioName}"   }  ],  "scenarios": {   "elkintegration": {    "script": "/bzt-configs/TestApp4JMeterLoadTests/LoadTests/elkintegration.jmx"   }"; line: 1, column: 0])
 at [Source: (byte[])" },  "execution": [   {    "scenario": "${ScenarioName}"   }  ],  "scenarios": {   "elkintegration": {    "script": "/bzt-configs/TestApp4JMeterLoadTests/LoadTests/elkintegration.jmx"   }"; line: 1, column: 3]>}

 [2023-10-17T09:51:14,396][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.835Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.835Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}
[2023-10-17T09:51:14,400][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.826Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.826Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}
[2023-10-17T09:51:14,397][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.863Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.863Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}
[2023-10-17T09:51:14,404][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.844Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.844Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}
[2023-10-17T09:51:14,407][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.845Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.845Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}
[2023-10-17T09:51:14,408][WARN ][logstash.outputs.elasticsearch][main][jmeter-elasticsearch-output-stat] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"jmeter-jtl-2023.10.17", :routing=>nil}, {"isTotal"=>false, "labels"=>["%{transaction}"], "@version"=>"1", "globalLabel"=>"%{transaction}", "filename"=>"effective", "@timestamp"=>2023-10-17T09:51:13.858Z, "testname"=>"effective", "timestamp"=>"2023-10-17T09:51:13.858Z", "label"=>"%{transaction}", "tags"=>["_jsonparsefailure"], "project"=>"undefined", "origin"=>"stat"}], :response=>{"index"=>{"_index"=>"jmeter-jtl-2023.10.17", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"only write ops with an op_type of create are allowed in data streams"}}}}

hello @johnqa
it's preferable to keep default index name or to have index with this format jmeter-jtl-* this not related to your error.
1- for this error ([ERROR][logstash.outputs.elasticsearch][main] Failed to install template {:message=>"Got response code '403') i think it's a permission error may be the user name doesn't have enough permissions to install template.
2- for this warn WARN ][logstash.filters.json    .., it's related to parsing statistics json, stattistics.json is generated with jmeter dashboard and it look like this https://github.com/anasoid/jmeter-logstash/blob/develop/testing/file/full/in/stats-admin-20211018-082256.json, if there is any json file in input folder may it will be considered as statistics json


[ci skip] adding user @Yannick-Dayer

Hi! This is the friendly automated conda-forge-webservice.
I've added user @Yannick-Dayer as instructed in #5.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #5

Ah, the CI tests fail here because the current version of auto-intersphinx (v1.1.0) is not compatible with sphinx>=7.4.0.
The fix for this comes with auto-intersphinx v1.2.0 which will be integrated in #4.
As the package will not be re-generated (because of skip-ci) it is safe to merge this PR.

Just add yourself on the other PR and close this one.

Closed by #4.

@anjos Could you re-open this PR and merge it, so I can become a maintainer of auto-intershpinx-feedstock too?

@Yannick-Dayer this is still failing… can you fix it?

It will fail until the next version v1.2.1 is added; an automatic PR will be created soon-ish by the bot (it might be delayed due to some conda-forge issues right now).

However, it should be safe to merge now anyway, as the CI will be skipped and nothing will be pushed to the conda-forge channel ([ci skip]).
This just adds me as maintainer in the recipe and edits the project's members list.


run sky_tool stop before the first sky app is run

This will ensure that the sky server is not already running and serving a different app (this is a problem for running on android devices).
In addition, between app runs where the app to run changes, we should make sure to bounce the server.

fixed in https://github.com/dart-atom/dartlang/pull/337


Allow maker to use PostgreSQL as database backend

Duplicate of https://github.com/itchysats/itchysats/issues/1545.


Transcription bar - Reinitialize Select2 fields

Issue
The Select2 fields retain their previous values when the transcription bar is reopened. This is somewhat confusing to the user - makes it seem like it didn't save properly.
Potential Solution
Reinitialize all fields except for date and time.

I'll keep the date, but the time will likely be different, so better to have it cleared as well.


Update CloudFormation spec to 2.15.0

Issue #, if available:
Description of changes:

Update CloudFormation Specs to v2.15.0

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

Will go green after #482

This PR got a little tangled. I'm going to close it so we can start fresh with a new one.


Fixes #6686: Prevent double-click on Publish/Save

Fixes #6686

Awesome! Anyone wants to try the feature to ensure it's not breaking any obvious scenario?

Combine it with lines 86 - 99

@sebastienros , @donaldboulton I have combined it with bulk-actions as well and made it more secure by binding it up with both buttons and inputs of type submit. The code checks if the associated form was previously submitted or not. If already submitted it prevents the action.
I did test with single page edit as well as Content bulk actions.


unique names in specifications

Currently, names in specifications are divided up by packet types, so it is possible for a register and event to have the same name. I propose that we disallow multiples uses of same name in a specification to reduce change for confusion.

@mmoskal this seem like a good idea

yes; I'll do it next time I get to the spectool unless someone beats me to it ;)

lemme take a look

Seems thiat this is already being done.

https://github.com/microsoft/jacdac/blob/fcecddd951984fb4839ffc486d2f19070c5ccad4/spectool/jdspec.ts#L585


KATA_SRC_REF is not used anywhere

We define KATA_SRC_REF but we don't make use of it anywhere. Also, during the podvm build, we expect the kata-containers repository to exist already.

I guess we rely on KATA_SRC_BRANCH a lot but not in the Makefile though. Since this is not in the Makefile, when doing local builds one has to manually go to the kata-containers directory sitting adjacent to the current CAA directory and manually checkout that directory, this is not documented anywhere. Not codified either.
I guess we should not rely on the kata-containers repository sitting adjacent to the CAA repo. We should download this tar directly from GH for the CCv0 branch and use that to do the builds.

This has been fixed in https://github.com/confidential-containers/cloud-api-adaptor/pull/1448


Add setting to specify "scope" of status bar indicator (file/project)

What?
Add an settings option to limit the "scope" of the status bar indicator and "Next Error" command to either file or project.
Why?
I prefer to work on a file-by-file basis while linting, and thus use the Line tab to show only errors/warning for the current line within the bottom panel. I can then use the Linter status bar indicator ("X errors") or my trusty key binding to move to the next error in the file.
However, as I was working on two separate files (the first had errors, the second did not), clicking the status indicator (or triggering my key binding) when in the file with no errors brought me to the file with errors. I also noticed that when viewing the file with no errors, the status indicator showed that there were errors (because I had the other file—the one with errors—open and inactive. This indicated to me that the status bar icon (as well as the "Next Error" command) works at the project level. Therefore, I would very much like an option to limit the scope of this to the current file only.
I hope that all makes sense. Please feel free to ask me for clarification.
Caleb

I think we had this option initially. but was removed 'cause no one wanted it. Votes people?

Make sense for me.

I think I am gonna do this one

I will use it for sure :+1: Thank's for spending so much time on the project @steelbrain

Pleasure :bow:


invalid dataset link of 'RGB 3D face dataset'

Thanks for your contribution! Excellent work!!
It seems that the link of your dataset 'RGB 3D face dataset' is invalid in your README.md. Can you update your dataset link?
Thanks ~!

It's classified as TBA, they probably have to clean it up and make sure they have the rights to post.

Is this dataset RGB 3D face dataset open to general developer in the future after the clean?

Sorry for the delay, the link to the RGB 3D Face dataset has been updated, please check the new README file for more details.


Move gNMI test cases that do not require an ATE

Pull Request Functional Test Report for #1666 / 66a4e3d2ed3f4d4d7199fcdc4d0a6768872388ed
Virtual Devices

Device
Test
Test Documentation
Job

Arista cEOS

FP-1.1: Power admin DOWN/UP TestgNMI-1.4: Telemetry: InventoryDP-1.7: One strict priority queue traffic testgNMI-1.12: Mixed OpenConfig/CLI OriginRT-1.2: BGP Policy & Route InstallationP4RT-2.1: P4RT ElectiongNOI-5.2: Traceroute Test

Cisco 8000E

FP-1.1: Power admin DOWN/UP TestgNMI-1.4: Telemetry: InventoryDP-1.7: One strict priority queue traffic testgNMI-1.12: Mixed OpenConfig/CLI OriginRT-1.2: BGP Policy & Route InstallationP4RT-2.1: P4RT ElectiongNOI-5.2: Traceroute Test

Cisco XRd

FP-1.1: Power admin DOWN/UP TestgNMI-1.4: Telemetry: InventoryDP-1.7: One strict priority queue traffic testgNMI-1.12: Mixed OpenConfig/CLI OriginRT-1.2: BGP Policy & Route InstallationP4RT-2.1: P4RT ElectiongNOI-5.2: Traceroute Test

Juniper cPTX

FP-1.1: Power admin DOWN/UP TestgNMI-1.4: Telemetry: InventoryDP-1.7: One strict priority queue traffic testgNMI-1.12: Mixed OpenConfig/CLI OriginRT-1.2: BGP Policy & Route InstallationP4RT-2.1: P4RT ElectiongNOI-5.2: Traceroute Test

Nokia SR Linux

FP-1.1: Power admin DOWN/UP TestgNMI-1.4: Telemetry: InventoryDP-1.7: One strict priority queue traffic testgNMI-1.12: Mixed OpenConfig/CLI OriginRT-1.2: BGP Policy & Route InstallationP4RT-2.1: P4RT ElectiongNOI-5.2: Traceroute Test


Update compiler activation for 1.17.6

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda smithy rerender

@conda-forge-admin please rerender

@conda-forge-admin please rerender


Accepting invites from federation fails

Describe the bug
If users on a synapse homeserver with this module get invited from a user via federation the invite is not automatically accepted.
To Reproduce
Steps to reproduce the behavior:

Install synapse and this module
Let an external Usere invite a user on your homeserver
The invite is not automatically accepted.

Expected behaviour
The invite is automatically accepted.
Desktop (please complete the following information):
does not apply
Smartphone (please complete the following information):
does not apply
Additional context
The tested homeservers are synapse on version 1.61.1 in a dockerized environment. The module was installed in the container with pip. koyax.org is the federated homeserver and lippesola.de the one with the module installed. lippesola.de has federation whitelisting enabled with koyax.org beeing part of that list. koyax.org has unrestricted federation.
** Logs **
This is the log of the synaspe server with the module installed when a federated user invites a local user.
2022-07-04 11:51:09,750 - synapse.http.matrixfederationclient - 620 - INFO - PUT-167 - {GET-O-13} [koyax.org] Got response headers: 403 Forbidden
2022-07-04 11:51:09,751 - synapse.http.matrixfederationclient - 700 - WARNING - PUT-167 - {GET-O-13} [koyax.org] Request failed: GET matrix://koyax.org/_matrix/federation/v1/make_join/%21gmGAJbNDZtuUfEIJvo%3Akoyax.org/%40admin%3Alippesola.de?ver=1&ver=2&ver=3&ver=4&ver=5&ver=6&ver=org.matrix.msc2176&ver=7&ver=8&ver=9&ver=org.matrix.msc2716v3&ver=org.matrix.msc3787: HttpResponseException('403: Forbidden')
2022-07-04 11:51:09,752 - synapse.events.third_party_rules - 406 - ERROR - PUT-167 - Failed to run module API callback <bound method InviteAutoAccepter.on_new_event of <synapse_auto_accept_invite.InviteAutoAccepter object at 0x7fceb94152b0>>: 403: You are not invited to this room.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/synapse/federation/federation_client.py", line 694, in _try_destination_list
    return await callback(destination)
  File "/usr/local/lib/python3.9/site-packages/synapse/federation/federation_client.py", line 791, in send_request
    ret = await self.transport_layer.make_membership_event(
  File "/usr/local/lib/python3.9/site-packages/synapse/federation/transport/client.py", line 322, in make_membership_event
    return await self.client.get_json(
  File "/usr/local/lib/python3.9/site-packages/synapse/http/matrixfederationclient.py", line 1066, in get_json
    response = await self._send_request_with_optional_trailing_slash(
  File "/usr/local/lib/python3.9/site-packages/synapse/http/matrixfederationclient.py", line 405, in _send_request_with_optional_trailing_slash
    response = await self._send_request(request, **send_request_args)
  File "/usr/local/lib/python3.9/site-packages/synapse/http/matrixfederationclient.py", line 659, in _send_request
    raise exc
synapse.api.errors.HttpResponseException: 403: Forbidden

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/synapse/events/third_party_rules.py", line 404, in on_new_event
    await callback(event, state_events)
  File "/usr/local/lib/python3.9/site-packages/synapse_auto_accept_invite/__init__.py", line 99, in on_new_event
    await self._api.update_room_membership(
  File "/usr/local/lib/python3.9/site-packages/synapse/module_api/__init__.py", line 999, in update_room_membership
    event_id, _ = await self._hs.get_room_member_handler().update_membership(
  File "/usr/local/lib/python3.9/site-packages/synapse/handlers/room_member.py", line 524, in update_membership
    result = await self.update_membership_locked(
  File "/usr/local/lib/python3.9/site-packages/synapse/handlers/room_member.py", line 860, in update_membership_locked
    remote_join_response = await self._remote_join(
  File "/usr/local/lib/python3.9/site-packages/synapse/handlers/room_member.py", line 1611, in _remote_join
    event_id, stream_id = await self.federation_handler.do_invite_join(
  File "/usr/local/lib/python3.9/site-packages/synapse/handlers/federation.py", line 487, in do_invite_join
    origin, event, room_version_obj = await self._make_and_verify_event(
  File "/usr/local/lib/python3.9/site-packages/synapse/handlers/federation.py", line 922, in _make_and_verify_event
    ) = await self.federation_client.make_membership_event(
  File "/usr/local/lib/python3.9/site-packages/synapse/federation/federation_client.py", line 842, in make_membership_event
    return await self._try_destination_list(
  File "/usr/local/lib/python3.9/site-packages/synapse/federation/federation_client.py", line 724, in _try_destination_list
    raise synapse_error from e
synapse.api.errors.ProxiedRequestError: 403: You are not invited to this room.
2022-07-04 11:51:09,756 - synapse.access.http.8008 - 450 - INFO - PUT-167 - <IP_ADDRESS> - 8008 - {koyax.org} Processed request: 0.646sec/0.001sec (0.019sec, 0.003sec) (0.015sec/0.122sec/12) 1485B 200 "PUT /_matrix/federation/v2/invite/%21gmGAJbNDZtuUfEIJvo%3Akoyax.org/%24GW-iHVMj0_tgK01fK0PeIOafb--4uYL9GwN_qHv9f6U HTTP/1.0" "Synapse/1.61.1" [0 dbevts]

Same here. It seems that the module doesn't support federation

Any clues on the cause of that or possible workarounds?

This has been fixed in v1.1.3 -> you can get the new version on pypi or github. I should note that while the releases say that the minimum compatible Synapse version for 1.1.3 of the module is Synapse 1.84.0, it should work with older versions of Synapse (but will break some of the tests/dev tooling.)