kubernetes_pod_example fails w/  ERROR - Failed to execute job 3 for task pod-task

Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration.
If your request is for a new feature, please use the Feature request template.

[x] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following for Terraform examples:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists
^^completed this step

Versions

Module version [Required]:

Terraform version:
v1.5.5

Provider version(s):

provider registry.terraform.io/hashicorp/aws v5.15.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.2
provider registry.terraform.io/hashicorp/helm v2.11.0
provider registry.terraform.io/hashicorp/kubernetes v2.23.0
provider registry.terraform.io/hashicorp/random v3.5.1
provider registry.terraform.io/hashicorp/time v0.9.1
provider registry.terraform.io/hashicorp/tls v4.0.4

Reproduction Code [Required]
Same code as kubernets_pod_example in schedulers/terraform/managed-airflow-mwaa
Steps to reproduce the behavior:
I just follow https://awslabs.github.io/data-on-eks/docs/blueprints/job-schedulers/aws-managed-airflow  and get a timeout error from the dag not being able to connect to EKS.
Expected behavior
Pod Example runs (authentication is successful)
Actual behavior
Timout error
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1083}} INFO - Dependencies all met for <TaskInstance: kubernetes_pod_example.pod-task manual__2023-09-06T16:53:06.944898+00:00 [queued]>
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1083}} INFO - Dependencies all met for <TaskInstance: kubernetes_pod_example.pod-task manual__2023-09-06T16:53:06.944898+00:00 [queued]>
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1279}} INFO -
--------------------------------------------------------------------------------
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1280}} INFO - Starting attempt 1 of 1
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1281}} INFO -
--------------------------------------------------------------------------------
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1300}} INFO - Executing <Task(KubernetesPodOperator): pod-task> on 2023-09-06 16:53:06.944898+00:00
[2023-09-06, 16:53:10 UTC] {{standard_task_runner.py:55}} INFO - Started process 436 to run task
[2023-09-06, 16:53:10 UTC] {{standard_task_runner.py:82}} INFO - Running: ['airflow', 'tasks', 'run', 'kubernetes_pod_example', 'pod-task', 'manual__2023-09-06T16:53:06.944898+00:00', '--job-id', '3', '--raw', '--subdir', 'DAGS_FOLDER/mwaa_pod_example.py', '--cfg-path', '/tmp/tmp1mz298b4']
[2023-09-06, 16:53:10 UTC] {{standard_task_runner.py:83}} INFO - Job 3: Subtask pod-task
[2023-09-06, 16:53:10 UTC] {{task_command.py:388}} INFO - Running <TaskInstance: kubernetes_pod_example.pod-task manual__2023-09-06T16:53:06.944898+00:00 [running]> on host ip-10-0-24-245.us-west-2.compute.internal
[2023-09-06, 16:53:10 UTC] {{taskinstance.py:1507}} INFO - Exporting the following env vars:
AIRFLOW_CTX_DAG_OWNER=aws
AIRFLOW_CTX_DAG_ID=kubernetes_pod_example
AIRFLOW_CTX_TASK_ID=pod-task
AIRFLOW_CTX_EXECUTION_DATE=2023-09-06T16:53:06.944898+00:00
AIRFLOW_CTX_TRY_NUMBER=1
AIRFLOW_CTX_DAG_RUN_ID=manual__2023-09-06T16:53:06.944898+00:00
[2023-09-06, 16:57:33 UTC] {{connectionpool.py:812}} WARNING - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f17b7f0b4c0>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)')': /api/v1/namespaces/mwaa/pods?labelSelector=dag_id%3Dkubernetes_pod_example%2Cexecution_date%3D2023-09-06T165306.9448980000-d1eddeb04%2Ctask_id%3Dpod-task
[2023-09-06, 17:01:55 UTC] {{connectionpool.py:812}} WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f17b7f0b5e0>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)')': /api/v1/namespaces/mwaa/pods?labelSelector=dag_id%3Dkubernetes_pod_example%2Cexecution_date%3D2023-09-06T165306.9448980000-d1eddeb04%2Ctask_id%3Dpod-task
[2023-09-06, 17:06:17 UTC] {{connectionpool.py:812}} WARNING - Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f17b7f0ab60>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)')': /api/v1/namespaces/mwaa/pods?labelSelector=dag_id%3Dkubernetes_pod_example%2Cexecution_date%3D2023-09-06T165306.9448980000-d1eddeb04%2Ctask_id%3Dpod-task
[2023-09-06, 17:10:39 UTC] {{taskinstance.py:1768}} ERROR - Task failed with exception
Traceback (most recent call last):
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
    conn.connect()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connection.py", line 358, in connect
    self.sock = conn = self._new_conn()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connection.py", line 179, in _new_conn
    raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f17b7f0bd90>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py", line 351, in execute
    pod_list = self.client.list_namespaced_pod(self.namespace, label_selector=label_selector)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/api/core_v1_api.py", line 12803, in list_namespaced_pod
    (data) = self.list_namespaced_pod_with_http_info(namespace, **kwargs)  # noqa: E501
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/api/core_v1_api.py", line 12891, in list_namespaced_pod_with_http_info
    return self.api_client.call_api(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/api_client.py", line 340, in call_api
    return self.__call_api(resource_path, method,
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/api_client.py", line 172, in __call_api
    response_data = self.request(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/api_client.py", line 362, in request
    return self.rest_client.GET(url,
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/rest.py", line 237, in GET
    return self.request("GET", url,
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/kubernetes/client/rest.py", line 210, in request
    r = self.pool_manager.request(method, url,
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/request.py", line 74, in request
    return self.request_encode_url(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/request.py", line 96, in request_encode_url
    return self.urlopen(method, url, **extra_kw)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/poolmanager.py", line 376, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    retries = retries.increment(
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com', port=443): Max retries exceeded with url: /api/v1/namespaces/mwaa/pods?labelSelector=dag_id%3Dkubernetes_pod_example%2Cexecution_date%3D2023-09-06T165306.9448980000-d1eddeb04%2Ctask_id%3Dpod-task (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f17b7f0bd90>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)'))
[2023-09-06, 17:10:39 UTC] {{taskinstance.py:1318}} INFO - Marking task as FAILED. dag_id=kubernetes_pod_example, task_id=pod-task, execution_date=20230906T165306, start_date=20230906T165310, end_date=20230906T171039
[2023-09-06, 17:10:39 UTC] {{standard_task_runner.py:100}} ERROR - Failed to execute job 3 for task pod-task (HTTPSConnectionPool(host='b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com', port=443): Max retries exceeded with url: /api/v1/namespaces/mwaa/pods?labelSelector=dag_id%3Dkubernetes_pod_example%2Cexecution_date%3D2023-09-06T165306.9448980000-d1eddeb04%2Ctask_id%3Dpod-task (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f17b7f0bd90>, 'Connection to b80346ff3be18abadbf5fc89bd601cbc.gr7.us-west-2.eks.amazonaws.com timed out. (connect timeout=None)')); 436)
[2023-09-06, 17:10:40 UTC] {{local_task_job.py:208}} INFO - Task exited with return code 1
[2023-09-06, 17:10:40 UTC] {{taskinstance.py:2578}} INFO - 0 downstream tasks scheduled from follow-on schedule check

Terminal Output Screenshot(s)

Additional context
I have a hunch this has to do with the providers list that MWAA uses by default. I would have to adjust the requirements.txt so I could get the default EMR task to run. I can confirm that the Virtual EMR cluster and EKS build. I can connect to the cluster via kubectl from my local (List Name Spaces and Pods). I have tried editing the kube_config file to match my local kube_config created from the awk eks update-kubeconfig command. I also used us-east-2  and us-west-2 on multiple builds when i start the build.sh command.
Here is a list of providers too...

This issues from Kubernets-Sigs repo sees to address this issue: https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/268
From Reading the Known Issue portion of this document I think I will need to add a setup.sh script to the mwaa configuration that runs after the Terraform deployment to configure a new service role that works with mwaa and eks.

@jagpk Have you seen this before?

I found that I need to expand the inbound rules security groups to allow for EKS and MWAA to communicate with each other. I will try and add this as a PR


Cleanup GPU Hist tests.

Remove GPU Hist gradient sampling test. The same properties are tested in the gradient sampler test suite.
Move basic histogram tests into the histogram test suite.
Remove the header inclusion of the updater_gpu_hist.cu in tests.

cc @rongou .


npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>

I had a separate issue and in trying to resolve that I installed visualstudio. Since then gulp-sass has failed to implement.
I have searched for a solution for a week. I have followed the troubleshooting: https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md#windows
Here are my details (taken from the top, running gulp):
$ gulp
fs.js:913
return binding.readdir(pathModule._makeLong(path), options.encoding);
^
Error: ENOENT: no such file or directory, scandir 'C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\vendor'
at Object.fs.readdirSync (fs.js:913:18)
at Object.getInstalledBinaries (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\extensions.js:122:13)
at foundBinariesList (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\errors.js:20:15)
at foundBinaries (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\errors.js:15:5)
at Object.module.exports.missingBinary (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\errors.js:45:5)
at module.exports (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\binding.js:15:30)
at Object. (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev\node_modules\node-sass\lib\index.js:14:35)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev
$ node -v
v7.7.2
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev
$ mkdir \temp1
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev
$ cd \temp1
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ node -p process.env.comspec
C:\Windows\system32\cmd.exe
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ npm -v
4.3.0
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ node -v
v7.7.2
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ node -p process.versions
{ http_parser: '2.7.0',
node: '7.7.2',
v8: '5.5.372.41',
uv: '1.11.0',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '51',
openssl: '1.0.2k',
icu: '58.2',
unicode: '9.0',
cldr: '30.0.3',
tz: '2016j' }
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ node -p process.platforms
undefined
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ node -p process.arch
x64
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ npm cache clean
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ npm install -ddd node-sass > npm.log 2> npm.err
User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ npm ls node-sass
<EMAIL_ADDRESS>C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gulp-dev
--<EMAIL_ADDRESS> -- UNMET DEPENDENCY<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>User@User-PC MINGW64 /c/Bitnami/wampstack-5.6.30-1/apache2/htdocs/20170302bumwp/wp-content/themes/gulp-dev/temp1
$ cd node_modules\node-sass\vendor
bash: cd: node_modulesnode-sassvendor: No such file or directory
Before opening an issue:

Read the common workarounds in the TROUBLESHOOTING.md
Search for duplicate or closed issues
Validate that it runs with both Ruby Sass and LibSass
Prepare a reduced test case for any bugs
Read the contributing guidelines

When reporting an bug, you must provide this information:

NPM version (npm -v):
Node version (node -v):
Node Process (node -p process.versions):
Node Platform (node -p process.platform):
Node architecture (node -p process.arch):
node-sass version (node -p "require('node-sass').info"):
npm node-sass versions (npm ls node-sass):

When encountering a syntax, or compilation issue:

Open an issue on LibSass. You
may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.

Can you take the bash shell out of the equation, you appear to be switching between the console and windows commandlines between your operations.

My apologies. Other factors got in the way of this one. Tried and got this from CMD:
module.js:472
throw err;
^
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302
bumwp\wp-content\themes\gulp-dev\node_modules\gulp-sass\index.js:187:21)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
C:\Bitnami\wampstack-5.6.30-1\apache2\htdocs\20170302bumwp\wp-content\themes\gul
p-dev>cd node-modules
The system cannot find the path specified.


Parameter format date and date-time break generation

The parameter format: date and date-timeannotation for parameter type: string breaks generation:
API definition:
---
swagger: '2.0'
x-api-first-package: controllers
info:
  version: 0.0.0
  title: Simple API Test
paths:
  /{bippy}:
    get:
      parameters:
        - in: path
          name: bippy
          type: string
          format: date
          # path parameter required as a workaround for issue 5
          required: true
      responses:
        200:
          description: bippy response
# model definition required as a workaround for issue 18
definitions:
  bop:
    properties:
      name:
        type: string

Generation:
[play-swagger-test] $ compile
[info] Updating {file:/Users/marco/Code/play-swagger-test/}root...
[info] Resolving jline#jline;2.12.1 ...
[info] Done updating.
[info] Compiling 17 Scala sources and 1 Java source to /Users/marco/Code/play-swagger-test/target/scala-2.11/classes...
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] /Users/marco/Code/play-swagger-test/conf/bippy.yaml:0: not found: type Date
[error] 6 errors found
[error] (compile:compileIncremental) Compilation failed
[error] Total time: 3 s, completed Oct 13, 2015 7:05:05 PM

Should be fixed in #42

In version 0.1.4 compilation fails because of the missing import for every generated component:
not found: type DateMidnight


Error while execuring the certs.sh script in WSL

[Enter feedback here]

Error while execuring the certs.sh script in WSL.
Also I see that [ req_distinguished_name ] has 0.organizationName is this correct ?

openssl.cnf content has follows
[ req ]
default_bits        = 4096
distinguished_name  = req_distinguished_name
string_mask         = utf8only
default_md          = sha512

[ req_distinguished_name ]
countryName                     = IN
stateOrProvinceName             = Karnataka
localityName                    = Bangalore
0.organizationName              = xyz-tech
organizationalUnitName          = dev
commonName                      = SelfSignedTest
emailAddress                    =<EMAIL_ADDRESS>
[ rootCA_ext ]
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints = critical, CA:true
keyUsage = critical, digitalSignature, cRLSign, keyCertSign

[ interCA_ext ]
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints = critical, CA:true, pathlen:1
keyUsage = critical, digitalSignature, cRLSign, keyCertSign

[ server_ext ]
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer
basicConstraints = critical, CA:false
keyUsage = critical, digitalSignature
extendedKeyUsage = serverAuth

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

ID: ef9f0dbe-23c4-5c17-56fd-ee40ff803cdd
Version Independent ID: d7ec7ba5-2933-8d42-9891-8f78aa2d73b9
Content: Azure Firewall Premium Preview certificates
Content Source: articles/firewall/premium-certificates.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

@madhub, Thanks for reaching out. We will investigate and update this thread.


fix: Network dropdown on explorer doesn't change(#6872)

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #6872

Did your issue had any of the "$" label on it?
my DOT address: Payout
Community participation

[x] Are you at KodaDot Discord?

Copilot Summary

🤖 Generated by Copilot at fb340ce
Fixed a bug in ChainDropdown.vue that caused an error when the user had no account. Added a check for accountId before getting the chainName.

🤖 Generated by Copilot at fb340ce

chainName depends
on accountId defined
fall leaves avoid null

pay 20 usd

pay 20 usd

hi, yangwao. There was something wrong in transaction. It was failed.

pay 20 usd
yeah we run out of balance:)

😍 Perfect, I’ve sent the payout
💵 $20 @ 4.46 USD/DOT ~ 4.484 $DOT
🧗 12jXHf7yYF4wTRjDPbwFB24V1nVRPRkuU2S8Ke5ZWTfvyBGW
🔗 0xec11fa0e494ecadeb86efbc23c8d3761e23736a699d058e69945e796560a0b22
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Incorrect error message when Dataset.from_sql fails and sqlalchemy not installed

Describe the bug
When calling Dataset.from_sql (in my case, with sqlite3), it fails with a message ValueError: Please pass `features` or at least one example when writing data when I don't have sqlalchemy installed.
Steps to reproduce the bug
Make a new sqlite db with sqlite3 and pandas from a remote URL.
import sqlite3
import pandas as pd
from datasets import Dataset

conn = sqlite3.connect('us_covid_data.db')
df = pd.read_csv('https://raw.githubusercontent.com/nytimes/covid-19-data/master/us-states.csv')
df.to_sql('states', conn, if_exists='replace')

Then if you try to query this DB like this:
ds = Dataset.from_sql('''SELECT * from states WHERE state=="New York";''', "sqlite:///us_covid_data.db")

You run into the error I described above:
ValueError: Please pass `features` or at least one example when writing data
However, if you try to pass features, as the error suggests, then you get an error that tells you the underlying problem...
from datasets import Dataset, Features, Value

features = Features({
    'date': Value('date32'),
    'label': Value('string'),
    'fips': Value('int32'),
    'cases': Value('int32'),
    'deaths': Value('int32')
})
ds = Dataset.from_sql(
    '''SELECT * from states WHERE state=="New York";''',
    "sqlite:///us_covid_data.db",
    features=features
)

Which results in the actual underlying error: ImportError: Using URI string without sqlalchemy installed.
Expected behavior
Instead of ValueError about needing to pass features, we should provide the actual underlying error about not having SQLAlchemy installed when it isn't found in the environment.
Environment info

datasets version: 2.6.1
Platform: macOS-10.16-x86_64-i386-64bit
Python version: 3.8.10
PyArrow version: 10.0.0
Pandas version: 1.2.5

Hi! The first Dataset.from_sql call also outputs the "ImportError: Using URI string without sqlalchemy installed."  after which the ValueError is printed. I agree that this behavior makes it easy to miss the original error.
I think we can improve this by not throwing the writer's ValueError if the error from a dataset script is already being handled to make debugging easier. @lhoestq @albertvillanova wdyt?

Yup ! Alternatively the error can be raised in sql.py before generating the examples ? In _info for example

yea @lhoestq that would probably be good. The 2nd error is useless if the 1st error is the real reason it failed.


gtk:x64-windows build failure

Host Environment

OS: Windows 10 64x
Compiler: Microsoft Visual Studio Professional 2019 Version 16.5.4

To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe install gtk:x64-windows
Failure logs
stdout-x64-windows:
Using cached C:/Tools/vcpkg/downloads/anholt-libepoxy-1.5.3.tar.gz
 -- Extracting source C:/Tools/vcpkg/downloads/anholt-libepoxy-1.5.3.tar.gz
 -- Using source at C:/Tools/vcpkg/buildtrees/libepoxy/src/1.5.3-d7b9d32fcb
 -- Acquiring MSYS Packages...
 CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: C:/Tools/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile  --norc -c "pacman -Sy --noconfirm --needed pkg-config"
    Working Directory: C:/Tools/vcpkg/downloads/tools/msys2
    Error code: 255
    See logs for more information:
      C:\Tools\vcpkg\buildtrees\libepoxy\msys-pacman-x64-windows-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_acquire_msys.cmake:108 (vcpkg_execute_required_process)
  scripts/cmake/vcpkg_configure_meson.cmake:106 (vcpkg_acquire_msys)
  ports/libepoxy/portfile.cmake:12 (vcpkg_configure_meson)
  scripts/ports.cmake:90 (include)

msys-pacman-x64-windows-err:
error: failed to initialize alpm library (could not find or read directory: /var/lib/pacman/)
Additional context
VS language packs English is installed.
vcpkg new build.

Error code: 255
See logs for more information:
C:\Tools\vcpkg\buildtrees\libepoxy\msys-pacman-x64-windows-err.log

It looks like the msys2/mingw tool is corrupt or was unable to download all the appropriate files.
My suggestion would be:

to make sure full access rights are given to the userid used to access the C:\Tools\vcpkg folder/files and all sub-folders/files
to rename the msys2 folder found in C:\Tools\vcpkg\downloads\tools\msys2 to msys2.old and try again
hopefully vcpkg will download/recreate the msys2/mingw tools
when all works then delete/remove C:\Tools\vcpkg\downloads\tools\msys2.old folder.

Hello, Timautry,
your suggestion was successful.
Thank you and stay healthy.
-- SZ
Installing package libepoxy[core]:x64-windows... done
Installing package gtk[core]:x64-windows... done


IP address allocations not released on failure while migrating networks of an instance_group with multiple instances

Describe the bug
When updating a deployment to move an instance group to a different network, if the instance_group has multiple instances, then IP address allocations are not correctly released if the canary fails. We observed that the canary instance's allocation is released, but the allocations made for the other instances are not.
To Reproduce
Steps to reproduce the behavior (example):

Deploy a bosh director on GCP, although we suspect issue is IaaS agnostic with multiple networks
Upload ubuntu-xenial/621.99 and a cloud config defining the multiple networks
Deploy an instance_group with at least 2 instances to the first network, we used the zookeeper-release
Modify the release to have a failing pre-start script
Redeploy the modified release, with the instance_group's network set to the second network.
Verify this fails.
Run bosh restart on the deployment, this brings things back to a green state, where the non-modified release is deployed on the first network again.
Redeploy the non-modified release to the second network, this should succeed.
Note that the canary will have the first IP from the dynamic range, but the additional instances will have skipped IP addresses. In a sufficiently large deployment, this can cause exhaustion of the available IP addresses.

We can additionally verify that there are extra IP address allocations for the instance_groups that aren't being used. See our logs below.
Expected behavior
Unused IP address allocations should not remain. Whether this is by steps 8/9 reconsuming the previously allocated IP addresses, or some other cleanup mechanism.
Logs
When we log into the bosh console, after step 9, we saw something like this:
irb(main):003:0> puts Bosh::Director::Models::IpAddress.map(&:info).grep(/zookeeper-bad/);nil
zookeeper-bad.zookeeper/1 - default2 - <IP_ADDRESS> (dynamic)    <--- orphaned
zookeeper-bad.zookeeper/2 - default2 - <IP_ADDRESS> (dynamic)   <--- orphaned
zookeeper-bad.zookeeper/0 - default2 - <IP_ADDRESS> (dynamic)   <--- canary
zookeeper-bad.zookeeper/1 - default2 - <IP_ADDRESS> (dynamic)    <--- matches `bosh vms`
zookeeper-bad.zookeeper/2 - default2 - <IP_ADDRESS> (dynamic)    <--- matches `bosh vms`

Versions (please complete the following information):

Infrastructure: GCP
BOSH version 271.2.0
BOSH CLI version [e.g. 5.1.1]
Stemcell version ubuntu-xenial/621.99

Fixed with the above commit.


Api mode to full fledged Rails

The readme does a good job at explaining how to convert an existing app to an api only app.
I recently had to do the opposite in a project I'm working on. We started with the api mode and wanted to serve a couple of simple views and forms in the app. So, we did the opposite of the readme and it worked as expected.
Could we add a small section to the readme, similar to "For already existing apps", that details the steps of the conversion? If so, do you mind if I open a PR for it?

closing this. :)


