RFC: add support for tegra tk1 (tegra124) machine

Just an RFC for now to see if this is something you would be willing take in the main layer. There is still room for improvement but this is the majority of the work done. Let me know your thoughts on it.
Boot and CUDA application tested on a TK1 Development board.
Notable missing support:

Flashtool type image
cudnn/visonworks support
X11 integration (binaries installed, but our image doesn't use X11 so untested)

A major quirk is that its built using the Linaro GCC 4.9 compiler support form meta-linaro-toolchain, this is due to CUDA 6.5 only supporting the GCC 4.x series compilers. It's very hard to work around as the C++ ABI changed in GCC 5.x which means the pre-compiled binary CUDA libs won't link if a newer compiler with additional workarounds is used (days were wasted on fighting this!).

Overall, this looks great.
I'm not sure what to do about the gcc 4.9 dependency - we have a similar problem with CUDA 8.0, which isn't compatible with gcc 6, but at least gcc 5.x is still available in oe-core morty/master.
I'm traveling at the moment, but I'll give these changes a try when I return. Many thanks!

 In our layer I sed out the unsupported error and with a few choice GCC flags you can get CUDA apps to compile with GCC 6. However with the ABI breakage between 4 and 5 you can't do that, so I can't even hack it to get it to build with a currently supported oe-core GCC. I'll keep ticking it over and ask around to see if anybody has come across something similar.

I've been through some test builds and, modulo a few tweaks, things look good.
For kernel builds, I've added a patches-l4t-r21.5 branch to my linux-tegra repo and added a few patches so the the kernel builds with gcc 5 or 6 as the host compiler and gcc 5 as the cross compiler.  With that branch in place, I think we can collapse the separate kernel recipes back into one.
I tweaked the mesa-related bbappends to avoid collisions for the tk1 builds, mirroring what I did for tx1.
For CUDA builds, I had success using gcc 5 with two approaches:

adding -D_GLIBCXX_USE_CXX11_ABI=0 to CXXFLAGS for any recipes compiling C++ code that might be used by a CUDA recipe
configuring the compiler and runtime with --with-default-libstdcxx-abi=gcc4-compatible
I had to delete the compiler version check in CUDA's host_config.h header file, too, of course.

How does that sound?  I can probably get to merging this in with these modifications over the weekend.

Sounds great to me, good spot on the gcc4-compatible, that's what I was missing before and hence having trouble linking with nvlibs old ABI, everything else new ABI. If you want to push a testing branch I can also give it a whirl here.

I pushed a tegra-k1-wip branch.  It's missing the patch of host_config.h to remove the compiler version check, and still needs some additional cleanup.
I'm not sure whether the compiler config modification or the CXXFLAGS setting is the better approach, both are in there at the moment.

I may be wrong here but I expect you would only need the compiler config modification, using the CXXFLAGS is redundant I think. However, I don't think you could use only the CXXFLAGS as then all the other binaries in the system would have the new ABI and then the CUDA apps wouldn't be able to link with system libs.
I'll give the branch a go and report back if it builds before I get off today ;)

Yes, you're right, and I mentioned it because of the redundancy.  The extra CXXFLAGS setting shouldn't break anything, though, and I'll get it cleaned up before merging.

OK, I can get CUDA apps to compile with GCC5 but GCC6 explodes, so we need a versioning in there to default to 5 as current master is default 6. What happens when 5 drops out of master I'm not sure... cross that bridge when we come to it.

Yeah, when I get some time I'll see if I can make gcc6 work as well.  Thanks!

Merged manually.  Many thanks!


Fix/attributes coherence

Storing dataset and variables attributes in .zcollection only

Attributes are removed at insertion
Attributes are restored at load

Fixing partitions listing for top level type partitioning

test_collection/test_insert_failed now fails, it might be due to a caching problem.

Thanks a lot for your contribution.


How to handle iterative/different screenProps

I'm wondering if I'm missing something, it seems like I should be possible to pass different props to the children of a navigator, but screenProps makes that rather confusing... For instance, if I want to have a dynamic set of tabs, with dynamic content that's passed through props, I currently have no idea how I'd do that. Is there a reason this would be bad, or is this already possible?

You shouldn't do that. It makes it impossible to optimize anything. Connect your individual screens instead of the root screen. If you really want to pass different props, just pass all of them in the object. All screens receive all props and they can choose what to use.


Web servers use more CPU than expected

walrus_web_server, ros_package_web_server, rosbridge_server, and tf2_web_republisher all appear to idle at about 8.5% CPU usage each when no web page is loaded

tf2_web_republisher issue should be solved by RobotWebTools/roslibjs#144
All other servers are based on tornado...

After more investigation it looks like most nodes were exhibiting this behavior. It also only occurs when running in simulation. It probably has to do with /clock (http://answers.ros.org/question/29425/rospy-horrible-performance-with-sim_time/)


Detect zero-width space and similar problematic characters?

We recently ran into an issue where some pasted code resulted in an undefined local variable or method "\u200B". It was within a deploy script so wasn't noticed in development.
(200B is a zero-width space: https://www.fileformat.info/info/unicode/char/200b/index.htm)
Is this something that RuboCop should warn of? Or would it be out of scope?

@andyw8 Can you provide a stripped-down example that shows the issue? It sounds as if the case should be covered by https://docs.rubocop.org/en/stable/cops_naming/#namingasciiidentifiers

Sorry, false alarm. The Naming/AsciiIdentifiers cop detects this but but had been disabled for this particular project.

These are some gnarly errors to deal with. We had a related issue where some SendGrid e-mails always failed to send due to invalid e-mail address, but when checking the address in the console, it looked fine.
Turns out the customer was copy-pasting e-mails from some other application that included a zero-width space when doing so. Took me the better part of one afternoon to get to the root cause. 😂


cloud-init no longer working.

Hi guys, I've been reading the issues and can't get my head around the fix needed to be able to run cloudinit templates. Luckily by old system still works, but I'm trying to implement it on a second promox system and I guess since some update it has broken. Could anyone please give feedback on what I am doing wrong?
I was able to make it so it at least starts creating the VMs, but now I get the error "Boot failed: no bootable disk." I can't seem to figure out what I am doing wrong.
terraform {
  required_providers {
    proxmox = {
      source  = "telmate/proxmox"
      version = "3.0.1-rc1"
    }
  }
}

provider "proxmox" {
  # url is the hostname Add /api2/json at the end for the API
  pm_api_url = "http://<IP_ADDRESS>:8006/api2/json"

  # api token id is in the form of: <username>@pam!<tokenId>
  pm_api_token_id = "terraform@pam!new_token_id"

  # this is the full secret wrapped in quotes.
  pm_api_token_secret = "x"

  # leave tls_insecure set to true unless proxmox SSL
  pm_tls_insecure = true
}

variable "vm_configs" {
  description = "Configuration for VMs"
  type        = map

  default = {
    velociraptor = {
      name        = "velociraptor"
      memory      = 2048
      ip_address  = "<IP_ADDRESS>"
      cores       = 2
      storage     = "local-lvm"
      storage_size = "10G"
    },
    plaso = {
      name        = "plaso"
      memory      = 4096
      ip_address  = "<IP_ADDRESS>"
      cores       = 2
      storage     = "local-lvm"
      storage_size = "20G"
    }
    # Add other VM configurations as needed
  }
}

resource "proxmox_vm_qemu" "vms" {
  for_each = var.vm_configs

  name       = each.value["name"]
  target_node = var.proxmox_host
  clone       = var.template_name

  agent    = 1
  os_type  = "cloud-init"
  cores    = each.value["cores"]
  sockets  = 1
  cpu      = "host"
  memory   = each.value["memory"]
  scsihw   = "virtio-scsi-pci"
  bootdisk = "scsi0"

   disks {
    virtio {
      virtio0 {
        disk {
          size            = 20
          cache           = "writeback"
          storage         = "local-lvm"
        }
      }
    }
  }

  network {
    model  = "virtio"
    bridge = "vmbr0"
  }

  lifecycle {
    ignore_changes = [
      network,
    ]
  }

  ipconfig0 = "ip=${each.value["ip_address"]}/24,gw=<IP_ADDRESS>"

  sshkeys = <<EOF
  ${var.ssh_key}
  EOF
}

@JGHLab check #915. I had the same issue.
@Tinyblargon answer:
resource "proxmox_vm_qemu" "instance" {
// omitted for brevity
  cloudinit_cdrom_storage = "local-lvm"
  ciuser = "root"
// omitted for brevity
}

@JGHLab virtio0 is a disk in the template as well?

@JGHLab looks like you have a mismatch between the bootdisk and the disks definition. You probably need to change the bootdisk to virtio0 or change the disks definition to be scsi like below. I had the same problem with cloning, the template disk was scsi0 but TF was creating a virtio0 disk:
  disks {
    scsi {
      scsi0 {
        disk {
          size            = 20
          cache           = "writeback"
          storage         = "local-lvm"
        }
      }
    }
  }

I seem to be having the same issue, it looks like it is deleting the cloud-init drive and adding 2 cdrom drives
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide1"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

@JGHLab Did adding cloudinit_cdrom_storage = "local-lvm" to your terraform fix the issue?
@hanley-development I see you already have the cloudini_cdrom_storage, are you using version 3.0.1-rc1 of the provider? You should have something like this in your terraform definitions:
terraform {
  required_providers {
    proxmox = {
      source = "Telmate/proxmox"
      version = "=3.0.1-rc1"
    }
  }
  required_version = ">= 0.14"
}

I suspect this is an issue from 2.9.14 or earlier that was fixed in 3.0.1-rc1 because IIRC the cloudinit drive was switched from using ide1 to using ide2 in that release.

@hestiahacker
yes I have it in my provider.tf
terraform {
  required_version = ">=0.13.0"
  required_providers {
    proxmox = {
    source = "Telmate/proxmox"
    version = "3.0.1-rc1"
    }
  }
}

After updating my clone with the following the issue was resolved
boot = "order=scsi0;ide2"
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide2"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template2"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

After updating my clone with the following the issue was resolved
boot = "order=scsi0;ide2"
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide2"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template2"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

When it comes to my setup, adding boot = "order=scsi0;ide2" didn't helped. Still cloudinit is deleted and receive empty cdrom without cloudinit.

local_file.cloud_init_network-config_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creation complete after 0s [id=bbbb0db273574b7267fed45ea998655ffc26a2e0]
local_file.cloud_init_network-config_file[0]: Creation complete after 0s [id=584397ad1c649775dfef64cff2484d781972e34c]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Creating...
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m20s elapsed]

https://github.com/sonic-networks/terraform/tree/master/proxmox/sonic

After updating my clone with the following the issue was resolved
boot = "order=scsi0;ide2"
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide2"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template2"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

When it comes to my setup, adding boot = "order=scsi0;ide2" didn't helped. Still cloudinit is deleted and receive empty cdrom without cloudinit.

local_file.cloud_init_network-config_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creation complete after 0s [id=bbbb0db273574b7267fed45ea998655ffc26a2e0]
local_file.cloud_init_network-config_file[0]: Creation complete after 0s [id=584397ad1c649775dfef64cff2484d781972e34c]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Creating...
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m20s elapsed]

https://github.com/sonic-networks/terraform/tree/master/proxmox/sonic

boot = "order=scsi0;ide3"
The above worked for me

After updating my clone with the following the issue was resolved
boot = "order=scsi0;ide2"
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide2"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template2"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

When it comes to my setup, adding boot = "order=scsi0;ide2" didn't helped. Still cloudinit is deleted and receive empty cdrom without cloudinit.

local_file.cloud_init_network-config_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creation complete after 0s [id=bbbb0db273574b7267fed45ea998655ffc26a2e0]
local_file.cloud_init_network-config_file[0]: Creation complete after 0s [id=584397ad1c649775dfef64cff2484d781972e34c]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Creating...
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m20s elapsed]

