Refactor API URLs to use environment variables

Title: Environment Configuration for Dynamic Base URL Setup
Description
This PR adds an environment-based configuration to dynamically manage the base API URL. Previously, the URLs were hardcoded (http://localhost:5000). With this update, the serverUrl from the environment file is used, allowing for different base URLs based on the environment (e.g., development, production).
Related Issue
Issue https://github.com/c2siorg/Webiu/issues/84
Motivation and Context
This change is required to make the codebase more flexible and environment-agnostic. By using the environment configuration, switching between environments (development, testing, production) is streamlined without modifying individual components. This also aligns with best practices for scalable applications.
Screenshots (In case of UI changes)
N/A
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
✅ New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

✅ My code follows the code style of this project.
✅ My change requires a change to the documentation.
✅ I have updated the documentation accordingly.
✅ All new and existing tests have passed and it does not give any unexpected error for the same.

@rajutkarsh07 can u suggest anything on https://github.com/c2siorg/Webiu/actions/runs/11572925997/job/32213937904?pr=85


Provide/disable date and other options

Is there a way of disabling the generated on date for the schema docs front page or providing fixed info instead using an option?
The date format is also fixed and not one we tend to use in the UK, so depending upon your solution you may wish to address that issue for foreign audiences too :)

Hi @KodeMunkie

Is there a way of disabling the generated on date for the schema docs front page or providing fixed info instead using an option?

Using the homepage option, you can set your own homepage.
Using CLI:
npx docusaurus graphql-to-doc --homepage custom_homepage_location.md

Using plugin config:
// ...
'@edno/docusaurus2-graphql-doc-generator',
{
  // ... other options
  homepage: 'custom_homepage_location.md'
}
// ...

You can copy the current homepage and change it as it suits you.

The date format is also fixed and not one we tend to use in the UK

The plugin uses .toLocaleString() for formatting the current data (see code), so this should respect your server locale.
However, if you want a more flexible behaviour, e.g. adding format to the replacement pattern ##generated-date-time(yyyy-dd-mm)##, then feel free to push a PR or describe the expected solution.


uppercase and lowercase username issue

Describe the issue
Sometimes users have problems with the uppercase username.

Requires to create a user with upper case.
Identify the underlying problem (either frontend or backend)
Fix the issue

Could you please assign this issue to me?

Hey @96RadhikaJadhav - thank you so much for volunteering! I've assigned the issue to you. Feel free to join our [community slack](Join me on Slack — it’s a faster, simpler way to work. Sign up here, from any device: https://join.slack.com/t/hubdb/shared_invite/zt-ivhsj8sz-GWv9c5FLBDVw8vn~sxRKqQ) to ask any questions as they arise.

Hey @mikayelh ..Thanks for giving me a chance :)  Could you please tell me in which file I could find username details?

Hi @96RadhikaJadhav,
Here are some notes that might be helpful.

Please take a look at the authentication part https://github.com/activeloopai/Hub/blob/release/v1.0.0-beta/hub/cli/auth.py, try to get a sense of how users register when they run >hub register and >hub login?
Then take a look at what is actually sent to the server https://github.com/activeloopai/Hub/blob/release/v1.0.0-beta/hub/client/auth.py, here you would need to inspect the rest api queries.
Then, once the user is registered, the token and authentication key is received which are stored in ~/.activeloop/store and ~/.activeloop/token, please take a look if the username matches the uppercase username that has been registered

Notes

It might be the case that the CLI tool is doing everything right. The backend is playing around with the username while retrieving the data. If that is the case please, report it here so we can take a deeper look at the backend.


plugin_not_installed

i do not know why with this plugin, i have install this plugin and add with ionic cordova add, but some times this plugin show the error plugin_not_installed, please help me why ?

Try calling the method inside platform.ready()


Upgrade to Gatsby 3 and fix Heroku caching

