wifi name of turtlebot4 change to clear6b and turtlebot wifi didn't apper at all

Please provide the following information:

OS: (e.g. Ubuntu 22.04
ROS : (e.g. humble)
Built from installed:

Expected behavior
so basically I was working to connect the robot to my computer and it connected successfully after that I try to send the wifi and the name of the main wifi to the robot to connect both robot and laptop to the same wifi after sending the information to the robot I didn't know if he receives it or not so I try to do that after switching it off and try again so the wireless name in the robot change from 'turtlebot4'
to 'clear6bbr'
note that before sending the information I was able to see the data of the robot but after switching it off the robot change to another wifi name as I mentioned

I'm not entirely sure I've captured your problem accurately, but it appears that you might have initially connected to the Turtlebot on access point mode, modified the Wi-Fi configurations, and lost the connection. One potential solution is to use an Ethernet cable to SSH into the Raspberry Pi.

Hi @Hanbali11,
My understanding is that you are running humble and thus used the turtlebot4-setup tool to configure your wifi credentials. When doing this, are you sure that you changed the robot from access point mode to client mode? If you left the robot in access point mode but changed the SSID and password, then the turtlebot will continue to broadcast its own network and adopt the new ssid and password that you entered. This could cause problems if there is already a network with this SSID.
Please connect to the turtlebot using the recovery instructions. Launch the turtlebot4-setup tool again and ensure that the Wi-Fi Setup settings show the mode as client

If you change any settings then ensure to apply the settings.

I  did what the recovery instruction say ,but the result came like ''$ ssh<EMAIL_ADDRESS>ssh: connect to host <IP_ADDRESS> port 22: Connection refused''

@Hanbali11 Can you restart by re-imaging the raspberry pi. Once you have it up and running again, ensure to follow the wifi set up instructions that correspond with the ros-distro that you are running (humble or galactic). As you run through this keep very detailed information on exactly what you do / run and then if you run into any issues give me the details here (include the name of which image you use and specific terminal outputs at each step).
It is possible that the origin of your issues was running the wrong wifi set up instructions for your ROS distro.

thank you


Enhance the list of attributes for creating storage

Hi Team,
I want to use AzureFile storage as a custom StorageClass to store the broker data and logs.  Can you please provide attributes to specify the storage account to be used and the PV naming format, by adding the following fields under storage.
storageAccountName - To specify a name for the Storage account under which the PV has to be created. Example: storageAccountName: broker-storage
pvNamePrefix - To specify a constant prefix for the PV names that are created. The actual PV name should be {pvNamePrefix}-pv-{index}. Example: pvNamePrefix : test-artemis-broker, and the PVs as per the artemis stateful set should be created as test-artemis-broker-pv-0.
deploymentPlan:
  storage:
    size: "5Gi"
    storageClassName: azureFile
    storageAccountName: <To be added>
    pvNamePrefix: <To be added>

Thanks.

The storageAccountName vs pvNamePrefix results in a hybrid. For the name option, the operator cannot enhance name while for the name prefix option, the operator can enhance name.
I'd suggest to align them:
storageAccountNamePrefix: To specify a name prefix for the Storage account under which the PV has to be created.
Example:
storageAccountNamePrefix: test-storage

The operator is free to name account e.g. test-storage-6d4cd707-7d14-414d-bd18-23eea00263e4 which is both human-friendly and it allows the operator to generate an unique name if needed.
pvNamePrefix: To specify a constant prefix for the PV names that are created. The actual PV name should be {pvNamePrefix}-{operators-naming}.
Example:
pvNamePrefix : test-broker

The operator is free to name PVs e.g. as test-broker-pv-0, test-broker-pv-1, test-broker-pv-2, ....
which is both human-friendly and it allows the operator to generate an unique name if needed.


Class attributes missing

The article omits attributes of ExchangeRateProviderOanda class, without any explanation.
My understanding is that ExportAttribute('Microsoft.Dynamics.ApplicationSuite.FinancialManagement.Currency.Framework.IExchangeRateProvider') is necessary for the provider to work - ExchangeRateProviderFactory.loadProviders() looks
for it. It's called when adding a provider through GUI (General ledger > Currencies > Configure exchange rate providers > New). Therefore the solution is incomplete.
I also believe (although I'm not completely sure) that ExportMetadataAttribute isn't needed anymore, therefore it's not something which must be added to demonstrated solution, but it would be good to mention why the article doesn't match actual code of F&O.

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

ID: ac12066f-98e2-9fa2-e27e-ffc00572a6c6
Version Independent ID: a42faab9-c4e7-38c5-e2fc-fd20d32de8fe
Content: Create exchange rate providers - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/financial/create-exchange-rate-providers.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @RobinARH
Microsoft Alias: jbye

@goshoom, thank you for this feedback.
@RobinARH, please review.

Bug 443470 has been logged to track this issue.

updated doc.

Closing, as Ryan updated the content.


pt-BR translation contribution

Fully translated til line 538 and other small corrections.

Thank you @danilofjr for your contribution! I've left my thoughts and some Portuguese phrases that I think could be improved.

Thanks @paulo-graca for the comments and suggestions!

Thank you @danilofjr , can you please address the comments that we both agree on?


DNS resolution issues on CoreDNS + Windows 1803

Is this a request for help?: Yes

Is this an ISSUE or FEATURE REQUEST? (choose one): Issue

What version of acs-engine?: v0.24.2

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm): Kubernetes v1.12.1
What happened: When deploying my hybrid Linux / Windows cluster pods on my Windows nodes are unable to communicate by their svc names. I can query them however by giving the full specification. This is not a caching issue however as running ipconfig /flushdns does not fix this issue.
What you expected to happen: That pods on the windows nodes are successfully able to communicate with one another using their service names.
How to reproduce it (as minimally and precisely as possible): Cluster Spec is given below.
{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorRelease": "1.12",
      "kubernetesConfig": {
        "addons": [
          {
            "name": "tiller",
            "enabled" : true
          },
          {
            "name": "kubernetes-dashboard",
            "enabled" : true
          },
          {
            "name": "rescheduler",
            "enabled" : true
          }
        ]
      }
    },
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "k8s-acs-stc-innovation",
      "vmSize": "Standard_D4s_v3",
      "OSDiskSizeGB": 200,
      "vnetSubnetId": "/subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Network/virtualNetworks/k8s-vnet/subnets/ContainerMaster",
      "firstConsecutiveStaticIP": "<IP_ADDRESS>",
      "vnetCidr": "<IP_ADDRESS>/24"
    },
    "agentPoolProfiles": [
      {
        "name": "linuxpool1",
        "count": 3,
        "customNodeLabels": {
          "os": "linux"
        },
        "vmSize": "Standard_D8s_v3",
        "OSDiskSizeGB": 200,
        "storageProfile" : "ManagedDisks",
        "availabilityProfile": "AvailabilitySet",
        "vnetSubnetId": "/subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Network/virtualNetworks/k8s-vnet/subnets/ContainerAgent"
      },
      {
        "name": "windowspool1",
        "count": 1,
        "customNodeLabels": {
          "os": "windows"
        },
        "osType": "Windows",
        "vmSize": "Standard_D8s_v3",
        "OSDiskSizeGB": 200,
        "storageProfile" : "ManagedDisks",
        "availabilityProfile": "AvailabilitySet",
        "vnetSubnetId": "/subscriptions/XXXX/resourceGroups/XXXX/providers/Microsoft.Network/virtualNetworks/k8s-vnet/subnets/ContainerAgent"
      }
    ],
    "linuxProfile": {
      "adminUsername": "azureuser",
      "ssh": {
        "publicKeys": [
          {
            "keyData": "ssh-rsa XXXX"
          }
        ]
      }
    },
    "windowsProfile": {
      "adminUsername": "azureuser",
      "adminPassword": "XXXX"
    },
    "servicePrincipalProfile": {
      "clientId": "XXXX",
      "secret": "XXXX"
    }
  }
}

Anything else we need to know: N/A

Core DNS + Kube Proxy
❯ kubectl logs coredns-94c9c9c86-lbcvc -n kube-system                                                                                (k8s-acs-stc-innovation/default)
.:53
2018/11/06 02:35:18 [INFO] CoreDNS-1.2.2
2018/11/06 02:35:18 [INFO] linux/amd64, go1.11, eb51e8b
CoreDNS-1.2.2
linux/amd64, go1.11, eb51e8b
2018/11/06 02:35:18 [INFO] plugin/reload: Running configuration MD5 = 18863a4483c30117a60ae2332bab9448

~
❯ kubectl logs kube-proxy-blkd9 -n kube-system                                                                                (k8s-acs-stc-innovation/default)
W1106 01:49:32.637970       1 server.go:194] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
E1106 01:49:32.908945       1 proxier.go:445] Failed to read file /lib/modules/4.15.0-1025-azure/modules.builtin with error open /lib/modules/4.15.0-1025-azure/modules.builtin: no such file or directory
W1106 01:49:32.962247       1 proxier.go:458] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1106 01:49:32.963263       1 proxier.go:458] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1106 01:49:32.964081       1 proxier.go:458] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1106 01:49:32.965026       1 proxier.go:458] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1106 01:49:32.966275       1 proxier.go:458] Failed to load kernel module nf_conntrack_ipv4 with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1106 01:49:33.021176       1 server_others.go:295] Flag proxy-mode="" unknown, assuming iptables proxy
I1106 01:49:33.297664       1 server_others.go:148] Using iptables Proxier.
I1106 01:49:33.297975       1 server_others.go:178] Tearing down inactive rules.
I1106 01:49:33.358311       1 server.go:447] Version: v1.12.1
I1106 01:49:33.365874       1 conntrack.go:98] Set sysctl 'net/netfilter/nf_conntrack_max' to 262144
I1106 01:49:33.366036       1 conntrack.go:52] Setting nf_conntrack_max to 262144
I1106 01:49:33.366170       1 conntrack.go:98] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400
I1106 01:49:33.366367       1 conntrack.go:98] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_close_wait' to 3600
I1106 01:49:33.366618       1 config.go:202] Starting service config controller
I1106 01:49:33.366640       1 controller_utils.go:1027] Waiting for caches to sync for service config controller
I1106 01:49:33.366675       1 config.go:102] Starting endpoints config controller
I1106 01:49:33.366738       1 controller_utils.go:1027] Waiting for caches to sync for endpoints config controller
I1106 01:49:33.466839       1 controller_utils.go:1034] Caches are synced for service config controller
I1106 01:49:33.466924       1 controller_utils.go:1034] Caches are synced for endpoints config controller