https://github.com/sonic-networks/terraform/tree/master/proxmox/sonic

boot = "order=scsi0;ide3"
The above worked for me

And how you set the cloudinit in that case? On the template when setting qm set <id> --ide2 local-lvm:cloudinit, you put --ide2 or --ide3 ?

After updating my clone with the following the issue was resolved
boot = "order=scsi0;ide2"
resource "proxmox_vm_qemu" "brick-layer00" {
    name = "brick-layer00"
    desc = "Automation Node"
    vmid = "400"
    target_node = "pve1"
    bios = "ovmf"
    scsihw = "virtio-scsi-pci"
    boot = "order=scsi0;ide2"
    agent = 1
    bootdisk = "scsi0"
    hotplug  = "network,disk,usb"
    clone = "ubuntu-2204-template2"
    full_clone = true
    cores = 2
    sockets = 1
    cpu = "host"
    memory = 2048

    network {
      bridge = "vmbr0"
      model = "virtio"
    }

    disks {
      scsi {
        scsi0 {
          disk {
            size = 32
            storage = "ceph-replicate"
            iothread = false
            emulatessd = true
            discard = true
            backup = true
           }
        }
      }
    }

    os_type = "cloud-init"
    ciuser = "mhanl"
    cloudinit_cdrom_storage = "ceph-replicate"
    cipassword = var.cipassword_var
    ipconfig0 = "ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>"
    sshkeys = var.ssh_key_var

}

When it comes to my setup, adding boot = "order=scsi0;ide2" didn't helped. Still cloudinit is deleted and receive empty cdrom without cloudinit.

local_file.cloud_init_network-config_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creating...
local_file.cloud_init_user_data_file[0]: Creation complete after 0s [id=bbbb0db273574b7267fed45ea998655ffc26a2e0]
local_file.cloud_init_network-config_file[0]: Creation complete after 0s [id=584397ad1c649775dfef64cff2484d781972e34c]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Creating...
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m20s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m30s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m40s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [1m50s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m0s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m10s elapsed]
proxmox_vm_qemu.cloudinit["srv-app-1"]: Still creating... [2m20s elapsed]

https://github.com/sonic-networks/terraform/tree/master/proxmox/sonic

boot = "order=scsi0;ide3"
The above worked for me

