Enhance Default From Address Handling in Message Templates

Issue:
The current default from address behaviour in message templates can lead to conflicts when switching email providers while using the same template.
Use Case:
For example, if a user creates a message template with a specific default from address and later switches from SendGrid to SMTP as the email provider, the default from address specified in the template may no longer be valid or appropriate for the new provider, leading to potential delivery issues.
Proposal:
To address this issue, we propose implementing dynamic default from address fetching based on the selected email provider. This would ensure consistency and accuracy in default from address usage across different providers. Additionally, providing user guidance and fallback mechanisms will help handle cases where the default address is not specified or cannot be fetched.

I think implementing a dynamic from address may be a fairly large change to the application. How about when you change the default, it alerts you if there are any existing email templates with different from addresses, and gives you the option of updating them?

Absolutely, looks like a reasonable approach. Whenever the default from address is changed in the settings, we will check all existing message templates and update the from address accordingly. Additionally, we will display a success message to inform users that their message templates have been updated.
Before moving forward with implementation, I'd like to confirm if you agree with the proposed approach. Once confirmed, I will proceed with implementing the changes as outlined.

@danish1112 apologies for the delayed response!

Whenever the default from address is changed in the settings, we will check all existing message templates and update the from address accordingly

Before performing the update, we should check if there are any templates with a different email and we should open up a modal giving the user the option to override existing templates (but not perform the override behavior by default).

Got it, I'll work on implementing this feature.

Kindly check this PR @maxgurewitz
https://github.com/dittofeed/dittofeed/pull/825


Introduce a Usage section for 0.5.x website docs

Pull in post-build task docs from recent PR

nice! thanks!


Language detection error

I like your library/tool as it is simple to use, compact, and generally produces good results, but I do have an issue/question. Why does it classify the following block as lt?
tinyld "Russia has been stripped of a multitude of tournaments following an IOC recommendation\n\nRussian Sports Minister Oleg Matytsin has warned the world of sport that the lack of competition from banned Russian athletes is harmful for all concerned, while stating the precise number of events which his country has been stripped of due to the conflict in Ukraine.\n\nRussia has lost major sporting showpieces in recent months following a recommendation from the International Olympic Committee (IOC) at the end of February that federations should neither invite Russian athletes to competitions nor host tournaments in the country.\n\nThat has led to Russia being deprived of events such as the UEFA Champions League final, which was scheduled for St. Petersburg in May, and the world championships in volleyball and ice hockey, planned for 2022 and 2023 respectively.\n\nSports Minister Matytsin has now put an exact figure on the number of events removed from Russia.\n\n“As of May 25, international sports organizations canceled/postponed 186 international sporting events planned in Russia in 2022-2023, including 36 major international sporting events,” said Matytsin, who has been heading a Russian delegation on a visit to India.\n\nThe minister added that Russian sports officials had been tasked with seeking compensation for canceled events – something the likes of the Russian Football Union (RFU) has already said it will do with UEFA and FIFA.\n\nBut as Russian and Belarusian athletes face widespread bans, Matytsin warned that it was not only athletes from the two countries who would suffer.\n\n“This theory [of a damaging absence of competition] applies not only to us, but to all world sports – the lack of competition with Russian athletes is harmful,” Matytsin said, as quoted by RIA Sport.\n\nMatytsin has previously cautioned that world sport cannot hope to develop “normally” without the participation of Russian athletes, arguing that various federations had already come to realize their errors in attempting to alienate Russian sport.\n\nOn the flip side, Matytsin said on Thursday that Russia was also stepping up its efforts to hold tournaments for its athletes and those from other countries.\n\n“From February to May 2022, more than 30 international competitions were held in Russia,” said the minister.\n\nAfter Russian athletes were banned on the eve of the Beijing Winter Paralympics in March, Russia promptly arranged an alternative event at the Siberian resort of Khanty-Mansiysk – something it has vowed to continue to do.\n\nMatytsin has taken the opportunity of his visit to India to discuss the strengthening of sporting ties between the two countries, suggesting that Russia would be more than willing to help India with organizing a future edition of the Olympic Games, should it be granted hosted rights."
[
  { lang: 'lt', accuracy: 0.7009174311926606 },
  { lang: 'en', accuracy: 0.29908256880733947 }
]

Sorry for the late answer, some summer vacation in the way 😄
After investigation, it looks like this specific sentence is confused by the family name, which contain unusual sequence of letters for english Matytsin repeated 8 times.
In a more recent build I slightly increase the number of chunk analyzed for long texts, which reduce the risk of this happening.
For this quote, I get the following result with version 1.3.0
[
  { lang: 'en', accuracy: 0.6393910561370124 },
  { lang: 'lt', accuracy: 0.36060894386298764 }
]


Fix Documentation not displaying properly for 'Docker wormhole pattern'

Fixes #4656

Looking good now, thanks for the PR 👍


updated fragment header for new nav

Docs generator gets nav from this. Updated html for new nav

Docs generator gets nav from website. These fragments don't seem to be actually used.


Are there any plans to support RocketMq trigger in the near feature

FEATURE REQUEST:
Are there any plans to support RocketMq trigger in the near feature?

Hi,
Not for the moment, we have documentation for contributors to create their own triggers that you can check in case you are interested:
https://kubeless.io/docs/implementing-new-trigger/


#27 - Changed Install-BicepCLI to use bicep installer.

@PalmEmanuel @bjompen Not sure if we should care about fixing this or not. Install-BicepCLI works great to install bicep CLI with the proposed change. But if I run Install-BicepCLI -Force after a successful install I get the error below.
 47 |          Start-Process $TargetFileName -ArgumentList '/VERYSILENT' -Wa …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | This command cannot be run due to the error: The process cannot access the file because it is being used by another process.


Change URLs of LDAP referrals to use LDAPS and docker hostnames

Merged, thanks!

@MiguelWeezardo I released snapshot of docker images: ed80722.
Let me know if this works and I'll release a proper version.

Thanks, but Grzegorz already published the release version.
I have a PR for presto-private to check if tests pass with these new images.
On Wed, Dec 11, 2019 at 1:46 PM Piotr Findeisen<EMAIL_ADDRESS>wrote:

@MiguelWeezardo https://github.com/MiguelWeezardo I released snapshot
of docker images: ed80722.
Let me know if this works and I'll release a proper version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prestosql/docker-images/pull/45?email_source=notifications&email_token=ABN6SGEEECSY4OP6K4D2UPTQYDOLFA5CNFSM4JZA5W3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGS7JHA#issuecomment-564524188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN6SGBOHTN2IB5L5DVOTRDQYDOLFANCNFSM4JZA5W3A
.


Add reset after submit

Reset form state after submit successfully

Agreed, this seems like a good idea. Any reason for not calling this? https://github.com/AngularAgility/AngularAgility/blob/master/src/formExtensions/directives/ngForm.js#L273

Didn't see this method.


Get-SecureScoreData Error

I have deployed the Get-SecureScoreData since mid of July, managed identity role assigned at the root management group with Reader role which is the preferred method.
https://github.com/Azure/Azure-Security-Center/tree/master/Secure Score/Get-SecureScoreData
Running well and recently not sure what changes to the API at the Microsoft end, The logic at failed to run since 23 August 2020., It hit error when get the secure score from a disabled subscription.
{
"statusCode": 404,
"headers": {
"Pragma": "no-cache",
"x-ms-ratelimit-remaining-subscription-resource-requests": "749",
"x-ms-request-id": "XXXX",
"x-ms-correlation-request-id": "XXXX",
"x-ms-routing-request-id": "XXXX",
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"Cache-Control": "no-cache",
"Date": "Thu, 27 Aug 2020 00:46:06 GMT",
"Content-Length": "136",
"Content-Type": "application/json",
"Expires": "-1"
},
"body": {
"Error": {
"Code": "ResourceNotFound",
"Message": "Secure score 'ascScore' does not exist in scope 'XXXX"
}
}
}

Hi @famjunxiang ,
thanks for reporting this issue. We're currently working on adding a condition so only enabled subscriptions will be used for getting Secure Score data in the future. Once we're finished, we'll merge the code change to the master branch.
Just for clarification: does the whole LogicApp fail, meaning you're not seeing any data since August 23rd in your Log Analytics workspace, or does it only show a failure in the Logic App's run history?

Hi @TomJanetscheck , thanks for your respond. yes the whole LogicApp fail, and not seeing any data since August 23rd.
Thanks.

@famjunxiang - you can either deploy the Get-SecureScoreData LogicApp from the latest version, or you go ahead and update the existing LogicApp in your environment. If you choose to update your existing artifact, please make sure to incorporate the following code as it was added in PR #205
,
{
"equals": [
"@items('For_each')?['state']",
"Enabled"
]
}
The code needs to be added after the check for a subscription's registration state, you can refer to the PR to see what's been changed and where to add it in your LogicApp code.
Closing this issue as a solution was provided.

Hi @TomJanetscheck  thank you so much for the update, the logic app run without any error now.

Hi @TomJanetscheck , the logic app run well between 1 - 3 September 2020, and since 4th September, it failed again with below error at HTTP2, after checking, i unable to locate any subscription in my tenant end with 80af. Thanks.
{
"Error": {
"Code": "ResourceNotFound",
"Message": "Secure score 'ascScore' does not exist in scope 'xxxxxxxx-xxxx-xxxx-xxxx-6bdbcbe080af'"
}
}