Builds off of #2848, adding a script that stabilized build paths to ensure Gatsby doesn't clean its cache when not necessary, among some other changes to help speed up builds as much as we can.
Build times
Old packages (Gatsby 2)
Completely cold cache: 1937s
Automatic cache clear: 612s
Fully warm cache (script backport in #2898): 170s
New packages (Gatsby 4 beta)
Completely cold cache: 840s
Automatic cache clear: 283s
Fully warm cache: 91s

Weird, this is what site looks like on my end:

Do we need to try rebuilding it?

That was weird, I got it too and a rebuild did indeed fix the fonts for me. The public folder was also malformed and triggered a full rebuild- not a good portent :grimacing:


"Select Unplanned failover"

Hello,
I think there is a typo in the docs where it says "Choose unplanned failover". Should be "planned" failover, I hope its not possible to choose unplanned failover.
Whole ASR docs need a complete upgrade, a lot of it is legacy docs and it is really hard to follow.
BR,
Rasmus

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

ID: 153df524-a28e-2ed8-7ebc-5f49662a8b11
Version Independent ID: fc9b67c1-af12-6f2d-5602-03d7372b2784
Content: Fail back VMware VMs/physical servers from Azure with Azure Site Recovery - Azure Site Recovery
Content Source: articles/site-recovery/vmware-azure-failback.md
Service: site-recovery
GitHub Login: @ankitaduttaMSFT
Microsoft Alias: ankitadutta

I completely agree.. The documentation for ASR needs to be updated.It is still showing legacy process.

@reduards Thanks for the feedback. Tagging @ankitaduttaMSFT for visibility, review and enhance document as appropriate.

Hi @reduards - seems like you are correct. It won't be "Planned failover" also, we only have the "Failover" button in this case which will be used to perform the failback. I will edit the documentation.
Thanks for your feedback around the documentation being old. We are working on improving the documentation for ASR.

#please-close


Fix CLI commands in UCP / DTR Backup and Restore

Proposed changes
The current UCP / DTR backup / restore commands do not work as the variables are not correct. I have fixed the CLI commands and standardised the formatting.
Fixes: https://github.com/docker/docker.github.io/issues/9193
Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 6319a2390adcfdbe900fc585a787f36cc38cbc19
https://deploy-preview-9209--docsdocker.netlify.com


Set idle_timeout to specific Request or Route

Hi, can we set idle_timeout only in specific Request. The idea is to set infinity idle_timeout to server side events.
Thanks for your time

There's an example at the bottom here: https://ninenines.eu/docs/en/cowboy/2.9/manual/cowboy_req.cast/


First draft

The goals for this library are probably best conveyed by the documentation:
Overall Idea / Sales Pitch

EnvT for explicit and/or "simple" use-cases

MockT for testing without disrupting existing specs

(ViaMock is cool, but not everyone runs specs in a custom example monad.)
ViaReader for what we'll actually be using in our own stack

(Lots of folks do run their app in a custom app monad.)
Some open naming questions

monad-aws instead of amazonka-mtl?
New names for Matcher like MatchRequest(MatchSend, MatchAwait)
New name for MockT like MatchersT or MatchingT or ???

LGTM! If i tried it i might have some suggestions, but otherwise :shipit:


Key Section is no longer current

The current Azure AAD application iis not like the listed screenshots. It does not contain anything about keys and the path is not current - is this substituted by keyvault or other? Please advise where I can find the Application Key when registering the service?

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

ID: 717d397d-4186-c7de-431d-3260d3f0484a
Version Independent ID: bdd7545b-5970-93e0-5cbb-a59da4ace01b
Content: Configure Power BI integration for workspaces - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/analytics/configure-power-bi-integration.md
Service: dynamics-ax-platform
GitHub Login: @MilindaV2
Microsoft Alias: milindav

Thank you for your comment. @milindav would you please review this?

Bug # 348403 has been logged to track this issue.

any news on this?

Instead of waiting on an update to the documentation, I suggest that you contact Support using one of the options described here: Support contact options. In particular, you might want to go to the Dynamics 365 for Finance and Operations community page to get help with your questions from the Dynamics community.

Thank you for the feedback
From: Tonya Fehr<EMAIL_ADDRESS>Sent: 13 August 2019 15:40
To: MicrosoftDocs/dynamics-365-unified-operations-public<EMAIL_ADDRESS>Cc: orichardt<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Key Section is no longer current (#1541)
Instead of waiting on an update to the documentation, I suggest that you contact Support using one of the options described here: Support contact optionshttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdynamics365%2Funified-operations%2Fdev-itpro%2Flifecycle-services%2Flcs-support&data=02|01||3a97070efd744754815908d71ff3b0d5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637013003813732324&sdata=0246gKI7Nb9ciKMpV6rVFLAdSTKum%2FiwmK3w7Q1skRI%3D&reserved=0. In particular, you might want to go to the Dynamics 365 for Finance and Operations community pagehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.dynamics.com%2F&data=02|01||3a97070efd744754815908d71ff3b0d5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637013003813742335&sdata=HSPlcZ5jNgida6R2TRWAdY7wkiKwn5jkeR7jisZXf4Y%3D&reserved=0 to get help with your questions from the Dynamics community.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-unified-operations-public%2Fissues%2F1541%3Femail_source%3Dnotifications%26email_token%3DAMYCA6J6AP7ECQJGHDMVJ4TQEK2RXA5CNFSM4IH5QQ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4FV33Q%23issuecomment-520838638&data=02|01||3a97070efd744754815908d71ff3b0d5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637013003813752346&sdata=64IDx5ExERfFU9fdtOvWqFkT5F9x9Tmcymz3N7d9pdw%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMYCA6NGYYOR4AQNYRY3FXLQEK2RXANCNFSM4IH5QQ4Q&data=02|01||3a97070efd744754815908d71ff3b0d5|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637013003813762357&sdata=XkJH3lB8HEojf7BM7egRcDROIJkFLQ5as8gTDgGTaew%3D&reserved=0.


Instrumentation for EFCore - add tracing and metrics

The landscape has changed here, we now believe all important metrics and tracing data should be (and in many cases already are) provided by the client drivers for any backing service.


TLS handshake error from IP: acme/autocert: host not configured

Rancher versions:
rancher/rancher:latest:v2.1.0
rancher/rancher-agent:v2.1.0
Infrastructure Stack versions:
kubernetes: v.11.3-rancher1-1
Docker version: (docker version,docker info preferred)
Containers: 39
 Running: 26
 Paused: 0
 Stopped: 13
Images: 22
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-36-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.79GiB
Name: quantum
ID: 3MB5:5ZZ5:SESA:NO65:3XJW:DDDZ:TVTF:YIWZ:EZEE:VYN7:DSIX:QH7B
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare metal

Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher (following steps from documentation for letsencrypt)
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes

Steps to Reproduce:
docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -v /docker/rancher:/var/lib/rancher \
  -e AUDIT_LEVEL=1 \
  rancher/rancher:latest \
  --acme-domain rancher.my-domain.com

docker logs -f rancher_server_container

Results:
Between 10 and 30 log lines per second like the ones below which at some point crash Rancher and that restarts the server container.
2018/10/11 13:03:53 [INFO] 2018/10/11 13:03:53 http: TLS handshake error from <IP_ADDRESS>:53344: acme/autocert: host not configured
2018/10/11 13:03:54 [INFO] 2018/10/11 13:03:54 http: TLS handshake error from <IP_ADDRESS>:56431: acme/autocert: host not configured
2018/10/11 13:03:54 [INFO] 2018/10/11 13:03:54 http: TLS handshake error from <IP_ADDRESS>:42404: acme/autocert: host not configured
2018/10/11 13:03:55 [INFO] 2018/10/11 13:03:55 http: TLS handshake error from <IP_ADDRESS>:47577: acme/autocert: host not configured
2018/10/11 13:03:56 [INFO] 2018/10/11 13:03:56 http: TLS handshake error from <IP_ADDRESS>:58896: acme/autocert: host not configured
2018/10/11 13:03:56 [INFO] 2018/10/11 13:03:56 http: TLS handshake error from <IP_ADDRESS>:63709: acme/autocert: host not configured
2018/10/11 13:03:56 [INFO] 2018/10/11 13:03:56 http: TLS handshake error from <IP_ADDRESS>:59552: acme/autocert: host not configured
panic: Header called after Handler finished

goroutine 148508 [running]:
net/http.(*http2responseWriter).Header(0xc00e1da730, 0xc00374ee00)
	/usr/local/go/src/net/http/h2_bundle.go:6310 +0x99
github.com/rancher/rancher/pkg/filter.(*wrapWriter).Write.func1(0xc0115f0960, 0xc015478000, 0x35264, 0x3b757)
	/go/src/github.com/rancher/rancher/pkg/filter/filter.go:37 +0x38
created by github.com/rancher/rancher/pkg/filter.(*wrapWriter).Write
	/go/src/github.com/rancher/rancher/pkg/filter/filter.go:36 +0xb4

Can you drop the   -e AUDIT_LEVEL=1 \ and does it still happen then?

Thanks for your fast response! I've recreated the container removing the -e AUDIT_LEVEL. This did not fix the http: TLS handshake error from IP: acme/autocert: host not configured error, but so far it looks like it won't crash.

I have managed to understand why we were seeing the handshake error. The machine where rancher.my-domain.com is hosted uses an IP which is also used for some other services we used to had. Bots are trying to index subdomains which are pointing to the same IP address. So what happens is a bot tries to access https://some-sub-domain.my-domain.com which resolves to the public ip where rancher.my-domain.com is hosted and currently Rancher has not been setup to respond to that request as we're migrating from 1.6.
I confirmed my finding by doing a curl from outside to https://some-sub-domain.my-domain.com and the IP address from which I was testing appeared in the logs with the same TLS handshake error.
Thanks for your help and fast responses! I think we could close this although it would be good if there was a nicer message about this.

I have the same error.
Can not reach the rancher ui by via domain name, via its IP it is working fine.
Not clear how you solved it

The same error occures for me.
I can not provision any new clusters.
Tested with ec2 and hetzner  as the provider.
Maybe related? #16220
My docker-compose.yml:
version: '3'

services:
  rancher:
    image: rancher/rancher:v2.1.1
    container_name: rancher
    network_mode: host
    restart: unless-stopped
    volumes:
      - /mnt/rancher2:/var/lib/rancher
    command: --acme-domain rancher.example.com

Full rancher log
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Creating namespace c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Creating Default project for cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Creating namespace p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Creating System project for cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Creating creator projectRoleTemplateBinding for user user-2fbzl for project p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Creating namespace p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Creating creator clusterRoleTemplateBinding for user user-2fbzl for cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Creating creator projectRoleTemplateBinding for user user-2fbzl for project p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Setting InitialRolesPopulated condition on project p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating clusterRole p-gtzwf-projectowner
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Setting InitialRolesPopulated condition on project p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Updating project p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating clusterRole c-tfmr6-clusterowner
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for membership in project p-gtzwf for subject user-2fbzl
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating clusterRole p-hc2qs-projectowner
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Updating project p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Setting InitialRolesPopulated condition on cluster
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating clusterRole c-tfmr6-clustermember
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating clusterRoleBinding for membership in cluster c-tfmr6 for subject user-2fbzl
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating clusterRoleBinding for membership in cluster c-tfmr6 for subject user-2fbzl
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for membership in project p-hc2qs for subject user-2fbzl
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Updating project p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Updating project p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Updating clusterRoleBinding clusterrolebinding-fr2q8 for cluster membership in cluster c-tfmr6 for subject user-2fbzl
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role project-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating roleBinding for subject user-2fbzl with role cluster-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role project-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-project-rbac-create] Updating project p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating role admin in namespace p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating roleBinding for subject user-2fbzl with role cluster-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace p-gtzwf
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role admin in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating role cluster-owner in namespace p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating role admin in namespace p-hc2qs
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role project-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role admin in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-2fbzl with role project-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-auth-crtb-controller] Creating roleBinding for subject user-2fbzl with role cluster-owner in namespace
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-tfmr6
2018/11/19 10:23:29 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-tfmr6
2018/11/19 10:23:30 [INFO] stdout: Creating CA: management-state/node/nodes/bb-8/certs/ca.pem
2018/11/19 10:23:30 [INFO] stdout: Creating client certificate: management-state/node/nodes/bb-8/certs/cert.pem
2018/11/19 10:23:31 [INFO] stdout: Running pre-create checks...
2018/11/19 10:23:31 [INFO] stdout: Creating machine...
2018/11/19 10:23:31 [INFO] stdout: (bb-8) Creating SSH key...
2018/11/19 10:23:31 [INFO] stdout: (bb-8) Creating Hetzner server...
2018/11/19 10:23:32 [INFO] stdout: (bb-8)  -> Creating server bb-8[1391215] in create_server[8279609]
2018/11/19 10:23:35 [INFO] stdout: (bb-8)  -> Server bb-8[1391215]: Waiting to come up...
2018/11/19 10:23:48 [INFO] stdout: Waiting for machine to be running, this may take a few minutes...
2018/11/19 10:23:48 [INFO] stdout: Detecting operating system of created instance...
2018/11/19 10:23:48 [INFO] stdout: Waiting for SSH to be available...
2018/11/19 10:24:19 [INFO] stdout: Detecting the provisioner...
2018/11/19 10:24:19 [INFO] stdout: Provisioning with ubuntu(systemd)...
2018/11/19 10:24:56 [INFO] stdout: Installing Docker...
2018/11/19 10:25:25 [INFO] stdout: Copying certs to the local machine directory...
2018/11/19 10:25:27 [INFO] stdout: Copying certs to the remote machine...
2018/11/19 10:25:29 [INFO] stdout: Setting Docker configuration on the remote daemon...
2018/11/19 10:25:32 [INFO] stdout: Checking connection to Docker...
2018/11/19 10:25:32 [INFO] stdout: Docker is up and running!
2018/11/19 10:25:44 [INFO] Generating and uploading node config bb-8
2018/11/19 10:25:44 [INFO] 2018/11/19 10:25:44 http: TLS handshake error from <IP_ADDRESS>:55296: acme/autocert: host not configured
2018/11/19 10:25:44 [INFO] Provisioning cluster [c-tfmr6]
2018/11/19 10:25:44 [INFO] Creating cluster [c-tfmr6]
2018/11/19 10:25:44 [INFO] cluster [c-tfmr6] provisioning: Building Kubernetes cluster
2018/11/19 10:25:44 [INFO] cluster [c-tfmr6] provisioning: [dialer] Setup tunnel for host [<IP_ADDRESS>]
2018/11/19 10:25:44 [INFO] cluster [c-tfmr6] provisioning: [network] Deploying port listener containers
2018/11/19 10:25:44 [INFO] cluster [c-tfmr6] provisioning: [network] Pulling image [rancher/rke-tools:v0.1.15] on host [<IP_ADDRESS>]
2018/11/19 10:25:44 [INFO] 2018/11/19 10:25:44 http: TLS handshake error from <IP_ADDRESS>:55300: acme/autocert: host not configured
2018/11/19 10:25:44 [INFO] 2018/11/19 10:25:44 http: TLS handshake error from <IP_ADDRESS>:55304: acme/autocert: host not configured
2018/11/19 10:25:45 [INFO] 2018/11/19 10:25:45 http: TLS handshake error from <IP_ADDRESS>:55308: acme/autocert: host not configured
2018/11/19 10:25:46 [INFO] 2018/11/19 10:25:46 http: TLS handshake error from <IP_ADDRESS>:55340: acme/autocert: host not configured
2018/11/19 10:25:48 [INFO] 2018/11/19 10:25:48 http: TLS handshake error from <IP_ADDRESS>:55368: acme/autocert: host not configured
2018/11/19 10:25:52 [INFO] 2018/11/19 10:25:52 http: TLS handshake error from <IP_ADDRESS>:55370: acme/autocert: host not configured
2018/11/19 10:25:53 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully pulled image [rancher/rke-tools:v0.1.15] on host [<IP_ADDRESS>]
2018/11/19 10:25:54 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-etcd-port-listener] container on host [<IP_ADDRESS>]
2018/11/19 10:25:54 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-cp-port-listener] container on host [<IP_ADDRESS>]
2018/11/19 10:25:55 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-worker-port-listener] container on host [<IP_ADDRESS>]
2018/11/19 10:25:55 [INFO] cluster [c-tfmr6] provisioning: [network] Port listener containers deployed successfully
2018/11/19 10:25:55 [INFO] cluster [c-tfmr6] provisioning: [network] Running control plane -> etcd port checks
2018/11/19 10:25:56 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
2018/11/19 10:25:56 [INFO] cluster [c-tfmr6] provisioning: [network] Running control plane -> worker port checks
2018/11/19 10:25:57 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
2018/11/19 10:25:57 [INFO] cluster [c-tfmr6] provisioning: [network] Running workers -> control plane port checks
2018/11/19 10:25:58 [INFO] cluster [c-tfmr6] provisioning: [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
2018/11/19 10:25:58 [INFO] cluster [c-tfmr6] provisioning: [network] Skipping kubeapi port check
2018/11/19 10:25:58 [INFO] cluster [c-tfmr6] provisioning: [network] Removing port listener containers
2018/11/19 10:25:58 [INFO] cluster [c-tfmr6] provisioning: [remove/rke-etcd-port-listener] Successfully removed container on host [<IP_ADDRESS>]
2018/11/19 10:25:59 [INFO] 2018/11/19 10:25:59 http: TLS handshake error from <IP_ADDRESS>:55372: acme/autocert: host not configured
2018/11/19 10:25:59 [INFO] cluster [c-tfmr6] provisioning: [remove/rke-cp-port-listener] Successfully removed container on host [<IP_ADDRESS>]
2018/11/19 10:26:00 [INFO] cluster [c-tfmr6] provisioning: [remove/rke-worker-port-listener] Successfully removed container on host [<IP_ADDRESS>]
2018/11/19 10:26:00 [INFO] cluster [c-tfmr6] provisioning: [network] Port listener containers removed successfully
2018/11/19 10:26:00 [INFO] cluster [c-tfmr6] provisioning: [certificates] Attempting to recover certificates from backup on [etcd,controlPlane] hosts
2018/11/19 10:26:00 [INFO] cluster [c-tfmr6] provisioning: [certificates] Successfully started [cert-fetcher] container on host [<IP_ADDRESS>]
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] No Certificate backup found on [etcd,controlPlane] hosts
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating CA kubernetes certificates
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kubernetes API server certificates
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kube Controller certificates
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kube Scheduler certificates
2018/11/19 10:26:01 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kube Proxy certificates
2018/11/19 10:26:02 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Node certificate
2018/11/19 10:26:02 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating admin certificates and kubeconfig
2018/11/19 10:26:02 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating etcd-<IP_ADDRESS> certificate and key
2018/11/19 10:26:03 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kubernetes API server aggregation layer requestheader client CA certificates
2018/11/19 10:26:03 [INFO] cluster [c-tfmr6] provisioning: [certificates] Generating Kubernetes API server proxy client certificates
2018/11/19 10:26:03 [INFO] cluster [c-tfmr6] provisioning: [certificates] Temporarily saving certs to [etcd,controlPlane] hosts
2018-11-19 10:26:07.962389 I | mvcc: store.index: compact 453157
2018-11-19 10:26:07.971374 I | mvcc: finished scheduled compaction at 453157 (took 6.234591ms)
2018/11/19 10:26:10 [INFO] cluster [c-tfmr6] provisioning: [certificates] Saved certs to [etcd,controlPlane] hosts
2018/11/19 10:26:10 [INFO] cluster [c-tfmr6] provisioning: [reconcile] Reconciling cluster state
2018/11/19 10:26:10 [INFO] cluster [c-tfmr6] provisioning: [reconcile] This is newly generated cluster
2018/11/19 10:26:10 [INFO] cluster [c-tfmr6] provisioning: [certificates] Deploying kubernetes certificates to Cluster nodes
2018/11/19 10:26:12 [INFO] 2018/11/19 10:26:12 http: TLS handshake error from <IP_ADDRESS>:55374: acme/autocert: host not configured
2018/11/19 10:26:15 [INFO] cluster [c-tfmr6] provisioning: Successfully Deployed local admin kubeconfig at [management-state/rke/rke-047776818/kube_config_cluster.yml]
2018/11/19 10:26:15 [INFO] cluster [c-tfmr6] provisioning: [certificates] Successfully deployed kubernetes certificates to Cluster nodes
2018/11/19 10:26:15 [INFO] cluster [c-tfmr6] provisioning: Pre-pulling kubernetes images
2018/11/19 10:26:15 [INFO] cluster [c-tfmr6] provisioning: [pre-deploy] Pulling image [rancher/hyperkube:v1.11.3-rancher1] on host [<IP_ADDRESS>]
2018/11/19 10:26:38 [INFO] 2018/11/19 10:26:38 http: TLS handshake error from <IP_ADDRESS>:55422: acme/autocert: host not configured
2018/11/19 10:27:04 [INFO] cluster [c-tfmr6] provisioning: [pre-deploy] Successfully pulled image [rancher/hyperkube:v1.11.3-rancher1] on host [<IP_ADDRESS>]
2018/11/19 10:27:04 [INFO] cluster [c-tfmr6] provisioning: Kubernetes images pulled successfully
2018/11/19 10:27:04 [INFO] cluster [c-tfmr6] provisioning: [etcd] Building up etcd plane..
2018/11/19 10:27:04 [INFO] cluster [c-tfmr6] provisioning: [etcd] Pulling image [rancher/coreos-etcd:v3.2.18] on host [<IP_ADDRESS>]
2018/11/19 10:27:07 [INFO] cluster [c-tfmr6] provisioning: [etcd] Successfully pulled image [rancher/coreos-etcd:v3.2.18] on host [<IP_ADDRESS>]
2018/11/19 10:27:08 [INFO] cluster [c-tfmr6] provisioning: [etcd] Successfully started [etcd] container on host [<IP_ADDRESS>]
2018/11/19 10:27:08 [INFO] cluster [c-tfmr6] provisioning: [etcd] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
2018/11/19 10:27:08 [INFO] cluster [c-tfmr6] provisioning: [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
2018/11/19 10:27:08 [INFO] cluster [c-tfmr6] provisioning: [etcd] Successfully started etcd plane..
2018/11/19 10:27:08 [INFO] cluster [c-tfmr6] provisioning: [controlplane] Building up Controller Plane..
2018/11/19 10:27:09 [INFO] cluster [c-tfmr6] provisioning: [controlplane] Successfully started [kube-apiserver] container on host [<IP_ADDRESS>]
2018/11/19 10:27:09 [INFO] cluster [c-tfmr6] provisioning: [healthcheck] Start Healthcheck on service [kube-apiserver] on host [<IP_ADDRESS>]
2018/11/19 10:27:30 [INFO] 2018/11/19 10:27:30 http: TLS handshake error from <IP_ADDRESS>:55608: acme/autocert: host not configured
2018/11/19 10:27:59 [ERROR] cluster [c-tfmr6] provisioning: [controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [<IP_ADDRESS>]: Get https://localhost:6443/healthz: can not build dialer to c-tfmr6:m-p6qc2, log: I1119 10:27:26.917706       1 storage_rbac.go:276] created rolebinding.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-public
2018/11/19 10:27:59 [ERROR] ClusterController c-tfmr6 [cluster-provisioner-controller] failed with : [controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [<IP_ADDRESS>]: Get https://localhost:6443/healthz: can not build dialer to c-tfmr6:m-p6qc2, log: I1119 10:27:26.917706       1 storage_rbac.go:276] created rolebinding.rbac.authorization.k8s.io/system:controller:bootstrap-signer in kube-public

I'm having the same issue. Ref: https://gist.github.com/nachokb/27f5f33ce7e1de261f6581a0df8efc6a (run command and rancher log).

host has public IP;
DNS is set up;
I can access the app if I ignore the invalid cert warnings;
ports 80 an 443 are exposed (as per the run command's -p arguments);
host has just been provisioned (there are no other apps listening);
error says http: TLS handshake error from <PUBLIC_IP>:39010: acme/autocert: host not configured;

this comes up sometimes 10 times a second;
port changes every time error shows up;
those ports are not exposed, and I don't think they could be either;

I followed instructions from Option 2-D in the Single Node Install Installation Guide

please check https://github.com/golang/crypto/pull/63

in my case I had set it yo using a different subdomain, then changed it
also changed it in settings, but that was not enough
as it was a new installation I just started over again

Root cause of this error is known, if this is reproducible on latest version, please supply steps to reproduce from scratch so we can investigate.


Add cifmw client container

This patch adds a new containerfile defining the container we will use with the upcoming CLI, maybe in CI jobs soon as well.
With every merge into the ci-framework repo the container will be build using the ref content and tagged with the Git SHA. If the PR is merged into the main branch the "latest" tag will be updated otherwise -latest will be used allowing users to pin to 18-purposed-latest for example
Jira: https://issues.redhat.com/browse/OSPRH-9458

This container is not in use anywhere yet, merging this will just start the container being built so we can work on things that will consume it.

Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/2257

/hold
Holding for now, need to check if GitHub action is the right direction, if not maybe OpenShift CI, if not create tiny Zuul job to build and push container.

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

recheck

/unhold

/approve


Adjust config for php-cs-fixer 2.0

Removes --levels and --fixers, adds --rules and --allow-risky.
If this looks good to you, I'll also update the documentation.

I noticed that this still needs some work. I'll try to get it working correctly. PHP-CS-Fixer is using stderr for all output except diffs which screws with the error detection at the moment. Wouldn't merge this at the moment

@rmbl I've added to this and published as 1.0.0 on npm. Upgrading to php-cs-fixer 2 meant rethinking how stderr output and exit codes were used. This update pushes decisions about what to output down to php-cs-fixer instead of trying to handle in the grunt task.


Exception "Sorry but parent: Project (Disposed) ... has already been disposed"

Exception message: Sorry but parent: Project (Disposed) project_name has already been disposed (see the cause for stacktrace) so the child: null 24506114: running=false; canceled=false; task=null will never be disposed
Addition information:
I had a project open. I opened an additional project window to look at its file watcher settings. After using the windows snipping tool to copy the file watcher settings I closed the additional project window. I made the desired changes to the filewatcher and added and removed empty lines to an .scss file to see whether the changes had the desired effect.
I committed the changes already made to the original project through the version control window. I then opened the gerrit window to see whether I had already merged changes made previously that day. At this point the error occured for the already closed additional project in the project I was originally working on.
(received as exception report)
Plugin version: 1.0.2-146
IntelliJ version: PhpStorm 2017.2.3 PS-172.4155.25
OS: Windows 10 10.0
Java: JetBrains s.r.o 1.8.0_152-release
Exception:
com.intellij.util.IncorrectOperationException: Sorry but parent: Project (Disposed) project_name has already been disposed (see the cause for stacktrace) so the child: null 24506114: running=false; canceled=false; task=null will never be disposed
    at com.intellij.openapi.util.objectTree.ObjectTree.register(ObjectTree.java:66)
    at com.intellij.openapi.util.Disposer.register(Disposer.java:97)
    at com.intellij.openapi.util.Disposer.register(Disposer.java:93)
    at com.intellij.openapi.progress.util.ProgressWindow.<init>(ProgressWindow.java:125)
    at com.intellij.openapi.progress.util.ProgressWindow.<init>(ProgressWindow.java:84)
    at com.intellij.openapi.progress.impl.BackgroundableProcessIndicator.<init>(BackgroundableProcessIndicator.java:63)
    at com.intellij.openapi.progress.impl.BackgroundableProcessIndicator.<init>(BackgroundableProcessIndicator.java:44)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcessWithProgressAsynchronously(ProgressManagerImpl.java:139)
    at com.intellij.openapi.progress.impl.CoreProgressManager.b(CoreProgressManager.java:341)
    at com.intellij.openapi.progress.impl.CoreProgressManager.run(CoreProgressManager.java:325)
    at com.intellij.openapi.progress.Task.queue(Task.java:115)
    at com.urswolfer.intellij.plugin.gerrit.rest.GerritUtil$20.run(GerritUtil.java:707)
    at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:314)
    at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.a(LaterInvocator.java:416)
    at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:399)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:762)
    at java.awt.EventQueue.access$500(EventQueue.java:98)
    at java.awt.EventQueue$3.run(EventQueue.java:715)
    at java.awt.EventQueue$3.run(EventQueue.java:709)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:732)
    at com.intellij.ide.IdeEventQueue.j(IdeEventQueue.java:821)
    at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:649)
    at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:365)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Thank you.