And how you set the cloudinit in that case? On the template when setting qm set <id> --ide2 local-lvm:cloudinit, you put --ide2 or --ide3 ? Because when changed, having template previously generated with --ide2 setup I received an error
╷
│ Error: error updating VM: 500 invalid bootorder: device 'ide3' does not exist', error status: {"data":null} (params: map[agent:1 bios:seabios boot:order=scsi0;ide3 cicustom:user=local:snippets/user-data_vm-srv-app-1.yaml,network=local:snippets/network-config_vm-srv-app-1.yaml cores:4 cpu:host hotplug:network,disk,usb ide2:none,media=cdrom kvm:true memory:8192 name:srv-app-1 net0:virtio=00:1E:67:01:10:01,bridge=skynet numa:false onboot:false scsi0:vms:vm-100-disk-0,replicate=0,ssd=1 scsihw:virtio-scsi-pci sockets:1 tablet:true vmid:100])
│
│   with proxmox_vm_qemu.cloudinit["srv-app-1"],
│   on main.tf line 1, in resource "proxmox_vm_qemu" "cloudinit":
│    1: resource "proxmox_vm_qemu" "cloudinit" {
│
╵

That helped me to make screenshot of the changes it wanted to do in WebGUI view. So I guess I need to generate template again to set it up on --ide3 ?
    - name: Settings for Cloudinit
      tags: cloudinit
      block:

        - name: Set fact for cloudinit disk to check if exists
          ansible.builtin.set_fact:
            cloudinit_image: "{{ cloudinit_image | default([]) + [item] }}"
          loop: "{{ qm_config.results }}"
          when: not item.stdout is search('vm-{{ item.item.template_id}}-cloudinit')

        - name: CloudInit results
          ansible.builtin.debug:
            var: cloudinit_image
            verbosity: 2

        - name: Add cloud-init image as CDROM
          ansible.builtin.command: "qm set {{ item.item.template_id }} --ide2->3 // <- Here // local-lvm:cloudinit"
          loop: "{{ cloudinit_image }}"
          when: cloudinit_image is defined

For me none of those solutions doesn't work. Still waiting for someone who will have cicustom with snippet approach instead of those limited ciuser, cipassword and so on.

@electropolis This issue is about the "Boot failed: no bootable disk." error, not anything related to cicustom. If you're having some issue specific to using cicustom, can you open a ticket about it with a minimal example that others can use to replicate the issue?
I looked at the terraform code you linked to and it seemed to have a lot of things that were not portable, such as running some security command (which others don't have) to search for a password to set an environment variable. We all have our own, deployment-specific things like this that are not portable, but when posting on the issue tracker, the common convention is to make a small, portable example to make it easy for people to provide help. Very frequently, just the process of trying to create this minimal example will allow you to determine the issue and solve it without ever having to open or comment on a ticket.
I recently added a template to help with bug reporting, which you can find here: https://github.com/Telmate/terraform-provider-proxmox/pull/950/files
You should be able to change the vars.tf file and deploy that example. If that works as expected, add just the part that is causing the problem and post that. I'll pull down those files, reproduce the issue, and we can move closer to a solution.
Please understand that I'm not doubting your having a problem, or that there very well may be a bug in the code that is causing it. But I'm not able to recreate it, so I'm asking for your help in doing so and trying to keep the issue tracker organized to reduce everyone's frustration as best I can. :heart:

I already crated the issue.

This should be resolved in the latest build #959 has an example.

With this code, it works :
proxmox_vm_qemu.tf :
resource "null_resource" "cloud_init_user_data_file" {
  connection {
    user        = "root"
    private_key = var.root_private_key
    host        = var.prx_node
    port        = 22
  }

  provisioner "file" {
    content = templatefile(
      "../files/cloud-init/cloud-init.cloud_config_user.tftpl",
      {
        hostname            = var.vm_name,
        user                = var.adm_username,
        password            = var.adm_pwd,
        ssh_authorized_keys = var.ssh_authorized_keys,
      }
    )
    destination = "/var/lib/vz/snippets/user_data_vm-${var.vm_name}.yml"
  }

  triggers = {
    hostname            = var.vm_name,
    user                = var.adm_username,
    ssh_authorized_keys = var.ssh_authorized_keys,
    password            = var.adm_pwd,
  }
}

resource "null_resource" "cloud_init_network_data_file" {
  connection {
    user        = "root"
    private_key = var.root_private_key
    host        = var.prx_node
    port        = 22
  }

  provisioner "file" {
    content = templatefile(
      "../files/cloud-init/cloud-init.cloud_config_network.tftpl",
      {
        ip_dns = var.ip_dns,
      }
    )
    destination = "/var/lib/vz/snippets/network_data_vm-${var.vm_name}.yml"
  }

  triggers = {
    ip_dns = var.ip_dns,
  }
}

resource "proxmox_vm_qemu" "main" {
  name                   = var.vm_name
  target_node            = var.prx_node
  clone                  = "cirocky9tpl"
  desc                   = "Rocky Linux 9 VM fully cloned from cirocky9tpl"
  agent                  = 1
  cores                  = 4
  define_connection_info = false
  force_create           = true
  memory                 = var.vm_memory
  onboot                 = true
  qemu_os                = "l26"
  scsihw                 = "virtio-scsi-single"

  disks {
    scsi {
      scsi0 {
        disk {
          size    = 50
          storage = "local"
          replicate            = true
        }
      }
    }
  }

  network {
    bridge  = "vmbr1"
    model   = "virtio"
    macaddr = var.vm_mac
  }

  os_type = "cloud-init"

  ciuser                = var.adm_username
  cipassword            = var.adm_pwd
  sshkeys = var.ssh_authorized_keys
  cloudinit_cdrom_storage = "local"
  cicustom = "user=local:snippets/user_data_vm-${var.vm_name}.yml,network=local:snippets/network_data_vm-${var.vm_name}.yml"

  provisioner "remote-exec" {
    connection {
      user                = var.adm_username
      private_key         = var.adm_private_key
      host                = self.name
      bastion_host        = var.bind_ip_address
      bastion_port        = var.bind_ssh_port
      bastion_user        = var.bind_ssh_user
      bastion_private_key = var.bind_ssh_private_key
    }
    inline = [
      "ip a"
    ]
  }

  depends_on = [
    null_resource.cloud_init_user_data_file,
    null_resource.cloud_init_network_data_file,
  ]

  lifecycle {
    replace_triggered_by = [
      null_resource.cloud_init_user_data_file,
      null_resource.cloud_init_network_data_file,
    ]
  }
}

cloud-init.cloud_config_user.tftpl :
#cloud-config
hostname: ${hostname}
fqdn: ${hostname}
manage_resolv_conf: true
user: ${user}
password: ${password}
ssh_authorized_keys:
  - ${ssh_authorized_keys}
chpasswd:
  expire: False
timezone: Europe/Paris
locale: fr_FR.UTF-8
keyboard:
  layout: fr
  variant: oss
package_upgrade: false
packages:
  - qemu-guest-agent
  - firewalld
  - bash-completion
runcmd:
  - sudo nmcli d disconnect eth0 && sleep 2 && sudo nmcli d connect eth0
  - sudo systemctl enable --now firewalld
output:
  init:
    output: "> /var/log/cloud-init.out"
    error: "> /var/log/cloud-init.err"
  config: "tee -a /var/log/cloud-config.log"
  final:
    - ">> /var/log/cloud-final.out"
    - "/var/log/cloud-final.err"

@LeoShivas  strange combination of using cicustom with ci from proxmox. Why do you use ssh-keys twice ? One in user-data and second in sshkeys = var.ssh_authorized_keys

@JGHLab looks like you have a mismatch between the bootdisk and the disks definition. You probably need to change the bootdisk to virtio0 or change the disks definition to be scsi like below. I had the same problem with cloning, the template disk was scsi0 but TF was creating a virtio0 disk:
  disks {
    scsi {
      scsi0 {
        disk {
          size            = 20
          cache           = "writeback"
          storage         = "local-lvm"
        }
      }
    }
  }

Thank you @jaket91-1, after matching disk with my template, now it work and no duplicate unused disk.

@LeoShivas ok I understand. So you can use the link provided by @Tinyblargon and it works with manual compilation of the provider from master branch. Than you can use pure cicustom


Nodes for tree-view

[Backend] - Model and implement node-like-system for retrieving surveys in order to recreate tree view on frontend

Semi-finished


Conversion protocol conventions

Has this been discussed on swift-evolution yet?  If not, please start a discussion there.

Yes, i posted a draft a day or two ago.  It received a few positive replies but not a lot of discussion.  Is that ok or should I try to restart the thread now that we're in the business week?

The proposal has been discussed, dissected, and reconstructed on swift-evolution, and was then updated in considerable depth.


Load test

Added a flag to get the cli tool to export the transaction to stdout only, without broadcasting it on tendermint
Created a load test that calls the cli tool, creates a transaction and uses it to load the network (see Tendermint Load Testing Framework)

Can you add a short paragraph in the readme explaining how this works?

Can you add a short paragraph in the readme explaining how this works?

Done


Ideas for optimizing performance

This issue is to collect some ideas on how it can be optimised when the need arises.

Reuse hashes for messages.
Reduce nested table calls.

✅ Reuse hashes for messages.


Renamed EqualityComparer property to ReferenceLoopEqualityComparer

Minor tweak, but renaming it, I feel, better communicates how the serializer is going to use the EqualityComparer. Thoughts?

I'm ok with the current name. It might be used to compare objects for other features in the future.


Installation instructions

In the book you state that this will do a complete installation of kinetic, rod, and tb3 components:
$ wget https://raw.githubusercontent.com/ROBOTIS-GIT/robotis_tools/master/install_ros_kinetic.sh
$ chmod 755 ./install_ros_kinetic.sh
$ bash ./install_ros_kinetic.sh

Does that procedure take care of all the steps that are in the TUrtlebot3 Wiki at this url: http://emanual.robotis.com/docs/en/platform/turtlebot3/pc_setup/#pc-setup
Because a single comprehensive master install script would be really nice!

Hi @pitosalas
Do you think it's better to have everything installed at once?
I would like to have some flexibility. :)

I ask because the install of ROS is so delicate that when I see two different procedures in totally different places, I wonder whether they are different, one is obsolete, or one is preferred.

The two installation methods mentioned above are the same. The install_ros_kinetic.sh file installs only the ROS.

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.


GIFs don't embed

It's exactly what it sounds like, GIFs on Twitter don't embed using pxTwitter at the moment

That was an easy fix actually


[add-resource] New Plugin/Theme

I would like to add my new plugin/theme to the Grav Repository.
Here are the project details: bobrocke/topicmenu

Thanks done! Should show up within the hour!


KubeDNS for kubernetes 1.6 Corrections

Get kubedns running for v1.6.
Noticed some typos in the config.
Also, some updates based on kubernetes proper example.
Need to add rbac for kubedns also.

Seems to be working even with the following log "errors":
I0524 19:59:16.295871       1 dns.go:581] Query for "kubernetes.default.svc.cluster.local.", exact: false
I0524 19:59:16.296035       1 dns.go:810] Not a federation query: len(["kubernetes" "default" "svc" "cluster" "local"]) != 4+len(["local" "cluster"])
I0524 19:59:16.296091       1 dns.go:701] Found 1 records for [local cluster svc default kubernetes] in the cache
I0524 19:59:16.296189       1 dns.go:708] getRecordsForPath retval=[{Host:<IP_ADDRESS> Port:0 Priority:10 Weight:10 Text: Mail:false Ttl:30 TargetStrip:0 Group: Key:/skydns/local/cluster/svc/default/kubernetes/33626633626263}], path=[local cluster svc default kubernetes]
I0524 19:59:16.296249       1 dns.go:610] Records for kubernetes.default.svc.cluster.local.: [{<IP_ADDRESS> 0 10 10  false 30 0  /skydns/local/cluster/svc/default/kubernetes/33626633626263}]
I0524 19:59:17.627567       1 dns.go:434] No service for endpoint "kube-controller-manager" in namespace "kube-system"
I0524 19:59:17.627634       1 dns.go:434] No service for endpoint "kube-controller-manager" in namespace "kube-system"
I0524 19:59:17.694156       1 dns.go:434] No service for endpoint "kube-scheduler" in namespace "kube-system"
I0524 19:59:17.694194       1 dns.go:434] No service for endpoint "kube-scheduler" in namespace "kube-system"
I0524 19:59:19.643691       1 dns.go:434] No service for endpoint "kube-controller-manager" in namespace "kube-system"
I0524 19:59:19.643715       1 dns.go:434] No service for endpoint "kube-controller-manager" in namespace "kube-system"
I0524 19:59:19.702628       1 dns.go:434] No service for endpoint "kube-scheduler" in namespace "kube-system"
I0524 19:59:19.702646       1 dns.go:434] No service for endpoint "kube-scheduler" in namespace "kube-system"

those are static pods so probably aren't getting installed in a manner that DNS is expecting.  I'm fine with filing a bug on them and carrying on.

merged


Cannot import module bitpay, because it's not a correct python package

There is a bug in this package resulting in a ImportError. There should be a init.py file inside the bitpay directory in order to be a python package.

this should be fixed in 2.3.4


remove gitignored files

These files are gitignored, and should not be in source control. I suspect some of them were responsible for https://github.com/bitcoin-hivemind/hivemind/issues/82. After a make clean, building on macOS was successful.

I'm going through this right now

Looks good to me, and it still builds fine on Linux :+1:

Nice!


msrest and msrestazure dependencies not installed

Is it just me, or does this package not install dependencies?

installed via pip3 install azure
from azure.common.credentials import UserPassCredentials resulted in ImportError: No module named 'msrest'
installed msrest via pip3 install msrest
from azure.common.credentials import UserPassCredentials resulted in ImportError: No module named 'msrestazure'
installed msrest azure via pip3 install msrestazure
from azure.common.credentials import UserPassCredentials finally worked