Hi @famjunxiang ,
The Logic App leverages the Secure Scores API in a For Each loop. The subscription ID is parsed from the output of a GET command against the subscriptions API. If the subscription ID you mention above is used in HTTP2, the respective subscription is in the Logic App's Managed Identity's read scope. You can test the API connection including the results that come back from the Get command yourself when you klick the link above. In the documentation, you will find a Try it button. Once you click that button, you are asked to authenticate. Please use an account with the same access rights as the Logic App's Managed Identity.


Code hash resolve fix + cleanup

Although we were adding code that was created during a txn to the local code hash resolve table, it was not getting added to the "global" lookup table. Previously I was using this funny closure to resolve code hashes, but this is pretty
unusable as soon as you need to add new entries to the current table. I ended up replacing this with a struct called CodeHashResolving, which I think is a lot easier to read.

Nice job

@Nashtare Yeah I'm fine with that.

I had updated the auto-merge 🤣


SQLiteCpp/Statement.h: add missing <cstdint> include

Without the change the build fails on gcc-15 as:
[  5%] Building CXX object CMakeFiles/SQLiteCpp.dir/src/Backup.cpp.o
In file included from /build/source/include/SQLiteCpp/Column.h:14,
                 from /build/source/include/SQLiteCpp/Database.h:14,
                 from /build/source/include/SQLiteCpp/Backup.h:15,
                 from /build/source/src/Backup.cpp:12:
/build/source/include/SQLiteCpp/Statement.h:132:39: error: 'uint32_t' does not name a type
  132 |     void bind(const int aIndex, const uint32_t      aValue);
      |                                       ^~~~~~~~
/build/source/include/SQLiteCpp/Statement.h:20:1: note: 'uint32_t' is defined in header '<cstdint>'; this is probably fixable by adding '#include <cstdint>'
   19 | #include <memory>
  +++ |+#include <cstdint>
   20 |

Thanks a lot for taking the time to contribute these two fixes, much appreciated


Fix ghooks call and replace with husky as is depreciated

@SteveALee sorry for the merge conflict :)

@jvanbruegge did you just add the precommit? The other line seems unchanged

yeah, but I just noticed that precommit is not ideal
the formatted code does not get added

OK I resolved the clash but won't commit. Over to you :)


Is there any firewall configuration that should be applied to the guest nodes as a prerequisite ?

Is this a BUG REPORT or FEATURE REQUEST?:
It seems like a bug, or maybe it is due to the VM provisionning.
What happened:
Setup is OK :
Setup of a cluster on 3 nodes : 1 master and 2 workers on Ubuntu VMs with Vagrant and Kismatic :

<IP_ADDRESS> : master
<IP_ADDRESS> : worker
<IP_ADDRESS> : worker

Plan installation ran fine, without any issue. All tests passed with [OK] flags.
Dashboard is deployed successfully.
I then deployed nginx pods and service to test the cluster :
apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 2
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.8
        ports:
        - containerPort: 80
kind: Service
metadata:
  name: nginx
  namespace: default
  labels:
    app: nginx
spec:
  selector:
    app: nginx
  type: NodePort
  ports:
  - name: web
    port: 80

kubectl get nodes -o wide
NAME          STATUS                     AGE       VERSION   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION
kube-node-1   Ready,SchedulingDisabled   2d        v1.8.2            Ubuntu 16.04.3 LTS   4.4.0-92-generic
kube-node-2   Ready                      2d        v1.8.2            Ubuntu 16.04.3 LTS   4.4.0-92-generic
kube-node-3   Ready                      2d        v1.8.2            Ubuntu 16.04.3 LTS   4.4.0-92-generic
kubectl get pods -o wide
NAME                     READY     STATUS    RESTARTS   AGE       IP               NODE
nginx-7cbc4b4d9c-5djm7   1/1       Running   0          4h        <IP_ADDRESS>   kube-node-2
nginx-7cbc4b4d9c-mvcgs   1/1       Running   0          4h        <IP_ADDRESS>    kube-node-3
kubectl get service -o wide
NAME         CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE       SELECTOR
kubernetes   <IP_ADDRESS>               443/TCP        2d
nginx        <IP_ADDRESS>          80:31402/TCP   1h        app=nginx,run=nginx
kubectl describe node kube-node-2
Name:			kube-node-2
Role:
Labels:			beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kismatic/cni-provider=calico
kismatic/host=kube-node-2
kubernetes.io/hostname=kube-node-2
Annotations:		alpha.kubernetes.io/provided-node-ip=<IP_ADDRESS>
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints:
CreationTimestamp:	Sat, 18 Nov 2017 23:56:22 +0100
Conditions:
Type			Status	LastHeartbeatTime			LastTransitionTime			Reason				Message

OutOfDisk 		False 	Tue, 21 Nov 2017 12:44:57 +0100 	Sat, 18 Nov 2017 23:56:22 +0100 	KubeletHasSufficientDisk 	kubelet has sufficient disk space available
MemoryPressure 	False 	Tue, 21 Nov 2017 12:44:57 +0100 	Tue, 21 Nov 2017 08:19:05 +0100 	KubeletHasSufficientMemory 	kubelet has sufficient memory available
DiskPressure 		False 	Tue, 21 Nov 2017 12:44:57 +0100 	Tue, 21 Nov 2017 08:19:05 +0100 	KubeletHasNoDiskPressure 	kubelet has no disk pressure
Ready 		True 	Tue, 21 Nov 2017 12:44:57 +0100 	Tue, 21 Nov 2017 08:19:05 +0100 	KubeletReady 			kubelet is posting ready status. AppArmor enabled
Addresses:
InternalIP:	<IP_ADDRESS>
Hostname:	kube-node-2
Capacity:
cpu:		1
memory:	2048284Ki
pods:		110
Allocatable:
cpu:		1
memory:	1945884Ki
pods:		110
System Info:
Machine ID:			8d4eadeb9ee9f4632342b055599cdf6b
System UUID:			09D0557C-E3C5-49C4-B63E-543219F882FF
Boot ID:			914ebcd8-2780-4058-a0f9-475ef2921f5b
Kernel Version:		4.4.0-92-generic
OS Image:			Ubuntu 16.04.3 LTS
Operating System:		linux
Architecture:			amd64
Container Runtime Version:	docker://1.12.6
Kubelet Version:		v1.8.2
Kube-Proxy Version:		v1.8.2
PodCIDR:			<IP_ADDRESS>/24
ExternalID:			kube-node-2
Non-terminated Pods:		(8 in total)
Namespace			Name							CPU Requests	CPU Limits	Memory Requests	Memory Limits

default			nginx-7cbc4b4d9c-5djm7					0 (0%)		0 (0%)		0 (0%)		0 (0%)
kube-system			calico-kube-controllers-66b5866555-4mjlf		0 (0%)		0 (0%)		0 (0%)		0 (0%)
kube-system			calico-node-g5gmx					250m (25%)	0 (0%)		0 (0%)		0 (0%)
kube-system			heapster-57bcd785b5-hxk6v				0 (0%)		0 (0%)		0 (0%)		0 (0%)
kube-system			kube-dns-76ff979c78-vs9w7				260m (26%)	0 (0%)		110Mi (5%)	170Mi (8%)
kube-system			kube-proxy-kube-node-2					0 (0%)		0 (0%)		0 (0%)		0 (0%)
kube-system			kubernetes-dashboard-6cfdb48488-6j6cb			100m (10%)	100m (10%)	50Mi (2%)	50Mi (2%)
kube-system			tiller-deploy-5458cb4cc-5454m				0 (0%)		0 (0%)		0 (0%)		0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests	CPU Limits	Memory Requests	Memory Limits