Delegate responsibility to engine to create grid data for simulation

:rocket:

[ ] Is your feature request essential for your project?

Describe the workflow you want to enable
Move the writing of the transformed grid into the binary file read by the engine into the wrapper. Different engine need different data to run. To illustrate, REISE.jl can now handle demand flexibility while MATPOWER can't. Keeping the current MAT-file structure to run CEM scenarios with PyPSA in the future will also  be extremely challenging.
Describe your proposed implementation, if applicable

Pickle the transformed grid in the SimulationInput class.
Send the binary file to the tmp folder on the server/container along with the profiles.
Give to each wrapper the responsibility to load the transformed grid enclosed in the pickle file and operate on the object to create the adequate input for the engine. The current export_case_mat function located in the powersimdata.input.exporter.export_to_reise module can be moved in the REISE and REISE.jl repositories. The extra-column giving the demand flexibility located in the bus data frame of a Grid object can be added to the bus table of the case.mat file for REISE.jl.
Convert the grid.mat into a pickle file in each wrapper after a run (applicable to REISE and REISE.jl engine). Classes and functions enclosed in the powersimdata.input.converter.reise_to_grid module can be moved in each wrapper.
Fetch the id_grid.pkl in theReady class via the get_grid method.

The wrappers will likely depend on PowerSimData. For example the class responsible for converting the grid.mat file created after the simulation (REISEConverter) inherits from the AbstractGrid. We will have to add PowerSimData as a dependency in the wrappers.
Describe alternatives you've considered, if relevant
We spent a considerable amount of time trying to figure out a way to use the same input files for different engines and there is no easy solution. Moving away from MAT-file is also very appealing.
Additional context
This is a multi-repository feature. We will also need to convert all existing scenario's grid.mat file on the server/blob. Note that this can easily be done with the current version of the code by:

Looping over the scenario list, using the current get_grid method;
Dumping the Grid object in a pickle file;
Uploading the files on the server/blob

Addressed in #701


Allow specifying functions for Petri Net place and transition names

I wanted to inspect the Petri Net that is generated by Baker, but due the generated place and transition names are so long that the graph is not readable.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d193e29). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #458   +/-   ##
=========================================
  Coverage          ?   79.13%
=========================================
  Files             ?      110
  Lines             ?     3418
  Branches          ?       83
=========================================
  Hits              ?     2705
  Misses            ?      713
  Partials          ?        0

Impacted Files
Coverage Δ

...main/scala/com/ing/baker/il/RecipeVisualizer.scala
91.93% <100.00%> (ø)

...com/ing/baker/runtime/serialization/ProtoMap.scala
95.83% <0.00%> (ø)

...ing/baker/il/petrinet/IntermediateTransition.scala
100.00% <0.00%> (ø)

...la/com/ing/baker/baas/state/ServiceDiscovery.scala
86.11% <0.00%> (ø)

...ain/scala/com/ing/baker/il/RecipeValidations.scala
97.29% <0.00%> (ø)

...or/process_index/SensoryEventResponseHandler.scala
85.05% <0.00%> (ø)

.../akka/actor/process_instance/ProcessInstance.scala
86.48% <0.00%> (ø)

.../failurestrategy/RetryWithIncrementalBackoff.scala
100.00% <0.00%> (ø)

...ker/baas/interaction/RemoteInteractionClient.scala
100.00% <0.00%> (ø)

...a/com/ing/baker/types/modules/JodaTimeModule.scala
71.42% <0.00%> (ø)

... and 101 more

Continue to review full report at Codecov.

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

Thanks!


errors during app startup