Hi @freefood89 ,
I saw rare situations where msrest(azure) dependencies are not installed. I think it's related to this pip issue:
https://github.com/pypa/pip/issues/988
Because msrest(azure) in a sub-dependencies of an azure-common extension called autorest. But since some other package does not need the extension, it seems that if pip sees an azure-common dependency before it sees azure-common[autorest] dependency, it does not install the extension.
Thank you for the feedback, I will try to find a smart way to make this more predictable.

I seem to have the same problem. I initially did: pip install azure==2.0.0rc5 and tried to run https://github.com/ansible/ansible/blob/devel/contrib/inventory/azure_rm.py but get:
[terraform@pc001 ~]$ ./azure_rm.py
The Azure python sdk is not installed (try 'pip install azure==2.0.0rc5') - No module named msrestazure.azure_exceptions

[terraform@pc001 ~]$ pip install azure==2.0.0rc5
Requirement already satisfied (use --upgrade to upgrade): azure==2.0.0rc5 in /usr/lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): azure-storage==0.32.0 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-servicebus==0.20.2 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-servicemanagement-legacy==0.20.3 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-batch==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-graphrbac==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): python-dateutil in /usr/lib/python2.7/site-packages (from azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-nspkg in /usr/lib/python2.7/site-packages (from azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): futures in /usr/lib/python2.7/site-packages (from azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): requests in /usr/lib/python2.7/site-packages (from azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-common in /usr/lib/python2.7/site-packages (from azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-scheduler==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-compute==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-keyvault==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-notificationhubs==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-cdn==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-powerbiembedded==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-redis==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-commerce==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-cognitiveservices==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-resource==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-storage==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-authorization==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-batch==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-network==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-logic==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-web==0.30.0rc5 in /usr/lib/python2.7/site-packages (from azure-mgmt==0.30.0rc5->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): six>=1.5 in /usr/lib/python2.7/site-packages (from python-dateutil->azure-storage==0.32.0->azure==2.0.0rc5)
Requirement already satisfied (use --upgrade to upgrade): azure-mgmt-nspkg in /usr/lib/python2.7/site-packages (from azure-mgmt-scheduler==0.30.0rc5->azure-mgmt==0.30.0rc5->azure==2.0.0rc5)

[terraform@pc001 ~]$ pip install msrestazure
Requirement already satisfied (use --upgrade to upgrade): msrestazure in /usr/lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): msrest>=0.4.0 in /usr/lib/python2.7/site-packages (from msrestazure)
Requirement already satisfied (use --upgrade to upgrade): chardet>=2.3.0 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): certifi>=2<IP_ADDRESS> in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): enum34>=1.0.4 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): keyring>=5.6 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): isodate>=0.5.4 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): requests>=2.7.0 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): requests-oauthlib>=0.5.0 in /usr/lib/python2.7/site-packages (from msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): secretstorage; sys_platform == "linux2" or sys_platform == "linux" in /usr/lib/python2.7/site-packages (from keyring>=5.6->msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): oauthlib>=0.6.2 in /usr/lib/python2.7/site-packages (from requests-oauthlib>=0.5.0->msrest>=0.4.0->msrestazure)
Requirement already satisfied (use --upgrade to upgrade): pycrypto in /usr/lib64/python2.7/site-packages (from secretstorage; sys_platform == "linux2" or sys_platform == "linux"->keyring>=5.6->msrest>=0.4.0->msrestazure)

mrestazure was not installed as a dependency during the initial install of pip install azure
Some versioning:
OS: Red Hat Enterprise Linux Server release 6.8 (Santiago)
PIP: pip 8.1.2 from /usr/lib/python2.7/site-packages (python 2.7)
Please note @lmazuel The above post is simply to showcase and inform that installing azure does not include all dependencies in specific situations as you've previously observed; the contrib script is out of scope for this section. (The fix was to point the contrib script to python 2.7 instead of 2.6).

Thanks for the feedback @elemantalcode !

Just ran into this same issue.
"pip install msrestazure" corrected the problem for me.
OS: Centos 7.2
PIP: 8.1.2
Python 2.7.5

@lmazuel
I install Azure Python SDK from the git source, but running into the same issue when "import azure.mgmt.redis"
I use the following commands to install SDK for Python3.5
git clone git://github.com/Azure/azure-sdk-for-python.git
cd azure-sdk-for-python
python3 setup.py install

This issue is now 6 months old, and there's still not a clean way to install the azure sdk for python. Any updates on this?

Hi, I have also problems with dependencies with Ansible (running Ubuntu 16.04 LTS)  with Azure SDK for python. I tried everything described on this page. nothing works. Still get the message   Try pip install azure==2.0.0rc5- No module named common.credentials

@trondhindenes I started to change the way I install msrestazure, replacing azure-common[autorest] that creates the problem by an explicit msrestazure dependency, see for instance this setup.py file. Each time I release a new package, I take this opportunity to update it. I thought it was too soon to answer here, but I didn't forget and eventually all packages will be fixed. This is NOT a fix in the azure meta-package, since as a meta-package it does not have a dependency on msrestazure.
@squasta if you have a message "no module named common.credentials", then you're not into this issue. This issue installs correctly azure.common.credentials BUT doesn't install the underlying package to make it work, so you got a msrestazure error that can be fixed installing manually msrestazure. If you still think you have the issue mentioned here, please provide a stackstrace. If not, please create a new issue with your specific stacktrace.

Thanks for the update @lmazuel , good to know that the issue is being worked on.

@trondhindenes I pushed a commit and changed them all:
https://github.com/Azure/azure-sdk-for-python/commit/3dc2d4f8047ce5b8421572eda9278a5c1a72ea3c
GH has closed the issue automatically, I guess it's fair, but the fix will be published package per package only each time I publish new release. I will not publish new version of everything just for this. However, an update of azure-mgmt-compute and azure-mgmt-resource is planned for early February, so since it's the most used packages, problem will disappear quickly.
Please feel free to still comment here, even closed, and I re-open it if necessary.

I am using Mac (10.12.3) and python 2.7.13
I manually run
sudo pip install msrest
sudo pip install msrestazure
sudo pip install "azure==2.0.0rc5"
All succeed but I still got :
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Do you have azure==2.0.0rc5 installed? Try pip install azure==2.0.0rc5- No module named msrest.serialization"}

I have the same issue , any update on this ?

I have problem with Python 2.7.10 , Python 2.7.13  got succeeded.

It's a random issue, depending on the order pip process the dependencies. This is not related to Python version (unless Python is shipped with pip and pip is newer with 2.7.13, it's possible).
New packages released since 01/2017 does not have the issue. I cannot fix the old one, where you might have to pip install msrestazure manually.
thanks,

Cheers @lmazuel , working fine , thanks for the help.

So I just installed azure az new installation on fedora 24, got the same error and cannot use module at all. Any advise ?

Hi @ment0s
You don't have the same error, since the missing module is azure.common.credentials, not msrestazure. Could you provide a more detailled description of the messages you got from pip during the installation?

pip output : http://pastebin.com/RgQDNF0s
With ansible from git I get these errors :
"Do you have azure==2.0.0rc5 installed? Try pip install azure==2.0.0rc5- cannot import name integer_types"

@ment0s , ansible using old version of python, just check in verbose mode, to execute any pthyon script ansible will use /usr/bin/python or something esle ?
/usr/bin/python --version
python --version
/usr/bin/lib/python --version
if you have done brew install then Cellar/bin/python --version
Compare which python is used while executing ansible python script, i have soft link 2.7 python library to /usr/bin/python, since ansible is using that location for me.

I have the same problem with a fresh install on MacOS
TASK [Create a resource group] ************************************************* fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Do you have msrestazure installed? Try pip install msrestazure- No module named msrest.serialization"}
Python version is 2.7.13.
My pip list is the following (only relevant packages).
azure (1.0.3) azure-batch (0.30.0rc5) azure-common (1.1.4) azure-graphrbac (0.30.0rc5) azure-mgmt (0.20.2) azure-mgmt-authorization (0.30.0rc5) azure-mgmt-batch (0.30.0rc5) azure-mgmt-cdn (0.30.0rc5) azure-mgmt-cognitiveservices (0.30.0rc5) azure-mgmt-commerce (0.30.0rc5) azure-mgmt-common (0.20.0) azure-mgmt-compute (0.20.1) azure-mgmt-keyvault (0.30.0rc5) azure-mgmt-logic (0.30.0rc5) azure-mgmt-network (0.20.1) azure-mgmt-notificationhubs (0.30.0rc5) azure-mgmt-nspkg (2.0.0) azure-mgmt-powerbiembedded (0.30.0rc5) azure-mgmt-redis (0.30.0rc5) azure-mgmt-resource (0.20.1) azure-mgmt-scheduler (0.30.0rc5) azure-mgmt-storage (0.20.0) azure-mgmt-web (0.30.0rc5) azure-nspkg (2.0.0) azure-servicebus (0.20.1) azure-servicemanagement-legacy (0.20.2) azure-storage (0.20.3) msrest (0.4.7) msrestazure (0.4.7)
I tried uninstalling and re-installing azure, azure-mgmt, msrest and msrestazure, but this didn't work.
Any idea about what is wrong?

Hi @mkesselaers
Can you open a python interpreter and type "import msrest"?
Thanks,

Hi @lmazuel,
This doesn't give any error, which seems like everything is fine.
Best regards,
Maarten