Push to Hub Support

Hey @yeyupiaoling! Thanks for building such a valuable resource for the Whisper community 🤗 It would be much appreciated to acknowledge the original Whisper fine-tuning blog post in the references, from which much of the fine-tuning code is inspired.
In addition, it would great to add push_to_hub support to upload model checkpoints directly to the Hugging Face Hub during training. The Hub provides:

Integrated version control: you can be sure that no model checkpoint is lost during training.
Tensorboard logs: track important metrics over the course of training.
Model cards: document what a model does and its intended use cases.
Community: an easy way to share and collaborate with the community!

To date, there are over 10 thousand fine-tuned Whisper checkpoints on the Hub. Enabling Hub support would grow the Chinese Whisper community further, particularly through the efforts of this repository!

@sanchit-gandhi Thank you for your contribution.

Thank you @yeyupiaoling!


Implement CMAKE

Meh. Regular make is good enough. I made the current makefile a little more concise.


FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.6/dist-packages/deep_daze/data/bpe_simple_vocab_16e6.txt'

I'm trying this out in colab and facing the above error.Here's the full stack:
Traceback (most recent call last):
File "/usr/local/bin/imagine", line 5, in
from deep_daze.cli import main
File "/usr/local/lib/python3.6/dist-packages/deep_daze/init.py", line 1, in
from deep_daze.deep_daze import DeepDaze, Imagine
File "/usr/local/lib/python3.6/dist-packages/deep_daze/deep_daze.py", line 11, in
from deep_daze.clip import load, tokenize, normalize_image
File "/usr/local/lib/python3.6/dist-packages/deep_daze/clip.py", line 223, in
_tokenizer = SimpleTokenizer()
File "/usr/local/lib/python3.6/dist-packages/deep_daze/clip.py", line 64, in init
merges = Path(bpe_path).read_text().split('\n')
File "/usr/lib/python3.6/pathlib.py", line 1196, in read_text
with self.open(mode='r', encoding=encoding, errors=errors) as f:
File "/usr/lib/python3.6/pathlib.py", line 1183, in open
opener=self._opener)
File "/usr/lib/python3.6/pathlib.py", line 1037, in _opener
return self._accessor.open(self, flags, mode)
File "/usr/lib/python3.6/pathlib.py", line 387, in wrapped
return strfunc(str(pathobj), *args)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.6/dist-packages/deep_daze/data/bpe_simple_vocab_16e6.txt'