@CecileRobertMichon

I have also tried the following fix to no avail:
FROM Microsoft/windowsservercore
SHELL ["powershell', "-Command", "$ErrorActionPreference = 'Stop';"]
New-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters' -Name MaxCacheTtl -Value 0 -Type DWord
New-ItemPropery -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters' -Name MaxNegativeCacheTtl -Value 0 -Type DWord

❯ kubectl get configmap coredns -n kube-system -o yaml                                                                                (k8s-acs-stc-innovation/default)
apiVersion: v1
data:
  Corefile: |
    .:53 {
        errors
        health
        kubernetes cluster.local in-addr.arpa ip6.arpa {
            pods insecure
            upstream
            fallthrough in-addr.arpa ip6.arpa
        }
        prometheus :9153
        proxy . /etc/resolv.conf
        cache 30
        loop
        reload
        loadbalance
    }
kind: ConfigMap
metadata:
  creationTimestamp: 2018-10-30T12:27:27Z
  labels:
    addonmanager.kubernetes.io/mode: EnsureExists
  name: coredns
  namespace: kube-system
  resourceVersion: "374"
  selfLink: /api/v1/namespaces/kube-system/configmaps/coredns
  uid: 298abc17-dc3f-11e8-9776-000d3af4a508

your screenshot shows a successful DNS lookup but failed ping. Can you access services over TCP/UDP?

This is using Azure CNI version 1.0.12 I presume.

Does resolve-dnsname kubernetes work?
Does service access (via IP) work?

Hey @daschott sorry for the delay.
      : No
   Autoconfiguration Enabled . . . .  : Disabled

Thx. Can you try moving to Azure CNI 1.0.13 and otherwise, is the DNS resolution not working only sometimes? If you still see this issue on Azure CNI 1.0.13, can you try to remove <IP_ADDRESS> from the CNI conf file ?

Sounds good, thanks so much for your help! Will report back :)

@sylus Can you try 1.0.14.? It was released recently and should have a fix for missing policy regression in 1.0.13:
https://github.com/Azure/azure-container-networking/releases/tag/v1.0.14

Oh exciting will do!

Any feedback about Azure CNI 1.0.14, is this working now ?

It worked for me and passes the CircleCI tests. If it doesn’t work can you open a new issue?
Also of note, acs-engine master branch deploys Windows Server 2019 by default now


Windows: [HMR] The following modules couldn't be hot updated: (Full reload needed)

I'm trying to get hot reloading working on Windows (node 0.12.2 / node 5.0.0). Hot Reloading works fine when the code is ran with Mac OSX (node 0.12.4).
I see the following output in various browsers on windows:
[HMR] connected bundle.js:61752:23
[HMR] bundle rebuilding bundle.js:61805:23
[HMR] bundle rebuilt in 1217ms bundle.js:61807:23
[HMR] Checking for updates on the server... bundle.js:61884:23
GET XHR http://localhost:3000/static/40c9217ec465f79054a8.hot-update.json [HTTP/1.1 200 OK 8ms]
GET http://localhost:3000/static/0.40c9217ec465f79054a8.hot-update.js [HTTP/1.1 200 OK 1ms]
[HMR] The following modules couldn't be hot updated: (Full reload needed) bundle.js:61918:1
[HMR]  - ./common/components/Dashboard.js bundle.js:61923:12
[HMR] Reloading page

As already mentioned, everything works fine on OSX.
webpack.config.js
server.js
The project is rendering a React + Redux app serverside.
Before connecting to HMR, I get a Ract warning, which I don't think is connected to the issue and is caused by using some Redux Devtools. But better make sure:
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) id=".1yovdae1q0w.0">Dashboard12312

 (server) id=".1yovdae1q0w.0">404

 node server
hot reloading works fine. But when running:
>set NODE_ENV=randomString && node server
hot reloading does not work.
Here are some working vs some not working examples:
working
> node server

working
> set NODE_ENV=development
> node server

not working
> set NODE_ENV=development && node server

not working
> set NODE_ENV=development && node server
[ctrl+c]
> node server

I was able to reproduce this issue with the react-transform-boilerplate:
# works
> node devServer.js
# does not work
> set NODE_ENV=foo && node devServer.js
>

I'm still not sure if I'm overlooking some detail, because this is really weird. Here some more examples:
# works
> echo foo && node server
# works
> set FOO_BAR=foobar && node server

I have this exact same issue after cloning and running the Shopping Cart example for Redux. Using Windows 10 / Node fully updated.

Did you ever find the reason for this? I'm experiencing the same, using react-transform-boilerplate after adding redux (the boilerplate works nice in it's original form).
Trying to pin down the exact change that causes this, I also stumbled upon this error:
<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/rackt/react-redux/releases/tag/v2.0.0 for the migration instructions.

Might have something to do with it?

Changing App from functional to extending React.Component, and moving setInterval inside App solved hot reloading for me.

Can this be closed? Is it still an issue?

Yes, this is still an issue, as @arekkas pointed out:
not working:
set NODE_ENV=development && node webpack/server.js
working:
set NODE_ENV=development node webpack/server.js

@pohy try set NODE_ENV=development&& node webpack/server.js (replace the whitespace)

@arekkas Wow, that solved the issue, many thanks.

Windows environment variables created with the SET command are persistent as long as cmd.exe is still running.
Also, Windows uses a single & to represent boolean and, instead of the double && that you're used to on OSX/*nix.
As you've discovered, the Windows' SET command is sensitive to whitespace. Another solution is to use quotes.
So, this:
set NODE_ENV=development && node webpack/server.js

should actually be this:
set NODE_ENV="development" & node webpack/server.js

or better yet:
set NODE_ENV="development"
node webpack/server.js
set NODE_ENV=

That last line unsets the NODE_ENV variable.

Another popular solution is to use the cross-env module, which allows you to set environment variables for a process in the same way across operating systems:
npm i --save-dev cross-env

node_modules/.bin/cross-env NODE_ENV=development node webpack/server.js

We also had great experiences with cross-env, definately recomment it


[8.x] Remove fallback links

now that L7 has the filesystems.links key by default, and the config file comes pre-populated with the storage to public link, let's remove it from the command.

I think it's fine to leave this to be honest.


Add libvirt channel

What this PR does / why we need it:
Add support for libvirt communication channel with QEMU guest agent.
Does not introduce further communication or read/write from guest agent.
Release note:

Adds support for QEMU guest agent communication channels. Prepares KubeVirt for guest agent support.

This change is

@SchSeba updated to the constant

In general I'd not in favor to auto-add devices (just liek virtio rng).
To auto-addition in this case is left to i.e. the templates whcih create VMs.

@rmohr @fabiand Autodetection is nice, however the user would not have the control over the process. Introducing autoattachGuestAgentChannel is a solution, however the guest agent will be configurable, therefore we will add the guestAgent  section either way.
I am sorry if I created confusion with splitting the code to multiple stages, but the second part is coming  in second PR. I did this to make the review process easier.

@rmohr @fabiand Autodetection is nice, however the user would not have the control over the process. Introducing autoattachGuestAgentChannel is a solution,

The struct itself is here and in the docs highly confusing for me. I did not see a clear separation between where it is meant to provide sources to install the agent vs. where it is meant to say, that the image has an agent. I can understand that we provide a PCI device and that this may lead to identity issues, however it is not different to any other device which we have right now, where we also don't provide PCI addresses and for some  like e.g. graphics, we just add it behind the scenes.

however the guest agent will be configurable, therefore we will add the guestAgent section either way.

What exactly will be configurable and why? I did not find anything in oVirt where it can be configured.
I would expect the following if I just bring in an image with a guest agent:

It will start to provide additinonal status info (e.g. ip addresses for all nics)
Optional I can configure a liveness probe baseed on the guest agent

We can for sure add specific structs once we know  why we need them, but why wouldn't we right now just simply always want to add the channel and make use of the agent if it is present?

We had this discussion already in https://docs.google.com/document/d/1tMPmFtCqNv5pED7T83AN7sxMVwe0iDNhtzZZOudtO8M/edit#heading=h.94xe2trd2ahu where as @fabiand pointed, instead of having switch to enable guest agent, it is better to have the solo structure.

I am not talking about enabling it. I was talking about explicitly disabling it. I don't understand why I would not want to connect to the agent by default, if it can be detected that it is there.

@rmohr as for the configuration. It is described in the original design document, we all agreed upon https://docs.google.com/document/d/1io69X-LCgy5hKC9sEV49LK6_43aF7lDUnMWzj41MfrE/edit#heading=h.ald6fo79ae6c

As for the actions from the document:

 tryShutdown: false  # opt-out if needed

Why wouldn't I always first try to do a shutdown via the agent if I detect it? We also don't make it configurable for ACPI to first try a shutdown via ACPI before we do a poweroff, we just do it.
I would expect the following: ACPI + guest-agent shutdown at the same time, if graceful timeout has passed, do a power-off.

 tryPoweroff: false  # opt-out if needed

What's the difference between a guest agent poweroff and a libvirt poweroff?
We also have the ACPI added by default, you have to explicitly opt out, if you don't want it.

Also there is a allow: true/false field in the docs, what is it used for? I don't see it here:
  domain:
    guestAgent:
      allow: true

Initially we discussed to just enable the channels. Now, while reviewing this PR I think it's not enough, specifically for testing.
Thus, @petrkotas I think it would be good to also include the basic guest agent status reporting in this PR as well.
You can retrieve the status by looking at this informations: <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>

@rmohr finished the work on this. Please would you kindly do the review? Thank you.

@rmohr finished the work on this. Please would you kindly do the review? Thank you.