App starts with the errors, but these errors appear :
npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>ADF 1.1. standard default app generated by the hipster yeoman tool : yo ng2-alfresco-app
Are these expected or not ?
Please advise,
Thanks.

Closing as a duplicate of this: https://github.com/Alfresco/alfresco-ng2-components/issues/1397

Sorry, I forgot to add: The errors can safely be ignored

@ohej Hi Ole, there is an additional error in my case that from the duplicate. The zone.js dependency.
Can that one be ignored as well ?

Hi @romainguinot Yes you can it is a install warning and is due to the verbose npm report.


Add Note to Install Locally

What kind of changes does this PR include?

New or updated content

Description

Closes #3045
What does this PR change? I added a note to the getting started page and manual install guide warning users to not install Astro globally.

Thanks, @sarah11918! I think I accepted your changes correctly

Everything looks great to me! Once the tests pass, we're good to go!  :partying_face:


Jimin/realtime config

Making this change to get Trouter and Trouter registration configs by calling chat gateway.
Test:

Use EU resource:
Trouter URL: https://go-eu.trouter.teams.microsoft.com/v3/c
Registration: https://teams.microsoft.com/registrar/prod/v3/registrations
Use non-EU resource
Trouter URL: https://go.trouter.teams.microsoft.com/v3
Registration: https://teams.microsoft.com/registrar/prod/v3/registrations
GCC resource
Trouter URL: https://go.trouter.gcc.teams.microsoft.com:443/v3/h
Registrar URL: https://teams.microsoft.com/registrar/prod/v3/registrations
GCCH
Trouter URL: https://go.trouter.gov.teams.microsoft.us:443/v3/h
registrarURL: https://registrar.gov.teams.microsoft.us/v3/registrations

/check-enforcer evaluate

/azp run android - communications - ci

/azp run android - communication - ci


Bad URL / target on docker backup

When executing the docker backup command as shown in README the following occurs:
INFO[0010] retrying...
INFO[0016] retrying...
ERRO[0019] Failed to backup volume filestore: failed to backup volume: failed to retrieve last backup info: after 3 attempts, last error: failed to retrieve full output from collection-status after 3 attempts

DEBU[0007]  Bad URL '/38f4b4ac2753/filestore'.
 Examples of URL strings are "scp://user@host.net:1234/path" and
 "file:///usr/local".  See the man page for more information.

The command from README has been copy pasted with url key and secret key changed
It seems that for some reason the target is not being propagated from the environment

@PCatinean could you provide us the whole command you run?

@mcanevet i'm sorry for the noise, I deleted all volumes copy pasted the string again and it started working out of the blue. I only then noticed an environment variable was misnamed :(


add keyword marker token filter docs #8065

Description
add keyword marker token filter docs
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/8065
Version
all
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@udabhas @varun-lodaya Please provide tech review approval to move this PR forward in the documentation process. Please review this week or provide a peer who can review it. Thank you.

Closing in favor of #8134


Prevent selection of diff line numbers

Same as https://github.com/go-gitea/gitea/pull/1860, but for diffs this time.

LGTM

LGTM


tests: spinlock: Clear test globals before each test

Clear test global variables before each test execution.

@finikorg if this is fixing one of the Up2 bugs, maybe add a “Fixes” entry?

@finikorg if this is fixing one of the Up2 bugs, maybe add a “Fixes” entry?

Cannot verify this for up2 board.

@finikorg if this is fixing one of the Up2 bugs, maybe add a “Fixes” entry?

Cannot verify this for up2 board.

It was verified here: https://github.com/zephyrproject-rtos/zephyr/issues/60330#issuecomment-1779279465
That said, the issue was already manually closed, so doesn't really make a difference..


Feat Multiplier does not apply to Animal Companions

It did work before 1.2.10

There was a fairly complex work around I had in during beta but it was breaking other stuff so I reset and started over with a simple patch and now will try to fix this stuff in other ways.


Code emphasis color in dark modes is not set - poor contrast.

I love the theme and am considering switching to it for a few of my projects!
One minor issue - it looks like the background color for emphasized code (HTML class hll) is not being overridden for dark modes. This results in some poor contrast.
For example:

Compared to light mode:

@amykyta3 Good catch. I've created a PR (https://github.com/piccolo-orm/piccolo_theme/pull/49) which makes the contract more subtle. What do you think about that?

Looks great!

@amykyta3 Cool - I've released it (piccolo_theme==0.15.0).


feat: Implement ScreenEvent and MPEvent classes

Summary
Implement MPEvent and ScreenEvent, replace usage in logEvent() and logScreenEvent().
I do think there is a case that using "CusomtEvent" would make more sense, but in terms of consistency with the native SDKs and all the other plugin/wrapper SDKS, "MPEvent" is definitely the current norm.
I also did not try to do any sort of inheritance. Even though it's true that "ScreenEvent is an MPEvent", we're in the plugin layer so we're not set up to accept ScreenEvents in logEvent(MPEvent), and saving a few lines of code isn't worth the additional complexity in accounting for that

Actually can you update the docs to also adhere to this, in this PR?

Looks good but I agree that we should update the docs too


Rename behavioral model folder/files to DASH

Related information
Item owned by NVidia, adding Marian
Scope - P4 DASH pipeline. Deprecate name "sirius" in P4 source files and change it to "dash"

Fixed by https://github.com/Azure/DASH/pull/128


Force all resource groups within single collection via option

Hi there,
This is a backward compatible change that adds --single-collection option to the CLI. This new option will force all resource groups to be created as Folder within the same Postman collection.
FYI @bomiteva

Hi, thanks for your contribution and sorry for this slow reply.
I think this is a great idea, but this breaks the app:
$ apiary2postman.py --only-collection api some_api
Traceback (most recent call last):
  File "./apiary2postman.py", line 123, in <module>
    main()
  File "./apiary2postman.py", line 120, in main
    write(input, output, args.only_collection, args.pretty, args.single_collection)
  File "/home/thecopy/dev/apiary2postman/apiary2postman/converter.py", line 83, in write
    result_out = _buildCollectionResponse(json_obj, single_collection)
  File "/home/thecopy/dev/apiary2postman/apiary2postman/converter.py", line 14, in _buildCollectionResponse
    single_collection)
  File "/home/thecopy/dev/apiary2postman/apiary2postman/converter.py", line 125, in parseResourceGroups
    for resourceGroup in apiary['resourceGroups']:
TypeError: list indices must be integers, not str

Any news on this?
Will it get merged?

Hey Erik, I have a very busy week, but happy to take a look next week if
that is OK.
Thanks,
E.
On 26 September 2016 at 23:16, thim81<EMAIL_ADDRESS>wrote:

Any news on this?
Will it get merged?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thecopy/apiary2postman/pull/15#issuecomment-249684573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5Aq-FtTFTsVkqz0cpr6H9kwcCW24auks5quCg5gaJpZM4GhBu1
.

I just applied the PR to the latest version apiary2postman and it worked perfectly.
No error or warnings PLUS the output was one single collection which imported without a problem, keeping my postman a very clean workplace.

@thim81 Yes, then added functionality works but it breaks already existing functionality.
@eabadjiev
Change the first argument for the call to parseResourceGroups on line 10 to apiary from apiary['resourceGroups']

@eabadjiev this is a 1 minute fix, if you could do it i will merge it asap


Isolate specific job configurations and framework configurations

Improve the design of the harness framework so that:

the framework will install/download its default comparator, not the specific job. The job should not have to change the comparator configurations (e.g. path to comparator script) unless it really needs to.
a specific job will be able to define its converter class(es) and configurations by extending the base classes provided by the framework.

On the second point, the framework currently provides the converter classes for ProvPy, ProvToolbox, ProvStore, and ProvTranslator. I think those should be moved to the corresponding job repos. By so doing, we will also provide examples for converters developed not by Southampton team how to take advantage of the interop test framework without the need to modify the test framework's code.

I have created package branches of:

interop-test-harness
provpy-interop-job
provstore-interop-job
provtoolbox-interop-job
provtranslator-interop-job

The contents of the branches, and how these differ from the original interoperability test harness, are as follows.
Each branch contains a Python package that can be installed using python setup.py install. The respective packages are:
prov_interop
prov_interop_provpy
prov_interop_provstore
prov_interop_provtoolbox
prov_interop_provtranslator

Default test harness configuration files are now located alongside the Python test harness files that read them e.g.

prov_interop/interop_tests: harness.py, harness.yaml
prov_interop_provpy/interop_tests: test_provpy.py, provpy.yaml
prov_interop_provstore/interop_tests: test_provstore.py, provstore.yaml
prov_interop_provtoolbox/interop_tests: test_provtoolbox, provtoolbox.yaml
prov_interop_provtranslator/interop_tests: test_provtranslator, provtranslator.yaml