@Vaibhav21pandit hello! want to try 0.1.7? :crossed_fingers:

@Vaibhav21pandit hello! want to try 0.1.7? :crossed_fingers:

@Vaibhav21pandit how did you run cuda10.2 stuff in colab? I get an error that pytorch and torchvision both have to be in cuda10.2

@Vaibhav21pandit how did you run cuda10.2 stuff in colab? I get an error that pytorch and torchvision both have to be in cuda10.2

@lucidrains can u drop a colab demo ? running 10.2 stuff on colab is difficult fr noobs like me. will tell u to close this issue if my colab nb successfully works with ur latest release.

@lucidrains can u drop a colab demo ? running 10.2 stuff on colab is difficult fr noobs like me. will tell u to close this issue if my colab nb successfully works with ur latest release.

@lucidrains  on colab
/usr/local/lib/python3.8/site-packages/torch/cuda/__init__.py:52: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 10010). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at  /opt/conda/conda-bld/pytorch_1607369981906/work/c10/cuda/CUDAFunctions.cpp:100.)
  return torch._C._cuda_getDeviceCount() > 0
Traceback (most recent call last):
  File "/usr/local/bin/imagine", line 5, in <module>
    from deep_daze.cli import main
  File "/usr/local/lib/python3.8/site-packages/deep_daze/__init__.py", line 1, in <module>
    from deep_daze.deep_daze import DeepDaze, Imagine
  File "/usr/local/lib/python3.8/site-packages/deep_daze/deep_daze.py", line 16, in <module>
    assert torch.cuda.is_available(), 'CUDA must be available in order to use Deep Daze'