Excellent. Reviewing.

@rmohr I have skipped the constants. With now having only one case: "connected" there is no benefit of having that in constants. The libvirt code also does not change in this manner, so no need to change that in the future.

@petrkotas you can cherry-pick this commit and use it for testing: https://github.com/rmohr/kubevirt/commit/2478fda78d699497c2f034dad3a8345a4a6a0719. Let me know if you have any questions.

@rmohr fixed those tests we discussed. It was more tricky than I thought. Will cherry pick in the morning.

@rmohr I updated the PR to reflect @davidvossel remarks.  :)

@petrkotas unit tests are segfaulting: https://travis-ci.org/kubevirt/kubevirt/builds/447720439#L1241

@petrkotas can you run make and commit the difference? can you squash the commits? Thanks!

@rmohr i have finished squashing. I will take care of @nertpinx comments. Would be ok to merge afterwards?

@rmohr done. As for the tests.GetRunningVirtualMachineInstanceDomainXML, it cannot be used. The status is added by libvirt. Returned XML by tests.GetRunningVirtualMachineInstanceDomainXML does not contain runtime information.

@rmohr done. As for the tests.GetRunningVirtualMachineInstanceDomainXML, it cannot be used. The status is added by libvirt. Returned XML by tests.GetRunningVirtualMachineInstanceDomainXML does not contain runtime information.

I extra prepared the function for you in https://github.com/rmohr/kubevirt/commit/2478fda78d699497c2f034dad3a8345a4a6a0719#diff-a5a178b4c66835110ceff63c61d28c96. Seems like these changes got removed when you cherry-picked it?

@rmohr ping?

@petrkotas once travis is happy we can merge.

@rmohr i see travis passing now. Would you agree to merge now?


The game won't launch after I log in

I am using the latest release as of writing this (0.1.8) and this issue has always occurred in the previous release as well (0.1.7)
I have tried closing and opening yaagl, verifying the file integrity, uninstalling the game files and launcher and re installing the latest release again off GitHub, but nothing seems to work and I have always had this problem from the start.
"Data error, please fully uninstall the game and download the latest game files from the official website again"

macOS Sonoma Beta 14.4
Device:  iMac 24-inch 2020
Chip: Apple M1
Memory: 8 GB
game_1708737830153.log

I solved this problem by switching the patch applied from the game section in the launcher settings. Please try adjusting it properly.

I solved this problem by switching the patch applied from the game section in the launcher settings. Please try adjusting it properly.

Would you please describe more detailed?  I tried every option combination in the Game section in the launcher Settings but the issue remains.
macOS Sonama Beta 14.4
MacBook Pro 16" 2021
Apple M1 Max
Memory: 64Gb

Hmm, I had the same problem...

First, I turned on Workaround #3
but the problem remains
Next, turn on Turn off the AC patch
I was able to start it.

But if you've tried every option, your problem may be different from this one. The problem varies depending on the environment, so I don't know of any better solution.

I solved this problem by switching the patch applied from the game section in the launcher settings. Please try adjusting it properly.

This worked for me thank you

Hmm, I had the same problem...

First, I turned on Workaround #3
but the problem remains
Next, turn on Turn off the AC patch
I was able to start it.

But if you've tried every option, your problem may be different from this one. The problem varies depending on the environment, so I don't know of any better solution.

Thank you.  I tried again, still no luck.

Hmm, I had the same problem...

First, I turned on Workaround #3
but the problem remains
Next, turn on Turn off the AC patch
I was able to start it.

But if you've tried every option, your problem may be different from this one. The problem varies depending on the environment, so I don't know of any better solution.

Tried turning on both options and worked flawlessly


[discord-rpc] Add v2.0.1

Issues to overcome:

Not properly configured for debug builds and always forced /MT. Fixed by patching cmake.
Unable to stop building of examples, so delete afterwards.

I will try to get these fixed upstream for next version.

LGTM, thanks for the PR!


Building the project to add functionality

Description
I'm trying to work on this project, to attempt to add SSR support. However, I can't seem to get the basics working.
Code sample
I've checked out the module, and done an npm link on it.
I made my changes.
I've run npm run build to get the latest version into /dist
But now I get this error:

 warning  in ./components/Search.vue

90:21-36 "export 'default' (imported as 'HotelDatePicker') was not found in 'vue-hotel-datepicker/dist/vue-hotel-datepicker.min.js'

Datepicker Version
github/master

@krystalcampioni Should this be closed now?

@amulchinock I guess @antony is trying to use npm link in order to use the datepicker in another project that uses SSR, in order to work on it as a separate package in dev mode.
Not sure why it's not working though, I'll try to replicate this error.

@krystalcampioni yeah - that's essentially it. I wanted to try out my usecase as I developed the project.

@antony @krystalcampioni Intriguing. I'm slightly embarrassed to admit that I've not come across SSR before now. Any reading material someone could point me at?

@amulchinock don't be embarrassed! With the speed new things are created everyday in the tech field ( and specially in the frontend field ) it's hardly impossible to come across everything. If you'd like to learn more about SSR with Vue, a great start is Nuxt.js:
https://nuxtjs.org/
If you'd rather watch a course instead of reading docs, I can surely recommend Sarah Drasner's intro to Vuejs course at Frontend Masters, which also covers SSR rendering with Nuxt:
https://frontendmasters.com/courses/vue/


How to validate exists with multiple connections

I've got 2 connections mysql and mysql2. I need to validate Name of Category on mysql2 connection.
This is my code on $form:
$form->text('name', 'Category')->rules('required|exists:mysql2.databsename.category.name');
This is error:

QueryException In Connection.php line 647 :

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.name where name = ?' at line 1 (SQL: select count(*) as aggregate from databasename.category.name where name = Romance)

Try rules('exists:connection.table,column');

Thanks z-song, It's worked


Play .vob DvDSub subtitle error

Hi, @lukasf
When I play some .vob files, I get an error at some time. After playing with potplayer, I found that there is bitmap subtitles, but ffmpeg does not detect subtitles.
Here is the sample file:
https://www.dropbox.com/s/3bludytyp4j9xxo/The Cranberries - 2002 - Stars.zip?dl=0
There will be an error when playing to the 10th second, I tried to disable video or audio, the problem is still

Hi @sundongg,
the problem with VOB files is that they do not have a file header, so streams can appear later in the file, and then we are not prepared for that. We have a check for the stream index for that exact case, but it has a bug, so the app crashes.
It will be easy to fix the crash. But we are

Thanks @lukasf ,
Will not crash after repair, but will stop playing

Oh, I did not checkin the complete changes. Please try with newest changeset, it should play the file fine until end.


[Feature] Add URL to allow enabling or disabling proxy

I would like to propose adding a Proxy option in the "Add Download - Extra Config" section.
While there is currently a Proxy option in the settings, I sometimes prefer not to use the proxy for all downloads or to use it for specific ones. It would be helpful to add an option to enable or disable the proxy on a per-download basis.
Feel free to adjust any part if needed!

Hi there thanks for your proposal this feature is mentioned here. and this is why I didn't implemented it yet.