The Python files above look for these files in the same directory as the Python file itself. If a developer wants to use their own configuration file, they can either edit the file, or point to the location of their own one using an environment variable (this latter aspect was already supported in the original design).
When python setup.py install is run, then these configuration files are copied too. So, for example, a developer can use the default configurations without having to set up any local copies of the configuration files:

prov_interop/interop_tests/harness.yaml specifies a default location for the test cases directory as testcases i.e. a directory in the same directory from which the tests are run.
prov_interop/interop_tests/harness.yaml assumes that ProvToolbox's provconvert is available on the PATH.
prov_interop_provpy/interop_tests/provpy.yaml assumes that ProvPy's prov-convert is available on the PATH.
prov_interop_provtoolbox/interop_tests/provtoolbox.yaml assumes that ProvToolbox's provconvert is available on the PATH.

For prov_interop_provstore tests there is a need for an API key for which, naturally, a default value that works cannot be provided. This test class will use any value in prov_interop_provstore/interop_tests/provstore.yaml unless a PROVSTORE_API_KEY environment variable is defined, in which case that is assumed to hold the API key value. This, again, saves the need to create a local copy of the configuration file.
prov_interop/interop_tests/test_converter.py had a function:
def configure(self, config_key, env_var, default_file_name)

which loaded in a converter-specific test harness configuration file and used it to configure a converter's test class. This has been renamed to:
def get_configuration(self, config_key, env_var, default_file_name)

which returns the configuration. A new function allows sub-classes to configure the converter-specific test class using this configuration.
def configure(config)

This has been introduced to allow developers to write their configuration in-code and configure their test class that way also without needing to use a configuration file at all prov_interop_provpy/interop_tests/test_provpy_hardcoded.py provides an example of an interop test class with hard-coded configuration.
interop-test-harness has scripts/install-prov-interop-comparator, a shell script that uses wget and unzip to download and install ProvToolbox from a ZIP file and update the PATH. This needs to be sourced e.g.
$ source scripts/install-prov-interop-comparator.sh

I'm not sure how ProvToolbox could be installed directly from within the test framework (i.e. within Python) as, while it could be downloaded and unpackaged, the challenge is updating PATH.
Returning to your requests:

the framework will install/download its default comparator, not the specific job.

Not done, beyond provision of a shell script, see above.

The job should not have to change the comparator configurations (e.g. path to comparator script) unless it really needs to.

Done

a specific job will be able to define its converter class(es) and configurations by extending the base classes provided by the framework.

Done

the framework currently provides the converter classes for ProvPy, ProvToolbox, ProvStore, and ProvTranslator. I think those should be moved to the corresponding job repos.

Done

In the above, the repositories with the converter-specific extensions serve two roles:

Repository for converter-specific extensions plus unit tests.
Test runner for interop tests for the associated converter (as embodied in the .travis.yml scripts).

A next step would be to migrate the .travis.yml content that runs the interop tests to yours' and Lucs' ProvPy and ProvToolbox .travis.yml jobs. These would then be responsible for the following:

Clone testcases.
Clone interop-test-harness and install package and, for ProvPy, install ProvToolbox binary.
Clone provpy_interop_job/provtoolbox_interop_job and install converter-specific package.
Run interop tests.

This would mean that the responsibility for running the interop tests falls to your ProvPy/ProvToolbox repositories (after unit tests have all succeeded, for example), and would be triggered every time ProvPy/ProvToolbox commits are done, which would be more in the spirit of Travis.


About MOS evaluation in the paper

Hi!
Thank you for your excellent work!
I have a question about the MOS evaluation in the paper.
In the paper, there are 95% confidence interval in the MOS assessment of roughly 2, which I think is quite large.
The MOS in the original BigVGAN paper is roughly 0.1.
This paper does not mention this point, but if there is any reason, could you please let me know?
Thanks.

Thank you for having an interest in our work! That's a good question.
Differences in generation quality between different vocoders (including recorded ground truth) are small now because BigVGAN/SAN can synthesize high-fidelity audio samples. And, this makes differences in recording quality between LibriTTS recorded samples relatively larger. In previous studies, raters should've had a strong tendency to give high scores to ground-truth samples and low scores to synthesized ones. In our test, raters might have struggled to find differences between provided samples and then sometimes gave low scores to ground-truth samples.
According to the paper https://arxiv.org/abs/2305.10608, listeners tend to use the entire range from 1 to 5 even when they are provided with only high-quality samples in a listening test. Our observation matches the phenomenon explained in the paper.
This is what happened. Does it make sense?

Thank you for your fast reply!
Yes, I think what you say is one of the causes, too.
In that case, I think the MOS for the test-other dataset should be generally lower and the MOS for the test-clean dataset should be generally higher.
How was this point?

(I wrongly replied with my private account yesterday. Sorry for the caused confusion.)
That's a good point. Unfortunately, I can't trace numbers regarding the test-clean/test-other sets. Instead, I've confirmed that MOS scores for each speech sample are differently distributed. MOS scores for one speech sample are

Ground truth: 4.62 ± 0.95
BigVGAN (our reprodcution): 3.75 ± 1.30
BigVSAN: 4.38 ± 1.36
BigVSAN (w/ snakebeta): 4.38 ± 0.95

, ane those for another speech sample are

Ground truth: 2.62 ± 1.94
BigVGAN (our reprodcution): 2.50 ± 2.40
BigVSAN: 2.50 ± 1.96
BigVSAN (w/ snakebeta): 2.75 ± 2.14

. The former one should be a clean speech sample, and the latter one should be a noisy sample.
Thank you for your insightful comment.

Thanks for sharing your results :)
I see when clean and noisy speech is used in the same MOS experiment, it may not be possible to properly evaluate how close it is to natural speech.
This finding will be helpful in designing future experiments.
Thank you very much for the useful information and constructive discussion!

Thanks for nice work :)
I also have the same question for the CI of MOS.
In my opinion, the authors may compute the confidence interval for each listener. However, in general, the confidence interval is computed for total samples the listener rated, so I think the high CI is reported in this paper.
Thank you again for very nice work!

@sh-lee-prml
Thank you very much for your comment!
We asked 8 listeners to rate 10 samples for each model (we have 4 models to be evaluated, so each listener rated 40 samples in total). Then, we got 80 ratings per model. We calculated averages and CIs using the 80 scores.