AssertionError: CUDA must be available in order to use Deep Daze

!pip list | grep torch
siren-pytorch     0.0.6
torch             1.7.1
torchvision       0.8.2

@lucidrains  on colab
/usr/local/lib/python3.8/site-packages/torch/cuda/__init__.py:52: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 10010). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at  /opt/conda/conda-bld/pytorch_1607369981906/work/c10/cuda/CUDAFunctions.cpp:100.)
  return torch._C._cuda_getDeviceCount() > 0
Traceback (most recent call last):
  File "/usr/local/bin/imagine", line 5, in <module>
    from deep_daze.cli import main
  File "/usr/local/lib/python3.8/site-packages/deep_daze/__init__.py", line 1, in <module>
    from deep_daze.deep_daze import DeepDaze, Imagine
  File "/usr/local/lib/python3.8/site-packages/deep_daze/deep_daze.py", line 16, in <module>
    assert torch.cuda.is_available(), 'CUDA must be available in order to use Deep Daze'
AssertionError: CUDA must be available in order to use Deep Daze

!pip list | grep torch
siren-pytorch     0.0.6
torch             1.7.1
torchvision       0.8.2

@forkbabu i updated the readme with colab links!

@forkbabu i updated the readme with colab links!

@Vaibhav21pandit how did you run cuda10.2 stuff in colab? I get this error -> https://stackoverflow.com/questions/63062741/pytorch-and-torchvision-are-compiled-different-cuda-versions

upgrade your torchvision separately that should solve this

@Vaibhav21pandit how did you run cuda10.2 stuff in colab? I get this error -> https://stackoverflow.com/questions/63062741/pytorch-and-torchvision-are-compiled-different-cuda-versions

upgrade your torchvision separately that should solve this

@Vaibhav21pandit hello! want to try 0.1.7? crossed_fingers

sure, will try and get back

@Vaibhav21pandit hello! want to try 0.1.7? crossed_fingers

sure, will try and get back

Just checked out the simplified notebook with the torchvision+cu101 works flawlessly.Thanks for this implementation @lucidrains

Just checked out the simplified notebook with the torchvision+cu101 works flawlessly.Thanks for this implementation @lucidrains


Settings aren't saved

Roam-highlighter v. <IP_ADDRESS>
Tested in Firefox v. 76 and Chrome v. 85

In a tab, Roam-highlighter panel expanded
Settings set to Obsidian
Hit save
Close browser
Reboot and go back to the same tab
Roam-highlighter has gone back to Roam as its default setting

@arthurjosse i know it’s confusing but for the default settings chooser you need to click “SET” to use those settings. I have changed that all together now and update should be out shortly. Just waiting for chrome store review. Now it will save “onChange” event so as soon as you switch drop down from Roam to obsidian it will save. Also the save button is now greyed out unless there is something to save in which case it turns blue until you click it.
Does that all make sense?

Thanks for your responsiveness and yes it completely makes sense.
I was already clicking on the "set" button but I think it worked as intended: resetting to default settings. It was a misunderstanding from my part.
But still, I have just tested the extension v. <IP_ADDRESS> in Chrome and it seems that not all settings are saved. The line breaks handling is saved but not the way the clipboard is showed. And we can tick both plain text and HTML, or left the two boxes unchecked. Shouldn't they be mutually exclusive? Shouldn't one of them be required? Also, a quick remark: although my monitor is crappy, I can barely see the text placeholders and my inputs have the same style as the placeholders.

“it seems that not all settings are saved.”
Do you specifically mean the plain text and HTML settings? That does not save as the default should show plain text because it’s more human readable. To be honest I’m probably going to remove these items. They are more for me when testing to see what the HTML on clipboard looks like.
“And we can tick both plain text and HTML, or left the two boxes unchecked. Shouldn't they be mutually exclusive? Shouldn't one of them be required?”
See my answer above. Does that help?
“Also, a quick remark: although my monitor is crappy, I can barely see the text placeholders and my inputs have the same style as the placeholders.”
This is great feedback. So are you saying it’s 1) it’s hard to read in general and 2) you can’t tell difference between placeholder text and actual inputted text and would like some more “contrast”/distinction between the two?

OK, got it, my settings are saved.
On my monitor I cannot see the placeholders if I don't lean over the screen. And yes there is no difference between the placeholders and the inputted text. Inputted values are greyed out. And some of the inputs are buggy: see the attached screenshot, the height input value style suddenly appeared, the caret is white and I can't highlight it (by holding down the left click). Can't say if "20%" is the placeholder or the value I've entered. Looks like they're overlaid.

@GitMurf A small question: I changed settings set from Roam Research to Obsidian, it will not be saved. Should I change it again and again when I use it to capture stuff?

Combined into Issue #50


--help fix: mentioning options also in stdin/stdout syntax

When doing node_modules/.bin/node-sass --help, the "Usage" text didn't mention options in the stdin/stdout syntax, but they are there. The example uses them.
This adds a mention of options to the help text.

Tervetola Asko! :tada:


If Attack, Require Reaction Card

It would be great to have the option in the rules to force a reaction card in the set if an attack card is picked.

Interesting idea! This would not have occurred to me.
This would probably be an addition to the Advanced Rules Panel (#43) after it is created.
One thing that does worry me: what to label this filter. Even if I can make it work in a few English words, I'm not sure how well it will translate over (the app is in 5 languages after all).

Push*! Maybe it can also depend that not only the Classic Defense cards are used but also if there are curses a disposal Card is enough. Also it could vary with the strength of the attack if the defence is really required.

@Mark-Lauman Can always start by English (or whatever your primary language is) and others will have to come in and help with translations later


review policy

Hi folks,
do we want some kind of explicit review policy for this repo?
I personally would prefer us to just directly merge typo fixes and the likes
while still requiring someone else to approve/merge anything more complex.
If this seems good to you all the other question is how we want to notify reviewers?
Do we just expect enough people to watch this repo, should we explicitly ping the whole project group
or more selectively try and ping individual people?
I think watching the repo is probably easiest while also allowing some of us to stop
watching the repo in case they do not want to get notified for everything.
cc @rust-lang/project-const-generics

I agree that for now merging small fixes and watching the repository should work for now.

I'm watching the repo. Just like the const-eval repo, I don't expect excessive traffic here and thus will just look at everything that happens

seems good ^^


Rename ThirdPartyNotices

Docs Build status updates of commit afb1957:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/DocsLegal-pr.en-SG, working directory: W:\idpm-s, target branch: HEAD, target branch commit: 2da4e8206aad02e0e063371c729b89c3a5b0e88d, source commit: afb19571b5515dbb0db63d588cc839a0e5be4ddd.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 73ab736:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Various Redstone fixes

This PR fixes two bugs:

Fluids breaking redstone components will now actually cause a redstone update
Redstone torches can now also be placed when there is a redstone dust on the opposite side

:+1: I'll test this out and merge it if it works.

Works, merging.


Daemon mode

Monitor changes to local files and upload to S3.

There are notification frameworks that support multiple platforms, but the events that occur on each platform are too different.
The Linux version is relatively easy to implement, but the MacOS and Windows versions are difficult to implement because the events are too different from Linux and there are few events similar to inotify.
The only version that can be implemented with a high level of reliability is the Linux version.
I don't want to implement it only on individual platforms, so I'm not going to do it now.

I don't want to implement it only on individual platforms, so I'm not going to do it now.


Add an additional escape sequence \e.

This is an idea I had when discussing #945 to avoid the need to support octal escape sequences.
Probably, the only common use for these nowadays is to encode the ESC character (0o33) itself in ANSI escape codes and adding an escape sequence for this will make life a little easier.
It's not a new idea as gcc, clang and tcc already support it as a non-standard extension to their C compilers.
I haven't added a test as the other escape sequences which represent control characters don't seem to have any.

@PureFox48 is it \033 or \33, I suspect you're missing a preceding 0 if using octal.
One alternative is adding \x instead, then ESC become \x1b and it's more general purpose than just \e.

@ruby0x1 the front 0 is optional, the escapes where always octal in all known conventions/implementations.

Yes, @mhermier is correct that the leading 0 is optional since octal escapes can be either 1, 2 or 3 characters following the /.
Wikipedia has a good summary here.
Although \x1b works fine, the reason I wanted to add \e is because you don't then have to remember the code for ESC when writing an ANSI escape code and (apart from \0 which we already have) it's the only common use for octal escapes these days. We wouldn't therefore need to support them as well as octal literals.

Adding \x will need to be done at some point to allow to ease creation of byte arrays, but it is not critical yet (till someone request for it).

We already have \x. See escaping in the docs towards the end of the secton.

Ah ok, I've somehow only ever noticed with a leading 0 but looked it up.
Also I forgot \x was there below. I'll make that table a bit clearer.
Noting that the Wren page also has this line, which hints that escapes aren't too precious or strictly minimal.
"\a" // Alarm beep. (Who uses this?)

Peopole who do console applications, probably wren-cli use it... was not able to run it since a while because of local changes...

Yes, I sometimes use \a myself as it's currently the only way to get a tweet out of Wren without using a game engine :)

Minor note: the new escape wasn't documented in this PR but I added it.
Thanks for the PR, I think I've used escape stuff enough in wren for unit tests, command line tools and logging that it's not unreasonable to making it cleaner considering the low impact of the change.

Excellent, thanks :)