610m (61%)	100m (10%)	160Mi (8%)	220Mi (11%)
Result :
I can reach the Nginx server from the worker nodes, but I can't reach it from the outside.
http <IP_ADDRESS>:80
http: error: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) while doing GET request to URL: http://<IP_ADDRESS>:80/
What you expected to happen:
Access Nginx web server through node IP.
How to reproduce it (as minimally and precisely as possible):
Vagrant setup :
`# boxes at https://atlas.hashicorp.com/search.
BOX_IMAGE = "bento/ubuntu-16.04"
NODE_COUNT = 3 # 1 node pour le master, 1 node pour etcd, 2 nodes worker
id_rsa_key_pub = File.read(File.join(Dir.home, ".ssh", "local_k8s_id_rsa.pub"))
Vagrant.configure("2") do |config|
#Creation des nodes Kubernetes (1 master, 1 etcd, 2 worker)
(1..NODE_COUNT).each do |i|
config.vm.define "kube-node-#{i}" do |subconfig|
subconfig.vm.box = BOX_IMAGE
subconfig.vm.provider "virtualbox" do |v|
v.memory = 2048
end
subconfig.vm.hostname = "kube-node-#{i}"
subconfig.vm.provision "file", source: "~/.ssh/local_k8s_id_rsa.pub", destination: "~/.ssh/local_k8s_id_rsa.pub"
subconfig.vm.network :private_network, ip: "10.0.0.#{10+i}"
end
end
config.vm.provision :shell,
:inline => "echo 'appending SSH Pub Key to ~vagrant/.ssh/authorized_keys' && echo '#{id_rsa_key_pub}' >> /home/vagrant/.ssh/authorized_keys && chmod 600 /home/vagrant/.ssh/authorized_keys"
end`
Anything else we need to know?:
It seems that the incoming requests are filtered by the worker nodes firewall.
nmap -P0 <IP_ADDRESS>
Starting Nmap 7.60 ( https://nmap.org ) at 2017-11-21 08:53 CET
Nmap scan report for <IP_ADDRESS>
Host is up (0.000048s latency).
All 1000 scanned ports on <IP_ADDRESS> are filtered
Kuberang test:
Kuberang reports an [ERROR IGNORED] while trying to access Nginx pod :
kuberang-darwin-amd64
Kubectl configured on this node                                                 [OK]
Delete existing deployments if they exist                                       [OK]
Nginx service does not already exist                                            [OK]
BusyBox service does not already exist                                          [OK]
Nginx service does not already exist                                            [OK]
Issued BusyBox start request                                                    [OK]
Issued Nginx start request                                                      [OK]
Issued expose Nginx service request                                             [OK]
Both deployments completed successfully within timeout                          [OK]
Grab nginx pod ip addresses                                                     [OK]
Grab nginx service ip address                                                   [OK]
Grab BusyBox pod name                                                           [OK]
Accessed Nginx service at <IP_ADDRESS> from BusyBox                            [OK]
Accessed Nginx service via DNS kuberang-nginx-1511266770609033000 from BusyBox  [OK]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                               [OK]
Accessed Nginx pod at <IP_ADDRESS> from BusyBox                                [OK]
Accessed Google.com from BusyBox                                                [OK]
Accessed Nginx pod at <IP_ADDRESS> from this node                             [ERROR IGNORED]
Accessed Nginx pod at <IP_ADDRESS> from this node                              [ERROR IGNORED]
Accessed Google.com from this node                                              [OK]
Powered down Nginx service                                                      [OK]
Powered down Busybox deployment                                                 [OK]
Powered down Nginx deployment                                                   [OK]
Environment:

Kismatic version (use kismatic version):
Kismatic:
Version: 1.6.1
Built: Mon Nov  6 15:54:47 UTC 2017
Go Version: go1.8.5
Plan file Gist (remove sensitive information if any): https://gist.github.com/emanuguerra/9c5274e92b57f36a03abe68ee26d9eb9
Cloud provider or hardware configuration:
Virtual Box 5.1.20 provisioned with Vagrant boxes bento/ubuntu-16.04
OS (e.g. from /etc/os-release):
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Kernel (e.g. uname -a):
Linux kube-node-3 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This is not a bug. With this setup, the Nginx server is accessed on a random port (in a range >30000) that can be read with kubectl describe service nginx : the NodePort.


linux_persist_priv_batch_4

Linux Persistence And Privilege Escalation Detections

linux_add_user_account.yml
linux_common_process_for_elevation_control.yml
linux_doas_conf_file_creation.yml
linux_doas_tool_execution.yml
linux_possible_access_to_credential_files.yml
linux_possible_access_to_sudoers_file.yml
linux_sudo_or_su_execution.yml

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Add User Account :white_check_mark:

diskUsage: 516096
runDuration: 2.422s
scanCount: 1412

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Doas Conf File Creation :white_check_mark:

diskUsage: 479232
runDuration: 5.507s
scanCount: 7226

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Doas Tool Execution :white_check_mark:

diskUsage: 507904
runDuration: 10.58s
scanCount: 14622

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Possible Access To Credential Files :white_check_mark:

diskUsage: 385024
runDuration: 3.031s
scanCount: 1160

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Sudo OR Su Execution :white_check_mark:

diskUsage: 409600
runDuration: 3.513s
scanCount: 3388

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Possible Access To Sudoers File :white_check_mark:

diskUsage: 364544
runDuration: 4.37s
scanCount: 1165

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Linux Common Process For Elevation Control :white_check_mark:

diskUsage: 516096
runDuration: 3.745s
scanCount: 3617


Anaconda download server down

I tried several time to access to this web page given in the Environment setup for the AI training session.
I have the following error :
Error 522 Ray ID: 46379291adc43bb1 • 2018-10-02 13:39:30 UTC Connection timed out
Here is the snapshot :

This works instead: https://www.anaconda.com/download/


[flet build windows] fails for some reason

I have all the requirements right:

Flet 0.19.0
Visual Studio Build Tools 2022:

Flutter 3.16.9 • Dart 3.2.6 • DevTools 2.28.5 (Added to PATH)
Developer Mode (I have windows 11)

I am using [flet build windows] in a To-Do app, the code works correctly.
------- LOG -------
$ flet build windows --verbose
Flutter bootstrap directory: C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh
Creating Flutter bootstrap project...OK
Customizing app icons and splash images...Copying C:\Users\USER\Desktop\FLET_TODO_2COND\assets\icon.png to
C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\images
OK
Generating app icons...OK
Packaging Python app...OK
Building Windows app...['C:\Users\USER\dev\flutter\bin\flutter.BAT', 'build', 'windows']
Resolving dependencies...
ffi 2.1.0 (2.1.2 available)
fl_chart 0.65.0 (0.66.1 available)
flutter_lints 2.0.3 (3.0.1 available)
flutter_native_splash 2.3.7 (2.3.9 available)
js 0.6.7 (0.7.0 available)
lints 2.1.1 (3.0.0 available)
matcher 0.12.16 (0.12.16+1 available)
material_color_utilities 0.5.0 (0.8.0 available)
meta 1.10.0 (1.11.0 available)
package_info_plus 4.2.0 (5.0.1 available)
path 1.8.3 (1.9.0 available)
petitparser 5.4.0 (6.0.2 available)
test_api 0.6.1 (0.7.0 available)
toml 0.14.0 (0.15.0 available)
web 0.3.0 (0.4.2 available)
web_socket_channel 2.4.0 (2.4.3 available)
xml 6.3.0 (6.5.0 available)
Got dependencies!
17 packages have newer versions incompatible with dependency constraints.
Try flutter pub outdated for more information.
windows/flutter/CMakeLists.txt does not use FLUTTER_TARGET_PLATFORM, updating.
Building Windows application...
Building Windows application...                                  1188.3s
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\ZERO_CHECK.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\serious_python_windows\CopyPyth
onDLLs.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\flutter\flutter_assemble.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\flutter\flutter_wrapper_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\audioplayers_windows\audioplaye
rs_windows_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\flutter\flutter_wrapper_app.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\screen_retriever\screen_retriev
er_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\serious_python_windows\serious_
python_windows_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.38.33130\include\format(42): warning
STL4038: The contents of  are available only with C++20 or later.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\serious_python_windows\serious_
python_windows_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\url_launcher_windows\url_launch
er_windows_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\window_manager\window_manager_p
lugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\plugins\window_to_front\window_to_front
_plugin.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\runner\flet_todo_2cond.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\ALL_BUILD.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could
lead to issues with incremental build.
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: The command "setlocal
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: "C:\Program Files
(x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe"
-DBUILD_TYPE=Release -P cmake_install.cmake
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: if %errorlevel% neq 0
goto :cmEnd [C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmEnd
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: endlocal & call
:cmErrorLevel %errorlevel% & goto :cmDone
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmErrorLevel
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: exit /b %1
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmDone
[C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: if %errorlevel% neq 0
goto :VCEnd [C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
C:\Program Files (x86)\Microsoft Visual
Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :VCEnd" exited with
code 1. [C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh\build\windows\x64\INSTALL.vcxproj]
Build process failed.
Deleting Flutter bootstrap directory C:\Users\USER\AppData\Local\Temp\flet_flutter_build_tJQQVZLCxh
Error building Flet app - see the log of failed command above.

Try upgrading to the latest "Dev" release of flet package: https://pypi.org/project/flet/0.20.0.dev2183/
Then build with flet build windows -vv - it will yield super-detailed output from flutter build command. Maybe we'll see some more details there.

Try upgrading to the latest "Dev" release of flet package: https://pypi.org/project/flet/0.20.0.dev2183/ Then build with flet build windows -vv - it will yield super-detailed output from flutter build command. Maybe we'll see some more details there.

(venv)
USER@DESKTOP-0D4Q1HS MINGW64 ~/Desktop/FLET_TODO_2COND
$ flet --version
0.20.0.dev2183
(venv)
USER@DESKTOP-0D4Q1HS MINGW64 ~/Desktop/FLET_TODO_2COND
$ flet build windows -vv
Flutter executable: C:\Users\USER\dev\flutter\bin\flutter.BAT
Dart executable: C:\Users\USER\dev\flutter\bin\dart.BAT
Flutter bootstrap directory: C:\Users\USER\AppData\Local\Temp\flet_flutter_build_SGVOKKnCzT
Creating Flutter bootstrap project...Deleting Flutter bootstrap directory C:\Users\USER\AppData\Local\Temp\flet_flutter_build_SGVOKKnCzT
The 0.20.0.dev2183 branch of repository https://github.com/flet-dev/flet-build-template.git could not found, have you made
a typo?
(venv)
USER@DESKTOP-0D4Q1HS MINGW64 ~/Desktop/FLET_TODO_2COND
$

Ah, good point!
Run it with:
flet build windows --template-ref 0.20.0 -vv

Ah, good point!
Run it with:
flet build windows --template-ref 0.20.0 -vv

Here is the log:
build_log.txt

Can you check if you have C:/Windows/system32/vcruntime140_1.dll file?

same problem

same problem

I have the same error  , the solution it work for me was INSTALL Visual Studio community 2022 ， after installed . build successd

INSTALL Visual Studio community 2022

@418kz can you give it a try.

I have a similar problem. I already installed Visual Studio 2022 but it did not compile successfully.

Dart SDK version: 3.5.0 (stable) (Tue Jul 30 02:17:59 2024 -0700) on "windows_x64"
Flutter 3.24.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 80c2e84975 (12 days ago) • 2024-07-30 23:06:49 +0700
Engine • revision b8800d88be
Tools • Dart 3.5.0 • DevTools 2.37.2

I am using poetry, and when I run poetry run flet build windows --verbose although it ends with the indication that the compilation was successful, in the middle of the process it sends warnings, especially this one:

MSBuild MSB8029: C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(541,5): warning MSB8029:The intermediate directory or the output directory cannot be in the temporary directory, as this could lead to problems with incremental compilation.

15 packages have newer versions incompatible with dependency constraints.

ChatGPT suggested a solution but I can't find the file it indicates:
''What you need to do is edit the project configuration files where CMake sets the output paths for binary files, libraries and application files. These files are usually called CMakeLists.txt.''

@carlos-alberto-code will you mind sharing your errors as text (in english)?

Following the prompts, I successfully compiled my project
The following is the detailed log
build.log
It is recommended to use the vscode tool with the log plug-in to view

Project Structure


feat: Kick off CLI runs straight away

People are quite sensitive to the amount of time they have to wait for Terraform runs kicked off from CLI, this change triggers such runs straight after it's created.
Additional changes:

Format
Remove excessive startNow call from createJobContextNow

On this topic @ alfespa17, any reasons we should not do the same for all the runs?

Hello @stanleyz there is a reason behind it.
When you create a job it validate if there are jobs running to continue the execution, if there are jobs running it will check in 1 minute
For example here, it validates if there are no previous jobs and does nothing until it checks again in 1 minute
https://github.com/AzBuilder/terrakube/blob/e30c9863d034fb8b7908ce566dab2a08a276215d/api/src/main/java/org/terrakube/api/plugin/scheduler/ScheduleJob.java#L109
If you trigger the job intermediately the quartz job will only run once and terraform cli will be waiting forever to continue because the job wont change from the initial pending status never here
https://github.com/AzBuilder/terrakube/blob/e30c9863d034fb8b7908ce566dab2a08a276215d/api/src/main/java/org/terrakube/api/plugin/scheduler/ScheduleJob.java#L112
And if you are running the CLI driven workflow the CLI is expecting previous jobs execute in order and shows something like this:
https://terrakube-api.minikube.net/app/simple/locked-remote/runs/run-876

Waiting for 29 queued run(s) to finish before starting...
Waiting for 28 queued run(s) to finish before starting... (30s elapsed)
Waiting for 27 queued run(s) to finish before starting... (1m0s elapsed)

This is why to start the job execution Terrakube always create the quartz job using using scheduleJobService.createJobContext(job); instead of scheduleJobService.createJobContextNow(job);
Once the job starts Terrakube trigger a job intermediately each time the Job entity is update here:
https://github.com/AzBuilder/terrakube/blob/e30c9863d034fb8b7908ce566dab2a08a276215d/api/src/main/java/org/terrakube/api/rs/hooks/job/JobManageHook.java#L37
let me know if you have any suggestion to improve that logic

Right, thanks @alfespa17 for the explanation, I didn't take a close a look on the CRON expressions.
Can we modify the createJobContext to kick off the job straight away with 30 seconds frequency (to be consistent with TF client prompting internal, or even make it customisable)?

Right, thanks @alfespa17 for the explanation, I didn't take a close a look on the CRON expressions.
Can we modify the createJobContext to kick off the job straight away with 30 seconds frequency (to be consistent with TF client prompting internal, or even make it customisable)?

Yeah sounds good, you can change that

The value is here by the way
https://github.com/AzBuilder/terrakube/blob/e30c9863d034fb8b7908ce566dab2a08a276215d/api/src/main/java/org/terrakube/api/plugin/scheduler/ScheduleJobService.java#L25

Can you please take a look @alfespa17 ? Thanks. I "feel" it's faster, if there are available executors, new job will be kicked off straight after it's created, otherwise the quartz will take about 20 seconds to pick it up.

hello @stanleyz I added some comments in the method scheduleJobService.createJobContextNow

hello @stanleyz I added some comments in the method scheduleJobService.createJobContextNow

Hi mate, I do not see your comment, did you submit?

hello @stanleyz I added some comments in the method scheduleJobService.createJobContextNow

Hi mate, I do not see your comment, did you submit?

Hello @stanleyz it was related to a .startNow() that was removed from method createJobContextNow but I just noticed it was duplicated, so forget about my comment I will merge the change


Double check version management for update site

This problem is unexpected because the fix was deployed to the update site already
https://forum.image.sc/t/sciview-requirements-for-fiji-users/36325/5

I'm having trouble reproducing this on Ubuntu from the current version on the update site. @skalarproduktraum could you check on Windows please?

We should change the upload to update site to use the git hash on the sciview jar

see https://travis-ci.org/github/scenerygraphics/sciview/jobs/675752625#L2128
There is a problem with deployment to the update site

This was a sync issue between Fiji and pom-scijava. Fixed now, open again if it reoccurs.


Reorganizing Compiler Module

📚 Description
In order to avoid increasing the size of the root directory from the Compiler Module, and keep the common things together, I thought it might be interesting to have them grouped in submodules in order to simplify the design.
This is an idea that I had since I realized the Compiler Module gets growing and getting bigger, but I never found time to try it out.
The motivation for this PR is the very same as for https://github.com/jenshaase/phel-lang/pull/126 but applied to the context of the Compiler Module this time.
🔖 Changes
These are the directories(submodules) in which the Compiler module gets splitter, leaving on its root directory only the CompilerFactory.

Compiler

Analyzer
Ast
Compiler
Emmiter
Environment
Lexer
Parser

@jenshaase, to check out the code I think it will be easier to pull the branch and check it out locally because I changed a lot of files (mostly because of the namespaces). I am also open to renaming any folder and/or also move to another folder any file if I moved it wrong.

I would like to make the following changes:

Move AST to Analyzer. The result of the Analyzer is an Abstract Syntax Tree (AST).
Also the Environment folder can be moved to the Analyzer. The node/global environment is mainly used by the Analyzer.
I would not make a Compiler directory inside the Compiler Directory. The File Compiler for example combines every step of the build chain. Therefore, I think it is ok to leave it in the main Compiler Directory
Optional: Split the Parser directory into a Parser and Reader directory. Then we have all steps of the compiler pipeline in one folder.

Currently the compiler pipeline is this:

Lexer
Parser
Reader
Analyzer
Emitter

I would like to make the following changes:

Move AST to Analyzer. The result of the Analyzer is an Abstract Syntax Tree (AST).
Also the Environment folder can be moved to the Analyzer. The node/global environment is mainly used by the Analyzer.
I would not make a Compiler directory inside the Compiler Directory. The File Compiler for example combines every step of the build chain. Therefore, I think it is ok to leave it in the main Compiler Directory
Optional: Split the Parser directory into a Parser and Reader directory. Then we have all steps of the compiler pipeline in one folder.

Currently the compiler pipeline is this:

Lexer
Parser
Reader
Analyzer
Emitter

I prefer your idea. I will change it to end up with your suggestion folder structure 🧵

I prefer your idea. I will change it to end up with your suggestion folder structure 🧵

@jenshaase double check that I didn't miss anything from your suggestions, please. Feel free to point any possible improvement related to the scope of this PR again. Otherwise, we could merge this one.
I like the result so far. It certainly helps us to visualize the scope and responsibilities of the Compiler Module itself. The very same principle applies to all rest modules 😄

@jenshaase double check that I didn't miss anything from your suggestions, please. Feel free to point any possible improvement related to the scope of this PR again. Otherwise, we could merge this one.
I like the result so far. It certainly helps us to visualize the scope and responsibilities of the Compiler Module itself. The very same principle applies to all rest modules 😄


Countries with subtitle not parsing correctly

command line: ~/covid19-cli $ ./dist/covid19-cli.sh -l --sort deaths
rough description: Country subtitles(?) are displayed under "cases" column and all remaining values for those countries seem to be shifted one column to the right in display.
output snippets:
|  China                             |  81285                             |  3947    |  1235      |  3287    |  74051      |  67           |  6             |  56                     |
|  Iran                              |   Islamic Republic of              |  29406   |  16715     |  2746    |  2234       |  10457        |  2389          |  157                    |  350  |
|  France                            |  29155                             |  22511   |  3375      |  1696    |  4948       |  3922         |  365           |  447                    |
|  Andorra                           |  224                               |  220     |  6         |  3       |  1          |  36           |  2             |  2                      |
|  Macedonia                         |   the former Yugoslav Republic of  |  201     |  195       |  1       |  3          |  3            |  24            |  0                      |  96   |
|  Congo                             |   the Democratic Republic of the   |  51      |  48        |  0       |  3          |  0            |  3             |  1                      |  0.6  |
|  Russia                            |  840                               |  799     |  8         |  3       |  38         |  182          |  0             |  6                      |
editing to add:

gentoo kernel 4.19 amd64
bash 4.4
coreutils 8.31

edit(2) to add '-l' to cmd line above

The following - generated by the latest git code (I updated that code just now) - might result from the same problem.
~/git/covid $ covid us
 ✔  Country: us

Cases:		85594	▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▂▂▃▃▄▅▆█
Deaths:		1300	▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▂▂▂▃▄▅▆█
Recovered:	1868
~/git/covid $ covid "united states"
 ✔  Country: united states

Cases:		13
Deaths:		0

Recovered:	0

Between latest update to code and newer data sets, it seems the problem is now gone.  I suspect the underlying data was changed, but can't be 100% certain it has or that it will remain.


regarding min_sizes and max_size in config file

can you please suggest how should i define the min_sizes and max_sizes for a costume dataset?

@isalirezag It mainly depends on your input size and the object size distribution of your dataset. I only use the default setting from original SSD, e.g., [0.1,0.2,0.37,0.54,0.7,0.88] of input size for VOC300. For your own dataset, I suggest you  use k-means like in YOLOv2, or just follow the original SSD.


Look into interpolation with b splines

B splines are a better alternative to using bezier curves. Changes in control points are more localized.

Okay, B-Splines are much better than Bezier. From top to bottom: linear, bezier, bspline. With the control points affects much more localized, the interpolation shows through all the colors more, but still keeps the transitions smooth.

B-Spline does so much better that I can't think of a reason to keep Bezier around.


Aligns the Getting Started Guide with IDF v5

Updating the Getting Started Guide
Description
Updates the instructions in the getting started guide to reflect ESP-IDF v5. In particular, the instructions for flashing the certificate partition have changed. Additionally, the sdk_config has been updated to preserve backward compatibility.
Test Steps
Successfully executed the new instructions locally.
Checklist:

[X] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

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

Looks good to me!


Remove unused datasets

Description
What is the current behavior?
We are not using this dataset for benchmarking, we should remove it. Also, there was a failure for the StackExchange dataset.

End-users use real datasets, which has allowed us to surface several issues with our stack. Much more than any synthetic dataset we have.
I believe we should have end-to-end tests that use these datasets instead of simply getting rid of them.

I agree @tatiana , but currently, we are not using it in our code base anywhere. When do we start doing that we can add them again to the codebase, WDYT? we can maybe create a ticket(s) to add a test case with a real dataset?

I'm happy for them to be removed and re-introduced as long as we have a task logged for us to have e2e tests using realistic datasets, referencing this PR :)

@tatiana Added a ticket for the same - https://github.com/astronomer/astro-sdk/issues/1612

Most of these data we have stored in gcs do you want to keep it or we should clean them also example gs://astro-sdk/benchmark/trimmed/github/github_timeline_100mb.csv @utkarsharma2 ?

We should do that as well. I'll merge this PR for now. I'll create a separate ticket for this.


feat: add neovim icons

Nerd fonts 3.1.0 added icons for neovim itself, which should really be added here: https://github.com/ryanoasis/nerd-fonts/releases/tag/v3.1.0

symbols are auto generated. make sure to only modify files using nvim --headless -c "luafile ./script/downloader.lua" -c "q"

oh, I see.
all right, reset & updated correctly then.

thanks :)


Replaceall does not correct image paths in actor biographies

As per title.
For example, I have a path that looks like this: characters/reghed-shaman/Reghed Shaman-bio-1.png after running:
fwt dedup --ext=".png" --ext=".webp" --byname --preferred=".*webp" .
# check, cleanup and delete trash
fwt renameall --remove="[0-9]{3}_-_" --replace="/_+/-/" --lower .
# check, cleanup and delete trash

The result should be: characters/reghed-shaman/reghed-shaman-bio-1.webp

Let's see if we can get this worked out. I'm not sure how the original path is included in the bio and I'm curious if the bio is being changed after each of the commands you included above. Can post a comment below with more about the problem?

How is the original path in the bio used? Please include the original path in your comment, and if it's in an HTML tag please include the entire tag as it originally existed.
Please include the path in the bio after running each of the commands above.

Thanks!

It appears in the bio as HTML, after running those commands above it looks like this:

I'm not preciseBefore running those commands it looked something like this:


Create a template to display detailed data about selected API

Reference https://github.com/apinf/platform/issues/2756

Done


Makefile Modules, Go Versions and Vendoring

This issue is to capture the battling I had with makefile-modules when trying to ensure a specific Go version was used (for testing something unrelated). This might inform how we handle vendoring in the future (since GOTOOLCHAIN can kinda do vendoring).
Important reading for background: https://go.dev/doc/toolchain - nothing is happening in makefile-modules which isn't documented there, but it can be surprising.
I'll list some scenarios below and the behaviour that happens with makefile modules today
Scenario 1: High go.mod Version, Default Configuration
The Go toolchain docs are clear that the go values in a go.mod file can take precedence over the actual version fo Go being used:

In the standard configuration, the go command uses its own bundled toolchain when that toolchain is at least as new as the go or toolchain lines in the main module or workspace.
For example, when using the go command bundled with Go 1.21.3 in a main module that says go 1.21.0, the go command uses Go 1.21.3.
When the go or toolchain line is newer than the bundled toolchain, the go command runs the newer toolchain instead. For example, when using the go command bundled with Go 1.21.3 in a main module that says go 1.21.9, the go command finds and runs Go 1.21.9 instead.

The "standard configuration" is GOTOOLCHAIN=auto which is the default (see footnotes).
This means that make vendor-go is mostly irrelevant to the actual version of Go being run - VENDORED_GO_VERSION sets the floor of how low the Go version can be, but if used on a project whose go.mod requests a version higher than VENDORED_GO_VERSION, the vendored go toolchain will just download that new Go version and run that higher version, sidestepping vendoring in makefile-modules almost entirely.
In this scenario, makefile-modules is simply a bootstrapper for Go as long as VENDORED_GO_VERSION is higher than 1.21 (when toolchains were first introduced).
Scenario 2: High go.mod Version, GOTOOLCHAIN=local
We can set GOTOOLCHAIN=local to force the version of Go to match the actual version in the binary. So if VENDORED_GO_VERSION=1.23.1, that version will always be used. If the go.mod file says go.1.23.2 in this scenario, the project will fail to build:

go: go.mod requires go >= 1.23.2 (running go 1.23.1; GOTOOLCHAIN=local)

Scenario 3: Explicit GOTOOLCHAIN Version
As long as a version of Go 1.21+ is available - either on the system or via  make vendor-go - GOTOOLCHAIN can be used to intentionally download a specific version of Go, which is similar how make vendor-go works.
GOTOOLCHAIN Playground
Create the following go.mod:
module github.com/sgtcodfish/goversions-makefile-modules

go 1.21.0

And the following main.go:
package main

import (
	"fmt"
	"runtime"
)

func main() {
	fmt.Println(runtime.Version())
}

Then the following will be the output:
$ go env GOTOOLCHAIN
local

$ go run main.go
go1.23.2

$ GOTOOLCHAIN=go1.21.1 go run main.go
go: downloading go1.21.1 (darwin/arm64)
go1.21.1

$ GOTOOLCHAIN=go1.23.2 go run main.go
go1.23.2

What's the problem?
In makefile-modules today, VENDORED_GO_VERSION is sometimes not respected because toolchain logic can override it.
With GOTOOLCHAIN=auto (which again is going to be the default - see footnotes), the best makefile-modules can do today is guarantee that the lowest version which will be used for building is either the value in go.mod or the value in VENDORED_GO_VERSION, whichever is higher.
Since we update VENDORED_GO_VERSION regularly and automatically, changing the GOTOOLCHAIN variable's value might seem redundant - most projects are going to be released having been built with the latest value of VENDORED_GO_VERSION.
The issues are that:

It's not immediately clear which version will be used from looking at the project. You can't rely on VENDORED_GO_VERSION or go.mod individually - you have to check both and know the logic that's used.
We're reimplementing logic for downloading Go in makefile-modules with complicated symlink magic
Go binaries downloaded through GOTOOLCHAIN are cached alongside Go modules, which might be more efficient in scenarios where we don't cache downloaded assets but do cache go modules. (see ls $(go env GOPATH)/pkg/mod/golang.org/ to see cached Go versions)

What should we do?
We have three options.
1. Set GOTOOLCHAIN=local
Knowing exactly what Go version will be used to build is valuable. It means that a quick glance at a commit will provide a single source of truth of what version will be used.
If we unconditionally set GOTOOLCHAIN=local when using make vendor-go we'll ensure that the Go version used is exactly VENDORED_GO_VERSION, and if go.mod is updated to require a newer version of Go the build will fail until the VENDORED_GO_VERSION is updated to the same version or newer.
2. Switch to using GOTOOLCHAIN to vendor Go
If make vendor-go were changed to set export GOTOOLCHAIN=go$(VENDORED_GO_VERSION) we'd have very similar behaviour to what we currently have except Go versions would be cached alongside Go modules, and we could remove our symlink logic.
Or, if we keep the symlink logic (or something like it) we'll download a Go toolchain using make vendor-go which will then be mostly ignored in favour of  GOTOOLCHAIN logic. This will help in environments with Go not installed (e.g. some CI jobs).
One advantage of this is that it would be quite easy to allow projects to vary the Go version they use, so we could keep e.g. cert-manager 1.16 on go1.23.x but use go1.24.x for cert-manager 1.17
3. Do Nothing
It won't be obvious at a glance which version of Go will be used to build, but maybe we accept that.
Footnotes
Default value for GOTOOLCHAIN: Downloaded go tarballs (i.e. the ones we download with make vendor-go) contain a go.env file in the GOROOT which sets GOTOOLCHAIN=auto. Your local value of GOTOOLCHAIN may have a different value, either because you set it with go env -w or because it defaulted to local or some other value.

I don't like the option of GOTOOLCHAIN=auto

Yeah I tend to agree. I don't like option 3 and I think we should change something.

We should explicitly what version of Go is used to compile and IMO in the context of CI I think GOTOOLCHAIN=local makes the most sense, why download one version just to have it download another.

Yeah that's fair. For option 2, I think in CI terms it would make some some sense as long as we ensure all of our base images include some version of Go >= 1.21 - then we'd no longer have to download a tarball with vendor-go in CI, and we'd still just be downloading one version of Go in most CI jobs (just we'd be using GOTOOLCHAIN to do it rather than make vendor-go).

I don't like the idea of varying the go version per project as it means we have more to track in terms of ensuring we are up to date, but if that is really a feature people want we could change VENDORED_GO_VERSION from := to ?=.

Good point, agreed. I like that we update everywhere at once, automatically.
I do like the idea of changing VENDORED_GO_VERSION to ?= - it would help with debugging in some cases but those cases are pretty niche!


Debug - build errors not links

I read that as "Make love not war" -- now I get it: build errors are not showing up as links.  Yes this requires a markup filter on the output of the Debug Console -- I can do that easily..

done


[Help Required] Release new version

What you are struggling with
We're using the sort order from https://github.com/yesoreyeram/yesoreyeram-boomtable-panel/commit/5b1c2ebc4665d77f0b0b681870a03c8ceb8ca084 in production. This fixes the column order when using the mixed datasource. Without that fix, the order randomly changes when the data is refreshed.
Could you consider releasing a new version to https://grafana.com/grafana/plugins/yesoreyeram-boomtable-panel/installation? This would allow us install the plugin unsing grafana-cli plugins install.
What you tried
As a workaround, we're now manually checking out master and using that.
Related Issues and Links
(none)

As a workaround, we're now manually checking out master and using that.

How do you do it exactly?
Thanks

I can't tell you exactly. Multiple teams were involved. I've tried to find a few pointers.
Basically:

Checkout the repo to /var/lib/grafana/data/plugins/yesoreyeram-boomtable-panel (or wherever your Grafana installation has it's plugin folder)
Check out the commit you want
Restart grafana

There might be some pieces missing, those guides helped us:

How to install pugins manually
Grafana Guide on developing plugins


wrong last stable version

for package SqlKata npm-gui show latest stable version 3.2.3, but last stable 2.4.0

Hi @askovpen
It appears that the issue you're experiencing is related to a potential cache inconsistency on the NuGet.org platform. It seems that a newer version of the package was uploaded, but subsequently removed. As a result, the JSON feed (accessible at this URL) might still be reflecting outdated or incorrect information due to the caching mechanism used by NuGet.org.
When packages are uploaded and then removed, NuGet's cache may not immediately update to reflect these changes. This can lead to situations where references to non-existent versions persist in the feed, causing confusion or errors during package retrieval.
To resolve this, you may need to wait for the cache to expire and refresh, or contact NuGet support to expedite the process if the issue persists.

this version (3.2.3) half year wrong

https://github.com/NuGet/NuGetGallery/issues/10164

https://github.com/NuGet/NuGetGallery/issues/10164#issuecomment-2315322282


Enable 'Method can be static' inspection in IntelliJ

For methods that don't need access to the current instance it is good practice to mark as static: only allow access to context that is actually needed.
Note that the corresponding inspection is already enabled for Groovy.

@bot-gradle test and merge this.

OK, I've already triggered a build for you.


plugin: separate language support for localizable texts

Fixes #1074
config screen with updated dll file

Important part

Before: There were
Langauge: en
Version: Intl

After: With my change
Parsing Plugin Langauge: en // was 'Language' before
PC Locale: ko-KR // new added information here
Version: Intl

PC Locale now used for config language, not parsing plugin's language.
Enforce 'zh' to 'cn'
Options.ShortLocale = e.detail.locale.substring(0, 2);
if (Options.ShortLocale == 'zh')
  Options.ShortLocale = 'cn';

Chinese locale is zh-**, but cactbot is using 'cn' for Chinese locale (or language).
So I've enforce to change to 'cn'.
Why do I check supportedLanguage?
const supportedLanguage = ['en', 'de', 'fr', 'ja', 'cn', 'ko'];
if (supportedLanguage.indexOf(shortLocale) == -1)
  shortLocale = 'en';
this.lang = shortLocale;

Most localized text are shown in English if not user's language is supported. But sometimes, there can be a mistake forgot to add || 'en' which is used to enforce use English if user's language is not supported.
Upper code will prevent this problem for other regions.
Example, ru-RU. (There were no 'ru' thing coming before since there's no FFXIV Parsing Plugin Language for Russian.)
Config text becomes [Object object] without || 'en'.
download for test
CactbotEventSource.zip

config screen is not changed to your locale before you apply my change with resources/user_config.js and ui/config/config.js, you can only check PC Locale: ko-KR thing on Overlay plugin Log with this dll file.

other helpful link
Langauge Code Table: http://www.lingoes.net/en/translator/langcode.htm
minor change with html class about language
After timeline supports changing language, language info in html class should be timelineLanguage.

I had this error so I changed some code.
/home/travis/build/Jaehyuk-Lee/cactbot/ui/raidboss/popup-text.js
  238:1  error  This line has a length of 102. Maximum allowed is 100  max-len

I think both line works the same. If doesn't please tell me. I had to make this line shorten.
            let netRegex = trigger[netRegexParseLang] ? trigger[netRegexParseLang] : trigger.netRegex;
            let netRegex = trigger[netRegexParseLang] || trigger.netRegex;

I've removed manual language setting on fisher.js, it worked well without it.
(Tested on English client and Japanese client, thanks to free login campaign :smiley:)
9e1390d

I've changed comment and text saying "locale" to "parser language" thing. I don't understand exactly what that means, so some transition might wrong. Please check this. thanks!
d9f469e

I wrote wrong code there and two codes actually had same speed, so removed that comment but you've seend it :sweat_smile:
I thought extreme performance improvement worth than readability.

Ha, thanks for the info.  I'm glad to know!

Thanks for all the changes.  I think this all looks good.  I want to try this out myself in game (and hopefully I should have time tomorrow or Friday), but I don't have any other feedback at this point.
As a followup, do you think we should remove alerts language / timeline language and have those use DisplayLanguage as well?

I think it's better to be remained. Skill names are like "proper noun" thing. Skill name's translation to each language client is not far different but rarely, their names are very different. So, this means people can't understand timeline with their display language since they see client's skill name.
Ummm... Someone would want to see as parsing plugin's language. I don't know if we should change to selection of "parsing plugin language" and "display language". It's okay for remaining as now.

I actually understood you wanted separate pull request but I was like easier to make changes in this branch because I have done some work for that displayLanguage thing. I was thinking that would be better for manual language selection which has higher priority of applying language than auto selected system language before you say about adding displayLanguage setting.

I actually understood you wanted separate pull request but I was like easier to make changes in this branch because I have done some work for that displayLanguage thing.

Ah, thanks for clarifying.  I think I just don't want you to feel like this pull request is taking forever to merge because there keeps being more things.  Sometimes it feels (for my own pull requests, at least?) simpler to merge one thing, and then do the next, rather than keep trying to append more and more into the same pull request.  Sometimes though it is harder and more complicated to break things up, so if you were already in the middle of it, then that's quite fine.
Mostly I am just apologizing for leaving so many comments here.  I just really think this is a nice feature and want to make sure it applies everywhere and makes sense with everything else that already exists.  :)

I was thinking that would be better for manual language selection which has higher priority of applying language than auto selected system language before you say about adding displayLanguage setting.

Ok, so to reiterate what you are saying, you're saying that you also think that the priority for languages should go:
AlertLanguage/TimelineLanguage > DisplayLanguage > ParserLanguage > English
(And for things that don't have AlertLanguage/TimelineLanguage, then just start with DisplayLanguage, if set.)

I gathered all changes about displayLanguage into one commit by resetting and pushing with force option, I thought this would be enough to review because reviewer have to see only one commit.

Yeah, this is fine! I think extra commits can make it easier to see what has changed, but it is not a big deal for me either way.

Ok, so to reiterate what you are saying, you're saying that you also think that the priority for languages should go:
AlertLanguage/TimelineLanguage > DisplayLanguage > ParserLanguage > English

I want
TimelineLanguage > ParserLanguage > English
(AlertLanguage > )DisplayLanguage > ParserLanguage > English
So, no display language for timeline

Ok, so to reiterate what you are saying, you're saying that you also think that the priority for languages should go:
AlertLanguage/TimelineLanguage > DisplayLanguage > ParserLanguage > English

I want
TimelineLanguage > ParserLanguage > English
(AlertLanguage > )DisplayLanguage > ParserLanguage > English
So, no display language for timeline
This is not actually a big deal to remove display language part on timeline language, because users can select manually with timeline language setting.

I think I disagree a tiny bit, but not very strongly.  It feels kind of inconsistent, and I worry a bit about the future bug report where somebody says "I put my display language in French, so why are the timeline entries in English??" However! I think you are much more in touch with what people are expecting when playing with multiple languages, and if you think this will make much more sense, then I will listen to your advice that timeline language should not use display language.
In other words, I am in agreement with what you said above.  Thank you for all the discussion.
Does that mean that the option for alert language should say "Use display language by default" instead of "use plugin language" or whatever it says now?

oh yes, I think "Use display language by default" is better for Alerts.

I don't know other language translation, so ... I didn't make any changes on alert language setting, someone should fix this.


Check java version during build

Check List:

Fixes NA
Unit tests :  NA
Javadoc with a code example (on API only) :  NA
PR meets the contributing guidelines

Description
It looks like project to build require java 11 at least, so check this requirement at the build beginning can help - especially for new contributors.

AssertJ v3.x should be buildable with Java 8+. Are you having a specific issue with versions older than 11?

GitHub Actions use

11 in main.yml, pitest-*.yml
14, 15, 16, 17-ea in  cross-version.yml

so I assume that 11 is minimum version

With

openjdk version "1.8.0_292"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)

and
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

I have errors:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project assertj-core: Compilation failure: Compilation failure:
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/Iterable_special_assertion_methods_in_assumptions_Test.java:[121,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(org.assertj.core.api.iterable.ThrowingExtractor<capture#1 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String,java.lang.Exception>,org.assertj.core.api.iterable.ThrowingExtractor<capture#2 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer,java.lang.Exception>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/Iterable_special_assertion_methods_in_assumptions_Test.java:[123,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(org.assertj.core.api.iterable.ThrowingExtractor<capture#3 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String,java.lang.Exception>,org.assertj.core.api.iterable.ThrowingExtractor<capture#4 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer,java.lang.Exception>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/Iterable_special_assertion_methods_in_assumptions_Test.java:[126,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(java.util.function.Function<capture#5 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String>,java.util.function.Function<capture#6 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/Iterable_special_assertion_methods_in_assumptions_Test.java:[128,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(java.util.function.Function<capture#7 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String>,java.util.function.Function<capture#8 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/List_special_assertion_methods_in_assumptions_Test.java:[117,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(org.assertj.core.api.iterable.ThrowingExtractor<capture#9 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String,java.lang.Exception>,org.assertj.core.api.iterable.ThrowingExtractor<capture#10 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer,java.lang.Exception>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/List_special_assertion_methods_in_assumptions_Test.java:[119,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(org.assertj.core.api.iterable.ThrowingExtractor<capture#11 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String,java.lang.Exception>,org.assertj.core.api.iterable.ThrowingExtractor<capture#12 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer,java.lang.Exception>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/List_special_assertion_methods_in_assumptions_Test.java:[122,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(java.util.function.Function<capture#13 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String>,java.util.function.Function<capture#14 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>
[ERROR] .../public/assertj-core/src/test/java/org/assertj/core/api/assumptions/List_special_assertion_methods_in_assumptions_Test.java:[124,65] cannot find symbol
[ERROR]   symbol:   method flatExtracting(java.util.function.Function<capture#15 of ? super org.assertj.core.data.TolkienCharacter,java.lang.String>,java.util.function.Function<capture#16 of ? super org.assertj.core.data.TolkienCharacter,java.lang.Integer>)
[ERROR]   location: class org.assertj.core.api.ObjectAssert<java.lang.Object>

so errors on 1.8 confirms my suspicion from 1

We use java 11 to generate the javadoc with the search capability.


Bad dependence

"material-ui": "^0.15.0-alpha.2",
I install this version but no lib folder,but four days ago it has,why?
I have try to install 0.14, it works good.

Read the README

which part?I have try npm install material-ui@next and got peer error

   "babel-core": "^6.4.5",
    "babel-loader": "^6.2.2",
    "babel-preset-es2015": "^6.3.13",
    "babel-preset-react": "^6.3.13",
    "babel-preset-react-hmre": "^1.1.0",
    "express": "^4.13.4",
    "material-ui": "^0.15.0-alpha.2",
    "mongodb": "^2.1.16",
    "mongoose": "^4.4.13",
    "radium": "^0.17.1",
    "react": "^0.14.7",
    "react-dom": "^0.14.7",
    "react-redux": "^4.4.2",
    "react-router": "^2.0.1",
    "react-router-redux": "^4.0.2",
    "react-tap-event-plugin": "^0.2.2",
    "redux": "^3.4.0",
    "redux-logger": "^2.6.1",
    "redux-thunk": "^2.0.1",
    "webpack": "^1.12.13",
    "webpack-dev-middleware": "^1.5.1",
    "webpack-hot-middleware": "^2.6.4"

Because you install  "react-tap-event-plugin": "^2.2.0",
which is for react 0.14
if you are react 0.15
install  "react-tap-event-plugin": "^1.0.0", then others package will just install fine


[QUESTION] Local musicgen models go where?

Wanting to use this with some large models that don't appear to be coded into audiocraft.py - was able to download and install and use the large model via audiocraft.py but I'm not sure where the webui puts them?
I'd also like to use facebook's newer stereo models but seem to be having an issue loading them. I'm guessing this may be due to incompatible format / coding - would they be throwing up errors if I tried to load them through the webui?
Lastly, it would be great to have an option not use huggingface for downloads/storage for models. A 'models dir' would be amazing. I've run into this a few times - when it works, great, but when you don't have an internet connection / you've spent hours meticulously organizing your models locally, having to go through the rigmarole of editing code to have a script point directly to your local files is a headache. That and I frankly have 0 faith in the longevity of any file hosted online.
Thanks for all your hard work!
Quick update - I'm getting errors trying to load any of the melody models:
Traceback (most recent call last):
File "/mnt/models/Audio/audio-webui/webui/modules/implementations/audiocraft.py", line 26, in create_model
model = MusicGen.get_pretrained(pretrained, device=map_device) if pretrained not in audiogen_models else AudioGen.get_pretrained(pretrained, device=map_device)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/models/musicgen.py", line 126, in get_pretrained
lm = load_lm_model(name, device=device)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/models/loaders.py", line 114, in load_lm_model
model = builders.get_lm_model(cfg)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/models/builders.py", line 97, in get_lm_model
condition_provider = get_conditioner_provider(kwargs["dim"], cfg).to(cfg.device)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/models/builders.py", line 141, in get_conditioner_provider
conditioners[str(cond)] = ChromaStemConditioner(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/modules/conditioners.py", line 546, in init
self.chroma_len = self._get_chroma_len()
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/modules/conditioners.py", line 596, in _get_chroma_len
dummy_chr = self.chroma(dummy_wav)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/audiocraft/modules/chroma.py", line 56, in forward
spec = self.spec(wav).squeeze(1)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/torchaudio/transforms/_transforms.py", line 110, in forward
return F.spectrogram(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/torchaudio/functional/functional.py", line 126, in spectrogram
spec_f = torch.stft(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/torch/functional.py", line 641, in stft
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
RuntimeError: cuFFT error: CUFFT_INTERNAL_ERROR
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/gradio/routes.py", line 437, in run_predict
output = await app.get_blocks().process_api(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/gradio/blocks.py", line 1352, in process_api
result = await self.call_function(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/gradio/blocks.py", line 1077, in call_function
prediction = await anyio.to_thread.run_sync(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/anyio/to_thread.py", line 33, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread
return await future
File "/mnt/models/Audio/audio-webui/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 807, in run
result = context.run(func, *args)
File "/mnt/models/Audio/audio-webui/webui/ui/tabs/audiocraft.py", line 23, in load_model
acrft.create_model(model)
File "/mnt/models/Audio/audio-webui/webui/modules/implementations/audiocraft.py", line 31, in create_model
raise gradio.Error('Could not load model!')
gradio.exceptions.Error: 'Could not load model!'
Think it's due to a lack of forward compatability for cuda 11.7 on the rtx 4090 as discussed here (was using cuda 11.8).
Going to give 11.7 a shot.
And for prosperity looks like everything is stored in the huggingface cache and I'm  a dumbass.
torch==2.0.1 torchvision torchaudio
https://github.com/neonbjb/tortoise-tts/discussions/597

Reinstalled with a frensh venv and yeah, looks like melody for audiocraft is broken.
Seems like a conflict with hydra-core. Audiocraft requires 1.1  installing 1.1 means fairseq and omegaconf's depends aren't satisfied.

@kronkinatorix did you ever find a solution for using the newer, larger stereo melody models? I couldn't get it working in audio-webui either...


[0.9] if="{{ 1 < 2 }}" not supporded?!

This si not working!
<template is="dom-repeat" items="{{items}}">
    <template is="dom-if" if="{{index == 2}}">
      <!-- show third item -->
    </template>
</template>

a bug or a feature?

http://jsbin.com/qevuzupoti/1/edit

Feature. No expressions are supported in bindings, except for ! and inline functions.
https://www.polymer-project.org/0.8/docs/migration.html#data-binding
In general, expressions like this can be replaced with inline functions or computed properties, like this:
<template is="dom-if" if="isIncluded(index)">

However, it appears that inline functions can't be defined on an auto-binding template. Not sure whether that's a bug or not.

Opened #1500 for autobinding template issue. Closing this because it's working as intended.

@arthurevans I think you mean this:
 <template is="dom-if" if="{{isIncluded(index)}}">

I have a working example at http://plnkr.co/edit/7KKqwIVVKVXt44nkuBgi?p=preview using this syntax with a custom element. It does not work using auto-bind

Yep, I was writing too fast there. Thanks, Chuck.

Ok, thanks for pointing out!

@teckays Also note, the case you showed is a good candidate for using the filter feature of dom-repeat.  It doesn't support filtering based on index (so if that's really your use case maybe not), but if your item has the criteria you would use to switch the dom-if, you'd be better using filter than dom-if, since you'd be stamping less stuff.
http://jsbin.com/dogizasicu/1/edit?html,console,output

@kevinpschaaf didn't know about the filter attribute, thank you for sharing, will definitely use it when appropriate. The use case I have requires stamping all items but some of them treat in a different way.


Triage replacing unwrap with result in runtime_args! macro.

The macro runtime_args is heavily used but contains a potentially dangerous unwrap:
https://github.com/casper-network/casper-node/blob/18571e0c22d7918a953f497649b733151cfb3c3c/types/src/runtime_args.rs#L206
Requestor: Hans

#[macro_export]
macro_rules! runtime_args {
    () => ($crate::RuntimeArgs::new());
    ( $($key:expr => $value:expr,)+ ) => (runtime_args!($($key => $value),+));
    ( $($key:expr => $value:expr),* ) => {
        {
            let mut named_args = $crate::RuntimeArgs::new();
            $(
                named_args.insert($key, $value).unwrap();
            )*
            named_args
        }
    };
}

Ed says , this is due to the underlying usage of a Vec which is a general issue if a Vec any Vec allocate more memory it must panic. It's right at the edge of an OOM. The alternative is to use an implementation that is equivalent to a Vec but exposes a fallible try allocation. Unless Michal knows a better alternative, this is essentially a won't do.


introduce way of loosening checks when testsuite not run standalone

There are tests that expect no policy being present on a cluster
before test starts in order to be able to do precide content checks.
When testsuite is run in parallel with other tests, this condition
is not met.
This commit introduces loosening of such checks which is enabled
by setting the environment variable
STANDALONE_TESTSUITE_EXECUTION
(resp. CYPRESS_STANDALONE_TESTSUITE_EXECUTION)
to 'FALSE'.

Can you set default it is turned off, only turn on when we set STANDALONE_TESTSUITE_EXECUTION?

I do not like that, honestly. IMHO tests should be run standalone by default and running tests in parallel is a special case which requires a custom configuration.
STANDALONE_TESTSUITE_EXECUTION=FALSE enables less precise checks. Additionally, running multiple tests in parallel would very likely cause issues also in other tests and if we didn't saw them yet it would be only due to a good luck. Additional policies change number of violations for a cluster, there could be also conflicts introduced by enforced policies.


Error: Minified React error #31 while adding a post

Describe the bug
When accessing to add a post section I have this message in the Editor :
Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=Sat%20Mar%2021%202020%2020%3A04%3A50%20GMT%2B0100%20(Central%20European%20Standard%20Time)&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

To Reproduce

Go to 'collections'
Click on 'post'
Click on 'new post'
See error above

Expected behavior
There should be the preview in here
Screenshots

Applicable Versions:

netlify-cms-app 2.9.7
netlify-cms-core 2.12.2
Git provider: GitHub
OS: MacOS X
Chrome

More specifically the bug occurs when I want to change the date :

It is date: '2020-03-27' in the post-one.md that works.
But it saves this way when I change the date using the datepicker :
date: 2020-03-24T23:00:00.000Z which is not the good format.

I forgot to use format field
{ label: Date / Order, name: date, widget: date, default: '', format: 'YYYY-MM-DD' }


Add support for insecure docker registry

Sometimes private docker registries don't use SSL-certificates.
Could cluster.yml have  option to add list of insecure registries, which would be added to
/etc/docker/daemon.json

{
...
"insecure-registries": ["insecure.server.local"]
...
}

Any updates on this? Can it be tagged for a milestone, please?

One option that does not need insecure-registries: https://github.com/helm/charts/tree/master/incubator/kube-registry-proxy
Proxy is deployed to every node via DaemonSet and images can be pulled via localhost:5000/xyz:latest .

This would be a bit odd because deployments will differ from the workflow used via external CI systems/developers.

This would be a bit odd because deployments will differ from the workflow used via external CI systems/developers.

I agree, bit odd and is not suitable for every use case.
Maybe we could add something like this to cluster.yml:
container_runtime:
  insecure_registries:
    - "<IP_ADDRESS>:5000"

This information would then be injected to docker/cri-o configuration files.


SAP HANA -- Ignore leading comments before anonymous blocks

Strictly speaking, it is a HANA error that occurs here, but dbeaver might circumvent it. Whenever a enclosed comment (/* */) is placed before a anonymous block and included in the statement sent to the HANA db, only statistics from the query are shown as results. Error does not occur when using single line comments (--):
/* Issue */
DO BEGIN
	SELECT * FROM dummy;
END;

-- No issue
DO BEGIN
	SELECT * FROM dummy;
END;

Could the parser be modified as to not automatically include comments before an anonymous block? SAP HANA Web-Based Development Workbench removes the comment, even when manually selecting it, such that the query produces a result. Thanks.

Can be connected with https://github.com/dbeaver/dbeaver/issues/17392

Hello @JBSP-code
Thanks for the report.
As shown in the Query Manager, DBeaver sends two identical statements.
But it seems the driver returns the result in the data form only in one case. So it can be an issue from the driver's side.
We should look into it.


feat: add organizations into ecosystem (BE/FE)

**User Story:

As an ecosystem lead, I should be able to add my organizations to my ecosystem.

Backend :

[x]  Develop a POST API to add organizations to the Ecosystem
[x] Modify a GET API to fetch all organizations by organization role
[x] Error handling

Frontend:

[x] Integrate GET API to get a list of owner organizations
[x] Integrate POST API to add organizations in the ecosystem
[x] Develop UI to show organization list
[x] Provide functionality to select multiple organizations on multiple pages

Pending Todos:
Backend

[ ]  When attempting to add another user's organization to the ecosystem using their organization ID, there is a need for validation. If the provided organization ID does not match the user's own organization ID, the system should return a '403 Forbidden' status code with the message: 'You do not have access'

Frontend

[ ] When multiple organizations are selected to add in the Ecosystem and the page is refreshed, the previously selected checkboxes should be reset

[ ] Error messages should  not be displayed after clicking the Refresh button.

As retested on the QA environment, it is working as expected


Injecting not working when adding /Zc:threadSafeInit-

So I'm trying to inject this .dll without -insecure enabled, and I read to add /Zc:threadSafeInit- to additional options when building. But, that didn't change anything. It still crashes on injection. So I'm kinda out of luck. I'm too lazy to make my own injector, and I've tried a ton of other injectors and none of them work.

Injector issue and plenty things could happen, just use loadlib and bypass stuffs there better than fixing dependencies


New version: Gnuplot v1.3.0

Registering package: Gnuplot
Repository: https://github.com/gcalderone/Gnuplot.jl
Created by: @gcalderone
Version: v1.3.0
Commit: 6bf1b80058a97347b40f91b84728cf9bdb39b760
Git reference: master

The Travis CI job 21521.2 failed, possibly because it used Julia 1.0 (in place of 1.2, as required in Project.toml.
I don't know how to proceed.
It's OK to drop this pull request, I will make a new one...

Please, if possible, ignore this PR.  I would like to open a new one to associate v1.3.0 to a new commit (I forgot to fix an important detail...)


Depsbot should be able to open PR

Please :(

+1

Also check https://github.com/hayd/deno-udd#scheduled-github-action


CI: codecov for multiprocessing

process replay wasn't really included in the codecov since it uses multiprocessing
with fix for athenad

additional coverage from process_replay:

Nice!


Feature Request: inhibit automatic link expansion

I navigate as much as possible by keyboard, but in obsidian, this is unusually messy, as obsidian expands a link any time you put a cursor on it.  This feature request would be to only expand links when asked to, and when asked, to make a popup or something like that.
Besides improving keyboard navigation, it would improve the ergonomics of editing the link text and destination, and of clicking on links when you want to go there, not edit it.
There are more details on my obsidian help feature request.  It's been up there for about a month with no takers, so I thought I'd shop it around here.

I agree that link expansion is suboptimal. However, I do not see a straightforward way to implement this feature. In this specific case, the best option would be to move your request from Help to a Feature request.

Here's the Obsidian feature request, if anybody wants to vote for it:  Inhibit automatic link address...


Fixing a small bug in the grafana tutorial

The Prometheus Helm Chart was installed incorrectly (-- I must have forgotten to convert the value back after playing around with it.)

@AnaisUrlichs could you please rebase with upstream