fix: yarn prepare

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (8): 4.00 (-96%)
note_trial_decrypting_time_in_ms (32): 103 (+58%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit c5fc95df and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
223,020
868,064
3,449,312

l1_rollup_execution_gas
842,107
3,595,172
22,204,681

l2_block_processing_time_in_ms
2,026 (+3%)
7,661 (+2%)
30,044 (+2%)

note_successful_decrypting_time_in_ms
301 (+1%)
897 (+5%)
3,258 (+4%)

note_trial_decrypting_time_in_ms
:warning: 4.00 (-96%)
:warning: 103 (+58%)
133 (-1%)

l2_block_building_time_in_ms
13,336 (+2%)
53,121 (+2%)
211,545 (+2%)

l2_block_rollup_simulation_time_in_ms
11,984 (+2%)
47,758 (+2%)
190,243 (+2%)

l2_block_public_tx_process_time_in_ms
1,314 (+2%)
5,221 (+2%)
20,803 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,431 (-1%)
42,018

note_history_successful_decrypting_time_in_ms
1,981 (-4%)
3,956 (-1%)

note_history_trial_decrypting_time_in_ms
120
143 (-1%)

node_database_size_in_bytes
1,628,949
1,094,120

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
782
61,697
18,905

private-kernel-ordering
123
24,297
8,153

base-rollup
1,771
656,311
814

root-rollup
77.3 (-3%)
4,072
1,097

private-kernel-inner
787
81,568
18,905

public-kernel-private-input
41.6
41,519
18,841

public-kernel-non-first-iteration
26.5
41,497
18,841

merge-rollup
0.928 (-2%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,787
27,547


Run npm audit fix --force and update the tests as necessary

Summary
To resolve the security vulnerability warnings, I've run npm audit fix --force (--force was necessary this time) and fixed the tests that started failing after that.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Hey @colmdoyle, can you take a look at this?


register question

do i need to call PushNotification.init every time that app is opening ?
it seems init method will register GCM token every time

@LightZam Yes, you need to call the init method each time the app is opened. Google periodically refreshes the registration ID so you'll want to check each time to see if it has changed.


TS complains about protected properties on PIXI.Graphics

First off, awesome work on Pixi 5 and 6. Upgrading was a breeze ❤🌈
Expected Behavior
I have a PIXI.Graphics object this.line, and my codebase (which was written with Pixi 4) is accessing this.line.currentPath.points to generate a hit-area for the line. Typescript is now complaining about currentPath being a protected property on my PIXI.Graphics object.
I'd expect either for currentPath in PIXI.Graphics to be typed as read-only instead of protected, or for there to be a simple helper method to get access to that Polygon.
The code still works fine at runtime... it's just TS that's complaining at me.
I did notice a comment in the d.ts file, and it prompted me to try the following:
this.line.drawPolygon();
const points = this.line.geometry.points;
this.line.clear();

However this didn't seem to work as the previous code const points = this.line.currentPath.points worked.
Current Behavior
Typescript complains and my attempts at using drawPolygon() and geometry didn't work as I hoped they would.
Possible Solution
Open the type of .currentPath to be read-only instead of protected, or provide a helper method to access those points simply. Or maybe there's a correct solution that I haven't found.
Steps to Reproduce
this.line = new PIXI.Graphics();
// draw a line or curve of your choice (mine are mostly bezier curves)
const points = this.line.currentPath.points;

Typescript should complain, underlining currentPath and saying "Property 'currentPath' is protected and only accessible within class 'Graphics' and its subclasses"
Environment

pixi.js version: 6.0.0
Browser & Version: Electron 11.3.0, Chromium 87
OS & Version: MacOS 10.15.7

Also, the title refers to PIXI.Graphics, but I don't think the protected/read-only question only applies in that file. It's just where it's complaining for me.


V0.2.1 bug fix

Description
V0.2.1 bug fix

no need. I'll just rebase locally and push to master instead.


Array 0.4

Hi,
GHC 7.4.1 ships with array 0.4. weighted-regexp's cabal file specifies a constraint that excludes this. It seems that this constraint can just be relaxed and the package will build just fine. Please consider making this change.
Thanks :-)

Tested and pushed: 49ddcfffdfb1782fbaaf2f5efc8342765a5d386a


More history than 43 minutes

📑 I have found these related issues/pull requests
Have not found
🏷 Feature Request Type
Status-page
🔖 Feature description
Hello,
We would appreciate to be able to see history more than 43 minutes ago in the status page. It would help us to see, for example by day, if there was any incedent past 30 days.
✔ Solution
Possibility to choose (by user) how far ago he wants to see the history of services in the status page.
❓ Alternatives
No response
📝 Additional Context
No response

The displayed time span ins currently based around the monitoring interval.
In v2 the part of the system responsible for this has been significantly changed and adding this feature is now possible.
This feature is tracked in #1167
Our contribution guide is here
=> closing as a duplicate


2 Missing UK Bank holidays

There are normally 8 bank holidays in the UK each year (https://www.gov.uk/bank-holidays), whilst holidays.CountryHoliday("UnitedKingdom", years=2023) lists 6 regulars bank holidays.
The missing bank holidays are the "Summer bank holiday" and the "Easter Monday bank holiday". This error occurs in both 2023 and 2024.

@will-judge, thank you for your comments and useful source!
These holidays (Easter Monday and Late Summer Bank Holiday) are not common to the entire United Kingdom, but only to England, Wales and Northern Ireland (they are not holidays in Scotland). So you may find them in something like
holidays.CountryHoliday("UK", subdiv="ENG", years=2023)
(also "NIR" or "WLS" instead of "ENG").

I believe this can be closed.


Custom CSS within YAML header

Hi there,
I like to use custom CSS (specifically the Typewriter Effect) for the title field in the YAML header (e.g., on the about page). I tried various options but couldn't quite figure out how to override the predefined CSS for that field using a custom .scss file. I am grateful for any tip! 🤗

I solved it by including the following CSS directly into the YAML header title field. It would be probably more elegant to place the CSS code somewhere else and link to that file, but I couldn't make it work. Happy if anyone proposes a more elegant solution :)
title: |

Title Text Goes Here


Remove nonexistent permission from Licence Finder API user.

This was causing the Signon API to crash when attempting to create the Authorisation.
Licence Finder doesn't currently have any additional permissions on its Authorisation for Publishing API. Publishing API doesn't have a permission called internal_app (or anything similar).
https://trello.com/c/F7vSHnws/841

Raised https://github.com/alphagov/signon/issues/1824 for the API bug. Not really a huge deal now that we know about it, but still would be nice if it gave a helpful error message (e.g. would have saved me maybe an hour of debugging).


  It leverages the trackerdict structure by setting tilt and azimuth to fixed.  It adds a new optional fixed_tilt_angle to main.set1axis() which triggers a fixed tilt simulation to be returned in a trackerdict.  it still uses the axis_azimuth input as the fixed tilt azimuth angle though...  hopefully this isn't too confusing.
I've checked the pytests, and a few GUI options.  Please check that all GUI functions are still working.

Oops - the gui input tracking_hourly for the full year isn't working correctly.

I think all of the gui buttons should be working now...

OK, I merged main into development so it should be up to date.  If you want the EUPVSEC stuff too, you can merge from development into your EUPVSEC branch once we get this pull request finished.

@shirubana :  Here's a question about default behavior  when both daydateSimulation and timestampRangeSimulation are False.  In this case, the modelChain always assumes that you want a full annual simulation - whether it's a cumulativesky or hourly simulation, and regardless of whether you pass start / end time details in the timeControlParamsDict, which are ignored unless you specificially trigger a limited time simulation with either of the above flags (daydate or timestamprange).  OK?

I think that sounds good.

Maybe it would need some sort of warning: "Information for day start/end, included, but since no specific time-simulation selected, proceeding to calculate WHOLE year"

this is a helper function for (me) the jupyter journals -- in case you're wanting to do a fixed tilt simulation and need to know the tracker's angles.
Right now fixed tilt is the only way to do multiple scene objects so I think we should leave this for when someone wants to do a tracker field with fixed tilt in it too..

This looks good, I'm going to merge it into development.

🥇

@shirubana  - I'm tagging this as a development release:  0.3.2-dev1

sweet.
I'm going to delete the Master EUPVSEc branch then ~~


Handing of "[DEP0062] DeprecationWarning: node --inspect --debug-brk is deprecated. Please use node --inspect-brk instead"

Hi team, I was reading through the closed issues on this deprecated warning but I still can't seem to get the message removed and am a little confused with exactly how it was resolved.  I've followed (I think) the instructions for using the setting "protocol": "inspector" but I still it being launched with the deprecated parameter and see the message even though I have this setting.
By using "protocol": "inspector" is that supposed to issue the correct node debug command?   In one of the discussions detailing this issue (here https://github.com/Microsoft/vscode/issues/32529), it was mentioned by @weinand that there is no way to remove this message because both debug parameters are submitted.  But surely this protocol setting could be smart and only submit the parameters required for more modern versions of node?    Also setting this parameter to auto fails and node will not start.
If you look at the command being issued it shows that node --inspect --debug-brk are the two parameters being passed.  Node is asking for --inspect-brk.  Maybe one other option would be to add a launch parameter to provide your own debug parameters should you desire.
Maybe I am doing something wrong, or maybe I am just late to the party and missed the solution, but I am still puzzled and have expired all of my searches on trying to resolve it.  Please point me to the article that shows the solution if so.
I am using node 9.5.0 on WSL with the latest Visual Code production build 1.20.1. I also checked on the insiders build of VC and it's also there.

My launch.json
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "queue",
            "protocol": "inspector",
            "program": "${workspaceFolder}/queue.js",
            "useWSL": true,
            "outputCapture": "std",
            "sourceMaps": true
        },
    ]
}

Cheers.

I cannot reproduce this problem on Windows with VS Code 1.20.1 and node.js v9.5.0:

Please verify that the node.js running in WSL has the version you are expect if to have.

Hi @weinand - I still get the same message on my desktop.  That is running a production build of Windows 10 with the latest creators update.
I tried again, this time on my Surface book which has Insiders build version of Windows 10 and Ubuntu 16.  I get the same issue.  I tried to force run a specific version of node within launch.json (as you can see below), but that still did not eliminate the message.  I've also tried upgrading to node 9.6.1 and downgrading to node 7x, but still I see the message.  I also tried the Visual Code insiders build, and still I see the message.
What's different about your environment?  Could it be something related to your .bashrc?
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "protocol": "inspector",
            "request": "launch",
            "name": "Run Elastc",
            "program": "${workspaceFolder}/elastc.js",
            "useWSL": true,
            "outputCapture": "std",
            "sourceMaps": true,
            "runtimeExecutable": "/home/aosman/.nvm/versions/node/v9.6.1/bin/node"
        },
    ]
}

@weinand what other info can I get you?

instead of running "elastc.js" please just run the trivial program version.js:
console.log(process.version)

What is the output?
If you set "useWSL" to false what is the output?

@weinand here it is with a simple test:

If I set useWSL to false, nothing will work.  I do not have node installed on Windows and my code is executing from within bash.  If you really need to know I will go ahead and install it, but that really is outside the realm of environment we are in.

So I cannot explain why you are seeing this but it is not really a problem at all. See this comment for why we are doing this:

It's not a bug, it's a valid way to put node 8 in debug mode, which they only kept to make life easier for IDEs. See https://github.com/nodejs/node/pull/12949 and related issues. Also I have #27731 to make version detection more sophisticated in the future and try to use --inspect-brk.

@roblourens might chime in...

@weinand It can't be coincidence that it is happening in two different desktop environments.  I even stripped my .bashrc back to barebones.  The only thing I have in there is my nvm setting.  Are you using nvm by any chance?
here's what I had in my .bashrc
export NVM_DIR="/home/aosman/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"

I also did this test: just running node at the command line.
aosman@falcon:~/elastc-app$ node --inspect=38071 --debug-brk test.js
Debugger listening on ws://<IP_ADDRESS>:38071/cb4889c2-7364-47f5-8116-64e02ae9583f
For help see https://nodejs.org/en/docs/inspector

Perhaps this may be related to running bash.exe from Windows land and then executing node?

I try to check the node version to determine whether it's safe to use --inspect-brk but I don't when there's a runtimeExecutable set (like for wsl). Soon I will switch the default to --inspect-brk. But in the meantime it's safe to ignore this message.


Refactor "check support" IO functions

Some IO classes have "check support" functions (for example modin.engines.base.io.text.csv_dispatcher.CSVDispatcher._read_csv_check_support and modin.engines.ray.generic.io.RayIO._to_csv_check_support functions), which takes IO function arguments and return bool indicating whether these arguments are supported or not. Returning of bool is not necessary and "not supported" action can be done inside "check supported" function.