Allow to by-pass by event-types as well (bundle:app:event_type)

Please wait a bit before merging this, I need to discuss the previous PR first.

I'm closing this PR because it won't be needed. @g-duval will open another PR to restrict the org ID validation to OCM events only.

@josejulio https://github.com/RedHatInsights/notifications-gw/pull/390 should solve your issue


feat(#3843): Add support for CanvasState.reset

Resolves issue #3843
Documented method according to https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/reset

Not exactly sure if i need to put a notice into the changelog. Ill leave it at this for now.

Ok with that, its ready for review now i think

@daxpedda good enough?


Ability to paginate based on last id/last timestamp

The idea is to handle pagination when the user of the gem doesn't want duplicates between pages (for example, if one object is created between both requests)

Next version


Support for Named Pipe connection

Support for a named pipe connection, so that java application can connect to LocalDB instance.

Hi @robustsoftware, support for named pipes is in our backlog but there is no timeline for it at this time. You can refer to #769 for the discussion that took before.

Any timing on this issue?

No. This item is still in the backlog but has no timeline associated with it.
Regards,
David


:construction_worker: (gomod) go mod tidy automatically

Codecov Report

Merging #10 (922074f) into main (a8460f4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          143       143
=========================================
  Hits           143       143


Current working directory is not used when I point to webpack.config.js in sibling directory

Do you want to request a feature or report a bug?
Request a feature, even though it migth be there already but I just don't know how to set it up.

What is the current behavior?

Basically I have webpack.config.js stored in different directory, not the child or parent, but sibling directory.
I'm using the --config switch to point to it and webpack finds it and reads from it.
However it gives an error when this line is read for example:
const CircularDependencyPlugin = require('circular-dependency-plugin');
Error says that it cannot find CircularDependencyPlugin.
It seems that webpack is looking for the node_modules in the directory where webpack.config.js is found and not in current working directory.
So when I work in app root directory and from it invoke webpack which points to webpack.config.js in sibling directory seems that this other directory is used by webpack to look for the node_modules.
Having duplicate node_modules in sibling directory is not an option.
What is the expected behavior?
I would like for webpack to use current working directory for node_modules lookup and do everything there even though I point to another webpack.config.js file in sibling directory with --config switch.
Is there any way to set it up to behave just like in cases when webpack.config.js is stored in current working directory?
If this is a feature request, what is motivation or use case for changing the behavior?
I have multiple different applications and they all have same file structure. I also have two versions of webpack.config.js, one for development bundling and one for production.
I will be using npm to abstract webpack bundle commands. In package.json I want to have two commands for bundling, in each I plan to use --config switch to point to the prod or dev webpack.config.js.
Right now I have to delete and replace webpack.config.js in current working directory every time I want to switch from development build to production build and vice versa. And I have to do that for every separate application.
What I want to do is cd to root directory of the app I'm working on, each app would have package.json with webpack bundle commands. Those would point to dev and prod webpack.config.js files in sibling directory, not the parent but side by side directory with other apps directories.
This way I could pack for dev or prod without copying config files.
Due to nature of this project, yes webpack.config.js files (dev and prod versions) can be universal for each app.
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Node.js 6.11.12, webpack 3.4.1, OS win 10 amd64

webpack uses node resolution algorithm. If your file is located at ./foo/bar/config.js, the following directories will be tested:

./foo/bar/node_modules/
./foo/node_modules/
./node_modules/ (webpack is here)

It seems that webpack is looking for the node_modules in the directory where webpack.config.js is found and not in current working directory.

That sounds like a correct behaviour.

Yes true, that is correct behaviour, but is there any way to tell webpack to use current working directory even when it comes to reading from config file in sibling directory?
So it treats that sibling directory only as a place where it reads config file from and nothing more?

Good idea.
I'm not that experienced in webpack so I haven't thought of that nor did I know that you can merge webpack config files.
Would you use webpack-merge or something else?

Yes, you would use webpack-merge. Basic usage would look something like this, this would live in your root
var merge = require('webpack-merge)
var appConfig = require('../path/to/config') // app-specific config

var webpackConfig = merge(appConfig, {
    // your base webpack config
}

module.exports = webpackConfig

I'm definitely gonna try that, thanks!
It is actually better solution than my original idea.
So basically when you do:
var webpackConfig = merge(appConfig, {     // your base webpack config }
webpack-merge merges all the plugins in plugins[] object member, as well as other entries in object.
And you can go in both directions?
Merge from base to dev/prod or from dev/prod to base.
Here is documented latter (from dev/prod to common) https://webpack.js.org/guides/production/
I need to merge from common to dev/prod.

Absolutely you can merge in either direction. You can pass in objects
directly as arguments pass in an array of objects to merge into a new
object. There's more details on it here:
https://github.com/survivejs/webpack-merge/blob/master/README.md
On Wed, Mar 28, 2018, 11:13 AM Toni Romic<EMAIL_ADDRESS>wrote:

I'm definitely gonna try that, thanks!
It is actually better solution than my original idea.
So basically when you do:
var webpackConfig = merge(appConfig, { // your base webpack config }
webpack-merge merges all the plugins in plugins[] object member, as well
as other entries in object.
And you can go in both directions?
Merge from base to dev/prod or from dev/prod to base.
Here is documented latter (from dev/prod to common)
https://webpack.js.org/guides/production/
I need to merge from common to dev/prod.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/6865#issuecomment-376922874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDDrPYwuoj9t1kyWut1nF-JVwPny7bBks5ti6h6gaJpZM4S7VPJ
.

Thanks.
Do you know how and which variable to set in the base config file so I can dynamically merge one or the other file, for dev or prod? Depending is the variable set for, let's say "production" or not.

This might help point you in the right direction.
https://medium.com/@justintulk/passing-environment-variables-into-your-code-with-webpack-cab09d8974b0


11/12/2018 00:54 : Create Pull Request for branch master -> prTesting1_2018111200

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


I'd like to know how to change the font in the file.  I can't seem to find the code block for that.

You can change them in the css file:

You can change them in the css file:

Got it!  Also noticed that the expand / collapse arrow is missing from the search area?

Got it! Also noticed that the expand / collapse arrow is missing from the search area?

I have fixed the bug in previous version, so you can update the theme either in Community Themes by clicking “use” button again in obsidian software, or download the css file in Releases page on Github and manually activate the theme.

Got it! Also noticed that the expand / collapse arrow is missing from the search area?

I have fixed the bug in previous version, so you can update the theme either in Community Themes by clicking “use” button again in obsidian software, or download the css file in Releases page on Github and manually activate the theme.

I am sorry that the last version caused the problem which I overlooked. Now I have fixed that. Thank you for your report.

I am sorry that the last version caused the problem which I overlooked. Now I have fixed that. Thank you for your report.

Fixed. Will be released in the next version. Thank you.


Configure update checker on installation page

I recently became aware that this was enabled by-default, I don't necessary agree with that and this should rather be configured by the user(this patch does that on the installation page) as it connects to a homeserver, which I'd prefer to avoid on my instance.

Should we mark this as breaking?

I think this is reasonable, but I'm wondering if it should be more prominent on the page.
Given Gitea usually fixes a few security issues between releases, staying up to date is important.

but I'm wondering if it should be more prominent on the page.

We can move it to the general section, which is not hidden under a <summary>.

43b4a9e6fcc1cb9038a6881b740ce662422b14df moved it to the General section, updated the screenshot accordingly.

Why not check it by default so that will be no break?

Why not check it by default so that will be no break?

It wouldn't break for new instances(as they can explicitly configure this option), but existing instances who follow the default value of the code will "break", as the update checker will now be disabled by-default.

Why not check it by default so that will be no break?

It wouldn't break for new instances(as they can explicitly configure this option), but existing instances who follow the default value of the code will "break", as the update checker will now be disabled by-default.

Like @jolheiser said, default check because we want the default values are security when possible. Both privacy and security are very important for users, we need a balance here.

we need a balance here.

I agree, but I think the privacy aspect is more important here (especially because it was enabled without notice, in my opinion) than the security aspect. We should encourage it, as such I moved it to the general area, and I can even make it check by default. However, enabling this should be entirely up to the user.

we need a balance here.

I agree, but I think the privacy aspect is more important here (especially because it was enabled without notice, in my opinion) than the security aspect. We should encourage it, as such I moved it to the general area, and I can even make it check by default. However, enabling this should be entirely up to the user.

I can't agree this privacy is more important than security, because it will only expose your IP address. If the instance is a public instance, the IP address of course has been exposed by himself. If the instance is not a public one, it should be behind at some public gateway, so the IP is that gateway's not this machine. I agree this PR is necessary to let user chose but we need to remind what's the option meaning.

I think making this disabled by default when there is no config is too breaking. People will have relied on this functionality and therefore changing the default is a BREAKING change and hence a bad thing no matter what your views of whether update-checkers should be running by default or not.
Therefore as questionable as it is that it is enabled by default and I missed that it had been set that way - it has been this way for a long time and therefore we have to leave it that way for those users.

I certainly agree that making an option on the install page is very helpful and useful and should have been there from the start.

It would however be easy to make it default to disabled for new installs:

Set the app.ini templates for the dockers to have [cron.update_checker] ENABLED=false set
Set the default in the install page to set this checkbox to false.

Alright seems like more people agree on leaving it enabled, rolling that particular code back. https://github.com/go-gitea/gitea/pull/21655/commits/c47cd923ffa9e88893d34dd0ce5e21ab85c513c7

Thanks for this PR @Gusted, as you can see from the original PR I wanted it to be disabled, however both @lafriks and @6543 requested it be made enabled by default.
I also added in a privacy enabling section, so if people didn't want to check the dl.gitea.io site, they could also check an alternative json file fully under their control.

The UI is broken.
The box should be in the same line of the text.

https://github.com/go-gitea/gitea/pull/21660


[FEATURE] Upgrade support of audit and event log

Is your feature request related to a problem? Please describe.

Requirement:
https://github.com/harvester/harvester/issues/577
https://github.com/harvester/harvester/issues/578
logging, event and audit will be enabled by default in v1.1.0, how about the upgrade?
Describe the solution you'd like

Add upgrade of logging, event and audit.

Describe alternatives you've considered

Manually deploy related resources after upgrading.
Additional context

HEP PR:
https://github.com/harvester/harvester/pull/2684
HEP 578 event and audit log
backend code PR:
https://github.com/harvester/harvester/pull/2844

For upgrade case, if UI can't get the related Logging CRDs, its pages should still work properly but adding a proper warning message, cc @WuJun2016

Could you provide steps for displacing available logging crd to unavailable, thanks!
@w13915984028
Expected behavior:

navi tabs should be visible if there is no logging crd.
warning tips should be visible on logging resource list pages.

UI PR has been merged.
The current design:
if there is missing crd

I am going to be unassigned, if you have any concerns, just let me know.
@w13915984028 @guangbochen

Singe node upgrade check

Check the following files and pods have no error

[ ] logging related pods
n1-103:~ # kubectl get pods -n cattle-logging-system
NAME                                                      READY   STATUS      RESTARTS      AGE
harvester-default-event-tailer-0                          1/1     Running     3 (39m ago)   69m
rancher-logging-574448c578-lhvbd                          1/1     Running     3 (39m ago)   70m
rancher-logging-kube-audit-fluentbit-7kq99                1/1     Running     3 (39m ago)   69m
rancher-logging-kube-audit-fluentd-0                      2/2     Running     6 (39m ago)   70m
rancher-logging-kube-audit-fluentd-configcheck-ac2d4553   0/1     Completed   0             70m
rancher-logging-rke2-journald-aggregator-4f9jl            1/1     Running     3 (39m ago)   70m
rancher-logging-root-fluentbit-tcd7z                      1/1     Running     3 (39m ago)   69m
rancher-logging-root-fluentd-0                            2/2     Running     6 (39m ago)   69m
rancher-logging-root-fluentd-configcheck-ac2d4553         0/1     Completed   0             70m

[ ] kube-audit files

[ ] config file exists
n1-103:~ # cat /etc/rancher/rke2/config.yaml.d/90-harvester-server.yaml
cni: multus,canal
cluster-cidr: <IP_ADDRESS>/16
service-cidr: <IP_ADDRESS>/16
cluster-dns: <IP_ADDRESS>
tls-san:
  - <IP_ADDRESS>
audit-policy-file: /etc/rancher/rke2/config.yaml.d/92-harvester-kube-audit-policy.yaml

n1-103:~ # cat /etc/rancher/rke2/config.yaml.d/92-harvester-kube-audit-policy.yaml
apiVersion: audit.k8s.io/v1
kind: Policy
omitStages:
  - "ResponseStarted"
  - "ResponseComplete"
rules:
  # Any include/exclude rules are added here
  # A catch-all rule to log all other (create/delete/patch) requests at the Metadata level
  - level: Metadata
    verbs: ["create", "delete", "patch"]
    omitStages:
      - "ResponseStarted"
      - "ResponseComplete"

[ ] /oem/99_custom.yaml is patched
n1-103:~ # grep "92-harvester" /oem/99_custom.yaml -5
            cluster-cidr: <IP_ADDRESS>/16
            service-cidr: <IP_ADDRESS>/16
            cluster-dns: <IP_ADDRESS>
            tls-san:
              - <IP_ADDRESS>
            audit-policy-file: /etc/rancher/rke2/config.yaml.d/92-harvester-kube-audit-policy.yaml
          encoding: ""
          ownerstring: ""
        - path: /etc/rancher/rke2/config.yaml.d/90-harvester-agent.yaml
          permissions: 384
          owner: 0
--
              valuesContent: |-
                flannel:
                  iface: harvester-mgmt
          encoding: ""
          ownerstring: ""
        - path: /etc/rancher/rke2/config.yaml.d/92-harvester-kube-audit-policy.yaml
          permissions: 384
          owner: 0
          group: 0
          content: |
            apiVersion: audit.k8s.io/v1

vim /oem/99_custom.yaml

- path: /etc/rancher/rke2/config.yaml.d/92-harvester-kube-audit-policy.yaml
          permissions: 384
          owner: 0
          group: 0
          content: |
            apiVersion: audit.k8s.io/v1
            kind: Policy
            omitStages:
              - "ResponseStarted"
              - "ResponseComplete"
            rules:
              # Any include/exclude rules are added here
              # A catch-all rule to log all other (create/delete/patch) requests at the Metadata level
              - level: Metadata
                verbs: ["create", "delete", "patch"]
                omitStages:
                  - "ResponseStarted"
                  - "ResponseComplete"
          encoding: ""
          ownerstring: ""

Check the UI of Monitoring & Logging work as in fresh installed cluster after upgrade to v1.1.0-rc2

Cluster Outputs

Cluster Flows

Logging configuration

Outputs

Flow

Monitoring configuration - Altermanager

Altermanager config

Check the audit and event log have applied after upgrading from v1.0.3 to v1.1.0-rc2 in above test plans.
Close this issue


Why did use refiner model in test.py?

both random model and refiner model used.
I'm curious to refiner model.

Refiner model helps you merge the results in a line

Refiner model helps you merge the results in a line

ah ha, ok thank you


HTTP client: Fix cleanup of TLS BIO via bio_update_fn callback

Make app_http_tls_cb() tidy up on disconnect the SSL BIO it pushes on connect. Make OSSL_HTTP_close() respect this.
In this way the unclean workaround using BIO_free_all() is removed.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged - thanks @paulidale


failed to process “api_def_Conv2D.pbtxt”: Attribute explicit_paddings not defined in base api for Conv2D

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  -
Mac OS X 10.13.6
TensorFlow version (use command below): -

tf.VERSION = 1.12.0
tf.GIT_VERSION = v1.12.0-rc2-3-ga6d8ffae09
tf.COMPILER_VERSION = v1.12.0-rc2-3-ga6d8ffae09
Sanity check: array([1], dtype=int32)

Python version:
Python 3.6.5

Describe the current behavior
Hi, I try to run tensorflow using golang,
When I execute the following command: go generate github.com/tensorflow/tensorflow/tensorflow/go/op
I get this error:
2019/01/27 18:21:15 failed to process “api_def_Conv2D.pbtxt”: Attribute explicit_paddings not defined in base api for Conv2D
exit status 1
op/generate.go:18: running “go”: exit status 1

@asimshankar Can you PTAL? Thanks

This is because your local libtensorflow.so has been compiled against older tree, which doesn't include commit ec81825aaf7e848d9f8ddffdf1e0d20aebe9172c which introduced this new attribute

@davidgtunity
Is this still an issue for you? Did you try this suggestion?

This is because your local libtensorflow.so has been compiled against older tree, which doesn't include commit ec81825 which introduced this new attribute

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Use context managers for file I/O

Description
To ensure proper file handling and avoid potential issues, we should use context managers when working with files. This will automatically close files after use, preventing resource leaks.
Example
In the load_yaml() function, replace open(file).read() with with open(file) as f: f.read().
def load_yaml(file: str) -> dict[str, Any]:
...
    try:
        with open(file) as f:
            return load(f.read(), Loader=SafeLoader)
...

Solved in commit https://github.com/LangTrans/LangTrans/commit/4b228da18a12433c21ddeba8aced5a37b709c41c


hyperboloid calculator

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
i wud like to add it

closing as this feature already exists


Use loguru, not logging module

Convert from logging module to loguru.
Loguru deps dont have conflict or adds any ML-specific libraries that will collide.

We should probably bound the version of loguru to prevent against upstream vulnerabilities

Ok good point. loguru is helpful on our side, but this repo is for vllm inference.
I can map which part of vllm uses what part of compressed_tensors. but its best not to add extra dependencies.
vllm doesnt use loguru
Ill close this for now


Add Plutus Version Column & consolidated level of open source column

In this I added the Plutus Version column, and consolidated the "Level of open source" column into the renamed "Open Source" column as a value enclosed in parentheses.
The idea from here would be for each project to start to have the '?' in the 'Plutus Version' column replaced by 'v1' or 'v2' etc. - by whoever can assert that a given project is currently published to mainnet with the given Plutus version.

Now that the community is ALSO becoming very aware of the desire to be on Plutus v2.

Cool. Seems reasonable.


Add a Comment Section

Add a section where the user can comment on someone memory

I would Like to work on this.

I would Like to work on this.

@sanjay270899 first complete the user profile part then I will assign it to you

@sanjay270899 first complete the user profile part then I will assign it to you

can i work on this issue

can i work on this issue

This issue can only be done after the USer profile section is implemented

This issue can only be done after the USer profile section is implemented

Go ahead @kenkirito

When a user comments his corresponding image and name should be shown

You can refer to Instagram for a better understanding

@Tejas1510 working on it

@kenkirito what is the progress?

@Tejas1510 I would Like to work on this.

Go ahead @sanjay270899


Can't use ky to make REST requests

Description
Hey! I am trying to use ky(https://www.npmjs.com/package/ky) to make REST calls from my extension but anytime I even import ky, I receive the following error:
TypeError: globalThis.Request is not a constructor
constants.ts:10:19
Object.<anonymous>:index.js:142:3
Module._compile:loader:1149:14
Module._extensions..js:loader:1203:10

This constants.ts file appears to be used by a package or maybe Raycast, not sure since it's the only output I get.
import ky from "ky";
import {BASE_URL, REFRESH_TOKEN} from "../const";

export const getAccessToken = async (): Promise<{ access_token: string }> => {
    return ky.post(`${BASE_URL}/auth/token`, {
        json: {
            refresh_token: REFRESH_TOKEN
        }
    }).json();
}

Steps To Reproduce

Install ky and import it.

Current Behaviour
Receiving the following error:
TypeError: globalThis.Request is not a constructor
constants.ts:10:19
Object.<anonymous>:index.js:142:3
Module._compile:loader:1149:14
Module._extensions..js:loader:1203:10

Expected Behaviour
Should make the request free of error.

From ky's README:

Ky targets modern browsers and Deno. For older browsers, you will need to transpile and use a fetch polyfill and globalThis polyfill. For isomorphic needs (Node.js + browser, like SSR), check out ky-universal.

You need to use packages compatible with Node.js


AttributeError: 'NoneType' object has no attribute 'get_function'

Description
Hi,
I was trying to implement a custom torch.autograd.Function by following this example: https://github.com/sniklaus/pytorch-extension/blob/master/hadamard.py and I tried to run it and found an error related to the cupy.cuda.compile_with_cache method:
AttributeError: 'NoneType' object has no attribute 'get_function'

On my main machine, it was working perfectly but since today nothing is working and I get the bug. (on my cluster machine it's the same bug and has never worked).
Do you have any clues on how to solve this bug please?
Also, do you think the example that I cited before is still relevant ? And if you have any tips with CuPy that would be really cool thank you! (Tips related to PyTorch + CuPy)
To Reproduce
cupy_cell_forward = """
    extern "C" __global__ void cupy_cell_forward(
    float* at, int size
    ) {
        int tid = blockDim.x * blockIdx.x + threadIdx.x;

        if (tid < size) {
            at[tid] = 0.0;
        }
    }
"""

@cupy.memoize(for_each_device=True)
def cunnex(strFunction):
    return cupy.cuda.compile_with_cache(globals()[strFunction]).get_function(strFunction)

cunnex("cupy_cell_forward")

then after that I do my stuff with the torch.autograd.Function
Installation
Conda-Forge (conda install ...)
Environment
Main machine:
OS                           : Linux-5.11.0-46-generic-x86_64-with-glibc2.17
Python Version               : 3.8.12
CuPy Version                 : 10.0.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.22.0
SciPy Version                : None
Cython Build Version         : 0.29.25
Cython Runtime Version       : None
CUDA Root                    : /home/adel/miniconda3/envs/speechbrain-dev
nvcc PATH                    : /usr/bin/nvcc
CUDA Build Version           : 11020
CUDA Driver Version          : 11050
CUDA Runtime Version         : 11050
cuBLAS Version               : (available)
cuFFT Version                : 10600
cuRAND Version               : 10207
cuSOLVER Version             : (11, 3, 2)
cuSPARSE Version             : (available)
NVRTC Version                : (11, 5)
Thrust Version               : 101000
CUB Build Version            : 101000
Jitify Build Version         : 7db7a57
cuDNN Build Version          : None
cuDNN Version                : None
NCCL Build Version           : None
NCCL Runtime Version         : None
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : NVIDIA GeForce RTX 3080 Ti
Device 0 Compute Capability  : 86
Device 0 PCI Bus ID          : 0000:05:00.0

cluster machine
OS                           : Linux-4.15.0-151-generic-x86_64-with-debian-buster-sid
Python Version               : 3.7.9
CuPy Version                 : 10.0.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.20.0
SciPy Version                : 1.7.3
Cython Build Version         : 0.29.22
Cython Runtime Version       : 0.29.22
CUDA Root                    : /usr/local/cuda
nvcc PATH                    : /usr/local/cuda/bin/nvcc
CUDA Build Version           : 10020
CUDA Driver Version          : 11000
CUDA Runtime Version         : 10020
cuBLAS Version               : (available)
cuFFT Version                : 10102
cuRAND Version               : 10102
cuSOLVER Version             : (10, 3, 0)
cuSPARSE Version             : (available)
NVRTC Version                : (10, 2)
Thrust Version               : 100907
CUB Build Version            : <unknown>
Jitify Build Version         : <unknown>
cuDNN Build Version          : None
cuDNN Version                : None
NCCL Build Version           : 2506
NCCL Runtime Version         : 2804
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : Tesla V100S-PCIE-32GB
Device 0 Compute Capability  : 70
Device 0 PCI Bus ID          : 0000:00:08.0

Additional Information
No response

This is a duplication of #6231, which will be fixed in v10.1.0. Note that compile_with_cache is marked as deprecated (and it's an internal API) so please try to avoid it, see here. For torch.autograd.Function examples see here.


Fix naming of PDB files for sfml-main

Description

sfml-main is always a static lib but shouldn't have -s postfix
The PCH target says in the comment that it uses sfml-s, but then used sfml-system

Someone asked for help with SFML on the forum and looking at the output, I realized that the naming of the PDB file(s) aren't correct.
What I don't know if sfml-s is useful in the PCH case, as it might not be automatically discovered.
Edit: Looks like it should be name sfml-system(-d), so I adjusted the message instead
Tasks

[x] Tested on Windows

How to test this PR?
The outputted PDB should have the correct naming

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 57.022%

Totals

Change from base Build<PHONE_NUMBER>2:
0.006%

Covered Lines:
12054

Relevant Lines:
19987

💛  - Coveralls


Boldly provide default maps?

So splitjoin.vim is pretty slick, and I feel like it deserves to claim a couple of maps. This would of course reduce friction for new users, and also make it easier for "distributions" like Janus to ship it by default. As a frequent pair programmer, I care about both of these greatly.
I'd imagine you'd agree that sj and sk are nonstarters (take it from the guy that used to map s in surround.vim). And leader maps are pretty lame. But there's still plenty of good options. You could pick a pair like cS and cJ (or cJ and cK, if that feels more natural), and have virtually zero chance of stepping on anyone, ever.
Think about it!

@tpope, I've had some (admittedly rare) issues with the gJ fallback, like #72. I think there was one more, but I have no memory of any details, just that there was one :). I can't figure out what the problem might be, though, so I'm thinking maybe I should just remove the "smart" functionality of gJ. It feels like not that many people would care (or really, even know) about this. What do you think?

Without even trying to understand that issue, would it be possible to leave the gJ fallback in place only for file types with zero splitjoin support?

 I just figured out the problem, and it's extremely easy to fix. Sorry to bother you :).