Thanks for details.
Then, I think it's right :)
and there is a easy MOS prediction model (https://github.com/tarepan/SpeechMOS).
It would be better if you increase the samples for MOS evaluation by using simple MOS prediction model!
Thank you 👍

@sh-lee-prml
I appreciate your helpful comment. Thank you!


FileMonitor Controller, Interceptor & Interface projects

the three projects not included in the solution but in the solution directory are the question here.
I have compiled them but they don't seem to work?  no errors either.  any thoughts on what is missing to make them work?

@asulwer thanks for pointing this out. I can't even remember these projects, so I'll check it out and either remove them completely or see if they are useful to include as examples.

sorry to post a 'bug' report for just this.

@asulver all good, could be confusing for some


Updated tests for new api version.

Updated policy tests for enforcementMode and data plane modes.

Looks like I need to sync again with master.

"Entries": [

looks like this is not in the right sessionRecords folder

Refers to: sdk/resources/Microsoft.Azure.Management.Resource/tests/SessionRecords/Policy.Tests.LivePolicyTests/CanCrudDataPlanePolicyDefinition.json:2 in abfbd6f. [](commit_id = abfbd6fedcba3275f16c1870b009f249839e79bc, deletion_comment = False)

I believe the csproj and maybe AssemblyInfo need to have their versions updated (may be wrong, been a long time)

.props as well acc

I believe the csproj and maybe AssemblyInfo need to have their versions updated (may be wrong, been a long time)

.props as well according to this:  https://github.com/Azure/azure-sdk-for-net/blob/master/Documentation/code-generation-instructions.md

LGTM.  Please get an ack from Tian Ouyang and Gaurav Bhatnagar that you are pushing a new Management.Resource SDK version before completing this PR.

swagger PR is here - https://github.com/Azure/azure-rest-api-specs/pull/6998

@sandipsh Thanks for the update, thought the eng\mgmt\mgmtmetadata\<rpName>.txt file still needs to be added to the PR. See https://github.com/Azure/adx-documentation-pr/blob/master/engineering/adx_netsdk_process.md#sdk-generation-from-updated-spec

Looks good to me.


Great work - a quick explernation of notebook settings

First of all, much appretiated work on this notebook and thanks for sharing. Seems that each and every day something changes and requires attention in the Stable Diffucion Colab universe... Steep learning curve :D
Argument descriptions
model_init
What does this parameter do, or what can I do with it ?
SDZ_Args
What is this for, what can I use this one for ?
Argument bugs
models_dir
Great quick install if having the SD install outside drive, however some models does not work from this folder in case
you are not aware. Whem adding the model below the setup creates a new model inside the SD setup with subfolders
and crashes due to memory overload.
Placing the models inside the stable_diffusion folder as you normally would do works fine so no problems there.
Example: models_dir = '/content/drive/MyDrive/models'
%cd /content/drive/MyDrive/models !wget -O HassanBlend1.4-Pruned.ckpt https://huggingface.co/hassanblend/hassanblend1.4/resolve/main/HassanBlend1.4-Pruned.ckpt !wget -O HassanBlend1.4-Pruned.vae.pt https://huggingface.co/stabilityai/sd-vae-ft-mse-original/resolve/main/vae-ft-mse-840000-ema-pruned.ckpt
Final wish
Finally, I have yet to try our the dreambooth extension in any colab as I cannot load a model - seems that creating the actual dreambooth model requires more memory than the colab notebook has - also I do not have a modern GPU locally either so I cannot create the model there either.
How on earth do I start up dreambooth with a "clean" model, I have looked for a Dreambooth SD1.5 model to download however havnt managed to find one. Would be a great addon to have this button I would think:
Download_dreambooth_base_model

You should add this one aswell, a new control


creating a codespace based on a repo from this template didn't do the recursive checkout

I had to
cd PETSIRD
git submodule update --init

@johnstairs is this something you know how to fix?

https://github.com/microsoft/vscode-remote-release/issues/5569 and others suggest (in a more complicated use-case)  to add it ti to the initializeCommand.
@casperdcl, any recommendation?

Closed by #5


fix(doc-tools): edit link should open a new tab

Summary

copilot:summary
Details

copilot:walkthrough
Related Issue

Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

delete your copliot code in summary


Transition using js hooks always run the initial render

Version
2.5.16
Reproduction link
https://jsfiddle.net/p1dthw6z/
Steps to reproduce
In the demo link, toggle checkbox 'odd'.
What is expected?
When rows appeared, both inner element transition using CSS (fade) and transition using hooks (slide) should not do initial render.
What is actually happening?
Transition using CSS do not run the initial render, as expected.
But the transition using hooks run the initial render, as if I have used <transition appear>, which I didn't.

I don't know if it is the intended behavior. If it is, I would like to know how to avoid the initial render in the hooked transition.

Hi, I looked at your JSFiddle, and toggling the checkbox 'odd' collapses the a2 and a4 rows. Are you referring to the initial slide transition that occurs when odd is unchecked?

@jwanggggg yes


Support connecting with ipv6 hostname

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[WFLY-16575] Upgrade WildFly Core to 19.0.0.Beta13

Jira issue:
https://issues.redhat.com/browse/WFLY-16575

Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/19.0.0.Beta13
Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/19.0.0.Beta12...19.0.0.Beta13

        Bug

[WFCORE-1960] -         Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

[WFCORE-5527] -         Undeploying doesn't delete non-empty content folder

[WFCORE-5927] -         Misleading message for embedded server configuration file

[WFCORE-5949] -         Adding meta-data to json-logger via YamlConfigurationExtension results in ClassCastException

[WFCORE-5953] -         List attribute are not properly updated with the YAML Extension

[WFCORE-5954] -         Yaml Extension doesn't add empty resources

        Task

[WFCORE-5781] -         Remove log4j 1.x module and support

[WFCORE-5950] -         Use recommended client-side JPMS settings in the wildfly-core pom

[WFCORE-5956] -         Align Jakarta Authorization and Authentication versions on wildfly-core-jakartaee with the ones used on WildFly Preview

        Component Upgrade

[WFCORE-5948] -         Upgrade JGit to <IP_ADDRESS>206071550-r

[WFCORE-5951] -         Upgrade JBoss Marshalling to 2.1.0.Final

[WFCORE-5959] -         Upgrade Jandex to 2.4.3.Final

[WFCORE-5961] -         Upgrade netty-codec-http from 4.1.71.Final to 4.1.77.Final in /testbom

I think this is ready to go, SingletonDeploymentJBossAllTestCase.test has failed with similar trace on other PRs, so it is unrelated to the WildFly Core upgrade


Tuning Up The Mod

Hello there, you'll see.. I use this and the "Grunt Mode 1" mods in order to play some private PvE matches.. what you guys have made here is the closest thing we have to a Bots mode on Titanfall, and I mean a real Bots mode.. with Pilots, Titans and everything..
What I wanted to ask ya is.. which file contains the parameter that determines when the Pilots, Reapers, Titans and etc start spawing on the match? I wanted to change the parameter so all of those NPC's showed up quicker.. I managed to made that change on the DBmaoha mod easily but.. couldnt find the option in your mod.
I like the class system you made, btw.. Also, I wanted to know.. is there a way to use that mod of yours on any other game mode besides of Attrition? Thanks..

Sorry for the late repsonse, the values are stored near the top of the
gamemode_aitdm file, it will be moved to be a mod.json convar soon
On Sat, Jul 8, 2023 at 18:17 sbmmsux @.***> wrote:

Hello there, you'll see.. I use this and the "Grunt Mode 1" mods in order
to play some private PvE matches.. what you guys have made here is the
closest thing we have to a Bots mode on Titanfall, and I mean a real Bots
mode.. with Pilots, Titans and everything..
What I wanted to ask ya is.. which file contains the parameter that
determines when the Pilots, Reapers, Titans and etc start spawing on the
match? I wanted to change the parameter so all of those NPC's showed up
quicker.. I managed to made that change on the DBmaoha mod easily but..
couldnt find the option in you mod.
I like the class system you made, btw.. Also, I wanted to know.. is there
a way to use that mod of yours on any other game mode besides of Attrition?
Thanks..
—
Reply to this email directly, view it on GitHub
https://github.com/EnderBoy9217/Grunt-Mode/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DZTMRLPC3CAVHMYYJZHZLXPHL6ZANCNFSM6AAAAAA2DC2DG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Nah, it's cool.. aint worry.. thx for the info.. Btw.. is there a way to implement ur mod on other game modes besides Attrition? Idk, maybe in Frontier War or some, just curious..

I have been thinking about adding it to amped hard points, I’ll likely do
that when the mod if “finished” so I don’t have to constantly repeat changes
On Sun, Jul 9, 2023 at 20:58 sbmmsux @.***> wrote:

Nah, it's cool.. aint worry.. thx for the info.. Btw.. is there a way to
implement ur mod on other game modes besides Attrition? Idk, maybe in
Frontier War or some, just curious..
—
Reply to this email directly, view it on GitHub
https://github.com/EnderBoy9217/Grunt-Mode/issues/13#issuecomment-1627896650,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DZTMTRCHTJEYS5YJCZN73XPNHSPANCNFSM6AAAAAA2DC2DG4
.
You are receiving this because you commented.Message ID:
@.***>

nice.. but.. how's that "hardpoint" mode in titanfall? i know it only because of cod jejeje.. and pretty sure it's not the same.. i mean, this hardpoint from titanfall would be pilots only, right?

Amped hard point is a gamemode on vanilla Titanfall that surprisingly few
people play on Northstar.
Essentially it’s like COD domination, but after you capture a hard point,
you can stay to defend it to get double the points from that hard point.
On Mon, Jul 10, 2023 at 20:42 sbmmsux @.***> wrote:

nice.. but.. how's that "hardpoint" mode in titanfall? i know it only
because of cod jejeje.. and pretty sure it's not the same.. i mean, this
hardpoint from titanfall would be pilots only, right?
—
Reply to this email directly, view it on GitHub
https://github.com/EnderBoy9217/Grunt-Mode/issues/13#issuecomment-1629925572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DZTMSCHLUBNZN6HDIL5G3XPSOPJANCNFSM6AAAAAA2DC2DG4
.
You are receiving this because you commented.Message ID:
@.***>

The gamemode disables the titan/boost bar entirely, if you still want to
have titans, I can send you a version with edits that allow it.
However, grunt classes would also be able to spawn titans, and entering a
titan with specific classes such as spectres will likely lead to a crash.
On Tue, Jul 11, 2023 at 04:00 sbmmsux @.***> wrote:

another question.. is there a possibility to make the pilot class in ur
mod can request titans? u know, the energy bar on bottom left of the screen
indicating if u can request a titan or not.. i played a match recently and
when i could respawn as a pilot.. didnt see that bar..
—
Reply to this email directly, view it on GitHub
https://github.com/EnderBoy9217/Grunt-Mode/issues/13#issuecomment-1630341148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DZTMV3XUVLKREPIUZLLSDXPUB3NANCNFSM6AAAAAA2DC2DG4
.
You are receiving this because you commented.Message ID:
@.***>

ouch! yeah.. we better leave it as it is jejeje.. thanks for ur response.. looking forward to play that "hardpoint" mode too.. i mean, attrition is cool but.. sometimes u just wanna play something else..


Finish implementing graph view

So far we have a very basic configuration of CytoscapeJS embedded for the graph view. This needs developing to have feature parity (or close enough) to OLS3.

Since we now nearly have the OLS3 graph view endpoints implemented, it may be quicker to simply embed the OLS3 graph view for the time being.


CHANGELOG for 1.5.0

Signed-off-by: David Kwon<EMAIL_ADDRESS>

I don't think I should add this to the changelog: https://github.com/redhat-developer/vscode-quarkus/pull/245

no it's irrelevant

Changed the snippet enhancement to Update Quarkus datasource snippet.


Toggle Crawl

Just like Sprinting and Sneaking you're able to set the modes on HOLD or TOGGLE in the accesebilty tab in the minecraft menu, and I wish this mod allows us to put it on toggle.

yes please ad a crawl toggle in


Add MetricsExporter interface

Specs issue : https://github.com/open-telemetry/opentelemetry-specification/issues/157
Similar to SpanExporter interface, add MetricsExporter interface -> An interface that allows different metrics services to export recorded data to the backend.

Is this issue and #443 blocked by open-telemetry/opentelemetry-specification#157 ?

It's right now implemented here: https://github.com/open-telemetry/opentelemetry-js/blob/master/packages/opentelemetry-metrics/src/export/types.ts#L344
shutdown is missing.


Date Range has a Small Gap in Between Certain Dates

Current behavior
Between Certain dates in the Date range, there is a gap in the range highlight.
How to reproduce?
On the date range documentation's snack you can launch it on the IOS simulator and see this. If you select a range ending on Friday (ex: March 15, 2023 - March 17, 2023), there will be a small gap by the end date. This is much more noticeable with a dark theme but still can be seen with a light theme.
Note: The date it appears on changes per device. On my personal project and device, it'll appear with a date range ending on Thursday or Saturday, but I have a coworker for whom it'll appear with a date range ending on Thursday, Friday, or Saturday
Preview
In the image below, there's a small gap between March 16, 2023 and March 17, 2023

Sounds like a duplicate of this https://github.com/web-ridge/react-native-paper-dates/issues/149

Hey, @iM-GeeKy It isn't a duplicate of that. I solved the issue mentioned in #149 on my end by setting the start date's hours, minutes, seconds, and milliseconds to 0.

Hey! Thanks for opening the issue. Can you provide a minimal repro which demonstrates the issue? Posting a snippet of your code in the issue is useful, but it's not usually straightforward to run. A repro will help us debug the issue faster. Please try to keep the repro as small as possible. The easiest way to provide a repro is on snack.expo.dev. If it's not possible to repro it on snack.expo.dev, then you can also provide the repro in a GitHub repository.

I mentioned this in the description above, but the snack from the date range documentation works perfectly fine to show this.
Link: https://snack.expo.dev/@fitzwabs/react-native-paper-dates-range-picker?platform=ios
Platform: IOS but the same thing happens on android when I locally test

Closed by https://github.com/web-ridge/react-native-paper-dates/issues/281

Hey, @iM-GeeKy thanks for making the changes! Everything looks good on IOS, but Android still seems to have this problem on version 0.16.1.


Why beforeRouteUpdate not working when I return to first page?

Full description of my problem in stackoverflow
Please help me resolve this issue

hi @tolyanor
Looks like you got it sorted.


Update the start arguments of a latest Polkadot node

With latest 1.13.0, our E2E tests are failing with:
Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
    WASM backtrace:
    error while executing at wasm backtrace:
        0: 0x6948bb - <unknown>!rust_begin_unwind
        1: 0x150e0 - <unknown>!core::panicking::panic_fmt::he07f4fcfc0e8e78f
        2: 0x42c1e9 - <unknown>!TaggedTransactionQueue_validate_transaction: RuntimeApi, Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\nerror while executing at wasm backtrace:\n    0: 0x6948bb - <unknown>!rust_begin_unwind\n    1: 0x150e0 - <unknown>!core::p…

      at apply (node_modules/@polkadot/util/cjs/logger.js:60:24)
      at Object.error (node_modules/@polkadot/util/cjs/logger.js:119:31)
      at logErrorMessage (node_modules/@polkadot/rpc-core/cjs/bundle.js:26:7)
      at node_modules/@polkadot/rpc-core/cjs/bundle.js:179:21

I don't know yet if we are messing something up (we are patching the binary after all), or if we discovered some breaking change in Polkadot.

Looks like the issue is with funding the treasury:
https://github.com/paritytech/substrate-tip-bot/blob/0b8b9eb693aabcfb40c27eecfdf971424b8b384e/src/tip-opengov.e2e.ts#L73
We fund the treasury in case it is empty, to allow it to send out funds after the tip referendum is approved.

There's been (announced) breaking changes in Polkadot - like that CheckMetadataHash feature.
I had to upgrade the PJS version and then it works.
I also had to wait for extrinsics to be included in blocks, because I had issues with nonces otherwise.
@mutantcornholio Could you review again please?


nodes construction when utilizing two adatas

I have a question about the node construction
nodes = cn.connect.nodes(adata_tissue)
when we want to connect two adatas (adata_tissue_A & adata_tissue_B), should I merge the these two first
(adata_tissue = adata_tissue_A.concatenate(adata_tissue_B))?
Thank you.

Hi!
cn.connect.nodes() accepts a list of adatas, so you could write nodes = cn.connect.nodes([adata_tissue_A, adata_tissue_B])
This would find all nodes in the two datasets. Note however that the names must be unique, otherwise cell type "A" in tissue A would be merge with cell type "A" in tissue B.
Hope that helps!
Kindly,
Jon


More tests

Current coverage is 49.44%

Merging #33 into develop will increase coverage by +24.95% as of a635949

@@            develop     #33   diff @@
=======================================
  Files            10      10
  Stmts           445     447     +2
  Branches          0       0
  Methods
=======================================
+ Hit             109     221   +112
  Partial           0       0
+ Missed          336     226   -110

Review entire Coverage Diff as of a635949

Powered by Codecov. Updated on successful CI builds.


plumed: allow for ILP64 builds

Description of changes
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

There is no such option as --enable-ilp64:
configure flags: --disable-static --disable-dependency-tracking --prefix=/nix/store/47693cpc6lklyyhbvdykihsqizqhgznl-plumed-2.9.1 --enable-ilp64
plumed> configure: WARNING: unrecognized options: --disable-static, --enable-ilp64

and also no such thing in the plumed source code: github.com/search?q=repo:plumed/plumed2%20ilp64&type=code

cc @markuskowa .

This was a byproduct. I wanted to remove that commit anyway. I may have become outdated in the last 8 months. I guess we can close this PR.


Error: 'LateInitializationError' isn't a type

Steps to Reproduce

Run flutter create bug.
Update the files as follows:

void main() {
  TryingToBeLate tryingToBeLate = TryingToBeLate();
  try {
    print(tryingToBeLate.lateString);
  } on LateInitializationError {
    print("Oops!");
  }
  runApp(MyApp());
}

// ...default code...

class TryingToBeLate {

  late final String lateString;

  TryingToBeLate(){
    // But never initializing it
  }

}

Run the app

Expected results:
App runs without errors
Actual results:
Dart error: Error: 'LateInitializationError' isn't a type.

Logs

...
[ +481 ms] Launching lib/main.dart on Chrome in debug mode...
[ +215 ms] Updating assets
[ +174 ms] Waiting for connection from debug service on Chrome...
[ +332 ms] <- reset
[  +24 ms] /Users/rohit/Applications/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/Users/rohit/Applications/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root
/Users/rohit/Applications/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata
-DFLUTTER_WEB_AUTO_DETECT=true --output-dill /var/folders/ks/8rd8hm0n18b3wh8dzchfc7400000gp/T/flutter_tools.xvq1f5/flutter_tool.Vt9kjc/app.dill
--libraries-spec file:///Users/rohit/Applications/flutter/bin/cache/flutter_web_sdk/libraries.json --packages
/Users/rohit/workspace/infitio/chartered_ui/bug/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts
--track-widget-creation --filesystem-root /var/folders/ks/8rd8hm0n18b3wh8dzchfc7400000gp/T/flutter_tools.xvq1f5/flutter_tools.9Alhly --filesystem-scheme
org-dartlang-app --initialize-from-dill build/b1b715402d823b7fd5c2b68d2edcb2ce.cache.dill.track.dill --platform
file:///Users/rohit/Applications/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill --sound-null-safety
[  +17 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+5581 ms] lib/main.dart:7:8: Error: 'LateInitializationError' isn't a type.
[   +2 ms]   } on LateInitializationError {
[        ]        ^^^^^^^^^^^^^^^^^^^^^^^

$ flutter analyze
 bug % flutter analyze
Analyzing bug...

   info • Omit type annotations for local variables • lib/main.dart:4:3 • omit_local_variable_types
   info • Prefer final for variable declarations if they are not reassigned • lib/main.dart:4:5 • prefer_final_locals
   info • A potentially nullable type can't be used in an 'on' clause because it isn't valid to throw a nullable expression • lib/main.dart:7:8 •
          nullable_type_in_catch_clause
  error • The name 'LateInitializationError' isn't a type and can't be used in an on-catch clause • lib/main.dart:7:8 • non_type_in_catch_clause
   info • Only use double quotes for strings containing single quotes • lib/main.dart:8:11 • prefer_single_quotes
   info • Use => for short members whose body is a single return statement • lib/main.dart:16:38 • prefer_expression_function_bodies
   info • Prefer declaring const constructors on `@immutable` classes • lib/main.dart:37:3 • prefer_const_constructors_in_immutables
   info • Use => for short members whose body is a single return statement • lib/main.dart:69:38 • prefer_expression_function_bodies
   info • Prefer const with constant constructors • lib/main.dart:102:13 • prefer_const_constructors
   info • Prefer const with constant constructors • lib/main.dart:115:16 • prefer_const_constructors
   info • Sort pub dependencies • pubspec.yaml:30:3 • sort_pub_dependencies
   info • Avoid annotating types for function expression parameters • test/widget_test.dart:14:49 • avoid_types_on_closure_parameters

12 issues found. (ran in 4.4s)

$ flutter doctor -v
~ % flutter doctor -v
[✓] Flutter (Channel beta, 1.26.0-17.3.pre, on macOS 11.1 20C69 darwin-x64, locale en-US)
    • Flutter version 1.26.0-17.3.pre at /Users/rohit/Applications/flutter
    • Framework revision 4b50ca7f7f (15 hours ago), 2021-02-04 19:44:27 -0800
    • Engine revision 2c527d6c7e
    • Dart version 2.12.0 (build 2.12.0-259.8.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/rohit/Library/Android/sdk
    • Platform android-30, build-tools 29.0.2
    • ANDROID_HOME = /Users/rohit/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 88.0.4324.150
    ! Error: Rohit’s iPhone is not connected. Xcode will continue when Rohit’s iPhone is connected. (code -13)

Hi @tiholic
From what I can see, the issue is related to Dart rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you

Hi @pedromassango !
I noticed this issue only after upgrading flutter beta from 1.25.0-8.3.pre to 1.26.0-17.3.pre
The logs I shared above are by following these steps:

flutter create bug
update code as mentioned in "Update the files as follows:" step (as per my issue description)
flutter run -v

PS: I understand this is a dart issue, but could it be due to bad dart version shipped with 1.26.0-17.3.pre version of flutter? (Creating a fresh project - bug and running with the changes above should have worked just fine otherwise)


Update Helm release topolvm to v14.1.2

This PR contains the following updates:

Package
Update
Change

topolvm
minor
14.0.0 -> 14.1.2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Tested on lab.


[Bug]: werewolf_utils:extract_name_and_id:58 - vote: invalid name wait and see, set to Abstain

AgentScope is an open-source project. To involve a broader community, we recommend asking your questions in English.
Describe the bug
I want to run game_werewolf example using local Ollama
To Reproduce
Steps to reproduce the behavior:

custom model_config.json

[
    {
        "config_name": "my_ollama_chat_config",
        "model_type": "ollama_chat",
        "model_name": "llama3.2:latest",
        "options": {
          "temperature": 0.5,
          "seed": 123
        },
        "keep_alive": "5m"
    },
    {
        "model_type": "post_api_chat",
        "config_name": "my_post_api",
        "api_url": "http://localhost:5000/",
        "headers": {},
        "json_args": {}
    }
]

custom agent_configs.json

[
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player1",
            "sys_prompt": "Act as a player in a werewolf game. You are Player1 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing werewolf in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    },
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player2",
            "sys_prompt": "Act as a player in a werewolf game. You are Player2 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing werewolf in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    },
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player3",
            "sys_prompt": "Act as a player in a werewolf game. You are Player3 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing villager in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    },
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player4",
            "sys_prompt": "Act as a player in a werewolf game. You are Player4 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing villager in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    },
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player5",
            "sys_prompt": "Act as a player in a werewolf game. You are Player5 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing seer in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    },
    {
        "class": "DictDialogAgent",
        "args": {
            "name": "Player6",
            "sys_prompt": "Act as a player in a werewolf game. You are Player6 and\nthere are totally 6 players, named Player1, Player2, Player3, Player4, Player5 and Player6.\n\nPLAYER ROLES:\nIn werewolf game, players are divided into two werewolves, two villagers, one seer and one witch. Note only werewolves know who are their teammates.\nWerewolves: They know their teammates' identities and attempt to eliminate a villager each night while trying to remain undetected.\nVillagers: They do not know who the werewolves are and must work together during the day to deduce who the werewolves might be and vote to eliminate them.\nSeer: A villager with the ability to learn the true identity of one player each night. This role is crucial for the villagers to gain information.\nWitch: A character who has a one-time ability to save a player from being eliminated at night (sometimes this is a potion of life) and a one-time ability to eliminate a player at night (a potion of death).\n\nGAME RULE:\nThe game is consisted of two phases: night phase and day phase. The two phases are repeated until werewolf or villager win the game.\n1. Night Phase: During the night, the werewolves discuss and vote for a player to eliminate. Special roles also perform their actions at this time (e.g., the Seer chooses a player to learn their role, the witch chooses a decide if save the player).\n2. Day Phase: During the day, all surviving players discuss who they suspect might be a werewolf. No one reveals their role unless it serves a strategic purpose. After the discussion, a vote is taken, and the player with the most votes is \"lynched\" or eliminated from the game.\n\nVICTORY CONDITION:\nFor werewolves, they win the game if the number of werewolves is equal to or greater than the number of remaining villagers.\nFor villagers, they win if they identify and eliminate all of the werewolves in the group.\n\nCONSTRAINTS:\n1. Your response should be in the first person.\n2. This is a conversational game. You should response only based on the conversation history and your strategy.\n\nYou are playing witch in this game.\n",
            "model_config_name": "my_ollama_chat_config",
            "use_memory": true
        }
    }
]

log anh error

Expected behavior
I am trying to find documents about customizing ollama this config in model_configs.json
original code
    {
        "model_type": "post_api_chat",
        "config_name": "my_post_api",
        "api_url": "https://xxx",
        "headers": {},
        "json_args": {}
    }

But I don't find anything can resolve, please help me edit this config with ollama and run this example.
Environment (please complete the following information):

AgentScope Version: 0.1.2dev0
Python Version: 3.9.20
OS: ubuntu 20.04 LTS

I have tried to change majority_vote.py like below, but still not working
def majority_vote(votes: list) -> Any:
    """majority_vote function"""
    votes_valid = [item for item in votes if item != "Abstain"]
    # Count the votes excluding abstentions.
    # If no valid votes after filtering abstains, return "Abstain"
    if not votes_valid:
        return "Abstain"
    unit, counts = np.unique(votes_valid, return_counts=True)
    return unit[np.argmax(counts)]

There are too many things that I don't know, please help me run the example to understand these knowledge. Thanks
http://localhost:5000 is url of agent scope ui

@qbc2016 please take a look at this issue.

Hello, your model configuration settings for ollama are correct, the following is all you need:
{
    "config_name": "my_ollama_chat_config",
    "model_type": "ollama_chat",
    "model_name": "llama3.2:latest",
    "options": {
      "temperature": 0.5,
      "seed": 123
    },
    "keep_alive": "5m"
}

The error occurs because the model does not follow the prompt correctly.
During the voting phase, each werewolf's vote for a player is appended after the "vote" field. However, since both werewolves did not vote, the code votes = [extract_name_and_id(wolf(hint).content)[0] for wolf in wolves] results in votes = ['Abstain', 'Abstain']. Then, in the majority_vote function, we have votes_valid = [item for item in votes if item != "Abstain"] which results in votes_valid being an empty list ([]). According to the game rules, this situation should not occur.
It is suggested to modify the prompt to ensure the model votes at this stage, or try using a larger model.
I see that you've modified the majority_vote function, which should prevent errors from occurring now, but you said that "still not working", could you please provide more details?

Thanks for reply, I'm focusing on game gomoku. I will come back this issue later.