If you are able to import msrest from a Python interpreter but Ansible can't, might be a problem with Ansible (it's Ansible right?)

Yes, you're right. But since the error that I've got was found on this thread, I thought that it would be best to post it here.
How did the other OPs solved it?

Try running,
ansible-playbook  test.yml  -e ansible_python_interpreter=/usr/local/opt/python/bin/python2.7

Hi @rkumar357 ,
This works indeed.
I presume that Ansible now defaults to python 3 as interpreter?
Thanks for your help!
Best regards,
Maarten

Cheers !!! for ansible i belive  python 2 is deafult.

@rkumar357 @mkesselaers Ansible does not support Python 3 at all for now (see on PyPI). So only option here is Python 2.7. I don't know how Ansible is defining his shebang, but if for some reason it starts with Py3 by default you will be in trouble.
I didn't know Ansible has a ansible_python_interpreter (thanks @rkumar357 :)). I will keep this in mind and that's indeed the correct solution.

I am running Ansible (<IP_ADDRESS> or <IP_ADDRESS>) inside a docker container and am receiving the same msrestazure.azure_exceptions error despite applying the various fixes noted above.
ansible-playbook -vvvv  -i /home/ansible/ansible/contrib/inventory/azure_rm.py generatevm.yml -e ansible_python_interpreter=/usr/local/opt/python/bin/python2.7
...
ERROR! Attempted to execute "/home/ansible/ansible/contrib/inventory/azure_rm.py" as inventory script: Inventory script (/home/ansible/ansible/contrib/inventory/azure_rm.py) had an execution error: The Azure python sdk is not installed (try `pip install 'azure>=2.0.0rc5' --upgrade`) - No module named msrestazure.azure_exceptions

pip show azure
Name: azure
Version: 2.0.0rc6
Summary: Microsoft Azure Client Libraries for Python
Home-page: https://github.com/Azure/azure-sdk-for-python
Author: Microsoft Corporation
Author-email<EMAIL_ADDRESS>License: MIT License
Location: /usr/local/lib/python2.7/dist-packages