Hi @amyskov! Has this issue been resolved? I know @noloerino put in a PR recently (#4647) that refactors the IO, but I don't know if that resolves this issue!

I think #4647 resolved this issue.


Update README.md

The Open Research Grants program was paused earlier this year, but applicants are still inquiring.

I made it clear that other programmes were paused too, moved RFP-14 to inactive, and removed link to the grants portal that no longer exists.


Log forwarding

We're releasing this feature as part of v1.6 of Runtime Fabric. Could we ensure the changes in this PR, once finalized, are only in v1.6? @paigehargrave


RAWv2-slow will regularily set the sensor to unavailable

After switching from RAWv2-fast to RAWv2-slow for some of the RuuviTags in order to save some battery lifetime, the sensors in HASS start to have larger gaps in the graphs, because their entities are set to unknown every few updates or so, instead of simply not updating the entities and possibly marking them as "unavailable" after some time, the current behavior will disrupt the history graphs.

Hi @makuser , is this issue related with https://github.com/ruuvi-friends/ruuvi-hass.io/pull/4 ?

Hi @makuser , is this issue related with #4 ?

Well it might be, that fixing #4 could help with this, to avoid the "small gaps" in the graps that you described.
But in even in general, a HASS component should not send 'unknown' as a value, but instead mark the sensor as unavailable, if necessary.
#4 additionally proposes to introduce a "data holding period", that I think might not even be necessary in this case.
So yeah, you can mark it as dup of #4 if you think that it is, otherwise you can leave it open and I will see if what you come up in #4 will also fix the issue with RuuviTags in RAWv2-slow mode.

Let's keep it open. I also have to dig if there has been any updates to the sensor api in Home Assistant, because I don't remember having this problem. As you saw in #4 previously if a sensor got our of range or not found, hass would just assume the previous value. I asked about this on the Discord and it seemed to be the expected behavior at the time, and that's the reason why I made that draft pr.

This should now be fixed by #14 .


Update OPA to v0.14.0

Automated pull request to revendor OPA

cc @ashutosh-narkar

Hello @danielpops, I am looking into this. Thanks !

See pr https://github.com/open-policy-agent/opa-istio-plugin/pull/138


Added jax.blocking

This methods takes any JAX method and turns it into a blocking version. Can be thought of as a more functional version of block_until_ready

Why not use a type variable so that the type of the function the decorator applies to doesn't get lost?

That's a good point. I will add that.


Props-Component does not work properly in Gatsby-Theme

Hello @pedronauck, thank your for this amazing library!
The Props-component does not work properly, when I use Docz as Gatsby Theme. The props-table only shows up, after I open the file of the imported component and save it.
After gatsby build the prop-table does not get rendered at all.

The same happens for me. Possibly related #893?


Check if tier 2 targets build in the nightly cron job

This PR adds a CI job that only runs nightly which will install Miri built from the latest commit, and try to build every Tier 2 without host tools target, as documented on https://doc.rust-lang.org/nightly/rustc/platform-support.html.
I'm not really excited about the idea of scraping the tier 2 without host tools list, but also keeping the list up-to-date by hand seems prone to forgetting to update it. And that update seems like the sort of manual maintenance we should automate.

LGTM, r=me after squashing.

@bors r=RalfJung

:pushpin: Commit cb10a73049e421fa1e8d8f8cd65099a06eb070c1 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit cb10a73049e421fa1e8d8f8cd65099a06eb070c1 with merge fa672fa2b884b4e889400d6c7ee3016b7c65e994...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing fa672fa2b884b4e889400d6c7ee3016b7c65e994 to master...


Unable to install paths

Hi, I was trying to install torch, but turns out it fails to install paths package. I'm using OSX 10.9.3 and I have lua (5.2.3), luagit (2.0.3), luarocks (2.0.13) installed via macports. Here is a full output of the error:
sudo luarocks --server=https://raw.githubusercontent.com/torch/rocks/master install paths
Installing https://raw.githubusercontent.com/torch/rocks/master/paths-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/paths-scm-1.rockspec... switching to 'build' mode
Cloning into 'paths'...
remote: Counting objects: 10, done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 10 (delta 0), reused 5 (delta 0)
Receiving objects: 100% (10/10), 12.11 KiB | 0 bytes/s, done.
Checking connectivity... done.
Warning: unmatched variable LUALIB
cmake -E make_directory build && cd build && cmake .. -DCMAKE_BUILD_TYPE=Release -DLUALIB= -DLUA_INCDIR="/opt/local/include" -DLUA_LIBDIR="/opt/local/lib" -DLUADIR="/opt/local/share/luarocks//lib/luarocks/rocks/paths/scm-1/lua" -DLIBDIR="/opt/local/share/luarocks//lib/luarocks/rocks/paths/scm-1/lib" -DCMAKE_INSTALL_PREFIX="/opt/local/share/luarocks//lib/luarocks/rocks/paths/scm-1" && make

-- The C compiler identification is AppleClang <IP_ADDRESS>30040
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30040
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Looking for include file unistd.h
-- Looking for include file unistd.h - found
-- Looking for include file dirent.h
-- Looking for include file dirent.h - found
-- Looking for include file time.h
-- Looking for include file time.h - found
-- Looking for include file sys/time.h
-- Looking for include file sys/time.h - found
-- Looking for include file sys/ndir.h
-- Looking for include file sys/ndir.h - not found
-- Looking for include file sys/utsname.h
-- Looking for include file sys/utsname.h - found
-- Looking for include file sys/dir.h
-- Looking for include file sys/dir.h - found
-- Looking for include file ndir.h
-- Looking for include file ndir.h - not found
-- Looking for getcwd
-- Looking for getcwd - found
-- Looking for dlopen in dl
-- Looking for dlopen in dl - found
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/luarocks_paths-scm-1-9991/paths/build
Scanning dependencies of target paths
[100%] Building C object CMakeFiles/paths.dir/paths.c.o
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:730:15: warning: 'tempnam' is deprecated: This function is provided for
      compatibility reasons only. Due to security concerns inherent in the design of tempnam(3), it is highly recommended
      that you use mkstemp(3) instead. [-Wdeprecated-declarations]
  char *tmp = tempnam(NULL, "luatmp");
              ^
/usr/include/stdio.h:389:7: note: 'tempnam' declared here
char    *tempnam(const char *, const char *) __DARWIN_ALIAS(tempnam);
         ^
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:991:20: error: use of undeclared identifier 'LUA_PATHSEP'
  while (*path == *LUA_PATHSEP) path++;  /* skip separators */
                   ^
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:993:21: error: use of undeclared identifier 'LUA_PATHSEP'
  l = strchr(path, *LUA_PATHSEP);  /* find next separator */
                    ^
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:1003:19: error: use of undeclared identifier 'LUA_GLOBALSINDEX'
  lua_getfield(L, LUA_GLOBALSINDEX, "package");
                  ^
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:1110:19: error: use of undeclared identifier 'LUA_GLOBALSINDEX'
  lua_setfield(L, LUA_GLOBALSINDEX, "paths");
                  ^
/tmp/luarocks_paths-scm-1-9991/paths/paths.c:1111:3: warning: implicit declaration of function 'luaL_register' is invalid
      in C99 [-Wimplicit-function-declaration]
  luaL_register(L, NULL, paths__);
  ^
2 warnings and 4 errors generated.
make[2]: *** [CMakeFiles/paths.dir/paths.c.o] Error 1
make[1]: *** [CMakeFiles/paths.dir/all] Error 2
make: *** [all] Error 2

Error: Build error: Failed building.

Can you tell from this error what's wrong on my system? Thanks, Valentin.

Hi, I am facing the following issue-
Installing https://raw.githubusercontent.com/torch/rocks/master/dpnn-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/dpnn-scm-1.rockspec... switching to 'build' mode
Cloning into 'dpnn'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Connection timed out
I am using Lua 5.2.3. Please tell me how this error can be solved.

the issue looks like still persist in the https://github.com/torch/distro.git two years later as of autumn 2016. Just following http://torch.ch/docs/getting-started.html  with TORCH_LUA_VERSION=LUA52 ./install.sh returns the same error.  Can the fix be merged into the official distribution?

The problem is still here, 4 years later!

That's true.

the issue looks like still persist in the https://github.com/torch/distro.git two years later as of autumn 2016. Just following http://torch.ch/docs/getting-started.html with TORCH_LUA_VERSION=LUA52 ./install.sh returns the same error. Can the fix be merged into the official distribution?

omg! I love u man


for gcp

Signed-off-by: Isaac Zaydens<EMAIL_ADDRESS>

Ignore this PR as it is only to pull this into GCP for training


k8s_status doesn't work when using lists

Assume current_cr is a fact that contains the current CR being processed.
- operator_sdk.util.k8s_status:
    api_version: "{{ current_cr.apiVersion }}"
    kind: "{{ current_cr.kind }}"
    name: "{{ current_cr.metadata.name }}"
    namespace: "{{ current_cr.metadata.namespace }}"
    status:
      foo: ["one", "two"]

- operator_sdk.util.k8s_status:
    api_version: "{{ current_cr.apiVersion }}"
    kind: "{{ current_cr.kind }}"
    name: "{{ current_cr.metadata.name }}"
    namespace: "{{ current_cr.metadata.namespace }}"
    status:
      foo: ["two"]

Results in the status.foo field containing both "one" and "two" rather than just "two" (which it should be):
status:
  conditions:
  - ansibleResult:
      changed: 17
    ...and the rest...
    message: Awaiting next reconciliation
  foo:
  - one
  - two

cc @fabianvf

Workarounds I've tried that do NOT work:

Make an initial call to set the field to an empty list []
Make an initial call to set the field to null (this actually results in an error in k8s_status.py - /tmp/ansible_operator_sdk.util.k8s_status_payload_An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: 'NoneType' object is not iterable

I haven't seen much activity in this repo - is this the correct place to submit this bug report?  Been about 4 months when this issue was reported and I haven't seen any triage performed on it.

@jmazzitelli ah yes, sorry, this repo doesn't get a ton of traffic and this one slipped my view, I'll put some better alerts up for it. I recently rewrote a large portion of the k8s_status module, are you still seeing this behavior?

I actually haven't tried since the workaround was implemented (I just use a string now - that's the workaround). I haven't tried using an array since I submitted this issue. In fact, right now, I'm probably going to keep it how I have it - QE is starting to test this operator with potentially very large lists of namespaces and I don't want to have to repeat that list here in the status (right now if the list is greater than 20, I just store a string "The number of namespaces is [N]". This is just informational in my operator, so I don't really need a list.

I'm having the same issue. I expected a list to be completely replaced.
Using replace paramater means adding logic outside the module. I'd say it would be better inside k8s_status module.

Now it is working. List are completely replaced in status. I'm not sure what the issue was. I suspect it was because of an old version of k8s_status in my local system vs the one in the actual operator.

Spoke too soon. It worked because of #19, which will always update status in certain conditions.  Right now, I'm testing a workaround to fully replace mismatching lists except conditions


update: updated support window to Go 1.18, 1.19

Update support window to Go 1.18, 1.19.
Resolves #261
Signed-off-by: wangxiaoxuan273<EMAIL_ADDRESS>

Codecov Report

Merging #270 (a7fa5f0) into main (c76df08) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #270   +/-   ##
=======================================
  Coverage   70.63%   70.63%
=======================================
  Files          36       36
  Lines        3293     3293
=======================================
  Hits         2326     2326
  Misses        718      718
  Partials      249      249

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Priors on the normalization of the global and emulator covariance matrix

The normalization of the global covariance is described by a free parameter logAmp (the actual normalization is (10**logAmp)**2). But if such normalization is much higher than the median value of the squared of the flux uncertainties, then the final covariance matrix could be dominated by the global covariance matrix. In this way, when we generate the plots to show the fitting residuals and the 1/2/3-sigma model scatters, even large residuals could be regarded as a good fit, given that they are anyway consistent within 1/2/3 sigma. However, this might not be always appropriate since Starfish could add "artifacts" into the covariance matrix to force the fitting look good.  This concern is also what some non-Starfish users expressed to me.
I have to clarify that I am not blaming the spectral emulator matrix and the global covariance matrix. On the other hand, I think they indeed make Starfish as an improved method than the traditional $\chi^{2}$ fitting: the spectral emulator can propagate the interpolation uncertainties which cannot be achieved from linear interpolation; the global covariance structure incorporates the instrumental effect. The inclusion of both spectral emulator and global covariance can help deliver more reasonable error estimates (i.e., small errors in best-fit parameters do not mean good fitting). However, I think it might be necessary to make sure we are not over-adding something into the covariance matrix, which might make Starfish not smart - but "arrogant".
Therefore, I am wondering whether we need to add a prior to the logAmp? An initial proposal would be something like: the 10**logAmp should never exceed a certain fraction (e.g., 0.5) of the median flux uncertainty, although I cannot think of any reasons for deciding a reasonable fraction. And such a fraction seems like another artifact... I naively think the fraction should be smaller than 1 or so to make sure the global covariance does not dominate, but I'd really like to hear your advice!
On the other hand, I know that the global covariance is designed due to the instrumental profile, so I was thinking if I could use the instrument properties to decide such a prior. Actually, the priors on the width of the global covariance kernel, described by the hyper-parameter l, can indeed be decided using the FWHM of the instrumental profile or resolution a.f.o. wavelength (I will recently post my research about this). But I do not know how to determine a reasonable prior on the normalization of the global covariance based on the properties of the instrumental profile (maybe we cannot?).
A similar question related to this would be: is it necessary at all to add any priors to make sure the emulator covariance matrix does not exceed the squared flux uncertainties too much? (I may check the math shown in the paper/code again to better understand this)
I may do some experiments by comparing the fitting results from adding and not adding my proposed normalization-priors on the global covariance and will post some updates when they are ready.

Although the covariance matrix for the emulator and the covariance both appear in the likelihood calculation, they have different origins and serve different purposes. Once the emulator is tuned to a subset of the synthetic spectral library, its parameters remained fixed, regardless of what specific data spectrum you may be fitting. The uncertainty in the range of emulated spectra is set by the density of gridpoints in your synthetic library, how many principal components you used to decompose it, and how well the tuning process went. The uncertainty from the emulator is marginalized over in the final calculation (Eqn 55).
The covariance matrix for the actual data is parameterized by (among other things) a "global" kernel, which can inflate the correlated noise in a fit. This isn't too different from fitting for a jitter term in an RV timeseries, and is meant to absorb some of the correlated errors that result from fitting a synthetic spectrum with limited parameters available. If you had access to the many tunable parameters that go into synthesizing a single stellar spectrum (T-P profile, correct opacities, microturbulence, limb-darkening etc etc) then you could probably synthesize a truly correct model that would fit within the measurement uncertainties. But, the point is that doing such a calculation over more than a relatively small wavelength region is computationally prohibitive, so most fits that are done will be dominated by (small-scale) systematic uncertainties, not observational uncertainties (e.g., see Section 2.3 of the paper). That said, if the only model that will fit your data requires really huge global covariance values, then that is a sign that your model isn't very good. If the fit isn't a good, fit, then it isn't a good fit, and this should be evident by the mismatch between the model and the data. I'm not sure what you mean by artifacts in this context.
I'm surprised that others would classify this sort of modeling approach as arrogant, because I would think that it's actually much more conservative in its assumptions than say chi^2. By allowing the noise to be parameterized (and inferring those parameters), such an approach opens up the otherwise strict requirements of say chi^2 fitting to investigation. For example, typical chi^2 would assuming that the model you are using is perfect (in the sense that the data could be considered "generated" from the model) and that the only source of noise is Poisson. If you fit for a global covariance parameter and it turns out to be small, then that's a good sign that your model does actually fit the data pretty well (i.e., the noise term is "penalized" in the same sense of adding jitter terms, one can't arbitrarily inflate the noise and get a good fit for all models). If you have a large global covariance parameter, then this is informing you that your range of available models do not accurately represent the data, and that other systematic sources of noise are required. In chi^2 fitting this would be hidden from you.
To your original question, it would be fine to put a prior on the value of logAmp if you so desire. But, the fact that large values seem to be required is probably telling you something about how well the synthetic model grid you are using can reproduce your dataset. It may be a useful exercise to look at the fits in detail to see where there is large data-model mismatch. At the end of the day, the quality of your parameter inferences depend most strongly on how good your models are.