Looking at the azure_rm.py code, it looks like it is just failing upon import (I'm not a python dev... yet).  From what I have read, providing the reference to the path where azure_rm.py lives should be sufficient for python to pick up the remaining libraries listed in the import... though I'm not certain.
I cloned https://github.com/ansible/ansible on Friday, so that shouldn't be out of date, and I've tried both rc5 & rc6 pip installs of azure .
Any tips would be appreciated.

Hi @aaronjones
Could you try:
/usr/local/opt/python/bin/python2.7 -c "import msrestazure; print(msrestazure.__version__)"

slightly embarrassing, but delivers the same result and same problem. (I didn't realize python wasn't installed in that same location, so it must have defaulted to what was installed)
Using the following command:
/usr/bin/python2.7 -c "import msrestazure; print(msrestazure.version)"
results in:
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named msrestazure

So, you can install msrestazure this way (assuming you have sudo access):
sudo /usr/bin/python2.7 -m pip install msrestazure

Sorry for the delay in response.  It has at least moved me forward to a credentials error, so that is progress.  I guess the ansible documentation or possibly the sdk readme may need updating to reflect the requirement of installing mrestazure separately?
https://docs.ansible.com/ansible/guide_azure.html
I'm guessing this is just an issue running ansible inside of docker given other positive responses above?

msrestazure is not supposed to be installed separately, but we got issues in the past with pip. We fixed that in recent packages, but likely you got it with old version :(
Installing the future azure 2.0.0rc7 should definitely fix the issue by forcing all packages to be in a recent version where the issue is fixed.

I just ran into this on OS X 10.11.6. Just in case someone else runs into this, my (seemingly) underlying issue was that I installed ansible via brew, which installs python 2.7.13 as a dep. Running pip install azure* via local python 2.7.10 ended with the ImportError: No module named 'msrestazure' issue.
The fix was to ensure that I'm using python 2.7.13 - I went ahead and updated my $PATH to include /usr/local/Cellar/python/2.7.13/bin. After this, running sudo pip install azure==2.0.0rc5 succeeded.

My solution is a workable way to solve No module named msrest.serialization issue.
In OS X 10.13.6, run brew instabll ansible to install the latest ansbile package (my case is 2.6.2)
Ansible 2.6.2 has its own python 2.7.15 in /usr/local/Cellar/ansible/2.6.2/libexec/bin directory
Need to use its pip script to install azure packages
/usr/local/Cellar/ansible/2.6.2/libexec/bin/pip install azure to fix the azure dependences.

I have a similar issue, not sure if its a compatibility issue between msrest version and azure commons , tried reinstalling, installling on a new venv. I am trying to use azure azure_rm_keyvault_info - Here is the error trace - Any suggestions would help >
  File "/var/folders/yh/9flcl8g13pd0fvdwq3_vpnb9t15tdk/T/ansible_azure_rm_keyvault_info_payload_90lcafqh/ansible_azure_rm_keyvault_info_payload.zip/ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common.py", line 222, in <module>
    from msrest.serialization import Serializer
ModuleNotFoundError: No module named 'msrest'
fatal: [localhost]: FAILED! => {
    "changed": false,
    "invocation": {

azure-keyvault-secrets 4.4.0 requires msrest>=0.6.21, but you have msrest 0.4.29 which is incompatible.
azure-mgmt-keyvault 0.30.0rc6 requires azure-common[autorest]==1.1.4, but you have azure-common 1.1.28 which is incompatible.
tried installing them manually
pip install "azure-common[autorest]==1.1.4"
pip install "msrest==0.6.21"
no luck


Syntax Color C++

Colors do not match the same as Vscode in C++.
NVIM:

VSCODE:

Please check this one out https://github.com/nvim-treesitter/nvim-treesitter
It's a plugin that give you a better syntax highlighting.

Can confirm the colors look like in the "VSCODE" picture when using treesitter.
Make sure to run its setup in your config or else its not enalbed, a minimal example:
require("nvim-treesitter.configs").setup({
    auto_install = true,
    highlight = {
        enable = true
    }
})


bugFix the problem that the parquet reader reads the missing sub-columns of the struct and fails. (#38718)

bp #38718
Proposed changes
Fix the problem that the parquet reader reads the missing sub-columns of the struct and fails.
for example :
suppose we have a column array<struct<a:int>> . And this column has two data
[{1},{2},{3}]
[{4},{5}]

Then we add a subcolumn b to the struct . Now the column structure is like this array<struct<a:int,b:string>>
The expected data for the query is as follows, instead of an error  :
[{1,null},{2,null},{3,null}]
[{4,null},{5,null}]

run buildall


Hardware capability warnings.

Description
There are multiple tools supplied by the WebGL API for detecting whether an operation is supported by the current hardware. For example, getParameter can be used to determine the maximum number of texture units. It would be helpful if Umbra automatically checked certain operations against their relevant parameters.
Possible solution
No response
Details
No response

Too expensive to automate.


Add links to a serie of articles in Netty documentation

Hi,
I suggest to add to Netty documentation a serie of articles I wrote about Netty. They are in French, but if you don't speak French then Google translate is your friend.
Netty (1/6)
https://groups.google.com/d/msg/techos/7OhdFbsHOjI/RZs1Ncs0EAAJ
Netty (2/6) : Modèle de programmation (programming model)
https://groups.google.com/d/msg/techos/BArGTlHcgu0/VKdJdz12EAAJ
Netty (3/6) : Recyclage de la mémoire (memory recycling)
https://groups.google.com/d/msg/techos/pPKiuxd3RkU/-vG78bDHEAAJ
Netty (4/6) : que faire avec (what to do with it)
https://groups.google.com/d/msg/techos/BZxM5IKKXXk/iGQwqgwqEQAJ
Netty (5/6) : Étude de cas ; existant (case study)
https://groups.google.com/d/msg/techos/y5p_y8fHdYA/5aHXc4BuEQAJ
Netty (6/6) : Constatations ; conclusion (facts and conclusion)
https://groups.google.com/d/msg/techos/CGGil5VK4oQ/6DWDc4puEQAJ

@caillette you can add them to http://netty.io/wiki/related-articles.html by yourself.


Enhance label placement for lines

Labels are currently created at the starting point of a newly created line. This approach was taken to solve #533. Labels should be created in the middle and follow the curvature of a line. This enhancement will follow labeling standards in ArcMap and ArcGIS Pro.
Note: With this new approach, labels created for lines crossing the international dateline will be an issue (please see #533)

@kgonzago Can you provide additional information on how this change will affect circles, rings, and ellipses in #533

@lfunkhouser This feature will not affect those other shapes you mentioned; only lines.

@kgonzago please provide a level of effort to label the lines along the line drawn.

Closing. Current implementation will not be updated at this time.


Delete Flow

After more than 4½ years of valuable service, Flow's role as a type checker in our codebase is coming to an end.
This patch fully expunges Flow-based type checking, and converts the last few files to TypeScript. The Flow dependencies and config have also been removed, and while there I did some spring cleaning in other dependencies. The result is a codebase that's substantially leaner, hopefully faster to type check, and all round easier to work with.
There's some lingering Prismic refactoring I want to do (including explaining how it actually works in prose documentation!), so I won't close that ticket yet – but this does close https://github.com/wellcomecollection/wellcomecollection.org/issues/7302

I'm going to merge it so it lands on staging, just to avoid any epic merge conflicts by Tuesday. (And so everyone can benefit from the TypeScript shininess.) I've looked at some pages and run it through the "try all pages" tool, so 🤞


added grocy

Surely this needs some cleanup, but it works.

I don't think I'm going to use grocy for my grocery or chore needs. It's working, though, so you can either add it to d.ry or just delete it.

still planning on checking it out, thanks!

I rebased this on the simplified docker-compose.instance.yaml that comes from the whoami example (the one you used from d.rymcg.tech create is inferior and still needs work.) I added some of the extra env vars to docker-compose.yaml otherwise they were not seen.


modified static cursor to 2 , so that PDO ODBC works.  NOTE:  Might h…

…ave issues with cursors,  although I have not seen it yet.
This change was made to get php-pdo-odbc to work.  That is the unixODBC driver had issues with nuodb odbc driver when SQL_STATIC_CURSOR_ATTRIBUTES2 was set to 0.   The unixODBC tried to wrap our driver with another one and then I was getting [access violation]. invalid function pointers.   After making this change the wrapper was not installed and all worked.
I honest don't know what a valid value would be here.   As I'm not familiar with the ODBC spec.

I either didn't get notified about this or, more likely, didn't notice it.  I have no problem with making this change but, like Dirk, I have no idea what it means.  Maybe one of the SQL folks might know more about ODBC and what this change actually does?
@TheDistributor or @pflynnnuodb any ideas?
@dbutson-mdsol also please be sure to keep your Git commit subject lines to a reasonable length ( <= 70 chars or so).  Here you've put the entire git commit into one line, in the subject.


remove clam from error sigpam

?
Note that it was just using the clam to print "what kind of card is this,
ignore body"; this could also be e.g. [&1 &2]:+.sih
On Wednesday, 24 October 2018, ixv<EMAIL_ADDRESS>wrote:

Merged #863 https://github.com/urbit/arvo/pull/863 into
release-candidate.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/863#event-1924814458, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABxXhh-8rTNtnUZs-0zIhJ89HwJNus9vks5uoO2ogaJpZM4X5Hq2
.


K8SSAND-1576 ⁃ Expose metrics for different actions performed during reconciliation in K8ssandraCluster controller

What is missing?
The controller-runtime already exposes a Prometheus for us that provides several metrics like total number of reconciliations per controller and the duration of reconciliations. We need to expose additional metrics for various operations that the controller performs.
Note: Part of the work involved for this issue is to determine what metrics we want to expose. This may involve creating additional, follow up tickets.
As a starting point, we should expose metrics for operations that involve calls across remote cluster. We should also expose metrics for any operations that involve calls to the management-api.
Why do we need it?
We need observability for the work that the K8ssandraCluster work is doing. This will also give us better observability around remote k8s clusters as well as the management-api and Cassandra.
Environment

K8ssandra Operator version:
v1.1.1

**Anything else we need to know?**:

#456 is related.
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1576
┆priority: Medium

So there are a few ways to do this. Questions:

Should metrics on the number of times a given mgmt api endpoint has been called come from mgmt api or from the operator? My feeling is that if you want to track hits on an endpoint this normally gets done by the server rather than the caller.
What particular operations do we want to track? I'd think some options might be:

Creation of all resources (e.g. StatefulSets, Deployments, Services etc.)
Reconciliation runs for each CR.
Creation of CRs.

Then do we take the cross product with failures and time-to-complete (where available) for each of these operations? Or do we stick to counts?

We get a number of metrics for free from controller-runtime. It would be good to get those documented (if it isn't already somewhere).
I may be wrong but creation of individual resources feels too fine grained. I think the time to reconcile each of the main CRS (CassandraDatacenter, Reaper, and Stargate) makes sense. It would also be good to capture metrics for management-api calls and CQL calls.

I may be wrong but creation of individual resources feels too fine grained. I think the time to reconcile each of the main CRS (CassandraDatacenter, Reaper, and Stargate) makes sense. It would also be good to capture metrics for management-api calls and CQL calls.

Mostly agree. Resources creation also feels like it is a k8s responsibility, so I'm inclined to agree with you there.


Make the branch tekton-support can run GitHub actions

Signed-off-by: GitHub<EMAIL_ADDRESS>

Codecov Report

Merging #181 (8a93c31) into master (8d180cc) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master    #181   +/-   ##
======================================
  Coverage    5.37%   5.37%
======================================
  Files          75      75
  Lines       21098   21098
======================================
  Hits         1135    1135
  Misses      19890   19890
  Partials       73      73

Flag
Coverage Δ

unittests
5.37% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/client/devops/jenkins/credential.go
30.46% <0.00%> (ø)

Continue to review full report at Codecov.

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

/lgtm


[Change Request] Codeunit 8618 Config. Excel Exchange

Function IsImportFromExcelConfirmed checks GUI and HideDialog before actual parsing Excel file.
It would be correct to have TempConfigPackageTable being filled before exiting function if no user involvement is required.
At the moment if no request shown excel sheet is not processed.
local procedure IsImportFromExcelConfirmed(var TempConfigPackageTable: Record "Config. Package Table" temporary): Boolean
var
    ConfigPackageImportPreview: Page "Config. Package Import Preview";
begin
    // old code start
    // if GuiAllowed and not HideDialog then
    //      if ReadPackageTableKeysFromExcel(TempConfigPackageTable) then begin
    // old code end
    // new code start
    if ReadPackageTableKeysFromExcel(TempConfigPackageTable) then
        if GuiAllowed and not HideDialog then begin
    // new code end
            ConfigPackageImportPreview.SetData(SelectedConfigPackage.Code, TempConfigPackageTable);
            ConfigPackageImportPreview.RunModal;
            exit(ConfigPackageImportPreview.IsImportConfirmed);
        end;
    exit(true);
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Availability update: We will publish a fix for this issue in the next update for release 18.


Add Arduino build-CI + badges in readme.md

@ripred
I do not understand why the release badge in the readme.md file looks weird. Will investigate.


feat(ui): allow enable / disable auto updating for installed (cluster)packages

Closes #1091
📑 Description

✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information

@kosmoz  Done !

Alright @christophenne, Would we reopen this PR in future?

That's fine @christophenne
Can I work on adding the same feature to the CLI or should I wait?


⚠ Processors has degraded performance

In 9080b04, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 53 ms

Resolved: Processors performance has improved in d6f5f13.


Updated Dockerfile

This introduces a Dockerfile for Karapace based on debian:stable-slim, this base image was chosen because of its size and compatibility with glibc.
Things taken care by this PR:

Images with th opencontainers pre-defined labels
The container's entrypoint was fixed to have the main application as PID 1, so that signals are properly delivered to the app (and not to the spawning shell).
The image is running with a user named karapace instead of root.
The image is using multi-stage setup to produce the wheels in a builder image, which are then installed on the runtime image. This reduces the end image size.
There are separate Dockerfiles for the REST and the schema-registry. These images are only for convenience and completely reuse the existing cached layers.
The RUN commands have been chosen to optimized layer cache reuse. Dependencies are handled independently from the main app because they change less often, and the caching layers can be reused.
The idea here is to set the ground work for reusable builds. The direct dependencies are pinned which is a start, next step is to pin the full dependency closure.

I tested this with:
./container/build_image.sh HEAD latest
(cd container; sudo docker-compose up -d)

Unfortunately I didn't manage to run this with podman-compose, it seems the tool can't use images from local repositories.

I did a quick check on the available base images. Here are some notes:

Alpine: This seems like a bad idea. tl;dr the whells won't work because alpine uses musl instead of glibc
Debian: stable (currently Debian 10 buster) is around 48MB, buster slim is 27MB.
Fedora: 33 is at 64MB. There is no slim version.
Ubuntu: groovy is at 30MB.

and then we have the python specific versions of each of the base images mentioned above:

python:alpine is around 16MB, but again, it uses musl
python:slim-buster is around 42MB.

Would it work to list those files in .dockerignore to solve caching etc. and skip not wanted files from ending up into container image?

That is a good question, I didn't check that.

I didn't quite catch why you generated image both as karapace_registry and karapace_rest as those images have equal contents?

There are separate Dockerfiles for the REST and the schema-registry. These images are only for convenience and completely reuse the existing cached layers.

Would it work to just launch the image with different args depending on what mode you want to run?

Yes.

Looks good to me, also tested locally building with podman-docker. In my setup I did not need sudo however, so I was thinking should it be included in shell script or not...

Yeah, I was not sure how to about that either. I preferred to keep the sudo in the script because I didn't want to run the whole script with sudo, specially because the previous implementation was not using the .dockerignore file and had a few calls to rm. I suppose we should see how that will work when we integrate that with the CI. Otherwise I don't think it is a big deal.

Why do we need Dockerfile.f31?

Why do we need Dockerfile.f31?

We don't actually, I had it there because it was my first iteration based on f31. Removing it from the source tree, if we ever need it again it should be in the git history.


How to know which payment method is selected On Stripe iOS when using PaymentMethodsViewController

It should have a delegate method like below
public void PaymentMethodsViewControllerSelectedPaymentMethod(PaymentMethodsViewController paymentMethodsViewController,PaymentMethod paymentMethod)
{
//DismissViewController(true, null);
}
The one we have is which call when user selects method is
public void PaymentMethodsViewControllerFinished(PaymentMethodsViewController paymentMethodsViewController)
{
    }

But it does not give any payment method information Which I am gonna need to generate Token

I need the last method from above image this is from stripe documentation from iOS
func paymentOptionsViewController(_ paymentOptionsViewController: STPPaymentOptionsViewController, didSelect paymentOption: STPPaymentOption) {
// Save selected payment option
selectedPaymentOption = paymentOption
}

I found out we have An extension method
public void PaymentMethodsViewControllerSelectedPaymentMethod(PaymentMethodsViewController paymentMethodsViewController,IPaymentMethod paymentMethod)
{
    }

For IPaymentMethodsViewControllerDelegate But I do not know how to implement that method it's not in sample too
Can anybody help me in this ?
Thanks


select option is not working

after run
name string -select:option1,option2,option3
fields. blade.php file missing

name string select:option1,option2,option3 should be the correct way.


Add a basic test suite

This functionality uses a lot of native AWS functionality (Steps distributed maps, restoring s3 objects etc) - so I don't think it is possible to make a mock test setup.
But we should make a test suite that can run which creates actual temp objects in a bucket and then copies

There are some tests here and there - so we are in a better state - but still not quite as rigorous as I would like. Keeping this open


"Settings sync" screen appears

"Settings sync" screen appears on every time I start vscode.
I already removed your plugin but it still appears.
I hate it.
How do i get rid of it?
Very annoying

@alkurop Can you make sure that you've properly removed the extension? This can't happen if you did.

I tried to uninstall it and the uninstall fails.  Same with disable. I ended up having to manually remove the extension.  On a mac you can run rm -rf ~/.vscode/extensions/shan.code-settings-sync-3.4.0.  Just make sure the version in the extension name matches what version is on your machine.

Yep, shows up every time I restart vscode.   :(

Is there no way to stop it from opening every time? I like Settings Sync and want to keep it but this screen opening every time I open VS Code is really irritating!

Yes, we are planning to fix this issue in next version.
Get Outlook for iOShttps://aka.ms/o0ukef

From: N U R O ™<EMAIL_ADDRESS>Sent: Wednesday, July 17, 2019 7:54:41 PM
To: shanalikhan/code-settings-sync
Cc: Subscribed
Subject: Re: [shanalikhan/code-settings-sync] "Settings sync" screen appears (#963)
Is there no way to stop it from opening every time? I like Settings Sync and want to keep it but this screen opening every time I open VS Code is really irritating!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/shanalikhan/code-settings-sync/issues/963?email_source=notifications&email_token=ACC6HHCKU5G7IRLNHLM4F23P74XDDA5CNFSM4IEAVD62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2EPFQY#issuecomment-512291523, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACC6HHACESU7LCOGYEISVULP74XDDANCNFSM4IEAVD6Q.

Same for me. Very annoying for an otherwise excellent extension. Would be better if you could release a hotfix for this instead of planning a fix in the next version 😉

Until it's fixed, you should try this dirty hack...
Open ~/.vscode/extensions/shan.code-settings-sync-3.4.0/out/extension.js.
Search for:
OpenLandingPage=function()
It should look like this:
e.prototype.OpenLandingPage=function(){var e=this,t=this.webviews[0]
Add "return;" After the opening braces and before everything else:
e.prototype.OpenLandingPage=function(){return;var e=this,t=this.webviews[0]
This prevents the landing page from showing.

i have a different issue but even if i uninstall and also remove the extension from ~/.vscode/extensions/ when i install again, i dont get the regular setup procedure. is there some cache i dont know about?

Would be better if you could release a hotfix

We have found some other things to improve the Setup Guide and making the UX more better. Hold on we will release in next days. :)
thanks for patience, i'm getting alot of bad reviews and emails mentioning this thing only :smile:

i'm getting alot of bad reviews and emails mentioning this thing only

I'm not surprised.
This is why (if I were you) I'd release a hotfix to stop this bug and bad reviews happening, then make your improvements 😞

This is why (if I were you) I'd release a hotfix to stop this bug

There was a delay due to other issues during setup. We have improved the UX alot. It is fixed in v3.4.1. Let us know in case of query.

Upgraded to 3.4.1, yet still I get the Settings Sync screen.

U can disable it using the checkbox in the bottom right corner
Get Outlook for iOShttps://aka.ms/o0ukef

From: Daniel Reznicek<EMAIL_ADDRESS>Sent: Monday, July 22, 2019 11:57:13 PM
To: shanalikhan/code-settings-sync
Cc: Shan Khan; State change
Subject: Re: [shanalikhan/code-settings-sync] "Settings sync" screen appears (#963)
Upgraded to 3.4.1, yet still I get the Settings Sync screen.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/shanalikhan/code-settings-sync/issues/963?email_source=notifications&email_token=ACC6HHEP4YOVNZ6BFD62ILTQAX7ITA5CNFSM4IEAVD62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2Q2ODI#issuecomment-513910541, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACC6HHAHTXTJWQ4NAX2BQHLQAX7ITANCNFSM4IEAVD6Q.

Upgraded to v3.4.1, unchecked the checkbox bottom right still getting this welcome screen.  Am going to uninstall it 😞

unchecked the checkbox bottom right still getting this welcome screen

have you reset the settings? after unchecking it.
It should not appear once you uncheck the checkbox until you reset the settings.

This welcome screen is a really bad idea anyway, no idea why it should even be there. Extensions should be invisible in the background.  If I want to know more I can go to the extension and check out the home page

I don't know what you mean by "reset the settings".  I unchecked the box, quit and opened again. Then checked it, quit and opened again, then unchecked it, quit and opened again.  No matter what I did it kept appearing.  I've removed it now.  May reinstall at a later date if I need to sync between machines.

Okay, let me explain the steps.

Settings Sync UI will appear on startup automatically when you don't have Github token setup.
It will appear on upload/download when you have not configured Github token.
You can always disable the startup UI appearance while unchecking the Don't Show at Startup on the bottom right. It will disable startup appearance and will only show UI on upload/download ( when token not configured )
If you do the Sync: Reset Extension Settings it will reset the extension settings and will cause the UI to load once again on startup and you need to uncheck that box.

If you find other behaviour as intended, open issue for it, We will fix it.

Duplicate of #959


Angular 2 turotials are not working in ja.onsen.io/tutorial/

@anatoo @frankdiox
Reported by a user ( https://twitter.com/bj1024/status/807108546768748544 ).
See https://ja.onsen.io/tutorial/ and select an Angular 2 tutorial.
It will report an error GET https://ja.onsen.io/js/onsenui.system.js 403 () like:

@asial-matagawa I don't think we are actually supporting that URL, it's probably just a mistake. It's only tutorial.onsen.io, there is no Japanese version.

@frankdiox
Thank you. I will fix the links in onsen.io and ja.onsen.io.


install rally from  esrally-dist-0.8.1.tar.gz and benchmarking an existing cluster

I want to know after download esrally-dist-0.8.1.tar.gz, run the install.sh, wheather can run esrally, in my enviroments nothings happen...
I need benchmarking an existing cluster,  and just only use the esrally, Is it OK?

Hi @wuyunfeng, we reserve Github for bug reports and feature requests only. Please ask questions like these in the Rally forum instead. Thank you!

OK, @danielmitterdorfer . thanks


Interaction limit parameter for SolarPILOT

The interaction limit defines the radius around any given heliostat that blocking or shadowing is considered from any other heliostat. Providing a limit reduces the computational requirement of evaluating shadowing and blocking, but has the potential to introduce inaccuracy in assessing these losses.
Different heliostat layouts or geometries may require different limits to balance accuracy and computational expense. This PR introduces a parameter that replaces the hard-coded limit of 100 x (heliostat height). In SAM and SSC, the default value is assumed, and the parameter is not exposed in the SAM interface.
Closes #161.

Travis issue appears to have caused build failure. Going ahead with merge.


We should be catching failures to redact messages

https://github.com/Half-Shot/matrix-appservice-discord/blob/9c142916b872748c9c976a19b5c6db1f5989b0bd/src/bot.ts#L601

This is done in https://github.com/Half-Shot/matrix-appservice-discord/commit/1f6fdf416cc5468db5172b20bbfa37cd57848e33


adding +47 gives multiple duplicates

                        InternationalPhoneInput(
                          onPhoneNumberChange: onPhoneNumberChange,
                          initialPhoneNumber: phoneNumber,
                          initialSelection: phoneIsoCode,
                          enabledCountries: ['+46', '+47'],
                        ),

will give me 3 flags of norway

There are 3 entries for +47 dialing code:

Bouvet Island
Norway
Svalbard and Jan Mayen

Besides Norway are remote jurisdictions of Norway.

have you solve it? i have other country with multiple values as well.


build.gradle has wrong version of modules in doc

Lines 41:45 should be:
    doc 'org.firstinspires.ftc:Hardware:7.0.0'
    doc 'org.firstinspires.ftc:RobotCore:7.0.0'
    doc 'org.firstinspires.ftc:FtcCommon:7.0.0'
    doc 'org.firstinspires.ftc:OnBotJava:7.0.0'
    doc 'org.firstinspires.ftc:Inspection:7.0.0'

This is needed so extractJavadoc can be run to have the Javadoc locally

Yeah, that didn't get updated because official hosting of javadocs has migrated to https://javadoc.io/doc/org.firstinspires.ftc and, when late in the release process it was discovered that this was a leftover from prior releases the consensus was anyone experienced enough to know what this is for would know to change those version numbers if they wanted to extract javadoc locally.  Additionally all of the other versioning that is done in gradle is done via the tooling that produces the release.   But there's no existing tooling for updating that particular dependencies block.
We can consider adding that tooling, or perhaps remove that block entirely.   There's a download button on javadoc.io so if you really want local copies you can get them there.  I'm somewhat in favor of simplification over adding more tooling given that an alternative is readily available.

I think it could be pulled.   You can use Android Studio to create the
javadoc instead of gradle.   I am a big fan of simplifying by removing
unnecessary code.
On a related subject, I would be a strong supporter of simplifying the
gradle scripts to remove redundancy.  For example, while TeamCode uses the
root build.common.gradle, the FtcRobotController does not.
I am willing to help with this cleanup, but not sure what the best way to
do that is.   (I could do pull requests, but if there is a better way then
please let me know.)
--Alan
On Tue, Sep 21, 2021 at 2:57 PM Craig MacFarlane @.***>
wrote:

Yeah, that didn't get updated because official hosting of javadocs has
migrated to https://javadoc.io/doc/org.firstinspires.ftc and, when late
in the release process it was discovered that this was a leftover from
prior releases the consensus was anyone experienced enough to know what
this is for would know to change those version numbers if they wanted to
extract javadoc locally. Additionally all of the other versioning that is
done in gradle is done via the tooling that produces the release. But
there's no existing tooling for updating that particular dependencies block.
We can consider adding that tooling, or perhaps remove that block
entirely. There's a download button on javadoc.io so if you really want
local copies you can get them there. I'm somewhat in favor of
simplification over adding more tooling given that an alternative is
readily available.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FIRST-Tech-Challenge/FtcRobotController/issues/162#issuecomment-924295336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF3Y75VWSB23XMQDDPKBWDUDDITJANCNFSM5EPC7R3A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

That particular block was being used to generate the javadoc that was going up on GitHub pages, which as I mentioned isn't being used anymore since the move the Maven and the free scraping by javadoc.io.
The release process isn't set up for the tech team to be able to take pull requests on the public SDK repository as any changes on FtcRobotController are at risk of getting overwritten on the next release, and the goal, not always met, but the goal anyhow is to have just release commits in the commit history of FtcRobotController in order to keep the commit history as clean as possible.
The gradle in question is shared between the public SDK and the private development SDK and goes through a bit of a transformation as it's pushed to the release and some of what you see in the release is because of dependencies on how things are built in the private SDK and avoiding duplication there.   If you really want to contribute the best course of action is to get know the OpenFTC people.  Maybe find something there needs to be fixed.  The tech team has in the past taken contributions to OpenFTC and pulled them into the official SDK.   If your goal for anything is upstreaming, getting to know the principles there, and getting them onboard with what you want to do is the best path forward.

This is being tracked internally.  Thank you for you comments.


usage of require limits file size of json

If you use the "require" to read the .json file, it will limit the size of the json file. A streamed json parser, like JSONStream might improve the capability to read large files. Granted, this approach would not solve the memory usage issue for those files once they are memory resident, but it would give a little more headroom.

See also https://github.com/firebase/firebase-streaming-import

I don't have a suitable python environment on the machine that I'm using to run firebase. I've forked the repo and plan on sending a PR with what I have in mind.

I think this is resolved via https://github.com/firebase/firebase-import/pull/18. Another pull request is needed to update the documentation to reflect that the file-size limit is no longer 250mb, but is roughly the amount of available memory on the machine.


getTrailFromPDOMEvent should be graceful for event targets that are not Elements

This assertion in Input.ts is too strict:
      const target = ( domEvent.target as unknown as Element );
      assert && assert( target instanceof window.Element, 'target is not an Element', target );

The event target may be the window or the document. This is especially true for event forwarding from keyboardEventForwarding (phet-io). For our uses it is OK for this to be graceful and for getTrailFromPDOMEvent to return null if the event target is not an Element.

Right. in our meeting we found that document is a Node, so contains() works fine with it. I will commit soon.

There might be trouble here, window is not a Node but could be the value of event.target.

@jessegreenberg, I believe I coded around that with an instanceof check, and by "I" I mean I copied with @samreid and @matthew-blackman had already written.
Commits are above.
@samreid @matthew-blackman, is this going to work for you in PDL? This should be a straight forward cherry pick, but please let me know if you need anything more.

Right, thanks! Looks good.


feat(rust): add ockam relay delete subcommand

Current behavior
No current relay subcommand exists to delete a relay
Closes #4437

Proposed changes
Added ockam relay delete subcommand

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

Apologies for taking so much time in closing this.
Do let me know if there's anything I might have missed.
Thanks

Thank you for yet another contribution!
This PR looks good, It'll try to squeeze it in tomorrow's release, but I can't make any promises!


Backport 2.7: Add depends-ciphers.pl

Backport of #1919 to mbedtls-2.7
Compared to the original, a new commit was added to this backport to fix an issue found by the enhancement of depends-pk-algs.pl in 2.7, that was not present in 2.16.

This PR would require significant rework, and a consolidated dependency checking script is in the pipeline, so it's probably best to focus our efforts on the more general solution rather than on this PR.


CRM individual camera angles

Not really an issue, but potentially an improvement (although probably not possible with ComfyUI in one workflow).
6 camera angles are required to make a "good" model in CRM. Something I've noticed is that all camera angles generated are done in one go, but some my be good while others are awful; and the awful ones can break a better 3D model being generated.
Now, there isn't much consistency between each seed. One seed might generate the perfect angle visually on the right side camera, some anomalies on the back camera, and an absolute monstrosity for the top camera. On another seed, the left and top cameras might be pretty good, but now the right camera is completely messed up.
So my question is this: is it possible to do one camera angle at a time (not all 6 for sake of time and efficiency)? The idea is that I would then re-run until I get a good result, save out the image, move on to the next camera angle, repeat until I have all 6 angles, then collect the images as a batch, and finally run through CRM. Hopefully this would produce a better 3d mesh as there is some human element involved as to what looks right or not.
I'm pretty verbose in python but I started using ComfyUI a couple days ago and only today finally got 3D pack running (literal nightmare) - so there's a bit of a learning curve to make something like it myself in Comfy. I imagine it'd be simple enough to break up the 'CRM Images MVDiffusion Model' so it generates only one angle instead of a multiview (or maybe generate 10 outputs of the same angle with varying seed). In a separate workflow, you could batch load the images and then continue on with the 'CRM CCMs MVDiffusion Model' stage.
Is this possible? And if so, how could I do it?

Is it possible to do one camera angle at a time?
Yes, but not with CRM, because it is trained with fixed 6 views ad once and it cannot specify camera poeses, we can achieve more consistent result with fine-tuned video diffusion model
There is a way to enhance CRM result without fine-tune the model
FreeControl: Training-Free Spatial Control of Any Text-to-Image Diffusion Model with Any Condition
Or using Instruct pix2pix (ip2p) or SD model plus IP-Adapter to modify those few not too good view images directly
Let me know, if you any other questions, cheers :)


Laravel Vite cannot be used to bundle a custom theme stylesheet

Package
filament/filament
Package Version
v2.13.14
Laravel Version
v9.19
Livewire Version
No response
PHP Version
8.1.4
Bug description
The Vite directive outputs the entire HTML string instead of just the resource URL. This means when using a custom theme stylesheet as outlined in the documentation here, we're unable to use themes bundled by Laravel Vite as Filament is expecting just the URL.
This could now be more of a problem now that new Laravel installations come pre-installed with Laravel Vite instead of Laravel Mix.
One method to get around this issue for now is by publishing the base layout view, and replacing the default theme stylesheet in the head with the<EMAIL_ADDRESS>directive.
Example:

Steps to reproduce

Ensure you're using Laravel Vite to compile a custom theme stylesheet
Add the following code to your AppServiceProvider::boot

use Illuminate\Foundation\Vite;

Filament::serving(function() {
    Filament::registerTheme(app(Vite::class)(['resources/css/app.css']));
});

Relevant log output
No response

I want to add official support soon, but does #3004 work?


Windows Portable and Environment Variables

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Does the Windows Portable version of Uptime Kuma support Environment Variables yet? If so - should the .env file be placed in the "exe directory" / core?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
Windows Runtime v1.0.0
💻 Operating System and Arch
Windows 11
🌐 Browser
N/A
🐋 Docker Version
No response
🟩 NodeJS Version
No response

You can try putting it in the /core folder.
Be aware that the windows portable version is deprecated and will not be maintained. (#3935)

Closing as we have decided that the pain of supporting the windows PE version of our sofware is too much of a pain for us to shoulder.
We recommend switching to switch to the methods from our installation guide: https://github.com/louislam/uptime-kuma/wiki/🔧-How-to-Install


Make sure the docs folder is up to date with new structure

What
Check that the documentation inside the repository (in docs) are up to date with the new repository structure, especially:

the docs for releasing to npm
the docs for pushing a pre-release as a branch on Github
but also all the other pieces of documentation in there

Why
We're making substantial changes to our repository structure ahead of v5. We need to ensure that our docs reflect these changes so they can help future us and contributors appropriately.
Pushing a pre-release branch, especially, is really helpful for contributors as it allows them to install their changes as an npm package (without releasing to npm)
Who needs to work on this
Developers, Tech writers?
Who needs to review this
Developers, Tech writers?
Done when
### We've reviewed
- [ ] The npm release docs (both from main and from support branch)
- [x] The docs for making a pre-release on Github
- [ ] The rest of the docs

Closed by #3975 (the PR was referencing the wrong issue).