Optimise getPostObjectName func

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/kind cleanup


feat: precision mode

Be more precise by reducing number of concurrent requests to prevent timeout and limiting.

Need to update tests/


Text is not visible in the footer section due to color of font

The footer section text is not visible as it almost seems to overlap with the footer background.
The color can be changed to something more readable.

Please assign this issue to me under GSSOC'24
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

plz assign this task to me

@ahinagangopadhyay go ahead

@Mukesh751 I have opened a pull request to solve this issue.Please review the request.


Jaeger exported traces are incomplete

I was experimenting with OpenCensus (thanks for open-sourcing this, it's a great project) and it looks like there are quite a few things I can't get working properly when exporting traces to Jaeger.
I setup a simple project where I create a span and try to add attributes, annotations and a status:
_, span := trace.StartSpan(ctx, "dummy/api")
defer span.End()
span.AddAttributes(trace.Int64Attribute("swag", 42))
span.Annotate([]trace.Attribute{trace.StringAttribute("attr", "this is an attribute")}, "this is an annotation")
span.SetStatus(trace.Status{Code: 2, Message: "failed"})
The traces are correctly exported to Jaeger and visible in Jaeger UI, but:

I see the key for the Int64Attribute but the value is empty
I see a log in the Jaeger UI which contains my 'swag' and 'attr' attributes (but swag is still empty) but it doesn't contain my annotation
the trace status isn't taken into account

Is there something I'm doing wrong, or is it because there are inconsistencies between Jaeger's format and OpenCensus'?

Fixed but please let us know if there is anything odd.

Thanks for the quick fix! It looks good now.
I'll keep experimenting and will let you know if I see anything weird.


chore: used GitHub Actions for simpler CI push jobs

Overview

Uses GitHub Actions instead of CircleCI for some simpler push jobs.

PR Checklist

~[ ] Related to designs:~
~[ ] Related to JIRA ticket: ABC-123~ (there were a few heh)
~[ ] I have run this code to verify it works~
~[ ] This PR includes unit tests for the code change~

🚀 Styleguide deploy preview ready!https://6184136b7cbd8e27a0281c90--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618aa960f277481252401016--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618ab3d79443d51da8573ed7--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618ab777dd41f92277069252--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618aba56c37f4c2e1996e350--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.12-alpha.d9f077.0@codecademy/gamut-labs@28.0.7-alpha.d9f077.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://618abc8489752b28f3f15753--gamut-preview.netlify.appDeploy Logs


Saving Date Metadata with Time-Zone instead of Auto-Converting to UTC

Description
Typst appears to be converting date metadata to UTC ("Zulu", "Z", UTC+00:00) Time.
Example of this Metadata:
<</Creator(Typst 0.11.0)/CreationDate(D:20240417105515Z)/ModDate(D:20240417105515Z)>>
While this is the correct time, the information in which time zone the PDF was originally created gets lost.
Preferably, it would be saved as:
<</Creator(Typst 0.11.0)/CreationDate(D:20240417125515+02'00')/ModDate(D:20240417125515+02'00')>>
Now we know that the PDF was created in UTC+2 Time Zone.
Use Case
When converting to UTC time, we lose important information, when we are then trying to figure out when a PDF was created, we need to know where we were and also account for daylight saving times etc....
Saving the Time Zone would make the metadata much clearer, because then it would be unmistakably when the PDF was created. As someone that is often in different time zones, it is currently very annoying to find the local time I created a document.
Concern:
An unknowing user could give away location information through his timezone. But if someone is concerned about these points, everybody is free to disable the automatic creation and modification date in Typst.
Welcomed side effect:
Some PDF Viewers seem to handle metadata different from others, converting to local time zone, or just stripping the time zone info away no matter what. When having the time zone info, we are later able to validate what some viewers show and also know in which time zones the PDF was created, offering more valuable metadata than without.
Microsoft Edge is bad at displaying the correct time info, because it just strips away any time zone info. Let's assume the reader and creator are both in UTC+2.
So, when something was created in UTC+2 with Typst and then saved in "zulu" time, Edge will display a time 2hrs earlier. But when it is saved with the time zone info. The time in Edge will be the correct one, because Edge just stripped away the time zone info. This of course will break when reader and viewer are in different time zones.

Sounds like a useful feature imo.

An unknowing user could give away location information through his timezone. But if someone is concerned about these points, everybody is free to disable the automatic creation and modification date in Typst.

I wonder if it's a good idea to make such timestamp creation an opt-in feature instead of an opt-out, so that no timestamp is created by default unless the user explicitly tells Typst to do so. This is privacy-by-default, and helps with reproducibility.

I think defaulting to none with the timestamp creation would not hurt too many. The file system timestamp will be enough in most cases.

I don't think it's really a particularly big privacy concern. It's good practice to include this metadata in PDF files and all other comparable software also writes it. Deviating from that would need a stronger reason in my opinion.

quick edit:
Edge now displays the time-zone info correctly. But I think this feature is still relevant, although many programs do not handle the timestamp metadata correctly.


1.x pendant to resource

i remember in 0.x it was possible to define something like "resource" to define under what url socket.io is listening.
correct me if i am wrong, it was possible to have several instances of socket.io running, listening on different urls.
is this still possible somehow? i read that 1.x is allways listening under /

1.x has path option instead of resource.  And it seems that resource also still remains for backward compatibility.


Add redirect and fix cross references

Learn Build status updates of commit 05b1325:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/ContactCard.xml
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/Crop.xml
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/DocumentInspectors.xml
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/GradientStops.xml
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/PickerDialog.xml
:white_check_mark:Succeeded

officedocs-dev-office-pia/xml/Microsoft.Office.Core/TextRange2.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Retrospective modification of finalised NEP5

https://github.com/neo-project/proposals/commit/8c6b427e2ada2e71f92081686c4a832351e9eaa0#diff-e5a1452ea0de8fa24b9c328151e94aff
Projects deployed on mainnet have implemented these optional methods. I don't agree that they should have been removed from a proposal that had been marked as final and I put forward that they should be restored.
If a new token standard is to be defined without the optional methods then a completely new proposal should be submitted for discussion.

In the morning, I'll do what should have been done a week or more ago - I'll fork and PR a new NEP that contains what used to be the optional methods in the old NEP-5 standard.  It will take 15-20 minutes and then we can move on.

Ignoring the retrospective editing of a previously finalised nep without any reference to the change..
If this new Nep is proposed as NEP-51 and the original NEP-5 is amended so it is clear that the previously optional methods should be referenced in NEP-51 I think it solves the issues people are having.

Closed due to https://github.com/neo-project/proposals/issues/59

@erikzhang I've created https://github.com/neo-project/proposals/pull/60 to be reviewed and approved.
@birmas @anfn101 @lllwvlvwlll


nickname support

Is there a reason why you guys aren't supporting nicknames anymore? There's a very simple Mojang API for getting the UUID from nickname at https://api.mojang.com/users/profiles/minecraft/Notch

Yes. As noted on the website, Mojang has disabled the skin API for usernames. In fact, Mojang had already deprecated usernames before Crafatar was started and we always had a warning on the website that usernames may break and be disabled at any time.
We looked into using the API endpoint you mentioned, but unfortunately it is strictly rate limited, which in practice means we can't support it. See #106 for the details and discussion.

If you want to use usernames, just do the conversion to UUIDs on your side and send UUIDs to Crafatar.


Clean up morphemic segmentations

Put English glosses into single quotes, as is standard practice with
language materials.
Put the morphemic segmentation in italics, differentiating it from the
layers above and below.
Only show commentary icons at the "Analysis" level.
Remove visual noise from morpheme buttons

I think this may be a solid improvement on readability, especially for the 5-layer "Segmentation" and "Analysis" modes. Y'all can see a preview here. I'd love to hear any thoughts @jgbourns @LN7-cyber @GracefulLemming

I think this may be a solid improvement on readability, especially for the 5-layer "Segmentation" and "Analysis" modes. Y'all can see a preview here. I'd love to hear any thoughts @jgbourns @LN7-cyber @GracefulLemming


run gcr-cleaner-cli as CronJob on GKE

Hello, i'm trying to run gcr-cleaner-cli as CronJob on GKE (version 1.19.13-gke.701) with workload identity enabled, but i have an issue with the authentication on artifact registry hosted on GCP.
The configuration step that i did to allow the pod to handle the artifact registry are the following:

create a service account on GCP named gcr-cleaner-gcp
1.a associate to this service account the role roles/artifactregistry.repoAdmin
1.b associate to this service account the workload identity binded with a ServiceAccount create in the cluster (gcr-cleaner-cluster) with role roles/iam.workloadIdentityUser
create a ServiceAccount in the cluster named gcr-cleaner-cluster
create a CronJob running with serviceAccountName: gcr-cleaner-cluster

Maybe the terraform step and the k8s yaml are easiest to understand:
Terraform:
resource "google_service_account" "gcr_cleaner" {
  account_id   = "gcr-cleaner"
  display_name = "GCR Cleaner Account"
}

resource "google_artifact_registry_repository_iam_binding" "artifact_registry_admin" {
  provider = google-beta

  depends_on = [
    google_service_account.gcr_cleaner
  ]

  project    = data.google_client_config.current.project
  location   = data.google_client_config.current.region
  repository = "container-registry"

  role = "roles/artifactregistry.repoAdmin"

  members = [
    "serviceAccount:${google_service_account.gcr_cleaner.email}"
  ]
}

resource "google_service_account_iam_binding" "service_account_workload_indentity" {
  depends_on = [
    google_service_account.gcr_cleaner
  ]

  service_account_id = google_service_account.gcr_cleaner.name
  role               = "roles/iam.workloadIdentityUser"

  members = [
    "serviceAccount:project-id.svc.id.goog[default/${google_service_account.gcr_cleaner.account_id}]",
  ]
}

K8s yaml:
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/instance: gcr-cleaner
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: gcr-cleaner
    app.kubernetes.io/version: 0.5.0
    helm.sh/chart: gcr-cleaner-0.1.5
  name: gcr-cleaner
  namespace: default
---
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: gcr-cleaner-prod
  labels:
    helm.sh/chart: gcr-cleaner-0.1.4
    app.kubernetes.io/name: gcr-cleaner
    app.kubernetes.io/instance: gcr-cleaner
    app.kubernetes.io/version: "0.5.0"
    app.kubernetes.io/managed-by: Helm
spec:
  schedule: 18 16 * * *
  concurrencyPolicy: Forbid
  startingDeadlineSeconds: 180
  suspend: false
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
  jobTemplate:
    metadata:
      labels:
        app.kubernetes.io/name: gcr-cleaner
        app.kubernetes.io/instance: gcr-cleaner
    spec:
      template:
        spec:
          serviceAccountName: gcr-cleaner
          containers:
            - name: gcr-cleaner
              image: "europe-docker.pkg.dev/gcr-cleaner/gcr-cleaner/gcr-cleaner-cli:latest"
              imagePullPolicy: IfNotPresent
              args:
                - -repo
                - "europe-west1-docker.pkg.dev/project-id/container-registry"
                - -recursive
                - -allow-tagged
                - -tag-filter
                - "^v?(\\d+\\.?){3}-\\d+$"
                - -keep
                - "3"
                - -grace
                - "24h"
              env:
                - name: GCRCLEANER_TOKEN
                  value: "hard coded token get by  gcloud auth print-access-token"
          restartPolicy: Never

Is there any chance to run gcr-cleaner-cli in this way ? I'm already using this strategy with node and python applications to authenticate them to other google services like Cloud Trace and Cloud Storage and it's work fine. At the moment to run a cleanup one time per week i'm updating the env var GCRCLEANER_TOKEN with an hard coded token ... but is a really dirty job 😭
Have a nice day 😃

Can you confirm that WI is configured correctly on the pod by replacing the container with gcloud and running gcloud auth list and gcloud info?

gcloud auth list
            Credentialed Accounts
ACTIVE  ACCOUNT
*       scm-maestroconnect-shared.svc.id.goog

To set the active account, run:
    $ gcloud config set account `ACCOUNT`

gcloud info
Google Cloud SDK [359.0.0]

Platform: [Linux, x86_64] uname_result(system='Linux', node='gcr-cleaner-demo-manual-vjdd8-zw6c2', release='5.4.129+', version='#1 SMP Thu Jul 8 19:57:33 PDT 2021', machine='x86_64', processor='')
Locale: ('en_US', 'UTF-8')
Python Version: [3.7.3 (default, Jan 22 2021, 20:04:44)  [GCC 8.3.0]]
Python Location: [/usr/bin/python3]
Site Packages: [Disabled]

Installation Root: [/usr/lib/google-cloud-sdk]
Installed Components:
  alpha: [2021.09.24]
  cloud-firestore-emulator: [1.13.0]
  kpt: [1.0.0-beta.5]
  bigtable: []
  app-engine-python-extras: [1.9.94]
  bq: [2.0.71]
  pubsub-emulator: [0.5.0]
  beta: [2021.09.24]
  cloud-datastore-emulator: [2.1.0]
  cloud-spanner-emulator: [1.3.0]
  datalab: [20190610]
  core: [2021.09.24]
  app-engine-go: [1.9.71]
  app-engine-java: [1.9.91]
  cbt: [0.10.1]
  gsutil: [5.2]
  app-engine-python: [1.9.94]
  local-extract: [1.3.1]
System PATH: [/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/google-cloud-sdk/bin/]
Python PATH: [/usr/bin/../lib/google-cloud-sdk/lib/third_party:/usr/lib/google-cloud-sdk/lib:/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload]
Cloud SDK on PATH: [False]
Kubectl on PATH: [/usr/bin/kubectl]

Installation Properties: [/usr/lib/google-cloud-sdk/properties]
User Config Directory: [/root/.config/gcloud]
Active Configuration Name: [default]
Active Configuration Path: [/root/.config/gcloud/configurations/config_default]

Account: [scm-maestroconnect-shared.svc.id.goog]
Project: [scm-maestroconnect-shared]

Current Properties:
  [core]
    account: [scm-maestroconnect-shared.svc.id.goog]
    disable_usage_reporting: [True]
    project: [scm-maestroconnect-shared]

Logs Directory: [/root/.config/gcloud/logs]
Last Log File: [/root/.config/gcloud/logs/2021.09.28/<IP_ADDRESS>504.log]

git: [git version 2.20.1]
ssh: [OpenSSH_7.9p1 Debian-10+deb10u2, OpenSSL 1.1.1d  10 Sep 2019]

Hmm okay so it's definitely getting the correct service account... I may need to add the special dance to support WIF.

I updated to the latest client libraries and confirmed this is working now.

Hello everyone,
I'm trying to deploy the GCR cleaner CLI using Kubernetes cronjob. I created the service account with the required IAM bindings but I still have the permission problem here, because I didn't declare this part of the deployment:
              env:
                - name: GCRCLEANER_TOKEN
                  value: "hard coded token get by  gcloud auth print-access-token"

So my question is how I can set this environment variable automatically?
Can I export a key on the service account and then put that to the secret manager and use that secret as a value of this environment variable?

Hello, if your service account binding (the service account created in the cluster with the service account created on GCP) you don't need to use the env variable GCRCLEANER_TOKEN.

@xpicio Thanks for your quick response!
So I think something is wrong on my terraform and kubernetes declarations:
my terraform:
resource "google_service_account" "ar_cleaner" {
  account_id   = "ar-cleaner"
  display_name = "Artifact Registry Cleaner Account"
}

resource "google_artifact_registry_repository_iam_binding" "artifact_registry_admin" {
  provider = google-beta

  depends_on = [
    google_service_account.ar_cleaner
  ]

  project    = "My project name that includes AR"
  repository = "my-repo-name in the AR"
  location   = "us-east1"

  role = "roles/artifactregistry.repoAdmin"

  members = [
    "serviceAccount:${google_service_account.ar_cleaner.email}"
  ]
}

resource "google_service_account_iam_binding" "service_account_workload_indentity" {
  depends_on = [
    google_service_account.ar_cleaner
  ]

  service_account_id = google_service_account.ar_cleaner.name
  role               = "roles/iam.workloadIdentityUser"

  members = [
    "serviceAccount:${local.project_id}.svc.id.goog[default/${google_service_account.ar_cleaner.account_id}]",
  ]
}

my k8s job:
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/instance: ar-cleaner
  name: ar-cleaner
  namespace: default
---
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: ar-cleaner-prod
spec:
  schedule: 40 14 * * *
  concurrencyPolicy: Forbid
  startingDeadlineSeconds: 180
  suspend: false
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
  jobTemplate:
    metadata:
      labels:
        app.kubernetes.io/name: ar-cleaner
        app.kubernetes.io/instance: ar-cleaner
    spec:
      template:
        spec:
          serviceAccountName: ar-cleaner
          containers:
            - name: ar-cleaner
              image: "us-docker.pkg.dev/gcr-cleaner/gcr-cleaner/gcr-cleaner-cli"
              imagePullPolicy: IfNotPresent
              args:
                - -repo
                - "My Repo Address"
                - -grace
                - "1920h"
          restartPolicy: Never

Is there any problem with these configurations?

It seems you missed the annotation on k8s ServiceAccount (oops .. i missed it too posting the issue 😄)
metadata:
  annotations:
    iam.gke.io/gcp-service-account<EMAIL_ADDRESS>

Thanks a lot, it worked 💯


Some possible QOL additions [enchancement]

Sorry, idk where to find API docs to new tile system for adequate write and connect functions, but i can suggest some improvements:

Floating windows always on top:
In theory, we can add window role for black/whitelisted apps (client.resourceClass, if i right understand code)
Or make another list for app, what's we need to guaranteed been floating

Prevent change screen, when retiling
As i see, we has func desctopChange with checking client.screen, but now on retiling it can change current app screen to main. Maybe we need add function for checking selected screen on retile, orr add suboption for app for remember it.

Add possiblity to save/remove user templates
Now we has only 3 default template on tile management screen. Idk, where find access to this, but if possible, we can realize this with create 2 new lists: 1 with user templates and second with default user, what's replace default list, if we has our custom templates, and add func to checking, for prevent user remove defaults.

Rearranging tiling inside areas and in global screen area through key combos (if possible)

Some code improvements
Like replace black/whitelists and some another lists from Array to Map's/Set, for prevent addition of same names and redundant rechecking through loops

I can give you a general idea about some of these suggestions right now, but some of the possible ones may not be implemented for a while because I have school tomorrow.

This is the purpose of the blacklist, and floating windows are always on top, at least in the latest release (0.2.2). Window roles kind of work, kind of don't on Wayland.
I cannot test this as I do not own more than 1 screen, can you be more specific?
This functionality is provided through KWin, and there's not really anything I can do about it with this script. I believe there is functionality to save layouts somewhere, though.
I can probably come up with something
Unfortunately, I need to check every individual element in the blacklist because I need to see if the strings include each other. I have code in place for a blacklist cache, which uses a set to see if that type of window has already been checked. This should somewhat improve performance.

A lot of keyboard shortcuts were added with v0.3.0. Try some of them out if you'd like, and see if there are any more you need.

Seems like combos not work under wayland (not tested on x11)
Also idea for improvement - add possibility lo remember app position in grid. If we has some apps, whats we launch on autostart, will be good to remember and restore his arrangement on session start.
Also there no publik API from kde? Ill be heppy to join on project, but you does work in blind... meh. You a hero

Keyboard shortcuts work for me, have you updated your script and shortcuts? I know for a fact that they won't work (along with most other things) on X11.
I don't think there's any way to remember app position through a script, as scripts don't offer any persistent data that I know of other than configs.

as i see, in tileClient func, you checking free position through loop
If i understand righ, tiling list it array of arrays, t.tiles.length is option of current subtile, and t.tiles is position, and all list seems like [tile, [tile, [tile, [etc...]]]] (if i understand, it also a reason, why you can work only with binary windows)
for save current app position, we can add option for required apps, and save count data from this loop into cache or something like. And for restoration, just use counter for app.
like, while count != 0 make new subArr, if subpos = 0, place here, else make new and place here

seems like it just didn't catch any input. i bind untile/retile into meta+f, but it similar to any combinations

мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Config Updated
мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: useWhitelist == false
мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: blacklist == krunner,yakuake,zerotier-gui,steam,gamescope,spectacle,dolphin,org.kde.polkit-kde-authentication-agent-1,org.kde.kdesu,octopi-sudo,xdg-desktop-portal-kde,org.freedesktop.impl.portal.desktop.kde,lutris,yakuake,org.qbittorrent.qBittorrent,org.kde.plasmashell,org.kde.kdialog,pamac-installer,electron
мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: tileDialogs == false
мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: borders == 1
мар 21 17:44:23 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: invertInsertion == true
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Config Updated
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: useWhitelist == false
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: blacklist == krunner,yakuake,zerotier-gui,steam,gamescope,spectacle,dolphin,org.kde.polkit-kde-authentication-agent-1,org.kde.kdesu,octopi-sudo,xdg-desktop-portal-kde,org.freedesktop.impl.portal.desktop.kde,lutris,yakuake,org.qbittorrent.qBittorrent,org.kde.plasmashell,org.kde.kdialog,pamac-installer,electron
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: tileDialogs == false
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: borders == 1
мар 21 17:44:25 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: invertInsertion == true
мар 21 17:44:28 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client WebCord
мар 21 17:44:34 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client firefoxdeveloperedition
мар 21 17:44:38 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client org.kde.konsole
мар 21 17:44:48 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: WebCord was moved out of a tile
мар 21 17:48:06 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client org.telegram.desktop
мар 21 17:48:30 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop minimized
мар 21 17:48:30 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop unminimized
мар 21 17:48:31 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop minimized
мар 21 17:48:32 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop unminimized
мар 21 17:48:32 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop minimized
мар 21 17:48:33 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop unminimized
мар 21 17:48:43 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop minimized
мар 21 17:48:43 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client org.telegram.desktop unminimized
мар 21 17:52:09 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved out of a tile
мар 21 17:52:29 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved back into a tile without windows
мар 21 17:52:35 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client vscodium
мар 21 17:52:38 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Removing client vscodium
мар 21 17:53:35 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: org.telegram.desktop was moved out of a tile
мар 21 17:53:37 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: org.telegram.desktop was moved back into a tile without windows
мар 21 17:53:39 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: WebCord was moved back into a tile without windows
мар 21 17:53:41 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: org.telegram.desktop was moved back into a tile without windows
мар 21 17:53:43 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: org.telegram.desktop was moved back into a tile without windows
мар 21 17:53:45 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: org.telegram.desktop was moved back into a tile without windows
мар 21 17:54:29 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved out of a tile
мар 21 17:54:38 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved back into a tile without windows
мар 21 17:54:39 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved back into a tile without windows
мар 21 17:56:53 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Tiling client systemsettings
мар 21 17:56:57 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client systemsettings minimized
мар 21 17:56:58 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client systemsettings unminimized
мар 21 17:56:59 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client systemsettings minimized
мар 21 17:56:59 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: Client systemsettings unminimized
мар 21 17:57:03 deathbyte-pc kwin_wayland[1768]: js: Autotile DBG: firefoxdeveloperedition was moved back into a tile without windows

also i see, autoretiling works not all times. maybe it depends to this broke function call, or not in design now:
when i move apps to a second screen, or untile this, tiling can doesnt apply automaticaly. I think, it can depends by moving with system shortcuts like meta-shift-arrow, whats make window go out from tile layout.
For this case, i think will be good to add event-handler, whats call tile function on move, or tile all windows on screen, what's haven't flag "keep above"

I know why the shortcut duplicated, it's because I changed the internal shortcut ID with update 0.3.0. You can go into your ~/.config/kglobalshortcutsrc and delete the entry that just says "RetileWindow"
All I can say for the other issues is that they work on my machine. I can look at it later.

Are the shortcuts still broken because they are overwritten by other applications, or could you find a fix?